From owner-freebsd-stable@FreeBSD.ORG Sun Sep 19 06:21:06 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB6941065693 for ; Sun, 19 Sep 2010 06:21:06 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail16.syd.optusnet.com.au (mail16.syd.optusnet.com.au [211.29.132.197]) by mx1.freebsd.org (Postfix) with ESMTP id 4B3DB8FC16 for ; Sun, 19 Sep 2010 06:21:05 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c220-239-116-103.belrs4.nsw.optusnet.com.au [220.239.116.103]) by mail16.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id o8J6L1o9000864 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 19 Sep 2010 16:21:03 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.4/8.14.4) with ESMTP id o8J6KxGM000951; Sun, 19 Sep 2010 16:20:59 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.4/8.14.4/Submit) id o8J6KvtF000950; Sun, 19 Sep 2010 16:20:57 +1000 (EST) (envelope-from peter) Date: Sun, 19 Sep 2010 16:20:57 +1000 From: Peter Jeremy To: Eivind E Message-ID: <20100919062057.GE52661@server.vk2pj.dyndns.org> References: <201009132016.o8DKGmw5053180@lurza.secnetix.de> <20100913234355.I96626@rumrunner.mine.nu> <20100914231728.D5192@rumrunner.mine.nu> <20100915214234.I13301@rumrunner.mine.nu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="i0/AhcQY5QxfSsSZ" Content-Disposition: inline In-Reply-To: <20100915214234.I13301@rumrunner.mine.nu> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable@freebsd.org Subject: Re: Freebsd 8.1 + xorg + radeonhd hang X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2010 06:21:06 -0000 --i0/AhcQY5QxfSsSZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2010-Sep-15 22:29:46 +0200, Eivind E wrote: >That has crossed my mind aswell, the only thing which makes me doubt >it is that after updating X number of months ago (probably about a >year and a half), it started to work with no problems whatsoever. >Now, after upgrading again, it has stopped working. Can I suggest adding a "Virtual 1280 1024" (or similar) to the 'SubSection "Display"' of 'Section "Screen"'. I ran into some wierd problems with multiple screens and found that the virtual size isn't correctly initialised unless it's explicitly specified. Also, specifying EXA acceleration is fairly mandatory: The default XAA acceleration is broken. --=20 Peter Jeremy --i0/AhcQY5QxfSsSZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEARECAAYFAkyVq8kACgkQ/opHv/APuIea7ACfXetrCKfqinm8lywKy8Om3rT9 Y1EAnA1L4/v565BlNW+sHKWs6nhiv0pL =kR0A -----END PGP SIGNATURE----- --i0/AhcQY5QxfSsSZ-- From owner-freebsd-stable@FreeBSD.ORG Sun Sep 19 09:18:19 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9180310657FA for ; Sun, 19 Sep 2010 09:18:19 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 481568FC0C for ; Sun, 19 Sep 2010 09:18:18 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1OxFkl-0004jr-Uu>; Sun, 19 Sep 2010 11:00:08 +0200 Received: from e178020196.adsl.alicedsl.de ([85.178.20.196] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1OxFkl-0002Rd-NV>; Sun, 19 Sep 2010 11:00:07 +0200 Message-ID: <4C95D117.1080309@mail.zedat.fu-berlin.de> Date: Sun, 19 Sep 2010 11:00:07 +0200 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20100918 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: Peter Jeremy References: <201009132016.o8DKGmw5053180@lurza.secnetix.de> <20100913234355.I96626@rumrunner.mine.nu> <20100914231728.D5192@rumrunner.mine.nu> <20100915214234.I13301@rumrunner.mine.nu> <20100919062057.GE52661@server.vk2pj.dyndns.org> In-Reply-To: <20100919062057.GE52661@server.vk2pj.dyndns.org> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: 85.178.20.196 Cc: freebsd-stable@freebsd.org, Eivind E Subject: Re: Freebsd 8.1 + xorg + radeonhd hang X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2010 09:18:19 -0000 On 09/19/10 08:20, Peter Jeremy wrote: > On 2010-Sep-15 22:29:46 +0200, Eivind E wrote: >> That has crossed my mind aswell, the only thing which makes me doubt >> it is that after updating X number of months ago (probably about a >> year and a half), it started to work with no problems whatsoever. >> Now, after upgrading again, it has stopped working. In my case, this is exactly the other way around. There was atime when radeonhd and radeon both worked with radeon boards, even with DRI set to on. I recall the the time, whe radeonhd was ugraded to semthing like 1.2.8 or so the problems started occuring (in my case) There is also an issue with SMP. On my private UP box I used a radeon HD4830, both with radeonhd and radeon (tend to use radeonhd because it was faster). Since this box got an hardware exchange (same FBSD 8.1 but with SMP kernel due to dual core, 4GB RAM etc.), both driver, radeon and radeonhd crashes when leaving a X11 session or sending a 'killall -HUP X'. The box simply freezes. My lab's box has now a HD4770 board. The box is also FreeBSD 8.1, SMP kernel, 8GB RAM. No matter what radeon driver, enabling DRI results in a immediate crash of the box when X comes up. Leaving a X11 session also results in a freeze (my crashes are always freezes, there is no coredump, just a black screen).The same happens with a HD4670 board. More interesting is the usage of DBUS and HALD. With both enabled, the box dies immediately when X comes up. No matter whether radeon or radeonhd is used. Well, without X, dbus and hald work well. with X. ... Regards, Oliver From owner-freebsd-stable@FreeBSD.ORG Sun Sep 19 12:28:09 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 423741065675 for ; Sun, 19 Sep 2010 12:28:09 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2-6.sentex.ca [IPv6:2607:f3e0:80:80::2]) by mx1.freebsd.org (Postfix) with ESMTP id BEDBD8FC13 for ; Sun, 19 Sep 2010 12:28:08 +0000 (UTC) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost2.sentex.ca (8.14.4/8.14.4) with ESMTP id o8JCS0be021816 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 19 Sep 2010 08:28:00 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.14.4/8.14.4) with ESMTP id o8JCRxWj052684 for ; Sun, 19 Sep 2010 08:28:00 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <201009191228.o8JCRxWj052684@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sun, 19 Sep 2010 08:27:52 -0400 To: freebsd-stable@freebsd.org From: Mike Tancsa Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.67 on 205.211.164.50 Subject: em nic getting wedged under high load X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2010 12:28:09 -0000 At first we thought it might be the NIC, but we have since changed out the nic, motherboard and power supply. Under high loads, we are seeing the nic become wedged to the point where we have to reboot the box to unwedge it This is an intel board (S3420GPX) from Intel with 8G of RAM, and i5, amd64 running RELENG_8. We first noticed it when we upgraded to an i7 board. Thinking it was hardware, we changed it out to the i5 and are still seeing the nic wedging under high nfs load. em0@pci0:0:25:0: class=0x020000 card=0x34ec8086 chip=0x10ef8086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 13[e0] = PCI Advanced Features: FLR TP em1@pci0:9:0:0: class=0x020000 card=0x34ec8086 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel 82574L Gigabit Ethernet Controller (82574L)' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) cap 11[a0] = MSI-X supports 5 messages in map 0x1c vmstat -i interrupt total rate irq16: siis0 510107 228 irq18: arcmsr0 479177 214 irq19: twa0 16297 7 irq21: ehci0 3390 1 irq23: ehci1 4628 2 cpu0: timer 4469679 1999 irq256: em0 1183006 529 irq257: em1 6120960 2738 irq258: ahci0 507884 227 cpu1: timer 4461694 1996 cpu2: timer 4461618 1996 cpu3: timer 4461832 1996 Total 26680272 11937 In its wedged state, the nic's stats show dev.em.1.%desc: Intel(R) PRO/1000 Network Connection 7.0.5 dev.em.1.%driver: em dev.em.1.%location: slot=0 function=0 handle=\_SB_.PCI0.PEX4.HART dev.em.1.%pnpinfo: vendor=0x8086 device=0x10d3 subvendor=0x8086 subdevice=0x34ec class=0x020000 dev.em.1.%parent: pci9 dev.em.1.nvm: -1 dev.em.1.rx_int_delay: 0 dev.em.1.tx_int_delay: 66 dev.em.1.rx_abs_int_delay: 66 dev.em.1.tx_abs_int_delay: 66 dev.em.1.rx_processing_limit: 100 dev.em.1.link_irq: 0 dev.em.1.mbuf_alloc_fail: 0 dev.em.1.cluster_alloc_fail: 0 dev.em.1.dropped: 0 dev.em.1.tx_dma_fail: 0 dev.em.1.fc_high_water: 18432 dev.em.1.fc_low_water: 16932 dev.em.1.mac_stats.excess_coll: 0 dev.em.1.mac_stats.symbol_errors: 0 dev.em.1.mac_stats.sequence_errors: 0 dev.em.1.mac_stats.defer_count: 0 dev.em.1.mac_stats.missed_packets: 41522 dev.em.1.mac_stats.recv_no_buff: 19 dev.em.1.mac_stats.recv_errs: 0 dev.em.1.mac_stats.crc_errs: 0 dev.em.1.mac_stats.alignment_errs: 0 dev.em.1.mac_stats.coll_ext_errs: 0 dev.em.1.mac_stats.rx_overruns: 41398 dev.em.1.mac_stats.watchdog_timeouts: 0 dev.em.1.mac_stats.xon_recvd: 0 dev.em.1.mac_stats.xon_txd: 0 dev.em.1.mac_stats.xoff_recvd: 0 dev.em.1.mac_stats.xoff_txd: 0 dev.em.1.mac_stats.total_pkts_recvd: 95229129 dev.em.1.mac_stats.good_pkts_recvd: 95187607 dev.em.1.mac_stats.bcast_pkts_recvd: 79244 dev.em.1.mac_stats.mcast_pkts_recvd: 0 dev.em.1.mac_stats.rx_frames_64: 93680 dev.em.1.mac_stats.rx_frames_65_127: 1516349 dev.em.1.mac_stats.rx_frames_128_255: 4464941 dev.em.1.mac_stats.rx_frames_256_511: 4024 dev.em.1.mac_stats.rx_frames_512_1023: 2096067 dev.em.1.mac_stats.rx_frames_1024_1522: 87012546 dev.em.1.mac_stats.good_octets_recvd: 0 dev.em.1.mac_stats.good_octest_txd: 0 dev.em.1.mac_stats.total_pkts_txd: 66775098 dev.em.1.mac_stats.good_pkts_txd: 66775098 dev.em.1.mac_stats.bcast_pkts_txd: 509 dev.em.1.mac_stats.mcast_pkts_txd: 7 dev.em.1.mac_stats.tx_frames_64: 48038472 dev.em.1.mac_stats.tx_frames_65_127: 13402833 dev.em.1.mac_stats.tx_frames_128_255: 5324413 dev.em.1.mac_stats.tx_frames_256_511: 957 dev.em.1.mac_stats.tx_frames_512_1023: 319 dev.em.1.mac_stats.tx_frames_1024_1522: 8104 dev.em.1.mac_stats.tso_txd: 1069 dev.em.1.mac_stats.tso_ctx_fail: 0 dev.em.1.interrupts.asserts: 0 dev.em.1.interrupts.rx_pkt_timer: 0 dev.em.1.interrupts.rx_abs_timer: 0 dev.em.1.interrupts.tx_pkt_timer: 0 dev.em.1.interrupts.tx_abs_timer: 0 dev.em.1.interrupts.tx_queue_empty: 0 dev.em.1.interrupts.tx_queue_min_thresh: 0 dev.em.1.interrupts.rx_desc_min_thresh: 0 dev.em.1.interrupts.rx_overrun: 0 dev.em.1.host.breaker_tx_pkt: 0 dev.em.1.host.host_tx_pkt_discard: 0 dev.em.1.host.rx_pkt: 0 dev.em.1.host.breaker_rx_pkts: 0 dev.em.1.host.breaker_rx_pkt_drop: 0 dev.em.1.host.tx_good_pkt: 0 dev.em.1.host.breaker_tx_pkt_drop: 0 dev.em.1.host.rx_good_bytes: 0 dev.em.1.host.tx_good_bytes: 0 dev.em.1.host.length_errors: 0 dev.em.1.host.serdes_violation_pkt: 0 dev.em.1.host.header_redir_missed: 0 -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike From owner-freebsd-stable@FreeBSD.ORG Sun Sep 19 14:11:49 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34DFA1065670 for ; Sun, 19 Sep 2010 14:11:49 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta11.emeryville.ca.mail.comcast.net (qmta11.emeryville.ca.mail.comcast.net [76.96.27.211]) by mx1.freebsd.org (Postfix) with ESMTP id 193AC8FC1E for ; Sun, 19 Sep 2010 14:11:48 +0000 (UTC) Received: from omta09.emeryville.ca.mail.comcast.net ([76.96.30.20]) by qmta11.emeryville.ca.mail.comcast.net with comcast id 8e9X1f0030S2fkCABeBoZT; Sun, 19 Sep 2010 14:11:48 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta09.emeryville.ca.mail.comcast.net with comcast id 8eBn1f0033LrwQ28VeBnoJ; Sun, 19 Sep 2010 14:11:48 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id F3D319B427; Sun, 19 Sep 2010 07:11:46 -0700 (PDT) Date: Sun, 19 Sep 2010 07:11:46 -0700 From: Jeremy Chadwick To: Ed Schouten Message-ID: <20100919141146.GA7518@icarus.home.lan> References: <20100913065658.GA44306@icarus.home.lan> <201009130721.o8D7LLId098604@lurza.secnetix.de> <20100913074050.GA45070@icarus.home.lan> <20100913184402.GH56986@hoeg.nl> <20100914041954.GA74330@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100914041954.GA74330@icarus.home.lan> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable@FreeBSD.ORG, Oliver Fromme Subject: Re: Serial console problems with stable/8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2010 14:11:49 -0000 On Mon, Sep 13, 2010 at 09:19:54PM -0700, Jeremy Chadwick wrote: > On Mon, Sep 13, 2010 at 08:44:02PM +0200, Ed Schouten wrote: > > Maybe we should just implement /dev/console in such a way that it can > > never get stuck on dcd. I've seen this break too many times. > > > > Below is an untested patch. Anyone willing to test it for me? > > I'll test this out on our RELENG_8 system tonight. RELENG_8 system in question rebuilt with patch; works fine! (Tested both single-user, and multi-user with getty) If solves Oliver's issue, I'd say commit it. :-) -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Sun Sep 19 16:53:21 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35630106566C; Sun, 19 Sep 2010 16:53:21 +0000 (UTC) (envelope-from mack@macktronics.com) Received: from coco.macktronics.com (coco.macktronics.com [209.181.253.65]) by mx1.freebsd.org (Postfix) with ESMTP id 0BF318FC0A; Sun, 19 Sep 2010 16:53:20 +0000 (UTC) Received: from [172.22.30.42] (dulse.macktronics.com [209.181.253.69]) by coco.macktronics.com (Postfix) with ESMTPA id 1712E4AC44; Sun, 19 Sep 2010 11:36:04 -0500 (CDT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=utf-8 From: Dan Mack In-Reply-To: <4C923ECD.8020809@FreeBSD.org> Date: Sun, 19 Sep 2010 11:36:01 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <38552F13-7E0C-4B18-B274-C88D7CE1F04F@macktronics.com> References: <201009152007.17320.Pascal.Stumpf@cubes.de> <201009151830.o8FIUWEZ021844@lava.sentex.ca> <4C911AB0.6090901@delphij.net> <4C91AEBF.50502@FreeBSD.org> <201009161355.o8GDtroR028629@lava.sentex.ca> <4C923557.40004@DataIX.net> <201009161543.o8GFhJnh029157@lava.sentex.ca> <4C923ECD.8020809@FreeBSD.org> To: Martin Matuska X-Mailer: Apple Mail (2.1081) Cc: jhell , stable@freebsd.org Subject: Re: MFC of ZFSv15 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2010 16:53:21 -0000 But I should be able to boot my ZFSv14 root pool using the ZFSv15 build = of FreeBSD, correct? But the problem scenario would be when I've = upgraded my root pool to v15 and I attempt to boot it with v14 boot = loader. At least that is what I think ... I guess what I'm getting at is ... you should be able to buildworld, = installkernel, reboot, installworld, reboot without worry. But after = your run 'zpool upgrade', you will need to re-write the bootcode using = gpart on each of your root pool ZFS disks. Am I understanding this correctly ? Thanks for all the work on ZFS BTW, it's great! Dan On Sep 16, 2010, at 10:59 AM, Martin Matuska wrote: > Dont forget to read the general "ZFS notes" section in UPDATING: >=20 > ZFS notes > --------- > When upgrading the boot ZFS pool to a new version, always follow > these two steps: >=20 > 1.) recompile and reinstall the ZFS boot loader and boot block > (this is part of "make buildworld" and "make installworld") >=20 > 2.) update the ZFS boot block on your boot drive >=20 > The following example updates the ZFS boot block on the first > partition (freebsd-boot) of a GPT partitioned drive ad0: > "gpart bootcode -p /boot/gptzfsboot -i 1 ad0" >=20 > Non-boot pools do not need these updates. >=20 > D=C5=88a 16. 9. 2010 17:43, Mike Tancsa wrote / nap=C3=ADsal(a): >> At 11:18 AM 9/16/2010, jhell wrote: >>> On 09/16/2010 09:55, Mike Tancsa wrote: >>>>=20 >>>> Thanks again for all the ZFS fixes and enhancements! Are there any >>>> caveats to upgrading ? >>>>=20 >>>> Do I just do >>>>=20 >>>> zpool upgrade -a >>>> zfs upgrade -a >>>>=20 >>>> or are there any extra steps ? >>>>=20 >>>=20 >>> Hi Mike, >>>=20 >>> No-one knows your bootcode better than you. So if you are upgrading >>> don't forget if you are on a ZFS root then your bootcode might need >>> updating. >>=20 >>=20 >> Hi, >> I am booting off UFS right now so no bootcode updates for me :) I did >> look at UPDATING which does mention >>=20 >> 20100915: >> A new version of ZFS (version 15) has been merged. >> This version uses a python library for the following subcommands: >> zfs allow, zfs unallow, zfs groupspace, zfs userspace. >> For full functionality of these commands the following port must >> be installed: sysutils/py-zfs >>=20 >> ---Mike >>=20 >>=20 >> -------------------------------------------------------------------- >> Mike Tancsa, tel +1 519 651 3400 >> Sentex Communications, mike@sentex.net >> Providing Internet since 1994 www.sentex.net >> Cambridge, Ontario Canada www.sentex.net/mike > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" Dan -- Dan Mack mack@macktronics.com From owner-freebsd-stable@FreeBSD.ORG Sun Sep 19 16:58:21 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 781D3106564A for ; Sun, 19 Sep 2010 16:58:21 +0000 (UTC) (envelope-from mack@macktronics.com) Received: from coco.macktronics.com (coco.macktronics.com [209.181.253.65]) by mx1.freebsd.org (Postfix) with ESMTP id 515618FC12 for ; Sun, 19 Sep 2010 16:58:21 +0000 (UTC) Received: from [172.22.30.42] (dulse.macktronics.com [209.181.253.69]) by coco.macktronics.com (Postfix) with ESMTPA id 13ECA4AC40; Sun, 19 Sep 2010 11:33:38 -0500 (CDT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Dan Mack In-Reply-To: <4C9269EB.8020002@restart.be> Date: Sun, 19 Sep 2010 11:33:33 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: <201009152007.17320.Pascal.Stumpf@cubes.de> <201009151830.o8FIUWEZ021844@lava.sentex.ca> <4C911AB0.6090901@delphij.net> <4C91AEBF.50502@FreeBSD.org> <201009161355.o8GDtroR028629@lava.sentex.ca> <4C923557.40004@DataIX.net> <4C9269EB.8020002@restart.be> To: Henri Hennebert X-Mailer: Apple Mail (2.1081) Cc: freebsd-stable@freebsd.org Subject: Re: MFC of ZFSv15 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2010 16:58:21 -0000 But I should be able to boot my ZFSv14 root pool using the ZFSv15 build = of FreeBSD, correct? But the problem scenario would be when I've = upgraded by root pool to v15 and I attempt to boot it with v14 boot = loader. At least that is what I think ... I guess what I'm getting at is ... you should be able to buildworld, = installkernel, reboot, installworld, reboot without worry. But when = after your run 'zpool upgrade', you will need to re-write the bootcode = using gpart on each of your root pool ZFS disks. Am I understanding this correctly ? Thanks for all the work on ZFS BTW, it's great! Dan On Sep 16, 2010, at 2:03 PM, Henri Hennebert wrote: > On 09/16/2010 17:18, jhell wrote: >> On 09/16/2010 09:55, Mike Tancsa wrote: >>>=20 >>> Thanks again for all the ZFS fixes and enhancements! Are there any >>> caveats to upgrading ? >>>=20 >>> Do I just do >>>=20 >>> zpool upgrade -a >>> zfs upgrade -a >>>=20 >>> or are there any extra steps ? >>>=20 >>=20 >> Hi Mike, >>=20 >> No-one knows your bootcode better than you. So if you are upgrading >> don't forget if you are on a ZFS root then your bootcode might need >> updating. >>=20 > I was bitten by this problem in a previous ZFS upgrade. >=20 > To be sure, I have added this patch to zfsimpl.c so, at boot I know if = zpool/zfs upgrade will be OK. >=20 > Henri >>=20 >> Regards, UPDATING should have anything else. >>=20 >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" Dan -- Dan Mack mack@macktronics.com From owner-freebsd-stable@FreeBSD.ORG Sun Sep 19 17:41:41 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10EFE1065674; Sun, 19 Sep 2010 17:41:41 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3fd3:cd67:fafa:3d78]) by mx1.freebsd.org (Postfix) with ESMTP id 82A778FC14; Sun, 19 Sep 2010 17:41:40 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [81.187.76.163]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.4/8.14.4) with ESMTP id o8JHfZZI026488 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 19 Sep 2010 18:41:35 +0100 (BST) (envelope-from m.seaman@infracaninophile.co.uk) Message-ID: <4C964B49.6080102@infracaninophile.co.uk> Date: Sun, 19 Sep 2010 18:41:29 +0100 From: Matthew Seaman Organization: Infracaninophile User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: Dan Mack References: <201009152007.17320.Pascal.Stumpf@cubes.de> <201009151830.o8FIUWEZ021844@lava.sentex.ca> <4C911AB0.6090901@delphij.net> <4C91AEBF.50502@FreeBSD.org> <201009161355.o8GDtroR028629@lava.sentex.ca> <4C923557.40004@DataIX.net> <201009161543.o8GFhJnh029157@lava.sentex.ca> <4C923ECD.8020809@FreeBSD.org> <38552F13-7E0C-4B18-B274-C88D7CE1F04F@macktronics.com> In-Reply-To: <38552F13-7E0C-4B18-B274-C88D7CE1F04F@macktronics.com> X-Enigmail-Version: 1.1.1 OpenPGP: id=60AE908C Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigAF501D63D208275920E42A13" X-Virus-Scanned: clamav-milter 0.96.2 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_20,DKIM_ADSP_ALL, SPF_FAIL autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on lucid-nonsense.infracaninophile.co.uk Cc: jhell , stable@freebsd.org, Martin Matuska Subject: Re: MFC of ZFSv15 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2010 17:41:41 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigAF501D63D208275920E42A13 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 19/09/2010 17:36:01, Dan Mack wrote: > But I should be able to boot my ZFSv14 root pool using the ZFSv15 > build of FreeBSD, correct? But the problem scenario would be when > I've upgraded my root pool to v15 and I attempt to boot it with v14 > boot loader. At least that is what I think ... Yes. The bootloader is not prescient, so bootloader compiled against v14 can't cope with a zpool using v15. It's only the on-disk format that counts in this: zfs software will operate perfectly well with older on-disk data formats. > I guess what I'm getting at is ... you should be able to buildworld, > installkernel, reboot, installworld, reboot without worry. But > after your run 'zpool upgrade', you will need to re-write the > bootcode using gpart on each of your root pool ZFS disks. If you want to be completely paranoid, you could update the bootcode on your boot drive (or one out of a mirror pair, if that's what you're using) at the point of running installkernel and way before you run 'zpool upgrade'. In theory, should this go horribly wrong and you end up with an unbootable system, you can recover by booting the 8.0 install media into FIXIT mode and reinstalling the bootblocks from there (or booting from the other disk in your mirror set). Once you've got a system you know will reboot with the new bootblocks, then go ahead and with installworld and updating the zpool version. > Am I understanding this correctly ? Yep. That's quite right. Running 'zpool upgrade -a' is one of those operations you can't easily reverse, so designing an upgrade plan where you can stop and back-out at any point is quite tricky. Fortunately, the risk of things going wrong at the point of running zpool upgrade is really very small, so for most purposes, just ploughing ahead and accepting the really very small risk is going to be acceptable. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matthew@infracaninophile.co.uk Kent, CT11 9PW --------------enigAF501D63D208275920E42A13 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyWS08ACgkQ8Mjk52CukIxuSACglXbPehlYot8K6XWTNd2NeLM1 sj8Anj5UlHd336UG7h+JW+anCNjUknPV =HtK/ -----END PGP SIGNATURE----- --------------enigAF501D63D208275920E42A13-- From owner-freebsd-stable@FreeBSD.ORG Sun Sep 19 18:24:42 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CADCB106566B; Sun, 19 Sep 2010 18:24:42 +0000 (UTC) (envelope-from mack@macktronics.com) Received: from coco.macktronics.com (coco.macktronics.com [209.181.253.65]) by mx1.freebsd.org (Postfix) with ESMTP id 86E9E8FC13; Sun, 19 Sep 2010 18:24:42 +0000 (UTC) Received: from [172.22.30.42] (dulse.macktronics.com [209.181.253.69]) by coco.macktronics.com (Postfix) with ESMTPA id D51994AC41; Sun, 19 Sep 2010 13:24:39 -0500 (CDT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Dan Mack In-Reply-To: <4C964B49.6080102@infracaninophile.co.uk> Date: Sun, 19 Sep 2010 13:24:39 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: <201009152007.17320.Pascal.Stumpf@cubes.de> <201009151830.o8FIUWEZ021844@lava.sentex.ca> <4C911AB0.6090901@delphij.net> <4C91AEBF.50502@FreeBSD.org> <201009161355.o8GDtroR028629@lava.sentex.ca> <4C923557.40004@DataIX.net> <201009161543.o8GFhJnh029157@lava.sentex.ca> <4C923ECD.8020809@FreeBSD.org> <38552F13-7E0C-4B18-B274-C88D7CE1F04F@macktronics.com> <4C964B49.6080102@infracaninophile.co.uk> To: Matthew Seaman X-Mailer: Apple Mail (2.1081) Cc: jhell , stable@freebsd.org, Martin Matuska Subject: Re: MFC of ZFSv15 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2010 18:24:42 -0000 Thanks for the confirmation. This worked fine and I did notice that = "zpool upgrade zroot" was nice enough to emit the reminder: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0 which is slightly different than the recipe given in /usr/src/UPDATING: "gpart bootcode -p /boot/gptzfsboot -i 1 ad0" Since the recipe for my root/zfs system included pmbr and gptzfsboot, I = used the example emitted from the zpool command instead of the one from = UPDATING. e.g. pool: zroot state: ONLINE status: The pool is formatted using an older on-disk format. The pool = can still be used, but some features are unavailable. action: Upgrade the pool using 'zpool upgrade'. Once this is done, the pool will no longer be accessible on older software versions. scrub: none requested config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 mirror ONLINE 0 0 0 gpt/disk0 ONLINE 0 0 0 gpt/disk1 ONLINE 0 0 0 errors: No known data errors (zfs) ~ # zpool upgrade zroot This system is currently running ZFS pool version 15. Successfully upgraded 'zroot' from version 14 to version 15 If you boot from pool 'zroot', don't forget to update boot code. Assuming you use GPT partitioning and da0 is your boot disk the following command will do it: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0 (zfs) ~/zfs # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad4 ad4 has bootcode (zfs) ~/zfs # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad5 ad5 has bootcode (zfs) ~/zfs # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad6 ad6 has bootcode (zfs) ~/zfs # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad7 ad7 has bootcode (zfs) ~/zfs # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad8 ad8 has bootcode (zfs) ~/zfs # reboot Dan On Sep 19, 2010, at 12:41 PM, Matthew Seaman wrote: > On 19/09/2010 17:36:01, Dan Mack wrote: >> But I should be able to boot my ZFSv14 root pool using the ZFSv15 >> build of FreeBSD, correct? But the problem scenario would be when >> I've upgraded my root pool to v15 and I attempt to boot it with v14 >> boot loader. At least that is what I think ... >=20 > Yes. The bootloader is not prescient, so bootloader compiled against > v14 can't cope with a zpool using v15. It's only the on-disk format > that counts in this: zfs software will operate perfectly well with = older > on-disk data formats. >=20 >> I guess what I'm getting at is ... you should be able to buildworld, >> installkernel, reboot, installworld, reboot without worry. But >> after your run 'zpool upgrade', you will need to re-write the >> bootcode using gpart on each of your root pool ZFS disks. >=20 > If you want to be completely paranoid, you could update the bootcode = on > your boot drive (or one out of a mirror pair, if that's what you're > using) at the point of running installkernel and way before you run > 'zpool upgrade'. In theory, should this go horribly wrong and you end > up with an unbootable system, you can recover by booting the 8.0 = install > media into FIXIT mode and reinstalling the bootblocks from there (or > booting from the other disk in your mirror set). Once you've got a > system you know will reboot with the new bootblocks, then go ahead and > with installworld and updating the zpool version. >=20 >> Am I understanding this correctly ? >=20 > Yep. That's quite right. Running 'zpool upgrade -a' is one of those > operations you can't easily reverse, so designing an upgrade plan = where > you can stop and back-out at any point is quite tricky. Fortunately, > the risk of things going wrong at the point of running zpool upgrade = is > really very small, so for most purposes, just ploughing ahead and > accepting the really very small risk is going to be acceptable. >=20 > Cheers, >=20 > Matthew >=20 > --=20 > Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard > Flat 3 > PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate > JID: matthew@infracaninophile.co.uk Kent, CT11 9PW >=20 Dan -- Dan Mack mack@macktronics.com From owner-freebsd-stable@FreeBSD.ORG Sun Sep 19 18:33:15 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 661101065670; Sun, 19 Sep 2010 18:33:15 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 3E5A48FC13; Sun, 19 Sep 2010 18:33:15 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id B9ADE46B8A; Sun, 19 Sep 2010 14:33:14 -0400 (EDT) Date: Sun, 19 Sep 2010 19:33:14 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Vadim Goncharov In-Reply-To: Message-ID: References: <201009011653.o81Grkm4056064@fire.js.berklix.net> <201009011902.06538.hselasky@c2i.net> <4C8627A6.1090308@icyb.net.ua> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-security@freebsd.org, freebsd-stable@freebsd.org Subject: Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2010 18:33:15 -0000 On Wed, 8 Sep 2010, Vadim Goncharov wrote: >> Which part of "support for the Giant lock *over the network stack* was >> removed" [emphasis mine] do you not understand? > > No, component removed was (1), I've underlined. > >> The reason is performance for overall network stack, not ideology. > > For a practical reasons, "it works but slow" is better than "doesn't work at > all (due to absence of code in the src tree)". > > "Make it work. Make it right. Make it fast. In that order", know this? > Sacrificing "work" for "fast"?.. Hmm, if it is not ideology, then what is > it?.. Doug has already clarified, but just to follow up with some detail: Moving to a parallel network stack required that all portions of the stack code be updated to operate without the Giant lock present -- the Giant lock was a fundamental assumption in all kernel code in FreeBSD 4.x and earlier. This decade-long project was highly successful, and relied on members of the community stepping forward to adapt a very large code base by adding fine-grained locking to each component. The results have been extremely impressive, allowing our network stack to scale to 8+ CPUs (I'm actually testing with 32-thread systems as part of some network stack work I'm doing right now). Towards the end of the project, it was clear that a few components in the stack had attracted no interest from the community, and as such, were not going to get updated. As such, we went through a public deprecation and removal process, in which we appealed repeatedly for community members to update the code. This included i4b, one of our three ATM implementations, and one of our two IPSEC implementations. I've attached the i4b schedule below (a three-year process), but you can find information on the full process here: http://wiki.freebsd.org/NONMPSAFE_DEORBIT This was not an issue of i4b operating more slowly than the rest of the stack: it was that the code required fundamental architectural changes without which it couldn't compile, let alone run. We're all happy to have ISDN support come back in the tree if there's an owner for doing it! In the end, any significant code base in the kernel requires ownership -- it can continue through many minor changes without an owner, but major retrofits, such as moving to fine-grained locking, need the attention of someone who understands the code, is able to test the code, and has the time to invest in the code. We do a pretty good job at arranging this with a multi-million line code base, all told. Robert Date Done Event 18 July 2005 yes Post MPSAFE network stack plan to arch@. 04 July 2007 yes Disconnect parts of I4B from the build. HEADS-UP to isdn@. 17 July 2007 yes Post NET_NEEDS_GIANT() reminder to arch@. 27 July 2007 yes Remove NET_NEEDS_GIANT(). 22 March 2008 yes Last call to seek for help rewriting I4B to keep it alive. 15 May 2008 yes Final announcement on isdn@ that I4B will be removed from 8/7. 26 May 2008 yes Remove i4b from HEAD. From owner-freebsd-stable@FreeBSD.ORG Sun Sep 19 18:37:22 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A192106566B for ; Sun, 19 Sep 2010 18:37:22 +0000 (UTC) (envelope-from prox@prolixium.com) Received: from nox.prolixium.com (nox.prolixium.com [IPv6:2001:48c8:1:104::1e]) by mx1.freebsd.org (Postfix) with ESMTP id 15D9E8FC1C for ; Sun, 19 Sep 2010 18:37:22 +0000 (UTC) Received: from prox by nox.prolixium.com with local (Exim 4.72) (envelope-from ) id 1OxOlN-0007Qf-4a for freebsd-stable@freebsd.org; Sun, 19 Sep 2010 14:37:21 -0400 Date: Sun, 19 Sep 2010 14:37:21 -0400 From: Mark Kamichoff To: freebsd-stable@freebsd.org Message-ID: <20100919183721.GA17616@prolixium.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0OAP2g/MAC+5xKAE" Content-Disposition: inline X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: prox@prolixium.com X-SA-Exim-Scanned: No (on nox.prolixium.com); SAEximRunCond expanded to false Subject: BIND9 built w/--disable-ipv6 on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2010 18:37:22 -0000 --0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi -=20 I just noticed (well, via a discussion in #ipv6 on freenode) that the default configure arguments for BIND9 on 8.1 include '--disable-ipv6'. % grep CONFIGARGS /usr/src/usr.sbin/named/Makefile=20 CONFIGARGS=3D'--prefix=3D/usr' '--infodir=3D/usr/share/info' '--mandir=3D/usr/share/man' '--enable-threads' '--disable-ipv6' '--enable-getifaddrs' '--disable-linux-caps' '--with-openssl=3D/usr' '--with-randomdev=3D/dev/random' This results in BIND9 not listening on IPv6 sockets, even if the listen-on-v6 directive is explicitly configured in the configuration file. Even worse, and why I didn't pick up on it until now, is that no warnings or errors are emitted about this during startup, although I suppose that is more of a BIND problem than a FreeBSD one. Strangely enough, the control socket still listens on ::1 in addition to 127.0.0.1. Does anyone know why this was done, or if there's any harm in reenabling it and rebuilding? - Mark --=20 Mark Kamichoff prox@prolixium.com http://www.prolixium.com/ --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkyWWGEACgkQ0TYC9KtF8BOTawCeJU9F41ZC/HJbrfDdcZsVTMlC cREAn2rSCTG8J+4B3EoceibmJhseESoS =2xjh -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE-- From owner-freebsd-stable@FreeBSD.ORG Sun Sep 19 18:55:28 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED6A7106564A for ; Sun, 19 Sep 2010 18:55:28 +0000 (UTC) (envelope-from prox@prolixium.com) Received: from nox.prolixium.com (nox.prolixium.com [IPv6:2001:48c8:1:104::1e]) by mx1.freebsd.org (Postfix) with ESMTP id B86F78FC16 for ; Sun, 19 Sep 2010 18:55:28 +0000 (UTC) Received: from prox by nox.prolixium.com with local (Exim 4.72) (envelope-from ) id 1OxP2u-0007pV-6K for freebsd-stable@freebsd.org; Sun, 19 Sep 2010 14:55:28 -0400 Date: Sun, 19 Sep 2010 14:55:28 -0400 From: Mark Kamichoff To: freebsd-stable@freebsd.org Message-ID: <20100919185528.GA28845@prolixium.com> References: <20100919183721.GA17616@prolixium.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RnlQjJ0d97Da+TV1" Content-Disposition: inline In-Reply-To: <20100919183721.GA17616@prolixium.com> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: prox@prolixium.com X-SA-Exim-Scanned: No (on nox.prolixium.com); SAEximRunCond expanded to false Subject: Re: BIND9 built w/--disable-ipv6 on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2010 18:55:29 -0000 --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 19, 2010 at 02:37:21PM -0400, Mark Kamichoff wrote: > I just noticed (well, via a discussion in #ipv6 on freenode) that the > default configure arguments for BIND9 on 8.1 include '--disable-ipv6'. >=20 > % grep CONFIGARGS /usr/src/usr.sbin/named/Makefile=20 > CONFIGARGS=3D'--prefix=3D/usr' '--infodir=3D/usr/share/info' > '--mandir=3D/usr/share/man' '--enable-threads' '--disable-ipv6' > '--enable-getifaddrs' '--disable-linux-caps' '--with-openssl=3D/usr' > '--with-randomdev=3D/dev/random' >=20 > This results in BIND9 not listening on IPv6 sockets, even if the > listen-on-v6 directive is explicitly configured in the configuration > file. Even worse, and why I didn't pick up on it until now, is that no > warnings or errors are emitted about this during startup, although I > suppose that is more of a BIND problem than a FreeBSD one. Strangely > enough, the control socket still listens on ::1 in addition to > 127.0.0.1. >=20 > Does anyone know why this was done, or if there's any harm in reenabling > it and rebuilding? Well, you can safely ignore this! I realized afterwards that '--disable-ipv6' just disables the default use of IPv6 in BIND, it doesn't completely disable the protocol. Turns out I was querying the wrong address with DIG when testing this, too. listen-on-v6 certainly works as expected, and enables IPv6 like it should. Although, that still does beg the question, why don't we want IPv6 enabled by default on new BIND installations? - Mark --=20 Mark Kamichoff prox@prolixium.com http://www.prolixium.com/ --RnlQjJ0d97Da+TV1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkyWXKAACgkQ0TYC9KtF8BPJKgCeMyQA2FLrz3t7TqzNXc7bt/GQ xAcAnj3XEXwppM1+JFnWuSd6nmdtyUHi =4roe -----END PGP SIGNATURE----- --RnlQjJ0d97Da+TV1-- From owner-freebsd-stable@FreeBSD.ORG Sun Sep 19 19:22:34 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3009F1065675 for ; Sun, 19 Sep 2010 19:22:34 +0000 (UTC) (envelope-from hlh@restart.be) Received: from tignes.restart.be (tignes.restart.be [IPv6:2001:41d0:2:2d29:0:1::]) by mx1.freebsd.org (Postfix) with ESMTP id A95D58FC15 for ; Sun, 19 Sep 2010 19:22:33 +0000 (UTC) Received: from restart.be (avoriaz.tunnel.bel [IPv6:2001:41d0:2:2d29:1:ffff::]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "smtp.restart.be", Issuer "CA master" (verified OK)) by tignes.restart.be (Postfix) with ESMTPS id 384D313F6D; Sun, 19 Sep 2010 21:22:32 +0200 (CEST) Received: from meribel.restart.bel (meribel.restart.bel [IPv6:2001:41d0:2:2d29:1:8::]) (authenticated bits=0) by restart.be (8.14.4/8.14.4) with ESMTP id o8JJMT4v061485 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Sun, 19 Sep 2010 21:22:31 +0200 (CEST) (envelope-from hlh@restart.be) X-DKIM: Sendmail DKIM Filter v2.8.3 restart.be o8JJMT4v061485 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=restart.be; s=avoriaz; t=1284924151; bh=QGK+1wcp4GmpB/otBWmmjzWLJf2jblZFYedcoZLu6zA=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=YEcuVbgylAQS3sj39x2zsskY7+5S2DvSW0MD92ZlWkYEEmbjPbviKwEqcoNllrtZR q9UsUEWYG7D39a34sUl4g== X-DomainKeys: Sendmail DomainKeys Filter v1.0.2 restart.be o8JJMT4v061485 DomainKey-Signature: a=rsa-sha1; s=avoriaz; d=restart.be; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:cc:subject: references:in-reply-to:x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=qd9GSENHzsYMVuAvbYmgUeb6x53wzQo66li+L2OLaZjAWSN4N6aXPscgRMEL2Rz0q 9AIB/koA4N4buQpbdyZOA== Message-ID: <4C9662F5.2070003@restart.be> Date: Sun, 19 Sep 2010 21:22:29 +0200 From: Henri Hennebert User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.12) Gecko/20100911 Thunderbird/3.0.7 MIME-Version: 1.0 To: Dan Mack References: <201009152007.17320.Pascal.Stumpf@cubes.de> <201009151830.o8FIUWEZ021844@lava.sentex.ca> <4C911AB0.6090901@delphij.net> <4C91AEBF.50502@FreeBSD.org> <201009161355.o8GDtroR028629@lava.sentex.ca> <4C923557.40004@DataIX.net> <4C9269EB.8020002@restart.be> In-Reply-To: X-Enigmail-Version: 1.0.1 OpenPGP: id=D351A503 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: MFC of ZFSv15 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2010 19:22:34 -0000 On 09/19/2010 18:33, Dan Mack wrote: > But I should be able to boot my ZFSv14 root pool using the ZFSv15 build of FreeBSD, correct? Yes > But the problem scenario would be when I've upgraded by root pool to v15 and I attempt to boot it with v14 boot loader. At least that is what I think ... You are right > > I guess what I'm getting at is ... you should be able to buildworld, installkernel, reboot, installworld, reboot without worry. It is the case > But when after your run 'zpool upgrade', you will need to re-write the bootcode using gpart on each of your root pool ZFS disks. I prefer to install bootcode BEFORE. Then reboot and check it with the printf of my simple patch. Then you can zpool/zfs upgrade without problem. > > Am I understanding this correctly ? > > Thanks for all the work on ZFS BTW, it's great! > > Dan > > On Sep 16, 2010, at 2:03 PM, Henri Hennebert wrote: > >> On 09/16/2010 17:18, jhell wrote: >>> On 09/16/2010 09:55, Mike Tancsa wrote: >>>> >>>> Thanks again for all the ZFS fixes and enhancements! Are there any >>>> caveats to upgrading ? >>>> >>>> Do I just do >>>> >>>> zpool upgrade -a >>>> zfs upgrade -a >>>> >>>> or are there any extra steps ? >>>> >>> >>> Hi Mike, >>> >>> No-one knows your bootcode better than you. So if you are upgrading >>> don't forget if you are on a ZFS root then your bootcode might need >>> updating. >>> >> I was bitten by this problem in a previous ZFS upgrade. >> >> To be sure, I have added this patch to zfsimpl.c so, at boot I know if zpool/zfs upgrade will be OK. >> >> Henri >>> >>> Regards, UPDATING should have anything else. >>> >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > Dan > -- > Dan Mack > mack@macktronics.com > > > > > > From owner-freebsd-stable@FreeBSD.ORG Sun Sep 19 22:31:25 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0DE3106566B for ; Sun, 19 Sep 2010 22:31:25 +0000 (UTC) (envelope-from lioux@FreeBSD.org) Received: from goat.gigo.com (ipv6.gigo.com [IPv6:2001:470:1:18::2]) by mx1.freebsd.org (Postfix) with ESMTP id C8FFA8FC08 for ; Sun, 19 Sep 2010 22:31:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by goat.gigo.com (Postfix) with ESMTP id AC88311462 for ; Sun, 19 Sep 2010 15:31:25 -0700 (PDT) Received: from goat.gigo.com ([127.0.0.1]) by localhost (vette.gigo.com [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id usqJoGQ3IuFg for ; Sun, 19 Sep 2010 15:31:25 -0700 (PDT) Received: from 200.101.95.66 (200-101-95-66.bsace702.dsl.brasiltelecom.net.br [200.101.95.66]) by goat.gigo.com (Postfix) with ESMTPSA id BC44911461 for ; Sun, 19 Sep 2010 15:31:24 -0700 (PDT) Received: (qmail 70669 invoked by uid 1001); 19 Sep 2010 19:28:13 -0300 Message-ID: <20100919222837.70629.qmail@exxodus.fedaykin.here> Date: Sun, 19 Sep 2010 19:28:13 -0300 From: Mario Sergio Fujikawa Ferreira To: freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Subject: Panic with chromium and 8.1-STABLE (Thu Sep 16 09:52:17 BRT 2010) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2010 22:31:26 -0000 Hi, I've just began trying chrome web browser from http://chromium.hybridsource.org/ but it triggered 2 panics on my 8.1-STABLE system. $ uname -a FreeBSD exxodus.fedaykin.here 8.1-STABLE FreeBSD 8.1-STABLE #26: Thu Sep 16 09:52:17 BRT 2010 lioux@exxodus:/usr/obj/usr/src/sys/LIOUX amd64 The panic information is: ------------ panic: vm_page_unwire: invalid wire count: 0 cpuid = 0 KDB: enter: panic 0xffffff006ecce000: tag ufs, type VREG usecount 1, writecount 1, refcount 4 mountedhere 0 flags () v_object 0xffffff0151489870 ref 0 pages 8 lock type ufs: EXCL by thread 0xffffff00200947c0 (pid 25025) ino 119526591, on dev ufs/fsusr 0xffffff011107f938: tag ufs, type VREG usecount 0, writecount 0, refcount 4 mountedhere 0 flags (VV_NOSYNC|VI_DOINGINACT) v_object 0xffffff0151f7f870 ref 0 pages 1284 lock type ufs: EXCL by thread 0xffffff01882cc7c0 (pid 26689) ino 263, on dev md0 ------------ I've made available 2 ddb textdumps at: http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.0 http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.1 I was able to use chrome prior to this latest kernel update. Now, I can reproduce a kernel panic even browsing www.google.com Please, let me know if I can provide any further information. Regards, -- Mario S F Ferreira - DF - Brazil - "I guess this is a signature." feature, n: a documented bug | bug, n: an undocumented feature From owner-freebsd-stable@FreeBSD.ORG Mon Sep 20 07:29:49 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 055FC106566B; Mon, 20 Sep 2010 07:29:49 +0000 (UTC) (envelope-from eugene@imedia.ru) Received: from lynx.imedia.ru (lynx.imedia.ru [83.242.167.254]) by mx1.freebsd.org (Postfix) with ESMTP id 518EF8FC0C; Mon, 20 Sep 2010 07:29:47 +0000 (UTC) X-All-Recipients: Received: from badger.imedia.ru (root@badger.imedia.ru [10.167.1.243]) by lynx.imedia.ru (8.14.3/8.14.3/TWINS7_LDAP) with ESMTP id o8K7DQEc094535; Mon, 20 Sep 2010 11:13:26 +0400 (MSD) (envelope-from eugene@imedia.ru) Received: from badger.imedia.ru (eugene@localhost [127.0.0.1]) by badger.imedia.ru (8.14.3/8.13.1) with ESMTP id o8K7DQ9s077565; Mon, 20 Sep 2010 11:13:26 +0400 (MSD) (envelope-from eugene@imedia.ru) Received: from localhost (localhost [[UNIX: localhost]]) by badger.imedia.ru (8.14.3/8.13.8/Submit) id o8K7DO5I077564; Mon, 20 Sep 2010 11:13:24 +0400 (MSD) (envelope-from eugene@imedia.ru) From: Eugene Mitrofanov Organization: Independent Media Sanoma Magazines To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Date: Mon, 20 Sep 2010 11:13:23 +0400 User-Agent: KMail/1.9.10 X-Origin: badger.imedia.ru MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201009201113.24220.eugene@imedia.ru> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (lynx.imedia.ru [10.167.0.252]); Mon, 20 Sep 2010 11:13:26 +0400 (MSD) X-Virus-Scanned: clamav-milter 0.96.2-exp at lynx.imedia.ru X-Virus-Status: Clean Cc: Subject: vlan + ng_ipfw + ng_netflow == no success X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Eugene Mitrofanov List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2010 07:29:49 -0000 Hello I need the advise. Does anybody got the Subj working? I have FreeBSD 7.3-p2, Generic kernel. I try to set up the netflow traffic accounting using ng_ipfw from vlan interface. I created vlan interface, ipfw rule, set up ng hooks but the netflow export is not working. tcpdump does not catch any packets to the collector. Any suggestion? Should I create the bug report? - - - - - - - - # ifconfig vlan1 create vlan 1 vlandev fxp0 inet 192.168.1.1 netmask 255.255.255.0 # ipfw add 10 ngtee 1 via vlan1 # ngctl -f - < - - - - - - - Good luck -- EMIT-RIPN, EVM7-RIPE From owner-freebsd-stable@FreeBSD.ORG Mon Sep 20 08:12:57 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 559581065674 for ; Mon, 20 Sep 2010 08:12:57 +0000 (UTC) (envelope-from jon.otterholm@ide.resurscentrum.se) Received: from mail1.cil.se (mail1.cil.se [217.197.56.125]) by mx1.freebsd.org (Postfix) with ESMTP id E7DEE8FC08 for ; Mon, 20 Sep 2010 08:12:56 +0000 (UTC) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 20 Sep 2010 10:00:48 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Dummynet Thread-Index: ActYmZCiLMMiYArDT7GIioYM11WNDg== From: "Jon Otterholm" To: Subject: Dummynet X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2010 08:12:57 -0000 Hi. Sorry for cross-posting, got nothing back from freebsd-ipfw... Installed a new router running 8-stable and encounter some problems when configuring dummynet pipes: When setting buckets above 1024... ipfw pipe 91 config bw 100Mbit/s mask src-ip 0xffffffff buckets 4096 ...I get the following error: Clamp sched buckets to 1024 (was 4096) # sysctl net.inet.ip.dummynet.hash_size net.inet.ip.dummynet.hash_size: 4096 from man ipfw: buckets hash-table-size Specifies the size of the hash table used for storing the various queues. Default value is 64 controlled by the sysctl(8) variable net.inet.ip.dummynet.hash_size, allowed range is 16 to 65536. Am I missing something here? This worked fine in the 7-branch. //JO From owner-freebsd-stable@FreeBSD.ORG Mon Sep 20 08:57:10 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3D88106566C for ; Mon, 20 Sep 2010 08:57:10 +0000 (UTC) (envelope-from serguey-grigoriev@yandex.ru) Received: from forward3.mail.yandex.net (forward3.mail.yandex.net [77.88.46.8]) by mx1.freebsd.org (Postfix) with ESMTP id 837E58FC21 for ; Mon, 20 Sep 2010 08:57:10 +0000 (UTC) Received: from web78.yandex.ru (web78.yandex.ru [77.88.47.203]) by forward3.mail.yandex.net (Yandex) with ESMTP id 8591956D8A83 for ; Mon, 20 Sep 2010 12:42:08 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1284972128; bh=jEjDWQUlIIbLXuhh33r7PyoEl/ZdKqkpkQ/4FlWasAk=; h=From:To:In-Reply-To:References:Subject:MIME-Version:Message-Id: Date:Content-Transfer-Encoding:Content-Type; b=Xy9qrXYI3Sy7JNUdAHRXiV8ZGuKLmgw1KuZ1SbZCo9RSiE4OsO1WnM8xIiRudEvFe TX7lQGDVg27qMQoiE2t251MES4hnXZ/CX0A4e0qqm1TeFlEc/5DfgQZ+m12GFxReLl rC6YGl/96nDNmC7aNtMIwkFy3//ewNHrhfkH6kt8= Received: from localhost (localhost.localdomain [127.0.0.1]) by web78.yandex.ru (Yandex) with ESMTP id 81C423A0036 for ; Mon, 20 Sep 2010 12:42:08 +0400 (MSD) X-Yandex-Spam: 0 X-Yandex-Front: web78.yandex.ru X-Yandex-TimeMark: 1284972128 Received: from netman.spbcity.net (netman.spbcity.net [77.244.18.5]) by mail.yandex.ru with HTTP; Mon, 20 Sep 2010 12:42:07 +0400 From: S.N.Grigoriev To: freebsd-stable@freebsd.org In-Reply-To: <4C7D01F7.4010003@zirakzigil.org> References: <4C7D01F7.4010003@zirakzigil.org> MIME-Version: 1.0 Message-Id: <265911284972128@web78.yandex.ru> Date: Mon, 20 Sep 2010 12:42:07 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain Subject: How to terminate a lot of jails correctly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2010 08:57:10 -0000 Hi list, I use a server (FreeBSD 8.1R amd64) with two dozens of jails configured. I've found out that only a few of them are terminated normally (via /etc/rc.shutdown) during the system shutdown. FreeBSD reports that 20sec interval has elapsed and simply kills all the jails that are not yet terminated. I would like to know in what way can I fix it using the system tools only (not ezjail, Qjail etc). Thanks, Serguey. From owner-freebsd-stable@FreeBSD.ORG Mon Sep 20 09:44:27 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 386FB106566C for ; Mon, 20 Sep 2010 09:44:27 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 822BB8FC22 for ; Mon, 20 Sep 2010 09:44:26 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA08545; Mon, 20 Sep 2010 12:44:24 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Oxcv9-000KRN-U8; Mon, 20 Sep 2010 12:44:24 +0300 Message-ID: <4C972CF7.3020601@icyb.net.ua> Date: Mon, 20 Sep 2010 12:44:23 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20100918 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: "S.N.Grigoriev" References: <4C7D01F7.4010003@zirakzigil.org> <265911284972128@web78.yandex.ru> In-Reply-To: <265911284972128@web78.yandex.ru> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=KOI8-U Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: How to terminate a lot of jails correctly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2010 09:44:27 -0000 on 20/09/2010 11:42 S.N.Grigoriev said the following: > > Hi list, > > I use a server (FreeBSD 8.1R amd64) with two dozens of jails configured. > I've found out that only a few of them are terminated normally (via > /etc/rc.shutdown) during the system shutdown. FreeBSD reports that > 20sec interval has elapsed and simply kills all the jails that are not yet > terminated. I would like to know in what way can I fix it using the system > tools only (not ezjail, Qjail etc). Maybe increase that interval? rcshutdown_timeout seems to be it. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Mon Sep 20 09:52:13 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44336106566C for ; Mon, 20 Sep 2010 09:52:13 +0000 (UTC) (envelope-from erik@tefre.com) Received: from mta1-filtered.netlife.no (mail.netlife.no [62.92.26.226]) by mx1.freebsd.org (Postfix) with ESMTP id EF1B28FC14 for ; Mon, 20 Sep 2010 09:52:12 +0000 (UTC) Received: from amavis.netlife.no (amavishost [10.115.1.11]) by mta1-filtered.netlife.no (Postfix) with ESMTP id 1B4B63C7869; Mon, 20 Sep 2010 11:37:03 +0200 (CEST) X-Virus-Scanned: amavisd-new at netlife.no Received: from mta1-submission.netlife.no ([62.92.26.226]) by amavis.netlife.no (amavis.netlife.no [10.115.1.11]) (amavisd-new, port 10026) with ESMTP id gh72LhfHSxTN; Mon, 20 Sep 2010 11:37:02 +0200 (CEST) Received: from baviandesktop.netlife.no (kontor.netlife.no [217.13.28.50]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: erik_pop@netlife.no) by mta1-submission.netlife.no (Postfix) with ESMTPSA id CCE0A3C785D; Mon, 20 Sep 2010 11:37:02 +0200 (CEST) Message-ID: <4C972B3E.2050108@tefre.com> Date: Mon, 20 Sep 2010 11:37:02 +0200 From: Erik Stian Tefre User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.12) Gecko/20100910 Thunderbird/3.0.7 MIME-Version: 1.0 To: "S.N.Grigoriev" References: <4C7D01F7.4010003@zirakzigil.org> <265911284972128@web78.yandex.ru> In-Reply-To: <265911284972128@web78.yandex.ru> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: How to terminate a lot of jails correctly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2010 09:52:13 -0000 > I use a server (FreeBSD 8.1R amd64) with two dozens of jails configured. > I've found out that only a few of them are terminated normally (via > /etc/rc.shutdown) during the system shutdown. FreeBSD reports that > 20sec interval has elapsed and simply kills all the jails that are not yet > terminated. I would like to know in what way can I fix it using the system > tools only (not ezjail, Qjail etc). Increasing rcshutdown_timeout in /etc/rc.conf may help. The default value is set to 30 seconds in /etc/defaults/rc.conf. -- Erik From owner-freebsd-stable@FreeBSD.ORG Mon Sep 20 10:07:41 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9898E1065672 for ; Mon, 20 Sep 2010 10:07:41 +0000 (UTC) (envelope-from serguey-grigoriev@yandex.ru) Received: from forward5.mail.yandex.net (forward5.mail.yandex.net [77.88.46.21]) by mx1.freebsd.org (Postfix) with ESMTP id 4820A8FC1F for ; Mon, 20 Sep 2010 10:07:41 +0000 (UTC) Received: from web78.yandex.ru (web78.yandex.ru [77.88.47.203]) by forward5.mail.yandex.net (Yandex) with ESMTP id 7DE9C14D0D90; Mon, 20 Sep 2010 14:07:39 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1284977259; bh=y+8I4oBjMPP8K7Fh15WBpb7NKskPXTZRb53vVKBliQQ=; h=From:To:Cc:In-Reply-To:References:Subject:MIME-Version:Message-Id: Date:Content-Transfer-Encoding:Content-Type; b=IwphFlQRZTOioPX0JdE8j8m+4zQmzLrMUL/Dp/quZmayRAC8OkjFULzsNfdxtc8am Ld6ZPOIUde26fUERLmKBN2PvWPHsZ/lDIb7y7ExJTNEASRw5s1Qz9AuXN5WDCseOCl 1BaRoMT4gXwMV46Vr9Vt74wrspxUM8Avp2GnVr7Y= Received: from localhost (localhost.localdomain [127.0.0.1]) by web78.yandex.ru (Yandex) with ESMTP id 786A63A0036; Mon, 20 Sep 2010 14:07:39 +0400 (MSD) X-Yandex-Spam: 0 X-Yandex-Front: web78.yandex.ru X-Yandex-TimeMark: 1284977259 Received: from netman.spbcity.net (netman.spbcity.net [77.244.18.5]) by mail.yandex.ru with HTTP; Mon, 20 Sep 2010 14:07:36 +0400 From: S.N.Grigoriev To: Erik Stian Tefre In-Reply-To: <4C972B3E.2050108@tefre.com> References: <4C7D01F7.4010003@zirakzigil.org> <265911284972128@web78.yandex.ru> <4C972B3E.2050108@tefre.com> MIME-Version: 1.0 Message-Id: <14311284977257@web78.yandex.ru> Date: Mon, 20 Sep 2010 14:07:36 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain Cc: freebsd-stable@freebsd.org Subject: Re: How to terminate a lot of jails correctly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2010 10:07:41 -0000 20.09.10, 13:37, "Erik Stian Tefre" : > > I use a server (FreeBSD 8.1R amd64) with two dozens of jails configured. > > I've found out that only a few of them are terminated normally (via > > /etc/rc.shutdown) during the system shutdown. FreeBSD reports that > > 20sec interval has elapsed and simply kills all the jails that are not yet > > terminated. I would like to know in what way can I fix it using the system > > tools only (not ezjail, Qjail etc). > > Increasing rcshutdown_timeout in /etc/rc.conf may help. The default > value is set to 30 seconds in /etc/defaults/rc.conf. > Erik, thank you for your tip. The only drawback of that approche is absence of ability to calculate a timeout. Try and error only. -- Regards, S.Grigoriev. From owner-freebsd-stable@FreeBSD.ORG Mon Sep 20 11:18:04 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14A3E1065679 for ; Mon, 20 Sep 2010 11:18:04 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail36.syd.optusnet.com.au (mail36.syd.optusnet.com.au [211.29.133.76]) by mx1.freebsd.org (Postfix) with ESMTP id 9723D8FC1A for ; Mon, 20 Sep 2010 11:18:03 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c220-239-116-103.belrs4.nsw.optusnet.com.au [220.239.116.103]) by mail36.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id o8KBHv44005529 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Sep 2010 21:17:59 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.4/8.14.4) with ESMTP id o8KBHuc4080757; Mon, 20 Sep 2010 21:17:56 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.4/8.14.4/Submit) id o8KBHt34080756; Mon, 20 Sep 2010 21:17:55 +1000 (EST) (envelope-from peter) Date: Mon, 20 Sep 2010 21:17:55 +1000 From: Peter Jeremy To: Bryce Edwards Message-ID: <20100920111755.GA80432@server.vk2pj.dyndns.org> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7JfCtLOvnd9MIVvH" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable@freebsd.org Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2010 11:18:04 -0000 --7JfCtLOvnd9MIVvH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2010-Sep-18 08:32:32 -0500, Bryce Edwards wrote: >I have a Supermicro with the C7X58 motherboard and an i7 930 cpu, and >it is nowhere near the performance it should be. A buildworld just >took 22.5 hours! That does sound a bit poor. I presume the system was basically unloaded during the buildworld. Can we see the output of: - vmstat -i - zpool status -v - df -k - mount -v - md5 -t [this will help determine if the problem is lack of CPU] - sysctl vm >I have tested the two system drives independently (currently a zfs >mirror), so it is not likely to be an hdd issue. How did you test them and what were the results? Do you know what revision your /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c is? (Or when/how did you last upgrade your source tree). --=20 Peter Jeremy --7JfCtLOvnd9MIVvH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEARECAAYFAkyXQuMACgkQ/opHv/APuIc68QCfa3kA5EDDS7vDI8acojTrUUqI fVcAnRJDZ5NjluTQmkV4+2ch+NWIFpK1 =sv7v -----END PGP SIGNATURE----- --7JfCtLOvnd9MIVvH-- From owner-freebsd-stable@FreeBSD.ORG Mon Sep 20 13:31:05 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A411A10656A3; Mon, 20 Sep 2010 13:31:05 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 5D9F28FC0A; Mon, 20 Sep 2010 13:31:05 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id o8KDV4rP036681; Mon, 20 Sep 2010 09:31:04 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o8KDV4nn036675; Mon, 20 Sep 2010 13:31:04 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Sep 2010 13:31:04 GMT Message-Id: <201009201331.o8KDV4nn036675@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [releng_8_1 tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2010 13:31:05 -0000 TB --- 2010-09-20 13:24:47 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-09-20 13:24:47 - starting RELENG_8_1 tinderbox run for amd64/amd64 TB --- 2010-09-20 13:24:47 - cleaning the object tree TB --- 2010-09-20 13:25:45 - cvsupping the source tree TB --- 2010-09-20 13:25:45 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup5.freebsd.org /tinderbox/RELENG_8_1/amd64/amd64/supfile TB --- 2010-09-20 13:31:04 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2010-09-20 13:31:04 - ERROR: unable to cvsup the source tree TB --- 2010-09-20 13:31:04 - 2.18 user 45.77 system 376.71 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8_1-amd64-amd64.full From owner-freebsd-stable@FreeBSD.ORG Mon Sep 20 14:41:29 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB46B1065670; Mon, 20 Sep 2010 14:41:29 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id A99208FC25; Mon, 20 Sep 2010 14:41:29 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id o8KEfSJ1079062; Mon, 20 Sep 2010 10:41:28 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o8KEfS3g079061; Mon, 20 Sep 2010 14:41:28 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Sep 2010 14:41:28 GMT Message-Id: <201009201441.o8KEfS3g079061@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [releng_8_1 tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2010 14:41:30 -0000 TB --- 2010-09-20 14:35:18 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-09-20 14:35:18 - starting RELENG_8_1 tinderbox run for ia64/ia64 TB --- 2010-09-20 14:35:18 - cleaning the object tree TB --- 2010-09-20 14:36:08 - cvsupping the source tree TB --- 2010-09-20 14:36:08 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup5.freebsd.org /tinderbox/RELENG_8_1/ia64/ia64/supfile TB --- 2010-09-20 14:41:28 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2010-09-20 14:41:28 - ERROR: unable to cvsup the source tree TB --- 2010-09-20 14:41:28 - 1.81 user 35.35 system 369.84 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8_1-ia64-ia64.full From owner-freebsd-stable@FreeBSD.ORG Mon Sep 20 22:34:07 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 801451065672 for ; Mon, 20 Sep 2010 22:34:07 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 308338FC1A for ; Mon, 20 Sep 2010 22:34:07 +0000 (UTC) Received: (qmail 1633 invoked by uid 399); 20 Sep 2010 22:34:06 -0000 Received: from localhost (HELO ?192.168.0.142?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 20 Sep 2010 22:34:06 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C97E15D.7070304@FreeBSD.org> Date: Mon, 20 Sep 2010 15:34:05 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: Mark Kamichoff References: <20100919183721.GA17616@prolixium.com> <20100919185528.GA28845@prolixium.com> In-Reply-To: <20100919185528.GA28845@prolixium.com> X-Enigmail-Version: 1.2a1pre OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: BIND9 built w/--disable-ipv6 on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2010 22:34:07 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 9/19/2010 11:55 AM, Mark Kamichoff wrote: | Well, you can safely ignore this! I realized afterwards that | '--disable-ipv6' just disables the default use of IPv6 in BIND, it | doesn't completely disable the protocol. Turns out I was querying the | wrong address with DIG when testing this, too. listen-on-v6 certainly | works as expected, and enables IPv6 like it should. I'm glad to hear that it worked out for you. | Although, that still does beg the question, No, it doesn't. :) See http://en.wikipedia.org/wiki/Beg_the_question | why don't we want IPv6 enabled by default on new BIND installations? It has to do with whether or not IPv6 support is compiled into the FreeBSD base system which is compiling BIND. If the configure option is set to enable but there is not the proper support in the base, then Bad Things(TM) happen. However, the way that it is set up now if the binaries are running on a system that has IPv6 support then that is detected, and you can use it if you choose. If the binaries are running on a system without IPv6 support, no harm, no foul. hth, Doug - -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (MingW32) iQEcBAEBCAAGBQJMl+FdAAoJEFzGhvEaGryEAxkIAIh6hGy0Anfa4DhE55C4Gd/E J/FV2jpfHuDsc6TNPItwIrojSa2Ql+7EHlAo7xOXEka04ydSfA2UBcWQXIz/+LT0 /4+cRtvKdt6O8tB1LHUg20AZ35/MGU9obnREQB2ZLnb1gTVGLN9ZHhRgDC1H8el3 FlC6rWH4raY63cSzU2m4yDKfBRmmcOuVGmJdN8Au9MGo7XlhtW/A101nb6HAUnCP hySDVsCa2t5vhvZiokFmrlL/OzddeD8QQSusEOMOzlieEIKg/OgrfiOkIm4dYi+r 5QLjS0attGqFEA90FemHJmqeFEa+vBNrTCh1XkB0cD2soB/iNd62fWDi1Bu4CY8= =rHnY -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 09:31:21 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C01081065693 for ; Tue, 21 Sep 2010 09:31:21 +0000 (UTC) (envelope-from bsd@lordcow.org) Received: from lordcow.org (lordcow.org [41.203.5.188]) by mx1.freebsd.org (Postfix) with ESMTP id BB0848FC12 for ; Tue, 21 Sep 2010 09:31:20 +0000 (UTC) Received: from lordcow.org (localhost [127.0.0.1]) by lordcow.org (8.14.4/8.14.4) with ESMTP id o8L9VBax095926 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Tue, 21 Sep 2010 11:31:11 +0200 (SAST) (envelope-from lordcow@lordcow.org) Received: (from lordcow@localhost) by lordcow.org (8.14.4/8.14.4/Submit) id o8L9V64E095921 for stable@freebsd.org; Tue, 21 Sep 2010 11:31:06 +0200 (SAST) (envelope-from lordcow) Date: Tue, 21 Sep 2010 11:31:06 +0200 From: Gareth de Vaux To: stable@freebsd.org Message-ID: <20100921093106.GA95379@lordcow.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on lordcow.org Cc: Subject: source tree out of sync X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 09:31:21 -0000 Hi all, in for example http://security.freebsd.org/advisories/FreeBSD-SA-10:08.bzip2.asc : # cd /usr/src # patch < /path/to/patch # cd /usr/src/lib/libbz2 # make obj && make depend && make && make install I assume I can't do this safely if my /usr/src tree has been updated since my last make world? From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 10:24:55 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 894A710656A8 for ; Tue, 21 Sep 2010 10:24:55 +0000 (UTC) (envelope-from bounce-3e4e9efc-2efd-4daa-9e82-aff73c82869d@bounce.gateway3.touchbasepro.com) Received: from gateway3.touchbasepro.com (gateway3.touchbasepro.com [72.3.177.36]) by mx1.freebsd.org (Postfix) with ESMTP id EFA418FC1A for ; Tue, 21 Sep 2010 10:24:54 +0000 (UTC) Precedence: bulk MIME-Version: 1.0 To: X-Complaints-To: abuse@touchbasepro.com Date: Tue, 21 Sep 2010 11:24:43 +0200 From: Brain Power Content-Return: prohibition X400-Content-Return: prohibition Message-ID: 3e4e9efc-2efd-4daa-9e82-aff73c82869d Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: Quoted-Printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: The Awesome Power of your Brain X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Reply-To: rania@brainpower.co.za List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 10:24:55 -0000 Untitled Document =0D=0ACan creative proble= m solving abilities be increased?=0D=0A Can talent and mental focus be su= mmoned at will?=0D=0A Can intellectual ability be expanded?=0D=0A Can som= ething be done to release the natural genius residing within each one of = us?The Human Brain is Infinitely Powerful, yet research tells us that we = are using a very small percentage of our brain=2E Why is that? Join accla= imed international speaker and accredited brain power expert, Mark Jansen= , in an inspiring, life-changing one-day seminar that will show you how t= o harness the awesome potential of your brain to ? =0D=0A Tap into your = natural genius Optimize your creative problem-solving skills Think quicke= r and think better under pressure Learn to focus at will Improve your int= ellectual capacity Enhance your emotional intelligence Learn to relax pro= perly Learn to defuse conflict Be more productive Reach higher levels of = success in every area of your life=2E ?Probably the training session wh= ich has, and will have, =0D=0A the most significant impact on my professi= onal and personal life=2E? ? Brian Makundi, PTA Bank?Goes into all life= areas and has the potential to change the world=2E? ? Grant Phillips, = Kolosus Holdngs?All I can say is WOW! Honestly, I have always known that = I had great potential but never knew how to unleash it =2E=2E=2E Now I do= !? ? Ennocentia Phore, South African Bank Note CompanyWhether you?re the = CEO, the employee, the manager or a home executive ? Brain Power will hel= p you get the best out of your most valuable asset: your brain=2EThrough = a host of practical techniques and numerous case studies of human beings = living powerful lives, you will begin to understand how to utilize this c= omplex mechanism to your advantage=2E?A thought provoking and highly stim= ulating workshop=2E=0D=0A An absolute must for everyone who wishes to liv= e an overall more meaningful and balanced life ? and should wish to rise = above the ordinary,=0D=0A You are provided with the tools to help you mak= e it happen=2E=0D=0A Dynamically presented in a way which is clear and ea= sily understood,=0D=0A By a true and dedicated student of the human brain= =2E"? Derick Stevens, Director, Bernina RSA?To capture and hold ever= yone?s attention from 8h00 to 17h00 speaks volumes about the competency a= nd charisma of the presenter=2E?? Michael Barber, Escor LtdCompanies that= have benefited from the Brain Power Seminar:=0D=0A Afrox ABSA ADT Afgri= Trading Alexander Forbes AngloGold Ashanti Bidvest Bank BMW SA (Pty) Ltd= BHP-Billiton Bernina RSA (Pty) Ltd CSIR De Beers Dimension Data Discover= y Health EMC Computers First National Bank Mercantile Bank McDonalds SA M= utual & Federal Multichoice Nedbank Nissan Rand Water Standard Bank SA Ba= nk Note Co=2E SA Reserve Bank SASOL SABS SARS Spoornet The Presidency Tra= nsnet Telkom UNISA University of Pretoria Water Research Com=2E Werksmans= Attorneys Zenith Bank, Nigeria =0D=0AAbout the author=0D=0A = and facilitatorMark Jansen has been studying this fascinating topic since= 1996=2E His seminars convert knowledge about the brain into potent busin= ess tools ? providing a bridge between logic and magic, heightening creat= ive thinking, allowing ordinary people to discover extraordinary powers t= o optimize their performance in business and in life=2EGive yourself, you= r staff and your loved ones the gift of this liberating information=2E Bo= ok to attend one of the following seminars:=0D=0A 2010 Dates Venue = 14 Oct Palazzo Hotel, Montecasino, Fourways, JHB 21 Oct Palazzo Hotel, = Montecasino, Fourways, JHB 2 Nov The Peninsula, Cape Town 11 Nov Pal= azzo Hotel, Montecasino, Fourways, JHB 25 Nov Palazzo Hotel, Montecasin= o, Fourways, JHB 2 Dec Palazzo Hotel, Montecasino, Fourways, JHB Tim= e: 8AM ? 5PM Price: R 2 500 (Excluding VAT) per person=2E =0D=0ASa= ve up to 25%When you book corporate or group workshop for 10 or more dele= gates on your premises!=0D=0A Includes:=0D=0A A comprehensive 90-page, A= 4, colour manual=2E An audio CD and reminder cards=2E DVD with video clip= s shown on the day=2E A certificate of completion=2E Executive lunch, tea= , coffee and snacks on arrival and at teatimes=2E =0D=0A?? Immensely po= werful, professionally enhancing ??? Tigere Muzenda, PTA Bank?Powerful=2E= Profound=2E Everybody should do this!=0D=0A I was particularly amazed at= how comfortably (and fittingly) love is talked about in a corporate sett= ing=2E Very special=2E=0D=0A Thank you so much for a really superb day a= nd incredibly valuable information=0D=0A which you so ?care-fully? compil= ed and presented=2E?? Theresa Muller, CEO, ZA Group?Excellent course, pre= sented with commitment and passion=2E=0D=0A The material supplied is some= thing I can revisit frequently=2E?? Lily Wessels, Standard Bank=2EBook he= re ( http://www=2Ebrainpower=2Eco=2Eza/booking=2Ephp ) NOW=0D=0A Or call = Deidre at 011 465 5788 or write to her at deidre@brainpower=2Eco=2Eza ( m= ailto:deidre@brainpower=2Eco=2Eza )=0D=0A You will discover a life of ins= pired creativity, optimal productivity and emotional stability=2EBooking = Code : BC 547Brain Power Peak Performance TrainingTel: +27 11 465 5788 | = Cell: 082 411 7281 | Fax: +27 11 4655306=0D=0A Email: info@brainpower=2Ec= o=2Eza ( mailto:info@brainpower=2Eco=2Eza ) | P O Box 71919, Bryanston, 2= 021, South AfricaCopyright Brain Power © 2010 | Privacy Policy ( htt= p://www=2Ebrainpower=2Eco=2Eza/privacy=2Ephp ) Click here to Unsubscribe = Click here to send to a friend Click here to subscribe to this mailing = Click here to report abuse =0D=0A =0D=0A=0D=0AClick on the link belo= w to unsubscribe yourself=2E=0D=0AClick here to unsubscribe:=0D=0Ahttp://= www=2Etracker1=2Eco=2Eza/Unsubscribe/761def82-b248-49b9-b1fe-4cfe5a903d00= /73244053-8795-4265-919c-f680e245c0c4=2Ehtm From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 10:38:41 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 423861065670 for ; Tue, 21 Sep 2010 10:38:41 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id B728C8FC23 for ; Tue, 21 Sep 2010 10:38:40 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Oy0FC-0000LE-U8 for freebsd-stable@freebsd.org; Tue, 21 Sep 2010 12:38:38 +0200 Received: from nuclight.avtf.net ([217.29.94.29]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Sep 2010 12:38:38 +0200 Received: from vadim_nuclight by nuclight.avtf.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Sep 2010 12:38:38 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Vadim Goncharov Date: Tue, 21 Sep 2010 10:38:29 +0000 (UTC) Organization: Nuclear Lightning @ Tomsk, TPU AVTF Hostel Lines: 30 Message-ID: References: <20100908073019.GA16493@lonesome.com> <4C89107A.6050802@DataIX.net> <4C93CF16.9080607@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: nuclight.avtf.net X-Comment-To: Doug Barton User-Agent: slrn/0.9.9p1 (FreeBSD) Subject: Re: Policy for removing working code X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vadim_nuclight@mail.ru List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 10:38:41 -0000 Hi Doug Barton! On Fri, 17 Sep 2010 13:27:02 -0700; Doug Barton wrote about 'Re: Policy for removing working code': >> You either not understanding that this situation is about entire project (not >> ISDN, but policy) > I think at this point that you've made your concerns clear. What you > don't seem to be understanding is: > 1) The policy is, and always has been, those who are interested in > keeping code alive work on it. > 2) No one was interested (by the definition above) in keeping the ISDN > code alive. Not quite. There are those who are interested in keeping code alive but can't work on it, i.e., users, not programmers. But they, if notified, could convince another people, programmers, to do the work (such events of volunteer calls are not often), e.g., hire someone. But announcements, may be, should be more clear about this, for the case such people wouldn't _guess_ such possibility exists. BSD tries to be more business-freindly, ain't it? :) > Now you have raised a valid point on how we can do the "volunteers > needed" notifications better in the future, and I think that those will > be taken to heart, and acted on the next time we face this situation. Indeed. Thanks for understanding. -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 11:39:57 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC2421065673; Tue, 21 Sep 2010 11:39:57 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id D067E8FC1D; Tue, 21 Sep 2010 11:39:56 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA04173; Tue, 21 Sep 2010 14:39:54 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4C989989.4050408@icyb.net.ua> Date: Tue, 21 Sep 2010 14:39:53 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20100909 Lightning/1.0b2 Thunderbird/3.1.3 MIME-Version: 1.0 To: vadim_nuclight@mail.ru References: <201009011653.o81Grkm4056064@fire.js.berklix.net> <201009011902.06538.hselasky@c2i.net> <4C8627A6.1090308@icyb.net.ua> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-security@freebsd.org, freebsd-stable@freebsd.org Subject: Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 11:39:57 -0000 > The Project is ultimately about the users, right? There are early signs that > some old FreeBSD users get tired from those changes, those removals, lesser > POLA adherence, marketing-not-technical-stuff for time-not-feature-based > releases, not so stable -STABLE as it used to be, and so on, migrating to > other systems. And older users are more valuable to project than newer ones. > May be it's time to revert to some of thet Old Good Things, if decade-long > project is mostly ended, while those signs are still early and not a strong > tendency?.. Given this thread, I've mentioned earlier about 12 messages in > announce@ from 2002 with such public calls for volunteers - there are several > years already without these. Hmm, it's really simple. If you want to shape the future of the project, then participate in the places where the future is shaped. If you want to know what's coming up in the future, then watch the places where the future is shaped. If you don't do either, you get what you get. Complaining post factum just doesn't work. (Numerous other examples and projects also demonstrate that). "Current", "stable" are not some alien versions of FreeBSD for some other strange people to use. Those are your future releases. Not looking into the future has its benefits - you are not doing anything; but it has costs too - you don't know your future. Looking into the future and shaping it has obvious costs, but the benefits are clear too. Business users and old FreeBSD users should know this best of all. It's strange that you try speak on their behalf but do not seem to realize these simple things. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 11:43:02 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D6AD1065673; Tue, 21 Sep 2010 11:43:02 +0000 (UTC) (envelope-from prox@prolixium.com) Received: from nox.prolixium.com (nox.prolixium.com [IPv6:2001:48c8:1:104::1e]) by mx1.freebsd.org (Postfix) with ESMTP id 47E958FC0C; Tue, 21 Sep 2010 11:43:02 +0000 (UTC) Received: from prox by nox.prolixium.com with local (Exim 4.72) (envelope-from ) id 1Oy1FU-00080a-6U; Tue, 21 Sep 2010 07:43:00 -0400 Date: Tue, 21 Sep 2010 07:43:00 -0400 From: Mark Kamichoff To: Doug Barton Message-ID: <20100921114300.GB16298@prolixium.com> References: <20100919183721.GA17616@prolixium.com> <20100919185528.GA28845@prolixium.com> <4C97E15D.7070304@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J2SCkAp4GZ/dPZZf" Content-Disposition: inline In-Reply-To: <4C97E15D.7070304@FreeBSD.org> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: prox@prolixium.com X-SA-Exim-Scanned: No (on nox.prolixium.com); SAEximRunCond expanded to false Cc: freebsd-stable@freebsd.org Subject: Re: BIND9 built w/--disable-ipv6 on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 11:43:02 -0000 --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 20, 2010 at 03:34:05PM -0700, Doug Barton wrote: > | Although, that still does beg the question, >=20 > No, it doesn't. :) See http://en.wikipedia.org/wiki/Beg_the_question http://en.wikipedia.org/wiki/Beg_the_question#Modern_usage > | why don't we want IPv6 enabled by default on new BIND installations? >=20 > It has to do with whether or not IPv6 support is compiled into the > FreeBSD base system which is compiling BIND. If the configure option > is set to enable but there is not the proper support in the base, then > Bad Things(TM) happen. However, the way that it is set up now if the > binaries are running on a system that has IPv6 support then that is > detected, and you can use it if you choose. If the binaries are > running on a system without IPv6 support, no harm, no foul. I see, that makes sense. However, as IPv6 becomes more widely used (perhaps quite far in the future, when folks are turning /off/ IPv4), it might need revisiting. - Mark --=20 Mark Kamichoff prox@prolixium.com http://www.prolixium.com/ --J2SCkAp4GZ/dPZZf Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkyYmkQACgkQ0TYC9KtF8BOhGQCdGU60cWaLhr3NkoO4I7pt9nBv Z24AoI2pnSKtoQahlTj6XnHA30y8Wjew =5SW0 -----END PGP SIGNATURE----- --J2SCkAp4GZ/dPZZf-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 12:08:08 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C223106566C for ; Tue, 21 Sep 2010 12:08:08 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id A05718FC22 for ; Tue, 21 Sep 2010 12:08:07 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Oy1dm-0001Mu-Of for freebsd-stable@freebsd.org; Tue, 21 Sep 2010 14:08:06 +0200 Received: from nuclight.avtf.net ([217.29.94.29]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Sep 2010 14:08:06 +0200 Received: from vadim_nuclight by nuclight.avtf.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Sep 2010 14:08:06 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Vadim Goncharov Date: Tue, 21 Sep 2010 12:07:57 +0000 (UTC) Organization: Nuclear Lightning @ Tomsk, TPU AVTF Hostel Lines: 66 Message-ID: References: <20100908073019.GA16493@lonesome.com> <4C89107A.6050802@DataIX.net> <4C935A92.7010204@icyb.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: nuclight.avtf.net X-Comment-To: Andriy Gapon User-Agent: slrn/0.9.9p1 (FreeBSD) Subject: Re: Policy for removing working code X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vadim_nuclight@mail.ru List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 12:08:08 -0000 Hi Andriy Gapon! On Fri, 17 Sep 2010 15:09:54 +0300; Andriy Gapon wrote about 'Re: Policy for removing working code': >> You either not understanding that this situation is about entire project (not >> ISDN, but policy) or assert that users just running FreeBSD should not care >> about the way things happen, which is wrong. And thus your "stop provoking" >> sounds like ostrich policy, which is even worse. > You either don't understand the situation or are a troll. > People who actively participate(d) in the project/community were very well aware > of the issue. Following the generalized principle of locality it was not expected > that much help would come from people who didn't already sufficiently participate. > This much belated and non-productive thread is a perfect demonstration. No, that is you who actively refuse to understand the main point, while several other people on this list already agreed with me. I've given arguments, valid arguments, but you din't answer them, repeating the same statement reworded. Moreover, you were wrong several times, e.g. at requirement for all users to read stable, while I've found that handbook/eresources.html agrees with me: === freebsd-announce Important events / milestones This is the mailing list for people interested only in occasional announcements of significant FreeBSD events. This includes announcements about snapshots and other releases. It contains announcements of new FreeBSD capabilities. It may contain calls for volunteers etc. This is a low volume, strictly moderated mailing list. === And Project actually did the things as documented, I've counted and wrote in another message 12 such letters in announce@ from 2002, then things stopped to go this way. Why you ignored this argument just as I didn't say anything? After all, your impolite accusements of non-productiveness and trolling. Should I answer the same way and say something about your self-conceit? I'll not come down to this but rather quote committers-guide: === Do not impugn the intentions of someone you disagree with. If they see a different solution to a problem than you, or even a different problem, it is not because they are stupid, because they have questionable parentage, or because they are trying to destroy your hard work, personal image, or FreeBSD, but simply because they have a different outlook on the world. Different is good. Disagree honestly. Argue your position from its merits, be honest about any shortcomings it may have, and be open to seeing their solution, or even their vision of the problem, with an open mind. Accept correction. We are all fallible. When you have made a mistake, apologize and get on with life. Do not beat up yourself, and certainly do not beat up others for your mistake. Do not waste time on embarrassment or recrimination, just fix the problem and move on. Ask for help. Seek out (and give) peer reviews. One of the ways open source software is supposed to excel is in the number of eyeballs applied to it; this does not apply if nobody will review code. === -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 12:36:22 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F3CB106564A for ; Tue, 21 Sep 2010 12:36:22 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id C9E148FC17 for ; Tue, 21 Sep 2010 12:36:21 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Oy253-0005hl-0M for freebsd-stable@freebsd.org; Tue, 21 Sep 2010 14:36:17 +0200 Received: from nuclight.avtf.net ([217.29.94.29]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Sep 2010 14:36:16 +0200 Received: from vadim_nuclight by nuclight.avtf.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Sep 2010 14:36:16 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Vadim Goncharov Date: Tue, 21 Sep 2010 12:36:04 +0000 (UTC) Organization: Nuclear Lightning @ Tomsk, TPU AVTF Hostel Lines: 59 Message-ID: References: <201009011653.o81Grkm4056064@fire.js.berklix.net> <201009011902.06538.hselasky@c2i.net> <4C8627A6.1090308@icyb.net.ua> <4C989989.4050408@icyb.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: nuclight.avtf.net X-Comment-To: Andriy Gapon User-Agent: slrn/0.9.9p1 (FreeBSD) Subject: Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vadim_nuclight@mail.ru List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 12:36:22 -0000 Hi Andriy Gapon! On Tue, 21 Sep 2010 14:39:53 +0300; Andriy Gapon wrote about 'Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon': >> The Project is ultimately about the users, right? There are early signs that >> some old FreeBSD users get tired from those changes, those removals, lesser >> POLA adherence, marketing-not-technical-stuff for time-not-feature-based >> releases, not so stable -STABLE as it used to be, and so on, migrating to >> other systems. And older users are more valuable to project than newer ones. >> May be it's time to revert to some of thet Old Good Things, if decade-long >> project is mostly ended, while those signs are still early and not a strong >> tendency?.. Given this thread, I've mentioned earlier about 12 messages in >> announce@ from 2002 with such public calls for volunteers - there are several >> years already without these. > Hmm, it's really simple. > If you want to shape the future of the project, then participate in the places > where the future is shaped. If you want to know what's coming up in the future, > then watch the places where the future is shaped. If you don't do either, you get > what you get. Complaining post factum just doesn't work. (Numerous other > examples and projects also demonstrate that). > "Current", "stable" are not some alien versions of FreeBSD for some other strange > people to use. > Those are your future releases. > Not looking into the future has its benefits - you are not doing anything; but it > has costs too - you don't know your future. > Looking into the future and shaping it has obvious costs, but the benefits are > clear too. > Business users and old FreeBSD users should know this best of all. > It's strange that you try speak on their behalf but do not seem to realize these > simple things. The essence of your words and your position in other letters is: "We are an open source project exactly the same kind like many others: we have no [moral] responsibility to our users, we are selfish and want only your code; give us your code and you will have the right to freedom of speech, otherwise you're an untermensch". But FreeBSD Project tries, to the extent possible (of course, volunteers are not paid), be different from those, and provides all those branches, lists, etc. for different people. Business users and old FreeBSD users value FreeBSD for this, and they know that it is official position and documented, e.g.: 12.1 Statement of General Intent The FreeBSD Project targets "production quality commercial off-the-shelf (COTS) workstation, server, and high-end embedded systems". And what they are complaining post factum is that things go _other way than declared_. And they are begin to go the way as you assertions above, which clearly contradicts FreeBSD's official declared goals. Yes, still that an open-source project, there are no liability, etc., etc. But my criticism earlier in the thread was not unconstructive - I've suggested one of the possible ways for those who cannot help us directly by code. Don't reject them just on this criteria (and Project never did before). -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 12:47:44 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 471FD1065670 for ; Tue, 21 Sep 2010 12:47:44 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id BE45C8FC14 for ; Tue, 21 Sep 2010 12:47:43 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Oy2G6-0002g3-Bk for freebsd-stable@freebsd.org; Tue, 21 Sep 2010 14:47:42 +0200 Received: from nuclight.avtf.net ([217.29.94.29]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Sep 2010 14:47:42 +0200 Received: from vadim_nuclight by nuclight.avtf.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Sep 2010 14:47:42 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Vadim Goncharov Date: Tue, 21 Sep 2010 12:47:30 +0000 (UTC) Organization: Nuclear Lightning @ Tomsk, TPU AVTF Hostel Lines: 38 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: nuclight.avtf.net X-Comment-To: Jon Otterholm User-Agent: slrn/0.9.9p1 (FreeBSD) Subject: Re: Dummynet X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vadim_nuclight@mail.ru List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 12:47:44 -0000 Hi Jon Otterholm! On Mon, 20 Sep 2010 10:00:48 +0200; Jon Otterholm wrote about 'Dummynet': > Installed a new router running 8-stable and encounter some problems when > configuring dummynet pipes: > When setting buckets above 1024... > ipfw pipe 91 config bw 100Mbit/s mask src-ip 0xffffffff buckets 4096 > ...I get the following error: > Clamp sched buckets to 1024 (was 4096) Try to write "buckets 4096" before "mask", though this is unlikely to help, there are some troubles with 8.1's changes in parser. > # sysctl net.inet.ip.dummynet.hash_size > net.inet.ip.dummynet.hash_size: 4096 Also, make sure you're doing this before any packets actually went to dummynet (e.g. just after reboot). > from man ipfw: > buckets hash-table-size > Specifies the size of the hash table used for storing the > various > queues. Default value is 64 controlled by the sysctl(8) > variable > net.inet.ip.dummynet.hash_size, allowed range is 16 to 65536. > Am I missing something here? This worked fine in the 7-branch. The reason is that luigi@ merged ipfw3 from -CURRENT between 8.0R and 8.1R. There are many new features and, as seen from many PRs, many new bugs. -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 12:53:59 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1E23106564A for ; Tue, 21 Sep 2010 12:53:59 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1190A8FC08 for ; Tue, 21 Sep 2010 12:53:58 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA05983; Tue, 21 Sep 2010 15:53:56 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4C98AAE4.9090105@icyb.net.ua> Date: Tue, 21 Sep 2010 15:53:56 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20100909 Lightning/1.0b2 Thunderbird/3.1.3 MIME-Version: 1.0 To: vadim_nuclight@mail.ru References: <201009011653.o81Grkm4056064@fire.js.berklix.net> <201009011902.06538.hselasky@c2i.net> <4C8627A6.1090308@icyb.net.ua> <4C989989.4050408@icyb.net.ua> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 12:53:59 -0000 on 21/09/2010 15:36 Vadim Goncharov said the following: > Hi Andriy Gapon! > > On Tue, 21 Sep 2010 14:39:53 +0300; Andriy Gapon wrote about 'Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon': > >>> The Project is ultimately about the users, right? There are early signs that >>> some old FreeBSD users get tired from those changes, those removals, lesser >>> POLA adherence, marketing-not-technical-stuff for time-not-feature-based >>> releases, not so stable -STABLE as it used to be, and so on, migrating to >>> other systems. And older users are more valuable to project than newer ones. >>> May be it's time to revert to some of thet Old Good Things, if decade-long >>> project is mostly ended, while those signs are still early and not a strong >>> tendency?.. Given this thread, I've mentioned earlier about 12 messages in >>> announce@ from 2002 with such public calls for volunteers - there are several >>> years already without these. >> Hmm, it's really simple. >> If you want to shape the future of the project, then participate in the places >> where the future is shaped. If you want to know what's coming up in the future, >> then watch the places where the future is shaped. If you don't do either, you get >> what you get. Complaining post factum just doesn't work. (Numerous other >> examples and projects also demonstrate that). >> "Current", "stable" are not some alien versions of FreeBSD for some other strange >> people to use. >> Those are your future releases. >> Not looking into the future has its benefits - you are not doing anything; but it >> has costs too - you don't know your future. >> Looking into the future and shaping it has obvious costs, but the benefits are >> clear too. >> Business users and old FreeBSD users should know this best of all. >> It's strange that you try speak on their behalf but do not seem to realize these >> simple things. > > The essence of your words and your position in other letters is: > > "We are an open source project exactly the same kind like many others: > we have no [moral] responsibility to our users, we are selfish and want only > your code; give us your code and you will have the right to freedom of speech, > otherwise you're an untermensch". Please don't put your words into my mouth. I've said what I've said. Your interpretations do not interest me. Have a good life. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 12:59:53 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 557221065670; Tue, 21 Sep 2010 12:59:53 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (mail.ip6.digiware.nl [IPv6:2001:4cb8:1:106::2]) by mx1.freebsd.org (Postfix) with ESMTP id DA7198FC1A; Tue, 21 Sep 2010 12:59:52 +0000 (UTC) Received: from localhost (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id DDC97153434; Tue, 21 Sep 2010 14:59:51 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by localhost (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pa6OhOkhSsTw; Tue, 21 Sep 2010 14:59:48 +0200 (CEST) Received: from [127.0.0.1] (opteron [192.168.10.67]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.digiware.nl (Postfix) with ESMTPSA id 78DA7153433; Tue, 21 Sep 2010 14:59:48 +0200 (CEST) Message-ID: <4C98AC42.1040104@digiware.nl> Date: Tue, 21 Sep 2010 14:59:46 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: Andriy Gapon References: <201009011653.o81Grkm4056064@fire.js.berklix.net> <201009011902.06538.hselasky@c2i.net> <4C8627A6.1090308@icyb.net.ua> <4C989989.4050408@icyb.net.ua> In-Reply-To: <4C989989.4050408@icyb.net.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: vadim_nuclight@mail.ru, freebsd-security@freebsd.org, freebsd-stable@freebsd.org Subject: Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 12:59:53 -0000 On 2010-09-21 13:39, Andriy Gapon wrote: >> The Project is ultimately about the users, right? There are early signs that >> some old FreeBSD users get tired from those changes, those removals, lesser >> POLA adherence, marketing-not-technical-stuff for time-not-feature-based >> releases, not so stable -STABLE as it used to be, and so on, migrating to >> other systems. And older users are more valuable to project than newer ones. >> May be it's time to revert to some of thet Old Good Things, if decade-long >> project is mostly ended, while those signs are still early and not a strong >> tendency?.. Given this thread, I've mentioned earlier about 12 messages in >> announce@ from 2002 with such public calls for volunteers - there are several >> years already without these. Well, let me pitch in here a bit, because this discussion has had me on the edge of commenting already for too long. I'm a FreeBSD user as early as 1993, still have the first 1.0 CD here as nice remembrance. So I guess that I qualify as one of those "old FreeBSD" users. And I completely disagree with you. If you have been such an old freebsd user,then you should know the immense effort there has been to move GIANT out of the way. I cann't even get close to describing what a huge respect I have for the people that dared to undertake such a humongous effort. With an high probability of being flamed to death... But still ever since 5.x I've seen things really improve for the better. And yes, I was sorry to see ISDN being removed, but as things have progressed another version has been returned instead. And sure I have more hardware than you can imagine that is no longer supported. But it is all old, and worn down, sometimes it is even still VESA stuff. And right,there have been variations in the level of what you would like to call stable. But compared to the "old days" I would say, it has always been above my expectation. And note that I have and still do run 24*7 business on this. FreeBSD has never NEVER ever let me down. So as far as I'm concerned you are barking up the wrong tree here. --WjW From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 13:02:32 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F5A610656AA; Tue, 21 Sep 2010 13:02:32 +0000 (UTC) (envelope-from unixmania@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id E66F68FC0C; Tue, 21 Sep 2010 13:02:31 +0000 (UTC) Received: by qyk31 with SMTP id 31so4149937qyk.13 for ; Tue, 21 Sep 2010 06:02:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=tC/5dZBohCSOZms6lQt65KLeRH+Nwu2S6XiWhpaczrk=; b=KiNtz/q3mpQfC0hWA5/KcYrATguFBSLhV42y98spjWkW/t26RdMGR48pvcFeic597W 86iogk1GWCoHXZ8xozuvGaqsgsRXoM2jETXxFJX+1J4tzK7kBZLxXYLWWdZ6F2AgFYuF /BSpvgBBfoTD+VbWwBixRC6gbvgLATofRhXzU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=NQ3D0zn/Gqvg76BEM+1NJwwG2abKVXkOyuqvqOHhhZfn9wSbTXUsEMTdbgGHfm+9bw +ppJ4lEZQ3TQAq0p0ewynUJUxjJdEvFfAksZ+oGTRsv/0R/HRnNG7NVj6UvKBijBwSdN 8lfa7SyjW1mrN3xW8LjftR8FI2kijHzcxhMA4= MIME-Version: 1.0 Received: by 10.229.96.16 with SMTP id f16mr7123124qcn.255.1285072797132; Tue, 21 Sep 2010 05:39:57 -0700 (PDT) Received: by 10.229.31.194 with HTTP; Tue, 21 Sep 2010 05:39:56 -0700 (PDT) In-Reply-To: <4C989989.4050408@icyb.net.ua> References: <201009011653.o81Grkm4056064@fire.js.berklix.net> <201009011902.06538.hselasky@c2i.net> <4C8627A6.1090308@icyb.net.ua> <4C989989.4050408@icyb.net.ua> Date: Tue, 21 Sep 2010 09:39:56 -0300 Message-ID: From: "Carlos A. M. dos Santos" To: freebsd-security@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 13:02:32 -0000 On Tue, Sep 21, 2010 at 8:39 AM, Andriy Gapon wrote: [...] > If you want to shape the future of the project, then participate in the p= laces > where the future is shaped. =A0If you want to know what's coming up in th= e future, > then watch the places where the future is shaped. =A0If you don't do eith= er, you get > what you get. =A0Complaining post factum just doesn't work. =A0(Numerous = other > examples and projects also demonstrate that). Stop feeding the troll, please. From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 13:16:12 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71BC310656A3 for ; Tue, 21 Sep 2010 13:16:12 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta15.emeryville.ca.mail.comcast.net (qmta15.emeryville.ca.mail.comcast.net [76.96.27.228]) by mx1.freebsd.org (Postfix) with ESMTP id 512AD8FC08 for ; Tue, 21 Sep 2010 13:16:12 +0000 (UTC) Received: from omta21.emeryville.ca.mail.comcast.net ([76.96.30.88]) by qmta15.emeryville.ca.mail.comcast.net with comcast id 9QUU1f0021u4NiLAFRGBkW; Tue, 21 Sep 2010 13:16:11 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta21.emeryville.ca.mail.comcast.net with comcast id 9RGA1f00D3LrwQ28hRGAsv; Tue, 21 Sep 2010 13:16:11 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 739BC9B427; Tue, 21 Sep 2010 06:16:10 -0700 (PDT) Date: Tue, 21 Sep 2010 06:16:10 -0700 From: Jeremy Chadwick To: Willem Jan Withagen Message-ID: <20100921131610.GA58719@icarus.home.lan> References: <201009011653.o81Grkm4056064@fire.js.berklix.net> <201009011902.06538.hselasky@c2i.net> <4C8627A6.1090308@icyb.net.ua> <4C989989.4050408@icyb.net.ua> <4C98AC42.1040104@digiware.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C98AC42.1040104@digiware.nl> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: vadim_nuclight@mail.ru, freebsd-security@freebsd.org, freebsd-stable@freebsd.org, Andriy Gapon Subject: Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 13:16:12 -0000 On Tue, Sep 21, 2010 at 02:59:46PM +0200, Willem Jan Withagen wrote: > On 2010-09-21 13:39, {some mysterious person :-)} wrote: > >>The Project is ultimately about the users, right? There are early signs that > >>some old FreeBSD users get tired from those changes, those removals, lesser > >>POLA adherence, marketing-not-technical-stuff for time-not-feature-based > >>releases, not so stable -STABLE as it used to be, and so on, migrating to > >>other systems. And older users are more valuable to project than newer ones. > >>May be it's time to revert to some of thet Old Good Things, if decade-long > >>project is mostly ended, while those signs are still early and not a strong > >>tendency?.. Given this thread, I've mentioned earlier about 12 messages in > >>announce@ from 2002 with such public calls for volunteers - there are several > >>years already without these. Andriy wasn't the one who wrote this. In fact, I'm not sure who the quote actually came from because I never received the Email it came from, but I'm under the impression it's from Vadim. My mail spool: $ grep "Old Good Things" Mail/freebsd/freebsd-stable > May be it's time to revert to some of thet Old Good Things, if decade-long >> May be it's time to revert to some of thet Old Good Things, if decade-long >>> May be it's time to revert to some of thet Old Good Things, if decade-long >> May be it's time to revert to some of thet Old Good Things, if decade-long The first mention of it was in an Email from Andriy, sent to Vadim, with Andriy quoting someone words (the first paragraph shown above). Strangely I can't find the mail on the official FreeBSD pipermail lists either. I'm staying out of the main discussion, but I'm just wanting to point out that Andriy did not write the above quote. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 13:46:11 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84BF1106566C for ; Tue, 21 Sep 2010 13:46:11 +0000 (UTC) (envelope-from bsd@lordcow.org) Received: from lordcow.org (lordcow.org [41.203.5.188]) by mx1.freebsd.org (Postfix) with ESMTP id 7B3FC8FC1C for ; Tue, 21 Sep 2010 13:46:09 +0000 (UTC) Received: from lordcow.org (localhost [127.0.0.1]) by lordcow.org (8.14.4/8.14.4) with ESMTP id o8LDk1fJ010984 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Tue, 21 Sep 2010 15:46:01 +0200 (SAST) (envelope-from lordcow@lordcow.org) Received: (from lordcow@localhost) by lordcow.org (8.14.4/8.14.4/Submit) id o8LDjuTs010978 for stable@freebsd.org; Tue, 21 Sep 2010 15:45:56 +0200 (SAST) (envelope-from lordcow) Date: Tue, 21 Sep 2010 15:45:54 +0200 From: Gareth de Vaux To: stable@freebsd.org Message-ID: <20100921134554.GA10927@lordcow.org> References: <20100921093106.GA95379@lordcow.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100921093106.GA95379@lordcow.org> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on lordcow.org Cc: Subject: Re: source tree out of sync X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 13:46:11 -0000 On Tue 2010-09-21 (11:31), Gareth de Vaux wrote: > I assume I can't do this safely if my /usr/src tree has been updated > since my last make world? Well, doesn't look like it's an issue for me in this instance. From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 13:49:34 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E930106564A; Tue, 21 Sep 2010 13:49:34 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (mail.ip6.digiware.nl [IPv6:2001:4cb8:1:106::2]) by mx1.freebsd.org (Postfix) with ESMTP id 154058FC08; Tue, 21 Sep 2010 13:49:33 +0000 (UTC) Received: from localhost (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id E89B0153434; Tue, 21 Sep 2010 15:49:32 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by localhost (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SHqVM2wMfVfD; Tue, 21 Sep 2010 15:49:29 +0200 (CEST) Received: from [127.0.0.1] (opteron [192.168.10.67]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.digiware.nl (Postfix) with ESMTPSA id 42FFC153433; Tue, 21 Sep 2010 15:49:29 +0200 (CEST) Message-ID: <4C98B7E7.1020403@digiware.nl> Date: Tue, 21 Sep 2010 15:49:27 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: Jeremy Chadwick References: <201009011653.o81Grkm4056064@fire.js.berklix.net> <201009011902.06538.hselasky@c2i.net> <4C8627A6.1090308@icyb.net.ua> <4C989989.4050408@icyb.net.ua> <4C98AC42.1040104@digiware.nl> <20100921131610.GA58719@icarus.home.lan> In-Reply-To: <20100921131610.GA58719@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: vadim_nuclight@mail.ru, freebsd-security@freebsd.org, freebsd-stable@freebsd.org, Andriy Gapon Subject: Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 13:49:34 -0000 On 2010-09-21 15:16, Jeremy Chadwick wrote: > On Tue, Sep 21, 2010 at 02:59:46PM +0200, Willem Jan Withagen wrote: >> On 2010-09-21 13:39, {some mysterious person :-)} wrote: >>>> The Project is ultimately about the users, right? There are early signs that >>>> some old FreeBSD users get tired from those changes, those removals, lesser >>>> POLA adherence, marketing-not-technical-stuff for time-not-feature-based >>>> releases, not so stable -STABLE as it used to be, and so on, migrating to >>>> other systems. And older users are more valuable to project than newer ones. >>>> May be it's time to revert to some of thet Old Good Things, if decade-long >>>> project is mostly ended, while those signs are still early and not a strong >>>> tendency?.. Given this thread, I've mentioned earlier about 12 messages in >>>> announce@ from 2002 with such public calls for volunteers - there are several >>>> years already without these. > > Andriy wasn't the one who wrote this. In fact, I'm not sure who the > quote actually came from because I never received the Email it came > from, but I'm under the impression it's from Vadim. My mail spool: My bad for not checking the included reference. I was also very much under the impression that that quote was Vadim's, since it was in completeline with his previous complaints/rants/whining. And yes, your are smart to stay out of the discussion. But this old fart just had too much urge to react. So now I'll just go back to my old lurking state. --WjW From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 13:54:18 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F873106567A for ; Tue, 21 Sep 2010 13:54:18 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id E6BA18FC19 for ; Tue, 21 Sep 2010 13:54:17 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Oy3IT-000215-LH for freebsd-stable@freebsd.org; Tue, 21 Sep 2010 15:54:13 +0200 Received: from nuclight.avtf.net ([217.29.94.29]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Sep 2010 15:54:13 +0200 Received: from vadim_nuclight by nuclight.avtf.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Sep 2010 15:54:13 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Vadim Goncharov Date: Tue, 21 Sep 2010 13:54:00 +0000 (UTC) Organization: Nuclear Lightning @ Tomsk, TPU AVTF Hostel Lines: 42 Message-ID: References: <201009011653.o81Grkm4056064@fire.js.berklix.net> <201009011902.06538.hselasky@c2i.net> <4C8627A6.1090308@icyb.net.ua> <4C989989.4050408@icyb.net.ua> <4C98AC42.1040104@digiware.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: nuclight.avtf.net X-Comment-To: Willem Jan Withagen User-Agent: slrn/0.9.9p1 (FreeBSD) Cc: freebsd-security@freebsd.org Subject: Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vadim_nuclight@mail.ru List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 13:54:18 -0000 Hi Willem Jan Withagen! On Tue, 21 Sep 2010 14:59:46 +0200; Willem Jan Withagen wrote about 'Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon': > I'm a FreeBSD user as early as 1993, still have the first 1.0 CD here as > nice remembrance. So I guess that I qualify as one of those "old > FreeBSD" users. > And I completely disagree with you. > If you have been such an old freebsd user,then you should know the > immense effort there has been to move GIANT out of the way. I cann't > even get close to describing what a huge respect I have for the people > that dared to undertake such a humongous effort. With an high > probability of being flamed to death... > But still ever since 5.x I've seen things really improve for the better. > And yes, I was sorry to see ISDN being removed, but as things have > progressed another version has been returned instead. > And sure I have more hardware than you can imagine that is no longer > supported. But it is all old, and worn down, sometimes it is even still > VESA stuff. > And right,there have been variations in the level of what you would like > to call stable. But compared to the "old days" I would say, it has > always been above my expectation. And note that I have and still do run > 24*7 business on this. FreeBSD has never NEVER ever let me down. That's for you. For me. For a lot of people. But when I see, in my circles, some old users - not any Linux newbies we shouldn't care, but old and skilled users - leaving or talking about where to go from FreeBSD, than you shouldn't ignore the facts. You should say that something, um, smells wrong. > So as far as I'm concerned you are barking up the wrong tree here. Even if you, while investigating for a bug, eventually find that it was not a bug, but during the search discover another bug, that is not the reason to fix the latter. This thread, to this moment, has one practical statement: calls for volunteers and other major notifications should go to announce@, perhaps to Web site, too, perhaps clarified how people can help with money or to hire something to work on the code. And that will make the FreeBSD Project better. So, not to flame more, do you disagree with this? -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 14:02:48 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5216A106566C for ; Tue, 21 Sep 2010 14:02:48 +0000 (UTC) (envelope-from jon.otterholm@ide.resurscentrum.se) Received: from mail1.cil.se (mail1.cil.se [217.197.56.125]) by mx1.freebsd.org (Postfix) with ESMTP id E16E98FC1E for ; Tue, 21 Sep 2010 14:02:47 +0000 (UTC) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Tue, 21 Sep 2010 16:02:44 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Dummynet Thread-Index: ActZi89bZZ4Du7nwTRCNSbGf9x9AKQACKOXQ References: From: "Jon Otterholm" To: Subject: SV: Dummynet X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 14:02:48 -0000 Hi Vadim! > -----Ursprungligt meddelande----- > Fr=E5n: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd- > stable@freebsd.org] F=F6r Vadim Goncharov > Skickat: den 21 september 2010 14:48 > Till: freebsd-stable@freebsd.org > =C4mne: Re: Dummynet >=20 > Hi Jon Otterholm! >=20 > On Mon, 20 Sep 2010 10:00:48 +0200; Jon Otterholm wrote about > 'Dummynet': >=20 > > Installed a new router running 8-stable and encounter some problems > > when configuring dummynet pipes: >=20 > > When setting buckets above 1024... > > ipfw pipe 91 config bw 100Mbit/s mask src-ip 0xffffffff buckets 4096 >=20 > > ...I get the following error: > > Clamp sched buckets to 1024 (was 4096) >=20 > Try to write "buckets 4096" before "mask", though this is unlikely to = help, > there are some troubles with 8.1's changes in parser. Didn't help.=20 >=20 > > # sysctl net.inet.ip.dummynet.hash_size > > net.inet.ip.dummynet.hash_size: 4096 >=20 > Also, make sure you're doing this before any packets actually went to > dummynet (e.g. just after reboot). This is set in /etc/sysctl.conf ... >=20 > > from man ipfw: > > buckets hash-table-size > > Specifies the size of the hash table used for storing the > > various > > queues. Default value is 64 controlled by the sysctl(8) > > variable > > net.inet.ip.dummynet.hash_size, allowed range is 16 to = 65536. >=20 > > Am I missing something here? This worked fine in the 7-branch. >=20 > The reason is that luigi@ merged ipfw3 from -CURRENT between 8.0R and > 8.1R. > There are many new features and, as seen from many PRs, many new bugs. OK. I just have to wait then for luigi@ to submit fixes. Thanks for the tips and info. Should I expect and be prepared for any other flaws from the current = version of dummynet in 8-STABLE? //JO From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 14:20:32 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B7061065675 for ; Tue, 21 Sep 2010 14:20:32 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 005208FC12 for ; Tue, 21 Sep 2010 14:20:31 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Oy3hu-0007FK-Kc for freebsd-stable@freebsd.org; Tue, 21 Sep 2010 16:20:30 +0200 Received: from nuclight.avtf.net ([217.29.94.29]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Sep 2010 16:20:30 +0200 Received: from vadim_nuclight by nuclight.avtf.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Sep 2010 16:20:30 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Vadim Goncharov Date: Tue, 21 Sep 2010 14:20:16 +0000 (UTC) Organization: Nuclear Lightning @ Tomsk, TPU AVTF Hostel Lines: 49 Message-ID: References: <201009011653.o81Grkm4056064@fire.js.berklix.net> <201009011902.06538.hselasky@c2i.net> <4C8627A6.1090308@icyb.net.ua> <4C989989.4050408@icyb.net.ua> <4C98AAE4.9090105@icyb.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: nuclight.avtf.net X-Comment-To: Andriy Gapon User-Agent: slrn/0.9.9p1 (FreeBSD) Subject: Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vadim_nuclight@mail.ru List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 14:20:32 -0000 Hi Andriy Gapon! On Tue, 21 Sep 2010 15:53:56 +0300; Andriy Gapon wrote about 'Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon': >>> Hmm, it's really simple. >>> If you want to shape the future of the project, then participate in the places >>> where the future is shaped. If you want to know what's coming up in the future, >>> then watch the places where the future is shaped. If you don't do either, you get >>> what you get. Complaining post factum just doesn't work. (Numerous other >>> examples and projects also demonstrate that). >>> "Current", "stable" are not some alien versions of FreeBSD for some other strange >>> people to use. >>> Those are your future releases. >>> Not looking into the future has its benefits - you are not doing anything; but it >>> has costs too - you don't know your future. >>> Looking into the future and shaping it has obvious costs, but the benefits are >>> clear too. >>> Business users and old FreeBSD users should know this best of all. >>> It's strange that you try speak on their behalf but do not seem to realize these >>> simple things. >> >> The essence of your words and your position in other letters is: >> >> "We are an open source project exactly the same kind like many others: >> we have no [moral] responsibility to our users, we are selfish and want only >> your code; give us your code and you will have the right to freedom of speech, >> otherwise you're an untermensch". > > Please don't put your words into my mouth. > I've said what I've said. > Your interpretations do not interest me. That's not argument, and my words are logical consequences from your words, and you didn't refute. Still, my statements after, which you skipped (again! you are again skipping the actual truth which discomforts you!), are valid: you say that people who want to know the future or help the Project must go places such as current@, and official FreeBSD docs say that they don't. Thus you are still wrong. But you've failed to hold constructive discussion for 4 RTTs. No logic in reasons, no respect to POVs other than yours -> no hope to prove you something correctly as it is done in science and should be in FreeBSD mail lists. Just accusements. Sad. I give up. -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 14:27:04 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2833B106566C for ; Tue, 21 Sep 2010 14:27:04 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id CFD1C8FC0C for ; Tue, 21 Sep 2010 14:27:03 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Oy3oA-0002KX-J8 for freebsd-stable@freebsd.org; Tue, 21 Sep 2010 16:26:58 +0200 Received: from nuclight.avtf.net ([217.29.94.29]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Sep 2010 16:26:58 +0200 Received: from vadim_nuclight by nuclight.avtf.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Sep 2010 16:26:58 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Vadim Goncharov Date: Tue, 21 Sep 2010 14:26:41 +0000 (UTC) Organization: Nuclear Lightning @ Tomsk, TPU AVTF Hostel Lines: 31 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: nuclight.avtf.net X-Comment-To: Jon Otterholm User-Agent: slrn/0.9.9p1 (FreeBSD) Subject: Re: Dummynet X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vadim_nuclight@mail.ru List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 14:27:04 -0000 Hi Jon Otterholm! On Tue, 21 Sep 2010 16:02:44 +0200; Jon Otterholm wrote about 'SV: Dummynet': >> Try to write "buckets 4096" before "mask", though this is unlikely to help, >> there are some troubles with 8.1's changes in parser. > Didn't help. I've heared about similar bug, but with "queue" after "mask", when it helped. >>> Am I missing something here? This worked fine in the 7-branch. >> >> The reason is that luigi@ merged ipfw3 from -CURRENT between 8.0R and >> 8.1R. >> There are many new features and, as seen from many PRs, many new bugs. > OK. I just have to wait then for luigi@ to submit fixes. > Thanks for the tips and info. > Should I expect and be prepared for any other flaws from the current version of dummynet in 8-STABLE? Yes. I think you should better go to http://www.freebsd.org/cgi/query-pr-summary.cgi?&sort=none&text=ipfw and http://www.freebsd.org/cgi/query-pr-summary.cgi?&sort=none&text=dummynet and find reports similar to yours. If there no such, create your one - because: 1) this is official place for bug reports, they won't get lost, and in mail lists - they may get lost 2) luigi@ just may be not knowing about the bug without report -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 15:23:01 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E562F106566C for ; Tue, 21 Sep 2010 15:23:01 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id A927C8FC27 for ; Tue, 21 Sep 2010 15:23:00 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 5AB1173098; Tue, 21 Sep 2010 17:34:38 +0200 (CEST) Date: Tue, 21 Sep 2010 17:34:38 +0200 From: Luigi Rizzo To: Vadim Goncharov Message-ID: <20100921153438.GC11958@onelab2.iet.unipi.it> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: Dummynet X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 15:23:02 -0000 On Tue, Sep 21, 2010 at 02:26:41PM +0000, Vadim Goncharov wrote: > Hi Jon Otterholm! > > On Tue, 21 Sep 2010 16:02:44 +0200; Jon Otterholm wrote about 'SV: Dummynet': > > >> Try to write "buckets 4096" before "mask", though this is unlikely to help, > >> there are some troubles with 8.1's changes in parser. > > Didn't help. > > I've heared about similar bug, but with "queue" after "mask", when it helped. > > >>> Am I missing something here? This worked fine in the 7-branch. > >> > >> The reason is that luigi@ merged ipfw3 from -CURRENT between 8.0R and > >> 8.1R. > >> There are many new features and, as seen from many PRs, many new bugs. > > OK. I just have to wait then for luigi@ to submit fixes. > > Thanks for the tips and info. > > Should I expect and be prepared for any other flaws from the current version of dummynet in 8-STABLE? > > Yes. I think you should better go to > http://www.freebsd.org/cgi/query-pr-summary.cgi?&sort=none&text=ipfw and > http://www.freebsd.org/cgi/query-pr-summary.cgi?&sort=none&text=dummynet > and find reports similar to yours. If there no such, create your one - > because: > 1) this is official place for bug reports, they won't get lost, and in > mail lists - they may get lost > 2) luigi@ just may be not knowing about the bug without report I believe this bug was reported and fixed in our internal tree, but did not find the time yet to commit it, due to the 8.1 release cycle and then vacation and other committments. cheers luigi From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 15:24:55 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02899106564A for ; Tue, 21 Sep 2010 15:24:55 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 9FB1F8FC14 for ; Tue, 21 Sep 2010 15:24:54 +0000 (UTC) Received: by qyk31 with SMTP id 31so4319546qyk.13 for ; Tue, 21 Sep 2010 08:24:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=96y5wzpfoZEvKRUgdCDYsOJ1Ueswei/uIUWUU6/6s54=; b=Lhp+qDg2Xo/RjkO9mBgfadceBZe1mQzWvz8dRLrkICET+jfwjDekUQJKLjfICblper SL2uiQdQVJ3yblJqo+SUw9zgQZpMaLXqK6DAOFGs8OWnqG+TaWvpWdYl5bCIoF4LnXBg jKfsyXL8ST9O4F14sBKK0WEpB9Ob447sQFMvo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=d7QBH05zvgNDvlxnItVgxFSLXGR0YnUfsytoyd6VQxe7PbNr9Txw91UmuSt71Soati TDworqzu027kScaskGUdxWI3w5yKQbYIRIcD4LPNKpRTP0EqUwez8plJMwp7m2r1WhVG GLxUDr2RocGzL5d6iVzMCa/wwSf2VNrEgsjq4= MIME-Version: 1.0 Received: by 10.224.28.145 with SMTP id m17mr7110654qac.196.1285082693845; Tue, 21 Sep 2010 08:24:53 -0700 (PDT) Received: by 10.229.236.15 with HTTP; Tue, 21 Sep 2010 08:24:52 -0700 (PDT) In-Reply-To: References: <201009011653.o81Grkm4056064@fire.js.berklix.net> <201009011902.06538.hselasky@c2i.net> <4C8627A6.1090308@icyb.net.ua> <4C989989.4050408@icyb.net.ua> <4C98AAE4.9090105@icyb.net.ua> Date: Tue, 21 Sep 2010 16:24:52 +0100 Message-ID: From: Tom Evans To: vadim_nuclight@mail.ru Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org Subject: Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 15:24:55 -0000 On Tue, Sep 21, 2010 at 3:20 PM, Vadim Goncharov wrote: > I give up. > Thank $DEITY. Cheers Tom From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 16:58:50 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE6401065670 for ; Tue, 21 Sep 2010 16:58:50 +0000 (UTC) (envelope-from Pascal.Stumpf@cubes.de) Received: from smtprelay04.ispgateway.de (smtprelay04.ispgateway.de [80.67.29.8]) by mx1.freebsd.org (Postfix) with ESMTP id 819B18FC21 for ; Tue, 21 Sep 2010 16:58:50 +0000 (UTC) Received: from [62.224.176.55] (helo=ikarus.local.cubes.de) by smtprelay04.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1Oy5zG-0001jo-LC for freebsd-stable@freebsd.org; Tue, 21 Sep 2010 18:46:34 +0200 From: Pascal Stumpf To: freebsd-stable@freebsd.org Date: Tue, 21 Sep 2010 18:46:34 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.5.1; amd64; ; ) References: <20100921093106.GA95379@lordcow.org> <20100921134554.GA10927@lordcow.org> In-Reply-To: <20100921134554.GA10927@lordcow.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201009211846.34982.Pascal.Stumpf@cubes.de> X-Df-Sender: 429867 Subject: Re: source tree out of sync X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 16:58:50 -0000 On Tuesday 21 September 2010 15:45:54 Gareth de Vaux wrote: > On Tue 2010-09-21 (11:31), Gareth de Vaux wrote: > > I assume I can't do this safely if my /usr/src tree has been > > updated since my last make world? >=20 > Well, doesn't look like it's an issue for me in this instance. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" =46or the record: It would not be a problem at all, at least in this=20 particular case: You=E2=80=99re only patching and reinstalling bzip2, which= =20 hasn=E2=80=99t had a commit for ages except this one security patch. See: http://www.freebsd.org/cgi/cvsweb.cgi/src/contrib/bzip2/ You=E2=80=99re not touching any other system component, so the date of your= =20 /usr/src checkout is not an issue. You could even csup the most recent=20 version instead of applying the patch manually and then recompile bzip2=20 only. Cheers, Pascal From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 17:33:23 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A848106564A; Tue, 21 Sep 2010 17:33:23 +0000 (UTC) (envelope-from joe.shevland@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id EE3208FC0C; Tue, 21 Sep 2010 17:33:22 +0000 (UTC) Received: by pzk7 with SMTP id 7so1956512pzk.13 for ; Tue, 21 Sep 2010 10:33:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=WdtjoWocMzxru7NXbrseDke2q4iMNT/x5vG9ETgDHO4=; b=LTdDXyxsx6SSOubg0n2HE3PTswFbV951jqkg/XRbSI++ghq0UToz5joDF6A6Cr3gFe wZUVtk8HRKviVzfq0eCabWSWvscf389Dg9NBD/3eNqoZZgLgIkEWZ7UfPZ0pZFx6Gd6Q oLrHRjXAdrG/adsFKSbWvJux7mOJE/T+7774g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=WoCX/qCuJDjC5X7Ketie348HIbmmhGUtksLj+x8BwWZvH8un+7ec6rWGgYjNyC90NT MJ+UffLPEURhra28RXEVMFNeOO65ZtG7c27zN8KaEKBOqfc7wR82WbpizA3ukwJDUdGs AcvLwILSJlp0TutmD8ioHyg5huYzESFQ3RfnE= Received: by 10.114.133.11 with SMTP id g11mr12005519wad.213.1285089049539; Tue, 21 Sep 2010 10:10:49 -0700 (PDT) Received: from [192.168.0.50] (d122-109-167-147.sun2.vic.optusnet.com.au [122.109.167.147]) by mx.google.com with ESMTPS id s5sm15884897wak.12.2010.09.21.10.10.45 (version=SSLv3 cipher=RC4-MD5); Tue, 21 Sep 2010 10:10:48 -0700 (PDT) Message-ID: <4C98E71F.4040800@gmail.com> Date: Wed, 22 Sep 2010 03:10:55 +1000 From: Joe Shevland User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: Willem Jan Withagen References: <201009011653.o81Grkm4056064@fire.js.berklix.net> <201009011902.06538.hselasky@c2i.net> <4C8627A6.1090308@icyb.net.ua> <4C989989.4050408@icyb.net.ua> <4C98AC42.1040104@digiware.nl> <20100921131610.GA58719@icarus.home.lan> <4C98B7E7.1020403@digiware.nl> In-Reply-To: <4C98B7E7.1020403@digiware.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: vadim_nuclight@mail.ru, freebsd-security@freebsd.org, freebsd-stable@freebsd.org, Andriy Gapon , Jeremy Chadwick Subject: Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 17:33:23 -0000 On 21/09/2010 11:49 PM, Willem Jan Withagen wrote: > On 2010-09-21 15:16, Jeremy Chadwick wrote: >> On Tue, Sep 21, 2010 at 02:59:46PM +0200, Willem Jan Withagen wrote: >>> On 2010-09-21 13:39, {some mysterious person :-)} wrote: >>>>> The Project is ultimately about the users, right? There are early >>>>> signs that >>>>> some old FreeBSD users get tired from those changes, those >>>>> removals, lesser >>>>> POLA adherence, marketing-not-technical-stuff for >>>>> time-not-feature-based >>>>> releases, not so stable -STABLE as it used to be, and so on, >>>>> migrating to >>>>> other systems. And older users are more valuable to project than >>>>> newer ones. >>>>> May be it's time to revert to some of thet Old Good Things, if >>>>> decade-long >>>>> project is mostly ended, while those signs are still early and not >>>>> a strong >>>>> tendency?.. Given this thread, I've mentioned earlier about 12 >>>>> messages in >>>>> announce@ from 2002 with such public calls for volunteers - there >>>>> are several >>>>> years already without these. >> >> Andriy wasn't the one who wrote this. In fact, I'm not sure who the >> quote actually came from because I never received the Email it came >> from, but I'm under the impression it's from Vadim. My mail spool: > > My bad for not checking the included reference. > I was also very much under the impression that that quote was Vadim's, > since it was in completeline with his previous complaints/rants/whining. > > And yes, your are smart to stay out of the discussion. But this old > fart just had too much urge to react. So now I'll just go back to my > old lurking state. My thoughts are below - remembering its a volunteer project, people spend their precious time to make it happen, and noneofthatwisthandingitsstilldamngood: a) if you don't like it, fix it. b) if you can't fix it, pay someone else to fix it c) if you can't fix it or otherwise be helpful, remain silent If you can't do a or b or c, and still have no options, below: d) whinging never helps e) those that whinge on volunteer projects are subject to the emperors wrath f) kill the heretic, the witch, the unbeliever. Recover the gene-seed at all costs. Cheers Joe > > --WjW > > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to > "freebsd-security-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 17:52:34 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7EC0D1065673; Tue, 21 Sep 2010 17:52:34 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 656E28FC18; Tue, 21 Sep 2010 17:52:32 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA12572; Tue, 21 Sep 2010 20:52:31 +0300 (EEST) (envelope-from avg@freebsd.org) Message-ID: <4C98F0DF.1000801@freebsd.org> Date: Tue, 21 Sep 2010 20:52:31 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20100920 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: Jung-uk Kim References: <201007141414.o6EEEUx9014690@lurza.secnetix.de> <4C77F6D6.9020402@icyb.net.ua> <201008271536.08773.jkim@FreeBSD.org> <201009011426.26111.jkim@FreeBSD.org> <4C7F5F90.3030407@icyb.net.ua> In-Reply-To: <4C7F5F90.3030407@icyb.net.ua> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: jeff@freebsd.org, freebsd-stable@freebsd.org Subject: Re: 8.1-PRERELEASE: CPU packages not detected correctly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 17:52:34 -0000 on 02/09/2010 11:25 Andriy Gapon said the following: > on 01/09/2010 21:26 Jung-uk Kim said the following: >> On Friday 27 August 2010 03:36 pm, Jung-uk Kim wrote: >>> [3] AMD is working on an SMT-capable CPU (code-named Bulldozer) and >>> my patch won't work on them. If anyone has a Bulldozer sample, >>> please look into it. >> >> I checked AMD website today and found out a new CPUID Spec. Rev. 2.34 >> was just released: >> >> http://support.amd.com/us/Embedded_TechDocs/25481.pdf >> >> They have added CPUID 0x8000001d and 0x8000001e to detect topology, it >> seems. Also, CPUID 0x80000001 %ecx bit 22 (TopologyExtensions) tells >> you whether the above CPUID functions are supported. >> >> Interesting... > > Yeah, I've heard that they are adding SMT capabilities in "Bulldozer" > processors, so I guess they have to change CPU topology detection indicators. The above comment by me is almost nonsense :) I looked at the document with better attention and I think that what the new way does is better/provides proper support for discovering non-uniform topologies based on APIC IDs of the cores. BTW, I am reading that AMD Bulldozer CPU package will consist of modules, which in turn will consist of cores. When a "core" would be something in between current notion of core and current notion of hardware thread (SMT/HTT/whatever). The Bulldozer cores will have independent arithmetic units and L1 caches, but shared FPU, L2, fetch+decode and some other elements; L3 cache is per package (shared by all "modules"). -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 18:06:44 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 139621065694 for ; Tue, 21 Sep 2010 18:06:44 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id AE4758FC1F for ; Tue, 21 Sep 2010 18:06:43 +0000 (UTC) Received: (qmail 5398 invoked by uid 399); 21 Sep 2010 18:06:42 -0000 Received: from localhost (HELO ?192.168.0.142?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 21 Sep 2010 18:06:42 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C98F433.6070506@FreeBSD.org> Date: Tue, 21 Sep 2010 11:06:43 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: Mark Kamichoff References: <20100919183721.GA17616@prolixium.com> <20100919185528.GA28845@prolixium.com> <4C97E15D.7070304@FreeBSD.org> <20100921114300.GB16298@prolixium.com> In-Reply-To: <20100921114300.GB16298@prolixium.com> X-Enigmail-Version: 1.2a1pre OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: BIND9 built w/--disable-ipv6 on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 18:06:44 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 9/21/2010 4:43 AM, Mark Kamichoff wrote: | On Mon, Sep 20, 2010 at 03:34:05PM -0700, Doug Barton wrote: |> | Although, that still does beg the question, |> |> No, it doesn't. :) See http://en.wikipedia.org/wiki/Beg_the_question | | http://en.wikipedia.org/wiki/Beg_the_question#Modern_usage Yes, especially the last bit, "Usage commentators have deemed using the term in this way to be incorrect." :) |> | why don't we want IPv6 enabled by default on new BIND installations? |> |> It has to do with whether or not IPv6 support is compiled into the |> FreeBSD base system which is compiling BIND. If the configure option |> is set to enable but there is not the proper support in the base, then |> Bad Things(TM) happen. However, the way that it is set up now if the |> binaries are running on a system that has IPv6 support then that is |> detected, and you can use it if you choose. If the binaries are |> running on a system without IPv6 support, no harm, no foul. | | I see, that makes sense. However, as IPv6 becomes more widely used | (perhaps quite far in the future, when folks are turning /off/ IPv4), it | might need revisiting. If I'm still alive when IPv6 is the norm and IPv4 is the exception, I promise to give it another look. :) Doug - -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (MingW32) iQEcBAEBCAAGBQJMmPQzAAoJEFzGhvEaGryEH+cH/1FV/oNnpFR82oQRG9QVV6GJ d1L4uNLcDEDTKsIboFS5oECQaO0H4lZL3OMmfUCXISg3+ZvbIW4tms/HKdXCi+Ks f4sCgRWWCuyOv/yg/FL4asUQXGwA1ESaIv4d34ZthAqbjWdE4cXb0Kwwhkllpcu/ B1ph4xyXZ71apxxSGzC1ZOppwtCTamwj/o0OgEnIrBHkPyiXL2FI7Ozo5vIt2HoN /Q5UDAB1fwd80pVcEY6Rw2wbgNmthgv4fa6HtchqscqA2PgpuqO7+0JbuE7zkik2 Ktf54uaMUQU4eWWGBIFVsZDy/uUSezlaQEsAFwsSM6WUcBkSBEMomwQwANMw+qM= =jN1T -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 18:50:49 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76D7E10656A3 for ; Tue, 21 Sep 2010 18:50:49 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id EF1BB8FC0C for ; Tue, 21 Sep 2010 18:50:46 +0000 (UTC) Received: (qmail 20355 invoked by uid 399); 21 Sep 2010 18:50:45 -0000 Received: from localhost (HELO ?192.168.0.142?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 21 Sep 2010 18:50:45 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C98FE85.6030006@FreeBSD.org> Date: Tue, 21 Sep 2010 11:50:45 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: vadim_nuclight@mail.ru References: <201009011653.o81Grkm4056064@fire.js.berklix.net> <201009011902.06538.hselasky@c2i.net> <4C8627A6.1090308@icyb.net.ua> <4C989989.4050408@icyb.net.ua> <4C98AC42.1040104@digiware.nl> In-Reply-To: X-Enigmail-Version: 1.2a1pre OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-security@freebsd.org, freebsd-stable@freebsd.org Subject: Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 18:50:49 -0000 On 9/21/2010 6:54 AM, Vadim Goncharov wrote: > This thread, to this moment, has one practical statement: calls for > volunteers and other major notifications should go to announce@, > perhaps to Web site, too ... and since you've made that point, and several people in the project leadership have agreed with you, perhaps it's time to give it a rest? Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 19:15:18 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CA391065693; Tue, 21 Sep 2010 19:15:18 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail1.es.net [IPv6:2001:400:201:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 67AEB8FC1A; Tue, 21 Sep 2010 19:15:18 +0000 (UTC) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id o8LJFHSp016805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 21 Sep 2010 12:15:18 -0700 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id AF60A1CC3D; Tue, 21 Sep 2010 12:15:17 -0700 (PDT) To: Doug Barton In-reply-to: Your message of "Tue, 21 Sep 2010 11:06:43 PDT." <4C98F433.6070506@FreeBSD.org> Date: Tue, 21 Sep 2010 12:15:17 -0700 From: "Kevin Oberman" Message-Id: <20100921191517.AF60A1CC3D@ptavv.es.net> Cc: freebsd-stable@freebsd.org, Mark Kamichoff Subject: Re: BIND9 built w/--disable-ipv6 on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 19:15:18 -0000 > Date: Tue, 21 Sep 2010 11:06:43 -0700 > From: Doug Barton > Sender: owner-freebsd-stable@freebsd.org > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 9/21/2010 4:43 AM, Mark Kamichoff wrote: > | On Mon, Sep 20, 2010 at 03:34:05PM -0700, Doug Barton wrote: > |> | Although, that still does beg the question, > |> > |> No, it doesn't. :) See http://en.wikipedia.org/wiki/Beg_the_question > | > | http://en.wikipedia.org/wiki/Beg_the_question#Modern_usage > > Yes, especially the last bit, "Usage commentators have deemed using the > term in this way to be incorrect." :) Sadly, I must note that Edwin Newman (http://en.wikipedia.org/wiki/Edwin_Newman) passed away last month. I fear the common, totally illogical use of this phrase is now a lost cause. I could care less (not sic). > |> | why don't we want IPv6 enabled by default on new BIND installations? > |> > |> It has to do with whether or not IPv6 support is compiled into the > |> FreeBSD base system which is compiling BIND. If the configure option > |> is set to enable but there is not the proper support in the base, then > |> Bad Things(TM) happen. However, the way that it is set up now if the > |> binaries are running on a system that has IPv6 support then that is > |> detected, and you can use it if you choose. If the binaries are > |> running on a system without IPv6 support, no harm, no foul. > | > | I see, that makes sense. However, as IPv6 becomes more widely used > | (perhaps quite far in the future, when folks are turning /off/ IPv4), it > | might need revisiting. > > If I'm still alive when IPv6 is the norm and IPv4 is the exception, I > promise to give it another look. :) I'd suggest looking at it when IPv6 becomes a standard part of system software and routing . That will happen long before IPv4 becomes an exception. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 19:24:52 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B69A81065675 for ; Tue, 21 Sep 2010 19:24:52 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 4CF048FC0A for ; Tue, 21 Sep 2010 19:24:52 +0000 (UTC) Received: (qmail 15203 invoked by uid 399); 21 Sep 2010 19:24:51 -0000 Received: from localhost (HELO ?192.168.0.142?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 21 Sep 2010 19:24:51 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C990683.8070302@FreeBSD.org> Date: Tue, 21 Sep 2010 12:24:51 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: Kevin Oberman References: <20100921191517.AF60A1CC3D@ptavv.es.net> In-Reply-To: <20100921191517.AF60A1CC3D@ptavv.es.net> X-Enigmail-Version: 1.2a1pre OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Mark Kamichoff Subject: Re: BIND9 built w/--disable-ipv6 on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 19:24:52 -0000 On 9/21/2010 12:15 PM, Kevin Oberman wrote: > I'd suggest looking at it when IPv6 becomes a standard part of system > software and routing . That will happen long before IPv4 becomes an > exception. I think you missed the bit where I pointed out that the current configuration works in all modern cases, both common and uncommon. The point I tried to humorously make in my previous post was that the current configuration will continue to work until such time as systems are commonly built without any IPv4 at all. BIND does not even have a configuration knob for "no IPv4" atm, nor should it, since it works perfectly well on IPv6-only systems. In short, there is no reason to make a change now, and long before there is any reason to make such a change the underlying software will have changed sufficiently to make the discussion moot. As always, users with special needs beyond what the base BIND provides are welcome to configure to their heart's content either with the port(s) of BIND, or if that's not enough knobs for you you can always build it yourself. hth, Doug PS, pardon the humorless nature of this reply, as attempting to make my point(s) with humor was apparently not very effective. -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-stable@FreeBSD.ORG Tue Sep 21 19:48:45 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 49A441065672; Tue, 21 Sep 2010 19:48:45 +0000 (UTC) (envelope-from db@db.net) Received: from diana.db.net (diana.db.net [66.113.102.10]) by mx1.freebsd.org (Postfix) with ESMTP id 30FAB8FC0A; Tue, 21 Sep 2010 19:48:44 +0000 (UTC) Received: from night.db.net (localhost [127.0.0.1]) by diana.db.net (Postfix) with ESMTP id 4E2372282A; Tue, 21 Sep 2010 13:29:43 -0600 (MDT) Received: by night.db.net (Postfix, from userid 100) id 259915C6E; Tue, 21 Sep 2010 15:31:01 -0400 (EDT) Date: Tue, 21 Sep 2010 15:31:01 -0400 From: Diane Bruce To: Kevin Oberman Message-ID: <20100921193101.GA95238@night.db.net> References: <4C98F433.6070506@FreeBSD.org> <20100921191517.AF60A1CC3D@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100921191517.AF60A1CC3D@ptavv.es.net> User-Agent: Mutt/1.4.2.3i Cc: Doug Barton , freebsd-stable@freebsd.org, Mark Kamichoff Subject: Re: BIND9 built w/--disable-ipv6 on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 19:48:45 -0000 On Tue, Sep 21, 2010 at 12:15:17PM -0700, Kevin Oberman wrote: > > Date: Tue, 21 Sep 2010 11:06:43 -0700 > > From: Doug Barton > > Sender: owner-freebsd-stable@freebsd.org > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA256 > > > > On 9/21/2010 4:43 AM, Mark Kamichoff wrote: > > | On Mon, Sep 20, 2010 at 03:34:05PM -0700, Doug Barton wrote: > > |> | Although, that still does beg the question, > > |> > > |> No, it doesn't. :) See http://en.wikipedia.org/wiki/Beg_the_question > > | > > | http://en.wikipedia.org/wiki/Beg_the_question#Modern_usage > > > > Yes, especially the last bit, "Usage commentators have deemed using the > > term in this way to be incorrect." :) > > Sadly, I must note that Edwin Newman > (http://en.wikipedia.org/wiki/Edwin_Newman) passed away last month. I All I would add is: http://www.qwantz.com/index.php?comic=693 http://languagelog.ldc.upenn.edu/nll/?p=2290 > fear the common, totally illogical use of this phrase is now a lost > cause. I could care less (not sic). It is annoying yes. Language changes underneath us though. > > |> | why don't we want IPv6 enabled by default on new BIND installations? > > |> > > |> It has to do with whether or not IPv6 support is compiled into the > > |> FreeBSD base system which is compiling BIND. If the configure option ... > > If I'm still alive when IPv6 is the norm and IPv4 is the exception, I > > promise to give it another look. :) IPv6 is more prevalent than you think. I can't understand the illogic of turning it off. > -- > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: oberman@es.net Phone: +1 510 486-8634 > Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" - Diane -- - db@FreeBSD.org db@db.net http://www.db.net/~db From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 03:02:10 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0CFC106564A for ; Wed, 22 Sep 2010 03:02:10 +0000 (UTC) (envelope-from bryce@bryce.net) Received: from mail-gy0-f186.google.com (mail-gy0-f186.google.com [209.85.160.186]) by mx1.freebsd.org (Postfix) with ESMTP id 69F1D8FC16 for ; Wed, 22 Sep 2010 03:02:09 +0000 (UTC) Received: by gyg4 with SMTP id 4so41996gyg.13 for ; Tue, 21 Sep 2010 20:02:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.101.8.33 with SMTP id l33mr437946ani.24.1285124529408; Tue, 21 Sep 2010 20:02:09 -0700 (PDT) Received: by q2g2000vbk.googlegroups.com with HTTP; Tue, 21 Sep 2010 20:02:09 -0700 (PDT) Date: Tue, 21 Sep 2010 20:02:09 -0700 (PDT) In-Reply-To: X-IP: 70.140.155.124 References: User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10,gzip(gfe) Message-ID: <10b0bdef-2bb1-44c8-9ffb-7d3167147a4f@q2g2000vbk.googlegroups.com> From: Bryce To: Peter Jeremy Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 03:02:10 -0000 On Sep 20, 6:17=A0am, peterjer...@acm.org (Peter Jeremy) wrote: > On 2010-Sep-18 08:32:32 -0500, Bryce Edwards wrote: > > >I have a Supermicro with the C7X58 motherboard and an i7 930 cpu, and > >it is nowhere near the performance it should be. =A0A buildworld just > >took 22.5 hours! > > That does sound a bit poor. =A0I presume the system was basically unloade= d > during the buildworld. > > Can we see the output of: > - vmstat -i interrupt total rate irq1: atkbd0 853 0 irq16: uhci0 mpt0 117706 0 irq17: fwohci0 1 0 irq23: uhci3 ehci1 22 0 cpu0: timer 1046064200 1979 irq256: em0 1861363 3 irq258: ahci0 3922875 7 cpu1: timer 1046058992 1979 cpu4: timer 1046056958 1979 cpu3: timer 1046058951 1979 cpu2: timer 1046055416 1979 cpu6: timer 1046057518 1979 cpu5: timer 1046058850 1979 cpu7: timer 1046058744 1979 Total 8374372449 15850 > - zpool status -v pool: data state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM data ONLINE 0 0 0 mirror ONLINE 0 0 0 gpt/hitachi0 ONLINE 0 0 0 gpt/hitachi1 ONLINE 0 0 0 errors: No known data errors pool: ext1 state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM ext1 ONLINE 0 0 0 da2 ONLINE 0 0 0 errors: No known data errors pool: storage state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM storage ONLINE 0 0 0 raidz1 ONLINE 0 0 0 gpt/samsung0 ONLINE 0 0 0 gpt/samsung1 ONLINE 0 0 0 gpt/samsung2 ONLINE 0 0 0 gpt/samsung3 ONLINE 0 0 0 errors: No known data errors pool: system state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM system ONLINE 0 0 0 mirror ONLINE 0 0 0 gpt/disk0 ONLINE 0 0 0 gpt/disk1 ONLINE 0 0 0 errors: No known data errors > - df -k Filesystem 1024-blocks Used Avail Capacity Mounted on system 142091977 611793 141480184 0% / devfs 1 1 0 100% /dev linprocfs 4 4 0 100% / compat/linux/proc storage 2729825067 38 2729825028 0% / storage storage/archive 2959080344 229255316 2729825028 8% / storage/archive storage/backups 2906677465 176852436 2729825028 6% / storage/backups data 1817823312 2487426 1815335886 0% / storage/data data/Pictures 1912868417 97532531 1815335886 5% / storage/data/Pictures storage/files 2794105921 64280893 2729825028 2% / storage/files storage/incoming 3712303044 982478016 2729825028 26% / storage/incoming storage/media 2835215837 105390809 2729825028 4% / storage/media storage/media/Games 2752775684 22950655 2729825028 1% / storage/media/Games storage/media/Movies 3745007442 1015182414 2729825028 27% / storage/media/Movies storage/media/Music 2811591585 81766557 2729825028 3% / storage/media/Music system/usr 142342976 862792 141480184 1% /usr system/usr/home 142105804 625620 141480184 0% /usr/ home system/usr/obj 143296312 1816128 141480184 1% /usr/ obj system/usr/ports 142059536 579352 141480184 0% /usr/ ports system/usr/src 141792965 312781 141480184 0% /usr/ src system/var 141715785 235601 141480184 0% /var /dev/md0 19566 12 19554 0% /tmp ext1 1092323986 25 1092323960 0% /mnt ext1/data 1094811390 2487429 1092323960 0% /mnt/ data ext1/data/Pictures 1189727469 97403509 1092323960 8% /mnt/ data/Pictures ext1/storage 1092323987 27 1092323960 0% /mnt/ storage ext1/storage/backups 1269282867 176958906 1092323960 14% /mnt/ storage/backups ext1/storage/files 1156645316 64321355 1092323960 6% /mnt/ storage/files ext1/system 1092935755 611794 1092323960 0% /mnt/ system ext1/system/usr 1093186866 862905 1092323960 0% /mnt/ system/usr ext1/system/usr/home 1092949651 625691 1092323960 0% /mnt/ system/usr/home ext1/system/var 1092559374 235413 1092323960 0% /mnt/ system/var > - mount -v system on / (zfs, local, noatime) devfs on /dev (devfs, local, multilabel) linprocfs on /compat/linux/proc (linprocfs, local) storage on /storage (zfs, local, noatime) storage/archive on /storage/archive (zfs, local, noatime) storage/backups on /storage/backups (zfs, local, noatime) data on /storage/data (zfs, local) data/Pictures on /storage/data/Pictures (zfs, local) storage/files on /storage/files (zfs, local, noatime) storage/incoming on /storage/incoming (zfs, local, noatime) storage/media on /storage/media (zfs, local, noatime) storage/media/Games on /storage/media/Games (zfs, local, noatime) storage/media/Movies on /storage/media/Movies (zfs, local, noatime) storage/media/Music on /storage/media/Music (zfs, local, noatime) system/usr on /usr (zfs, local, noatime) system/usr/home on /usr/home (zfs, local, noatime, nosuid) system/usr/obj on /usr/obj (zfs, local, noatime) system/usr/ports on /usr/ports (zfs, local, noatime, nosuid) system/usr/src on /usr/src (zfs, local, noatime, noexec, nosuid) system/var on /var (zfs, local, noatime) /dev/md0 on /tmp (ufs, asynchronous, local, noatime) ext1 on /mnt (zfs, local) ext1/data on /mnt/data (zfs, local) ext1/data/Pictures on /mnt/data/Pictures (zfs, local) ext1/storage on /mnt/storage (zfs, local) ext1/storage/backups on /mnt/storage/backups (zfs, local) ext1/storage/files on /mnt/storage/files (zfs, local) ext1/system on /mnt/system (zfs, local) ext1/system/usr on /mnt/system/usr (zfs, local) ext1/system/usr/home on /mnt/system/usr/home (zfs, local) ext1/system/var on /mnt/system/var (zfs, local) > - md5 -t =A0 [this will help determine if the problem is lack of CPU] MD5 time trial. Digesting 100000 10000-byte blocks ... done Digest =3D 766a2bb5d24bddae466c572bcabca3ee Time =3D 5.421381 seconds Speed =3D 184454848.000000 bytes/second > - sysctl vm vm.vmtotal: System wide totals computed every five seconds: (values in kilobytes) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Processes: (RUNQ: 1 Disk Wait: 0 Page Wait: 0 Sleep: 32) Virtual Memory: (Total: 1074279508K, Active 422412K) Real Memory: (Total: 1252504K Active 28660K) Shared Virtual Memory: (Total: 28792K Active: 13456K) Shared Real Memory: (Total: 8716K Active: 6520K) Free Memory Pages: 3035952K vm.loadavg: { 0.00 0.00 0.00 } vm.v_free_min: 9590 vm.v_free_target: 40381 vm.v_free_reserved: 2021 vm.v_inactive_target: 60571 vm.v_cache_min: 40381 vm.v_cache_max: 80762 vm.v_pageout_free_min: 34 vm.pageout_algorithm: 0 vm.swap_enabled: 1 vm.kmem_size_scale: 3 vm.kmem_size_max: 329853485875 vm.kmem_size_min: 0 vm.kmem_size: 2067320832 vm.nswapdev: 2 vm.dmmax: 32 vm.swap_async_max: 4 vm.overcommit: 0 vm.swap_reserved: 395976704 vm.swap_total: 8589934592 vm.zone_count: 191 vm.swap_idle_threshold2: 10 vm.swap_idle_threshold1: 2 vm.kstacks: 724 vm.kstack_cache_size: 128 vm.exec_map_entries: 16 vm.stats.misc.zero_page_count: 189 vm.stats.misc.cnt_prezero: 0 vm.stats.vm.v_kthreadpages: 0 vm.stats.vm.v_rforkpages: 0 vm.stats.vm.v_vforkpages: 36355379 vm.stats.vm.v_forkpages: 113127423 vm.stats.vm.v_kthreads: 28 vm.stats.vm.v_rforks: 0 vm.stats.vm.v_vforks: 173728 vm.stats.vm.v_forks: 441695 vm.stats.vm.v_interrupt_free_min: 2 vm.stats.vm.v_pageout_free_min: 34 vm.stats.vm.v_cache_max: 80762 vm.stats.vm.v_cache_min: 40381 vm.stats.vm.v_cache_count: 8123 vm.stats.vm.v_inactive_count: 1310 vm.stats.vm.v_inactive_target: 60571 vm.stats.vm.v_active_count: 41328 vm.stats.vm.v_wire_count: 712096 vm.stats.vm.v_free_count: 750836 vm.stats.vm.v_free_min: 9590 vm.stats.vm.v_free_target: 40381 vm.stats.vm.v_free_reserved: 2021 vm.stats.vm.v_page_count: 1514151 vm.stats.vm.v_page_size: 4096 vm.stats.vm.v_tfree: 167732869 vm.stats.vm.v_pfree: 98570493 vm.stats.vm.v_dfree: 0 vm.stats.vm.v_tcached: 103875 vm.stats.vm.v_pdpages: 0 vm.stats.vm.v_pdwakeups: 0 vm.stats.vm.v_reactivated: 72388 vm.stats.vm.v_intrans: 4408 vm.stats.vm.v_vnodepgsout: 12785 vm.stats.vm.v_vnodepgsin: 109922 vm.stats.vm.v_vnodeout: 10042 vm.stats.vm.v_vnodein: 109922 vm.stats.vm.v_swappgsout: 0 vm.stats.vm.v_swappgsin: 0 vm.stats.vm.v_swapout: 0 vm.stats.vm.v_swapin: 0 vm.stats.vm.v_ozfod: 0 vm.stats.vm.v_zfod: 113400918 vm.stats.vm.v_cow_optim: 33371 vm.stats.vm.v_cow_faults: 18233444 vm.stats.vm.v_vm_faults: 147005945 vm.stats.sys.v_soft: 81806059 vm.stats.sys.v_intr: 5903805 vm.stats.sys.v_syscall: 126779283 vm.stats.sys.v_trap: 157285021 vm.stats.sys.v_swtch: 252443163 vm.stats.object.bypasses: 143582 vm.stats.object.collapses: 1817130 vm.v_free_severe: 5805 vm.max_proc_mmap: 172276 vm.old_msync: 0 vm.msync_flush_flags: 3 vm.boot_pages: 48 vm.max_wired: 495315 vm.pageout_lock_miss: 0 vm.disable_swapspace_pageouts: 0 vm.defer_swapspace_pageouts: 0 vm.swap_idle_enabled: 0 vm.pageout_stats_interval: 5 vm.pageout_full_stats_interval: 20 vm.pageout_stats_max: 40381 vm.max_launder: 32 vm.phys_segs: SEGMENT 0: start: 0x1000 end: 0x99000 free list: 0xffffffff80c77e08 SEGMENT 1: start: 0x1073000 end: 0xbea92000 free list: 0xffffffff80c77a60 SEGMENT 2: start: 0x100000000 end: 0x1b3ff0000 free list: 0xffffffff80c77a60 vm.phys_free: FREE LIST 0: ORDER (SIZE) | NUMBER | POOL 0 | POOL 1 | POOL 2 -- -- -- -- -- -- -- -- 12 (016384K) | 000119 | 000000 | 000000 11 (008192K) | 000026 | 000001 | 000000 10 (004096K) | 000058 | 000001 | 000000 09 (002048K) | 000053 | 000001 | 000000 08 (001024K) | 000001 | 000000 | 000000 07 (000512K) | 000002 | 000000 | 000000 06 (000256K) | 000004 | 000000 | 000000 05 (000128K) | 000019 | 000001 | 000004 04 (000064K) | 000078 | 000001 | 000015 03 (000032K) | 000206 | 000004 | 000202 02 (000016K) | 000650 | 000012 | 000434 01 (000008K) | 001112 | 000016 | 001479 00 (000004K) | 000652 | 000005 | 003424 FREE LIST 1: ORDER (SIZE) | NUMBER | POOL 0 | POOL 1 | POOL 2 -- -- -- -- -- -- -- -- 12 (016384K) | 000000 | 000000 | 000000 11 (008192K) | 000000 | 000000 | 000000 10 (004096K) | 000000 | 000000 | 000000 09 (002048K) | 000000 | 000000 | 000000 08 (001024K) | 000000 | 000000 | 000000 07 (000512K) | 000000 | 000000 | 000000 06 (000256K) | 000001 | 000000 | 000000 05 (000128K) | 000001 | 000000 | 000000 04 (000064K) | 000001 | 000000 | 000000 03 (000032K) | 000002 | 000000 | 000000 02 (000016K) | 000000 | 000000 | 000000 01 (000008K) | 000001 | 000000 | 000000 00 (000004K) | 000002 | 000000 | 000000 vm.reserv.reclaimed: 0 vm.reserv.partpopq: LEVEL SIZE NUMBER -00001: 432112K, 000734 vm.reserv.freed: 1850255 vm.reserv.broken: 436 vm.idlezero_enable: 0 vm.kvm_free: 546738008064 vm.kvm_size: 549755809792 vm.pmap.pmap_collect_active: 0 vm.pmap.pmap_collect_inactive: 0 vm.pmap.pv_entry_spare: 3523 vm.pmap.pv_entry_allocs: 490764507 vm.pmap.pv_entry_frees: 490746022 vm.pmap.pc_chunk_tryfail: 0 vm.pmap.pc_chunk_frees: 3217597 vm.pmap.pc_chunk_allocs: 3217728 vm.pmap.pc_chunk_count: 131 vm.pmap.pv_entry_count: 18485 vm.pmap.pdpe.demotions: 0 vm.pmap.pde.promotions: 183512 vm.pmap.pde.p_failures: 3208458 vm.pmap.pde.mappings: 0 vm.pmap.pde.demotions: 135426 vm.pmap.shpgperproc: 200 vm.pmap.pv_entry_max: 2746951 vm.pmap.pg_ps_enabled: 1 > > >I have tested the two system drives independently (currently a zfs > >mirror), so it is not likely to be an hdd issue. > > How did you test them and what were the results? > > Do you know what revision your > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c is? > (Or when/how did you last upgrade your source tree). I did a make update just before the buildworld, the same day as the original message post. > > -- > Peter Jeremy > > =A0application_pgp-signature_part > < 1KViewDownload In case it helps, here kldstat output: Id Refs Address Size Name 1 32 0xffffffff80100000 d7b280 kernel 2 1 0xffffffff80e7c000 19e1f8 zfs.ko 3 2 0xffffffff8101b000 3860 opensolaris.ko 4 1 0xffffffff8101f000 f090 aio.ko 5 1 0xffffffff81030000 fe68 ahci.ko 6 1 0xffffffff81222000 39f7 linprocfs.ko 7 1 0xffffffff81226000 1cc4d linux.ko 8 1 0xffffffff81243000 216 green_saver.ko 9 1 0xffffffff81244000 86c coretemp.ko From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 08:12:39 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99C061065670 for ; Wed, 22 Sep 2010 08:12:39 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail35.syd.optusnet.com.au (mail35.syd.optusnet.com.au [211.29.133.51]) by mx1.freebsd.org (Postfix) with ESMTP id 28F748FC17 for ; Wed, 22 Sep 2010 08:12:38 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c220-239-116-103.belrs4.nsw.optusnet.com.au [220.239.116.103]) by mail35.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id o8M8CW3P026961 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Sep 2010 18:12:34 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.4/8.14.4) with ESMTP id o8M8CV6A021169; Wed, 22 Sep 2010 18:12:31 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.4/8.14.4/Submit) id o8M8CUQ1021168; Wed, 22 Sep 2010 18:12:30 +1000 (EST) (envelope-from peter) Date: Wed, 22 Sep 2010 18:12:30 +1000 From: Peter Jeremy To: Bryce Message-ID: <20100922081230.GA20489@server.vk2pj.dyndns.org> References: <10b0bdef-2bb1-44c8-9ffb-7d3167147a4f@q2g2000vbk.googlegroups.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="r5Pyd7+fXNt84Ff3" Content-Disposition: inline In-Reply-To: <10b0bdef-2bb1-44c8-9ffb-7d3167147a4f@q2g2000vbk.googlegroups.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable@freebsd.org Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 08:12:39 -0000 --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2010-Sep-21 20:02:09 -0700, Bryce wrote: >On Sep 20, 6:17=A0am, peterjer...@acm.org (Peter Jeremy) wrote: >> On 2010-Sep-18 08:32:32 -0500, Bryce Edwards wrote: >> >> >I have a Supermicro with the C7X58 motherboard and an i7 930 cpu, and >> >it is nowhere near the performance it should be. =A0A buildworld just >> >took 22.5 hours! >> - md5 -t =A0 [this will help determine if the problem is lack of CPU] > >MD5 time trial. Digesting 100000 10000-byte blocks ... done >Digest =3D 766a2bb5d24bddae466c572bcabca3ee >Time =3D 5.421381 seconds >Speed =3D 184454848.000000 bytes/second I think something is badly wrong here. That's less than 1/2 the speed of my Athlon 4850e (2.5GHz) and only 60% more than my Atom N270. None of the other figures you posted look anomolous. Are you sure the CPU is actually running at full speed and you haven't done something like disable the caches in BIOS? --=20 Peter Jeremy --r5Pyd7+fXNt84Ff3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEARECAAYFAkyZum4ACgkQ/opHv/APuIfbZgCfZQ1nUw1+dMSlGdmU6zHOIlCI KnUAniULSbKXJRcyWejXdCcWPVk85fN7 =MSiL -----END PGP SIGNATURE----- --r5Pyd7+fXNt84Ff3-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 08:30:36 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B30701065672 for ; Wed, 22 Sep 2010 08:30:36 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3B6108FC17 for ; Wed, 22 Sep 2010 08:30:35 +0000 (UTC) Received: by fxm9 with SMTP id 9so172563fxm.13 for ; Wed, 22 Sep 2010 01:30:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=OoIcEIj1vB/tWoN6hMNlbCEyATae4ed0eyfYJbV8tAE=; b=bvYefj9yDgWBZLJDYnQmcje45ANwBqxiv/us4lbcb2iTglF9Qx6uD86FOXEAst7laf 07qKTIhOp9buULu8U+PVpnf+JB2cRI9kTiWyq+9KM5I4qfpiOlSP0HOvln1yYYaB1lKl AI3Qsz4eD8c/qT+iOMcYK/uw9Mdn+4Lj0SIGw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=L6mwc1dq4JapMQ1DrVuSQIz7ZrWLJ5ylcY8TNpl8w11d3ZKGqfoQLna9ys2nG0GclU fejgTAquKo+CUAKYkqGsEPy2e9G+JGNqZI25affSTAujISr5MAmdT17A+OJgLJVAM7G0 VpUgDgGw/v2MhblTyXInizoshlyZna5zflD28= MIME-Version: 1.0 Received: by 10.223.119.69 with SMTP id y5mr7281659faq.100.1285144233764; Wed, 22 Sep 2010 01:30:33 -0700 (PDT) Received: by 10.223.57.20 with HTTP; Wed, 22 Sep 2010 01:30:33 -0700 (PDT) In-Reply-To: <20100922081230.GA20489@server.vk2pj.dyndns.org> References: <10b0bdef-2bb1-44c8-9ffb-7d3167147a4f@q2g2000vbk.googlegroups.com> <20100922081230.GA20489@server.vk2pj.dyndns.org> Date: Wed, 22 Sep 2010 03:30:33 -0500 Message-ID: From: Adam Vande More To: Peter Jeremy Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org, Bryce Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 08:30:36 -0000 On Wed, Sep 22, 2010 at 3:12 AM, Peter Jeremy wrote: > I think something is badly wrong here. That's less than 1/2 the speed > of my Athlon 4850e (2.5GHz) and only 60% more than my Atom N270. None > of the other figures you posted look anomolous. Are you sure the CPU > is actually running at full speed and you haven't done something like > disable the caches in BIOS? > FWIW: FreeBSD galacticdominator.com 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #1: Sun Jun 20 21:05:37 CDT 2010 adam@galacticdominator.com:/usr/obj/usr/src/sys/GENERIC amd64 CPU: Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz (2940.64-MHz K8-class CPU) MD5 time trial. Digesting 100000 10000-byte blocks ... done Digest = 766a2bb5d24bddae466c572bcabca3ee Time = 2.012719 seconds Speed = 496840352.000000 bytes/second vmstat -i interrupt total rate irq16: vgapci0+ 10720642 54 irq18: fwohci0 2 0 irq23: ehci1 623712 3 cpu0: timer 393496151 1996 irq256: hdac0 8063581 40 irq257: re0 4136265 20 irq259: ahci1 1925783 9 cpu1: timer 393494902 1996 cpu6: timer 393494606 1996 cpu5: timer 393494653 1996 cpu7: timer 393494701 1996 cpu4: timer 393494785 1996 cpu3: timer 393494732 1996 cpu2: timer 393494404 1996 Total 3173428919 16102 His interrupts seem high compared to this setup, but I don't what expected values should be. -- Adam Vande More From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 08:43:12 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AF851065672 for ; Wed, 22 Sep 2010 08:43:12 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta14.emeryville.ca.mail.comcast.net (qmta14.emeryville.ca.mail.comcast.net [76.96.27.212]) by mx1.freebsd.org (Postfix) with ESMTP id 7CB378FC14 for ; Wed, 22 Sep 2010 08:43:12 +0000 (UTC) Received: from omta24.emeryville.ca.mail.comcast.net ([76.96.30.92]) by qmta14.emeryville.ca.mail.comcast.net with comcast id 9khb1f0041zF43QAEkjCCc; Wed, 22 Sep 2010 08:43:12 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta24.emeryville.ca.mail.comcast.net with comcast id 9kjB1f0023LrwQ28kkjBRX; Wed, 22 Sep 2010 08:43:11 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id E5D5A9B418; Wed, 22 Sep 2010 01:43:10 -0700 (PDT) Date: Wed, 22 Sep 2010 01:43:10 -0700 From: Jeremy Chadwick To: Adam Vande More Message-ID: <20100922084310.GA6760@icarus.home.lan> References: <10b0bdef-2bb1-44c8-9ffb-7d3167147a4f@q2g2000vbk.googlegroups.com> <20100922081230.GA20489@server.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Bryce , freebsd-stable@freebsd.org, Peter Jeremy Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 08:43:12 -0000 On Wed, Sep 22, 2010 at 03:30:33AM -0500, Adam Vande More wrote: > On Wed, Sep 22, 2010 at 3:12 AM, Peter Jeremy wrote: > > > I think something is badly wrong here. That's less than 1/2 the speed > > of my Athlon 4850e (2.5GHz) and only 60% more than my Atom N270. None > > of the other figures you posted look anomolous. Are you sure the CPU > > is actually running at full speed and you haven't done something like > > disable the caches in BIOS? > > > > FWIW: > > FreeBSD galacticdominator.com 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #1: Sun > Jun 20 21:05:37 CDT 2010 > adam@galacticdominator.com:/usr/obj/usr/src/sys/GENERIC > amd64 > CPU: Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz (2940.64-MHz K8-class > CPU) > > MD5 time trial. Digesting 100000 10000-byte blocks ... done > Digest = 766a2bb5d24bddae466c572bcabca3ee > Time = 2.012719 seconds > Speed = 496840352.000000 bytes/second > > vmstat > -i > > interrupt total > rate > > irq16: vgapci0+ 10720642 54 > irq18: fwohci0 2 0 > irq23: ehci1 623712 3 > cpu0: timer 393496151 1996 > irq256: hdac0 8063581 40 > irq257: re0 4136265 20 > irq259: ahci1 1925783 9 > cpu1: timer 393494902 1996 > cpu6: timer 393494606 1996 > cpu5: timer 393494653 1996 > cpu7: timer 393494701 1996 > cpu4: timer 393494785 1996 > cpu3: timer 393494732 1996 > cpu2: timer 393494404 1996 > Total 3173428919 16102 > > His interrupts seem high compared to this setup, but I don't what expected > values should be. How are his interrupt rates "higher" than yours? If you're focused on the cpuX entries, don't be. To the OP: 1) I don't see how/why USB Legacy support would have anything to do with your problem (meaning: you stated that things "improved a little" if you disabled USB Legacy support in the BIOS, which makes no sense given what that option does). 2) There's been a discussion on -stable about FreeBSD incorrectly determining different kinds of CPU characteristics on newer processors like the i7, with HTT in use. I can dig up the thread if you'd like. It does include a patch. 3) Reset the BIOS settings to Factory Defaults ("Load Setup Defaults" or the like), and then write down whatever you change, then post the changes here. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 09:43:11 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19628106566C for ; Wed, 22 Sep 2010 09:43:11 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail17.syd.optusnet.com.au (mail17.syd.optusnet.com.au [211.29.132.198]) by mx1.freebsd.org (Postfix) with ESMTP id 7FFED8FC08 for ; Wed, 22 Sep 2010 09:43:10 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c220-239-116-103.belrs4.nsw.optusnet.com.au [220.239.116.103]) by mail17.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id o8M9h4j2032264 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Sep 2010 19:43:06 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.4/8.14.4) with ESMTP id o8M9h4s5021806; Wed, 22 Sep 2010 19:43:04 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.4/8.14.4/Submit) id o8M9h3OL021805; Wed, 22 Sep 2010 19:43:03 +1000 (EST) (envelope-from peter) Date: Wed, 22 Sep 2010 19:43:03 +1000 From: Peter Jeremy To: Bryce Message-ID: <20100922094303.GB21399@server.vk2pj.dyndns.org> References: <10b0bdef-2bb1-44c8-9ffb-7d3167147a4f@q2g2000vbk.googlegroups.com> <20100922081230.GA20489@server.vk2pj.dyndns.org> <20100922084310.GA6760@icarus.home.lan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gatW/ieO32f1wygP" Content-Disposition: inline In-Reply-To: <20100922084310.GA6760@icarus.home.lan> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable@freebsd.org Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 09:43:11 -0000 --gatW/ieO32f1wygP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2010-Sep-22 01:43:10 -0700, Jeremy Chadwick w= rote: >To the OP: =2E.. 4) Check the CPU core temperature (via coretemp(4) or similar) and make sure the heatsink is correctly attached. --=20 Peter Jeremy --gatW/ieO32f1wygP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEARECAAYFAkyZz6cACgkQ/opHv/APuIfYcQCguvdglAbehNcWeNGjaDHnJSPb OVkAni6ffDdd4oSduj/lRhtjxtaiaPby =ctt6 -----END PGP SIGNATURE----- --gatW/ieO32f1wygP-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 09:51:04 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13ECB106564A for ; Wed, 22 Sep 2010 09:51:04 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 676D08FC18 for ; Wed, 22 Sep 2010 09:51:03 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id o8M9p0mU012414; Wed, 22 Sep 2010 19:51:01 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Wed, 22 Sep 2010 19:51:00 +1000 (EST) From: Ian Smith To: Ted Faber In-Reply-To: <20100226013551.GA67689@zod.isi.edu> Message-ID: <20100922181029.D11124@sola.nimnet.asn.au> References: <20100224165203.GA10423@zod.isi.edu> <20100225152711.M16250@sola.nimnet.asn.au> <20100226013551.GA67689@zod.isi.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org Subject: Re: resume slow on Thinkpad T42 FreeBSD 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 09:51:04 -0000 On Thu, 25 Feb 2010 17:35:51 -0800, Ted Faber wrote: > On Thu, Feb 25, 2010 at 05:18:22PM +1100, Ian Smith wrote: > > On Wed, 24 Feb 2010, Ted Faber wrote: > > > > > I'm running a recent (yesterday) FreeBSD 8-STABLE on my T42. When I > > > resume from suspend the fan starts screen returns immediately (to text > > > mode) and then the system idles for about a minute until it shakes > > > itself awake. The keyboard LEDs cycle, the disk runs and X returns. > > > > Good to hear, Ted .. I thought it was just me :) Your symptoms appear > > entirely identical to mine as posted on Dec 13th to mobile@ and acpi@, > > see thread 'Thinkpad T23 60 second stall on resuming 8.0-RELEASE/i386' > > http://lists.freebsd.org/pipermail/freebsd-acpi/2009-December/006192.html > > > > Nate Lawson thought it an ATA rather than an ACPI problem and I assume > > he's likely right, but I've had too much $work (and too little solar > > power during an exceptionally wet summer) to follow it up. > > Yeah, that sounds like the problem. I'll poke at ata if I get the > chance, but that seems unlikely for a while. > > > In case relevant, my ad0 is a 120GB Fujitsu MHV2120AH, but your TOSHIBA > > MK4026GAX looks more likely to be the original disk? > > Likely, but I can't be sure. I bought it used. > > > > > I've no time to spend on hunting this now, and know nothing about ATA > > anyway, assuming that's where the problem lies, but I'll be quick to > > test any suggested solution/s! > > Like I say, assuming I ever get free time, I'll have a look. Brought my Thinkpad T23 (actually a replacement, similar model, same HD) to '8.1-STABLE #0: Sun Sep 5 15:53:00 EST 2010' but this issue persists, as it does if booted from 8.1-i386-memstick, HD present but not mounted; this one has the CDRW rather than the original's DVD-ROM, if relevant. Before excruciating detail of the issue in mobile@ and acpi@ again in hope of debugging hints, have you (Ted or anyone) any further news on Thinkpad T-series (or other) 60 second stalls/freezes on S3 resume? [Please read the abovementioned thread before asking any questions] cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 09:55:07 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 655451065675 for ; Wed, 22 Sep 2010 09:55:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [IPv6:2001:4068:10::3]) by mx1.freebsd.org (Postfix) with ESMTP id EAAD88FC1A for ; Wed, 22 Sep 2010 09:55:06 +0000 (UTC) Received: from localhost (amavis.fra.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id F13F941C7A4; Wed, 22 Sep 2010 11:55:05 +0200 (CEST) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([192.168.74.103]) by localhost (amavis.fra.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id wveCk0OIZ3Xg; Wed, 22 Sep 2010 11:55:05 +0200 (CEST) Received: by mail.cksoft.de (Postfix, from userid 66) id 82F7E41C7B5; Wed, 22 Sep 2010 11:55:05 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 4DD2C4448FA; Wed, 22 Sep 2010 09:53:22 +0000 (UTC) Date: Wed, 22 Sep 2010 09:53:22 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: "S.N.Grigoriev" In-Reply-To: <14311284977257@web78.yandex.ru> Message-ID: <20100922095218.F31898@maildrop.int.zabbadoz.net> References: <4C7D01F7.4010003@zirakzigil.org> <265911284972128@web78.yandex.ru> <4C972B3E.2050108@tefre.com> <14311284977257@web78.yandex.ru> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: How to terminate a lot of jails correctly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 09:55:07 -0000 On Mon, 20 Sep 2010, S.N.Grigoriev wrote: > thank you for your tip. The only drawback of that approche is absence of > ability to calculate a timeout. Try and error only. Well, you could do a try-run just shutiing down all your jails by time sh /etc/rc.d/jail stop measuring the time it takes and maybe add a bit for extra safety? /bz -- Bjoern A. Zeeb Welcome a new stage of life. From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 10:05:07 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14E78106566C; Wed, 22 Sep 2010 10:05:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [IPv6:2001:4068:10::3]) by mx1.freebsd.org (Postfix) with ESMTP id C2C0D8FC19; Wed, 22 Sep 2010 10:05:06 +0000 (UTC) Received: from localhost (amavis.fra.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 21C6441C7AE; Wed, 22 Sep 2010 12:05:06 +0200 (CEST) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([192.168.74.103]) by localhost (amavis.fra.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id 4ZRqtMWItk00; Wed, 22 Sep 2010 12:05:05 +0200 (CEST) Received: by mail.cksoft.de (Postfix, from userid 66) id 99E7841C75E; Wed, 22 Sep 2010 12:05:05 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id AC50E4448FA; Wed, 22 Sep 2010 10:02:08 +0000 (UTC) Date: Wed, 22 Sep 2010 10:02:08 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Doug Barton In-Reply-To: <20100921193101.GA95238@night.db.net> Message-ID: <20100922095724.C31898@maildrop.int.zabbadoz.net> References: <4C98F433.6070506@FreeBSD.org> <20100921191517.AF60A1CC3D@ptavv.es.net> <20100921193101.GA95238@night.db.net> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Diane Bruce , Mark Kamichoff , freebsd-stable@freebsd.org Subject: Re: BIND9 built w/--disable-ipv6 on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 10:05:07 -0000 On Tue, 21 Sep 2010, Diane Bruce wrote: >>> |> | why don't we want IPv6 enabled by default on new BIND installations? >>> |> >>> |> It has to do with whether or not IPv6 support is compiled into the >>> |> FreeBSD base system which is compiling BIND. If the configure option > ... >>> If I'm still alive when IPv6 is the norm and IPv4 is the exception, I >>> promise to give it another look. :) > > IPv6 is more prevalent than you think. I can't understand the illogic > of turning it off. Can't we just do what lib/bind/config.mk already does? Index: usr.sbin/named/Makefile =================================================================== --- usr.sbin/named/Makefile (revision 211503) +++ usr.sbin/named/Makefile (working copy) @@ -9,7 +9,10 @@ SRCDIR= ${BIND_DIR}/bin/named PROG= named -CONFIGARGS='--prefix=/usr' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--enable-threads' '--disable-ipv6' '--enable-getifaddrs' '--disable-linux-caps' '--with-openssl=/usr' '--with-randomdev=/dev/random' +CONFIGARGS='--prefix=/usr' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--enable-threads' '--enable-getifaddrs' '--disable-linux-caps' '--with-openssl=/usr' '--with-randomdev=/dev/random' +.if ${MK_INET6_SUPPORT} == "no" +CONFIGARGS+='--disable-ipv6' +.endif # Optional features .if ${MK_BIND_LARGE_FILE} == "yes" and leave it to the user to build world without INET6 support if (s)he build the kernel without it? Thanks, /bz -- Bjoern A. Zeeb Welcome a new stage of life. From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 11:20:03 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26213106564A for ; Wed, 22 Sep 2010 11:20:03 +0000 (UTC) (envelope-from bartsch@dssgmbh.de) Received: from mail.incore.de (dss.incore.de [195.145.1.138]) by mx1.freebsd.org (Postfix) with ESMTP id D8CB58FC17 for ; Wed, 22 Sep 2010 11:20:02 +0000 (UTC) Received: from localhost (inetmail.dmz [10.3.0.3]) by mail.incore.de (Postfix) with ESMTP id AA90D6503B; Wed, 22 Sep 2010 13:01:17 +0200 (CEST) X-Virus-Scanned: amavisd-new at incore.de Received: from mail.incore.de ([10.3.0.3]) by localhost (inetmail.dmz [10.3.0.3]) (amavisd-new, port 10024) with LMTP id 4AKA96f+KjOT; Wed, 22 Sep 2010 13:01:16 +0200 (CEST) Received: from mail.incore (fwintern.dmz [10.0.0.253]) by mail.incore.de (Postfix) with ESMTP id 890CD65031; Wed, 22 Sep 2010 13:01:16 +0200 (CEST) Received: from pcbart.incore (pcbart.incore [192.168.0.57]) by mail.incore (Postfix) with ESMTPA id 7F94145085; Wed, 22 Sep 2010 13:01:16 +0200 (CEST) Message-ID: <4C99E1FC.2000902@dssgmbh.de> Date: Wed, 22 Sep 2010 13:01:16 +0200 From: Alfred Bartsch User-Agent: Thunderbird 2.0.0.19 (X11/20090113) MIME-Version: 1.0 To: "S.N.Grigoriev" References: <4C7D01F7.4010003@zirakzigil.org> <265911284972128@web78.yandex.ru> <4C972B3E.2050108@tefre.com> <14311284977257@web78.yandex.ru> In-Reply-To: <14311284977257@web78.yandex.ru> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: How to terminate a lot of jails correctly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 11:20:03 -0000 S.N.Grigoriev wrote: > > 20.09.10, 13:37, "Erik Stian Tefre" : > >>> I use a server (FreeBSD 8.1R amd64) with two dozens of jails configured. >> > I've found out that only a few of them are terminated normally (via >> > /etc/rc.shutdown) during the system shutdown. FreeBSD reports that >> > 20sec interval has elapsed and simply kills all the jails that are not yet >> > terminated. I would like to know in what way can I fix it using the system >> > tools only (not ezjail, Qjail etc). >> >> Increasing rcshutdown_timeout in /etc/rc.conf may help. The default >> value is set to 30 seconds in /etc/defaults/rc.conf. >> > > Erik, > > thank you for your tip. The only drawback of that approche is absence of > ability to calculate a timeout. Try and error only. > to avoid such trial and error, we always set 'rcshutdown_timeout=""' in /etc/rc.conf on all our servers. "man init" reads: When shutting down the machine, init will try to run the /etc/rc.shutdown script. This script can be used to cleanly terminate specific programs such as innd (the InterNetNews server). If this script does not terminate within 120 seconds, init will terminate it. The timeout can be configured via the sysctl(8) variable kern.init_shutdown_timeout. So disabling the variable 'rcshutdown_timeout' should expand the timeout of every single rc-script to a total of 2 minutes for all rc-scripts. If this is not sufficient, try increasing "kern.init_shutdown_timeout". -- Alfred Bartsch From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 13:28:16 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 642571065672 for ; Wed, 22 Sep 2010 13:28:16 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id A1F4A8FC19 for ; Wed, 22 Sep 2010 13:28:15 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id o8MDS2mo087571 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Sep 2010 16:28:02 +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.4/8.14.4) with ESMTP id o8MDS1rX042482; Wed, 22 Sep 2010 16:28:01 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id o8MDS10t042481; Wed, 22 Sep 2010 16:28: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: Wed, 22 Sep 2010 16:28:01 +0300 From: Kostik Belousov To: Mario Sergio Fujikawa Ferreira Message-ID: <20100922132801.GV2389@deviant.kiev.zoral.com.ua> References: <20100919222837.70629.qmail@exxodus.fedaykin.here> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="f+yJoTRZrSg+ZFQF" Content-Disposition: inline In-Reply-To: <20100919222837.70629.qmail@exxodus.fedaykin.here> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-stable@freebsd.org Subject: Re: Panic with chromium and 8.1-STABLE (Thu Sep 16 09:52:17 BRT 2010) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 13:28:16 -0000 --f+yJoTRZrSg+ZFQF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 19, 2010 at 07:28:13PM -0300, Mario Sergio Fujikawa Ferreira wr= ote: > Hi, >=20 > I've just began trying chrome web browser from > http://chromium.hybridsource.org/ but it triggered 2 panics on my > 8.1-STABLE system. >=20 > $ uname -a > FreeBSD exxodus.fedaykin.here 8.1-STABLE FreeBSD 8.1-STABLE #26: Thu Sep = 16 09:52:17 BRT 2010 lioux@exxodus:/usr/obj/usr/src/sys/LIOUX amd64 >=20 > The panic information is: >=20 > ------------ > panic: vm_page_unwire: invalid wire count: 0 > cpuid =3D 0 > KDB: enter: panic >=20 > 0xffffff006ecce000: tag ufs, type VREG > usecount 1, writecount 1, refcount 4 mountedhere 0 > flags () > v_object 0xffffff0151489870 ref 0 pages 8 > lock type ufs: EXCL by thread 0xffffff00200947c0 (pid 25025) > ino 119526591, on dev ufs/fsusr >=20 > 0xffffff011107f938: tag ufs, type VREG > usecount 0, writecount 0, refcount 4 mountedhere 0 > flags (VV_NOSYNC|VI_DOINGINACT) > v_object 0xffffff0151f7f870 ref 0 pages 1284 > lock type ufs: EXCL by thread 0xffffff01882cc7c0 (pid 26689) > ino 263, on dev md0 > ------------ >=20 > I've made available 2 ddb textdumps at: >=20 > http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.0 > http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.1 >=20 > I was able to use chrome prior to this latest kernel update. > Now, I can reproduce a kernel panic even browsing www.google.com >=20 > Please, let me know if I can provide any further information. Does it panic if you remove ZERO_COPY_SOCKETS option from the kernel config ? --f+yJoTRZrSg+ZFQF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkyaBGEACgkQC3+MBN1Mb4hI2wCgrQdUdsSRfWaBCi+ZwZnyImVR MBsAoOiIvNSjEW1fx4vMecFJryshh5Jy =y+6f -----END PGP SIGNATURE----- --f+yJoTRZrSg+ZFQF-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 13:50:29 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF41610656A3 for ; Wed, 22 Sep 2010 13:50:29 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 061CB8FC1A for ; Wed, 22 Sep 2010 13:50:28 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id o8MDoGo4026381; Wed, 22 Sep 2010 23:50:17 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Wed, 22 Sep 2010 23:50:16 +1000 (EST) From: Ian Smith To: Peter Jeremy In-Reply-To: <20100922081230.GA20489@server.vk2pj.dyndns.org> Message-ID: <20100922230552.D11124@sola.nimnet.asn.au> References: <10b0bdef-2bb1-44c8-9ffb-7d3167147a4f@q2g2000vbk.googlegroups.com> <20100922081230.GA20489@server.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1641429527-1285160925=:11124" Content-ID: <20100922231016.A11124@sola.nimnet.asn.au> Cc: Adam Vande More , Bryce , freebsd-stable@freebsd.org Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 13:50:29 -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-1641429527-1285160925=:11124 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Transfer-Encoding: 8BIT Content-ID: <20100922231016.R11124@sola.nimnet.asn.au> On Wed, 22 Sep 2010 18:12:30 +1000, Peter Jeremy wrote: > On 2010-Sep-21 20:02:09 -0700, Bryce wrote: > >On Sep 20, 6:17 am, peterjer...@acm.org (Peter Jeremy) wrote: > >> On 2010-Sep-18 08:32:32 -0500, Bryce Edwards wrote: > >> > >> >I have a Supermicro with the C7X58 motherboard and an i7 930 cpu, and > >> >it is nowhere near the performance it should be.  A buildworld just > >> >took 22.5 hours! > > >> - md5 -t   [this will help determine if the problem is lack of CPU] > > > >MD5 time trial. Digesting 100000 10000-byte blocks ... done > >Digest = 766a2bb5d24bddae466c572bcabca3ee > >Time = 5.421381 seconds > >Speed = 184454848.000000 bytes/second > > I think something is badly wrong here. That's less than 1/2 the speed > of my Athlon 4850e (2.5GHz) and only 60% more than my Atom N270. None > of the other figures you posted look anomolous. Are you sure the CPU > is actually running at full speed and you haven't done something like > disable the caches in BIOS? It seems far more than just CPU performance is awry. Adam's data from his i7 shows 2.7 times Bryce's speed for the md5 -t, maybe a lower EST rate? - but that could no way account for buildworld taking 22.5 hours. Recent buildworld (albeit i386) on my Thinkpad T23 ran just shy of 3.5 hours, without -j on an 1133MHz P3-M, 768MB of 133MHz RAM, 5400rpm UFS disk - with X/KDE running meanwhile (~5-7% CPU penalty). cheers, Ian --0-1641429527-1285160925=:11124-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 13:52:29 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 25280106566C for ; Wed, 22 Sep 2010 13:52:29 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id D09868FC16 for ; Wed, 22 Sep 2010 13:52:28 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 69FC046B51; Wed, 22 Sep 2010 09:52:28 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id DA4458A050; Wed, 22 Sep 2010 09:52:26 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Wed, 22 Sep 2010 09:48:39 -0400 User-Agent: KMail/1.13.5 (FreeBSD/7.3-CBSD-20100819; KDE/4.4.5; amd64; ; ) References: <20100922084310.GA6760@icarus.home.lan> In-Reply-To: <20100922084310.GA6760@icarus.home.lan> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201009220948.39309.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 22 Sep 2010 09:52:27 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Adam Vande More , Bryce , Peter Jeremy , Jeremy Chadwick Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 13:52:29 -0000 On Wednesday, September 22, 2010 4:43:10 am Jeremy Chadwick wrote: > On Wed, Sep 22, 2010 at 03:30:33AM -0500, Adam Vande More wrote: > > On Wed, Sep 22, 2010 at 3:12 AM, Peter Jeremy wrote: > > > > > I think something is badly wrong here. That's less than 1/2 the speed > > > of my Athlon 4850e (2.5GHz) and only 60% more than my Atom N270. None > > > of the other figures you posted look anomolous. Are you sure the CPU > > > is actually running at full speed and you haven't done something like > > > disable the caches in BIOS? > > > > > > > FWIW: > > > > FreeBSD galacticdominator.com 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #1: Sun > > Jun 20 21:05:37 CDT 2010 > > adam@galacticdominator.com:/usr/obj/usr/src/sys/GENERIC > > amd64 > > CPU: Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz (2940.64-MHz K8-class > > CPU) > > > > MD5 time trial. Digesting 100000 10000-byte blocks ... done > > Digest = 766a2bb5d24bddae466c572bcabca3ee > > Time = 2.012719 seconds > > Speed = 496840352.000000 bytes/second > > > > vmstat > > -i > > > > interrupt total > > rate > > > > irq16: vgapci0+ 10720642 54 > > irq18: fwohci0 2 0 > > irq23: ehci1 623712 3 > > cpu0: timer 393496151 1996 > > irq256: hdac0 8063581 40 > > irq257: re0 4136265 20 > > irq259: ahci1 1925783 9 > > cpu1: timer 393494902 1996 > > cpu6: timer 393494606 1996 > > cpu5: timer 393494653 1996 > > cpu7: timer 393494701 1996 > > cpu4: timer 393494785 1996 > > cpu3: timer 393494732 1996 > > cpu2: timer 393494404 1996 > > Total 3173428919 16102 > > > > His interrupts seem high compared to this setup, but I don't what expected > > values should be. > > How are his interrupt rates "higher" than yours? If you're focused on > the cpuX entries, don't be. > > To the OP: > > 1) I don't see how/why USB Legacy support would have anything to do with > your problem (meaning: you stated that things "improved a little" if you > disabled USB Legacy support in the BIOS, which makes no sense given what > that option does). Actually, if he does not have any USB drivers loaded then it means that the BIOS is triggering an SMI# at least once a second. It would not explain all of his problem, but it might have a small effect. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 13:52:30 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F9D61065673; Wed, 22 Sep 2010 13:52:30 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 1BB7D8FC1F; Wed, 22 Sep 2010 13:52:30 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id ADD7D46B52; Wed, 22 Sep 2010 09:52:29 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id B81018A051; Wed, 22 Sep 2010 09:52:28 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Wed, 22 Sep 2010 09:50:32 -0400 User-Agent: KMail/1.13.5 (FreeBSD/7.3-CBSD-20100819; KDE/4.4.5; amd64; ; ) References: <4C98F433.6070506@FreeBSD.org> <20100921193101.GA95238@night.db.net> <20100922095724.C31898@maildrop.int.zabbadoz.net> In-Reply-To: <20100922095724.C31898@maildrop.int.zabbadoz.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201009220950.32294.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 22 Sep 2010 09:52:28 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: "Bjoern A. Zeeb" , Diane Bruce , Doug Barton , Mark Kamichoff Subject: Re: BIND9 built w/--disable-ipv6 on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 13:52:30 -0000 On Wednesday, September 22, 2010 6:02:08 am Bjoern A. Zeeb wrote: > On Tue, 21 Sep 2010, Diane Bruce wrote: > > >>> |> | why don't we want IPv6 enabled by default on new BIND installations? > >>> |> > >>> |> It has to do with whether or not IPv6 support is compiled into the > >>> |> FreeBSD base system which is compiling BIND. If the configure option > > ... > >>> If I'm still alive when IPv6 is the norm and IPv4 is the exception, I > >>> promise to give it another look. :) > > > > IPv6 is more prevalent than you think. I can't understand the illogic > > of turning it off. > > Can't we just do what lib/bind/config.mk already does? > > Index: usr.sbin/named/Makefile > =================================================================== > --- usr.sbin/named/Makefile (revision 211503) > +++ usr.sbin/named/Makefile (working copy) > @@ -9,7 +9,10 @@ SRCDIR= ${BIND_DIR}/bin/named > > PROG= named > > -CONFIGARGS='--prefix=/usr' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--enable-threads' '--disable-ipv6' '--enable-getifaddrs' '-- disable-linux-caps' '--with-openssl=/usr' '--with-randomdev=/dev/random' > +CONFIGARGS='--prefix=/usr' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--enable-threads' '--enable-getifaddrs' '--disable-linux-caps' '--with-openssl=/usr' '--with-randomdev=/dev/random' > +.if ${MK_INET6_SUPPORT} == "no" > +CONFIGARGS+='--disable-ipv6' > +.endif > > # Optional features > .if ${MK_BIND_LARGE_FILE} == "yes" > > and leave it to the user to build world without INET6 support if (s)he > build the kernel without it? Actually, I frequently build custom kernels w/o INET6, but don't necessarily disable INET6 for the world build. However, why can't BIND just be fixed to have sane behavior if the kernel doesn't support INET6? Other applications like sendmail don't need this sort of special treatment, they just don't use IPv6 if it isn't present. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 14:26:19 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86E5C106564A for ; Wed, 22 Sep 2010 14:26:19 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3BC958FC13 for ; Wed, 22 Sep 2010 14:26:18 +0000 (UTC) Received: by gyg4 with SMTP id 4so213214gyg.13 for ; Wed, 22 Sep 2010 07:26:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=1zrJ4wGax9oY8i4cnK75ZBgbCb61rtE2hPPtWglJabM=; b=g9J2XrLHo29uf45WjQpD5hCrny+os1rp0rhLIkKx9ahE09Kz4ooYqjfE85SaNkVMiN WZD+DzJZ2GMHtVpkyCu+2JJieSesN74+qmNPyvcOdBwTHGqkdzeaEQOlcAjlcBakPk4g CTpuYN+nYXUiIhSfONAMm2UQj/BLeqRL9nm+E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=hZoE880MwThoEqrwDz9EsI4ilolXJUUpYboDm2eLu6A7E6RN0uX8MEoCCmtAX8YVfM elofnHfREJLREjzciOp0ZJK3Z7gh/+iHcbAIXTvvQbqwTFp0ld+TTYDqOrqlBcUSr4Xk T0/Umo3iNukyWAFpqk2BdsXTKandPN8vnUrKc= MIME-Version: 1.0 Received: by 10.229.10.200 with SMTP id q8mr111751qcq.288.1285165049795; Wed, 22 Sep 2010 07:17:29 -0700 (PDT) Received: by 10.229.236.15 with HTTP; Wed, 22 Sep 2010 07:17:29 -0700 (PDT) In-Reply-To: <20100922230552.D11124@sola.nimnet.asn.au> References: <10b0bdef-2bb1-44c8-9ffb-7d3167147a4f@q2g2000vbk.googlegroups.com> <20100922081230.GA20489@server.vk2pj.dyndns.org> <20100922230552.D11124@sola.nimnet.asn.au> Date: Wed, 22 Sep 2010 15:17:29 +0100 Message-ID: From: Tom Evans To: Ian Smith Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Adam Vande More , Bryce , freebsd-stable@freebsd.org, Peter Jeremy Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 14:26:19 -0000 On Wed, Sep 22, 2010 at 2:50 PM, Ian Smith wrote: > It seems far more than just CPU performance is awry. =C2=A0Adam's data fr= om > his i7 shows 2.7 times Bryce's speed for the md5 -t, maybe a lower EST > rate? - but that could no way account for buildworld taking 22.5 hours. > > Recent buildworld (albeit i386) on my Thinkpad T23 ran just shy of 3.5 > hours, without -j on an 1133MHz P3-M, 768MB of 133MHz RAM, 5400rpm UFS > disk - with X/KDE running meanwhile (~5-7% CPU penalty). > > cheers, Ian md5 -t is quite a small benchmark, even with his misfunctioning CPU it took <6 seconds to complete. If his problem is a misapplied heatsink/fan, then his CPU could be throttling when it gets hot, the hotter it gets the more it throttles, which could explain his massive buildworld walltime. Perhaps running something like: apply -0 "md5 -t" `jot 10` would display a notable difference. Intel chips are quite good at running without much cooling and not dieing, using thermal throttling to preserve the CPU. Cheers Tom From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 14:59:27 2010 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9C85106566C for ; Wed, 22 Sep 2010 14:59:27 +0000 (UTC) (envelope-from marck@FreeBSD.org) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id 5A0FE8FC16 for ; Wed, 22 Sep 2010 14:59:26 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.4/8.14.4) with ESMTP id o8MEgFe5055231 for ; Wed, 22 Sep 2010 18:42:15 +0400 (MSD) (envelope-from marck@FreeBSD.org) Date: Wed, 22 Sep 2010 18:42:15 +0400 (MSD) From: Dmitry Morozovsky X-X-Sender: marck@woozle.rinet.ru To: stable@FreeBSD.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (woozle.rinet.ru [0.0.0.0]); Wed, 22 Sep 2010 18:42:15 +0400 (MSD) Cc: Subject: kern/150859: tmpfs on stable/8-amd64 panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 14:59:28 -0000 Dear colleagues, I've finally managed to get good crashdump with tmpfs stressing under ports tinderbox. I've filed kern/150859 Any other info I missed to track the issue further? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 15:00:33 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 319471065670 for ; Wed, 22 Sep 2010 15:00:33 +0000 (UTC) (envelope-from nickolasbug@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id D19658FC1A for ; Wed, 22 Sep 2010 15:00:32 +0000 (UTC) Received: by qyk4 with SMTP id 4so939063qyk.13 for ; Wed, 22 Sep 2010 08:00:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=HYB+UwZxT60lDUPViMErMaQ1MCOZi455/O6w/ZTfucw=; b=V5hl3lVNVqouLD4xIOkXrANt9Z75ohIUqOWd7uldOKXxKqcFcCseAmaODMKbb2J1wP 73BZOckcr2bEta2xvs64FnbM91NuMcggQ7d5h2xzVgbIyEtSXz3sST8lXys8g4etZA+o aEM0sAl0FBLN1yb8hUd5RB0xQnpmDL1GQd5SE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=PQaNHsXCa/K14aF+Klxk/TBG4kIs93S4cDxgCo6zsijIQ188ed68ZKnw/4RwDThYLI hxx3Fc+PXwib7dUdkw9DD7QC0HXmfbF6vnXB5t8vZAW/WO2sMaJfq6xaeeHYHskS/3sv poQ+pto2rmknFcNP4FBPPpOoZBnMkwfBxgBMg= MIME-Version: 1.0 Received: by 10.224.122.196 with SMTP id m4mr214954qar.105.1285166153722; Wed, 22 Sep 2010 07:35:53 -0700 (PDT) Received: by 10.229.190.212 with HTTP; Wed, 22 Sep 2010 07:35:53 -0700 (PDT) In-Reply-To: References: <10b0bdef-2bb1-44c8-9ffb-7d3167147a4f@q2g2000vbk.googlegroups.com> <20100922081230.GA20489@server.vk2pj.dyndns.org> <20100922230552.D11124@sola.nimnet.asn.au> Date: Wed, 22 Sep 2010 17:35:53 +0300 Message-ID: From: nickolasbug@gmail.com To: Tom Evans Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Adam Vande More , Peter Jeremy , Bryce , Ian Smith , freebsd-stable@freebsd.org Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 15:00:33 -0000 > md5 -t is quite a small benchmark, even with his misfunctioning CPU it > took <6 seconds to complete. > > If his problem is a misapplied heatsink/fan, then his CPU could be > throttling when it gets hot, the hotter it gets the more it throttles, > which could explain his massive buildworld walltime. Perhaps running > something like: > > =A0apply -0 "md5 -t" `jot 10` > > would display a notable difference. You may also run openssl speed or "linpack" test (/usr/ports/math/linpack) or hpl (/usr/ports/benchmarks/hpl) to load your CPU From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 15:32:40 2010 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CFA6106564A for ; Wed, 22 Sep 2010 15:32:40 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1D2448FC08 for ; Wed, 22 Sep 2010 15:32:38 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA03279; Wed, 22 Sep 2010 18:32:37 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4C9A2195.7040606@icyb.net.ua> Date: Wed, 22 Sep 2010 18:32:37 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20100920 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: Dmitry Morozovsky References: In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: stable@FreeBSD.org Subject: Re: kern/150859: tmpfs on stable/8-amd64 panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 15:32:40 -0000 on 22/09/2010 17:42 Dmitry Morozovsky said the following: > Dear colleagues, > > I've finally managed to get good crashdump with tmpfs stressing under ports > tinderbox. > > I've filed kern/150859 Please, in frame 10 print *node and *vp. Thanks! -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 15:34:08 2010 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74E211065673 for ; Wed, 22 Sep 2010 15:34:08 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 746198FC2F for ; Wed, 22 Sep 2010 15:34:07 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA03304; Wed, 22 Sep 2010 18:34:05 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4C9A21ED.9010206@icyb.net.ua> Date: Wed, 22 Sep 2010 18:34:05 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20100920 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: Dmitry Morozovsky References: In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: stable@FreeBSD.org Subject: Re: kern/150859: tmpfs on stable/8-amd64 panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 15:34:08 -0000 on 22/09/2010 17:42 Dmitry Morozovsky said the following: > > Any other info I missed to track the issue further? Yeah, actual panic message never hurts :) -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 16:04:03 2010 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC8291065675 for ; Wed, 22 Sep 2010 16:04:03 +0000 (UTC) (envelope-from marck@FreeBSD.org) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id 41D6D8FC13 for ; Wed, 22 Sep 2010 16:04:02 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.4/8.14.4) with ESMTP id o8MG41XZ066694; Wed, 22 Sep 2010 20:04:01 +0400 (MSD) (envelope-from marck@FreeBSD.org) Date: Wed, 22 Sep 2010 20:04:01 +0400 (MSD) From: Dmitry Morozovsky X-X-Sender: marck@woozle.rinet.ru To: Andriy Gapon In-Reply-To: <4C9A2195.7040606@icyb.net.ua> Message-ID: References: <4C9A2195.7040606@icyb.net.ua> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (woozle.rinet.ru [0.0.0.0]); Wed, 22 Sep 2010 20:04:01 +0400 (MSD) Cc: stable@FreeBSD.org Subject: Re: kern/150859: tmpfs on stable/8-amd64 panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 16:04:03 -0000 On Wed, 22 Sep 2010, Andriy Gapon wrote: AG> on 22/09/2010 17:42 Dmitry Morozovsky said the following: AG> > Dear colleagues, AG> > AG> > I've finally managed to get good crashdump with tmpfs stressing under ports AG> > tinderbox. AG> > AG> > I've filed kern/150859 AG> AG> Please, in frame 10 print *node and *vp. AG> Thanks! (kgdb) up 10 #10 0xffffffff80c24f5e in tmpfs_alloc_vp (mp=0xffffff000a230000, node=0xffffff001f8fa7e0, lkflag=525312, vpp=0xffffff81ddf542f0) at /usr/src/sys/modules/tmpfs/../../fs/tmpfs/tmpfs_subr.c:383 383 panic("tmpfs_alloc_vp: type %p %d", node, (int)node->tn_type); (kgdb) p *node $1 = {tn_entries = {le_next = 0xffffff006357fd20, le_prev = 0xffffff01457602a0}, tn_type = VNON, tn_id = 19, tn_status = 14, tn_size = 0, tn_uid = 0, tn_gid = 0, tn_mode = 1023, tn_flags = 0, tn_links = 0, tn_atime = {tv_sec = 1285154193, tv_nsec = 0}, tn_mtime = {tv_sec = 1285154193, tv_nsec = 0}, tn_ctime = {tv_sec = 1285154193, tv_nsec = 0}, tn_birthtime = {tv_sec = 1284235757, tv_nsec = 0}, tn_gen = 3591316855, tn_vnode = 0x0, tn_interlock = {lock_object = {lo_name = 0xffffffff80c26166 "tmpfs node interlock", lo_flags = 16973824, lo_data = 0, lo_witness = 0x0}, mtx_lock = 4}, tn_vpstate = 1, tn_spec = {tn_rdev = 894943680, tn_dir = {tn_parent = 0xffffff013557c1c0, tn_dirhead = { tqh_first = 0x0, tqh_last = 0xffffff001f8fa8a0}, tn_readdir_lastn = 0, tn_readdir_lastp = 0x0}, tn_link = 0xffffff013557c1c0 "", tn_reg = {tn_aobj = 0xffffff013557c1c0, tn_aobj_pages = 0}, tn_fifo = {tn_fo_read = 0xffffff013557c1c0, tn_fo_write = 0}}} (kgdb) p *vp $2 = {v_type = VNON, v_tag = 0xffffffff80c261b4 "tmpfs", v_op = 0xffffffff80c26260, v_data = 0xffffff001f8fa7e0, v_mount = 0x0, v_nmntvnodes = {tqe_next = 0x0, tqe_prev = 0x0}, v_un = {vu_mount = 0x0, vu_socket = 0x0, vu_cdev = 0x0, vu_fifoinfo = 0x0, vu_yield = 0}, v_hashlist = {le_next = 0x0, le_prev = 0x0}, v_hash = 0, v_cache_src = { lh_first = 0x0}, v_cache_dst = {tqh_first = 0x0, tqh_last = 0xffffff0013258998}, v_cache_dd = 0x0, v_cstart = 0, v_lasta = 0, v_lastw = 0, v_clen = 0, v_lock = { lock_object = {lo_name = 0xffffffff80c261b4 "tmpfs", lo_flags = 91422728, lo_data = 0, lo_witness = 0x0}, lk_lock = 18446742976956241856, lk_timo = 51, lk_pri = 80}, v_interlock = {lock_object = {lo_name = 0xffffffff80566220 "vnode interlock", lo_flags = 16973824, lo_data = 0, lo_witness = 0x0}, mtx_lock = 4}, v_vnlock = 0xffffff00132589d0, v_holdcnt = 1, v_usecount = 1, v_iflag = 0, v_vflag = 0, v_writecount = 0, v_freelist = {tqe_next = 0x0, tqe_prev = 0x0}, v_bufobj = {bo_mtx = { lock_object = {lo_name = 0xffffffff80566230 "bufobj interlock", lo_flags = 16973824, lo_data = 0, lo_witness = 0x0}, mtx_lock = 4}, bo_clean = {bv_hd = {tqh_first = 0x0, tqh_last = 0xffffff0013258a70}, bv_root = 0x0, bv_cnt = 0}, bo_dirty = {bv_hd = {tqh_first = 0x0, tqh_last = 0xffffff0013258a90}, bv_root = 0x0, bv_cnt = 0}, bo_numoutput = 0, bo_flag = 0, bo_ops = 0xffffffff806d1c40, bo_bsize = 4096, bo_object = 0x0, bo_synclist = {le_next = 0x0, le_prev = 0x0}, bo_private = 0xffffff0013258938, __bo_vnode = 0xffffff0013258938}, v_pollinfo = 0x0, v_label = 0x0, v_lockf = 0x0} Actual panic message: panic: tmpfs_alloc_vp: type 0xffffff001f8fa7e0 0 cpuid = 2 KDB: enter: panic -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] --------------------------------------------------------------------------- *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@FreeBSD.org *** --------------------------------------------------------------------------- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 16:43:17 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9F9C1065696 for ; Wed, 22 Sep 2010 16:43:17 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 0BDCF8FC12 for ; Wed, 22 Sep 2010 16:43:16 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id o8MGh6Vg036504; Thu, 23 Sep 2010 02:43:06 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Thu, 23 Sep 2010 02:43:06 +1000 (EST) From: Ian Smith To: Tom Evans In-Reply-To: Message-ID: <20100923012846.V11124@sola.nimnet.asn.au> References: <10b0bdef-2bb1-44c8-9ffb-7d3167147a4f@q2g2000vbk.googlegroups.com> <20100922081230.GA20489@server.vk2pj.dyndns.org> <20100922230552.D11124@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-724426006-1285172803=:11124" Content-ID: <20100923022750.X11124@sola.nimnet.asn.au> Cc: Adam Vande More , Bryce , freebsd-stable@freebsd.org, Peter Jeremy Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 16:43:17 -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-724426006-1285172803=:11124 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Transfer-Encoding: 8BIT Content-ID: <20100923022750.V11124@sola.nimnet.asn.au> On Wed, 22 Sep 2010, Tom Evans wrote: > On Wed, Sep 22, 2010 at 2:50 PM, Ian Smith wrote: > > It seems far more than just CPU performance is awry.  Adam's data from > > his i7 shows 2.7 times Bryce's speed for the md5 -t, maybe a lower EST > > rate? - but that could no way account for buildworld taking 22.5 hours. > > > > Recent buildworld (albeit i386) on my Thinkpad T23 ran just shy of 3.5 > > hours, without -j on an 1133MHz P3-M, 768MB of 133MHz RAM, 5400rpm UFS > > disk - with X/KDE running meanwhile (~5-7% CPU penalty). > > md5 -t is quite a small benchmark, even with his misfunctioning CPU it > took <6 seconds to complete. > > If his problem is a misapplied heatsink/fan, then his CPU could be > throttling when it gets hot, the hotter it gets the more it throttles, > which could explain his massive buildworld walltime. Perhaps running > something like: > > apply -0 "md5 -t" `jot 10` > > would display a notable difference. > > Intel chips are quite good at running without much cooling and not > dieing, using thermal throttling to preserve the CPU. I guess you mean on-package, without p4tcc or ACPI throttle support? >From Bryce's original message: # Disable throttle control (and rely on EIST) hint.p4tcc.0.disabled="1" hint.acpi_throttle.0.disabled="1" which is sensible, and seems to have been applied to all CPUs, but from http://www.bryce.net/files/dmesg.boot we see for each of cpu[0-7]: est0: on cpu0 est0: Invalid id16 (set, cur) = (20, 21) est0: Can't check freq 2667, it may be invalid est0: Invalid id16 (set, cur) = (19, 21) est0: Can't check freq 2533, it may be invalid est0: Invalid id16 (set, cur) = (18, 21) est0: Can't check freq 2400, it may be invalid est0: Invalid id16 (set, cur) = (17, 21) est0: Can't check freq 2267, it may be invalid est0: Invalid id16 (set, cur) = (16, 21) est0: Can't check freq 2133, it may be invalid est0: Invalid id16 (set, cur) = (15, 21) est0: Can't check freq 2000, it may be invalid est0: Invalid id16 (set, cur) = (14, 21) est0: Can't check freq 1867, it may be invalid est0: Invalid id16 (set, cur) = (13, 21) est0: Can't check freq 1733, it may be invalid est0: Invalid id16 (set, cur) = (12, 21) est0: Can't check freq 1600, it may be invalid which looks a bit ominous? What does 'sysctl hw.acpi dev.cpu' say? Running multiple md5s or say 'dd if=/dev/random of=/dev/null bs=1M &' in a short sleep loop echoing "`date` `sysctl -n dev.cpu.0.freq` plus indicative coretemp sysctls might reveal something as it heats up? Surprisingly (?) the dmesg shows no ACPI thermal zones (detected). cheers, Ian --0-724426006-1285172803=:11124-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 17:49:32 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5079610656A7 for ; Wed, 22 Sep 2010 17:49:32 +0000 (UTC) (envelope-from faber@zod.isi.edu) Received: from zod.isi.edu (zod.isi.edu [128.9.168.221]) by mx1.freebsd.org (Postfix) with ESMTP id 32FFF8FC16 for ; Wed, 22 Sep 2010 17:49:31 +0000 (UTC) Received: from zod.isi.edu (localhost [127.0.0.1]) by zod.isi.edu (8.14.4/8.14.4) with ESMTP id o8MHA8lF092128; Wed, 22 Sep 2010 10:10:08 -0700 (PDT) (envelope-from faber@zod.isi.edu) Received: (from faber@localhost) by zod.isi.edu (8.14.4/8.14.4/Submit) id o8MHA8jM092127; Wed, 22 Sep 2010 10:10:08 -0700 (PDT) (envelope-from faber) Date: Wed, 22 Sep 2010 10:10:08 -0700 From: Ted Faber To: Ian Smith Message-ID: <20100922171008.GA92070@zod.isi.edu> References: <20100224165203.GA10423@zod.isi.edu> <20100225152711.M16250@sola.nimnet.asn.au> <20100226013551.GA67689@zod.isi.edu> <20100922181029.D11124@sola.nimnet.asn.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline In-Reply-To: <20100922181029.D11124@sola.nimnet.asn.au> User-Agent: Mutt/1.4.2.3i X-url: http://www.isi.edu/~faber Cc: freebsd-stable@freebsd.org Subject: Re: resume slow on Thinkpad T42 FreeBSD 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 17:49:32 -0000 --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 22, 2010 at 07:51:00PM +1000, Ian Smith wrote: > On Thu, 25 Feb 2010 17:35:51 -0800, Ted Faber wrote: > > On Thu, Feb 25, 2010 at 05:18:22PM +1100, Ian Smith wrote: > > > On Wed, 24 Feb 2010, Ted Faber wrote: > > >=20 > > > > I'm running a recent (yesterday) FreeBSD 8-STABLE on my T42. Whe= n I > > > > resume from suspend the fan starts screen returns immediately (to= text > > > > mode) and then the system idles for about a minute until it shakes > > > > itself awake. The keyboard LEDs cycle, the disk runs and X retur= ns. > > >=20 > > > Good to hear, Ted .. I thought it was just me :) Your symptoms appe= ar=20 > > > entirely identical to mine as posted on Dec 13th to mobile@ and acpi= @,=20 > > > see thread 'Thinkpad T23 60 second stall on resuming 8.0-RELEASE/i38= 6'=20 > > > http://lists.freebsd.org/pipermail/freebsd-acpi/2009-December/006192= .html > > >=20 > > > Nate Lawson thought it an ATA rather than an ACPI problem and I assu= me=20 > > > he's likely right, but I've had too much $work (and too little solar= =20 > > > power during an exceptionally wet summer) to follow it up. > >=20 > > Yeah, that sounds like the problem. I'll poke at ata if I get the > > chance, but that seems unlikely for a while. > >=20 > > > In case relevant, my ad0 is a 120GB Fujitsu MHV2120AH, but your TOSH= IBA=20 > > > MK4026GAX looks more likely to be the original disk? > >=20 > > Likely, but I can't be sure. I bought it used. > >=20 > > >=20 > > > I've no time to spend on hunting this now, and know nothing about AT= A=20 > > > anyway, assuming that's where the problem lies, but I'll be quick to= =20 > > > test any suggested solution/s! > >=20 > > Like I say, assuming I ever get free time, I'll have a look. >=20 > Brought my Thinkpad T23 (actually a replacement, similar model, same HD)= =20 > to '8.1-STABLE #0: Sun Sep 5 15:53:00 EST 2010' but this issue persists,= =20 > as it does if booted from 8.1-i386-memstick, HD present but not mounted;= =20 > this one has the CDRW rather than the original's DVD-ROM, if relevant. >=20 > Before excruciating detail of the issue in mobile@ and acpi@ again in=20 > hope of debugging hints, have you (Ted or anyone) any further news on=20 > Thinkpad T-series (or other) 60 second stalls/freezes on S3 resume? >=20 > [Please read the abovementioned thread before asking any questions] Sorry, Ian, I don't have anything new, wrt the ATA. --=20 Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.= asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#= SIG --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkyaOHAACgkQaUz3f+Zf+Xv76wCfY4xCQuMZE4kWzDSBC9TVK+yu T0QAoIav8p33oq7drPIObVi9t3VXSuIA =GRAs -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 17:53:14 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9FA2106564A for ; Wed, 22 Sep 2010 17:53:14 +0000 (UTC) (envelope-from rpaulo@freebsd.org) Received: from karen.lavabit.com (karen.lavabit.com [72.249.41.33]) by mx1.freebsd.org (Postfix) with ESMTP id 8627A8FC14 for ; Wed, 22 Sep 2010 17:53:14 +0000 (UTC) Received: from d.earth.lavabit.com (d.earth.lavabit.com [192.168.111.13]) by karen.lavabit.com (Postfix) with ESMTP id 2628F11B94D for ; Wed, 22 Sep 2010 12:23:40 -0500 (CDT) Received: from 10.0.10.3 (221.163.108.93.rev.vodafone.pt [93.108.163.221]) by lavabit.com with ESMTP id 133TNNABN5SZ for ; Wed, 22 Sep 2010 12:23:40 -0500 From: Rui Paulo Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Wed, 22 Sep 2010 18:23:37 +0100 Message-Id: <7EDB90C5-D638-44AB-80B9-AF2CDC566231@FreeBSD.org> To: stable@freebsd.org Mime-Version: 1.0 (Apple Message framework v1081) X-Mailer: Apple Mail (2.1081) Cc: Subject: HEADS UP: instability on stable/8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 17:53:14 -0000 Hi, While I'm merging the userland DTrace bits to stable/8 you might = experience some instability if you use DTrace. If you use DTrace, I = suggest you don't try to upgrade during the next 5 days. Thanks for your patience, -- Rui Paulo From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 18:41:07 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C11B71065670 for ; Wed, 22 Sep 2010 18:41:07 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 4E3D88FC29 for ; Wed, 22 Sep 2010 18:41:06 +0000 (UTC) Received: (qmail 25202 invoked by uid 399); 22 Sep 2010 18:41:06 -0000 Received: from localhost (HELO ?192.168.0.142?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 22 Sep 2010 18:41:06 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C9A4DC3.60001@FreeBSD.org> Date: Wed, 22 Sep 2010 11:41:07 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: John Baldwin References: <4C98F433.6070506@FreeBSD.org> <20100921193101.GA95238@night.db.net> <20100922095724.C31898@maildrop.int.zabbadoz.net> <201009220950.32294.jhb@freebsd.org> In-Reply-To: <201009220950.32294.jhb@freebsd.org> X-Enigmail-Version: 1.2a1pre OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Bjoern A. Zeeb" , freebsd-stable@freebsd.org Subject: Re: BIND9 built w/--disable-ipv6 on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 18:41:07 -0000 On 9/22/2010 6:50 AM, John Baldwin wrote: > On Wednesday, September 22, 2010 6:02:08 am Bjoern A. Zeeb wrote: >> Can't we just do what lib/bind/config.mk already does? Since I've already answered this twice in the same thread, I'll leave it as an exercise for the reader to determine why I will not be making your proposed change. > Actually, I frequently build custom kernels w/o INET6, but don't necessarily > disable INET6 for the world build. However, why can't BIND just be fixed to > have sane behavior if the kernel doesn't support INET6? It already behaves as you expect it should, which I've already explained in detail twice in this same thread. These are not the droids you're looking for, move along. Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 19:58:17 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91F721065679 for ; Wed, 22 Sep 2010 19:58:17 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 50CB78FC1B for ; Wed, 22 Sep 2010 19:58:16 +0000 (UTC) Received: by iwn34 with SMTP id 34so920401iwn.13 for ; Wed, 22 Sep 2010 12:58:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=Val2YWRr71CuHQDFLpssPT99IhFjB3iQscXli7+6Res=; b=L08u+INwaGjMQL/EFJLW4vOsMyobEUUliGH9dW0wgDrjxqFPCFBq83p24H1RaPSLkp /YiYmUHe962x7jCSGngx+DfON1MEWmkMBc2srfa2xstiPp+TU21KU4Haqm0a+u1razV8 iRJfyvG0YrQoMCtG7WMBcloNComeGwOMVi0FM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=A+frCy458snytjJ/FFAyUoH8V/tImrJL4nFZHQdrwA9PKmkdkv6ICEeuKhY/3hKlqq jMs4DRO21yr/5yl8RGewzOxE/x4Z0L1wBwdxW3czHnX2So5HbwflMliDwYEds8jBflUH hiCl7XRUtlc19ihgWR2LG2s2+le8JHgvOgFWc= Received: by 10.231.174.206 with SMTP id u14mr661783ibz.103.1285185496483; Wed, 22 Sep 2010 12:58:16 -0700 (PDT) Received: from centel.dataix.local (adsl-99-181-130-119.dsl.klmzmi.sbcglobal.net [99.181.130.119]) by mx.google.com with ESMTPS id o4sm3708474iba.12.2010.09.22.12.58.14 (version=SSLv3 cipher=RC4-MD5); Wed, 22 Sep 2010 12:58:14 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C9A5FD4.8000901@DataIX.net> Date: Wed, 22 Sep 2010 15:58:12 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.9) Gecko/20100917 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Kostik Belousov References: <20100919222837.70629.qmail@exxodus.fedaykin.here> <20100922132801.GV2389@deviant.kiev.zoral.com.ua> In-Reply-To: <20100922132801.GV2389@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Mario Sergio Fujikawa Ferreira Subject: Re: Panic with chromium and 8.1-STABLE (Thu Sep 16 09:52:17 BRT 2010) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 19:58:17 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/22/2010 09:28, Kostik Belousov wrote: > On Sun, Sep 19, 2010 at 07:28:13PM -0300, Mario Sergio Fujikawa Ferreira wrote: >> Hi, >> >> I've just began trying chrome web browser from >> http://chromium.hybridsource.org/ but it triggered 2 panics on my >> 8.1-STABLE system. >> >> $ uname -a >> FreeBSD exxodus.fedaykin.here 8.1-STABLE FreeBSD 8.1-STABLE #26: Thu Sep 16 09:52:17 BRT 2010 lioux@exxodus:/usr/obj/usr/src/sys/LIOUX amd64 >> >> The panic information is: >> >> ------------ >> panic: vm_page_unwire: invalid wire count: 0 >> cpuid = 0 >> KDB: enter: panic >> >> 0xffffff006ecce000: tag ufs, type VREG >> usecount 1, writecount 1, refcount 4 mountedhere 0 >> flags () >> v_object 0xffffff0151489870 ref 0 pages 8 >> lock type ufs: EXCL by thread 0xffffff00200947c0 (pid 25025) >> ino 119526591, on dev ufs/fsusr >> >> 0xffffff011107f938: tag ufs, type VREG >> usecount 0, writecount 0, refcount 4 mountedhere 0 >> flags (VV_NOSYNC|VI_DOINGINACT) >> v_object 0xffffff0151f7f870 ref 0 pages 1284 >> lock type ufs: EXCL by thread 0xffffff01882cc7c0 (pid 26689) >> ino 263, on dev md0 >> ------------ >> >> I've made available 2 ddb textdumps at: >> >> http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.0 >> http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.1 >> >> I was able to use chrome prior to this latest kernel update. >> Now, I can reproduce a kernel panic even browsing www.google.com >> >> Please, let me know if I can provide any further information. > > Does it panic if you remove ZERO_COPY_SOCKETS option from the kernel > config ? This is triggered as well on a system without ZERO_COPY_SOCKETS just to clear that bit up. Kostik, I am going to forward you two core.txt.NN files I had generated on a ZFS system that I used chrome on as well. I can trigger this repeatedly from 20-30 minutes of using chrome. Not sure whats going on here but maybe you can shed some light over both issues that seem to be the same thing. I do not mind if you forward these core.txt.NN files to other devs that may be interested and able to help. I still have the kernels for both of these so if more information is needed just let me know. Regards, - -- jhell,v -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJMml/UAAoJEJBXh4mJ2FR+EkIH/j9lfSg1ZTMtn4vRgybvd+3F 0Sy88IgvltQmIicEaQ4MbQ9IpO/owsc362UexQvnbx38zVLRivfJYsDefAmG6Dex OVRuewzJzgr3YWv89t4OxZgWNcsyTFVZCLavCuGiUzbw52m83klc3Fubr0+wXI1G OtIEsaIFqaGHvgVSvGKlHLiv2/Q93bZ1kWCCHdHM3l4QIPG9ARuRR08bOVDQK0Xd GhMUVXfvV7fOF1cwzecQ5+AP4UDaExA3JRrkYf7IC8KkFgATbdA3RLbxypkkOf75 XVqBFmqjAQfIPc8vUvVd9WmC1tNfqJzJPQ3kl3B3HHs2K3g/BoZpeaUEGacXJ8o= =FyGm -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 20:01:50 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D02B1065672 for ; Wed, 22 Sep 2010 20:01:50 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout026.mac.com (asmtpout026.mac.com [17.148.16.101]) by mx1.freebsd.org (Postfix) with ESMTP id 44E358FC1F for ; Wed, 22 Sep 2010 20:01:50 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii Received: from cswiger1.apple.com ([17.209.4.71]) by asmtp026.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0L9500HCTWV0IV10@asmtp026.mac.com> for freebsd-stable@freebsd.org; Wed, 22 Sep 2010 12:01:49 -0700 (PDT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1004200000 definitions=main-1009220163 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.0.10011,1.0.148,0.0.0000 definitions=2010-09-22_09:2010-09-22, 2010-09-22, 1970-01-01 signatures=0 From: Chuck Swiger In-reply-to: <20100921193101.GA95238@night.db.net> Date: Wed, 22 Sep 2010 12:01:48 -0700 Message-id: <9FF55FD3-4168-471B-A7C1-2D23880F3091@mac.com> References: <4C98F433.6070506@FreeBSD.org> <20100921191517.AF60A1CC3D@ptavv.es.net> <20100921193101.GA95238@night.db.net> To: Diane Bruce X-Mailer: Apple Mail (2.1081) Cc: "freebsd-stable@freebsd.org List" Subject: Re: BIND9 built w/--disable-ipv6 on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 20:01:50 -0000 Hi-- On Sep 21, 2010, at 12:31 PM, Diane Bruce wrote: [ ... ] >> Doug Barton wrote: >> If I'm still alive when IPv6 is the norm and IPv4 is the exception, I >> promise to give it another look. :) > > IPv6 is more prevalent than you think. I can't understand the illogic of turning it off. Well, I can't understand illogic either, but it's not too hard to obtain data about the issue and make rational decisions about IPv6 vs. IPv4 networking. :-) http://www.ripe.net/ripe/meetings/ripe-57/presentations/Colitti-Global_IPv6_statistics_-_Measuring_the_current_state_of_IPv6_for_ordinary_users_.7gzD.pdf Quoting from page 5: "* 0.238% of users have useful IPv6 connectivity (and prefer IPv6) * 0.09% of users have broken IPv6 connectivity That is, adding an AAAA record will make these users unable to view your site" Approximately 2 or 3 users per thousand prefer IPv6, and approximately 38% of these IPv6 users have broken connectivity, as of [2008]. Regards, -- -Chuck PS: Taken from a NetBSD thread here: http://mail-index.netbsd.org/tech-net/2009/12/04/msg001762.html From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 20:31:27 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8756F1065696 for ; Wed, 22 Sep 2010 20:31:27 +0000 (UTC) (envelope-from eivinde@terraplane.org) Received: from mail43.e.nsc.no (mail43.e.nsc.no [193.213.115.43]) by mx1.freebsd.org (Postfix) with ESMTP id D3A878FC20 for ; Wed, 22 Sep 2010 20:31:26 +0000 (UTC) Received: from rumrunner.mine.nu (ti0027a380-0792.bb.online.no [80.212.66.26]) by mail43.nsc.no (8.14.3/8.14.3) with ESMTP id o8MKVJc9015835 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 22 Sep 2010 22:31:21 +0200 (MEST) Received: from rumrunner.mine.nu (localhost [127.0.0.1]) by rumrunner.mine.nu (8.14.4/8.14.2) with ESMTP id o8MKVIgq073569; Wed, 22 Sep 2010 22:31:18 +0200 (CEST) (envelope-from eivinde@terraplane.org) Received: from localhost (rumrunner@localhost) by rumrunner.mine.nu (8.14.4/8.13.8/Submit) with ESMTP id o8MKVIHQ073566; Wed, 22 Sep 2010 22:31:18 +0200 (CEST) (envelope-from eivinde@terraplane.org) X-Authentication-Warning: rumrunner.mine.nu: rumrunner owned process doing -bs Date: Wed, 22 Sep 2010 22:31:18 +0200 (CEST) From: Eivind E X-X-Sender: rumrunner@rumrunner.mine.nu To: Peter Jeremy In-Reply-To: <20100919062057.GE52661@server.vk2pj.dyndns.org> Message-ID: <20100922214617.A73209@rumrunner.mine.nu> References: <201009132016.o8DKGmw5053180@lurza.secnetix.de> <20100913234355.I96626@rumrunner.mine.nu> <20100914231728.D5192@rumrunner.mine.nu> <20100915214234.I13301@rumrunner.mine.nu> <20100919062057.GE52661@server.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Freebsd 8.1 + xorg + radeonhd hang X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: eivinde@terraplane.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 20:31:27 -0000 On Sun, 19 Sep 2010, Peter Jeremy wrote: > Can I suggest adding a "Virtual 1280 1024" (or similar) to the > 'SubSection "Display"' of 'Section "Screen"'. I ran into some wierd > problems with multiple screens and found that the virtual size isn't > correctly initialised unless it's explicitly specified. Oh, my setup is one single monitor only. > Also, specifying EXA acceleration is fairly mandatory: The default XAA > acceleration is broken. Yeah, tried that aswell, from another tip. -- _ _ // \\// Eivind Evensen \/ From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 20:34:47 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 519B91065693 for ; Wed, 22 Sep 2010 20:34:47 +0000 (UTC) (envelope-from eivinde@terraplane.org) Received: from mail47.e.nsc.no (mail47.e.nsc.no [193.213.115.47]) by mx1.freebsd.org (Postfix) with ESMTP id 9FC278FC20 for ; Wed, 22 Sep 2010 20:34:46 +0000 (UTC) Received: from rumrunner.mine.nu (ti0027a380-0792.bb.online.no [80.212.66.26]) by mail47.nsc.no (8.14.3/8.14.3) with ESMTP id o8MKYdCm012103 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 22 Sep 2010 22:34:41 +0200 (MEST) Received: from rumrunner.mine.nu (localhost [127.0.0.1]) by rumrunner.mine.nu (8.14.4/8.14.2) with ESMTP id o8MKYcon073613; Wed, 22 Sep 2010 22:34:38 +0200 (CEST) (envelope-from eivinde@terraplane.org) Received: from localhost (rumrunner@localhost) by rumrunner.mine.nu (8.14.4/8.13.8/Submit) with ESMTP id o8MKYcaO073610; Wed, 22 Sep 2010 22:34:38 +0200 (CEST) (envelope-from eivinde@terraplane.org) X-Authentication-Warning: rumrunner.mine.nu: rumrunner owned process doing -bs Date: Wed, 22 Sep 2010 22:34:38 +0200 (CEST) From: Eivind E X-X-Sender: rumrunner@rumrunner.mine.nu To: "O. Hartmann" In-Reply-To: <4C95D117.1080309@mail.zedat.fu-berlin.de> Message-ID: <20100922223226.N73209@rumrunner.mine.nu> References: <201009132016.o8DKGmw5053180@lurza.secnetix.de> <20100913234355.I96626@rumrunner.mine.nu> <20100914231728.D5192@rumrunner.mine.nu> <20100915214234.I13301@rumrunner.mine.nu> <20100919062057.GE52661@server.vk2pj.dyndns.org> <4C95D117.1080309@mail.zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, Peter Jeremy Subject: Re: Freebsd 8.1 + xorg + radeonhd hang X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: eivinde@terraplane.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 20:34:47 -0000 On Sun, 19 Sep 2010, O. Hartmann wrote: > In my case, this is exactly the other way around. There was atime when > radeonhd and radeon both worked with radeon boards, even with DRI set to on. > I recall the the time, whe radeonhd was ugraded to semthing like 1.2.8 or so > the problems started occuring (in my case) Seems the driver ain't good at all with certain revisions of the radeoncards. > screen).The same happens with a HD4670 board. More interesting is the usage > of DBUS and HALD. With both enabled, the box dies immediately when X comes > up. No matter whether radeon or radeonhd is used. > Well, without X, dbus and hald work well. with X. I've never seen a need for those, I've used Option "AllowEmptyInput" "Off", and now, after another suggestion Option "AutoAddDevices" "Off" to get keyboard and mouse working without. I've never understood what hald could give me. -- _ _ // \\// Eivind Evensen \/ From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 20:38:01 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8439D1065672; Wed, 22 Sep 2010 20:38:01 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 1CDAC8FC20; Wed, 22 Sep 2010 20:38:00 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id o8MKbs6t020721 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Sep 2010 23:37:54 +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.4/8.14.4) with ESMTP id o8MKbsgn009947; Wed, 22 Sep 2010 23:37:54 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id o8MKbrfd009946; Wed, 22 Sep 2010 23:37:53 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 22 Sep 2010 23:37:53 +0300 From: Kostik Belousov To: jhell Message-ID: <20100922203753.GB2389@deviant.kiev.zoral.com.ua> References: <20100919222837.70629.qmail@exxodus.fedaykin.here> <20100922132801.GV2389@deviant.kiev.zoral.com.ua> <4C9A5FD4.8000901@DataIX.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vAlDtAs5WEb1aNYe" Content-Disposition: inline In-Reply-To: <4C9A5FD4.8000901@DataIX.net> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-stable@freebsd.org, Mario Sergio Fujikawa Ferreira Subject: Re: Panic with chromium and 8.1-STABLE (Thu Sep 16 09:52:17 BRT 2010) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 20:38:01 -0000 --vAlDtAs5WEb1aNYe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 22, 2010 at 03:58:12PM -0400, jhell wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > On 09/22/2010 09:28, Kostik Belousov wrote: > > On Sun, Sep 19, 2010 at 07:28:13PM -0300, Mario Sergio Fujikawa Ferreir= a wrote: > >> Hi, > >> > >> I've just began trying chrome web browser from > >> http://chromium.hybridsource.org/ but it triggered 2 panics on my > >> 8.1-STABLE system. > >> > >> $ uname -a > >> FreeBSD exxodus.fedaykin.here 8.1-STABLE FreeBSD 8.1-STABLE #26: Thu S= ep 16 09:52:17 BRT 2010 lioux@exxodus:/usr/obj/usr/src/sys/LIOUX amd64 > >> > >> The panic information is: > >> > >> ------------ > >> panic: vm_page_unwire: invalid wire count: 0 > >> cpuid =3D 0 > >> KDB: enter: panic > >> > >> 0xffffff006ecce000: tag ufs, type VREG > >> usecount 1, writecount 1, refcount 4 mountedhere 0 > >> flags () > >> v_object 0xffffff0151489870 ref 0 pages 8 > >> lock type ufs: EXCL by thread 0xffffff00200947c0 (pid 25025) > >> ino 119526591, on dev ufs/fsusr > >> > >> 0xffffff011107f938: tag ufs, type VREG > >> usecount 0, writecount 0, refcount 4 mountedhere 0 > >> flags (VV_NOSYNC|VI_DOINGINACT) > >> v_object 0xffffff0151f7f870 ref 0 pages 1284 > >> lock type ufs: EXCL by thread 0xffffff01882cc7c0 (pid 26689) > >> ino 263, on dev md0 > >> ------------ > >> > >> I've made available 2 ddb textdumps at: > >> > >> http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.0 > >> http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.1 > >> > >> I was able to use chrome prior to this latest kernel update. > >> Now, I can reproduce a kernel panic even browsing www.google.com > >> > >> Please, let me know if I can provide any further information. > >=20 > > Does it panic if you remove ZERO_COPY_SOCKETS option from the kernel > > config ? >=20 > This is triggered as well on a system without ZERO_COPY_SOCKETS just to > clear that bit up. I do not know what did prompted you to decide that the issue is the same. There is nothing common except the word "panic" in the report by lioux and your backtraces. You could have better luck showing your traces on the fs@ or asking zfs porters directly. --vAlDtAs5WEb1aNYe Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkyaaSEACgkQC3+MBN1Mb4ib1ACfYDtOr1Gyydr0JcTILJ+VLl20 KDsAoIMVJLvn+FwJYFd6S9RZ7YyH/36T =7PW4 -----END PGP SIGNATURE----- --vAlDtAs5WEb1aNYe-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 20:47:49 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 713081065672; Wed, 22 Sep 2010 20:47:49 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id CA5BB8FC0C; Wed, 22 Sep 2010 20:47:48 +0000 (UTC) Received: by wyb33 with SMTP id 33so1238553wyb.13 for ; Wed, 22 Sep 2010 13:47:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=lfZ1o5aP9GNS/1ONdxoYzMig+imYtYcNJLB4tMRAKC0=; b=HzvIIFUeJbvkAXLxwtmjX4/SlXhSHvjRn/E7gY+PGZlrpLQoFmJ8Us+NZsb1655/p7 XdxmpC4Sz3M/nSosISkAFBIscMsEDnvfbj0sCAqwYIbNaejRgJuI7ZVzLCeiPnwyIfSd KAGv3a2LqeMc8LTVz43kXkkwYrlOPcShl85SA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=NKE8XHxS2C/mxQe1fZpxB5KsUFhbubUU99rS8H0mh79PaihzemVAHUQq49UBuk9leb +iaQIt6FwjIB1D3RbHmBj96fnMalXkbHO6qYMTZfLyfxlt1/EWbJH+Q0aWRJ08eyutCy 8yNQGrn/kLE865/GwrNL78cDDBx215mYMLx9E= Received: by 10.227.155.6 with SMTP id q6mr691865wbw.141.1285188467712; Wed, 22 Sep 2010 13:47:47 -0700 (PDT) Received: from centel.dataix.local (adsl-99-181-130-119.dsl.klmzmi.sbcglobal.net [99.181.130.119]) by mx.google.com with ESMTPS id bc3sm4405732wbb.2.2010.09.22.13.47.45 (version=SSLv3 cipher=RC4-MD5); Wed, 22 Sep 2010 13:47:46 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C9A6B70.7000903@DataIX.net> Date: Wed, 22 Sep 2010 16:47:44 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.9) Gecko/20100917 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Kostik Belousov References: <20100919222837.70629.qmail@exxodus.fedaykin.here> <20100922132801.GV2389@deviant.kiev.zoral.com.ua> <4C9A5FD4.8000901@DataIX.net> <20100922203753.GB2389@deviant.kiev.zoral.com.ua> In-Reply-To: <20100922203753.GB2389@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Mario Sergio Fujikawa Ferreira Subject: Re: Panic with chromium and 8.1-STABLE (Thu Sep 16 09:52:17 BRT 2010) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 20:47:49 -0000 On 09/22/2010 16:37, Kostik Belousov wrote: > On Wed, Sep 22, 2010 at 03:58:12PM -0400, jhell wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 09/22/2010 09:28, Kostik Belousov wrote: >>> On Sun, Sep 19, 2010 at 07:28:13PM -0300, Mario Sergio Fujikawa Ferreira wrote: >>>> Hi, >>>> >>>> I've just began trying chrome web browser from >>>> http://chromium.hybridsource.org/ but it triggered 2 panics on my >>>> 8.1-STABLE system. >>>> >>>> $ uname -a >>>> FreeBSD exxodus.fedaykin.here 8.1-STABLE FreeBSD 8.1-STABLE #26: Thu Sep 16 09:52:17 BRT 2010 lioux@exxodus:/usr/obj/usr/src/sys/LIOUX amd64 >>>> >>>> The panic information is: >>>> >>>> ------------ >>>> panic: vm_page_unwire: invalid wire count: 0 >>>> cpuid = 0 >>>> KDB: enter: panic >>>> >>>> 0xffffff006ecce000: tag ufs, type VREG >>>> usecount 1, writecount 1, refcount 4 mountedhere 0 >>>> flags () >>>> v_object 0xffffff0151489870 ref 0 pages 8 >>>> lock type ufs: EXCL by thread 0xffffff00200947c0 (pid 25025) >>>> ino 119526591, on dev ufs/fsusr >>>> >>>> 0xffffff011107f938: tag ufs, type VREG >>>> usecount 0, writecount 0, refcount 4 mountedhere 0 >>>> flags (VV_NOSYNC|VI_DOINGINACT) >>>> v_object 0xffffff0151f7f870 ref 0 pages 1284 >>>> lock type ufs: EXCL by thread 0xffffff01882cc7c0 (pid 26689) >>>> ino 263, on dev md0 >>>> ------------ >>>> >>>> I've made available 2 ddb textdumps at: >>>> >>>> http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.0 >>>> http://people.freebsd.org/~lioux/panic/2010091900/textdump.tar.1 >>>> >>>> I was able to use chrome prior to this latest kernel update. >>>> Now, I can reproduce a kernel panic even browsing www.google.com >>>> >>>> Please, let me know if I can provide any further information. >>> >>> Does it panic if you remove ZERO_COPY_SOCKETS option from the kernel >>> config ? >> >> This is triggered as well on a system without ZERO_COPY_SOCKETS just to >> clear that bit up. > I do not know what did prompted you to decide that the issue is the same. > There is nothing common except the word "panic" in the report by > lioux and your backtraces. > > You could have better luck showing your traces on the fs@ or asking zfs > porters directly. Well taking a stab at it I thought you were involved with that. Considering it is being triggered on the FS level there is somthing in common but that won't always mean the traces will be exact for two different file-systems. It may just as well be two different cases so Ill just forward them on to the correct people. Thanks anyway. Regards, -- jhell,v From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 21:02:03 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8B2D91065674 for ; Wed, 22 Sep 2010 21:02:03 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3fd3:cd67:fafa:3d78]) by mx1.freebsd.org (Postfix) with ESMTP id DCD288FC17 for ; Wed, 22 Sep 2010 21:02:02 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [81.187.76.163]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.4/8.14.4) with ESMTP id o8ML1mRA036614 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 22 Sep 2010 22:01:49 +0100 (BST) (envelope-from m.seaman@infracaninophile.co.uk) Message-ID: <4C9A6EB5.1060607@infracaninophile.co.uk> Date: Wed, 22 Sep 2010 22:01:41 +0100 From: Matthew Seaman Organization: Infracaninophile User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: Chuck Swiger References: <4C98F433.6070506@FreeBSD.org> <20100921191517.AF60A1CC3D@ptavv.es.net> <20100921193101.GA95238@night.db.net> <9FF55FD3-4168-471B-A7C1-2D23880F3091@mac.com> In-Reply-To: <9FF55FD3-4168-471B-A7C1-2D23880F3091@mac.com> X-Enigmail-Version: 1.1.1 OpenPGP: id=60AE908C Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig3E06FE072A08C097C37B8C0A" X-Virus-Scanned: clamav-milter 0.96.2 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_40,DKIM_ADSP_ALL, SPF_FAIL autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on lucid-nonsense.infracaninophile.co.uk Cc: Diane Bruce , "freebsd-stable@freebsd.org List" Subject: Re: BIND9 built w/--disable-ipv6 on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 21:02:03 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig3E06FE072A08C097C37B8C0A Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 22/09/2010 20:01:48, Chuck Swiger wrote: > Hi-- >=20 > On Sep 21, 2010, at 12:31 PM, Diane Bruce wrote: > [ ... ] >>> Doug Barton wrote: >=20 >>> If I'm still alive when IPv6 is the norm and IPv4 is the exception, I= >>> promise to give it another look. :) >> >> IPv6 is more prevalent than you think. I can't understand the illogic = of turning it off. >=20 > Well, I can't understand illogic either, but it's not too hard to obtai= n data about the issue and make rational decisions about IPv6 vs. IPv4 ne= tworking. :-) >=20 > http://www.ripe.net/ripe/meetings/ripe-57/presentations/Colitti-Global_= IPv6_statistics_-_Measuring_the_current_state_of_IPv6_for_ordinary_users_= =2E7gzD.pdf >=20 > Quoting from page 5: >=20 > "* 0.238% of users have useful IPv6 connectivity (and prefer IPv6) > * 0.09% of users have broken IPv6 connectivity > That is, adding an AAAA record will make these users unable to view = your site" >=20 > Approximately 2 or 3 users per thousand prefer IPv6, and approximately = 38% of these IPv6 users have broken connectivity, as of [2008]. >=20 Yeah. "Ordinary" users won't like and don't generally use IPv6 because it is *still* virtually impossible to get consumer-grade items like WiFi and ADSL routers with IPv6 capability. Apple equipment (AirPort, etc) is an honourable exception. This is really a travesty, and something that manufacturers should be being browbeaten about at every possible opportunity. To counter: IPv6 is not some vague far future thing any more. The IANA pool of unallocated IPv4 address space is forecast to run out in May of next year. The unallocated pools held by Regional Internet Registries (RIPE, ARIN, APNIC and so forth) will run out in January 2012. Note: these numbers don't even try and account for attempts to obtain and hoard address space once it becomes really scarce, something that will probably cause address space exhaustion rather sooner than the current predictions. http://www.potaroo.net/tools/ipv4/index.html After that, there are some legacy /8 network assignments from the very early days of the Internet which are under-used and should be broken up. Then it's down to haggling over dribs and drabs of IPv4 space as they are released back to the registries as part of normal turn-over. If you haven't got hold of all the IPv4 address space you are ever going to need within the next 15 months or so, then you are S.O.L. Honestly, any company that relies on the Internet for their business and that does not by now have at least a well-developed IPv6 implementation plan, urgently needs to fire their current IT management and hire someone with a clue. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matthew@infracaninophile.co.uk Kent, CT11 9PW --------------enig3E06FE072A08C097C37B8C0A Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyabrwACgkQ8Mjk52CukIxBgACZAYocYXVuYYgQ5ILAuYXitaSa H+AAn0bvf9SKk5clj0ibl0jtXSlS9eZe =Pna8 -----END PGP SIGNATURE----- --------------enig3E06FE072A08C097C37B8C0A-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 21:46:59 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 871E71065672 for ; Wed, 22 Sep 2010 21:46:59 +0000 (UTC) (envelope-from kc5vdj.freebsd@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4E37C8FC1A for ; Wed, 22 Sep 2010 21:46:59 +0000 (UTC) Received: by iwn34 with SMTP id 34so1012112iwn.13 for ; Wed, 22 Sep 2010 14:46:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=OrB507hIkH/7MJJt4gBxVXtMJaBf/GADrXHJPvv5vsc=; b=L8QwNghpN4fs3j3C3w3AKrGCxGzLbo1O3+s5CtLmZ7uwm/omMP4R7EgoHRV0py2Nqc 9ngAkeendmpcvw6AEz4IaWe/eoORpJ0fNboZaEoEHMtvjNOjvSlO5nzOu0qV8irAHJ3G k8Wn2/QaJu6ne4HBp0puOLjWON6rLP1gXOQ38= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=V5BkBX0mlKRdZq5HI0rer5FbAtbU+hOsy3KPE0WiS1lZsag9Vi5gutaLTcsSSySYqZ x35CKdSCyg924zJ7jAHyRCZ7uOl6Xk43+gWXoJM1HEtuYUL4db2ycQg9OIgfJyBpMnGl krPs1ZRanLJ6DHyADJutAr0Es0QcFRyoZlCCc= Received: by 10.231.183.81 with SMTP id cf17mr899838ibb.32.1285192018378; Wed, 22 Sep 2010 14:46:58 -0700 (PDT) Received: from argus.electron-tube.net (desm-47-213.dsl.netins.net [167.142.47.213]) by mx.google.com with ESMTPS id h8sm26118ibk.3.2010.09.22.14.46.57 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 22 Sep 2010 14:46:57 -0700 (PDT) Message-ID: <4C9A7943.1020806@gmail.com> Date: Wed, 22 Sep 2010 16:46:43 -0500 From: Jim Bryant User-Agent: Thunderbird 2.0.0.24 (X11/20100911) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: wifi issues under -stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 21:46:59 -0000 i have two laptops, both are Compaq(HP) C300 series using the motherboards with the 945GM chipset and using T7200 and T7600 Core2 Duos. One (this one) has an intel pro wireless 3945ABG installed, which returns: wpi0: irq 18 at device 0.0 on pci6 wpi0: Driver Revision 20071127 wpi0: 0x1000 bytes of rid 0x10 res 3 failed (0, 0xffffffffffffffff). wpi0: could not allocate memory resource device_attach: wpi0 attach returned 6 and the broadcom used in the other does the exact same thing. I'm thinking that this isn't really a problem with the wifi, but may be a mini-pci-e issue. does anyone know how to solve this problem? previous attempts under fbsd-7 using the previous ndis driver would always panic upon kldload. both laptops are currently running -stable with kernels from around the 6th of this month. any help would be appreciated. i currently have to operate tethered with a linksys ural0 compat usb adapter. jim From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 00:37:09 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BEBA2106566C for ; Thu, 23 Sep 2010 00:37:09 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 7BAAD8FC1A for ; Thu, 23 Sep 2010 00:37:09 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.4/8.14.4) with ESMTP id o8N0b8GR073793; Wed, 22 Sep 2010 18:37:08 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.4/8.14.4/Submit) with ESMTP id o8N0b8kc073790; Wed, 22 Sep 2010 18:37:08 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Wed, 22 Sep 2010 18:37:08 -0600 (MDT) From: Warren Block To: Jim Bryant In-Reply-To: <4C9A7943.1020806@gmail.com> Message-ID: References: <4C9A7943.1020806@gmail.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (wonkity.com [127.0.0.1]); Wed, 22 Sep 2010 18:37:08 -0600 (MDT) Cc: freebsd-stable@freebsd.org Subject: Re: wifi issues under -stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 00:37:09 -0000 On Wed, 22 Sep 2010, Jim Bryant wrote: > i have two laptops, both are Compaq(HP) C300 series using the motherboards > with the 945GM chipset and using T7200 and T7600 Core2 Duos. > > One (this one) has an intel pro wireless 3945ABG installed, which returns: > > wpi0: irq 18 at device 0.0 on pci6 > wpi0: Driver Revision 20071127 > wpi0: 0x1000 bytes of rid 0x10 res 3 failed (0, 0xffffffffffffffff). > wpi0: could not allocate memory resource > device_attach: wpi0 attach returned 6 > > and the broadcom used in the other does the exact same thing. > > I'm thinking that this isn't really a problem with the wifi, but may be a > mini-pci-e issue. Don't know about the Intel, but some Broadcoms work. Please show what you're doing in /boot/loader.conf and /etc/rc.conf. From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 00:45:24 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22B911065670 for ; Thu, 23 Sep 2010 00:45:24 +0000 (UTC) (envelope-from bryce@bryce.net) Received: from mail-gx0-f186.google.com (mail-gx0-f186.google.com [209.85.161.186]) by mx1.freebsd.org (Postfix) with ESMTP id CE5EA8FC14 for ; Thu, 23 Sep 2010 00:45:23 +0000 (UTC) Received: by gxk1 with SMTP id 1so1006439gxk.13 for ; Wed, 22 Sep 2010 17:45:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.235.38 with SMTP id i38mr42103anh.7.1285202723105; Wed, 22 Sep 2010 17:45:23 -0700 (PDT) Received: by c16g2000vbp.googlegroups.com with HTTP; Wed, 22 Sep 2010 17:45:22 -0700 (PDT) Date: Wed, 22 Sep 2010 17:45:22 -0700 (PDT) In-Reply-To: X-IP: 70.140.155.124 References: User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10,gzip(gfe) Message-ID: <12466724-cf4e-449b-8a6a-464e08c1c17f@c16g2000vbp.googlegroups.com> From: Bryce To: Ian Smith Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 00:45:24 -0000 On Sep 22, 11:43=A0am, smi...@nimnet.asn.au (Ian Smith) wrote: > On Wed, 22 Sep 2010, Tom Evans wrote: > > =A0> On Wed, Sep 22, 2010 at 2:50 PM, Ian Smith wr= ote: > =A0> > It seems far more than just CPU performance is awry. =A0Adam's dat= a from > =A0> > his i7 shows 2.7 times Bryce's speed for the md5 -t, maybe a lower= EST > =A0> > rate? - but that could no way account for buildworld taking 22.5 h= ours. > =A0> > > =A0> > Recent buildworld (albeit i386) on my Thinkpad T23 ran just shy of= 3.5 > =A0> > hours, without -j on an 1133MHz P3-M, 768MB of 133MHz RAM, 5400rpm= UFS > =A0> > disk - with X/KDE running meanwhile (~5-7% CPU penalty). > =A0> > =A0> md5 -t is quite a small benchmark, even with his misfunctioning CPU = it > =A0> took <6 seconds to complete. > =A0> > =A0> If his problem is a misapplied heatsink/fan, then his CPU could be > =A0> throttling when it gets hot, the hotter it gets the more it throttle= s, > =A0> which could explain his massive buildworld walltime. Perhaps running > =A0> something like: > =A0> > =A0> =A0 apply -0 "md5 -t" `jot 10` > =A0> > =A0> would display a notable difference. > =A0> > =A0> Intel chips are quite good at running without much cooling and not > =A0> dieing, using thermal throttling to preserve the CPU. > > I guess you mean on-package, without p4tcc or ACPI throttle support? > > >From Bryce's original message: > > # Disable throttle control (and rely on EIST) > hint.p4tcc.0.disabled=3D"1" > hint.acpi_throttle.0.disabled=3D"1" > > which is sensible, and seems to have been applied to all CPUs, but fromht= tp://www.bryce.net/files/dmesg.bootwe see for each of cpu[0-7]: > > est0: on cpu0 > est0: Invalid id16 (set, cur) =3D (20, 21) > est0: Can't check freq 2667, it may be invalid > est0: Invalid id16 (set, cur) =3D (19, 21) > est0: Can't check freq 2533, it may be invalid > est0: Invalid id16 (set, cur) =3D (18, 21) > est0: Can't check freq 2400, it may be invalid > est0: Invalid id16 (set, cur) =3D (17, 21) > est0: Can't check freq 2267, it may be invalid > est0: Invalid id16 (set, cur) =3D (16, 21) > est0: Can't check freq 2133, it may be invalid > est0: Invalid id16 (set, cur) =3D (15, 21) > est0: Can't check freq 2000, it may be invalid > est0: Invalid id16 (set, cur) =3D (14, 21) > est0: Can't check freq 1867, it may be invalid > est0: Invalid id16 (set, cur) =3D (13, 21) > est0: Can't check freq 1733, it may be invalid > est0: Invalid id16 (set, cur) =3D (12, 21) > est0: Can't check freq 1600, it may be invalid > > which looks a bit ominous? =A0What does 'sysctl hw.acpi dev.cpu' say? hw.acpi.supported_sleep_state: S1 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: S1 hw.acpi.suspend_state: NONE hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 0 hw.acpi.verbose: 1 hw.acpi.disable_on_reboot: 0 hw.acpi.handle_reboot: 0 hw.acpi.reset_video: 0 hw.acpi.cpu.cx_lowest: C1 dev.cpu.0.%desc: ACPI CPU dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=3D\_PR_.P001 dev.cpu.0.%pnpinfo: _HID=3Dnone _UID=3D0 dev.cpu.0.%parent: acpi0 dev.cpu.0.freq: 2801 dev.cpu.0.freq_levels: 2801/143000 2667/114000 2533/100000 2400/87000 2267/76000 2133/68000 2000/59000 1867/51000 1733/44000 1600/40000 dev.cpu.0.cx_supported: C1/32 C2/96 C3/128 dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% last 372us dev.cpu.0.temperature: 51.0C dev.cpu.1.%desc: ACPI CPU dev.cpu.1.%driver: cpu dev.cpu.1.%location: handle=3D\_PR_.P002 dev.cpu.1.%pnpinfo: _HID=3Dnone _UID=3D0 dev.cpu.1.%parent: acpi0 dev.cpu.1.cx_supported: C1/32 C2/96 C3/128 dev.cpu.1.cx_lowest: C1 dev.cpu.1.cx_usage: 100.00% 0.00% 0.00% last 178us dev.cpu.1.temperature: 51.0C dev.cpu.2.%desc: ACPI CPU dev.cpu.2.%driver: cpu dev.cpu.2.%location: handle=3D\_PR_.P003 dev.cpu.2.%pnpinfo: _HID=3Dnone _UID=3D0 dev.cpu.2.%parent: acpi0 dev.cpu.2.cx_supported: C1/32 C2/96 C3/128 dev.cpu.2.cx_lowest: C1 dev.cpu.2.cx_usage: 100.00% 0.00% 0.00% last 386us dev.cpu.2.temperature: 48.0C dev.cpu.3.%desc: ACPI CPU dev.cpu.3.%driver: cpu dev.cpu.3.%location: handle=3D\_PR_.P004 dev.cpu.3.%pnpinfo: _HID=3Dnone _UID=3D0 dev.cpu.3.%parent: acpi0 dev.cpu.3.cx_supported: C1/32 C2/96 C3/128 dev.cpu.3.cx_lowest: C1 dev.cpu.3.cx_usage: 100.00% 0.00% 0.00% last 391us dev.cpu.3.temperature: 49.0C dev.cpu.4.%desc: ACPI CPU dev.cpu.4.%driver: cpu dev.cpu.4.%location: handle=3D\_PR_.P005 dev.cpu.4.%pnpinfo: _HID=3Dnone _UID=3D0 dev.cpu.4.%parent: acpi0 dev.cpu.4.cx_supported: C1/32 C2/96 C3/128 dev.cpu.4.cx_lowest: C1 dev.cpu.4.cx_usage: 100.00% 0.00% 0.00% last 413us dev.cpu.4.temperature: 50.0C dev.cpu.5.%desc: ACPI CPU dev.cpu.5.%driver: cpu dev.cpu.5.%location: handle=3D\_PR_.P006 dev.cpu.5.%pnpinfo: _HID=3Dnone _UID=3D0 dev.cpu.5.%parent: acpi0 dev.cpu.5.cx_supported: C1/32 C2/96 C3/128 dev.cpu.5.cx_lowest: C1 dev.cpu.5.cx_usage: 100.00% 0.00% 0.00% last 381us dev.cpu.5.temperature: 51.0C dev.cpu.6.%desc: ACPI CPU dev.cpu.6.%driver: cpu dev.cpu.6.%location: handle=3D\_PR_.P007 dev.cpu.6.%pnpinfo: _HID=3Dnone _UID=3D0 dev.cpu.6.%parent: acpi0 dev.cpu.6.cx_supported: C1/32 C2/96 C3/128 dev.cpu.6.cx_lowest: C1 dev.cpu.6.cx_usage: 100.00% 0.00% 0.00% last 411us dev.cpu.6.temperature: 48.0C dev.cpu.7.%desc: ACPI CPU dev.cpu.7.%driver: cpu dev.cpu.7.%location: handle=3D\_PR_.P008 dev.cpu.7.%pnpinfo: _HID=3Dnone _UID=3D0 dev.cpu.7.%parent: acpi0 dev.cpu.7.cx_supported: C1/32 C2/96 C3/128 dev.cpu.7.cx_lowest: C1 dev.cpu.7.cx_usage: 100.00% 0.00% 0.00% last 330us dev.cpu.7.temperature: 48.0C > > Running multiple md5s or say 'dd if=3D/dev/random of=3D/dev/null bs=3D1M = &' > in a short sleep loop echoing "`date` `sysctl -n dev.cpu.0.freq` plus > indicative coretemp sysctls might reveal something as it heats up? =A0 > Surprisingly (?) the dmesg shows no ACPI thermal zones (detected). I don't think it is temperature, I have never seen temps above the low 60's C and the speed never goes down from 2.8 Ghz. This is what I see when running your dd for a while: bryce@tahiti[~]>sysctl -a | grep temperature dev.cpu.0.temperature: 55.0C dev.cpu.1.temperature: 55.0C dev.cpu.2.temperature: 51.0C dev.cpu.3.temperature: 52.0C dev.cpu.4.temperature: 59.0C dev.cpu.5.temperature: 61.0C dev.cpu.6.temperature: 51.0C dev.cpu.7.temperature: 52.0C bryce@tahiti[~]>sysctl -n dev.cpu.0.freq 2801 > > cheers, Ian > > _______________________________________________ > freebsd-sta...@freebsd.org mailing listhttp://lists.freebsd.org/mailman/l= istinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 00:54:47 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1667106564A for ; Thu, 23 Sep 2010 00:54:47 +0000 (UTC) (envelope-from bryce@bryce.net) Received: from mail-yx0-f186.google.com (mail-yx0-f186.google.com [209.85.213.186]) by mx1.freebsd.org (Postfix) with ESMTP id 630398FC08 for ; Thu, 23 Sep 2010 00:54:46 +0000 (UTC) Received: by yxf34 with SMTP id 34so1010172yxf.13 for ; Wed, 22 Sep 2010 17:54:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.91.103.11 with SMTP id f11mr182646agm.59.1285203286423; Wed, 22 Sep 2010 17:54:46 -0700 (PDT) Received: by g18g2000vbn.googlegroups.com with HTTP; Wed, 22 Sep 2010 17:54:46 -0700 (PDT) Date: Wed, 22 Sep 2010 17:54:46 -0700 (PDT) In-Reply-To: X-IP: 70.140.155.124 References: User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10,gzip(gfe) Message-ID: From: Bryce To: Jeremy Chadwick Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 00:54:47 -0000 On Sep 22, 3:43=A0am, free...@jdc.parodius.com (Jeremy Chadwick) wrote: > On Wed, Sep 22, 2010 at 03:30:33AM -0500, Adam Vande More wrote: > > On Wed, Sep 22, 2010 at 3:12 AM, Peter Jeremy wro= te: > > > > I think something is badly wrong here. =A0That's less than 1/2 the sp= eed > > > of my Athlon 4850e (2.5GHz) and only 60% more than my Atom N270. =A0N= one > > > of the other figures you posted look anomolous. =A0Are you sure the C= PU > > > is actually running at full speed and you haven't done something like > > > disable the caches in BIOS? > > > FWIW: > > > FreeBSD galacticdominator.com 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #1:= Sun > > Jun 20 21:05:37 CDT 2010 > > a...@galacticdominator.com:/usr/obj/usr/src/sys/GENERIC > > amd64 > > CPU: Intel(R) Core(TM) i7 CPU =A0 =A0 =A0 =A0 870 =A0@ 2.93GHz (2940.64= -MHz K8-class > > CPU) > > > MD5 time trial. Digesting 100000 10000-byte blocks ... done > > Digest =3D 766a2bb5d24bddae466c572bcabca3ee > > Time =3D 2.012719 seconds > > Speed =3D 496840352.000000 bytes/second > > > vmstat > > -i > > > interrupt =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0total > > rate > > > irq16: vgapci0+ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 10720642 =A0 =A0 =A0 = =A0 54 > > irq18: fwohci0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 2 =A0 = =A0 =A0 =A0 =A00 > > irq23: ehci1 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0623712 =A0 =A0 = =A0 =A0 =A03 > > cpu0: timer =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0393496151 =A0 =A0 = =A0 1996 > > irq256: hdac0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A08063581 =A0 =A0 = =A0 =A0 40 > > irq257: re0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A04136265 =A0 =A0 = =A0 =A0 20 > > irq259: ahci1 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01925783 =A0 =A0 = =A0 =A0 =A09 > > cpu1: timer =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0393494902 =A0 =A0 = =A0 1996 > > cpu6: timer =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0393494606 =A0 =A0 = =A0 1996 > > cpu5: timer =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0393494653 =A0 =A0 = =A0 1996 > > cpu7: timer =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0393494701 =A0 =A0 = =A0 1996 > > cpu4: timer =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0393494785 =A0 =A0 = =A0 1996 > > cpu3: timer =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0393494732 =A0 =A0 = =A0 1996 > > cpu2: timer =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0393494404 =A0 =A0 = =A0 1996 > > Total =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 3173428919 =A0 = =A0 =A016102 > > > His interrupts seem high compared to this setup, but I don't what expec= ted > > values should be. > > How are his interrupt rates "higher" than yours? =A0If you're focused on > the cpuX entries, don't be. > > To the OP: > > 1) I don't see how/why USB Legacy support would have anything to do with > your problem (meaning: you stated that things "improved a little" if you > disabled USB Legacy support in the BIOS, which makes no sense given what > that option does). The machine runs *MUCH* slower if Legacy BIOS is not disabled. Just booting up is excruciating, and takes forever. > > 2) There's been a discussion on -stable about FreeBSD incorrectly > determining different kinds of CPU characteristics on newer processors > like the i7, with HTT in use. =A0I can dig up the thread if you'd like. > It does include a patch. Yes, I'd like that. In case this helps: kern.sched.topology_spec: 0, 1, 2, 3, 4, 5, 6, 7 0, 1, 2, 3, 4, 5, 6, 7 0, 1 THREAD groupSMT group 2, 3 THREAD groupSMT group 4, 5 THREAD groupSMT group 6, 7 THREAD groupSMT group > > 3) Reset the BIOS settings to Factory Defaults ("Load Setup Defaults" > or the like), and then write down whatever you change, then post the > changes here. After resetting BIOS, I make the following changes: - Disable Legacy BIOS - Change drive controller from enhanced mode to AHCI and for your #4, the temp is almost always between 49-60 degrees C and the cpu freq is always 2801. > > -- > | Jeremy Chadwick =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 j...@parodius.com | > | Parodius Networking =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0http://w= ww.parodius.com/| > | UNIX Systems Administrator =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Mountain = View, CA, USA | > | Making life hard for others since 1977. =A0 =A0 =A0 =A0 =A0 =A0 =A0PGP:= 4BD6C0CB | > > _______________________________________________ > freebsd-sta...@freebsd.org mailing listhttp://lists.freebsd.org/mailman/l= istinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" I am not running powerd as I saw odd behavior and wanted to get a know good before introducing other variables. ::Bryce:: From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 01:44:33 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2987E106566B for ; Thu, 23 Sep 2010 01:44:33 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id C8F308FC08 for ; Thu, 23 Sep 2010 01:44:32 +0000 (UTC) Received: by qyk31 with SMTP id 31so6783230qyk.13 for ; Wed, 22 Sep 2010 18:44:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=8sn0mPncoZY6bI9HnsKwWEW9yKDoIXRyRy3Akuey60Y=; b=Hb3+nnFCncNpXwxM5MVDfFohnO7vaFDe7Moh2Mhry7pzNU/y5Bd3IGPink3YvZZIpM +aMo7BtPAgqQVkr/AJ92Zf/at8d81d0lEPSF1A4L502TpB165HLpd4+uR6/yskA2oowS KTtoZaAebRyL46CuCaR6MNgdrsl1l0u2poDBY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=dyi4sIHcv0geBwezuMQJnzE1zge6QDmF/Te+9kvAFOjBS/aBOhE3YyEAL3f1jWciPm mpJDQj1PQ90ofUmw5T6/87rivykjhFlHwpC6xeRfUYkysIfRD/v9V8S9OV3LpHxVk85r RsUnILUNBeRrdX85FDpJjwJOdwKnWQn/dNUpo= Received: by 10.224.60.131 with SMTP id p3mr768685qah.119.1285206271182; Wed, 22 Sep 2010 18:44:31 -0700 (PDT) Received: from centel.dataix.local (adsl-99-19-43-205.dsl.klmzmi.sbcglobal.net [99.19.43.205]) by mx.google.com with ESMTPS id t24sm265914qcs.35.2010.09.22.18.44.29 (version=SSLv3 cipher=RC4-MD5); Wed, 22 Sep 2010 18:44:29 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C9AB0FC.9000703@DataIX.net> Date: Wed, 22 Sep 2010 21:44:28 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.9) Gecko/20100917 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Rui Paulo References: <7EDB90C5-D638-44AB-80B9-AF2CDC566231@FreeBSD.org> In-Reply-To: <7EDB90C5-D638-44AB-80B9-AF2CDC566231@FreeBSD.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: HEADS UP: instability on stable/8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 01:44:33 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/22/2010 13:23, Rui Paulo wrote: > Hi, While I'm merging the userland DTrace bits to stable/8 you might > experience some instability if you use DTrace. If you use DTrace, I > suggest you don't try to upgrade during the next 5 days. > > Thanks for your patience, -- Rui Paulo > Thank you Rui this is much appreciated. If there is a specific version when you start those commits could that be noted as well on this thread ? Thanks again, - -- jhell,v -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJMmrD7AAoJEJBXh4mJ2FR+cjgH/jbe3+JPdRJvsrD3oU31PMUb yZJgzzLGh2EDCdx7ADkOD/P/Bm4jWS0vxEFtzNH/rq7tSgcGYpLi0Btre/wE16BY WJQEssJUerwJ2qNMNnfLAZySJLxC2Bz3HXwvLsxOwhRRNDAWj+Mstzqakd5F+V0W kQvvHWmDfGYmWoloE6K++cj+Q8YjHVz6qHqf2vcmGCerAmvBE9/5xOfJqAGsZKoR aH//luRPH1GUroUMl6hi+59NtSDaONokAR2Ot0FT4G3jDRbetngkJAyrXIMSmNdl JBeAx2yY+P+v9pyl3Wir5FhH08wxJgJBeIy+n4W8z/fYyFcUmGC7sOiKyFABprE= =YFQU -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 04:51:01 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E48A9106566B for ; Thu, 23 Sep 2010 04:51:01 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [76.96.30.32]) by mx1.freebsd.org (Postfix) with ESMTP id C54918FC13 for ; Thu, 23 Sep 2010 04:51:01 +0000 (UTC) Received: from omta16.emeryville.ca.mail.comcast.net ([76.96.30.72]) by qmta03.emeryville.ca.mail.comcast.net with comcast id A4Uj1f0051ZMdJ4A34r1mM; Thu, 23 Sep 2010 04:51:01 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta16.emeryville.ca.mail.comcast.net with comcast id A4qz1f00F3LrwQ28c4r0jy; Thu, 23 Sep 2010 04:51:00 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id A0A699B418; Wed, 22 Sep 2010 21:50:59 -0700 (PDT) Date: Wed, 22 Sep 2010 21:50:59 -0700 From: Jeremy Chadwick To: Bryce Message-ID: <20100923045059.GA29396@icarus.home.lan> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable@freebsd.org Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 04:51:02 -0000 On Wed, Sep 22, 2010 at 05:54:46PM -0700, Bryce wrote: > On Sep 22, 3:43 am, free...@jdc.parodius.com (Jeremy Chadwick) wrote: > > On Wed, Sep 22, 2010 at 03:30:33AM -0500, Adam Vande More wrote: > > > On Wed, Sep 22, 2010 at 3:12 AM, Peter Jeremy wrote: > > > > > > I think something is badly wrong here.  That's less than 1/2 the speed > > > > of my Athlon 4850e (2.5GHz) and only 60% more than my Atom N270.  None > > > > of the other figures you posted look anomolous.  Are you sure the CPU > > > > is actually running at full speed and you haven't done something like > > > > disable the caches in BIOS? > > > > > FWIW: > > > > > FreeBSD galacticdominator.com 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #1: Sun > > > Jun 20 21:05:37 CDT 2010 > > > a...@galacticdominator.com:/usr/obj/usr/src/sys/GENERIC > > > amd64 > > > CPU: Intel(R) Core(TM) i7 CPU         870  @ 2.93GHz (2940.64-MHz K8-class > > > CPU) > > > > > MD5 time trial. Digesting 100000 10000-byte blocks ... done > > > Digest = 766a2bb5d24bddae466c572bcabca3ee > > > Time = 2.012719 seconds > > > Speed = 496840352.000000 bytes/second > > > > > vmstat > > > -i > > > > > interrupt                          total > > > rate > > > > > irq16: vgapci0+                 10720642         54 > > > irq18: fwohci0                         2          0 > > > irq23: ehci1                      623712          3 > > > cpu0: timer                    393496151       1996 > > > irq256: hdac0                    8063581         40 > > > irq257: re0                      4136265         20 > > > irq259: ahci1                    1925783          9 > > > cpu1: timer                    393494902       1996 > > > cpu6: timer                    393494606       1996 > > > cpu5: timer                    393494653       1996 > > > cpu7: timer                    393494701       1996 > > > cpu4: timer                    393494785       1996 > > > cpu3: timer                    393494732       1996 > > > cpu2: timer                    393494404       1996 > > > Total                         3173428919      16102 > > > > > His interrupts seem high compared to this setup, but I don't what expected > > > values should be. > > > > How are his interrupt rates "higher" than yours?  If you're focused on > > the cpuX entries, don't be. > > > > To the OP: > > > > 1) I don't see how/why USB Legacy support would have anything to do with > > your problem (meaning: you stated that things "improved a little" if you > > disabled USB Legacy support in the BIOS, which makes no sense given what > > that option does). > > The machine runs *MUCH* slower if Legacy BIOS is not disabled. Just > booting up is excruciating, and takes forever. I'm not sure what "Legacy BIOS" is (you mention it twice in your mail), but I think it's just a typo for "Legacy USB" or "USB Legacy". Regarding "the machine runs much slower", can you provide something as simple as "md5 -t" both with the option enabled and with the option disabled? System boot time increasing due to this option wouldn't surprise me; I've battled Supermicro in the past over USB-related issues during or after BIOS POST (though they were specific to booting from USB flash drives): http://koitsu.wordpress.com/2008/04/05/supermicro-pdsmi-bios-bugs/ http://koitsu.wordpress.com/2008/07/10/supermicro-pdsmi-bios-bugs-finale/ I've run into other BIOS bugs as well: http://koitsu.wordpress.com/2009/01/06/supermicro-x7sba-and-ecc-ram-part-1/ http://koitsu.wordpress.com/2009/01/22/supermicro-x7sba-and-ecc-ram-finale/ I hate defaulting to this kind of response, but I assume you're running the latest available BIOS for your mainboard? > > 2) There's been a discussion on -stable about FreeBSD incorrectly > > determining different kinds of CPU characteristics on newer processors > > like the i7, with HTT in use.  I can dig up the thread if you'd like. > > It does include a patch. > > Yes, I'd like that. In case this helps: > > kern.sched.topology_spec: > > 0, 1, 2, 3, 4, 5, 6, 7 > > > 0, 1, 2, 3, 4, 5, 6, 7 > > > 0, 1 > THREAD group name="SMT">SMT group > > > 2, 3 > THREAD group name="SMT">SMT group > > > 4, 5 > THREAD group name="SMT">SMT group > > > 6, 7 > THREAD group name="SMT">SMT group > > > > > > Worth reading -- apparently you're not the only one. Not sure if your boards or setups are identical though: http://lists.freebsd.org/pipermail/freebsd-stable/2010-May/056591.html http://lists.freebsd.org/pipermail/freebsd-stable/2010-May/056607.html http://lists.freebsd.org/pipermail/freebsd-stable/2010-May/thread.html#56591 As for the Intel processor topology patch: http://lists.freebsd.org/pipermail/freebsd-stable/2010-September/058668.html http://lists.freebsd.org/pipermail/freebsd-stable/2010-September/thread.html#58668 > > 3) Reset the BIOS settings to Factory Defaults ("Load Setup Defaults" > > or the like), and then write down whatever you change, then post the > > changes here. > > After resetting BIOS, I make the following changes: > > - Disable Legacy BIOS > - Change drive controller from enhanced mode to AHCI > > and for your #4, the temp is almost always between 49-60 degrees C > and the cpu freq is always 2801. > > I am not running powerd as I saw odd behavior and wanted to get a know > good before introducing other variables. I think your core temperatures are fine -- they look about right for Core i7 CPUs (a few Celsius on the high side, but that's going to vary from environment to environment). -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 06:24:09 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D5FE1065673 for ; Thu, 23 Sep 2010 06:24:09 +0000 (UTC) (envelope-from rpaulo@freebsd.org) Received: from karen.lavabit.com (karen.lavabit.com [72.249.41.33]) by mx1.freebsd.org (Postfix) with ESMTP id 077658FC21 for ; Thu, 23 Sep 2010 06:24:08 +0000 (UTC) Received: from d.earth.lavabit.com (d.earth.lavabit.com [192.168.111.13]) by karen.lavabit.com (Postfix) with ESMTP id C039B11B81C; Thu, 23 Sep 2010 01:24:07 -0500 (CDT) Received: from 10.0.10.3 (221.163.108.93.rev.vodafone.pt [93.108.163.221]) by lavabit.com with ESMTP id QUFIZGPNMYSZ; Thu, 23 Sep 2010 01:24:07 -0500 Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Rui Paulo In-Reply-To: <4C9AB0FC.9000703@DataIX.net> Date: Thu, 23 Sep 2010 07:24:04 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <9B672590-D867-478A-B9B5-B8A30546F318@FreeBSD.org> References: <7EDB90C5-D638-44AB-80B9-AF2CDC566231@FreeBSD.org> <4C9AB0FC.9000703@DataIX.net> To: jhell X-Mailer: Apple Mail (2.1081) Cc: stable@freebsd.org Subject: Re: HEADS UP: instability on stable/8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 06:24:09 -0000 On 23 Sep 2010, at 02:44, jhell wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > On 09/22/2010 13:23, Rui Paulo wrote: >> Hi, While I'm merging the userland DTrace bits to stable/8 you might >> experience some instability if you use DTrace. If you use DTrace, I >> suggest you don't try to upgrade during the next 5 days. >>=20 >> Thanks for your patience, -- Rui Paulo >>=20 >=20 > Thank you Rui this is much appreciated. If there is a specific version > when you start those commits could that be noted as well on this = thread ? I haven't merged anything yet because I'm stuck with a technical = discussion about whether or not one particular change (not DTrace = related) breaks KBI. I'll let you know when I start merging things. Regards, -- Rui Paulo From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 08:26:28 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 664A6106566C for ; Thu, 23 Sep 2010 08:26:28 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id E12428FC08 for ; Thu, 23 Sep 2010 08:26:27 +0000 (UTC) Received: by bwz15 with SMTP id 15so1402463bwz.13 for ; Thu, 23 Sep 2010 01:26:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=G3QyypNvPEXLlK2r3p4Jqr5+xOOgYeKy9/YQIEqj/Zo=; b=PcUgrEhn0hdH2vhAOzuQusJPGBUULMds47B/+rjVxyZ0RiAodWSE8CgS0ghyUHkIqT JYda+etRlxNShCmC0X80I+xJCjnOOMTkNgYxkwBiNIriM+wlbJcpNZjb8h5bHVhBmgWB 8X3OL6IDOFvLl/+BIkw+cc1gJVpc9D0G0DS6I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=tZMCv4NC2Ii78xDWPfaYWbdeuaIcj0d4w86FGCtjc54oTWoAZXlAxVkr7I3exDEObt Umote3f/pm2fhQq5pyvzfVSEPjv1GrJKTquW2hdhytLX4en5aGfM7Cp1GVZGD1t2Aum0 2G45ng2kzEUU/ssPnPF/3dhN63Nofv30a33Ss= Received: by 10.204.84.37 with SMTP id h37mr738836bkl.201.1285230386963; Thu, 23 Sep 2010 01:26:26 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id s34sm390771bkk.1.2010.09.23.01.26.24 (version=SSLv3 cipher=RC4-MD5); Thu, 23 Sep 2010 01:26:25 -0700 (PDT) Sender: Alexander Motin Message-ID: <4C9B0F2C.20601@FreeBSD.org> Date: Thu, 23 Sep 2010 11:26:20 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.24 (X11/20100402) MIME-Version: 1.0 To: Bryce , FreeBSD Stable References: In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 08:26:28 -0000 Bryce wrote: > I don't think it is temperature, I have never seen temps above the low > 60's C and the speed never goes down from 2.8 Ghz. This is what I see > when running your dd for a while: > > bryce@tahiti[~]>sysctl -a | grep temperature > dev.cpu.0.temperature: 55.0C > dev.cpu.1.temperature: 55.0C > dev.cpu.2.temperature: 51.0C > dev.cpu.3.temperature: 52.0C > dev.cpu.4.temperature: 59.0C > dev.cpu.5.temperature: 61.0C > dev.cpu.6.temperature: 51.0C > dev.cpu.7.temperature: 52.0C > bryce@tahiti[~]>sysctl -n dev.cpu.0.freq > 2801 Looks not bad, but I would checked it during good compilation, using all cores. Just to compare, my Core i7-870 with boxed cooler reports: 31C being idle with tuned power management, 53C being idle without any power management, 85C during `make -j16`. That system did `make -j16 universe` in about 3 hours AFAIR. PS: AFAIK dev.cpu.0.freq won't report you if frequency was lowered due to overheating. -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 11:56:33 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9DDFB1065693; Thu, 23 Sep 2010 11:56:33 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B5DCF8FC1B; Thu, 23 Sep 2010 11:56:32 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA23094; Thu, 23 Sep 2010 14:56:29 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1OykPd-00059l-Jk; Thu, 23 Sep 2010 14:56:29 +0300 Message-ID: <4C9B406D.3000201@icyb.net.ua> Date: Thu, 23 Sep 2010 14:56:29 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20100918 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: Alexander Motin References: <4C9B0F2C.20601@FreeBSD.org> In-Reply-To: <4C9B0F2C.20601@FreeBSD.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable , Bryce Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 11:56:33 -0000 on 23/09/2010 11:26 Alexander Motin said the following: > PS: AFAIK dev.cpu.0.freq won't report you if frequency was lowered due > to overheating. I think that you are correct about this. And last I checked we simply ignored thermal throttling interrupt. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 12:38:01 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3856106566C; Thu, 23 Sep 2010 12:38:01 +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 458B18FC14; Thu, 23 Sep 2010 12:38:00 +0000 (UTC) Received: from 223.30.70.115.static.exetel.com.au (223.30.70.115.static.exetel.com.au [115.70.30.223]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id o8NCbhF0000914 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 23 Sep 2010 22:07:51 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: "Daniel O'Connor" In-Reply-To: <4C9B406D.3000201@icyb.net.ua> Date: Thu, 23 Sep 2010 22:07:39 +0930 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4C9B0F2C.20601@FreeBSD.org> <4C9B406D.3000201@icyb.net.ua> To: Andriy Gapon X-Mailer: Apple Mail (2.1081) X-Spam-Score: 6.454 (******) BAYES_00, HELO_DYNAMIC_IPADDR2, HELO_DYNAMIC_SPLIT_IP, TVD_RCVD_IP X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: Bryce , Alexander Motin , FreeBSD Stable Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 12:38:01 -0000 On 23/09/2010, at 21:26, Andriy Gapon wrote: > on 23/09/2010 11:26 Alexander Motin said the following: >> PS: AFAIK dev.cpu.0.freq won't report you if frequency was lowered = due >> to overheating. >=20 > I think that you are correct about this. > And last I checked we simply ignored thermal throttling interrupt. I could not get cpufreq to show a lower frequency when I tried = overheating a CPU even though the performance dropped. It would be really nice if there was some notification of CPU throttling = :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 13:06:01 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6C4451065672 for ; Thu, 23 Sep 2010 13:06:01 +0000 (UTC) (envelope-from bryce@bryce.net) Received: from mail-qw0-f58.google.com (mail-qw0-f58.google.com [209.85.216.58]) by mx1.freebsd.org (Postfix) with ESMTP id 2E03E8FC08 for ; Thu, 23 Sep 2010 13:06:00 +0000 (UTC) Received: by qwf7 with SMTP id 7so4213575qwf.13 for ; Thu, 23 Sep 2010 06:06:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.125.86 with SMTP id x22mr13663vcr.31.1285247160065; Thu, 23 Sep 2010 06:06:00 -0700 (PDT) Received: by t7g2000vbj.googlegroups.com with HTTP; Thu, 23 Sep 2010 06:05:59 -0700 (PDT) Date: Thu, 23 Sep 2010 06:05:59 -0700 (PDT) In-Reply-To: X-IP: 70.140.155.124 References: User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10,gzip(gfe) Message-ID: From: Bryce To: nickolasbug@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 13:06:01 -0000 On Sep 22, 9:35=A0am, nickolas...@gmail.com wrote: > > md5 -t is quite a small benchmark, even with his misfunctioning CPU it > > took <6 seconds to complete. > > > If his problem is a misapplied heatsink/fan, then his CPU could be > > throttling when it gets hot, the hotter it gets the more it throttles, > > which could explain his massive buildworld walltime. Perhaps running > > something like: > > > =A0apply -0 "md5 -t" `jot 10` > > > would display a notable difference. > I don't think is heat & throttling related. Here's the temps while doing a make -j16 buildworld: dev.cpu.0.temperature: 57.0C dev.cpu.1.temperature: 57.0C dev.cpu.2.temperature: 54.0C dev.cpu.3.temperature: 54.0C dev.cpu.4.temperature: 57.0C dev.cpu.5.temperature: 57.0C dev.cpu.6.temperature: 55.0C dev.cpu.7.temperature: 55.0C IMO, the problem is preventing the system from even loading up the CPU's enough to even get hot - I have never seen it over 61 C. If sit & watch top -P during a buildworld, it rarely get's all 8 CPU's loaded up with idle numbers near 0%. A vast majority of the time one CPU is maxed and the others are mostly idle. > You may also run openssl speed or "linpack" test > (/usr/ports/math/linpack) or hpl (/usr/ports/benchmarks/hpl) to load > your CPU > _______________________________________________ > freebsd-sta...@freebsd.org mailing listhttp://lists.freebsd.org/mailman/l= istinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 14:35:55 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DC5B1065675; Thu, 23 Sep 2010 14:35:55 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 62ACA8FC19; Thu, 23 Sep 2010 14:35:53 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA26010; Thu, 23 Sep 2010 17:35:41 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4C9B65BC.4010305@icyb.net.ua> Date: Thu, 23 Sep 2010 17:35:40 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20100920 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: "Daniel O'Connor" References: <4C9B0F2C.20601@FreeBSD.org> <4C9B406D.3000201@icyb.net.ua> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Alexander Motin , FreeBSD Stable Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 14:35:55 -0000 on 23/09/2010 15:37 Daniel O'Connor said the following: > > On 23/09/2010, at 21:26, Andriy Gapon wrote: >> on 23/09/2010 11:26 Alexander Motin said the following: >>> PS: AFAIK dev.cpu.0.freq won't report you if frequency was lowered due >>> to overheating. >> >> I think that you are correct about this. >> And last I checked we simply ignored thermal throttling interrupt. > > I could not get cpufreq to show a lower frequency when I tried overheating a CPU even though the performance dropped. > > It would be really nice if there was some notification of CPU throttling :) cpufreq is not designed to monitor what is going on in cpu. cpufreq knows what cpu supports and knows host to set a certain frequency (performance level rather). -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 14:41:39 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1AF641065674; Thu, 23 Sep 2010 14:41:39 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id BEA478FC1C; Thu, 23 Sep 2010 14:41:38 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id o8NEfbDM011983; Thu, 23 Sep 2010 10:41:37 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o8NEfbDD011979; Thu, 23 Sep 2010 14:41:37 GMT (envelope-from tinderbox@freebsd.org) Date: Thu, 23 Sep 2010 14:41:37 GMT Message-Id: <201009231441.o8NEfbDD011979@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [releng_8 tinderbox] failure on mips/mips X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 14:41:39 -0000 TB --- 2010-09-23 11:13:24 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-09-23 11:13:24 - starting RELENG_8 tinderbox run for mips/mips TB --- 2010-09-23 11:13:24 - cleaning the object tree TB --- 2010-09-23 11:14:35 - cvsupping the source tree TB --- 2010-09-23 11:14:35 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup5.freebsd.org /tinderbox/RELENG_8/mips/mips/supfile TB --- 2010-09-23 11:18:16 - building world TB --- 2010-09-23 11:18:16 - MAKEOBJDIRPREFIX=/obj TB --- 2010-09-23 11:18:16 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-09-23 11:18:16 - TARGET=mips TB --- 2010-09-23 11:18:16 - TARGET_ARCH=mips TB --- 2010-09-23 11:18:16 - TZ=UTC TB --- 2010-09-23 11:18:16 - __MAKE_CONF=/dev/null TB --- 2010-09-23 11:18:16 - cd /src TB --- 2010-09-23 11:18:16 - /usr/bin/make -B buildworld >>> World build started on Thu Sep 23 11:18:17 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] /obj/mips/src/tmp/usr/bin/ld: BFD 2.15 [FreeBSD] 2004-05-23 assertion fail /src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elfxx-mips.c:1899 /obj/mips/src/tmp/usr/bin/ld: BFD 2.15 [FreeBSD] 2004-05-23 assertion fail /src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elfxx-mips.c:1902 /obj/mips/src/tmp/usr/bin/ld: BFD 2.15 [FreeBSD] 2004-05-23 assertion fail /src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elfxx-mips.c:1899 /obj/mips/src/tmp/usr/bin/ld: BFD 2.15 [FreeBSD] 2004-05-23 assertion fail /src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elfxx-mips.c:1902 /obj/mips/src/tmp/usr/bin/ld: BFD 2.15 [FreeBSD] 2004-05-23 assertion fail /src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elfxx-mips.c:1899 /obj/mips/src/tmp/usr/bin/ld: BFD 2.15 [FreeBSD] 2004-05-23 assertion fail /src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elfxx-mips.c:1902 /obj/mips/src/tmp/usr/bin/ld: BFD 2.15 [FreeBSD] 2004-05-23 assertion fail /src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elfxx-mips.c:1899 /obj/mips/src/tmp/usr/bin/ld: BFD 2.15 [FreeBSD] 2004-05-23 assertion fail /src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elfxx-mips.c:1902 *** Error code 1 Stop in /src/usr.bin/tftp. *** Error code 1 Stop in /src/usr.bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-09-23 14:41:37 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-09-23 14:41:37 - ERROR: failed to build world TB --- 2010-09-23 14:41:37 - 2068.47 user 6701.08 system 12493.33 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-mips-mips.full From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 16:08:43 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29385106566C for ; Thu, 23 Sep 2010 16:08:43 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from thalia-smout.broadpark.no (thalia-smout.broadpark.no [80.202.8.21]) by mx1.freebsd.org (Postfix) with ESMTP id D9D128FC08 for ; Thu, 23 Sep 2010 16:08:42 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from terra-smin.broadpark.no ([80.202.8.13]) by thalia-smout.broadpark.no (Sun Java(tm) System Messaging Server 7u3-15.01 64bit (built Feb 12 2010)) with ESMTP id <0L9700F0VJIH0R70@thalia-smout.broadpark.no> for freebsd-stable@freebsd.org; Thu, 23 Sep 2010 18:08:41 +0200 (CEST) Received: from kg-v2.kg4.no ([80.203.109.34]) by terra-smin.broadpark.no (Sun Java(tm) System Messaging Server 7u3-15.01 64bit (built Feb 12 2010)) with SMTP id <0L9700IKDJIGF3W0@terra-smin.broadpark.no> for freebsd-stable@freebsd.org; Thu, 23 Sep 2010 18:08:41 +0200 (CEST) Date: Thu, 23 Sep 2010 18:08:40 +0200 From: Torfinn Ingolfsen To: freebsd-stable@freebsd.org Message-id: <20100923180840.ac828e05.torfinn.ingolfsen@broadpark.no> In-reply-to: <4C9A7943.1020806@gmail.com> References: <4C9A7943.1020806@gmail.com> X-Mailer: Sylpheed 3.0.3 (GTK+ 2.20.1; amd64-portbld-freebsd8.0) X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH Subject: Re: wifi issues under -stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 16:08:43 -0000 On Wed, 22 Sep 2010 16:46:43 -0500 Jim Bryant wrote: > One (this one) has an intel pro wireless 3945ABG installed, which returns: > > wpi0: irq 18 at device 0.0 on pci6 > wpi0: Driver Revision 20071127 > wpi0: 0x1000 bytes of rid 0x10 res 3 failed (0, 0xffffffffffffffff). > wpi0: could not allocate memory resource > device_attach: wpi0 attach returned 6 > > and the broadcom used in the other does the exact same thing. > > I'm thinking that this isn't really a problem with the wifi, but may be > a mini-pci-e issue. More likelely, it is ACPI-related. Simply put: many laptops have broken ACPI implementations. Other OS'es might have a workaround for them, but FreeBSD does not. Since almost none of todays' laptops work correctly with ACPI disabled, this is a major pain. (Some laptops overheat when ACPI is disbled, because of disabled thermal management). You can try to figure out if the problem is acpi-related with the following hint in /boot/loader.conf (but beware of thermal problems; don't run the laptop too long with acpi disabled): hint.acpi.0.disabled="1" > does anyone know how to solve this problem? Well, if you can identify exactly where the problem is, you might be able to work around it. However, the task isn't easy. Sometimes, forcing IRQ routing might help (but at least in 7.x this only works with acpi disabled). Using other OS'es (Linux) to identify if they do something different with the resources (irq, memeory etc. for devices) migh help pointing out wherer the problem might be. However, you will be speninding some time comparing outputs from a FreeBSD verbose boot with the same information from Linux. (This thread reminds me that I should test FreeBSD 8.1 on my old Acer laptop, which have acpi problems, and haven't worked with 6.0 - 8.0.) -- Torfinn From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 16:36:26 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DD0E106566B; Thu, 23 Sep 2010 16:36:26 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 7D6E38FC1B; Thu, 23 Sep 2010 16:36:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id o8NGaHeI021629; Fri, 24 Sep 2010 02:36:18 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Fri, 24 Sep 2010 02:36:17 +1000 (EST) From: Ian Smith To: Alexander Motin In-Reply-To: <4C9B0F2C.20601@FreeBSD.org> Message-ID: <20100924022558.T11124@sola.nimnet.asn.au> References: <4C9B0F2C.20601@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: FreeBSD Stable , Bryce Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 16:36:26 -0000 On Thu, 23 Sep 2010, Alexander Motin wrote: > Bryce wrote: > > I don't think it is temperature, I have never seen temps above the low > > 60's C and the speed never goes down from 2.8 Ghz. This is what I see > > when running your dd for a while: > > > > bryce@tahiti[~]>sysctl -a | grep temperature > > dev.cpu.0.temperature: 55.0C > > dev.cpu.1.temperature: 55.0C > > dev.cpu.2.temperature: 51.0C > > dev.cpu.3.temperature: 52.0C > > dev.cpu.4.temperature: 59.0C > > dev.cpu.5.temperature: 61.0C > > dev.cpu.6.temperature: 51.0C > > dev.cpu.7.temperature: 52.0C > > bryce@tahiti[~]>sysctl -n dev.cpu.0.freq > > 2801 > > Looks not bad, but I would checked it during good compilation, using all > cores. > > Just to compare, my Core i7-870 with boxed cooler reports: > 31C being idle with tuned power management, > 53C being idle without any power management, > 85C during `make -j16`. > That system did `make -j16 universe` in about 3 hours AFAIR. > > PS: AFAIK dev.cpu.0.freq won't report you if frequency was lowered due > to overheating. Thanks, I've often wondered about that (among other things :) So not looking much like overheating. But don't these messages requoted below seem at all significant? At least, I've never seen them before: > est0: on cpu0 > est0: Invalid id16 (set, cur) = (20, 21) > est0: Can't check freq 2667, it may be invalid > est0: Invalid id16 (set, cur) = (19, 21) > est0: Can't check freq 2533, it may be invalid > est0: Invalid id16 (set, cur) = (18, 21) > est0: Can't check freq 2400, it may be invalid > est0: Invalid id16 (set, cur) = (17, 21) > est0: Can't check freq 2267, it may be invalid > est0: Invalid id16 (set, cur) = (16, 21) > est0: Can't check freq 2133, it may be invalid > est0: Invalid id16 (set, cur) = (15, 21) > est0: Can't check freq 2000, it may be invalid > est0: Invalid id16 (set, cur) = (14, 21) > est0: Can't check freq 1867, it may be invalid > est0: Invalid id16 (set, cur) = (13, 21) > est0: Can't check freq 1733, it may be invalid > est0: Invalid id16 (set, cur) = (12, 21) > est0: Can't check freq 1600, it may be invalid cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 16:42:43 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F158106564A for ; Thu, 23 Sep 2010 16:42:43 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id D8C0C8FC18 for ; Thu, 23 Sep 2010 16:42:42 +0000 (UTC) Received: by bwz15 with SMTP id 15so1803238bwz.13 for ; Thu, 23 Sep 2010 09:42:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=lC4Jqh+exugDs/OEoFPkPWg/5cdd6Gl2R1ZETEB2aVk=; b=RIZFFn6W7xS+/r3ItS9UqRMTL7LOYb0zuTqbky2RzN/oWFGwA0QUQ26jqDXL8SS1at 9GvTN6w8CVRIQzsmcZVDzHynUQiQwhFIUdo5x0NzumiFndnzvi4VvbJqZ9VQh4xL90/o kPSwk4IihY7D8riyLzOC8UctLslygkKvIiq1U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=du534UHeRhVMDCir4XbNUMbhbRicfFFMg5isH86QIOFCQrQLXnbWX4v8XYc5vwFmnM LxFOA0iyGh4viNPnvBRdLZ9oohLd+5FHEYC04wY4J3cxIHwsxbZ+HDJ0zl0YyqlrPLcw ZGbqdo+GuNcddRN86BbglDvhQbQZHPZ+Oki8A= Received: by 10.204.70.206 with SMTP id e14mr1193908bkj.143.1285260161773; Thu, 23 Sep 2010 09:42:41 -0700 (PDT) Received: from mavbook2.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id s34sm786359bkk.1.2010.09.23.09.42.39 (version=SSLv3 cipher=RC4-MD5); Thu, 23 Sep 2010 09:42:40 -0700 (PDT) Sender: Alexander Motin Message-ID: <4C9B8375.4070505@FreeBSD.org> Date: Thu, 23 Sep 2010 19:42:29 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Ian Smith References: <4C9B0F2C.20601@FreeBSD.org> <20100924022558.T11124@sola.nimnet.asn.au> In-Reply-To: <20100924022558.T11124@sola.nimnet.asn.au> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable , Bryce Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 16:42:43 -0000 Ian Smith wrote: > So not looking much like overheating. But don't these messages requoted > below seem at all significant? At least, I've never seen them before: > >> est0: on cpu0 >> est0: Invalid id16 (set, cur) = (20, 21) >> est0: Can't check freq 2667, it may be invalid >> est0: Invalid id16 (set, cur) = (19, 21) >> est0: Can't check freq 2533, it may be invalid >> est0: Invalid id16 (set, cur) = (18, 21) >> est0: Can't check freq 2400, it may be invalid >> est0: Invalid id16 (set, cur) = (17, 21) >> est0: Can't check freq 2267, it may be invalid >> est0: Invalid id16 (set, cur) = (16, 21) >> est0: Can't check freq 2133, it may be invalid >> est0: Invalid id16 (set, cur) = (15, 21) >> est0: Can't check freq 2000, it may be invalid >> est0: Invalid id16 (set, cur) = (14, 21) >> est0: Can't check freq 1867, it may be invalid >> est0: Invalid id16 (set, cur) = (13, 21) >> est0: Can't check freq 1733, it may be invalid >> est0: Invalid id16 (set, cur) = (12, 21) >> est0: Can't check freq 1600, it may be invalid They are not. It is specifics of EIST behavior on multicore CPUs. It is impossible to test P-states during driver attach (before AP CPUs started). I have already disabled this check for SMP systems. -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 16:47:08 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74E7E1065672; Thu, 23 Sep 2010 16:47:08 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id E17968FC08; Thu, 23 Sep 2010 16:47:06 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id o8NGl1Nv022246; Fri, 24 Sep 2010 02:47:01 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Fri, 24 Sep 2010 02:47:01 +1000 (EST) From: Ian Smith To: Alexander Motin In-Reply-To: <4C9B8375.4070505@FreeBSD.org> Message-ID: <20100924024527.M11124@sola.nimnet.asn.au> References: <4C9B0F2C.20601@FreeBSD.org> <20100924022558.T11124@sola.nimnet.asn.au> <4C9B8375.4070505@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: FreeBSD Stable , Bryce Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 16:47:08 -0000 On Thu, 23 Sep 2010, Alexander Motin wrote: > Date: Thu, 23 Sep 2010 19:42:29 +0300 > From: Alexander Motin > To: Ian Smith > Cc: Bryce , FreeBSD Stable > Subject: Re: SuperMicro i7 (UP) - very slow performance > > Ian Smith wrote: > > So not looking much like overheating. But don't these messages requoted > > below seem at all significant? At least, I've never seen them before: > > > >> est0: on cpu0 > >> est0: Invalid id16 (set, cur) = (20, 21) > >> est0: Can't check freq 2667, it may be invalid > >> est0: Invalid id16 (set, cur) = (19, 21) > >> est0: Can't check freq 2533, it may be invalid > >> est0: Invalid id16 (set, cur) = (18, 21) > >> est0: Can't check freq 2400, it may be invalid > >> est0: Invalid id16 (set, cur) = (17, 21) > >> est0: Can't check freq 2267, it may be invalid > >> est0: Invalid id16 (set, cur) = (16, 21) > >> est0: Can't check freq 2133, it may be invalid > >> est0: Invalid id16 (set, cur) = (15, 21) > >> est0: Can't check freq 2000, it may be invalid > >> est0: Invalid id16 (set, cur) = (14, 21) > >> est0: Can't check freq 1867, it may be invalid > >> est0: Invalid id16 (set, cur) = (13, 21) > >> est0: Can't check freq 1733, it may be invalid > >> est0: Invalid id16 (set, cur) = (12, 21) > >> est0: Can't check freq 1600, it may be invalid > > They are not. It is specifics of EIST behavior on multicore CPUs. It is > impossible to test P-states during driver attach (before AP CPUs > started). I have already disabled this check for SMP systems. Ok, thanks. That's me out of ideas .. but lurking with interest. cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 17:14:14 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7885106566C for ; Thu, 23 Sep 2010 17:14:14 +0000 (UTC) (envelope-from ozkan.kirik@gmail.com) Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7FAA48FC0A for ; Thu, 23 Sep 2010 17:14:14 +0000 (UTC) Received: by pxi17 with SMTP id 17so647436pxi.13 for ; Thu, 23 Sep 2010 10:14:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=WfLD8LdLIhZBoLAwACaktb9XEDzkq/jsbjNA1ePD0FE=; b=pnY0XvD7tvHM4zmg8rEIE53bzzqzdYwrylOcJwmJpNrmywlGjRNL/fiXvUke8oahAs fF+psOdJf+/r2NW8roLUwWpyR8m0oLPfc6u61dEJfB3DPOgFpn57abMNWTK0gam0eUnM YWHKtnPW3wERSOIBdYhDtiif60o1beL8P0zGg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=cpUQaueeuymlZwVSks/c3HlOLfz452slPGRbDGgkYmiFKvsGYL3m/JY7HFDvT5hv0E M/lrNzr6nWl/2mteSTyYoPWRuRsrGggT1ZJvL3tnZLQDuW2cyPUN7ht6YZP8yb0uQ/Gq 4py2GVsLq6tHqjVKaVmeIB2w2lvlVPRaxxt0g= MIME-Version: 1.0 Received: by 10.142.43.14 with SMTP id q14mr1631696wfq.221.1285260188360; Thu, 23 Sep 2010 09:43:08 -0700 (PDT) Received: by 10.143.24.36 with HTTP; Thu, 23 Sep 2010 09:43:08 -0700 (PDT) Date: Thu, 23 Sep 2010 19:43:08 +0300 Message-ID: From: =?ISO-8859-1?Q?=D6zkan_KIRIK?= To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: kernel: arpresolve: can't allocate llinfo for 10.6.10.240 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 17:14:14 -0000 Hi all, I'm using FreeBSD 8.1-201008 amd64 snapshot. When I watch log messages I see "kernel: arpresolve: can't allocate llinfo for 10.0.16.251" messages repeating once per 2 minutes. When I saw this log, default router changes unexpectedly. Normally default router should be 193.X.Y.Z, but after this log default router shown as 10.0.16.251. And routing really changes. I watch the changes on routing table via "route -n monitor" command. I couldnt see anything about default route changes. I tried with both net.inet net.inet.flowtable.enable=3D0 and net.inet.flowtable.enable=3D1. Nothing changes. I think, arp table overflows and overwrites the routing table. I captured the packges while this problem occurs. the tcpdump file: http://193.255.128.30/~ryland/flowdata_10_0_16_251 tcpdump -w /home/flowdata_10_0_16_251 -ni bce0.116 host 10.0.16.251 system has 2x 4core Xeon, 32GB ram, about 5000 clients and 152 if_vlan interfaces, 5 real NICs. Any ideas? Regards, =D6zkan KIRIK Mersin University @ Turkey From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 18:17:42 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E007106566B for ; Thu, 23 Sep 2010 18:17:42 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id E25E98FC1D for ; Thu, 23 Sep 2010 18:17:41 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 8CFB746B2D; Thu, 23 Sep 2010 14:17:41 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id B92048A04E; Thu, 23 Sep 2010 14:17:40 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Thu, 23 Sep 2010 14:17:02 -0400 User-Agent: KMail/1.13.5 (FreeBSD/7.3-CBSD-20100819; KDE/4.4.5; amd64; ; ) References: <4C9A7943.1020806@gmail.com> <20100923180840.ac828e05.torfinn.ingolfsen@broadpark.no> In-Reply-To: <20100923180840.ac828e05.torfinn.ingolfsen@broadpark.no> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201009231417.02965.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Thu, 23 Sep 2010 14:17:40 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Torfinn Ingolfsen Subject: Re: wifi issues under -stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 18:17:42 -0000 On Thursday, September 23, 2010 12:08:40 pm Torfinn Ingolfsen wrote: > On Wed, 22 Sep 2010 16:46:43 -0500 > Jim Bryant wrote: > > > One (this one) has an intel pro wireless 3945ABG installed, which returns: > > > > wpi0: irq 18 at device 0.0 on pci6 > > wpi0: Driver Revision 20071127 > > wpi0: 0x1000 bytes of rid 0x10 res 3 failed (0, 0xffffffffffffffff). > > wpi0: could not allocate memory resource > > device_attach: wpi0 attach returned 6 > > > > and the broadcom used in the other does the exact same thing. > > > > I'm thinking that this isn't really a problem with the wifi, but may be > > a mini-pci-e issue. > > More likelely, it is ACPI-related. Simply put: many laptops have > broken ACPI implementations. Other OS'es might have a workaround for > them, but FreeBSD does not. Well, in this case the breakage is probably that something in the ACPI initialization clears the resource ranges in a PCI-PCI bridge. However, I would not quite say that ACPI is broken in that case as FreeBSD's PCI-PCI bridge driver needs to handle this sort of case anyway in order to truly handle hotplug devices and 'PNP OS == YES', so this is really FreeBSD's fault rather than ACPI or the BIOS. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 18:38:40 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E76F9106564A for ; Thu, 23 Sep 2010 18:38:40 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 739268FC1B for ; Thu, 23 Sep 2010 18:38:40 +0000 (UTC) Received: by wyb33 with SMTP id 33so2518693wyb.13 for ; Thu, 23 Sep 2010 11:38:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=mrBly7zNJR6WY6GpnaZmLkpQ8k/9GlGcyUqWs8H3pqY=; b=uAdaZpEsnguQXRjyObe4/PSVGbDfYrv3YIpSSiA/cgkymfuMrgcGpTCXK/Yes0bgVU 9repCAxNro1d9gb94MEmWCSyOmRUH3hocwNIzfBLDSbIVZ4Vgw/jAyiRv+ep5pBq7Lzi +eSPmJs97FlFXUcZCS+7jNVNlBaW5JTlpGgSI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=Ez5rhFLboYH1vtkh85Q9OM5xvkLnCT+FnnTgT0DV/KyK68zSvwlQXYU4TgFwQGaBa9 fDabqLJmPiZiAZKSK+k30RoVMr8ptqIekwJhW6Z+85dC6BAOJjkgPbsvZc4I158IIKc2 tk+utz0JZkfBsdRrHPXOR/UZd5CKjj9YPn/eY= Received: by 10.227.69.134 with SMTP id z6mr1715160wbi.201.1285267119346; Thu, 23 Sep 2010 11:38:39 -0700 (PDT) Received: from centel.dataix.local ([99.19.43.205]) by mx.google.com with ESMTPS id m5sm964429wbc.15.2010.09.23.11.38.36 (version=SSLv3 cipher=RC4-MD5); Thu, 23 Sep 2010 11:38:37 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C9B9EAB.4050704@DataIX.net> Date: Thu, 23 Sep 2010 14:38:35 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.9) Gecko/20100917 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Michael BlackHeart References: <20100916164930.GA31869@icarus.home.lan> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Jeremy Chadwick Subject: Re: FreeBSD 8.1 Stable Unreasanoble Rebooting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 18:38:41 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/16/2010 15:33, Michael BlackHeart wrote: > 2010/9/16 Jeremy Chadwick : >> On Thu, Sep 16, 2010 at 08:37:29PM +0400, Michael BlackHeart wrote: >>> Today I've got a pretty strange event. It looks like a reboot but >>> unreasonable as far as I see. Before server's uptime was over month, >>> it's sometimes have to reboot for kernel updates or somethings like >>> that. I've digen all logs and didn't find a reason, so here they all. >>> >>> auth.log >>> Sep 16 13:59:58 diablo sshd[2284]: Received signal 15; terminating. >>> Sep 16 14:04:26 diablo sshd[2290]: Server listening on 0.0.0.0 port 22442. >>> >>> cron - nothing >>> debug.log - nothing >>> dmesg - nothing >>> >>> messages >>> Sep 16 13:44:55 diablo transmission-daemon[7965]: Couldn't create >>> socket: Protocol not supported (fdlimit.c:651) >>> Sep 16 13:45:31 diablo last message repeated 5 times >>> Sep 16 13:47:23 diablo last message repeated 13 times >>> Sep 16 13:57:40 diablo last message repeated 51 times >>> Sep 16 13:59:48 diablo last message repeated 12 times >>> Sep 16 14:00:18 diablo named[1575]: stopping command channel on 127.0.0.1#953 >>> Sep 16 14:00:18 diablo named[1575]: exiting >>> Sep 16 14:00:18 diablo syslogd: exiting on signal 15 >>> Sep 16 14:02:31 diablo syslogd: kernel boot file is /boot/kernel/kernel >>> Sep 16 14:02:31 diablo kernel: Copyright (c) 1992-2010 The FreeBSD Project. >>> {...} >> >> This sure looks like a legitimate reboot to me (e.g. shutdown -r now); >> note how your system daemons (named, syslogd) are being shut down with >> SIGTERM. You can check with "last" (shutdown/reboot vs. crash). >> >> >> I would highly recommend taking this machine offline and reinstalling >> the OS, in addition to newfs'ing all existing filesystems (restore from >> last known good backup). buildworld/installworld and >> buildkernel/installkernel may not be enough depending on what the >> individual did. It's likely the machine could be compromised in some >> way, especially if there's any service on it which is public-facing, >> regardless of authentication mechanisms you've deployed in front of it. >> >> >> -- >> | Jeremy Chadwick jdc@parodius.com | >> | Parodius Networking http://www.parodius.com/ | >> | UNIX Systems Administrator Mountain View, CA, USA | >> | Making life hard for others since 1977. PGP: 4BD6C0CB | >> >> > > That looks reasonable > last says: > reboot ~ th 16 sen 14:04 > reboot ~ th 16 sen 14:03 > shutdown ~ th 16 sen 13:59 > > and it's pretty good syncs with logs but there's no anybody access to > physical console 'cos it's not even plugged in. That's for the first. > Next, I've got, I believe, pretty strong passwords, and also root > can't log in directly, but wheel user also is in operators so he also > can reboot or shutdown, but there's no any attempts or successful > logins. All potentialy dangerous services run under their own > unprerileged users, and so on. Crontabs also doesn't contain scripts, > I prefer periodic system, and there's no anyway anything that cause > reboot. > Thing that worries me it that there were multiple reboots and shutdown > that goes up by itself without anyone pressing a button. And in > messages log there's fsck segment that indicates to unnormal shutdown > or reboot. It looks like it started to shutting down but was in some > case interrupted and after powering up it few times reboots itself. > But commonly FreeBSD doesn't reboot by it's own will. > The same hardware worked over a half a year under 8.0 stables without > such a problem. I just would like to understand from where this > problem comes up. > This machine doesn't contain any critical info so I'll wait for a bit. > Also I'd like to notice that recently I've tuned hdd's spindown exept > system hdd by atacontrol port, powerd and CPU frequency lowering in > idle, maybe something of this could cause this problem? And where > could I check this out? You might just want to go through your /etc/rc.d/*, crontabs, /etc/periodic/* and /etc/rc* to check for any commands that call shutdown(8) or reboot(8). Not really malicious but a rogue user that was once a staffer can plant a shutdown/reboot command in any one of the above matching files and have it run by at(1). This really sounds like the case here. 1). Check the above files. egrep -nr "(shutdown|reboot)" on those. 2). Inspect the files for at(1) reboot(8) shutdown(8) or paths to unintelligible binaries that have been setuid=0(u+s) owner=root. 3). Keep in mind a rogue staffer may have well cp(1) shutdown(8) to another command or created a script containing shutdown(8) to another command that matches another system command or has replaced one. Thats just a few things to go on for now. Others may have more to add to it. Regards & Good luck, - -- jhell,v -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJMm56rAAoJEJBXh4mJ2FR+P8wH/RyMxZSsQGKODwtWNNipeUSZ iMA+n7ub3GStz1k7hfQQfsWqdWtfrO73Nrw6Af5vnGWdLGjatwD36qOmcLqfg1tE ZBc7QGFYyFkqHxL2Dor58Q6XV2GxS1zEGyT5Rf2mNGqMOyaTVdBpIlfX02mUdpX3 0KDRdNivEXK/A8sGSK0WN46E7+uSO7L7n4zfv3fEFmsZh9VhtRwf558MJxO39UgN FsLKQRy0DVPMAnb9zr6dWvRtAVpnCgQhlLdspETN7SFamO4CAs/8ZiasPaNzG/jl G3avQZhhT1Ws/DpDBdYwj5nOpkTU2Y90PUoLXktGjg90tNvOaWfboAhA80tzyWA= =hDLt -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 23 18:42:29 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E68A4106566B for ; Thu, 23 Sep 2010 18:42:29 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id ADD408FC16 for ; Thu, 23 Sep 2010 18:42:29 +0000 (UTC) Received: by pxi17 with SMTP id 17so727545pxi.13 for ; Thu, 23 Sep 2010 11:42:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=UhUy11T5gict2tvyNduP9knM08YDHSbB1iBdg+UEKSw=; b=P3dR1q+UaE/6qZhbQ5icE5PjhWkHn/SEFG3FjcqXUtkc8XzOM4FpGpQ6J00A3ADfyv MpCFv8gXDRGBzLc4mQtxSiRYbD04cwdrAkl9qY9wFT8Z+iWJHxKUJJ5KcTk9loS5G/WZ JFPoUSouF04ts8sUdfQiQnBC1DJNLhu4nxRlU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=pWtmzoeYf4vi15+9Q4Kd6o5ClbVQL9ERvSTKZllP8izDlk9D0bRvJf08fsOT7jeXb1 AfVTlMevKhALfkez/FG8ZsgagtFm02dK9PCqnOJysaXbU5+OJY4MYhjoCTYLQs+Ry3VM BcYY3vfRwnCnaX4iIq7MPXUybd/C8TrSyW6Es= Received: by 10.142.216.2 with SMTP id o2mr1796503wfg.142.1285267349236; Thu, 23 Sep 2010 11:42:29 -0700 (PDT) Received: from centel.dataix.local (adsl-99-19-43-205.dsl.klmzmi.sbcglobal.net [99.19.43.205]) by mx.google.com with ESMTPS id n9sm349585vch.43.2010.09.23.11.42.27 (version=SSLv3 cipher=RC4-MD5); Thu, 23 Sep 2010 11:42:28 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C9B9F92.5030102@DataIX.net> Date: Thu, 23 Sep 2010 14:42:26 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.9) Gecko/20100917 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Michael BlackHeart References: <20100916164930.GA31869@icarus.home.lan> <4C9B9EAB.4050704@DataIX.net> In-Reply-To: <4C9B9EAB.4050704@DataIX.net> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Jeremy Chadwick Subject: Re: FreeBSD 8.1 Stable Unreasanoble Rebooting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 18:42:30 -0000 On 09/23/2010 14:38, jhell wrote: > On 09/16/2010 15:33, Michael BlackHeart wrote: >> 2010/9/16 Jeremy Chadwick : >>> On Thu, Sep 16, 2010 at 08:37:29PM +0400, Michael BlackHeart wrote: >>>> Today I've got a pretty strange event. It looks like a reboot but >>>> unreasonable as far as I see. Before server's uptime was over month, >>>> it's sometimes have to reboot for kernel updates or somethings like >>>> that. I've digen all logs and didn't find a reason, so here they all. >>>> >>>> auth.log >>>> Sep 16 13:59:58 diablo sshd[2284]: Received signal 15; terminating. >>>> Sep 16 14:04:26 diablo sshd[2290]: Server listening on 0.0.0.0 port 22442. >>>> >>>> cron - nothing >>>> debug.log - nothing >>>> dmesg - nothing >>>> >>>> messages >>>> Sep 16 13:44:55 diablo transmission-daemon[7965]: Couldn't create >>>> socket: Protocol not supported (fdlimit.c:651) >>>> Sep 16 13:45:31 diablo last message repeated 5 times >>>> Sep 16 13:47:23 diablo last message repeated 13 times >>>> Sep 16 13:57:40 diablo last message repeated 51 times >>>> Sep 16 13:59:48 diablo last message repeated 12 times >>>> Sep 16 14:00:18 diablo named[1575]: stopping command channel on 127.0.0.1#953 >>>> Sep 16 14:00:18 diablo named[1575]: exiting >>>> Sep 16 14:00:18 diablo syslogd: exiting on signal 15 >>>> Sep 16 14:02:31 diablo syslogd: kernel boot file is /boot/kernel/kernel >>>> Sep 16 14:02:31 diablo kernel: Copyright (c) 1992-2010 The FreeBSD Project. >>>> {...} >>> >>> This sure looks like a legitimate reboot to me (e.g. shutdown -r now); >>> note how your system daemons (named, syslogd) are being shut down with >>> SIGTERM. You can check with "last" (shutdown/reboot vs. crash). >>> >>> >>> I would highly recommend taking this machine offline and reinstalling >>> the OS, in addition to newfs'ing all existing filesystems (restore from >>> last known good backup). buildworld/installworld and >>> buildkernel/installkernel may not be enough depending on what the >>> individual did. It's likely the machine could be compromised in some >>> way, especially if there's any service on it which is public-facing, >>> regardless of authentication mechanisms you've deployed in front of it. >>> >>> >>> -- >>> | Jeremy Chadwick jdc@parodius.com | >>> | Parodius Networking http://www.parodius.com/ | >>> | UNIX Systems Administrator Mountain View, CA, USA | >>> | Making life hard for others since 1977. PGP: 4BD6C0CB | >>> >>> > >> That looks reasonable >> last says: >> reboot ~ th 16 sen 14:04 >> reboot ~ th 16 sen 14:03 >> shutdown ~ th 16 sen 13:59 > >> and it's pretty good syncs with logs but there's no anybody access to >> physical console 'cos it's not even plugged in. That's for the first. >> Next, I've got, I believe, pretty strong passwords, and also root >> can't log in directly, but wheel user also is in operators so he also >> can reboot or shutdown, but there's no any attempts or successful >> logins. All potentialy dangerous services run under their own >> unprerileged users, and so on. Crontabs also doesn't contain scripts, >> I prefer periodic system, and there's no anyway anything that cause >> reboot. >> Thing that worries me it that there were multiple reboots and shutdown >> that goes up by itself without anyone pressing a button. And in >> messages log there's fsck segment that indicates to unnormal shutdown >> or reboot. It looks like it started to shutting down but was in some >> case interrupted and after powering up it few times reboots itself. >> But commonly FreeBSD doesn't reboot by it's own will. >> The same hardware worked over a half a year under 8.0 stables without >> such a problem. I just would like to understand from where this >> problem comes up. >> This machine doesn't contain any critical info so I'll wait for a bit. >> Also I'd like to notice that recently I've tuned hdd's spindown exept >> system hdd by atacontrol port, powerd and CPU frequency lowering in >> idle, maybe something of this could cause this problem? And where >> could I check this out? > > You might just want to go through your /etc/rc.d/*, crontabs, > /etc/periodic/* and /etc/rc* to check for any commands that call > shutdown(8) or reboot(8). > > Not really malicious but a rogue user that was once a staffer can plant > a shutdown/reboot command in any one of the above matching files and > have it run by at(1). This really sounds like the case here. > > 1). Check the above files. egrep -nr "(shutdown|reboot)" on those. > 2). Inspect the files for at(1) reboot(8) shutdown(8) or paths to > unintelligible binaries that have been setuid=0(u+s) owner=root. > 3). Keep in mind a rogue staffer may have well cp(1) shutdown(8) to > another command or created a script containing shutdown(8) to another > command that matches another system command or has replaced one. > > Thats just a few things to go on for now. Others may have more to add to it. > > > Regards & Good luck, > One more thing I would like to add to this is audit(8). This can prove to be an invaluable tool to find rogue binaries on the system and track down exactly to where one is being executed. Since your looking at a specific time-frame that this is happening it would be real easy for you to track this back. Regards again, -- jhell,v From owner-freebsd-stable@FreeBSD.ORG Fri Sep 24 00:43:16 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4A1D1065674 for ; Fri, 24 Sep 2010 00:43:16 +0000 (UTC) (envelope-from bryce@bryce.net) Received: from mail-qy0-f186.google.com (mail-qy0-f186.google.com [209.85.216.186]) by mx1.freebsd.org (Postfix) with ESMTP id 91CE48FC1B for ; Fri, 24 Sep 2010 00:43:16 +0000 (UTC) Received: by qyk5 with SMTP id 5so5219698qyk.13 for ; Thu, 23 Sep 2010 17:43:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.76.1 with SMTP id a1mr354526qak.19.1285288995534; Thu, 23 Sep 2010 17:43:15 -0700 (PDT) Received: by q18g2000vbm.googlegroups.com with HTTP; Thu, 23 Sep 2010 17:43:15 -0700 (PDT) Date: Thu, 23 Sep 2010 17:43:15 -0700 (PDT) In-Reply-To: X-IP: 70.140.155.124 References: User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10,gzip(gfe) Message-ID: From: Bryce To: Bryce Edwards Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2010 00:43:16 -0000 Just wanted to follow up and show what things looks like in the 'building everything' part of build world. It has been running almost 23 hours... bryce@tahiti[~]>vmstat 1 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 in sy cs us sy id 11 0 0 1201M 2770M 282 0 0 0 318 0 0 0 10 238 475 14 1 85 12 2 0 1185M 2773M 1269 0 0 0 1944 0 0 0 2 279 643 97 3 0 12 0 0 1154M 2811M 1756 0 0 0 11603 0 0 0 6 893 701 95 3 2 12 0 0 1157M 2808M 845 0 0 0 63 0 0 0 2 475 575 96 2 2 11 0 0 1157M 2804M 1917 0 0 0 1077 0 0 0 8 970 737 97 3 0 11 0 0 1158M 2801M 1597 0 0 0 930 0 0 0 10 1213 664 96 4 0 11 0 0 1172M 2796M 1782 0 0 0 467 0 0 0 8 1009 692 97 3 0 11 0 0 1178M 2792M 1128 0 0 0 1 0 0 0 2 205 546 99 1 0 ^C bryce@tahiti[~]>iostat 1 tty da0 da1 da2 cpu tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id 0 221 39.75 0 0.00 39.92 0 0.00 36.16 0 0.00 13 1 1 0 85 0 545 0.00 0 0.00 0.00 0 0.00 0.00 0 0.00 97 0 3 0 0 0 295 0.00 0 0.00 0.00 0 0.00 0.00 0 0.00 98 0 2 0 0 0 537 0.00 0 0.00 0.00 0 0.00 0.00 0 0.00 98 0 1 0 0 0 78 0.00 0 0.00 0.00 0 0.00 0.00 0 0.00 99 0 1 0 0 0 78 0.00 0 0.00 0.00 0 0.00 0.00 0 0.00 96 0 4 0 0 0 307 0.00 0 0.00 0.00 0 0.00 0.00 0 0.00 97 0 2 0 1 0 78 0.00 0 0.00 0.00 0 0.00 0.00 0 0.00 98 0 2 0 0 ^C bryce@tahiti[~]>sysctl dev.cpu | grep temperature dev.cpu.0.temperature: 59.0C dev.cpu.1.temperature: 59.0C dev.cpu.2.temperature: 56.0C dev.cpu.3.temperature: 56.0C dev.cpu.4.temperature: 59.0C dev.cpu.5.temperature: 59.0C dev.cpu.6.temperature: 56.0C dev.cpu.7.temperature: 56.0C From owner-freebsd-stable@FreeBSD.ORG Fri Sep 24 01:20:39 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C29A0106564A for ; Fri, 24 Sep 2010 01:20:39 +0000 (UTC) (envelope-from marka@isc.org) Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by mx1.freebsd.org (Postfix) with ESMTP id 5910C8FC0A for ; Fri, 24 Sep 2010 01:20:39 +0000 (UTC) Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "farside.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id DD4385F983B; Fri, 24 Sep 2010 01:20:23 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (unknown [IPv6:2001:4f8:3:65:6233:4bff:fe01:7585]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by farside.isc.org (Postfix) with ESMTP id E03AEE6030; Fri, 24 Sep 2010 01:20:21 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 15F1C500BB0; Fri, 24 Sep 2010 11:20:21 +1000 (EST) To: Matthew Seaman From: Mark Andrews References: <4C98F433.6070506@FreeBSD.org> <20100921191517.AF60A1CC3D@ptavv.es.net> <20100921193101.GA95238@night.db.net> <9FF55FD3-4168-471B-A7C1-2D23880F3091@mac.com><4C9A6EB5.1060607@infracaninophile.co.uk> In-reply-to: Your message of "Wed, 22 Sep 2010 22:01:41 +0100." <4C9A6EB5.1060607@infracaninophile.co.uk> Date: Fri, 24 Sep 2010 11:20:21 +1000 Message-Id: <20100924012021.15F1C500BB0@drugs.dv.isc.org> X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00, T_RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mx.ams1.isc.org Cc: Diane Bruce , "freebsd-stable@freebsd.org List" Subject: Re: BIND9 built w/--disable-ipv6 on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2010 01:20:39 -0000 There is way too much misinformation here. named probes the kernel to work out if it supports IPv6 or not. named -4 turns off IPv6 so there is no need to disable it at compile time. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org From owner-freebsd-stable@FreeBSD.ORG Fri Sep 24 03:58:29 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 236A81065672 for ; Fri, 24 Sep 2010 03:58:29 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 648B68FC12 for ; Fri, 24 Sep 2010 03:58:27 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id o8O3wAUn062911; Fri, 24 Sep 2010 13:58:11 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Fri, 24 Sep 2010 13:58:10 +1000 (EST) From: Ian Smith To: jhell In-Reply-To: <4C9B9EAB.4050704@DataIX.net> Message-ID: <20100924130332.U11124@sola.nimnet.asn.au> References: <20100916164930.GA31869@icarus.home.lan> <4C9B9EAB.4050704@DataIX.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org, Jeremy Chadwick , Michael BlackHeart Subject: Re: FreeBSD 8.1 Stable Unreasanoble Rebooting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2010 03:58:29 -0000 On Thu, 23 Sep 2010, jhell wrote: > On 09/16/2010 15:33, Michael BlackHeart wrote: > > 2010/9/16 Jeremy Chadwick : > >> On Thu, Sep 16, 2010 at 08:37:29PM +0400, Michael BlackHeart wrote: > >>> Today I've got a pretty strange event. It looks like a reboot but > >>> unreasonable as far as I see. Before server's uptime was over month, > >>> it's sometimes have to reboot for kernel updates or somethings like > >>> that. I've digen all logs and didn't find a reason, so here they all. > >>> > >>> auth.log > >>> Sep 16 13:59:58 diablo sshd[2284]: Received signal 15; terminating. > >>> Sep 16 14:04:26 diablo sshd[2290]: Server listening on 0.0.0.0 port 22442. > >>> > >>> cron - nothing > >>> debug.log - nothing > >>> dmesg - nothing > >>> > >>> messages > >>> Sep 16 13:44:55 diablo transmission-daemon[7965]: Couldn't create > >>> socket: Protocol not supported (fdlimit.c:651) > >>> Sep 16 13:45:31 diablo last message repeated 5 times > >>> Sep 16 13:47:23 diablo last message repeated 13 times > >>> Sep 16 13:57:40 diablo last message repeated 51 times > >>> Sep 16 13:59:48 diablo last message repeated 12 times Michael, were these above messages to be expected? > >>> Sep 16 14:00:18 diablo named[1575]: stopping command channel on 127.0.0.1#953 > >>> Sep 16 14:00:18 diablo named[1575]: exiting > >>> Sep 16 14:00:18 diablo syslogd: exiting on signal 15 > >>> Sep 16 14:02:31 diablo syslogd: kernel boot file is /boot/kernel/kernel > >>> Sep 16 14:02:31 diablo kernel: Copyright (c) 1992-2010 The FreeBSD Project. > >>> {...} > >> > >> This sure looks like a legitimate reboot to me (e.g. shutdown -r now); > >> note how your system daemons (named, syslogd) are being shut down with > >> SIGTERM. You can check with "last" (shutdown/reboot vs. crash). > >> > >> > >> I would highly recommend taking this machine offline and reinstalling > >> the OS, in addition to newfs'ing all existing filesystems (restore from > >> last known good backup). buildworld/installworld and > >> buildkernel/installkernel may not be enough depending on what the > >> individual did. It's likely the machine could be compromised in some > >> way, especially if there's any service on it which is public-facing, > >> regardless of authentication mechanisms you've deployed in front of it. > >> [..] > > That looks reasonable > > last says: > > reboot ~ th 16 sen 14:04 > > reboot ~ th 16 sen 14:03 > > shutdown ~ th 16 sen 13:59 > > > > and it's pretty good syncs with logs but there's no anybody access to > > physical console 'cos it's not even plugged in. That's for the first. > > Next, I've got, I believe, pretty strong passwords, and also root > > can't log in directly, but wheel user also is in operators so he also > > can reboot or shutdown, but there's no any attempts or successful > > logins. All potentialy dangerous services run under their own > > unprerileged users, and so on. Crontabs also doesn't contain scripts, > > I prefer periodic system, and there's no anyway anything that cause > > reboot. > > Thing that worries me it that there were multiple reboots and shutdown > > that goes up by itself without anyone pressing a button. And in > > messages log there's fsck segment that indicates to unnormal shutdown > > or reboot. It looks like it started to shutting down but was in some > > case interrupted and after powering up it few times reboots itself. > > But commonly FreeBSD doesn't reboot by it's own will. > > The same hardware worked over a half a year under 8.0 stables without > > such a problem. I just would like to understand from where this > > problem comes up. > > This machine doesn't contain any critical info so I'll wait for a bit. > > Also I'd like to notice that recently I've tuned hdd's spindown exept > > system hdd by atacontrol port, powerd and CPU frequency lowering in > > idle, maybe something of this could cause this problem? And where > > could I check this out? > > You might just want to go through your /etc/rc.d/*, crontabs, > /etc/periodic/* and /etc/rc* to check for any commands that call > shutdown(8) or reboot(8). > > Not really malicious but a rogue user that was once a staffer can plant > a shutdown/reboot command in any one of the above matching files and > have it run by at(1). This really sounds like the case here. > > 1). Check the above files. egrep -nr "(shutdown|reboot)" on those. > 2). Inspect the files for at(1) reboot(8) shutdown(8) or paths to > unintelligible binaries that have been setuid=0(u+s) owner=root. > 3). Keep in mind a rogue staffer may have well cp(1) shutdown(8) to > another command or created a script containing shutdown(8) to another > command that matches another system command or has replaced one. > > Thats just a few things to go on for now. Others may have more to add to it. Might help to turn on process accounting to log who ran what, when? Add accounting_enable="YES" to rc.conf, (touch /var/account/acct; accton) to begin accounting before/without rebooting. Then something like 'lastcomm -eE [-f /var/account/acct.N] | less' to perouse the|[some] day's doings. To adjust how many days to keep etc: grep account /etc/defaults/periodic.conf cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Fri Sep 24 07:12:12 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA6FB106564A for ; Fri, 24 Sep 2010 07:12:12 +0000 (UTC) (envelope-from john@theusgroup.com) Received: from theusgroup.com (theusgroup.com [64.122.243.222]) by mx1.freebsd.org (Postfix) with ESMTP id A4B878FC14 for ; Fri, 24 Sep 2010 07:12:11 +0000 (UTC) Received: from server.theusgroup.com (localhost.theusgroup.com [127.0.0.1]) by theusgroup.com (Postfix) with ESMTP id BAF5E5F4C for ; Thu, 23 Sep 2010 23:56:31 -0700 (PDT) To: FreeBSD Stable In-reply-to: <4C9B0F2C.20601@FreeBSD.org> References: <4C9B0F2C.20601@FreeBSD.org> Comments: In-reply-to Alexander Motin message dated "Thu, 23 Sep 2010 11:26:20 +0300." Date: Thu, 23 Sep 2010 23:56:31 -0700 From: John Theus Message-Id: <20100924065636.BAF5E5F4C@theusgroup.com> Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2010 07:12:12 -0000 Alexander Motin wrote: >Just to compare, my Core i7-870 with boxed cooler reports: > 31C being idle with tuned power management, > 53C being idle without any power management, > 85C during `make -j16`. >That system did `make -j16 universe` in about 3 hours AFAIR. Another data point and a comment about temperatures. i5-650/H55, half the cores and about 60% the cost compared to the above. 8.1-STABLE amd64 make -j16 universe in 4 hours 5 minutes. all cores running at 100% according to top -P 30C idle 42C max during make I'm a EE and I used to make my living designing microprocessor-based computers. Our design standard for maximum chip temperature was 45C. Above that and the MTBF starts falling fast. Today's motherboards have a lot fewer components, so 45C is too low if you have a single motherboard, but not if you have 100. For the i7-870 above, the intel datasheet says at a maximum power of 95w, the maximum permitted temperature is 72.7C. For the i5-650 at 73w, the maximum permitted temperature is 66C. John Theus TheUsGroup.com From owner-freebsd-stable@FreeBSD.ORG Fri Sep 24 08:23:00 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98A641065670 for ; Fri, 24 Sep 2010 08:23:00 +0000 (UTC) (envelope-from prvs=1883808c8e=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 3536E8FC14 for ; Fri, 24 Sep 2010 08:23:00 +0000 (UTC) X-MDAV-Processed: mail1.multiplay.co.uk, Fri, 24 Sep 2010 09:12:00 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Fri, 24 Sep 2010 09:12:00 +0100 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-5.0 required=6.0 tests=USER_IN_WHITELIST shortcircuit=ham autolearn=disabled version=3.2.5 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v10.0.4) with ESMTP id md50011293362.msg for ; Fri, 24 Sep 2010 09:12:00 +0100 X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=1883808c8e=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-stable@freebsd.org Message-ID: From: "Steven Hartland" To: "Bryce" References: Date: Fri, 24 Sep 2010 09:12:01 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.5994 Cc: freebsd-stable@freebsd.org Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2010 08:23:00 -0000 I know it might seem a bit like overkill but have you put windows or Linux on this box and tried some basic tests? Might be a way to eliminate so sort of hardware failure and not something that's FreeBSD specific? Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Fri Sep 24 08:51:47 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 419E7106566C for ; Fri, 24 Sep 2010 08:51:47 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 214718FC18 for ; Fri, 24 Sep 2010 08:51:47 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id o8O8pksP061705 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 24 Sep 2010 01:51:46 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id o8O8pkK3061704; Fri, 24 Sep 2010 01:51:46 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA09394; Fri, 24 Sep 10 01:40:25 PDT Date: Fri, 24 Sep 2010 01:40:25 -0700 From: perryh@pluto.rain.com To: ozkan.kirik@gmail.com Message-Id: <4c9c63f9.lhj3A4EvK30Z5YGw%perryh@pluto.rain.com> References: In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: kernel: arpresolve: can't allocate llinfo for 10.6.10.240 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2010 08:51:47 -0000 ?zkan KIRIK wrote: > When I watch log messages I see "kernel: arpresolve: can't allocate > llinfo for 10.0.16.251" messages ... "can't allocate llinfo" has been in the network code for a _very_ long time. One cause is, or at least used to be, the machine having no netmask defined for its own IP address. From owner-freebsd-stable@FreeBSD.ORG Fri Sep 24 11:52:50 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2F9E106566C for ; Fri, 24 Sep 2010 11:52:49 +0000 (UTC) (envelope-from leroy.vanlogchem@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 98A7B8FC19 for ; Fri, 24 Sep 2010 11:52:49 +0000 (UTC) Received: by qyk7 with SMTP id 7so851085qyk.13 for ; Fri, 24 Sep 2010 04:52:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=YOHAij+U/cMWCD/7RitVhC3K164K1U1se2WqXDX4NDA=; b=dR7AG4qQ+Qt09FcIztCM4m6CmjtoakxF6ipupOjbqY2iSu8zkNZh8kGTUaB79dW/fB IziuFXDttJXlOwLpBh6PI9PZ7sxX6FHZNv43kAE7qq2y+r0JQslgXRNQWtBbHR8Xy7Sx FY1j8m9jNoddy0txt91x/p5GRGqJRLxWB05HU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=S8frbi2j77qtf3S8+X0BoEfIufYUquNV8i07vrmWZ1ogQ3+t6POqYQnJYmUpI/Dsia pv5ezvEe61/6d96BhCum6uTfI1LpMwia+QP2uaUcpXFTuckJP8bh/ZpAfSZC+wZcvTzf 49N6+elhrMy81QpWNmNuHuiLWqAfp8DFztI2g= MIME-Version: 1.0 Received: by 10.224.60.136 with SMTP id p8mr2289317qah.386.1285327486138; Fri, 24 Sep 2010 04:24:46 -0700 (PDT) Received: by 10.229.2.25 with HTTP; Fri, 24 Sep 2010 04:24:46 -0700 (PDT) Date: Fri, 24 Sep 2010 13:24:46 +0200 Message-ID: From: Leroy van Logchem To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: 8.1-RELEASE: [zfs] [kmem] zfs destroy snapshot results in panic: kmem_map too small X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2010 11:52:50 -0000 ----------------------------------------------------------------------------- Problem : Kernel panic "kmem_malloc(114688): kmem_map too small Trigger : Destroy ZFS snapshots (each bigger >80GB) Version : FreeBSD 8.1-RELEASE (GENERIC AMD64 but with DDB) Workaround : kmem / zfs arc tuning in /boot/loader.conf System Info : Manufacturer: Supermicro Mainboard : X8DTN Cpu(s) Two : Intel(R) Xeon(R) E5520 @ 2.27GHz Memory : 10240 MB (speed: 1066 MHz) Storage : mpt0 Adapter: Board Name: SAS3081E Board Assembly: L3-00159-02D Chip Name: C1068E 24 drives are connected to mpt0: /dev/da[0 up to 23] Each drive : 512 # sectorsize 2000398934016 # mediasize in bytes (1.8T) 3907029168 # mediasize in sectors 243201 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. JK1130YAHUSJMT # Disk ident. # zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT tank 43.5T 31.0T 12.5T 71% ONLINE - ----------------------------------------------------------------------------- This server has been running since dec 2009 without downtime. We keep 14 daily zfs snapshots. The problem of our nightly kernel panic started when the size of each snapshot exceeded about 80 GB. A cronjob first creates new snapshots just fine and destroys expired (older >14 days) snapshots. During the command "zfs destroy " the memory free seen in top(1) drops very quickly and soon after that this panic is generated: panic: kmem_malloc(114688): kmem_map too small: 3307884544 total allocated cpuid = 2 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a panic() at panic+0x182 kmem_malloc() at kmem_malloc+0x5b5 uma_large_malloc() at uma_large_malloc+0x4a malloc() at malloc+0x14b zio_compress_data() at zio_compress_data+0xa2 zio_write_bp_init() at zio_write_bp_init+0xc2 zio_exectute() at zio_execute+0x77 taskq_run_safe() at taskq_run_safe+0x13 taskqueue_run() at taskqueue_run+0x91 taskqueue_thread_loop() at taskqueue_thread_loop+0x3f fork_exit() at fork_exit+0x12a fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff81261edd30, rbp = 0 --- panic: kmem_malloc(118784): kmem_map too small: 3307884544 total allocated cpuid = 2 During these panics no tuning or /boot/loader.conf values where present. Only after hitting this behaviour yesterday i created boot/loader.conf: vm.kmem_size=18G vfs.zfs.arc_max=6G After which the snapshots could be destroyed without panic. Questions: Are users required to tune? If so, are there reliable guidelines regarding memory and ZFS? Are the -quickly- chosen values any good? (service window was closing) --- Leroy From owner-freebsd-stable@FreeBSD.ORG Fri Sep 24 12:33:33 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B28CE106564A for ; Fri, 24 Sep 2010 12:33:33 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [76.96.30.32]) by mx1.freebsd.org (Postfix) with ESMTP id 972948FC13 for ; Fri, 24 Sep 2010 12:33:33 +0000 (UTC) Received: from omta12.emeryville.ca.mail.comcast.net ([76.96.30.44]) by qmta03.emeryville.ca.mail.comcast.net with comcast id Abov1f0010x6nqcA3cZZcq; Fri, 24 Sep 2010 12:33:33 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta12.emeryville.ca.mail.comcast.net with comcast id AcZY1f0023LrwQ28YcZY0k; Fri, 24 Sep 2010 12:33:32 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id F357F9B425; Fri, 24 Sep 2010 05:33:31 -0700 (PDT) Date: Fri, 24 Sep 2010 05:33:31 -0700 From: Jeremy Chadwick To: Leroy van Logchem Message-ID: <20100924123331.GA62762@icarus.home.lan> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable@freebsd.org Subject: Re: 8.1-RELEASE: [zfs] [kmem] zfs destroy snapshot results in panic: kmem_map too small X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2010 12:33:33 -0000 On Fri, Sep 24, 2010 at 01:24:46PM +0200, Leroy van Logchem wrote: > ----------------------------------------------------------------------------- > Problem : Kernel panic "kmem_malloc(114688): kmem_map too small > Trigger : Destroy ZFS snapshots (each bigger >80GB) > Version : FreeBSD 8.1-RELEASE (GENERIC AMD64 but with DDB) > ... > panic: kmem_malloc(114688): kmem_map too small: 3307884544 total allocated > cpuid = 2 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > panic() at panic+0x182 > kmem_malloc() at kmem_malloc+0x5b5 > uma_large_malloc() at uma_large_malloc+0x4a > malloc() at malloc+0x14b > zio_compress_data() at zio_compress_data+0xa2 > zio_write_bp_init() at zio_write_bp_init+0xc2 > zio_exectute() at zio_execute+0x77 > taskq_run_safe() at taskq_run_safe+0x13 > taskqueue_run() at taskqueue_run+0x91 > taskqueue_thread_loop() at taskqueue_thread_loop+0x3f > fork_exit() at fork_exit+0x12a > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffff81261edd30, rbp = 0 --- > panic: kmem_malloc(118784): kmem_map too small: 3307884544 total allocated > cpuid = 2 Can you please provide uname -a output? The built date of your kernel matters in this case. The panic looks like uma(9) is in use, which was enabled by default and then later reverted/removed, so this is why the build date matters. If "sysctl vfs.zfs.zio.use_uma" shows a value of 1, then please put this in your /boot/loader.conf to disable uma use: # Disable UMA (uma(9)) for ZFS; amd64 was moved to exclusively use UMA # on 2010/05/24. # http://lists.freebsd.org/pipermail/freebsd-stable/2010-June/057162.html vfs.zfs.zio.use_uma="0" If you upgrade to RELENG_8, you won't have to set this. As for your questions under "Questions" -- yes you have to tune, no there aren't really "reliable guidelines" and I've been asking for such since ZFS came out for FreeBSD, but your values look fine. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri Sep 24 12:46:56 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80A77106566C for ; Fri, 24 Sep 2010 12:46:56 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id C34988FC08 for ; Fri, 24 Sep 2010 12:46:55 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA16691; Fri, 24 Sep 2010 15:46:50 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4C9C9DB9.6060106@icyb.net.ua> Date: Fri, 24 Sep 2010 15:46:49 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20100920 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: Jeremy Chadwick References: <20100924123331.GA62762@icarus.home.lan> In-Reply-To: <20100924123331.GA62762@icarus.home.lan> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Leroy van Logchem Subject: Re: 8.1-RELEASE: [zfs] [kmem] zfs destroy snapshot results in panic: kmem_map too small X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2010 12:46:56 -0000 on 24/09/2010 15:33 Jeremy Chadwick said the following: > On Fri, Sep 24, 2010 at 01:24:46PM +0200, Leroy van Logchem wrote: >> ----------------------------------------------------------------------------- >> Problem : Kernel panic "kmem_malloc(114688): kmem_map too small >> Trigger : Destroy ZFS snapshots (each bigger >80GB) >> Version : FreeBSD 8.1-RELEASE (GENERIC AMD64 but with DDB) >> ... >> panic: kmem_malloc(114688): kmem_map too small: 3307884544 total allocated >> cpuid = 2 >> KDB: stack backtrace: >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2a >> panic() at panic+0x182 >> kmem_malloc() at kmem_malloc+0x5b5 >> uma_large_malloc() at uma_large_malloc+0x4a >> malloc() at malloc+0x14b >> zio_compress_data() at zio_compress_data+0xa2 >> zio_write_bp_init() at zio_write_bp_init+0xc2 >> zio_exectute() at zio_execute+0x77 >> taskq_run_safe() at taskq_run_safe+0x13 >> taskqueue_run() at taskqueue_run+0x91 >> taskqueue_thread_loop() at taskqueue_thread_loop+0x3f >> fork_exit() at fork_exit+0x12a >> fork_trampoline() at fork_trampoline+0xe >> --- trap 0, rip = 0, rsp = 0xffffff81261edd30, rbp = 0 --- >> panic: kmem_malloc(118784): kmem_map too small: 3307884544 total allocated >> cpuid = 2 > > Can you please provide uname -a output? The built date of your kernel > matters in this case. The panic looks like uma(9) is in use No, it doesn't. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Fri Sep 24 12:53:18 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40670106564A for ; Fri, 24 Sep 2010 12:53:18 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta09.emeryville.ca.mail.comcast.net (qmta09.emeryville.ca.mail.comcast.net [76.96.30.96]) by mx1.freebsd.org (Postfix) with ESMTP id 240C48FC08 for ; Fri, 24 Sep 2010 12:53:16 +0000 (UTC) Received: from omta20.emeryville.ca.mail.comcast.net ([76.96.30.87]) by qmta09.emeryville.ca.mail.comcast.net with comcast id Ac6G1f0031smiN4A9ctGy2; Fri, 24 Sep 2010 12:53:16 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta20.emeryville.ca.mail.comcast.net with comcast id ActF1f0093LrwQ28gctGMk; Fri, 24 Sep 2010 12:53:16 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 9B8159B418; Fri, 24 Sep 2010 05:53:15 -0700 (PDT) Date: Fri, 24 Sep 2010 05:53:15 -0700 From: Jeremy Chadwick To: Andriy Gapon Message-ID: <20100924125315.GA63297@icarus.home.lan> References: <20100924123331.GA62762@icarus.home.lan> <4C9C9DB9.6060106@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C9C9DB9.6060106@icyb.net.ua> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Leroy van Logchem , freebsd-stable@freebsd.org Subject: Re: 8.1-RELEASE: [zfs] [kmem] zfs destroy snapshot results in panic: kmem_map too small X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2010 12:53:18 -0000 On Fri, Sep 24, 2010 at 03:46:49PM +0300, Andriy Gapon wrote: > on 24/09/2010 15:33 Jeremy Chadwick said the following: > > On Fri, Sep 24, 2010 at 01:24:46PM +0200, Leroy van Logchem wrote: > >> ----------------------------------------------------------------------------- > >> Problem : Kernel panic "kmem_malloc(114688): kmem_map too small > >> Trigger : Destroy ZFS snapshots (each bigger >80GB) > >> Version : FreeBSD 8.1-RELEASE (GENERIC AMD64 but with DDB) > >> ... > >> panic: kmem_malloc(114688): kmem_map too small: 3307884544 total allocated > >> cpuid = 2 > >> KDB: stack backtrace: > >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > >> panic() at panic+0x182 > >> kmem_malloc() at kmem_malloc+0x5b5 > >> uma_large_malloc() at uma_large_malloc+0x4a > >> malloc() at malloc+0x14b > >> zio_compress_data() at zio_compress_data+0xa2 > >> zio_write_bp_init() at zio_write_bp_init+0xc2 > >> zio_exectute() at zio_execute+0x77 > >> taskq_run_safe() at taskq_run_safe+0x13 > >> taskqueue_run() at taskqueue_run+0x91 > >> taskqueue_thread_loop() at taskqueue_thread_loop+0x3f > >> fork_exit() at fork_exit+0x12a > >> fork_trampoline() at fork_trampoline+0xe > >> --- trap 0, rip = 0, rsp = 0xffffff81261edd30, rbp = 0 --- > >> panic: kmem_malloc(118784): kmem_map too small: 3307884544 total allocated > >> cpuid = 2 > > > > Can you please provide uname -a output? The built date of your kernel > > matters in this case. The panic looks like uma(9) is in use > > No, it doesn't. You're right, sorry, I missed the malloc(9) call. (I thought it was zio_compress_data() followed by uma_large_malloc()). Leroy, you can ignore my advice of adjusting your loader.conf with the tunable in question. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri Sep 24 13:02:00 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BEC7E106566C for ; Fri, 24 Sep 2010 13:02:00 +0000 (UTC) (envelope-from ozkan.kirik@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 7A4288FC1B for ; Fri, 24 Sep 2010 13:02:00 +0000 (UTC) Received: by qyk31 with SMTP id 31so1330501qyk.13 for ; Fri, 24 Sep 2010 06:01:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=p4USFtzyPAzbMMWnx5fVw4be/k/ob0bfahPoWokE8Y8=; b=gFoh+wsx98fOjFjR6eMG9oE+XddMxycrar/ltf5NSCtd4jZW0/zNNzt1OidayguzS5 sOxiT4PHbmvl0b4DsPa9K6UPat5qBuc3WqUTAVxD361AXDyf7h9Jbi5eOw45x2CS93c1 ooNlaUANUOMeOTNBhPoTHkGqALkgCQE3Nat8g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=BycDEPhlCwLIpDtLF2+cavKCe4P4LOrHxZED44HKQOTzv1kN6AoFD3e/M3RNIrG1i2 FWO0NRGVXVaTK3XHPcz/kTuKmkVIcY+GAQkkju0LayB05WZ71JduLoV3toIoiQa/sN6l gQ/Zb/j/LYZg82WO6Xdq/M47nvhbyPYp+I6cM= MIME-Version: 1.0 Received: by 10.224.60.213 with SMTP id q21mr1677741qah.353.1285333319409; Fri, 24 Sep 2010 06:01:59 -0700 (PDT) Received: by 10.229.192.204 with HTTP; Fri, 24 Sep 2010 06:01:59 -0700 (PDT) In-Reply-To: <4c9c63f9.lhj3A4EvK30Z5YGw%perryh@pluto.rain.com> References: <4c9c63f9.lhj3A4EvK30Z5YGw%perryh@pluto.rain.com> Date: Fri, 24 Sep 2010 16:01:59 +0300 Message-ID: From: =?ISO-8859-1?Q?=D6zkan_KIRIK?= To: perryh@pluto.rain.com Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org Subject: Re: kernel: arpresolve: can't allocate llinfo for 10.6.10.240 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2010 13:02:00 -0000 Thanks for fast reply, version of source file: src/sys/net/if.c,v 1.359.2.23 2010/07/30 21:58:35 but problem still occurs. #arp -an | grep 10.0.16.251 ? (10.0.16.251) at 00:21:5e:56:83:76 on bce0.116 expires in 1131 seconds [vlan] # ifconfig bce0.116 bce0.116: flags=8843 metric 0 mtu 1500 options=103 ether 00:1b:78:38:55:f8 inet 10.0.16.254 netmask 0xffffff00 broadcast 10.0.16.255 inet 1.1.31.254 netmask 0xffffff00 broadcast 1.1.31.255 media: Ethernet autoselect (1000baseSX ) status: active vlan: 116 parent interface: bce0 interface has own IP & mask. I dont understand why this error occurs altough this IP address exists in arp table. This message ( kernel: arpresolve: can't allocate llinfo for 10.0.16.251 ) repeats too frequently. ( nearly once per 10 seconds. ) On Fri, Sep 24, 2010 at 11:40 AM, wrote: > ?zkan KIRIK wrote: > >> When I watch log messages I see "kernel: arpresolve: can't allocate >> llinfo for 10.0.16.251" messages ... > > "can't allocate llinfo" has been in the network code for a _very_ > long time. > > One cause is, or at least used to be, the machine having no netmask > defined for its own IP address. > From owner-freebsd-stable@FreeBSD.ORG Fri Sep 24 13:04:08 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C228C106566B for ; Fri, 24 Sep 2010 13:04:08 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 189608FC1E for ; Fri, 24 Sep 2010 13:04:07 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA16971; Fri, 24 Sep 2010 16:04:03 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4C9CA1C3.5070608@icyb.net.ua> Date: Fri, 24 Sep 2010 16:04:03 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20100920 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: Jeremy Chadwick , Leroy van Logchem References: <20100924123331.GA62762@icarus.home.lan> In-Reply-To: <20100924123331.GA62762@icarus.home.lan> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: 8.1-RELEASE: [zfs] [kmem] zfs destroy snapshot results in panic: kmem_map too small X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2010 13:04:08 -0000 on 24/09/2010 15:33 Jeremy Chadwick said the following: > As for your questions under "Questions" -- yes you have to tune, no > there aren't really "reliable guidelines" and I've been asking for such > since ZFS came out for FreeBSD, but your values look fine. I can't provide you "reliable" or "authoritative" guidelines, but I have an advice which seems to work. On amd64 set your vm.kmem_size to at least the amount of available memory that you got, or even more (1.5x, 2x). An easy way to do that (1x) is to set vm.kmem_size_scale="1". In head this is already done automatically, MFC to stable/8 is expected. As to arc_max/arc_min, set them based your needs according to general ZFS recommendations. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Fri Sep 24 13:37:16 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5F86106566B for ; Fri, 24 Sep 2010 13:37:16 +0000 (UTC) (envelope-from leroy.vanlogchem@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 6BD7F8FC12 for ; Fri, 24 Sep 2010 13:37:15 +0000 (UTC) Received: by qyk31 with SMTP id 31so1374546qyk.13 for ; Fri, 24 Sep 2010 06:37:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=mJexI2JDQoGlOQyPbuh1OCU4w4K6WeP2LU3omB5mXH8=; b=GTm8eWsaPtX6pxTxVovgnjs71uiFITV5mdcDQWWscwdWfJjn4R2BeRiv2TP4gXSfZ9 66RnkC55ibJL052Ca6jECcFceCIgJMa0za7HluIrHqRAHRdKcVYIa+6pSoBg4t0Ty3Mw Q94xHJI/2sp19FJQqZf2x2FsD585eKqRjy0g0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=J6yqom3JyQHsS/87Vh2iq/hdS0/CCgpH6LqtfIH4IIOi4xpn+hCJsl63oqGx8I4roW QekXiaiT8UXmxmgVgPP191hZbQ6W4m5aJi1ZbB99IB2VZshTx4bferm1+fbmtBfllWvx bux28XaWN0Rc4h+8BglBcHkYJCYbBrao72m3s= MIME-Version: 1.0 Received: by 10.224.49.148 with SMTP id v20mr2428574qaf.352.1285335435542; Fri, 24 Sep 2010 06:37:15 -0700 (PDT) Received: by 10.229.2.25 with HTTP; Fri, 24 Sep 2010 06:37:14 -0700 (PDT) In-Reply-To: <4C9CA1C3.5070608@icyb.net.ua> References: <20100924123331.GA62762@icarus.home.lan> <4C9CA1C3.5070608@icyb.net.ua> Date: Fri, 24 Sep 2010 15:37:14 +0200 Message-ID: From: Leroy van Logchem To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org, Jeremy Chadwick Subject: Re: 8.1-RELEASE: [zfs] [kmem] zfs destroy snapshot results in panic: kmem_map too small X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2010 13:37:16 -0000 On Fri, Sep 24, 2010 at 3:04 PM, Andriy Gapon wrote: > On amd64 set your vm.kmem_size to at least the amount of available memory that you > got, or even more (1.5x, 2x). > An easy way to do that (1x) is to set vm.kmem_size_scale="1". > In head this is already done automatically, MFC to stable/8 is expected. Thank you all for the swift answers and advice. The upcoming auto scaling sounds promising. Just to be sure, does the kmem_size_scale apply when using 8.1-R? --- Leroy From owner-freebsd-stable@FreeBSD.ORG Fri Sep 24 13:41:26 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 408911065672 for ; Fri, 24 Sep 2010 13:41:26 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 8108C8FC27 for ; Fri, 24 Sep 2010 13:41:25 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA17643; Fri, 24 Sep 2010 16:41:21 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4C9CAA80.3060607@icyb.net.ua> Date: Fri, 24 Sep 2010 16:41:20 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20100920 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: Leroy van Logchem References: <20100924123331.GA62762@icarus.home.lan> <4C9CA1C3.5070608@icyb.net.ua> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Jeremy Chadwick Subject: Re: 8.1-RELEASE: [zfs] [kmem] zfs destroy snapshot results in panic: kmem_map too small X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2010 13:41:26 -0000 on 24/09/2010 16:37 Leroy van Logchem said the following: > On Fri, Sep 24, 2010 at 3:04 PM, Andriy Gapon wrote: >> On amd64 set your vm.kmem_size to at least the amount of available memory that you >> got, or even more (1.5x, 2x). >> An easy way to do that (1x) is to set vm.kmem_size_scale="1". >> In head this is already done automatically, MFC to stable/8 is expected. > > Thank you all for the swift answers and advice. The upcoming auto scaling sounds > promising. Just to be sure, does the kmem_size_scale apply when using 8.1-R? Yes. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Fri Sep 24 18:16:56 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8BC771065696 for ; Fri, 24 Sep 2010 18:16:56 +0000 (UTC) (envelope-from bryce@bryce.net) Received: from mail-qy0-f186.google.com (mail-qy0-f186.google.com [209.85.216.186]) by mx1.freebsd.org (Postfix) with ESMTP id 4D9818FC20 for ; Fri, 24 Sep 2010 18:16:55 +0000 (UTC) Received: by qyk5 with SMTP id 5so7698003qyk.13 for ; Fri, 24 Sep 2010 11:16:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.70.79 with SMTP id c15mr60742vcj.10.1285352215588; Fri, 24 Sep 2010 11:16:55 -0700 (PDT) Received: by t11g2000vbc.googlegroups.com with HTTP; Fri, 24 Sep 2010 11:16:55 -0700 (PDT) Date: Fri, 24 Sep 2010 11:16:55 -0700 (PDT) In-Reply-To: X-IP: 75.125.126.8 References: User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10,gzip(gfe) Message-ID: From: Bryce To: Bryce Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2010 18:16:56 -0000 Yay! I have solved the problem.... I got a new BIOS from SuperMicro support, and it has resolved the performance issues I was seeing. I also no longer have to disable Legacy USB. Here's the new & improved times for buildworld && buildkernel (with - j12). 19 minutes for world and kernel (with all modules) is not bad at all! >>> World build started on Fri Sep 24 03:26:06 CDT 2010 >>> World build completed on Fri Sep 24 03:38:44 CDT 2010 >>> Kernel build for GENERIC started on Fri Sep 24 03:38:44 CDT 2010 >>> Kernel build for GENERIC completed on Fri Sep 24 03:44:47 CDT 2010 Thanks everyone for all the help & ideas... From owner-freebsd-stable@FreeBSD.ORG Fri Sep 24 18:31:20 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C4D61065670 for ; Fri, 24 Sep 2010 18:31:20 +0000 (UTC) (envelope-from prvs=1883808c8e=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id E7FB58FC1D for ; Fri, 24 Sep 2010 18:31:19 +0000 (UTC) X-MDAV-Processed: mail1.multiplay.co.uk, Fri, 24 Sep 2010 19:31:03 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Fri, 24 Sep 2010 19:31:03 +0100 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-5.0 required=6.0 tests=USER_IN_WHITELIST shortcircuit=ham autolearn=disabled version=3.2.5 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v10.0.4) with ESMTP id md50011295440.msg for ; Fri, 24 Sep 2010 19:31:01 +0100 X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=1883808c8e=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-stable@freebsd.org Message-ID: From: "Steven Hartland" To: "Bryce" References: Date: Fri, 24 Sep 2010 19:31:02 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.5994 Cc: freebsd-stable@freebsd.org Subject: Re: SuperMicro i7 (UP) - very slow performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2010 18:31:20 -0000 ---- Original Message ----- From: "Bryce" > Yay! I have solved the problem.... > > I got a new BIOS from SuperMicro support, and it has resolved the > performance issues I was seeing. I also no longer have to disable > Legacy USB. > > Here's the new & improved times for buildworld && buildkernel (with - > j12). 19 minutes for world and kernel (with all modules) is not bad at all! That's one hell of a bios bug! Unable to disable USB on SuperMicro systems with IPMI support is standard as you do and you loose all remote access if you do as it runs via USB. Found that one out the hard way ;-) Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Fri Sep 24 22:36:11 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE8B3106566B for ; Fri, 24 Sep 2010 22:36:11 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 16C748FC0C for ; Fri, 24 Sep 2010 22:36:08 +0000 (UTC) Received: by wyb33 with SMTP id 33so4162453wyb.13 for ; Fri, 24 Sep 2010 15:36:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=k6tG5KZKdYFf7jyB4jcMRgOHn3axk0Gpnft9t+A1DNc=; b=DH862wBMUFkUmo9+jk5d8jI99y4YePO29RGkX3ahSWVc+YY1hfAHDmItUXwMlIjAli CP727gIkqnWGFfTM/OZr6UfU6GnA+WOA9gp+JLy56RB7L+Nn6+LXjbRaBLzleC4+TlYR N0hvno5ODWknbzEYwtAQSjEVX6n+wp0WjjWoY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=taUEgJT3KTTihqZBHid7qmedNrWJk4ERuNbXUnHWo5K/o8LNWTbkCCdTtcFOsya+cf H+kZcfG/k7BX3NmmXf463AyLAt33/IPa7uOVmE0kTQGZi493RWFj5+SXMWLtJemvAoWL 65NyDtaMQDsfwtMBEqVKMv80yZ0BmZJQbmi6w= MIME-Version: 1.0 Received: by 10.216.10.5 with SMTP id 5mr3277356weu.81.1285367767446; Fri, 24 Sep 2010 15:36:07 -0700 (PDT) Received: by 10.216.48.20 with HTTP; Fri, 24 Sep 2010 15:36:07 -0700 (PDT) In-Reply-To: <201009141759.o8EHxcZ0013539@lava.sentex.ca> References: <201006102031.o5AKVCH2016467@lava.sentex.ca> <201007021739.o62HdMOU092319@lava.sentex.ca> <20100702193654.GD10862@michelle.cdnetworks.com> <201008162107.o7GL76pA080191@lava.sentex.ca> <20100817185208.GA6482@michelle.cdnetworks.com> <201008171955.o7HJt67T087902@lava.sentex.ca> <20100817200020.GE6482@michelle.cdnetworks.com> <201009141759.o8EHxcZ0013539@lava.sentex.ca> Date: Fri, 24 Sep 2010 15:36:07 -0700 Message-ID: From: Jack Vogel To: Mike Tancsa Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: pyunyh@gmail.com, freebsd-stable@freebsd.org Subject: Re: RELENG_7 em problems (and RELENG_8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2010 22:36:11 -0000 There is a new revision of the em driver coming next week, its going thru some stress pounding over the weekend, if no issues show up I'll put it into HEAD. Yongari's changes in TX context handling which effects checksum and tso are added. I've also decided that multiple queues in 82574 just are a source of problems without a lot of benefit, so it still uses MSIX but with only 3 vectors, meaning it seperates TX and RX but has a single queue. Its looking very stable, I hope it fixes everyone's issues. Jack On Tue, Sep 14, 2010 at 10:59 AM, Mike Tancsa wrote: > Hi Jack, > Any plans to commit the patch below ? I have been running it on a > number of boxes and it works as expected with no side effects. > > ---Mike > > > > At 04:00 PM 8/17/2010, Pyun YongHyeon wrote: > >> On Tue, Aug 17, 2010 at 03:55:12PM -0400, Mike Tancsa wrote: >> > At 02:52 PM 8/17/2010, Pyun YongHyeon wrote: >> > >> > >Here is updated patch for HEAD and stable/8. >> > >http://people.freebsd.org/~yongari/em.csum_tso.20100817.patch >> > > >> > >It seems to work as expected under my limited environments. If >> > >> > Thanks! The patch applies cleanly and all works as expected now! I am >> > no longer able to trigger the bug. I just use the stock unmodified >> > driver normally, so no multi queues >> > >> >> Glad to hear that. Thanks for testing! >> >> > # vmstat -i >> > interrupt total rate >> > irq256: em0 149 0 >> > irq257: em1 3 0 >> > irq259: em3 971 2 >> > irq260: ahci0 1520 3 >> > >> > >> > >> > em3: flags=8843 metric 0 mtu >> 1500 >> > >> options=219b >> > ether 00:15:17:xx:xx:xx >> > inet6 fe80::215:17ff:fexx:xxxx%em3 prefixlen 64 scopeid 0x4 >> > inet 192.168.xx.xx netmask 0xffffff00 broadcast 192.168.xx.xx >> > nd6 options=3 >> > media: Ethernet autoselect (100baseTX ) >> > status: active >> > >> > >> > em3@pci0:3:0:0: class=0x020000 card=0x34ec8086 chip=0x10d38086 >> > rev=0x00 hdr=0x00 >> > vendor = 'Intel Corporation' >> > device = 'Intel 82574L Gigabit Ethernet Controller (82574L)' >> > class = network >> > subclass = ethernet >> > cap 01[c8] = powerspec 2 supports D0 D3 current D0 >> > cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message >> > cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) >> > cap 11[a0] = MSI-X supports 5 messages in map 0x1c >> > >> > >> > >> > patch < em.csum_tso.20100817.patch >> > Hmm... Looks like a unified diff to me... >> > The text leading up to this was: >> > -------------------------- >> > |Index: sys/dev/e1000/if_em.c >> > |=================================================================== >> > |--- sys/dev/e1000/if_em.c (revision 211398) >> > |+++ sys/dev/e1000/if_em.c (working copy) >> > -------------------------- >> > Patching file sys/dev/e1000/if_em.c using Plan A... >> > Hunk #1 succeeded at 237. >> > Hunk #2 succeeded at 1730. >> > Hunk #3 succeeded at 1759. >> > Hunk #4 succeeded at 1930. >> > Hunk #5 succeeded at 3148. >> > Hunk #6 succeeded at 3351. >> > Hunk #7 succeeded at 3533. >> > Hunk #8 succeeded at 3590. >> > Hunk #9 succeeded at 3603. >> > Hmm... The next patch looks like a unified diff to me... >> > The text leading up to this was: >> > -------------------------- >> > |Index: sys/dev/e1000/if_em.h >> > |=================================================================== >> > |--- sys/dev/e1000/if_em.h (revision 211398) >> > |+++ sys/dev/e1000/if_em.h (working copy) >> > -------------------------- >> > Patching file sys/dev/e1000/if_em.h using Plan A... >> > Hunk #1 succeeded at 284. >> > done >> > >> > ---Mike >> > >> > >> > >you're using multiple Tx queues with em(4) it would be better to >> > >disable Tx checksum offloading as driver always have to create a >> > >new checksum context for each frame. This will effectively disable >> > >pipelined Tx data DMA which in turn greatly slows down Tx >> > >performance for small sized frames. The reason driver have to >> > >create a new checksum context when it uses multiple Tx queues comes >> > >from hardware limitation. The controller tracks only for the last >> > >context descriptor that was written such that driver does not know >> > >the state of checksum context configured in other Tx queue. >> > >Hope this helps. >> > > >> > >> >> > >> >> > >> ---Mike >> > >> >> > >> >> > >> At 03:36 PM 7/2/2010, Pyun YongHyeon wrote: >> > >> >On Fri, Jul 02, 2010 at 01:39:22PM -0400, Mike Tancsa wrote: >> > >> >> Hi Jack, >> > >> >> Just a followup to the email below. I now saw what appears >> > >> >> to be the same problem on RELENG_8, but on a different nic and >> with >> > >> >> VLANs. So not sure if this is a general em problem, a problem >> > >> >> specific to some em NICs, or a TSO problem in general. The issue >> > >> >> seemed to be triggered when I added a new vlan based on >> > >> >> >> > >> >> em3@pci0:14:0:0: class=0x020000 card=0x109a15d9 >> > >> >> chip=0x109a8086 rev=0x00 hdr=0x00 >> > >> >> vendor = 'Intel Corporation' >> > >> >> device = 'Intel PRO/1000 PL Network Adaptor (82573L)' >> > >> >> class = network >> > >> >> subclass = ethernet >> > >> >> cap 01[c8] = powerspec 2 supports D0 D3 current D0 >> > >> >> cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 >> message >> > >> >> cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link >> x1(x1) >> > >> >> >> > >> >> pci14: on pcib5 >> > >> >> em3: port >> 0x6000-0x601f >> > >> >> mem 0xe8300000-0xe831ffff irq 17 at device 0.0 on pci14 >> > >> >> em3: Using MSI interrupt >> > >> >> em3: [FILTER] >> > >> >> em3: Ethernet address: 00:30:48:9f:eb:81 >> > >> >> >> > >> >> em3: flags=8943 >> > >> >> metric 0 mtu 1500 >> > >> >> >> options=2098 >> > >> >> ether 00:30:48:9f:eb:81 >> > >> >> inet 10.255.255.254 netmask 0xfffffffc broadcast >> > >10.255.255.255 >> > >> >> media: Ethernet autoselect (1000baseT ) >> > >> >> status: active >> > >> >> >> > >> >> I had to disable tso, rxcsum and txsum in order to see the devices >> on >> > >> >> the other side of the two vlans trunked off em3. Unfortunately, >> the >> > >> >> other sides were switches 100km and 500km away so I didnt have any >> > >> >> tcpdump capabilities to diagnose the issue. I had already created >> > >> >> one vlan off this NIC and all was fine. A few weeks later, I >> added a >> > >> >> new one and I could no longer telnet into the remote switches from >> > >> >> the local machine.... But, I could telnet into the switches from >> > >> >> machines not on the problem box. Hence, it would appear to be a >> > >> >> general TSO issue no ? I disabled tso on the nic (I didnt disable >> > >> >> net.inet.tcp.tso as I forgot about that).. Still nothing. I could >> > >> >> always ping the remote devices, but no tcp services. I then >> > >> >> remembered this issue from before, so I tried disabling tso on the >> > >> >> NIC. Still nothing. Then I disabled rxcsum and txcsum and I could >> > >> >> then telnet into the remote devices. >> > >> >> >> > >> >> This newly observed issue was from a buildworld on Mon Jun 14 >> > >> >> 11:29:12 EDT 2010. >> > >> >> >> > >> >> I will try and recreate the issue locally again to see if I can >> > >> >> trigger the problem on demand. Any thoughts on what it might be ? >> > >> >> Perhaps an issue specific to certain em nics ? >> > >> >> >> > >> > >> > >> >http://www.freebsd.org/cgi/query-pr.cgi?pr=141843 >> > >> >I'm not sure whether you're seeing the same issue though. >> > >> >I didn't have chance to try latest em(4) on stable/7. >> > >> >> > >> -------------------------------------------------------------------- >> > >> Mike Tancsa, tel +1 519 651 3400 >> > >> Sentex Communications, mike@sentex.net >> > >> Providing Internet since 1994 www.sentex.net >> > >> Cambridge, Ontario Canada >> www.sentex.net/mike >> > >> >> > >> > -------------------------------------------------------------------- >> > Mike Tancsa, tel +1 519 651 3400 >> > Sentex Communications, mike@sentex.net >> > Providing Internet since 1994 www.sentex.net >> > Cambridge, Ontario Canada www.sentex.net/mike >> > >> > > -------------------------------------------------------------------- > Mike Tancsa, tel +1 519 651 3400 > Sentex Communications, mike@sentex.net > Providing Internet since 1994 www.sentex.net > Cambridge, Ontario Canada www.sentex.net/mike > > From owner-freebsd-stable@FreeBSD.ORG Sat Sep 25 00:22:07 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B01F8106566B; Sat, 25 Sep 2010 00:22:07 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 66E1A8FC20; Sat, 25 Sep 2010 00:22:07 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id E5C5A1FFC34; Sat, 25 Sep 2010 00:03:14 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id BF2018452F; Sat, 25 Sep 2010 02:03:14 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Joe Shevland References: <201009011653.o81Grkm4056064@fire.js.berklix.net> <201009011902.06538.hselasky@c2i.net> <4C8627A6.1090308@icyb.net.ua> <4C989989.4050408@icyb.net.ua> <4C98AC42.1040104@digiware.nl> <20100921131610.GA58719@icarus.home.lan> <4C98B7E7.1020403@digiware.nl> <4C98E71F.4040800@gmail.com> Date: Sat, 25 Sep 2010 02:03:14 +0200 In-Reply-To: <4C98E71F.4040800@gmail.com> (Joe Shevland's message of "Wed, 22 Sep 2010 03:10:55 +1000") Message-ID: <868w2qofjx.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org, Andriy Gapon , vadim_nuclight@mail.ru, freebsd-security@freebsd.org, Willem Jan Withagen , Jeremy Chadwick Subject: Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Sep 2010 00:22:07 -0000 Joe Shevland writes: > My thoughts are below - remembering its a volunteer project, people > spend their precious time to make it happen, and > noneofthatwisthandingitsstilldamngood: > > a) if you don't like it, fix it. > b) if you can't fix it, pay someone else to fix it > c) if you can't fix it or otherwise be helpful, remain silent That's a bit harsh. In more general terms, to get something done, you need someone with a) knowledge, b) opportunity and c) motivation. If you don't have all three, find someone who has at least one and provide what's missing. Money can provide opportunity, motivation, or both, but it is not the only solution. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-stable@FreeBSD.ORG Sat Sep 25 08:13:45 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76181106564A for ; Sat, 25 Sep 2010 08:13:45 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id D8BB08FC2B for ; Sat, 25 Sep 2010 08:13:44 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id o8P8DgNf063399; Sat, 25 Sep 2010 18:13:42 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sat, 25 Sep 2010 18:13:41 +1000 (EST) From: Ian Smith To: Ted Faber In-Reply-To: <20100922171008.GA92070@zod.isi.edu> Message-ID: <20100925181038.T11124@sola.nimnet.asn.au> References: <20100224165203.GA10423@zod.isi.edu> <20100225152711.M16250@sola.nimnet.asn.au> <20100226013551.GA67689@zod.isi.edu> <20100922181029.D11124@sola.nimnet.asn.au> <20100922171008.GA92070@zod.isi.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org Subject: Re: resume slow on Thinkpad T42 FreeBSD 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Sep 2010 08:13:45 -0000 On Wed, 22 Sep 2010, Ted Faber wrote: > Sorry, Ian, I don't have anything new, wrt the ATA. Thanks Ted. Interesting that nobody else seems to have run into this issue, must be a (some?) Thinkpads thing .. cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Sat Sep 25 09:11:59 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7CAB1065674 for ; Sat, 25 Sep 2010 09:11:59 +0000 (UTC) (envelope-from vmagerya@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3FB168FC1B for ; Sat, 25 Sep 2010 09:11:58 +0000 (UTC) Received: by bwz15 with SMTP id 15so3222841bwz.13 for ; Sat, 25 Sep 2010 02:11:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=E0REVE2kw9SDo3zLEmTVbIr+Ghso/A4unxgtm+uV4Pc=; b=Pj+fCWMEfjujgYwKr5VJeTciWj19SXhpd70EQNKCPu+NazP7j2bSD59/oNu2K+ccY0 m3mjdX7IT3hLGDu698lKy2soBfmwPfa2RFs6nEbvnXftxDwCurHatu2VeLHtIDCz4h8Q VwbcPAzl3YBx7A5cbtReGfElKBEkk+XesMl28= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=aVvGjnrDfI6+7WoWGleTKImSdTztH5r/lOy1xtU2F7maT89IRdAaaP4rEiFxIuU46O b62yi9ngiQyuM0mMm9RPypGfePbwwfpfX41rTPGcOwMwQJ1pR/2E+Wp8rLUYxeWTVtoI axvT0zNS7LRnIU2FrbLQFcijWWrsOamO91+Pw= Received: by 10.204.56.143 with SMTP id y15mr2798193bkg.198.1285404509066; Sat, 25 Sep 2010 01:48:29 -0700 (PDT) Received: from [172.16.0.6] (tx97.net [85.198.160.156]) by mx.google.com with ESMTPS id f18sm2315378bkf.15.2010.09.25.01.48.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 25 Sep 2010 01:48:28 -0700 (PDT) Message-ID: <4C9DB6F5.6010305@gmail.com> Date: Sat, 25 Sep 2010 11:46:45 +0300 From: Vitaly Magerya User-Agent: Thunderbird MIME-Version: 1.0 To: Ian Smith References: <20100224165203.GA10423@zod.isi.edu> <20100225152711.M16250@sola.nimnet.asn.au> <20100226013551.GA67689@zod.isi.edu> <20100922181029.D11124@sola.nimnet.asn.au> <20100922171008.GA92070@zod.isi.edu> <20100925181038.T11124@sola.nimnet.asn.au> In-Reply-To: <20100925181038.T11124@sola.nimnet.asn.au> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Ted Faber Subject: Re: resume slow on Thinkpad T42 FreeBSD 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Sep 2010 09:11:59 -0000 Ian Smith wrote: > On Wed, 22 Sep 2010, Ted Faber wrote: > > > Sorry, Ian, I don't have anything new, wrt the ATA. > > Thanks Ted. Interesting that nobody else seems to have run into this > issue, must be a (some?) Thinkpads thing .. FWIW, my Thinkpad T40 does the same thing on 8.1: after resume from S3 it's unusably slow (it takes seconds between a key is pressed and it's displayed on screen), and then after a while it works ok. This has been like this in 7.0 too (except I don't know if it ever recovered the speed; I remember shutting it down as soon as I saw how slow it is). From owner-freebsd-stable@FreeBSD.ORG Sat Sep 25 09:39:44 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5564B106566C; Sat, 25 Sep 2010 09:39:44 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 0EEF48FC15; Sat, 25 Sep 2010 09:39:43 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id o8P9dhsH045736; Sat, 25 Sep 2010 05:39:43 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o8P9dgJ4045735; Sat, 25 Sep 2010 09:39:42 GMT (envelope-from tinderbox@freebsd.org) Date: Sat, 25 Sep 2010 09:39:42 GMT Message-Id: <201009250939.o8P9dgJ4045735@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [releng_8_1 tinderbox] failure on i386/i386 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Sep 2010 09:39:44 -0000 TB --- 2010-09-25 09:27:31 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-09-25 09:27:31 - starting RELENG_8_1 tinderbox run for i386/i386 TB --- 2010-09-25 09:27:31 - cleaning the object tree TB --- 2010-09-25 09:32:30 - cvsupping the source tree TB --- 2010-09-25 09:32:30 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup5.freebsd.org /tinderbox/RELENG_8_1/i386/i386/supfile TB --- 2010-09-25 09:39:42 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2010-09-25 09:39:42 - ERROR: unable to cvsup the source tree TB --- 2010-09-25 09:39:42 - 2.52 user 214.91 system 731.88 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8_1-i386-i386.full From owner-freebsd-stable@FreeBSD.ORG Sat Sep 25 13:50:22 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 316D1106567A; Sat, 25 Sep 2010 13:50:22 +0000 (UTC) (envelope-from alexander@kojevnikov.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id D15598FC14; Sat, 25 Sep 2010 13:50:21 +0000 (UTC) Received: by qyk31 with SMTP id 31so2795243qyk.13 for ; Sat, 25 Sep 2010 06:50:21 -0700 (PDT) Received: by 10.220.60.10 with SMTP id n10mr1506210vch.185.1285421080968; Sat, 25 Sep 2010 06:24:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.115.169 with HTTP; Sat, 25 Sep 2010 06:24:20 -0700 (PDT) From: Alexander Kojevnikov Date: Sat, 25 Sep 2010 23:24:20 +1000 Message-ID: To: freebsd-ports@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: Subject: Web feeds for UPDATING files X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Sep 2010 13:50:22 -0000 On 25 September 2010 17:04, Alexander Kojevnikov wrote: > On 25 September 2010 15:44, jhell wrote: >> Really awesome! >> >> This will come in handy to serve up stable/*/UPDATING and head/UPDATING >> to. And thinking along those lines it could probably be incorporated >> directly into the DAV tree on svn. to serve directly from there. > > Great idea, I'll try to implement both feeds during the weekend and > will post here and on freebsd-current@ and freebsd-stable@ when it's > done. ...and done: http://updating.versia.com/ The site now features Atom feeds for the following files: * ports/UPDATING * head/UPDATING * stable/7/UPDATING * stable/8/UPDATING Hope you find the feeds useful. Cheers, Alex PS: I apologise to ports/UPDATING subscribers who got quite a few duplicate entries. I barely missed the Ballmer Peak, just delete those. From owner-freebsd-stable@FreeBSD.ORG Sat Sep 25 18:13:17 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BC3E106564A; Sat, 25 Sep 2010 18:13:17 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id AECF98FC16; Sat, 25 Sep 2010 18:13:16 +0000 (UTC) Received: by iwn34 with SMTP id 34so4280006iwn.13 for ; Sat, 25 Sep 2010 11:13:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=16IK9/Ajg6H8t8Jmx2C80/asBI1hNn5dB4U84+owuXo=; b=hAuSJKk5AAbnAVRarL9VuLUV4mAL8kOjSZb4+Dk1oTy7UyMdkxfMdgNl395890+yXU ZJjgyi0ZU8oF/wXb+iJu5RVg/0VtGWqjcSTv9OO85Ob52YIYTroAZXSLxr5alkSP6B5T voCGAfgJQBIFMCXXXGYwJuKaO2S46i58DQEiI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=I4TxpE97OSediVfxRTBvspkuBAzi83kXHzyOnlhIknr/AuJ5SxET05z6hBH0PwK27y 1/rGON3pbjXjuyIao9pcr5r8VwTEVLBIUa/K2+BiBoOR7Q0Ln+oWNjvG1bkFAoD7uM8I vc7nF/Tf8HCvmiTtCOwzPJ/0fFHBDUvIYleCs= Received: by 10.231.35.202 with SMTP id q10mr5942088ibd.138.1285438395536; Sat, 25 Sep 2010 11:13:15 -0700 (PDT) Received: from centel.dataix.local (adsl-99-19-43-205.dsl.klmzmi.sbcglobal.net [99.19.43.205]) by mx.google.com with ESMTPS id h8sm3878464ibk.3.2010.09.25.11.13.13 (version=SSLv3 cipher=RC4-MD5); Sat, 25 Sep 2010 11:13:14 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C9E3BB9.2040800@DataIX.net> Date: Sat, 25 Sep 2010 14:13:13 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.9) Gecko/20100917 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Alexander Kojevnikov References: In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org, freebsd-ports@freebsd.org Subject: Re: Web feeds for UPDATING files X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Sep 2010 18:13:17 -0000 On 09/25/2010 09:24, Alexander Kojevnikov wrote: > On 25 September 2010 17:04, Alexander Kojevnikov > wrote: >> On 25 September 2010 15:44, jhell wrote: >>> Really awesome! >>> >>> This will come in handy to serve up stable/*/UPDATING and head/UPDATING >>> to. And thinking along those lines it could probably be incorporated >>> directly into the DAV tree on svn. to serve directly from there. >> >> Great idea, I'll try to implement both feeds during the weekend and >> will post here and on freebsd-current@ and freebsd-stable@ when it's >> done. > > ...and done: > > http://updating.versia.com/ > > The site now features Atom feeds for the following files: > > * ports/UPDATING > * head/UPDATING > * stable/7/UPDATING > * stable/8/UPDATING > > Hope you find the feeds useful. > > Cheers, > Alex > > PS: I apologise to ports/UPDATING subscribers who got quite a few > duplicate entries. I barely missed the Ballmer Peak, just delete > those. Your amazing! Thanks Alexander! -- jhell,v From owner-freebsd-stable@FreeBSD.ORG Sat Sep 25 20:25:07 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4BF591065675; Sat, 25 Sep 2010 20:25:07 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 74ED08FC17; Sat, 25 Sep 2010 20:25:06 +0000 (UTC) Received: by bwz15 with SMTP id 15so3472640bwz.13 for ; Sat, 25 Sep 2010 13:25:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=w8MMhcf9Im+v5GsKTTXjbUw4o7ml9iPLZDTPWHKs1Hg=; b=jdPtl5x0n4z4bnlDVA5zkdYIKIY18lRaD9Zkgrq44wn8J0G1slU+XAWMihCi2LONE9 i0Wm/N4AoEuaVUzoCWw3vS7vNHyhRg19i7JS6fUzr7O8CxFMWBtLfLJxl//mJUiGu3FO J70SIU/UeAo+aLmySFy2wN4KrJKNN6xButCgU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=rSMMDAJ1BfouIbRxPBhPQylTPlzEvN6YNMjk7oMcqJrIogeuXToMitnxmAA6xEnGv2 jt+WQDZiBumYTiH5zPSVlYDrSVeApL7xNa1WK0M9DtoavXpBK3kcp651ZapB/A2CxNLk ksMzTeKOvI2ZdpHFr39KoXsX+a6zyJoHaHK7I= MIME-Version: 1.0 Received: by 10.204.137.80 with SMTP id v16mr3561950bkt.46.1285446304042; Sat, 25 Sep 2010 13:25:04 -0700 (PDT) Received: by 10.204.97.208 with HTTP; Sat, 25 Sep 2010 13:25:03 -0700 (PDT) In-Reply-To: <4C9E3BB9.2040800@DataIX.net> References: <4C9E3BB9.2040800@DataIX.net> Date: Sat, 25 Sep 2010 22:25:03 +0200 Message-ID: From: David DEMELIER To: jhell Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org, Alexander Kojevnikov , freebsd-ports@freebsd.org Subject: Re: Web feeds for UPDATING files X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Sep 2010 20:25:07 -0000 2010/9/25 jhell : > On 09/25/2010 09:24, Alexander Kojevnikov wrote: >> On 25 September 2010 17:04, Alexander Kojevnikov >> wrote: >>> On 25 September 2010 15:44, jhell wrote: >>>> Really awesome! >>>> >>>> This will come in handy to serve up stable/*/UPDATING and head/UPDATIN= G >>>> to. And thinking along those lines it could probably be incorporated >>>> directly into the DAV tree on svn. to serve directly from there. >>> >>> Great idea, I'll try to implement both feeds during the weekend and >>> will post here and on freebsd-current@ and freebsd-stable@ when it's >>> done. >> >> ...and done: >> >> http://updating.versia.com/ >> >> The site now features Atom feeds for the following files: >> >> * ports/UPDATING >> * head/UPDATING >> * stable/7/UPDATING >> * stable/8/UPDATING >> >> Hope you find the feeds useful. >> >> Cheers, >> Alex >> >> PS: I apologise to ports/UPDATING subscribers who got quite a few >> duplicate entries. I barely missed the Ballmer Peak, just delete >> those. > > Your amazing! > > Thanks Alexander! > > -- > > =C2=A0jhell,v > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > It's so great that it should be merge to the official FreeBSD web page! Thanks a lot! Kind regards, --=20 Demelier David