From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 01:33:57 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 49F5B16A417 for ; Sun, 19 Aug 2007 01:33:57 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 20FFA13C442 for ; Sun, 19 Aug 2007 01:33:57 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from [10.0.0.222] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id l7J1IiH7053482; Sat, 18 Aug 2007 18:18:49 -0700 (PDT) (envelope-from tim@kientzle.com) Message-ID: <46C79A74.9050703@kientzle.com> Date: Sat, 18 Aug 2007 18:18:44 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joerg Sonnenberger , "'freebsd-current@freebsd.org'" Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: RFC: #mtree signature X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 01:33:57 -0000 I'm experimenting with having bsdtar able to read mtree files and convert them into tar archives. This works quite well, although there is one stumbling block: libarchive likes to auto-detect formats and the current mtree format lacks any mandatory leading signature. Any concerns or thoughts about the following patch, which simply adds "#mtree" as the first line of every mtree file? I would also, of course, like to: * add this signature to the FreeBSD /etc/mtree/ files as a first step towards getting this convention to be more widely adopted and used, * update /etc/magic to reflect this convention, * get this added to NetBSD's "mtree" utility. Tim Kientzle Index: create.c =================================================================== RCS file: /usr/cvs/FreeBSD-CVS/src/usr.sbin/mtree/create.c,v retrieving revision 1.37 diff -u -r1.37 create.c --- create.c 29 Mar 2005 11:44:17 -0000 1.37 +++ create.c 18 Aug 2007 23:52:06 -0000 @@ -87,6 +87,7 @@ char dot[] = "."; int indent = 0; + (void)printf("#mtree\n"); if (!nflag) { (void)time(&cl); (void)gethostname(host, sizeof(host)); From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 02:43:04 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2610816A417 for ; Sun, 19 Aug 2007 02:43:04 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mx1.freebsd.org (Postfix) with ESMTP id AB06913C442 for ; Sun, 19 Aug 2007 02:43:03 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l7J2gxLR027329; Sun, 19 Aug 2007 12:42:59 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l7J2gwcp027328; Sun, 19 Aug 2007 12:42:58 +1000 (EST) (envelope-from peter) Date: Sun, 19 Aug 2007 12:42:58 +1000 From: Peter Jeremy To: Tim Kientzle Message-ID: <20070819024258.GA23080@turion.vk2pj.dyndns.org> References: <46C79A74.9050703@kientzle.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: <46C79A74.9050703@kientzle.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.16 (2007-06-09) Cc: "'freebsd-current@freebsd.org'" , Joerg Sonnenberger Subject: Re: RFC: #mtree signature X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 02:43:04 -0000 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-Aug-18 18:18:44 -0700, Tim Kientzle wrote: >Any concerns or thoughts about the following >patch, which simply adds "#mtree" as the first >line of every mtree file? Sounds like a good idea. I would suggest that if we're going to add a signature block, it include a version string in case we want to incompatibly change the mtree format at some future date. Maybe: "#mtree v1.0\n". --=20 Peter Jeremy --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGx64y/opHv/APuIcRAnHqAKCwFbowLdvPd7KyaR2ee77dWoXWIACaAgdg jzjKtL8c8332IR1/F0v/BXQ= =eUbY -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o-- From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 02:43:44 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6FBD116A418 for ; Sun, 19 Aug 2007 02:43:44 +0000 (UTC) (envelope-from william88@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.182]) by mx1.freebsd.org (Postfix) with ESMTP id 43F7913C46C for ; Sun, 19 Aug 2007 02:43:44 +0000 (UTC) (envelope-from william88@gmail.com) Received: by wa-out-1112.google.com with SMTP id m33so370761wag for ; Sat, 18 Aug 2007 19:43:44 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=Cy+L2ZQFGrN+Fj1tIJKpCSD3yc+vLC7ajXbk9jo1SiIWRB4JOydg0G85YoWrHJi/71XIVQ7Ds11GMd3jWnePHNaTesjyINOE60lV4fO+TbeTyvxLn9EavAUMuMLiZHKN439zVyNsD3FC1E+eswJNYCpcI6DqoWyIUWgv31Fimiw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=pwvlY3Hwfy7cE5ndJlCLcrvwMNTLKSQEr/3WiCDxxoreI9/kTJrVqC4sbG6eWQUw2O2WxnsL0OBfx9zxy3R6C0LY5/KR+VQMuI7VpNrXS0kTlKMazXSzNOFyod1aON314lLgZTvyQRzp9Ru9CJvgykIXYgLoic23HDExrDZvUlY= Received: by 10.114.159.1 with SMTP id h1mr178335wae.1187491423860; Sat, 18 Aug 2007 19:43:43 -0700 (PDT) Received: by 10.114.111.4 with HTTP; Sat, 18 Aug 2007 19:43:43 -0700 (PDT) Message-ID: <632825b40708181943l64662014w8c60535cb3380c0a@mail.gmail.com> Date: Sat, 18 Aug 2007 23:43:43 -0300 From: "William Grzybowski" To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_80868_31911850.1187491423798" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: mskc ethernet with acpi issue X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 02:43:44 -0000 ------=_Part_80868_31911850.1187491423798 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi! I have a Marvell Yukon 88E8038 PCI-E Fast Ethernet Controller running on a yesterday -CURRENT x86 SMP. I'm having an issue when booting with acpi enable with it, when i boot with acpi disable it works fine. I found some guys on google with the same probleam but without a solution and without answers. I tried to install -RELEASE but the kernel doesn't recognize the ethernet card. dmesg: mskc0: irq 16 at device 0.0 on pci2 mskc0: 0x4000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). mskc0: unknown device: id=0x00, rev=0x00 device_attach: mskc0 attach returned 6 I'm attaching my dmesg output and the acpidump hoping to help in anyway... Please let me know if there is anything that i can do. Thanks :) -- William Grzybowski ------------------------------------------ Jabber: william88 at gmail dot com Msn: william.grz at hotmail dot com Curitiba/PR ------=_Part_80868_31911850.1187491423798-- From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 03:01:32 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44DF016A417; Sun, 19 Aug 2007 03:01:32 +0000 (UTC) (envelope-from ken@tydfam.jp) Received: from ns.tydfam.jp (ns.tydfam.jp [61.197.228.42]) by mx1.freebsd.org (Postfix) with ESMTP id DBD5213C459; Sun, 19 Aug 2007 03:01:24 +0000 (UTC) (envelope-from ken@tydfam.jp) Received: from localhost (tyd3.sub.tydfam.jp [192.168.1.3]) by ns.tydfam.jp (8.14.1/8.14.1) with ESMTP id l7J3058n015377; Sun, 19 Aug 2007 12:00:05 +0900 (JST) (envelope-from ken@tydfam.jp) Date: Sun, 19 Aug 2007 12:01:36 +0900 (JST) Message-Id: <20070819.120136.41629169.ken@tydfam.jp> To: anrays@gmail.com From: Ken Yamada In-Reply-To: <864piweemc.fsf@santinel.home.ua> References: <20070815144804.GC5151@misty.eyesbeyond.com> <20070818.213208.74754361.ken@tydfam.jp> <864piweemc.fsf@santinel.home.ua> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91/3991/Sun Aug 19 09:31:39 2007 on ns.tydfam.jp X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.1 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on ns.tydfam.jp Cc: glewis@eyesbeyond.com, lists_freebsd_org@07.antispam.web-wahnsinn.de, freebsd-current@freebsd.org, freebsd-java@freebsd.org Subject: Re: Gcc bugs break java/jdk15 build? [Workaround] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 03:01:32 -0000 Does this mean that GCC 4.2.1 does not solve "loop optimization bug" pointed out by Andrey Chernov (http://docs.freebsd.org/cgi/getmsg.cgi?fetch=282888+0+archive/2007/freebsd-current/20070701.freebsd-current) on 4.2.0? Is it a good idea of adding -fno-tree-vrp to CFLAGS in /etc/make.conf to avoid this optimization bug for all compilation? (BTW, I leave -O3 of CFLAGS as is in make.conf and just added -fno-tree-vrp to the end of the line.) From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 03:23:53 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 344D916A41A for ; Sun, 19 Aug 2007 03:23:53 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id EAACE13C428 for ; Sun, 19 Aug 2007 03:23:52 +0000 (UTC) (envelope-from sam@errno.com) Received: from sam-lefflers-powerbook-g4-15.local ([10.0.0.178]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l7J3NqCe088504 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 18 Aug 2007 20:23:52 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <46C7B7C7.7060105@errno.com> Date: Sat, 18 Aug 2007 20:23:51 -0700 From: Sam Leffler Organization: Errno Consulting User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Jacob Hart References: <632825b40708171855u155d0195udb6994999de12d15@mail.gmail.com> <46C664D0.3060906@errno.com> <139a3a1b0708180019n183eeda6j493b0ca8eec2c4b4@mail.gmail.com> In-Reply-To: <139a3a1b0708180019n183eeda6j493b0ca8eec2c4b4@mail.gmail.com> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Atheros AR5006 abg minipci [really v0.9.30.3 support for 5418] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 03:23:53 -0000 Jacob Hart wrote: > Sam, > > I'm using the 0.9.30.3 hal on a recently built -CURRENT, and my > wireless is detected as shown: > > ath0: mem 0x90100000-0x9010ffff irq 17 at device 0.0 on pci2 > ath0: [ITHREAD] > ath0: using obsoleted if_watchdog interface > ath0: Ethernet address: 00:17:f2:e9:64:19 > ath0: mac 12.10 phy 8.1 radio 12.0 This doesn't look like an AR5006 part > > In my quest for a quieter notebook I've been experimenting with > powerd. The wireless connection works reliably if > debug.cpufreq.lowest sysctl is set to restrict the CPU frequency to > 1.16GHz or greater (it is a 2GHz core2 duo using the est driver), but > anything under that it begins to show some instability. > > At 1GHz and 875MHz the wireless connection will intermittently freeze. > I can usually resurrect the connection by forcing wpa_supplicant to > reassociate with the AP (from wpa_cli) or, if not, by restarting the > ath0 interface via /etc/rc.d/netif restart. > > At 750MHz I experience the same problem as above, but occasionally the > if_ath module must be unloaded and re-loaded, then the ath0 interface > brought back up before the driver will be able to associate with an > AP. > > At 500MHz i must always unload and reload the if_ath module. Scanning > usually works, but association with an AP is not guaranteed at this > speed; i'd estimate it works about 25% of the time. At speeds below > 500Mhz, it is not possible to scan or associate with an AP. > > Is this a known known issue with the driver or is it specific to my > system? Further, is there anything I can do to help track down the > problem? I've had one previous report of something similar. The 5418 support in 0.9.30.3 has known (serious) issues; this is one of them. I'm not likely to look at any ath issues until Oct-Nov. Sam > > -j > > On 8/18/07, Sam Leffler wrote: >> William Grzybowski wrote: >>> Hi, >>> >>> I got wireless minipci atheros ar5006 with -CURRENT. >>> Cant use it even with if_ndis and i didnt tried on stable/release yet. >>> dmesg: >>> >>> ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) >>> ath0: mem 0xd0000000-0xd000ffff irq 16 at device 0.0 on >>> pci3 >>> ath0: [ITHREAD] >>> ath0: unable to attach hardware; HAL status 13 >>> device_attach: ath0 attach returned 6 >>> >>> I tried to search about it on the history without success, does it means >>> this card isn't supported yey? could i do anything providing info to help? >>> Should I forward this message to another list? >> You can try the test hal in http://www.freebsd.org/~sam. Beware it is >> not a release (has not undergone full testing and has known issues). If >> the 0.9.30.3 hal doesn't work then your part is probably a 2425. >> Support for that part has been blocked waiting on Atheros for >1 month. >> No idea when it might show up. >> >> Sam >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> > > From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 05:14:10 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A9C316A419 for ; Sun, 19 Aug 2007 05:14:10 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from webmail23.mail.yandex.net (webmail23.mail.yandex.net [213.180.223.149]) by mx1.freebsd.org (Postfix) with ESMTP id 1F0E613C48A for ; Sun, 19 Aug 2007 05:14:09 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from YAMAIL (webmail23) by mail.yandex.ru id S2891890AbXHSFOC for (+ 1 other); Sun, 19 Aug 2007 09:14:02 +0400 X-Yandex-Spam: 1 Received: from [77.72.136.71] ([77.72.136.71]) by mail.yandex.ru with HTTP; Sun, 19 Aug 2007 09:14:01 +0400 From: "Andrey V. Elsukov" To: freebsd-current@freebsd.org MIME-Version: 1.0 Message-Id: <48941187500441@webmail23.yandex.ru> Date: Sun, 19 Aug 2007 09:14:01 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Type: multipart/mixed; boundary="----==--bound.4895.webmail23.yandex.ru" Cc: mav@freebsd.org Subject: panic when mpd4 starting X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 05:14:10 -0000 ------==--bound.4895.webmail23.yandex.ru Content-Transfer-Encoding: 7bit Content-Type: text/plain Hi, today i got a kernel panic when mpd4 starting. My system is CURRENT at the end of July. I use ULE, nfe(4) with polling. Backtrace attached. -- WBR, Andrey V. Elsukov ------==--bound.4895.webmail23.yandex.ru Content-Disposition: attachment; filename="bt.txt" Content-Transfer-Encoding: base64 Content-Type: text/plain; name="bt.txt" ClVucmVhZCBwb3J0aW9uIG9mIHRoZSBrZXJuZWwgbWVzc2FnZSBidWZmZXI6Cmtlcm5lbCB0cmFw IDEyIHdpdGggaW50ZXJydXB0cyBkaXNhYmxlZAoKCkZhdGFsIHRyYXAgMTI6IHBhZ2UgZmF1bHQg d2hpbGUgaW4ga2VybmVsIG1vZGUKY3B1aWQgPSAwOyBhcGljIGlkID0gMDAKZmF1bHQgdmlydHVh bCBhZGRyZXNzCT0gMHgxODgKZmF1bHQgY29kZQkJPSBzdXBlcnZpc29yIHJlYWQsIHBhZ2Ugbm90 IHByZXNlbnQKaW5zdHJ1Y3Rpb24gcG9pbnRlcgk9IDB4MjA6MHhjMDU4NWVlNQpzdGFjayBwb2lu dGVyCSAgICAgICAgPSAweDI4OjB4ZDNmNmRhNmMKZnJhbWUgcG9pbnRlcgkgICAgICAgID0gMHgy ODoweGQzZjZkYTg0CmNvZGUgc2VnbWVudAkJPSBiYXNlIDB4MCwgbGltaXQgMHhmZmZmZiwgdHlw ZSAweDFiCgkJCT0gRFBMIDAsIHByZXMgMSwgZGVmMzIgMSwgZ3JhbiAxCnByb2Nlc3NvciBlZmxh Z3MJPSByZXN1bWUsIElPUEwgPSAwCmN1cnJlbnQgcHJvY2VzcwkJPSAxMDIzIChpZmNvbmZpZykK cGFuaWM6IGZyb20gZGVidWdnZXIKY3B1aWQgPSAwClVwdGltZTogNDhzClBoeXNpY2FsIG1lbW9y eTogNDMwIE1CCkR1bXBpbmcgNTEgTUI6IDM2IDIwIDQKCiMwICBkb2FkdW1wICgpIGF0IHBjcHUu aDoxOTUKCWluIHBjcHUuaAooa2dkYikgYnQKIzAgIGRvYWR1bXAgKCkgYXQgcGNwdS5oOjE5NQoj MSAgMHhjMDU5MzM1NyBpbiBib290IChob3d0bz0yNjApIGF0IC91c3Ivc3JjL3N5cy9rZXJuL2tl cm5fc2h1dGRvd24uYzo0MDkKIzIgIDB4YzA1OTM2NGIgaW4gcGFuaWMgKGZtdD0pIGF0IC91c3Iv c3JjL3N5cy9rZXJuL2tlcm5fc2h1dGRvd24uYzo1NjMKIzMgIDB4YzA0NjM2YjcgaW4gZGJfcGFu aWMgKGFkZHI9KSBhdCAvdXNyL3NyYy9zeXMvZGRiL2RiX2NvbW1hbmQuYzo0MzMKIzQgIDB4YzA0 NjNlMTUgaW4gZGJfY29tbWFuZF9sb29wICgpIGF0IC91c3Ivc3JjL3N5cy9kZGIvZGJfY29tbWFu ZC5jOjQwMQojNSAgMHhjMDQ2NTg0NSBpbiBkYl90cmFwICh0eXBlPTEyLCBjb2RlPTApIGF0IC91 c3Ivc3JjL3N5cy9kZGIvZGJfbWFpbi5jOjIyMgojNiAgMHhjMDViYjE5NiBpbiBrZGJfdHJhcCAo dHlwZT0xMiwgY29kZT0wLCB0Zj0weGQzZjZkYTJjKSBhdCAvdXNyL3NyYy9zeXMva2Vybi9zdWJy X2tkYi5jOjUwMgojNyAgMHhjMDdiMTkyYyBpbiB0cmFwX2ZhdGFsIChmcmFtZT0weGQzZjZkYTJj LCBldmE9MzkyKSBhdCAvdXNyL3NyYy9zeXMvaTM4Ni9pMzg2L3RyYXAuYzo4NjEKIzggIDB4YzA3 YjIzMDMgaW4gdHJhcCAoZnJhbWU9MHhkM2Y2ZGEyYykgYXQgL3Vzci9zcmMvc3lzL2kzODYvaTM4 Ni90cmFwLmM6Mjc2CiM5ICAweGMwNzk3YmZiIGluIGNhbGx0cmFwICgpIGF0IC91c3Ivc3JjL3N5 cy9pMzg2L2kzODYvZXhjZXB0aW9uLnM6MTM5CiMxMCAweGMwNTg1ZWU1IGluIF9tdHhfbG9ja19z bGVlcCAobT0weGMzNjk2YjI4LCB0aWQ9MzI4MTk0NTEyMCwgb3B0cz0wLCBmaWxlPTB4MCwgbGlu ZT0wKSBhdCAvdXNyL3NyYy9zeXMva2Vybi9rZXJuX211dGV4LmM6MzYxCiMxMSAweGMwNjMyN2Uy IGluIHJ0ZXhwdW5nZSAocnQ9MHhjMzY5NmE1MCkgYXQgL3Vzci9zcmMvc3lzL25ldC9yb3V0ZS5j OjYzOQojMTIgMHhjMDY2MWQyMyBpbiBpbl9pZmFkb3dua2lsbCAocm49MHhjMzY5NmE1MCwgeGFw PTB4ZDNmNmRiNDApIGF0IC91c3Ivc3JjL3N5cy9uZXRpbmV0L2luX3JteC5jOjM3NgojMTMgMHhj MDYzMGZjNSBpbiBybl93YWxrdHJlZSAoaD0weGMyZmZlMzAwLCBmPTB4YzA2NjFjYjAgPGluX2lm YWRvd25raWxsPiwgdz0weGQzZjZkYjQwKSBhdCAvdXNyL3NyYy9zeXMvbmV0L3JhZGl4LmM6MTA4 MwojMTQgMHhjMDY2MWM0YiBpbiBpbl9pZmFkb3duIChpZmE9MHhjMzc4NjEwMCwgZGVsZXRlPTEp IGF0IC91c3Ivc3JjL3N5cy9uZXRpbmV0L2luX3JteC5jOjM5NQojMTUgMHhjMDY1YmEyMiBpbiBp bl9jb250cm9sIChzbz0weGMzNjkzNGE0LCBjbWQ9MjE0OTYwNzcwNSwgZGF0YT0weGMzNWI0OTQw ICJuZmUwIiwgaWZwPTB4YzJmYTc4MDAsIHRkPTB4YzM5ZTgyMjApCiAgICBhdCAvdXNyL3NyYy9z eXMvbmV0aW5ldC9pbi5jOjQ3MgojMTYgMHhjMDYyYWZkZCBpbiBpZmlvY3RsIChzbz0weGMzNjkz NGE0LCBjbWQ9MjE0OTYwNzcwNSwgZGF0YT0weGMzNWI0OTQwICJuZmUwIiwgdGQ9MHhjMzllODIy MCkgYXQgL3Vzci9zcmMvc3lzL25ldC9pZi5jOjE4ODgKIzE3IDB4YzA1Y2YyYzQgaW4gc29vX2lv Y3RsIChmcD0weGMzMTEyN2UwLCBjbWQ9MjE0OTYwNzcwNSwgZGF0YT0weGMzNWI0OTQwLCBhY3Rp dmVfY3JlZD0weGMyZTRhNjAwLCB0ZD0weGMzOWU4MjIwKQogICAgYXQgL3Vzci9zcmMvc3lzL2tl cm4vc3lzX3NvY2tldC5jOjIwMgojMTggMHhjMDVjODA1NSBpbiBrZXJuX2lvY3RsICh0ZD0weGMz OWU4MjIwLCBmZD0zLCBjb209MjE0OTYwNzcwNSwgZGF0YT0weGMzNWI0OTQwICJuZmUwIikgYXQg ZmlsZS5oOjI2NgojMTkgMHhjMDVjODFiNCBpbiBpb2N0bCAodGQ9MHhjMzllODIyMCwgdWFwPTB4 ZDNmNmRjZmMpIGF0IC91c3Ivc3JjL3N5cy9rZXJuL3N5c19nZW5lcmljLmM6NTcwCiMyMCAweGMw N2IxZjQ1IGluIHN5c2NhbGwgKGZyYW1lPTB4ZDNmNmRkMzgpIGF0IC91c3Ivc3JjL3N5cy9pMzg2 L2kzODYvdHJhcC5jOjEwMDYKIzIxIDB4YzA3OTdjNjAgaW4gWGludDB4ODBfc3lzY2FsbCAoKSBh dCAvdXNyL3NyYy9zeXMvaTM4Ni9pMzg2L2V4Y2VwdGlvbi5zOjE5NgojMjIgMHgwMDAwMDAzMyBp biA/PyAoKQooa2dkYikg ------==--bound.4895.webmail23.yandex.ru-- From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 06:01:56 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9EA216A41A for ; Sun, 19 Aug 2007 06:01:56 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from omta04sl.mx.bigpond.com (omta04sl.mx.bigpond.com [144.140.93.156]) by mx1.freebsd.org (Postfix) with ESMTP id 61F9D13C458 for ; Sun, 19 Aug 2007 06:01:51 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from oaamta02sl.mx.bigpond.com ([124.188.162.95]) by omta04sl.mx.bigpond.com with ESMTP id <20070819060150.JNWD4018.omta04sl.mx.bigpond.com@oaamta02sl.mx.bigpond.com> for ; Sun, 19 Aug 2007 06:01:50 +0000 Received: from areilly.bpa.nu ([124.188.162.95]) by oaamta02sl.mx.bigpond.com with ESMTP id <20070819060150.SYSS2725.oaamta02sl.mx.bigpond.com@areilly.bpa.nu> for ; Sun, 19 Aug 2007 06:01:50 +0000 Received: (qmail 56521 invoked by uid 501); 19 Aug 2007 06:01:39 -0000 Date: Sun, 19 Aug 2007 16:01:39 +1000 From: Andrew Reilly To: Randy Bush Message-ID: <20070819060139.GA40369@duncan.reilly.home> References: <20070815122747.GA62123@duncan.reilly.home> <18117.37649.6266.369458@jerusalem.litteratus.org> <18119.3872.547510.973785@roam.psg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18119.3872.547510.973785@roam.psg.com> User-Agent: Mutt/1.4.2.3i Cc: Robert Huff , freebsd-current@freebsd.org Subject: Re: Does 7-CURRENT (aka cvsup tag=.) build under 6-STABLE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 06:01:56 -0000 On Sat, Aug 18, 2007 at 05:24:16AM -1000, Randy Bush wrote: > i just upgraded two RELENG_6 boxes to 7-CURRENT last eve. no prob. > i was silly and broke the union rules by following the instructions > at the bottom of /usr/src/UPDATING. it is extremely rare that i > have had problems on this path, 4 to 5, 5 to 6, 6 to 7. have not > tried 7 to 8 yet. Thanks for the "it works" reports, folks. Re-supped and currently re-building, and it seems to be going OK now. Yes, I've upgraded in-place on most previous occasions, too. (Only exception was to 6, from memory, because a dump/wipe/install/restore seemed to be the easiest way to get UFS2 onto the disks...) Oh: there's an 8? I didn't think that 7 had been tagged/branched, yet. Cheers, -- Andrew From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 06:52:14 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CCE3916A418 for ; Sun, 19 Aug 2007 06:52:14 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 8A56513C469 for ; Sun, 19 Aug 2007 06:52:14 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id 0A99017383; Sun, 19 Aug 2007 06:52:13 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.1/8.14.1) with ESMTP id l7J6qBiG082868; Sun, 19 Aug 2007 06:52:11 GMT (envelope-from phk@critter.freebsd.dk) To: Tim Kientzle From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 18 Aug 2007 18:18:44 MST." <46C79A74.9050703@kientzle.com> Date: Sun, 19 Aug 2007 06:52:11 +0000 Message-ID: <82867.1187506331@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: "'freebsd-current@freebsd.org'" , Joerg Sonnenberger Subject: Re: RFC: #mtree signature X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 06:52:14 -0000 In message <46C79A74.9050703@kientzle.com>, Tim Kientzle writes: >Any concerns or thoughts about the following >patch, which simply adds "#mtree" as the first >line of every mtree file? Good idea, but add a version number as well. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 08:06:37 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6EB6B16A468 for ; Sun, 19 Aug 2007 08:06:37 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from smtp001.mail.ukl.yahoo.com (smtp001.mail.ukl.yahoo.com [217.12.11.32]) by mx1.freebsd.org (Postfix) with SMTP id DCA8513C469 for ; Sun, 19 Aug 2007 08:06:36 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: (qmail 44965 invoked from network); 19 Aug 2007 07:39:54 -0000 Received: from unknown (HELO Gatekeeper.FreeBSD.org) (st.esser@80.135.178.118 with login) by smtp001.mail.ukl.yahoo.com with SMTP; 19 Aug 2007 07:39:54 -0000 X-YMail-OSG: RmGRFIwVM1lZeWAhlnixiBk53lqOnLUNG9x3IwTUk1VJcCmFmYpkCPhSeVr.4cRs3c86oVu7J66x1beaeHw3lrV0DfbxhwJHdA-- Received: by Gatekeeper.FreeBSD.org (Postfix, from userid 200) id EB5A418FB; Sun, 19 Aug 2007 09:39:53 +0200 (CEST) Date: Sun, 19 Aug 2007 09:39:53 +0200 From: Stefan =?iso-8859-1?Q?E=DFer?= To: Ken Yamada Message-ID: <20070819073953.GA36594@Gatekeeper.FreeBSD.org> Mail-Followup-To: Stefan =?iso-8859-1?Q?E=DFer?= , Ken Yamada , anrays@gmail.com, glewis@eyesbeyond.com, lists_freebsd_org@07.antispam.web-wahnsinn.de, freebsd-current@freebsd.org, freebsd-java@freebsd.org References: <20070815144804.GC5151@misty.eyesbeyond.com> <20070818.213208.74754361.ken@tydfam.jp> <864piweemc.fsf@santinel.home.ua> <20070819.120136.41629169.ken@tydfam.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070819.120136.41629169.ken@tydfam.jp> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: glewis@eyesbeyond.com, anrays@gmail.com, lists_freebsd_org@07.antispam.web-wahnsinn.de, freebsd-java@freebsd.org, freebsd-current@freebsd.org Subject: Re: Gcc bugs break java/jdk15 build? [Workaround] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 08:06:37 -0000 On 2007-08-19 12:01 +0900, Ken Yamada wrote: > Does this mean that GCC 4.2.1 does not solve "loop optimization bug" > pointed out by Andrey Chernov (http://docs.freebsd.org/cgi/getmsg.cgi?fetch=282888+0+archive/2007/freebsd-current/20070701.freebsd-current) on 4.2.0? > > Is it a good idea of adding -fno-tree-vrp to CFLAGS in /etc/make.conf > to avoid this optimization bug for all compilation? (BTW, I leave -O3 > of CFLAGS as is in make.conf and just added -fno-tree-vrp to the end of > the line.) I did just that (added -fno-tree-vrp to CFLAGS) after it was found that gcc-4.2 had the optimizer bug, and have continued to build my system with -O2 (or other optimization levels as required). This seems to work just fine (no problems with ports that are not working when built with a plain -O2). I had suggested to make -fno-tree-vrp the default for our CC (could be overridden on the command line, but would allow to use all -O levels without being hit by the compiler bug; but it appears that nobody else liked the idea at that time, i.e. no response at all ...). Regards, STefan From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 09:48:04 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6FF916A418 for ; Sun, 19 Aug 2007 09:48:04 +0000 (UTC) (envelope-from jacob.hart@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.186]) by mx1.freebsd.org (Postfix) with ESMTP id 9E49D13C457 for ; Sun, 19 Aug 2007 09:48:04 +0000 (UTC) (envelope-from jacob.hart@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so743410rvb for ; Sun, 19 Aug 2007 02:48:04 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; b=e+W2gKgMY9kw626rxKXVGhBaXyFGU7vEC6jZpQZr0wJlw94ML0ERVbehHSI51OguC/S+d2Xvum6UVaxTfQVjpul6AFTO6BgsqBnUC73KcQCuH3LZZ82gKQjCi+w42J5ZsGweiaiZyFqjI64eXYuNuz7Om9U4HjtH5lMi7sq3xoQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; b=SaSH/HLG2FcGRqETNG/IHWQLDZe7WSqMRpY5sCcJoKFW7mGn6U/S1jBHAFDmdipvD7KmGvmE2rAaikMIYG+osoSwms5dmwvenMVV/FUSu3htC1rGysHiZ+wIwTIfYYmhcMoZIkBsRoqjtEFFPnFI5rT7Qwe75Zrect5INT1//I8= Received: by 10.115.22.1 with SMTP id z1mr340358wai.1187516884295; Sun, 19 Aug 2007 02:48:04 -0700 (PDT) Received: by 10.114.150.11 with HTTP; Sun, 19 Aug 2007 02:48:04 -0700 (PDT) Message-ID: <139a3a1b0708190248w66b746f9w313600578334572@mail.gmail.com> Date: Sun, 19 Aug 2007 19:48:04 +1000 From: "Jacob Hart" Sender: jacob.hart@gmail.com To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_2730_32213699.1187516884264" X-Google-Sender-Auth: a22ff67fe54b99e0 Subject: Allow TCP/UDP services in /etc/rc.firewall X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 09:48:04 -0000 ------=_Part_2730_32213699.1187516884264 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Small patch that changes workstation profile in /etc/rc.firewall to allow UDP services. All ports without a protocol specifier are treated as TCP by default to keep backwards compatibility. For example, setting firewall_myservices="22 tcp:2000 udp:2001" in /etc/rc.conf creates ipfw rules for tcp ports 22,2000 and udp port 2001. -j ------=_Part_2730_32213699.1187516884264 Content-Type: text/x-patch; name="rc.firewall.diff" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="rc.firewall.diff" X-Attachment-Id: f_f5jcuyo1 LS0tIC9ldGMvcmMuZmlyZXdhbGwub3JpZwkyMDA3LTA4LTE5IDE4OjAzOjQzLjAwMDAwMDAwMCAr MTAwMAorKysgL2V0Yy9yYy5maXJld2FsbAkyMDA3LTA4LTE5IDE5OjE4OjQyLjAwMDAwMDAwMCAr MTAwMApAQCAtMzQ5LDggKzM0OSwxMCBAQAogCSMKIAlmb3IgaSBpbiAke2ZpcmV3YWxsX2FsbG93 c2VydmljZXN9IDsgZG8KIAkgIGZvciBqIGluICR7ZmlyZXdhbGxfbXlzZXJ2aWNlc30gOyBkbwot CSAgICAke2Z3Y21kfSBhZGQgcGFzcyB0Y3AgZnJvbSAkaSB0byBtZSAkagotCSAgZG9uZQorICAg ICAgICAgICAgcHJvdG89YChlY2hvICRqIHwgYXdrICcvOi8ge3NwbGl0KCQwLGEsIjoiKTsgcHJp bnQgYVsxXX0nKWAKKyAgICAgICAgICAgIHBvcnQ9YChlY2hvICRqIHwgc2VkIC1lICdzLy4qOi8v MScpYAorICAgICAgICAgICAgJHtmd2NtZH0gYWRkIHBhc3MgJHtwcm90bzotdGNwfSBmcm9tICRp IHRvIG1lICR7cG9ydH0KKyAgICAgICAgICBkb25lCiAJZG9uZQogCiAJIyBBbGxvdyBhbGwgY29u bmVjdGlvbnMgZnJvbSB0cnVzdGVkIElQcy4K ------=_Part_2730_32213699.1187516884264-- From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 09:54:11 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A61116A41A for ; Sun, 19 Aug 2007 09:54:11 +0000 (UTC) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (nagual.pp.ru [194.87.13.69]) by mx1.freebsd.org (Postfix) with ESMTP id C7E1313C428 for ; Sun, 19 Aug 2007 09:54:10 +0000 (UTC) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.14.1/8.14.1) with ESMTP id l7J9re76079933; Sun, 19 Aug 2007 13:53:41 +0400 (MSD) (envelope-from ache@nagual.pp.ru) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nagual.pp.ru; s=default; t=1187517221; bh=hILdqoeVBgsdcYYyFgY6KeMlJ5+lb6yUp7DrKIw qUX0=; l=668; h=Received:Date:From:To:Cc:Subject:Message-ID: Mail-Followup-To:References:MIME-Version:Content-Type: Content-Disposition:In-Reply-To:User-Agent; b=jLruKHi5QNjCxIZrbcIm wbILWOGf/VqcewKMjqolhYuAmA6x4mrvYo7adboJh9/tTf2gXakUd+fJ/9Dz8PZdVtc C/vFjzdh4MJMVJia/RgCQTJqoNCr33yxsq0eyx9dWrZb3itAACrv7/ras8mPvsG7nt2 d9mz29KCft8CLJNqg= Received: (from ache@localhost) by nagual.pp.ru (8.14.1/8.14.1/Submit) id l7J9rdGX079932; Sun, 19 Aug 2007 13:53:39 +0400 (MSD) (envelope-from ache) Date: Sun, 19 Aug 2007 13:53:39 +0400 From: Andrey Chernov To: Ken Yamada Message-ID: <20070819095339.GA79882@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Ken Yamada , anrays@gmail.com, glewis@eyesbeyond.com, lists_freebsd_org@07.antispam.web-wahnsinn.de, freebsd-current@FreeBSD.ORG, freebsd-java@FreeBSD.ORG References: <20070815144804.GC5151@misty.eyesbeyond.com> <20070818.213208.74754361.ken@tydfam.jp> <864piweemc.fsf@santinel.home.ua> <20070819.120136.41629169.ken@tydfam.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070819.120136.41629169.ken@tydfam.jp> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: glewis@eyesbeyond.com, anrays@gmail.com, lists_freebsd_org@07.antispam.web-wahnsinn.de, freebsd-current@FreeBSD.ORG, freebsd-java@FreeBSD.ORG Subject: Re: Gcc bugs break java/jdk15 build? [Workaround] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 09:54:11 -0000 On Sun, Aug 19, 2007 at 12:01:36PM +0900, Ken Yamada wrote: > Does this mean that GCC 4.2.1 does not solve "loop optimization bug" pointed out by Andrey Chernov (http://docs.freebsd.org/cgi/getmsg.cgi?fetch=282888+0+archive/2007/freebsd-current/20070701.freebsd-current) on 4.2.0? That bug is fixed, but it doesn't mean that no other tree-vrp bugs left. > Is it a good idea of adding -fno-tree-vrp to CFLAGS in /etc/make.conf to avoid this optimization bug for all compilation? (BTW, I leave -O3 of CFLAGS as is in make.conf and just added -fno-tree-vrp to the end of the line.) It is good idea to extract minimal bug code sample and submit it to gcc bugzilla. -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 11:56:02 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3224716A46C; Sun, 19 Aug 2007 11:56:02 +0000 (UTC) (envelope-from davidt@yadt.co.uk) Received: from outcold.yadt.co.uk (outcold.yadt.co.uk [81.187.204.178]) by mx1.freebsd.org (Postfix) with ESMTP id D39EE13C45A; Sun, 19 Aug 2007 11:56:01 +0000 (UTC) (envelope-from davidt@yadt.co.uk) Received: from localhost (localhost [127.0.0.1]) by outcold.yadt.co.uk (Postfix) with ESMTP id 466DF57A58; Thu, 19 Jul 2007 18:48:50 +0100 (BST) X-Virus-Scanned: amavisd-new at yadt.co.uk Received: from outcold.yadt.co.uk ([127.0.0.1]) by localhost (outcold.yadt.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gsx5qCOzafFx; Thu, 19 Jul 2007 18:48:47 +0100 (BST) Received: by outcold.yadt.co.uk (Postfix, from userid 1001) id 7050457A5A; Thu, 19 Jul 2007 18:48:47 +0100 (BST) From: David Taylor To: "Wojciech A. Koszek" , freebsd-current@freebsd.org Message-ID: <20070719174847.GA5853@outcold.yadt.co.uk> Mail-Followup-To: "Wojciech A. Koszek" , freebsd-current@freebsd.org References: <20070506164247.GA77786@FreeBSD.czest.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <20070506164247.GA77786@FreeBSD.czest.pl> User-Agent: Mutt/1.4.2.3i Cc: Subject: Re: INCLUDE_CONFIG_FILE patches X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Sun, 19 Aug 2007 11:56:02 -0000 X-Original-Date: Thu, 19 Jul 2007 18:48:47 +0100 X-List-Received-Date: Sun, 19 Aug 2007 11:56:02 -0000 On Sun, 06 May 2007, Wojciech A. Koszek wrote: > Hello, > > We talked about improved INCLUDE_CONFIG_FILE work some time ago. I > cleaned it up, and I have prepared a patch for the latest -CURRENT. > > It's here: > > http://people.freebsd.org/~wkoszek/patches/kernconf.patch > > If you have any suggestions, please let me know as I'd really like to > see this patch into the tree before RELENG_7. Hi, I've discovered a small problem with this patch (or at least, whatever version is in RELENG_6 as of 2007-07-18). If your config file contains a trigraph (in my case, I had a comment containing "??)"), gcc will process it as a trigraph and produce a warning, which will break the build with a confusing and unhelpful error message in config.c. This caused no problems before the new INCLUDE_CONFIG_FILE option (as the config file wasn't included in the C source file). Not sure what the best solution is, but some kind of warning that this can happen would perhaps save someone 30 minutes of frustration! Alternatively, some method of escaping any potential trigraphs would be great. -- David Taylor From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 12:27:33 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4AD416A418 for ; Sun, 19 Aug 2007 12:27:33 +0000 (UTC) (envelope-from william88@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.191]) by mx1.freebsd.org (Postfix) with ESMTP id 7BD0313C457 for ; Sun, 19 Aug 2007 12:27:33 +0000 (UTC) (envelope-from william88@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so757800rvb for ; Sun, 19 Aug 2007 05:27:32 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=F0qRNKO6FWtFPldb7dY2qiLOHfp7+mKVhLcE+F5Lj+Sw0Ij1EokCs8bkpObts7iCJa3gooatreRngTaDOaBuJh9qqGTIxirxwhVeuI46mLri+a12d9f1pKHCwJaD4vRNgrKNQ1Ty6weoHA6OfFGiZz4JwT6Ui4hOwXk7I25Bo8M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=dWRqwM8fNp4IyPzQQW1Wn3PKCtaB/IoLRgbiWZTES0cjvtG504dR0vL0DWZKni2s21VLwQ7nBUvu2RJGYtYNbgTKBO2QlKyiPPAbNH2nCPrOlmdocNKWLSBkXr7yp5Jg70dKhphl7QnZhgdGrlr5reEJlGojM2/GO3f2pYkallI= Received: by 10.115.91.2 with SMTP id t2mr3052803wal.1187526452827; Sun, 19 Aug 2007 05:27:32 -0700 (PDT) Received: by 10.114.111.4 with HTTP; Sun, 19 Aug 2007 05:27:32 -0700 (PDT) Message-ID: <632825b40708190527ydaf73c1pa113932b6c01a8ef@mail.gmail.com> Date: Sun, 19 Aug 2007 09:27:32 -0300 From: "William Grzybowski" To: "Sam Leffler" In-Reply-To: <46C664D0.3060906@errno.com> MIME-Version: 1.0 References: <632825b40708171855u155d0195udb6994999de12d15@mail.gmail.com> <46C664D0.3060906@errno.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: Atheros AR5006 abg minipci X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 12:27:33 -0000 On 8/18/07, Sam Leffler wrote: > > William Grzybowski wrote: > > Hi, > > > > I got wireless minipci atheros ar5006 with -CURRENT. > > Cant use it even with if_ndis and i didnt tried on stable/release yet. > > dmesg: > > > > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, > RF5413) > > ath0: mem 0xd0000000-0xd000ffff irq 16 at device 0.0on > > pci3 > > ath0: [ITHREAD] > > ath0: unable to attach hardware; HAL status 13 > > device_attach: ath0 attach returned 6 > > > > I tried to search about it on the history without success, does it means > > this card isn't supported yey? could i do anything providing info to > help? > > Should I forward this message to another list? > > You can try the test hal in http://www.freebsd.org/~sam. Beware it is > not a release (has not undergone full testing and has known issues). If > the 0.9.30.3 hal doesn't work then your part is probably a 2425. > Support for that part has been blocked waiting on Atheros for >1 month. > No idea when it might show up. > > Sam I tried it but didn't work ;( So I guess that we have wait for it Thanks -- William Grzybowski ------------------------------------------ Jabber: william88 at gmail dot com Msn: william.grz at hotmail dot com Curitiba/PR From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 13:24:54 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F77116A468 for ; Sun, 19 Aug 2007 13:24:54 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.178]) by mx1.freebsd.org (Postfix) with ESMTP id 679BB13C45E for ; Sun, 19 Aug 2007 13:24:54 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: by wa-out-1112.google.com with SMTP id m33so477792wag for ; Sun, 19 Aug 2007 06:24:54 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=AmEqBaF8mvV8FgCWfC+5SnRvfOUgH8Sm5sYjxHNSgJsNTPGQW7gW1oj9leLiCrE3MWqlvar9+9ypzSiF4KaYLXxVxxUGW4yznoALnaINUQP492kzvLEtb/GblCDN8E01mHHLl2QRyI3xgaKmqxUXQ5jXNNXseeaze2pl2+eCyIs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nFfEg/g9wRdLrLkKdoOKTHyHyjhvbFUWyuAGlamQbAWleb8jnALcxgPV/i+RT1acBWATecrBWDTjtN3ZbhEX6/nOcKiPQgVrJwXnT0tW3XZBYf/ChpZAFSM2+0ItUJSRV4uk7E6R9Lr3FKXqDhMmT6pbrEHHLVgLqs3zgnDhfIw= Received: by 10.114.149.2 with SMTP id w2mr4443314wad.1187529893801; Sun, 19 Aug 2007 06:24:53 -0700 (PDT) Received: by 10.115.76.11 with HTTP; Sun, 19 Aug 2007 06:24:53 -0700 (PDT) Message-ID: <4956a5e50708190624t4168ed02nbbc25f107cde94fc@mail.gmail.com> Date: Sun, 19 Aug 2007 10:24:53 -0300 From: Nenhum_de_Nos To: "Ian FREISLICH" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4956a5e50708081849s393be47bv931310df0e59fb66@mail.gmail.com> X-Mailman-Approved-At: Sun, 19 Aug 2007 13:38:23 +0000 Cc: freebsd-current@freebsd.org Subject: Re: hostapd and atheros - anyone else with dropping connections ?! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 13:24:54 -0000 On 8/9/07, Ian FREISLICH wrote: > Nenhum_de_Nos wrote: > > I have a wifi atheros card: > > > > ath0@pci0:10:0: class=0x020000 card=0x3a131186 chip=0x0013168c rev=0x01 hdr=0 > x00 > > vendor = 'Atheros Communications Inc.' > > device = 'AR5212, AR5213 802.11a/b/g Wireless Adapter' > > class = network > > subclass = ethernet > > > > and an hostapd AP. > > > > from time to time, I need to restart hostapd. and this time is not long. > > > > I'll update now and try again. > > > > if anyone is having the same issue, please say :) > > I'm having a similar issue on similar and more recent hardware (5212 > and 5006), but not with hostap. Have you tried 'arp -d -a' on > either or both of the hosts? I find this fixes my disappearing > wireless connectivity. > > Ian > > -- > Ian Freislich no good for me, I waited till now to see the issue and test. when I did the "arp -d -a", I got no wifi connection back, and as bonus, I cant get in the ap box using ssh, just now when I had direct access to it(monitor and keyboard directly attached). Trying to kill arp -d -a, that is still running, doesnt work even when killall -9 is used. I tryed to update my current machine, but it keeps killing the gcc process, as there is not ram enough for everyone, and dmesg says it has been killed. another weird issue, dmesg keeps saying: ath0: ath_rx_proc: no mbuf! my present dmesg has just this entries ... I'll try to update current, but this is not easy as usually was/should be. :( this is a Athlon XP 1700+ 512MB PC2100 running -CURRENT from July 29. I have mldonkey and Folding at home running, but before this current, I could do all three jobs just fine. I'll csup again and let hust gcc be alone, if anyone has any hints, thanks matheus -- We will call you cygnus, The God of balance you shall be From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 13:42:06 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A6B616A419 for ; Sun, 19 Aug 2007 13:42:06 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.182]) by mx1.freebsd.org (Postfix) with ESMTP id 00BB213C45D for ; Sun, 19 Aug 2007 13:42:05 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: by wa-out-1112.google.com with SMTP id m33so480613wag for ; Sun, 19 Aug 2007 06:42:05 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=P4ly5ZGwG8rmNzEXlNndsHDWzbDY1LBevg2i+ykrKd5vtDMyFjtRglkt2/l3cLb6HZoz4Wuosna2b6QPxqhlElPKs1efwO8Mxf0L/2zCwKqH3eIN4XpICKfCpOu3TUNbfqrjOB0GDVE+ZxhsQVnk6BQDw7bvdXZqnVfStPAXOAY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WbqBAj/4niN/c6b4OijX1KK3kmRU0MEGTz/NNT/M7/g5Q+5mslkC1CZtS+C9mpwOsV7P4RjLh/ZeDwNiETvIPivpO/1Nl9rHgPampQ4tPFsezSI5psD/JjlXzwftpI036s3qH2MtDFlfVJWNX1roZnZ08evHfYTdlv3hjVTnihQ= Received: by 10.114.53.1 with SMTP id b1mr62174waa.1187530925349; Sun, 19 Aug 2007 06:42:05 -0700 (PDT) Received: by 10.115.76.11 with HTTP; Sun, 19 Aug 2007 06:42:05 -0700 (PDT) Message-ID: <4956a5e50708190642t284f5142r137a85b77f4bd2c4@mail.gmail.com> Date: Sun, 19 Aug 2007 10:42:05 -0300 From: Nenhum_de_Nos To: "Ian FREISLICH" In-Reply-To: <4956a5e50708190624t4168ed02nbbc25f107cde94fc@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4956a5e50708081849s393be47bv931310df0e59fb66@mail.gmail.com> <4956a5e50708190624t4168ed02nbbc25f107cde94fc@mail.gmail.com> X-Mailman-Approved-At: Sun, 19 Aug 2007 14:12:12 +0000 Cc: freebsd-current@freebsd.org Subject: Re: hostapd and atheros - anyone else with dropping connections ?! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 13:42:06 -0000 On 8/19/07, Nenhum_de_Nos wrote: > On 8/9/07, Ian FREISLICH wrote: > > Nenhum_de_Nos wrote: > > > I have a wifi atheros card: > > > > > > ath0@pci0:10:0: class=0x020000 card=0x3a131186 chip=0x0013168c rev=0x01 hdr=0 > > x00 > > > vendor = 'Atheros Communications Inc.' > > > device = 'AR5212, AR5213 802.11a/b/g Wireless Adapter' > > > class = network > > > subclass = ethernet > > > > > > and an hostapd AP. > > > > > > from time to time, I need to restart hostapd. and this time is not long. > > > > > > I'll update now and try again. > > > > > > if anyone is having the same issue, please say :) > > > > I'm having a similar issue on similar and more recent hardware (5212 > > and 5006), but not with hostap. Have you tried 'arp -d -a' on > > either or both of the hosts? I find this fixes my disappearing > > wireless connectivity. > > > > Ian > > > > -- > > Ian Freislich > > no good for me, I waited till now to see the issue and test. when I > did the "arp -d -a", I got no wifi connection back, and as bonus, I > cant get in the ap box using ssh, just now when I had direct access to > it(monitor and keyboard directly attached). Trying to kill arp -d -a, > that is still running, doesnt work even when killall -9 is used. > > I tryed to update my current machine, but it keeps killing the gcc > process, as there is not ram enough for everyone, and dmesg says it > has been killed. another weird issue, dmesg keeps saying: > > ath0: ath_rx_proc: no mbuf! > > my present dmesg has just this entries ... > > I'll try to update current, but this is not easy as usually was/should be. :( > > this is a Athlon XP 1700+ 512MB PC2100 running -CURRENT from July 29. > I have mldonkey and Folding at home running, but before this current, > I could do all three jobs just fine. > > I'll csup again and let hust gcc be alone, > > if anyone has any hints, > > thanks > > matheus just a small update, every program I run on it begins running, but never ends. even control+C works ... well, at least csup now is in this way, and although I can ping any other host, I cant ssh anyone. I'll reboot and try again. matheus -- We will call you cygnus, The God of balance you shall be From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 15:43:47 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D456616A46D for ; Sun, 19 Aug 2007 15:43:47 +0000 (UTC) (envelope-from amistry@am-productions.biz) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.freebsd.org (Postfix) with ESMTP id 7A0A613C4A7 for ; Sun, 19 Aug 2007 15:43:47 +0000 (UTC) (envelope-from amistry@am-productions.biz) Received: from [192.168.1.100] (cpe-71-72-80-132.columbus.res.rr.com [71.72.80.132]) (authenticated bits=0) by mail.united-ware.com (8.13.8/8.13.8) with ESMTP id l7JGLhw3045415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 19 Aug 2007 12:21:50 -0400 (EDT) (envelope-from amistry@am-productions.biz) From: Anish Mistry Organization: AM Productions To: freebsd-current@freebsd.org User-Agent: KMail/1.9.6 MIME-Version: 1.0 Date: Sun, 19 Aug 2007 11:46:52 -0400 Content-Type: multipart/signed; boundary="nextPart3587851.3JDjFgElT8"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200708191147.10340.amistry@am-productions.biz> X-Virus-Scanned: ClamAV 0.90.3/3991/Sat Aug 18 20:31:39 2007 on mail.united-ware.com X-Virus-Status: Clean X-Mailman-Approved-At: Sun, 19 Aug 2007 16:06:46 +0000 Subject: Can't create TCP connections to certain IP addresses X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 15:43:47 -0000 --nextPart3587851.3JDjFgElT8 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I'm sending this again as I didn't receive any responses before and=20 the problem persists as of yesterday's CURRENT. Just let me know=20 what other debug info I need to provide. This has been happening for a while, I just don't remember when it=20 started (it's been happening for at least a couple of months now),=20 but I know everything was working in April. I'm trying to debug a=20 strange problem I'm having with my -CURRENT system. I can not=20 connect to certain IP addresses. I can connect to=20 am-productions.biz, but not slashdot.org, etc. When the connection=20 can't be made I see the state as SYN_SENT (via netstat). This isn't=20 a DNS issue since I can resolve and ping the sites. I've tried other on other networks just in case it was a problem with=20 my network, but the same thing happens there too. This is using an=20 rl NIC in my laptop. Using the ath wireless leads to the same=20 results as the rl. Connecting to the cvsup server that I'm using does work, so I can=20 update easily. I've linked to various information. If there is some more=20 information I need to provide let me know. tcpdump.txt contains a failed connection. tcpdump-good.txt contains=20 a succeeded connection. http://am-productions.biz/debug/littleguy/dmesg.boot http://am-productions.biz/debug/littleguy/LITTLEGUY http://am-productions.biz/debug/littleguy/tcpdump-good.txt http://am-productions.biz/debug/littleguy/sysctl-tcp.txt http://am-productions.biz/debug/littleguy/tcpdump.txt http://am-productions.biz/debug/littleguy/sysctl.conf Thanks, =2D-=20 Anish Mistry amistry@am-productions.biz AM Productions http://am-productions.biz/ --nextPart3587851.3JDjFgElT8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBGyGX+xqA5ziudZT0RAoGnAJ47XboFOfWsGX9dxNFzYvQV4MPojACePktR mXuA8w2vU7pPXzrwH6Ybffs= =ws+3 -----END PGP SIGNATURE----- --nextPart3587851.3JDjFgElT8-- From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 16:08:05 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F14716A41A for ; Sun, 19 Aug 2007 16:08:05 +0000 (UTC) (envelope-from daniel.tourde@spray.se) Received: from proxy2.bredband.net (proxy2.bredband.net [195.54.101.72]) by mx1.freebsd.org (Postfix) with ESMTP id 614B213C49D for ; Sun, 19 Aug 2007 16:08:05 +0000 (UTC) (envelope-from daniel.tourde@spray.se) Received: from maerlyn.bredbandsbolaget.se (213.114.133.105) by proxy2.bredband.net (7.3.127) id 46C6D3C600028CE8 for freebsd-current@freebsd.org; Sun, 19 Aug 2007 17:47:02 +0200 From: Daniel Tourde To: freebsd-current@freebsd.org Date: Sun, 19 Aug 2007 17:47:18 +0200 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200708191747.18556.daniel.tourde@spray.se> Subject: How to build 'current' without debugging options? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: daniel.tourde@spray.se List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 16:08:05 -0000 Hello, I am trying 7.0-current and I am planning to use CVS. At the moment I have the snapshot of June 07 installed on my machine. I would like to know: - How to build without all the debug flags? - I saw that by default, during bootstrap, gfortran and gdb aren't built. Do I simply need to comment the two NO_ flags in Makefile.incl to get gfortran and gdb or do I need to do anything else? Daniel From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 16:46:10 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1B5F16A418 for ; Sun, 19 Aug 2007 16:46:10 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id D12CB13C461 for ; Sun, 19 Aug 2007 16:46:10 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from [10.0.0.222] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id l7JGk3H7057673; Sun, 19 Aug 2007 09:46:03 -0700 (PDT) (envelope-from tim@kientzle.com) Message-ID: <46C873CB.7010503@kientzle.com> Date: Sun, 19 Aug 2007 09:46:03 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Jeremy References: <46C79A74.9050703@kientzle.com> <20070819024258.GA23080@turion.vk2pj.dyndns.org> In-Reply-To: <20070819024258.GA23080@turion.vk2pj.dyndns.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: "'freebsd-current@freebsd.org'" , Joerg Sonnenberger Subject: Re: RFC: #mtree signature X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 16:46:11 -0000 Peter Jeremy wrote: > On 2007-Aug-18 18:18:44 -0700, Tim Kientzle wrote: > >>Any concerns or thoughts about the following >>patch, which simply adds "#mtree" as the first >>line of every mtree file? > > > Sounds like a good idea. I would suggest that if we're going to add > a signature block, it include a version string in case we want to > incompatibly change the mtree format at some future date. > > Maybe: "#mtree v1.0\n". Good point. That will mean a little more effort to coordinate with the NetBSD folks, who have already revved the format. I suppose their "mtree -C" format should be marked "#mtree v2.0\n". Tim Kientzle From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 17:33:59 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 897A316A41A for ; Sun, 19 Aug 2007 17:33:59 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 2C40513C457 for ; Sun, 19 Aug 2007 17:33:59 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.222] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id l7JHLiH7057813; Sun, 19 Aug 2007 10:21:44 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <46C87C28.4020603@freebsd.org> Date: Sun, 19 Aug 2007 10:21:44 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org, netbsd-docs@netbsd.org, Joerg Sonnenberger Content-Type: multipart/mixed; boundary="------------040909030809040908060604" Cc: Subject: RFC: Proposed mtree.5 man page X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 17:33:59 -0000 This is a multi-part message in MIME format. --------------040909030809040908060604 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit I'm experimenting with mtree support for bsdtar, which led me to look for a definitive statement of "the mtree format." Not finding one, I cobbled together the attached draft by pulling details from the mtree.8 pages for FreeBSD and NetBSD and adding a few choice tidbits from the source code. I've also included my proposal for a "#mtree" signature at the beginning of any mtree file. My goal is for this to become the defining document for the mtree format across all current implementations. In particular, I'm looking for comments from people knowledgable about the existing mtree tools. Feedback/comments appreciated, Tim Kientzle --------------040909030809040908060604 Content-Type: text/plain; name="mtree.5" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="mtree.5" .\" Copyright (c) 1989, 1990, 1993 .\" The Regents of the University of California. All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 4. Neither the name of the University nor the names of its contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" .\" From: @(#)mtree.8 8.2 (Berkeley) 12/11/93 .\" $FreeBSD$ .\" .Dd August 20, 2007 .Dt MTREE 5 .Os .Sh NAME .Nm mtree .Nd format of mtree dir heirarchy files .Sh DESCRIPTION The .Nm format is a textual format that describes a collection of filesystem objects. Such files are typically used to create or verify directory heirarchies. .Ss General Format An .Nm file consists of a series of lines, each providing information about a single filesystem object. Leading whitespace is always ignored. .Pp When encoding file or pathnames, any backslash character or character outside of the 95 printable ASCII characters must be encoded as a a backslash followed by three octal digits. When reading mtree files, any appearance of a backslash followed by three octal digits should be converted into the corresponding character. .Pp Each line is interpreted independently as one of the following types: .Bl -tag -width Cm .It Signature The first line of any mtree file must begin with .Dq #mtree . If a file contains any full path entries, the first line should begin with .Dq #mtree v2.0 , otherwise, the first line should begin with .Dq #mtree v1.0 . .It Blank Blank lines are ignored. .It Comment Lines beginning with .Cm # are ignored. .It Special Lines beginning with .Cm / are special commands that influence the interpretation of later lines. .It Relative If the first whitespace-delimited word has no .Cm / characters, it is the name of a file in the current directory. Any relative entry that describes a directory changes the current directory. .It dot-dot As a special case, a relative entry with the filename .Pa .. changes the current directory to the parent directory. Options on dot-dot entries are always ignored. .It Full If the first whitespace-delimited word has a .Cm / character after the first character, it is the pathname of a file relative to the starting directory. There can be multiple full entries describing the same file. .El .Pp Some tools that process .Nm files may require that multiple lines describing the same file occur consecutively. It is not permitted for the same file to be mentioned using both a relative and a full file specification. .Ss Special commands Two special commands are currently defined: .Bl -tag -width Cm .It Cm /set This command defines default values for one or more keywords. It is followed on the same line by one or more whitespace-separated keyword definitions. These definitions apply to all following files that do not specify a value for that keyword. .It Cm /unset This command removes any default value set by a previous .Cm /set command. It is followed on the same line by one or more keywords separated by whitespace. .El .Ss Keywords After the filename, a full or relative entry consists of zero or more whitespace-separated keyword definitions. Each such definitions consists of a key from the following list immediately followed by an '=' sign and a value. Software programs reading mtree files should warn about unrecognized keywords. .Pp Currently supported keywords are as follows: .Bl -tag -width Cm .It Cm cksum The checksum of the file using the default algorithm specified by the .Xr cksum 1 utility. .It Cm contents The full pathname of a file whose contents should be compared to the contents of this file. .It Cm flags The file flags as a symbolic name. See .Xr chflags 1 for information on these names. If no flags are to be set the string .Dq none may be used to override the current default. .It Cm ignore Ignore any file hierarchy below this file. .It Cm gid The file group as a numeric value. .It Cm gname The file group as a symbolic name. .It Cm md5 The MD5 message digest of the file. .It Cm md5digest A synonym for .Cm md5 . .It Cm sha1 The .Tn FIPS 160-1 .Pq Dq Tn SHA-1 message digest of the file. .It Cm sha1digest A synonym for .Cm sha1 . .It Cm sha256 The .Tn FIPS 180-2 .Pq Dq Tn SHA-256 message digest of the file. .It Cm sha256digest A synonym for .Cm sha256 . .It Cm ripemd160digest The .Tn RIPEMD160 message digest of the file. .It Cm rmd160 A synonym for .Cm ripemd160digest . .It Cm rmd160digest A synonym for .Cm ripemd160digest . .It Cm mode The current file's permissions as a numeric (octal) or symbolic value. .It Cm nlink The number of hard links the file is expected to have. .It Cm nochange Make sure this file or directory exists but otherwise ignore all attributes. .It Cm uid The file owner as a numeric value. .It Cm uname The file owner as a symbolic name. .It Cm size The size, in bytes, of the file. .It Cm link The file the symbolic link is expected to reference. .It Cm time The last modification time of the file. .It Cm type The type of the file; may be set to any one of the following: .Pp .Bl -tag -width Cm -compact .It Cm block block special device .It Cm char character special device .It Cm dir directory .It Cm fifo fifo .It Cm file regular file .It Cm link symbolic link .It Cm socket socket .El .El .Pp .Sh SEE ALSO .Xr cksum 1 , .Xr find 1 , .Xr mtree 8 .Sh BUGS The .Fx implementation of mtree does not currently support the .Nm 2.0 format. The requirement for a .Dq #mtree signature line is new and not yet widely implemented. .Sh HISTORY The .Nm utility appeared in .Bx 4.3 Reno . The .Tn MD5 digest capability was added in .Fx 2.1 , in response to the widespread use of programs which can spoof .Xr cksum 1 . The .Tn SHA-1 and .Tn RIPEMD160 digests were added in .Fx 4.0 , as new attacks have demonstrated weaknesses in .Tn MD5 . The .Tn SHA-256 digest was added in .Fx 6.0 . Support for file flags was added in .Fx 4.0 , and mostly comes from .Nx . The .Dq full entry format was added by .Nx . --------------040909030809040908060604-- From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 19:16:51 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B8B516A419 for ; Sun, 19 Aug 2007 19:16:51 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [IPv6:2001:770:10:300::86e2:510b]) by mx1.freebsd.org (Postfix) with SMTP id 50C0913C458 for ; Sun, 19 Aug 2007 19:16:50 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 19 Aug 2007 20:16:48 +0100 (BST) Date: Sun, 19 Aug 2007 20:16:47 +0100 From: David Malone To: Anish Mistry Message-ID: <20070819191647.GA59444@walton.maths.tcd.ie> References: <200708191147.10340.amistry@am-productions.biz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200708191147.10340.amistry@am-productions.biz> User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: freebsd-current@freebsd.org Subject: Re: Can't create TCP connections to certain IP addresses X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 19:16:51 -0000 On Sun, Aug 19, 2007 at 11:46:52AM -0400, Anish Mistry wrote: > tcpdump.txt contains a failed connection. tcpdump-good.txt contains > a succeeded connection. As you say, the SYN packet is being sent, but no reply be being received. Can you run a tcpdump on your router/firewall and see if the SYN packets are being recieved (and forwarded) and check if the SYN ACK packets are getting back that far? David. From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 19:26:46 2007 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD95816A41B; Sun, 19 Aug 2007 19:26:46 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 9DABD13C465; Sun, 19 Aug 2007 19:26:46 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from rot26.obsecurity.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 28BB31A3C1A; Sun, 19 Aug 2007 12:25:00 -0700 (PDT) Received: by rot26.obsecurity.org (Postfix, from userid 1001) id 068C5C3EB; Sun, 19 Aug 2007 15:26:45 -0400 (EDT) Date: Sun, 19 Aug 2007 15:26:44 -0400 From: Kris Kennaway To: current@FreeBSD.org Message-ID: <20070819192644.GA59961@rot26.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: davidxu@FreeBSD.org Subject: "panic: ureadc" from aio X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 19:26:46 -0000 --vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I was running stress2 which hung somehow, so I ^Ced it and it panicked: panic: ureadc cpuid = 1 KDB: enter: panic [thread pid 8507 tid 100609 ] Stopped at kdb_enter+0x33: leave db> wh Tracing pid 8507 tid 100609 td 0xc5d63cc0 kdb_enter(c0780dbf,1,c0781318,ed2619fc,1,...) at kdb_enter+0x33 panic(c0781318,0,77,c4e3b400,ed261bf0,...) at panic+0xed ureadc(77,ed261cb0,159,c0788008,0,...) at ureadc+0x87 ttread(c4e3b400,ed261cb0,0,c537f800,ed261cb0,...) at ttread+0x304 ptsread(c537f800,ed261cb0,0,168,0,...) at ptsread+0x38 giant_read(c537f800,ed261cb0,0,1,0,...) at giant_read+0x48 devfs_read_f(c50d21a0,ed261cb0,c53c2100,1,c5d63cc0,...) at devfs_read_f+0x6b aio_daemon(1,ed261d38,c077d7d0,315,c846e000,...) at aio_daemon+0x34c fork_exit(c05da285,1,ed261d38) at fork_exit+0xa6 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xed261d70, ebp = 0 --- The panic is here: if (uio->uio_iovcnt == 0 || uio->uio_resid == 0) panic("ureadc"); 12548 1 12548 0 RLs CPU 0 [aiod5] 12327 1 1395 1003 SE+ aioprn 0xc571d748 syscall 12214 1 1395 1003 SE+ aioprn 0xccf9b9f4 syscall 8510 1 8510 0 RLs CPU 3 [aiod4] 8509 1 8509 0 RLs [aiod3] 8508 1 8508 0 RLs CPU 2 [aiod2] 8507 1 8507 0 RLs CPU 1 [aiod1] I think aio has more input validation bugs. Kris --vtzGhvizbBRQ85DL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFGyJl0Wry0BWjoQKURAgPeAJ9XpbvAFQcdWEhIbYJJ9wMq/JM2vQCeOpT0 LSXTobjzXgXO+h+1F1BZMGA= =ByrI -----END PGP SIGNATURE----- --vtzGhvizbBRQ85DL-- From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 20:54:27 2007 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D96E16A419; Sun, 19 Aug 2007 20:54:27 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 2EEB913C45D; Sun, 19 Aug 2007 20:54:27 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id E1E8B4A3A0; Sun, 19 Aug 2007 16:54:26 -0400 (EDT) Date: Sun, 19 Aug 2007 21:54:26 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: dds@FreeBSD.org, jeff@FreeBSD.org, attilio@FreeBSD.org Message-ID: <20070819214953.I1099@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@FreeBSD.org Subject: Crash in accounting code: encode_long(), due to bad rusage data? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 20:54:27 -0000 Diomidis, Jeff, Attilio, I recently upgraded two servers from FreeBSD 6-STABLE to FreeBSD 7-CURRENT in anticipation of the forthcoming release. Both of them run with accounting enabled at all times. When a large pine session was exiting on one of the two boxes, I ran into the following panic: panic: encode_long: -ve value -32749 KDB: enter: panic db> bt Tracing pid 81759 tid 100377 td 0xc4a76400 kdb_enter(c0a9f844,1,c0a9ab3f,e6937b10,1,...) at kdb_enter+0x32 panic(c0a9ab3f,ffff8013,e6937bb0,e6937c14,c0719dc2,...) at panic+0x124 encode_long(e6937bb0,e6937bb8,e6937bc0,e6937bb8,0,...) at encode_long+0x1d acct_process(c4a76400,c0a9c0c2,162,129,e6937c50,...) at acct_process+0x1c2 exit1(c4a76400,0,e6937d2c,c0a08303,c4a76400,...) at exit1+0x957 sys_exit(c4a76400,e6937cfc,4,e6937d38,c0b4bed8,...) at sys_exit+0x1d syscall(e6937d38) at syscall+0x2b3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x355f2093, esp = 0xbfbfe0ec, ebp = 0xbfbfe108 --- kgdb was of mixed helpfulness: #2 0xc048d575 in db_command_loop () at /usr/src/sys/ddb/db_command.c:401 #3 0xc048ece5 in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_main.c:222 #4 0xc0773d56 in kdb_trap (type=3, code=0, tf=0xe6937a90) at /usr/src/sys/kern/subr_kdb.c:502 #5 0xc0a08aeb in trap (frame=0xe6937a90) at /usr/src/sys/i386/i386/trap.c:621 #6 0xc09ede3b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc0773ed2 in kdb_enter (msg=0xc0a9f844 "panic") at cpufunc.h:60 #8 0xc074c5d4 in panic (fmt=0xc0a9ab3f "encode_long: -ve value %ld") at /usr/src/sys/kern/kern_shutdown.c:547 #9 0xc0719bad in encode_long (val=18) at /usr/src/sys/kern/kern_acct.c:525 #10 0xc0719dc2 in acct_process (td=0xc4a76400) at /usr/src/sys/kern/kern_acct.c:391 #11 0xc072d7e7 in exit1 (td=0xc4a76400, rv=0) at /usr/src/sys/kern/kern_exit.c:355 #12 0xc072e21d in sys_exit (td=Could not find the frame base for "sys_exit". ) at /usr/src/sys/kern/kern_exit.c:98 #13 0xc0a08303 in syscall (frame=0xe6937d38) at /usr/src/sys/i386/i386/trap.c:1008 #14 0xc09edea0 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:196 #15 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) frame 9 #9 0xc0719bad in encode_long (val=18) at /usr/src/sys/kern/kern_acct.c:525 525 KASSERT(val >= 0, ("encode_long: -ve value %ld", val)); (kgdb) print val $1 = 18 (kgdb) list 520 encode_long(long val) 521 { 522 int norm_exp; /* Normalized exponent */ 523 int shift; 524 525 KASSERT(val >= 0, ("encode_long: -ve value %ld", val)); 526 if (val == 0) 527 return (0); 528 norm_exp = fls(val) - 1; 529 shift = FLT_MANT_DIG - norm_exp - 1; (kgdb) up #10 0xc0719dc2 in acct_process (td=0xc4a76400) at /usr/src/sys/kern/kern_acct.c:391 391 acct.ac_mem = encode_long((ru.ru_ixrss + ru.ru_idrss + (kgdb) list 386 tmp = ut; 387 timevaladd(&tmp, &st); 388 /* Convert tmp (i.e. u + s) into hz units to match ru_i*. */ 389 t = tmp.tv_sec * hz + tmp.tv_usec / tick; 390 if (t) 391 acct.ac_mem = encode_long((ru.ru_ixrss + ru.ru_idrss + 392 + ru.ru_isrss) / t); 393 else 394 acct.ac_mem = 0; 395 (kgdb) inspect ru $2 = {ru_utime = {tv_sec = 0, tv_usec = 0}, ru_stime = {tv_sec = 0, tv_usec = 0}, ru_maxrss = 509908, ru_ixrss = 26810576, ru_idrss = -2016077424, ru_isrss = 1044992, ru_minflt = 372535, ru_majflt = 42, ru_nswap = 0, ru_inblock = 58, ru_oublock = 278, ru_msgsnd = 1907, ru_msgrcv = 4671, ru_nsignals = 32, ru_nvcsw = 19892, ru_nivcsw = 4614} I find the large negative value in ru_idrss somewhat sad to contemplate, and while this could well be a problem with capturing of process runtime information, I'd like it if the accounting code were robust against this sort of bug, rather than panicking, and I guess I'd also rather than the process runtime information also be correctly captured :-). I have a usable core dump, and have disabled accounting in the interim. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 21:48:16 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FF1016A418; Sun, 19 Aug 2007 21:48:16 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from webaccess-cl.virtdom.com (webaccess-cl.virtdom.com [216.240.101.25]) by mx1.freebsd.org (Postfix) with ESMTP id 18A2A13C45B; Sun, 19 Aug 2007 21:48:16 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from [192.168.1.103] (c-67-160-44-208.hsd1.wa.comcast.net [67.160.44.208]) (authenticated bits=0) by webaccess-cl.virtdom.com (8.13.6/8.13.6) with ESMTP id l7JLm97R087698 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Sun, 19 Aug 2007 17:48:10 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Sun, 19 Aug 2007 14:50:55 -0700 (PDT) From: Jeff Roberson X-X-Sender: jroberson@10.0.0.1 To: Robert Watson In-Reply-To: <20070819214953.I1099@fledge.watson.org> Message-ID: <20070819144903.U568@10.0.0.1> References: <20070819214953.I1099@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: attilio@freebsd.org, dds@freebsd.org, current@freebsd.org Subject: Re: Crash in accounting code: encode_long(), due to bad rusage data? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 21:48:16 -0000 On Sun, 19 Aug 2007, Robert Watson wrote: > > Diomidis, Jeff, Attilio, > > I recently upgraded two servers from FreeBSD 6-STABLE to FreeBSD 7-CURRENT in > anticipation of the forthcoming release. Both of them run with accounting > enabled at all times. When a large pine session was exiting on one of the > two boxes, I ran into the following panic: > > panic: encode_long: -ve value -32749 > KDB: enter: panic > db> bt > Tracing pid 81759 tid 100377 td 0xc4a76400 > kdb_enter(c0a9f844,1,c0a9ab3f,e6937b10,1,...) at kdb_enter+0x32 > panic(c0a9ab3f,ffff8013,e6937bb0,e6937c14,c0719dc2,...) at panic+0x124 > encode_long(e6937bb0,e6937bb8,e6937bc0,e6937bb8,0,...) at encode_long+0x1d > acct_process(c4a76400,c0a9c0c2,162,129,e6937c50,...) at acct_process+0x1c2 > exit1(c4a76400,0,e6937d2c,c0a08303,c4a76400,...) at exit1+0x957 > sys_exit(c4a76400,e6937cfc,4,e6937d38,c0b4bed8,...) at sys_exit+0x1d > syscall(e6937d38) at syscall+0x2b3 > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x355f2093, esp = 0xbfbfe0ec, > ebp = 0xbfbfe108 --- > > kgdb was of mixed helpfulness: > > #2 0xc048d575 in db_command_loop () at /usr/src/sys/ddb/db_command.c:401 > #3 0xc048ece5 in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_main.c:222 > #4 0xc0773d56 in kdb_trap (type=3, code=0, tf=0xe6937a90) > at /usr/src/sys/kern/subr_kdb.c:502 > #5 0xc0a08aeb in trap (frame=0xe6937a90) at > /usr/src/sys/i386/i386/trap.c:621 > #6 0xc09ede3b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 > #7 0xc0773ed2 in kdb_enter (msg=0xc0a9f844 "panic") at cpufunc.h:60 > #8 0xc074c5d4 in panic (fmt=0xc0a9ab3f "encode_long: -ve value %ld") > at /usr/src/sys/kern/kern_shutdown.c:547 > #9 0xc0719bad in encode_long (val=18) at /usr/src/sys/kern/kern_acct.c:525 > #10 0xc0719dc2 in acct_process (td=0xc4a76400) > at /usr/src/sys/kern/kern_acct.c:391 > #11 0xc072d7e7 in exit1 (td=0xc4a76400, rv=0) > at /usr/src/sys/kern/kern_exit.c:355 > #12 0xc072e21d in sys_exit (td=Could not find the frame base for "sys_exit". > ) at /usr/src/sys/kern/kern_exit.c:98 > #13 0xc0a08303 in syscall (frame=0xe6937d38) > at /usr/src/sys/i386/i386/trap.c:1008 > #14 0xc09edea0 in Xint0x80_syscall () > at /usr/src/sys/i386/i386/exception.s:196 > #15 0x00000033 in ?? () > Previous frame inner to this frame (corrupt stack?) > (kgdb) frame 9 > #9 0xc0719bad in encode_long (val=18) at /usr/src/sys/kern/kern_acct.c:525 > 525 KASSERT(val >= 0, ("encode_long: -ve value %ld", val)); > (kgdb) print val > $1 = 18 > (kgdb) list > 520 encode_long(long val) > 521 { > 522 int norm_exp; /* Normalized exponent */ > 523 int shift; > 524 > 525 KASSERT(val >= 0, ("encode_long: -ve value %ld", val)); > 526 if (val == 0) > 527 return (0); > 528 norm_exp = fls(val) - 1; > 529 shift = FLT_MANT_DIG - norm_exp - 1; > (kgdb) up > #10 0xc0719dc2 in acct_process (td=0xc4a76400) > at /usr/src/sys/kern/kern_acct.c:391 > 391 acct.ac_mem = encode_long((ru.ru_ixrss + ru.ru_idrss ru_idrss an integral value of the amount of unshared memory residing in the data segment of a process (expressed in units of kilobytes * ticks-of-execution). That seems like it's pretty prone to overflow given that this is a 32bit machine. This may just be an improper assert. I'm shocked that noone has run into this so far. Jeff > + > (kgdb) list > 386 tmp = ut; > 387 timevaladd(&tmp, &st); > 388 /* Convert tmp (i.e. u + s) into hz units to match ru_i*. */ > 389 t = tmp.tv_sec * hz + tmp.tv_usec / tick; > 390 if (t) > 391 acct.ac_mem = encode_long((ru.ru_ixrss + ru.ru_idrss > + > 392 + ru.ru_isrss) / t); > 393 else > 394 acct.ac_mem = 0; > 395 > (kgdb) inspect ru > $2 = {ru_utime = {tv_sec = 0, tv_usec = 0}, ru_stime = {tv_sec = 0, > tv_usec = 0}, ru_maxrss = 509908, ru_ixrss = 26810576, > ru_idrss = -2016077424, ru_isrss = 1044992, ru_minflt = 372535, > ru_majflt = 42, ru_nswap = 0, ru_inblock = 58, ru_oublock = 278, > ru_msgsnd = 1907, ru_msgrcv = 4671, ru_nsignals = 32, ru_nvcsw = 19892, > ru_nivcsw = 4614} > > I find the large negative value in ru_idrss somewhat sad to contemplate, and > while this could well be a problem with capturing of process runtime > information, I'd like it if the accounting code were robust against this sort > of bug, rather than panicking, and I guess I'd also rather than the process > runtime information also be correctly captured :-). > > I have a usable core dump, and have disabled accounting in the interim. > > Robert N M Watson > Computer Laboratory > University of Cambridge > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 21:53:55 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE2BD16A418; Sun, 19 Aug 2007 21:53:55 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from webaccess-cl.virtdom.com (webaccess-cl.virtdom.com [216.240.101.25]) by mx1.freebsd.org (Postfix) with ESMTP id A7E2413C428; Sun, 19 Aug 2007 21:53:55 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from [192.168.1.103] (c-67-160-44-208.hsd1.wa.comcast.net [67.160.44.208]) (authenticated bits=0) by webaccess-cl.virtdom.com (8.13.6/8.13.6) with ESMTP id l7JLrqQY088531 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Sun, 19 Aug 2007 17:53:54 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Sun, 19 Aug 2007 14:56:38 -0700 (PDT) From: Jeff Roberson X-X-Sender: jroberson@10.0.0.1 To: Robert Watson In-Reply-To: <20070819144903.U568@10.0.0.1> Message-ID: <20070819145532.O568@10.0.0.1> References: <20070819214953.I1099@fledge.watson.org> <20070819144903.U568@10.0.0.1> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: attilio@freebsd.org, dds@freebsd.org, current@freebsd.org Subject: Re: Crash in accounting code: encode_long(), due to bad rusage data? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 21:53:56 -0000 On Sun, 19 Aug 2007, Jeff Roberson wrote: > On Sun, 19 Aug 2007, Robert Watson wrote: > >> >> Diomidis, Jeff, Attilio, >> >> I recently upgraded two servers from FreeBSD 6-STABLE to FreeBSD 7-CURRENT >> in anticipation of the forthcoming release. Both of them run with >> accounting enabled at all times. When a large pine session was exiting on >> one of the two boxes, I ran into the following panic: >> >> panic: encode_long: -ve value -32749 >> KDB: enter: panic >> db> bt >> Tracing pid 81759 tid 100377 td 0xc4a76400 >> kdb_enter(c0a9f844,1,c0a9ab3f,e6937b10,1,...) at kdb_enter+0x32 >> panic(c0a9ab3f,ffff8013,e6937bb0,e6937c14,c0719dc2,...) at panic+0x124 >> encode_long(e6937bb0,e6937bb8,e6937bc0,e6937bb8,0,...) at encode_long+0x1d >> acct_process(c4a76400,c0a9c0c2,162,129,e6937c50,...) at acct_process+0x1c2 >> exit1(c4a76400,0,e6937d2c,c0a08303,c4a76400,...) at exit1+0x957 >> sys_exit(c4a76400,e6937cfc,4,e6937d38,c0b4bed8,...) at sys_exit+0x1d >> syscall(e6937d38) at syscall+0x2b3 >> Xint0x80_syscall() at Xint0x80_syscall+0x20 >> --- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x355f2093, esp = >> 0xbfbfe0ec, ebp = 0xbfbfe108 --- >> >> kgdb was of mixed helpfulness: >> >> #2 0xc048d575 in db_command_loop () at /usr/src/sys/ddb/db_command.c:401 >> #3 0xc048ece5 in db_trap (type=3, code=0) at >> /usr/src/sys/ddb/db_main.c:222 >> #4 0xc0773d56 in kdb_trap (type=3, code=0, tf=0xe6937a90) >> at /usr/src/sys/kern/subr_kdb.c:502 >> #5 0xc0a08aeb in trap (frame=0xe6937a90) at >> /usr/src/sys/i386/i386/trap.c:621 >> #6 0xc09ede3b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 >> #7 0xc0773ed2 in kdb_enter (msg=0xc0a9f844 "panic") at cpufunc.h:60 >> #8 0xc074c5d4 in panic (fmt=0xc0a9ab3f "encode_long: -ve value %ld") >> at /usr/src/sys/kern/kern_shutdown.c:547 >> #9 0xc0719bad in encode_long (val=18) at /usr/src/sys/kern/kern_acct.c:525 >> #10 0xc0719dc2 in acct_process (td=0xc4a76400) >> at /usr/src/sys/kern/kern_acct.c:391 >> #11 0xc072d7e7 in exit1 (td=0xc4a76400, rv=0) >> at /usr/src/sys/kern/kern_exit.c:355 >> #12 0xc072e21d in sys_exit (td=Could not find the frame base for >> "sys_exit". >> ) at /usr/src/sys/kern/kern_exit.c:98 >> #13 0xc0a08303 in syscall (frame=0xe6937d38) >> at /usr/src/sys/i386/i386/trap.c:1008 >> #14 0xc09edea0 in Xint0x80_syscall () >> at /usr/src/sys/i386/i386/exception.s:196 >> #15 0x00000033 in ?? () >> Previous frame inner to this frame (corrupt stack?) >> (kgdb) frame 9 >> #9 0xc0719bad in encode_long (val=18) at /usr/src/sys/kern/kern_acct.c:525 >> 525 KASSERT(val >= 0, ("encode_long: -ve value %ld", val)); >> (kgdb) print val >> $1 = 18 >> (kgdb) list >> 520 encode_long(long val) >> 521 { >> 522 int norm_exp; /* Normalized exponent */ >> 523 int shift; >> 524 >> 525 KASSERT(val >= 0, ("encode_long: -ve value %ld", val)); >> 526 if (val == 0) >> 527 return (0); >> 528 norm_exp = fls(val) - 1; >> 529 shift = FLT_MANT_DIG - norm_exp - 1; >> (kgdb) up >> #10 0xc0719dc2 in acct_process (td=0xc4a76400) >> at /usr/src/sys/kern/kern_acct.c:391 >> 391 acct.ac_mem = encode_long((ru.ru_ixrss + >> ru.ru_idrss > > ru_idrss an integral value of the amount of unshared memory residing > in the data segment of a process (expressed in units of > kilobytes * ticks-of-execution). > > That seems like it's pretty prone to overflow given that this is a 32bit > machine. This may just be an improper assert. I'm shocked that noone has > run into this so far. Sorry, should elaborate, see below. > > Jeff > >> + >> (kgdb) list >> 386 tmp = ut; >> 387 timevaladd(&tmp, &st); >> 388 /* Convert tmp (i.e. u + s) into hz units to match ru_i*. >> */ >> 389 t = tmp.tv_sec * hz + tmp.tv_usec / tick; >> 390 if (t) >> 391 acct.ac_mem = encode_long((ru.ru_ixrss + >> ru.ru_idrss + >> 392 + ru.ru_isrss) / t); >> 393 else >> 394 acct.ac_mem = 0; >> 395 >> (kgdb) inspect ru >> $2 = {ru_utime = {tv_sec = 0, tv_usec = 0}, ru_stime = {tv_sec = 0, >> tv_usec = 0}, ru_maxrss = 509908, ru_ixrss = 26810576, >> ru_idrss = -2016077424, ru_isrss = 1044992, ru_minflt = 372535, >> ru_majflt = 42, ru_nswap = 0, ru_inblock = 58, ru_oublock = 278, >> ru_msgsnd = 1907, ru_msgrcv = 4671, ru_nsignals = 32, ru_nvcsw = 19892, >> ru_nivcsw = 4614} > Can you tell me what's in t, tmp, hz and tick? Thanks, Jeff > >> I find the large negative value in ru_idrss somewhat sad to contemplate, >> and while this could well be a problem with capturing of process runtime >> information, I'd like it if the accounting code were robust against this >> sort of bug, rather than panicking, and I guess I'd also rather than the >> process runtime information also be correctly captured :-). >> >> I have a usable core dump, and have disabled accounting in the interim. >> >> Robert N M Watson >> Computer Laboratory >> University of Cambridge >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> > From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 21:48:01 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACDA716A418 for ; Sun, 19 Aug 2007 21:48:01 +0000 (UTC) (envelope-from amistry@am-productions.biz) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.freebsd.org (Postfix) with ESMTP id 6CAAD13C45D for ; Sun, 19 Aug 2007 21:48:01 +0000 (UTC) (envelope-from amistry@am-productions.biz) Received: from [192.168.1.100] (cpe-71-72-80-132.columbus.res.rr.com [71.72.80.132]) (authenticated bits=0) by mail.united-ware.com (8.13.8/8.13.8) with ESMTP id l7JMPvOn050285 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 19 Aug 2007 18:26:05 -0400 (EDT) (envelope-from amistry@am-productions.biz) From: Anish Mistry Organization: AM Productions To: David Malone Date: Sun, 19 Aug 2007 17:51:14 -0400 User-Agent: KMail/1.9.6 References: <200708191147.10340.amistry@am-productions.biz> <20070819191647.GA59444@walton.maths.tcd.ie> In-Reply-To: <20070819191647.GA59444@walton.maths.tcd.ie> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1636205.MF3fOSrMhG"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200708191751.23094.amistry@am-productions.biz> X-Virus-Scanned: ClamAV 0.90.3/3997/Sun Aug 19 11:04:14 2007 on mail.united-ware.com X-Virus-Status: Clean X-Mailman-Approved-At: Sun, 19 Aug 2007 21:56:49 +0000 Cc: freebsd-current@freebsd.org Subject: Re: Can't create TCP connections to certain IP addresses X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 21:48:01 -0000 --nextPart1636205.MF3fOSrMhG Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 19 August 2007, David Malone wrote: > On Sun, Aug 19, 2007 at 11:46:52AM -0400, Anish Mistry wrote: > > tcpdump.txt contains a failed connection. tcpdump-good.txt > > contains a succeeded connection. > > As you say, the SYN packet is being sent, but no reply be being > received. Can you run a tcpdump on your router/firewall and see if > the SYN packets are being recieved (and forwarded) and check if the > SYN ACK packets are getting back that far? I'm not sure how to do that with the version of m0nowall that the=20 router is running. But I can exhibit this behavior on the local LAN=20 without going through the router. =2D-=20 Anish Mistry amistry@am-productions.biz AM Productions http://am-productions.biz/ --nextPart1636205.MF3fOSrMhG Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBGyLtbxqA5ziudZT0RAmRiAJ9l7Gonl4nGrzaNuxhXF+fKraeqEgCglzvZ sL1fWbU5ROAbDSyvzqKzsyc= =XWoK -----END PGP SIGNATURE----- --nextPart1636205.MF3fOSrMhG-- From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 23:32:46 2007 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4B5F16A418; Sun, 19 Aug 2007 23:32:46 +0000 (UTC) (envelope-from dds@aueb.gr) Received: from mx-out-04.forthnet.gr (mx-out.forthnet.gr [193.92.150.103]) by mx1.freebsd.org (Postfix) with ESMTP id 2A7B713C46A; Sun, 19 Aug 2007 23:32:45 +0000 (UTC) (envelope-from dds@aueb.gr) Received: from mx-av-01.forthnet.gr (mx-av.forthnet.gr [193.92.150.27]) by mx-out-04.forthnet.gr (8.13.8/8.13.8) with ESMTP id l7JMOAFd029289; Mon, 20 Aug 2007 01:24:10 +0300 Received: from MX-IN-03.forthnet.gr (mx-in-03.forthnet.gr [193.92.150.26]) by mx-av-01.forthnet.gr (8.14.1/8.14.1) with ESMTP id l7JMOAoV017137; Mon, 20 Aug 2007 01:24:10 +0300 Received: from [213.16.200.70] (ppp1-70.kef.forthnet.gr [213.16.200.70]) by MX-IN-03.forthnet.gr (8.14.1/8.14.1) with ESMTP id l7JMNqkO010474; Mon, 20 Aug 2007 01:24:04 +0300 Authentication-Results: MX-IN-03.forthnet.gr smtp.mail=dds@aueb.gr; spf=neutral Authentication-Results: MX-IN-03.forthnet.gr header.from=dds@aueb.gr; sender-id=neutral Message-ID: <46C8C2E6.9030405@aueb.gr> Date: Mon, 20 Aug 2007 01:23:34 +0300 From: Diomidis Spinellis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 MIME-Version: 1.0 To: Robert Watson References: <20070819214953.I1099@fledge.watson.org> In-Reply-To: <20070819214953.I1099@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 19 Aug 2007 23:38:20 +0000 Cc: attilio@FreeBSD.ORG, jeff@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Crash in accounting code: encode_long(), due to bad rusage data? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 23:32:46 -0000 Robert Watson wrote: > I recently upgraded two servers from FreeBSD 6-STABLE to FreeBSD > 7-CURRENT in anticipation of the forthcoming release. Both of them run > with accounting enabled at all times. When a large pine session was > exiting on one of the two boxes, I ran into the following panic: > > panic: encode_long: -ve value -32749 Getting rid of the panic is easy: --- kern_acct.c 2007-08-20 01:15:18.000000000 +0300 +++ kern_acct.c.new 2007-08-20 01:16:06.000000000 +0300 @@ -523,8 +523,7 @@ int norm_exp; /* Normalized exponent */ int shift; - KASSERT(val >= 0, ("encode_long: -ve value %ld", val)); - if (val == 0) + if (val <= 0) return (0); norm_exp = fls(val) - 1; shift = FLT_MANT_DIG - norm_exp - 1; However, as you wrote, this doesn't fix the root of the problem. > I find the large negative value in ru_idrss somewhat sad to contemplate, > and while this could well be a problem with capturing of process runtime > information, I'd like it if the accounting code were robust against this > sort of bug, rather than panicking, and I guess I'd also rather than the > process runtime information also be correctly captured :-). Do you think it makes any sense for encode_long to be correctly encoding negative numbers, or should we concentrate on locating and fixing the negative ru_idrss problem? Diomidis Spinellis - http://www.spinellis.gr From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 23:43:44 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0844416A419 for ; Sun, 19 Aug 2007 23:43:44 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from webaccess-cl.virtdom.com (webaccess-cl.virtdom.com [216.240.101.25]) by mx1.freebsd.org (Postfix) with ESMTP id A9B6913C459 for ; Sun, 19 Aug 2007 23:43:43 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from [192.168.1.103] (c-67-160-44-208.hsd1.wa.comcast.net [67.160.44.208]) (authenticated bits=0) by webaccess-cl.virtdom.com (8.13.6/8.13.6) with ESMTP id l7JNhOWd007978 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Sun, 19 Aug 2007 19:43:25 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Sun, 19 Aug 2007 16:46:10 -0700 (PDT) From: Jeff Roberson X-X-Sender: jroberson@10.0.0.1 To: freebsd-current@freebsd.org, d@delphij.net In-Reply-To: <200708170939.l7H9diEk054469@lurza.secnetix.de> Message-ID: <20070819163934.V568@10.0.0.1> References: <200708170939.l7H9diEk054469@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1647518475-1187567170=:568" Cc: Subject: Re: Why we don't use bzip2 in sysinstall/rescue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 23:43:44 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1647518475-1187567170=:568 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Fri, 17 Aug 2007, Oliver Fromme wrote: > LI Xin wrote: > > As a side note. For networked installation, using bzip2 would reduce > > traffic by ~11%. > > And increase local installation time by 900% (except maybe > on high-end machines). > > I just tested extracting a 10 MB .bz2 file to /dev/null > on our 800 MHz server: It took 57 seconds. Recompressing > the result to .gz, extracting that took only 5 seconds. > The installation data is roughly 30 times that much. I tried this on my 1.8ghz pentium M laptop with 5.6MB of jpg data. I did: tar cvf foo.tar foo cat foo.tar >> /dev/null time bzip2/gzip foo.tar I removed and recreated the tar each time. The cat was to make sure it=20 was in cache, although it certainly was from the creation step before. Anyway, the results are: bzip2 2.452u 0.026s 0:07.65 32.2% 92+3227k 5+43io 0pf+0w 1849c/6w gzip 0.539u 0.020s 0:01.75 31.4% 109+3268k 2+44io 0pf+0w 493c/3w So only 4.6x slower here although my processor is twice as fast. Still, I= =20 imagine local installation is actually dominated by transfer rates from=20 the cd and file creation time on the new volume. Making lots of little=20 files is relatively slow, and I bet we don't use softupdates on the=20 target volume during sysinstall. A better test would be to actually=20 extract a bzip and a gzip from a cd to a local filesystem and=20 measure the times. I wouldn't rule it out just yet. Thanks, Jeff > > Best regards > Oliver > > --=20 > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. > Handelsregister: Registergericht Muenchen, HRA 74606, Gesch=E4ftsfuehrun= g: > secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M=FC= n- > chen, HRB 125758, Gesch=E4ftsf=FChrer: Maik Bachmann, Olaf Erb, Ralf Geb= hart > > FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd > > "... there are two ways of constructing a software design: One way > is to make it so simple that there are _obviously_ no deficiencies and > the other way is to make it so complicated that there are no _obvious_ > deficiencies." -- C.A.R. Hoare, ACM Turing Award Lecture, 1980 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > --0-1647518475-1187567170=:568-- From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 23:49:33 2007 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2E1416A41B; Sun, 19 Aug 2007 23:49:32 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from webaccess-cl.virtdom.com (webaccess-cl.virtdom.com [216.240.101.25]) by mx1.freebsd.org (Postfix) with ESMTP id BA0DA13C45D; Sun, 19 Aug 2007 23:49:32 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from [192.168.1.103] (c-67-160-44-208.hsd1.wa.comcast.net [67.160.44.208]) (authenticated bits=0) by webaccess-cl.virtdom.com (8.13.6/8.13.6) with ESMTP id l7JNnRmF009233 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Sun, 19 Aug 2007 19:49:28 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Sun, 19 Aug 2007 16:52:12 -0700 (PDT) From: Jeff Roberson X-X-Sender: jroberson@10.0.0.1 To: Diomidis Spinellis In-Reply-To: <46C8C2E6.9030405@aueb.gr> Message-ID: <20070819164823.H568@10.0.0.1> References: <20070819214953.I1099@fledge.watson.org> <46C8C2E6.9030405@aueb.gr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: attilio@FreeBSD.ORG, jeff@FreeBSD.ORG, Robert Watson , current@FreeBSD.ORG Subject: Re: Crash in accounting code: encode_long(), due to bad rusage data? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 23:49:33 -0000 On Mon, 20 Aug 2007, Diomidis Spinellis wrote: > Robert Watson wrote: >> I recently upgraded two servers from FreeBSD 6-STABLE to FreeBSD 7-CURRENT >> in anticipation of the forthcoming release. Both of them run with >> accounting enabled at all times. When a large pine session was exiting on >> one of the two boxes, I ran into the following panic: >> >> panic: encode_long: -ve value -32749 > > Getting rid of the panic is easy: > > --- kern_acct.c 2007-08-20 01:15:18.000000000 +0300 > +++ kern_acct.c.new 2007-08-20 01:16:06.000000000 +0300 > @@ -523,8 +523,7 @@ > int norm_exp; /* Normalized exponent */ > int shift; > > - KASSERT(val >= 0, ("encode_long: -ve value %ld", val)); > - if (val == 0) > + if (val <= 0) > return (0); > norm_exp = fls(val) - 1; > shift = FLT_MANT_DIG - norm_exp - 1; > > However, as you wrote, this doesn't fix the root of the problem. > >> I find the large negative value in ru_idrss somewhat sad to contemplate, >> and while this could well be a problem with capturing of process runtime >> information, I'd like it if the accounting code were robust against this >> sort of bug, rather than panicking, and I guess I'd also rather than the >> process runtime information also be correctly captured :-). > > Do you think it makes any sense for encode_long to be correctly encoding > negative numbers, or should we concentrate on locating and fixing the > negative ru_idrss problem? The number overflowed. Based on information from robert on IRC it probably wrapped more than once so the data is meaningless. For this to continue to be useful we'd have to make irss and drss 64bit on 32bit platforms. The problem probably doesn't occur on 64bit machines. Basically irss/drss are kilobytes per tick. If ticks are 1000 that works out to almost bytes per second of runtime. So you can see how this easily overflows with a long-running high-memory application like pine. What do you think about simply putting in a max value if we overflow? We could then make a note about it in process accounting docs. We might want to fix this in rusage as well. Jeff > > Diomidis Spinellis - http://www.spinellis.gr > From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 23:50:58 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2728C16A419 for ; Sun, 19 Aug 2007 23:50:58 +0000 (UTC) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by mx1.freebsd.org (Postfix) with ESMTP id A210C13C428 for ; Sun, 19 Aug 2007 23:50:57 +0000 (UTC) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by freebsd.czest.pl (8.13.4/8.12.9) with ESMTP id l7K07MpF085414 for ; Mon, 20 Aug 2007 00:07:22 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.13.4/8.12.9/Submit) id l7K07Mha085413 for freebsd-current@freebsd.org; Mon, 20 Aug 2007 00:07:22 GMT (envelope-from dunstan) Date: Mon, 20 Aug 2007 00:07:21 +0000 From: "Wojciech A. Koszek" To: freebsd-current@freebsd.org Message-ID: <20070820000721.GA85364@FreeBSD.czest.pl> Mail-Followup-To: "Wojciech A. Koszek" , freebsd-current@freebsd.org References: <20070506164247.GA77786@FreeBSD.czest.pl> <20070719174847.GA5853@outcold.yadt.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <20070719174847.GA5853@outcold.yadt.co.uk> User-Agent: Mutt/1.4.2.1i X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-2.0.2 (freebsd.czest.pl [80.48.250.4]); Mon, 20 Aug 2007 00:07:22 +0000 (UTC) Subject: Re: INCLUDE_CONFIG_FILE patches X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 23:50:58 -0000 On Thu, Jul 19, 2007 at 06:48:47PM +0100, David Taylor wrote: > On Sun, 06 May 2007, Wojciech A. Koszek wrote: > > Hello, > > > > We talked about improved INCLUDE_CONFIG_FILE work some time ago. I > > cleaned it up, and I have prepared a patch for the latest -CURRENT. > > > > It's here: > > > > http://people.freebsd.org/~wkoszek/patches/kernconf.patch > > > > If you have any suggestions, please let me know as I'd really like to > > see this patch into the tree before RELENG_7. > > Hi, I've discovered a small problem with this patch (or at least, > whatever version is in RELENG_6 as of 2007-07-18). > > If your config file contains a trigraph (in my case, I had a comment > containing "??)"), gcc will process it as a trigraph and produce a > warning, which will break the build with a confusing and unhelpful > error message in config.c. This caused no problems before the > new INCLUDE_CONFIG_FILE option (as the config file wasn't included > in the C source file). > > Not sure what the best solution is, but some kind of warning that > this can happen would perhaps save someone 30 minutes of frustration! > Alternatively, some method of escaping any potential trigraphs would > be great. Here's the patch I prepared for you: http://people.freebsd.org/~wkoszek/patches/config-trigraph.patch Apply it within src/usr.sbin/config directory: cd src/usr.sbin/config && patch < config-trigraph.patch And rebuild config(8). Please let me know whether it works for you correctly. I tested it very roughly both with and without -C flag against GENERIC and LINT configurations tweaked a little bit to contain trigraphs within comments and options containing value. Sorry for long delay in replying, Thanks for your report! -- Wojciech A. Koszek wkoszek@FreeBSD.org http://FreeBSD.czest.pl/dunstan/ From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 01:46:20 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E4F916A419 for ; Mon, 20 Aug 2007 01:46:20 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from smtp02.dentaku.gol.com (smtp02.dentaku.gol.com [203.216.5.72]) by mx1.freebsd.org (Postfix) with ESMTP id 52C4813C46A for ; Mon, 20 Aug 2007 01:46:20 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from pat.gol.co.jp ([203.216.1.191] helo=[127.0.0.1]) by smtp02.dentaku.gol.com with esmtpa (Dentaku) id 1IMwLS-0003xV-JV for ; Mon, 20 Aug 2007 10:46:18 +0900 Message-ID: <46C8F269.2030200@fusiongol.com> Date: Mon, 20 Aug 2007 10:46:17 +0900 From: Nathan Butcher User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <46C4FD44.1060105@fusiongol.com> <86odh6ikcf.fsf@ds4.des.no> In-Reply-To: <86odh6ikcf.fsf@ds4.des.no> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV GOL X-Abuse-Complaints: abuse@gol.com Subject: Re: Promise SATA 300 TX4 cause X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 01:46:20 -0000 > Once again, *no*. This commit may have exacerbated the problem, but > people were having trouble with Promise controllers already in April. > > DES I'm not going to argue with you. All I'm saying is that whatever problems happened in April weren't there any longer in the 200706 snapshot when the card was stable. These vm changes ruined that somehow. That's all I know, and that's all I can confirm. If you have any evidence of it being something else - please share your wisdom. I'm all ears. From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 02:47:06 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8BD116A417 for ; Mon, 20 Aug 2007 02:47:06 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.freebsd.org (Postfix) with ESMTP id AB98213C45B for ; Mon, 20 Aug 2007 02:47:06 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.1/8.14.1) id l7K2kweS063085; Sun, 19 Aug 2007 21:46:58 -0500 (CDT) (envelope-from dan) Date: Sun, 19 Aug 2007 21:46:58 -0500 From: Dan Nelson To: Jeff Roberson Message-ID: <20070820024658.GB46690@dan.emsphone.com> References: <20070819214953.I1099@fledge.watson.org> <20070819144903.U568@10.0.0.1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070819144903.U568@10.0.0.1> X-OS: FreeBSD 7.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: attilio@freebsd.org, Robert Watson , dds@freebsd.org, current@freebsd.org Subject: Re: Crash in accounting code: encode_long(), due to bad rusage data? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 02:47:07 -0000 In the last episode (Aug 19), Jeff Roberson said: > On Sun, 19 Aug 2007, Robert Watson wrote: >> Diomidis, Jeff, Attilio, >> >> I recently upgraded two servers from FreeBSD 6-STABLE to FreeBSD >> 7-CURRENT in anticipation of the forthcoming release. Both of them >> run with accounting enabled at all times. When a large pine session >> was exiting on one of the two boxes, I ran into the following panic: >> >> panic: encode_long: -ve value -32749 [..] >> (kgdb) up >> #10 0xc0719dc2 in acct_process (td=0xc4a76400) >> at /usr/src/sys/kern/kern_acct.c:391 >> 391 acct.ac_mem = encode_long((ru.ru_ixrss + >> ru.ru_idrss > > ru_idrss an integral value of the amount of unshared memory > residing in the data segment of a process > (expressed in units of kilobytes * > ticks-of-execution). > > That seems like it's pretty prone to overflow given that this is a 32bit > machine. This may just be an improper assert. I'm shocked that noone has > run into this so far. You'll also hit this any time you get a "calcru: runtime went backwards" which on some machines is very frequent. I disabled the panic as doon as I upgraded to 7 :) -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 07:25:16 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5225B16A417 for ; Mon, 20 Aug 2007 07:25:16 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 10ACF13C45D for ; Mon, 20 Aug 2007 07:25:16 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 8FA9D20B1; Mon, 20 Aug 2007 09:25:09 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 81C9F208A; Mon, 20 Aug 2007 09:25:09 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id 622168444F; Mon, 20 Aug 2007 09:25:09 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Nathan Butcher References: <46C4FD44.1060105@fusiongol.com> <86odh6ikcf.fsf@ds4.des.no> <46C8F269.2030200@fusiongol.com> Date: Mon, 20 Aug 2007 09:25:09 +0200 In-Reply-To: <46C8F269.2030200@fusiongol.com> (Nathan Butcher's message of "Mon\, 20 Aug 2007 10\:46\:17 +0900") Message-ID: <86vebafz1m.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: Promise SATA 300 TX4 cause X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 07:25:16 -0000 Nathan Butcher writes: > Dag-Erling Sm=C3=B8rgrav writes: > > Once again, *no*. This commit may have exacerbated the problem, but > > people were having trouble with Promise controllers already in > > April. > I'm not going to argue with you. All I'm saying is that whatever > problems happened in April weren't there any longer in the 200706 > snapshot when the card was stable. These vm changes ruined that > somehow. It was not stable in any way, shape or form at any point from I started using ZFS in April until I ditched the Promise controller late last month. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 07:26:10 2007 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00F0516A420; Mon, 20 Aug 2007 07:26:10 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id C835C13C469; Mon, 20 Aug 2007 07:26:09 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 7B0D247572; Mon, 20 Aug 2007 03:26:09 -0400 (EDT) Date: Mon, 20 Aug 2007 08:26:09 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Diomidis Spinellis In-Reply-To: <46C8C2E6.9030405@aueb.gr> Message-ID: <20070820082429.L15651@fledge.watson.org> References: <20070819214953.I1099@fledge.watson.org> <46C8C2E6.9030405@aueb.gr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: attilio@FreeBSD.ORG, jeff@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Crash in accounting code: encode_long(), due to bad rusage data? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 07:26:10 -0000 On Mon, 20 Aug 2007, Diomidis Spinellis wrote: > Robert Watson wrote: > >> I recently upgraded two servers from FreeBSD 6-STABLE to FreeBSD 7-CURRENT >> in anticipation of the forthcoming release. Both of them run with >> accounting enabled at all times. When a large pine session was exiting on >> one of the two boxes, I ran into the following panic: >> >> panic: encode_long: -ve value -32749 > > Getting rid of the panic is easy: > > --- kern_acct.c 2007-08-20 01:15:18.000000000 +0300 > +++ kern_acct.c.new 2007-08-20 01:16:06.000000000 +0300 > @@ -523,8 +523,7 @@ > int norm_exp; /* Normalized exponent */ > int shift; > > - KASSERT(val >= 0, ("encode_long: -ve value %ld", val)); > - if (val == 0) > + if (val <= 0) > return (0); > norm_exp = fls(val) - 1; > shift = FLT_MANT_DIG - norm_exp - 1; > > However, as you wrote, this doesn't fix the root of the problem. > >> I find the large negative value in ru_idrss somewhat sad to contemplate, >> and while this could well be a problem with capturing of process runtime >> information, I'd like it if the accounting code were robust against this >> sort of bug, rather than panicking, and I guess I'd also rather than the >> process runtime information also be correctly captured :-). > > Do you think it makes any sense for encode_long to be correctly encoding > negative numbers, or should we concentrate on locating and fixing the > negative ru_idrss problem? I'm not sure it's worth being able to encode negative numbers based on the current set of measurements, but it's probably worth having some sort of encoding for an error case. (0) is a fine encoding of an error from my perspective, and we might consider a printf warning as opposed to a panic so we catch these in a more gentle way. As Jeff has mentioned in his e-mail, this is almost certainly a usage stat that requires upgrading to 64-bit, as 32 bits for that stat is so small as to be entirely unuseful :-). Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 08:48:03 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0881116A417 for ; Mon, 20 Aug 2007 08:48:03 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [IPv6:2001:770:10:300::86e2:510b]) by mx1.freebsd.org (Postfix) with SMTP id DFE2513C457 for ; Mon, 20 Aug 2007 08:48:01 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 20 Aug 2007 09:48:00 +0100 (BST) Date: Mon, 20 Aug 2007 09:47:59 +0100 From: David Malone To: Anish Mistry Message-ID: <20070820084759.GA65560@walton.maths.tcd.ie> References: <200708191147.10340.amistry@am-productions.biz> <20070819191647.GA59444@walton.maths.tcd.ie> <200708191751.23094.amistry@am-productions.biz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200708191751.23094.amistry@am-productions.biz> User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: freebsd-current@freebsd.org Subject: Re: Can't create TCP connections to certain IP addresses X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 08:48:03 -0000 On Sun, Aug 19, 2007 at 05:51:14PM -0400, Anish Mistry wrote: > I'm not sure how to do that with the version of m0nowall that the > router is running. But I can exhibit this behavior on the local LAN > without going through the router. In that case, run a tcpdump on both ends and see if the SYN packet is arriving at the far end. You might also want to try using "tcpdump -s0 -v" to check the checksums on the packets (though they can't always be trusted on the packet's sender if the network card supports checksum offloading). David. From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 10:17:09 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D395C16A418; Mon, 20 Aug 2007 10:17:09 +0000 (UTC) (envelope-from piso@southcross.wired.org) Received: from mail.oltrelinux.com (krisma.oltrelinux.com [194.242.226.43]) by mx1.freebsd.org (Postfix) with ESMTP id 6122313C442; Mon, 20 Aug 2007 10:17:09 +0000 (UTC) (envelope-from piso@southcross.wired.org) Received: from southcross.wired.org (host-84-221-232-126.cust-adsl.tiscali.it [84.221.232.126]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.oltrelinux.com (Postfix) with ESMTP id 90A7C11AE43; Mon, 20 Aug 2007 11:51:00 +0200 (CEST) Received: from southcross.wired.org (localhost [127.0.0.1]) by southcross.wired.org (8.14.1/8.14.1) with ESMTP id l7K9pBBt063846; Mon, 20 Aug 2007 11:51:12 +0200 (CEST) (envelope-from piso@southcross.wired.org) Received: (from piso@localhost) by southcross.wired.org (8.14.1/8.14.1/Submit) id l7K9pAHo063845; Mon, 20 Aug 2007 11:51:10 +0200 (CEST) (envelope-from piso) Date: Mon, 20 Aug 2007 11:51:09 +0200 From: Paolo Pisati To: freebsd-scsi@freebsd.org Message-ID: <20070820095109.GA63694@tin.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.16 (2007-06-09) X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at krisma.oltrelinux.com Cc: freebsd-current@freebsd.org Subject: FreeBSD 6.x/7.x & mpt => "panic: Bad link elm 0xc406d450 next->prev != elm" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 10:17:09 -0000 Hi, i filled a PR (http://www.freebsd.org/cgi/query-pr.cgi?pr=115606) regarding some problems i have with FreeBSD 6.x/7.x and the mpt controller. Basically, any i/o activity on a disk attached to that controller brings a panic. mpt0: mpt_cam_event: 0xc0 mpt0: Unhandled Event Notify Frame. Event 0xc0afa2c0 (ACK not required). mpt0: completing timedout/aborted req 0xc406d450:5896 panic: Bad link elm 0xc406d450 next->prev != elm cpuid = 0 KDB: enter: panic Dumping 1023 MB (2 chunks) chunk 0: 1MB (157 pages) ... ok chunk 1: 1023MB (261868 pages) 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:195 H") at /usr/src/sys/ddb/db_command.c:486 #2 0xc048d095 in db_command_loop () at /usr/src/sys/ddb/db_command.c:401 #3 0xc048e805 in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_main.c:222 #4 0xc0773066 in kdb_trap (type=3, code=0, tf=0xe43fcb80) at /usr/src/sys/kern/subr_kdb.c:502 #5 0xc09fd15b in trap (frame=0xe43fcb80) at /usr/src/sys/i386/i386/trap.c:621 #6 0xc09e2b7b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc07731e2 in kdb_enter (msg=0xc0a93413 "panic") at cpufunc.h:60 #8 0xc074c3e4 in panic (fmt=0xc0a49d68 "Bad link elm %p next->prev != elm") at /usr/src/sys/kern/kern_shutdown.c:547 #9 0xc06065c5 in mpt_scsi_reply_handler (mpt=0xc4066000, req=0xc406d450, reply_desc=65820, reply_frame=0xe43fcc58) at /usr/src/sys/dev/mpt/mpt_cam.c:2661 #10 0xc06033be in mpt_complete_request_chain (mpt=0xc4066000, chain=0xc40663c4, iocstatus=8) at /usr/src/sys/dev/mpt/mpt.c:849 #11 0xc0606734 in mpt_cam_ioc_reset (mpt=0xc4066000, type=0) at /usr/src/sys/dev/mpt/mpt_cam.c:3041 #12 0xc0604acf in mpt_reset (mpt=0xc4066000, reinit=1) at /usr/src/sys/dev/mpt/mpt.c:1145 #13 0xc0607bf2 in mpt_recovery_thread (arg=0xc4066000) at /usr/src/sys/dev/mpt/mpt_cam.c:4176 #14 0xc072e258 in fork_exit (callout=0xc0607920 , arg=0xc4066000, frame=0xe43fcd38) at /usr/src/sys/kern/kern_fork.c:797 #15 0xc09e2bf0 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:205 #1 0xc048cb29 in db_fncall (dummy1=-465581460, dummy2=0, dummy3=524358, dummy4=0xe43fc9d8 " kernel.debug and vmcore are available here: fetch http://people.tomato.it/piso/vmcore.1.gz fetch http://people.tomato.it/piso/kernel.debug.gz On FreeBSD 6.x the panic was different, something like "trap 12: page fault in kernel mode" in softclock thread then i updated the box to 7.x to see if the panic was fixed. The same hw worked flawlessly with FreeBSD 4.x. Hope someone can shed some light. bye, P. From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 10:31:58 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4388916A41A for ; Mon, 20 Aug 2007 10:31:58 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id B049713C468 for ; Mon, 20 Aug 2007 10:31:57 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (vader.bytemobile.ondsl.gr [83.235.244.135]) (authenticated bits=128) by igloo.linux.gr (8.14.1/8.14.1/Debian-8) with ESMTP id l7KAVCgU017198 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 20 Aug 2007 13:31:21 +0300 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.1/8.14.1) with ESMTP id l7KAUtmg003025; Mon, 20 Aug 2007 13:31:11 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.14.1/8.14.1/Submit) id l7KAUrZE003024; Mon, 20 Aug 2007 13:30:53 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Mon, 20 Aug 2007 13:30:52 +0300 From: Giorgos Keramidas To: Jeff Roberson Message-ID: <20070820103052.GA2997@kobe.laptop> References: <200708170939.l7H9diEk054469@lurza.secnetix.de> <20070819163934.V568@10.0.0.1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070819163934.V568@10.0.0.1> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.926, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.47, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-current@freebsd.org, d@delphij.net Subject: Re: Why we don't use bzip2 in sysinstall/rescue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 10:31:58 -0000 On 2007-08-19 16:46, Jeff Roberson wrote: >On Fri, 17 Aug 2007, Oliver Fromme wrote: >>LI Xin wrote: >>> As a side note. For networked installation, using bzip2 would >>> reduce traffic by ~11%. >> >> And increase local installation time by 900% (except maybe on >> high-end machines). >> >> I just tested extracting a 10 MB .bz2 file to /dev/null on our 800 >> MHz server: It took 57 seconds. Recompressing the result to .gz, >> extracting that took only 5 seconds. The installation data is >> roughly 30 times that much. > > I tried this on my 1.8ghz pentium M laptop with 5.6MB of jpg data. > > I did: > > tar cvf foo.tar foo > cat foo.tar >> /dev/null > time bzip2/gzip foo.tar > > I removed and recreated the tar each time. The cat was to make sure > it was in cache, although it certainly was from the creation step > before. > > Anyway, the results are: > > bzip2 > 2.452u 0.026s 0:07.65 32.2% 92+3227k 5+43io 0pf+0w 1849c/6w > > gzip > 0.539u 0.020s 0:01.75 31.4% 109+3268k 2+44io 0pf+0w 493c/3w > > So only 4.6x slower here although my processor is twice as fast. > Still, I imagine local installation is actually dominated by transfer > rates from the cd and file creation time on the new volume. Making > lots of little files is relatively slow, and I bet we don't use > softupdates on the target volume during sysinstall. A better test > would be to actually extract a bzip and a gzip from a cd to a local > filesystem and measure the times. My own tests with compressing stuff yielded similar results to what Oliver and Jeff have. bzip2 results in 5-10% more compression, but at the expense of 4x or 5x CPU time to compress everything. A more interesting test would be what Jeff suggests, i.e. to find out what the CPU-time penalty of *decompressing* bzip2 archives would be, and writing them back on disk. - Giorgos From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 10:34:37 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2385516A41A for ; Mon, 20 Aug 2007 10:34:37 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mx1.freebsd.org (Postfix) with ESMTP id 7E8E613C481 for ; Mon, 20 Aug 2007 10:34:36 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l7KAYP35001880; Mon, 20 Aug 2007 20:34:25 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l7KAYOnd001879; Mon, 20 Aug 2007 20:34:24 +1000 (EST) (envelope-from peter) Date: Mon, 20 Aug 2007 20:34:24 +1000 From: Peter Jeremy To: Jeff Roberson Message-ID: <20070820103424.GG1164@turion.vk2pj.dyndns.org> References: <200708170939.l7H9diEk054469@lurza.secnetix.de> <20070819163934.V568@10.0.0.1> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="h31gzZEtNLTqOjlF" Content-Disposition: inline In-Reply-To: <20070819163934.V568@10.0.0.1> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org Subject: Re: Why we don't use bzip2 in sysinstall/rescue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 10:34:37 -0000 --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-Aug-19 16:46:10 -0700, Jeff Roberson wro= te: >I tried this on my 1.8ghz pentium M laptop with 5.6MB of jpg data. > >I did: > >tar cvf foo.tar foo >cat foo.tar >> /dev/null >time bzip2/gzip foo.tar > >I removed and recreated the tar each time. The cat was to make sure it wa= s=20 >in cache, although it certainly was from the creation step before. > >Anyway, the results are: > >bzip2 >2.452u 0.026s 0:07.65 32.2% 92+3227k 5+43io 0pf+0w 1849c/6w > >gzip >0.539u 0.020s 0:01.75 31.4% 109+3268k 2+44io 0pf+0w 493c/3w I don't believe this is a reasonable test because: 1) You are measuring compression time, whilst it's decompression time that is relevant to installation. 2) jpeg images should not be compressible and are not representative of the type of data in a FreeBSD release. I've tried what I believe is a more reasonable benchmark on an Athlon XP-1800, running a recent 7-CURRENT using all the installation images in 6.2-RELEASE-i386-disk1.iso. I concatenated all the 6.2-RELEASE/*/*.?? parts into */*.tgz files as well as copying ports.tgz (a total of 31 files). I also decompressed each file and recompressed it into a bzip2 file. The total sizes were: */*.tbz: 237717490 */*.tgz: 281754511 Like you, I used "cat */*.t{g,b}z >/dev/null" to cache the files and use systat to verify that they were cached. Timing the gzcat and bzcat runs gives: gzcat -v */*.tgz > /dev/null 12.01s user 0.88s system 98% cpu 13.115 total gzcat -v */*.tgz > /dev/null 11.95s user 0.95s system 98% cpu 13.124 total gzcat -v */*.tgz > /dev/null 11.96s user 0.91s system 98% cpu 13.092 total bzcat -v */*.tbz > /dev/null 153.29s user 3.43s system 98% cpu 2:39.03 tot= al bzcat -v */*.tbz > /dev/null 153.32s user 3.26s system 98% cpu 2:39.14 tot= al bzcat -v */*.tbz > /dev/null 153.16s user 3.48s system 98% cpu 2:39.02 tot= al This is nearly 13:1 slower for bzcat, with a size reduction of about 15%. As for the CPU vs I/O tradeoff, I believe that gzcat will be I/O bound whilst bzcat will be CPU bound in most situations, though I haven't actually verified this. --=20 Peter Jeremy --h31gzZEtNLTqOjlF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGyW4w/opHv/APuIcRAmReAKCfSZuBMvLC5yvHcOfX1iDw3nstPACfRKw6 Ou72FokBGz6lfivWXCrFQIQ= =9uD6 -----END PGP SIGNATURE----- --h31gzZEtNLTqOjlF-- From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 10:35:54 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D1AD16A417 for ; Mon, 20 Aug 2007 10:35:54 +0000 (UTC) (envelope-from karol.kwiat@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.freebsd.org (Postfix) with ESMTP id 07CA013C4B0 for ; Mon, 20 Aug 2007 10:35:53 +0000 (UTC) (envelope-from karol.kwiat@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so621691nfb for ; Mon, 20 Aug 2007 03:35:52 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:openpgp:content-type; b=gMjMbHdFn7FGpqaHm+TsnMSZYBcFp9SXcBNkl68ILOSR1Po6+Cu19vJnA1nCCkzeVnnQRTpl/avS7G30RIdmHBk4y50V8VqpvTh/x6RVisou6vcCEIJEEDm7pvMMuQzn2hWNxwWHsD3n4FWGHohh5xHMAlZrGhGtQDDAzF4tcvo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:openpgp:content-type; b=hWnlOswOfNs7Lhm2qxgBcFj2vjKpMr+NECeFMdefAiHbADgmj7wmYhwcFRjzflnu3esUZLWTmlM30+xLC6g9GPxWBh03ocRl+XB3pu2YLkjev1xDiTFQiqEaErL2Vk9AjfwSUZinKr4OQ/laO6BjXVOr53GUaA5Re2lyp3HH2YU= Received: by 10.86.79.19 with SMTP id c19mr4440134fgb.1187606152505; Mon, 20 Aug 2007 03:35:52 -0700 (PDT) Received: from persephone.orchid.homeunix.org ( [84.10.173.180]) by mx.google.com with ESMTPS id g28sm9418892fkg.2007.08.20.03.35.50 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 20 Aug 2007 03:35:51 -0700 (PDT) Message-ID: <46C96E75.7070106@gmail.com> Date: Mon, 20 Aug 2007 12:35:33 +0200 From: Karol Kwiatkowski User-Agent: Thunderbird 2.0.0.6 (X11/20070803) MIME-Version: 1.0 To: Craig Rodrigues References: <46BAF87E.8020406@gmail.com> <20070815183852.GA2463@crodrigues.org> In-Reply-To: <20070815183852.GA2463@crodrigues.org> X-Enigmail-Version: 0.95.2 OpenPGP: id=06E09309; url=http://www.orchid.homeunix.org/carlos/gpg/0x06E09309.asc Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enigE01E9A716E9BC50B4DD7B8C5" Cc: Scot Hetzel , freebsd-current@freebsd.org Subject: Re: Can't remove 'noatime' on mounted filesystem on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: karol.kwiat@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 10:35:54 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE01E9A716E9BC50B4DD7B8C5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Craig Rodrigues wrote: > On Thu, Aug 09, 2007 at 01:20:30PM +0200, Karol Kwiatkowski wrote: >> It seems to be impossible to remove 'noatime' property on mounted >> filesystem (via -u option): >=20 > Hi, >=20 > Can you update your sources so that you get this patch: > http://lists.freebsd.org/pipermail/cvs-src/2007-August/081243.html >=20 > This should address your issue. Yes, that fixed it (with UFS), thanks. Karol --=20 Karol Kwiatkowski OpenPGP 0x06E09309 --------------enigE01E9A716E9BC50B4DD7B8C5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBRslufQhgT0HIecD5AQhVogf/TymC6OLl3sN4rzPswwv5/IBpw2xguVOg JsD2Gt7U50OHNxaCYIUQaFPuG/n7Bmg+DwU/VfeI/l67+9uvxll4VlXCDMTSM4M1 voXItTG8UFh7GRohd1h9qmqsXgkTRVEVQUC84vEbM9TtBSMyhaRFpxGK7WGwBI1C yfm8UIULrE4Ap9vR21I5eyT8hwynI9+DRF2W26a/x+fx+2OqkgiWJUfs4gVmfOxb ZHXEn4g7LkRLO5zpspQgL504Nd7iw+FfxZy4MxS0k+ntDRXjcS6cYy7mT0YgOG5N po8dSmZh2yFxQ60Haaymyq5hHyvm3+0KK0RnUUw1Ye2PdcBYmyEQMw== =Ar4H -----END PGP SIGNATURE----- --------------enigE01E9A716E9BC50B4DD7B8C5-- From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 10:38:37 2007 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B3ED16A420; Mon, 20 Aug 2007 10:38:37 +0000 (UTC) (envelope-from dds@aueb.gr) Received: from mx-out-01.forthnet.gr (mx-out.forthnet.gr [193.92.150.103]) by mx1.freebsd.org (Postfix) with ESMTP id 5BA9B13C458; Mon, 20 Aug 2007 10:38:35 +0000 (UTC) (envelope-from dds@aueb.gr) Received: from mx-av-01.forthnet.gr (mx-av.forthnet.gr [193.92.150.27]) by mx-out-01.forthnet.gr (8.13.8/8.13.8) with ESMTP id l7KAcKGg029120; Mon, 20 Aug 2007 13:38:20 +0300 Received: from MX-IN-04.forthnet.gr (mx-in-04.forthnet.gr [193.92.150.163]) by mx-av-01.forthnet.gr (8.14.1/8.14.1) with ESMTP id l7KAcK0R017355; Mon, 20 Aug 2007 13:38:20 +0300 Received: from [213.16.200.36] (ppp1-36.kef.forthnet.gr [213.16.200.36]) by MX-IN-04.forthnet.gr (8.14.1/8.14.1) with ESMTP id l7KAcAwG011497; Mon, 20 Aug 2007 13:38:12 +0300 Authentication-Results: MX-IN-04.forthnet.gr smtp.mail=dds@aueb.gr; spf=neutral Authentication-Results: MX-IN-04.forthnet.gr header.from=dds@aueb.gr; sender-id=neutral Message-ID: <46C96EFE.6070400@aueb.gr> Date: Mon, 20 Aug 2007 13:37:50 +0300 From: Diomidis Spinellis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 MIME-Version: 1.0 To: Jeff Roberson References: <20070819214953.I1099@fledge.watson.org> <46C8C2E6.9030405@aueb.gr> <20070819164823.H568@10.0.0.1> In-Reply-To: <20070819164823.H568@10.0.0.1> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 20 Aug 2007 11:18:48 +0000 Cc: attilio@FreeBSD.ORG, jeff@FreeBSD.ORG, Robert Watson , current@FreeBSD.ORG Subject: Re: Crash in accounting code: encode_long(), due to bad rusage data? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 10:38:37 -0000 Jeff Roberson wrote: >> Robert Watson wrote: >>> I recently upgraded two servers from FreeBSD 6-STABLE to FreeBSD >>> 7-CURRENT in anticipation of the forthcoming release. Both of them >>> run with accounting enabled at all times. When a large pine session >>> was exiting on one of the two boxes, I ran into the following panic: >>> >>> panic: encode_long: -ve value -32749 [...] > What do you think about simply putting in a max value if we overflow? > We could then make a note about it in process accounting docs. We might > want to fix this in rusage as well. Encoding LONG_MAX and issuing a printf warning is I think a reasonable solution. I'll be away from a broadband connection until Friday, so if anybody else wants to commit this, go ahead. Otherwise I can do it over the coming weekend. Diomidis Spinellis - http://www.spinellis.gr From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 11:20:29 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB17D16A420 for ; Mon, 20 Aug 2007 11:20:29 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: from akis.salford.ac.uk (akis.salford.ac.uk [146.87.0.14]) by mx1.freebsd.org (Postfix) with SMTP id 1245313C468 for ; Mon, 20 Aug 2007 11:20:28 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 58497 invoked by uid 98); 20 Aug 2007 12:20:25 +0100 Received: from 146.87.255.121 by akis.salford.ac.uk (envelope-from , uid 401) with qmail-scanner-2.01 (clamdscan: 0.90/3843. spamassassin: 3.1.8. Clear:RC:1(146.87.255.121):. Processed in 0.030469 secs); 20 Aug 2007 11:20:25 -0000 Received: from rust.salford.ac.uk (HELO rust.salford.ac.uk) (146.87.255.121) by akis.salford.ac.uk (qpsmtpd/0.3x.614) with SMTP; Mon, 20 Aug 2007 12:20:25 +0100 Received: (qmail 93649 invoked by uid 1002); 20 Aug 2007 11:20:23 -0000 Date: 20 Aug 2007 11:20:23 -0000 Message-ID: <20070820112023.93648.qmail@rust.salford.ac.uk> To: freebsd-current@freebsd.org From: "Mark Powell" In-Reply-To: <20070818163810.I75076@rust.salford.ac.uk> References: <20070818163810.I75076@rust.salford.ac.uk> Subject: PATA-SATA convertor drive inaccessibility (was 7.0-CURRENT MCP55 PATA to SATA convertor problems on Asus M2N32 WS Pro) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 11:20:29 -0000 Replying to my own posts :( Surely this problem with PATA-SATA convertors not working is a minor oversight somewhere, if they are working fine in 6.2? Isn't this going to affect everyone with such convertors? Without wanting to cause offence, isn't that going to be a bit of an embarassing show stopper for 7.0-RELEASE? Many thanks. From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 11:42:13 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC0EE16A46C for ; Mon, 20 Aug 2007 11:42:13 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id A110513C461 for ; Mon, 20 Aug 2007 11:42:13 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (localhost [127.0.0.1]) by blah.sun-fish.com (Postfix) with ESMTP id E8F3D1B10EEB; Mon, 20 Aug 2007 13:42:11 +0200 (CEST) Received: from hater.cmotd.com (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id E54BE1B10EE8; Mon, 20 Aug 2007 13:42:11 +0200 (CEST) Message-ID: <46C97E13.3080002@moneybookers.com> Date: Mon, 20 Aug 2007 14:42:11 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.4pre (X11/20070711) MIME-Version: 1.0 To: Eygene Ryabinkin References: <46C18B60.8050400@moneybookers.com> <20070814145759.GB25169@void.codelabs.ru> <20070814193150.GA21553@rot26.obsecurity.org> <46C30FA6.7060108@moneybookers.com> <20070815145640.GQ988@void.codelabs.ru> <46C319DD.3010806@moneybookers.com> <20070815172731.GR988@void.codelabs.ru> <46C3FEBC.80409@moneybookers.com> <20070816080516.GW988@void.codelabs.ru> <46C55684.4050402@moneybookers.com> <20070817083135.GM988@void.codelabs.ru> In-Reply-To: <20070817083135.GM988@void.codelabs.ru> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP on BLAH Cc: current@freebsd.org Subject: Re: "tcpflags 0x18; tcp_do_segment" kernel messages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 11:42:14 -0000 Hello Eygene, Eygene Ryabinkin wrote: > Stefan, good day. > > Fri, Aug 17, 2007 at 11:04:20AM +0300, Stefan Lambrev wrote: > >> Their response is that the mail server timeout. >> > > And how they are detecting the timeout? They are using alarm(), > just polling for the time with non-blocking read calls, setting the > socket timeout or something else? > They do not provide such information. But they have some kind of cronjob to restart the program if the PHP script stall, which makes me think that it is not something very rare in this case. I'm still waiting better response from their support team and if this happened will let you know. > >> Now the question is why the program things that the server timeouts when it >> does not :) >> > > May be this is connected to the socket timeout stuff: chances are > good that the PHP program uses apr_socket_timeout_set(), so there > can be issues with SO_SNDTIMEO/SO_RCVTIMEO socket options in the > -CURRENT. At least Apache (that I have problems with) sets keep-alived > sockets with apr_socket_timeout_set(). I will try to have a look > if this can be true. > > Thanks for your information! > > Mike, Robert, there are chances that some timeout code behaves > weirdly. And maybe the magic number 3 (every 3rd keep-alived > connection seems to be dropped due to the timeout, Stefan sees it > too) should be searched in the timeout code. Maybe you can give > some hints or point to the exact place where the error can occur? > > Thank you. > -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 12:48:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C038E16A420 for ; Mon, 20 Aug 2007 12:48:18 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 509D913C491 for ; Mon, 20 Aug 2007 12:48:17 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id l7KCmGmc092403; Mon, 20 Aug 2007 14:48:16 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id l7KCmAtZ053652 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Aug 2007 14:48:10 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id l7KCmAYS097447; Mon, 20 Aug 2007 14:48:10 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id l7KCm9bx097446; Mon, 20 Aug 2007 14:48:09 +0200 (CEST) (envelope-from ticso) Date: Mon, 20 Aug 2007 14:48:09 +0200 From: Bernd Walter To: Mark Powell Message-ID: <20070820124808.GM72415@cicely12.cicely.de> References: <20070818163810.I75076@rust.salford.ac.uk> <20070820112023.93648.qmail@rust.salford.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070820112023.93648.qmail@rust.salford.ac.uk> X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1.8, BAYES_00=-2.599 autolearn=ham version=3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on cicely12.cicely.de Cc: freebsd-current@freebsd.org Subject: Re: PATA-SATA convertor drive inaccessibility (was 7.0-CURRENT MCP55 PATA to SATA convertor problems on Asus M2N32 WS Pro) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 12:48:18 -0000 On Mon, Aug 20, 2007 at 11:20:23AM -0000, Mark Powell wrote: > Replying to my own posts :( > > Surely this problem with PATA-SATA convertors not working is a minor oversight > somewhere, if they are working fine in 6.2? > Isn't this going to affect everyone with such convertors? > Without wanting to cause offence, isn't that going to be a bit of an embarassing > show stopper for 7.0-RELEASE? Don't know about your problem, but I use such converters without problems. atapci1: port 0xeff0-0xeff7,0xefe4-0xefe7,0xefa8-0xefaf,0xefe0-0xefe3,0xef60-0xef6f mem 0xffafcc00-0xffafcfff irq 7 at device 15.0 on pci0 atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] ata4: on atapci1 ata4: [ITHREAD] ata5: on atapci1 ata5: [ITHREAD] [...] ad4: 98166MB at ata2-master UDMA100 ad6: 98166MB at ata3-master UDMA100 OS is -current from 12th 07 this year. About your problem: there are SATA controllers out there that put two SATA header onto the same channel. In this case the PATA bridging can't work in that case, because they have to be alone on each channel. You might want to try a single drive first and test all SATA ports. You have to know that those converters are not making PATA drives into PATA, they bridge PATA over SATA, therefor FreeBSD knows and can even control the PATA transfer-mode. -- B.Walter http://www.bwct.de http://www.fizon.de bernd@bwct.de info@bwct.de support@fizon.de From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 12:55:09 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2660316A41B for ; Mon, 20 Aug 2007 12:55:09 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: from akis.salford.ac.uk (akis.salford.ac.uk [146.87.0.14]) by mx1.freebsd.org (Postfix) with SMTP id 59C0B13C4A7 for ; Mon, 20 Aug 2007 12:55:07 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 12044 invoked by uid 98); 20 Aug 2007 13:55:06 +0100 Received: from 146.87.255.121 by akis.salford.ac.uk (envelope-from , uid 401) with qmail-scanner-2.01 (clamdscan: 0.90/3843. spamassassin: 3.1.8. Clear:RC:1(146.87.255.121):. Processed in 0.069413 secs); 20 Aug 2007 12:55:06 -0000 Received: from rust.salford.ac.uk (HELO rust.salford.ac.uk) (146.87.255.121) by akis.salford.ac.uk (qpsmtpd/0.3x.614) with SMTP; Mon, 20 Aug 2007 13:55:06 +0100 Received: (qmail 94276 invoked by uid 1002); 20 Aug 2007 12:55:03 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 20 Aug 2007 12:55:03 -0000 Date: Mon, 20 Aug 2007 13:55:03 +0100 (BST) From: "Mark Powell" To: sos@freebsd.org, ticso@cicely.de In-Reply-To: <20070820124808.GM72415@cicely12.cicely.de> Message-ID: <20070820135021.W93439@rust.salford.ac.uk> References: <20070818163810.I75076@rust.salford.ac.uk> <20070820112023.93648.qmail@rust.salford.ac.uk> <20070820124808.GM72415@cicely12.cicely.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: PATA-SATA convertor drive inaccessibility (was 7.0-CURRENT MCP55 PATA to SATA convertor problems on Asus M2N32 WS Pro) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 12:55:09 -0000 On Mon, 20 Aug 2007, Bernd Walter wrote: > About your problem: there are SATA controllers out there that put two > SATA header onto the same channel. In this case the PATA bridging can't > work in that case, because they have to be alone on each channel. You > might want to try a single drive first and test all SATA ports. You have > to know that those converters are not making PATA drives into PATA, they > bridge PATA over SATA, therefor FreeBSD knows and can even control the > PATA transfer-mode. Ok some further info. I can put a single PATA drive converted to SATA onto an MCP55 SATA port, with 6.2 on it. It will bootup detect drives and shut down ok. More importantly the BIOS will then properly detect all drives at restart i.e. no problems at all. With 7.0 I have found that with just a proper SATA drive connected or even no SATA drives at all connected, after 7.0 has run the BIOS cannot then detect any drives at restart. It just hangs. Something 7.0 is doing is screwing up this controller. So not only is 7.0 failing to probe PATA-SATA converted drives, it is also messing up the controller full stop. There seems to be something screwy in the 7.0 ata code? Many thanks. -- Mark Powell - UNIX System Administrator - The University of Salford Information Services Division, Clifford Whitworth Building, Salford University, Manchester, M5 4WT, UK. Tel: +44 161 295 4837 Fax: +44 161 295 5888 www.pgp.com for PGP key From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 13:06:56 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B33D316A41B for ; Mon, 20 Aug 2007 13:06:56 +0000 (UTC) (envelope-from lists_freebsd_org@07.antispam.web-wahnsinn.de) Received: from smtprelay07.ispgateway.de (smtprelay07.ispgateway.de [80.67.29.7]) by mx1.freebsd.org (Postfix) with ESMTP id 25F2F13C4B3 for ; Mon, 20 Aug 2007 13:06:55 +0000 (UTC) (envelope-from lists_freebsd_org@07.antispam.web-wahnsinn.de) Received: (qmail 22979 invoked from network); 20 Aug 2007 13:06:54 -0000 Received: from unknown (HELO [192.168.1.34]) (023415@[84.56.41.234]) (envelope-sender ) by smtprelay07.ispgateway.de (qmail-ldap-1.03) with SMTP; 20 Aug 2007 13:06:54 -0000 From: Tobias Grosser To: Greg Lewis In-Reply-To: <20070816144458.kv2datmjkk4kcok8@webmail.df.eu> References: <1186303666.36623.23.camel@tobias.wg.> <20070815144804.GC5151@misty.eyesbeyond.com> <20070816144458.kv2datmjkk4kcok8@webmail.df.eu> Content-Type: text/plain Date: Mon, 20 Aug 2007 15:06:38 +0200 Message-Id: <1187615198.939.3.camel@tobias.wg.> Mime-Version: 1.0 X-Mailer: Evolution 2.10.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-java@freebsd.org Subject: Re: Gcc bugs break java/jdk15 build? [Workaround] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lists_freebsd_org@07.antispam.web-wahnsinn.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 13:06:56 -0000 Am Donnerstag, den 16.08.2007, 14:44 +0200 schrieb Tobias Grosser: > Zitat von Greg Lewis : > > On Sun, Aug 05, 2007 at 10:47:46AM +0200, Tobias Grosser wrote: > >> since the last gcc import (Update to 4.2) I had problems to compile > >> java/jdk15 (using linux-sun-jdk14/15 and diablo-jdk15), because often > >> the linux-sun-jdk crashed or I got the following errors: > >> > >> ../../../../../src/share/classes/sun/security/util/SignatureFileVerifier.java:22: cannot find > >> symbol > >> symbol : class timestamp > >> location: package sun.security > >> import sun.security.timestamp.TimestampToken; > >> ^ > > > > Can you, and people with similar errors, try again after updating to a > > -CURRENT after the GCC 4.2.1 import. This should fix these errors but > > it would be great to get some confirmation. > > I tried already with the gcc 4.2.1 patch from > (http://people.freebsd.org/~kan/contrib-gcc421.tar.gz), > but the build also breaks with optimization. (I am not sure, if it was > the same error) Without optimization it was working. > When I am back from holiday at Tuesday, I will try again after gcc > import, and post the error log or report success. ;-) I am back again. The java build also breaks with freebsd from yesterday without make.conf, but works if I add "CFLAGS=-O2 -fno-tree-vrp -pipe" to my make.conf From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 13:27:59 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6690016A418 for ; Mon, 20 Aug 2007 13:27:59 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: from abbe.salford.ac.uk (abbe.salford.ac.uk [146.87.0.10]) by mx1.freebsd.org (Postfix) with SMTP id 96BD613C461 for ; Mon, 20 Aug 2007 13:27:56 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 71419 invoked by uid 98); 20 Aug 2007 14:27:51 +0100 Received: from 146.87.255.121 by abbe.salford.ac.uk (envelope-from , uid 401) with qmail-scanner-2.01 (clamdscan: 0.90/3838. spamassassin: 3.1.8. Clear:RC:1(146.87.255.121):. Processed in 0.052014 secs); 20 Aug 2007 13:27:51 -0000 Received: from rust.salford.ac.uk (HELO rust.salford.ac.uk) (146.87.255.121) by abbe.salford.ac.uk (qpsmtpd/0.3x.614) with SMTP; Mon, 20 Aug 2007 14:27:51 +0100 Received: (qmail 94509 invoked by uid 1002); 20 Aug 2007 13:27:49 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 20 Aug 2007 13:27:49 -0000 Date: Mon, 20 Aug 2007 14:27:49 +0100 (BST) From: "Mark Powell" To: sos@freebsd.org, ticso@cicely.de In-Reply-To: <20070820135021.W93439@rust.salford.ac.uk> Message-ID: <20070820142224.D94437@rust.salford.ac.uk> References: <20070818163810.I75076@rust.salford.ac.uk> <20070820112023.93648.qmail@rust.salford.ac.uk> <20070820124808.GM72415@cicely12.cicely.de> <20070820135021.W93439@rust.salford.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: MCP55 SATA problems (was Re: PATA-SATA convertor drive inaccessibility) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 13:27:59 -0000 On Mon, 20 Aug 2007, Mark Powell wrote: > Ok some further info. This seems MCP55 related. I have moved my two PATA SATA converted drives onto a Sil 3132 2-port PCI-E controller. I have no drives on the MCP55 SATA ports. I have cabled my 3rd drive directly into the MCP55 IDE port. No problems whatsoever with 7.0 now. My zfs raidz has come back to life :) The system reboots properly now and the BIOS is happy restarting the PC. 7.0 is definately doing something screwy with the MCP55 SATA controllers, but only when a drive is connected to them. Otherwise it's fine. Many thanks. -- Mark Powell - UNIX System Administrator - The University of Salford Information Services Division, Clifford Whitworth Building, Salford University, Manchester, M5 4WT, UK. Tel: +44 161 295 4837 Fax: +44 161 295 5888 www.pgp.com for PGP key From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 13:46:51 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34D8C16A41A; Mon, 20 Aug 2007 13:46:51 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from spider.deepcore.dk (cpe.atm2-0-70484.0x50a6c9a6.abnxx16.customer.tele.dk [80.166.201.166]) by mx1.freebsd.org (Postfix) with ESMTP id B694A13C46C; Mon, 20 Aug 2007 13:46:50 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from ws.deepcore.dk (ws.deepcore.dk [194.192.25.137]) by spider.deepcore.dk (8.13.8/8.13.8) with ESMTP id l7KDkk5c015543; Mon, 20 Aug 2007 15:46:46 +0200 (CEST) (envelope-from sos@deepcore.dk) Message-ID: <46C99B46.3000605@deepcore.dk> Date: Mon, 20 Aug 2007 15:46:46 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Mark Powell References: <20070818163810.I75076@rust.salford.ac.uk> <20070820112023.93648.qmail@rust.salford.ac.uk> <20070820124808.GM72415@cicely12.cicely.de> <20070820135021.W93439@rust.salford.ac.uk> <20070820142224.D94437@rust.salford.ac.uk> In-Reply-To: <20070820142224.D94437@rust.salford.ac.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@FreeBSD.ORG, ticso@cicely.de, sos@FreeBSD.ORG Subject: Re: MCP55 SATA problems (was Re: PATA-SATA convertor drive inaccessibility) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 13:46:51 -0000 Mark Powell wrote: > On Mon, 20 Aug 2007, Mark Powell wrote: > >> Ok some further info. > > This seems MCP55 related. > I have moved my two PATA SATA converted drives onto a Sil 3132=20 > 2-port PCI-E controller. I have no drives on the MCP55 SATA ports. I=20 > have cabled my 3rd drive directly into the MCP55 IDE port. No problems = > whatsoever with 7.0 now. My zfs raidz has come back to life :) > The system reboots properly now and the BIOS is happy restarting the = > PC. > 7.0 is definately doing something screwy with the MCP55 SATA=20 > controllers, but only when a drive is connected to them. Otherwise=20 > it's fine. Hmm, it does work fine here even with PATA<>SATA dongels in use on a=20 MCP55 system... I'll check the code for obvious faults once again, but since nVidia=20 doesn't hand out docs it might be more sinister than that.... -S=F8ren From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 14:44:36 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC18416A420; Mon, 20 Aug 2007 14:44:36 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from webmail16.mail.yandex.net (webmail16.mail.yandex.net [213.180.200.38]) by mx1.freebsd.org (Postfix) with ESMTP id 40D5613C480; Mon, 20 Aug 2007 14:44:36 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from YAMAIL (webmail16) by mail.yandex.ru id S8675764AbXHTOod for (+ 1 other); Mon, 20 Aug 2007 18:44:33 +0400 X-Yandex-Spam: 1 Received: from [77.72.136.71] ([77.72.136.71]) by mail.yandex.ru with HTTP; Mon, 20 Aug 2007 18:44:33 +0400 From: "Andrey V. Elsukov" To: M.S.Powell@salford.ac.uk In-Reply-To: 1550000000201688019 References: <20070818163810.I75076@rust.salford.ac.uk> <20070820112023.93648.qmail@rust.salford.ac.uk> <20070820124808.GM72415@cicely12.cicely.de> 1550000000201688019 MIME-Version: 1.0 Message-Id: <87531187621073@webmail16.yandex.ru> Date: Mon, 20 Aug 2007 18:44:33 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain Cc: freebsd-current@freebsd.org, ticso@cicely.de, sos@freebsd.org Subject: Re: PATA-SATA convertor drive inaccessibility (was 7.0-CURRENT MCP55 PATA to SATA convertor problems on Asus M2N32 WS Pro) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 14:44:36 -0000 > On Mon, 20 Aug 2007, Bernd Walter wrote: > With 7.0 I have found that with just a proper SATA drive connected or > even no SATA drives at all connected, after 7.0 has run the BIOS cannot > then detect any drives at restart. It just hangs. Something 7.0 is doing > is screwing up this controller. On my motherboard BIOS revision is 0403. I have two SATA300 drives (WD1200JS) connected to the MCP55 in the mirror (NVIDIA MediaShield RAID1). All works fine. -- WBR, Andrey V. Elsukov From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 15:18:13 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9304116A417 for ; Mon, 20 Aug 2007 15:18:13 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.freebsd.org (Postfix) with ESMTP id 4E50013C45E for ; Mon, 20 Aug 2007 15:18:13 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (cpe-71-72-80-132.columbus.res.rr.com [71.72.80.132]) (authenticated bits=0) by mail.united-ware.com (8.13.8/8.13.8) with ESMTP id l7KFuE4d081152 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Aug 2007 11:56:21 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: David Malone Date: Mon, 20 Aug 2007 11:21:28 -0400 User-Agent: KMail/1.9.6 References: <200708191147.10340.amistry@am-productions.biz> <200708191751.23094.amistry@am-productions.biz> <20070820084759.GA65560@walton.maths.tcd.ie> In-Reply-To: <20070820084759.GA65560@walton.maths.tcd.ie> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1889172.9WWZj0gFI5"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200708201121.37098.mistry.7@osu.edu> X-Virus-Scanned: ClamAV 0.90.3/4005/Sun Aug 19 18:33:30 2007 on mail.united-ware.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: Can't create TCP connections to certain IP addresses X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 15:18:13 -0000 --nextPart1889172.9WWZj0gFI5 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 20 August 2007, David Malone wrote: > On Sun, Aug 19, 2007 at 05:51:14PM -0400, Anish Mistry wrote: > > I'm not sure how to do that with the version of m0nowall that the > > router is running. But I can exhibit this behavior on the local > > LAN without going through the router. > > In that case, run a tcpdump on both ends and see if the SYN packet > is arriving at the far end. You might also want to try using > "tcpdump -s0 -v" to check the checksums on the packets (though they > can't always be trusted on the packet's sender if the network card > supports checksum offloading). > > David. There doesn't seem to be checksum offloading on the sender ath0 sender: tcpdump -s0 -v=20 http://am-productions.biz/debug/littleguy.tcpdump.txt =46ar end: tcpdump -s0 -v host 192.168.1.188 http://am-productions.biz/debug/bigguy.tcpdump.txt =2D-=20 Anish Mistry --nextPart1889172.9WWZj0gFI5 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBGybGBxqA5ziudZT0RAhEUAJ9WbjV7dIVjvxp0/2Cf44QOf/unhgCfbvSd LDxXrdgjc5tjYiXMF2+GK/8= =NomB -----END PGP SIGNATURE----- --nextPart1889172.9WWZj0gFI5-- From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 15:42:56 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80ACD16A41A for ; Mon, 20 Aug 2007 15:42:56 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.188]) by mx1.freebsd.org (Postfix) with ESMTP id 0B64013C46B for ; Mon, 20 Aug 2007 15:42:55 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: by fk-out-0910.google.com with SMTP id b27so1441464fka for ; Mon, 20 Aug 2007 08:42:54 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=uYh2aNzR1Jy3OimaH1/UNqPZqFdk564ZV4WVky1gB4hr9OmAtdl2KL/FPJ9VrT6XkwOHoqlyqL0JINceFKw34KSokKv5IP1JPZCQPdNZMT4i0OS1GWU5wiDWXN1FcPQteLZVdIl8I2D2Q9Qs8lvD0VtLWplUw8TLcUViQTn6GNw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=pKe4RFIT/nbnAswaQCHZrZlKxJoU2/hv9/E9QU/9d+NWSJlolQeNgm/02Ipm9HA+1JVstMGAI88fc9PTXZtZj4i0O/wURnVfwFiTV3rvnK/p90HCG0h9PmCK9KpJjHZWQkWWQeFpuyFkZja/AUVEZF64E9pJHsDvwz/jJ0tC37Y= Received: by 10.82.127.14 with SMTP id z14mr7944855buc.1187622918394; Mon, 20 Aug 2007 08:15:18 -0700 (PDT) Received: from roadrunner.spoerlein.net ( [85.180.149.79]) by mx.google.com with ESMTPS id j2sm19261674mue.2007.08.20.08.15.17 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 20 Aug 2007 08:15:18 -0700 (PDT) Received: from roadrunner.spoerlein.net (localhost [127.0.0.1]) by roadrunner.spoerlein.net (8.14.1/8.14.1) with ESMTP id l7KE7SoC040910; Mon, 20 Aug 2007 16:07:28 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Received: (from q@localhost) by roadrunner.spoerlein.net (8.14.1/8.14.1/Submit) id l7KE7RCW040904; Mon, 20 Aug 2007 16:07:27 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Date: Mon, 20 Aug 2007 16:07:27 +0200 From: Ulrich Spoerlein To: Oliver Fromme Message-ID: <20070820140726.GC1455@roadrunner.spoerlein.net> Mail-Followup-To: Oliver Fromme , freebsd-current@FreeBSD.ORG References: <20070815013342.GA25882@rot26.obsecurity.org> <200708161122.l7GBMd2f097695@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200708161122.l7GBMd2f097695@lurza.secnetix.de> User-Agent: Mutt/1.5.15 (2007-04-06) Cc: freebsd-current@FreeBSD.ORG Subject: Re: IP over HTTP? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 15:42:56 -0000 On Thu, 16.08.2007 at 13:22:39 +0200, Oliver Fromme wrote: > Note, however, that some HTTP proxies are configured to > disallow connections to arbitrary ports, for security > reasons. If that's the case for you, run you sshd server > on port 443 wich should always be allowed by proxies > (only possible if you don't already run a HTTPS server > on port 443, of course). If your company has a limited set of external IPs it's probably better to redirect port 443 than to abandon HTTPS (whatever happened to HTTP + STARTTLS, btw?) pf.conf: rdr on $ext_if proto tcp from $company to any port 443 -> ($ext_if) port 22 Cheers, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt. From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 15:48:10 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1275D16A474 for ; Mon, 20 Aug 2007 15:48:10 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.freebsd.org (Postfix) with ESMTP id 6A55A13C457 for ; Mon, 20 Aug 2007 15:48:09 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so692841nfb for ; Mon, 20 Aug 2007 08:48:07 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:reply-to:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:message-id; b=iiDxoM3Xjn6gYFl30ch3ABK7FMcU+W5SiJANrcFCVVbszBFAWjsrYj7jmRclX5OXayXev04RfvMLcRXyii1UmxUFrSxPpYf8Ff9TVKk6fRdnwGoayXJv9OlAQwpnvVhRftKav1Od6Uz2U9B8DubrIMDki6MYASjCV+A2Qqr5tbQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:reply-to:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:message-id; b=VueZA/yl9FwoI2hzqJ/TIAi44hT48UvOrvQInZ7g0y0TRPN7psDFCaXl3mNc0gsNJLODG9uJj3nLFN1TAhwsKMC0bSqidplu8vyeRcZuQx3gdwNuLhXwX+yQlkvxxbqROKGAgVJZOasTyKFp7fCsxgIJ3LMXroanf0QzM6RSfaA= Received: by 10.78.186.9 with SMTP id j9mr2059321huf.1187624887139; Mon, 20 Aug 2007 08:48:07 -0700 (PDT) Received: from 77-109-34-34.dynamic.peoplenet.ua ( [77.109.34.34]) by mx.google.com with ESMTPS id 37sm2524240hub.2007.08.20.08.48.03 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 20 Aug 2007 08:48:06 -0700 (PDT) From: Nikolay Pavlov To: freebsd-current@freebsd.org Date: Mon, 20 Aug 2007 18:48:17 +0300 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1202593.QvTtQ08CXd"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200708201848.22157.qpadla@gmail.com> Subject: Panic on todays current (panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/kern/vfs_mount.c:1046) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: qpadla@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 15:48:10 -0000 --nextPart1202593.QvTtQ08CXd Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello. I've got this while booting: Starting file system checks: /dev/ad0s4a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s4a: clean, 6113 free (241 frags, 734 blocks, 0.2% fragmentation) /dev/ad0s4f: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s4f: clean, 67511 free (2623 frags, 8111 blocks, 0.4%=20 fragmentation) /dev/ad0s4e.journal: FILE SYSTEM CLEAN; SKIPPING CHECKS Setting hostuuid: 44454C4C-4400-1039-8030-B6C04F4A324A. Setting hostid: 0x7817d87e. Mounting local file systems: panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/kern/vfs_mount.c:1046 cpuid =3D 0 KDB: enter: panic exclusive sleep mutex Giant r =3D 0 (0xc0ba7350) locked=20 @ /usr/src/sys/kern/kern_module.c:117 panic: from debugger cpuid =3D 0 Uptime: 6s Physical memory: 1003 MB Dumping 47 MB: 32 16 #0 doadump () at pcpu.h:195 195 __asm __volatile("movl %%fs:0,%0" : "=3Dr" (td)); (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc074c19e in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:4= 09 #2 0xc074c45b in panic (fmt=3DVariable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:563 #3 0xc048c6d7 in db_panic (addr=3DCould not find the frame base=20 for "db_panic". ) at /usr/src/sys/ddb/db_command.c:433 #4 0xc048d0c5 in db_command_loop () at /usr/src/sys/ddb/db_command.c:401 #5 0xc048e835 in db_trap (type=3D3, code=3D0)=20 at /usr/src/sys/ddb/db_main.c:222 #6 0xc07730c6 in kdb_trap (type=3D3, code=3D0, tf=3D0xe46959f0)=20 at /usr/src/sys/kern/subr_kdb.c:502 #7 0xc09fd25b in trap (frame=3D0xe46959f0)=20 at /usr/src/sys/i386/i386/trap.c:621 #8 0xc09e2c8b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #9 0xc0773242 in kdb_enter (msg=3D0xc0a93513 "panic") at cpufunc.h:60 #10 0xc074c444 in panic (fmt=3D0xc0a92475 "mtx_lock() of spin mutex %s @ %s: %d") at /usr/src/sys/kern/kern_shutdown.c:547 #11 0xc0740d3a in _mtx_lock_flags (m=3D0xc42b0000, opts=3D0,=20 file=3D0xc0a9e111 "/usr/src/sys/kern/vfs_mount.c", line=3D1046)=20 at /usr/src/sys/kern/kern_mutex.c:180 #12 0xc07c154b in vfs_donmount (td=3D0xc429f800, fsflags=3D0,=20 fsoptions=3D0xc431ce00) at /usr/src/sys/kern/vfs_mount.c:1046 #13 0xc07c25e3 in nmount (td=3D0xc429f800, uap=3D0xe4695cfc)=20 at /usr/src/sys/kern/vfs_mount.c:413 #14 0xc09fca13 in syscall (frame=3D0xe4695d38)=20 at /usr/src/sys/i386/i386/trap.c:1008 #15 0xc09e2cf0 in Xint0x80_syscall ()=20 at /usr/src/sys/i386/i386/exception.s:196 #16 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) =2D-=20 * Best regards, Nikolay Pavlov * --nextPart1202593.QvTtQ08CXd Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBGybfG/2R6KvEYGaIRAj1kAJ4rneqOenx5ZDfZpscZqxyzt4oq+QCfQMRC HNKRtXybgrz9IOn9QCGleg4= =WnMt -----END PGP SIGNATURE----- --nextPart1202593.QvTtQ08CXd-- From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 16:15:13 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 498F916A417 for ; Mon, 20 Aug 2007 16:15:13 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id 6C05E13C46B for ; Mon, 20 Aug 2007 16:15:10 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (localhost [127.0.0.1]) by blah.sun-fish.com (Postfix) with ESMTP id F3DD61B10EE7 for ; Mon, 20 Aug 2007 17:56:12 +0200 (CEST) Received: from hater.cmotd.com (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id F03031B10EE2 for ; Mon, 20 Aug 2007 17:56:12 +0200 (CEST) Message-ID: <46C9B99C.1060403@moneybookers.com> Date: Mon, 20 Aug 2007 18:56:12 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.4pre (X11/20070711) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP on BLAH Subject: kernel panic with memory disks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 16:15:13 -0000 Hello, I do not know if this is know behavior, and I know that 6.2 panic if the memory disk got full, but on 7-current the panic is before the disk got full. Here is what I do: mdconfig -a -t malloc -s 800m newfs /dev/md0 mount /dev/md0 /mnt cp 600mb.file /mnt and here is the output: g_vfs_done():md0[WRITE(offset=76087296, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=76218368, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=76349440, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=76480512, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=76611584, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=76742656, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=76873728, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77004800, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77135872, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77266944, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77398016, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77529088, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77660160, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77791232, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77922304, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78053376, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78184448, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78315520, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78446592, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78577664, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78708736, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78839808, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78970880, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79101952, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79233024, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79364096, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79495168, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79626240, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79757312, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79888384, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80019456, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80150528, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80281600, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80412672, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80543744, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80674816, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80805888, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80936960, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81068032, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81199104, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81330176, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81461248, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81592320, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81723392, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81854464, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81985536, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82116608, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82247680, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82378752, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82509824, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82640896, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82771968, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82903040, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=83034112, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=83165184, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=83296256, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=83427328, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=83558400, length=131072)]error = 28 g_vfs_done():md0[WRITE(poafnicf: kmem_maslleoct(16=3884)3: kmem_6m8ap 9t4o7o 2sm,all : 3354l74e6n88 tgottalh all=oc1ated3 21puid 0= 73 )]error = 28 gU_vfs_done():md0[WRITE(offset=83820544, length=131072)]error = 28 ptime: 5m47s Physical memory: 3831 MB Dumping 521 MB: 506 490 474 458g_vfs_done():md0[WRITE(offset=76087296, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=76218368, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=76349440, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=76480512, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=76611584, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=76742656, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=76873728, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77004800, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77135872, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77266944, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77398016, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77529088, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77660160, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77791232, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77922304, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78053376, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78184448, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78315520, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78446592, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78577664, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=192708608, length=32768)]error = 28 g_vfs_done():md0[WRITE(offset=192741376, length=16384)]error = 28 g_vfs_done():md0[WRITE(offset=385400832, length=16384)]error = 28 g_vfs_done():md0[WRITE(offset=385417216, length=16384)]error = 28 g_vfs_done():md0[WRITE(offset=385433600, length=16384)]error = 28 g_vfs_done():md0[WRITE(offset=578093056, length=16384)]error = 28 g_vfs_done():md0[WRITE(offset=578109440, length=16384)]error = 28 g_vfs_done():md0[WRITE(offset=78708736, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78839808, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78970880, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79101952, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79233024, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79364096, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79495168, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79626240, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79757312, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79888384, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80019456, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80150528, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80281600, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80412672, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80543744, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80674816, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80805888, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80936960, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81068032, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81199104, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81330176, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81461248, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81592320, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81723392, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81854464, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81985536, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82116608, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82247680, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82378752, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82509824, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82640896, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82771968, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82903040, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=83034112, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=83165184, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=83296256, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=83427328, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=83558400, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=83689472, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=83820544, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=76087296, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=76218368, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=76349440, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=76480512, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=76611584, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=76742656, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=76873728, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77004800, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77135872, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77266944, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77398016, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77529088, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77660160, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77791232, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=77922304, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78053376, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78184448, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78315520, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78446592, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78577664, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=192708608, length=32768)]error = 28 g_vfs_done():md0[WRITE(offset=192741376, length=16384)]error = 28 g_vfs_done():md0[WRITE(offset=385400832, length=16384)]error = 28 g_vfs_done():md0[WRITE(offset=385417216, length=16384)]error = 28 g_vfs_done():md0[WRITE(offset=385433600, length=16384)]error = 28 g_vfs_done():md0[WRITE(offset=578093056, length=16384)]error = 28 g_vfs_done():md0[WRITE(offset=578109440, length=16384)]error = 28 g_vfs_done():md0[WRITE(offset=78708736, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78839808, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=78970880, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79101952, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79233024, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79364096, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79495168, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79626240, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79757312, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=79888384, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80019456, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80150528, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80281600, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80412672, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80543744, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80674816, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80805888, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=80936960, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81068032, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81199104, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81330176, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81461248, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81592320, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81723392, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81854464, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=81985536, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82116608, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82247680, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82378752, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82509824, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82640896, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82771968, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=82903040, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=83034112, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=83165184, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=83296256, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=83427328, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=83558400, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=83689472, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=83820544, length=131072)]error = 28 Error dumping block 0x0 ** DUMP FAILED (ERROR 5) ** aac0: shutting down controller...done Automatic reboot in 15 seconds - press a key on the console to abort -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 16:46:54 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32E7A16A420 for ; Mon, 20 Aug 2007 16:46:54 +0000 (UTC) (envelope-from bsd-current@epcdirect.co.uk) Received: from gunfright.epcdirect.co.uk (gunfright.epcdirect.co.uk [195.10.242.32]) by mx1.freebsd.org (Postfix) with ESMTP id D2CF613C45A for ; Mon, 20 Aug 2007 16:46:53 +0000 (UTC) (envelope-from bsd-current@epcdirect.co.uk) Received: from localhost (localhost.epcdirect.co.uk [127.0.0.1]) by gunfright.epcdirect.co.uk (Postfix) with ESMTP id 18C636190 for ; Mon, 20 Aug 2007 17:46:53 +0100 (BST) X-Virus-Scanned: by GunFright.EPCDirect.co.uk Received: from gunfright.epcdirect.co.uk ([127.0.0.1]) by localhost (gunfright.epcdirect.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GziQXeD+pWfs for ; Mon, 20 Aug 2007 17:46:52 +0100 (BST) Received: by gunfright.epcdirect.co.uk (Postfix, from userid 125) id CA2C2610D; Mon, 20 Aug 2007 17:45:55 +0100 (BST) Received: from localhost (localhost.epcdirect.co.uk [127.0.0.1]) by gunfright.epcdirect.co.uk (Postfix) with ESMTP id 234DC6191 for ; Mon, 20 Aug 2007 17:43:55 +0100 (BST) X-Virus-Scanned: by GunFright.EPCDirect.co.uk Received: from gunfright.epcdirect.co.uk ([127.0.0.1]) by localhost (gunfright.epcdirect.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mjgFEkOihLfo for ; Mon, 20 Aug 2007 17:43:54 +0100 (BST) Received: by gunfright.epcdirect.co.uk (Postfix, from userid 125) id E4E1D6190; Mon, 20 Aug 2007 17:42:57 +0100 (BST) Received: from localhost (localhost.epcdirect.co.uk [127.0.0.1]) by gunfright.epcdirect.co.uk (Postfix) with ESMTP id 551AA60F8 for ; Mon, 20 Aug 2007 17:41:55 +0100 (BST) X-Virus-Scanned: by GunFright.EPCDirect.co.uk Received: from gunfright.epcdirect.co.uk ([127.0.0.1]) by localhost (gunfright.epcdirect.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X3j1RuiAhZM5 for ; Mon, 20 Aug 2007 17:41:54 +0100 (BST) Received: by gunfright.epcdirect.co.uk (Postfix, from userid 125) id 4963160F1; Mon, 20 Aug 2007 17:41:49 +0100 (BST) Received: from localhost (localhost.epcdirect.co.uk [127.0.0.1]) by gunfright.epcdirect.co.uk (Postfix) with ESMTP id 3BEAD61C7 for ; Mon, 20 Aug 2007 17:35:47 +0100 (BST) X-Virus-Scanned: by GunFright.EPCDirect.co.uk Received: from gunfright.epcdirect.co.uk ([127.0.0.1]) by localhost (gunfright.epcdirect.co.uk [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id PnJpc8iTqI6S for ; Mon, 20 Aug 2007 17:35:47 +0100 (BST) Received: from lfarr (l-farr.int.epcdirect.co.uk [192.168.6.200]) by gunfright.epcdirect.co.uk (Postfix) with ESMTP id 0775E61AC for ; Mon, 20 Aug 2007 17:35:47 +0100 (BST) From: "Lawrence Farr" To: References: <46C9B99C.1060403@moneybookers.com> In-Reply-To: <46C9B99C.1060403@moneybookers.com> Date: Mon, 20 Aug 2007 17:35:45 +0100 Message-ID: <012501c7e348$288c6af0$79a540d0$@co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcfjRWdgQLLL82wpRXW0XbhfpTnnKgAATWlQ Content-Language: en-gb Subject: Solid hang with bge interface X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 16:46:54 -0000 I have a Supermicro H8DAR-T based server, that was happily running 6-stable from last year sometime. I swapped it out and have been trying to get -CURRENT installed on it but it hangs solid as soon as you configure the bge0 interface. The bge1 interface will work occasionally tho. To try and rule out a hardware fault I booted an AMD64-6.0RC1 cd that I had, which had no problems at all with the interface: http://www.epcdirect.com/bootlog/6boot.txt But the current snapshot from June, and from todays source hangs solid as soon as you try to set up the bge0 interface. http://www.epcdirect.com/bootlog/currentboot.txt As you can see, it hangs solid at "Setting hostname". I've also removed the 3ware card "just in case" but it made no difference. Latest BIOS too. I found some references to a similar problem with bge recently too: http://lists.freebsd.org/pipermail/freebsd-current/2007-August/075998.html Anyone else seeing this? From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 16:57:01 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 514C016A41A for ; Mon, 20 Aug 2007 16:57:01 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.freebsd.org (Postfix) with ESMTP id CF85213C48D for ; Mon, 20 Aug 2007 16:57:00 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so711504nfb for ; Mon, 20 Aug 2007 09:56:59 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; b=urtn8SpW+6oraxnCzWbpJu2kGtbsON133j31GK4B3TESE6nu6WNNuDicdrvgx82Miha1hS4SM6KZ7ptflX0D2c+0qIBBQzitpemZYwzMvtOmy0kNCN0xUGoLpV/wogHThXSgGnlvkoid+4QtquOKeECOf6PSx81ccCJOgxQHcns= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; b=GHLh2KXnfzorCsjrBK7ey6rXcrhMIDQ3CkwigTVBumlpx5KVQzjguCYfXX0dmkfiiJpxCFrPOEZ6gaDyeO4vN9ClzpTF7/gPCaGNWzbqJkPCPNeAsUONCZ6UVkDEtqfd3j0LnX/xrYrGCiMxqZdZ+Zkd7MULpruacJ04YzCPAz4= Received: by 10.78.145.5 with SMTP id s5mr2107251hud.1187629019645; Mon, 20 Aug 2007 09:56:59 -0700 (PDT) Received: from 77-109-34-147.dynamic.peoplenet.ua ( [77.109.34.147]) by mx.google.com with ESMTPS id 8sm1677875hug.2007.08.20.09.56.56 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 20 Aug 2007 09:56:58 -0700 (PDT) From: Nikolay Pavlov To: Kostik Belousov Date: Mon, 20 Aug 2007 19:56:35 +0300 User-Agent: KMail/1.9.7 References: <200708201848.22157.qpadla@gmail.com> <20070820162311.GT2738@deviant.kiev.zoral.com.ua> In-Reply-To: <20070820162311.GT2738@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3627466.ZRgBLM02zv"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200708201956.40383.qpadla@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Panic on todays current (panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/kern/vfs_mount.c:1046) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: qpadla@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 16:57:01 -0000 --nextPart3627466.ZRgBLM02zv Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 20 August 2007 19:23:11 Kostik Belousov wrote: > The line where the reported panic happens is located at the point where > several successfull locks of the mount structure interlock alread happen > (see, for instance, line 983). In between, there is a call to > VFS_MOUNT() method of the fs. > > It would be interesting to look at the type of the filesystem being > mounted. This line from the fstab is a trigger for this panic: tmpfs /tmp tmpfs rw,mode=3D777 0 0 > > Just a guess: > Could it be that mounted filesystem comes from module, that uses > incompatible binary interface (for instance, built with different kernel > options or for different kernel version) ? No. The kernel is GENERIC. The command was a plain "make buildkernel -j3"=20 and i don't have any special build arguments nither in src.conf nor=20 make.conf.=20 =2D-=20 * Best regards, Nikolay Pavlov * --nextPart3627466.ZRgBLM02zv Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBGycfI/2R6KvEYGaIRAp4UAKCNUNuZuzxpn7YSBoyhDbrMisyyiQCeJ4IZ 5EDmoH5r2Zmlt6xFq1Un93g= =eCzM -----END PGP SIGNATURE----- --nextPart3627466.ZRgBLM02zv-- From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 17:49:03 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 000A116A41A for ; Mon, 20 Aug 2007 17:49:02 +0000 (UTC) (envelope-from illoai@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.189]) by mx1.freebsd.org (Postfix) with ESMTP id 7F32713C428 for ; Mon, 20 Aug 2007 17:49:02 +0000 (UTC) (envelope-from illoai@gmail.com) Received: by mu-out-0910.google.com with SMTP id w9so1483061mue for ; Mon, 20 Aug 2007 10:49:01 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=iL29InSqsGxYSSf0L2OrgZ7wFxse7yIeMoR5Ejs5GI0GDnNL8QQu+VWIfbOodqYCWMLMJqBomKbEqqHbkrrcKrMxxhBebT/29wOLml13ijiKrEzh1D5CuXYCbwEzcYRsP5brWghw59ZFdw9c45JbzavG/mfNTPjKIUrYp7IM+1c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pHBo5/oYE9RloYwoxfegaWyn7eGc79fg1X9wpgMYkRznB2mhnsanCQAH7GyQ7e++4VzS7BEYEF5ak9I2yoq2Hmqo+IalO0hFE0TghzBF0Hp56TIjo2oPqmLJSUGcCHCDJKnm4TnGUTQGAXcikuz8zAzVSHtUwaz30q/pSHnq7HE= Received: by 10.82.174.20 with SMTP id w20mr8251312bue.1187632140724; Mon, 20 Aug 2007 10:49:00 -0700 (PDT) Received: by 10.82.185.5 with HTTP; Mon, 20 Aug 2007 10:49:00 -0700 (PDT) Message-ID: Date: Mon, 20 Aug 2007 12:49:00 -0500 From: "illoai@gmail.com" To: "Andrew Reilly" In-Reply-To: <20070819060139.GA40369@duncan.reilly.home> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070815122747.GA62123@duncan.reilly.home> <18117.37649.6266.369458@jerusalem.litteratus.org> <18119.3872.547510.973785@roam.psg.com> <20070819060139.GA40369@duncan.reilly.home> Cc: Randy Bush , Robert Huff , freebsd-current@freebsd.org Subject: Re: Does 7-CURRENT (aka cvsup tag=.) build under 6-STABLE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 17:49:03 -0000 On 19/08/07, Andrew Reilly wrote: > On Sat, Aug 18, 2007 at 05:24:16AM -1000, Randy Bush wrote: > > i just upgraded two RELENG_6 boxes to 7-CURRENT last eve. no prob. > > i was silly and broke the union rules by following the instructions > > at the bottom of /usr/src/UPDATING. it is extremely rare that i > > have had problems on this path, 4 to 5, 5 to 6, 6 to 7. have not > > tried 7 to 8 yet. > > Thanks for the "it works" reports, folks. Re-supped and > currently re-building, and it seems to be going OK now. Yes, > I've upgraded in-place on most previous occasions, too. (Only > exception was to 6, from memory, because a dump/wipe/install/restore > seemed to be the easiest way to get UFS2 onto the disks...) > > Oh: there's an 8? I didn't think that 7 had been > tagged/branched, yet. If the "." tag gives you 7, I seriously doubt there's an 8, although you might get into some double secret order of banana scouts if you can figure out the right tag. Call me from the Bildeberg, if you [cflmrt]ake it. -- -- From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 17:54:54 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4FFE16A420 for ; Mon, 20 Aug 2007 17:54:54 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 75FE713C4A3 for ; Mon, 20 Aug 2007 17:54:54 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id CF6DB46C0A; Mon, 20 Aug 2007 13:54:53 -0400 (EDT) Date: Mon, 20 Aug 2007 18:54:53 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Stefan Lambrev In-Reply-To: <46C9B99C.1060403@moneybookers.com> Message-ID: <20070820185402.A97677@fledge.watson.org> References: <46C9B99C.1060403@moneybookers.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: kernel panic with memory disks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 17:54:54 -0000 On Mon, 20 Aug 2007, Stefan Lambrev wrote: > I do not know if this is know behavior, and I know that 6.2 panic if the > memory disk got full, but on 7-current the panic is before the disk got > full. > > Here is what I do: > > mdconfig -a -t malloc -s 800m newfs /dev/md0 mount /dev/md0 /mnt cp > 600mb.file /mnt You probably mean to be using "-t swap" -- 800mb of kernel address space and memory is quite a bit. Error 28 is ENOMEM, btw, which seems consistent with that concern. Try using "-t swap" and see if things go better. Robert N M Watson Computer Laboratory University of Cambridge > > and here is the output: > > g_vfs_done():md0[WRITE(offset=76087296, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=76218368, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=76349440, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=76480512, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=76611584, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=76742656, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=76873728, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77004800, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77135872, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77266944, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77398016, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77529088, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77660160, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77791232, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77922304, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78053376, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78184448, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78315520, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78446592, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78577664, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78708736, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78839808, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78970880, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79101952, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79233024, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79364096, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79495168, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79626240, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79757312, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79888384, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80019456, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80150528, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80281600, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80412672, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80543744, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80674816, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80805888, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80936960, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81068032, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81199104, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81330176, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81461248, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81592320, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81723392, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81854464, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81985536, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82116608, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82247680, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82378752, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82509824, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82640896, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82771968, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82903040, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=83034112, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=83165184, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=83296256, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=83427328, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=83558400, length=131072)]error = 28 > g_vfs_done():md0[WRITE(poafnicf: kmem_maslleoct(16=3884)3: kmem_6m8ap 9t4o7o > 2sm,all : 3354l74e6n88 tgottalh all=oc1ated3 > 21puid 0= 73 > )]error = 28 > gU_vfs_done():md0[WRITE(offset=83820544, length=131072)]error = 28 > ptime: 5m47s > Physical memory: 3831 MB > Dumping 521 MB: 506 490 474 458g_vfs_done():md0[WRITE(offset=76087296, > length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=76218368, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=76349440, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=76480512, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=76611584, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=76742656, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=76873728, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77004800, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77135872, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77266944, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77398016, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77529088, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77660160, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77791232, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77922304, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78053376, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78184448, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78315520, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78446592, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78577664, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=192708608, length=32768)]error = 28 > g_vfs_done():md0[WRITE(offset=192741376, length=16384)]error = 28 > g_vfs_done():md0[WRITE(offset=385400832, length=16384)]error = 28 > g_vfs_done():md0[WRITE(offset=385417216, length=16384)]error = 28 > g_vfs_done():md0[WRITE(offset=385433600, length=16384)]error = 28 > g_vfs_done():md0[WRITE(offset=578093056, length=16384)]error = 28 > g_vfs_done():md0[WRITE(offset=578109440, length=16384)]error = 28 > g_vfs_done():md0[WRITE(offset=78708736, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78839808, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78970880, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79101952, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79233024, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79364096, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79495168, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79626240, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79757312, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79888384, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80019456, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80150528, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80281600, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80412672, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80543744, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80674816, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80805888, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80936960, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81068032, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81199104, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81330176, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81461248, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81592320, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81723392, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81854464, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81985536, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82116608, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82247680, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82378752, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82509824, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82640896, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82771968, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82903040, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=83034112, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=83165184, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=83296256, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=83427328, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=83558400, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=83689472, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=83820544, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=76087296, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=76218368, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=76349440, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=76480512, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=76611584, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=76742656, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=76873728, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77004800, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77135872, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77266944, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77398016, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77529088, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77660160, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77791232, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=77922304, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78053376, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78184448, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78315520, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78446592, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78577664, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=192708608, length=32768)]error = 28 > g_vfs_done():md0[WRITE(offset=192741376, length=16384)]error = 28 > g_vfs_done():md0[WRITE(offset=385400832, length=16384)]error = 28 > g_vfs_done():md0[WRITE(offset=385417216, length=16384)]error = 28 > g_vfs_done():md0[WRITE(offset=385433600, length=16384)]error = 28 > g_vfs_done():md0[WRITE(offset=578093056, length=16384)]error = 28 > g_vfs_done():md0[WRITE(offset=578109440, length=16384)]error = 28 > g_vfs_done():md0[WRITE(offset=78708736, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78839808, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=78970880, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79101952, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79233024, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79364096, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79495168, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79626240, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79757312, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=79888384, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80019456, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80150528, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80281600, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80412672, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80543744, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80674816, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80805888, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=80936960, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81068032, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81199104, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81330176, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81461248, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81592320, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81723392, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81854464, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=81985536, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82116608, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82247680, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82378752, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82509824, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82640896, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82771968, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=82903040, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=83034112, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=83165184, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=83296256, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=83427328, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=83558400, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=83689472, length=131072)]error = 28 > g_vfs_done():md0[WRITE(offset=83820544, length=131072)]error = 28 > Error dumping block 0x0 > > ** DUMP FAILED (ERROR 5) ** > aac0: shutting down controller...done > Automatic reboot in 15 seconds - press a key on the console to abort > > -- > > Best Wishes, > Stefan Lambrev > ICQ# 24134177 > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 18:17:32 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6482816A417 for ; Mon, 20 Aug 2007 18:17:32 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: from akis.salford.ac.uk (akis.salford.ac.uk [146.87.0.14]) by mx1.freebsd.org (Postfix) with SMTP id B7BF613C459 for ; Mon, 20 Aug 2007 18:17:28 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 25987 invoked by uid 98); 20 Aug 2007 19:17:23 +0100 Received: from 146.87.255.121 by akis.salford.ac.uk (envelope-from , uid 401) with qmail-scanner-2.01 (clamdscan: 0.90/3843. spamassassin: 3.1.8. Clear:RC:1(146.87.255.121):. Processed in 0.049278 secs); 20 Aug 2007 18:17:23 -0000 Received: from rust.salford.ac.uk (HELO rust.salford.ac.uk) (146.87.255.121) by akis.salford.ac.uk (qpsmtpd/0.3x.614) with SMTP; Mon, 20 Aug 2007 19:17:23 +0100 Received: (qmail 96701 invoked by uid 1002); 20 Aug 2007 18:17:21 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 20 Aug 2007 18:17:21 -0000 Date: Mon, 20 Aug 2007 19:17:21 +0100 (BST) From: "Mark Powell" To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= In-Reply-To: <46C99B46.3000605@deepcore.dk> Message-ID: <20070820191558.I96699@rust.salford.ac.uk> References: <20070818163810.I75076@rust.salford.ac.uk> <20070820112023.93648.qmail@rust.salford.ac.uk> <20070820124808.GM72415@cicely12.cicely.de> <20070820135021.W93439@rust.salford.ac.uk> <20070820142224.D94437@rust.salford.ac.uk> <46C99B46.3000605@deepcore.dk> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-134151921-1187633841=:96699" Cc: freebsd-current@FreeBSD.ORG, ticso@cicely.de, sos@FreeBSD.ORG Subject: Re: MCP55 SATA problems (was Re: PATA-SATA convertor drive inaccessibility) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 18:17:32 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-134151921-1187633841=:96699 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Mon, 20 Aug 2007, S=F8ren Schmidt wrote: Soren, Thanks for the reply. > Hmm, it does work fine here even with PATA<>SATA dongels in use on a=20 > MCP55 system... > > I'll check the code for obvious faults once again, but since nVidia=20 > doesn't hand out docs it might be more sinister than that.... But doesn't the fact that everything works fine on the same hardware on=20 6.2, seem to suggest that something got changed in 7 that has broken this? Many thanks. --=20 Mark Powell - UNIX System Administrator - The University of Salford Information Services Division, Clifford Whitworth Building, Salford University, Manchester, M5 4WT, UK. Tel: +44 161 295 4837 Fax: +44 161 295 5888 www.pgp.com for PGP key --0-134151921-1187633841=:96699-- From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 18:18:28 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D46BF16A46E for ; Mon, 20 Aug 2007 18:18:28 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [IPv6:2001:770:10:300::86e2:510b]) by mx1.freebsd.org (Postfix) with SMTP id A49C413C49D for ; Mon, 20 Aug 2007 18:18:27 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 20 Aug 2007 19:18:25 +0100 (BST) Date: Mon, 20 Aug 2007 19:18:21 +0100 From: David Malone To: Anish Mistry Message-ID: <20070820181821.GA74449@walton.maths.tcd.ie> References: <200708191147.10340.amistry@am-productions.biz> <200708191751.23094.amistry@am-productions.biz> <20070820084759.GA65560@walton.maths.tcd.ie> <200708201121.37098.mistry.7@osu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200708201121.37098.mistry.7@osu.edu> User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: freebsd-current@freebsd.org Subject: Re: Can't create TCP connections to certain IP addresses X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 18:18:28 -0000 On Mon, Aug 20, 2007 at 11:21:28AM -0400, Anish Mistry wrote: > There doesn't seem to be checksum offloading on the sender ath0 > sender: tcpdump -s0 -v > http://am-productions.biz/debug/littleguy.tcpdump.txt > > Far end: tcpdump -s0 -v host 192.168.1.188 > http://am-productions.biz/debug/bigguy.tcpdump.txt It looks like you might be generating packets with bad checksums some times. There's an open PR about this, but it depends on what CFLAGS you used to compile your kernel. Could you check and see what flags you are using? David. From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 18:23:04 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CD0016A417 for ; Mon, 20 Aug 2007 18:23:04 +0000 (UTC) (envelope-from kjelderg@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.freebsd.org (Postfix) with ESMTP id C252013C480 for ; Mon, 20 Aug 2007 18:23:03 +0000 (UTC) (envelope-from kjelderg@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so732942nfb for ; Mon, 20 Aug 2007 11:23:02 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=RuHN0+Lj2z+sRYJ/5YkUEssyq0P70fpyKbU69+GbqXp/FeDKsjb/BTK+ZP983bCRgsj7p8rTJF2FyAwFT+GBGblgsJ+7r7OVyHW1CAJGcucl4uC0wl4NN+wsZG96QxFKKF6eflQ8NmA4eO0zddQfqVMZzt0ExGs2Ivqjz2Nh7IA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=MI65SsJzngWhL6wSFcaMBgfjzPPjfiQKnL2TZ78zSk79YXOVnRt26eKy8b51breJS1DY7pNcW0lp5QJDYP1fvTY74IALnRbA4y2ooz+mRNfWoK1J5HxqFRQX5jrJG7R3cdtYDT4utgYBYit5sratPXcESdJqAj0XPZ9RZ1jPrCg= Received: by 10.86.23.17 with SMTP id 17mr4705729fgw.1187632725785; Mon, 20 Aug 2007 10:58:45 -0700 (PDT) Received: by 10.86.31.6 with HTTP; Mon, 20 Aug 2007 10:58:45 -0700 (PDT) Message-ID: Date: Mon, 20 Aug 2007 12:58:45 -0500 From: "Eric Kjeldergaard" To: "Stefan Lambrev" In-Reply-To: <46C9B99C.1060403@moneybookers.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46C9B99C.1060403@moneybookers.com> Cc: freebsd-current@freebsd.org Subject: Re: kernel panic with memory disks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 18:23:04 -0000 On 20/08/07, Stefan Lambrev wrote: > Hello, > > I do not know if this is know behavior, and I know that 6.2 panic if the > memory disk got full, > but on 7-current the panic is before the disk got full. > > Here is what I do: > > mdconfig -a -t malloc -s 800m > newfs /dev/md0 > mount /dev/md0 /mnt > cp 600mb.file /mnt -t type Select the type of the memory disk. malloc Storage for this type of memory disk is allocated with malloc(9). This limits the size to the malloc bucket limit in the kernel. If the -o reserve option is not set, creating and filling a large malloc-backed memory disk is a very easy way to panic a system. -- mdconfig(8) -- If I write a sig emails are personalised people are happy From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 18:59:01 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7264C16A419 for ; Mon, 20 Aug 2007 18:59:01 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mx1.freebsd.org (Postfix) with ESMTP id EE97813C458 for ; Mon, 20 Aug 2007 18:59:00 +0000 (UTC) (envelope-from max@love2party.net) Received: from dslb-088-064-187-186.pools.arcor-ip.net [88.64.187.186] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu5) with ESMTP (Nemesis), id 0ML25U-1INCSZ3sMp-0007lZ; Mon, 20 Aug 2007 20:58:45 +0200 From: Max Laier Organization: FreeBSD To: freebsd-current@freebsd.org Date: Mon, 20 Aug 2007 20:58:23 +0200 User-Agent: KMail/1.9.7 References: <200708170939.l7H9diEk054469@lurza.secnetix.de> <20070819163934.V568@10.0.0.1> <20070820103424.GG1164@turion.vk2pj.dyndns.org> In-Reply-To: <20070820103424.GG1164@turion.vk2pj.dyndns.org> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2870256.GJF9jbluCR"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200708202058.39565.max@love2party.net> X-Provags-ID: V01U2FsdGVkX19cOq6FX6Su6MfQNIFoWhSQ0d9ypoidADUX6Cq eBWUZ4uqaCmeNv2GYe0FZz33EnQKYv6v6nCxF9rzl6k7vFr5nT AXzogWOPyv5i6jPnzZieCDZ+TJHs1MuIQxifYoIGmc= Cc: Peter Jeremy , Jeff Roberson Subject: Re: Why we don't use bzip2 in sysinstall/rescue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 18:59:01 -0000 --nextPart2870256.GJF9jbluCR Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 20 August 2007, Peter Jeremy wrote: > On 2007-Aug-19 16:46:10 -0700, Jeff Roberson =20 wrote: > >I tried this on my 1.8ghz pentium M laptop with 5.6MB of jpg data. > > > >I did: > > > >tar cvf foo.tar foo > >cat foo.tar >> /dev/null > >time bzip2/gzip foo.tar > > > >I removed and recreated the tar each time. The cat was to make sure > > it was in cache, although it certainly was from the creation step > > before. > > > >Anyway, the results are: > > > >bzip2 > >2.452u 0.026s 0:07.65 32.2% 92+3227k 5+43io 0pf+0w 1849c/6w > > > >gzip > >0.539u 0.020s 0:01.75 31.4% 109+3268k 2+44io 0pf+0w 493c/3w > > I don't believe this is a reasonable test because: > 1) You are measuring compression time, whilst it's decompression time > that is relevant to installation. > 2) jpeg images should not be compressible and are not representative > of the type of data in a FreeBSD release. > > I've tried what I believe is a more reasonable benchmark on an > Athlon XP-1800, running a recent 7-CURRENT using all the installation > images in 6.2-RELEASE-i386-disk1.iso. > > I concatenated all the 6.2-RELEASE/*/*.?? parts into */*.tgz files as > well as copying ports.tgz (a total of 31 files). I also decompressed > each file and recompressed it into a bzip2 file. The total sizes > were: > */*.tbz: 237717490 > */*.tgz: 281754511 > > Like you, I used "cat */*.t{g,b}z >/dev/null" to cache the files > and use systat to verify that they were cached. > > Timing the gzcat and bzcat runs gives: > gzcat -v */*.tgz > /dev/null 12.01s user 0.88s system 98% cpu 13.115=20 > total=20 > gzcat -v */*.tgz > /dev/null 11.95s user 0.95s system 98% cpu 13.124=20 > total=20 > gzcat -v */*.tgz > /dev/null 11.96s user 0.91s system 98% cpu 13.092=20 > total=20 > bzcat -v */*.tbz > /dev/null 153.29s user 3.43s system 98% cpu 2:39.03 > total=20 > bzcat -v */*.tbz > /dev/null 153.32s user 3.26s system 98% cpu 2:39.14 > total=20 > bzcat -v */*.tbz > /dev/null 153.16s user 3.48s system 98% cpu 2:39.02 > total=20 > > This is nearly 13:1 slower for bzcat, with a size reduction of about > 15%. > > As for the CPU vs I/O tradeoff, I believe that gzcat will be I/O bound > whilst bzcat will be CPU bound in most situations, though I haven't > actually verified this. With an amd64 world(236M) tar'ed together with -czf / -cyf respectively I=20 get the following input bandwidth numbers (gathered via dd=20 if=3Damd64.t{g,b}z of=3D/dev/stdio | {g,b}zcat > /dev/null): hw.model: Intel(R) Pentium(R) 4 CPU 2.00GHz: x bz + gz N Min Max Median Avg Stddev x 13 1411432 1554463 1544446 1521445.7 50394.705 + 13 13391136 13847045 13804007 13726781 138363.27 Difference at 95.0% confidence 1.22053e+07 +/- 84296.2 802.22% +/- 5.54053% (Student's t, pooled s =3D 104125) hw.model=3DAMD Opteron(tm) Processor 275: x fast.bz + fast.gz N Min Max Median Avg Stddev x 10 3429556 3889574 3449869 3525725.6 169675.46 + 10 41967910 46046387 45944662 45490300 1257435.8 Difference at 95.0% confidence 4.19646e+07 +/- 843005 1190.24% +/- 23.9101% (Student's t, pooled s =3D 897200) So it seems that bzip2 will indeed be bound to CPU - at least when=20 installing from CD. netinst over the internet is a different story,=20 though. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart2870256.GJF9jbluCR Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBGyeRfXyyEoT62BG0RAkwVAJ997GbvWwS9meNewwnpJsyAAmlrKQCfcip8 nw2QMwF3JYszR6oXcr4JvwM= =Pezz -----END PGP SIGNATURE----- --nextPart2870256.GJF9jbluCR-- From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 19:36:05 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 892F116A418; Mon, 20 Aug 2007 19:36:05 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 23AE613C458; Mon, 20 Aug 2007 19:36:05 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 0958C493C3; Mon, 20 Aug 2007 15:36:04 -0400 (EDT) Date: Mon, 20 Aug 2007 20:36:03 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jeff Roberson In-Reply-To: <20070819145532.O568@10.0.0.1> Message-ID: <20070820203420.R97677@fledge.watson.org> References: <20070819214953.I1099@fledge.watson.org> <20070819144903.U568@10.0.0.1> <20070819145532.O568@10.0.0.1> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: attilio@freebsd.org, dds@freebsd.org, current@freebsd.org Subject: Re: Crash in accounting code: encode_long(), due to bad rusage data? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 19:36:05 -0000 On Sun, 19 Aug 2007, Jeff Roberson wrote: >>> (kgdb) list >>> 386 tmp = ut; >>> 387 timevaladd(&tmp, &st); >>> 388 /* Convert tmp (i.e. u + s) into hz units to match ru_i*. >>> */ >>> 389 t = tmp.tv_sec * hz + tmp.tv_usec / tick; >>> 390 if (t) >>> 391 acct.ac_mem = encode_long((ru.ru_ixrss + >>> ru.ru_idrss + >>> 392 + ru.ru_isrss) / t); >>> 393 else >>> 394 acct.ac_mem = 0; >>> 395 >>> (kgdb) inspect ru >>> $2 = {ru_utime = {tv_sec = 0, tv_usec = 0}, ru_stime = {tv_sec = 0, >>> tv_usec = 0}, ru_maxrss = 509908, ru_ixrss = 26810576, >>> ru_idrss = -2016077424, ru_isrss = 1044992, ru_minflt = 372535, >>> ru_majflt = 42, ru_nswap = 0, ru_inblock = 58, ru_oublock = 278, >>> ru_msgsnd = 1907, ru_msgrcv = 4671, ru_nsignals = 32, ru_nvcsw = 19892, >>> ru_nivcsw = 4614} > > Can you tell me what's in t, tmp, hz and tick? For the benefit of those not present for my conversation with Jeff, here are the values: (kgdb) inspect t $1 = {tv_sec = 94826, tv_usec = 91516} (kgdb) inspect hz $2 = 1000 (kgdb) inspect tick $3 = 1000 (kgdb) inspect tmp $4 = 0 Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 19:41:04 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7741316A417 for ; Mon, 20 Aug 2007 19:41:04 +0000 (UTC) (envelope-from serguey-grigoriev@yandex.ru) Received: from webmail31.mail.yandex.net (webmail31.mail.yandex.net [213.180.223.177]) by mx1.freebsd.org (Postfix) with ESMTP id DE56613C4CC for ; Mon, 20 Aug 2007 19:41:03 +0000 (UTC) (envelope-from serguey-grigoriev@yandex.ru) Received: from YAMAIL (webmail31) by mail.yandex.ru id S6455596AbXHTSuT for ; Mon, 20 Aug 2007 22:50:19 +0400 X-Yandex-Spam: 1 Received: from [91.122.49.58] ([91.122.49.58]) by mail.yandex.ru with HTTP; Mon, 20 Aug 2007 22:50:18 +0400 From: "S.N.Grigoriev" To: freebsd-current@freebsd.org MIME-Version: 1.0 Message-Id: <786091187635818@webmail31.yandex.ru> Date: Mon, 20 Aug 2007 22:50:18 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailman-Approved-At: Mon, 20 Aug 2007 19:51:59 +0000 Subject: Cisco PIX/ASA VPN client X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 19:41:04 -0000 Hi list, I need to use my 7-CURRENT workstation as an IPSec client for Cisco PIX/ASA devices. I try to use /usr/ports/security/vpnc for this purpose. But when i start vpnc the following error message appears: socket(PF_INET, SOCK_RAW, IPPROTO_ESP): Protocol not supported Who knows if it is possible to use vpnc with CURRENT? Or may be I have to use another approach to solve my task? Thanks in advance, Serguey. From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 20:00:35 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BE7A16A417 for ; Mon, 20 Aug 2007 20:00:35 +0000 (UTC) (envelope-from cb@severious.net) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.freebsd.org (Postfix) with ESMTP id 06C4E13C458 for ; Mon, 20 Aug 2007 20:00:34 +0000 (UTC) (envelope-from cb@severious.net) Received: by ion.gank.org (Postfix, from userid 1001) id B73DD110E3; Mon, 20 Aug 2007 15:00:34 -0500 (CDT) Date: Mon, 20 Aug 2007 15:00:19 -0500 From: Craig Boston To: "S.N.Grigoriev" Message-ID: <20070820200018.GA29482@nowhere> Mail-Followup-To: Craig Boston , "S.N.Grigoriev" , freebsd-current@freebsd.org References: <786091187635818@webmail31.yandex.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <786091187635818@webmail31.yandex.ru> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: Cisco PIX/ASA VPN client X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 20:00:35 -0000 On Mon, Aug 20, 2007 at 10:50:18PM +0400, S.N.Grigoriev wrote: > I need to use my 7-CURRENT workstation as an IPSec client for > Cisco PIX/ASA devices. I try to use /usr/ports/security/vpnc > for this purpose. But when i start vpnc the following error > message appears: > > socket(PF_INET, SOCK_RAW, IPPROTO_ESP): Protocol not supported Do you have options IPSEC in your kernel? I believe this may prevent vpnc from sending/receiving the encapsulated packets. If you're not using IPSEC for anything else, removing the option should do the trick. Also, make sure that you're running it as root, not only for raw socket access but also so it can create the tun device. > Who knows if it is possible to use vpnc with CURRENT? Or may be I have > to use another approach to solve my task? I use vpnc quite a bit on CURRENT, and it works quite well, with the exception of fighting with dhclient over the resolv.conf file. (I know about exit hooks, but then I forget to remove them and wonder why DNS isn't working). Craig From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 20:26:49 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC98116A417 for ; Mon, 20 Aug 2007 20:26:49 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: from ik-out-1112.google.com (ik-out-1112.google.com [66.249.90.178]) by mx1.freebsd.org (Postfix) with ESMTP id A6DC813C458 for ; Mon, 20 Aug 2007 20:26:48 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: by ik-out-1112.google.com with SMTP id c21so307909ika for ; Mon, 20 Aug 2007 13:26:47 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:reply-to:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:message-id; b=MxHlbWpmltpHOY6Bo/kSe3ZDPdhEMOjnKB6CT1AiOf5FT7SohZO969xboUP4g/eIDtuW5FIBzrx3bM9HZIseM3IgMJA5Yq4T6rALXk7tWQvZFGDaP6M3AmaT8nKSLtU9YumHVK1HLZXYa7Jwfq8q2KqE1ILx+b4OmDjP67164wg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:reply-to:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:message-id; b=FKoEwiWpEJGP3ZJyEJHMReHSzGyWqSZKLu4b+mtPAr3zoGmwNdiYc1AUKEZyepCIpAX5JDp1odTCYHGo1R2N1TPjUKvmSPb1z4aR5np16ViYOJaeIc9Tn682KvmHDqtqBkGaz07w4H5C/z8UliKHF0qDMQln5dDP3Dj+FH/vj4Q= Received: by 10.78.168.1 with SMTP id q1mr2235513hue.1187641606425; Mon, 20 Aug 2007 13:26:46 -0700 (PDT) Received: from 77-109-34-147.dynamic.peoplenet.ua ( [77.109.34.147]) by mx.google.com with ESMTPS id 18sm2647165hue.2007.08.20.13.26.43 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 20 Aug 2007 13:26:44 -0700 (PDT) From: Nikolay Pavlov To: freebsd-current@freebsd.org Date: Mon, 20 Aug 2007 23:26:59 +0300 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4682400.etQkBxHyO7"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200708202327.03951.qpadla@gmail.com> Subject: Crash in todays current (panic: bio_caller1 used by the provider ad0s4e) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: qpadla@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 20:26:50 -0000 --nextPart4682400.etQkBxHyO7 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Another one panic caused by geom_journal journal initialization (sorry for= =20 tautology) at the final stage of EVERY kernel booting process. I am unable to get a full crashdump because my dump device is not ready at= =20 that moment. I see the message: panic: bio_caller1 used by the provider ad0s4e And a backtrace like this one: kdb_enter panic g_io_deliver g_std_done biodone g_io_schedule_up g_up_procbody fork_exit fork_trempoline And the current thread is pid 3 "g_up" The intresting thing is that i do not have this panic with GENERIC kernel. My kernel is deffer from it by this lines: #!commented! options WITNESS_SKIPSPIN options DEBUG_LOCKS options DEBUG_VFS_LOCKS options DIAGNOSTIC=20 =2D-=20 * Best regards, Nikolay Pavlov * --nextPart4682400.etQkBxHyO7 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBGyfkX/2R6KvEYGaIRAjMyAKCAFddLIPk6V4Nu7pgHlYftldwN2QCfSR/5 oC+0DxYnLDbqcVD55x8fLaQ= =xsIM -----END PGP SIGNATURE----- --nextPart4682400.etQkBxHyO7-- From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 20:40:19 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B074216A46E for ; Mon, 20 Aug 2007 20:40:19 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.freebsd.org (Postfix) with ESMTP id 0957713C459 for ; Mon, 20 Aug 2007 20:40:16 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so764042nfb for ; Mon, 20 Aug 2007 13:40:15 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:reply-to:to:subject:date:user-agent:cc:mime-version:content-type:content-transfer-encoding:message-id; b=IyjhMXW33of1VQGjGQt1DvPAcQyNsjo8awlmFf7RurE2CmW13pZiqh9Je9Y9pXFHyJDeT7se61IZgMFmWa+3WRzoLgwEkoTXeLd8KaEC4ElVY1QBRa3Q67lv2yzz0geoM+KClPIgCbRN9ed/bsbJ84Ex3RHYbHMbMzRSQLwvdVM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:reply-to:to:subject:date:user-agent:cc:mime-version:content-type:content-transfer-encoding:message-id; b=pEetQnTNZD3fqTXR9nz0b0mcq4QES9pS/14Ebmgx3aPw5fun2d0kljS97HQvDvHFBbIijYU5pLpjK6oG6zr1cqD7mTUjvaDxXBYVZUNfSEvkf+ISPEPgBBYw3inUvAWC29RszEJzCdM0cIrMBPoXhsPSEZRfZTbI48tW6l3QfB8= Received: by 10.78.188.10 with SMTP id l10mr2251315huf.1187642414594; Mon, 20 Aug 2007 13:40:14 -0700 (PDT) Received: from 77-109-34-147.dynamic.peoplenet.ua ( [77.109.34.147]) by mx.google.com with ESMTPS id 30sm2670855hub.2007.08.20.13.40.06 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 20 Aug 2007 13:40:09 -0700 (PDT) From: Nikolay Pavlov To: freebsd-current@freebsd.org Date: Mon, 20 Aug 2007 23:40:29 +0300 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart11003335.p7u4GOryHQ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200708202340.29678.qpadla@gmail.com> Cc: rwatson@freebsd.org Subject: And probably the final crash for today's current :) (panic: filesystem goof: vop_panic[vop_print]) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: qpadla@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 20:40:19 -0000 --nextPart11003335.p7u4GOryHQ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I am testing latest coda client code.=20 After simple ls -l /coda i am getting this panic: Unread portion of the kernel message buffer: KDB: stack backtrace: db_trace_self_wrapper(c0a9e0a9,e69729b0,c07c7933,0,e69729b0,...) at=20 db_trace_self_wrapper+0x26 kdb_backtrace(0,e69729b0,c0a15cf5,e69729c0,c821ac3c,...) at=20 kdb_backtrace+0x29 vfs_badlock(c4448c80,e69729c0,c0b7efc0,c821ac3c,0) at vfs_badlock+0x23 assert_vop_locked(c821ac3c,c0acdaac,810,0,c65aca00,...) at=20 assert_vop_locked+0x50 VOP_OPEN_APV(c4448c80,e6972a18,1,c483a500,c4867ab0,...) at=20 VOP_OPEN_APV+0x8a coda_open(e6972a8c,c0acdaac,c4864c00,0,e6972b80,...) at coda_open+0x11e VOP_OPEN_APV(c83ee6e0,e6972a8c,e6972a78,246,c8242984,...) at=20 VOP_OPEN_APV+0xc5 vn_open_cred(e6972b80,e6972c78,0,c483a500,c48358b8,...) at=20 vn_open_cred+0x43b vn_open(e6972b80,e6972c78,0,c48358b8,0,...) at vn_open+0x33 kern_open(c4864c00,281b280c,0,1,0,...) at kern_open+0xe7 open(c4864c00,e6972cfc,c,c0aa0d7e,c0b48838,...) at open+0x30 syscall(e6972d38) at syscall+0x2d3 Xint0x80_syscall() at Xint0x80_syscall+0x20 =2D-- syscall (5, FreeBSD ELF32, open), eip =3D 0x2819af0b, esp =3D 0xbfbfe= 64c,=20 ebp =3D 0xbfbfe688 --- VOP_OPEN: 0xc821ac3c is not locked but should be KDB: enter: lock violation exclusive sleep mutex Giant r =3D 0 (0xc0bb0a30) locked=20 @ /usr/src/sys/kern/vfs_lookup.c:658 Locked vnodes 0xc8242984: tag coda, type VDIR usecount 7, writecount 0, refcount 7 mountedhere 0 flags (VV_ROOT) lock type coda: EXCL (count 1) by thread 0xc4864c00 (pid 1247)#0=20 0xc073efc0 at _lockmgr+0x560 #1 0xc07bcb30 at vop_stdlock+0x40 #2 0xc0a18ea5 at VOP_LOCK1_APV+0xa5 #3 0xc07d6a68 at _vn_lock+0xf8 #4 0xc07bfbe0 at lookup+0xf0 #5 0xc07c0bce at namei+0x35e #6 0xc07d6529 at vn_open_cred+0x2b9 #7 0xc07d67c3 at vn_open+0x33 #8 0xc07d5417 at kern_open+0xe7 #9 0xc07d5900 at open+0x30 #10 0xc0a01ea3 at syscall+0x2d3 #11 0xc09e8190 at Xint0x80_syscall+0x20 panic: filesystem goof: vop_panic[vop_print] cpuid =3D 0 Uptime: 15m52s Physical memory: 1003 MB Dumping 205 MB: 190 174 158 142 126 110 94 78 62 46 30 14 #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc074ec7e in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:4= 09 #2 0xc074ef3b in panic (fmt=3DVariable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:563 #3 0xc07bca9d in vop_panic (ap=3DCould not find the frame base=20 for "vop_panic". ) at /usr/src/sys/kern/vfs_default.c:152 #4 0xc0a15f25 in VOP_PRINT_APV (vop=3D0xc83ee6e0, a=3D0xe6972634) at=20 vnode_if.c:1873 #5 0xc07c84af in vn_printf (vp=3D0xc8242984, fmt=3D0xc0a64c81 "%s\n") at=20 vnode_if.h:978 #6 0xc07cabf1 in lockedvnodes (addr=3D-1065918974, have_addr=3D0, count=3D= =2D1,=20 modif=3D0xe697279c "") at /usr/src/sys/kern/vfs_subr.c:2662 #7 0xc048d255 in db_command_loop () at /usr/src/sys/ddb/db_command.c:401 #8 0xc048e9c5 in db_trap (type=3D3, code=3D0)=20 at /usr/src/sys/ddb/db_main.c:222 #9 0xc0775c86 in kdb_trap (type=3D3, code=3D0, tf=3D0xe6972944)=20 at /usr/src/sys/kern/subr_kdb.c:502 #10 0xc0a026eb in trap (frame=3D0xe6972944)=20 at /usr/src/sys/i386/i386/trap.c:621 #11 0xc09e812b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #12 0xc0775e02 in kdb_enter (msg=3D0xc0aa6bc4 "lock violation") at=20 cpufunc.h:60 #13 0xc07c7969 in vfs_badlock (msg=3D0xc0aa6c19 "is not locked but should=20 be", str=3D0xc0acdaac "VOP_OPEN", vp=3D0xc821ac3c)=20 at /usr/src/sys/kern/vfs_subr.c:3432 #14 0xc07ca360 in assert_vop_locked (vp=3D0xc821ac3c,=20 str=3D0xc0acdaac "VOP_OPEN") at /usr/src/sys/kern/vfs_subr.c:3456 #15 0xc0a1841a in VOP_OPEN_APV (vop=3D0xc4448c80, a=3D0xe6972a18) at=20 vnode_if.c:369 #16 0xc83ea78e in ?? () #17 0xc4448c80 in ?? () #18 0xe6972a18 in ?? () #19 0x00000001 in ?? () #20 0xc483a500 in ?? () #21 0xc4867ab0 in ?? () #22 0xe6972a30 in ?? () #23 0x00000001 in ?? () #24 0xc483a500 in ?? () #25 0xc4864c00 in ?? () #26 0xc0b7f080 in vop_mknod_desc () #27 0xc821ac3c in ?? () #28 0x00000001 in ?? () #29 0xc483a500 in ?? () #30 0xc4864c00 in ?? () #31 0x00000000 in ?? () #32 0xc821ac3c in ?? () #33 0xc83ee6e0 in ?? () #34 0xe6972a8c in ?? () #35 0x00000001 in ?? () #36 0xe6972a5c in ?? () #37 0xc0a18455 in VOP_OPEN_APV (vop=3D0x0, a=3D0xc65aca00) at vnode_if.c:371 Previous frame identical to this frame (corrupt stack?) P.S. I forgot the original CODA maintainer email, could some forward this=20 to him? =2D-=20 * Best regards, Nikolay Pavlov * --nextPart11003335.p7u4GOryHQ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBGyfw9/2R6KvEYGaIRAsgFAJ98BTcTch4ewVAmRNmTNxRJwBrlgACeOi62 SprD231UUi04YBi0n2iBixw= =bd7A -----END PGP SIGNATURE----- --nextPart11003335.p7u4GOryHQ-- From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 20:42:35 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC19D16A420 for ; Mon, 20 Aug 2007 20:42:35 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from spacemail2-out.mgmt.space.net (spacemail2-out.mgmt.space.net [194.97.149.148]) by mx1.freebsd.org (Postfix) with ESMTP id 7A83613C491 for ; Mon, 20 Aug 2007 20:42:35 +0000 (UTC) (envelope-from se@FreeBSD.org) X-SpaceNet-SBRS: None X-IronPort-AV: E=Sophos;i="4.19,285,1183327200"; d="scan'208";a="33087131" Received: from mail.atsec.com ([195.30.252.105]) by spacemail2-out.mgmt.space.net with ESMTP; 20 Aug 2007 22:12:51 +0200 Received: from [192.168.0.12] (p5087A28C.dip0.t-ipconnect.de [80.135.162.140]) (Authenticated sender: se@atsec.com) by mail.atsec.com (Postfix) with ESMTP id C7ED47209ED; Mon, 20 Aug 2007 22:12:50 +0200 (CEST) Message-ID: <46C9F5C0.6000209@FreeBSD.org> Date: Mon, 20 Aug 2007 22:12:48 +0200 From: Stefan Esser User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Max Laier References: <200708170939.l7H9diEk054469@lurza.secnetix.de> <20070819163934.V568@10.0.0.1> <20070820103424.GG1164@turion.vk2pj.dyndns.org> <200708202058.39565.max@love2party.net> In-Reply-To: <200708202058.39565.max@love2party.net> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: Peter Jeremy , freebsd-current@freebsd.org, Jeff Roberson Subject: Re: Why we don't use bzip2 in sysinstall/rescue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 20:42:36 -0000 Max Laier schrieb: > With an amd64 world(236M) tar'ed together with -czf / -cyf respectively I > get the following input bandwidth numbers (gathered via dd > if=amd64.t{g,b}z of=/dev/stdio | {g,b}zcat > /dev/null): > > hw.model: Intel(R) Pentium(R) 4 CPU 2.00GHz: > x bz + gz > N Min Max Median Avg Stddev > x 13 1411432 1554463 1544446 1521445.7 50394.705 > + 13 13391136 13847045 13804007 13726781 138363.27 Instead of measuring data rates on the input side (compressed) I think what matters is the output data rate, since that is what needs to be written to disk during an installation. If I assume a compression by a factor of 4 for bzip2, the data rate will be some 6MB/s after decompression on a P4/2GHz and 14MB/s on the Opteron 275. I have measured an P3/733 to deliver 3.25MB/s for bzip2 (and 40MB/s for gzip with a compression of about 1:3.5). > Difference at 95.0% confidence > 1.22053e+07 +/- 84296.2 > 802.22% +/- 5.54053% > (Student's t, pooled s = 104125) > > hw.model=AMD Opteron(tm) Processor 275: > x fast.bz + fast.gz > N Min Max Median Avg Stddev > x 10 3429556 3889574 3449869 3525725.6 169675.46 > + 10 41967910 46046387 45944662 45490300 1257435.8 > Difference at 95.0% confidence > 4.19646e+07 +/- 843005 > 1190.24% +/- 23.9101% > (Student's t, pooled s = 897200) > > So it seems that bzip2 will indeed be bound to CPU - at least when > installing from CD. netinst over the internet is a different story, > though. Since lots of small files are written, we have to consider the transaction rate of the disk and file system being written to. And while 3MB/s is a little low, 6MB/s does not look unreasonable and 14MB/s is definitely sufficient to make the target disk drive become the limiting component (except when you install to a RAM disk or to a RAID storage system with gigabytes of cache ;-) Regards, STefan From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 21:19:59 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F9BE16A419 for ; Mon, 20 Aug 2007 21:19:59 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 3B70813C478 for ; Mon, 20 Aug 2007 21:19:59 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id D416946EBE; Mon, 20 Aug 2007 17:19:58 -0400 (EDT) Date: Mon, 20 Aug 2007 22:19:58 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jan Harkes Message-ID: <20070820221934.I97677@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@FreeBSD.org Subject: And probably the final crash for today's current :) (panic: filesystem goof: vop_panic[vop_print]) (fwd) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 21:19:59 -0000 Jan, I think this may be for you :-). Robert N M Watson Computer Laboratory University of Cambridge ---------- Forwarded message ---------- Date: Mon, 20 Aug 2007 23:40:29 +0300 From: Nikolay Pavlov To: freebsd-current@freebsd.org Cc: rwatson@freebsd.org Subject: And probably the final crash for today's current :) (panic: filesystem goof: vop_panic[vop_print]) I am testing latest coda client code. After simple ls -l /coda i am getting this panic: Unread portion of the kernel message buffer: KDB: stack backtrace: db_trace_self_wrapper(c0a9e0a9,e69729b0,c07c7933,0,e69729b0,...) at db_trace_self_wrapper+0x26 kdb_backtrace(0,e69729b0,c0a15cf5,e69729c0,c821ac3c,...) at kdb_backtrace+0x29 vfs_badlock(c4448c80,e69729c0,c0b7efc0,c821ac3c,0) at vfs_badlock+0x23 assert_vop_locked(c821ac3c,c0acdaac,810,0,c65aca00,...) at assert_vop_locked+0x50 VOP_OPEN_APV(c4448c80,e6972a18,1,c483a500,c4867ab0,...) at VOP_OPEN_APV+0x8a coda_open(e6972a8c,c0acdaac,c4864c00,0,e6972b80,...) at coda_open+0x11e VOP_OPEN_APV(c83ee6e0,e6972a8c,e6972a78,246,c8242984,...) at VOP_OPEN_APV+0xc5 vn_open_cred(e6972b80,e6972c78,0,c483a500,c48358b8,...) at vn_open_cred+0x43b vn_open(e6972b80,e6972c78,0,c48358b8,0,...) at vn_open+0x33 kern_open(c4864c00,281b280c,0,1,0,...) at kern_open+0xe7 open(c4864c00,e6972cfc,c,c0aa0d7e,c0b48838,...) at open+0x30 syscall(e6972d38) at syscall+0x2d3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (5, FreeBSD ELF32, open), eip = 0x2819af0b, esp = 0xbfbfe64c, ebp = 0xbfbfe688 --- VOP_OPEN: 0xc821ac3c is not locked but should be KDB: enter: lock violation exclusive sleep mutex Giant r = 0 (0xc0bb0a30) locked @ /usr/src/sys/kern/vfs_lookup.c:658 Locked vnodes 0xc8242984: tag coda, type VDIR usecount 7, writecount 0, refcount 7 mountedhere 0 flags (VV_ROOT) lock type coda: EXCL (count 1) by thread 0xc4864c00 (pid 1247)#0 0xc073efc0 at _lockmgr+0x560 #1 0xc07bcb30 at vop_stdlock+0x40 #2 0xc0a18ea5 at VOP_LOCK1_APV+0xa5 #3 0xc07d6a68 at _vn_lock+0xf8 #4 0xc07bfbe0 at lookup+0xf0 #5 0xc07c0bce at namei+0x35e #6 0xc07d6529 at vn_open_cred+0x2b9 #7 0xc07d67c3 at vn_open+0x33 #8 0xc07d5417 at kern_open+0xe7 #9 0xc07d5900 at open+0x30 #10 0xc0a01ea3 at syscall+0x2d3 #11 0xc09e8190 at Xint0x80_syscall+0x20 panic: filesystem goof: vop_panic[vop_print] cpuid = 0 Uptime: 15m52s Physical memory: 1003 MB Dumping 205 MB: 190 174 158 142 126 110 94 78 62 46 30 14 #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc074ec7e in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #2 0xc074ef3b in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:563 #3 0xc07bca9d in vop_panic (ap=Could not find the frame base for "vop_panic". ) at /usr/src/sys/kern/vfs_default.c:152 #4 0xc0a15f25 in VOP_PRINT_APV (vop=0xc83ee6e0, a=0xe6972634) at vnode_if.c:1873 #5 0xc07c84af in vn_printf (vp=0xc8242984, fmt=0xc0a64c81 "%s\n") at vnode_if.h:978 #6 0xc07cabf1 in lockedvnodes (addr=-1065918974, have_addr=0, count=-1, modif=0xe697279c "") at /usr/src/sys/kern/vfs_subr.c:2662 #7 0xc048d255 in db_command_loop () at /usr/src/sys/ddb/db_command.c:401 #8 0xc048e9c5 in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_main.c:222 #9 0xc0775c86 in kdb_trap (type=3, code=0, tf=0xe6972944) at /usr/src/sys/kern/subr_kdb.c:502 #10 0xc0a026eb in trap (frame=0xe6972944) at /usr/src/sys/i386/i386/trap.c:621 #11 0xc09e812b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #12 0xc0775e02 in kdb_enter (msg=0xc0aa6bc4 "lock violation") at cpufunc.h:60 #13 0xc07c7969 in vfs_badlock (msg=0xc0aa6c19 "is not locked but should be", str=0xc0acdaac "VOP_OPEN", vp=0xc821ac3c) at /usr/src/sys/kern/vfs_subr.c:3432 #14 0xc07ca360 in assert_vop_locked (vp=0xc821ac3c, str=0xc0acdaac "VOP_OPEN") at /usr/src/sys/kern/vfs_subr.c:3456 #15 0xc0a1841a in VOP_OPEN_APV (vop=0xc4448c80, a=0xe6972a18) at vnode_if.c:369 #16 0xc83ea78e in ?? () #17 0xc4448c80 in ?? () #18 0xe6972a18 in ?? () #19 0x00000001 in ?? () #20 0xc483a500 in ?? () #21 0xc4867ab0 in ?? () #22 0xe6972a30 in ?? () #23 0x00000001 in ?? () #24 0xc483a500 in ?? () #25 0xc4864c00 in ?? () #26 0xc0b7f080 in vop_mknod_desc () #27 0xc821ac3c in ?? () #28 0x00000001 in ?? () #29 0xc483a500 in ?? () #30 0xc4864c00 in ?? () #31 0x00000000 in ?? () #32 0xc821ac3c in ?? () #33 0xc83ee6e0 in ?? () #34 0xe6972a8c in ?? () #35 0x00000001 in ?? () #36 0xe6972a5c in ?? () #37 0xc0a18455 in VOP_OPEN_APV (vop=0x0, a=0xc65aca00) at vnode_if.c:371 Previous frame identical to this frame (corrupt stack?) P.S. I forgot the original CODA maintainer email, could some forward this to him? -- * Best regards, Nikolay Pavlov * From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 00:23:47 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63A5816A418 for ; Tue, 21 Aug 2007 00:23:47 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by mx1.freebsd.org (Postfix) with ESMTP id 31DE913C483 for ; Tue, 21 Aug 2007 00:23:47 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so1000159waf for ; Mon, 20 Aug 2007 17:23:46 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=GOypTV+QT0B09gOdJL+Ua+MZYlW4dObP3t6Pt+GRkOvpG28P+v9ciZ6M/DOxlJzbCriLMBeJ/UxsuEtJiHnh7Aau06suo9A7U4MMb4iMAohJ6TLFDQSUHE1zFP6ujub0nYbarFM+KeS0KCP5JsChXWL6pEPEyNGY+C3Jwsm589Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=FdDanO8FpTfG/tA7heW16DHYaOYXCWOlqLyqKCOttaZbfViGa/JiwcguOokrvXjb1iHLHt8j8b4XvTmh3hGz6sx9UfDpnHiI/odsHlRKGe1/3fSUSKPMQnlZnHHl9Xx/nkTTS0myuMrZxwMJMuSYfho/D20hFXatPMiZIc3AI68= Received: by 10.115.108.1 with SMTP id k1mr3790975wam.1187655826672; Mon, 20 Aug 2007 17:23:46 -0700 (PDT) Received: by 10.115.77.13 with HTTP; Mon, 20 Aug 2007 17:23:46 -0700 (PDT) Message-ID: <4956a5e50708201723l623cf384ub10edd3ceea88e62@mail.gmail.com> Date: Mon, 20 Aug 2007 21:23:46 -0300 From: Nenhum_de_Nos To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mailman-Approved-At: Tue, 21 Aug 2007 02:16:35 +0000 Subject: error building yesterday code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 00:23:47 -0000 ===> ata/atapicd (all) cc -O2 -fno-strict-aliasing -pipe -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/xxx_7/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/xxx_7 -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/ata/atapicd/../../../dev/ata/atapi-cd.c /usr/src/sys/modules/ata/atapicd/../../../dev/ata/atapi-cd.c: In function 'acd_geom_ioctl': /usr/src/sys/modules/ata/atapicd/../../../dev/ata/atapi-cd.c:210: internal compiler error: Segmentation fault: 11 Please submit a full bug report, with preprocessed source if appropriate. See for instructions. *** Error code 1 Stop in /usr/src/sys/modules/ata/atapicd. *** Error code 1 Stop in /usr/src/sys/modules/ata. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/xxx_7. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. [root@xxx /usr/src]# if anyona has any hints ... this happened before, for building world I had to keep repeating the make command with -DNOCLEAN till it ended good ... thanks in advance matheus -- We will call you cygnus, The God of balance you shall be From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 03:49:20 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 171F416A417 for ; Tue, 21 Aug 2007 03:49:20 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay02.kiev.sovam.com (relay02.kiev.sovam.com [62.64.120.197]) by mx1.freebsd.org (Postfix) with ESMTP id 9E4E813C467 for ; Tue, 21 Aug 2007 03:49:19 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from [89.162.146.170] (helo=skuns.kiev.zoral.com.ua) by relay02.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1INKjs-000LCW-Nm; Tue, 21 Aug 2007 06:49:17 +0300 Received: from deviant.kiev.zoral.com.ua (root@[10.1.1.148]) by skuns.kiev.zoral.com.ua (8.14.1/8.14.1) with ESMTP id l7KKq1FK059254 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Aug 2007 23:52:01 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.1/8.14.1) with ESMTP id l7KKq1x8049102; Mon, 20 Aug 2007 23:52:01 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.1/8.14.1/Submit) id l7KKq1Ng049101; Mon, 20 Aug 2007 23:52:01 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 20 Aug 2007 23:52:01 +0300 From: Kostik Belousov To: Nikolay Pavlov Message-ID: <20070820205201.GW2738@deviant.kiev.zoral.com.ua> References: <200708202340.29678.qpadla@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vLS+sh2tCBRapC7G" Content-Disposition: inline In-Reply-To: <200708202340.29678.qpadla@gmail.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.91.1, clamav-milter version 0.91.1 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.2.1 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on skuns.kiev.zoral.com.ua X-Scanner-Signature: dc9851233e967de4527dd65bbc92362e X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Header: Not Detected X-SpamTest-Info: Profiles 1391 [August 20 2007] X-SpamTest-Info: helo_type=3 X-SpamTest-Method: none X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release Cc: freebsd-current@freebsd.org, rwatson@freebsd.org Subject: Re: And probably the final crash for today's current :) (panic: filesystem goof: vop_panic[vop_print]) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 03:49:20 -0000 --vLS+sh2tCBRapC7G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 20, 2007 at 11:40:29PM +0300, Nikolay Pavlov wrote: > I am testing latest coda client code.=20 > After simple ls -l /coda i am getting this panic: >=20 > Unread portion of the kernel message buffer: > KDB: stack backtrace: > db_trace_self_wrapper(c0a9e0a9,e69729b0,c07c7933,0,e69729b0,...) at=20 > db_trace_self_wrapper+0x26 > kdb_backtrace(0,e69729b0,c0a15cf5,e69729c0,c821ac3c,...) at=20 > kdb_backtrace+0x29 > vfs_badlock(c4448c80,e69729c0,c0b7efc0,c821ac3c,0) at vfs_badlock+0x23 > assert_vop_locked(c821ac3c,c0acdaac,810,0,c65aca00,...) at=20 > assert_vop_locked+0x50 > VOP_OPEN_APV(c4448c80,e6972a18,1,c483a500,c4867ab0,...) at=20 > VOP_OPEN_APV+0x8a > coda_open(e6972a8c,c0acdaac,c4864c00,0,e6972b80,...) at coda_open+0x11e > VOP_OPEN_APV(c83ee6e0,e6972a8c,e6972a78,246,c8242984,...) at=20 > VOP_OPEN_APV+0xc5 > vn_open_cred(e6972b80,e6972c78,0,c483a500,c48358b8,...) at=20 > vn_open_cred+0x43b > vn_open(e6972b80,e6972c78,0,c48358b8,0,...) at vn_open+0x33 > kern_open(c4864c00,281b280c,0,1,0,...) at kern_open+0xe7 > open(c4864c00,e6972cfc,c,c0aa0d7e,c0b48838,...) at open+0x30 > syscall(e6972d38) at syscall+0x2d3 > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (5, FreeBSD ELF32, open), eip =3D 0x2819af0b, esp =3D 0xbfbfe= 64c,=20 > ebp =3D 0xbfbfe688 --- > VOP_OPEN: 0xc821ac3c is not locked but should be > KDB: enter: lock violation > exclusive sleep mutex Giant r =3D 0 (0xc0bb0a30) locked=20 > @ /usr/src/sys/kern/vfs_lookup.c:658 > Locked vnodes >=20 > 0xc8242984: tag coda, type VDIR > usecount 7, writecount 0, refcount 7 mountedhere 0 > flags (VV_ROOT) > lock type coda: EXCL (count 1) by thread 0xc4864c00 (pid 1247)#0=20 > 0xc073efc0 at _lockmgr+0x560 > #1 0xc07bcb30 at vop_stdlock+0x40 > #2 0xc0a18ea5 at VOP_LOCK1_APV+0xa5 > #3 0xc07d6a68 at _vn_lock+0xf8 > #4 0xc07bfbe0 at lookup+0xf0 > #5 0xc07c0bce at namei+0x35e > #6 0xc07d6529 at vn_open_cred+0x2b9 > #7 0xc07d67c3 at vn_open+0x33 > #8 0xc07d5417 at kern_open+0xe7 > #9 0xc07d5900 at open+0x30 > #10 0xc0a01ea3 at syscall+0x2d3 > #11 0xc09e8190 at Xint0x80_syscall+0x20 >=20 > panic: filesystem goof: vop_panic[vop_print] > cpuid =3D 0 > Uptime: 15m52s > Physical memory: 1003 MB > Dumping 205 MB: 190 174 158 142 126 110 94 78 62 46 30 14 >=20 > #0 doadump () at pcpu.h:195 > 195 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) bt > #0 doadump () at pcpu.h:195 > #1 0xc074ec7e in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c= :409 > #2 0xc074ef3b in panic (fmt=3DVariable "fmt" is not available. > ) at /usr/src/sys/kern/kern_shutdown.c:563 > #3 0xc07bca9d in vop_panic (ap=3DCould not find the frame base=20 > for "vop_panic". > ) at /usr/src/sys/kern/vfs_default.c:152 > #4 0xc0a15f25 in VOP_PRINT_APV (vop=3D0xc83ee6e0, a=3D0xe6972634) at=20 > vnode_if.c:1873 > #5 0xc07c84af in vn_printf (vp=3D0xc8242984, fmt=3D0xc0a64c81 "%s\n") at= =20 > vnode_if.h:978 > #6 0xc07cabf1 in lockedvnodes (addr=3D-1065918974, have_addr=3D0, count= =3D-1,=20 > modif=3D0xe697279c "") at /usr/src/sys/kern/vfs_subr.c:2662 > #7 0xc048d255 in db_command_loop () at /usr/src/sys/ddb/db_command.c:401 > #8 0xc048e9c5 in db_trap (type=3D3, code=3D0)=20 > at /usr/src/sys/ddb/db_main.c:222 > #9 0xc0775c86 in kdb_trap (type=3D3, code=3D0, tf=3D0xe6972944)=20 > at /usr/src/sys/kern/subr_kdb.c:502 > #10 0xc0a026eb in trap (frame=3D0xe6972944)=20 > at /usr/src/sys/i386/i386/trap.c:621 > #11 0xc09e812b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 > #12 0xc0775e02 in kdb_enter (msg=3D0xc0aa6bc4 "lock violation") at=20 > cpufunc.h:60 > #13 0xc07c7969 in vfs_badlock (msg=3D0xc0aa6c19 "is not locked but should= =20 > be", str=3D0xc0acdaac "VOP_OPEN", vp=3D0xc821ac3c)=20 > at /usr/src/sys/kern/vfs_subr.c:3432 > #14 0xc07ca360 in assert_vop_locked (vp=3D0xc821ac3c,=20 > str=3D0xc0acdaac "VOP_OPEN") at /usr/src/sys/kern/vfs_subr.c:3456 > #15 0xc0a1841a in VOP_OPEN_APV (vop=3D0xc4448c80, a=3D0xe6972a18) at=20 > vnode_if.c:369 > #16 0xc83ea78e in ?? () > #17 0xc4448c80 in ?? () > #18 0xe6972a18 in ?? () > #19 0x00000001 in ?? () > #20 0xc483a500 in ?? () > #21 0xc4867ab0 in ?? () > #22 0xe6972a30 in ?? () > #23 0x00000001 in ?? () > #24 0xc483a500 in ?? () > #25 0xc4864c00 in ?? () > #26 0xc0b7f080 in vop_mknod_desc () > #27 0xc821ac3c in ?? () > #28 0x00000001 in ?? () > #29 0xc483a500 in ?? () > #30 0xc4864c00 in ?? () > #31 0x00000000 in ?? () > #32 0xc821ac3c in ?? () > #33 0xc83ee6e0 in ?? () > #34 0xe6972a8c in ?? () > #35 0x00000001 in ?? () > #36 0xe6972a5c in ?? () > #37 0xc0a18455 in VOP_OPEN_APV (vop=3D0x0, a=3D0xc65aca00) at vnode_if.c:= 371 > Previous frame identical to this frame (corrupt stack?) >=20 > P.S. I forgot the original CODA maintainer email, could some forward this= =20 > to him? Quite often, the "impossible" panics with vnode locking are happens because some other thread already paniced the kernel. Then, lockmgr passes all lock requests without actually locking. I would suggest looking around to make sure this is not the case there. --vLS+sh2tCBRapC7G Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGyf7wC3+MBN1Mb4gRAiu5AKCIdwuAPZwq6hH+o9vspxXdq709AgCguhTs /mPnOPAgVh/jE86QElyftxg= =hPhV -----END PGP SIGNATURE----- --vLS+sh2tCBRapC7G-- From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 03:49:38 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A17416A418 for ; Tue, 21 Aug 2007 03:49:38 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay02.kiev.sovam.com (relay02.kiev.sovam.com [62.64.120.197]) by mx1.freebsd.org (Postfix) with ESMTP id 35A4E13C474 for ; Tue, 21 Aug 2007 03:49:38 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from [89.162.146.170] (helo=skuns.kiev.zoral.com.ua) by relay02.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1INKkC-000LCW-Q3 for freebsd-current@freebsd.org; Tue, 21 Aug 2007 06:49:37 +0300 Received: from deviant.kiev.zoral.com.ua (root@[10.1.1.148]) by skuns.kiev.zoral.com.ua (8.14.1/8.14.1) with ESMTP id l7KGNBIo054102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Aug 2007 19:23:11 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.1/8.14.1) with ESMTP id l7KGNBuu089254; Mon, 20 Aug 2007 19:23:11 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.1/8.14.1/Submit) id l7KGNBFk089253; Mon, 20 Aug 2007 19:23:11 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 20 Aug 2007 19:23:11 +0300 From: Kostik Belousov To: Nikolay Pavlov Message-ID: <20070820162311.GT2738@deviant.kiev.zoral.com.ua> References: <200708201848.22157.qpadla@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pLlCf/bEWtYPubJE" Content-Disposition: inline In-Reply-To: <200708201848.22157.qpadla@gmail.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.91.1, clamav-milter version 0.91.1 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.2.1 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on skuns.kiev.zoral.com.ua X-Scanner-Signature: 16f7817bad8e28cbcc8c205d7fb50ad4 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Header: Not Detected X-SpamTest-Info: Profiles 1391 [August 20 2007] X-SpamTest-Info: helo_type=3 X-SpamTest-Method: none X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release Cc: freebsd-current@freebsd.org Subject: Re: Panic on todays current (panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/kern/vfs_mount.c:1046) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 03:49:38 -0000 --pLlCf/bEWtYPubJE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 20, 2007 at 06:48:17PM +0300, Nikolay Pavlov wrote: > Hello. I've got this while booting: >=20 > Starting file system checks: > /dev/ad0s4a: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/ad0s4a: clean, 6113 free (241 frags, 734 blocks, 0.2% fragmentation) > /dev/ad0s4f: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/ad0s4f: clean, 67511 free (2623 frags, 8111 blocks, 0.4%=20 > fragmentation) > /dev/ad0s4e.journal: FILE SYSTEM CLEAN; SKIPPING CHECKS > Setting hostuuid: 44454C4C-4400-1039-8030-B6C04F4A324A. > Setting hostid: 0x7817d87e. > Mounting local file systems: > panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/kern/vfs_mount.c:10= 46 > cpuid =3D 0 > KDB: enter: panic > exclusive sleep mutex Giant r =3D 0 (0xc0ba7350) locked=20 > @ /usr/src/sys/kern/kern_module.c:117 > panic: from debugger > cpuid =3D 0 > Uptime: 6s > Physical memory: 1003 MB > Dumping 47 MB: 32 16 >=20 > #0 doadump () at pcpu.h:195 > 195 __asm __volatile("movl %%fs:0,%0" : "=3Dr" (td)); > (kgdb) bt > #0 doadump () at pcpu.h:195 > #1 0xc074c19e in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c= :409 > #2 0xc074c45b in panic (fmt=3DVariable "fmt" is not available. > ) at /usr/src/sys/kern/kern_shutdown.c:563 > #3 0xc048c6d7 in db_panic (addr=3DCould not find the frame base=20 > for "db_panic". > ) at /usr/src/sys/ddb/db_command.c:433 > #4 0xc048d0c5 in db_command_loop () at /usr/src/sys/ddb/db_command.c:401 > #5 0xc048e835 in db_trap (type=3D3, code=3D0)=20 > at /usr/src/sys/ddb/db_main.c:222 > #6 0xc07730c6 in kdb_trap (type=3D3, code=3D0, tf=3D0xe46959f0)=20 > at /usr/src/sys/kern/subr_kdb.c:502 > #7 0xc09fd25b in trap (frame=3D0xe46959f0)=20 > at /usr/src/sys/i386/i386/trap.c:621 > #8 0xc09e2c8b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 > #9 0xc0773242 in kdb_enter (msg=3D0xc0a93513 "panic") at cpufunc.h:60 > #10 0xc074c444 in panic (fmt=3D0xc0a92475 "mtx_lock() of spin mutex %s @ = %s: > %d") at /usr/src/sys/kern/kern_shutdown.c:547 > #11 0xc0740d3a in _mtx_lock_flags (m=3D0xc42b0000, opts=3D0,=20 > file=3D0xc0a9e111 "/usr/src/sys/kern/vfs_mount.c", line=3D1046)=20 > at /usr/src/sys/kern/kern_mutex.c:180 > #12 0xc07c154b in vfs_donmount (td=3D0xc429f800, fsflags=3D0,=20 > fsoptions=3D0xc431ce00) at /usr/src/sys/kern/vfs_mount.c:1046 > #13 0xc07c25e3 in nmount (td=3D0xc429f800, uap=3D0xe4695cfc)=20 > at /usr/src/sys/kern/vfs_mount.c:413 > #14 0xc09fca13 in syscall (frame=3D0xe4695d38)=20 > at /usr/src/sys/i386/i386/trap.c:1008 > #15 0xc09e2cf0 in Xint0x80_syscall ()=20 > at /usr/src/sys/i386/i386/exception.s:196 > #16 0x00000033 in ?? () > Previous frame inner to this frame (corrupt stack?) The line where the reported panic happens is located at the point where several successfull locks of the mount structure interlock alread happen (see, for instance, line 983). In between, there is a call to VFS_MOUNT() method of the fs. It would be interesting to look at the type of the filesystem being mounted. Just a guess: Could it be that mounted filesystem comes from module, that uses incompatib= le binary interface (for instance, built with different kernel options or for different kernel version) ? --pLlCf/bEWtYPubJE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGyb/uC3+MBN1Mb4gRAomNAKCXGp0JrVX62M4ZGeGCDW0EPUHSMgCfTxTl /dxaoya0KcWA2krD66xnmxU= =m/IY -----END PGP SIGNATURE----- --pLlCf/bEWtYPubJE-- From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 02:31:46 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B143D16A418 for ; Tue, 21 Aug 2007 02:31:46 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.179]) by mx1.freebsd.org (Postfix) with ESMTP id 8CA4A13C467 for ; Tue, 21 Aug 2007 02:31:46 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: by wa-out-1112.google.com with SMTP id m33so964407wag for ; Mon, 20 Aug 2007 19:31:46 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=eAo7OL1WCNvE7UAabL3siU5qbXalYvBkHsVsI1jBR+/tYh9mOJQQb7PWr+EmAqe4ZBqbgwQARdq2MCRVwYlFMEacTJu6/qQAfwgLTQULL0Q5lzWjt952bt9xyZM2lzjnmVDsJh9+6fKqXu2DOmUFxEvNA26+3RcfMynhhHrOlwM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qSqD4Qel+Jjodze8gxNpRt669VU1rOpT7B3VujqcD1tL76yJymleU1e261P15ZAHk+jBl/2AUBzLoOtU8JqPdPi053FAt8RCE7cvGMFDqAhqt7R5O2jane0Awn1INEzCgfurWIILgG3fwZcAeT/R+WG6vjdg4KF5/rlqxrYTZ+Y= Received: by 10.114.109.1 with SMTP id h1mr944697wac.1187663506076; Mon, 20 Aug 2007 19:31:46 -0700 (PDT) Received: by 10.115.77.13 with HTTP; Mon, 20 Aug 2007 19:31:46 -0700 (PDT) Message-ID: <4956a5e50708201931t5e55d1d3lb329ed53b0edb356@mail.gmail.com> Date: Mon, 20 Aug 2007 23:31:46 -0300 From: Nenhum_de_Nos To: freebsd-current@freebsd.org In-Reply-To: <4956a5e50708201723l623cf384ub10edd3ceea88e62@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4956a5e50708201723l623cf384ub10edd3ceea88e62@mail.gmail.com> X-Mailman-Approved-At: Tue, 21 Aug 2007 04:24:43 +0000 Subject: Re: error building yesterday code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 02:31:46 -0000 c++ -I/usr/src/gnu/lib/libstdc++/../../../contrib/gcc -I/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include -I/usr/src/gnu/lib/libstdc++/../../../contrib/gcclibs/include -I/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include -I. -frandom-seed=RepeatabilityConsideredGood -fno-implicit-templates -ffunction-sections -fdata-sections -Wno-deprecated -c /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/fstream-inst.cc /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/fstream-inst.cc: In member function 'void std::basic_ifstream<_CharT, _Traits>::open(const char*, std::_Ios_Openmode) [with _CharT = wchar_t, _Traits = std::char_traits]': /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/fstream-inst.cc:50: internal compiler error: Segmentation fault: 11 Please submit a full bug report, with preprocessed source if appropriate. See for instructions. *** Error code 1 Stop in /usr/src/gnu/lib/libstdc++. *** Error code 1 Stop in /usr/src/gnu/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. [root@xxx /usr/src]# today's sources are no better :( matheus -- We will call you cygnus, The God of balance you shall be From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 04:32:55 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 649D416A46C for ; Tue, 21 Aug 2007 04:32:55 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.freebsd.org (Postfix) with ESMTP id D51A213C459 for ; Tue, 21 Aug 2007 04:32:54 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so844477nfb for ; Mon, 20 Aug 2007 21:32:52 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=FfY48W88bSLJmEsBPb97tuxssdPwU7n6FM9SgkQRDrcny0B1n98MvMjvAXJL3bd5oF2QcMrTqEM3zg4V2+Cmv4EbBLaT+HUiDAkMlLHbirbSmEv44HVk0eAG8T1s1ZT/BlGQlFoKfVE+wc+NXhRwWeC0fs7SFSruw42/q+Tj0fU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ur025F8D51WJFPWkSjCkMahlPb8aLplk2mgiYqsDZw8kA+7lmAEmif2eXJzdaScrbD6kZLd9SNn6Z3K816jU+uAqZAS3iUN8Zh4rTNqwjT1PkwGQ30dYxQ3/DFNTMfaAm9DGcqyEsbbAQ5c259yBulQtwBYhHKNvMm1E6fWNHIk= Received: by 10.78.136.9 with SMTP id j9mr2493710hud.1187670772164; Mon, 20 Aug 2007 21:32:52 -0700 (PDT) Received: by 10.78.162.18 with HTTP; Mon, 20 Aug 2007 21:32:52 -0700 (PDT) Message-ID: Date: Mon, 20 Aug 2007 21:32:52 -0700 From: "Kip Macy" To: Nenhum_de_Nos In-Reply-To: <4956a5e50708201931t5e55d1d3lb329ed53b0edb356@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4956a5e50708201723l623cf384ub10edd3ceea88e62@mail.gmail.com> <4956a5e50708201931t5e55d1d3lb329ed53b0edb356@mail.gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: error building yesterday code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 04:32:55 -0000 Sounds like bad memory. Try memtest. -Kip On 8/20/07, Nenhum_de_Nos wrote: > c++ -I/usr/src/gnu/lib/libstdc++/../../../contrib/gcc > -I/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include > -I/usr/src/gnu/lib/libstdc++/../../../contrib/gcclibs/include > -I/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include -I. > -frandom-seed=RepeatabilityConsideredGood -fno-implicit-templates > -ffunction-sections -fdata-sections -Wno-deprecated -c > /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/fstream-inst.cc > /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/fstream-inst.cc: > In member function 'void std::basic_ifstream<_CharT, > _Traits>::open(const char*, std::_Ios_Openmode) [with _CharT = > wchar_t, _Traits = std::char_traits]': > /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/fstream-inst.cc:50: > internal compiler error: Segmentation fault: 11 > Please submit a full bug report, > with preprocessed source if appropriate. > See for instructions. > *** Error code 1 > > Stop in /usr/src/gnu/lib/libstdc++. > *** Error code 1 > > Stop in /usr/src/gnu/lib. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > [root@xxx /usr/src]# > > today's sources are no better :( > > matheus > > -- > We will call you cygnus, > The God of balance you shall be > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 04:50:52 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C24816A417 for ; Tue, 21 Aug 2007 04:50:52 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.freebsd.org (Postfix) with ESMTP id 4E91813C45A for ; Tue, 21 Aug 2007 04:50:52 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from localhost (168-215-61-194.static.twtelecom.net [168.215.61.194]) (authenticated bits=0) by mail.united-ware.com (8.13.8/8.13.8) with ESMTP id l7L5Su3U090398 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Aug 2007 01:29:04 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: David Malone Date: Tue, 21 Aug 2007 00:45:38 -0400 User-Agent: KMail/1.9.6 References: <200708191147.10340.amistry@am-productions.biz> <200708201121.37098.mistry.7@osu.edu> <20070820181821.GA74449@walton.maths.tcd.ie> In-Reply-To: <20070820181821.GA74449@walton.maths.tcd.ie> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1639514.s8AbbvRXnd"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200708210045.45732.mistry.7@osu.edu> X-Virus-Scanned: ClamAV 0.90.3/4014/Mon Aug 20 15:33:05 2007 on mail.united-ware.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: Can't create TCP connections to certain IP addresses X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 04:50:52 -0000 --nextPart1639514.s8AbbvRXnd Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 20 August 2007, you wrote: > On Mon, Aug 20, 2007 at 11:21:28AM -0400, Anish Mistry wrote: > > There doesn't seem to be checksum offloading on the sender ath0 > > sender: tcpdump -s0 -v > > http://am-productions.biz/debug/littleguy.tcpdump.txt > > > > Far end: tcpdump -s0 -v host 192.168.1.188 > > http://am-productions.biz/debug/bigguy.tcpdump.txt > > It looks like you might be generating packets with bad checksums > some times. There's an open PR about this, but it depends on what > CFLAGS you used to compile your kernel. Could you check and see > what flags you are using? > > David. What's the PR number? COPTFLAGS+=3D-O2 CPUTYPE=3Di586/mmx =2D-=20 Anish Mistry --nextPart1639514.s8AbbvRXnd Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBGym35xqA5ziudZT0RAptYAKC3LRqJ4r4kPHHY3z1tm5cSiVTTBQCcCIlV kcgnqBc6qnhHbON+ncGJJH4= =18/y -----END PGP SIGNATURE----- --nextPart1639514.s8AbbvRXnd-- From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 04:57:41 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0385D16A420; Tue, 21 Aug 2007 04:57:41 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id E7A0313C48D; Tue, 21 Aug 2007 04:57:40 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from rot26.obsecurity.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 57EDE1A3C1A; Mon, 20 Aug 2007 21:55:49 -0700 (PDT) Received: by rot26.obsecurity.org (Postfix, from userid 1001) id 3F93AC3EB; Tue, 21 Aug 2007 00:57:40 -0400 (EDT) Date: Tue, 21 Aug 2007 00:57:40 -0400 From: Kris Kennaway To: Kostik Belousov Message-ID: <20070821045739.GA83774@rot26.obsecurity.org> References: <200708202340.29678.qpadla@gmail.com> <20070820205201.GW2738@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070820205201.GW2738@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org, rwatson@freebsd.org Subject: Re: And probably the final crash for today's current :) (panic: filesystem goof: vop_panic[vop_print]) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 04:57:41 -0000 On Mon, Aug 20, 2007 at 11:52:01PM +0300, Kostik Belousov wrote: > Quite often, the "impossible" panics with vnode locking are happens > because some other thread already paniced the kernel. Then, lockmgr > passes all lock requests without actually locking. I would suggest > looking around to make sure this is not the case there. Is there a good reason to be doing that? Kris From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 07:32:47 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B5FC16A417 for ; Tue, 21 Aug 2007 07:32:47 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id A5B1613C457 for ; Tue, 21 Aug 2007 07:32:46 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (localhost [127.0.0.1]) by blah.sun-fish.com (Postfix) with ESMTP id EEB5E1B10EA4; Tue, 21 Aug 2007 09:32:44 +0200 (CEST) Received: from hater.cmotd.com (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id EB64B1B10E0D; Tue, 21 Aug 2007 09:32:44 +0200 (CEST) Message-ID: <46CA951D.1060303@moneybookers.com> Date: Tue, 21 Aug 2007 10:32:45 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.4pre (X11/20070711) MIME-Version: 1.0 To: Eric Kjeldergaard References: <46C9B99C.1060403@moneybookers.com> In-Reply-To: Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP on BLAH Cc: freebsd-current@freebsd.org Subject: Re: kernel panic with memory disks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 07:32:47 -0000 Hello, Eric Kjeldergaard wrote: > On 20/08/07, Stefan Lambrev wrote: > >> Hello, >> >> I do not know if this is know behavior, and I know that 6.2 panic if the >> memory disk got full, >> but on 7-current the panic is before the disk got full. >> >> Here is what I do: >> >> mdconfig -a -t malloc -s 800m >> newfs /dev/md0 >> mount /dev/md0 /mnt >> cp 600mb.file /mnt >> > > -t type > Select the type of the memory disk. > > malloc Storage for this type of memory disk is allocated with > malloc(9). This limits the size to the malloc bucket > limit in the kernel. If the -o reserve option is not > set, creating and filling a large malloc-backed memory > disk is a very easy way to panic a system. > -- mdconfig(8) > > I really should read manuals more carefully :) Thanks for the information. Just one more question - to prevent panic I should use "-o reserve" and have to increase: vfs.maxmallocbufspace vfs.bufmallocspace -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 07:45:17 2007 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 68C8616A417; Tue, 21 Aug 2007 07:45:17 +0000 (UTC) (envelope-from mpp@freebsd.org) Received: from mail4.gulftel.com (mail4.gulftel.com [216.231.163.45]) by mx1.freebsd.org (Postfix) with ESMTP id 40AA813C45D; Tue, 21 Aug 2007 07:45:17 +0000 (UTC) (envelope-from mpp@freebsd.org) Received: from localhost (localhost [127.0.0.1]) by mail4.gulftel.com (Postfix) with ESMTP id 0CB05DADB; Tue, 21 Aug 2007 01:31:11 -0500 (CDT) X-Virus-Scanned: amavisd-new at gulftel.com Received: from mail4.gulftel.com ([127.0.0.1]) by localhost (mail4.gulftel.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qW6OdIEhEpYC; Tue, 21 Aug 2007 01:31:10 -0500 (CDT) Received: from mail.mppsystems.com (unknown [10.17.6.142]) by mail4.gulftel.com (Postfix) with ESMTP id D9470DABF; Tue, 21 Aug 2007 01:31:09 -0500 (CDT) Received: by mail.mppsystems.com (Postfix, from userid 1000) id AAEF111515; Tue, 21 Aug 2007 01:31:08 -0500 (CDT) Date: Tue, 21 Aug 2007 01:31:08 -0500 From: Mike Pritchard To: Diomidis Spinellis Message-ID: <20070821063108.GA36879@freebsd.org> References: <20070819214953.I1099@fledge.watson.org> <46C8C2E6.9030405@aueb.gr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46C8C2E6.9030405@aueb.gr> User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: attilio@FreeBSD.ORG, jeff@FreeBSD.ORG, Robert Watson , current@FreeBSD.ORG Subject: Re: Crash in accounting code: encode_long(), due to bad rusage data?y X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 07:45:17 -0000 On Mon, Aug 20, 2007 at 01:23:34AM +0300, Diomidis Spinellis wrote: > Robert Watson wrote: > >I recently upgraded two servers from FreeBSD 6-STABLE to FreeBSD 7-CURRENT in > >anticipation of the forthcoming release. Both of them run with accounting > >enabled at all times. When a large pine session was exiting on one of the two > >boxes, I ran into the following panic: > >panic: encode_long: -ve value -32749 > > Getting rid of the panic is easy: > > --- kern_acct.c 2007-08-20 01:15:18.000000000 +0300 > +++ kern_acct.c.new 2007-08-20 01:16:06.000000000 +0300 > @@ -523,8 +523,7 @@ > int norm_exp; /* Normalized exponent */ > int shift; > > - KASSERT(val >= 0, ("encode_long: -ve value %ld", val)); > - if (val == 0) > + if (val <= 0) > return (0); > norm_exp = fls(val) - 1; > shift = FLT_MANT_DIG - norm_exp - 1; > > However, as you wrote, this doesn't fix the root of the problem. > > >I find the large negative value in ru_idrss somewhat sad to contemplate, and > >while this could well be a problem with capturing of process runtime > >information, I'd like it if the accounting code were robust against this sort > >of bug, rather than panicking, and I guess I'd also rather than the process > >runtime information also be correctly captured :-). Thats the exact same fix I applied to my system to work around this panic. I started seeing it over a month ago (but that system had been running a 4 or 5 month old kernel until then). But have just been to busy to look into it more than preventing the panic. I always see it from a perl proc spawned by procmail/spamassin. I think something in that code path is buggy, because a process that is only around for 2 mins tops shouldn't be able to generate this panic. I think a KASSERT around the integral update for idrss might be in order (I think thats the value that looked like it was overflowing... Sorry, its been a a month since I looked at this) (rest of this is off topic, sorry...but been thinking about mothballing that computer, but its been so good to me...) I'm guessing less and less of us are running 32bit uniprocessor machines. The machine I see it on is my server, which is a 9 year old K6-2-550 machine. Its a workhorse. lost 2 cpu fans (maybe 3) and 1 Hd and it is still kicking! I want to replace it, but its been been so good to me. Its best track record: (shut it down due to a power outage that my UPS couldn't ride out...power was out for 3 days it turns out) 4:14PM up 505 days, 12:01, 2 users, load averages: 38.23, 19.59, 12.24 -- Mike Pritchard mpp @ FreeBSD.org "If tyranny and oppression come to this land, it will be in the guise of fighting a foreign enemy." - James Madison (1787) From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 08:28:44 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AAD3F16A417 for ; Tue, 21 Aug 2007 08:28:44 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [IPv6:2001:770:10:300::86e2:510b]) by mx1.freebsd.org (Postfix) with SMTP id 07D2C13C474 for ; Tue, 21 Aug 2007 08:28:43 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 21 Aug 2007 09:28:42 +0100 (BST) Received: from localhost ([127.0.0.1] helo=maths.tcd.ie) by walton.maths.tcd.ie with SMTP id ; 21 Aug 2007 09:28:38 +0100 (BST) To: Anish Mistry In-reply-to: Your message of "Tue, 21 Aug 2007 00:45:38 EDT." <200708210045.45732.mistry.7@osu.edu> X-Request-Do: Date: Tue, 21 Aug 2007 09:28:38 +0100 From: David Malone Message-ID: <200708210928.aa80674@walton.maths.tcd.ie> Cc: freebsd-current@freebsd.org Subject: Re: Can't create TCP connections to certain IP addresses X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 08:28:44 -0000 > What's the PR number? The PR that I am thinking of is: http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/69257 > COPTFLAGS+=-O2 > CPUTYPE=i586/mmx I guess you may not be directly be effected, as you're using -O2, but it might be another interaction with gcc, so I'd try compiling a kernel with -O, just to see if you get a different result. (Record the output of building the kernel, just to make sure it is using the flags you think it is.) David. From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 09:25:55 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB31816A41A for ; Tue, 21 Aug 2007 09:25:55 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.228]) by mx1.freebsd.org (Postfix) with ESMTP id 3A52813C45A for ; Tue, 21 Aug 2007 09:25:55 +0000 (UTC) (envelope-from grafan@gmail.com) Received: by wr-out-0506.google.com with SMTP id 70so1081372wra for ; Tue, 21 Aug 2007 02:25:54 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=dqQNXrqNHrehqTLluaFQE2wUuZJE+s2ruQIBDOrR5lMbRASiAi9NBGeINIVhNwnLMo/NbRzhLcGnmr9nUBrNtMvFASaR76mC64mmaPepr0e3yPDzJxcJRFbPHFG8TjJSfeeBI/XTrws70UhVtHMamPGs1p4qwb78oem3mhuYqbI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=V5+TEBbdMSihlVhenJ36BV3yvQtB/42fBVVrHw/Yk3e2tEWG/txBW5M78FV/46pKvXPNkzlD2Szl3pe18IxsU/lZM2w6yNg90F1k/LadwW2ICqTTMG3aXkPipME9LGEIz0maLVSPcFfRPrqzhBHJ88rW+qNS/kvMZHRfwJHQaRk= Received: by 10.90.102.20 with SMTP id z20mr1470819agb.1187688353855; Tue, 21 Aug 2007 02:25:53 -0700 (PDT) Received: by 10.64.185.10 with HTTP; Tue, 21 Aug 2007 02:25:53 -0700 (PDT) Message-ID: <6eb82e0708210225n361dfc12pd9e6239b4e557f66@mail.gmail.com> Date: Tue, 21 Aug 2007 17:25:53 +0800 From: "Rong-en Fan" To: qpadla@gmail.com In-Reply-To: <200708201956.40383.qpadla@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200708201848.22157.qpadla@gmail.com> <20070820162311.GT2738@deviant.kiev.zoral.com.ua> <200708201956.40383.qpadla@gmail.com> Cc: Kostik Belousov , freebsd-current@freebsd.org, Xin LI Subject: Re: Panic on todays current (panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/kern/vfs_mount.c:1046) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 09:25:55 -0000 On 8/21/07, Nikolay Pavlov wrote: > On Monday 20 August 2007 19:23:11 Kostik Belousov wrote: > > The line where the reported panic happens is located at the point where > > several successfull locks of the mount structure interlock alread happen > > (see, for instance, line 983). In between, there is a call to > > VFS_MOUNT() method of the fs. > > > > It would be interesting to look at the type of the filesystem being > > mounted. > > This line from the fstab is a trigger for this panic: > > tmpfs /tmp tmpfs rw,mode=777 0 0 Looks like a tmpfs issue? delphij@ is CC'ed. BTW, tmpfs will automatically inherit mount point's permission settings. I'm using tmpfs from fstab without problem. Regards, Rong-En Fan > > > > > Just a guess: > > Could it be that mounted filesystem comes from module, that uses > > incompatible binary interface (for instance, built with different kernel > > options or for different kernel version) ? > > No. The kernel is GENERIC. The command was a plain "make buildkernel -j3" > and i don't have any special build arguments nither in src.conf nor > make.conf. > > -- > > * Best regards, Nikolay Pavlov * > > > From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 09:43:29 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9334D16A417 for ; Tue, 21 Aug 2007 09:43:29 +0000 (UTC) (envelope-from remy.nonnenmacher@activnetworks.com) Received: from mallaury.nerim.net (mallaury.ipv6.nerim.net [IPv6:2001:7a8:1:5::82]) by mx1.freebsd.org (Postfix) with ESMTP id 1601F13C459 for ; Tue, 21 Aug 2007 09:43:29 +0000 (UTC) (envelope-from remy.nonnenmacher@activnetworks.com) Received: from rn.activnetworks.com (anwadmin.net8.nerim.net [213.41.185.85]) by mallaury.nerim.net (Postfix) with ESMTP id 625474F3EC; Tue, 21 Aug 2007 11:43:21 +0200 (CEST) Message-ID: <46CAB40B.6030605@activnetworks.com> Date: Tue, 21 Aug 2007 11:44:43 +0200 From: Remy Nonnenmacher User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.4) Gecko/20070709 SeaMonkey/1.1.2 MIME-Version: 1.0 To: Lawrence Farr References: <46C9B99C.1060403@moneybookers.com> <012501c7e348$288c6af0$79a540d0$@co.uk> In-Reply-To: <012501c7e348$288c6af0$79a540d0$@co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Solid hang with bge interface X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 09:43:29 -0000 Lawrence Farr wrote: > I have a Supermicro H8DAR-T based server, that was happily > running 6-stable from last year sometime. I swapped it out and > have been trying to get -CURRENT installed on it but it hangs > solid as soon as you configure the bge0 interface. The bge1 > interface will work occasionally tho. To try and rule out a > hardware fault I booted an AMD64-6.0RC1 cd that I had, which > had no problems at all with the interface: > > http://www.epcdirect.com/bootlog/6boot.txt > > But the current snapshot from June, and from todays source > hangs solid as soon as you try to set up the bge0 interface. > > http://www.epcdirect.com/bootlog/currentboot.txt > > As you can see, it hangs solid at "Setting hostname". > > I've also removed the 3ware card "just in case" but it made > no difference. Latest BIOS too. I found some references to > a similar problem with bge recently too: > > http://lists.freebsd.org/pipermail/freebsd-current/2007-August/075998.html > > > Anyone else seeing this? > Same here with a Supermicro H8SSL-I2 (Serverworks HT1000 based). bge0 locks the system hard when going up, bge1 OK (but goes down a few hours after start). Also, an ifconfig indicates: bge0: flags=8802 metric 0 mtu 1500 options=9b ether 00:30:48:5e:6e:56 media: Ethernet autoselect (none ) ^^^^^^^^^^^^^^^^^^ status: no carrier bge1: flags=8843 metric 0 mtu 1500 options=9b ether 00:30:48:5e:6e:57 inet 192.168.1.49 netmask 0xffffff00 broadcast 192.168.1.255 media: Ethernet autoselect (1000baseTX ) status: active An the dmesg shows: (see "^^^^..") . . bge0: mem 0xff4f0000-0xff4fffff irq 24 at device 3.0 on pci2 miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge0: Ethernet address: 00:30:48:5e:6e:56 bge0: [ITHREAD] pci2:3:1: bad VPD cksum, remain 14 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ bge1: mem 0xff4e0000-0xff4effff irq 25 at device 3.1 on pci2 miibus1: on bge1 brgphy1: PHY 1 on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge1: Ethernet address: 00:30:48:5e:6e:57 bge1: [ITHREAD] . . (I also have strange problems with the SATA controller and recent kernels (that works fine on other machines) that seems to read random sectors (at least not those requested) causing core-dumps, compiler internal errors, trashed sources and false positives about corrupted filesystems.I don't know what is going on on this platform but it smells^Gdoesn't looks very sane.) RN. IeM From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 11:35:12 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8651E16A419; Tue, 21 Aug 2007 11:35:12 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay02.kiev.sovam.com (relay02.kiev.sovam.com [62.64.120.197]) by mx1.freebsd.org (Postfix) with ESMTP id 30A7113C46A; Tue, 21 Aug 2007 11:35:12 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from [212.82.216.226] (helo=deviant.kiev.zoral.com.ua) by relay02.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1INS0q-00047u-OC; Tue, 21 Aug 2007 14:35:11 +0300 Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.1/8.14.1) with ESMTP id l7LBZ5k7036031; Tue, 21 Aug 2007 14:35:05 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.1/8.14.1/Submit) id l7LBZ4nH036030; Tue, 21 Aug 2007 14:35:04 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 21 Aug 2007 14:35:04 +0300 From: Kostik Belousov To: Kris Kennaway Message-ID: <20070821113504.GA2738@deviant.kiev.zoral.com.ua> References: <200708202340.29678.qpadla@gmail.com> <20070820205201.GW2738@deviant.kiev.zoral.com.ua> <20070821045739.GA83774@rot26.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZkFfH+RuFRkNoGBj" Content-Disposition: inline In-Reply-To: <20070821045739.GA83774@rot26.obsecurity.org> User-Agent: Mutt/1.4.2.3i X-Scanner-Signature: 7ffaa6bc246e67c9b1a22e0c753f4a43 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 1391 [August 20 2007] X-SpamTest-Info: helo_type=3 X-SpamTest-Info: {received from trusted relay: not dialup} X-SpamTest-Method: none X-SpamTest-Method: Local Lists X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release Cc: freebsd-current@freebsd.org, rwatson@freebsd.org Subject: Re: And probably the final crash for today's current :) (panic: filesystem goof: vop_panic[vop_print]) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 11:35:12 -0000 --ZkFfH+RuFRkNoGBj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 21, 2007 at 12:57:40AM -0400, Kris Kennaway wrote: > On Mon, Aug 20, 2007 at 11:52:01PM +0300, Kostik Belousov wrote: >=20 > > Quite often, the "impossible" panics with vnode locking are happens > > because some other thread already paniced the kernel. Then, lockmgr > > passes all lock requests without actually locking. I would suggest > > looking around to make sure this is not the case there. >=20 > Is there a good reason to be doing that? Hmm. This is revision 1.47 of sys/kern/kern_lock.c: date: 2001/08/10 23:29:15; author: jhb; state: Exp; lines: +6 -1 If we've panic'd already, then just bail in lockmgr rather than blocking or possibly panic'ing again. --ZkFfH+RuFRkNoGBj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGys3oC3+MBN1Mb4gRArAqAJ9w/FQO+olZbKzDCAXJqcksJWglpgCcCyHd GpmncZJbSn6bNciIUBrK5LU= =oExS -----END PGP SIGNATURE----- --ZkFfH+RuFRkNoGBj-- From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 14:25:03 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3313C16A46E for ; Tue, 21 Aug 2007 14:25:03 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.191]) by mx1.freebsd.org (Postfix) with ESMTP id EAFDE13C4B3 for ; Tue, 21 Aug 2007 14:25:02 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so1175810rvb for ; Tue, 21 Aug 2007 07:25:02 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=Y5fOdSzXroOnzkMzciZtwT+l3Vht03MYIAw2/ELR7HedelmMBxAH2a6nhKDwFmE59pO+Z3zeh5tx7t6xFt6EvbbM9m46IX5lBjKWbGdy3MJBzGxkCVEXlhzlezamlnqUmQa9sGDsDyZ+8pr6eBB8+xm/Pf5dskNyIW94cIBz+Gw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=oCtVWlFMYP658ZPe6s5mHSMJOE97aOQfeIucqhDuPyHZliyNdLnXb135CToOystSfbtuZYVYdyr7eW0LxDm4FQ+H0GN2dMzw9o0lncEmfFHaYR5jg8ImDzdIvgkwx0O+KWSCSYUfhGZSFPyijAzaKMJMAU+mWj8Ydlxd5kr5d3A= Received: by 10.115.54.1 with SMTP id g1mr4094809wak.1187706302174; Tue, 21 Aug 2007 07:25:02 -0700 (PDT) Received: by 10.115.77.13 with HTTP; Tue, 21 Aug 2007 07:25:02 -0700 (PDT) Message-ID: <4956a5e50708210725k76925c45l46410719029d6dd4@mail.gmail.com> Date: Tue, 21 Aug 2007 11:25:02 -0300 From: Nenhum_de_Nos To: "Kip Macy" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4956a5e50708201723l623cf384ub10edd3ceea88e62@mail.gmail.com> <4956a5e50708201931t5e55d1d3lb329ed53b0edb356@mail.gmail.com> X-Mailman-Approved-At: Tue, 21 Aug 2007 14:32:10 +0000 Cc: freebsd-current@freebsd.org Subject: Re: error building yesterday code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 14:25:03 -0000 On 8/21/07, Kip Macy wrote: > Sounds like bad memory. Try memtest. > -Kip > > > On 8/20/07, Nenhum_de_Nos wrote: > > c++ -I/usr/src/gnu/lib/libstdc++/../../../contrib/gcc > > -I/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include > > -I/usr/src/gnu/lib/libstdc++/../../../contrib/gcclibs/include > > -I/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include -I. > > -frandom-seed=RepeatabilityConsideredGood -fno-implicit-templates > > -ffunction-sections -fdata-sections -Wno-deprecated -c > > /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/fstream-inst.cc > > /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/fstream-inst.cc: > > In member function 'void std::basic_ifstream<_CharT, > > _Traits>::open(const char*, std::_Ios_Openmode) [with _CharT = > > wchar_t, _Traits = std::char_traits]': > > /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/fstream-inst.cc:50: > > internal compiler error: Segmentation fault: 11 > > Please submit a full bug report, > > with preprocessed source if appropriate. > > See for instructions. > > *** Error code 1 > > > > Stop in /usr/src/gnu/lib/libstdc++. > > *** Error code 1 > > > > Stop in /usr/src/gnu/lib. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > [root@xxx /usr/src]# > > > > today's sources are no better :( > > > > matheus memtest is 91% ano bad nothing ... at night I can make further tests, but so far I'm not blaming the memory any other ideas ? all I thought was a reinstall ... a fresh -current ... thanks matheus -- We will call you cygnus, The God of balance you shall be From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 14:26:14 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7DB916A468 for ; Tue, 21 Aug 2007 14:26:14 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6D40113C48E for ; Tue, 21 Aug 2007 14:26:14 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so2718570pyb for ; Tue, 21 Aug 2007 07:26:12 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=RhNeTN9e+FnHwY1PNr3Hd+xXW2Ia5pdnWbKDicZTQFWUcFA8Fh70Ejv0jhBemO+p5TZM0qwt3GIgTp94RodILpvple8mLTucxe0HDde06xHjYjwmY43YVUa5S6Htfh2F16btxr4FwkiMp2NcCGiPg0q9+j3RjUSFNnGtoD/NW+o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=e8/JftvWJX5C0jYzuHaWy1q8Q42cYk1pq6ImUXlIq1vlGa7a6Th4crNX1U6ZShjTZJilIOUNYxGWBVx4xfD9FWOoqTF5wF2AKxud4Z4COvQPydgzN3Ulr9lsBX97rWCOPnk1NDOo/DhOK6iJoVowF96i3iIIKUqbRtTryKBrSuA= Received: by 10.114.73.1 with SMTP id v1mr725385waa.1187706371557; Tue, 21 Aug 2007 07:26:11 -0700 (PDT) Received: by 10.115.77.13 with HTTP; Tue, 21 Aug 2007 07:26:11 -0700 (PDT) Message-ID: <4956a5e50708210726q71596cb0l74be9d8801996a3d@mail.gmail.com> Date: Tue, 21 Aug 2007 11:26:11 -0300 From: Nenhum_de_Nos To: "Kip Macy" In-Reply-To: <4956a5e50708210725k76925c45l46410719029d6dd4@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4956a5e50708201723l623cf384ub10edd3ceea88e62@mail.gmail.com> <4956a5e50708201931t5e55d1d3lb329ed53b0edb356@mail.gmail.com> <4956a5e50708210725k76925c45l46410719029d6dd4@mail.gmail.com> X-Mailman-Approved-At: Tue, 21 Aug 2007 14:32:10 +0000 Cc: freebsd-current@freebsd.org Subject: Re: error building yesterday code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 14:26:14 -0000 > memtest is 91% ano bad nothing ... and no bad nothing ... (just made a complete loop and again all fine) matheus > at night I can make further tests, but so far I'm not blaming the memory > > any other ideas ? > > all I thought was a reinstall ... a fresh -current ... > > thanks > > matheus > > -- > We will call you cygnus, > The God of balance you shall be > -- We will call you cygnus, The God of balance you shall be From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 14:43:14 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB48E16A420 for ; Tue, 21 Aug 2007 14:43:13 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay02.kiev.sovam.com (relay02.kiev.sovam.com [62.64.120.197]) by mx1.freebsd.org (Postfix) with ESMTP id 7088213C478 for ; Tue, 21 Aug 2007 14:43:13 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from [212.82.216.226] (helo=deviant.kiev.zoral.com.ua) by relay02.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1INUwn-000IFX-LU; Tue, 21 Aug 2007 17:43:12 +0300 Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.1/8.14.1) with ESMTP id l7LEh4nn038544; Tue, 21 Aug 2007 17:43:04 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.1/8.14.1/Submit) id l7LEh3RU038543; Tue, 21 Aug 2007 17:43:03 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 21 Aug 2007 17:43:03 +0300 From: Kostik Belousov To: Peter Jeremy Message-ID: <20070821144303.GD2738@deviant.kiev.zoral.com.ua> References: <20070817073321.GA6321@turion.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0IfLThn+1cz+gOna" Content-Disposition: inline In-Reply-To: <20070817073321.GA6321@turion.vk2pj.dyndns.org> User-Agent: Mutt/1.4.2.3i X-Scanner-Signature: 21f1cdc77deae757bfd40713fd6c3781 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 1394 [August 21 2007] X-SpamTest-Info: helo_type=3 X-SpamTest-Info: {received from trusted relay: not dialup} X-SpamTest-Method: none X-SpamTest-Method: Local Lists X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release Cc: freebsd-current@freebsd.org, tegge@freebsd.org Subject: insmntque for syncvnode panic [Was: Re: panic unmounting filesystems] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 14:43:14 -0000 --0IfLThn+1cz+gOna Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 17, 2007 at 05:33:21PM +1000, Peter Jeremy wrote: > After upgrading to current as of about 24 hours ago, I now consistently > get panics when I try to unmount filesystems with pending I/O. If I > just mount and unmount a filesystem, it works but if I try to unmount > a filesystem that has been active, I get: >=20 > handle_workitem_remove: vget: got error 16 while accessing filesystem > softdep_waitidle: Failed to flush worklist for 0xc2c6429c I think that this errors are supposed to happen on busy fs. > panic: vfs_allocate_syncvnode: insmntque failed This one is the real problem. >=20 > I have a crashdump and the backtrace looks like: > #8 0xc055c545 in panic (fmt=3D0xc07309f1 "vfs_allocate_syncvnode: insmnt= que failed") > at /usr/src/sys/kern/kern_shutdown.c:547 > #9 0xc05d6b9a in vfs_allocate_syncvnode (mp=3D0xc2c6429c) at /usr/src/sy= s/kern/vfs_subr.c:3111 > #10 0xc05d1222 in dounmount (mp=3D0xc2c6429c, flags=3D0x8000000, td=3D0xc= 2d9c600) at /usr/src/sys/kern/vfs_mount.c:1289 > #11 0xc05d16ff in unmount (td=3D0xc2d9c600, uap=3D0xd6218cfc) at /usr/src= /sys/kern/vfs_mount.c:1170 > #12 0xc06de9ea in syscall (frame=3D0xd6218d38) at /usr/src/sys/i386/i386/= trap.c:1008 > #13 0xc06cc5c0 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception= .s:196 >=20 > According to kgdb, insmntque() returned both EXDEV and EBUSY. The former > is impossible so I suspect kgdb is confused and the latter is correct. >=20 > The mountpoint shows as in the process of being unmounted and has > mnt_nvnodelistsize =3D=3D 0 so insmntque() makes sense at the micro level. > Having a system panic as a result does not make sense. Sure. I think that syncvnode shall be allocated after the MNTK_UNMOUNT flag is cleared. Could you, please, test the patch below ? >=20 > The softdep_waitidle() error looks suspicious - at a quick glance, it > appears to only wait for 10 ticks (10msec) for the dependency chain to > empty. This seems unreasonably short for an operation that probably > includes physical I/O. Is my reasoning correct? >=20 > Does anyone have any suggestions on where to look next? >=20 diff --git a/sys/kern/vfs_mount.c b/sys/kern/vfs_mount.c index 702efc3..09f4d1e 100644 --- a/sys/kern/vfs_mount.c +++ b/sys/kern/vfs_mount.c @@ -1285,14 +1285,16 @@ dounmount(mp, flags, td) } vput(fsrootvp); } - if ((mp->mnt_flag & MNT_RDONLY) =3D=3D 0 && mp->mnt_syncer =3D=3D NULL) - (void) vfs_allocate_syncvnode(mp); MNT_ILOCK(mp); mp->mnt_kern_flag &=3D ~(MNTK_UNMOUNT | MNTK_UNMOUNTF); mp->mnt_flag |=3D async_flag; if ((mp->mnt_flag & MNT_ASYNC) !=3D 0 && mp->mnt_noasync =3D=3D 0) mp->mnt_kern_flag |=3D MNTK_ASYNC; + MNT_IUNLOCK(mp); + if ((mp->mnt_flag & MNT_RDONLY) =3D=3D 0 && mp->mnt_syncer =3D=3D NULL) + (void) vfs_allocate_syncvnode(mp); lockmgr(&mp->mnt_lock, LK_RELEASE, NULL, td); + MNT_ILOCK(mp); if (mp->mnt_kern_flag & MNTK_MWAIT) wakeup(mp); MNT_IUNLOCK(mp); --0IfLThn+1cz+gOna Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGyvn2C3+MBN1Mb4gRApm0AKDOJc8LZMCJ91aHYj8LB6uf3XVjUgCeP0AD VaeIyVZaEWrraDXskGguDtE= =BWF7 -----END PGP SIGNATURE----- --0IfLThn+1cz+gOna-- From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 14:54:50 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9CF8716A418 for ; Tue, 21 Aug 2007 14:54:50 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: from akis.salford.ac.uk (akis.salford.ac.uk [146.87.0.14]) by mx1.freebsd.org (Postfix) with SMTP id F162F13C465 for ; Tue, 21 Aug 2007 14:54:49 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 37956 invoked by uid 98); 21 Aug 2007 15:54:48 +0100 Received: from 146.87.255.121 by akis.salford.ac.uk (envelope-from , uid 401) with qmail-scanner-2.01 (clamdscan: 0.90/3843. spamassassin: 3.1.8. Clear:RC:1(146.87.255.121):. Processed in 0.060732 secs); 21 Aug 2007 14:54:48 -0000 Received: from rust.salford.ac.uk (HELO rust.salford.ac.uk) (146.87.255.121) by akis.salford.ac.uk (qpsmtpd/0.3x.614) with SMTP; Tue, 21 Aug 2007 15:54:48 +0100 Received: (qmail 4772 invoked by uid 1002); 21 Aug 2007 14:54:45 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 21 Aug 2007 14:54:45 -0000 Date: Tue, 21 Aug 2007 15:54:45 +0100 (BST) From: "Mark Powell" To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= In-Reply-To: <20070820191558.I96699@rust.salford.ac.uk> Message-ID: <20070821155215.P4273@rust.salford.ac.uk> References: <20070818163810.I75076@rust.salford.ac.uk> <20070820112023.93648.qmail@rust.salford.ac.uk> <20070820124808.GM72415@cicely12.cicely.de> <20070820135021.W93439@rust.salford.ac.uk> <20070820142224.D94437@rust.salford.ac.uk> <46C99B46.3000605@deepcore.dk> <20070820191558.I96699@rust.salford.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@FreeBSD.ORG, ticso@cicely.de, sos@FreeBSD.ORG Subject: Re: MCP55 SATA problems (was Re: PATA-SATA convertor drive inaccessibility) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 14:54:50 -0000 On Mon, 20 Aug 2007, Mark Powell wrote: > But doesn't the fact that everything works fine on the same hardware on 6.2, > seem to suggest that something got changed in 7 that has broken this? Moved the 3 PATA drive array back to my old Athlon XP board with an Sil3112 on board. I connected 2 of the drives via SATA dongles to the the 2 SATA ports and the 3rd via IDE. Works perfectly with same 7.0 that can't detect dongled drives on MCP55. Cheers. -- Mark Powell - UNIX System Administrator - The University of Salford Information Services Division, Clifford Whitworth Building, Salford University, Manchester, M5 4WT, UK. Tel: +44 161 295 4837 Fax: +44 161 295 5888 www.pgp.com for PGP key From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 15:20:30 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4CF516A469 for ; Tue, 21 Aug 2007 15:20:30 +0000 (UTC) (envelope-from dashmoho@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.234]) by mx1.freebsd.org (Postfix) with ESMTP id 9E64D13C4B6 for ; Tue, 21 Aug 2007 15:20:30 +0000 (UTC) (envelope-from dashmoho@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so567008nzf for ; Tue, 21 Aug 2007 08:20:30 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=AFXvw51nBvK7rg45FWlfb71PI4v9B6njp4slXZqOx3nWg709yNGHs1a73PNR/ElqnWhIe9xCC9NtG4/QJyvSQswidoyQ3A2tmxdCe0TrJrpR3ja9sXcf0wXvoad4ekYqbUM1C/dpDjZ/nrx/xdzdtu28Du3pcmdX+Le1CKRljt8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=GLozPFoULMHPEUrq90FFbHIfIf0n479bmfSL0FPZomO3WOZBIyCG3L8Ud35yTJiPus1IcFugOD7fMYb/YMT9bARH1932iUQ1T2AC7liRDcEDcQVV9F8uJGFfAAVrshbKM+oJ5+woBVieIMGBsiJ9Zj1Fc0hnQWRBmlhQA74GAtA= Received: by 10.143.1.2 with SMTP id d2mr851694wfi.1187708083341; Tue, 21 Aug 2007 07:54:43 -0700 (PDT) Received: by 10.65.132.15 with HTTP; Tue, 21 Aug 2007 07:54:43 -0700 (PDT) Message-ID: <2dcd50ec0708210754u24445cb6m5f9164fa9eeae6d0@mail.gmail.com> Date: Tue, 21 Aug 2007 16:54:43 +0200 From: "Daniel Horecki" Sender: dashmoho@gmail.com To: Nenhum_de_Nos In-Reply-To: <4956a5e50708210726q71596cb0l74be9d8801996a3d@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4956a5e50708201723l623cf384ub10edd3ceea88e62@mail.gmail.com> <4956a5e50708201931t5e55d1d3lb329ed53b0edb356@mail.gmail.com> <4956a5e50708210725k76925c45l46410719029d6dd4@mail.gmail.com> <4956a5e50708210726q71596cb0l74be9d8801996a3d@mail.gmail.com> X-Google-Sender-Auth: d53d256304e73a20 Cc: Kip Macy , freebsd-current@freebsd.org Subject: Re: error building yesterday code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 15:20:31 -0000 2007/8/21, Nenhum_de_Nos : > > memtest is 91% ano bad nothing ... > > and no bad nothing ... (just made a complete loop and again all fine) > > > matheus > > > at night I can make further tests, but so far I'm not blaming the memory > > > > any other ideas ? > > Overheating CPU? Failing disk? It _rather_ problem with hardware. -- Daniel 'Shinden' Horecki http://morr.pl From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 16:08:19 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B35C16A417 for ; Tue, 21 Aug 2007 16:08:19 +0000 (UTC) (envelope-from remy.nonnenmacher@activnetworks.com) Received: from mallaury.nerim.net (mallaury.ipv6.nerim.net [IPv6:2001:7a8:1:5::82]) by mx1.freebsd.org (Postfix) with ESMTP id 07C3813C45B for ; Tue, 21 Aug 2007 16:08:19 +0000 (UTC) (envelope-from remy.nonnenmacher@activnetworks.com) Received: from rn.activnetworks.com (anwadmin.net8.nerim.net [213.41.185.85]) by mallaury.nerim.net (Postfix) with ESMTP id 3CB944F432; Tue, 21 Aug 2007 18:08:05 +0200 (CEST) Message-ID: <46CB0E3C.8040503@activnetworks.com> Date: Tue, 21 Aug 2007 18:09:32 +0200 From: Remy Nonnenmacher User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.4) Gecko/20070709 SeaMonkey/1.1.2 MIME-Version: 1.0 To: Daniel Horecki References: <4956a5e50708201723l623cf384ub10edd3ceea88e62@mail.gmail.com> <4956a5e50708201931t5e55d1d3lb329ed53b0edb356@mail.gmail.com> <4956a5e50708210725k76925c45l46410719029d6dd4@mail.gmail.com> <4956a5e50708210726q71596cb0l74be9d8801996a3d@mail.gmail.com> <2dcd50ec0708210754u24445cb6m5f9164fa9eeae6d0@mail.gmail.com> In-Reply-To: <2dcd50ec0708210754u24445cb6m5f9164fa9eeae6d0@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Kip Macy , freebsd-current@freebsd.org, Nenhum_de_Nos Subject: Re: error building yesterday code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 16:08:19 -0000 Daniel Horecki wrote: > 2007/8/21, Nenhum_de_Nos : >>> memtest is 91% ano bad nothing ... >> and no bad nothing ... (just made a complete loop and again all fine) >> >> >> matheus >> >>> at night I can make further tests, but so far I'm not blaming the memory >>> >>> any other ideas ? >>> > > Overheating CPU? Failing disk? It _rather_ problem with hardware. > If you have disabled WITNESS and INVARIANTS for performance, you may want to try with a standard GENERIC file (with those options). I have had 'unexplained mysteries' recently without flags and got back to normal with. RN. ItM From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 15:52:53 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F283916A41A for ; Tue, 21 Aug 2007 15:52:53 +0000 (UTC) (envelope-from jaharkes@cs.cmu.edu) Received: from delft.aura.cs.cmu.edu (unknown [IPv6:2002:8002:ce58::1]) by mx1.freebsd.org (Postfix) with ESMTP id ABC7F13C45A for ; Tue, 21 Aug 2007 15:52:53 +0000 (UTC) (envelope-from jaharkes@cs.cmu.edu) Received: from jaharkes by delft.aura.cs.cmu.edu with local (Exim 4.67) (envelope-from ) id 1INW2E-0001Ql-VB for freebsd-current@freebsd.org; Tue, 21 Aug 2007 11:52:50 -0400 Date: Tue, 21 Aug 2007 11:52:50 -0400 From: Jan Harkes To: freebsd-current@freebsd.org Message-ID: <20070821155250.GA30679@cs.cmu.edu> Mail-Followup-To: freebsd-current@freebsd.org References: <200708202340.29678.qpadla@gmail.com> <20070820205201.GW2738@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070820205201.GW2738@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.5.16 (2007-06-11) X-Mailman-Approved-At: Tue, 21 Aug 2007 16:23:03 +0000 Subject: Re: And probably the final crash for today's current :) (panic: filesystem goof: vop_panic[vop_print]) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 15:52:54 -0000 On Mon, Aug 20, 2007 at 11:52:01PM +0300, Kostik Belousov wrote: > On Mon, Aug 20, 2007 at 11:40:29PM +0300, Nikolay Pavlov wrote: > > I am testing latest coda client code. > > After simple ls -l /coda i am getting this panic: > > > > vfs_badlock(c4448c80,e69729c0,c0b7efc0,c821ac3c,0) at vfs_badlock+0x23 > > assert_vop_locked(c821ac3c,c0acdaac,810,0,c65aca00,...) at > > assert_vop_locked+0x50 > > VOP_OPEN_APV(c4448c80,e6972a18,1,c483a500,c4867ab0,...) at > > VOP_OPEN_APV+0x8a > > coda_open(e6972a8c,c0acdaac,c4864c00,0,e6972b80,...) at coda_open+0x11e ... > Quite often, the "impossible" panics with vnode locking are happens > because some other thread already paniced the kernel. Then, lockmgr > passes all lock requests without actually locking. I would suggest > looking around to make sure this is not the case there. I think this is a valid vnode locking panic. In the coda_open function (fs/coda/coda_vnops.c) we try to open the file which was handed down by the userspace cache manager. However the code only grabs a reference, there probably needs to be something extra around the VOP_OPEN to grab the lock I'm not totally up to speed on the FBSD locking, but I think the call to VOP_OPEN needs to be surrounded by vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, td); and ... VOP_UNLOCK(vp, 0, td); I'm resyncing my freebsd install with current to see if I can reproduce the panic and if this actually fixes it. Jan From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 15:59:46 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C55BB16A41A for ; Tue, 21 Aug 2007 15:59:46 +0000 (UTC) (envelope-from mattboll@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.freebsd.org (Postfix) with ESMTP id 5482613C480 for ; Tue, 21 Aug 2007 15:59:46 +0000 (UTC) (envelope-from mattboll@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so986823nfb for ; Tue, 21 Aug 2007 08:59:45 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=E9SKhFzITJ/CT/Yimf42e4h14HGooHl5ZwuTZcdVTCRcqvGKiW3KoaHISVbae8C3P5ma8a4A/EMIMYKkGaM+IddVWTv2Fnp5PFBtyFIsWQpa6waKr7JMae9fYnIIG58FvmBl1LJCjVqI8sKGtWmY6BGvhjFikgFYayfzIg0oMbw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=POVkHAAdW2BRdbPp6T2BbFW5xfcBnusUQ0bYlAcGaqyftitV0EuZGReHBxXeEcs+158rfoE/pjIrfwKRDYE1hI5D5PhdvGwiIcfnTHxwNFrCWKaU9KJADtRqATCBf/51gTIN8IqYF12wg1cDOVlOEZoXtyZ1GlhOKK97/2XTpXI= Received: by 10.86.70.8 with SMTP id s8mr5520844fga.1187710309868; Tue, 21 Aug 2007 08:31:49 -0700 (PDT) Received: from ?172.16.2.44? ( [81.56.151.195]) by mx.google.com with ESMTPS id 22sm12183007fkr.2007.08.21.08.31.48 (version=SSLv3 cipher=RC4-MD5); Tue, 21 Aug 2007 08:31:48 -0700 (PDT) From: Matthieu Bollot To: freebsd-current@freebsd.org In-Reply-To: <4956a5e50708210726q71596cb0l74be9d8801996a3d@mail.gmail.com> References: <4956a5e50708201723l623cf384ub10edd3ceea88e62@mail.gmail.com> <4956a5e50708201931t5e55d1d3lb329ed53b0edb356@mail.gmail.com> <4956a5e50708210725k76925c45l46410719029d6dd4@mail.gmail.com> <4956a5e50708210726q71596cb0l74be9d8801996a3d@mail.gmail.com> Content-Type: text/plain Date: Tue, 21 Aug 2007 17:32:37 +0200 Message-Id: <1187710357.1214.11.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.10.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 21 Aug 2007 16:23:03 +0000 Subject: Re: error building yesterday code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 15:59:46 -0000 Hi, sometimes the compilation options make problems (/etc/make.conf) (I had something like that with -O -pipe options) but bugreporting to gcc can be an other solution. On Tue, 2007-08-21 at 11:26 -0300, Nenhum_de_Nos wrote: > > memtest is 91% ano bad nothing ... > > and no bad nothing ... (just made a complete loop and again all fine) > > > matheus > > > at night I can make further tests, but so far I'm not blaming the memory > > > > any other ideas ? > > > > all I thought was a reinstall ... a fresh -current ... > > > > thanks > > > > matheus > > > > -- > > We will call you cygnus, > > The God of balance you shall be > > > > From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 16:37:31 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7391816A419 for ; Tue, 21 Aug 2007 16:37:31 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 6055A13C458 for ; Tue, 21 Aug 2007 16:37:31 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from rot26.obsecurity.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 9186E1A4D86; Tue, 21 Aug 2007 09:35:37 -0700 (PDT) Received: by rot26.obsecurity.org (Postfix, from userid 1001) id 6EF76BB78; Tue, 21 Aug 2007 12:37:30 -0400 (EDT) Date: Tue, 21 Aug 2007 12:37:30 -0400 From: Kris Kennaway To: Stefan Lambrev Message-ID: <20070821163729.GA91485@rot26.obsecurity.org> References: <46C9B99C.1060403@moneybookers.com> <46CA951D.1060303@moneybookers.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46CA951D.1060303@moneybookers.com> User-Agent: Mutt/1.4.2.3i Cc: Eric Kjeldergaard , freebsd-current@freebsd.org Subject: Re: kernel panic with memory disks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 16:37:31 -0000 On Tue, Aug 21, 2007 at 10:32:45AM +0300, Stefan Lambrev wrote: > Hello, > > Eric Kjeldergaard wrote: > >On 20/08/07, Stefan Lambrev wrote: > > > >>Hello, > >> > >>I do not know if this is know behavior, and I know that 6.2 panic if the > >>memory disk got full, > >>but on 7-current the panic is before the disk got full. > >> > >>Here is what I do: > >> > >>mdconfig -a -t malloc -s 800m > >>newfs /dev/md0 > >>mount /dev/md0 /mnt > >>cp 600mb.file /mnt > >> > > > > -t type > > Select the type of the memory disk. > > > > malloc Storage for this type of memory disk is allocated > > with > > malloc(9). This limits the size to the malloc bucket > > limit in the kernel. If the -o reserve option is not > > set, creating and filling a large malloc-backed > > memory > > disk is a very easy way to panic a system. > >-- mdconfig(8) > > > > > I really should read manuals more carefully :) Thanks for the information. > > Just one more question - to prevent panic I should use "-o reserve" and > have to increase: > vfs.maxmallocbufspace > vfs.bufmallocspace No, you should use -o swap. Where did it tell you to change the sysctls? Kris From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 16:49:16 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 030BE16A420 for ; Tue, 21 Aug 2007 16:49:16 +0000 (UTC) (envelope-from serguey-grigoriev@yandex.ru) Received: from webmail34.mail.yandex.net (webmail34.mail.yandex.net [213.180.223.183]) by mx1.freebsd.org (Postfix) with ESMTP id 7F59D13C442 for ; Tue, 21 Aug 2007 16:49:15 +0000 (UTC) (envelope-from serguey-grigoriev@yandex.ru) Received: from YAMAIL (webmail34) by mail.yandex.ru id S6467797AbXHUQtB for ; Tue, 21 Aug 2007 20:49:01 +0400 X-Yandex-Spam: 1 Received: from [91.122.49.58] ([91.122.49.58]) by mail.yandex.ru with HTTP; Tue, 21 Aug 2007 20:48:59 +0400 From: "S.N.Grigoriev" To: cb@severious.net In-Reply-To: 9070000000006146794 References: <786091187635818@webmail31.yandex.ru> 9070000000006146794 MIME-Version: 1.0 Message-Id: <124781187714940@webmail34.yandex.ru> Date: Tue, 21 Aug 2007 20:49:00 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailman-Approved-At: Tue, 21 Aug 2007 16:51:59 +0000 Cc: freebsd-current@freebsd.org Subject: Re: Cisco PIX/ASA VPN client X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 16:49:16 -0000 21.08.07, 00:00, Craig Boston (cb@severious.net) wrote: > On Mon, Aug 20, 2007 at 10:50:18PM +0400, S.N.Grigoriev wrote: > > I need to use my 7-CURRENT workstation as an IPSec client for > > Cisco PIX/ASA devices. I try to use /usr/ports/security/vpnc > > for this purpose. But when i start vpnc the following error > > message appears: > > > > socket(PF_INET, SOCK_RAW, IPPROTO_ESP): Protocol not supported > > Do you have options IPSEC in your kernel? I believe this may prevent > vpnc from sending/receiving the encapsulated packets. If you're not > using IPSEC for anything else, removing the option should do the trick. > Also, make sure that you're running it as root, not only for raw socket > access but also so it can create the tun device. Thank you very much, Craig, I've removed IPSEC options from my kernel config and now vpnc works fine for me! The only thing I need to know: if CURRENT IPSec and vpnc are completely incompatible? If so, how to reproduce the vpnc behaviour using IPSec? Regards, Serguey. From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 17:13:47 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5037E16A417 for ; Tue, 21 Aug 2007 17:13:47 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.freebsd.org (Postfix) with ESMTP id 146C913C483 for ; Tue, 21 Aug 2007 17:13:46 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from thor.farley.org (thor.farley.org [192.168.1.5]) by mail.farley.org (8.14.1/8.14.1) with ESMTP id l7LHDgT4003292; Tue, 21 Aug 2007 12:13:42 -0500 (CDT) (envelope-from scf@FreeBSD.org) Date: Tue, 21 Aug 2007 12:13:42 -0500 (CDT) From: "Sean C. Farley" To: Nenhum_de_Nos In-Reply-To: <4956a5e50708210725k76925c45l46410719029d6dd4@mail.gmail.com> Message-ID: References: <4956a5e50708201723l623cf384ub10edd3ceea88e62@mail.gmail.com> <4956a5e50708201931t5e55d1d3lb329ed53b0edb356@mail.gmail.com> <4956a5e50708210725k76925c45l46410719029d6dd4@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=us-ascii; format=flowed X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.1 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on mail.farley.org Cc: freebsd-current@FreeBSD.org Subject: Re: error building yesterday code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 17:13:47 -0000 On Tue, 21 Aug 2007, Nenhum_de_Nos wrote: > On 8/21/07, Kip Macy wrote: >> Sounds like bad memory. Try memtest. >> > memtest is 91% ano bad nothing ... > > at night I can make further tests, but so far I'm not blaming the > memory > > any other ideas ? Bad caps (http://www.badcaps.net/)? The site tells you what to examine. I had some capacitors go bad on two motherboards (circa 2001). In fact, one of the boards did not show any physical problems with the capacitors until much later. memtest did not show any issues, and I ran it many times. If it is happening at various locations in the code as opposed to the same line each time, it usually points to hardware issues. Sean -- scf@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 17:50:01 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1929E16A419 for ; Tue, 21 Aug 2007 17:50:01 +0000 (UTC) (envelope-from davidt@yadt.co.uk) Received: from outcold.yadt.co.uk (outcold.yadt.co.uk [81.187.204.178]) by mx1.freebsd.org (Postfix) with ESMTP id B93F413C4B3 for ; Tue, 21 Aug 2007 17:50:00 +0000 (UTC) (envelope-from davidt@yadt.co.uk) Received: from localhost (localhost [127.0.0.1]) by outcold.yadt.co.uk (Postfix) with ESMTP id 90FA2569B2 for ; Tue, 21 Aug 2007 18:49:52 +0100 (BST) X-Virus-Scanned: amavisd-new at yadt.co.uk Received: from outcold.yadt.co.uk ([127.0.0.1]) by localhost (outcold.yadt.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b8ZELoCdkoYK for ; Tue, 21 Aug 2007 18:49:37 +0100 (BST) Received: by outcold.yadt.co.uk (Postfix, from userid 1001) id DDAD0569B1; Tue, 21 Aug 2007 18:49:36 +0100 (BST) Date: Tue, 21 Aug 2007 18:49:36 +0100 From: David Taylor To: freebsd-current@freebsd.org Message-ID: <20070821174936.GA8085@outcold.yadt.co.uk> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: buildworld failing at kdump_subr.c (SEEK_HOLE and SEEK_DATA) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 17:50:01 -0000 Hi, I'm having a problem compiling world, and I don't quite understand why it hasn't broken the world build for everyone. But anyway. The build is failing in usr.bin/kdump/ compiling kdump_subr.c. This file is generated by usr.bin/kdump/mksubr. The first line in this file is "#include ". Shortly afterwards it includes . The build fails as SEEK_HOLE and SEEK_DATA are undefined. This is because is defining SEEK_SET, SEEK_CUR, and SEEK_END. As a result, is not defining SEEK_, as SEEK_SET is already defined. I appear to have successfully worked around the problem by removing from kdump_subr.c the include of (which is presumably included again implicitly at some point after , as I get no warnings about the use of stdio functions. As I said, I don't understand how everyone else is successfully compiling kdump, but as there's no screaming, I assume they are... -- David Taylor From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 19:38:50 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F53D16A419 for ; Tue, 21 Aug 2007 19:38:50 +0000 (UTC) (envelope-from jgordeev@dir.bg) Received: from dir.bg (mail.dir.bg [194.145.63.28]) by mx1.freebsd.org (Postfix) with ESMTP id 0E75C13C4A5 for ; Tue, 21 Aug 2007 19:38:49 +0000 (UTC) (envelope-from jgordeev@dir.bg) Received: from [87.126.88.98] (account jgordeev HELO [10.102.9.50]) by dir.bg (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 29549140 for current@freebsd.org; Tue, 21 Aug 2007 21:38:47 +0300 Message-ID: <46CB315C.8020906@dir.bg> Date: Tue, 21 Aug 2007 21:39:24 +0300 From: Jordan Gordeev User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20070606 X-Accept-Language: bg, en MIME-Version: 1.0 To: current@freebsd.org References: <46C2263F.4080607@cisco.com> In-Reply-To: <46C2263F.4080607@cisco.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 21 Aug 2007 20:20:14 +0000 Cc: Subject: Re: IP over HTTP? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 19:38:50 -0000 Randall Stewart wrote: > Hi all: > > Just curious.. as anyone did this on BSD? > > If so, pointers would be nice.. if not... I may (but > I won't go into the rant as why ;-D) > > R Running IP over HTTP means your're likely to end up running TCP over TCP (TCP over IP over HTTP over TCP). AFAIK there's a problem with retransmission timers when running TCP over TCP. From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 21:21:52 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB96F16A417 for ; Tue, 21 Aug 2007 21:21:52 +0000 (UTC) (envelope-from cnst@FreeBSD.org) Received: from mojo.ru (mojo.ru [84.252.152.63]) by mx1.freebsd.org (Postfix) with ESMTP id 40F1213C45A for ; Tue, 21 Aug 2007 21:21:52 +0000 (UTC) (envelope-from cnst@FreeBSD.org) Received: from [192.168.0.16] (nc-76-4-28-21.dhcp.embarqhsd.net [76.4.28.21]) (authenticated bits=0) by mojo.ru (8.12.11.20060308/8.12.10) with ESMTP id l7LKsemU002279 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Aug 2007 00:54:48 +0400 Message-ID: <46CB50FE.7000306@FreeBSD.org> Date: Tue, 21 Aug 2007 16:54:22 -0400 From: "Constantine A. Murenin" Organization: Google Summer of Code 2007 Student @ The FreeBSD Project User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-gb, en-gb-oed, en, en-us, ru, ru-ru, ru-su MIME-Version: 1.0 To: freebsd-current@FreeBSD.org References: <200708210339.l7L3dUX0038042@repoman.freebsd.org> In-Reply-To: <200708210339.l7L3dUX0038042@repoman.freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Leidinger , Shteryana Shopova , "Constantine A. Murenin" Subject: GSoC2007: cnst-sensors.2007-08-20.patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 21:21:52 -0000 Dear freebsd-current@, It is my pleasure to present a Technology Preview patch that ports most of the base components of OpenBSD's hardware sensors framework to FreeBSD. Apart from the kernel framework for registering and accessing hardware sensors, this patch includes the lm(4) driver that supports nearly all known Winbond Super I/O chips that the majority of PCs have today. It also includes a patch that converts coretemp(4) driver to the new framework. Most noticeably, this patch does not yet include sysctl(8) access to hardware sensors; however, sensor readings can be conveniently monitored with systat(1) sensors display and logged with the included sensorsd(8). (As this project is about porting the framework, no iic(4) drivers were or will be ported from OpenBSD at this time -- however, if you are willing to port some drivers and need help with sensors framework, let me know.) Apply to FreeBSD 7.0-CURRENT as of 2007-08-20 by doing: cd /usr/src fetch http://p4web.freebsd.org/depot/projects/soc2007/cnst-sensors/cnst-sensors.2007-08-20.patch mkdir sys/dev/lm sys/modules/lm usr.sbin/sensorsd patch < cnst-sensors.2007-08-20.patch More details, including some installation instructions, are available in my LJ: http://cnst.livejournal.com/34170.html Cheers, Constantine, Google Summer of Code 2007 Student @ The FreeBSD Project. :) On 20/08/2007 23:39, Constantine A. Murenin wrote: > http://perforce.freebsd.org/chv.cgi?CH=125477 > > Change 125477 by cnst@dale on 2007/08/21 03:38:31 > > This is a complete `cvs diff` of cnst-sensors > GSoC2007 project as of 2007-08-20. > > It includes the following components, listed below in > the very same order as they are appearing in this diff: > > * sample configuration file for sensorsd > * sysctl(3) doc fixes for CTL_HW tree > * sysctl(3) documentation for hardware sensors > * sysctl(8) doc fixes for hw tree > * sysctl(8) documentation for hardware sensors > * assorted KNF fixes for sysctl(8) > * lm(4) documentation > * sensor_attach(9) et al documentation > * coretemp(4) conversion to hw.sensors framework > * lm(4) isa driver ported from OpenBSD > * /sys/kern/kern_sensors.c > o sensor_attach(9) API for drivers to register sensors > o sensor_task_register(9) API for the update task > o sysctl(3) glue code > * assorted KNF and bug-fixes for /sys/kern/kern_sysctl.c > * lm(4) module for testing sensor_attach/detach et al > * > * assorted bug-fixes and HW_SENSORS definition for > * sensors display for systat(1), including all documentation > * sensorsd(8) and all applicable documentation > > The most noticeable component that this patch does not include is > sysctl(8) support for hw.sensors, which is still in the works ATM. > Everything else should compile and should be fully functioning. > Please test. Sensor readings can be viewed with `systat -sensors` > and logged with `sensorsd`. > > This patch is submitted partially due to the 2007-08-20 deadline, > but mostly because no-one has ever reported running with this code > on FreeBSD, although several people have contacted me personally > and expressed their interest in this project -- I hope this unified > diff should make things a bit easier for potential testers. ;) > > Submitted by: cnst@FreeBSD.org (Constantine A. Murenin) > Obtained from: generated by sensors.cvsdiff.sh from > //depot/projects/soc2007/cnst_sensors/ > Sponsored by: Google Summer of Code 2007 > > Affected files ... > > .. //depot/projects/soc2007/cnst-sensors/cnst-sensors.2007-08-20.patch#1 add > > Differences ... > From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 00:12:40 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81B3D16A418 for ; Wed, 22 Aug 2007 00:12:40 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 3DCAF13C442 for ; Wed, 22 Aug 2007 00:12:39 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1INdpd-0007iD-HV for freebsd-current@freebsd.org; Wed, 22 Aug 2007 02:12:32 +0200 Received: from 84-51-160-73.pambow882.adsl.metronet.co.uk ([84.51.160.73]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 22 Aug 2007 02:12:21 +0200 Received: from robin-lists by 84-51-160-73.pambow882.adsl.metronet.co.uk with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 22 Aug 2007 02:12:21 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Robin Bowes Date: Wed, 22 Aug 2007 01:12:03 +0100 Lines: 45 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 84-51-160-73.pambow882.adsl.metronet.co.uk User-Agent: Thunderbird 2.0.0.6 (X11/20070811) X-Enigmail-Version: 0.95.3 Sender: news Subject: BTX halted with 7.0-CURRENT-2007-06 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 00:12:40 -0000 Hi, I'm trying to install 7.0-CURRENT on an Epox EP-D3VA motherboard with dual PIII processors (1Ghz) and 1.5GB RAM The CDROM is a Plextor installed as Primary on IDE Channel 0 There are two Promise SATA150 TX4 controllers each with three 250GB Maxtor SATA drives (6 drives in total). There is also a Highpoint HPT-370 controller on the mother board, which cna't be disabled but is not being used. I am already running Fedora Core 6 and Windows XP from different partitions on the first drive. When I boot from the FreeBSD 7.0-CURRENT disk (cd 1) I get this error: Boot from CD : CD Loader 1.2 Building the boot loader arguments Looking up /BOOT/LOADER... Found Relocating the loader and the BTX Starting the BTX loader BTX Loader 1.00 BTX Version is 1.01 Consoles: internal video/keyboard BIOS CD is cd0 int=0000000d err=00004890 efl=00010046 eip=00009257 eax=00000601 ebx=00000700 ecx=00000000 edf=0000184f esi=0000000c edi=00000000 edp=00000000 esp=000017dc cs=0008 ds=0010 es=0010 fs=0000 gs=0000 ss=0010 cs:eip=07 1f 0f a1 0f a9 cf fc-6a 10 1f 60 89 e5 0f b7 7d 2c c1 e7 04 0b 75 28-01 fe 31 c9 b1 02 31 c0 ss:eip=92 40 00 00 b0 48 00 00-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 BTX halted Can anyone help debug this? Thanks, R. From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 06:56:07 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E3CF16A41A for ; Wed, 22 Aug 2007 06:56:07 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id BBCFB13C457 for ; Wed, 22 Aug 2007 06:56:06 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (localhost [127.0.0.1]) by blah.sun-fish.com (Postfix) with ESMTP id 34A9A1B10EE7; Wed, 22 Aug 2007 08:56:05 +0200 (CEST) Received: from hater.cmotd.com (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id 319881B10EE0; Wed, 22 Aug 2007 08:56:05 +0200 (CEST) Message-ID: <46CBDE05.2030007@moneybookers.com> Date: Wed, 22 Aug 2007 09:56:05 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.4pre (X11/20070711) MIME-Version: 1.0 To: Kris Kennaway References: <46C9B99C.1060403@moneybookers.com> <46CA951D.1060303@moneybookers.com> <20070821163729.GA91485@rot26.obsecurity.org> In-Reply-To: <20070821163729.GA91485@rot26.obsecurity.org> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP on BLAH Cc: Eric Kjeldergaard , freebsd-current@freebsd.org Subject: Re: kernel panic with memory disks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 06:56:07 -0000 Kris Kennaway wrote: > On Tue, Aug 21, 2007 at 10:32:45AM +0300, Stefan Lambrev wrote: > >> Hello, >> >> Eric Kjeldergaard wrote: >> >>> On 20/08/07, Stefan Lambrev wrote: >>> >>> >>>> Hello, >>>> >>>> I do not know if this is know behavior, and I know that 6.2 panic if the >>>> memory disk got full, >>>> but on 7-current the panic is before the disk got full. >>>> >>>> Here is what I do: >>>> >>>> mdconfig -a -t malloc -s 800m >>>> newfs /dev/md0 >>>> mount /dev/md0 /mnt >>>> cp 600mb.file /mnt >>>> >>>> >>> -t type >>> Select the type of the memory disk. >>> >>> malloc Storage for this type of memory disk is allocated >>> with >>> malloc(9). This limits the size to the malloc bucket >>> limit in the kernel. If the -o reserve option is not >>> set, creating and filling a large malloc-backed >>> memory >>> disk is a very easy way to panic a system. >>> -- mdconfig(8) >>> >>> >>> >> I really should read manuals more carefully :) Thanks for the information. >> >> Just one more question - to prevent panic I should use "-o reserve" and >> have to increase: >> vfs.maxmallocbufspace >> vfs.bufmallocspace >> > > No, you should use -o swap. Where did it tell you to change the > sysctls? > > Kris > Nowhere just guessing. I just needed one big file in the memory to ignore the slowness of hard drives, to run few small benchmarks :) I did this using tmpfs, but it act just like "-t swap" :) Btw the confusion comes from the manual of mdconfig where it states: swap Swap space is used to back this memory disk. and I thought that type swap is always stored on the hard drives. and md(4) explains it a lot better: swap Backing store is allocated from buffer memory. Pages get pushed out to the swap when the system is under memory pressure, other- wise they stay in the operating memory. Using swap backing is generally preferable over malloc backing. -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 08:02:22 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB21C16A419 for ; Wed, 22 Aug 2007 08:02:22 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72]) by mx1.freebsd.org (Postfix) with ESMTP id B74BB13C474 for ; Wed, 22 Aug 2007 08:02:22 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-3.cisco.com with ESMTP; 22 Aug 2007 01:02:19 -0700 X-IronPort-AV: i="4.19,293,1183359600"; d="scan'208"; a="515883331:sNHT43421884" Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7M82IJ6020747 for ; Wed, 22 Aug 2007 01:02:18 -0700 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l7M82IJJ002117 for ; Wed, 22 Aug 2007 08:02:18 GMT Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 22 Aug 2007 01:02:18 -0700 Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 22 Aug 2007 01:02:17 -0700 Message-ID: <46CBED98.8060107@cisco.com> Date: Wed, 22 Aug 2007 04:02:32 -0400 From: Randall Stewart User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20070601 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 22 Aug 2007 08:02:17.0974 (UTC) FILETIME=[C2502960:01C7E492] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=746; t=1187769738; x=1188633738; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rrs@cisco.com; z=From:=20Randall=20Stewart=20 |Subject:=20IBM=20T43=20sleep=20issue |Sender:=20; bh=us63oxmBNv+iSRb0QDqfypoBY6lOVjLch37Xk0oWIhI=; b=A/e+J2YyYX38C5R9xCsetIpBc+TwZsQgs8LpSIzNlzp5YHkJZirKV3A+87CTy/ujgF+LdPxO LRDwIqCb04OKuFyD2PGfLMrchm44Pdr2tsaeyei8njwdvDJApzC7aB9C; Authentication-Results: sj-dkim-2; header.From=rrs@cisco.com; dkim=pass (sig from cisco.com/sjdkim2002 verified; ); Cc: Subject: IBM T43 sleep issue X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 08:02:22 -0000 Hi all: I just updated current last Sunday and now I have an issue with sleeping my T43. It used to work as a one-shot.. i.e. I can sleep once.. and wake up.. but it will never sleep again (I guess some driver had/has a flag hung to say wake-back-up)... But now, when it comes out of sleep it panics.. something about apic or something... Has anyone seen this? I can reproduce it quite regular.. but I cannot get a kernel dump (I guess the disk system is not initialized).. If someone is interested I can reproduce it and write down the stack trace from DDB ... Oh, and a .. update now and try again is also a fine answer.. :-D R -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 803-317-4952 (cell) From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 09:47:21 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5A8F16A41A for ; Wed, 22 Aug 2007 09:47:21 +0000 (UTC) (envelope-from uwe@grohnwaldt.eu) Received: from server02.lando.cc (server02.lando.cc [87.106.141.202]) by mx1.freebsd.org (Postfix) with ESMTP id 0FF3613C46C for ; Wed, 22 Aug 2007 09:47:20 +0000 (UTC) (envelope-from uwe@grohnwaldt.eu) Received: (qmail 31422 invoked from network); 22 Aug 2007 11:20:38 +0200 Received: from wlan033082.uni-rostock.de (HELO Winter) (139.30.33.82) by server02.lando.cc with (DHE-RSA-AES256-SHA encrypted) SMTP; 22 Aug 2007 11:20:37 +0200 Date: Wed, 22 Aug 2007 11:20:19 +0200 From: Uwe Grohnwaldt To: freebsd-current@freebsd.org Message-ID: <20070822112019.4151b937@Winter> In-Reply-To: <46CBED98.8060107@cisco.com> References: <46CBED98.8060107@cisco.com> X-Mailer: Claws Mail 2.10.0 (GTK+ 2.10.14; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: IBM T43 sleep issue X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 09:47:21 -0000 Am Wed, 22 Aug 2007 04:02:32 -0400 schrieb Randall Stewart : > Hi all: > > I just updated current last Sunday and now I have an issue > with sleeping my T43. > > It used to work as a one-shot.. i.e. I can sleep > once.. and wake up.. but it will never sleep again (I guess > some driver had/has a flag hung to say wake-back-up)... > > But now, when it comes out of sleep it panics.. something > about apic or something... Has anyone seen this? I can > reproduce it quite regular.. but I cannot get a kernel > dump (I guess the disk system is not initialized).. > > If someone is interested I can reproduce it and write down > the stack trace from DDB ... > > Oh, and a .. update now and try again is also a fine > answer.. :-D > > R Hi, I have the problem on my T43p since an update some weeks ago. It worked quite well unitl this Update. Sending it to sleep more than one time worked again. It would be nice if it will work again. :) Cheers, Uwe From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 10:36:18 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1DBA16A417 for ; Wed, 22 Aug 2007 10:36:18 +0000 (UTC) (envelope-from ianf@clue.co.za) Received: from munchkin.clue.co.za (munchkin.clue.co.za [66.219.59.160]) by mx1.freebsd.org (Postfix) with ESMTP id 8D65113C468 for ; Wed, 22 Aug 2007 10:36:18 +0000 (UTC) (envelope-from ianf@clue.co.za) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=20070313; d=clue.co.za; h=Received:Received:Received:To:Subject:From:X-Attribution:Date:Message-Id; b=Si4LnzEsOO6TcwDWifJZ8VVEpzz5CkPjwwWIPughoFhDQzCWtVjM5SqYtIiTug/Rlg3yyii/UgBUoIkPy4WCU8GlGEVLMEgNEq1U/xS3yc7SS6epu+s7uBSzcCvWTDMsQx5PzBCVSsMyeon1CFUlo+YHd/yzS/RQpmqpZ+zkp3uzsMzPKTpRGSzvra1+x/MsXl3qsTVcaKuAodD+z/vhXvAJ2xivj7xHJQK+c7mwItzlnsNx7/aZbIZ4qQBBHiMr; Received: from uucp by munchkin.clue.co.za with local-rmail (Exim 4.66) (envelope-from ) id 1INnZS-0007fQ-0W for current@freebsd.org; Wed, 22 Aug 2007 10:36:18 +0000 Received: from dsl-241-3-109.telkomadsl.co.za ([41.241.3.109] helo=clue.co.za) by urchin.clue.co.za with esmtpa (Exim 4.66) (envelope-from ) id 1INnZC-00046v-0h for current@freebsd.org; Wed, 22 Aug 2007 10:36:02 +0000 Received: from localhost ([127.0.0.1] helo=clue.co.za) by clue.co.za with esmtp (Exim 4.67 (FreeBSD)) (envelope-from ) id 1INnZ4-0000PN-8U for current@freebsd.org; Wed, 22 Aug 2007 12:35:54 +0200 To: current@freebsd.org From: Ian FREISLICH X-Attribution: BOFH Date: Wed, 22 Aug 2007 12:35:54 +0200 Message-Id: Cc: Subject: ATA DMA FAILURE - non aligned DMA transfer attempted X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 10:36:18 -0000 Hi I upgraded my home machine to -CURRENT recently and since then (until now) I've not been able to play dvds on it. This used to work. Hardware is: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x37 6,0xffa0-0xffaf at device 7.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] ad0: 76319MB at ata0-master UDMA66 acd0: DMA limited to UDMA33, device found non-ATA66 cable acd0: DVDR at ata1-master UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [2278670 x 2048 byte records] It's lying about the cable - it is a ATA66 cable, perhaps the port on the motherboard is not UDMA-66 capable. I get the following error: acd0: FAILURE - REPORT_KEY ILLEGAL REQUEST asc=0x6f ascq=0x04 acd0: FAILURE - REPORT_KEY ILLEGAL REQUEST asc=0x2c ascq=0x00 ata1: FAILURE - non aligned DMA transfer attempted acd0: setting up DMA failed If I set the mode on acd0 to WDMA2, then it works fine. Ian -- Ian Freislich From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 07:23:12 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D3CE16A418 for ; Wed, 22 Aug 2007 07:23:12 +0000 (UTC) (envelope-from mgrooms@shrew.net) Received: from shrew.net (206-223-169-85.beanfield.net [206.223.169.85]) by mx1.freebsd.org (Postfix) with ESMTP id 32EA013C461 for ; Wed, 22 Aug 2007 07:23:12 +0000 (UTC) (envelope-from mgrooms@shrew.net) Received: from localhost (206-223-169-82.beanfield.net [206.223.169.82]) by shrew.net (Postfix) with ESMTP id 10C6979DA82; Wed, 22 Aug 2007 01:57:27 -0500 (CDT) Received: from shrew.net ([206.223.169.85]) by localhost (mx1.hub.org [206.223.169.82]) (amavisd-new, port 10024) with ESMTP id 22844-01; Wed, 22 Aug 2007 06:57:26 +0000 (UTC) Received: from hole.shrew.net (cpe-66-25-136-5.austin.res.rr.com [66.25.136.5]) by shrew.net (Postfix) with ESMTP id 7F3A679DA81; Wed, 22 Aug 2007 01:57:26 -0500 (CDT) Received: from [10.22.200.21] ([10.22.200.21]) by hole.shrew.net (8.13.8/8.13.6) with ESMTP id l7LNwhSf081311; Tue, 21 Aug 2007 23:58:43 GMT (envelope-from mgrooms@shrew.net) Message-ID: <46CBDE6E.3090506@shrew.net> Date: Wed, 22 Aug 2007 01:57:50 -0500 From: Matthew Grooms User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org, serguey-grigoriev@yandex.ru References: <46CBD789.8060407@shrew.net> In-Reply-To: <46CBD789.8060407@shrew.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 22 Aug 2007 11:26:17 +0000 Cc: Subject: Re: Cisco PIX/ASA VPN client X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 07:23:12 -0000 > 21.08.07, 00:00, Craig Boston (cb@severious.net) wrote: > > Thank you very much, Craig, > > I've removed IPSEC options from my kernel config > and now vpnc works fine for me! > The only thing I need to know: if CURRENT IPSec and > vpnc are completely incompatible? If so, how to reproduce > the vpnc behaviour using IPSec? > You can try the ipsec tools racoon software which uses kernel ipsec protocol support and can communicate with cisco gateway products. As an alternative, you are welcome to give my ike software a try which also uses kernel ipsec protocol support. It is a port of an ike daemon and qt/gui front end applications originally written for a win32 client. I use it quite regularly to connect to a cisco ASA and supports FreeBSD, NetBSD and Linux platforms. Although it hasn't been tested much on current, it certainly works well with a 6.2 release ( w or w/o NAT-T patches ). The open source licensed code can be had from the following subversion repository ( see README.TXT for build and usage details ) ... svn://svn.shrew.net/ike/head ... a few screenshots ( 2 Win32, 1 FreeBSD ) for the curious ... http://www.shrew.net/?page=software I have a FreeBSD ports entry for this as well that I need to submit. -Matthew From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 13:17:57 2007 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8AE5016A419; Wed, 22 Aug 2007 13:17:57 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 5EE4B13C4A6; Wed, 22 Aug 2007 13:17:57 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id E508F4A784; Wed, 22 Aug 2007 09:17:56 -0400 (EDT) Date: Wed, 22 Aug 2007 14:17:56 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Diomidis Spinellis In-Reply-To: <46C96EFE.6070400@aueb.gr> Message-ID: <20070822141726.E64808@fledge.watson.org> References: <20070819214953.I1099@fledge.watson.org> <46C8C2E6.9030405@aueb.gr> <20070819164823.H568@10.0.0.1> <46C96EFE.6070400@aueb.gr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: attilio@FreeBSD.ORG, Jeff Roberson , jeff@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Crash in accounting code: encode_long(), due to bad rusage data? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 13:17:57 -0000 On Mon, 20 Aug 2007, Diomidis Spinellis wrote: > Jeff Roberson wrote: >>> Robert Watson wrote: >>>> I recently upgraded two servers from FreeBSD 6-STABLE to FreeBSD >>>> 7-CURRENT in anticipation of the forthcoming release. Both of them run >>>> with accounting enabled at all times. When a large pine session was >>>> exiting on one of the two boxes, I ran into the following panic: >>>> >>>> panic: encode_long: -ve value -32749 > [...] >> What do you think about simply putting in a max value if we overflow? We >> could then make a note about it in process accounting docs. We might want >> to fix this in rusage as well. > > Encoding LONG_MAX and issuing a printf warning is I think a reasonable > solution. I'll be away from a broadband connection until Friday, so if > anybody else wants to commit this, go ahead. Otherwise I can do it over the > coming weekend. I'm pretty maxed out here right now, so certainly won't get to it sooner, so if you don't mind doing it this weekend, that would be good. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 13:59:34 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 769A316A420 for ; Wed, 22 Aug 2007 13:59:34 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 60D9813C4DA for ; Wed, 22 Aug 2007 13:59:34 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from rot26.obsecurity.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id C951F1A3C1A; Wed, 22 Aug 2007 06:57:36 -0700 (PDT) Received: by rot26.obsecurity.org (Postfix, from userid 1001) id 462E9C3ED; Wed, 22 Aug 2007 09:59:33 -0400 (EDT) Date: Wed, 22 Aug 2007 09:59:33 -0400 From: Kris Kennaway To: Stefan Lambrev Message-ID: <20070822135932.GA9190@rot26.obsecurity.org> References: <46C9B99C.1060403@moneybookers.com> <46CA951D.1060303@moneybookers.com> <20070821163729.GA91485@rot26.obsecurity.org> <46CBDE05.2030007@moneybookers.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46CBDE05.2030007@moneybookers.com> User-Agent: Mutt/1.4.2.3i Cc: Eric Kjeldergaard , freebsd-current@freebsd.org, Kris Kennaway Subject: Re: kernel panic with memory disks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 13:59:34 -0000 On Wed, Aug 22, 2007 at 09:56:05AM +0300, Stefan Lambrev wrote: > >No, you should use -o swap. Where did it tell you to change the > >sysctls? > > > >Kris > > > Nowhere just guessing. OK, often not a good idea :) > I just needed one big file in the memory to ignore the slowness of hard > drives, to run few small benchmarks :) > I did this using tmpfs, but it act just like "-t swap" :) Yes, when you don't have enough RAM to do the thing you want. > Btw the confusion comes from the manual of mdconfig where it states: > > swap Swap space is used to back this memory disk. > > and I thought that type swap is always stored on the hard drives. > > and md(4) explains it a lot better: > > swap Backing store is allocated from buffer memory. Pages get pushed > out to the swap when the system is under memory pressure, > other- > wise they stay in the operating memory. Using swap backing is > generally preferable over malloc backing. OK, that could certainly be improved. Can you please submit a PR? Kris From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 14:46:56 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 444F816A419 for ; Wed, 22 Aug 2007 14:46:56 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id E161613C49D for ; Wed, 22 Aug 2007 14:46:55 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (localhost [127.0.0.1]) by blah.sun-fish.com (Postfix) with ESMTP id 262A01B10ED2; Wed, 22 Aug 2007 16:46:55 +0200 (CEST) Received: from hater.cmotd.com (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id 234E31B10EB5; Wed, 22 Aug 2007 16:46:55 +0200 (CEST) Message-ID: <46CC4C5F.9050704@moneybookers.com> Date: Wed, 22 Aug 2007 17:46:55 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.4pre (X11/20070711) MIME-Version: 1.0 To: Kris Kennaway References: <46C9B99C.1060403@moneybookers.com> <46CA951D.1060303@moneybookers.com> <20070821163729.GA91485@rot26.obsecurity.org> <46CBDE05.2030007@moneybookers.com> <20070822135932.GA9190@rot26.obsecurity.org> In-Reply-To: <20070822135932.GA9190@rot26.obsecurity.org> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP on BLAH Cc: Eric Kjeldergaard , freebsd-current@freebsd.org Subject: Re: kernel panic with memory disks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 14:46:56 -0000 Hello, Kris Kennaway wrote: > On Wed, Aug 22, 2007 at 09:56:05AM +0300, Stefan Lambrev wrote: > > >>> No, you should use -o swap. Where did it tell you to change the >>> sysctls? >>> >>> Kris >>> >>> >> Nowhere just guessing. >> > > OK, often not a good idea :) > > >> I just needed one big file in the memory to ignore the slowness of hard >> drives, to run few small benchmarks :) >> I did this using tmpfs, but it act just like "-t swap" :) >> > > Yes, when you don't have enough RAM to do the thing you want. > > >> Btw the confusion comes from the manual of mdconfig where it states: >> >> swap Swap space is used to back this memory disk. >> >> and I thought that type swap is always stored on the hard drives. >> >> and md(4) explains it a lot better: >> >> swap Backing store is allocated from buffer memory. Pages get pushed >> out to the swap when the system is under memory pressure, >> other- >> wise they stay in the operating memory. Using swap backing is >> generally preferable over malloc backing. >> > > OK, that could certainly be improved. Can you please submit a PR? > > Kris > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > Ok sent. Should be visible at some point here: http://www.freebsd.org/cgi/query-pr.cgi?pr=115721 -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 14:48:43 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E9BF16A41A for ; Wed, 22 Aug 2007 14:48:43 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id A6BD013C45E for ; Wed, 22 Aug 2007 14:48:42 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1INrVd-0005iE-Tg for freebsd-current@freebsd.org; Wed, 22 Aug 2007 16:48:37 +0200 Received: from mulderlab.f5.com ([205.229.151.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 22 Aug 2007 16:48:37 +0200 Received: from atkin901 by mulderlab.f5.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 22 Aug 2007 16:48:37 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Mark Atkinson Date: Wed, 22 Aug 2007 07:48:19 -0700 Lines: 74 Message-ID: References: <7F42CA7D-24C4-4A47-AC67-8F5E6A248380@siliconlandmark.com> <20070809172302.GA13685@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: mulderlab.f5.com User-Agent: KNode/0.10.5 Sender: news Subject: Re: panic: mtx_lock() of destroyed mutex @ /usr/src/sys/net/route.c:1306 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 14:48:43 -0000 Dan Nelson wrote: > In the last episode (Mar 27), Andre Guibert de Bruet said: >> I got this earlier today. I managed to get what appears to be a sane >> dump: >> >> Unread portion of the kernel message buffer: >> panic: mtx_lock() of destroyed mutex @ /usr/src/sys/net/route.c:1306 >> cpuid = 0 >> KDB: enter: panic >> Physical memory: 3575 MB >> Dumping 324 MB: 309 293 277 261 245 229 213 197 181 165 149 133 117 101 >> 85 69 53 37 21 5 > > I just booted today's -current and got the same panic with a similar > stack trace. I've actually been getting it once a week or so since I > switched to -current in June, but it's bugging me today. > > panic: mtx_lock() of destroyed mutex @ ../../../net/route.c:1303 me too on this one on -current built on the 10th, but it looks like it's been there for a while. FreeBSD 7.0-CURRENT #11: Fri Aug 10 09:06:48 PDT 2007 panic: mtx_lock() of destroyed mutex @ /usr/src/sys/net/route.c:1303 cpuid = 0 KDB: enter: panic [thread pid 60672 tid 100113 ] Stopped at kdb_enter+0x32: leave db> db> bt Tracing pid 60672 tid 100113 td 0xc6a8b440 kdb_enter(c0aa8eb9,0,c0aa7df5,e67e49b8,0,...) at kdb_enter+0x32 panic(c0aa7df5,c0ab6a61,517,507,c40b257c,...) at panic+0x126 _mtx_lock_flags(c6a90d08,0,c0ab6a61,517,e67e4a24,...) at _mtx_lock_flags+0x65 rt_check(e67e4a1c,e67e4a38,c54800f0,c0b5b3e4,c0ab6a61,...) at rt_check+0x111 arpresolve(c4040400,c43667f8,c43be000,c54800f0,e67e4a52,...) at arpresolve+0xaf ether_output(c4040400,c43be000,c54800f0,c43667f8,e67e4aa0,...) at ether_output+0x7e ip_output(c43be000,0,e67e4ac8,0,0,...) at ip_output+0xa09 udp_send(c879dad4,0,c43be000,0,0,...) at udp_send+0x586 sosend_dgram(c879dad4,0,e67e4be8,c43be000,0,...) at sosend_dgram+0x35f sosend(c879dad4,0,e67e4be8,0,0,...) at sosend+0x54 kern_sendit(c6a8b440,6,e67e4c64,0,0,...) at kern_sendit+0x104 sendit(0,bfbee85f,0,0,0,...) at sendit+0xb1 sendto(c6a8b440,e67e4cfc,18,c0aaf36c,c0b55d18,...) at sendto+0x48 syscall(e67e4d38) at syscall+0x2f3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (133, FreeBSD ELF32, sendto), eip = 0x28388797, esp = 0xbfbedf8c, ebp = 0xbfbedfb8 --- db> show alllocks Process 60673 (sendmail) thread 0xc6a8b000 (100115) exclusive sleep mutex radix node head r = 1 (0xc40b257c) locked @ /usr/src/sys/net/route.c:684 exclusive sleep mutex inp (udpinp) r = 0 (0xc43627c8) locked @ /usr/src/sys/netinet/udp_usrreq.c:841 Process 60672 (sendmail) thread 0xc6a8b440 (100113) exclusive sleep mutex rtentry r = 0 (0xc4366858) locked @ /usr/src/sys/net/route.c:1287 exclusive sleep mutex inp (udpinp) r = 0 (0xc4363090) locked @ /usr/src/sys/netinet/udp_usrreq.c:841 db> --- Mark Atkinson atkin901@yahoo.com (!wired)?(coffee++):(wired); From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 15:00:48 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C9B816A420 for ; Wed, 22 Aug 2007 15:00:48 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from qsrv02ps.mx.bigpond.com (qsrv02ps.mx.bigpond.com [144.140.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 31FB113C48E for ; Wed, 22 Aug 2007 15:00:47 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from oaamta08ps.mx.bigpond.com ([124.188.162.95]) by omta04ps.mx.bigpond.com with ESMTP id <20070822130613.MNIM1991.omta04ps.mx.bigpond.com@oaamta08ps.mx.bigpond.com> for ; Wed, 22 Aug 2007 13:06:13 +0000 Received: from areilly.bpa.nu ([124.188.162.95]) by oaamta08ps.mx.bigpond.com with ESMTP id <20070822130613.LLBP20695.oaamta08ps.mx.bigpond.com@areilly.bpa.nu> for ; Wed, 22 Aug 2007 13:06:13 +0000 Received: (qmail 97932 invoked by uid 501); 22 Aug 2007 13:06:03 -0000 Date: Wed, 22 Aug 2007 23:06:03 +1000 From: Andrew Reilly To: raven@katsurajima.seya.yokohama.jp, current@freebsd.org Message-ID: <20070822130603.GA97698@duncan.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: who to talk to about sound device issues? (M-Audio Delta 1010: envy24) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 15:00:48 -0000 Hi there, I'd like to help (if I can) to get the envy24 sound device support working with an M-Audio Delta 1010, which is what I have. Who should I talk to about it? Who should I talk to about the FreeBSD PCM framework, to the extent that it differs from the oss device drivers that I've been using up to now? (Specifically, multi-channel, and the fact that the pcm devices don't seem to show up int /dev/ the way I expected, and actually seem to become less accessible over time.) Thanks in advance, -- Andrew From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 15:14:23 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D71B016A46D for ; Wed, 22 Aug 2007 15:14:23 +0000 (UTC) (envelope-from pj@smo.de) Received: from ilk.de (mx-out13.ilk.de [194.121.104.13]) by mx1.freebsd.org (Postfix) with ESMTP id 597EC13C46B for ; Wed, 22 Aug 2007 15:14:22 +0000 (UTC) (envelope-from pj@smo.de) Received: from bologna.intern.smo.de (pool45.ka.ilk.net [212.86.194.45]) by ilk.de (8.13.4/8.13.4/ilk-relay) with ESMTP id l7MFEGva007090; Wed, 22 Aug 2007 17:14:16 +0200 Received: from [192.168.153.75] (ancona.intern.smo.de [192.168.153.75]) by bologna.intern.smo.de (8.13.4+Sun/8.13.4) with ESMTP id l7MFB3vC000312; Wed, 22 Aug 2007 17:11:03 +0200 (CEST) Message-ID: <46CC52E3.3030708@smo.de> Date: Wed, 22 Aug 2007 17:14:43 +0200 From: Philipp Ost User-Agent: Thunderbird 2.0.0.0 (X11/20070423) MIME-Version: 1.0 To: Andrew Reilly References: <20070822130603.GA97698@duncan.reilly.home> In-Reply-To: <20070822130603.GA97698@duncan.reilly.home> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: who to talk to about sound device issues? (M-Audio Delta 1010: envy24) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 15:14:23 -0000 Andrew Reilly schrieb: > Hi there, > > I'd like to help (if I can) to get the envy24 sound device > support working with an M-Audio Delta 1010, which is what I > have. Who should I talk to about it? > > Who should I talk to about the FreeBSD PCM framework, to the > extent that it differs from the oss device drivers that I've > been using up to now? (Specifically, multi-channel, and the > fact that the pcm devices don't seem to show up int /dev/ the > way I expected, and actually seem to become less accessible over > time.) > > Thanks in advance, > Konstantin Dimitrov is/has been working on envy24 support. Check the multimedia@-archives, there are several threads on this topic ;-) HTH, Philipp From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 15:38:38 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA05316A420 for ; Wed, 22 Aug 2007 15:38:38 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from webmail25.mail.yandex.net (webmail25.mail.yandex.net [213.180.223.153]) by mx1.freebsd.org (Postfix) with ESMTP id 4115D13C4D1 for ; Wed, 22 Aug 2007 15:38:38 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from YAMAIL (webmail25) by mail.yandex.ru id S7721393AbXHVPie for ; Wed, 22 Aug 2007 19:38:34 +0400 X-Yandex-Spam: 1 Received: from [77.72.136.71] ([77.72.136.71]) by mail.yandex.ru with HTTP; Wed, 22 Aug 2007 19:38:34 +0400 From: "Andrey V. Elsukov" To: atkin901@yahoo.com In-Reply-To: 1550000000202904530 References: <7F42CA7D-24C4-4A47-AC67-8F5E6A248380@siliconlandmark.com> <20070809172302.GA13685@dan.emsphone.com> 1550000000202904530 MIME-Version: 1.0 Message-Id: <145511187797114@webmail25.yandex.ru> Date: Wed, 22 Aug 2007 19:38:34 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain Cc: freebsd-current@freebsd.org Subject: Re: panic: mtx_lock() of destroyed mutex @ /usr/src/sys/net/route.c:1306 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 15:38:38 -0000 > Dan Nelson wrote: > >> panic: mtx_lock() of destroyed mutex @ /usr/src/sys/net/route.c:1306 > >> cpuid = 0 > >> KDB: enter: panic > >> Physical memory: 3575 MB > >> Dumping 324 MB: 309 293 277 261 245 229 213 197 181 165 149 133 117 101 > >> 85 69 53 37 21 5 > > > > I just booted today's -current and got the same panic with a similar > > stack trace. I've actually been getting it once a week or so since I > > switched to -current in June, but it's bugging me today. I think my problem is related to routing code too. http://lists.freebsd.org/pipermail/freebsd-current/2007-August/076270.html (kgdb) l *0xc0585ee5 0xc0585ee5 is in _mtx_lock_sleep (/usr/src/sys/kern/kern_mutex.c:363). 358 * If the current owner of the lock is executing on another 359 * CPU, spin instead of blocking. 360 */ 361 owner = (struct thread *)(v & ~MTX_FLAGMASK); 362 #ifdef ADAPTIVE_GIANT 363 if (TD_IS_RUNNING(owner)) 364 #else 365 if (m != &Giant && TD_IS_RUNNING(owner)) 366 #endif 367 { (kgdb) f 10 #10 0xc0585ee5 in _mtx_lock_sleep (m=0xc3696b28, tid=3281945120, opts=0, file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:361 361 owner = (struct thread *)(v & ~MTX_FLAGMASK); (kgdb) p *m $1 = {lock_object = {lo_name = 0xc0807e84 "rtentry", lo_type = 0xc0807e84 "rtentry", lo_flags = 21102592, lo_witness_data = {lod_list = { stqe_next = 0x0}, lod_witness = 0x0}}, mtx_lock = 6, mtx_recurse = 0} The mtx_lock value is 6 - this is MTX_DESTROYED. My coredump and kernel is here: http://butcher.heavennet.ru/panic/ -- WBR, Andrey V. Elsukov From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 19:59:22 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5A6A16A418 for ; Wed, 22 Aug 2007 19:59:22 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.freebsd.org (Postfix) with ESMTP id 8679C13C465 for ; Wed, 22 Aug 2007 19:59:22 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (cpe-71-72-80-132.columbus.res.rr.com [71.72.80.132]) (authenticated bits=0) by mail.united-ware.com (8.13.8/8.13.8) with ESMTP id l7MKbb0V060195 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Aug 2007 16:37:44 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: David Malone Date: Wed, 22 Aug 2007 16:02:32 -0400 User-Agent: KMail/1.9.6 References: <200708210928.aa80674@walton.maths.tcd.ie> In-Reply-To: <200708210928.aa80674@walton.maths.tcd.ie> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2033423.lNeCjCqxub"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200708221602.42191.mistry.7@osu.edu> X-Virus-Scanned: ClamAV 0.90.3/4025/Tue Aug 21 19:37:57 2007 on mail.united-ware.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: Can't create TCP connections to certain IP addresses X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 19:59:22 -0000 --nextPart2033423.lNeCjCqxub Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 21 August 2007, David Malone wrote: > > What's the PR number? > > The PR that I am thinking of is: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Di386/69257 > > > COPTFLAGS+=3D-O2 > > CPUTYPE=3Di586/mmx > > I guess you may not be directly be effected, as you're using -O2, > but it might be another interaction with gcc, so I'd try compiling > a kernel with -O, just to see if you get a different result. > > (Record the output of building the kernel, just to make sure it is > using the flags you think it is.) I had to specify CFLAGS=3D-O -pipe in make.conf to force the kernel to build without -O2 even after=20 removing the COPTFLAGS and CPUTYPE. It's fixed now by forcing -O, but this seems to be a serious issue=20 as -O2 is the default. Is this fixed in 4.2.1? And will that make it=20 into 7.0? =2D-=20 Anish Mistry --nextPart2033423.lNeCjCqxub Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBGzJZixqA5ziudZT0RAqYsAJ0YJ4ESV23T7tCvZx3j/midIiRiogCfQtG/ R0sreihTck3/9aBATUnUTIY= =mism -----END PGP SIGNATURE----- --nextPart2033423.lNeCjCqxub-- From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 22:30:12 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81F4916A419 for ; Wed, 22 Aug 2007 22:30:12 +0000 (UTC) (envelope-from h.schmalzbauer@omnisec.de) Received: from host.omnisec.de (host.omnisec.de [62.245.232.135]) by mx1.freebsd.org (Postfix) with ESMTP id E87A713C45E for ; Wed, 22 Aug 2007 22:30:11 +0000 (UTC) (envelope-from h.schmalzbauer@omnisec.de) Received: from akima.flintsbach.schmalzbauer.de (akima.flintsbach.schmalzbauer.de [172.21.1.35]) (authenticated bits=0) by host.omnisec.de (8.13.8/8.13.8) with ESMTP id l7MMU9s6034991 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 23 Aug 2007 00:30:10 +0200 (CEST) (envelope-from h.schmalzbauer@omnisec.de) From: Harald Schmalzbauer Organization: OmniSEC To: freebsd-current@freebsd.org Date: Thu, 23 Aug 2007 00:30:04 +0200 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200708230030.05749.h.schmalzbauer@omnisec.de> Subject: vidcontrol modes for ATI ES1000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 22:30:12 -0000 Hello, I have a Intel Server Board S3000AHV, which has an ATI ES1000 VGA Chip with 16B onboard. I have SC_PIXEL_MODE and VESA in my kernel, but 'vidconsole -i mode' shows only one! line: 24 (0x018) 0x00000001 T 80x25 8x16 0xb000 32k 32k 0x00000000 32k Does vidconsole (SC) rely on the VGA BIOS? If so probably it's not the best designed VGA BIOS. Are there any other ways to get 800x600 Text console? The funny thing is that accessing the EFI shell(or even just booting) the board uses a higher resolution (800x600 I think), so it doesn't use the promoted mode itself! Thanks, -Harry From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 01:46:02 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D430D16A41B for ; Thu, 23 Aug 2007 01:46:02 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from omta03sl.mx.bigpond.com (omta03sl.mx.bigpond.com [144.140.92.155]) by mx1.freebsd.org (Postfix) with ESMTP id 6226F13C483 for ; Thu, 23 Aug 2007 01:46:01 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from oaamta03sl.mx.bigpond.com ([124.188.162.95]) by omta03sl.mx.bigpond.com with ESMTP id <20070823014600.EXUV12810.omta03sl.mx.bigpond.com@oaamta03sl.mx.bigpond.com> for ; Thu, 23 Aug 2007 01:46:00 +0000 Received: from areilly.bpa.nu ([124.188.162.95]) by oaamta03sl.mx.bigpond.com with ESMTP id <20070823014559.QDTP15989.oaamta03sl.mx.bigpond.com@areilly.bpa.nu> for ; Thu, 23 Aug 2007 01:45:59 +0000 Received: (qmail 21898 invoked by uid 501); 23 Aug 2007 01:45:49 -0000 Date: Thu, 23 Aug 2007 11:45:49 +1000 From: Andrew Reilly To: Philipp Ost Message-ID: <20070823014549.GA21876@duncan.reilly.home> References: <20070822130603.GA97698@duncan.reilly.home> <46CC52E3.3030708@smo.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46CC52E3.3030708@smo.de> User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org Subject: Re: who to talk to about sound device issues? (M-Audio Delta 1010: envy24) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 01:46:02 -0000 On Wed, Aug 22, 2007 at 05:14:43PM +0200, Philipp Ost wrote: > Konstantin Dimitrov is/has been working on envy24 support. Check the > multimedia@-archives, there are several threads on this topic ;-) Thanks for that. I thought that I was subscribed to that list, but it seems that I'm not. Oh, well. I'll catch up. Cheers, -- Andrew From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 02:19:50 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7055316A419 for ; Thu, 23 Aug 2007 02:19:50 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 2E10813C45B for ; Thu, 23 Aug 2007 02:19:50 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.8/8.13.4) with ESMTP id l7N2ImTl024399; Wed, 22 Aug 2007 20:18:48 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 22 Aug 2007 20:18:51 -0600 (MDT) Message-Id: <20070822.201851.-1889957000.imp@bsdimp.com> To: se@freebsd.org From: "M. Warner Losh" In-Reply-To: <20070819073953.GA36594@Gatekeeper.FreeBSD.org> References: <864piweemc.fsf@santinel.home.ua> <20070819.120136.41629169.ken@tydfam.jp> <20070819073953.GA36594@Gatekeeper.FreeBSD.org> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 22 Aug 2007 20:18:51 -0600 (MDT) Cc: anrays@gmail.com, freebsd-current@freebsd.org, glewis@eyesbeyond.com, lists_freebsd_org@07.antispam.web-wahnsinn.de, freebsd-java@freebsd.org Subject: Re: Gcc bugs break java/jdk15 build? [Workaround] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 02:19:50 -0000 In message: <20070819073953.GA36594@Gatekeeper.FreeBSD.org> Stefan E=DFer writes: : On 2007-08-19 12:01 +0900, Ken Yamada wrote: : > Does this mean that GCC 4.2.1 does not solve "loop optimization b= ug" = : > pointed out by Andrey Chernov (http://docs.freebsd.org/cgi/getmsg= .cgi?fetch=3D282888+0+archive/2007/freebsd-current/20070701.freebsd-cur= rent) on 4.2.0? : > = : > Is it a good idea of adding -fno-tree-vrp to CFLAGS in /etc/make.= conf = : > to avoid this optimization bug for all compilation? (BTW, I leav= e -O3 = : > of CFLAGS as is in make.conf and just added -fno-tree-vrp to the = end of = : > the line.) : = : I did just that (added -fno-tree-vrp to CFLAGS) after it was found : that gcc-4.2 had the optimizer bug, and have continued to build my : system with -O2 (or other optimization levels as required). This = : seems to work just fine (no problems with ports that are not working : when built with a plain -O2). I had suggested to make -fno-tree-vrp : the default for our CC (could be overridden on the command line, but : would allow to use all -O levels without being hit by the compiler : bug; but it appears that nobody else liked the idea at that time, = : i.e. no response at all ...). Actually, it was added to the tree and then backed out because it broke the upgrade path. Warner From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 02:43:22 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17A6C16A420 for ; Thu, 23 Aug 2007 02:43:22 +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 A351E13C48D for ; Thu, 23 Aug 2007 02:43:21 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.61]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id l7N2hIWI013685 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Aug 2007 12:13:18 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Thu, 23 Aug 2007 12:13:03 +0930 User-Agent: KMail/1.9.7 References: <200708230030.05749.h.schmalzbauer@omnisec.de> In-Reply-To: <200708230030.05749.h.schmalzbauer@omnisec.de> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2758030.gj0y55rb62"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200708231213.16908.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.58 on 203.31.81.10 Cc: Harald Schmalzbauer Subject: Re: vidcontrol modes for ATI ES1000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 02:43:22 -0000 --nextPart2758030.gj0y55rb62 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 23 Aug 2007, Harald Schmalzbauer wrote: > Does vidconsole (SC) rely on the VGA BIOS? > If so probably it's not the best designed VGA BIOS. AFAIK yes. > Are there any other ways to get 800x600 Text console? > The funny thing is that accessing the EFI shell(or even just booting) > the board uses a higher resolution (800x600 I think), so it doesn't > use the promoted mode itself! Use X :) (Goes a lot faster that VESA pixel displays) =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 --nextPart2758030.gj0y55rb62 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBGzPRE5ZPcIHs/zowRAiwyAJ9QHOe8mYOdBZ5CrlqpDUhn4j6/kgCeNB1i oNIFovEN33s3lHwf28QFyXo= =JhhS -----END PGP SIGNATURE----- --nextPart2758030.gj0y55rb62-- From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 02:55:40 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6AFD716A417 for ; Thu, 23 Aug 2007 02:55:40 +0000 (UTC) (envelope-from freebsd@gm.nunu.org) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.224]) by mx1.freebsd.org (Postfix) with ESMTP id 203CE13C459 for ; Thu, 23 Aug 2007 02:55:39 +0000 (UTC) (envelope-from freebsd@gm.nunu.org) Received: by nz-out-0506.google.com with SMTP id l8so231109nzf for ; Wed, 22 Aug 2007 19:55:39 -0700 (PDT) Received: by 10.142.156.13 with SMTP id d13mr154543wfe.1187837738335; Wed, 22 Aug 2007 19:55:38 -0700 (PDT) Received: by 10.142.203.18 with HTTP; Wed, 22 Aug 2007 19:55:38 -0700 (PDT) Message-ID: <626eb4530708221955p3dd65df6h31e5b7cc79e8ced6@mail.gmail.com> Date: Thu, 23 Aug 2007 11:55:38 +0900 From: "Hidetoshi Shimokawa" Sender: freebsd@gm.nunu.org To: "Daniel O'Connor" In-Reply-To: <200708182340.00680.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_2102_8443763.1187837738266" References: <200708100010.46487.h.schmalzbauer@omnisec.de> <200708100052.39861.h.schmalzbauer@omnisec.de> <626eb4530708091703j18bd2cd7w99f9b96a3f3c402c@mail.gmail.com> <200708182340.00680.doconnor@gsoft.com.au> X-Google-Sender-Auth: eb703ec98f106069 Cc: freebsd-current@freebsd.org, Harald Schmalzbauer Subject: Re: firewire problem (root node is not cycle master capable) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 02:55:40 -0000 ------=_Part_2102_8443763.1187837738266 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Sure, please find attached a patch. On 8/18/07, Daniel O'Connor wrote: > On Fri, 10 Aug 2007, Hidetoshi Shimokawa wrote: > > On 8/10/07, Harald Schmalzbauer wrote: > > > Am Freitag, 10. August 2007 00:23:41 schrieb Hidetoshi Shimokawa: > > > > Basically, you don't need the cycle master for sbp devices. > > > > Try the following. > > > > > > > > 1. fwcontrol -r > > > > 2. fwcontrol -f 0 -r > > > > > > Hm, I think that's a typo, the man page doesn't show "-f" nor does > > > my fwcontrol understand it. > > > > Oops, it was an uncommited option in my repository which sends > > force_root packets. > > Any chance you can post a diff? I see this on a remote machine and would > like to try it. > > -- > 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 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- /\ Hidetoshi Shimokawa \/ simokawa@FreeBSD.ORG ------=_Part_2102_8443763.1187837738266 Content-Type: application/octet-stream; name=fwcontrol.patch Content-Transfer-Encoding: base64 X-Attachment-Id: f_f5onrk0f Content-Disposition: attachment; filename="fwcontrol.patch" SW5kZXg6IGZ3Y29udHJvbC44Cj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KUkNTIGZpbGU6IC9ob21lL25jdnMvc3JjL3Vz ci5zYmluL2Z3Y29udHJvbC9md2NvbnRyb2wuOCx2CnJldHJpZXZpbmcgcmV2aXNpb24gMS4xOApk aWZmIC11IC1yMS4xOCBmd2NvbnRyb2wuOAotLS0gZndjb250cm9sLjgJMjkgRGVjIDIwMDYgMTM6 MDg6NDYgLTAwMDAJMS4xOAorKysgZndjb250cm9sLjgJMjIgTWFyIDIwMDcgMTU6MjY6NDAgLTAw MDAKQEAgLTM5LDYgKzM5LDcgQEAKIC5PcCBGbCBvIEFyIG5vZGUKIC5PcCBGbCBzIEFyIG5vZGUK IC5PcCBGbCBsIEFyIGZpbGUKKy5PcCBGbCBmIEFyIG5vZGUKIC5PcCBGbCBnIEFyIGdhcF9jb3Vu dAogLk9wIEZsIGIgQXIgcHJpX3JlcQogLk9wIEZsIE0gQXIgbW9kZQpAQCAtNzcsNiArNzgsMTAg QEAKIHJlZ2lzdGVyIG9uIHRoZSBub2RlLgogLkl0IEZsIGwgQXIgZmlsZQogTG9hZCBoZXggZHVt cCBmaWxlIG9mIHRoZSBjb25maWd1cmF0aW9uIFJPTSBhbmQgcGFyc2UgaXQuCisuSXQgRmwgZiBB ciBub2RlCitGb3JjZSBzcGVjaWZpZWQKKy5BciBub2RlCit0byBiZSB0aGUgcm9vdCBub2RlIG9u IHRoZSBuZXh0IGJ1cyByZXNldC4KIC5JdCBGbCBnIEFyIGdhcF9jb3VudAogQnJvYWRjYXN0CiAu QXIgZ2FwX2NvdW50CkBAIC05OCw3ICsxMDMsNyBAQAogLkl0IEZsIFIgQXIgZmlsZW5hbWUKIFJl Y2VpdmUgRFYgb3IgTVBFRyBUUyBzdHJlYW0gYW5kIGR1bXAgaXQgdG8gYSBmaWxlLgogVXNlIEN0 cmwtQyB0byBzdG9wIHRoZSByZWNlaXZpbmcuCi1Tb21lIERWIGNhbWVyYXMgc2VlbSBub3QgdG8g c2VuZCB0aGUgc3RyZWFtIGlmIGEgYnVzIG1hbmFnZXIgZXhpdHMuCitTb21lIERWIGNhbWVyYXMg c2VlbSBub3QgdG8gc2VuZCB0aGUgc3RyZWFtIGlmIGEgYnVzIG1hbmFnZXIgZXhpc3RzLgogSWYg eW91IGNhbm5vdCBnZXQgdGhlIHN0cmVhbSwgdHJ5IHRoZSBmb2xsb3dpbmcgY29tbWFuZHM6CiAu QmQgLWxpdGVyYWwgLW9mZnNldCBpbmRlbnQKIHN5c2N0bCBody5maXJld2lyZS50cnlfYm1yPTAK SW5kZXg6IGZ3Y29udHJvbC5jCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KUkNTIGZpbGU6IC9ob21lL25jdnMvc3JjL3Vz ci5zYmluL2Z3Y29udHJvbC9md2NvbnRyb2wuYyx2CnJldHJpZXZpbmcgcmV2aXNpb24gMS4yMwpk aWZmIC11IC1yMS4yMyBmd2NvbnRyb2wuYwotLS0gZndjb250cm9sLmMJMjYgT2N0IDIwMDYgMjI6 MzM6MzggLTAwMDAJMS4yMworKysgZndjb250cm9sLmMJMjIgTWFyIDIwMDcgMTU6NTc6NDMgLTAw MDAKQEAgLTY0LDEwICs2NCwxMiBAQAogdXNhZ2Uodm9pZCkKIHsKIAlmcHJpbnRmKHN0ZGVyciwK LQkJImZ3Y29udHJvbCBbLXUgYnVzX251bV0gWy1ydF0gWy1nIGdhcF9jb3VudF0gWy1vIG5vZGVd ICIKKwkJImZ3Y29udHJvbCBbLXUgYnVzX251bV0gWy1ydF0gWy1mIG5vZGVdIFstZyBnYXBfY291 bnRdICIKKwkJICAgICJbLW8gbm9kZV0gIgogCQkgICAgIlstYiBwcmlfcmVxXSBbLWMgbm9kZV0g Wy1kIG5vZGVdIFstbCBmaWxlXSAiCiAJCSAgICAiWy1SIGZpbGVdIFstUyBmaWxlXSBbLW0gdGFy Z2V0XVxuIgogCQkiXHQtdTogc3BlY2lmeSBidXMgbnVtYmVyXG4iCisJCSJcdC1mOiBicm9hZGNh c3QgZm9yY2Vfcm9vdCBieSBwaHlfY29uZmlnIHBhY2tldFxuIgogCQkiXHQtZzogYnJvYWRjYXN0 IGdhcF9jb3VudCBieSBwaHlfY29uZmlnIHBhY2tldFxuIgogCQkiXHQtbzogc2VuZCBsaW5rLW9u IHBhY2tldCB0byB0aGUgbm9kZVxuIgogCQkiXHQtczogd3JpdGUgUkVTRVRfU1RBUlQgcmVnaXN0 ZXIgb24gdGhlIG5vZGVcbiIKQEAgLTE1MywyMCArMTU1LDIzIEBACiAJc3RydWN0IGZ3X2Rldmxz dHJlcSAqZGF0YTsKIAlzdHJ1Y3QgZndfZGV2aW5mbyAqZGV2aW5mbzsKIAlzdHJ1Y3QgZXVpNjQg ZXVpOwotCWNoYXIgYWRkcltFVUk2NF9TSVpdOworCWNoYXIgYWRkcltFVUk2NF9TSVpdLCBob3N0 bmFtZVs0MF07CiAJaW50IGk7CiAKIAlkYXRhID0gZ2V0X2RldihmZCk7CiAJcHJpbnRmKCIlZCBk ZXZpY2VzIChpbmZvX2xlbj0lZClcbiIsIGRhdGEtPm4sIGRhdGEtPmluZm9fbGVuKTsKLQlwcmlu dGYoIm5vZGUgICAgICAgICAgIEVVSTY0ICAgICAgICAgIHN0YXR1c1xuIik7CisJcHJpbnRmKCJu b2RlICAgICAgICAgICBFVUk2NCAgICAgICAgICBzdGF0dXMgICAgaG9zdG5hbWVcbiIpOwogCWZv ciAoaSA9IDA7IGkgPCBkYXRhLT5pbmZvX2xlbjsgaSsrKSB7CiAJCWRldmluZm8gPSAmZGF0YS0+ ZGV2W2ldOwogCQlmd2V1aTJldWk2NCgmZGV2aW5mby0+ZXVpLCAmZXVpKTsKIAkJZXVpNjRfbnRv YSgmZXVpLCBhZGRyLCBzaXplb2YoYWRkcikpOwotCQlwcmludGYoIiU0ZCAgJXMgJTZkXG4iLAor CSAgICAgICAgaWYgKGV1aTY0X250b2hvc3QoaG9zdG5hbWUsIHNpemVvZihob3N0bmFtZSksICZl dWkpKQorCQkJaG9zdG5hbWVbMF0gPSAwOworCQlwcmludGYoIiU0ZCAgJXMgJTZkICAgICVzXG4i LAogCQkJKGRldmluZm8tPnN0YXR1cyB8fCBpID09IDApID8gZGV2aW5mby0+ZHN0IDogLTEsCiAJ CQlhZGRyLAotCQkJZGV2aW5mby0+c3RhdHVzCisJCQlkZXZpbmZvLT5zdGF0dXMsCisJCQlob3N0 bmFtZQogCQkpOwogCX0KIAlmcmVlKCh2b2lkICopZGF0YSk7CkBAIC0xOTgsNyArMjAzLDcgQEAK IAogCXFsZCA9ICh1X2ludDMyX3QgKikmYXN5cmVxLT5wa3Q7CiAJaWYgKCFyZWFkbW9kZSkKLQkJ YXN5cmVxLT5wa3QubW9kZS53cmVxcS5kYXRhID0gZGF0YTsKKwkJYXN5cmVxLT5wa3QubW9kZS53 cmVxcS5kYXRhID0gaHRvbmwoZGF0YSk7CiAKIAlpZiAoaW9jdGwoZmQsIEZXX0FTWVJFUSwgYXN5 cmVxKSA8IDApIHsKICAgICAgICAJCWVycigxLCAiaW9jdGwiKTsKQEAgLTQ3MSwxNiArNDc2LDQy IEBACiAJcHJpbnRmKCJjcmNfbGVuOiAlZCBnZW5lcmF0aW9uOiVkIG5vZGVfY291bnQ6JWQgc2lk X2NvdW50OiVkXG4iLAogCQl0bWFwLT5jcmNfbGVuLCB0bWFwLT5nZW5lcmF0aW9uLAogCQl0bWFw LT5ub2RlX2NvdW50LCB0bWFwLT5zZWxmX2lkX2NvdW50KTsKLQlwcmludGYoImlkIGxpbmsgZ2Fw X2NudCBzcGVlZCBkZWxheSBjSVJNIHBvd2VyIHBvcnQwIHBvcnQxIHBvcnQyIgotCQkiIGluaSBt b3JlXG4iKTsKKwlwcmludGYoImlkICBsaW5rIGdhcCBzcGVlZCBkZWxheSBjSVJNIHBvd2VyIGlu aSBtb3JlICAiCisJCSJwb3J0cyAgICAgICAgICAwMCAwMSAwMlxuIik7CisJcHJpbnRmKCIgICAg IgorCQkiICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIgorCQkiMDMg MDQgMDUgMDYgMDcgMDggMDkgMTBcbiIpOworI2lmIDAKKwlwcmludGYoIiAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAiCisJCSIxMSAxMiAxMyAxNCAxNSAxNiAx NyAxOFxuIik7CisJcHJpbnRmKCIgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgIgorCQkiMTkgMjAgMjEgMjIgMjMgMjQgMjUgMjZcbiIpOworI2VuZGlmCisJcHJp bnRmKCItLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSIKKwkJIi0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tXG4iKTsKIAlmb3IgKGkgPSAwOyBpIDwgdG1hcC0+Y3Jj X2xlbiAtIDI7IGkrKykgewogCQlzaWQgPSB0bWFwLT5zZWxmX2lkW2ldOwogCQlpZiAoc2lkLnAw LnNlcXVlbCkgewotCQkJcHJpbnRmKCIlMDJkIHNlcXVlbCBwYWNrZXRcbiIsIHNpZC5wMC5waHlf aWQpOworCQkJcHJpbnRmKCIlMmQoJWQpIgorCQkJCSIgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICIKKwkJCQkiJWQgICAiCisJCQkJIiVzICAlcyAgJXMgICVzICAlcyAgJXMg ICVzICAlc1xuIiwKKwkJCQlzaWQucDEucGh5X2lkLAorCQkJCXNpZC5wMS5zZXF1ZW5jZV9udW0s CisJCQkJc2lkLnAxLm1vcmVfcGFja2V0cywKKwkJCQlwb3J0X3N0YXR1c1tzaWQucDEucG9ydGFd LAorCQkJCXBvcnRfc3RhdHVzW3NpZC5wMS5wb3J0Yl0sCisJCQkJcG9ydF9zdGF0dXNbc2lkLnAx LnBvcnRjXSwKKwkJCQlwb3J0X3N0YXR1c1tzaWQucDEucG9ydGRdLAorCQkJCXBvcnRfc3RhdHVz W3NpZC5wMS5wb3J0ZV0sCisJCQkJcG9ydF9zdGF0dXNbc2lkLnAxLnBvcnRmXSwKKwkJCQlwb3J0 X3N0YXR1c1tzaWQucDEucG9ydGddLAorCQkJCXBvcnRfc3RhdHVzW3NpZC5wMS5wb3J0aF0KKwkJ CSk7CiAJCQljb250aW51ZTsKIAkJfQotCQlwcmludGYoIiUwMmQgICAlMmQgICAgICAlMmQgICU0 cyAgICAgJWQgICAgJWQgICAlM3MiCi0JCQkJIiAgICAgJXMgICAgICVzICAgICAlcyAgICVkICAg ICVkXG4iLAorCQlwcmludGYoIiUyZCAgICAlMmQgICUyZCAgJTRzICAgICAlZCAgICAlZCAgICUz cyAgICVkICAgICVkIgorCQkJCSIgICAgICAgICAgICAgICAgICAlcyAgJXMgICVzXG4iLAogCQkJ c2lkLnAwLnBoeV9pZCwKIAkJCXNpZC5wMC5saW5rX2FjdGl2ZSwKIAkJCXNpZC5wMC5nYXBfY291 bnQsCkBAIC00ODgsMTEgKzUxOSwxMSBAQAogCQkJc2lkLnAwLnBoeV9kZWxheSwKIAkJCXNpZC5w MC5jb250ZW5kZXIsCiAJCQlwd3JfY2xhc3Nbc2lkLnAwLnBvd2VyX2NsYXNzXSwKKwkJCXNpZC5w MC5pbml0aWF0ZWRfcmVzZXQsCisJCQlzaWQucDAubW9yZV9wYWNrZXRzLAogCQkJcG9ydF9zdGF0 dXNbc2lkLnAwLnBvcnQwXSwKIAkJCXBvcnRfc3RhdHVzW3NpZC5wMC5wb3J0MV0sCi0JCQlwb3J0 X3N0YXR1c1tzaWQucDAucG9ydDJdLAotCQkJc2lkLnAwLmluaXRpYXRlZF9yZXNldCwKLQkJCXNp ZC5wMC5tb3JlX3BhY2tldHMKKwkJCXBvcnRfc3RhdHVzW3NpZC5wMC5wb3J0Ml0KIAkJKTsKIAl9 CiAJZnJlZSh0bWFwKTsKQEAgLTY3Niw3ICs3MDcsNyBAQAogCQlsaXN0X2RldihmZCk7CiAJfQog Ci0Jd2hpbGUgKChjaCA9IGdldG9wdChhcmdjLCBhcmd2LCAiTTpnOm06bzpzOmI6cHJ0YzpkOmw6 dTpSOlM6IikpICE9IC0xKQorCXdoaWxlICgoY2ggPSBnZXRvcHQoYXJnYywgYXJndiwgIk06Zjpn Om06bzpzOmI6cHJ0YzpkOmw6dTpSOlM6IikpICE9IC0xKQogCQlzd2l0Y2goY2gpIHsKIAkJY2Fz ZSAnYic6CiAJCQl0bXAgPSBzdHJ0b2wob3B0YXJnLCBOVUxMLCAwKTsKQEAgLTY5Nyw2ICs3Mjgs MTEgQEAKIAkJCWdldF9jcm9tKGZkLCB0bXAsIGNyb21fYnVmLCBsZW4pOwogCQkJZHVtcF9jcm9t KGNyb21fYnVmKTsKIAkJCWJyZWFrOworCQljYXNlICdmJzoKKwkJCXRtcCA9IHN0cnRvbChvcHRh cmcsIE5VTEwsIDApOworCQkJb3Blbl9kZXYoJmZkLCBkZXZiYXNlKTsKKwkJCXNlbmRfcGh5X2Nv bmZpZyhmZCwgdG1wLCAtMSk7CisJCQlicmVhazsKIAkJY2FzZSAnZyc6CiAJCQl0bXAgPSBzdHJ0 b2wob3B0YXJnLCBOVUxMLCAwKTsKIAkJCW9wZW5fZGV2KCZmZCwgZGV2YmFzZSk7Cg== ------=_Part_2102_8443763.1187837738266-- From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 03:03:54 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FBFE16A417 for ; Thu, 23 Aug 2007 03:03:54 +0000 (UTC) (envelope-from freebsd@gm.nunu.org) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.187]) by mx1.freebsd.org (Postfix) with ESMTP id 0EF2113C457 for ; Thu, 23 Aug 2007 03:03:54 +0000 (UTC) (envelope-from freebsd@gm.nunu.org) Received: by rv-out-0910.google.com with SMTP id l15so265974rvb for ; Wed, 22 Aug 2007 20:03:53 -0700 (PDT) Received: by 10.142.212.19 with SMTP id k19mr155848wfg.1187836640240; Wed, 22 Aug 2007 19:37:20 -0700 (PDT) Received: by 10.142.203.18 with HTTP; Wed, 22 Aug 2007 19:37:20 -0700 (PDT) Message-ID: <626eb4530708221937h31c8f37fu9527e941ed4000b6@mail.gmail.com> Date: Thu, 23 Aug 2007 11:37:20 +0900 From: "Hidetoshi Shimokawa" Sender: freebsd@gm.nunu.org To: "Bruce Cran" , "KOT MATPOCKuH" , gary.jennejohn@freenet.de In-Reply-To: <46BE1D6C.6040903@cran.org.uk> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_2094_784845.1187836640200" References: <3979a4b0707291120v4927a20cm357b845f6d1f3567@mail.gmail.com> <46BE1D6C.6040903@cran.org.uk> X-Google-Sender-Auth: a8ebb6138b44f2a6 Cc: current@freebsd.org Subject: Re: console hangs after setting hostname X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 03:03:54 -0000 ------=_Part_2094_784845.1187836640200 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline It looks that the low level console is not locked though the high level console is locked by Giant. Could you try the attached patch? On 8/12/07, Bruce Cran wrote: > KOT MATPOCKuH wrote: > > I got a problem. After messages on console: > > ... > > Mounting local files systems:. > > Setting hostname: green. > > fxp: link state changed to UP > > nfe0: link state changed to DOWN > > > > console hangs. > > No any new messages, I can't input anything from keyboard, changing virtual > > consoles is not working. After X is started, console is not switched to xdm > > display. > > But system is works - I can login to system via ssh, ... > > > > dmesg.boot is attached. > > > > Where is a problem and what I need to do? :) > > > > I'm also seeing the console hang, but in a different situation. If I > attach and remove my iPod the console hangs - the only key press that's > accepted is ctrl-alt-esc to break into the debugger. > > umass0: on uhub5 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-0 device > da0: 40.000MB/s transfers > da0: 19073MB (39063024 512 byte sectors: 255H 63S/T 2431C) > (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 2 54 d ef 0 0 1 0 > (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error > (da0:umass-sim0:0:0:0): SCSI Status: Check Condition > (da0:umass-sim0:0:0:0): ILLEGAL REQUEST asc:21,0 > (da0:umass-sim0:0:0:0): Logical block address out of range > (da0:umass-sim0:0:0:0): Unretryable error > (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 2 54 d ef 0 0 1 0 > (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error > (da0:umass-sim0:0:0:0): SCSI Status: Check Condition > (da0:umass-sim0:0:0:0): ILLEGAL REQUEST asc:21,0 > (da0:umass-sim0:0:0:0): Logical block address out of range > (da0:umass-sim0:0:0:0): Unretryable error > GEOM_LABEL: Label for provider da0s2 is msdosfs/IPOD. > > When I remove the iPod I get the following messages: > > umass0: at uhub5 port 1 (addr 2) disconnected > da0:umass-sim0:0:0G:0EO :M _LlAoBst L d ev aibceel > )m(sd ao0s:fs m/aIsPsO-Ds irme0m:o0v:ed :.0 > : removing device entry > umass0: detached > > enter: manual escape to debugger > [thread pid 19 tid 100018 ] > Stopped at kdb_enter+0x31: leave > db> wh > Tracing pid 19 tid 100018 td 0xffffff000112d350 > kdb_enter() > scgetc() > sckbdevent() > kbdmux_intr() > kdbmux_kdb_intr() > taskqueue_run() > taskqueue_swi_giant_run() > ithread_loop > fork_exit() > fork_trampoline() > --- trap 0, rip = 0, rsp = 0xffffffff9ca59d30, rbp = 0 --- > db> > > I'm using ULE. > uname -a: > FreeBSD muon.draftnet 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Sat Aug 11 > 21:07:09 BST 2007 > brucec@muon.draftnet:/usr/obj/usr/src/sys/INSPIRON amd64 > > -- > Bruce Cran > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- /\ Hidetoshi Shimokawa \/ simokawa@FreeBSD.ORG ------=_Part_2094_784845.1187836640200 Content-Type: application/octet-stream; name=syscons-lock Content-Transfer-Encoding: base64 X-Attachment-Id: f_f5on65lt Content-Disposition: attachment; filename="syscons-lock" SW5kZXg6IHN5c2NvbnMuYwo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09ClJDUyBmaWxlOiAvaG9tZS9uY3ZzL3NyYy9zeXMv ZGV2L3N5c2NvbnMvc3lzY29ucy5jLHYKcmV0cmlldmluZyByZXZpc2lvbiAxLjQ1MQpkaWZmIC11 IC1yMS40NTEgc3lzY29ucy5jCi0tLSBzeXNjb25zLmMJNCBKdW4gMjAwNyAyMzo1NzozMCAtMDAw MAkxLjQ1MQorKysgc3lzY29ucy5jCTIzIEF1ZyAyMDA3IDAyOjE0OjM5IC0wMDAwCkBAIC0yNTEx LDE0ICsyNTExLDIzIEBACiB2b2lkCiBzY19wdXRzKHNjcl9zdGF0ICpzY3AsIHVfY2hhciAqYnVm LCBpbnQgbGVuKQogeworICAgIGludCBuZWVkX3VubG9jayA9IDA7CisKICNpZmRlZiBERVZfU1BM QVNICiAgICAgLyogbWFrZSBzY3JlZW5zYXZlciBoYXBweSAqLwogICAgIGlmICghc3RpY2t5X3Nw bGFzaCAmJiBzY3AgPT0gc2NwLT5zYy0+Y3VyX3NjcCAmJiAhc2Nfc2F2ZXJfa2V5Yl9vbmx5KQog CXJ1bl9zY3JuX3NhdmVyID0gRkFMU0U7CiAjZW5kaWYKIAotICAgIGlmIChzY3AtPnRzdykKKyAg ICBpZiAoc2NwLT50c3cpIHsKKwlpZiAoIWtkYl9hY3RpdmUgJiYgIW10eF9vd25lZCgmc2NwLT5z Y3JfbG9jaykpIHsKKwkJbmVlZF91bmxvY2sgPSAxOworCQltdHhfbG9ja19zcGluKCZzY3AtPnNj cl9sb2NrKTsKKwl9CiAJKCpzY3AtPnRzdy0+dGVfcHV0cykoc2NwLCBidWYsIGxlbik7CisJaWYg KG5lZWRfdW5sb2NrKQorCQltdHhfdW5sb2NrX3NwaW4oJnNjcC0+c2NyX2xvY2spOworICAgIH0K IAogICAgIGlmIChzY3AtPnNjLT5kZWxheWVkX25leHRfc2NyKQogCXNjX3N3aXRjaF9zY3Ioc2Nw LT5zYywgc2NwLT5zYy0+ZGVsYXllZF9uZXh0X3NjciAtIDEpOwpAQCAtMjg5Niw2ICsyOTA1LDcg QEAKIAkoKnNjcC0+dHN3LT50ZV90ZXJtKShzY3AsICZzY3AtPnRzKTsKICAgICBpZiAoc2NwLT50 cyAhPSBOVUxMKQogCWZyZWUoc2NwLT50cywgTV9ERVZCVUYpOworICAgIG10eF9kZXN0cm95KCZz Y3AtPnNjcl9sb2NrKTsKIAogICAgIC8qIGNsZWFyIHRoZSBzdHJ1Y3R1cmUgKi8KICAgICBpZiAo IShmbGFncyAmIFNDX0tFUk5FTF9DT05TT0xFKSkgewpAQCAtMzA3OSw2ICszMDg5LDggQEAKICAg ICBzY3AtPmhpc3RvcnkgPSBOVUxMOwogICAgIHNjcC0+aGlzdG9yeV9wb3MgPSAwOwogICAgIHNj cC0+aGlzdG9yeV9zaXplID0gMDsKKworICAgIG10eF9pbml0KCZzY3AtPnNjcl9sb2NrLCAic2Ny bG9jayIsIE5VTEwsIE1UWF9TUElOKTsKIH0KIAogaW50CkluZGV4OiBzeXNjb25zLmgKPT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PQpSQ1MgZmlsZTogL2hvbWUvbmN2cy9zcmMvc3lzL2Rldi9zeXNjb25zL3N5c2NvbnMuaCx2 CnJldHJpZXZpbmcgcmV2aXNpb24gMS44NwpkaWZmIC11IC1yMS44NyBzeXNjb25zLmgKLS0tIHN5 c2NvbnMuaAkxMyBTZXAgMjAwNiAxNTo0ODoxNSAtMDAwMAkxLjg3CisrKyBzeXNjb25zLmgJMjMg QXVnIDIwMDcgMDI6MzA6MTggLTAwMDAKQEAgLTMzMyw2ICszMzMsNyBAQAogCiAJaW50CQlzcGxh c2hfc2F2ZV9tb2RlOwkvKiBzYXZlZCBtb2RlIGZvciBzcGxhc2ggc2NyZWVuICovCiAJaW50CQlz cGxhc2hfc2F2ZV9zdGF0dXM7CS8qIHNhdmVkIHN0YXR1cyBmb3Igc3BsYXNoIHNjcmVlbiAqLwor CXN0cnVjdCBtdHgJc2NyX2xvY2s7CQkvKiBtdXRleCBmb3Igc2NfcHV0cygpICovCiAjaWZkZWYg X1NDUl9NRF9TVEFUX0RFQ0xBUkVEXwogCXNjcl9tZF9zdGF0X3QJbWQ7CQkJLyogbWFjaGluZSBk ZXBlbmRlbnQgdmFycyAqLwogI2VuZGlmCg== ------=_Part_2094_784845.1187836640200-- From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 05:42:25 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF75816A420 for ; Thu, 23 Aug 2007 05:42:25 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Received: from mail.asahi-net.or.jp (mail1.asahi-net.or.jp [202.224.39.197]) by mx1.freebsd.org (Postfix) with ESMTP id 92BB413C467 for ; Thu, 23 Aug 2007 05:42:25 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Received: from pavillion-freebsd.advok.com (pool-141-151-77-139.phlapa.east.verizon.net [141.151.77.139]) by mail.asahi-net.or.jp (Postfix) with ESMTP id 6974E541C4 for ; Thu, 23 Aug 2007 14:42:23 +0900 (JST) Date: Thu, 23 Aug 2007 01:42:14 -0400 From: Yoshihiro Ota To: freebsd-current@freebsd.org Message-Id: <20070823014214.a869857a.ota@j.email.ne.jp> X-Mailer: Sylpheed 2.4.0 (GTK+ 2.10.12; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: What is the status of UTF-8 support? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 05:42:25 -0000 About a year ago, I used some paches from the following link to use UTF-8, for namely smbfs. http://people.freebsd.org/~imura/kiconv/ Does anyone know the current status of unicode/utf-8 handling in the filesystems in the CURRENT? Are these patches applied? Did anyone do anything else on multi-byte related issues? Thanks, Hiro From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 07:11:23 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB64E16A41B for ; Thu, 23 Aug 2007 07:11:23 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by mx1.freebsd.org (Postfix) with ESMTP id ADE3E13C4A7 for ; Thu, 23 Aug 2007 07:11:23 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp5-g19.free.fr (localhost.localdomain [127.0.0.1]) by smtp5-g19.free.fr (Postfix) with ESMTP id 607ED5FCA; Thu, 23 Aug 2007 09:11:22 +0200 (CEST) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp5-g19.free.fr (Postfix) with ESMTP id 5B2BC35BBB; Thu, 23 Aug 2007 09:11:21 +0200 (CEST) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id CB4BD9B497; Thu, 23 Aug 2007 07:10:56 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id B9E9D405B; Thu, 23 Aug 2007 09:10:56 +0200 (CEST) Date: Thu, 23 Aug 2007 09:10:56 +0200 From: Jeremie Le Hen To: Ulf Lilleengen Message-ID: <20070823071056.GA50852@obiwan.tataz.chchile.org> References: <46BFE620.8070906@fusiongol.com> <20070813091802.GB3078@stud.ntnu.no> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070813091802.GB3078@stud.ntnu.no> User-Agent: Mutt/1.5.15 (2007-04-06) Cc: Nathan Butcher , freebsd-current@freebsd.org Subject: Re: Promise SATA 300 TX4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 07:11:24 -0000 Hi Ulf, On Mon, Aug 13, 2007 at 11:18:02AM +0200, Ulf Lilleengen wrote: > I have problems with this card in -CURRENT too. Details can be found > here: > http://lists.freebsd.org/pipermail/freebsd-current/2007-July/074960.html > > I never bothered trying with earlier versions of -CURRENT, but it > works good in 6.2. I'm planning to switch my own server from 6.2 to -CURRENT soon. Are you still experiencing such problems? Thank you. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 08:16:14 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9573216A418 for ; Thu, 23 Aug 2007 08:16:14 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from smtp02.dentaku.gol.com (smtp02.dentaku.gol.com [203.216.5.72]) by mx1.freebsd.org (Postfix) with ESMTP id 6415B13C442 for ; Thu, 23 Aug 2007 08:16:14 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from pat.gol.co.jp ([203.216.1.191] helo=[127.0.0.1]) by smtp02.dentaku.gol.com with esmtpa (Dentaku) id 1IO7rD-0000em-Bp; Thu, 23 Aug 2007 17:15:59 +0900 Message-ID: <46CD423F.9070104@fusiongol.com> Date: Thu, 23 Aug 2007 17:15:59 +0900 From: Nathan Butcher User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Jeremie Le Hen References: <46BFE620.8070906@fusiongol.com> <20070813091802.GB3078@stud.ntnu.no> <20070823071056.GA50852@obiwan.tataz.chchile.org> In-Reply-To: <20070823071056.GA50852@obiwan.tataz.chchile.org> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Abuse-Complaints: abuse@gol.com Cc: freebsd-current@freebsd.org, Ulf Lilleengen Subject: Re: Promise SATA 300 TX4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 08:16:14 -0000 It's still acting erratic, as of 10 hours ago when I last did a buildworld and buildkernel. I noticed some changes in the vm code during the update, but it didn't solve the problem. Jeremie Le Hen wrote: > Hi Ulf, > > On Mon, Aug 13, 2007 at 11:18:02AM +0200, Ulf Lilleengen wrote: >> I have problems with this card in -CURRENT too. Details can be found >> here: >> http://lists.freebsd.org/pipermail/freebsd-current/2007-July/074960.html >> >> I never bothered trying with earlier versions of -CURRENT, but it >> works good in 6.2. > > I'm planning to switch my own server from 6.2 to -CURRENT soon. > Are you still experiencing such problems? > > Thank you. > Regards, From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 08:27:34 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A43A16A421 for ; Thu, 23 Aug 2007 08:27:34 +0000 (UTC) (envelope-from h.schmalzbauer@omnisec.de) Received: from host.omnisec.de (host.omnisec.de [62.245.232.135]) by mx1.freebsd.org (Postfix) with ESMTP id 7CA7613C4B0 for ; Thu, 23 Aug 2007 08:27:31 +0000 (UTC) (envelope-from h.schmalzbauer@omnisec.de) Received: from tek.flintsbach.schmalzbauer.de (tek.flintsbach.schmalzbauer.de [172.21.2.3]) by host.omnisec.de (8.13.8/8.13.8) with ESMTP id l7N8ROZm042679 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 23 Aug 2007 10:27:29 +0200 (CEST) (envelope-from h.schmalzbauer@omnisec.de) Received: from titan.flintsbach.schmalzbauer.de (titan.flintsbach.schmalzbauer.de [IPv6:fec0::1:0:0:1:1]) by tek.flintsbach.schmalzbauer.de (8.13.8/8.13.8) with ESMTP id l7N8ROUq091033 for ; Thu, 23 Aug 2007 10:27:24 +0200 (CEST) (envelope-from h.schmalzbauer@omnisec.de) Received: from localhost (localhost [[UNIX: localhost]]) by titan.flintsbach.schmalzbauer.de (8.14.1/8.14.1/Submit) id l7N8S7Vg010241 for freebsd-current@freebsd.org; Thu, 23 Aug 2007 10:28:07 +0200 (CEST) (envelope-from h.schmalzbauer@omnisec.de) X-Authentication-Warning: titan.flintsbach.schmalzbauer.de: harry set sender to h.schmalzbauer@omnisec.de using -f From: Harald Schmalzbauer Organization: OmniSEC To: freebsd-current@freebsd.org Date: Thu, 23 Aug 2007 10:28:07 +0200 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200708231028.07743.h.schmalzbauer@omnisec.de> Subject: ichwd and teethless watchdogd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 08:27:34 -0000 Hello, I had tested the ich 6/7/8 ichwd patch some months ago on a ich7 FSC machine and it worked fine. On my ich8 desktop probing found ichwd0 but it didn't work. My new ich9 machine doesn't show ichwd0. But now (with -current after imported ichwd patch) I also have problems on an Intel Server board with ich7. SIGKILL to watchdogd should reboot the machine, right? It doesn't, but probing reports two times ichwd0. How can I find out what's going on? Can I watch the dog watching? Best regards, -Harry From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 10:17:39 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41A7416A41B for ; Thu, 23 Aug 2007 10:17:39 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mx1.freebsd.org (Postfix) with ESMTP id B86C913C442 for ; Thu, 23 Aug 2007 10:17:38 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l7NAHbDj001749 for ; Thu, 23 Aug 2007 20:17:37 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l7NAHbUB001748 for freebsd-current@freebsd.org; Thu, 23 Aug 2007 20:17:37 +1000 (EST) (envelope-from peter) Date: Thu, 23 Aug 2007 20:17:37 +1000 From: Peter Jeremy To: freebsd-current@freebsd.org Message-ID: <20070823101737.GA1161@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k1lZvvs/B4yU6o8G" Content-Disposition: inline X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.16 (2007-06-09) Subject: idprio(1) broken in recent -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 10:17:39 -0000 --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Following my latest -current update (to 17th August), setiathome stopped working and started complaining about missing heartbeats. After rebuilding all the ports and a bit of hair removal, I tracked the problem to the 'idprio' command in /usr/local/etc/rc.d/boinc - without that, all works fine. If I include that, boinc_client stops sending heartbeat messages. This was working correctly in late June. Has anyone else seen anything similar? --=20 Peter Jeremy --k1lZvvs/B4yU6o8G Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGzV7B/opHv/APuIcRAn3GAJ4pKxxh7BXBLbZmjEBsGbmIo2avhwCcDFPj HNy2yslOMLHSGLIaIfwJCy4= =tlN9 -----END PGP SIGNATURE----- --k1lZvvs/B4yU6o8G-- From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 10:18:09 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06D9D16A41A for ; Thu, 23 Aug 2007 10:18:09 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id B7B7013C4A3 for ; Thu, 23 Aug 2007 10:18:08 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id AA8C220B0; Thu, 23 Aug 2007 12:18:04 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 2AF56208A; Thu, 23 Aug 2007 12:18:04 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id 05FD184479; Thu, 23 Aug 2007 12:18:04 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Harald Schmalzbauer References: <200708231028.07743.h.schmalzbauer@omnisec.de> Date: Thu, 23 Aug 2007 12:18:03 +0200 In-Reply-To: <200708231028.07743.h.schmalzbauer@omnisec.de> (Harald Schmalzbauer's message of "Thu\, 23 Aug 2007 10\:28\:07 +0200") Message-ID: <86r6lu1rms.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: ichwd and teethless watchdogd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 10:18:09 -0000 Harald Schmalzbauer writes: > I had tested the ich 6/7/8 ichwd patch some months ago on a ich7 FSC > machine and it worked fine. On my ich8 desktop probing found ichwd0 > but it didn't work. My new ich9 machine doesn't show ichwd0. It should work on ICH9 if you add the correct PCI ID. > But now (with -current after imported ichwd patch) I also have > problems on an Intel Server board with ich7. SIGKILL to watchdogd > should reboot the machine, right? Yes. > It doesn't, but probing reports two times ichwd0. A verbose dmesg would be nice. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 10:40:19 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F030316A419 for ; Thu, 23 Aug 2007 10:40:19 +0000 (UTC) (envelope-from jgordeev@dir.bg) Received: from dir.bg (mail.dir.bg [194.145.63.28]) by mx1.freebsd.org (Postfix) with ESMTP id 4737213C45B for ; Thu, 23 Aug 2007 10:40:18 +0000 (UTC) (envelope-from jgordeev@dir.bg) Received: from [87.126.192.227] (account jgordeev HELO [10.102.9.50]) by dir.bg (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 29888919; Thu, 23 Aug 2007 13:40:16 +0300 Message-ID: <46CD643F.9040003@dir.bg> Date: Thu, 23 Aug 2007 13:41:03 +0300 From: Jordan Gordeev User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20070606 X-Accept-Language: bg, en MIME-Version: 1.0 To: Stefan Lambrev References: <46C18B60.8050400@moneybookers.com> <20070814145759.GB25169@void.codelabs.ru> <20070814193150.GA21553@rot26.obsecurity.org> <46C30FA6.7060108@moneybookers.com> <20070815145640.GQ988@void.codelabs.ru> <46C319DD.3010806@moneybookers.com> <20070815172731.GR988@void.codelabs.ru> <46C3FEBC.80409@moneybookers.com> <20070816080516.GW988@void.codelabs.ru> <46C55684.4050402@moneybookers.com> <20070817083135.GM988@void.codelabs.ru> <46C97E13.3080002@moneybookers.com> In-Reply-To: <46C97E13.3080002@moneybookers.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: "tcpflags 0x18; tcp_do_segment" kernel messages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 10:40:20 -0000 Stefan Lambrev wrote: > Hello Eygene, > > Eygene Ryabinkin wrote: > >> Stefan, good day. >> >> Fri, Aug 17, 2007 at 11:04:20AM +0300, Stefan Lambrev wrote: >> >> >>> Their response is that the mail server timeout. >>> >> >> >> And how they are detecting the timeout? They are using alarm(), >> just polling for the time with non-blocking read calls, setting the >> socket timeout or something else? >> > > They do not provide such information. > But they have some kind of cronjob to restart the program if the PHP > script stall, which makes me think > that it is not something very rare in this case. > I'm still waiting better response from their support team and if this > happened will let you know. Stefan, you can use ktrace to see what the program's doing and what it is getting from the kernel. I think the ktrace output + the tcpdump packet trace will be quite useful in tracking the problem down. > >> >> >>> Now the question is why the program things that the server timeouts >>> when it does not :) >>> >> >> >> May be this is connected to the socket timeout stuff: chances are >> good that the PHP program uses apr_socket_timeout_set(), so there >> can be issues with SO_SNDTIMEO/SO_RCVTIMEO socket options in the >> -CURRENT. At least Apache (that I have problems with) sets keep-alived >> sockets with apr_socket_timeout_set(). I will try to have a look >> if this can be true. >> >> Thanks for your information! >> >> Mike, Robert, there are chances that some timeout code behaves >> weirdly. And maybe the magic number 3 (every 3rd keep-alived >> connection seems to be dropped due to the timeout, Stefan sees it >> too) should be searched in the timeout code. Maybe you can give >> some hints or point to the exact place where the error can occur? >> >> Thank you. >> > > From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 12:31:57 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 723FB16A417 for ; Thu, 23 Aug 2007 12:31:57 +0000 (UTC) (envelope-from Johan@double-l.nl) Received: from smtp-vbr15.xs4all.nl (smtp-vbr15.xs4all.nl [194.109.24.35]) by mx1.freebsd.org (Postfix) with ESMTP id 0CC4913C45A for ; Thu, 23 Aug 2007 12:31:56 +0000 (UTC) (envelope-from Johan@double-l.nl) Received: from w2003s01.double-l.local (dpm.xs4all.nl [213.84.11.61]) by smtp-vbr15.xs4all.nl (8.13.8/8.13.8) with ESMTP id l7NCVtXE015426; Thu, 23 Aug 2007 14:31:55 +0200 (CEST) (envelope-from Johan@double-l.nl) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Thu, 23 Aug 2007 14:31:54 +0200 Message-ID: <57200BF94E69E54880C9BB1AF714BBCB19BC8D@w2003s01.double-l.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Can't create TCP connections to certain IP addresses Thread-Index: Acfk90dSN43olv8fRX6tOa/xr4m+GwAigIIQ References: <200708210928.aa80674@walton.maths.tcd.ie> <200708221602.42191.mistry.7@osu.edu> From: "Johan Hendriks" To: "Anish Mistry" X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-current@freebsd.org Subject: RE: Can't create TCP connections to certain IP addresses X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 12:31:57 -0000 On Tuesday 21 August 2007, David Malone wrote: >> > What's the PR number? >> >> The PR that I am thinking of is: >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=3Di386/69257 >> >> > COPTFLAGS+=3D-O2 >> > CPUTYPE=3Di586/mmx >> >> I guess you may not be directly be effected, as you're using -O2, but >> it might be another interaction with gcc, so I'd try compiling a=20 >> kernel with -O, just to see if you get a different result. >> >> (Record the output of building the kernel, just to make sure it is=20 >> using the flags you think it is.) >I had to specify >CFLAGS=3D-O -pipe >in make.conf to force the kernel to build without -O2 even after removing the COPTFLAGS and CPUTYPE. >It's fixed now by forcing -O, but this seems to be a serious issue as -O2 is the default. Is this fixed in 4.2.1? And will that make it into >7.0? -- >Anish Mistry 4.2.1 is in at the moment. admin@beasty ~ $ gcc --version gcc (GCC) 4.2.1 20070719 [FreeBSD] Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Regards, Johan From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 09:28:08 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1725216A41B for ; Thu, 23 Aug 2007 09:28:08 +0000 (UTC) (envelope-from swildner@erpicon.de) Received: from beate.erpicon.de (port-87-234-219-38.static.qsc.de [87.234.219.38]) by mx1.freebsd.org (Postfix) with ESMTP id CAEBE13C45A for ; Thu, 23 Aug 2007 09:28:07 +0000 (UTC) (envelope-from swildner@erpicon.de) Received: from beate (localhost [127.0.0.1]) by beate (Postfix) with ESMTP id 7C5E9245EB for ; Thu, 23 Aug 2007 11:03:35 +0200 (CEST) Received: from [127.0.0.1] (unknown [194.49.16.5]) by beate.erpicon.de (Postfix) with ESMTP id 3F25424575 for ; Thu, 23 Aug 2007 11:03:35 +0200 (CEST) Message-ID: <46CD4D7B.1030100@erpicon.de> Date: Thu, 23 Aug 2007 11:03:55 +0200 From: Sascha Wildner User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <200708230030.05749.h.schmalzbauer@omnisec.de> In-Reply-To: <200708230030.05749.h.schmalzbauer@omnisec.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Anti-Virus: Kaspersky Anti-Virus for MailServers 5.5.10/RELEASE, bases: 23082007 #363495, status: clean X-Mailman-Approved-At: Thu, 23 Aug 2007 13:48:48 +0000 Subject: Re: vidcontrol modes for ATI ES1000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 09:28:08 -0000 Harald Schmalzbauer wrote: > Hello, > > I have a Intel Server Board S3000AHV, which has an ATI ES1000 VGA Chip with > 16B onboard. > I have SC_PIXEL_MODE and VESA in my kernel, but 'vidconsole -i mode' shows > only one! line: > > 24 (0x018) 0x00000001 T 80x25 8x16 0xb000 32k 32k 0x00000000 32k Could you try compiling with 'options VESA_DEBUG=2' and check if VESA reports any more modes in dmesg? There is a slight possibility that the card has mode numbers >0x1ff. Sascha From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 14:24:21 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9106A16A417 for ; Thu, 23 Aug 2007 14:24:21 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 4BA8E13C45D for ; Thu, 23 Aug 2007 14:24:21 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from mr08.lnh.mail.rcn.net ([207.172.157.28]) by smtp02.lnh.mail.rcn.net with ESMTP; 23 Aug 2007 10:24:21 -0400 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr08.lnh.mail.rcn.net (MOS 3.8.3-GA) with ESMTP id JAK38921; Thu, 23 Aug 2007 10:24:20 -0400 (EDT) Received: from 65-78-26-179.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([65.78.26.179]) by smtp01.lnh.mail.rcn.net with ESMTP; 23 Aug 2007 10:24:19 -0400 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18125.39066.727736.863664@jerusalem.litteratus.org> Date: Thu, 23 Aug 2007 10:24:26 -0400 To: freebsd-current@freebsd.org In-Reply-To: <20070823101737.GA1161@turion.vk2pj.dyndns.org> References: <20070823101737.GA1161@turion.vk2pj.dyndns.org> X-Mailer: VM 7.17 under 21.5 (beta28) "fuki" XEmacs Lucid X-Junkmail-Whitelist: YES (by domain whitelist at mr08.lnh.mail.rcn.net) Subject: idprio(1) broken in recent -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 14:24:21 -0000 Peter Jeremy writes: > Following my latest -current update (to 17th August), setiathome > stopped working and started complaining about missing heartbeats. > After rebuilding all the ports and a bit of hair removal, I > tracked the problem to the 'idprio' command in > /usr/local/etc/rc.d/boinc - without that, all works fine. If I > include that, boinc_client stops sending heartbeat messages. > > This was working correctly in late June. > > Has anyone else seen anything similar? Possibly. I updat4ed on the 20th, and since then boinc/seti has worked fitfully if at all; I haven't had time to investigate. Collateral issue: I tried to re-build boinc, which choked with: checking for curl-config... /usr/local/bin/curl-config checking for the version of libcurl... 7.16.1 checking for libcurl >= version 7.15.5... yes checking whether libcurl is usable... no configure: error: ================================================================================ ERROR: could not find (recent enough) development-libs for libcurl. This library is required to build the boinc-client. (If you don't want to build the client, use --disable-client with configure. If libcurl-dev is installed on your system, make sure that the script 'curl-config' is found in your PATH, and that 'curl-config --version' gives something recent enough (see above). You can download libcurl from: http://curl.haxx.se/ ================================================================================ ===> Script "configure" failed unexpectedly. Trying to rebuild (lib)curl failed, with a complaint about curl not playing nicely with libssh2. I have e-mailed the maintainer, but so far no response. (PR is "http://www.freebsd.org/cgi/query-pr.cgi?pr=114477") Robert Huff From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 15:29:28 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A95116A417 for ; Thu, 23 Aug 2007 15:29:28 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id CE40C13C468 for ; Thu, 23 Aug 2007 15:29:27 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id B0C9E47BA7; Thu, 23 Aug 2007 11:29:26 -0400 (EDT) Date: Thu, 23 Aug 2007 16:29:26 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Peter Jeremy In-Reply-To: <20070823101737.GA1161@turion.vk2pj.dyndns.org> Message-ID: <20070823162802.T2662@fledge.watson.org> References: <20070823101737.GA1161@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: idprio(1) broken in recent -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 15:29:28 -0000 On Thu, 23 Aug 2007, Peter Jeremy wrote: > Following my latest -current update (to 17th August), setiathome stopped > working and started complaining about missing heartbeats. After rebuilding > all the ports and a bit of hair removal, I tracked the problem to the > 'idprio' command in /usr/local/etc/rc.d/boinc - without that, all works > fine. If I include that, boinc_client stops sending heartbeat messages. > > This was working correctly in late June. > > Has anyone else seen anything similar? When I run "idprio 20 echo hi", it seems to execute per normal as root, and not at all as an unprivileged user, which I think is the desired symptom of using it. I've not tried checking that things execute occasionally with a mostly busy system, so could you be more specific about what you're seeing? If you're running things with idprio, is it definitely the case that your system is sometimes idle allowing the program to run once in a while? Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 15:32:59 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0DBF416A420 for ; Thu, 23 Aug 2007 15:32:59 +0000 (UTC) (envelope-from lveax.m@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.238]) by mx1.freebsd.org (Postfix) with ESMTP id BEFF813C442 for ; Thu, 23 Aug 2007 15:32:58 +0000 (UTC) (envelope-from lveax.m@gmail.com) Received: by wr-out-0506.google.com with SMTP id 70so393713wra for ; Thu, 23 Aug 2007 08:32:58 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=EuPpsU5MpLjyc0YVC11Zdlg4rsEsV0Luj5ywjV3IALZmHMZVN3Wdvg6IGvIRXxYftBPaayEvpNSs7DG++pUhdl/6srhJQ8dbmIl+6QDXcufrw37iNKHMzxk8QzUc3fYJze6s1K+b1yzaDqyLo9AK/NtOlCndboPhNnFs2Fx73Kg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SlVqPFEjvwj4nVrH24bbcgHdyBU7aqUkg7G54OX4rYTq0IU/+53dLK5ejvtcybbG7mA9prhuC9XfP3GiKo4LFDlDEjdFnjNXassVU01Dyp8QdTrP4hSgpjvaDYvbusFsT3LI7Ke70kJp/6TADigRM4SI8k0NGw2UOSmRAJNRZeY= Received: by 10.90.71.3 with SMTP id t3mr61353aga.1187881572821; Thu, 23 Aug 2007 08:06:12 -0700 (PDT) Received: by 10.90.86.8 with HTTP; Thu, 23 Aug 2007 08:06:12 -0700 (PDT) Message-ID: <576dcbc20708230806y1eabe48cpdd90e14033243389@mail.gmail.com> Date: Thu, 23 Aug 2007 23:06:12 +0800 From: lveax To: "Yoshihiro Ota" In-Reply-To: <20070823014214.a869857a.ota@j.email.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070823014214.a869857a.ota@j.email.ne.jp> Cc: freebsd-current@freebsd.org Subject: Re: What is the status of UTF-8 support? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 15:32:59 -0000 On 8/23/07, Yoshihiro Ota wrote: > About a year ago, I used some paches from the following link > to use UTF-8, for namely smbfs. > > http://people.freebsd.org/~imura/kiconv/ > > > Does anyone know the current status of unicode/utf-8 handling > in the filesystems in the CURRENT? > > Are these patches applied? > > Did anyone do anything else on multi-byte related issues? > > Thanks, > Hiro seems these patches were didn't applied.. i also have multi-byte related issues,i'm a chinese user. i sent a mail to imura@ a couple of months algo,but there is no reply. ;( From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 17:19:42 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2C1A16A421 for ; Thu, 23 Aug 2007 17:19:42 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.226]) by mx1.freebsd.org (Postfix) with ESMTP id A087613C48D for ; Thu, 23 Aug 2007 17:19:42 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so334729nzf for ; Thu, 23 Aug 2007 10:19:42 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=Q7Yutgxt4gBrnpKkMJ4QtAjA6hDxLtGQ/fQLLICN6NqpxS2CvpY13YQa08MhPL05LzTMwezNBePTWowKmWPIx0UWrkUSb4lMOtvPzx+rHFlsH3asxAS7ph14itd/HSBu78y6LmktYjDBc8AoWbAG3o8uglOB2ZZ7ustzjTF/Ya0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LjweeftCPP7gvZ210uY4vhekh1kXljUjx2y7eSDZJeOn6sh/RGGrv0CJh6oaTQdWtP39JL36jz5zFfI/fSWuS8fMBR5yqh0+4Mg8EfTwenbyZA/ud0QTF+ZkmbQyvlAYYWstYmaihX5bfcp3Gf7J9WBBk11vYjMXuh5b4XcNLBM= Received: by 10.115.33.1 with SMTP id l1mr15963waj.1187887949224; Thu, 23 Aug 2007 09:52:29 -0700 (PDT) Received: by 10.66.238.4 with HTTP; Thu, 23 Aug 2007 09:52:29 -0700 (PDT) Message-ID: <3aaaa3a0708230952p331e924vbba57b1f02454412@mail.gmail.com> Date: Thu, 23 Aug 2007 17:52:29 +0100 From: Chris To: "Oliver Fromme" In-Reply-To: <200708090850.l798oJfL089684@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20070809092710.papk9jozk0kswgcg@webmail.leidinger.net> <200708090850.l798oJfL089684@lurza.secnetix.de> Cc: Alexander Leidinger , freebsd-current@freebsd.org, dan@danneh.org Subject: Re: nfe(4) issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 17:19:43 -0000 On 09/08/07, Oliver Fromme wrote: > > Alexander Leidinger wrote: > > Tony Holmes wrote: > > > Let me add a "I concur" to this. I upgaded to 7-current 4 weeks ago > > > for this very reason and I have been pleased with the stability and > > > performance. I have enough confidence to deploy into production in > > > the next couple of weeks. > > > > gcc 4.2.0 in -current has known defects. > > Yes, I know, that's why the default optimization setting > in 7-current has been changed from -O2 to -O1 recently, > until gcc 4.2.1 is in the tree. With -O1 I haven't > encountered any problems so far ... Of course that > doesn't mean there aren't any problems. But I'm > actually very confident right now. :-) > > Best regards > Oliver > > -- > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. > Handelsregister: Registergericht Muenchen, HRA 74606, Gesch=E4ftsfuehrun= g: > secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M=FC= n- > chen, HRB 125758, Gesch=E4ftsf=FChrer: Maik Bachmann, Olaf Erb, Ralf Geb= hart > > FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd > > "And believe me, as a C++ programmer, I don't hesitate to question > the decisions of language designers. After a decent amount of C++ > exposure, Python's flaws seem ridiculously small." -- Ville Vainio > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > Is there a good reason why 7.0 is going to be released using a bad version of gcc? or is 4.2.1 going in before release? Chris From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 17:23:08 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC99D16A41B for ; Thu, 23 Aug 2007 17:23:08 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (cl-162.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:a1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2C30C13C467 for ; Thu, 23 Aug 2007 17:23:08 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.13.8/8.13.8) with ESMTP id l7NHN4bu097540; Thu, 23 Aug 2007 12:23:05 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.13.8/8.13.8/Submit) id l7NHN494097539; Thu, 23 Aug 2007 12:23:04 -0500 (CDT) (envelope-from brooks) Date: Thu, 23 Aug 2007 12:23:04 -0500 From: Brooks Davis To: Chris Message-ID: <20070823172304.GA97274@lor.one-eyed-alien.net> References: <20070809092710.papk9jozk0kswgcg@webmail.leidinger.net> <200708090850.l798oJfL089684@lurza.secnetix.de> <3aaaa3a0708230952p331e924vbba57b1f02454412@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qDbXVdCdHGoSgWSk" Content-Disposition: inline In-Reply-To: <3aaaa3a0708230952p331e924vbba57b1f02454412@mail.gmail.com> User-Agent: Mutt/1.5.15 (2007-04-06) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Thu, 23 Aug 2007 12:23:05 -0500 (CDT) Cc: Alexander Leidinger , freebsd-current@freebsd.org, Oliver Fromme , dan@danneh.org Subject: Re: nfe(4) issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 17:23:08 -0000 --qDbXVdCdHGoSgWSk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 23, 2007 at 05:52:29PM +0100, Chris wrote: > On 09/08/07, Oliver Fromme wrote: > > > > Alexander Leidinger wrote: > > > Tony Holmes wrote: > > > > Let me add a "I concur" to this. I upgaded to 7-current 4 weeks ago > > > > for this very reason and I have been pleased with the stability and > > > > performance. I have enough confidence to deploy into production in > > > > the next couple of weeks. > > > > > > gcc 4.2.0 in -current has known defects. > > > > Yes, I know, that's why the default optimization setting > > in 7-current has been changed from -O2 to -O1 recently, > > until gcc 4.2.1 is in the tree. With -O1 I haven't > > encountered any problems so far ... Of course that > > doesn't mean there aren't any problems. But I'm > > actually very confident right now. :-) > > > > Best regards > > Oliver > > > > -- > > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. = M. > > Handelsregister: Registergericht Muenchen, HRA 74606, Gesch?ftsfuehrun= g: > > secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M?= n- > > chen, HRB 125758, Gesch?ftsf?hrer: Maik Bachmann, Olaf Erb, Ralf Gebha= rt > > > > FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/b= sd > > > > "And believe me, as a C++ programmer, I don't hesitate to question > > the decisions of language designers. After a decent amount of C++ > > exposure, Python's flaws seem ridiculously small." -- Ville Vainio > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" > > >=20 > Is there a good reason why 7.0 is going to be released using a bad > version of gcc? or is 4.2.1 going in before release? 4.2.1 has been in for a week or two... -- Brooks --qDbXVdCdHGoSgWSk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFGzcJ4XY6L6fI4GtQRAgSYAJ4i3dWf4DTkSYr4bD9SfKJ44Gp/2ACgqmG0 0h/uptbYRqcnkjnm2Bz8g+g= =39vR -----END PGP SIGNATURE----- --qDbXVdCdHGoSgWSk-- From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 17:25:31 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1516B16A420 for ; Thu, 23 Aug 2007 17:25:31 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id A0D9913C45E for ; Thu, 23 Aug 2007 17:25:30 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.13.8/jtpda-5.4) with ESMTP id l7NGYiiP005256 for ; Thu, 23 Aug 2007 18:34:44 +0200 (CEST) X-Ids: 164 Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.13.3/jtpda-5.2) with ESMTP id l7NGYhxR000667 for ; Thu, 23 Aug 2007 18:34:43 +0200 (MEST) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.13.3/8.13.1/Submit) id l7NGYhhL000664; Thu, 23 Aug 2007 18:34:43 +0200 (MEST) (envelope-from arno) To: freebsd-current@freebsd.org References: <46BFE620.8070906@fusiongol.com> <20070813091802.GB3078@stud.ntnu.no> <20070823071056.GA50852@obiwan.tataz.chchile.org> From: "Arno J. Klaassen" Date: 23 Aug 2007 18:34:43 +0200 In-Reply-To: <20070823071056.GA50852@obiwan.tataz.chchile.org> Message-ID: Lines: 48 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (shiva.jussieu.fr [134.157.0.164]); Thu, 23 Aug 2007 18:34:44 +0200 (CEST) X-Virus-Scanned: ClamAV 0.88.7/4033/Thu Aug 23 11:36:42 2007 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at shiva.jussieu.fr with ID 46CDB724.003 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Subject: Re: Promise SATA 300 TX4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 17:25:31 -0000 Hello, Jeremie Le Hen writes: > Hi Ulf, > > On Mon, Aug 13, 2007 at 11:18:02AM +0200, Ulf Lilleengen wrote: > > I have problems with this card in -CURRENT too. Details can be found > > here: > > http://lists.freebsd.org/pipermail/freebsd-current/2007-July/074960.html > > > > I never bothered trying with earlier versions of -CURRENT, but it > > works good in 6.2. > > I'm planning to switch my own server from 6.2 to -CURRENT soon. > Are you still experiencing such problems? might be related : I see similar problems (tons of 'taskqueue timeout' 'READ_DMA48 retrying' and finaly 'adX : FAILURE device detached' ) on 6-STABLE-amd64' (verified on two different mother-boards). And I remarked a curious message in de dmesg : atapci0: port 0xe400-0xe47f,0xe500-0xe5ff mem 0xf60c2000-0xf60c2fff,0xf60a0000-0xf60bffff irq 16 at device 8.0 on pci0 pci0: child atapci0 requested type 4 for rid 0x20, but the BAR says it is an memio ... atapci1: port 0xe600-0xe67f,0xe700-0xe7ff mem 0xf60c5000-0xf60c5fff,0xf6080000-0xf609ffff irq 18 at device 10.0 on pci0 pci0: child atapci1 requested type 4 for rid 0x20, but the BAR says it is an memio The ' .. but the BAR says .. ' messages seem to come from pci_alloc_map() and the code has the following comment : * Note: atapci in legacy mode are special and handled elsewhere * in the code. If you have a atapci device in legacy mode and * it fails here, that other code is broken. */ I can provide more info or test ideas/patches. Thanx in advance, regards, Arno From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 18:25:47 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16AA216A418 for ; Thu, 23 Aug 2007 18:25:47 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.freebsd.org (Postfix) with ESMTP id A172813C457 for ; Thu, 23 Aug 2007 18:25:46 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (cpe-71-72-80-132.columbus.res.rr.com [71.72.80.132]) (authenticated bits=0) by mail.united-ware.com (8.13.8/8.13.8) with ESMTP id l7NJ41LE095599 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Aug 2007 15:04:08 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: Johan Hendriks Date: Thu, 23 Aug 2007 14:28:51 -0400 User-Agent: KMail/1.9.6 References: <200708210928.aa80674@walton.maths.tcd.ie> <200708221602.42191.mistry.7@osu.edu> <57200BF94E69E54880C9BB1AF714BBCB19BC8D@w2003s01.double-l.local> In-Reply-To: <57200BF94E69E54880C9BB1AF714BBCB19BC8D@w2003s01.double-l.local> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4245130.VI22QEzGIH"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200708231429.01929.mistry.7@osu.edu> X-Virus-Scanned: ClamAV 0.90.3/4034/Thu Aug 23 11:11:55 2007 on mail.united-ware.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: Can't create TCP connections to certain IP addresses X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 18:25:47 -0000 --nextPart4245130.VI22QEzGIH Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 23 August 2007, Johan Hendriks wrote: > On Tuesday 21 August 2007, David Malone wrote: > >> > What's the PR number? > >> > >> The PR that I am thinking of is: > >> > >> http://www.freebsd.org/cgi/query-pr.cgi?pr=3Di386/69257 > >> > >> > COPTFLAGS+=3D-O2 > >> > CPUTYPE=3Di586/mmx > >> > >> I guess you may not be directly be effected, as you're using > >> -O2, but > >> > >> it might be another interaction with gcc, so I'd try compiling a > >> kernel with -O, just to see if you get a different result. > >> > >> (Record the output of building the kernel, just to make sure it > >> is using the flags you think it is.) > > > >I had to specify > >CFLAGS=3D-O -pipe > >in make.conf to force the kernel to build without -O2 even after > > removing the COPTFLAGS and CPUTYPE. > > >It's fixed now by forcing -O, but this seems to be a serious issue > > as > > -O2 is the default. Is this fixed in 4.2.1? And will that make it > into > > >7.0? > > -- > > >Anish Mistry > > 4.2.1 is in at the moment. > > admin@beasty ~ $ gcc --version > gcc (GCC) 4.2.1 20070719 [FreeBSD] > Copyright (C) 2007 Free Software Foundation, Inc. > This is free software; see the source for copying conditions.=20 > There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR > PURPOSE. Hmmm...right you are. That's unfortunate that the problem remains. =2D-=20 Anish Mistry --nextPart4245130.VI22QEzGIH Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBGzdHtxqA5ziudZT0RAqWWAJ9pzSJ+1IuzrKcdqVQPtaJGyjvB/QCcCRbM ujuNZebLBKHQRcoCQZiH9+k= =NRzA -----END PGP SIGNATURE----- --nextPart4245130.VI22QEzGIH-- From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 19:23:24 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7C5A16A419 for ; Thu, 23 Aug 2007 19:23:24 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mx1.freebsd.org (Postfix) with ESMTP id 3776C13C428 for ; Thu, 23 Aug 2007 19:23:23 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l7NJNMvX004115; Fri, 24 Aug 2007 05:23:22 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l7NJNMHA004114; Fri, 24 Aug 2007 05:23:22 +1000 (EST) (envelope-from peter) Date: Fri, 24 Aug 2007 05:23:22 +1000 From: Peter Jeremy To: Robert Watson Message-ID: <20070823192322.GQ1161@turion.vk2pj.dyndns.org> References: <20070823101737.GA1161@turion.vk2pj.dyndns.org> <20070823162802.T2662@fledge.watson.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yVhtmJPUSI46BTXb" Content-Disposition: inline In-Reply-To: <20070823162802.T2662@fledge.watson.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@FreeBSD.org Subject: Re: idprio(1) broken in recent -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 19:23:24 -0000 --yVhtmJPUSI46BTXb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-Aug-23 16:29:26 +0100, Robert Watson wrote: >> all the ports and a bit of hair removal, I tracked the problem to the=20 >> 'idprio' command in /usr/local/etc/rc.d/boinc - without that, all works= =20 >> fine. If I include that, boinc_client stops sending heartbeat messages. >When I run "idprio 20 echo hi", it seems to execute per normal as root, an= d=20 >not at all as an unprivileged user, which I think is the desired symptom o= f=20 >using it. The offending command in the rc.d is (as root): idprio 31 su - boinc -c '/usr/local/bin/boinc_client ...&' boinc_client forks the actual computation process (setiathome etc). The setiathome process is basically CPU bound but calls usleep() occasionally (so on an otherwise idle system, top shows it using around 95% CPU and in nanslp). boinc_client is supposed to write a watchdog flag in a shared SysV SHM block every second. The setiathome process regularly polls the SHM and if it doesn't see the watchdog for 31 seconds, it will abort. boinc_client basically sits in a loop and uses select() timeouts. I wrote a program to monitor the SHM and it shows that SHM is not being updated. It looks like the kernel isn't cleanly handling the situation where there are multiple idprio processes. I will try some more experimenting this evening. >If you're running things with idprio, is it definitely the case that your= =20 >system is sometimes idle allowing the program to run once in a while? It used to work fine even whilst doing a buildworld, now it won't work on an otherwise idle system... --=20 Peter Jeremy --yVhtmJPUSI46BTXb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGzd6q/opHv/APuIcRAs6xAJ99fo/O8LOs3Uk3kDPy4+MGAyF/OgCdE5/T qouhs82wKvGz0gBt7vnFXhk= =ZKWd -----END PGP SIGNATURE----- --yVhtmJPUSI46BTXb-- From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 20:14:06 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E566716A419 for ; Thu, 23 Aug 2007 20:14:06 +0000 (UTC) (envelope-from mkhitrov@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.176]) by mx1.freebsd.org (Postfix) with ESMTP id A624313C467 for ; Thu, 23 Aug 2007 20:14:06 +0000 (UTC) (envelope-from mkhitrov@gmail.com) Received: by el-out-1112.google.com with SMTP id s27so141486ele for ; Thu, 23 Aug 2007 13:14:06 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Sb4tmvBkb6W8B+JXkhuS44xvVPGageuKW4tnkzBbfVJLwza5yPFFFJbQxNWLbw5UFMOZxJRLCst1LHv8iUhxg2MODa/A9sXW264EeHvk5fDhyfdEdgVFxy/YjCLbIV6oiregZDqRAedhfWwAtwL4yF/BLwTc4kiWciPsPK8yPag= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=icNVFmNaZtn5dkqiWQ9uouHl83ljQPyjRkkr32ysoy5sl5tWiCrNcUfQmwCOLWm17vNA9Wyfj9MVDNx+Ng0PiSZYtShKXz5PMi74kvD3MCGeDHn7HMWVt19majHDAwl+wxCG7fNh1nJiIUg1jdSCTp67eTT/dzIFVBvPJm/UztY= Received: by 10.143.34.11 with SMTP id m11mr78079wfj.1187898542941; Thu, 23 Aug 2007 12:49:02 -0700 (PDT) Received: by 10.143.10.17 with HTTP; Thu, 23 Aug 2007 12:49:02 -0700 (PDT) Message-ID: <26ddd1750708231249h3666b5cbjf6935cc010ebe40@mail.gmail.com> Date: Thu, 23 Aug 2007 15:49:02 -0400 From: "Maxim Khitrov" To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: X Server Problems: 100% CPU usage, no keyboard X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 20:14:07 -0000 Hello, I'm not exactly sure how to best proceed in my situation, so thought I'd ask here. I'm running FreeBSD 7.0-CURRENT on my Fujitsu P7010 laptop. I installed xorg and gnome2-lite ports, configured the X server, and am now trying to get gnome to run. The problem is this; if I boot using the GENERIC kernel and run startx, everything works great. I get my gnome desktop and can continue working there. However, when I switch to my own kernel, starting the X server causes CPU usage to go to 100% (permanently) and my keyboard stops working. I can't even do Ctrl-Alt-Backspace to kill the server. The mouse still works, so I can logout back to the console at which point CPU goes to idle and keyboard works again. I looked through my kernel config and don't see anything wrong there. The keyboard-related options are the same as GENERIC. My only guess is that it's something that I've added to the kernel that is causing these problems, but I don't want to go removing one thing at a time at random to see if it makes a difference. My config is posted on pastebin (URL below). Can you please take a look at it and see if you can spot what could be causing the problem? My configuration file: http://pastebin.com/m1a39ace1 Thanks, Maxim Khitrov From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 20:19:08 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B21016A41A for ; Thu, 23 Aug 2007 20:19:08 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id 31BF213C45A for ; Thu, 23 Aug 2007 20:19:07 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.13.8/jtpda-5.4) with ESMTP id l7NKJ6Nc087539 for ; Thu, 23 Aug 2007 22:19:06 +0200 (CEST) X-Ids: 164 Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.13.3/jtpda-5.2) with ESMTP id l7NKJ5Nn001599 for ; Thu, 23 Aug 2007 22:19:05 +0200 (MEST) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.13.3/8.13.1/Submit) id l7NKJ4N0001596; Thu, 23 Aug 2007 22:19:04 +0200 (MEST) (envelope-from arno) To: freebsd-current@freebsd.org References: <46BFE620.8070906@fusiongol.com> <20070813091802.GB3078@stud.ntnu.no> <20070823071056.GA50852@obiwan.tataz.chchile.org> From: "Arno J. Klaassen" Date: 23 Aug 2007 22:19:02 +0200 In-Reply-To: <20070823071056.GA50852@obiwan.tataz.chchile.org> Message-ID: Lines: 16 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (shiva.jussieu.fr [134.157.0.164]); Thu, 23 Aug 2007 22:19:06 +0200 (CEST) X-Virus-Scanned: ClamAV 0.88.7/4036/Thu Aug 23 20:43:43 2007 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at shiva.jussieu.fr with ID 46CDEBBA.007 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Subject: Re: Promise SATA 300 TX4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 20:19:08 -0000 Re, > On Mon, Aug 13, 2007 at 11:18:02AM +0200, Ulf Lilleengen wrote: > > I have problems with this card in -CURRENT too. Details can be found > > here: > > http://lists.freebsd.org/pipermail/freebsd-current/2007-July/074960.html I re-read the above email a bit more attentively (?) and noticed that, as Ulf, I use Adaptec SCSI (ahc or ahd) to boot from and have nothing on standard irq-14/15 IDE subsystem. Once again, I experience the problems on -STABLE-amd64, but can dig up a good-old (not so fast) SCSI-disk to test the (almost) same hardware setup under -CURRENT. Arno From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 21:51:47 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 48B5116A417 for ; Thu, 23 Aug 2007 21:51:47 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.184]) by mx1.freebsd.org (Postfix) with ESMTP id 1BDD013C491 for ; Thu, 23 Aug 2007 21:51:47 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so455358rvb for ; Thu, 23 Aug 2007 14:51:46 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=RoQG0RNOq+Vd0AFS2XAMyp5IMc7FVwU4LlpMpvOITyXrw8H7OTG50mU8ScRWhyj50gC3fcT05W1uCAXW6APJF59/KGSfRiPKfxhDzBbTeJoAjPAxcoVFuQ74zUxppTv8SLUz7Etu6Ya7ehHGB5A5qLqD2C/rDj9I9bwX4DpHE8U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dz9uCElD2l3JQdGzjszu+qWZ5h4k2uxhrI5ysFI7W/67i/I++hcJAvKysHFlodefpVQQv+Sym5ZcZEUZwQQqd28Ctt1dLdmZeEO2S8OUSAsi4o2d10Vwnq/MYLYkzDgaYzCOpiu1SugINYkN/8ePnnefiC8TZuLyPCaXzTAH2ng= Received: by 10.141.209.7 with SMTP id l7mr167297rvq.1187904277777; Thu, 23 Aug 2007 14:24:37 -0700 (PDT) Received: by 10.141.86.8 with HTTP; Thu, 23 Aug 2007 14:24:37 -0700 (PDT) Message-ID: Date: Fri, 24 Aug 2007 01:24:37 +0400 From: pluknet To: "Andrew Thompson" In-Reply-To: <20070723114821.GA6575@heff.fud.org.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070619011908.GA53748@heff.fud.org.nz> <20070620042023.GA17424@nowhere> <4678B1E4.7080909@errno.com> <467ED084.4000002@petri.cc> <46A484CA.8030805@petri.cc> <20070723114821.GA6575@heff.fud.org.nz> Cc: FreeBSD Current Subject: Re: wireless X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 21:51:47 -0000 Hello, Andrew. On 23/07/07, Andrew Thompson wrote: > On Mon, Jul 23, 2007 at 12:36:58PM +0200, Nicolai Petri (lists) wrote: > > Nicolai Petri (lists) wrote: > > > > > >>>In short, ipw doesn't seem to work at all for me anymore. It worked > > >>>okay in 6-stable with an occasional hiccup, but upon upgrading to > > >>>current it doesn't seem to be doing anything. > > >>>Sometimes "ifconfig scan" does nothing, sometimes it results in a panic. > > >> > > >>I'm not sure how well ipw got tested while the changes were in p4. > > >>We'll need to test again now that code has been merged to CVS. I'll try > > >>to look at this weekend if noone else beats me to it. > > >> > > >> Sam > > > > > > > > >I'm running -current from following time : Thu Jun 20 > > > > > >Best regards, > > >Nicolai Petri > > > > > Are there any news on this matter ? We are now 1 month closer to beta > > and ipw is still useless. I'm willing to test if anyone have patches but > > I don't have time to look at code myself. > > You can test this WIP. > > > cheers, > Andrew I have a firmware problem with iwi(4) on recent current. iwi0: It throws "iwi0: firmware error" if it has setup to associate in authmode WPA (via wpa_supplicant). It worked for me before 80211n introduce. Otherwise, it associates as well in authmode OPEN (without supplicant). Any hopes it will be fixed before 7.0? Also I can get "firmware error" if I kill watchdogd and then system goes to KDB state over a specific timeout. Nevertheless, after 'continue' command it associates in OPEN, and not in WPA (i.e. same as mentioned above). Cut from dmesg right after watchdogd's death: interrupt total irq0: clk 23255323 irq1: atkbd0 198187 irq8: rtc 14882328 irq9: pcm0 iwi0+ 173519 irq11: fxp0 uhci0* 215 irq12: psm0 489456 irq14: ata0 194865 irq15: ata1 844 Total 39194737 KDB: stack backtrace: db_trace_self_wrapper(c07a8e50,cba76c04,c051f4b5,c07a3ba7,2561071,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c07a3ba7,2561071,0,2561071,0,...) at kdb_backtrace+0x29 hardclock(0,c0a68c65,c1ebce80,0,cba76c44,...) at hardclock+0x1b5 clkintr(cba76c70,0,0,c1cd3660,c1cd0c00,...) at clkintr+0xda intr_execute_handlers(c0807280,cba76c70,0,c1d64200,c1d64218,...) at intr_execute_handlers+0xf5 atpic_handle_intr(0,cba76c70) at atpic_handle_intr+0xbc Xatpic_intr0() at Xatpic_intr0+0x21 --- interrupt, eip = 0xc0a68c65, esp = 0xcba76cb0, ebp = 0xcba76cb0 --- acpi_cpu_c1(1,10,c1cd3660,c1d64218,0,...) at acpi_cpu_c1+0x5 acpi_cpu_idle(cba76cf4,c05729c5,cba76d24,c05354e1,0,...) at acpi_cpu_idle+0x271 cpu_idle(cba76d24,c05354e1,0,cba76d38,0,...) at cpu_idle+0x26 sched_idletd(0,cba76d38,0,0,0,...) at sched_idletd+0x15 fork_exit(c05729b0,0,cba76d38) at fork_exit+0xa1 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xcba76d70, ebp = 0 --- KDB: enter: watchdog timeout interrupt total irq0: clk 23255324 irq1: atkbd0 198187 irq8: rtc 14882328 irq9: pcm0 iwi0+ 173519 irq11: fxp0 uhci0* 215 irq12: psm0 489456 irq14: ata0 194865 irq15: ata1 844 Total 39194738 KDB: stack backtrace: db_trace_self_wrapper(c07a8e50,cba7cc0c,c051f4b5,c07a3ba7,2561072,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c07a3ba7,2561072,0,2561072,0,...) at kdb_backtrace+0x29 hardclock(0,c0754129,c1ebce80,0,cba7cc4c,...) at hardclock+0x1b5 clkintr(cba7cc78,1ca0,0,c1cd3aa0,c1cd0c00,...) at clkintr+0xda intr_execute_handlers(c0807280,cba7cc78,c1cd3aa0,c1cd0400,0,...) at intr_execute_handlers+0xf5 atpic_handle_intr(0,cba7cc78) at atpic_handle_intr+0xbc Xatpic_intr0() at Xatpic_intr0+0x21 --- interrupt, eip = 0xc0754129, esp = 0xcba7ccb8, ebp = 0xcba7ccbc --- spinlock_exit(1,0,c07a4a4c,46b,0,...) at spinlock_exit+0x29 ithread_loop(c1c9f460,cba7cd38,0,0,0,...) at ithread_loop+0x353 fork_exit(c0538a60,c1c9f460,cba7cd38) at fork_exit+0xa1 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xcba7cd70, ebp = 0 --- KDB: enter: watchdog timeout iwi0: firmware error ^^^^ iwi0: link state changed to DOWN iwi0: link state changed to UP From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 23:25:40 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6404516A417 for ; Thu, 23 Aug 2007 23:25:40 +0000 (UTC) (envelope-from mkhitrov@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.228]) by mx1.freebsd.org (Postfix) with ESMTP id 21F5213C459 for ; Thu, 23 Aug 2007 23:25:40 +0000 (UTC) (envelope-from mkhitrov@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so400932nzf for ; Thu, 23 Aug 2007 16:25:39 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=IjVZdEqwi6sAgZF6DSeBkyhjuOJuYTYcdIZ37ZP4fMA3hpryFvlihKz2ZaJyOo9yAkqbXPgFnmb55zN/I+L5nVNvzXD8mKbvreD0Pbyp00RKKIQ5pj2I79Xqwx45uHF5/f4o3lOu+6hTV7KOgtNp4m4WZBUtofXvSZkvU17u6X8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Vh40wL2SoAev+N5hFV9SpDgI9BQRKrE7loKGjR4/+5TRvbLNWVSAcIDAJ7yfUZ/ZyZH6vf9doNYBYGAmXfodgV8B3DcmmrjjreqEr39wewC2+qqyV3f3pYJTb9bBvo7aRLO69qWtLwt1HI+18Cvn8DRsSIN0fQlummoixplpx3s= Received: by 10.143.1.2 with SMTP id d2mr288251wfi.1187911539030; Thu, 23 Aug 2007 16:25:39 -0700 (PDT) Received: by 10.143.10.17 with HTTP; Thu, 23 Aug 2007 16:25:38 -0700 (PDT) Message-ID: <26ddd1750708231625s36ffb874u7863d34654606a3c@mail.gmail.com> Date: Thu, 23 Aug 2007 19:25:38 -0400 From: "Maxim Khitrov" To: freebsd-current@freebsd.org In-Reply-To: <26ddd1750708231249h3666b5cbjf6935cc010ebe40@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <26ddd1750708231249h3666b5cbjf6935cc010ebe40@mail.gmail.com> Subject: Re: X Server Problems: 100% CPU usage, no keyboard X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 23:25:40 -0000 On 8/23/07, Maxim Khitrov wrote: > Hello, > > I'm not exactly sure how to best proceed in my situation, so thought > I'd ask here. I'm running FreeBSD 7.0-CURRENT on my Fujitsu P7010 > laptop. I installed xorg and gnome2-lite ports, configured the X > server, and am now trying to get gnome to run. > > The problem is this; if I boot using the GENERIC kernel and run > startx, everything works great. I get my gnome desktop and can > continue working there. However, when I switch to my own kernel, > starting the X server causes CPU usage to go to 100% (permanently) and > my keyboard stops working. I can't even do Ctrl-Alt-Backspace to kill > the server. The mouse still works, so I can logout back to the console > at which point CPU goes to idle and keyboard works again. > > I looked through my kernel config and don't see anything wrong there. > The keyboard-related options are the same as GENERIC. My only guess is > that it's something that I've added to the kernel that is causing > these problems, but I don't want to go removing one thing at a time at > random to see if it makes a difference. My config is posted on > pastebin (URL below). Can you please take a look at it and see if you > can spot what could be causing the problem? > > My configuration file: http://pastebin.com/m1a39ace1 > > Thanks, > Maxim Khitrov Well it took a while, but I was able to figure out what was causing the problem. And yes, it was my mistake :) In my configuration I set MAXCONS to 4, but I made an error when editing /etc/ttys and left 4 of the consoles turned on. The original idea was to have three text-mode consoles and one for X. All the allowed consoles were taken, so the X server was starting on ttyv4 instead of ttyv3. I still have no idea why it behaved the way it did (100% CPU and no keyboard), but marking ttyv3 as off in /etc/ttys solved the problem. I would have expected the server to tell me that there are no available consoles to use, but at any rate... Glad I was able to fix it. And it only took 12 kernel recompilations (good thing I use ccache :) - Max From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 03:00:58 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA57C16A418 for ; Fri, 24 Aug 2007 03:00:58 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by mx1.freebsd.org (Postfix) with ESMTP id B47CB13C458 for ; Fri, 24 Aug 2007 03:00:58 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 23 Aug 2007 20:00:55 -0700 X-IronPort-AV: i="4.19,302,1183359600"; d="scan'208"; a="205606677:sNHT42841287" Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7O30tpp023201 for ; Thu, 23 Aug 2007 20:00:55 -0700 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7O30rl7012048 for ; Fri, 24 Aug 2007 03:00:55 GMT Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Aug 2007 20:00:53 -0700 Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Aug 2007 20:00:53 -0700 Message-ID: <46CE49F0.9070204@cisco.com> Date: Thu, 23 Aug 2007 23:01:04 -0400 From: Randall Stewart User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20070601 X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD Current Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 24 Aug 2007 03:00:53.0316 (UTC) FILETIME=[FBD7D840:01C7E5FA] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=829; t=1187924455; x=1188788455; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rrs@cisco.com; z=From:=20Randall=20Stewart=20 |Subject:=20Crash=20when=20we=20wakeup=20from=20a=20sleep=20on=20IBM=20T4 3 |Sender:=20; bh=JqUQtGs7SJ25/fS6LwXJFyMCe8TtqyrLiMbPU9Wxwv0=; b=BTC/MDHjeUPv8HA/OuRb/ODICv8NKSXHAQJkfmTOCFEsdVgGtGTTCVtlVnW7pGbcgCnU/JeS hdj0AduUFztCQymObGTz6HGXm4oglrVFivYbYYuGToFAvYn/DkOPlO66; Authentication-Results: sj-dkim-2; header.From=rrs@cisco.com; dkim=pass (sig from cisco.com/sjdkim2002 verified; ); Subject: Crash when we wakeup from a sleep on IBM T43 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 03:00:58 -0000 Hi all: Ok I can easily reproduce this.. and I have pinpointed at least one of the culprits.. witness says its: recursed on non-recursive lock in OsdSync.c line 377 acpi subsystem... You can find here (thanks to fellow sctp-interop participants) jpegs of the crash and a picture of a ddb> trace The crash: http://www.sctp.org/sleep_crash1.jpg The trace: http://www.sctp.org/sleep_crash2.jpg Would someone who owns the acpi subsystem take a look at this.. and if you need more info, it would be good to hear from you.. I can do DDB commands if you want more info and at the interop until tommorrow I have access to a D200 to actually take photos of it... or of course there is the manual transcribe :-0 R -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 803-317-4952 (cell) From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 06:28:52 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36DF516A419 for ; Fri, 24 Aug 2007 06:28:52 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from fep02.xtra.co.nz (fep02.xtra.co.nz [210.54.141.244]) by mx1.freebsd.org (Postfix) with ESMTP id CAB8213C48A for ; Fri, 24 Aug 2007 06:28:51 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from fep03.xtra.co.nz ([172.23.12.31]) by mta02.xtra.co.nz with ESMTP id <20070824061629.HRXC27853.mta02.xtra.co.nz@fep03.xtra.co.nz> for ; Fri, 24 Aug 2007 18:16:29 +1200 Received: from serv.int.fubar.geek.nz ([219.89.91.5]) by fep03.xtra.co.nz with ESMTP id <20070824061629.CNUT19268.fep03.xtra.co.nz@serv.int.fubar.geek.nz> for ; Fri, 24 Aug 2007 18:16:29 +1200 Date: Fri, 24 Aug 2007 18:16:27 +1200 From: Andrew Turner To: freebsd-current@freebsd.org Message-ID: <20070824181627.57bed401@hermies.int.fubar.geek.nz> X-Mailer: Claws Mail 2.10.0 (GTK+ 2.10.14; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: FreeBSD on xen hvm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 06:28:52 -0000 I've been working on getting -CURRENT i386 to boot on the Xen amd64 hvm. It provides full vitalization to allow operating systems to boot without modification. The problem is the GENERIC kernel can't boot under it. I've found three options that, when disabled, allow FreeBSD to work. 1) PREEMPTION Preemption causes the kernel to panic with a page fault. The dmesg is available from [1]. 2) SMP With SMP enabled the kernel it enters an infinite loop in uma_zalloc_bucket. The problem is uma_zone_slab returns a slab but slab->us_freecount is 0. It then enters uma_zone_slab and gets the same slab again. It appears there is a race condition setting us_freecount to zero. The zone is always turnstile_zone. 3) INVARIANTS Invariants causes a panic from a page fault. See [2] for the dmesg and backtrace. I can provide people with more information to track down the problem and try patches. Andrew [1] http://fubar.geek.nz/files/freebsd/xen/xen_crash_preemption.txt [2] http://fubar.geek.nz/files/freebsd/xen/xen_crash_invariants.txt -- Andrew Turner http://fubar.geek.nz/blog/ From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 08:17:32 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 876C616A417 for ; Fri, 24 Aug 2007 08:17:32 +0000 (UTC) (envelope-from yuri@darklight.org.ru) Received: from darklight.org.ru (crsd-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2d5::2]) by mx1.freebsd.org (Postfix) with ESMTP id 236E913C459 for ; Fri, 24 Aug 2007 08:17:29 +0000 (UTC) (envelope-from yuri@darklight.org.ru) Received: from darklight.org.ru (yuri@darklight.org.ru [127.0.0.1]) by darklight.org.ru (8.14.1/8.14.1) with ESMTP id l7O8HRdm069168 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 24 Aug 2007 12:17:27 +0400 (MSD) (envelope-from yuri@darklight.org.ru) Received: (from yuri@localhost) by darklight.org.ru (8.14.1/8.14.1/Submit) id l7O8HR8O069167 for freebsd-current@freebsd.org; Fri, 24 Aug 2007 12:17:27 +0400 (MSD) (envelope-from yuri@darklight.org.ru) Date: Fri, 24 Aug 2007 12:17:26 +0400 From: Yuri Pankov To: freebsd-current@freebsd.org Message-ID: <20070824081726.GC6571@darklight.org.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.16 (2007-06-09) Subject: rtfree: 0xffffff00036fb1e0 has 1 refs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 08:17:32 -0000 Hi, I've recently started using he.net's ipv6 tunnel and getting this message: rtfree: 0xffffff00036fb1e0 has 1 refs I've added kdb_backtrace() in route.c as Gleb Smirnoff suggested before. Here's backtrace: rtfree: 0xffffff00036fb1e0 has 1 refs KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a rtfree() at rtfree+0xba gif_encapcheck4() at gif_encapcheck4+0x118 gif_encapcheck() at gif_encapcheck+0xfd encap4_input() at encap4_input+0xcc ip_input() at ip_input+0xc0 tunwrite() at tunwrite+0x1d5 giant_write() at giant_write+0x51 devfs_write_f() at devfs_write_f+0x9c dofilewrite() at dofilewrite+0x85 kern_writev() at kern_writev+0x4c write() at write+0x54 syscall() at syscall+0x1ce Xfast_syscall() at Xfast_syscall+0xab --- syscall (4, FreeBSD ELF64, write), rip = 0x80125c35c, rsp = 0x7fffffffda18, rbp = 0x60 --- ifconfig: gif0: flags=8051 metric 0 mtu 1280 tunnel inet 194.186.18.14 --> 64.71.128.83 inet6 fe80::20f:eaff:fe7d:f320%gif0 prefixlen 64 scopeid 0x5 inet6 2001:470:1f03:2d5::2 --> 2001:470:1f03:2d5::1 prefixlen 128 inet6 2001:470:1f01:725::1 prefixlen 64 tun0: flags=8051 metric 0 mtu 1500 inet6 fe80::20f:eaff:fe7d:f320%tun0 prefixlen 64 scopeid 0x6 inet 194.186.18.14 --> 194.186.18.2 netmask 0xffffff00 Opened by PID 458 Yuri From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 12:30:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B05916A420 for ; Fri, 24 Aug 2007 12:30:18 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 067F413C478 for ; Fri, 24 Aug 2007 12:30:18 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 89AE548EC5; Fri, 24 Aug 2007 08:30:17 -0400 (EDT) Date: Fri, 24 Aug 2007 13:30:17 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Andrew Turner In-Reply-To: <20070824181627.57bed401@hermies.int.fubar.geek.nz> Message-ID: <20070824132409.W3900@fledge.watson.org> References: <20070824181627.57bed401@hermies.int.fubar.geek.nz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD on xen hvm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 12:30:18 -0000 On Fri, 24 Aug 2007, Andrew Turner wrote: > 1) PREEMPTION Preemption causes the kernel to panic with a page fault. The > dmesg is available from [1]. Any chance it's possible to get a core for this, or attach GDB somehow to the VM? It looks like timing in Xen may be exposing a race in some or another subsystem with timers, but figuring out which subsystem it is will be most easily done if we can inspect the callout information, which is most easily done with GDB since you can inspect the callout structure more easily. If not, then we can add some printfs to extract the information, I expect, or extend DDB. We need to find out what the function pointer in the callout structure is for. > 3) INVARIANTS Invariants causes a panic from a page fault. See [2] for the > dmesg and backtrace. This appears to be in the start up of Audit as it creates a kernel thread. Possibly it's creating the thread too early, or possibly something else is going on. Can you try creating a kernel without options AUDIT and see if it works better, or if it just panics when the next thread is created? It sounds like Xen may start the timer firing sooner than on plain hardware, or possibly at a faster rate initially, and that's causing things to happen in a different order, so I expect we'll either bump into a series of races of this sort based on different ordering of events, or discover the timer isn't properly being disabled or managed in Xen :-). Robert N M Watson Computer Laboratory University of Cambridge > > I can provide people with more information to track down the problem > and try patches. > > Andrew > > [1] http://fubar.geek.nz/files/freebsd/xen/xen_crash_preemption.txt > [2] http://fubar.geek.nz/files/freebsd/xen/xen_crash_invariants.txt > > -- > Andrew Turner > http://fubar.geek.nz/blog/ > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 13:42:36 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F4FC16A417 for ; Fri, 24 Aug 2007 13:42:36 +0000 (UTC) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw2.york.ac.uk (mail-gw2.york.ac.uk [144.32.128.247]) by mx1.freebsd.org (Postfix) with ESMTP id 8C9C113C48A for ; Fri, 24 Aug 2007 13:42:35 +0000 (UTC) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw6.york.ac.uk (mail-gw6.york.ac.uk [144.32.129.26]) by mail-gw2.york.ac.uk (8.13.6/8.13.6) with ESMTP id l7ODCAcZ017909; Fri, 24 Aug 2007 14:12:10 +0100 (BST) Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk) by mail-gw6.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1IOYxO-0004Ts-GG; Fri, 24 Aug 2007 14:12:10 +0100 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.1/8.14.1) with ESMTP id l7ODC771026852; Fri, 24 Aug 2007 14:12:07 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.1/8.14.1/Submit) id l7ODC3hq026851; Fri, 24 Aug 2007 14:12:03 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: gowmo@itecgyn.com.br In-Reply-To: <044112fd226062ed9e5d4ac73ecd1337@localhost> References: <903f4bc2118c595b4baf82815ea99ca6@localhost> <044112fd226062ed9e5d4ac73ecd1337@localhost> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Date: Fri, 24 Aug 2007 14:12:03 +0100 Message-Id: <1187961123.26044.19.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Cc: freebsd-current@freebsd.org Subject: Re: Cant load Marvell Yukon network interface with acpi enabled andAtherosAR5005 with acpi disabled. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 13:42:36 -0000 On Mon, 2007-08-13 at 14:15 +0000, Wildes Miranda de Oliveira wrote: > can anyone help me ? Looking at the output, you may be better off asking on the freebsd-acpi mailing list. Gavin > thanks. >=20 > On Mon, 6 Aug 2007 22:03:46 +0000, Wildes Miranda de Oliveira wrote: > >> hi list, > >> > >> excuse-me my poorly english. > >> > >> recently i bought one notebook acer aspire 3680, and i have had proble= ms > >> for load network interfaces on them. > >> the problem is that the interface ethernet Marvell Yukon don't load wi= th > >> acpi enabled, and the interface > >> wireless Atheros AR5005 don't load with acpi disabled, with this it=B4= s > >> never load on same bootstrap. > >> i'm annexing informations about dmesg with acpi enabled/disabled , > >> acpidump and pciconf -lv. > >> > >> i wish ask you about tunning of acpi described in man page. could this > >> solve my problem ? > >> > >> LOADER TUNABLES > >> Tunables can be set at the loader(8) prompt before booting the > > kernel > >> or > >> stored in /boot/loader.conf. Many of these tunables also have a > >> matching > >> > >> hw.acpi.serialize_methods > >> > >> Allow override of whether methods execute in parallel or > > not. > >> Enable this for serial behavior, which fixes > >> "AE_ALREADY_EXISTS" > >> errors for AML that really cannot handle parallel method > >> execu- > >> tion. It is off by default since this breaks recursive > >> methods > >> and some IBMs use such code. > >> > >> hw.pci.link.%s.%d.irq > >> > >> Override the interrupt to use for this link and index.=20 > > This > >> capability should be used carefully, and only if a device > > is > >> not > >> working with acpi enabled. "%s" is the name of the link > >> (e.g., > >> LNKA). "%d" is the resource index when the link supports > >> multi- > >> ple IRQs. Most PCI links only have one IRQ resource, so > > the > >> below form should be used. > >> > >> hw.pci.link.%s.irq > >> > >> Override the interrupt to use. This capability should be > >> used > >> carefully, and only if a device is not working with acpi > >> enabled. > >> "%s" is the name of the link (e.g., LNKA). > >> > >> #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ACPI DISABLED > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >> > >> Copyright (c) 1992-2007 The FreeBSD Project. > >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 19= 94 > >> The Regents of the University of California. All rights reserved. > >> FreeBSD is a registered trademark of The FreeBSD Foundation. > >> FreeBSD 7.0-CURRENT-200706 #0: Sun Jun 3 18:41:02 UTC 2007 > >> root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > >> WARNING: WITNESS option enabled, expect reduced performance. > >> MPTable: > >> Timecounter "i8254" frequency 1193182 Hz quality 0 > >> CPU: Intel(R) Celeron(R) M CPU 430 @ 1.73GHz (1733.41-MHz > >> 686-class CPU) > >> Origin =3D "GenuineIntel" Id =3D 0x6e8 Stepping =3D 8 > >> > >> > > Features=3D0xafe9fbff > >> Features2=3D0xc109 > >> AMD Features=3D0x100000 > >> real memory =3D 526974976 (502 MB) > >> avail memory =3D 501780480 (478 MB) > >> ioapic0: Assuming intbase of 0 > >> ioapic0 irqs 0-23 on motherboard > >> kbd1 at kbdmux0 > >> ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, > > RF5413) > >> cpu0 on motherboard > >> pcib0: pcibus 0 on motherboard > >> pci0: on pcib0 > >> vgapci0: port 0x1800-0x1807 mem > >> 0xd0200000-0xd027ffff,0xc0000000-0xcfffffff,0xd0300000-0xd033ffff irq = 16 > > at > >> device 2.0 on pci0 > >> agp0: on vgapci0 > >> agp0: detected 7932k stolen memory > >> agp0: aperture size is 256M > >> vgapci1: mem 0xd0280000-0xd02fffff at device > > 2.1 > >> on pci0 > >> pci0: at device 27.0 (no driver attached) > >> pcib1: irq 16 at device 28.0 on pci0 > >> pci2: on pcib1 > >> mskc0: port 0x2000-0x20ff mem > >> 0xd0100000-0xd0103fff irq 16 at device 0.0 on pci2 > >> msk0: on msk= c0 > >> msk0: Ethernet address: 00:16:36:d1:56:ce > >> miibus0: on msk0 > >> e1000phy0: PHY 0 on miibus0 > >> e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > >> ukphy0: PHY 3 on miibus0 > >> ukphy0: no media present > >> ukphy1: PHY 6 on miibus0 > >> ukphy1: no media present > >> mskc0: [FILTER] > >> pcib2: irq 17 at device 28.1 on pci0 > >> pci3: on pcib2 > >> pcib3: irq 18 at device 28.2 on pci0 > >> pci4: on pcib3 > >> pcib4: irq 19 at device 28.3 on pci0 > >> pci5: on pcib4 > >> uhci0: port 0x1820-0x183f irq 23 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 0x1840-0x185f 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 0x1860-0x187f 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 > >> uhci3: port 0x1880-0x189f irq 16 at > > device > >> 29.3 on pci0 > >> uhci3: [GIANT-LOCKED] > >> uhci3: [ITHREAD] > >> usb3: on uhci3 > >> usb3: USB revision 1.0 > >> uhub3: on usb3 > >> uhub3: 2 ports with 2 removable, self powered > >> ehci0: mem > >> 0xd0544000-0xd05443ff irq 23 at device 29.7 on pci0 > >> ehci0: [GIANT-LOCKED] > >> ehci0: [ITHREAD] > >> usb4: EHCI version 1.0 > >> usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 > >> usb4: on ehci0 > >> usb4: USB revision 2.0 > >> uhub4: on usb4 > >> uhub4: 8 ports with 8 removable, self powered > >> pcib5: at device 30.0 on pci0 > >> pci10: on pcib5 > >> ath0: mem 0xd0000000-0xd000ffff at device 3.0 on pci10 > >> pcib5: unable to route slot 3 INTA > >> ath0: could not map interrupt > >> device_attach: ath0 attach returned 6 > >> cbb0: mem 0xd0014000-0xd0014fff irq 20 at device > > 9.0 > >> on pci10 > >> cardbus0: on cbb0 > >> pccard0: <16-bit PCCard bus> on cbb0 > >> cbb0: [ITHREAD] > >> pci10: at device 9.2 (no driver attached) > >> isab0: at device 31.0 on pci0 > >> isa0: on isab0 > >> atapci0: port > >> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x18b0-0x18bf at device 31.2 on pc= i0 > >> ata0: on atapci0 > >> ata0: [ITHREAD] > >> ata1: on atapci0 > >> ata1: [ITHREAD] > >> pci0: at device 31.3 (no driver attached) > >> pmtimer0 on isa0 > >> orm0: at iomem 0xcf000-0xcffff,0xdf800-0xdffff pnpid > >> ORM0000 on isa0 > >> atkbdc0: at port 0x60,0x64 on isa0 > >> 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 Generic PS/2 mouse, device ID 0 > >> ppc0: parallel port not found. > >> sc0: at flags 0x100 on isa0 > >> sc0: VGA <16 virtual consoles, flags=3D0x300> > >> sio0: configured irq 4 not in bitmap of probed irqs 0 > >> sio0: port may not be enabled > >> sio0: configured irq 4 not in bitmap of probed irqs 0 > >> sio0: port may not be enabled > >> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > >> sio0: type 8250 or not responding > >> sio0: [FILTER] > >> sio1: configured irq 3 not in bitmap of probed irqs 0 > >> sio1: port may not be enabled > >> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on > > isa0 > >> unknown: can't assign resources (memory) > >> unknown: can't assign resources (port) > >> unknown: can't assign resources (memory) > >> unknown: can't assign resources (memory) > >> unknown: can't assign resources (memory) > >> unknown: can't assign resources (memory) > >> unknown: can't assign resources (memory) > >> unknown: can't assign resources (irq) > >> Timecounter "TSC" frequency 1733412980 Hz quality 800 > >> Timecounters tick every 1.000 msec > >> ad0: 76319MB at ata0-master SATA150 > >> acd0: CDRW at ata1-master UDMA33 > >> GEOM_LABEL: Label for provider ad0s3 is msdosfs/DADOS. > >> Trying to mount root from ufs:/dev/ad0s1a > >> msk0: link state changed to UP > >> > >> #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D AC= PI ENABLED > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >> > >> Copyright (c) 1992-2007 The FreeBSD Project. > >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 19= 94 > >> The Regents of the University of California. All rights reserved. > >> FreeBSD is a registered trademark of The FreeBSD Foundation. > >> FreeBSD 7.0-CURRENT-200706 #0: Sun Jun 3 18:41:02 UTC 2007 > >> root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > >> WARNING: WITNESS option enabled, expect reduced performance. > >> ACPI APIC Table: > >> Timecounter "i8254" frequency 1193182 Hz quality 0 > >> CPU: Intel(R) Celeron(R) M CPU 430 @ 1.73GHz (1733.41-MHz > >> 686-class CPU) > >> Origin =3D "GenuineIntel" Id =3D 0x6e8 Stepping =3D 8 > >> > >> > > Features=3D0xafe9fbff > >> Features2=3D0xc109 > >> AMD Features=3D0x100000 > >> real memory =3D 526974976 (502 MB) > >> avail memory =3D 501760000 (478 MB) > >> ioapic0 irqs 0-23 on motherboard > >> kbd1 at kbdmux0 > >> ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, > > RF5413) > >> acpi0: on motherboard > >> acpi0: [ITHREAD] > >> acpi_hpet0: iomem 0xfed00000-0xfed003ff o= n > >> acpi0 > >> Timecounter "HPET" frequency 14318180 Hz quality 2000 > >> acpi0: Power Button (fixed) > >> unknown: I/O range not supported > >> acpi0: reservation of fed00000, 400 (3) failed > >> Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > >> acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 > >> acpi_ec0: port 0x62,0x66 on acpi0 > >> cpu0: on acpi0 > >> acpi_throttle0: on cpu0 > >> pcib0: port 0xcf8-0xcff on acpi0 > >> pci0: on pcib0 > >> vgapci0: port 0x1800-0x1807 mem > >> 0xd0200000-0xd027ffff,0xc0000000-0xcfffffff,0xd0300000-0xd033ffff irq = 16 > > at > >> device 2.0 on pci0 > >> agp0: on vgapci0 > >> agp0: detected 7932k stolen memory > >> agp0: aperture size is 256M > >> vgapci1: mem 0xd0280000-0xd02fffff at device > > 2.1 > >> on pci0 > >> pci0: at device 27.0 (no driver attached) > >> pcib1: irq 16 at device 28.0 on pci0 > >> pci2: on pcib1 > >> mskc0: irq 16 at device 0.0 o= n > >> pci2 > >> mskc0: 0x4000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). > >> mskc0: unknown device: id=3D0x00, rev=3D0x00 > >> device_attach: mskc0 attach returned 6 > >> pcib2: irq 17 at device 28.1 on pci0 > >> pci3: on pcib2 > >> pcib3: irq 18 at device 28.2 on pci0 > >> pci4: on pcib3 > >> uhci0: port 0x1820-0x183f irq 23 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 0x1840-0x185f 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 0x1860-0x187f 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 > >> uhci3: port 0x1880-0x189f irq 16 at > > device > >> 29.3 on pci0 > >> uhci3: [GIANT-LOCKED] > >> uhci3: [ITHREAD] > >> usb3: on uhci3 > >> usb3: USB revision 1.0 > >> uhub3: on usb3 > >> uhub3: 2 ports with 2 removable, self powered > >> ehci0: mem > >> 0xd0544000-0xd05443ff irq 23 at device 29.7 on pci0 > >> ehci0: [GIANT-LOCKED] > >> ehci0: [ITHREAD] > >> usb4: EHCI version 1.0 > >> usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 > >> usb4: on ehci0 > >> usb4: USB revision 2.0 > >> uhub4: on usb4 > >> uhub4: 8 ports with 8 removable, self powered > >> pcib4: at device 30.0 on pci0 > >> pci10: on pcib4 > >> ath0: mem 0xd0000000-0xd000ffff at device 3.0 on pci10 > >> ath0: [ITHREAD] > >> ath0: using obsoleted if_watchdog interface > >> ath0: Ethernet address: 00:19:7d:47:ed:84 > >> ath0: mac 7.8 phy 4.5 radio 5.6 > >> cbb0: mem 0xd0014000-0xd0014fff irq 20 at device > > 9.0 > >> on pci10 > >> cardbus0: on cbb0 > >> pccard0: <16-bit PCCard bus> on cbb0 > >> cbb0: [ITHREAD] > >> pci10: at device 9.2 (no driver attached) > >> isab0: at device 31.0 on pci0 > >> isa0: on isab0 > >> atapci0: port > >> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x18b0-0x18bf at device 31.2 on pc= i0 > >> ata0: on atapci0 > >> ata0: [ITHREAD] > >> ata1: on atapci0 > >> ata1: [ITHREAD] > >> pci0: at device 31.3 (no driver attached) > >> acpi_acad0: on acpi0 > >> battery0: on acpi0 > >> acpi_lid0: on acpi0 > >> acpi_button0: on acpi0 > >> acpi_button1: on acpi0 > >> acpi_tz0: on acpi0 > >> atkbdc0: port 0x60,0x64 irq 1 on acpi0 > >> atkbd0: irq 1 on atkbdc0 > >> kbd0 at atkbd0 > >> atkbd0: [GIANT-LOCKED] > >> atkbd0: [ITHREAD] > >> psm0: irq 12 on atkbdc0 > >> psm0: [GIANT-LOCKED] > >> psm0: [ITHREAD] > >> psm0: model Generic PS/2 mouse, device ID 0 > >> pmtimer0 on isa0 > >> orm0: at iomem 0xcf000-0xcffff,0xdf800-0xdffff pnpid > >> ORM0000 on isa0 > >> ppc0: parallel port not found. > >> sc0: at flags 0x100 on isa0 > >> sc0: VGA <16 virtual consoles, flags=3D0x300> > >> sio0: configured irq 4 not in bitmap of probed irqs 0 > >> sio0: port may not be enabled > >> sio0: configured irq 4 not in bitmap of probed irqs 0 > >> sio0: port may not be enabled > >> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > >> sio0: type 8250 or not responding > >> sio0: [FILTER] > >> sio1: configured irq 3 not in bitmap of probed irqs 0 > >> sio1: port may not be enabled > >> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on > > isa0 > >> Timecounter "TSC" frequency 1733409431 Hz quality 800 > >> Timecounters tick every 1.000 msec > >> ad0: 76319MB at ata0-master SATA150 > >> acd0: CDRW at ata1-master UDMA33 > >> GEOM_LABEL: Label for provider ad0s3 is msdosfs/DADOS. > >> Trying to mount root from ufs:/dev/ad0s1a > >> > >> #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D PCICONF -LV > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >> > >> hostb0@pci0:0:0: class=3D0x060000 card=3D0x01101025 chip=3D0x27a08086 = rev=3D0x03 > >> hdr=3D0x00 > >> vendor =3D 'Intel Corporation' > >> device =3D '955XM/945GM/PM/GMS/940GML Express Processor to DRA= M > >> Controller' > >> class =3D bridge > >> subclass =3D HOST-PCI > >> vgapci0@pci0:2:0: class=3D0x030000 card=3D0x01101025 chip=3D0x27a28086 > > rev=3D0x03 > >> hdr=3D0x00 > >> vendor =3D 'Intel Corporation' > >> device =3D 'Mobile Integrated Graphics Controller' > >> class =3D display > >> subclass =3D VGA > >> vgapci1@pci0:2:1: class=3D0x038000 card=3D0x01101025 chip=3D0x27a68086 > > rev=3D0x03 > >> hdr=3D0x00 > >> vendor =3D 'Intel Corporation' > >> device =3D 'Mobile Integrated Graphics Controller' > >> class =3D display > >> none0@pci0:27:0: class=3D0x040300 card=3D0x01101025 chip=3D0x27d88086 = rev=3D0x02 > >> hdr=3D0x00 > >> vendor =3D 'Intel Corporation' > >> device =3D '82801G (ICH7 Family) High Definition Audio' > >> class =3D multimedia > >> pcib1@pci0:28:0: class=3D0x060400 card=3D0x01101025 chip=3D0x27d08086 = rev=3D0x02 > >> hdr=3D0x01 > >> vendor =3D 'Intel Corporation' > >> device =3D '82801G (ICH7 Family) PCI Express Root Port' > >> class =3D bridge > >> subclass =3D PCI-PCI > >> pcib2@pci0:28:1: class=3D0x060400 card=3D0x01101025 chip=3D0x27d28086 = rev=3D0x02 > >> hdr=3D0x01 > >> vendor =3D 'Intel Corporation' > >> device =3D '82801G (ICH7 Family) PCI Express Root Port' > >> class =3D bridge > >> subclass =3D PCI-PCI > >> pcib3@pci0:28:2: class=3D0x060400 card=3D0x01101025 chip=3D0x27d48086 = rev=3D0x02 > >> hdr=3D0x01 > >> vendor =3D 'Intel Corporation' > >> device =3D '82801G (ICH7 Family) PCI Express Root Port' > >> class =3D bridge > >> subclass =3D PCI-PCI > >> uhci0@pci0:29:0: class=3D0x0c0300 card=3D0x01101025 chip=3D0x27c88086 = rev=3D0x02 > >> hdr=3D0x00 > >> vendor =3D 'Intel Corporation' > >> device =3D '82801G (ICH7 Family) USB Universal Host Controller= ' > >> class =3D serial bus > >> subclass =3D USB > >> uhci1@pci0:29:1: class=3D0x0c0300 card=3D0x01101025 chip=3D0x27c98086 = rev=3D0x02 > >> hdr=3D0x00 > >> vendor =3D 'Intel Corporation' > >> device =3D '82801G (ICH7 Family) USB Universal Host Controller= ' > >> class =3D serial bus > >> subclass =3D USB > >> uhci2@pci0:29:2: class=3D0x0c0300 card=3D0x01101025 chip=3D0x27ca8086 = rev=3D0x02 > >> hdr=3D0x00 > >> vendor =3D 'Intel Corporation' > >> device =3D '82801G (ICH7 Family) USB Universal Host Controller= ' > >> class =3D serial bus > >> subclass =3D USB > >> uhci3@pci0:29:3: class=3D0x0c0300 card=3D0x01101025 chip=3D0x27cb8086 = rev=3D0x02 > >> hdr=3D0x00 > >> vendor =3D 'Intel Corporation' > >> device =3D '82801G (ICH7 Family) USB Universal Host Controller= ' > >> class =3D serial bus > >> subclass =3D USB > >> ehci0@pci0:29:7: class=3D0x0c0320 card=3D0x01101025 chip=3D0x27cc8086 = rev=3D0x02 > >> hdr=3D0x00 > >> vendor =3D 'Intel Corporation' > >> device =3D '82801G (ICH7 Family) USB 2.0 Enhanced Host Control= ler' > >> class =3D serial bus > >> subclass =3D USB > >> pcib4@pci0:30:0: class=3D0x060401 card=3D0x01101025 chip=3D0x24488086 = rev=3D0xe2 > >> hdr=3D0x01 > >> vendor =3D 'Intel Corporation' > >> device =3D '82801BAM/CAM/DBM (ICH2-M/3-M/4-M) Hub Interface to= PCI > >> Bridge' > >> class =3D bridge > >> subclass =3D PCI-PCI > >> isab0@pci0:31:0: class=3D0x060100 card=3D0x01101025 chip=3D0x27b98086 = rev=3D0x02 > >> hdr=3D0x00 > >> vendor =3D 'Intel Corporation' > >> device =3D '82801GBM (ICH7-M) LPC Interface Controller' > >> class =3D bridge > >> subclass =3D PCI-ISA > >> atapci0@pci0:31:2: class=3D0x010180 card=3D0x01101025 chip=3D0x27c4808= 6 > > rev=3D0x02 > >> hdr=3D0x00 > >> vendor =3D 'Intel Corporation' > >> device =3D '82801GBM/GHM (ICH7-M Family) Serial ATA Storage > >> Controller' > >> class =3D mass storage > >> subclass =3D ATA > >> none1@pci0:31:3: class=3D0x0c0500 card=3D0x01101025 chip=3D0x27da8086 = rev=3D0x02 > >> hdr=3D0x00 > >> vendor =3D 'Intel Corporation' > >> device =3D '82801G (ICH7 Family) SMBus Controller' > >> class =3D serial bus > >> subclass =3D SMBus > >> mskc0@pci2:0:0: class=3D0x020000 card=3D0x01101025 chip=3D0x435211ab r= ev=3D0x14 > >> hdr=3D0x00 > >> vendor =3D 'Marvell Semiconductor (Was: Galileo Technology Ltd= )' > >> device =3D 'Yukon 88E8038 PCI-E Fast Ethernet Controller' > >> class =3D network > >> subclass =3D ethernet > >> ath0@pci10:3:0: class=3D0x020000 card=3D0x04181468 chip=3D0x001a168c r= ev=3D0x01 > >> hdr=3D0x00 > >> vendor =3D 'Atheros Communications Inc.' > >> device =3D 'Atheros AR5005G Atheros AR5005G 802.11abg NIC Chip= set' > >> class =3D network > >> subclass =3D ethernet > >> cbb0@pci10:9:0: class=3D0x060700 card=3D0x01101025 chip=3D0x8039104c r= ev=3D0x00 > >> hdr=3D0x02 > >> vendor =3D 'Texas Instruments (TI)' > >> device =3D 'PCIxx12 Cardbus Controller' > >> class =3D bridge > >> subclass =3D PCI-CardBus > >> none2@pci10:9:2: class=3D0x018000 card=3D0x01101025 chip=3D0x803b104c = rev=3D0x00 > >> hdr=3D0x00 > >> vendor =3D 'Texas Instruments (TI)' > >> device =3D 'PCIxx12 Integrated Flash Media Controller' > >> class =3D mass storage >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 15:02:24 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8A3716A419 for ; Fri, 24 Aug 2007 15:02:24 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.bluestop.org (muon.bluestop.org [80.68.94.188]) by mx1.freebsd.org (Postfix) with ESMTP id 7163213C467 for ; Fri, 24 Aug 2007 15:02:24 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.draftnet (dyn-62-56-125-93.dslaccess.co.uk [62.56.125.93]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTP id E3C8F3000D; Fri, 24 Aug 2007 15:58:22 +0100 (BST) Message-ID: <46CEF2C0.6010904@cran.org.uk> Date: Fri, 24 Aug 2007 16:01:20 +0100 From: Bruce Cran User-Agent: Thunderbird 2.0.0.6 (X11/20070809) MIME-Version: 1.0 To: Hidetoshi Shimokawa References: <3979a4b0707291120v4927a20cm357b845f6d1f3567@mail.gmail.com> <46BE1D6C.6040903@cran.org.uk> <626eb4530708221937h31c8f37fu9527e941ed4000b6@mail.gmail.com> In-Reply-To: <626eb4530708221937h31c8f37fu9527e941ed4000b6@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: KOT MATPOCKuH , current@freebsd.org Subject: Re: console hangs after setting hostname X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 15:02:25 -0000 Hidetoshi Shimokawa wrote: > It looks that the low level console is not locked though the high level console > is locked by Giant. > > Could you try the attached patch? > Thanks, after applying the patch the console doesn't hang, and remains available. The garbled output still occurs though: GEOM_LABEL: Label for provider da0s2 is msdosfs/IPOD. [Unplug device] umass0: at uhub5 port 1 (addr 2) disconnected (da0:umass-simG0E:O0M:_0L:A0B)E:L :l oLsatb edle vmiscdeos fs(/dIaP0O:Du mraesmso-vseidm.0: 0:0:0): removing device entry umass0: detached -- Bruce Cran > > On 8/12/07, Bruce Cran wrote: > >> KOT MATPOCKuH wrote: >> >>> I got a problem. After messages on console: >>> ... >>> Mounting local files systems:. >>> Setting hostname: green. >>> fxp: link state changed to UP >>> nfe0: link state changed to DOWN >>> >>> console hangs. >>> No any new messages, I can't input anything from keyboard, changing virtual >>> consoles is not working. After X is started, console is not switched to xdm >>> display. >>> But system is works - I can login to system via ssh, ... >>> >>> dmesg.boot is attached. >>> >>> Where is a problem and what I need to do? :) >>> >>> >> I'm also seeing the console hang, but in a different situation. If I >> attach and remove my iPod the console hangs - the only key press that's >> accepted is ctrl-alt-esc to break into the debugger. >> >> umass0: on uhub5 >> da0 at umass-sim0 bus 0 target 0 lun 0 >> da0: Removable Direct Access SCSI-0 device >> da0: 40.000MB/s transfers >> da0: 19073MB (39063024 512 byte sectors: 255H 63S/T 2431C) >> (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 2 54 d ef 0 0 1 0 >> (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error >> (da0:umass-sim0:0:0:0): SCSI Status: Check Condition >> (da0:umass-sim0:0:0:0): ILLEGAL REQUEST asc:21,0 >> (da0:umass-sim0:0:0:0): Logical block address out of range >> (da0:umass-sim0:0:0:0): Unretryable error >> (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 2 54 d ef 0 0 1 0 >> (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error >> (da0:umass-sim0:0:0:0): SCSI Status: Check Condition >> (da0:umass-sim0:0:0:0): ILLEGAL REQUEST asc:21,0 >> (da0:umass-sim0:0:0:0): Logical block address out of range >> (da0:umass-sim0:0:0:0): Unretryable error >> GEOM_LABEL: Label for provider da0s2 is msdosfs/IPOD. >> >> When I remove the iPod I get the following messages: >> >> umass0: at uhub5 port 1 (addr 2) disconnected >> da0:umass-sim0:0:0G:0EO :M _LlAoBst L d ev aibceel >> )m(sd ao0s:fs m/aIsPsO-Ds irme0m:o0v:ed :.0 >> : removing device entry >> umass0: detached >> >> enter: manual escape to debugger >> [thread pid 19 tid 100018 ] >> Stopped at kdb_enter+0x31: leave >> db> wh >> Tracing pid 19 tid 100018 td 0xffffff000112d350 >> kdb_enter() >> scgetc() >> sckbdevent() >> kbdmux_intr() >> kdbmux_kdb_intr() >> taskqueue_run() >> taskqueue_swi_giant_run() >> ithread_loop >> fork_exit() >> fork_trampoline() >> --- trap 0, rip = 0, rsp = 0xffffffff9ca59d30, rbp = 0 --- >> db> >> >> I'm using ULE. >> uname -a: >> FreeBSD muon.draftnet 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Sat Aug 11 >> 21:07:09 BST 2007 >> brucec@muon.draftnet:/usr/obj/usr/src/sys/INSPIRON amd64 From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 16:29:41 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9846516A419 for ; Fri, 24 Aug 2007 16:29:41 +0000 (UTC) (envelope-from matpockuh@gmail.com) Received: from ik-out-1112.google.com (ik-out-1112.google.com [66.249.90.183]) by mx1.freebsd.org (Postfix) with ESMTP id 1BC5813C459 for ; Fri, 24 Aug 2007 16:29:40 +0000 (UTC) (envelope-from matpockuh@gmail.com) Received: by ik-out-1112.google.com with SMTP id c21so407251ika for ; Fri, 24 Aug 2007 09:29:39 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=AP2NauJMRHVQQjzcbtPWjqvLdl7ZTLfxfF1Nblp/bG7A3eSRTbXwtnEmxx4BWIffaQCYhisiCVDP1U139w4Dj0bBzhNsJH6l7v1tIkmNVznDJS53W0FcxYf+RgWqjjPXN5W+NmhZ6ayAjXdSasS0izRHnOiZhHuZSNdB0vwkc5U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=uGWkI0gEsdgLUmNOWYVD6GOWIeeqv/CE0/BV6mgookNmC2XbH/8l6RSnHxN62OFCNhVG//BDz8p4zZmmdqRshZeOcheAopREJ1CaqXdsKTXfwshEV9NTmO7pptowNeTd7yZlrQ4qpxVBe+cKeHmILolI79D7l+cdJsCk8MJ5V6c= Received: by 10.78.193.5 with SMTP id q5mr2106493huf.1187972979235; Fri, 24 Aug 2007 09:29:39 -0700 (PDT) Received: by 10.78.160.10 with HTTP; Fri, 24 Aug 2007 09:29:39 -0700 (PDT) Message-ID: <3979a4b0708240929p5f42b54ev412d5af16e9fb020@mail.gmail.com> Date: Fri, 24 Aug 2007 20:29:39 +0400 From: "KOT MATPOCKuH" To: "Hidetoshi Shimokawa" In-Reply-To: <626eb4530708221937h31c8f37fu9527e941ed4000b6@mail.gmail.com> MIME-Version: 1.0 References: <3979a4b0707291120v4927a20cm357b845f6d1f3567@mail.gmail.com> <46BE1D6C.6040903@cran.org.uk> <626eb4530708221937h31c8f37fu9527e941ed4000b6@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Bruce Cran , current@freebsd.org Subject: Re: console hangs after setting hostname X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 16:29:41 -0000 On 8/23/07, Hidetoshi Shimokawa wrote: > > It looks that the low level console is not locked though the high level > console > is locked by Giant. > > Could you try the attached patch? > Thanks you! Console doesn't hangs... ...and I'm too see corrupt messages in /var/run/dmesg.boot and on console: cd0: <_NEC DVD_RW ND-3540A 1.01> Removable CD-ROM SCSI-0 device cdS0M:P :3 3A.P 0C0P0UM B#/s1 tLraaunnscfheerds! -- MATPOCKuH From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 17:30:15 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 593BE16A41B for ; Fri, 24 Aug 2007 17:30:15 +0000 (UTC) (envelope-from brooks@illuminati.org) Received: from zmail.illuminati.org (mail.illuminati.org [70.42.141.33]) by mx1.freebsd.org (Postfix) with ESMTP id 4277A13C4B3 for ; Fri, 24 Aug 2007 17:30:15 +0000 (UTC) (envelope-from brooks@illuminati.org) Received: from localhost (localhost.localdomain [127.0.0.1]) by zmail.illuminati.org (Postfix) with ESMTP id 0AA8016C86E0 for ; Fri, 24 Aug 2007 09:57:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at X-Spam-Score: -4.38 X-Spam-Level: X-Spam-Status: No, score=-4.38 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, AWL=0.019, BAYES_00=-2.599] Received: from zmail.illuminati.org ([127.0.0.1]) by localhost (zmail.illuminati.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rP7+Eor843dU for ; Fri, 24 Aug 2007 09:57:40 -0700 (PDT) Received: from zmail.illuminati.org (zmail.illuminati.org [10.32.1.33]) by zmail.illuminati.org (Postfix) with ESMTP id EB53216C86DE for ; Fri, 24 Aug 2007 09:57:40 -0700 (PDT) Date: Fri, 24 Aug 2007 09:57:40 -0700 (PDT) From: Brooks Talley To: freebsd-current@freebsd.org Message-ID: <31796970.30371187974660912.JavaMail.root@zmail.illuminati.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [63.231.27.116] Subject: ZFS + Samba/NFS = ugh X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 17:30:15 -0000 Hi everyone. So far, 7.0 is being pretty darned sweet for me. It's probably a known issue, but I haven't seen it referenced anywhere: it seems that ZFS filesystems can be shared/exported with Samba/NFS, but they do not accept any kind of writes over the network, and have other issues with smbclient ("Error in diskattr: Call returned zero bytes (EOF)" comes up a lot). Anyone run into this? Any known fixes? -b From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 18:41:53 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 687AC16A417 for ; Fri, 24 Aug 2007 18:41:53 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 1A83413C467 for ; Fri, 24 Aug 2007 18:41:52 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IOe6Q-0003i7-GI for freebsd-current@freebsd.org; Fri, 24 Aug 2007 20:41:50 +0200 Received: from 78-0-73-123.adsl.net.t-com.hr ([78.0.73.123]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 24 Aug 2007 20:41:50 +0200 Received: from ivoras by 78-0-73-123.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 24 Aug 2007 20:41:50 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Fri, 24 Aug 2007 20:41:34 +0200 Lines: 37 Message-ID: References: <31796970.30371187974660912.JavaMail.root@zmail.illuminati.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigDC337C654CE1B4399DCD9AC7" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 78-0-73-123.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) In-Reply-To: <31796970.30371187974660912.JavaMail.root@zmail.illuminati.org> X-Enigmail-Version: 0.95.3 Sender: news Subject: Re: ZFS + Samba/NFS = ugh X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 18:41:53 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDC337C654CE1B4399DCD9AC7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Brooks Talley wrote: > Hi everyone. So far, 7.0 is being pretty darned sweet for me. >=20 > It's probably a known issue, but I haven't seen it referenced anywhere:= it seems that ZFS filesystems can be shared/exported with Samba/NFS, but= they do not accept any kind of writes over the network, and have other i= ssues with smbclient ("Error in diskattr: Call returned zero bytes (EOF)"= comes up a lot). >=20 > Anyone run into this? Any known fixes? NFS _and_ Samba? Samba is a userland daemon - if it had problems, other applications would have also had problems. --------------enigDC337C654CE1B4399DCD9AC7 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.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGzyZjldnAQVacBcgRAsTuAJ9AbfG9g3NcCTKW+k5SIxfEhuPFAACeNIhe O+NAinnI5udp0gHa2+idrqk= =3Two -----END PGP SIGNATURE----- --------------enigDC337C654CE1B4399DCD9AC7-- From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 15:19:29 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C66616A468; Fri, 24 Aug 2007 15:19:29 +0000 (UTC) (envelope-from jaharkes@cs.cmu.edu) Received: from delft.aura.cs.cmu.edu (unknown [IPv6:2002:8002:ce58::1]) by mx1.freebsd.org (Postfix) with ESMTP id A241913C47E; Fri, 24 Aug 2007 15:19:28 +0000 (UTC) (envelope-from jaharkes@cs.cmu.edu) Received: from jaharkes by delft.aura.cs.cmu.edu with local (Exim 4.67) (envelope-from ) id 1IOawZ-0003pY-Ia; Fri, 24 Aug 2007 11:19:27 -0400 Date: Fri, 24 Aug 2007 11:19:27 -0400 From: Jan Harkes To: Nikolay Pavlov Message-ID: <20070824151927.GA11642@cs.cmu.edu> Mail-Followup-To: Nikolay Pavlov , freebsd-current@freebsd.org, rwatson@freebsd.org References: <200708202340.29678.qpadla@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200708202340.29678.qpadla@gmail.com> User-Agent: Mutt/1.5.16 (2007-06-11) X-Mailman-Approved-At: Fri, 24 Aug 2007 19:59:30 +0000 Cc: freebsd-current@freebsd.org, rwatson@freebsd.org Subject: Re: And probably the final crash for today's current :) (panic: filesystem goof: vop_panic[vop_print]) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 15:19:29 -0000 On Mon, Aug 20, 2007 at 11:40:29PM +0300, Nikolay Pavlov wrote: > I am testing latest coda client code. > After simple ls -l /coda i am getting this panic: Coda's kernel module performed various VOP_OPEN/CLOSE/READ operations on the vnodes of the 'container files' (files containing the actual data which are created on a normal (non-coda) filesystem and handed to the Coda kernel module when a Coda file is opened). The following patch adds locking around VOP_ operations. I ran some tests and it seems like I got them all. For some reason I could only get the warnings to go away when using exclusive locks, but since the overhead in our case really is in userspace and we still hold the giant lock pretty much everywhere there shouldn't be a measurable difference. The one questionable change in this patch is in coda_namecache.c. We are flushing some internal name->vnode lookup cache and while doing so we check if VV_TEXT has been set in ->v_vflags. We really should take a lock there, but I have no idea how to propagate a struct thread * down there (since this flush is called from some places like vc_nb_write (write on the /dev/cfs0 device) were it isn't obvious to me if it has access to the thread context. So I commented out the assertion just to shut up the warning. I don't really know what the preferred policy in this case is, the flush only triggered during unmount and the assertion doesn't drops the kernel in the debugger when it is compiled with the default options. Jan ------------------------------------------------------------------- We need to lock before we call VOP_ operations on the container files. diff --git a/coda_namecache.c b/coda_namecache.c index 916e605..0bf284d 100644 --- a/coda_namecache.c +++ b/coda_namecache.c @@ -607,7 +607,10 @@ coda_nc_flush(dcstat) } vrele(CTOV(cncp->dcp)); - ASSERT_VOP_LOCKED(CTOV(cncp->cp), "coda_nc_flush"); + /* We really should lock because we're looking at + * ->v_vflag. On the other hand we're just looking and + * it isn't clear how to propagate *td to here. */ + /* ASSERT_VOP_LOCKED(CTOV(cncp->cp), "coda_nc_flush");*/ if (CTOV(cncp->cp)->v_vflag & VV_TEXT) { if (coda_vmflush(cncp->cp)) CODADEBUG(CODA_FLUSH, diff --git a/coda_vfsops.c b/coda_vfsops.c index bfd0834..bc24aec 100644 --- a/coda_vfsops.c +++ b/coda_vfsops.c @@ -229,8 +229,11 @@ coda_unmount(vfsp, mntflags, td) vrele(mi->mi_rootvp); vrele(coda_ctlvp); active = coda_kill(vfsp, NOT_DOWNCALL); - ASSERT_VOP_LOCKED(mi->mi_rootvp, "coda_unmount"); + + vn_lock(mi->mi_rootvp, LK_RETRY|LK_EXCLUSIVE, td); mi->mi_rootvp->v_vflag &= ~VV_ROOT; + VOP_UNLOCK(mi->mi_rootvp, 0, td); + error = vflush(mi->mi_vfsp, 0, FORCECLOSE, td); #ifdef CODA_VERBOSE printf("coda_unmount: active = %d, vflush active %d\n", active, error); diff --git a/coda_vnops.c b/coda_vnops.c index 11f1c39..968fe19 100644 --- a/coda_vnops.c +++ b/coda_vnops.c @@ -240,7 +240,10 @@ coda_open(struct vop_open_args *ap) } /* Open the cache file. */ + vn_lock(vp, LK_RETRY|LK_EXCLUSIVE, td); error = VOP_OPEN(vp, flag, cred, td, NULL); + VOP_UNLOCK(vp, 0, td); + if (error) { printf("coda_open: VOP_OPEN on container failed %d\n", error); return (error); @@ -274,7 +277,9 @@ coda_close(struct vop_close_args *ap) } if (cp->c_ovp) { + vn_lock(cp->c_ovp, LK_RETRY|LK_EXCLUSIVE, td); VOP_CLOSE(cp->c_ovp, flag, cred, td); /* Do errors matter here? */ + VOP_UNLOCK(cp->c_ovp, 0, td); vrele(cp->c_ovp); } #ifdef CODA_VERBOSE @@ -346,8 +351,10 @@ coda_rdwr(struct vnode *vp, struct uio *uiop, enum uio_rw rw, int ioflag, if (cfvp == NULL) { opened_internally = 1; MARK_INT_GEN(CODA_OPEN_STATS); - error = VOP_OPEN(vp, (rw == UIO_READ ? FREAD : FWRITE), cred, td, NULL); printf("coda_rdwr: Internally Opening %p\n", vp); + vn_lock(vp, LK_RETRY|LK_EXCLUSIVE, td); + error = VOP_OPEN(vp, (rw == UIO_READ ? FREAD : FWRITE), cred, td, NULL); + VOP_UNLOCK(vp, 0, td); if (error) { printf("coda_rdwr: VOP_OPEN on container failed %d\n", error); return (error); @@ -358,6 +365,8 @@ coda_rdwr(struct vnode *vp, struct uio *uiop, enum uio_rw rw, int ioflag, /* Have UFS handle the call. */ CODADEBUG(CODA_RDWR, myprintf(("indirect rdwr: fid = %s, refcnt = %d\n", coda_f2s(&cp->c_fid), CTOV(cp)->v_usecount)); ) + + vn_lock(cfvp, LK_RETRY|LK_EXCLUSIVE, td); if (rw == UIO_READ) { error = VOP_READ(cfvp, uiop, ioflag, cred); } else { @@ -371,6 +380,7 @@ coda_rdwr(struct vnode *vp, struct uio *uiop, enum uio_rw rw, int ioflag, } } } + VOP_UNLOCK(cfvp, 0, td); if (error) MARK_INT_FAIL(CODA_RDWR_STATS); @@ -380,7 +390,9 @@ coda_rdwr(struct vnode *vp, struct uio *uiop, enum uio_rw rw, int ioflag, /* Do an internal close if necessary. */ if (opened_internally) { MARK_INT_GEN(CODA_CLOSE_STATS); + vn_lock(vp, LK_RETRY|LK_EXCLUSIVE, td); (void)VOP_CLOSE(vp, (rw == UIO_READ ? FREAD : FWRITE), cred, td); + VOP_UNLOCK(vp, 0, td); } /* Invalidate cached attributes if writing. */ @@ -694,8 +706,11 @@ coda_fsync(struct vop_fsync_args *ap) return(0); } - if (convp) + if (convp) { + vn_lock(convp, LK_RETRY|LK_EXCLUSIVE, td); VOP_FSYNC(convp, MNT_WAIT, td); + VOP_UNLOCK(convp, 0, td); + } /* * We see fsyncs with usecount == 1 then usecount == 0. @@ -1408,8 +1423,11 @@ coda_symlink(struct vop_symlink_args *ap) /* Invalidate the parent's attr cache, the modification time has changed */ tdcp->c_flags &= ~C_VATTR; - if (error == 0) + if (error == 0) { + vn_lock(tdvp, LK_RETRY|LK_EXCLUSIVE, td); error = VOP_LOOKUP(tdvp, vpp, cnp); + VOP_UNLOCK(tdvp, 0, td); + } exit: CODADEBUG(CODA_SYMLINK, myprintf(("in symlink result %d\n",error)); ) @@ -1452,22 +1470,29 @@ coda_readdir(struct vop_readdir_args *ap) { /* If directory is not already open do an "internal open" on it. */ int opened_internally = 0; + if (cp->c_ovp == NULL) { opened_internally = 1; MARK_INT_GEN(CODA_OPEN_STATS); - error = VOP_OPEN(vp, FREAD, cred, td, NULL); + + vn_lock(vp, LK_RETRY|LK_EXCLUSIVE, td); printf("coda_readdir: Internally Opening %p\n", vp); + error = VOP_OPEN(vp, FREAD, cred, td, NULL); + VOP_UNLOCK(vp, 0, td); + if (error) { printf("coda_readdir: VOP_OPEN on container failed %d\n", error); return (error); } } - + + vn_lock(cp->c_ovp, LK_RETRY|LK_EXCLUSIVE, td); /* Have UFS handle the call. */ CODADEBUG(CODA_READDIR, myprintf(("indirect readdir: fid = %s, refcnt = %d\n", coda_f2s(&cp->c_fid), vp->v_usecount)); ) error = VOP_READDIR(cp->c_ovp, uiop, cred, eofflag, ncookies, cookies); - + VOP_UNLOCK(cp->c_ovp, 0, td); + if (error) MARK_INT_FAIL(CODA_READDIR_STATS); else @@ -1476,7 +1501,9 @@ coda_readdir(struct vop_readdir_args *ap) /* Do an "internal close" if necessary. */ if (opened_internally) { MARK_INT_GEN(CODA_CLOSE_STATS); + vn_lock(vp, LK_RETRY|LK_EXCLUSIVE, td); (void)VOP_CLOSE(vp, FREAD, cred, td); + VOP_UNLOCK(vp, 0, td); } } @@ -1505,6 +1532,7 @@ coda_bmap(struct vop_bmap_args *ap) cp = VTOC(vp); if (cp->c_ovp) { return EINVAL; +/* looks like we never actually call VOP_BMAP, probably would need locking */ ret = VOP_BMAP(cp->c_ovp, bn, bop, bnp, ap->a_runp, ap->a_runb); #if 0 printf("VOP_BMAP(cp->c_ovp %p, bn %p, bop %p, bnp %lld, ap->a_runp %p, ap->a_runb %p) = %d\n", From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 20:33:00 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CF3B16A41A for ; Fri, 24 Aug 2007 20:33:00 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 34BBF13C468 for ; Fri, 24 Aug 2007 20:33:00 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id C26C6244C5; Fri, 24 Aug 2007 16:32:59 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 24 Aug 2007 16:32:59 -0400 X-Sasl-enc: EaqxPf2wtCkM03foHpNNk5zC/9dg7BjWmsg0ILtZVr+K 1187987579 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 ESMTP id 4D32A20E8D; Fri, 24 Aug 2007 16:32:59 -0400 (EDT) Message-ID: <46CF407A.2050906@FreeBSD.org> Date: Fri, 24 Aug 2007 21:32:58 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.4 (X11/20070630) MIME-Version: 1.0 To: Andrew Turner References: <20070824181627.57bed401@hermies.int.fubar.geek.nz> In-Reply-To: <20070824181627.57bed401@hermies.int.fubar.geek.nz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD on xen hvm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 20:33:00 -0000 Andrew Turner wrote: > I've been working on getting -CURRENT i386 to boot on the Xen > amd64 hvm. It provides full vitalization to allow operating systems to > boot without modification. > By the way, many thanks for attempting this and publishing your results, it is greatly appreciated. Cheers BMS From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 20:35:45 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55E0516A417 for ; Fri, 24 Aug 2007 20:35:45 +0000 (UTC) (envelope-from erik@cepheid.org) Received: from mail.cepheid.org (wintermute.cepheid.org [64.92.165.98]) by mx1.freebsd.org (Postfix) with ESMTP id 3B5F013C457 for ; Fri, 24 Aug 2007 20:35:45 +0000 (UTC) (envelope-from erik@cepheid.org) Received: by mail.cepheid.org (Postfix, from userid 1006) id 97957170E4; Fri, 24 Aug 2007 15:07:26 -0500 (CDT) Date: Fri, 24 Aug 2007 15:07:26 -0500 From: Erik Osterholm To: Ivan Voras Message-ID: <20070824200726.GA66242@idoru.cepheid.org> Mail-Followup-To: Erik Osterholm , Ivan Voras , freebsd-current@freebsd.org References: <31796970.30371187974660912.JavaMail.root@zmail.illuminati.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: freebsd-current@freebsd.org Subject: Re: ZFS + Samba/NFS = ugh X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 20:35:45 -0000 On Fri, Aug 24, 2007 at 08:41:34PM +0200, Ivan Voras wrote: > Brooks Talley wrote: > > Hi everyone. So far, 7.0 is being pretty darned sweet for me. > > > > It's probably a known issue, but I haven't seen it referenced anywhere: it seems that ZFS filesystems can be shared/exported with Samba/NFS, but they do not accept any kind of writes over the network, and have other issues with smbclient ("Error in diskattr: Call returned zero bytes (EOF)" comes up a lot). > > > > Anyone run into this? Any known fixes? > > NFS _and_ Samba? > > Samba is a userland daemon - if it had problems, other applications > would have also had problems. The issue has been discussed before. It is very real: http://lists.freebsd.org/pipermail/freebsd-current/2007-June/072991.html Erik From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 21:24:04 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B16816A417 for ; Fri, 24 Aug 2007 21:24:04 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.freebsd.org (Postfix) with ESMTP id C2A1313C483 for ; Fri, 24 Aug 2007 21:24:03 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so801314nfb for ; Fri, 24 Aug 2007 14:24:02 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=N/rxAZuJHUC8XYOv+6di/9eHesal/WB1EPFsRVClOwRf6TMUfZHs21mvd6+e+xWvEilQq2gL1AP5+HZN7HGJUbIdQC6SQKohSt6ocYjS7bo7SoqphSa2MtEi+DW7todQsBzLiX13UfenrAnvxdXGt+01qdhT/h7W5B53WE9L+A4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=rfdw4Gr7iGBFKs19mx1l5RL+9JDA8UFL0n4Xhk44/UZKGM4Js2LfRg8fBebySqh7kGq7kHkAdDu7wSYwNN0gVdbRobIJVJoUNJfY2dihYSewm+P7Od6g6Ulbj7zwHzz3jlGoC+xVskRU5mYK8PZp6/C3UsQUD1fO+qE3uHAbEqc= Received: by 10.86.60.7 with SMTP id i7mr2568479fga.1187990642490; Fri, 24 Aug 2007 14:24:02 -0700 (PDT) Received: by 10.86.71.6 with HTTP; Fri, 24 Aug 2007 14:24:02 -0700 (PDT) Message-ID: <790a9fff0708241424r44517517h357318b8a2004982@mail.gmail.com> Date: Fri, 24 Aug 2007 16:24:02 -0500 From: "Scot Hetzel" To: "Brook Tally" , "Ivan Voras" In-Reply-To: <20070824200726.GA66242@idoru.cepheid.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <31796970.30371187974660912.JavaMail.root@zmail.illuminati.org> <20070824200726.GA66242@idoru.cepheid.org> Cc: freebsd-current@freebsd.org, Erik Osterholm Subject: Re: ZFS + Samba/NFS = ugh X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 21:24:04 -0000 On 8/24/07, Erik Osterholm wrote: > On Fri, Aug 24, 2007 at 08:41:34PM +0200, Ivan Voras wrote: > > Brooks Talley wrote: > > > Hi everyone. So far, 7.0 is being pretty darned sweet for me. > > > > > > It's probably a known issue, but I haven't seen it referenced anywhere: it seems that ZFS filesystems can be shared/exported with Samba/NFS, but they do not accept any kind of writes over the network, and have other issues with smbclient ("Error in diskattr: Call returned zero bytes (EOF)" comes up a lot). > > > > > > Anyone run into this? Any known fixes? > > > > NFS _and_ Samba? > > > > Samba is a userland daemon - if it had problems, other applications > > would have also had problems. > > The issue has been discussed before. It is very real: > http://lists.freebsd.org/pipermail/freebsd-current/2007-June/072991.html > It was also discussed in: http://lists.freebsd.org/pipermail/freebsd-current/2007-July/074495.html where it was found to be caused by lseek behaving differently on ZFS: http://lists.freebsd.org/pipermail/freebsd-current/2007-July/074584.html And one person found a work arround for ZFS by removing the repdir_get* sources from samba: http://lists.freebsd.org/pipermail/freebsd-current/2007-July/074592.html http://lists.freebsd.org/pipermail/freebsd-current/2007-July/074600.html http://lists.freebsd.org/pipermail/freebsd-current/2007-July/074601.html Here is a test program thats shows some problems with the consistency of telldir/seekdir behavior: http://lists.freebsd.org/pipermail/freebsd-current/2007-July/075401.html Read the full thread to get all the information on the problem. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 08:28:43 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D865F16A417 for ; Sat, 25 Aug 2007 08:28:43 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by mx1.freebsd.org (Postfix) with ESMTP id 967DE13C481 for ; Sat, 25 Aug 2007 08:28:43 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp5-g19.free.fr (localhost.localdomain [127.0.0.1]) by smtp5-g19.free.fr (Postfix) with ESMTP id 435FE442A8; Sat, 25 Aug 2007 10:28:42 +0200 (CEST) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp5-g19.free.fr (Postfix) with ESMTP id 5D79B603D; Sat, 25 Aug 2007 10:28:41 +0200 (CEST) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id 236329B497; Sat, 25 Aug 2007 08:28:12 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id 13DB1405B; Sat, 25 Aug 2007 10:28:12 +0200 (CEST) Date: Sat, 25 Aug 2007 10:28:12 +0200 From: Jeremie Le Hen To: "Arno J. Klaassen" , Nathan Butcher Message-ID: <20070825082812.GE50852@obiwan.tataz.chchile.org> References: <46BFE620.8070906@fusiongol.com> <20070813091802.GB3078@stud.ntnu.no> <20070823071056.GA50852@obiwan.tataz.chchile.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.15 (2007-04-06) Cc: freebsd-current@freebsd.org Subject: Re: Promise SATA 300 TX4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 08:28:43 -0000 Nathan, On Thu, Aug 23, 2007 at 10:19:02PM +0200, Arno J. Klaassen wrote: > I re-read the above email a bit more attentively (?) and noticed > that, as Ulf, I use Adaptec SCSI (ahc or ahd) to boot from and > have nothing on standard irq-14/15 IDE subsystem. > > Once again, I experience the problems on -STABLE-amd64, but can > dig up a good-old (not so fast) SCSI-disk to test the (almost) same > hardware setup under -CURRENT. Which arch are you running? amd64 or i386? Also do you use an Adapter SCSI controller in the same time? Thanks. Best regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 11:33:37 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B0A5F16A419; Sat, 25 Aug 2007 11:33:37 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mx1.freebsd.org (Postfix) with ESMTP id 2858613C45B; Sat, 25 Aug 2007 11:33:34 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l7PBXXO3018389; Sat, 25 Aug 2007 21:33:33 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l7PBXXAB018388; Sat, 25 Aug 2007 21:33:33 +1000 (EST) (envelope-from peter) Date: Sat, 25 Aug 2007 21:33:33 +1000 From: Peter Jeremy To: Robert Watson Message-ID: <20070825113333.GA18197@turion.vk2pj.dyndns.org> References: <20070823101737.GA1161@turion.vk2pj.dyndns.org> <20070823162802.T2662@fledge.watson.org> <20070823192322.GQ1161@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV" Content-Disposition: inline In-Reply-To: <20070823192322.GQ1161@turion.vk2pj.dyndns.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@FreeBSD.org Subject: Re: idprio(1) broken in recent -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 11:33:37 -0000 --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-Aug-24 05:23:22 +1000, Peter Jeremy = wrote: >boinc_client is supposed to write a watchdog flag in a shared SysV SHM >block every second. The setiathome process regularly polls the SHM >and if it doesn't see the watchdog for 31 seconds, it will abort. >boinc_client basically sits in a loop and uses select() timeouts. >I wrote a program to monitor the SHM and it shows that SHM is not >being updated. > >It looks like the kernel isn't cleanly handling the situation where >there are multiple idprio processes. I will try some more experimenting >this evening. Sorry for the delay. The select() in boinc_client is not timing out and so isn't returning until the child process dies. When I 'nice' boinc_client, 'ps' shows is waiting in 'select' - which is what I would expect. When I 'idprio' it, 'ps' shows it remaining running, though it is non-responsive. The setiathome process is deliberately allowing context switches (by calling usleep() regularly). It looks like a recent scheduler change means that multiple idprio processes don't round-robin but instead re-schedules the previously running process. I'm running SCHED_4BSD. Pity I don't have dtrace... --=20 Peter Jeremy --HcAYCG3uE/tztfnV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFG0BON/opHv/APuIcRAjQ8AJ9EcdKuleW7o8nXe1FD8rRRiuFYgQCfRcEf fwRQ6TfuYSdCvxR3v7pAkj0= =0GmH -----END PGP SIGNATURE----- --HcAYCG3uE/tztfnV-- From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 12:07:17 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5EC716A41A for ; Sat, 25 Aug 2007 12:07:16 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from mta01.xtra.co.nz (mta01.xtra.co.nz [210.54.141.254]) by mx1.freebsd.org (Postfix) with ESMTP id 4385E13C45A for ; Sat, 25 Aug 2007 12:07:15 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from fep05.xtra.co.nz ([172.23.12.51]) by mta01.xtra.co.nz with ESMTP id <20070825120709.JYIL3105.mta01.xtra.co.nz@fep05.xtra.co.nz>; Sun, 26 Aug 2007 00:07:09 +1200 Received: from serv.int.fubar.geek.nz ([219.89.91.5]) by fep05.xtra.co.nz with ESMTP id <20070825120709.HJIV20018.fep05.xtra.co.nz@serv.int.fubar.geek.nz>; Sun, 26 Aug 2007 00:07:09 +1200 Date: Sun, 26 Aug 2007 00:07:08 +1200 From: Andrew Turner To: Robert Watson Message-ID: <20070826000708.15fbb5bb@hermies.int.fubar.geek.nz> In-Reply-To: <20070824132409.W3900@fledge.watson.org> References: <20070824181627.57bed401@hermies.int.fubar.geek.nz> <20070824132409.W3900@fledge.watson.org> X-Mailer: Claws Mail 2.10.0 (GTK+ 2.10.14; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD on xen hvm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 12:07:17 -0000 On Fri, 24 Aug 2007 13:30:17 +0100 (BST) Robert Watson wrote: > On Fri, 24 Aug 2007, Andrew Turner wrote: > > > 1) PREEMPTION Preemption causes the kernel to panic with a page > > fault. The dmesg is available from [1]. > > Any chance it's possible to get a core for this, or attach GDB > somehow to the VM? I haven't managed to get either remote GDB working and it's too early in the boot for a core. I can get a xen core dump but it would require processing to get it into something gdb could use. > It looks like timing in Xen may be exposing a > race in some or another subsystem with timers, but figuring out which > subsystem it is will be most easily done if we can inspect the > callout information, which is most easily done with GDB since you can > inspect the callout structure more easily. If not, then we can add > some printfs to extract the information, I expect, or extend DDB. We > need to find out what the function pointer in the callout structure > is for. I've created a patch at [1] to add "show callouts" to ddb. It prints all the callouts in callwheel and the name of the function they call. The callouts with preemption are: loadav in6_tmpaddrtimer in6_rtqtimo in_rtqtimo in6_mtutimo uma_timeout nd6_slowtimo nfsrv_timer tcp_isn_tick scrn_timer roundrobin atkbd_timeout sleepq_timeout sleepq_timeout sleepq_timeout sleepq_timeout pffasttimo pfslowtimo kbdmux_kbd_intr_timo if_slowtimo ipport_tick nd6_timer lboltcb tcp_hc_purge Preemption does not always cause the kernel to panic, however when it doesn't it shows the mountroot> prompt and is unable to load the root as no disk drives show up. > > > 3) INVARIANTS Invariants causes a panic from a page fault. See [2] > > for the dmesg and backtrace. > > This appears to be in the start up of Audit as it creates a kernel > thread. Possibly it's creating the thread too early, or possibly > something else is going on. Can you try creating a kernel without > options AUDIT and see if it works better, or if it just panics when > the next thread is created? It just panics in the next thread created. > > It sounds like Xen may start the timer firing sooner than on plain > hardware, or possibly at a faster rate initially, and that's causing > things to happen in a different order, so I expect we'll either bump > into a series of races of this sort based on different ordering of > events, or discover the timer isn't properly being disabled or > managed in Xen :-). I'm suspecting the timer isn't being managed properly. The timer in the loader always stays at 10 and with DIAGNOSTIC I'm getting lines like: Expensive timeout(9) function: 0xc097da70(0xc0bbaa00) -1.982636062 s Andrew [1] http://fubar.geek.nz/files/freebsd/ddb-callout.diff -- Andrew Turner http://fubar.geek.nz/blog/ From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 12:37:56 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E4F616A417 for ; Sat, 25 Aug 2007 12:37:56 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mx1.freebsd.org (Postfix) with ESMTP id A5A2113C469 for ; Sat, 25 Aug 2007 12:37:55 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l7PCbsQc018737; Sat, 25 Aug 2007 22:37:54 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l7PCbsfN018736; Sat, 25 Aug 2007 22:37:54 +1000 (EST) (envelope-from peter) Date: Sat, 25 Aug 2007 22:37:54 +1000 From: Peter Jeremy To: Kostik Belousov Message-ID: <20070825123754.GM17244@turion.vk2pj.dyndns.org> References: <20070817073321.GA6321@turion.vk2pj.dyndns.org> <20070821144303.GD2738@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline In-Reply-To: <20070821144303.GD2738@deviant.kiev.zoral.com.ua> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org, tegge@freebsd.org Subject: Re: insmntque for syncvnode panic [Was: Re: panic unmounting filesystems] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 12:37:56 -0000 --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-Aug-21 17:43:03 +0300, Kostik Belousov wrote: >> The mountpoint shows as in the process of being unmounted and has >> mnt_nvnodelistsize =3D=3D 0 so insmntque() makes sense at the micro leve= l. >> Having a system panic as a result does not make sense. >Sure. I think that syncvnode shall be allocated after the MNTK_UNMOUNT >flag is cleared. > >Could you, please, test the patch below ? >diff --git a/sys/kern/vfs_mount.c b/sys/kern/vfs_mount.c >index 702efc3..09f4d1e 100644 This appears to have resolved the problem - after adding the patch, I've been unable to get umount to panic. Thanks for the fix. --=20 Peter Jeremy --M9NhX3UHpAaciwkO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFG0CKi/opHv/APuIcRArufAJ90mcntnnYsCGZJp/+25kf2PoTjdACfWka4 s3+yM9g6hYlfC7eSkZeleFY= =z5Ih -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO-- From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 14:31:59 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F190216A41B for ; Sat, 25 Aug 2007 14:31:59 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: from hu-out-0506.google.com (hu-out-0506.google.com [72.14.214.237]) by mx1.freebsd.org (Postfix) with ESMTP id 5F16813C474 for ; Sat, 25 Aug 2007 14:31:59 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: by hu-out-0506.google.com with SMTP id 28so783127hub for ; Sat, 25 Aug 2007 07:31:58 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; b=XowAi1W1W2KzLWSHQCW3BGHOHZhJwElCuQKhgcixtMVvhjBIlooKMJrZSS7WMqhq8AmaJ7433z8ho5lIr6KGd0uGfY5t043HvjkKlGuIYSPVs+zHF1hRV3I0WJFKRuDHPkve9lswBQlYugnhF77nTh2hqgoYmrlg6lHqwQHKMq0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; b=DY2tpVlY1k2DmNSy81awPlCVebsDTB/81wmA20dCvUTy1fXNFgmcGHQ4MExKVQCO0xts/F8cWUwmweVEqFZaMMiBm1bvzTAlSKW6zQxjxdi8cMJhapeMEiEW5FhfC/vI7YDM0lBUrC0bdj09Q9lYJGVfkKazCUZW1yB9JZfIC2A= Received: by 10.78.168.1 with SMTP id q1mr2570007hue.1188052317505; Sat, 25 Aug 2007 07:31:57 -0700 (PDT) Received: from 77-109-36-77.dynamic.peoplenet.ua ( [77.109.36.77]) by mx.google.com with ESMTPS id 19sm1434181hub.2007.08.25.07.31.50 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 25 Aug 2007 07:31:55 -0700 (PDT) From: Nikolay Pavlov To: Jan Harkes Date: Sat, 25 Aug 2007 17:32:13 +0300 User-Agent: KMail/1.9.7 References: <200708202340.29678.qpadla@gmail.com> <20070824151927.GA11642@cs.cmu.edu> In-Reply-To: <20070824151927.GA11642@cs.cmu.edu> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1369032.4krqKLkfdp"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200708251732.17394.qpadla@gmail.com> Cc: freebsd-current@freebsd.org, rwatson@freebsd.org Subject: Re: And probably the final crash for today's current :) (panic: filesystem goof: vop_panic[vop_print]) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: qpadla@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 14:32:00 -0000 --nextPart1369032.4krqKLkfdp Content-Type: multipart/mixed; boundary="Boundary-01=_t1D0GhRWpPtu/aI" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_t1D0GhRWpPtu/aI Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 24 August 2007 18:19:27 Jan Harkes wrote: > The following patch adds locking around VOP_ operations. I ran some > tests and it seems like I got them all. For some reason I could only get > the warnings to go away when using exclusive locks, but since the > overhead in our case really is in userspace and we still hold the giant > lock pretty much everywhere there shouldn't be a measurable difference. With your patch everything works fine, but only if i'am using UFS as a=20 cachedir, rvm and checkpointdir backend. If i'am using ZFS as a backend a panic occur with "ls -l /coda" command. =20 See in attachment. =2D-=20 * Best regards, Nikolay Pavlov * --Boundary-01=_t1D0GhRWpPtu/aI Content-Type: text/plain; charset="iso-8859-1"; name="coda_panic.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="coda_panic.txt" panic: Assertion !mtx_owned(&w_mtx) failed at /usr/src/sys/kern/subr_witness.c:958 cpuid = 0 KDB: enter: panic exclusive sleep mutex Giant r = 0 (0xc0bb1250) locked @ /usr/src/sys/kern/vfs_syscalls.c:3727 shared spin mutex (exclusive sleep mutex Giant r = 0 (0xc0bb1250) locked @ /usr/src/sys/kern/vfs_syscalls.c:3727 shared spin mutex (shared spin mutex (panic: from debugger cpuid = 0 Uptime: 53s Physical memory: 1003 MB Dumping 95 MB: 80 64 48 32 16 #0 doadump () at pcpu.h:195 195 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc074ec6e in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #2 0xc074ef2b in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:563 #3 0xc048c887 in db_panic (addr=Could not find the frame base for "db_panic". ) at /usr/src/sys/ddb/db_command.c:433 #4 0xc048d275 in db_command_loop () at /usr/src/sys/ddb/db_command.c:401 #5 0xc048e9e5 in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_main.c:222 #6 0xc0775c76 in kdb_trap (type=3, code=0, tf=0xe69ea140) at /usr/src/sys/kern/subr_kdb.c:502 #7 0xc0a02e6b in trap (frame=0xe69ea140) at /usr/src/sys/i386/i386/trap.c:621 #8 0xc09e889b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #9 0xc0775df2 in kdb_enter (msg=0xc0a9bd83 "panic") at cpufunc.h:60 #10 0xc074ef14 in panic (fmt=0xc0a971f1 "Assertion %s failed at %s:%d") at /usr/src/sys/kern/kern_shutdown.c:547 #11 0xc0786349 in witness_checkorder (lock=0xc0c22a60, flags=Variable "flags" is not available. ) at /usr/src/sys/kern/subr_witness.c:958 #12 0xc0743a2f in _mtx_lock_spin_flags (m=0xc0c22a60, opts=0, file=0xc0a8920f "/usr/src/sys/dev/syscons/syscons.c", line=1801) at /usr/src/sys/kern/kern_mutex.c:223 #13 0xc0677b1d in scrn_update (scp=0xc0bad260, show_cursor=1) at /usr/src/sys/dev/syscons/syscons.c:1801 #14 0xc0679826 in sccnupdate (scp=0xc0bad260) at /usr/src/sys/dev/syscons/syscons.c:1683 #15 0xc067b59d in sc_cnputc (cd=0xc0b0a320, c=107) at /usr/src/sys/dev/syscons/syscons.c:1571 #16 0xc0798b6f in cnputc (c=107) at /usr/src/sys/kern/tty_cons.c:632 #17 0xc0779367 in putcons (c=Variable "c" is not available. ) at /usr/src/sys/kern/subr_prf.c:372 #18 0xc0779431 in putchar (c=107, arg=0xe69ea40c) at /usr/src/sys/kern/subr_prf.c:413 #19 0xc0777e05 in kvprintf (fmt=0xc0aca641 "ernel trap %d with interrupts disabled\n", func=0xc07793d0 , arg=0xe69ea40c, radix=10, ap=0xe69ea438 "\f") at /usr/src/sys/kern/subr_prf.c:599 #20 0xc0778f6e in printf (fmt=0xc0aca640 "kernel trap %d with interrupts disabled\n") at /usr/src/sys/kern/subr_prf.c:314 #21 0xc0a029ce in trap (frame=0xe69ea4cc) at /usr/src/sys/i386/i386/trap.c:237 #22 0xc09e889b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #23 0xc07841b3 in isitmychild (parent=0xc607c4ec, child=0xc0bc14c8) at /usr/src/sys/kern/subr_witness.c:1614 #24 0xc078637e in witness_checkorder (lock=0xc0c22a60, flags=Variable "flags" is not available. ) at /usr/src/sys/kern/subr_witness.c:965 #25 0xc0743a2f in _mtx_lock_spin_flags (m=0xc0c22a60, opts=0, file=0xc0a8920f "/usr/src/sys/dev/syscons/syscons.c", line=1801) at /usr/src/sys/kern/kern_mutex.c:223 #26 0xc0677b1d in scrn_update (scp=0xc0bad260, show_cursor=1) at /usr/src/sys/dev/syscons/syscons.c:1801 #27 0xc0679826 in sccnupdate (scp=0xc0bad260) at /usr/src/sys/dev/syscons/syscons.c:1683 #28 0xc067b59d in sc_cnputc (cd=0xc0b0a320, c=75) at /usr/src/sys/dev/syscons/syscons.c:1571 #29 0xc0798b6f in cnputc (c=75) at /usr/src/sys/kern/tty_cons.c:632 #30 0xc0779367 in putcons (c=Variable "c" is not available. ) at /usr/src/sys/kern/subr_prf.c:372 #31 0xc0779431 in putchar (c=75, arg=0xe69ea768) at /usr/src/sys/kern/subr_prf.c:413 #32 0xc0777e05 in kvprintf (fmt=0xc0aca66a "ernel page fault", func=0xc07793d0 , arg=0xe69ea768, radix=10, ap=0xe69ea7cc "") at /usr/src/sys/kern/subr_prf.c:599 #33 0xc0778e8b in vprintf (fmt=0xc0aca669 "Kernel page fault", ap=0xe69ea7cc "") at /usr/src/sys/kern/subr_prf.c:352 #34 0xc0785861 in witness_warn (flags=5, lock=0x0, fmt=0xc0aca669 "Kernel page fault") at /usr/src/sys/kern/subr_witness.c:1385 #35 0xc0a02a22 in trap (frame=0xe69ea858) at /usr/src/sys/i386/i386/trap.c:274 #36 0xc09e889b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #37 0xc43f6ab0 in ?? () --Boundary-01=_t1D0GhRWpPtu/aI-- --nextPart1369032.4krqKLkfdp Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBG0D1x/2R6KvEYGaIRApE0AJ0WntWkHZ6CFUqn+XJ9Eg3ugWpJMwCg0mm8 LB0L9wR1hf9o0w300qvcd3w= =QDcx -----END PGP SIGNATURE----- --nextPart1369032.4krqKLkfdp-- From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 17:41:13 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C71F916A418 for ; Sat, 25 Aug 2007 17:41:13 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.freebsd.org (Postfix) with ESMTP id 550CE13C469 for ; Sat, 25 Aug 2007 17:41:13 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so919632nfb for ; Sat, 25 Aug 2007 10:41:13 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=PRusjW807i0R0fu/uP2hz1iJYiiWBOOnhv38HYGyd1RRt056tl/nfp1ZJNb7j5rfoFoIBjWTPeYdWV/H4o68sLACk3pYbDV3F36AfeYcfvFqfOVFZSYfc2icAFc2/vaIT/gpbLtOrTvDr4+MbI1U4RqmomadlffqVtxYQXakZnE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NKKz3gTWGV7BiBAq9nV+1aHWnY43Nm//m2g8dB6rg0jZIMXiRZqZMHY4LZPPMD3ZCWBTYBW8Ra2hjYNwhIKWvmfHM7xB1f1QHTomi0EHXAsZ8Bj96gYYOQeJrATdYwAPG9M1+fFxymT6bKo7Yt3MSBWiOlgxfVnVmnyVkVKpLbI= Received: by 10.78.134.2 with SMTP id h2mr2612490hud.1188063669631; Sat, 25 Aug 2007 10:41:09 -0700 (PDT) Received: by 10.78.162.18 with HTTP; Sat, 25 Aug 2007 10:41:09 -0700 (PDT) Message-ID: Date: Sat, 25 Aug 2007 10:41:09 -0700 From: "Kip Macy" To: "Andrew Turner" , "Robert Watson" , freebsd-current@freebsd.org In-Reply-To: <20070826000708.15fbb5bb@hermies.int.fubar.geek.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070824181627.57bed401@hermies.int.fubar.geek.nz> <20070824132409.W3900@fledge.watson.org> <20070826000708.15fbb5bb@hermies.int.fubar.geek.nz> Cc: Subject: Re: FreeBSD on xen hvm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 17:41:13 -0000 Have you tried gdbserver? -Kip On 8/25/07, Andrew Turner wrote: > On Fri, 24 Aug 2007 13:30:17 +0100 (BST) > Robert Watson wrote: > > On Fri, 24 Aug 2007, Andrew Turner wrote: > > > > > 1) PREEMPTION Preemption causes the kernel to panic with a page > > > fault. The dmesg is available from [1]. > > > > Any chance it's possible to get a core for this, or attach GDB > > somehow to the VM? > I haven't managed to get either remote GDB working and it's too early > in the boot for a core. I can get a xen core dump but it would require > processing to get it into something gdb could use. > > It looks like timing in Xen may be exposing a > > race in some or another subsystem with timers, but figuring out which > > subsystem it is will be most easily done if we can inspect the > > callout information, which is most easily done with GDB since you can > > inspect the callout structure more easily. If not, then we can add > > some printfs to extract the information, I expect, or extend DDB. We > > need to find out what the function pointer in the callout structure > > is for. > I've created a patch at [1] to add "show callouts" to ddb. It prints > all the callouts in callwheel and the name of the function they call. > The callouts with preemption are: > loadav > in6_tmpaddrtimer > in6_rtqtimo > in_rtqtimo > in6_mtutimo > uma_timeout > nd6_slowtimo > nfsrv_timer > tcp_isn_tick > scrn_timer > roundrobin > atkbd_timeout > sleepq_timeout > sleepq_timeout > sleepq_timeout > sleepq_timeout > pffasttimo > pfslowtimo > kbdmux_kbd_intr_timo > if_slowtimo > ipport_tick > nd6_timer > lboltcb > tcp_hc_purge > > Preemption does not always cause the kernel to panic, however when it > doesn't it shows the mountroot> prompt and is unable to load the root > as no disk drives show up. > > > > > 3) INVARIANTS Invariants causes a panic from a page fault. See [2] > > > for the dmesg and backtrace. > > > > This appears to be in the start up of Audit as it creates a kernel > > thread. Possibly it's creating the thread too early, or possibly > > something else is going on. Can you try creating a kernel without > > options AUDIT and see if it works better, or if it just panics when > > the next thread is created? > It just panics in the next thread created. > > > > It sounds like Xen may start the timer firing sooner than on plain > > hardware, or possibly at a faster rate initially, and that's causing > > things to happen in a different order, so I expect we'll either bump > > into a series of races of this sort based on different ordering of > > events, or discover the timer isn't properly being disabled or > > managed in Xen :-). > I'm suspecting the timer isn't being managed properly. The timer in the > loader always stays at 10 and with DIAGNOSTIC I'm getting lines like: > Expensive timeout(9) function: 0xc097da70(0xc0bbaa00) -1.982636062 s > > Andrew > > [1] http://fubar.geek.nz/files/freebsd/ddb-callout.diff > > -- > Andrew Turner > http://fubar.geek.nz/blog/ > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 17:43:03 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9411616A419 for ; Sat, 25 Aug 2007 17:43:03 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.freebsd.org (Postfix) with ESMTP id 132BE13C49D for ; Sat, 25 Aug 2007 17:43:02 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so919847nfb for ; Sat, 25 Aug 2007 10:43:02 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=YPJRigqEv6e3Od8VZPkQ8vyK8Smg4X/ch+a2rlLDRoFLY+KZ87uImj1H/wxkGaQVNDoET1HFqM/dNlq5yPOyOGaHFNOIMyTbi8DKWxPDmIPvVq2JLEBAIgt/3na/97Nfj3Aq+zBvQZZS1ltIU4Opjox2gAwTtFBq4zE4VmBhqy8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=fOSYCGJXZla1fc7VR1nD46Cl9ScK7wTJfLaLudwhQoFl+7jec81zlspYdcXqXeSbxF5Q70wNYk01HT2QqLYpu8OGSMcNByU7rQNdBQv8j+HA2rrInTbkLwNSeBDHiXEbc0UpIZpeIiTAdjTEHZ7Imw1GXCGUC02mhxf4IRhaskU= Received: by 10.78.195.9 with SMTP id s9mr2620027huf.1188063780906; Sat, 25 Aug 2007 10:43:00 -0700 (PDT) Received: by 10.78.162.18 with HTTP; Sat, 25 Aug 2007 10:43:00 -0700 (PDT) Message-ID: Date: Sat, 25 Aug 2007 10:43:00 -0700 From: "Kip Macy" To: "Andrew Turner" , "Robert Watson" , freebsd-current@freebsd.org In-Reply-To: <20070826000708.15fbb5bb@hermies.int.fubar.geek.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070824181627.57bed401@hermies.int.fubar.geek.nz> <20070824132409.W3900@fledge.watson.org> <20070826000708.15fbb5bb@hermies.int.fubar.geek.nz> Cc: Subject: Re: FreeBSD on xen hvm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 17:43:03 -0000 Have you tried gdbserver? -Kip On 8/25/07, Andrew Turner wrote: > On Fri, 24 Aug 2007 13:30:17 +0100 (BST) > Robert Watson wrote: > > On Fri, 24 Aug 2007, Andrew Turner wrote: > > > > > 1) PREEMPTION Preemption causes the kernel to panic with a page > > > fault. The dmesg is available from [1]. > > > > Any chance it's possible to get a core for this, or attach GDB > > somehow to the VM? > I haven't managed to get either remote GDB working and it's too early > in the boot for a core. I can get a xen core dump but it would require > processing to get it into something gdb could use. > > It looks like timing in Xen may be exposing a > > race in some or another subsystem with timers, but figuring out which > > subsystem it is will be most easily done if we can inspect the > > callout information, which is most easily done with GDB since you can > > inspect the callout structure more easily. If not, then we can add > > some printfs to extract the information, I expect, or extend DDB. We > > need to find out what the function pointer in the callout structure > > is for. > I've created a patch at [1] to add "show callouts" to ddb. It prints > all the callouts in callwheel and the name of the function they call. > The callouts with preemption are: > loadav > in6_tmpaddrtimer > in6_rtqtimo > in_rtqtimo > in6_mtutimo > uma_timeout > nd6_slowtimo > nfsrv_timer > tcp_isn_tick > scrn_timer > roundrobin > atkbd_timeout > sleepq_timeout > sleepq_timeout > sleepq_timeout > sleepq_timeout > pffasttimo > pfslowtimo > kbdmux_kbd_intr_timo > if_slowtimo > ipport_tick > nd6_timer > lboltcb > tcp_hc_purge > > Preemption does not always cause the kernel to panic, however when it > doesn't it shows the mountroot> prompt and is unable to load the root > as no disk drives show up. > > > > > 3) INVARIANTS Invariants causes a panic from a page fault. See [2] > > > for the dmesg and backtrace. > > > > This appears to be in the start up of Audit as it creates a kernel > > thread. Possibly it's creating the thread too early, or possibly > > something else is going on. Can you try creating a kernel without > > options AUDIT and see if it works better, or if it just panics when > > the next thread is created? > It just panics in the next thread created. > > > > It sounds like Xen may start the timer firing sooner than on plain > > hardware, or possibly at a faster rate initially, and that's causing > > things to happen in a different order, so I expect we'll either bump > > into a series of races of this sort based on different ordering of > > events, or discover the timer isn't properly being disabled or > > managed in Xen :-). > I'm suspecting the timer isn't being managed properly. The timer in the > loader always stays at 10 and with DIAGNOSTIC I'm getting lines like: > Expensive timeout(9) function: 0xc097da70(0xc0bbaa00) -1.982636062 s > > Andrew > > [1] http://fubar.geek.nz/files/freebsd/ddb-callout.diff > > -- > Andrew Turner > http://fubar.geek.nz/blog/ > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 19:52:37 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2595416A41B for ; Sat, 25 Aug 2007 19:52:37 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by mx1.freebsd.org (Postfix) with ESMTP id 993C613C48A for ; Sat, 25 Aug 2007 19:52:36 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so933899nfb for ; Sat, 25 Aug 2007 12:52:35 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=t/5yo0xJ05u+PoWw9i19Jdl7V49TMkRZ/xkNaHmGejXEjgtCGYzE1L6raJyESjZoMEDs+H+mgdb0RLNLI0oqRJGSGpyQUmpjcKeCCA37R3LsFUZPLhqVvnff0pT7HcY3KoRzvPu+HhhqtjbGcaC2nXa9HOuYptIo7rnCysUtN54= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=uE8m+P51r2U3djt16Ls0+/2NfiOCgo3J32Cu8o6N5EPH9UbZwWyV4SaQFICctPyKfih+ZzDmKHWZuDvukzIQE4lGZ8sDCA5KZUiFIO2uFE3oJzFyQtItNIgtlvA6Lsxy5nLwxUWlFTJ/SWqH70uaRwmw88fe9T887F9OBqETEsQ= Received: by 10.78.193.5 with SMTP id q5mr2691973huf.1188071554477; Sat, 25 Aug 2007 12:52:34 -0700 (PDT) Received: by 10.78.162.18 with HTTP; Sat, 25 Aug 2007 12:52:34 -0700 (PDT) Message-ID: Date: Sat, 25 Aug 2007 12:52:34 -0700 From: "Kip Macy" To: "Andrew Turner" , "Robert Watson" , freebsd-current@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070824181627.57bed401@hermies.int.fubar.geek.nz> <20070824132409.W3900@fledge.watson.org> <20070826000708.15fbb5bb@hermies.int.fubar.geek.nz> Cc: Subject: Re: FreeBSD on xen hvm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 19:52:37 -0000 On 8/25/07, Kip Macy wrote: > Have you tried gdbserver? Sorry gmail client freaked out. I know that the gdbserver worked with hvm guests at least at one point. Please let me know if that is not the case. -Kip > > -Kip > > > On 8/25/07, Andrew Turner wrote: > > On Fri, 24 Aug 2007 13:30:17 +0100 (BST) > > Robert Watson wrote: > > > On Fri, 24 Aug 2007, Andrew Turner wrote: > > > > > > > 1) PREEMPTION Preemption causes the kernel to panic with a page > > > > fault. The dmesg is available from [1]. > > > > > > Any chance it's possible to get a core for this, or attach GDB > > > somehow to the VM? > > I haven't managed to get either remote GDB working and it's too early > > in the boot for a core. I can get a xen core dump but it would require > > processing to get it into something gdb could use. > > > It looks like timing in Xen may be exposing a > > > race in some or another subsystem with timers, but figuring out which > > > subsystem it is will be most easily done if we can inspect the > > > callout information, which is most easily done with GDB since you can > > > inspect the callout structure more easily. If not, then we can add > > > some printfs to extract the information, I expect, or extend DDB. We > > > need to find out what the function pointer in the callout structure > > > is for. > > I've created a patch at [1] to add "show callouts" to ddb. It prints > > all the callouts in callwheel and the name of the function they call. > > The callouts with preemption are: > > loadav > > in6_tmpaddrtimer > > in6_rtqtimo > > in_rtqtimo > > in6_mtutimo > > uma_timeout > > nd6_slowtimo > > nfsrv_timer > > tcp_isn_tick > > scrn_timer > > roundrobin > > atkbd_timeout > > sleepq_timeout > > sleepq_timeout > > sleepq_timeout > > sleepq_timeout > > pffasttimo > > pfslowtimo > > kbdmux_kbd_intr_timo > > if_slowtimo > > ipport_tick > > nd6_timer > > lboltcb > > tcp_hc_purge > > > > Preemption does not always cause the kernel to panic, however when it > > doesn't it shows the mountroot> prompt and is unable to load the root > > as no disk drives show up. > > > > > > > 3) INVARIANTS Invariants causes a panic from a page fault. See [2] > > > > for the dmesg and backtrace. > > > > > > This appears to be in the start up of Audit as it creates a kernel > > > thread. Possibly it's creating the thread too early, or possibly > > > something else is going on. Can you try creating a kernel without > > > options AUDIT and see if it works better, or if it just panics when > > > the next thread is created? > > It just panics in the next thread created. > > > > > > It sounds like Xen may start the timer firing sooner than on plain > > > hardware, or possibly at a faster rate initially, and that's causing > > > things to happen in a different order, so I expect we'll either bump > > > into a series of races of this sort based on different ordering of > > > events, or discover the timer isn't properly being disabled or > > > managed in Xen :-). > > I'm suspecting the timer isn't being managed properly. The timer in the > > loader always stays at 10 and with DIAGNOSTIC I'm getting lines like: > > Expensive timeout(9) function: 0xc097da70(0xc0bbaa00) -1.982636062 s > > > > Andrew > > > > [1] http://fubar.geek.nz/files/freebsd/ddb-callout.diff > > > > -- > > Andrew Turner > > http://fubar.geek.nz/blog/ > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 20:20:34 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1850416A420 for ; Sat, 25 Aug 2007 20:20:34 +0000 (UTC) (envelope-from h.schmalzbauer@omnisec.de) Received: from host.omnisec.de (host.omnisec.de [62.245.232.135]) by mx1.freebsd.org (Postfix) with ESMTP id 8D5DF13C442 for ; Sat, 25 Aug 2007 20:20:33 +0000 (UTC) (envelope-from h.schmalzbauer@omnisec.de) Received: from akima.flintsbach.schmalzbauer.de (akima.flintsbach.schmalzbauer.de [172.21.1.35]) (authenticated bits=0) by host.omnisec.de (8.13.8/8.13.8) with ESMTP id l7PKKUsh082687 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 25 Aug 2007 22:20:31 +0200 (CEST) (envelope-from h.schmalzbauer@omnisec.de) From: Harald Schmalzbauer Organization: OmniSEC To: freebsd-current@freebsd.org Date: Sat, 25 Aug 2007 22:20:21 +0200 User-Agent: KMail/1.9.7 References: <200708231028.07743.h.schmalzbauer@omnisec.de> <86r6lu1rms.fsf@ds4.des.no> In-Reply-To: <86r6lu1rms.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200708252220.27373.h.schmalzbauer@omnisec.de> Cc: Dag-Erling =?utf-8?q?Sm=C3=B8rgrav?= Subject: Re: ichwd and teethless watchdogd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 20:20:34 -0000 Am Donnerstag, 23. August 2007 12:18:03 schrieb Dag-Erling Sm=C3=B8rgrav: > Harald Schmalzbauer writes: > > I had tested the ich 6/7/8 ichwd patch some months ago on a ich7 FSC > > machine and it worked fine. On my ich8 desktop probing found ichwd0 > > but it didn't work. My new ich9 machine doesn't show ichwd0. > > It should work on ICH9 if you add the correct PCI ID. > > > But now (with -current after imported ichwd patch) I also have > > problems on an Intel Server board with ich7. SIGKILL to watchdogd > > should reboot the machine, right? > > Yes. > > > It doesn't, but probing reports two times ichwd0. > > A verbose dmesg would be nice. Here are the relevant lines: ichwd0: on isa0 isab0: found ICH7 or equivalent chipset: Intel ICH7 watchdog timer ichwd0: Intel ICH7 watchdog timer (ICH7 or equivalent) ichwd0: timer disabled After watchdogd has started I get this message every second: ichwd0: timer reloaded I guess the ichwd is hardware disabled by the bios. Can this be corrected somehow? The BIOS of that Intel server motherboard is somewhat horrible. No AHCI=20 support, no console redirectiojn for the RAID setup, only one mode in VGA=20 BIOS and now ichwd disabled. I'll stay with FujitsuSiemens. =2DHarry From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 20:33:38 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C486C16A4C8 for ; Sat, 25 Aug 2007 20:33:38 +0000 (UTC) (envelope-from h.schmalzbauer@omnisec.de) Received: from host.omnisec.de (host.omnisec.de [62.245.232.135]) by mx1.freebsd.org (Postfix) with ESMTP id 4A07313C48A for ; Sat, 25 Aug 2007 20:33:37 +0000 (UTC) (envelope-from h.schmalzbauer@omnisec.de) Received: from akima.flintsbach.schmalzbauer.de (akima.flintsbach.schmalzbauer.de [172.21.1.35]) (authenticated bits=0) by host.omnisec.de (8.13.8/8.13.8) with ESMTP id l7PKXain082864 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 25 Aug 2007 22:33:36 +0200 (CEST) (envelope-from h.schmalzbauer@omnisec.de) From: Harald Schmalzbauer Organization: OmniSEC To: freebsd-current@freebsd.org Date: Sat, 25 Aug 2007 22:33:28 +0200 User-Agent: KMail/1.9.7 References: <200708231028.07743.h.schmalzbauer@omnisec.de> <86r6lu1rms.fsf@ds4.des.no> <200708252220.27373.h.schmalzbauer@omnisec.de> In-Reply-To: <200708252220.27373.h.schmalzbauer@omnisec.de> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200708252233.30392.h.schmalzbauer@omnisec.de> Cc: Dag-Erling =?utf-8?q?Sm=C3=B8rgrav?= Subject: Re: ichwd and teethless watchdogd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 20:33:38 -0000 Am Samstag, 25. August 2007 22:20:21 schrieb Harald Schmalzbauer: [*SNIP*] > I guess the ichwd is hardware disabled by the bios. > Can this be corrected somehow? > The BIOS of that Intel server motherboard is somewhat horrible. No AHCI > support, no console redirectiojn for the RAID setup, only one mode in VGA > BIOS and now ichwd disabled. I'll stay with FujitsuSiemens. Sorry, I have to corret that. I thought I was sure that I checked the bios setting and wd timer was set to on, but maybe after the laste BIOS update it was reset to off. Problem solved, the box reboots whe sigkilling watchdogd. Thanks and sorry for the noise, -Harry From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 20:47:50 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B29316A421 for ; Sat, 25 Aug 2007 20:47:50 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id E100713C442 for ; Sat, 25 Aug 2007 20:47:49 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 49B7A2084; Sat, 25 Aug 2007 22:47:43 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 3BC012083; Sat, 25 Aug 2007 22:47:43 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id 2680884479; Sat, 25 Aug 2007 22:47:43 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Harald Schmalzbauer References: <200708231028.07743.h.schmalzbauer@omnisec.de> <86r6lu1rms.fsf@ds4.des.no> <200708252220.27373.h.schmalzbauer@omnisec.de> Date: Sat, 25 Aug 2007 22:47:43 +0200 In-Reply-To: <200708252220.27373.h.schmalzbauer@omnisec.de> (Harald Schmalzbauer's message of "Sat\, 25 Aug 2007 22\:20\:21 +0200") Message-ID: <864pinmjdc.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: ichwd and teethless watchdogd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 20:47:50 -0000 Harald Schmalzbauer writes: > Here are the relevant lines: > > ichwd0: on isa0 > isab0: found ICH7 or equivalent chipset: Intel ICH7 watchdog timer > ichwd0: Intel ICH7 watchdog timer (ICH7 or equivalent) > ichwd0: timer disabled > > After watchdogd has started I get this message every second: > ichwd0: timer reloaded Looks fine so far. If you kill or suspend watchdogd, these messages should stop, and the system should reboot after the timer expires twice (the first time it expires, the chipset triggers an SMI; the second time, it resets the CPU). However, the timeout is probably not what you set it to; due to the design of the watchdog framework, the timeout you specify is converted to nanoseconds, the rounded up to the nearest power of two. The ICH WDT has a resolution of approximately 0.6 seconds, and the driver rounds down to that, so the actual timeout value you end up with is one of 0.6s, 1.8s, 4.2s, 8.4s, 16.8s, 34.2s, 68.4s, 137.4s, 274.8s... The following C99 code will enumerate the possible values: for (int i =3D 1; i < 64; ++i) { uint64_t timeout =3D 1; timeout <<=3D i; timeout /=3D 600000000LLU; timeout *=3D 600; if (timeout > 0) printf("%.1fs\n", (double)(timeout / 1000.0)); } > I guess the ichwd is hardware disabled by the bios. No, it isn't; the driver would tell you if that was the case. Something else is wrong. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 22:05:20 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4FA416A41B for ; Sat, 25 Aug 2007 22:05:20 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id 5CA0F13C461 for ; Sat, 25 Aug 2007 22:05:20 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from ap-h.matik.com.br (ap-h.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id l7PM5LTt015104; Sat, 25 Aug 2007 19:05:21 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-current@freebsd.org Date: Sat, 25 Aug 2007 19:05:18 -0300 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200708251905.18834.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.90.3, clamav-milter version 0.90.3 on msrv.matik.com.br X-Virus-Status: Clean Subject: if_wi channel set problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 22:05:21 -0000 Hi I sent this some time ago but nothing changed. Whatever channel I try to set on a wi card it stays at channel 3, I use hos= tap Even hardcoding the default channel in if_wi.c does not help, it is not=20 possible setting the channel to anything else as channel 3 which it is=20 already when the driver comes up somebody has a help for me? =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 22:54:46 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1EAA16A417 for ; Sat, 25 Aug 2007 22:54:46 +0000 (UTC) (envelope-from h.schmalzbauer@omnisec.de) Received: from host.omnisec.de (host.omnisec.de [62.245.232.135]) by mx1.freebsd.org (Postfix) with ESMTP id 1F80013C46B for ; Sat, 25 Aug 2007 22:54:45 +0000 (UTC) (envelope-from h.schmalzbauer@omnisec.de) Received: from akima.flintsbach.schmalzbauer.de (akima.flintsbach.schmalzbauer.de [172.21.1.35]) (authenticated bits=0) by host.omnisec.de (8.13.8/8.13.8) with ESMTP id l7PMsix8085204 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Aug 2007 00:54:44 +0200 (CEST) (envelope-from h.schmalzbauer@omnisec.de) From: Harald Schmalzbauer Organization: OmniSEC To: freebsd-current@freebsd.org Date: Sun, 26 Aug 2007 00:54:41 +0200 User-Agent: KMail/1.9.7 References: <200708210339.l7L3dUX0038042@repoman.freebsd.org> <46CB50FE.7000306@FreeBSD.org> In-Reply-To: <46CB50FE.7000306@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200708260054.42892.h.schmalzbauer@omnisec.de> Cc: "Constantine A. Murenin" Subject: Re: GSoC2007: cnst-sensors.2007-08-20.patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 22:54:46 -0000 Am Dienstag, 21. August 2007 22:54:22 schrieb Constantine A. Murenin: > http://p4web.freebsd.org/depot/projects/soc2007/cnst-sensors/cnst-sensors.2 >007-08-20.patch Thanks a lot for your hard work. I'd love to test it but the 08-20 patch doesn't cleanly apply to todays -current in coretemp. Can you supply a diff to that patch or reroll a new patch? Thank you, -Harry From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 23:30:08 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6ECCB16A417 for ; Sat, 25 Aug 2007 23:30:08 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 2F92613C45A for ; Sat, 25 Aug 2007 23:30:08 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 89DFF2085; Sun, 26 Aug 2007 01:30:02 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 55D652084; Sun, 26 Aug 2007 01:30:02 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id 26E2B84468; Sun, 26 Aug 2007 01:30:02 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Harald Schmalzbauer References: <200708231028.07743.h.schmalzbauer@omnisec.de> <86r6lu1rms.fsf@ds4.des.no> <200708252220.27373.h.schmalzbauer@omnisec.de> <200708252233.30392.h.schmalzbauer@omnisec.de> Date: Sun, 26 Aug 2007 01:30:01 +0200 In-Reply-To: <200708252233.30392.h.schmalzbauer@omnisec.de> (Harald Schmalzbauer's message of "Sat\, 25 Aug 2007 22\:33\:28 +0200") Message-ID: <86zm0fkxae.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: ichwd and teethless watchdogd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 23:30:08 -0000 Harald Schmalzbauer writes: > I thought I was sure that I checked the bios setting and wd timer was > set to on, but maybe after the laste BIOS update it was reset to off. > Problem solved, the box reboots whe sigkilling watchdogd. Interesting, if your BIOS can disable the WDT without the driver noticing, it must mean that it implements an SMI handler that resets (or perhaps stops) the WDT when it expires. AFAIK there is no (documented) way to either detect or prevent this. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 23:45:00 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76DF716A41B; Sat, 25 Aug 2007 23:45:00 +0000 (UTC) (envelope-from cnst@FreeBSD.org) Received: from mojo.ru (mojo.ru [84.252.152.63]) by mx1.freebsd.org (Postfix) with ESMTP id D74E213C49D; Sat, 25 Aug 2007 23:44:59 +0000 (UTC) (envelope-from cnst@FreeBSD.org) Received: from [192.168.0.16] (nc-76-4-28-21.dhcp.embarqhsd.net [76.4.28.21]) (authenticated bits=0) by mojo.ru (8.12.11.20060308/8.12.10) with ESMTP id l7PNj1MF024670 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Aug 2007 03:45:05 +0400 Message-ID: <46D0BEEF.1020601@FreeBSD.org> Date: Sat, 25 Aug 2007 19:44:47 -0400 From: "Constantine A. Murenin" Organization: Google Summer of Code 2007 Student @ The FreeBSD Project User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-gb, en-gb-oed, en, en-us, ru, ru-ru, ru-su MIME-Version: 1.0 To: Harald Schmalzbauer , freebsd-current@FreeBSD.org References: <200708210339.l7L3dUX0038042@repoman.freebsd.org> <46CB50FE.7000306@FreeBSD.org> <200708260054.42892.h.schmalzbauer@omnisec.de> In-Reply-To: <200708260054.42892.h.schmalzbauer@omnisec.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Shteryana Shopova , "Constantine A. Murenin" Subject: Re: GSoC2007: cnst-sensors.2007-08-20.patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 23:45:00 -0000 On 25/08/2007 18:54, Harald Schmalzbauer wrote: > Am Dienstag, 21. August 2007 22:54:22 schrieb Constantine A. Murenin: > >>http://p4web.freebsd.org/depot/projects/soc2007/cnst-sensors/cnst-sensors.2 >>007-08-20.patch > > > Thanks a lot for your hard work. > I'd love to test it but the 08-20 patch doesn't cleanly apply to > todays -current in coretemp. > Can you supply a diff to that patch or reroll a new patch? Thanks for testing! The coretemp.c updated to contain the 2007-08-23 change from the CVS (coretemp.c#rev1.2) can be downloaded directly from my perforce branch: http://p4web.freebsd.org/@sr=125633@//depot/projects/soc2007/cnst-sensors/sys.dev.coretemp/coretemp.c P.S. BTW, please do report back how the tests went. Don't forget to include the information on which exact chip you tested (for example, you might have tried this code on Winbond W83627DHG and Core 2 Duo E4300). Best regards, Constantine. From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 23:46:33 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A79E416A474 for ; Sat, 25 Aug 2007 23:46:33 +0000 (UTC) (envelope-from h.schmalzbauer@omnisec.de) Received: from host.omnisec.de (host.omnisec.de [62.245.232.135]) by mx1.freebsd.org (Postfix) with ESMTP id 32E3013C4DA for ; Sat, 25 Aug 2007 23:46:32 +0000 (UTC) (envelope-from h.schmalzbauer@omnisec.de) Received: from akima.flintsbach.schmalzbauer.de (akima.flintsbach.schmalzbauer.de [172.21.1.35]) (authenticated bits=0) by host.omnisec.de (8.13.8/8.13.8) with ESMTP id l7PNkVQr086076 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Aug 2007 01:46:31 +0200 (CEST) (envelope-from h.schmalzbauer@omnisec.de) From: Harald Schmalzbauer Organization: OmniSEC To: freebsd-current@freebsd.org Date: Sun, 26 Aug 2007 01:46:28 +0200 User-Agent: KMail/1.9.7 References: <200708231028.07743.h.schmalzbauer@omnisec.de> <200708252233.30392.h.schmalzbauer@omnisec.de> <86zm0fkxae.fsf@ds4.des.no> In-Reply-To: <86zm0fkxae.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200708260146.30283.h.schmalzbauer@omnisec.de> Cc: Dag-Erling =?utf-8?q?Sm=C3=B8rgrav?= Subject: Re: ichwd and teethless watchdogd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 23:46:33 -0000 Am Sonntag, 26. August 2007 01:30:01 schrieb Dag-Erling Sm=C3=B8rgrav: > Harald Schmalzbauer writes: > > I thought I was sure that I checked the bios setting and wd timer was > > set to on, but maybe after the laste BIOS update it was reset to off. > > Problem solved, the box reboots whe sigkilling watchdogd. > > Interesting, if your BIOS can disable the WDT without the driver > noticing, it must mean that it implements an SMI handler that resets (or > perhaps stops) the WDT when it expires. AFAIK there is no (documented) > way to either detect or prevent this. If you are interested in the verbose dmesg please find it here: http://www.schmalzbauer.de/korso2/dmesg.verbose I could give you access via serial console too, it's not in production yet. Thanks, =2DHarry