From owner-freebsd-stable@FreeBSD.ORG Sun Dec 7 03:45:12 2008 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 F3E411065672 for ; Sun, 7 Dec 2008 03:45:11 +0000 (UTC) (envelope-from lists@aquezada.com) Received: from aphrodite.aquezada.com (h216-235-8-211.host.egate.net [216.235.8.211]) by mx1.freebsd.org (Postfix) with ESMTP id B527C8FC0A for ; Sun, 7 Dec 2008 03:45:11 +0000 (UTC) (envelope-from lists@aquezada.com) Received: from localhost (localhost [127.0.0.1]) by aphrodite.acf.aquezada.com (Postfix) with ESMTP id A134E3F43F for ; Sat, 6 Dec 2008 22:29:23 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aquezada.com; h= x-mailer:mime-version:message-id:date:organization :content-transfer-encoding:content-type:from:subject:received :received:received:received:x-virus-scanned; s=sel-sept-2008; t= 1228620547; bh=lxYEalh9HQ/9Wen9BUgs4KTfqAfi77OgpIu0prCpRQc=; b=j Nuo4FKqE/5fd7OviV+vvcufHKwmd9hFAW63T6P0XwfkApB0yZn6CfEC8EFw7mt57 B9+57j2IEukcuUDHOKv/7Jp5IkV0XZKh+FXiC9SFvqw+pwP1j/GJdBFl2n1NNLRD AbB/IBv3Y5EMToibZn2h+MpJrCjX6pIv+OaoepETuU= X-Virus-Scanned: amavisd-new at aquezada.com Received: from aphrodite.acf.aquezada.com ([127.0.0.1]) by localhost (aphrodite.acf.aquezada.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id IQTnZj1oWP3V for ; Sat, 6 Dec 2008 22:29:07 -0500 (EST) Received: from jupiter.acf.aquezada.com (jupiter.acf.aquezada.com [192.168.5.5]) by aphrodite.acf.aquezada.com (Postfix) with ESMTP id E4F193F438 for ; Sat, 6 Dec 2008 22:29:06 -0500 (EST) Received: from jupiter.acf.aquezada.com (jupiter.acf.aquezada.com [127.0.0.1]) by jupiter.acf.aquezada.com (8.14.3/8.14.2) with ESMTP id mB73T55U016229 for ; Sat, 6 Dec 2008 22:29:06 -0500 Received: (from jdunn@localhost) by jupiter.acf.aquezada.com (8.14.3/8.14.3/Submit) id mB73T5XU016227 for stable@freebsd.org; Sat, 6 Dec 2008 22:29:05 -0500 X-Authentication-Warning: jupiter.acf.aquezada.com: jdunn set sender to lists@aquezada.com using -f From: "Julian C. Dunn" To: stable@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Aquezada Productions Date: Sat, 06 Dec 2008 22:29:04 -0500 Message-Id: <1228620544.2949.3.camel@jupiter.acf.aquezada.com> Mime-Version: 1.0 X-Mailer: Evolution 2.24.2 (2.24.2-1.fc10) Cc: Subject: bsnmpd hrProcessorLoad results (still) incorrect X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Dec 2008 03:45:12 -0000 After seeing that my CPU utilization is constantly "100%" according to bsnmpd, I Googled and found this thread: http://kerneltrap.org/mailarchive/freebsd-current/2008/5/7/1747854/thread It seems to have gone nowhere. Any idea if a fix is in the works? - Julian -- [ Julian C. Dunn * Sorry, I'm ] [ WWW: http://www.aquezada.com/staff/julian * only Web 1.0 ] [ gopher://sdf.lonestar.org/11/users/keymaker * compliant! ] [ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9 ] From owner-freebsd-stable@FreeBSD.ORG Sun Dec 7 06:18:33 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8368106564A for ; Sun, 7 Dec 2008 06:18:33 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id AA8988FC18 for ; Sun, 7 Dec 2008 06:18:33 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id E26571D0531; Sun, 7 Dec 2008 01:18:32 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Sun, 07 Dec 2008 01:18:32 -0500 X-Sasl-enc: BEYsYZ7FETBtOx8AVpz0jGvVIry7QuvUHkFb3CkTeKL5 1228630712 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 1C118AFB6; Sun, 7 Dec 2008 01:18:32 -0500 (EST) Message-ID: <493B6AB6.2040704@incunabulum.net> Date: Sun, 07 Dec 2008 06:18:30 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: josh.carroll@gmail.com References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> <200812041747.09040.gnemmi@gmail.com> <8cb6106e0812040902g69ec2f84t814c2f2b5cdb33f6@mail.gmail.com> In-Reply-To: <8cb6106e0812040902g69ec2f84t814c2f2b5cdb33f6@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org, Gonzalo Nemmi Subject: Re: ext2 inode size patch - RE: PR kern/124621 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2008 06:18:33 -0000 FYI: The ext2 IFS driver for Windows v1.11a also appears to have the inode size issue: http://www.fs-driver.org/ I was not able to mount an ext2 filesystem with 256 byte inode size using this driver. Its installer will see that the filesystem exists, that it's ext2, but whenever you try to mount, you get nothing -- a very similar failure mode to the FreeBSD ext2fs driver. Again, it sounds like the author is actively maintaining it, so it might be worth contacting him to pool resources. cheers, BMS From owner-freebsd-stable@FreeBSD.ORG Sun Dec 7 19:36:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64562106564A for ; Sun, 7 Dec 2008 19:36:38 +0000 (UTC) (envelope-from danielgonzalesn@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.190]) by mx1.freebsd.org (Postfix) with ESMTP id DCB798FC18 for ; Sun, 7 Dec 2008 19:36:37 +0000 (UTC) (envelope-from danielgonzalesn@gmail.com) Received: by fk-out-0910.google.com with SMTP id k31so1450687fkk.11 for ; Sun, 07 Dec 2008 11:36:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=+dh8u8upe5ROqyY6jFe14c4jhfCwAwEo+9ZfenAJDlQ=; b=rCNsMAn5Rxzh7U8/w0IyhV6W3fvmY3+0j1K6tVKKABjCw9kFVOwcVc1c3UM7/TszS/ DtBUF+/P9delTWjvoYyg69iexhhgZKT2LGKq4o3R5hFgJec41Qtg1mY6lTBn/8nKHjFl hyxy2RcD2UP9LJ7PN2ut/ju65rJ9nijngeAO0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=w7iBQiZKbxj+3wbgjdvYA/6lLRSg5Qbwl7kzN2yQUFG2cTbjyIz4q1KD+Cr54pDgBN ac5CdCsvQULoPbaVtoLNXeWn/JLSb6trVqD0JEXBUDfAjWEdJwlMa2V5PyZnvNH59UsZ kQ44I05TACymVdQ4Hr3AVDxvxV5DUcIyIlHYo= Received: by 10.223.107.198 with SMTP id c6mr1116892fap.32.1228676666872; Sun, 07 Dec 2008 11:04:26 -0800 (PST) Received: by 10.223.109.74 with HTTP; Sun, 7 Dec 2008 11:04:26 -0800 (PST) Message-ID: <993c11f30812071104x3751b4a3g1ba39417eda68a12@mail.gmail.com> Date: Sun, 7 Dec 2008 14:04:26 -0500 From: DanielX To: freebsd-stable@freebsd.org, freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Error install FreeBSD 7.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2008 19:36:38 -0000 hello, I had problems when trying to install FreeBSD 7.0 (amd and i386) to my dv2125nr HP Pavilion laptop and other HP Pavilion dv9700t laptop comes this error, install succeed, but I doubt it comes out that error: loading required module `pci` ACPI autoload failed - no search file or directory int=3D00000006 en=3D000000000 efl=3D00010882 eip=3D00460da8 =85.. BTX halted Thank you --=20 DanielX H. Gonzales Nu=F1ez Est. Ing. Sistemas Uni. Privada del Norte From owner-freebsd-stable@FreeBSD.ORG Sun Dec 7 20:24:04 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 696BC1065673 for ; Sun, 7 Dec 2008 20:24:04 +0000 (UTC) (envelope-from david@esn.org.za) Received: from serendipity.wcape.school.za (seren.esn.org.za [196.211.28.252]) by mx1.freebsd.org (Postfix) with ESMTP id 54B428FC1A for ; Sun, 7 Dec 2008 20:24:02 +0000 (UTC) (envelope-from david@esn.org.za) Received: from intsika.ct.esn.org.za ([196.211.28.250] helo=ct.esn.org.za) by serendipity.wcape.school.za with esmtp (Exim 4.30) id 1L9QAY-000Jl3-IV; Sun, 07 Dec 2008 22:23:58 +0200 Received: from ct.esn.org.za ([192.168.0.32]) by ct.esn.org.za with Microsoft SMTPSVC(6.0.3790.3959); Sun, 7 Dec 2008 22:23:58 +0200 Received: from exchange.ct.esn.org.za ([fe80::3c71:5518:de45:c66c]) by exchange.ct.esn.org.za ([fe80::3c71:5518:de45:c66c%10]) with mapi; Sun, 7 Dec 2008 22:23:57 +0200 From: David Peall To: Christian Peron Date: Sun, 7 Dec 2008 22:23:57 +0200 Thread-Topic: rtfree: 0xffffff00013797c0 has 1 refs Thread-Index: AclX60PsEcRQH2Q8QAaMlLN5ZkqA6gAvAWMA Message-ID: <0807767D2D53E649827BC55A3A53B06709C6C0DD9C@exchange.ct.esn.org.za> References: <0807767D2D53E649827BC55A3A53B06709C6C04BFE@exchange.ct.esn.org.za> <20081206211344.GA60861@jnz.sqrt.ca> In-Reply-To: <20081206211344.GA60861@jnz.sqrt.ca> Accept-Language: en-US, en-ZA Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-ZA Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 07 Dec 2008 20:23:58.0036 (UTC) FILETIME=[BBCE8140:01C958A9] X-Antivirus-Scanned: Clean by seren.wcsn.org.za Cc: "'freebsd-stable@freebsd.org'" Subject: RE: rtfree: 0xffffff00013797c0 has 1 refs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Dec 2008 20:24:04 -0000 > -----Original Message----- > From: Christian Peron [mailto:csjp@freebsd.org] > Sent: 06 December 2008 11:14 PM > To: David Peall > Cc: 'freebsd-stable@freebsd.org' > Subject: Re: rtfree: 0xffffff00013797c0 has 1 refs > > I have just fixed a similar (possibly the same) issue in -CURRENT. > > Please try the patch at: > > http://people.freebsd.org/~csjp/if_ether.1228494489.diff > > (Fetch it into /usr/src/sys/netinet and apply there). > > Let me know if this solves your problem, if it does I will try to get > it > in for the release. Patch is applied, messages seem to have stopped I was getting every few sec= onds. I will keep an eye on it and let you know if anything pops up. Thanks! -- David Peall :: IT Manager e-Schools' Network :: http://www.esn.org.za/ Phone +27 (021) 674-9140 From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 08:50:19 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20E641065673 for ; Mon, 8 Dec 2008 08:50:19 +0000 (UTC) (envelope-from frode@nordahl.net) Received: from smtp3.powertech.no (smtp3.powertech.no [195.159.0.178]) by mx1.freebsd.org (Postfix) with ESMTP id A2DF38FC25 for ; Mon, 8 Dec 2008 08:50:18 +0000 (UTC) (envelope-from frode@nordahl.net) Received: from ws24.ns5.powertech.no (ws24.ns5.powertech.no [195.159.6.24]) by smtp3.powertech.no (Postfix) with ESMTP id 4E5A1C5638; Mon, 8 Dec 2008 09:50:17 +0100 (CET) Message-Id: From: Frode Nordahl To: Kostik Belousov In-Reply-To: <20081205195922.GP2038@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Mon, 8 Dec 2008 09:50:16 +0100 References: <3B675385-956D-4A26-8E09-E338DF7D7244@nordahl.net> <20081203173939.GA2401@deviant.kiev.zoral.com.ua> <20081203194348.GB2401@deviant.kiev.zoral.com.ua> <8A6A8FA5-07A6-4A12-B9AD-6E77E534CED7@nordahl.net> <20081204120736.GC2038@deviant.kiev.zoral.com.ua> <576BB990-78D8-4CE8-9660-55EB989EE3BA@nordahl.net> <20081205195922.GP2038@deviant.kiev.zoral.com.ua> X-Mailer: Apple Mail (2.929.2) Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.1-PRERELEASE-p1, panic: dqget: free dquot isn't X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Dec 2008 08:50:19 -0000 On 5. des.. 2008, at 20.59, Kostik Belousov wrote: > On Fri, Dec 05, 2008 at 08:11:02PM +0100, Frode Nordahl wrote: >> >> On 4. des.. 2008, at 13.20, Frode Nordahl wrote: >> >>> On 4. des.. 2008, at 13.07, Kostik Belousov wrote: >>> >>>> On Thu, Dec 04, 2008 at 08:12:45AM +0100, Frode Nordahl wrote: >>>>> Got it! >>>>> >>>>> panic: dqget: free dquot isn't dq=0xffffff00b3d27000 >>>>> (kgdb) p/x *(struct dquot *)0xffffff00b3d27000 >>>>> $1 = {dq_hash = {le_next = 0x0, le_prev = 0xffffff010b9da700}, >>>>> dq_freelist = { >>>>> tqe_next = 0xffffff0055e2de00, tqe_prev = 0xffffffff80b03710}, >>>>> dq_lock = { >>>>> lock_object = {lo_name = 0xffffffff8088c21c, lo_type = >>>>> 0xffffffff8088c21c, >>>>> lo_flags = 0x1030000, lo_witness_data = {lod_list = {stqe_next >>>>> = 0x0}, >>>>> lod_witness = 0x0}}, mtx_lock = 0x4, mtx_recurse = 0x0}, >>>>> dq_flags = 0xc, dq_type = 0x0, dq_cnt = 0x0, dq_id = 0x16a37d, >>>>> dq_ump = 0xffffff00038e1600, dq_dqb = {dqb_bhardlimit = 0x0, >>>>> dqb_bsoftlimit = 0x0, dqb_curblocks = 0x0, dqb_ihardlimit = 0x0, >>>>> dqb_isoftlimit = 0x0, dqb_curinodes = 0x1, dqb_btime = 0x493ef2b5, >>>>> dqb_itime = 0x493ef2b5}} >>>>> >>>>> Let me know if I can provide any more information! >>>>> >>>>> Updated the crashinfo archive you got an URL to yesterday if you >>>>> want >>>>> to poke around yourself. >>>> >>>> Please, try the patch below, it should fix a race I see. Quite >>>> possible, >>>> this is what you tripped over. >>> >>> Thanks! I will apply the patch and retry the steps that lead to the >>> panic! >> >> >> Good news! I have run through two and have started on the third >> iteration of the test that lead to the panic without your patch, and >> no panic so far! >> >> I will let it run through the weekend, it prooves usefull as a burn- >> in- >> test as well :-) >> >> Will this patch make it into 7.1-RELEASE? > > There is a possibility. Please inform me about the weekend burn-test > results. If results are encouranging, I am almost sure that I can > squeeze it into the release. The test has run trough the weekend without any incidents! I really hope this patch will make it into the release. Thank you for your help solving this issue! -- Frode Nordahl From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 09:53:23 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FC2E106564A; Mon, 8 Dec 2008 09:53:23 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 034CC8FC0C; Mon, 8 Dec 2008 09:53:22 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id EBD111D574B; Mon, 8 Dec 2008 04:53:21 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Mon, 08 Dec 2008 04:53:21 -0500 X-Sasl-enc: rhfjXg4Yrj5X31Es0yCqqUod8Waew8NFB37cQG82go0R 1228730001 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 48DCA13183; Mon, 8 Dec 2008 04:53:21 -0500 (EST) Message-ID: <493CEE90.7050104@FreeBSD.org> Date: Mon, 08 Dec 2008 09:53:20 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.18 (X11/20081205) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> <200812041747.09040.gnemmi@gmail.com> <4938FE44.9090608@FreeBSD.org> <4939133E.2000701@FreeBSD.org> In-Reply-To: <4939133E.2000701@FreeBSD.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: josh.carroll@gmail.com, freebsd-fs@freebsd.org Subject: Re: ext2fuse: user-space ext2 implementation X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2008 09:53:23 -0000 I have rolled a port for ext2fuse: http://people.freebsd.org/~bms/dump/fusefs-ext2fs.tar I look forward to your feedback. thanks, BMS From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 09:53:34 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 310FF1065672 for ; Mon, 8 Dec 2008 09:53:34 +0000 (UTC) (envelope-from slayer@yandex-team.ru) Received: from cavolo.yandex.ru (cavolo.yandex.ru [87.250.244.45]) by mx1.freebsd.org (Postfix) with ESMTP id A54218FC13 for ; Mon, 8 Dec 2008 09:53:33 +0000 (UTC) (envelope-from slayer@yandex-team.ru) Received: from slayer.yandex.ru (dhcp250-232.yandex.ru [87.250.250.232]) by cavolo.yandex.ru (8.14.2/8.14.2) with ESMTP id mB89TRHq050330; Mon, 8 Dec 2008 12:29:32 +0300 (MSK) (envelope-from slayer@yandex-team.ru) Message-ID: <493CE8F7.5010204@yandex-team.ru> Date: Mon, 08 Dec 2008 12:29:27 +0300 From: Oleg Gorokhov Organization: Yandex LLC User-Agent: Thunderbird 2.0.0.18 (X11/20081127) MIME-Version: 1.0 To: d@delphij.net References: <4935069A.8060209@ec-marseille.fr> <49357BD0.4000008@delphij.net> <4935944A.9090509@ec-marseille.fr> <4935C453.8070301@delphij.net> <4935D67E.4070204@delphij.net> <4936F8C4.6090006@ec-marseille.fr> <49399FA6.3060108@delphij.net> In-Reply-To: <49399FA6.3060108@delphij.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: Dr.Web (R) for Mail Servers on cavolo.yandex.ru host X-Antivirus-Code: 100000 Cc: delphij@delphij.net, freebsd-stable@freebsd.org Subject: Re: RELENG_7_1: bce driver change generating too much interrupts ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: slayer@yandex-team.ru List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2008 09:53:34 -0000 This patch committed fixes the issue reported earlier with interruptions but there is one more problem discussed here: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2008-11/msg00144.html We also have observed similar bad behavior for network (especially ssl-based) operations: imaps, ssh and smtp starttls connections - all of them were failed to establish after a day of successful operation: Dec 7 23:32:41 imaps[62530]: accepted connection Dec 7 23:32:41 imaps[62530]: SSL_accept() incomplete -> wait Dec 7 23:32:41 imaps[62530]: wrong version number in SSL_accept() -> fail Dec 7 23:32:41 master[3930]: process 62530 exited, status 75 Dec 7 23:32:41 master[3930]: service imaps pid 62530 in BUSY state: terminated abnormally Dec 7 23:39:26 imaps[91999]: SSL_accept() incomplete -> wait Dec 7 23:39:26 imaps[91999]: decryption failed or bad record mac in SSL_accept() -> fail Dec 7 23:32:44 lmtp[77715]: [lmtpd] STARTTLS failed: gamgee.yandex.ru [77.88.19.54] We have reverted back to stable before the last bce driver update was commited to releng branch and now hope that the system should run as expected. Xin LI wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > FYI, I have committed the patch as r185653 (stable/7) and r185654 > (releng/7.1) so new build would get this issue fixed. Thanks goes to > David who gave review for the changes and all who tested the earlier > patches. > > Cheers, > - -- > Xin LI http://www.delphij.net/ > FreeBSD - The Power to Serve! > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.9 (FreeBSD) > > iEYEARECAAYFAkk5n6YACgkQi+vbBBjt66BToACfTp+1hqno30HTpNfcvMn7SpAF > 6XoAn1St590CMK2Lz9jLwlnTLDKGW8cV > =/FVN > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- Oleg Gorokhov System Administrator, Yandex Tel.: +7 (495) 739-7000 (+7166) From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 09:57:42 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CE9F106564A for ; Mon, 8 Dec 2008 09:57:42 +0000 (UTC) (envelope-from ari@ish.com.au) Received: from fish.ish.com.au (eth5921.nsw.adsl.internode.on.net [59.167.240.32]) by mx1.freebsd.org (Postfix) with ESMTP id CB2E38FC16 for ; Mon, 8 Dec 2008 09:57:41 +0000 (UTC) (envelope-from ari@ish.com.au) Received: from ip-132.ish.com.au ([203.29.62.132]:56360) by fish.ish.com.au with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1L9dNe-0001GK-2W for freebsd-stable@freebsd.org; Mon, 08 Dec 2008 21:30:22 +1100 Message-Id: From: Aristedes Maniatis To: freebsd-stable Stable Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Mon, 8 Dec 2008 20:57:37 +1100 X-Mailer: Apple Mail (2.929.2) Subject: visibility of release process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Dec 2008 09:57:42 -0000 I've resisted sending this email for a while since I really don't want to start a bikeshed nor a flame. However there comes a time to express my thoughts over the lack of visibility of the release process for FreeBSD 7.1. Here are the resources I am aware of: * release timeline [1]. This page makes no mention of beta 2 which is now some weeks old, so I assume the page is not actively used as a communication tool for the status of the release. * this list [2]. Although betas are announced here, there is no information about what is happening next. * subversion. Without checking out the whole repository, it is a little hard to use this as a news source and emails to the commit list still look more like cvs than svn so it is a bit hard to see which branch commits are going to. [3] * the bug tracker. Let's just say that FreeBSD's bug tracker is fairly primitive and 'target release' is not an option. I'd like to make several suggestions which could improve the transparency of the release process: 1. Short term fix: re could make a progress announcement on the appropriate lists every 14 days during the release process. Just a short summary of URLs pointing to the bug tracker. 2. Some web based friendly end-user visibility on the commit process, per branch. People can see what is going in and being fixed, but not what is left outstanding. Fisheye is an option because it costs nothing except the small load on the svn server. 3. Improvements to the bug tracker. Personally I'd love to see something like Jira used [4] with all the sophistication of workflow, release notes, voting for bugs, etc, etc. I'm happy to help with 2 and/or 3 in terms of contribution of my time and experience. Cheers Ari Maniatis [1] http://www.freebsd.org/releases/7.1R/schedule.html [2] That is FreeBSD-stable [3] I've also made an attempt to have Atlassian use Fisheye to produce an friendly overview of the repository, however I need to get permission from FreeBSD for this to happen before Atlassian will go ahead and index the whole svn repository. I've been unable to get anyone to respond to my requests in that regard. The result might look a bit like this: http://fisheye6.atlassian.com/ [4] Disclaimer: I am an Atlassian partner and like their products, but stand to gain nothing by the decision FreeBSD core make, I just think it is the best product for FreeBSD's requirements and it works well over at Apache. --------------------------> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 11:51:31 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 763E8106564A for ; Mon, 8 Dec 2008 11:51:31 +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 A5EA18FC14 for ; Mon, 8 Dec 2008 11:51:30 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA06998 for ; Mon, 08 Dec 2008 13:51:27 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <493D0A3F.5060705@icyb.net.ua> Date: Mon, 08 Dec 2008 13:51:27 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.18 (X11/20081124) MIME-Version: 1.0 To: FreeBSD Stable Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Attempt to write outside dump device boundaries X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Dec 2008 11:51:31 -0000 System: FreeBSD 7.1-PRERELEASE r185725 amd64 Peculiarities: ZFS, GPART There is 4GB of RAM and 4GB swap/dump partition. The partition is typical swap partition only created via GPART. minidumps are enabled. I had a crash recently and here's a message from it: Dec 6 10:23:17 odyssey kernel: Uptime: 7d20h12m51s Dec 6 10:23:17 odyssey kernel: Physical memory: 4009 MB Dec 6 10:23:17 odyssey kernel: Dumping 2110 MB: 2095 2079 2063 2047 2031 2015 1999 1983 1967 1951 1935 1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023 1007 991 975 959 943 927 91 1 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15Attempt to write outside dump device boundaries. Dec 6 10:23:17 odyssey kernel: Dec 6 10:23:17 odyssey kernel: ** DUMP FAILED (ERROR 6) ** Dec 6 10:23:17 odyssey kernel: Automatic reboot in 15 seconds - press a key on the console to abort I guess the large size of the dump is because of the ZFS but I wonder why enough room for the dump could not be found. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 11:52:13 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 857261065673 for ; Mon, 8 Dec 2008 11:52:13 +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 9DF7B8FC21 for ; Mon, 8 Dec 2008 11:52:12 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA07006; Mon, 08 Dec 2008 13:52:10 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <493D0A6A.7060102@icyb.net.ua> Date: Mon, 08 Dec 2008 13:52:10 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.18 (X11/20081124) MIME-Version: 1.0 To: FreeBSD Stable , freebsd-ipfw@freebsd.org References: <4937B194.1020606@icyb.net.ua> In-Reply-To: <4937B194.1020606@icyb.net.ua> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: Re: rc.firewall: default loopback rules are set up even for custom file X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Dec 2008 11:52:13 -0000 on 04/12/2008 12:31 Andriy Gapon said the following: > I've just realized that I see in releng/7 something that I did not see > in releng/6 - even if I use a file with custom rules in firewall_type I > still get default loopback rules installed. > I think that this is not correct, I am using custom rules exactly > because I want to control *everything* (e.g. all deny rules come with > log logamount xxx). > Comments? -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 12:36:17 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D06A1065673 for ; Mon, 8 Dec 2008 12:36:17 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id F1EAE8FC1B for ; Mon, 8 Dec 2008 12:36:16 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1L9fLN-00064S-11 for freebsd-stable@freebsd.org; Mon, 08 Dec 2008 12:36:09 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 08 Dec 2008 12:36:09 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 08 Dec 2008 12:36:09 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Mon, 08 Dec 2008 13:36:01 +0100 Lines: 37 Message-ID: References: <4937B194.1020606@icyb.net.ua> <493D0A6A.7060102@icyb.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig234CFED023C56EFCBB67E622" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.18 (X11/20081125) In-Reply-To: <493D0A6A.7060102@icyb.net.ua> X-Enigmail-Version: 0.95.0 Sender: news Cc: freebsd-ipfw@freebsd.org Subject: Re: rc.firewall: default loopback rules are set up even for custom file X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Dec 2008 12:36:17 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig234CFED023C56EFCBB67E622 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Andriy Gapon wrote: > on 04/12/2008 12:31 Andriy Gapon said the following: >> I've just realized that I see in releng/7 something that I did not see= >> in releng/6 - even if I use a file with custom rules in firewall_type = I >> still get default loopback rules installed. >> I think that this is not correct, I am using custom rules exactly >> because I want to control *everything* (e.g. all deny rules come with >> log logamount xxx). >> >=20 > Comments? I agree with you - I also see them, and I'd rather not :) --------------enig234CFED023C56EFCBB67E622 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJPRSxldnAQVacBcgRApC/AKDiX4TShEutPu+qy18Bv9yU38fLewCg1S1a Sjjk30kjjPLvQ8GK/QckX8U= =egc5 -----END PGP SIGNATURE----- --------------enig234CFED023C56EFCBB67E622-- From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 14:36:25 2008 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 E4C1D1065670 for ; Mon, 8 Dec 2008 14:36:25 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from collaborativefusion.com (mx01.pub.collaborativefusion.com [206.210.89.201]) by mx1.freebsd.org (Postfix) with ESMTP id 75D238FC16 for ; Mon, 8 Dec 2008 14:36:25 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from Internal Mail-Server by mx01 (envelope-from bseklecki@collaborativefusion.com) with SMTP; 8 Dec 2008 09:36:24 -0500 From: "Brian A. Seklecki" To: Peter Jeremy In-Reply-To: <20081206210316.GP58682@server.vk2pj.dyndns.org> References: <20080812120307.GD64458@server.vk2pj.dyndns.org> <1228480461.2805.469.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> <20081206210316.GP58682@server.vk2pj.dyndns.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-VwUhoW0j05D2XMAIIYGf" Organization: Collaborative Fusion, Inc. Date: Mon, 08 Dec 2008 09:36:23 -0500 Message-Id: <1228746983.2805.567.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 (2.22.3.1-1.fc9) Cc: stable@freebsd.org, eugen@kuzbass.ru, Marian Hettwer , Pete French Subject: Re: lagg(4) and failover X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bseklecki@collaborativefusion.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2008 14:36:26 -0000 --=-VwUhoW0j05D2XMAIIYGf Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2008-12-07 at 08:03 +1100, Peter Jeremy wrote: > On 2008-Dec-05 07:34:21 -0500, "Brian A. Seklecki" > wrote: > >Well ... name a price for the development; HA L1/L2 is a feature the > >community would gladly sponsor the development of. >=20 > net/ifstated covers at least some of this. I was thinking something like a heartbeat protocol could work well w/o LACP hacking on mid-range switches. I think that's how Dell does it with the RHEL crap for Broadcom. Send multicast packets on both an active/standby link. If either node discontinues to see the others packets, some admin-configurable logic promotes (Metric/Bias/Weighting). ~BAS --=20 Brian A. Seklecki Collaborative Fusion, Inc. --=-VwUhoW0j05D2XMAIIYGf Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAkk9MOcACgkQCne6BNDQ+R8ztgCcDtQRCaddGG0FlcHtDXrxGREP e50Ani8IWwhIGiGi6h8V8p1X130/Y/gF =yClh -----END PGP SIGNATURE----- --=-VwUhoW0j05D2XMAIIYGf-- From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 14:47:26 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A86771065672 for ; Mon, 8 Dec 2008 14:47:26 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 80AD78FC12 for ; Mon, 8 Dec 2008 14:47:26 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 53E061D0332 for ; Mon, 8 Dec 2008 09:47:25 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Mon, 08 Dec 2008 09:47:25 -0500 X-Sasl-enc: YlwIJceIGHQiV7FJgtkkwFnPlbWQVwooj5ZHdcqEy7wV 1228747644 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id D434023EFB for ; Mon, 8 Dec 2008 09:47:24 -0500 (EST) Message-ID: <493D337B.1020204@incunabulum.net> Date: Mon, 08 Dec 2008 14:47:23 +0000 From: Bruce M Simpson User-Agent: Thunderbird 2.0.0.18 (X11/20081205) MIME-Version: 1.0 To: FreeBSD stable X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Experience with RDX removable backup drives? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Dec 2008 14:47:26 -0000 Are these any good? Has anyone tried them with FreeBSD and/or bacula? For small office, these look like where the price point is for backups... cheers BMS From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 16:25:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 39CEA1065676 for ; Mon, 8 Dec 2008 16:25:25 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from phoebe.cse.buffalo.edu (phoebe.cse.buffalo.edu [128.205.32.89]) by mx1.freebsd.org (Postfix) with ESMTP id EE0588FC20 for ; Mon, 8 Dec 2008 16:25:24 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from [128.205.32.76] (bauer.cse.buffalo.edu [128.205.32.76]) (authenticated bits=0) by phoebe.cse.buffalo.edu (8.14.1/8.13.7) with ESMTP id mB8GPHDV087321 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Dec 2008 11:25:18 -0500 (EST) (envelope-from kensmith@cse.buffalo.edu) From: Ken Smith To: Aristedes Maniatis In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-T13Ak8JHVDjXOAVCf97N" Organization: U. Buffalo CSE Department Date: Mon, 08 Dec 2008 11:25:17 -0500 Message-Id: <1228753517.56532.25.camel@bauer.cse.buffalo.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port X-DCC-Buffalo.EDU-Metrics: phoebe.cse.buffalo.edu 1336; Body=0 Fuz1=0 Fuz2=0 X-Spam-Status: No, score=-4.0 required=5.0 tests=RCVD_IN_DNSWL_MED autolearn=failed version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on phoebe.cse.buffalo.edu Cc: freebsd-stable Stable Subject: Re: visibility of release process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Dec 2008 16:25:25 -0000 --=-T13Ak8JHVDjXOAVCf97N Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2008-12-08 at 20:57 +1100, Aristedes Maniatis wrote: > I've resisted sending this email for a while since I really don't want =20 > to start a bikeshed nor a flame. However there comes a time to express =20 > my thoughts over the lack of visibility of the release process for =20 > FreeBSD 7.1. Here are the resources I am aware of: [ Readers' Digest Version: Known problem. Unfortunately very slowly being worked on... ] Bottom line is my communication skills suck and of the bazillion other things I could do with my time these sorts of housekeeping chores wind up at a low enough priority they don't get done. But as you and others have made clear the priority needs to get raised and I need to deal with it. That's the part being worked on. > I'd like to make several suggestions which could improve the =20 > transparency of the release process: >=20 > 1. Short term fix: re could make a progress announcement on the =20 > appropriate lists every 14 days during the release process. Just a =20 > short summary of URLs pointing to the bug tracker. That's what I'll be working on fixing short-term. Weekly status reports here. One coming tomorrow (not coincidentally likely to include 7.1-RC1 is ready, that's why its not coming today; if you look around you can probably find it but a few misc. tidbits aren't ready yet). > 2. Some web based friendly end-user visibility on the commit process, =20 > per branch. People can see what is going in and being fixed, but not =20 > what is left outstanding. Fisheye is an option because it costs =20 > nothing except the small load on the svn server. >=20 > 3. Improvements to the bug tracker. Personally I'd love to see =20 > something like Jira used [4] with all the sophistication of workflow, =20 > release notes, voting for bugs, etc, etc. Those aren't really something I'd be likely to address any time in the near future mostly because there are other folks around who are involved in those areas. They both look like they require hooks into the guts of various systems I'm more than happy other folks are much more involved in. So comments on those likely need to come from someone else(s). --=20 Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | --=-T13Ak8JHVDjXOAVCf97N Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkk9SmUACgkQ/G14VSmup/ZmEQCbBMxOYN7l5W9EhcAFHmrkKoml 32sAn2WI5C6NnAKkP+U6avUtt84/YUzt =EF4W -----END PGP SIGNATURE----- --=-T13Ak8JHVDjXOAVCf97N-- From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 18:21:16 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F886106564A for ; Mon, 8 Dec 2008 18:21:16 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail17.syd.optusnet.com.au (mail17.syd.optusnet.com.au [211.29.132.198]) by mx1.freebsd.org (Postfix) with ESMTP id 1244F8FC08 for ; Mon, 8 Dec 2008 18:21:15 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail17.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id mB8ILCEk001619 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Dec 2008 05:21:13 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id mB8ILCmg081451; Tue, 9 Dec 2008 05:21:12 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id mB8ILCa0081450; Tue, 9 Dec 2008 05:21:12 +1100 (EST) (envelope-from peter) Date: Tue, 9 Dec 2008 05:21:12 +1100 From: Peter Jeremy To: Aristedes Maniatis Message-ID: <20081208182112.GW58682@server.vk2pj.dyndns.org> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ImSVV91IQg5ga+3z" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable Stable Subject: Re: visibility of release process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Dec 2008 18:21:16 -0000 --ImSVV91IQg5ga+3z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Dec-08 20:57:37 +1100, Aristedes Maniatis wrote: >* subversion. Without checking out the whole repository, it is a =20 >little hard to use this as a news source and emails to the commit list =20 >still look more like cvs than svn so it is a bit hard to see which =20 >branch commits are going to. [3] I'm not sure what you want here. The branch is clearly indicated in both the subject and body of commit messages. What do you mean as "news source"? Commits are inherently low level and it's difficult to see how a commit could be massaged into some sort of press release without a fair amount of meta information in the commit log. >* the bug tracker. Let's just say that FreeBSD's bug tracker is fairly =20 >primitive and 'target release' is not an option. Agreed. This is an issue that comes up regularly but I don't believe a solution has been identified. I suspect one of the requirements would be that it be FOSS. >2. Some web based friendly end-user visibility on the commit process, =20 >per branch. I presume you're aware of svn.freebsd.org. > People can see what is going in and being fixed, but not =20 >what is left outstanding. If you mean open PRs, lists are regularly reported to various mailing lists and can be accessed via http://www.freebsd.org/cgi/query-pr.cgi Better integration of the PR and commit process might be nice but I'm not sure if it's practical with gnats. >[3] I've also made an attempt to have Atlassian use Fisheye to =20 >produce an friendly overview of the repository, I've had a look at several of the fisheye sites and am not sure what it would buy the Project, other than some pretty graphs. I don't see how this is any more "friendly" than svn.freebsd.org. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --ImSVV91IQg5ga+3z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkk9ZZgACgkQ/opHv/APuIeYKQCfVza5p2xHXWtBx4Dr/Vq2GOEo D6UAoMFan4Fr3tLJI7oZ39/7OXM2xAR6 =R614 -----END PGP SIGNATURE----- --ImSVV91IQg5ga+3z-- From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 19:46:08 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 75B76106564A for ; Mon, 8 Dec 2008 19:46:08 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp114.rog.mail.re2.yahoo.com (smtp114.rog.mail.re2.yahoo.com [68.142.225.230]) by mx1.freebsd.org (Postfix) with SMTP id 0B9688FC0C for ; Mon, 8 Dec 2008 19:46:07 +0000 (UTC) (envelope-from mikej@rogers.com) Received: (qmail 21066 invoked from network); 8 Dec 2008 19:46:07 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Received:Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:Importance; b=X1MrQQRgkJ2JePw7iqjNpiV4UJpLlHxOfsqKmNFObXdHab0DnwjcvNFHYyZGFacAyms9QuuGMSbNBrinaTvj8jcuZmg9AzLDtyowQu22Lu1Jr0YksbyLWbTryTxvLlxgOcP0tmJrAbQMYFyuBHukb4nHwu+OW6reWwsQucGDf1Q= ; Received: from unknown (HELO wettoast.dyndns.org) (mikej@99.227.98.203 with login) by smtp114.rog.mail.re2.yahoo.com with SMTP; 8 Dec 2008 19:46:03 -0000 X-YMail-OSG: HCB.M4wVM1ldZ46lf6iPAERSl8kYXi3hpPyvjYI5_dxyaLUfVBI.nfeTvoVGtrtRjQ-- X-Yahoo-Newman-Property: ymail-3 Received: from 38.99.187.34 (SquirrelMail authenticated user mikej) by wettoast.dyndns.org with HTTP; Mon, 8 Dec 2008 14:46:11 -0500 (EST) Message-ID: <3a6fb7145a0a6c8af136ea1a0824e5ed.squirrel@wettoast.dyndns.org> In-Reply-To: <493CE8F7.5010204@yandex-team.ru> References: <4935069A.8060209@ec-marseille.fr> <49357BD0.4000008@delphij.net> <4935944A.9090509@ec-marseille.fr> <4935C453.8070301@delphij.net> <4935D67E.4070204@delphij.net> <4936F8C4.6090006@ec-marseille.fr> <49399FA6.3060108@delphij.net> <493CE8F7.5010204@yandex-team.ru> Date: Mon, 8 Dec 2008 14:46:11 -0500 (EST) From: "Mike Jakubik" To: slayer@yandex-team.ru User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: delphij@delphij.net, d@delphij.net, freebsd-stable@freebsd.org Subject: Re: RELENG_7_1: bce driver change generating too much interrupts ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Dec 2008 19:46:08 -0000 On Mon, December 8, 2008 4:29 am, Oleg Gorokhov wrote: > This patch committed fixes the issue reported earlier with interruptions > but there is one more problem discussed here: > > http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2008-11/msg00144.html > > We also have observed similar bad behavior for network (especially > ssl-based) operations: imaps, ssh and smtp starttls connections - all of > them were failed to establish after a day of successful operation: > I wonder if my problem is related to this. I have a java chat service application that starts dropping connections after about 4 days of uptime. There is nothing in the applications logs, and i know this works fine on Linux. Will try updating to the latest bce patch tonight to see if it helps. From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 20:13:15 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CBFA1065676 for ; Mon, 8 Dec 2008 20:13:15 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id F40C78FC21 for ; Mon, 8 Dec 2008 20:13:14 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1L9mTc-0006Jl-Hd for freebsd-stable@freebsd.org; Mon, 08 Dec 2008 20:13:08 +0000 Received: from 93-138-120-23.adsl.net.t-com.hr ([93.138.120.23]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 08 Dec 2008 20:13:08 +0000 Received: from ivoras by 93-138-120-23.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 08 Dec 2008 20:13:08 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Mon, 08 Dec 2008 21:12:53 +0100 Lines: 45 Message-ID: References: <1228753517.56532.25.camel@bauer.cse.buffalo.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig816AA5C3E92CB5CF4DA49B71" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 93-138-120-23.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) In-Reply-To: <1228753517.56532.25.camel@bauer.cse.buffalo.edu> X-Enigmail-Version: 0.95.7 Sender: news Subject: Re: visibility of release process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Dec 2008 20:13:15 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig816AA5C3E92CB5CF4DA49B71 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ken Smith wrote: > On Mon, 2008-12-08 at 20:57 +1100, Aristedes Maniatis wrote: >> I've resisted sending this email for a while since I really don't want= =20 >> to start a bikeshed nor a flame. However there comes a time to express= =20 >> my thoughts over the lack of visibility of the release process for =20 >> FreeBSD 7.1. Here are the resources I am aware of: >=20 > [ Readers' Digest Version: Known problem. Unfortunately very slowly > being worked on... ] >=20 > Bottom line is my communication skills suck and of the bazillion other > things I could do with my time these sorts of housekeeping chores wind > up at a low enough priority they don't get done. But as you and others= > have made clear the priority needs to get raised and I need to deal wit= h > it. That's the part being worked on. Hmm, would something twitter-like + a cron-job reminding you to write something help? :) . --------------enig816AA5C3E92CB5CF4DA49B71 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkk9f8UACgkQldnAQVacBciB4gCg58ljbkM8MbH/zBPFWc3KpLQ1 ilMAoNZuyft0ga5EJwrLONQma4q8adLl =otYa -----END PGP SIGNATURE----- --------------enig816AA5C3E92CB5CF4DA49B71-- From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 22:12:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE6771065670 for ; Mon, 8 Dec 2008 22:12:43 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6EE418FC08 for ; Mon, 8 Dec 2008 22:12:43 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id 6A1A928448 for ; Tue, 9 Dec 2008 06:12:42 +0800 (CST) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id 893E2EC2017; Tue, 9 Dec 2008 06:12:41 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id l-ax8HR410G5; Tue, 9 Dec 2008 06:12:35 +0800 (CST) Received: from charlie.delphij.net (adsl-76-237-33-62.dsl.pltn13.sbcglobal.net [76.237.33.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 4611CEC2010; Tue, 9 Dec 2008 06:12:25 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=WCcsb0EWB3ypwR7sawR1Zgx8F3q7NPi4193lA+NUZQ4AgSht1JtYOhtbVG6XsJiLY iv4PL84JVDTh0X3ygn6pw== Message-ID: <493D9BC6.8050902@delphij.net> Date: Mon, 08 Dec 2008 14:12:22 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 To: Mike Jakubik References: <4935069A.8060209@ec-marseille.fr> <49357BD0.4000008@delphij.net> <4935944A.9090509@ec-marseille.fr> <4935C453.8070301@delphij.net> <4935D67E.4070204@delphij.net> <4936F8C4.6090006@ec-marseille.fr> <49399FA6.3060108@delphij.net> <493CE8F7.5010204@yandex-team.ru> <3a6fb7145a0a6c8af136ea1a0824e5ed.squirrel@wettoast.dyndns.org> In-Reply-To: <3a6fb7145a0a6c8af136ea1a0824e5ed.squirrel@wettoast.dyndns.org> X-Enigmail-Version: 0.95.7 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, d@delphij.net, slayer@yandex-team.ru Subject: Re: RELENG_7_1: bce driver change generating too much interrupts ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2008 22:12:43 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mike Jakubik wrote: > On Mon, December 8, 2008 4:29 am, Oleg Gorokhov wrote: >> This patch committed fixes the issue reported earlier with interruptions >> but there is one more problem discussed here: >> >> http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2008-11/msg00144.html >> >> We also have observed similar bad behavior for network (especially >> ssl-based) operations: imaps, ssh and smtp starttls connections - all of >> them were failed to establish after a day of successful operation: >> > > I wonder if my problem is related to this. I have a java chat service > application that starts dropping connections after about 4 days of uptime. > There is nothing in the applications logs, and i know this works fine on > Linux. Will try updating to the latest bce patch tonight to see if it > helps. Which version are you currently using? My previous commit only fixes the excessive interrupt issue, I think this could be a different problem, I'm taking a look at the code to see if I can have something for you. Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkk9m8UACgkQi+vbBBjt66DAEQCeNHjriIsvmEB252283KhW2gvt 2WcAoKM5uQ30+mLJPgON+XdTG6qoH1uX =tGel -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 22:22:27 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5BF5106567B for ; Mon, 8 Dec 2008 22:22:27 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp130.rog.mail.re2.yahoo.com (smtp130.rog.mail.re2.yahoo.com [206.190.53.35]) by mx1.freebsd.org (Postfix) with SMTP id 54A428FC26 for ; Mon, 8 Dec 2008 22:22:27 +0000 (UTC) (envelope-from mikej@rogers.com) Received: (qmail 19559 invoked from network); 8 Dec 2008 22:22:26 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Received:Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:Importance; b=b4VtxGB8X6vO2VortnoNE6FWE+LKrOetW1HdSBsSb+dGRA2JTEsA1buLZ4WL82BM6bA2aQJf3scixkm34u47l8urg6hitUTk35NTcbIj9mFuxXfgxoP2LGrSPpj5zD08lvrSXQm4+IyWjtAXmmyHfzElrqxGktY3ZF6sqhxt3NY= ; Received: from unknown (HELO wettoast.dyndns.org) (mikej@99.227.98.203 with login) by smtp130.rog.mail.re2.yahoo.com with SMTP; 8 Dec 2008 22:22:26 -0000 X-YMail-OSG: QlZUFzQVM1l4BbptE1V3h.tkO..JgwHY92GGaDQcB5v2otKW3ltVcIaiQyfsx8Ng9w-- X-Yahoo-Newman-Property: ymail-3 Received: from 38.99.187.34 (SquirrelMail authenticated user mikej) by wettoast.dyndns.org with HTTP; Mon, 8 Dec 2008 17:22:32 -0500 (EST) Message-ID: <4fe0419b44a3a4c4a28b1e60fbb3a3c8.squirrel@wettoast.dyndns.org> In-Reply-To: <493D9BC6.8050902@delphij.net> References: <4935069A.8060209@ec-marseille.fr> <49357BD0.4000008@delphij.net> <4935944A.9090509@ec-marseille.fr> <4935C453.8070301@delphij.net> <4935D67E.4070204@delphij.net> <4936F8C4.6090006@ec-marseille.fr> <49399FA6.3060108@delphij.net> <493CE8F7.5010204@yandex-team.ru> <3a6fb7145a0a6c8af136ea1a0824e5ed.squirrel@wettoast.dyndns.org> <493D9BC6.8050902@delphij.net> Date: Mon, 8 Dec 2008 17:22:32 -0500 (EST) From: "Mike Jakubik" To: d@delphij.net User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-stable@freebsd.org, slayer@yandex-team.ru Subject: Re: RELENG_7_1: bce driver change generating too much interrupts ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Dec 2008 22:22:27 -0000 On Mon, December 8, 2008 5:12 pm, Xin LI wrote: > Which version are you currently using? My previous commit only fixes > the excessive interrupt issue, I think this could be a different > problem, I'm taking a look at the code to see if I can have something > for you. I was running on the version just prior to the latest interrupt commit. I have now updated to the one with the interrupt fix. Will let you know if things change. Thank You. From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 22:40:50 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A616B106567C for ; Mon, 8 Dec 2008 22:40:50 +0000 (UTC) (envelope-from ubm.freebsd@googlemail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by mx1.freebsd.org (Postfix) with ESMTP id 3436E8FC2B for ; Mon, 8 Dec 2008 22:40:49 +0000 (UTC) (envelope-from ubm.freebsd@googlemail.com) Received: by fg-out-1718.google.com with SMTP id l26so1594327fgb.35 for ; Mon, 08 Dec 2008 14:40:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:date:to:subject:message-id :x-mailer:mime-version:content-type:content-transfer-encoding:from; bh=sBVFJuKUyN5605x32rrhMciaixhdTg9PbRI19TSXw/A=; b=jPr61/UBUnfqjrP3a/poiERIyDqwG2cg77KNvqdouwccfcllizUHQ8KN0YULOOe64X MaATAxgAb2b7f9P6k6cPaZT4U3E4xlRVSV+eTxxqlFRJsZ4k33e+IajTKzS2hjgCc4fy CChu1ViVyMkHOVWFrd/4qqWHHTYjvVdWCz11s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:to:subject:message-id:x-mailer:mime-version:content-type :content-transfer-encoding:from; b=HSuBS0XMjVlkYGQ0vS518vNFnpYR9o+6VxPPcXa2VCwN8ZEZmfHqKpNyeeMcrQogb4 RQ8YLPha3YdFcMen8wHDKNU1yp1fL5FhOE1YavK3nrr0+vPI5DhjcGWjJAi7ZzDsBDAY fIY7w8tdf7oDMYroB7Sd+ET6sOV0+zS9ZlLVk= Received: by 10.181.60.13 with SMTP id n13mr1388736bkk.39.1228774597233; Mon, 08 Dec 2008 14:16:37 -0800 (PST) Received: from ubm.mine.nu (e181020103.adsl.alicedsl.de [85.181.20.103]) by mx.google.com with ESMTPS id d13sm16070410fka.5.2008.12.08.14.16.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 08 Dec 2008 14:16:36 -0800 (PST) Date: Mon, 8 Dec 2008 23:16:33 +0100 To: freebsd-stable@freebsd.org Message-Id: <20081208231633.89943a49.ubm.freebsd@gmail.com> X-Mailer: Sylpheed 2.5.0 (GTK+ 2.12.10; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit From: Marc UBM Bocklet Subject: Promise TX4302 working with -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, 08 Dec 2008 22:40:50 -0000 Hiho! :-) I'm planning to buy a Promise TX4302. The idea is to just plug in some disks via esata and then put zfs on them. Anybody got some experience with the TX4302? Googling didn't really turn up much, so I guess the controller "just works"? :-) Greetings, Marc From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 00:32:47 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 75BC41065675 for ; Tue, 9 Dec 2008 00:32:47 +0000 (UTC) (envelope-from bf2006a@yahoo.com) Received: from web39103.mail.mud.yahoo.com (web39103.mail.mud.yahoo.com [209.191.86.254]) by mx1.freebsd.org (Postfix) with SMTP id 1E9E48FC20 for ; Tue, 9 Dec 2008 00:32:46 +0000 (UTC) (envelope-from bf2006a@yahoo.com) Received: (qmail 82679 invoked by uid 60001); 9 Dec 2008 00:06:06 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=r212UdkmrRs5j85EsdeiYzq/C1B/nPk3jYMxK5PPL1xrRf7o0s/WVn/7qj6I0gk69HFt2ZCgRB8/HepOZRrfhfu+17m8tQehjaadfgzfHLHzQbo0uFEJ/9siBEbjQXQ8sQdN5081gSJCS0FVqzkN3RTQQDwjUUNol0dcc8Uy7hU=; X-YMail-OSG: ZQ3qiVYVM1khkx2.GyMlEqwuVJ5MVNXsJb_5uOMlbt1NFhaJIRu422pHe08YahU4M_Z4sxQoGOfaep8nQSanrKQKsrM1rOsBN.SnkJ5scJkXYqV6DZ9ydy_P1rmpsLjamhgtQcq7.EgASEt4XNlTtvNGEXdBCSr5eKLHanvSdoug68Lihz.fzxjpu4Ph1m8Ll6wGA6mm1olrh9I- Received: from [212.112.242.89] by web39103.mail.mud.yahoo.com via HTTP; Mon, 08 Dec 2008 16:06:06 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Mon, 8 Dec 2008 16:06:06 -0800 (PST) From: bf To: freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <382641.82375.qm@web39103.mail.mud.yahoo.com> Cc: Subject: Re: visibility of release process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bf2006a@yahoo.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 00:32:47 -0000 I'd also appreciate a little more frequent updating of the release schedule, maybe with some terse "we're waiting on this ... " notes, like there were for some past releases. I'd guess the amount of time involved in doing so would be modest. > * subversion. Without checking out the whole repository, it is a > little hard to use this as a news source and emails to the commit list > still look more like cvs than svn so it is a bit hard to see which > branch commits are going to. [3] Other than the comments that have already been made about the subject and the body of the messages, what's the matter with the other svn-src-stable-* or other svn-src-* mailing lists, some of which will focus more closely on those commits affecting the release(s)? Or, as someone suggested recently on one of the lists, something like: svn log -v -r '{2008-2-27}:HEAD' svn://svn.freebsd.org/base/stable/7/ Regards, b. From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 02:18:18 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DEBB106564A for ; Tue, 9 Dec 2008 02:18:18 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id 111FA8FC19 for ; Tue, 9 Dec 2008 02:18:18 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 437828C065; Mon, 8 Dec 2008 19:58:32 -0600 (CST) Date: Mon, 8 Dec 2008 19:58:32 -0600 To: Aristedes Maniatis Message-ID: <20081209015832.GA25363@soaustin.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) From: linimon@lonesome.com (Mark Linimon) Cc: freebsd-stable Stable Subject: Re: visibility of release process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Dec 2008 02:18:18 -0000 On Mon, Dec 08, 2008 at 08:57:37PM +1100, Aristedes Maniatis wrote: > 3. Improvements to the bug tracker. Personally I'd love to see > something like Jira used [4] with all the sophistication of workflow, > release notes, voting for bugs, etc, etc. I have some notes for some prototyping ideas, but I've been involved in package building issues more than bugbusting issues lately. I think it's time to task-switch ... mcl From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 08:35:09 2008 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 8E408106564A for ; Tue, 9 Dec 2008 08:35:09 +0000 (UTC) (envelope-from tom@samplonius.org) Received: from ly.sdf.com (ly.sdf.com [216.113.193.83]) by mx1.freebsd.org (Postfix) with ESMTP id 55CE78FC17 for ; Tue, 9 Dec 2008 08:35:09 +0000 (UTC) (envelope-from tom@samplonius.org) Received: from localhost (localhost [127.0.0.1]) by ly.sdf.com (Postfix) with ESMTP id C79B937C002; Mon, 8 Dec 2008 23:58:04 -0800 (PST) X-Virus-Scanned: amavisd-new at X-Spam-Score: -4.052 X-Spam-Level: X-Spam-Status: No, score=-4.052 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, AWL=0.347, BAYES_00=-2.599] Received: from ly.sdf.com ([127.0.0.1]) by localhost (ly.sdf.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KdokKYKPfSgf; Mon, 8 Dec 2008 23:58:01 -0800 (PST) Received: from ly.sdf.com (ly.sdf.com [216.113.193.83]) by ly.sdf.com (Postfix) with ESMTP id 106BE37C001; Mon, 8 Dec 2008 23:58:01 -0800 (PST) Date: Mon, 8 Dec 2008 23:58:00 -0800 (PST) From: Tom Samplonius To: bseklecki@collaborativefusion.com Message-ID: <11397385.9861228809480949.JavaMail.root@ly.sdf.com> In-Reply-To: <1228746983.2805.567.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [216.113.193.90] Cc: Peter Jeremy , stable@freebsd.org, eugen@kuzbass.ru, Pete French , Marian Hettwer Subject: Re: lagg(4) and failover X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Dec 2008 08:35:09 -0000 ----- "Brian A. Seklecki" wrote: > On Sun, 2008-12-07 at 08:03 +1100, Peter Jeremy wrote: > > On 2008-Dec-05 07:34:21 -0500, "Brian A. Seklecki" > > wrote: > > >Well ... name a price for the development; HA L1/L2 is a feature > the > > >community would gladly sponsor the development of. > > > > net/ifstated covers at least some of this. > > I was thinking something like a heartbeat protocol could work well > w/o > LACP hacking on mid-range switches. > > I think that's how Dell does it with the RHEL crap for Broadcom. > > Send multicast packets on both an active/standby link. If either > node > discontinues to see the others packets, some admin-configurable logic > promotes (Metric/Bias/Weighting). I don't know if that is such a great idea, as that would only test the switch that you are connected to. The Linux bonding driver supports probing the default gateway. Now, it uses ARP for this (probably because the ARP who-has code is also in the kernel and easily accessible), which also not so great, as a ARP who-has is a broadcast. So if you have lots of servers on the LAN using the bonding driver, you get a lot of broadcast traffic. ICMP echo-request would be a better approach, but my take on this, is that the echo-request/reply handling code would have to be written, so this hasn't been done yet. But ultimately, gateway probing is the best, as not only does it verify the directly connected switch, but also that you can get from that switch to the outside world. lagg is ultimately a problem as a high-availability solution since most switches do not support multi-switch 802.3ad yet, and most probably never well. So you are limited to a single switch. So 802.3ad is good only for aggregation, and not for high availability. So an active-standby system with probing is the way to go for high-availability. It seems that FreeBSD has most of the components of this already. ng_one2many was a possible base for this. > ~BAS > > -- > Brian A. Seklecki > Collaborative Fusion, Inc. Tom From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 09:02:12 2008 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 D26ED1065670 for ; Tue, 9 Dec 2008 09:02:12 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail14.syd.optusnet.com.au (mail14.syd.optusnet.com.au [211.29.132.195]) by mx1.freebsd.org (Postfix) with ESMTP id 663808FC14 for ; Tue, 9 Dec 2008 09:02:12 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail14.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id mB99294S019430 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Dec 2008 20:02:10 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id mB9928tS084693; Tue, 9 Dec 2008 20:02:08 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id mB992803084692; Tue, 9 Dec 2008 20:02:08 +1100 (EST) (envelope-from peter) Date: Tue, 9 Dec 2008 20:02:08 +1100 From: Peter Jeremy To: Tom Samplonius Message-ID: <20081209090208.GZ58682@server.vk2pj.dyndns.org> References: <1228746983.2805.567.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> <11397385.9861228809480949.JavaMail.root@ly.sdf.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FmwJltL8yKUx7YXQ" Content-Disposition: inline In-Reply-To: <11397385.9861228809480949.JavaMail.root@ly.sdf.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: stable@freebsd.org Subject: Re: lagg(4) and failover X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Dec 2008 09:02:12 -0000 --FmwJltL8yKUx7YXQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Please wrap your mail before 80 columns. On 2008-Dec-08 23:58:00 -0800, Tom Samplonius wrote: > The Linux bonding driver supports probing the default gateway. This is the same brokenness as Solaris IPMP. I agree that probing an external IP address (probably, but not necessarily a gateway) is the way to go but you need to be able to configure this. Otherwise you need to jump through hoops where the interfaces you are protecting is not the default route (or there are multiple independent groups of interfaces being protected). > Now, it uses ARP for this (probably because the ARP who-has code is >also in the kernel and easily accessible), which also not so great, I don't see that it's necessary to have the interface failover code in the kernel. The kernel needs hooks to allow a daemon to bind to the physical interfaces and control which one is active, but the actual code that decides how to determine which interface is active should be in userland. (Note that routing works this way). >switches do not support multi-switch 802.3ad yet, and most probably >never well. So you are limited to a single switch. So 802.3ad is >good only for aggregation, and not for high availability. Keep in mind that higher-end switches as well as stacked lower-end switches have a reasonable amount of internal redundancy so 802.3ad within one distinct components of one physical switch may be adequate for many purposes. Keep in mind that you'll still need multiple FreeBSD boxes to prevent them being a single point of failure. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --FmwJltL8yKUx7YXQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkk+NBAACgkQ/opHv/APuIcLcACePuDtU8gKvpbCJUibRp5Doa1k qlYAnRJIAeAwSRHVtexkseTrnwEYcE9b =o724 -----END PGP SIGNATURE----- --FmwJltL8yKUx7YXQ-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 09:34:59 2008 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 B9CA1106564A for ; Tue, 9 Dec 2008 09:34:59 +0000 (UTC) (envelope-from goran.lowkrantz@ismobile.com) Received: from mail.ismobile.com (mail.ismobile.com [62.119.44.68]) by mx1.freebsd.org (Postfix) with ESMTP id 6E27D8FC13 for ; Tue, 9 Dec 2008 09:34:59 +0000 (UTC) (envelope-from goran.lowkrantz@ismobile.com) Received: from mail.ismobile.com (localhost [127.0.0.1]) by mail.ismobile.com (Postfix) with ESMTP id 8976FDAF for ; Tue, 9 Dec 2008 10:18:05 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=ismobile.com; h=date:from :to:subject:message-id:mime-version:content-type: content-transfer-encoding; s=selector1; bh=tdSMTw/avt8Lb2cO1q94O 5zPs44=; b=B0DRcwlh1fbd4tKEHLB/kzo+jqu7wZlzDpmFI/Jf/MOyzcIcFmX0G 8yQRc5wcq6kA7IEtg4dYJwG+fYaxk6XAi8ZOr1FNrx6oQBn9DPa6+qZyCBS+6Yby T7uVZKFq4Up82aU3pIjiFRBvDPGWLEgkVaYIr6aTPVCvRc/FenrrUY= Received: from [172.16.2.124] (syn.hq.ismobile.com [172.16.2.124]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.ismobile.com (Postfix) with ESMTPSA id 10574DAE for ; Tue, 9 Dec 2008 10:18:04 +0100 (CET) Date: Tue, 09 Dec 2008 10:18:03 +0100 From: Goran Lowkrantz To: stable@freebsd.org Message-ID: X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: Regression in vr - not receiveing multicast X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Dec 2008 09:34:59 -0000 Hi, in July, vr had this problem and was fixed: but now it's back again! On a system with the following: 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Thu Oct 16 12:31:04 UTC 2008 I have to set all vr interfaces in promisc to get routing info. Using Quagga # pkg_info -Ix uagga quagga-0.99.10_3 Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software on an inner network using RIPv2 # ifmcstat -i vr0 vr0: inet xxx.xxx.xxx.xxx group 224.0.0.9 igmpv2 mcast-macaddr 01:00:5e:00:00:09 refcnt 1 group 224.0.0.1 mcast-macaddr 01:00:5e:00:00:01 refcnt 1 On the same box, we have some em devices also and they work without any=20 problems. Let me know what I can do to help fix this. /glz ................................................... the future isMobile Goran Lowkrantz System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Lule=E5, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ............................................... From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 09:37:43 2008 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 B2B86106564A for ; Tue, 9 Dec 2008 09:37:43 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 71EC18FC19 for ; Tue, 9 Dec 2008 09:37:43 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id 12DA1172D8; Tue, 9 Dec 2008 20:22:12 +1100 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.20.30.101] (60.218.233.220.exetel.com.au [220.233.218.60]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id BDCD41732D; Tue, 9 Dec 2008 20:21:59 +1100 (EST) Message-ID: <493E38B5.30608@modulus.org> Date: Tue, 09 Dec 2008 20:21:57 +1100 From: Andrew Snow User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Tom Samplonius References: <11397385.9861228809480949.JavaMail.root@ly.sdf.com> In-Reply-To: <11397385.9861228809480949.JavaMail.root@ly.sdf.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, Pete French , Peter Jeremy , eugen@kuzbass.ru, bseklecki@collaborativefusion.com, Marian Hettwer Subject: Re: lagg(4) and failover X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Dec 2008 09:37:43 -0000 > lagg is ultimately a problem as a high-availability solution since most switches do not support multi-switch 802.3ad yet, and most probably never well. So you are limited to a single switch. So 802.3ad is good only for aggregation, and not for high availability. What about using STP or RSTP instead of lagg? Which L2 managed switches like 3com and HP support. Then you could connect each of two NICs to a different switch, as well as connect the switches to each other. From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 09:56:27 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC8941065673 for ; Tue, 9 Dec 2008 09:56:27 +0000 (UTC) (envelope-from ari@ish.com.au) Received: from fish.ish.com.au (eth5921.nsw.adsl.internode.on.net [59.167.240.32]) by mx1.freebsd.org (Postfix) with ESMTP id 639D98FC17 for ; Tue, 9 Dec 2008 09:56:26 +0000 (UTC) (envelope-from ari@ish.com.au) Received: from ip-132.ish.com.au ([203.29.62.132]:62977) by fish.ish.com.au with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1L9zq1-0006oF-1a; Tue, 09 Dec 2008 21:29:09 +1100 Message-Id: From: Aristedes Maniatis To: Peter Jeremy In-Reply-To: <20081208182112.GW58682@server.vk2pj.dyndns.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Tue, 9 Dec 2008 20:56:14 +1100 References: <20081208182112.GW58682@server.vk2pj.dyndns.org> X-Mailer: Apple Mail (2.929.2) Cc: freebsd-stable Stable Subject: Re: visibility of release process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Dec 2008 09:56:27 -0000 On 09/12/2008, at 5:21 AM, Peter Jeremy wrote: > What do you mean as "news source"? Commits are inherently low level > and it's difficult to see how a commit could be massaged into some > sort of press release without a fair amount of meta information in > the commit log. Well, I use this as a way of tracking activity sometimes: http://news.gmane.org/gmane.os.freebsd.devel.cvs And indeed, I notice now it has been improved recently. The commit messages now include full paths and diffs. Very helpful. >> * the bug tracker. Let's just say that FreeBSD's bug tracker is >> fairly >> primitive and 'target release' is not an option. > > Agreed. This is an issue that comes up regularly but I don't believe > a solution has been identified. I suspect one of the requirements > would be that it be FOSS I don't understand why it should be necessarily FOSS. I believe the best solution should be chosen by those people who would use it most: the core developers. I know for a fact that many non-free providers would give FreeBSD a free perpetual license for the goodwill it would create, as for instance Atlassian do for Jira at Apache and other open source projects. Is it also a requirement that FreeBSD only be hosted on servers with FOSS bios? What about P4? My personal wish list would be: * rich search interface * workflow (eg. if a critical task remains open for more than x days without attention, it is automatically escalated) * svn integration (so that commit messages reference the task and vice versa) * release notes and roadmap * ease of integration with multiple front end tools, so developers can comment on issues from the command line or their iphone >> I've had a look at several of the fisheye sites and am not sure what > it would buy the Project, other than some pretty graphs. I don't see > how this is any more "friendly" than svn.freebsd.org. Sure, but show me how to go to http://svn.freebsd.org/viewvc/base/ and see commit log per branch or any other way to see what is going on in a branch. Fisheye gives you that in a really clear way and it costs nothing to add another option for users. Cheers Ari Maniatis --------------------------> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 09:59:27 2008 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 1749D1065673 for ; Tue, 9 Dec 2008 09:59:27 +0000 (UTC) (envelope-from glz@hidden-powers.com) Received: from mail.hidden-powers.com (mail.hidden-powers.com [213.242.135.162]) by mx1.freebsd.org (Postfix) with ESMTP id BD0348FC14 for ; Tue, 9 Dec 2008 09:59:26 +0000 (UTC) (envelope-from glz@hidden-powers.com) Received: from mail.hidden-powers.com (localhost [127.0.0.1]) by dkim.hidden-powers.com (Postfix) with ESMTP id DAC6C6D5E4 for ; Tue, 9 Dec 2008 10:40:19 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hidden-powers.com; h=date :from:to:subject:message-id:mime-version:content-type: content-transfer-encoding; s=selector1; bh=sC9SYB6A+r6/WK/Pchgq8 6OyGIw=; b=M2hQA4c6PRjnOSC1gv8r2tyleexwonQ/me8DKnbfDJhLbwJ5FgT4Z FvdViSx62qvZEbPWkTepgGa6HxuCusvkcC+c/5ftYup4ApwAok8W9TYPQ0eAEIoB fZbO0ykmaF/A5hTtQrlePB2oJPiPt99J27ET0OUBbtaD98RPABYHXc= Received: from [172.16.2.124] (gw01.ismobile.com [212.73.186.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.hidden-powers.com (Postfix) with ESMTPSA id 9B05D6D5E2 for ; Tue, 9 Dec 2008 10:40:19 +0100 (CET) Date: Tue, 09 Dec 2008 10:40:17 +0100 From: Goran Lowkrantz To: stable@freebsd.org Message-ID: X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; FORMAT=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: Regression in vr - not receiveing multicast X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Dec 2008 09:59:27 -0000 Hi, in July, vr had this problem and was fixed: but now it's back again! On a system with the following: 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Thu Oct 16 12:31:04 UTC 2008 I have to set all vr interfaces in promisc to get routing info. Using Quagga # pkg_info -Ix uagga quagga-0.99.10_3 Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software on an inner network using RIPv2 # ifmcstat -i vr0 vr0: inet xxx.xxx.xxx.xxx group 224.0.0.9 igmpv2 mcast-macaddr 01:00:5e:00:00:09 refcnt 1 group 224.0.0.1 mcast-macaddr 01:00:5e:00:00:01 refcnt 1 On the same box, we have some em devices also and they work without any=20 problems. Let me know what I can do to help fix this. /glz ................................................... the future isMobile Goran Lowkrantz System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Lule=E5, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ............................................... --- "There is hopeful symbolism in the fact that flags do not wave in a = vacuum." -- Arthur C. Clarke From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 10:17:12 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18E251065675 for ; Tue, 9 Dec 2008 10:17:12 +0000 (UTC) (envelope-from ruben@verweg.com) Received: from erg.verweg.com (unknown [IPv6:2001:980:fff:96::c0a8:181]) by mx1.freebsd.org (Postfix) with ESMTP id 97F488FC13 for ; Tue, 9 Dec 2008 10:17:11 +0000 (UTC) (envelope-from ruben@verweg.com) Received: from [IPv6:::1] (chimp.ripe.net [193.0.1.199]) (authenticated bits=0) by erg.verweg.com (8.14.3/8.14.3) with ESMTP id mB9AGvG4070072 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 9 Dec 2008 10:17:03 GMT (envelope-from ruben@verweg.com) X-Authentication-Warning: erg.verweg.com: Host chimp.ripe.net [193.0.1.199] claimed to be [IPv6:::1] Message-Id: <02D7BFFB-7B09-42DB-BBDF-F83AFDE45BD3@verweg.com> From: Ruben van Staveren To: Aristedes Maniatis In-Reply-To: Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-64--744969109" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Tue, 9 Dec 2008 11:16:57 +0100 References: <20081208182112.GW58682@server.vk2pj.dyndns.org> X-Pgp-Agent: GPGMail d52 (v52, Leopard) X-Mailer: Apple Mail (2.929.2) X-Virus-Scanned: ClamAV 0.94.2/8734/Tue Dec 9 07:12:11 2008 on erg.verweg.com X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (erg.verweg.com [192.168.1.129]); Tue, 09 Dec 2008 10:17:03 +0000 (UTC) Cc: Peter Jeremy , freebsd-stable Stable Subject: Re: visibility of release process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Dec 2008 10:17:12 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-64--744969109 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit On 9 Dec 2008, at 10:56, Aristedes Maniatis wrote: > Sure, but show me how to go to http://svn.freebsd.org/viewvc/base/ > and see commit log per branch or any other way to see what is going > on in a branch. Fisheye gives you that in a really clear way and it > costs nothing to add another option for users. Though experimental, I'm greatly enjoying http://www.secnetix.de/olli/FreeBSD/svnews/?p=/stable/7 Maybe it is worth considering to team up and bring this under the freebsd.org umbrella ? Regards, Ruben --Apple-Mail-64--744969109 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (Darwin) iD8DBQFJPkWaZ88+mcQxRw0RAhOSAJ4raTivjZ1P3MXIqvasFU+K9mZ44wCdF++V /bF6SYRTiCj1NmDu3lpLfZE= =J2jN -----END PGP SIGNATURE----- --Apple-Mail-64--744969109-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 11:53:08 2008 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 BD3B71065670 for ; Tue, 9 Dec 2008 11:53:08 +0000 (UTC) (envelope-from glz@hidden-powers.com) Received: from mail.hidden-powers.com (mail.hidden-powers.com [213.242.135.162]) by mx1.freebsd.org (Postfix) with ESMTP id 6C2FC8FC21 for ; Tue, 9 Dec 2008 11:53:08 +0000 (UTC) (envelope-from glz@hidden-powers.com) Received: from mail.hidden-powers.com (localhost [127.0.0.1]) by dkim.hidden-powers.com (Postfix) with ESMTP id CB2066D5DF; Tue, 9 Dec 2008 12:53:06 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hidden-powers.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s= selector1; bh=7dbp6oE3Z2w5o+PJXgYZrI5Fhos=; b=HPVyQKefWop28hWyxT +9LNj/+I9bxA+yeGA618UXtzAZlL+dwGVLryY2A1QIBDOSyIH7tz5i4kj4xXywO6 WPhFC1v2IsfdVhLzcb8xDEX4HmUb+018QCQ3vzvIvnujuR1JrIiecOudQWnLXs7t 8Gr3JY7aW/Jl5W/dVtKMz1s5Q= Received: from [172.16.2.124] (gw01.ismobile.com [212.73.186.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.hidden-powers.com (Postfix) with ESMTPSA id 037666D4DE; Tue, 9 Dec 2008 12:53:05 +0100 (CET) Date: Tue, 09 Dec 2008 12:53:05 +0100 From: Goran Lowkrantz To: pyunyh@gmail.com Message-ID: <80D07D8C17DAC73D69DCDC9A@[172.16.2.124]> In-Reply-To: <20081209114723.GE33723@cdnetworks.co.kr> References: <20081209114723.GE33723@cdnetworks.co.kr> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: stable@freebsd.org Subject: Re: Regression in vr - not receiveing multicast X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Dec 2008 11:53:08 -0000 --On December 9, 2008 20:47:23 +0900 Pyun YongHyeon wrote: > On Tue, Dec 09, 2008 at 10:40:17AM +0100, Goran Lowkrantz wrote: > > Hi, > > > > in July, vr had this problem and was fixed: > > > > > > > > but now it's back again! > > > > There was just one bug fix since then and I guess the fix is not > related with your issue. > > > On a system with the following: > > 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Thu Oct 16 12:31:04 UTC 2008 > > > > I have to set all vr interfaces in promisc to get routing info. > > > > Using Quagga > > # pkg_info -Ix uagga > > quagga-0.99.10_3 Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route > software > > > on an inner network using RIPv2 > > # ifmcstat -i vr0 > > vr0: > > inet xxx.xxx.xxx.xxx > > group 224.0.0.9 > > igmpv2 > > mcast-macaddr 01:00:5e:00:00:09 refcnt 1 > > group 224.0.0.1 > > mcast-macaddr 01:00:5e:00:00:01 refcnt 1 > > > > > > On the same box, we have some em devices also and they work without > any > problems. > > > > There is fundamental differences between em(4) and vr(4). The > vr(4) for VT6105M takes advantage of perfect multicast filtering > feature which is not present on all em(4) interface. Perfect > multicast filtering can reduce unwanted multicast traffics such > that it could save a lot of CPU cycles. The downside is that vr(4) > cannot accept multicast frames for a multicast group without > joining the multicast group first. > For multicast routing purpose I guess 'options MROUTING' kernel > option should be enabled to accept all multicast frames. > Does your kernel have that option? No it has not. I will create such a beast and return with stories. /glz From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 12:08:57 2008 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 ED2FB1065670 for ; Tue, 9 Dec 2008 12:08:57 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.228]) by mx1.freebsd.org (Postfix) with ESMTP id B6C138FC17 for ; Tue, 9 Dec 2008 12:08:57 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id f9so1319129rvb.4 for ; Tue, 09 Dec 2008 04:08:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=Hte1yJOQQjLt2qk0RVYq10ZU2RRzOkZcjvspLTWBWgg=; b=l/ipDpNuZZjtyJICscns6cTc20XB9LJZISu5PmCZB02L8QlPu0sVSQHT8XLFYXD4+y nGech8EvgCiY5qyK4K/8Dbz6wb2jEj39k8vYqPctBdrGRKFVJRZmTHa/CWmRH3MBnzkL KxqzoxFZMxHTlAD8lJnxuEciwzZLzhpCoCA6c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=fj7Oa9WJ7z9zzRslMsJ/ZG3Vs82MauB3JbiKMMnxFUEKaEQoMybopPLcpj5HZdTW0k mqB6XsFdQaXq4/IrSU/AXCOvJoRA6eNHXNPqXhtkp1KmYJ/mqqcUkDY1ZHxch64DwxQh RUP0//9aifpcSerdymPqfXzjBqYziagTVUkxM= Received: by 10.141.67.21 with SMTP id u21mr12103rvk.123.1228823254222; Tue, 09 Dec 2008 03:47:34 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id k37sm9818803rvb.1.2008.12.09.03.47.31 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 09 Dec 2008 03:47:33 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id mB9BlPK7035800 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Dec 2008 20:47:25 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id mB9BlNPh035799; Tue, 9 Dec 2008 20:47:23 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 9 Dec 2008 20:47:23 +0900 From: Pyun YongHyeon To: Goran Lowkrantz Message-ID: <20081209114723.GE33723@cdnetworks.co.kr> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: Regression in vr - not receiveing multicast X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 12:08:58 -0000 On Tue, Dec 09, 2008 at 10:40:17AM +0100, Goran Lowkrantz wrote: > Hi, > > in July, vr had this problem and was fixed: > > > > but now it's back again! > There was just one bug fix since then and I guess the fix is not related with your issue. > On a system with the following: > 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Thu Oct 16 12:31:04 UTC 2008 > > I have to set all vr interfaces in promisc to get routing info. > > Using Quagga > # pkg_info -Ix uagga > quagga-0.99.10_3 Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software > > on an inner network using RIPv2 > # ifmcstat -i vr0 > vr0: > inet xxx.xxx.xxx.xxx > group 224.0.0.9 > igmpv2 > mcast-macaddr 01:00:5e:00:00:09 refcnt 1 > group 224.0.0.1 > mcast-macaddr 01:00:5e:00:00:01 refcnt 1 > > > On the same box, we have some em devices also and they work without any > problems. > There is fundamental differences between em(4) and vr(4). The vr(4) for VT6105M takes advantage of perfect multicast filtering feature which is not present on all em(4) interface. Perfect multicast filtering can reduce unwanted multicast traffics such that it could save a lot of CPU cycles. The downside is that vr(4) cannot accept multicast frames for a multicast group without joining the multicast group first. For multicast routing purpose I guess 'options MROUTING' kernel option should be enabled to accept all multicast frames. Does your kernel have that option? > Let me know what I can do to help fix this. > > /glz > -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 13:57:10 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4200B106567C for ; Tue, 9 Dec 2008 13:57:10 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-gx0-f19.google.com (mail-gx0-f19.google.com [209.85.217.19]) by mx1.freebsd.org (Postfix) with ESMTP id E2DDC8FC19 for ; Tue, 9 Dec 2008 13:57:09 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by gxk12 with SMTP id 12so1561978gxk.19 for ; Tue, 09 Dec 2008 05:57:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=BY/SoZplUP+5delFx/jwuQJZ5fzxwXQtKdB/M24NAI8=; b=A/74/Ft83cWtDFKErjaeL7e2hcGmXTozkJ5zwSs69IJp26mWyPksfaYf2+wlfFe8Zr eY5aeW/5Rui+1uMamARJFtBHOWUI91w8XFqsN88y2hpwYoBfIsKK5X8szoh/2kXUUd0b 0jUlkX/2huJG3KCo3GodV8lXWGF+fS16904Kk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=E16Ei+xk3zGv1fhaIX0PBc+VH3hhPCpOaQPKyFmifAqvNrXjkxoQCaFOYAwRDpj6ip uU1nkB3SRIrWYC/vpfpGWWA12b15tfnN3CceneRPA2igOyZsves28EpdsSiaKKNbdRuN CU1HhbeqA/8zXLvWarzw7wo/l9gG1bIyj3hTE= Received: by 10.231.16.74 with SMTP id n10mr1498iba.28.1228830829288; Tue, 09 Dec 2008 05:53:49 -0800 (PST) Received: by 10.231.16.194 with HTTP; Tue, 9 Dec 2008 05:53:49 -0800 (PST) Message-ID: <3a142e750812090553l564bff84pe1f02cd1b03090ff@mail.gmail.com> Date: Tue, 9 Dec 2008 14:53:49 +0100 From: "Paul B. Mahol" To: "Bruce M. Simpson" In-Reply-To: <493CEE90.7050104@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> <200812041747.09040.gnemmi@gmail.com> <4938FE44.9090608@FreeBSD.org> <4939133E.2000701@FreeBSD.org> <493CEE90.7050104@FreeBSD.org> Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: ext2fuse: user-space ext2 implementation X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 13:57:10 -0000 On 12/8/08, Bruce M. Simpson wrote: > I have rolled a port for ext2fuse: > http://people.freebsd.org/~bms/dump/fusefs-ext2fs.tar Ignoring fact that is buggy, slooow and port doesnt have any cache implemented and port leaves files behind in share/doc/ext2fuse when package deleted it looks fine. -- Paul From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 15:34:49 2008 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 4863D1065670 for ; Tue, 9 Dec 2008 15:34:49 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from collaborativefusion.com (mx01.pub.collaborativefusion.com [206.210.89.201]) by mx1.freebsd.org (Postfix) with ESMTP id CF1038FC12 for ; Tue, 9 Dec 2008 15:34:48 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from Internal Mail-Server by mx01 (envelope-from bseklecki@collaborativefusion.com) with SMTP; 9 Dec 2008 10:34:47 -0500 From: "Brian A. Seklecki" To: Tom Samplonius In-Reply-To: <11397385.9861228809480949.JavaMail.root@ly.sdf.com> References: <11397385.9861228809480949.JavaMail.root@ly.sdf.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-z5+1OIZC6ydPVOR0CeLk" Organization: Collaborative Fusion, Inc. Date: Tue, 09 Dec 2008 10:34:47 -0500 Message-Id: <1228836887.2805.697.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 (2.22.3.1-1.fc9) Cc: Peter Jeremy , stable@freebsd.org, eugen@kuzbass.ru, Pete French , Marian Hettwer Subject: Re: lagg(4) and failover X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bseklecki@collaborativefusion.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 15:34:49 -0000 --=-z5+1OIZC6ydPVOR0CeLk Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2008-12-08 at 23:58 -0800, Tom Samplonius wrote: > I don't know if that is such a great idea, as that would only test > the switch that you are connected to. Heatbeats (STP,CARP) and active sanity checking (Nagios, ifwatchd(8)) are the two main options. Results may vary in every system/network device permutation. At least we're talking about it -- even if just for the sake of the archives -- that wasn't happening before. --=20 Brian A. Seklecki Collaborative Fusion, Inc. --=-z5+1OIZC6ydPVOR0CeLk Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAkk+kBcACgkQCne6BNDQ+R+omQCdFEtxfTYFkQAoD1FDzQ40InEA SkkAn3R6Ea2zZvDxCaTBOkoUzxwe5ABM =Bc4r -----END PGP SIGNATURE----- --=-z5+1OIZC6ydPVOR0CeLk-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 16:55:39 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00684106564A for ; Tue, 9 Dec 2008 16:55:39 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id BE71A8FC12 for ; Tue, 9 Dec 2008 16:55:38 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id mB9GtbwP052201 for ; Tue, 9 Dec 2008 11:55:37 -0500 (EST) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id mB9GtapH048081 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 9 Dec 2008 11:55:36 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200812091655.mB9GtapH048081@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 09 Dec 2008 11:55:35 -0500 To: freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <200811260219.mAQ2JFEL065881@lava.sentex.ca> References: <200811260219.mAQ2JFEL065881@lava.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Subject: Re: sio vs uart vs ucomm problems / differences X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Dec 2008 16:55:39 -0000 At 09:19 PM 11/25/2008, Mike Tancsa wrote: >We are in the process of migrating one of our embedded apps to use >uart by default instead of sio in RELENG_7 in prep for the day when >sio eventually disappears. Unfortunately, the application doesnt >want to work with uart >with puc backed devices, but still works with sio. Stranger still, the app For the archives, We were sort of able to figure it out in http://lists.freebsd.org/pipermail/freebsd-current/2008-December/001052.html and http://lists.freebsd.org/pipermail/freebsd-usb/2008-December/005817.html ---Mike From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 17:27:42 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FF281065676 for ; Tue, 9 Dec 2008 17:27:42 +0000 (UTC) (envelope-from fernan.aguero@gmail.com) Received: from mail-qy0-f18.google.com (mail-qy0-f18.google.com [209.85.221.18]) by mx1.freebsd.org (Postfix) with ESMTP id 331728FC1B for ; Tue, 9 Dec 2008 17:27:41 +0000 (UTC) (envelope-from fernan.aguero@gmail.com) Received: by qyk11 with SMTP id 11so182709qyk.19 for ; Tue, 09 Dec 2008 09:27:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=kFued+pZrm4PfO+9pR5paxHr7XgXv3A5gzmsLFW1M9Y=; b=qd62hleZjttLIA+eeV2DO+D0nupaByQlCp8XEXapxSFll0lwMWBzCa5T8WLqJrKJnF +9Fwh+9k052viGJ0PBy/vQ/7AsV7x/bR+LA+Sxn7n1lmAAOv+D/EbhQG4L03omuXB/xO 3ySXVKzNTm8HC6iiA77phYPzMDtoUfQs61kAs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=eDmrMtGbLTumLDWjxEgfP+GtW3KiiZi+lKHqpsfinASloRXO8p9GxpNCjq5tmoO7Ak 6flVZyjPWYVSEXGQYzQVxQNYwz4wXLG/aSD7B0+9bWSfA/2m7U/0HVq/8cFlI3xQeFfY ryzabrDK15CQm6nQfD25XhERFwR4nV9ZXkW8A= Received: by 10.214.12.6 with SMTP id 6mr520446qal.359.1228843661275; Tue, 09 Dec 2008 09:27:41 -0800 (PST) Received: by 10.214.150.15 with HTTP; Tue, 9 Dec 2008 09:27:41 -0800 (PST) Message-ID: <520894aa0812090927h4034e7ecnff5d05d2d6138554@mail.gmail.com> Date: Tue, 9 Dec 2008 15:27:41 -0200 From: "Fernan Aguero" To: freebsd-stable@freebsd.org, re@freebsd.org, doc@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_52492_14039423.1228843661256" Cc: Subject: update release schedule information? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Dec 2008 17:27:42 -0000 ------=_Part_52492_14039423.1228843661256 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, the release schedule information available in http://www.freebsd.org/releases/7.1R/schedule.html is outdated. You probably already know about this ... and I also know 7.1-RELEASE is delayed, but the schedule page does not provide any useful information on what's going to happen next. BETA2 has already passed but it has not been mentioned in this document. The front page for the project (www.freebsd.org) links to ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/ISO-IMAGES/7.1/ with the text 'Upcoming Release 7.1 - BETA2' (but BETA2 is not mentioned in schedule.html) If you navigate to the FTP site using that link now, you'll find that the images for the RC1 are already available (Dec 7th). But the 'actual' dates for the RC1 builds are missing from schedule.html. I'm not familiar with the docproj procedures, but have tried to help by editing the release.ent and schedule.sgml files (patches attached), which looked as the obvious candidates to me. If someone can check them, complete the missing dates in schedule.sgml, and commit the changes, that would be great! Cheers, -- fernan ------=_Part_52492_14039423.1228843661256 Content-Type: text/x-patch; name=release.ent.diff Content-Transfer-Encoding: base64 X-Attachment-Id: f_foisjmg20 Content-Disposition: attachment; filename=release.ent.diff MzRjMzQKPCA8IUVOVElUWSBiZXRhcmVsLnZlcnMgJ0JFVEEyJz4KLS0tCj4gPCFFTlRJVFkgYmV0 YXJlbC52ZXJzICdSQzEnPgo= ------=_Part_52492_14039423.1228843661256 Content-Type: text/x-patch; name=schedule.sgml.diff Content-Transfer-Encoding: base64 X-Attachment-Id: f_foiskep52 Content-Disposition: attachment; filename=schedule.sgml.diff LS0tIHd3dy9lbi9yZWxlYXNlcy83LjFSL3NjaGVkdWxlLnNnbWwub3JpZwkyMDA4LTEyLTA5IDEz OjM0OjIyLjAwMDAwMDAwMCAtMDMwMAorKysgd3d3L2VuL3JlbGVhc2VzLzcuMVIvc2NoZWR1bGUu c2dtbAkyMDA4LTEyLTA5IDEzOjM4OjQ1LjAwMDAwMDAwMCAtMDMwMApAQCAtMTEwLDYgKzExMCwx MyBAQAogICAgICAgPHRkPkJlZ2luIEJFVEExIGJ1aWxkcy48L3RkPgogICAgIDwvdHI+CiAKKyAg ICA8dHI+CisgICAgICA8dGQ+PHR0PkJFVEEyPC90dD4gYnVpbGRzPC90ZD4KKyAgICAgIDx0ZD4t LTwvdGQ+CisgICAgICA8dGQ+LS08L3RkPgorICAgICAgPHRkPkJlZ2luIEJFVEEyIGJ1aWxkcy48 L3RkPgorICAgIDwvdHI+CisKIAogICAgIDx0cj4KICAgICAgIDx0ZD48dHQ+UkVMRU5HXzdfMTwv dHQ+IGJyYW5jaDwvdGQ+CkBAIC0xMjIsNyArMTI5LDcgQEAKICAgICA8dHI+CiAgICAgICA8dGQ+ PHR0PlJDMTwvdHQ+IGJ1aWxkczwvdGQ+CiAgICAgICA8dGQ+MTUmbmJzcDtTZXB0ZW1iZXImbmJz cDsyMDA4PC90ZD4KLSAgICAgIDx0ZD4tLTwvdGQ+CisgICAgICA8dGQ+NyZuYnNwO0RlY2VtYmVy Jm5ic3A7MjAwODwvdGQ+CiAgICAgICA8dGQ+QmVnaW4gUkMxIGJ1aWxkcy48L3RkPgogICAgIDwv dHI+CiAK ------=_Part_52492_14039423.1228843661256-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 17:50:36 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C93A91065679 for ; Tue, 9 Dec 2008 17:50:36 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id AD9CB8FC30 for ; Tue, 9 Dec 2008 17:50:36 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 1E16B1A3C3C; Tue, 9 Dec 2008 09:30:53 -0800 (PST) Date: Tue, 9 Dec 2008 09:30:53 -0800 From: Alfred Perlstein To: Jo Rhett Message-ID: <20081209173053.GZ27096@elvis.mu.org> References: <4912E462.4090608@icyb.net.ua> <491586B9.2020303@vwsoft.com> <4919851B.7050800@icyb.net.ua> <492FF127.807@icyb.net.ua> <31DE68A5-D3CB-4C33-86E6-515581B425E1@netconsonance.com> <7A8CC4E4-D59A-4841-8800-A3509C9DB68E@netconsonance.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7A8CC4E4-D59A-4841-8800-A3509C9DB68E@netconsonance.com> User-Agent: Mutt/1.4.2.3i Cc: "George V. Neville-Neil" , FreeBSD Stable Subject: Re: confirming bugs is bad behavior, etc. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Dec 2008 17:50:36 -0000 Jo, I'm trying to get FreeBSD to consider not supporting another "6.4" or "5.5" as both seems to have some of the problems you're describing due to a the next gen -stable being out for so long sucking away developer time. As a user, what do you think about this? I hate to force users to upgrade, but I also hate to potentially be falsly advertising "stability" when there might not be enough maintainers to keep that true. Thoughts? -Alfred * Jo Rhett [081201 12:28] wrote: > On Dec 1, 2008, at 11:59 AM, George V. Neville-Neil wrote: > >I have mostly stayed away from these threads because they've often > >devolved into unproductive finger pointing. > > > >Please leave the hyperbole out of your posts, or at least attempt to > >cut it back. People on these lists are working quite hard to solve > >problems for the whole of the FreeBSD community and your posts, such > >as this one, are not helping us to move forward. > > > My posts have always been directed at solving very real, operational > problems with using FreeBSD on server platforms, which is exactly the > stated goal for freebsd. I have always offered not only problems, but > resources to help test or evaluate the issues, and serious > considerations for ways to improve the process. > > Yes, you're right. Threads I start about real problems always devolve > into unproductive finger pointing. That would be the freebsd > developers attacking the reporter for identifying a real, operational > problem. Take a look at the posts of the FreeBSD developers, and view > for yourself the unprofessional attacks and personal insults hurled by > them at people who are simply trying to get real problems resolved. > > And yet, instead of asking your developers to stop violating the > posted rules of the mailing list, you are asking a bug reporter who > simply informed another bug reporter that their problem was both > widespread and not limited to USB devices to stop posting to the > list. Because god knows that "yes we saw it too and it's widely > reported" is bad behavior. Much worse that personal attacks which are > strictly against the list rules. > > Yes, I'm sure that the personal attacks really do help drive freebsd > development forward. Much more so than me bringing resources and > actually testing things does. > > Now that Core has clearly spoken their mind on this issue, by refusing > to ask freebsd developers to avoid violating the list charter and then > publicly calling out someone for just saying "yeah, it's a widely > reported problem" ... leaves any doubt that positive change is going > to happen here. > > Your request is accepted. I'm unsubscribing now. > > -- > Jo Rhett > Net Consonance : consonant endings by net philanthropy, open source > and other randomness > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- - Alfred Perlstein From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 18:52:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35F281065677 for ; Tue, 9 Dec 2008 18:52:43 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.bsdes.net (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.freebsd.org (Postfix) with ESMTP id 802878FC3A for ; Tue, 9 Dec 2008 18:52:39 +0000 (UTC) (envelope-from victor@bsdes.net) Received: by alf.bsdes.net (Postfix, from userid 1001) id 3EB07119CF7; Tue, 9 Dec 2008 19:52:37 +0100 (CET) Date: Tue, 9 Dec 2008 19:52:37 +0100 From: Victor Balada Diaz To: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Message-ID: <20081209185236.GA1320@alf.bsdes.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4.2.3i Cc: Subject: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 18:52:43 -0000 --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit Hello, I got various machines[1] at hetzner.de and I've been having problems with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've been trying to narrow the problem so someone more knowledgeable than me is able to fix it. This mail is an other attempt to ask a question with regards ATA code to see if this time i got something. For the ones that don't actually know what happened: With FreeBSD 7.0 -RELEASE for amd64 and default kernel the system shared re0 interrupt with OHCI and this caused re(4) to corrupt packets and create interrupt storms. Tried updating to 7.1 -BETA2 and still had some problems with it. I've opened the PR kern/128287[2] and Remko quickly answered with a workaround: that workaround was removing USB support from my kernel. I did it and re(4) wasn't sharing interrupts anylonger, and the interrupt storms were gone. Now sometime later the interface goes up and down from time to time, but less often. Also sometimes the machine losts the network interface but continues to work. I know it continues to work because some days later i can see that it tried to deliver the status reports but was unable to resolve the aliases hostnames. I can't ping the machine and i know the network is OK. If i reboot the machine everything is working again. When switched from 7.0 to 7.1 BETA2 i also found that under load after some hours the machine created interrupt storms on ATA disks. Digging at linux source code i've found that they do some special things for this chipset that i've been unable to find on our code. This is linux code for my chipset: 371 AHCI_HFLAGS (AHCI_HFLAG_IGN_SERR_INTERNAL | 372 AHCI_HFLAG_32BIT_ONLY | AHCI_HFLAG_NO_MSI | 373 AHCI_HFLAG_SECT255), File and the rest of the code in here[3]. As i saw AHCI_HFLAG_NO_MSI i tried doing the easiest thing i could think of, switching MSI and MSI-x off for the whole system, so i added to /boot/loader.conf this tunables: hw.pci.enable_msix="0" hw.pci.enable_msi="0" And then rebooted the machine. After various hours of doing almost nothing i've found that the machine answered ping but was unable to answer any request (eg, ssh, nagios nrpe, etc). The machine recovered itself after some minutes and when i was able to ssh into i saw the following in dmesg: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=1463123158 and a lot more errors like that. I didn't get this errors with MSI enabled. I see WRITE_DMA48 and in linux code i saw AHCI_HFLAG_32BIT_ONLY which is later used for DMA related things. Could someone who is more knowledgeable check if we're doing the right thing? I've attached verbose dmesg of a machine that's like this one with 7.1 -BETA2, MSI enabled and GENERIC kernel minus USB and firewrire. Also, please, could someone give me a hand on how could i continue debugging this interrupt issues? I'm a bit lost and digging code and posting each time i think i've found something is not going to go anywhere. I would also like to say that i've seen reports of this kind of problems on amd64 machines in the lists since various years ago, so i don't think this is just a problem with this BIOS/motherboard (MSI K9AG Neo2 Digital) on the lists Thanks in advance for any help. Regards. [1]: http://www.hetzner.de/hosting/produkte_rootserver/ds7000/ [2]: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/128287 [3]: http://fxr.watson.org/fxr/source/drivers/ata/ahci.c?v=linux-2.6#L369 -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg.verbose" Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-BETA2 #1: Wed Oct 22 13:19:14 CEST 2008 victor@foo.bar.com:/usr/obj/usr/src/sys/NOUSB Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff80c12000. Preloaded elf obj module "/boot/kernel/geom_mirror.ko" at 0xffffffff80c121a8. Preloaded elf obj module "/boot/kernel/accf_data.ko" at 0xffffffff80c12818. Preloaded elf obj module "/boot/kernel/accf_http.ko" at 0xffffffff80c12cc8. Preloaded elf obj module "/boot/kernel/k8temp.ko" at 0xffffffff80c13238. Preloaded elf obj module "/boot/kernel/geom_journal.ko" at 0xffffffff80c13720. Calibrating clock(s) ... i8254 clock: 1193242 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2999975813 Hz CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ (2999.98-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40f33 Stepping = 3 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1f Cores per package: 2 L1 2MB data TLB: 8 entries, fully associative L1 2MB instruction TLB: 8 entries, fully associative L1 4KB data TLB: 32 entries, fully associative L1 4KB instruction TLB: 32 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 2MB unified TLB: 0 entries, disabled/not present L2 4KB data TLB: 512 entries, 4-way associative L2 4KB instruction TLB: 512 entries, 4-way associative L2 unified cache: 1024 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative usable memory = 6395625472 (6099 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009bfff, 634880 bytes (155 pages) 0x0000000000d13000 - 0x00000000d1c6bfff, 3505754112 bytes (855897 pages) 0x0000000100000000 - 0x000000019ffeffff, 2684289024 bytes (655344 pages) avail memory = 6179069952 (5892 MB) ACPI APIC Table: INTR: Adding local APIC 1 as a target FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 APIC: CPU 0 has ACPI ID 1 APIC: CPU 1 has ACPI ID 2 ULE: setup cpu group 0 ULE: setup cpu 0 ULE: adding cpu 0 to group 0: cpus 1 mask 0x1 ULE: setup cpu group 1 ULE: setup cpu 1 ULE: adding cpu 1 to group 1: cpus 1 mask 0x2 ACPI: RSDP @ 0x0xf98a0/0x0014 (v 0 ACPIAM) ACPI: RSDT @ 0x0xddfd0000/0x003C (v 1 M S I OEMRSDT 0x10000731 MSFT 0x00000097) ACPI: FACP @ 0x0xddfd0200/0x0084 (v 2 M S I OEMFACP 0x10000731 MSFT 0x00000097) ACPI: DSDT @ 0x0xddfd0430/0x40D9 (v 1 1ADNC 1ADNC000 0x00000000 INTL 0x20051117) ACPI: FACS @ 0x0xddfde000/0x0040 ACPI: APIC @ 0x0xddfd0390/0x005C (v 1 M S I OEMAPIC 0x10000731 MSFT 0x00000097) ACPI: MCFG @ 0x0xddfd03f0/0x003C (v 1 M S I OEMMCFG 0x10000731 MSFT 0x00000097) ACPI: OEMB @ 0x0xddfde040/0x0060 (v 1 M S I AMI_OEM 0x10000731 MSFT 0x00000097) ACPI: EPTH @ 0x0xddfd4510/0x0038 (v 1 M S I OEMHPET 0x10000731 MSFT 0x00000097) ACPI: SSDT @ 0x0xddfd4550/0x030E (v 1 A M I POWERNOW 0x00000001 AMD 0x00000001) MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec00000 ioapic0: Routing external 8259A's -> intpin 0 MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level ioapic0: intpin 9 polarity: low ioapic0 irqs 0-23 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x0001000f pcm: 0x00010000 wlan: <802.11 Link Layer> ath_rate: version 1.2 wlan_amrr: nfslock: pseudo-device kbd: new array size 4 kbd1 at kbdmux0 mem: null: io: random: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 (Oct 22 2008 13:19:08) acpi0: on motherboard ioapic0: routing intpin 9 (ISA IRQ 9) to vector 48 acpi0: [MPSAFE] acpi0: [ITHREAD] acpi0: Power Button (fixed) AcpiOsDerivePciId: \\_SB_.PCI0.RS48.NB2_ -> bus 0 dev 0 func 0 acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, ddf00000 (3) failed ACPI timer: 0/838 0/839 0/841 0/895 0/842 0/840 0/837 0/890 0/836 0/837 -> 0 Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 pci_link0: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 3 4 5 7 10 11 12 14 15 Validation 0 5 N 0 3 4 5 7 10 11 12 14 15 After Disable 0 255 N 0 3 4 5 7 10 11 12 14 15 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 7 N 0 3 4 5 7 10 11 12 14 15 Validation 0 7 N 0 3 4 5 7 10 11 12 14 15 After Disable 0 255 N 0 3 4 5 7 10 11 12 14 15 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 3 4 5 7 10 11 12 14 15 Validation 0 10 N 0 3 4 5 7 10 11 12 14 15 After Disable 0 255 N 0 3 4 5 7 10 11 12 14 15 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 3 4 5 7 10 11 12 14 15 Validation 0 10 N 0 3 4 5 7 10 11 12 14 15 After Disable 0 255 N 0 3 4 5 7 10 11 12 14 15 pci_link4: Index IRQ Rtd Ref IRQs Initial Probe 0 4 N 0 3 4 5 7 10 11 12 14 15 Validation 0 4 N 0 3 4 5 7 10 11 12 14 15 After Disable 0 255 N 0 3 4 5 7 10 11 12 14 15 pci_link5: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 3 4 5 7 10 11 12 14 15 Validation 0 255 N 0 3 4 5 7 10 11 12 14 15 After Disable 0 255 N 0 3 4 5 7 10 11 12 14 15 pci_link6: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 3 4 5 7 10 11 12 14 15 Validation 0 11 N 0 3 4 5 7 10 11 12 14 15 After Disable 0 255 N 0 3 4 5 7 10 11 12 14 15 pci_link7: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 3 4 5 7 10 11 12 14 15 Validation 0 255 N 0 3 4 5 7 10 11 12 14 15 After Disable 0 255 N 0 3 4 5 7 10 11 12 14 15 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x1002, dev=0x7910, revid=0x00 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x2220, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1002, dev=0x7912, revid=0x00 domain=0, bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x1a (6500 ns), maxlat=0x00 (0 ns) found-> vendor=0x1002, dev=0x7917, revid=0x00 domain=0, bus=0, slot=7, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x4010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x00 (0 ns) powerspec 3 supports D0 D3 current D0 MSI supports 1 message found-> vendor=0x1002, dev=0x4380, revid=0x00 domain=0, bus=0, slot=18, func=0 class=01-01-8f, hdrtype=0x00, mfdev=0 cmdreg=0x0107, statreg=0x0230, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0xb000, size 3, enabled map[14]: type I/O Port, range 32, base 0xa000, size 2, enabled map[18]: type I/O Port, range 32, base 0x9000, size 3, enabled map[1c]: type I/O Port, range 32, base 0x8000, size 2, enabled map[20]: type I/O Port, range 32, base 0x7000, size 4, enabled map[24]: type Memory, range 32, base 0xfe7ff800, size 10, enabled pcib0: matched entry for 0.18.INTA pcib0: slot 18 INTA hardwired to IRQ 22 found-> vendor=0x1002, dev=0x4387, revid=0x00 domain=0, bus=0, slot=19, func=0 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0517, statreg=0x02a0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 map[10]: type Memory, range 32, base 0xfe7fe000, size 12, enabled pcib0: matched entry for 0.19.INTA pcib0: slot 19 INTA hardwired to IRQ 16 found-> vendor=0x1002, dev=0x4388, revid=0x00 domain=0, bus=0, slot=19, func=1 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0517, statreg=0x02a0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=7 map[10]: type Memory, range 32, base 0xfe7fd000, size 12, enabled pcib0: matched entry for 0.19.INTB pcib0: slot 19 INTB hardwired to IRQ 17 found-> vendor=0x1002, dev=0x4389, revid=0x00 domain=0, bus=0, slot=19, func=2 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x02a0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=10 map[10]: type Memory, range 32, base 0xfe7fc000, size 12, enabled pcib0: matched entry for 0.19.INTC pcib0: slot 19 INTC hardwired to IRQ 18 found-> vendor=0x1002, dev=0x438a, revid=0x00 domain=0, bus=0, slot=19, func=3 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x02a0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=7 map[10]: type Memory, range 32, base 0xfe7fb000, size 12, enabled pcib0: matched entry for 0.19.INTB pcib0: slot 19 INTB hardwired to IRQ 17 found-> vendor=0x1002, dev=0x438b, revid=0x00 domain=0, bus=0, slot=19, func=4 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x02a0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=10 map[10]: type Memory, range 32, base 0xfe7fa000, size 12, enabled pcib0: matched entry for 0.19.INTC pcib0: slot 19 INTC hardwired to IRQ 18 found-> vendor=0x1002, dev=0x4386, revid=0x00 domain=0, bus=0, slot=19, func=5 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0517, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfe7ff000, size 8, enabled pcib0: matched entry for 0.19.INTD pcib0: slot 19 INTD hardwired to IRQ 19 found-> vendor=0x1002, dev=0x4385, revid=0x14 domain=0, bus=0, slot=20, func=0 class=0c-05-00, hdrtype=0x00, mfdev=1 cmdreg=0x0401, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type I/O Port, range 32, base 0xb00, size 4, enabled found-> vendor=0x1002, dev=0x438c, revid=0x00 domain=0, bus=0, slot=20, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0220, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 map[20]: type I/O Port, range 32, base 0xff00, size 4, enabled found-> vendor=0x1002, dev=0x438d, revid=0x00 domain=0, bus=0, slot=20, func=3 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x0220, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1002, dev=0x4384, revid=0x00 domain=0, bus=0, slot=20, func=4 class=06-04-01, hdrtype=0x01, mfdev=1 cmdreg=0x0107, statreg=0x02a0, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x03 (750 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1100, revid=0x00 domain=0, bus=0, slot=24, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1101, revid=0x00 domain=0, bus=0, slot=24, func=1 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1102, revid=0x00 domain=0, bus=0, slot=24, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1103, revid=0x00 domain=0, bus=0, slot=24, func=3 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) pcib1: at device 1.0 on pci0 pcib1: domain 0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xc000-0xcfff pcib1: memory decode 0xfe800000-0xfe9fffff pcib1: prefetched decode 0xfc000000-0xfdffffff pci1: on pcib1 pci1: domain=0, physical bus=1 found-> vendor=0x1002, dev=0x791e, revid=0x00 domain=0, bus=1, slot=5, func=0 class=03-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Prefetchable Memory, range 64, base 0xfc000000, size 25, enabled pcib1: requested memory range 0xfc000000-0xfdffffff: good map[18]: type Memory, range 64, base 0xfe9f0000, size 16, enabled pcib1: requested memory range 0xfe9f0000-0xfe9fffff: good map[20]: type I/O Port, range 32, base 0xc000, size 8, enabled pcib1: requested I/O range 0xc000-0xc0ff: in range map[24]: type Memory, range 32, base 0xfe800000, size 20, enabled pcib1: requested memory range 0xfe800000-0xfe8fffff: good pcib1: matched entry for 1.5.INTA pcib1: slot 5 INTA hardwired to IRQ 18 found-> vendor=0x1002, dev=0x7919, revid=0x00 domain=0, bus=1, slot=5, func=2 class=04-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=10 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Memory, range 64, base 0xfe9e8000, size 14, enabled pcib1: requested memory range 0xfe9e8000-0xfe9ebfff: good pcib1: matched entry for 1.5.INTB pcib1: slot 5 INTB hardwired to IRQ 19 vgapci0: port 0xc000-0xc0ff mem 0xfc000000-0xfdffffff,0xfe9f0000-0xfe9fffff,0xfe800000-0xfe8fffff irq 18 at device 5.0 on pci1 pci1: at device 5.2 (no driver attached) pcib2: at device 7.0 on pci0 pcib2: domain 0 pcib2: secondary bus 2 pcib2: subordinate bus 2 pcib2: I/O decode 0xd000-0xdfff pcib2: memory decode 0xfea00000-0xfeafffff pcib2: no prefetched decode pci2: on pcib2 pci2: domain=0, physical bus=2 found-> vendor=0x10ec, dev=0x8168, revid=0x01 domain=0, bus=2, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x4010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 MSI supports 2 messages, 64 bit map[10]: type I/O Port, range 32, base 0xd800, size 8, enabled pcib2: requested I/O range 0xd800-0xd8ff: in range map[18]: type Memory, range 64, base 0xfeaff000, size 12, enabled pcib2: requested memory range 0xfeaff000-0xfeafffff: good pcib2: matched entry for 2.0.INTA pcib2: slot 0 INTA hardwired to IRQ 19 re0: port 0xd800-0xd8ff mem 0xfeaff000-0xfeafffff irq 19 at device 0.0 on pci2 re0: Reserved 0x1000 bytes for rid 0x18 type 3 at 0xfeaff000 re0: MSI count : 2 re0: turning off MSI enable bit. re0: Chip rev. 0x38000000 re0: MAC rev. 0x00000000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: bpf attached re0: Ethernet address: 00:21:85:15:30:14 ioapic0: routing intpin 19 (PCI IRQ 19) to vector 49 re0: [MPSAFE] re0: [FILTER] atapci0: port 0xb000-0xb007,0xa000-0xa003,0x9000-0x9007,0x8000-0x8003,0x7000-0x700f mem 0xfe7ff800-0xfe7ffbff irq 22 at device 18.0 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x7000 atapci0: Reserved 0x400 bytes for rid 0x24 type 3 at 0xfe7ff800 ioapic0: routing intpin 22 (PCI IRQ 22) to vector 50 atapci0: [MPSAFE] atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 4 ports detected ata2: on atapci0 ata2: SATA connect time=0ms ata2: SIGNATURE: 00000101 ata2: ahci_reset devices=0x1 ata2: [MPSAFE] ata2: [ITHREAD] ata3: on atapci0 ata3: SATA connect time=0ms ata3: SIGNATURE: 00000101 ata3: ahci_reset devices=0x1 ata3: [MPSAFE] ata3: [ITHREAD] ata4: on atapci0 ata4: SATA connect status=00000000 ata4: ahci_reset devices=0x0 ata4: [MPSAFE] ata4: [ITHREAD] ata5: on atapci0 ata5: SATA connect status=00000000 ata5: ahci_reset devices=0x0 ata5: [MPSAFE] ata5: [ITHREAD] pci0: at device 19.0 (no driver attached) pci0: at device 19.1 (no driver attached) pci0: at device 19.2 (no driver attached) pci0: at device 19.3 (no driver attached) pci0: at device 19.4 (no driver attached) pci0: at device 19.5 (no driver attached) pci0: at device 20.0 (no driver attached) atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xff00 ata0: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci1: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=00 ostat0=ff ostat1=ff ioapic0: routing intpin 14 (ISA IRQ 14) to vector 51 ata0: [MPSAFE] ata0: [ITHREAD] isab0: at device 20.3 on pci0 isa0: on isab0 pcib3: at device 20.4 on pci0 pcib3: domain 0 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode 0xe000-0xefff pcib3: memory decode 0xfeb00000-0xfebfffff pcib3: no prefetched decode pcib3: Subtractively decoded bridge. pci3: on pcib3 pci3: domain=0, physical bus=3 k8temp0: on hostb4 acpi_button0: on acpi0 sio0: configured irq 3 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: irq maps: 0 0 0 0 sio0: configured irq 3 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: irq maps: 0 0 0 0 sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on acpi0 sio0: type 16550A ioapic0: routing intpin 3 (ISA IRQ 3) to vector 52 sio0: [FILTER] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 ioapic0: routing intpin 1 (ISA IRQ 1) to vector 53 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: unable to allocate IRQ cpu0: on acpi0 cpu0: switching to generic Cx mode acpi_throttle0: on cpu0 acpi_throttle0: CLK_VAL field overlaps THT_EN bit device_attach: acpi_throttle0 attach returned 6 powernow0: on cpu0 cpu1: on acpi0 powernow1: on cpu1 ex_isa_identify() atkbdc: atkbdc0 already exists; skipping it sio: sio0 already exists; skipping it ahc_isa_probe 0: ioport 0xc00 alloc failed sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: at iomem 0xcd800-0xce7ff on isa0 fdc0 failed to probe at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 ppc0: cannot reserve I/O port range ppc0: failed to probe at irq 7 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd1, terminal emulator: sc (syscons terminal) sio1 failed to probe at port 0x2f8 irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 isa_probe_children: probing PnP devices Device configuration finished. Reducing kern.maxvnodes 235635 -> 100000 procfs registered lapic: Divisor 2, Frequency 99999202 hz Timecounter "TSC" frequency 2999975813 Hz quality -100 Timecounters tick every 1.000 msec lo0: bpf attached hptrr: no controller detected. ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad4: 715404MB at ata2-master SATA300 ad4: 1465149168 sectors [1453521C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad4 ad4: Silicon Image check1 failed ad4: Adaptec check1 failed ad4: LSI (v3) check1 failed ad4: LSI (v2) check1 failed ad4: FreeBSD check1 failed ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad6: 715404MB at ata3-master SATA300 ad6: 1465149168 sectors [1453521C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad6 ad6: Silicon Image check1 failed ad6: Adaptec check1 failed ad6: LSI (v3) check1 failed ad6: LSI (v2) check1 failed ad6: FreeBSD check1 failed ATA PseudoRAID loaded SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 ioapic0: Assigning ISA IRQ 1 to local APIC 0 ioapic0: Assigning ISA IRQ 3 to local APIC 1 ioapic0: Assigning ISA IRQ 9 to local APIC 0 ioapic0: Assigning ISA IRQ 14 to local APIC 1 ioapic0: Assigning PCI IRQ 19 to local APIC 0 ioapic0: Assigning PCI IRQ 22 to local APIC 1 GEOM_MIRROR: Device mirror/os launched (2/2). GEOM_JOURNAL: Journal 647493113: mirror/oss1g contains data. GEOM_JOURNAL: Journal 647493113: mirror/oss1g contains journal. GEOM_JOURNAL: Journal mirror/oss1g clean. Trying to mount root from ufs:/dev/mirror/oss1a start_init: trying /sbin/init re0: link state changed to UP --XsQoSWH+UP9D9v3l-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 20:17:24 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7403A1065670 for ; Tue, 9 Dec 2008 20:17:24 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [91.121.44.19]) by mx1.freebsd.org (Postfix) with ESMTP id 37F528FC1C for ; Tue, 9 Dec 2008 20:17:24 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from baby-jane.lamaiziere.net (246.10.87-79.rev.gaoland.net [79.87.10.246]) by smtp.lamaiziere.net (Postfix) with ESMTPA id 52E9063366E; Tue, 9 Dec 2008 20:58:09 +0100 (CET) Received: from baby-jane (localhost [127.0.0.1]) by baby-jane.lamaiziere.net (Postfix) with ESMTP id 298EC67552C; Tue, 9 Dec 2008 20:58:08 +0100 (CET) Date: Tue, 9 Dec 2008 20:58:06 +0100 From: Patrick =?ISO-8859-15?Q?Lamaizi=E8re?= To: freebsd-stable Stable Message-ID: <20081209205806.6e3f0c5e@baby-jane> In-Reply-To: <02D7BFFB-7B09-42DB-BBDF-F83AFDE45BD3@verweg.com> References: <20081208182112.GW58682@server.vk2pj.dyndns.org> <02D7BFFB-7B09-42DB-BBDF-F83AFDE45BD3@verweg.com> Organization: /dave/nulle X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.9; i386-apple-darwin9.3.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit Cc: Subject: Re: visibility of release process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Dec 2008 20:17:24 -0000 Le Tue, 9 Dec 2008 11:16:57 +0100, Ruben van Staveren a écrit : > > Sure, but show me how to go to http://svn.freebsd.org/viewvc/base/ > > and see commit log per branch or any other way to see what is > > going on in a branch. Fisheye gives you that in a really clear way > > and it costs nothing to add another option for users. > > Though experimental, I'm greatly enjoying > http://www.secnetix.de/olli/FreeBSD/svnews/?p=/stable/7 Nice. There is also http://freshbsd.org/ (really cool IMHO). Regards. From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 21:20:02 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18FED106567A for ; Tue, 9 Dec 2008 21:20:02 +0000 (UTC) (envelope-from toasty@dragondata.com) Received: from tokyo01.jp.mail.your.org (tokyo01.jp.mail.your.org [204.9.54.5]) by mx1.freebsd.org (Postfix) with ESMTP id CD3CA8FC23 for ; Tue, 9 Dec 2008 21:20:01 +0000 (UTC) (envelope-from toasty@dragondata.com) Received: from tokyo01.jp.mail.your.org (localhost.your.org [127.0.0.1]) by tokyo01.jp.mail.your.org (Postfix) with ESMTP id DD1D22AD545E; Tue, 9 Dec 2008 21:19:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=dragondata.com; h=cc :message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references; s=selector1; bh=cG3m5Iszd2bOBmaXnb9Eyst7x2M=; b=C7/gWlLtbfyB23u efkep12dqaWU97hBLywTwoGO7zwsnyh3LmCjpZN4Qw2eBLX4JUP0kdVGkkta8Oga oDbhuwdD2ThsWkVQCDv4pmbAy4fYrTs2K0ZmGqvr7rQAyyHosDkeKFPKrY6o7Hn+ eZ+NM/+3Os1UNkkBewLMSxwKGhJs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=dragondata.com; h=cc:message-id :from:to:in-reply-to:content-type:content-transfer-encoding :mime-version:subject:date:references; q=dns; s=selector1; b=0eI 3JnnE1AaTiE2m+zP8rwHNYhj4A/ca5FFSKZ0vhzRUwxttVqvnbqP3rKlokJZ0Wee d2i4b7zVBf258Z1QINzxo6H9p/8zfoIH7DrMZ8q4meEAfDYKtL4ec/xf74zgdXkF h0jdRuvxYmA72Hd+kUHsmwDJImXM1ubtR2UtRjQg= Received: from mail.your.org (server3-a.your.org [64.202.112.67]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by tokyo01.jp.mail.your.org (Postfix) with ESMTPS id 7A54F2AD5415; Tue, 9 Dec 2008 21:19:59 +0000 (UTC) Received: from [IPv6:2002:451f:630b:1::1] (unknown [IPv6:2002:451f:630b:1::1]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.your.org (Postfix) with ESMTPSA id 552DDA0A40B; Tue, 9 Dec 2008 21:19:45 +0000 (UTC) Message-Id: <55FAF790-6169-42BE-9285-1217C3284CDB@dragondata.com> From: Kevin Day To: Ken Smith In-Reply-To: <1228753517.56532.25.camel@bauer.cse.buffalo.edu> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Tue, 9 Dec 2008 15:19:53 -0600 References: <1228753517.56532.25.camel@bauer.cse.buffalo.edu> X-Mailer: Apple Mail (2.929.2) Cc: freebsd-stable Stable Subject: Re: visibility of release process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Dec 2008 21:20:02 -0000 On Dec 8, 2008, at 10:25 AM, Ken Smith wrote: > > Bottom line is my communication skills suck and of the bazillion other > things I could do with my time these sorts of housekeeping chores wind > up at a low enough priority they don't get done. But as you and > others > have made clear the priority needs to get raised and I need to deal > with > it. That's the part being worked on. Personally, as a end user, developer and cluster manager there are a few things that I would find extremely useful. I mean no disrespect to you or any of the work anyone on the team is putting forth for this - it's way more than I'm contributing so I'm grateful of what's being done now. This is just a wishlist. :) * Make the release notes a working document throughout the development cycle. Major caveats that anything in it before it's actually released is subject to change, but until the release notes are published I have a really tough time knowing what the next release even has in it. Is it worth holding off upgrading 50 servers for something we'd actually use, or are the changes of no concern? Is it something I didn't even know was in the tree that I might backport myself? If the release notes actually are available somewhere before the final stages of a release, I haven't been able to find them. * More notice to hubs@ before the release notes are generated. The releases always come with a "At the time of this writing, these mirrors have the full distribution" list. If it was announced to us mirror operators before that list is made, we could make sure we were synced in time to be included. Maybe even a semi-shaming of "These mirrors do not appear to have the required bits:". The difference in bandwidth we see on our public mirror (ftp3.us) is pretty extreme if we're listed there or not, which seems to be a 50/50 coin-toss on the last few releases. I'm honestly not sure why, since we can easily pull >50mbps from ftp-master. * The published release schedules are usually pretty far out of date. Beta/RCs get put up but the schedule says they haven't been, schedules sometimes have obviously slipped but it's unclear if it's affecting the final release date or not, etc. I know there aren't always answers to the unknowns, but more information would help. * Where are the BETA/RCs announced? Taking a page from apple, a mini- release notes saying "These items have changed since the last release/ beta/rc:" "These areas could use additional testing:" "These bugs are believed to be fixed, if you're still experiencing them let us know:" would probably get more people testing them. and give more insight into what's new. On anything other than a -RELEASE, make mention of this document in /etc/motd. I understand this would require effort from people working on those features, but if the beta readme file was in CVS and it was easier for developers to add to it themselves... If I'm not on the right mailing list, I won't see the "Call for testers" email that some send out. * Non FreeBSD users have a tough time with understanding that FreeBSD 6.4 was released after 7.0. I don't think the version numbering system should change, but new/novice users need a clearer guide as to which version to install on a fresh system. For example, the /releases/ page says: Release 7.0 (February 2008) Release 6.4 (November 2008) Which one of those is considered stable? If I know nothing about FreeBSD which one is "better" for me? Maybe a page that lists new features in rows, and a column/notes about its status in each version. FreeBSD has support for the Q1235 RAID controller from FooWare, but what version did it gain that? I'd love to help, but I'm not sure how/were an outsider can really make much impact here. But, I'm semi-volunteering. :) -- Kevin From owner-freebsd-stable@FreeBSD.ORG Tue Dec 9 23:58:22 2008 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 420461065670 for ; Tue, 9 Dec 2008 23:58:22 +0000 (UTC) (envelope-from confirm-return-stable=FreeBSD.org@returns.groups.yahoo.com) Received: from n17c.bullet.sp1.yahoo.com (n17c.bullet.sp1.yahoo.com [69.147.64.126]) by mx1.freebsd.org (Postfix) with SMTP id 0F5488FC08 for ; Tue, 9 Dec 2008 23:58:22 +0000 (UTC) (envelope-from confirm-return-stable=FreeBSD.org@returns.groups.yahoo.com) Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=lima; d=yahoogroups.com; b=W5maEWXvrzSAopSYvD2qDvlS/L8y3vNWjgu4BWvrV7GcI8Mqv4xI5wH8hwyJ8jqlPEt/lJajHgCUboCBiqf5vXrQaKwaIwm2ppO4vuta6o8Dq4uSc3e7/cQw6AL/Hk28; Received: from [69.147.65.147] by n17.bullet.sp1.yahoo.com with NNFMP; 09 Dec 2008 23:45:10 -0000 Received: from [66.218.67.33] by t10.bullet.mail.sp1.yahoo.com with NNFMP; 09 Dec 2008 23:45:10 -0000 Date: 9 Dec 2008 23:45:08 -0000 Message-ID: <1228866308.86.30548.w126@yahoogroups.com> X-Yahoo-Newman-Property: groups-unconfirmed From: Yahoo! Groups To: stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Subject: Please confirm your request to join SKATINGEXTREME X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: confirm-s2-yvl4asaeasr2mkc2uta5qvz53fy2pwjx-stable=FreeBSD.org@yahoogroups.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 23:58:22 -0000 Hello stable@FreeBSD.org, We have received your request to join the SKATINGEXTREME group hosted by Yahoo! Groups, a free, easy-to-use community service. This request will expire in 7 days. TO BECOME A MEMBER OF THE GROUP: 1) Go to the Yahoo! Groups site by clicking on this link: http://groups.yahoo.com/i?i=yvl4asaeasr2mkc2uta5qvz53fy2pwjx&e=stable%40FreeBSD%2Eorg (If clicking doesn't work, "Cut" and "Paste" the line above into your Web browser's address bar.) -OR- 2) REPLY to this email by clicking "Reply" and then "Send" in your email program If you did not request, or do not want, a membership in the SKATINGEXTREME group, please accept our apologies and ignore this message. Regards, Yahoo! Groups Customer Care Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 02:39:34 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 797AC1065670 for ; Wed, 10 Dec 2008 02:39:34 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from phoebe.cse.buffalo.edu (phoebe.cse.buffalo.edu [128.205.32.89]) by mx1.freebsd.org (Postfix) with ESMTP id 4B2288FC13 for ; Wed, 10 Dec 2008 02:39:34 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from [128.205.32.76] (bauer.cse.buffalo.edu [128.205.32.76]) (authenticated bits=0) by phoebe.cse.buffalo.edu (8.14.1/8.13.7) with ESMTP id mBA2dQfQ094633 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 9 Dec 2008 21:39:27 -0500 (EST) (envelope-from kensmith@cse.buffalo.edu) From: Ken Smith To: freebsd-stable Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-KcA3VEL6+bCkhDt6Esmh" Organization: U. Buffalo CSE Department Date: Tue, 09 Dec 2008 21:39:26 -0500 Message-Id: <1228876766.35416.23.camel@bauer.cse.buffalo.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port X-DCC-Buffalo.EDU-Metrics: phoebe.cse.buffalo.edu 1029; Body=0 Fuz1=0 Fuz2=0 X-Spam-Status: No, score=-4.0 required=5.0 tests=RCVD_IN_DNSWL_MED autolearn=failed version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on phoebe.cse.buffalo.edu Subject: FreeBSD 7.1-RC1 Available... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Dec 2008 02:39:34 -0000 --=-KcA3VEL6+bCkhDt6Esmh Content-Type: text/plain Content-Transfer-Encoding: quoted-printable So... Two show-stoppers, one Security Advisory, and one "Gee. Did we really implement that new interface that way? That needs a bit more work." later... FreeBSD 7.1-RC1 is now available, the first of the Release Candidates. There will be at least one more Release Candidate before the release so the release itself is likely around 3 weeks from now IF no new show-stoppers are uncovered during testing. In addition to general testing we're looking for information about potential problems with the boot loader. There has been traffic here about problems but the reports haven't helped narrow down the causes yet. So far it seems to be related to USB keyboards and at least so far systems with more than one processor in them. More data points like cases where a USB keyboard was not involved as well as if possible things like which motherboard it is might help us narrow down the cause. Testing on a variety of motherboards, of varying ages and manufacturers would help. And a late arrival that's not possible to test without the packages, sysinstall's issues with excessive disc swapping when installing large sets of packages off the CDROMs should be fixed. Given the package layout it should ask for a disc no more than once. Testing to make sure that's working would be appreciated. NOTE: If updating from a 7.0 or earlier system due to a change in the Vendor's drivers certain Intel NICs will now come up as igb(4) instead of em(4). We normally try to avoid changes like that in stable branches but the vendor felt it necessary in order to support the new adapters. See the UPDATING entry dated 20080811 for details. There are only 3 PCI ID's that should have their name changed from em(4) to igb(4): 0x10A7, 0x10A9, and 0x10D6. You should be able to determine if your card will change names by running the command "pciconf -l", and for the line representing your NIC (should be named em on older systems, e.g. em0 or em1, etc) check the fourth column. If it says "chip=3D0x10a7" (or one of the other two IDs given above) you will have the adapter's name change. The ISO images and FTP install trees are available on the FreeBSD Mirror sites. Using the primary site as an example: ftp://ftp.freebsd.org/pub/FreeBSD/releases/${arch}/ISO-IMAGES/7.1/ where ${arch} is one of amd64, i386, ia64, pc98, powerpc, or sparc64. The ISOs for amd64, i386, and sparc64 include what is expected to be the final package set. For all architectures the ISOs with "disc" in their names are CDROM-sized, if you intend to install a variety of packages during installation you will need all three. For amd64 and i386 there is a gzip-ed iso with "dvd" in its name which is DVD-sized. It contains everything (install bits, livefs, docs, and packages) and can be used if your machine has a DVD drive in it. If you would like to do a source-based update to 7.1-RC1 from an already installed machine you can update your tree to RELENG_7_1 using normal cvsup/csup methods. Note that due to an unfortunate side-effect of the "real" source code repository now being in SVN it will look like all files have a new version so mergemaster may be a bit tedious. The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.0-RELEASE, 7.1-BETA, or 7.1-BETA2 can upgrade as follows: =20 # freebsd-update upgrade -r 7.1-RC1 During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. =20 # freebsd-update install The system must be rebooted with the newly installed kernel before continui= ng. # shutdown -r now =20 After rebooting, freebsd-update needs to be run again to install the new userland components, and the system needs to be rebooted again: # freebsd-update install # shutdown -r now =20 Users of Intel network interfaces which are changing their name from "em" t= o "igb" should make necessary changes to configuration files BEFORE running freebsd-update, since otherwise the network interface will not be configure= d appropriately after rebooting for the first time. =20 Users of earlier FreeBSD releases (FreeBSD 6.x) can also use freebsd-update= to upgrade to FreeBSD 7.1, but will be prompted to rebuild all third-party applications (e.g., anything installed from the ports tree) after the secon= d invocation of "freebsd-update install", in order to handle differences in t= he system libraries between FreeBSD 6.x and FreeBSD 7.x. --=20 Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | --=-KcA3VEL6+bCkhDt6Esmh Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkk/K9IACgkQ/G14VSmup/bQ2wCfaIqJKwGLnRbUAgRsRFh29zuc 5a4An0EQHjmR+WvypQtt8yOUA5ogSzKy =lfjk -----END PGP SIGNATURE----- --=-KcA3VEL6+bCkhDt6Esmh-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 02:49:11 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6DC41065676 for ; Wed, 10 Dec 2008 02:49:11 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from phoebe.cse.buffalo.edu (phoebe.cse.buffalo.edu [128.205.32.89]) by mx1.freebsd.org (Postfix) with ESMTP id ACBE88FC1C for ; Wed, 10 Dec 2008 02:49:11 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from [128.205.32.76] (bauer.cse.buffalo.edu [128.205.32.76]) (authenticated bits=0) by phoebe.cse.buffalo.edu (8.14.1/8.13.7) with ESMTP id mBA2n5Y7094674 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 9 Dec 2008 21:49:05 -0500 (EST) (envelope-from kensmith@cse.buffalo.edu) From: Ken Smith To: freebsd-stable In-Reply-To: <1228876766.35416.23.camel@bauer.cse.buffalo.edu> References: <1228876766.35416.23.camel@bauer.cse.buffalo.edu> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-E5gaaX0xLaq6XSGMix8O" Organization: U. Buffalo CSE Department Date: Tue, 09 Dec 2008 21:49:05 -0500 Message-Id: <1228877345.35416.27.camel@bauer.cse.buffalo.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port X-DCC-Buffalo.EDU-Metrics: phoebe.cse.buffalo.edu 1029; Body=0 Fuz1=0 X-Spam-Status: No, score=-4.0 required=5.0 tests=RCVD_IN_DNSWL_MED autolearn=failed version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on phoebe.cse.buffalo.edu Subject: Re: FreeBSD 7.1-RC1 Available... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Dec 2008 02:49:12 -0000 --=-E5gaaX0xLaq6XSGMix8O Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Sigh. Sorry, did it again... Note the checksum for the dvd1 images is for them in their ungzip-ed form so uncompress them before trying to verify the checksums. Checksums: MD5 (7.1-RC1-amd64-bootonly.iso) =3D de6338599df1be6915dd01001c1ef4e5 MD5 (7.1-RC1-amd64-disc1.iso) =3D 116d0dbff53871778fb0e1e90ce4f2a6 MD5 (7.1-RC1-amd64-disc2.iso) =3D 2fb908291c90330b665098bb785d0746 MD5 (7.1-RC1-amd64-disc3.iso) =3D 1aecb94dbdc8cce4e1d793d308d32364 MD5 (7.1-RC1-amd64-docs.iso) =3D 440b5eb826a710d5e07f579d31142551 MD5 (7.1-RC1-amd64-dvd1.iso) =3D 205147c332524d49521f3b98c8b1b73b MD5 (7.1-RC1-amd64-livefs.iso) =3D 1972008c2b34eb3e51074ebd61a4a454 MD5 (7.1-RC1-i386-bootonly.iso) =3D e12d84609a00bdc6f996e77eff77226a MD5 (7.1-RC1-i386-disc1.iso) =3D 8743fff3a445d99b36772ff9984f7cae MD5 (7.1-RC1-i386-disc2.iso) =3D 4dabd0b245e42c2eb88a89ac4e132bad MD5 (7.1-RC1-i386-disc3.iso) =3D 63860e393c8001015c38cceb263b9ac7 MD5 (7.1-RC1-i386-docs.iso) =3D 57bfd48213da28789af84ea10301895a MD5 (7.1-RC1-i386-dvd1.iso) =3D e5acb528569ca5cc7fbc5d41fc2ae636 MD5 (7.1-RC1-i386-livefs.iso) =3D b261a6d73a491d188ac2dd1f913a86ef MD5 (7.1-RC1-ia64-bootonly.iso) =3D 07dfef578edb3aab31c2389c7f2d2bbe MD5 (7.1-RC1-ia64-disc1.iso) =3D 332009d292433d9232c0e4c906ee69c7 MD5 (7.1-RC1-ia64-disc2.iso) =3D f217c565ee264d883de71ccc3c94f91a MD5 (7.1-RC1-ia64-disc3.iso) =3D 15b8393ea09706ee7715bfdd62f11071 MD5 (7.1-RC1-ia64-docs.iso) =3D 16d95be27399605a487b1c1b61b02be5 MD5 (7.1-RC1-ia64-livefs.iso) =3D 15069a0e7142791a35fc25b64bf1d16c MD5 (7.1-RC1-pc98-bootonly.iso) =3D be89ea6f9010c86839815ebb6d5d29df MD5 (7.1-RC1-pc98-disc1.iso) =3D ff94a112a96cc5c7f1f9ca8039106a7d MD5 (7.1-RC1-pc98-livefs.iso) =3D 2cc908c7f9449256eb807782229f7288 MD5 (7.1-RC1-powerpc-bootonly.iso) =3D e87dcd0649e66743ee54a461669f3401 MD5 (7.1-RC1-powerpc-disc1.iso) =3D 5109252f3fa6b42458c1a01692b37833 MD5 (7.1-RC1-powerpc-disc2.iso) =3D 9870248b2ebce575e675541ade94f4eb MD5 (7.1-RC1-powerpc-disc3.iso) =3D 42b5a3c0228860d161679fd8c54c2266 MD5 (7.1-RC1-powerpc-docs.iso) =3D 81272f56de121e9491f3aeb48f7eb2cc MD5 (7.1-RC1-sparc64-bootonly.iso) =3D d65c6d0120e17661b50593cf1cea35a0 MD5 (7.1-RC1-sparc64-disc1.iso) =3D 47990a92b36bfcbb8fc10e8fa33ea16a MD5 (7.1-RC1-sparc64-disc2.iso) =3D a5debb7feab8e21870f46ea0dc689e1a MD5 (7.1-RC1-sparc64-disc3.iso) =3D b3c1e1b3aa26c71b91c68e89c57661d8 MD5 (7.1-RC1-sparc64-docs.iso) =3D 01d2184ae88c1a94403ee63de7333f18 SHA256 (7.1-RC1-amd64-bootonly.iso) =3D be7d99f1f29c56ea107eb41feb786833593= 79a82d6ce80dbcd0fc3126f5b7ec4 SHA256 (7.1-RC1-amd64-disc1.iso) =3D 3be67ca088868059df0790251e0484ec67f617= fdd04a382e91ca0bae239c9d87 SHA256 (7.1-RC1-amd64-disc2.iso) =3D 91ba01dade4d37245ff5a5ff23d4a9b62d99e4= 1decd1958389d078e3b400309e SHA256 (7.1-RC1-amd64-disc3.iso) =3D 301e34f1ff84acdf568abd7a298eb16d9d41e7= 362d6814137ad888c046930b7e SHA256 (7.1-RC1-amd64-docs.iso) =3D f783cefa13144062d14db44ddb44969a571f1b2= 98930a8a544c7ac5e50e12cc3 SHA256 (7.1-RC1-amd64-dvd1.iso) =3D 971b8a21b53eaf583a4bb02c63a5eaba73dc29e= aa638d5712805ffc933eb643e SHA256 (7.1-RC1-amd64-livefs.iso) =3D b81e4b42fa8e908eb9d75708daae4cb8b92e3= 73e1e58fea306502920b7b52b33 SHA256 (7.1-RC1-i386-bootonly.iso) =3D b40e292d89c3e7167524bc9a9db543751881= 60e7e5855530471e8b2454727c11 SHA256 (7.1-RC1-i386-disc1.iso) =3D 13b88f219569748b5f760e190948e87a0febc38= 24278909d96db4173d6858820 SHA256 (7.1-RC1-i386-disc2.iso) =3D be7d09d59f921f121b3bb31e6d642f7b9a17a79= bd15e2c4ae0f2c25ba041cbba SHA256 (7.1-RC1-i386-disc3.iso) =3D 70c2fe469b0d99e73e711d11542bf303a3d8193= eae22c35e7187c79aa22d1a41 SHA256 (7.1-RC1-i386-docs.iso) =3D 64b96484e324d8cfec79c894f259dc3f1dfeb55f= 87ecd59c1c6049b59e8cfbc9 SHA256 (7.1-RC1-i386-dvd1.iso) =3D 5a265d19a6d8ed410e0e91d53cbf358bfa7b7e7e= 168cd6332a21dcdfddd0d37d SHA256 (7.1-RC1-i386-livefs.iso) =3D ba8be5619e0de22a5c69d5f8e245e7547cf5e3= b1a5a6047ecdc71a5d3444ee4b SHA256 (7.1-RC1-ia64-bootonly.iso) =3D 413a31029e32c64cc137cb3e2c6dfddac107= 79bef17e2de0f7ed3a02cc2dff9a SHA256 (7.1-RC1-ia64-disc1.iso) =3D 2f5fe288fcb5312347c89e147a78a634d906b57= 5104692a28b016b7514f5b541 SHA256 (7.1-RC1-ia64-disc2.iso) =3D 282fc15c7c2b594eff5041d5bd75337218f64ef= 41f1d97e991a2bc8c125a8e7c SHA256 (7.1-RC1-ia64-disc3.iso) =3D d4eada87243a20c7d2645096442e85e11717977= bfff6f30d98766a09f31c66c1 SHA256 (7.1-RC1-ia64-docs.iso) =3D b5ec27943a48588c12678c8653553e5eff1d0a38= 2ccc26ce1aa0b642310eee2d SHA256 (7.1-RC1-ia64-livefs.iso) =3D 33dfe5eada1d01bf8ed7c3093561eb5d92d4be= d6a2dd2c5c69c50abe4db1523c SHA256 (7.1-RC1-pc98-bootonly.iso) =3D f5aa07453a9a4444b84e26949d70bb5b2982= 778724afbd74553678e2142e2950 SHA256 (7.1-RC1-pc98-disc1.iso) =3D 24cf624b2edc719452da4ddfcf961dfb40bbc89= 64321ee10c7d3af1715ec6f74 SHA256 (7.1-RC1-pc98-livefs.iso) =3D ffd6d1065f3d991b0676a18e8ff4b2c69647e6= 9eda9c980510a25415bf65fcab SHA256 (7.1-RC1-powerpc-bootonly.iso) =3D 779110e8d426f5847fc2a89e273641933= cdb2c1b535a8f8cb5b7d94bbe62b6d0 SHA256 (7.1-RC1-powerpc-disc1.iso) =3D 5cab6aa5bb22e25fc30ebd4909de2df005cc= 070f5338175446d721ef0fac662f SHA256 (7.1-RC1-powerpc-disc2.iso) =3D 487722bef61d3bfd1bf9d507b1cd98f5e7a2= 2a0629ce3f6548e5394f3831189b SHA256 (7.1-RC1-powerpc-disc3.iso) =3D 07eb57953c2f62e32320af835fbc27809c33= ab1b9d07adeb90f4e94f89265815 SHA256 (7.1-RC1-powerpc-docs.iso) =3D fbe50671e2c49f83cd9aace1d008daed19a2a= 022536a27ffabb1b4d426cda633 SHA256 (7.1-RC1-sparc64-bootonly.iso) =3D 12d65300c950b6661d16715cdad902aca= fc5cf892731655082a2190707195225 SHA256 (7.1-RC1-sparc64-disc1.iso) =3D bc54c89619c3e99d57c94dc244fdc0fe71d5= 7093bcf12041abe5bf8c9e6d63d2 SHA256 (7.1-RC1-sparc64-disc2.iso) =3D 1242751d9c0a2f82923904f09fca0f4a6304= 1f3d68e3287963f1f48d81013ff2 SHA256 (7.1-RC1-sparc64-disc3.iso) =3D 216db6bf1123de281affa6d2ce1cea13f63f= be41bee0f825bc51d13b01411dcc SHA256 (7.1-RC1-sparc64-docs.iso) =3D c7a904e4897e8f5c16fbb2f66dd6e59c54366= 58f55c24648e5f3fb11e5986c8e --=20 Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | --=-E5gaaX0xLaq6XSGMix8O Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkk/LiEACgkQ/G14VSmup/ZcOACfUSUK7YcrSwzeqvFV1uFIcO5o neAAn07ovdvyiGvwpzQYfY4zl3LJkiAV =Gjun -----END PGP SIGNATURE----- --=-E5gaaX0xLaq6XSGMix8O-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 06:12:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C90AF106568C for ; Wed, 10 Dec 2008 06:12:38 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.231]) by mx1.freebsd.org (Postfix) with ESMTP id 8CEAC8FC2A for ; Wed, 10 Dec 2008 06:12:38 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so269543rvf.43 for ; Tue, 09 Dec 2008 22:12:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=QcNRwdk5TE4/471haVCtuNFM69b3fZbafBotTOqSmwA=; b=Dz+mcvUffJjlvXWPDYtcxPnGcySmBvvDV5Df16vh8Xbkt/MnnGKramOWv7S7f2rUzb qmCl8d/aeKvyMaITeAZS3Y97uoTW62Yj37xobLGqSP4F9PNHtC+0TGIYN+fft8LVnXyV KDDTGb9NkmsqPfDPq2QEk/baKc0jNJimmlpX8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=llKlzC31kl9n38b+aeY3qjyk4/6JA956Fb/mV8d1d0/1f4LJmVDw/Aqspa+fr9Fuz4 Xzygh/MKCZ44Zooya4qhXwLi2zjGGLJg4/lXLggUFxejudUVWDvwl0WyP8oLHss37Et3 CAgv2VcF5RgmS+GUqUzRhJuiCPeOP61nl9mAw= Received: by 10.140.193.15 with SMTP id q15mr464966rvf.274.1228889558062; Tue, 09 Dec 2008 22:12:38 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id l31sm1974933rvb.2.2008.12.09.22.12.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 09 Dec 2008 22:12:36 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id mBA6CTZ7038941 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Dec 2008 15:12:29 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id mBA6CQjL038940; Wed, 10 Dec 2008 15:12:26 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 10 Dec 2008 15:12:26 +0900 From: Pyun YongHyeon To: Victor Balada Diaz Message-ID: <20081210061226.GC37837@cdnetworks.co.kr> References: <20081209185236.GA1320@alf.bsdes.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081209185236.GA1320@alf.bsdes.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 06:12:38 -0000 On Tue, Dec 09, 2008 at 07:52:37PM +0100, Victor Balada Diaz wrote: > Hello, > > I got various machines[1] at hetzner.de and I've been having problems > with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've > been trying to narrow the problem so someone more knowledgeable than me > is able to fix it. This mail is an other attempt to ask a question > with regards ATA code to see if this time i got something. > > For the ones that don't actually know what happened: > > With FreeBSD 7.0 -RELEASE for amd64 and default kernel > the system shared re0 interrupt with OHCI and this caused > re(4) to corrupt packets and create interrupt storms. Tried re(4) in 7.0-RELEASE had bus_dma(9) bug which could be easily triggered on systems with > 4GB memory. But I dont' know whether this is related with interrupt storms. > updating to 7.1 -BETA2 and still had some problems with it. > > I've opened the PR kern/128287[2] and Remko quickly answered > with a workaround: that workaround was removing USB support from > my kernel. I did it and re(4) wasn't sharing interrupts anylonger, > and the interrupt storms were gone. Now sometime later the interface > goes up and down from time to time, but less often. Also sometimes > the machine losts the network interface but continues to work. > It seems that your controller supports MSI so you can set a tunable hw.re.msi_disable to 0 to enable MSI. With MSI you can remove interrupt sharing(e.g. add hw.re.msi_disable="0" to /boot/loader.conf file.) However there were several issues on re(4) w.r.t MSI so it was off by default. > I know it continues to work because some days later i can see that > it tried to deliver the status reports but was unable to resolve the > aliases hostnames. I can't ping the machine and i know the network > is OK. If i reboot the machine everything is working again. > Recently I've made small changes to re(4) which may help to detect link state change event. Would you try re(4) in HEAD? -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 07:06:20 2008 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 8E16B106567F for ; Wed, 10 Dec 2008 07:06:20 +0000 (UTC) (envelope-from goran.lowkrantz@ismobile.com) Received: from mail.ismobile.com (mail.ismobile.com [62.119.44.68]) by mx1.freebsd.org (Postfix) with ESMTP id 3BF0C8FC19 for ; Wed, 10 Dec 2008 07:06:20 +0000 (UTC) (envelope-from goran.lowkrantz@ismobile.com) Received: from mail.ismobile.com (localhost [127.0.0.1]) by mail.ismobile.com (Postfix) with ESMTP id 08296278; Wed, 10 Dec 2008 08:06:18 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=ismobile.com; h=date:from :to:cc:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=selector1; bh=sZukWEl krVW7P+GdaNb+abxJfV8=; b=iPz8bkCXEXk+bV/xPDFHwQnTdnw8VohV+PkGqbX 0VRFfyThMzTv7iLfnpk7rYz8hg8+NJ3oxw6sc1lfH5NgVvgZTqKmaoxFL0u1IWU5 Z2Ras8mEnFyt1jR5WU3HHutkXnBeRAy9SFKZJqRXRXfKm+nmf1CSQzarKNq8n1Tt im1Q= Received: from [172.16.2.128] (syn.hq.ismobile.com [172.16.2.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.ismobile.com (Postfix) with ESMTPSA id 28C96277; Wed, 10 Dec 2008 08:06:16 +0100 (CET) Date: Wed, 10 Dec 2008 08:06:16 +0100 From: Goran Lowkrantz To: pyunyh@gmail.com Message-ID: In-Reply-To: <80D07D8C17DAC73D69DCDC9A@[172.16.2.124]> References: <20081209114723.GE33723@cdnetworks.co.kr> <80D07D8C17DAC73D69DCDC9A@[172.16.2.124]> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: stable@freebsd.org Subject: Re: Regression in vr - not receiveing multicast X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Dec 2008 07:06:20 -0000 --On December 9, 2008 12:53:05 +0100 Goran Lowkrantz wrote: > --On December 9, 2008 20:47:23 +0900 Pyun YongHyeon > wrote: > >> On Tue, Dec 09, 2008 at 10:40:17AM +0100, Goran Lowkrantz wrote: >> > Hi, >> > >> > in July, vr had this problem and was fixed: >> > >> > >> > >> > but now it's back again! >> > >> >> There was just one bug fix since then and I guess the fix is not >> related with your issue. >> >> > On a system with the following: >> > 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Thu Oct 16 12:31:04 UTC 2008 >> > >> > I have to set all vr interfaces in promisc to get routing info. >> > >> > Using Quagga >> > # pkg_info -Ix uagga >> > quagga-0.99.10_3 Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route >> software > >> > on an inner network using RIPv2 >> > # ifmcstat -i vr0 >> > vr0: >> > inet xxx.xxx.xxx.xxx >> > group 224.0.0.9 >> > igmpv2 >> > mcast-macaddr 01:00:5e:00:00:09 refcnt 1 >> > group 224.0.0.1 >> > mcast-macaddr 01:00:5e:00:00:01 refcnt 1 >> > >> > >> > On the same box, we have some em devices also and they work without >> any > problems. >> > >> >> There is fundamental differences between em(4) and vr(4). The >> vr(4) for VT6105M takes advantage of perfect multicast filtering >> feature which is not present on all em(4) interface. Perfect >> multicast filtering can reduce unwanted multicast traffics such >> that it could save a lot of CPU cycles. The downside is that vr(4) >> cannot accept multicast frames for a multicast group without >> joining the multicast group first. >> For multicast routing purpose I guess 'options MROUTING' kernel >> option should be enabled to accept all multicast frames. >> Does your kernel have that option? > > No it has not. I will create such a beast and return with stories. > I have tried with 'options MROUTING' and it didn't work. Did I miss something? Do I have to install and run mrouted also? It seems like maybe the first two packages are accepted after registration as I don't lose the routes until after about 6 min uptime. But to get further updates, I need the interfaces in promisc. So, next step? /glz From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 07:19:44 2008 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 E525A1065675 for ; Wed, 10 Dec 2008 07:19:43 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.233]) by mx1.freebsd.org (Postfix) with ESMTP id A931A8FC24 for ; Wed, 10 Dec 2008 07:19:43 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so286905rvf.43 for ; Tue, 09 Dec 2008 23:19:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=SaDYS5jzufT73g2CRJsd1BWoPxeWm/FSoWJEkwS6jXs=; b=Oq3Jn8Hsr7zYJtuvSerAG54AxYRZsSE+1XFyFGaU8INx6etirVdIEnUAefdqhyzyW8 o8eQjyRzO+4oEaqYff5KLO9YItIGjbKVHNd0joR38lifDjm1U27HH3psh3MqIZHRyQhf UjdgU7ZPoNQGytFlUEZeWWTCWBfp5HqG+OZfU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=SB2wv0C6CSQPU9/qaD4YZezuy2m7mR1L7FEZDBvL7uLs+V2AWVR8UfjdZXg9PEL4dZ wjwc5L/k4nHK5loiYtekACsFTv3ggXzG2iNB4zXsP4oN9Blmvxl9sVIrdo3cDvUnS35+ PxezPP3lydXgrlMOhX2iol9bPeHPLG4RK7slU= Received: by 10.141.40.7 with SMTP id s7mr450821rvj.268.1228893583500; Tue, 09 Dec 2008 23:19:43 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id l31sm2099541rvb.2.2008.12.09.23.19.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 09 Dec 2008 23:19:40 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id mBA7JYjT039184 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Dec 2008 16:19:35 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id mBA7JYvq039183; Wed, 10 Dec 2008 16:19:34 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 10 Dec 2008 16:19:33 +0900 From: Pyun YongHyeon To: Goran Lowkrantz Message-ID: <20081210071932.GD37837@cdnetworks.co.kr> References: <20081209114723.GE33723@cdnetworks.co.kr> <80D07D8C17DAC73D69DCDC9A@[172.16.2.124]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: Regression in vr - not receiveing multicast X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 07:19:44 -0000 On Wed, Dec 10, 2008 at 08:06:16AM +0100, Goran Lowkrantz wrote: > --On December 9, 2008 12:53:05 +0100 Goran Lowkrantz > wrote: > > >--On December 9, 2008 20:47:23 +0900 Pyun YongHyeon > >wrote: > > > >>On Tue, Dec 09, 2008 at 10:40:17AM +0100, Goran Lowkrantz wrote: > >> > Hi, > >> > > >> > in July, vr had this problem and was fixed: > >> > > >> > > >> > > >> > but now it's back again! > >> > > >> > >>There was just one bug fix since then and I guess the fix is not > >>related with your issue. > >> > >> > On a system with the following: > >> > 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Thu Oct 16 12:31:04 UTC 2008 > >> > > >> > I have to set all vr interfaces in promisc to get routing info. > >> > > >> > Using Quagga > >> > # pkg_info -Ix uagga > >> > quagga-0.99.10_3 Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route > >>software > > >> > on an inner network using RIPv2 > >> > # ifmcstat -i vr0 > >> > vr0: > >> > inet xxx.xxx.xxx.xxx > >> > group 224.0.0.9 > >> > igmpv2 > >> > mcast-macaddr 01:00:5e:00:00:09 refcnt 1 > >> > group 224.0.0.1 > >> > mcast-macaddr 01:00:5e:00:00:01 refcnt 1 > >> > > >> > > >> > On the same box, we have some em devices also and they work without > >>any > problems. > >> > > >> > >>There is fundamental differences between em(4) and vr(4). The > >>vr(4) for VT6105M takes advantage of perfect multicast filtering > >>feature which is not present on all em(4) interface. Perfect > >>multicast filtering can reduce unwanted multicast traffics such > >>that it could save a lot of CPU cycles. The downside is that vr(4) > >>cannot accept multicast frames for a multicast group without > >>joining the multicast group first. > >>For multicast routing purpose I guess 'options MROUTING' kernel > >>option should be enabled to accept all multicast frames. > >>Does your kernel have that option? > > > >No it has not. I will create such a beast and return with stories. > > > > > I have tried with 'options MROUTING' and it didn't work. > > Did I miss something? Do I have to install and run mrouted also? > > It seems like maybe the first two packages are accepted after registration > as I don't lose the routes until after about 6 min uptime. But to get > further updates, I need the interfaces in promisc. > > So, next step? > Can you see ALLMULTI flag from the output of "ifconfig vr0"? -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 07:25:59 2008 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 C9E901065673 for ; Wed, 10 Dec 2008 07:25:59 +0000 (UTC) (envelope-from goran.lowkrantz@ismobile.com) Received: from mail.ismobile.com (mail.ismobile.com [62.119.44.68]) by mx1.freebsd.org (Postfix) with ESMTP id 468C38FC0C for ; Wed, 10 Dec 2008 07:25:59 +0000 (UTC) (envelope-from goran.lowkrantz@ismobile.com) Received: from mail.ismobile.com (localhost [127.0.0.1]) by mail.ismobile.com (Postfix) with ESMTP id 051BE285; Wed, 10 Dec 2008 08:25:58 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=ismobile.com; h=date:from :to:cc:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=selector1; bh=Vll5PDX VpthSUj5fdLlDc88rXjU=; b=YRqWfRDuescqfJsfirVtrjahJCEDN+UBq47h9+f Xj9wWijXkIDvH2bLslpw1D1RJh0UzF3kQAzQjB30rhemv70tZQCkK0f8B1U7Vebk nUX58fuYfvhKsUWMfLm9+eEdgD/mDViCTOmCpWuiU8ieFADum/fFvvR6ijD0dOYG 6kBc= Received: from [172.16.2.128] (syn.hq.ismobile.com [172.16.2.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.ismobile.com (Postfix) with ESMTPSA id 4176C284; Wed, 10 Dec 2008 08:25:57 +0100 (CET) Date: Wed, 10 Dec 2008 08:25:56 +0100 From: Goran Lowkrantz To: pyunyh@gmail.com Message-ID: <47381931A80CB93CADD10DC7@[172.16.2.128]> In-Reply-To: <20081210071932.GD37837@cdnetworks.co.kr> References: <20081209114723.GE33723@cdnetworks.co.kr> <80D07D8C17DAC73D69DCDC9A@[172.16.2.124]> <20081210071932.GD37837@cdnetworks.co.kr> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: stable@freebsd.org Subject: Re: Regression in vr - not receiveing multicast X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Dec 2008 07:25:59 -0000 --On December 10, 2008 16:19:33 +0900 Pyun YongHyeon wrote: > On Wed, Dec 10, 2008 at 08:06:16AM +0100, Goran Lowkrantz wrote: > > --On December 9, 2008 12:53:05 +0100 Goran Lowkrantz > > wrote: > > > > >--On December 9, 2008 20:47:23 +0900 Pyun YongHyeon > > >wrote: > > > > > >>On Tue, Dec 09, 2008 at 10:40:17AM +0100, Goran Lowkrantz wrote: > > >> > Hi, > > >> > > > >> > in July, vr had this problem and was fixed: > > >> > > > >> > > > >> > > > >> > but now it's back again! > > >> > > > >> > > >>There was just one bug fix since then and I guess the fix is not > > >>related with your issue. > > >> > > >> > On a system with the following: > > >> > 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Thu Oct 16 12:31:04 UTC > 2008 > >> > > > >> > I have to set all vr interfaces in promisc to get routing info. > > >> > > > >> > Using Quagga > > >> > # pkg_info -Ix uagga > > >> > quagga-0.99.10_3 Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route > > >>software > > > >> > on an inner network using RIPv2 > > >> > # ifmcstat -i vr0 > > >> > vr0: > > >> > inet xxx.xxx.xxx.xxx > > >> > group 224.0.0.9 > > >> > igmpv2 > > >> > mcast-macaddr 01:00:5e:00:00:09 refcnt 1 > > >> > group 224.0.0.1 > > >> > mcast-macaddr 01:00:5e:00:00:01 refcnt 1 > > >> > > > >> > > > >> > On the same box, we have some em devices also and they work > without > >>any > problems. > > >> > > > >> > > >>There is fundamental differences between em(4) and vr(4). The > > >>vr(4) for VT6105M takes advantage of perfect multicast filtering > > >>feature which is not present on all em(4) interface. Perfect > > >>multicast filtering can reduce unwanted multicast traffics such > > >>that it could save a lot of CPU cycles. The downside is that vr(4) > > >>cannot accept multicast frames for a multicast group without > > >>joining the multicast group first. > > >>For multicast routing purpose I guess 'options MROUTING' kernel > > >>option should be enabled to accept all multicast frames. > > >>Does your kernel have that option? > > > > > >No it has not. I will create such a beast and return with stories. > > > > > > > > > I have tried with 'options MROUTING' and it didn't work. > > > > Did I miss something? Do I have to install and run mrouted also? > > > > It seems like maybe the first two packages are accepted after > registration > as I don't lose the routes until after about 6 min > uptime. But to get > further updates, I need the interfaces in promisc. > > > > So, next step? > > > > Can you see ALLMULTI flag from the output of "ifconfig vr0"? > No -> # ifconfig vr0 vr0: flags=8943 metric 0 mtu 1500 options=284b ether 00:00:24:c8:e0:9c inet xxx.xxx.xxx.xxx netmask 0xfffffff8 broadcast xxx.xxx.xxx.yyy media: Ethernet autoselect (100baseTX ) status: active /glz From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 08:58:27 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 33EB91065676; Wed, 10 Dec 2008 08:58:27 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forwards4.yandex.ru (forwards4.yandex.ru [77.88.32.20]) by mx1.freebsd.org (Postfix) with ESMTP id A22E98FC29; Wed, 10 Dec 2008 08:58:26 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp5.yandex.ru (smtp5.yandex.ru [77.88.32.24]) by forwards4.yandex.ru (Yandex) with ESMTP id 9A41D1935FE; Wed, 10 Dec 2008 11:58:24 +0300 (MSK) Received: from ns.kirov.so-cdu.ru ([77.72.136.145]:19191 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S6144119AbYLJI6P (ORCPT + 3 others); Wed, 10 Dec 2008 11:58:15 +0300 X-Yandex-Spam: 1 X-Yandex-Front: smtp5 X-Yandex-TimeMark: 1228899495 X-BornDate: 1137963600 X-Yandex-Karma: 0 X-Yandex-KarmaStatus: 0 X-MsgDayCount: 4 X-Comment: RFC 2476 MSA function at smtp5.yandex.ru logged sender identity as: bu7cher Message-ID: <493F84A4.1080308@yandex.ru> Date: Wed, 10 Dec 2008 11:58:12 +0300 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: Victor Balada Diaz References: <20081209185236.GA1320@alf.bsdes.net> In-Reply-To: <20081209185236.GA1320@alf.bsdes.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org, =?UTF-8?B?U8O4?= =?UTF-8?B?cmVuIFNjaG1pZHQ=?= Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 08:58:27 -0000 Victor Balada Diaz wrote: > Digging at linux source code i've found that they do some special things > for this chipset that i've been unable to find on our code. This is > linux code for my chipset: > > 371 AHCI_HFLAGS (AHCI_HFLAG_IGN_SERR_INTERNAL | > 372 AHCI_HFLAG_32BIT_ONLY | AHCI_HFLAG_NO_MSI | > 373 AHCI_HFLAG_SECT255), > > File and the rest of the code in here[3]. > > As i saw AHCI_HFLAG_NO_MSI i tried doing the easiest thing i could > think of, switching MSI and MSI-x off for the whole system, so > i added to /boot/loader.conf this tunables: FreeBSD's ata(4) driver doesn't support MSI. This flag in linux's libata used in if ((hpriv->flags & AHCI_HFLAG_NO_MSI) || pci_enable_msi(pdev)) pci_intx(pdev, 1); In FreeBSD's code we have the same: /* enable PCI interrupt */ pci_write_config(dev, PCIR_COMMAND, pci_read_config(dev, PCIR_COMMAND, 2) & ~0x0400, 2); AHCI_HFLAG_IGN_SERR_INTERNAL flag targeted to ignore SERR_INTERNAL errors. FreeBSD's ata(4) driver ignores they too. AHCI_HFLAG_32BIT_ONLY flag limits to use 32-bit DMA only. If AHCI CAP register reports that controller supports 64-bit DMA driver will use 64-bit. So i think there can be added one quirk for you, but i'm not sure that problem is here.. AHCI_HFLAG_SECT255 flag limits I/O operation to 255 sectors, FreeBSD uses 128-limit by default. -- WBR, Andrey V. Elsukov From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 08:59:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 49B8B1065677; Wed, 10 Dec 2008 08:59:38 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.bsdes.net (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.freebsd.org (Postfix) with ESMTP id DD4948FC12; Wed, 10 Dec 2008 08:59:37 +0000 (UTC) (envelope-from victor@bsdes.net) Received: by alf.bsdes.net (Postfix, from userid 1001) id 5382C119CF7; Wed, 10 Dec 2008 09:59:35 +0100 (CET) Date: Wed, 10 Dec 2008 09:59:35 +0100 From: Victor Balada Diaz To: Pyun YongHyeon Message-ID: <20081210085934.GB1320@alf.bsdes.net> References: <20081209185236.GA1320@alf.bsdes.net> <20081210061226.GC37837@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20081210061226.GC37837@cdnetworks.co.kr> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 08:59:38 -0000 On Wed, Dec 10, 2008 at 03:12:26PM +0900, Pyun YongHyeon wrote: > On Tue, Dec 09, 2008 at 07:52:37PM +0100, Victor Balada Diaz wrote: > > Hello, > > > > I got various machines[1] at hetzner.de and I've been having problems > > with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've > > been trying to narrow the problem so someone more knowledgeable than me > > is able to fix it. This mail is an other attempt to ask a question > > with regards ATA code to see if this time i got something. > > > > For the ones that don't actually know what happened: > > > > With FreeBSD 7.0 -RELEASE for amd64 and default kernel > > the system shared re0 interrupt with OHCI and this caused > > re(4) to corrupt packets and create interrupt storms. Tried > > re(4) in 7.0-RELEASE had bus_dma(9) bug which could be easily > triggered on systems with > 4GB memory. But I dont' know whether > this is related with interrupt storms. > > > updating to 7.1 -BETA2 and still had some problems with it. > > > > I've opened the PR kern/128287[2] and Remko quickly answered > > with a workaround: that workaround was removing USB support from > > my kernel. I did it and re(4) wasn't sharing interrupts anylonger, > > and the interrupt storms were gone. Now sometime later the interface > > goes up and down from time to time, but less often. Also sometimes > > the machine losts the network interface but continues to work. > > > > It seems that your controller supports MSI so you can set a tunable > hw.re.msi_disable to 0 to enable MSI. With MSI you can remove > interrupt sharing(e.g. add hw.re.msi_disable="0" to > /boot/loader.conf file.) However there were several issues on re(4) > w.r.t MSI so it was off by default. This is undocumented and with sysctl -a i can't find the tunable. Is this a HEAD feature or it's also in 7.1 -BETA2? Should i add hw.re_msi_disable="0" to /boot/loader.conf? This was sharing interrupt with USB, does USB need any special MSI handling or with re using MSI is enough to not share the interrupt? > > > I know it continues to work because some days later i can see that > > it tried to deliver the status reports but was unable to resolve the > > aliases hostnames. I can't ping the machine and i know the network > > is OK. If i reboot the machine everything is working again. > > > > Recently I've made small changes to re(4) which may help to detect > link state change event. Would you try re(4) in HEAD? Can i just drop HEAD's /stable/7/sys/dev/re/ in -STABLE and test that or do i need to test the whole HEAD kernel? Regards. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 09:11:09 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CD37106564A; Wed, 10 Dec 2008 09:11:09 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.bsdes.net (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.freebsd.org (Postfix) with ESMTP id 0DC368FC17; Wed, 10 Dec 2008 09:11:09 +0000 (UTC) (envelope-from victor@bsdes.net) Received: by alf.bsdes.net (Postfix, from userid 1001) id CFDF3119CF7; Wed, 10 Dec 2008 10:11:07 +0100 (CET) Date: Wed, 10 Dec 2008 10:11:07 +0100 From: Victor Balada Diaz To: "Andrey V. Elsukov" Message-ID: <20081210091107.GC1320@alf.bsdes.net> References: <20081209185236.GA1320@alf.bsdes.net> <493F84A4.1080308@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <493F84A4.1080308@yandex.ru> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org, =?iso-8859-1?Q?S=F8ren?= Schmidt Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 09:11:09 -0000 On Wed, Dec 10, 2008 at 11:58:12AM +0300, Andrey V. Elsukov wrote: > Victor Balada Diaz wrote: > >Digging at linux source code i've found that they do some special things > >for this chipset that i've been unable to find on our code. This is > >linux code for my chipset: > > > >371 AHCI_HFLAGS (AHCI_HFLAG_IGN_SERR_INTERNAL | > >372 AHCI_HFLAG_32BIT_ONLY | > >AHCI_HFLAG_NO_MSI | > >373 AHCI_HFLAG_SECT255), > > > >File and the rest of the code in here[3]. > > > >As i saw AHCI_HFLAG_NO_MSI i tried doing the easiest thing i could > >think of, switching MSI and MSI-x off for the whole system, so > >i added to /boot/loader.conf this tunables: > > FreeBSD's ata(4) driver doesn't support MSI. This flag in linux's libata > used in > > if ((hpriv->flags & AHCI_HFLAG_NO_MSI) || pci_enable_msi(pdev)) > pci_intx(pdev, 1); > > In FreeBSD's code we have the same: > > /* enable PCI interrupt */ > pci_write_config(dev, PCIR_COMMAND, > pci_read_config(dev, PCIR_COMMAND, 2) & ~0x0400, 2); > > AHCI_HFLAG_IGN_SERR_INTERNAL flag targeted to ignore SERR_INTERNAL errors. > FreeBSD's ata(4) driver ignores they too. > > AHCI_HFLAG_32BIT_ONLY flag limits to use 32-bit DMA only. > If AHCI CAP register reports that controller supports 64-bit DMA driver > will use 64-bit. > So i think there can be added one quirk for you, but i'm not sure that > problem is here.. > > AHCI_HFLAG_SECT255 flag limits I/O operation to 255 sectors, FreeBSD uses > 128-limit > by default. Thanks for explaining me what the flags do. I'm not skilled enough to create the DMA quirks but if you could give me some patches i'll test them. Also if you have any other idea on what could i test or how can i debug this it would be more than welcome. Thanks. Regards. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 09:55:40 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC8E11065673; Wed, 10 Dec 2008 09:55:40 +0000 (UTC) (envelope-from sos@FreeBSD.ORG) Received: from deepcore.dk (adsl.deepcore.dk [87.63.29.106]) by mx1.freebsd.org (Postfix) with ESMTP id 29DF68FC13; Wed, 10 Dec 2008 09:55:39 +0000 (UTC) (envelope-from sos@FreeBSD.ORG) Received: from [172.18.2.117] (axiell-gw1.novi.dk [77.243.61.137]) by deepcore.dk (8.14.3/8.14.2) with ESMTP id mBA9tZ1O029537; Wed, 10 Dec 2008 10:55:36 +0100 (CET) (envelope-from sos@FreeBSD.ORG) Message-Id: From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= To: Victor Balada Diaz In-Reply-To: <20081210091107.GC1320@alf.bsdes.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v929.2) Date: Wed, 10 Dec 2008 10:55:35 +0100 References: <20081209185236.GA1320@alf.bsdes.net> <493F84A4.1080308@yandex.ru> <20081210091107.GC1320@alf.bsdes.net> X-Mailer: Apple Mail (2.929.2) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (deepcore.dk [87.63.29.106]); Wed, 10 Dec 2008 10:55:36 +0100 (CET) Cc: "Andrey V. Elsukov" , freebsd-stable@FreeBSD.ORG, freebsd-amd64@FreeBSD.ORG Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 09:55:40 -0000 On 10Dec, 2008, at 10:11 , Victor Balada Diaz wrote: > > Thanks for explaining me what the flags do. I'm not skilled enough =20 > to create > the DMA quirks but if you could give me some patches i'll test them. =20= > Also > if you have any other idea on what could i test or how can i debug =20 > this > it would be more than welcome. Comment out the following two lines in ata_ahci_dmainit(): if (ATA_INL(ctlr->r_res2, ATA_AHCI_CAP) & ATA_AHCI_CAP_64BIT) ch->dma->max_address =3D BUS_SPACE_MAXADDR; And you will not use 64bit DMA even if the chipset supports it. =20 However I have not seen any chipsets supporting this fail, YMMV as =20 usual :) -S=F8ren From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 10:28:15 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B039A1065678 for ; Wed, 10 Dec 2008 10:28:15 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229]) by mx1.freebsd.org (Postfix) with ESMTP id 727CE8FC19 for ; Wed, 10 Dec 2008 10:28:15 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id f9so1630122rvb.5 for ; Wed, 10 Dec 2008 02:28:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=V4t22znMbAxNdMDLmK/8B6oe+dOwJ4C2xPuAepc2ONk=; b=ihCEW8SEoPPGvDNO5mZl1Ulal6UMSlfu2H+w8WSoZSfVzW+1TSgVAPKqIZfKjKh9iu pPHgX7993bo3u8M0LKk4ThgUdDcSu+HxQKiWbV0bEPiYxDOd50lZruzULVyv1xIhtieI 5PdOPujiAKQuVy/2y9qHyjE8OAum9qvQ0590E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=o03HV45TzzGHo2KwPoDJLIv2whfTnysWKpO42sXPETH59CSGY96em7ZSemeYB8fMPw P+jccPgyvbh05s+7deiS4sMg9h+1lfy93hhJ27khdWZrwO/keDB9FL4yKO5F5ew3vauy C2wa9KAUM0xUr2Lav+neYLO5LdVc4ZLqFNq1w= Received: by 10.141.87.13 with SMTP id p13mr570374rvl.286.1228904895217; Wed, 10 Dec 2008 02:28:15 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id l31sm2452342rvb.2.2008.12.10.02.28.12 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 10 Dec 2008 02:28:14 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id mBAAS4bq039891 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Dec 2008 19:28:04 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id mBAAS1Yl039890; Wed, 10 Dec 2008 19:28:01 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 10 Dec 2008 19:28:00 +0900 From: Pyun YongHyeon To: Victor Balada Diaz Message-ID: <20081210102800.GH37837@cdnetworks.co.kr> References: <20081209185236.GA1320@alf.bsdes.net> <20081210061226.GC37837@cdnetworks.co.kr> <20081210085934.GB1320@alf.bsdes.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081210085934.GB1320@alf.bsdes.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 10:28:15 -0000 On Wed, Dec 10, 2008 at 09:59:35AM +0100, Victor Balada Diaz wrote: > On Wed, Dec 10, 2008 at 03:12:26PM +0900, Pyun YongHyeon wrote: > > On Tue, Dec 09, 2008 at 07:52:37PM +0100, Victor Balada Diaz wrote: > > > Hello, > > > > > > I got various machines[1] at hetzner.de and I've been having problems > > > with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've > > > been trying to narrow the problem so someone more knowledgeable than me > > > is able to fix it. This mail is an other attempt to ask a question > > > with regards ATA code to see if this time i got something. > > > > > > For the ones that don't actually know what happened: > > > > > > With FreeBSD 7.0 -RELEASE for amd64 and default kernel > > > the system shared re0 interrupt with OHCI and this caused > > > re(4) to corrupt packets and create interrupt storms. Tried > > > > re(4) in 7.0-RELEASE had bus_dma(9) bug which could be easily > > triggered on systems with > 4GB memory. But I dont' know whether > > this is related with interrupt storms. > > > > > updating to 7.1 -BETA2 and still had some problems with it. > > > > > > I've opened the PR kern/128287[2] and Remko quickly answered > > > with a workaround: that workaround was removing USB support from > > > my kernel. I did it and re(4) wasn't sharing interrupts anylonger, > > > and the interrupt storms were gone. Now sometime later the interface > > > goes up and down from time to time, but less often. Also sometimes > > > the machine losts the network interface but continues to work. > > > > > > > It seems that your controller supports MSI so you can set a tunable > > hw.re.msi_disable to 0 to enable MSI. With MSI you can remove > > interrupt sharing(e.g. add hw.re.msi_disable="0" to > > /boot/loader.conf file.) However there were several issues on re(4) > > w.r.t MSI so it was off by default. > > This is undocumented and with sysctl -a i can't find the tunable. Is this > a HEAD feature or it's also in 7.1 -BETA2? Should i add Yeah it's an undocmented feature. But most drivers written by me have similar kobs. Both HEAD and stable/7 including 7.1 BETA2 have the tunable. > hw.re_msi_disable="0" to /boot/loader.conf? ^^^^^^^^^^^^^^^^^^^^^ Shoule be hw.re.msi_disable="0" > Yes, just add it to /boot/loader.conf. Note, you should not disable system-wide MSI control(e.g. hw.pci.enable_msi == 1). > This was sharing interrupt with USB, does USB need any special MSI handling > or with re using MSI is enough to not share the interrupt? If re(4) can use MSI, you don't need to worry about interrupt sharing with USB. Check the output of "vmstat -i". You normally get an irq256 or higher for MSI enabled driver. > > > > > > > I know it continues to work because some days later i can see that > > > it tried to deliver the status reports but was unable to resolve the > > > aliases hostnames. I can't ping the machine and i know the network > > > is OK. If i reboot the machine everything is working again. > > > > > > > Recently I've made small changes to re(4) which may help to detect > > link state change event. Would you try re(4) in HEAD? > > Can i just drop HEAD's /stable/7/sys/dev/re/ in -STABLE and test that Yes, you can. It should build without problems. Just replace re(4) on stable/7 with HEAD version. > or do i need to test the whole HEAD kernel? > No you don't have to that. -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 11:32:28 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44F8B1065670; Wed, 10 Dec 2008 11:32:28 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.bsdes.net (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.freebsd.org (Postfix) with ESMTP id 94C8C8FC12; Wed, 10 Dec 2008 11:32:27 +0000 (UTC) (envelope-from victor@bsdes.net) Received: by alf.bsdes.net (Postfix, from userid 1001) id 16175119CF7; Wed, 10 Dec 2008 12:32:26 +0100 (CET) Date: Wed, 10 Dec 2008 12:32:25 +0100 From: Victor Balada Diaz To: Pyun YongHyeon Message-ID: <20081210113225.GD1320@alf.bsdes.net> References: <20081209185236.GA1320@alf.bsdes.net> <20081210061226.GC37837@cdnetworks.co.kr> <20081210085934.GB1320@alf.bsdes.net> <20081210102800.GH37837@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20081210102800.GH37837@cdnetworks.co.kr> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 11:32:28 -0000 On Wed, Dec 10, 2008 at 07:28:00PM +0900, Pyun YongHyeon wrote: > On Wed, Dec 10, 2008 at 09:59:35AM +0100, Victor Balada Diaz wrote: > > On Wed, Dec 10, 2008 at 03:12:26PM +0900, Pyun YongHyeon wrote: > > > On Tue, Dec 09, 2008 at 07:52:37PM +0100, Victor Balada Diaz wrote: > > > > Hello, > > > > > > > > I got various machines[1] at hetzner.de and I've been having problems > > > > with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've > > > > been trying to narrow the problem so someone more knowledgeable than me > > > > is able to fix it. This mail is an other attempt to ask a question > > > > with regards ATA code to see if this time i got something. > > > > > > > > For the ones that don't actually know what happened: > > > > > > > > With FreeBSD 7.0 -RELEASE for amd64 and default kernel > > > > the system shared re0 interrupt with OHCI and this caused > > > > re(4) to corrupt packets and create interrupt storms. Tried > > > > > > re(4) in 7.0-RELEASE had bus_dma(9) bug which could be easily > > > triggered on systems with > 4GB memory. But I dont' know whether > > > this is related with interrupt storms. > > > > > > > updating to 7.1 -BETA2 and still had some problems with it. > > > > > > > > I've opened the PR kern/128287[2] and Remko quickly answered > > > > with a workaround: that workaround was removing USB support from > > > > my kernel. I did it and re(4) wasn't sharing interrupts anylonger, > > > > and the interrupt storms were gone. Now sometime later the interface > > > > goes up and down from time to time, but less often. Also sometimes > > > > the machine losts the network interface but continues to work. > > > > > > > > > > It seems that your controller supports MSI so you can set a tunable > > > hw.re.msi_disable to 0 to enable MSI. With MSI you can remove > > > interrupt sharing(e.g. add hw.re.msi_disable="0" to > > > /boot/loader.conf file.) However there were several issues on re(4) > > > w.r.t MSI so it was off by default. > > > > This is undocumented and with sysctl -a i can't find the tunable. Is this > > a HEAD feature or it's also in 7.1 -BETA2? Should i add > > Yeah it's an undocmented feature. But most drivers written by me > have similar kobs. Both HEAD and stable/7 including 7.1 BETA2 have > the tunable. I think it could be great if you could document it or at least show it by default when you do sysctl -ad with a small description. > > > hw.re_msi_disable="0" to /boot/loader.conf? > ^^^^^^^^^^^^^^^^^^^^^ > Shoule be hw.re.msi_disable="0" > > > > Yes, just add it to /boot/loader.conf. Note, you should not disable > system-wide MSI control(e.g. hw.pci.enable_msi == 1). > > > This was sharing interrupt with USB, does USB need any special MSI handling > > or with re using MSI is enough to not share the interrupt? > > If re(4) can use MSI, you don't need to worry about interrupt > sharing with USB. Check the output of "vmstat -i". You normally get > an irq256 or higher for MSI enabled driver. > > > > > > > > > > > > I know it continues to work because some days later i can see that > > > > it tried to deliver the status reports but was unable to resolve the > > > > aliases hostnames. I can't ping the machine and i know the network > > > > is OK. If i reboot the machine everything is working again. > > > > > > > > > > Recently I've made small changes to re(4) which may help to detect > > > link state change event. Would you try re(4) in HEAD? > > > > Can i just drop HEAD's /stable/7/sys/dev/re/ in -STABLE and test that > > Yes, you can. It should build without problems. Just replace re(4) on > stable/7 with HEAD version. > > > or do i need to test the whole HEAD kernel? > > > > No you don't have to that. Backporting the changes i've found that it didn't compile so in the end i got from HEAD the following files: base/head/sys/dev/re/if_re.c base/head/sys/pci/if_rl.c base/head/sys/pci/if_rlreg.h After that i've recompiled 7.1 -BETA2 GENERIC kernel and enabled the knob you suggested in /boot/loader.conf. With the new kernel and MSI the interrupts are like this: # vmstat -i interrupt total rate irq9: acpi0 1 0 irq16: ohci0 1 0 irq17: ohci1 ohci3 1 0 irq18: ohci2 ohci4 1 0 irq22: atapci0 19215 15 cpu0: timer 2502718 1998 irq256: re0 4967726 3967 cpu1: timer 2502525 1998 Total 9992188 7980 The high interrupt numbers are because i've been running iperf to check everything it's fine, not because of interrupt storms. So far i didn't find any interrupt storms related to USB or re(4) driver but while doing the tests i've found this error: re0: watchdog timeout (missed Tx interrupts) -- recovering This didn't create any error on the interfaces (netstat -i). Also i didn't see any problem with interfaces going up and down, but that usually happen after some hours of uptime, so i'll let you know if the error happens again. As these seems to improve the current situation, is there any chance of merging -current driver in 7.1 before release? Thanks! Regards. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 12:07:29 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 62CDA1065679 for ; Wed, 10 Dec 2008 12:07:29 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.230]) by mx1.freebsd.org (Postfix) with ESMTP id 296F58FC12 for ; Wed, 10 Dec 2008 12:07:29 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so366261rvf.43 for ; Wed, 10 Dec 2008 04:07:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=6D+Ra47muEmnYAQ1QZRzcDlC3iLHShC6NSG1/RcIdBs=; b=U8Y6GB/iw1bYN+E+oYVa9V8o9QXf79d7pmkkMhN3wSFwXTFZHKBdtXVKZioT+bwypU ncdj1z0bDNQOkLz1BCPMNhG7mXUV1rWIgTQ0Cw5nzrpfbUSs8O/j9mfdBiEk0yq28ExE p7JK+sVQjHGX4LOEyN8+/wQSYc+GQ4ryqSg4w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=A+yKhLEZ7T2gZxYLj5Q3My37S6th2a79GKckzBDDbJg4EnPjeqqBoLsrCu7F/KKigq XsofD91ahm5ywzPIdRkr2nLZCZZZyCIklR/aaT+SoybmqVNNv29PjoaH1vzFRZDYfTYJ GiyEeE5kE89Xc+qBW4mNh5Sq+mJfPj0/slJvU= Received: by 10.141.106.14 with SMTP id i14mr630953rvm.143.1228910848644; Wed, 10 Dec 2008 04:07:28 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id l31sm2674990rvb.2.2008.12.10.04.07.25 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 10 Dec 2008 04:07:27 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id mBAC7KmS040243 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Dec 2008 21:07:20 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id mBAC7J55040242; Wed, 10 Dec 2008 21:07:19 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 10 Dec 2008 21:07:19 +0900 From: Pyun YongHyeon To: Victor Balada Diaz Message-ID: <20081210120719.GK37837@cdnetworks.co.kr> References: <20081209185236.GA1320@alf.bsdes.net> <20081210061226.GC37837@cdnetworks.co.kr> <20081210085934.GB1320@alf.bsdes.net> <20081210102800.GH37837@cdnetworks.co.kr> <20081210113225.GD1320@alf.bsdes.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081210113225.GD1320@alf.bsdes.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 12:07:29 -0000 On Wed, Dec 10, 2008 at 12:32:25PM +0100, Victor Balada Diaz wrote: > On Wed, Dec 10, 2008 at 07:28:00PM +0900, Pyun YongHyeon wrote: > > On Wed, Dec 10, 2008 at 09:59:35AM +0100, Victor Balada Diaz wrote: > > > On Wed, Dec 10, 2008 at 03:12:26PM +0900, Pyun YongHyeon wrote: > > > > On Tue, Dec 09, 2008 at 07:52:37PM +0100, Victor Balada Diaz wrote: > > > > > Hello, > > > > > > > > > > I got various machines[1] at hetzner.de and I've been having problems > > > > > with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've > > > > > been trying to narrow the problem so someone more knowledgeable than me > > > > > is able to fix it. This mail is an other attempt to ask a question > > > > > with regards ATA code to see if this time i got something. > > > > > > > > > > For the ones that don't actually know what happened: > > > > > > > > > > With FreeBSD 7.0 -RELEASE for amd64 and default kernel > > > > > the system shared re0 interrupt with OHCI and this caused > > > > > re(4) to corrupt packets and create interrupt storms. Tried > > > > > > > > re(4) in 7.0-RELEASE had bus_dma(9) bug which could be easily > > > > triggered on systems with > 4GB memory. But I dont' know whether > > > > this is related with interrupt storms. > > > > > > > > > updating to 7.1 -BETA2 and still had some problems with it. > > > > > > > > > > I've opened the PR kern/128287[2] and Remko quickly answered > > > > > with a workaround: that workaround was removing USB support from > > > > > my kernel. I did it and re(4) wasn't sharing interrupts anylonger, > > > > > and the interrupt storms were gone. Now sometime later the interface > > > > > goes up and down from time to time, but less often. Also sometimes > > > > > the machine losts the network interface but continues to work. > > > > > > > > > > > > > It seems that your controller supports MSI so you can set a tunable > > > > hw.re.msi_disable to 0 to enable MSI. With MSI you can remove > > > > interrupt sharing(e.g. add hw.re.msi_disable="0" to > > > > /boot/loader.conf file.) However there were several issues on re(4) > > > > w.r.t MSI so it was off by default. > > > > > > This is undocumented and with sysctl -a i can't find the tunable. Is this > > > a HEAD feature or it's also in 7.1 -BETA2? Should i add > > > > Yeah it's an undocmented feature. But most drivers written by me > > have similar kobs. Both HEAD and stable/7 including 7.1 BETA2 have > > the tunable. > > I think it could be great if you could document it or at least > show it by default when you do sysctl -ad with a small description. > If MSI worked as expected I would have documented it as I did in msk(4)/nfe(4)/ale(4)/age(4)/jme(4) etc. Using MSI on RealTek does not seem to stable. I tried hard to fix that but some users still reported watchdog timeouts. Working without documentation and hardware also made it hard to complete the work. This was the main reason why MSI was disabled on re(4). > > > > > hw.re_msi_disable="0" to /boot/loader.conf? > > ^^^^^^^^^^^^^^^^^^^^^ > > Shoule be hw.re.msi_disable="0" > > > > > > > Yes, just add it to /boot/loader.conf. Note, you should not disable > > system-wide MSI control(e.g. hw.pci.enable_msi == 1). > > > > > This was sharing interrupt with USB, does USB need any special MSI handling > > > or with re using MSI is enough to not share the interrupt? > > > > If re(4) can use MSI, you don't need to worry about interrupt > > sharing with USB. Check the output of "vmstat -i". You normally get > > an irq256 or higher for MSI enabled driver. > > > > > > > > > > > > > > > > > I know it continues to work because some days later i can see that > > > > > it tried to deliver the status reports but was unable to resolve the > > > > > aliases hostnames. I can't ping the machine and i know the network > > > > > is OK. If i reboot the machine everything is working again. > > > > > > > > > > > > > Recently I've made small changes to re(4) which may help to detect > > > > link state change event. Would you try re(4) in HEAD? > > > > > > Can i just drop HEAD's /stable/7/sys/dev/re/ in -STABLE and test that > > > > Yes, you can. It should build without problems. Just replace re(4) on > > stable/7 with HEAD version. > > > > > or do i need to test the whole HEAD kernel? > > > > > > > No you don't have to that. > > Backporting the changes i've found that it didn't compile so in > the end i got from HEAD the following files: > > base/head/sys/dev/re/if_re.c > base/head/sys/pci/if_rl.c > base/head/sys/pci/if_rlreg.h > Ah,, sorry about that. Recently there was some changes. I forgot that. > After that i've recompiled 7.1 -BETA2 GENERIC kernel and enabled > the knob you suggested in /boot/loader.conf. > > With the new kernel and MSI the interrupts are like this: > > # vmstat -i > interrupt total rate > irq9: acpi0 1 0 > irq16: ohci0 1 0 > irq17: ohci1 ohci3 1 0 > irq18: ohci2 ohci4 1 0 > irq22: atapci0 19215 15 > cpu0: timer 2502718 1998 > irq256: re0 4967726 3967 > cpu1: timer 2502525 1998 > Total 9992188 7980 > > The high interrupt numbers are because i've been running iperf to > check everything it's fine, not because of interrupt storms. So far > i didn't find any interrupt storms related to USB or re(4) driver > but while doing the tests i've found this error: > > re0: watchdog timeout (missed Tx interrupts) -- recovering > > This didn't create any error on the interfaces (netstat -i). > This was triggered by new code in HEAD. It indicates re(4) missed Tx completion interrupt. It could be a bug in driver or hardware bug. If you can live with that message you can safely ignore that as now re(4) does not reinitialize the hardware if it detect missing Tx completion interrupt. > Also i didn't see any problem with interfaces going up and down, > but that usually happen after some hours of uptime, so i'll let > you know if the error happens again. > Ok. > As these seems to improve the current situation, is there any > chance of merging -current driver in 7.1 before release? > I think re(4) in HEAD needs more testing. As you might know RealTek produced too many chipsets. :-( -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 12:11:01 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 61A3E1065673 for ; Wed, 10 Dec 2008 12:11:01 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from phoebe.cse.buffalo.edu (phoebe.cse.buffalo.edu [128.205.32.89]) by mx1.freebsd.org (Postfix) with ESMTP id 351298FC16 for ; Wed, 10 Dec 2008 12:11:00 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from [128.205.32.76] (bauer.cse.buffalo.edu [128.205.32.76]) (authenticated bits=0) by phoebe.cse.buffalo.edu (8.14.1/8.13.7) with ESMTP id mBACAqas097654 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Dec 2008 07:10:53 -0500 (EST) (envelope-from kensmith@cse.buffalo.edu) From: Ken Smith To: Kevin Day In-Reply-To: <55FAF790-6169-42BE-9285-1217C3284CDB@dragondata.com> References: <1228753517.56532.25.camel@bauer.cse.buffalo.edu> <55FAF790-6169-42BE-9285-1217C3284CDB@dragondata.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-sByCOEQUj+W5+mP05QY1" Organization: U. Buffalo CSE Department Date: Wed, 10 Dec 2008 07:10:52 -0500 Message-Id: <1228911052.57305.15.camel@bauer.cse.buffalo.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port X-DCC-Buffalo.EDU-Metrics: phoebe.cse.buffalo.edu 1029; Body=0 Fuz1=0 Fuz2=0 X-Spam-Status: No, score=-4.0 required=5.0 tests=RCVD_IN_DNSWL_MED autolearn=failed version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on phoebe.cse.buffalo.edu Cc: freebsd-stable Stable Subject: Re: visibility of release process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Dec 2008 12:11:01 -0000 --=-sByCOEQUj+W5+mP05QY1 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2008-12-09 at 15:19 -0600, Kevin Day wrote: [ Other points were not ignored, just nothing to really say about them other than "Yes" and/or "Will try", etc. ] > * More notice to hubs@ before the release notes are generated. The =20 > releases always come with a "At the time of this writing, these =20 > mirrors have the full distribution" list. If it was announced to us =20 > mirror operators before that list is made, we could make sure we were =20 > synced in time to be included. Maybe even a semi-shaming of "These =20 > mirrors do not appear to have the required bits:". The difference in =20 > bandwidth we see on our public mirror (ftp3.us) is pretty extreme if =20 > we're listed there or not, which seems to be a 50/50 coin-toss on the =20 > last few releases. I'm honestly not sure why, since we can easily pull =20 > >50mbps from ftp-master. I have absolutely no clue how to fairly handle what needs to be done with this so, as you noted, its something of a coin toss at the moment. The issue is that the Release Announcement needs to include a list of FTP sites, but the list can't be "too long" (as in can't be every mirror site we've got). The Release Announcement should be relatively short and to the point. An exhaustive list of every mirror is a bit too much in that regard. Ideally we'd just say "Its available on a mirror site, get it from there.". But people want easy so we need to include something to click on. With the 7.0 release I tried giving just the URL of the primary site (ftp.freebsd.org) but that proved people don't just want easy - they're lazy. For the most part they just clicked on that and didn't look around for a mirror. Hence your observation about the difference in bandwidth when you're listed versus when you're not listed. Since we don't have any sort of "click here and automagically land on a nice fast mirror real close to you" I basically make a quick survey of some FTP sites shooting for having several of the primary mirror sites (ftpX.freebsd.org) and a sampling of geographically diverse country mirrors (ftpX.au.freebsd.org, ftpX.ru.freebsd.org, etc.). If you're one of the ones I check and if you've got the right sparc64 checksum file (I'm looking for sites that carry everything, and since sparc64 is usually the last to get loaded on ftp-master ...) you make the list. Sorry, I know it sucks. Until we've got something automagic I'm not quite sure how to fairly handle having a list that's not "too long" for a release announcement but still providing a reasonable starting point for people who want something to click on in the release announcement. --=20 Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | --=-sByCOEQUj+W5+mP05QY1 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkk/scMACgkQ/G14VSmup/b9nwCdGDBjTDQX5FaiivcnvwjJYWNI hd4AniLV9yt1BEJMusr2zp8kWcB1fNcZ =VoWo -----END PGP SIGNATURE----- --=-sByCOEQUj+W5+mP05QY1-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 12:18:05 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D0E911065689; Wed, 10 Dec 2008 12:18:05 +0000 (UTC) (envelope-from arnaud.houdelette@tzim.net) Received: from golanth.tzim.net (unknown [IPv6:2001:41d0:1:d91f:21c:c0ff:fe4b:cf32]) by mx1.freebsd.org (Postfix) with ESMTP id 734678FC19; Wed, 10 Dec 2008 12:18:05 +0000 (UTC) (envelope-from arnaud.houdelette@tzim.net) Received: from path-wifi.irisa.fr ([131.254.64.80]) by golanth.tzim.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LAO0w-0008yc-7H; Wed, 10 Dec 2008 13:18:02 +0100 Message-ID: <493FB378.5030106@tzim.net> Date: Wed, 10 Dec 2008 13:18:00 +0100 From: Arnaud Houdelette User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) MIME-Version: 1.0 To: Victor Balada Diaz References: <20081209185236.GA1320@alf.bsdes.net> In-Reply-To: <20081209185236.GA1320@alf.bsdes.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Authenticated-User: tzim@tzim.net X-Authenticator: plain Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 12:18:06 -0000 Victor Balada Diaz a écrit : > Hello, > > I got various machines[1] at hetzner.de and I've been having problems > with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've > been trying to narrow the problem so someone more knowledgeable than me > is able to fix it. This mail is an other attempt to ask a question > with regards ATA code to see if this time i got something. > > For the ones that don't actually know what happened: > > With FreeBSD 7.0 -RELEASE for amd64 and default kernel > the system shared re0 interrupt with OHCI and this caused > re(4) to corrupt packets and create interrupt storms. Tried > updating to 7.1 -BETA2 and still had some problems with it. > > I've opened the PR kern/128287[2] and Remko quickly answered > with a workaround: that workaround was removing USB support from > my kernel. I did it and re(4) wasn't sharing interrupts anylonger, > and the interrupt storms were gone. Now sometime later the interface > goes up and down from time to time, but less often. Also sometimes > the machine losts the network interface but continues to work. > > I know it continues to work because some days later i can see that > it tried to deliver the status reports but was unable to resolve the > aliases hostnames. I can't ping the machine and i know the network > is OK. If i reboot the machine everything is working again. > > When switched from 7.0 to 7.1 BETA2 i also found that under load > after some hours the machine created interrupt storms on ATA disks. > > Digging at linux source code i've found that they do some special things > for this chipset that i've been unable to find on our code. This is > linux code for my chipset: > > 371 AHCI_HFLAGS (AHCI_HFLAG_IGN_SERR_INTERNAL | > 372 AHCI_HFLAG_32BIT_ONLY | AHCI_HFLAG_NO_MSI | > 373 AHCI_HFLAG_SECT255), > > File and the rest of the code in here[3]. > > As i saw AHCI_HFLAG_NO_MSI i tried doing the easiest thing i could > think of, switching MSI and MSI-x off for the whole system, so > i added to /boot/loader.conf this tunables: > > hw.pci.enable_msix="0" > hw.pci.enable_msi="0" > > And then rebooted the machine. After various hours of doing almost nothing > i've found that the machine answered ping but was unable to answer any > request (eg, ssh, nagios nrpe, etc). The machine recovered itself after > some minutes and when i was able to ssh into i saw the following in dmesg: > > ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly > ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly > ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly > ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly > ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly > ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=1463123158 > > and a lot more errors like that. I didn't get this errors with MSI enabled. > I see WRITE_DMA48 and in linux code i saw AHCI_HFLAG_32BIT_ONLY which is later > used for DMA related things. Could someone who is more knowledgeable check > if we're doing the right thing? > > I've attached verbose dmesg of a machine that's like this one with > 7.1 -BETA2, MSI enabled and GENERIC kernel minus USB and firewrire. > > Also, please, could someone give me a hand on how could i continue debugging > this interrupt issues? I'm a bit lost and digging code and posting each > time i think i've found something is not going to go anywhere. > > I would also like to say that i've seen reports of this kind of problems > on amd64 machines in the lists since various years ago, so i don't think > this is just a problem with this BIOS/motherboard (MSI K9AG Neo2 Digital) > on the lists > > > Thanks in advance for any help. > Regards. > > > [1]: http://www.hetzner.de/hosting/produkte_rootserver/ds7000/ > [2]: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/128287 > [3]: http://fxr.watson.org/fxr/source/drivers/ata/ahci.c?v=linux-2.6#L369 > Sorry I didn't take the time to read all the thread, but I got similar problem with the same IXP600 chipset. Only it was'nt with a Realtek NIC (re) but with a Ralink wireless one. The simptoms where similar : interrupt 22 was shared between the sata controler and the wireless card. And I got Interrupt Storms at random times when using the wireless network. No problem since I removed the ral(4) NIC (got a real access point now). You might not want to point the finger at the re(4) driver too fast. Arnaud Houdelette From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 12:25:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2128E106564A; Wed, 10 Dec 2008 12:25:43 +0000 (UTC) (envelope-from oliver@nemesis.charlie.mouhaha.de) Received: from nemesis.charlie.mouhaha.de (nemesis.charlie.mouhaha.de [78.47.10.193]) by mx1.freebsd.org (Postfix) with ESMTP id A89DD8FC35; Wed, 10 Dec 2008 12:25:42 +0000 (UTC) (envelope-from oliver@nemesis.charlie.mouhaha.de) Received: from localhost (nemesis.charlie.mouhaha.de [78.47.10.193]) by nemesis.charlie.mouhaha.de (Postfix) with ESMTP id 1B9FC35FE6; Wed, 10 Dec 2008 12:08:52 +0000 (GMT) X-Virus-Scanned: amavisd-new at mouhaha.de Received: from nemesis.charlie.mouhaha.de ([78.47.10.193]) by localhost (nemesis.charlie.mouhaha.de [78.47.10.193]) (amavisd-new, port 10024) with ESMTP id R-1fHWpc-Y1B; Wed, 10 Dec 2008 12:08:40 +0000 (GMT) Received: by nemesis.charlie.mouhaha.de (Postfix, from userid 1001) id ACC1335CEF; Wed, 10 Dec 2008 12:08:40 +0000 (GMT) Date: Wed, 10 Dec 2008 12:08:40 +0000 From: Oliver Peter To: Victor Balada Diaz Message-ID: <20081210120840.GA36443@nemesis.frida.mouhaha.de> References: <20081209185236.GA1320@alf.bsdes.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <20081209185236.GA1320@alf.bsdes.net> X-Operating-System: FreeBSD 7.0-RELEASE-p6 amd64 User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 12:25:43 -0000 On Tue, Dec 09, 2008 at 07:52:37PM +0100, Victor Balada Diaz wrote: > Hello, >=20 > I got various machines[1] at hetzner.de and I've been having problems > with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've > been trying to narrow the problem so someone more knowledgeable than me > is able to fix it. This mail is an other attempt to ask a question > with regards ATA code to see if this time i got something. Just want to add a quick note and say that I'm having the same problem with my 7.0-RELEASE-p6/amd64 hetzner machine: http://lists.freebsd.org/pipermail/freebsd-acpi/2008-September/005095.= html I would be happy to test patches as well. Thanks. --=20 Oliver PETER, email: oliver@peter.de.com, ICQ# 113969174 "If it feels good, you're doing something wrong." -- Coach McTavish From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 13:14:54 2008 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 38FCB106564A for ; Wed, 10 Dec 2008 13:14:54 +0000 (UTC) (envelope-from notify-return-stable=FreeBSD.org@returns.groups.yahoo.com) Received: from n33a.bullet.sp1.yahoo.com (n33a.bullet.sp1.yahoo.com [209.131.38.214]) by mx1.freebsd.org (Postfix) with SMTP id 0EA2A8FC1D for ; Wed, 10 Dec 2008 13:14:54 +0000 (UTC) (envelope-from notify-return-stable=FreeBSD.org@returns.groups.yahoo.com) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=lima; d=yahoogroups.com; b=aVqBa8U31tSs1m2jGE0JbctyH0BssqHO2hmXl+MhrCA2iFea1V9n6VzwZk89gL765lQGCB750BtTznRQOpJ/VkA3taL08v8efeSGWcd2nPCxdWekBBXBVLy2762DFmla; Received: from [69.147.65.172] by n33.bullet.sp1.yahoo.com with NNFMP; 10 Dec 2008 13:02:12 -0000 Received: from [69.147.108.101] by t14.bullet.mail.sp1.yahoo.com with NNFMP; 10 Dec 2008 13:02:12 -0000 Date: 10 Dec 2008 13:02:11 -0000 Message-ID: <1228914131.1611.89729.w111@yahoogroups.com> X-Yahoo-Newman-Property: groups-notify From: SKATINGEXTREME Moderator To: stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Subject: Yahoo! Groups: Welcome to SKATINGEXTREME. Visit today! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Dec 2008 13:14:54 -0000 Hello, Thank you for being a subscriber to this list. I hope that you get a chance to check out my web sites. I have one at http://www.howard.net/hilary and one also at http://www.webpost.net/sk/SkatersChoice . I will try to be in the chat room on Thursday evenings. Go to Hilarys Skating Center then if you want to try to chat. I would love to get a lot of skaters out there in a chat. Pass the word and lets find some skaters eh. Thanks, Hilary Complete your Yahoo! Groups account: ---------------------------------------------------------------------- Your email address has been added to the email list of a Yahoo! Group. To gain access to all of your group's web features (previous messages, photos, files, calendar, etc.) and easier control of your message delivery options, we highly recommend that you complete your account by connecting your email address to Yahoo account. It is easy and free. Please visit: http://groups.yahoo.com/convacct?email=stable%40FreeBSD.org&list=SKATINGEXTREME Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 14:00:53 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 090D61065670 for ; Wed, 10 Dec 2008 14:00:53 +0000 (UTC) (envelope-from skip@menantico.com) Received: from vms042pub.verizon.net (vms042pub.verizon.net [206.46.252.42]) by mx1.freebsd.org (Postfix) with ESMTP id DDA318FC0C for ; Wed, 10 Dec 2008 14:00:52 +0000 (UTC) (envelope-from skip@menantico.com) Received: from mx.menantico.com ([71.168.243.250]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0KBN0079MYWV0UE1@vms042.mailsrvcs.net> for freebsd-stable@freebsd.org; Wed, 10 Dec 2008 08:00:32 -0600 (CST) Date: Wed, 10 Dec 2008 09:06:36 -0500 From: Skip Ford In-reply-to: <1228911052.57305.15.camel@bauer.cse.buffalo.edu> To: Ken Smith Message-id: <20081210140636.GA31418@menantico.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline References: <1228753517.56532.25.camel@bauer.cse.buffalo.edu> <55FAF790-6169-42BE-9285-1217C3284CDB@dragondata.com> <1228911052.57305.15.camel@bauer.cse.buffalo.edu> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable , Kevin Day Subject: Re: visibility of release process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Dec 2008 14:00:53 -0000 Ken Smith wrote: > With the 7.0 release I tried giving just the URL > of the primary site (ftp.freebsd.org) but that proved people don't just > want easy - they're lazy. For the most part they just clicked on that > and didn't look around for a mirror. Hence your observation about the > difference in bandwidth when you're listed versus when you're not > listed. Any idea if most of those ISO downloaders are really installing a fresh system or are just updating from a previous release by reinstalling? It seems to me many more people could be using freebsd-update(8) so the announcement really could focus on upgrades rather than fresh installs. I obviously like FreeBSD myself, but how many new users who need to download ISOs really come on board with each new release? The freebsd-update(8) portion of "Updating existing systems" could be the main focus of the announcement, and the "Availability" section and "updating existing systems from source" sections could just contain a link pointing to the web site since (I believe) the number of users needing those should be limited. No FTP listing in the announcement at all. I guess freebsd-update(8) currently has some limitations that make it not so cut-and-dry. But I'm a little confused anyway at this point as to what the long-term plans are. There's a CVS repo, SVN repo which appears to be the way things will be, a "projects" svn repo, a "projects" p4 repo, cvs(1) in base, csup(1) in base which is still being worked on even though there appears to be a slow migration to svn, svn(1) is in ports, there's no SVN repo for the ports tree but there is for src, freebsd-update(8) exists for binary upgrades which seems to be the way of the future for a huge majority of end-users, and yet the official mirrors are missing both the SVN src repo and binary update files. It seems to me the mirrors and release announcement are behind the times by pointing to source upgrades and ISO downloads, or maybe I'm just a little too early. I hope core has a plan for all of this. :) -- Skip From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 14:01:32 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C14311065672; Wed, 10 Dec 2008 14:01:32 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.bsdes.net (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.freebsd.org (Postfix) with ESMTP id B7BFF8FC1B; Wed, 10 Dec 2008 14:01:31 +0000 (UTC) (envelope-from victor@bsdes.net) Received: by alf.bsdes.net (Postfix, from userid 1001) id 437EF119CF8; Wed, 10 Dec 2008 15:01:30 +0100 (CET) Date: Wed, 10 Dec 2008 15:01:30 +0100 From: Victor Balada Diaz To: Oliver Peter Message-ID: <20081210140129.GE1320@alf.bsdes.net> References: <20081209185236.GA1320@alf.bsdes.net> <20081210120840.GA36443@nemesis.frida.mouhaha.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20081210120840.GA36443@nemesis.frida.mouhaha.de> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 14:01:32 -0000 On Wed, Dec 10, 2008 at 12:08:40PM +0000, Oliver Peter wrote: > On Tue, Dec 09, 2008 at 07:52:37PM +0100, Victor Balada Diaz wrote: > > Hello, > > > > I got various machines[1] at hetzner.de and I've been having problems > > with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've > > been trying to narrow the problem so someone more knowledgeable than me > > is able to fix it. This mail is an other attempt to ask a question > > with regards ATA code to see if this time i got something. > > Just want to add a quick note and say that I'm having the same problem > with my 7.0-RELEASE-p6/amd64 hetzner machine: > > http://lists.freebsd.org/pipermail/freebsd-acpi/2008-September/005095.html > > I would be happy to test patches as well. Thanks. Hello Oliver, What i did so far and improved a lot the experience was: 1) Upgrade at least the if_re code to RELENG_7. This fixes issues of packet corruption on ssh sessions. 2) Delete from your kernel config USB and firewire. This prevents the realtek interrupt to be shared. After this, with 7.1 -BETA2 the systems are more or less stable, but after a while the ATA controller starts to create interrupt storms. I wasn't able to find why. With the help that i've received in this thread from Pyun YongHyeon (Thanks!!) i'm also trying this suggestions: 3) Backport this 3 files from current to 7.1 -BETA2: base/head/sys/dev/re/if_re.c base/head/sys/pci/if_rl.c base/head/sys/pci/if_rlreg.h You can fetch them from http://svn.freebsd.org/. With them and adding to /boot/loader.conf this tunable: hw.re.msi_disable="0" I can use GENERIC kernel again (ie, USB enabled) and so far i didn't find any problem yet. No more interface up/down problems and no more interrupt storms. I must say that i haven't tested this enough, because the interrupt storms in ATA code start to happen after a few days of uptime load, but at least the problems with the realtek seem to be gone. If you upgrade to 7.1 -BETA2 you'll also get SATA support for the IXP card. With 7.0 it will work as ATA 33 in compatibility mode. Maybe someone with write access to the wiki could add it somewhere so that other hetzner users that are having the same problems could use the same workarounds :) I hope this helps you. Regards. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 14:02:14 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C7BF10656D8; Wed, 10 Dec 2008 14:02:14 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout3.freenet.de (mout3.freenet.de [IPv6:2001:748:100:40::2:5]) by mx1.freebsd.org (Postfix) with ESMTP id CB1778FC1D; Wed, 10 Dec 2008 14:02:13 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from [195.4.92.19] (helo=9.mx.freenet.de) by mout3.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #65) id 1LAPdj-0001cg-Do; Wed, 10 Dec 2008 15:02:11 +0100 Received: from ma878.m.pppool.de ([89.49.168.120]:65294 helo=ernst.jennejohn.org) by 9.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #68) id 1LAPdj-0006Tm-6e; Wed, 10 Dec 2008 15:02:11 +0100 Date: Wed, 10 Dec 2008 15:02:07 +0100 From: Gary Jennejohn To: pyunyh@gmail.com Message-ID: <20081210150207.4951a157@ernst.jennejohn.org> In-Reply-To: <20081210120719.GK37837@cdnetworks.co.kr> References: <20081209185236.GA1320@alf.bsdes.net> <20081210061226.GC37837@cdnetworks.co.kr> <20081210085934.GB1320@alf.bsdes.net> <20081210102800.GH37837@cdnetworks.co.kr> <20081210113225.GD1320@alf.bsdes.net> <20081210120719.GK37837@cdnetworks.co.kr> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Victor Balada Diaz , freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 14:02:14 -0000 On Wed, 10 Dec 2008 21:07:19 +0900 Pyun YongHyeon wrote: > On Wed, Dec 10, 2008 at 12:32:25PM +0100, Victor Balada Diaz wrote: > > As these seems to improve the current situation, is there any > > chance of merging -current driver in 7.1 before release? > > > > I think re(4) in HEAD needs more testing. As you might know RealTek > produced too many chipsets. :-( > FYI I've now turned MSI on in HEAD and will see what happens. Before my re0 was sharing interrupts with 3 USB controllers. Now it's all by itself on irq256. I'm running amd64 with re0: port 0xde00-0xdeff mem 0xfdaff000-0xfdafffff, 0xfdae0000-0xfdaeffff irq 18 at device 0.0 on pci2 --- Gary Jennejohn From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 14:08:26 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 561691065670; Wed, 10 Dec 2008 14:08:26 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.bsdes.net (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.freebsd.org (Postfix) with ESMTP id 6C3A38FC08; Wed, 10 Dec 2008 14:08:25 +0000 (UTC) (envelope-from victor@bsdes.net) Received: by alf.bsdes.net (Postfix, from userid 1001) id 76EAB119CF7; Wed, 10 Dec 2008 15:08:24 +0100 (CET) Date: Wed, 10 Dec 2008 15:08:24 +0100 From: Victor Balada Diaz To: Pyun YongHyeon Message-ID: <20081210140823.GF1320@alf.bsdes.net> References: <20081209185236.GA1320@alf.bsdes.net> <20081210061226.GC37837@cdnetworks.co.kr> <20081210085934.GB1320@alf.bsdes.net> <20081210102800.GH37837@cdnetworks.co.kr> <20081210113225.GD1320@alf.bsdes.net> <20081210120719.GK37837@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20081210120719.GK37837@cdnetworks.co.kr> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 14:08:26 -0000 On Wed, Dec 10, 2008 at 09:07:19PM +0900, Pyun YongHyeon wrote: > On Wed, Dec 10, 2008 at 12:32:25PM +0100, Victor Balada Diaz wrote: > > On Wed, Dec 10, 2008 at 07:28:00PM +0900, Pyun YongHyeon wrote: > > > On Wed, Dec 10, 2008 at 09:59:35AM +0100, Victor Balada Diaz wrote: > > > > On Wed, Dec 10, 2008 at 03:12:26PM +0900, Pyun YongHyeon wrote: > > > > > On Tue, Dec 09, 2008 at 07:52:37PM +0100, Victor Balada Diaz wrote: > > > > > > Hello, > > > > > > > > > > > > I got various machines[1] at hetzner.de and I've been having problems > > > > > > with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've > > > > > > been trying to narrow the problem so someone more knowledgeable than me > > > > > > is able to fix it. This mail is an other attempt to ask a question > > > > > > with regards ATA code to see if this time i got something. > > > > > > > > > > > > For the ones that don't actually know what happened: > > > > > > > > > > > > With FreeBSD 7.0 -RELEASE for amd64 and default kernel > > > > > > the system shared re0 interrupt with OHCI and this caused > > > > > > re(4) to corrupt packets and create interrupt storms. Tried > > > > > > > > > > re(4) in 7.0-RELEASE had bus_dma(9) bug which could be easily > > > > > triggered on systems with > 4GB memory. But I dont' know whether > > > > > this is related with interrupt storms. > > > > > > > > > > > updating to 7.1 -BETA2 and still had some problems with it. > > > > > > > > > > > > I've opened the PR kern/128287[2] and Remko quickly answered > > > > > > with a workaround: that workaround was removing USB support from > > > > > > my kernel. I did it and re(4) wasn't sharing interrupts anylonger, > > > > > > and the interrupt storms were gone. Now sometime later the interface > > > > > > goes up and down from time to time, but less often. Also sometimes > > > > > > the machine losts the network interface but continues to work. > > > > > > > > > > > > > > > > It seems that your controller supports MSI so you can set a tunable > > > > > hw.re.msi_disable to 0 to enable MSI. With MSI you can remove > > > > > interrupt sharing(e.g. add hw.re.msi_disable="0" to > > > > > /boot/loader.conf file.) However there were several issues on re(4) > > > > > w.r.t MSI so it was off by default. > > > > > > > > This is undocumented and with sysctl -a i can't find the tunable. Is this > > > > a HEAD feature or it's also in 7.1 -BETA2? Should i add > > > > > > Yeah it's an undocmented feature. But most drivers written by me > > > have similar kobs. Both HEAD and stable/7 including 7.1 BETA2 have > > > the tunable. > > > > I think it could be great if you could document it or at least > > show it by default when you do sysctl -ad with a small description. > > > > If MSI worked as expected I would have documented it as I did > in msk(4)/nfe(4)/ale(4)/age(4)/jme(4) etc. > Using MSI on RealTek does not seem to stable. I tried hard to fix > that but some users still reported watchdog timeouts. Working > without documentation and hardware also made it hard to complete > the work. This was the main reason why MSI was disabled on re(4). What do you think about adding a note in the man page telling that it's experimental and in some cases it could improve the situation but in others it will give errors? > > > > > > > > hw.re_msi_disable="0" to /boot/loader.conf? > > > ^^^^^^^^^^^^^^^^^^^^^ > > > Shoule be hw.re.msi_disable="0" > > > > > > > > > > Yes, just add it to /boot/loader.conf. Note, you should not disable > > > system-wide MSI control(e.g. hw.pci.enable_msi == 1). > > > > > > > This was sharing interrupt with USB, does USB need any special MSI handling > > > > or with re using MSI is enough to not share the interrupt? > > > > > > If re(4) can use MSI, you don't need to worry about interrupt > > > sharing with USB. Check the output of "vmstat -i". You normally get > > > an irq256 or higher for MSI enabled driver. > > > > > > > > > > > > > > > > > > > > > > I know it continues to work because some days later i can see that > > > > > > it tried to deliver the status reports but was unable to resolve the > > > > > > aliases hostnames. I can't ping the machine and i know the network > > > > > > is OK. If i reboot the machine everything is working again. > > > > > > > > > > > > > > > > Recently I've made small changes to re(4) which may help to detect > > > > > link state change event. Would you try re(4) in HEAD? > > > > > > > > Can i just drop HEAD's /stable/7/sys/dev/re/ in -STABLE and test that > > > > > > Yes, you can. It should build without problems. Just replace re(4) on > > > stable/7 with HEAD version. > > > > > > > or do i need to test the whole HEAD kernel? > > > > > > > > > > No you don't have to that. > > > > Backporting the changes i've found that it didn't compile so in > > the end i got from HEAD the following files: > > > > base/head/sys/dev/re/if_re.c > > base/head/sys/pci/if_rl.c > > base/head/sys/pci/if_rlreg.h > > > > Ah,, sorry about that. Recently there was some changes. I forgot > that. > > > After that i've recompiled 7.1 -BETA2 GENERIC kernel and enabled > > the knob you suggested in /boot/loader.conf. > > > > With the new kernel and MSI the interrupts are like this: > > > > # vmstat -i > > interrupt total rate > > irq9: acpi0 1 0 > > irq16: ohci0 1 0 > > irq17: ohci1 ohci3 1 0 > > irq18: ohci2 ohci4 1 0 > > irq22: atapci0 19215 15 > > cpu0: timer 2502718 1998 > > irq256: re0 4967726 3967 > > cpu1: timer 2502525 1998 > > Total 9992188 7980 > > > > The high interrupt numbers are because i've been running iperf to > > check everything it's fine, not because of interrupt storms. So far > > i didn't find any interrupt storms related to USB or re(4) driver > > but while doing the tests i've found this error: > > > > re0: watchdog timeout (missed Tx interrupts) -- recovering > > > > This didn't create any error on the interfaces (netstat -i). > > > > This was triggered by new code in HEAD. It indicates re(4) missed > Tx completion interrupt. It could be a bug in driver or hardware > bug. If you can live with that message you can safely ignore that > as now re(4) does not reinitialize the hardware if it detect > missing Tx completion interrupt. Yeah, just happened once, and i'm used to receiving a lot of interface UP/DOWN messages that now are gone, so this is an improvement. > > > Also i didn't see any problem with interfaces going up and down, > > but that usually happen after some hours of uptime, so i'll let > > you know if the error happens again. > > > > Ok. > > > As these seems to improve the current situation, is there any > > chance of merging -current driver in 7.1 before release? > > > > I think re(4) in HEAD needs more testing. As you might know RealTek > produced too many chipsets. :-( Ok, i'll use the backported driver as it works better for me :-) If i can help you testing any patches i'm more than welcome to do it. Thanks a lot for your help Pyun YongHyeon. Regards. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 14:17:03 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 081121065692 for ; Wed, 10 Dec 2008 14:17:03 +0000 (UTC) (envelope-from rebehn@ant.uni-bremen.de) Received: from antsrv1.ant.uni-bremen.de (antsrv1.ant.uni-bremen.de [134.102.176.16]) by mx1.freebsd.org (Postfix) with ESMTP id C0A718FC1C for ; Wed, 10 Dec 2008 14:17:02 +0000 (UTC) (envelope-from rebehn@ant.uni-bremen.de) Received: from bremerhaven.ant.uni-bremen.de ([134.102.176.10]) by antsrv1.ant.uni-bremen.de with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1LAPWl-000A9C-38; Wed, 10 Dec 2008 14:54:59 +0100 Message-Id: From: Heinrich Rebehn To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Wed, 10 Dec 2008 14:54:59 +0100 X-Mailer: Apple Mail (2.919.2) Subject: iir(4) support under 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 14:17:03 -0000 Hi list, i am planning to upgrade our main server from 6.1 to 7.1. The machine has a ICP Vortex GDT8524RZ raid controller which is handled buy the iir(4) driver. Since i have seen various discussions in the past about Adaptec no longer supporting these controllers, driver reaching EOE, data corruption in 64bit configurtions with > 4G RAM and so on, i just wanted to ask what the current state of the driver is. Thanks for your help, Heinrich Rebehn University of Bremen Physics / Electrical and Electronics Engineering - Department of Telecommunications - Phone : +49/421/218-4664 Fax : -3341 From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 14:18:47 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D26D81065673; Wed, 10 Dec 2008 14:18:47 +0000 (UTC) (envelope-from oliver@nemesis.charlie.mouhaha.de) Received: from nemesis.charlie.mouhaha.de (nemesis.charlie.mouhaha.de [78.47.10.193]) by mx1.freebsd.org (Postfix) with ESMTP id 697D28FC12; Wed, 10 Dec 2008 14:18:47 +0000 (UTC) (envelope-from oliver@nemesis.charlie.mouhaha.de) Received: from localhost (nemesis.charlie.mouhaha.de [78.47.10.193]) by nemesis.charlie.mouhaha.de (Postfix) with ESMTP id 460F22D2F4; Wed, 10 Dec 2008 14:18:46 +0000 (GMT) X-Virus-Scanned: amavisd-new at mouhaha.de Received: from nemesis.charlie.mouhaha.de ([78.47.10.193]) by localhost (nemesis.charlie.mouhaha.de [78.47.10.193]) (amavisd-new, port 10024) with ESMTP id vhmo2AubaKB5; Wed, 10 Dec 2008 14:18:34 +0000 (GMT) Received: by nemesis.charlie.mouhaha.de (Postfix, from userid 1001) id C19F42D2D3; Wed, 10 Dec 2008 14:18:34 +0000 (GMT) Date: Wed, 10 Dec 2008 14:18:34 +0000 From: Oliver Peter To: Victor Balada Diaz Message-ID: <20081210141834.GB36443@nemesis.frida.mouhaha.de> References: <20081209185236.GA1320@alf.bsdes.net> <20081210120840.GA36443@nemesis.frida.mouhaha.de> <20081210140129.GE1320@alf.bsdes.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081210140129.GE1320@alf.bsdes.net> X-Operating-System: FreeBSD 7.0-RELEASE-p6 amd64 User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Oliver Peter , freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 14:18:47 -0000 On Wed, Dec 10, 2008 at 03:01:30PM +0100, Victor Balada Diaz wrote: > On Wed, Dec 10, 2008 at 12:08:40PM +0000, Oliver Peter wrote: > > On Tue, Dec 09, 2008 at 07:52:37PM +0100, Victor Balada Diaz wrote: ... > I can use GENERIC kernel again (ie, USB enabled) and so far > i didn't find any problem yet. No more interface up/down problems > and no more interrupt storms. I must say that i haven't tested > this enough, because the interrupt storms in ATA code start to > happen after a few days of uptime load, but at least the problems > with the realtek seem to be gone. I found out that I'm able to 'force' the interrupt storm by provoking higher disk I/O. Just let dd write to a file in a loop for some hours and watch vmstat: while true; do dd if=/dev/zero of=BLA bs=1M count=1000; done First you'll see that the throughput will decrease, and a few hours later you'll have /var/log/messages / dmesg full of interrupt storm messages. > If you upgrade to 7.1 -BETA2 you'll also get SATA support for > the IXP card. With 7.0 it will work as ATA 33 in compatibility mode. Wow! That's good to hear as well. I'll definitely switch to -STABLE or 7.1-PRERELASE sooner or later. I'll just give it a try on my other machines at first. > I hope this helps you. Absolutely, cheers mate. I owe you one! ~ollie -- Oliver PETER, email: oliver@peter.de.com, ICQ# 113969174 "If it feels good, you're doing something wrong." -- Coach McTavish From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 14:21:08 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D792C1065679; Wed, 10 Dec 2008 14:21:08 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.bsdes.net (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.freebsd.org (Postfix) with ESMTP id 806058FC25; Wed, 10 Dec 2008 14:21:08 +0000 (UTC) (envelope-from victor@bsdes.net) Received: by alf.bsdes.net (Postfix, from userid 1001) id 8DD3F119CF8; Wed, 10 Dec 2008 15:21:07 +0100 (CET) Date: Wed, 10 Dec 2008 15:21:07 +0100 From: Victor Balada Diaz To: Arnaud Houdelette Message-ID: <20081210142107.GG1320@alf.bsdes.net> References: <20081209185236.GA1320@alf.bsdes.net> <493FB378.5030106@tzim.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <493FB378.5030106@tzim.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 14:21:08 -0000 On Wed, Dec 10, 2008 at 01:18:00PM +0100, Arnaud Houdelette wrote: > Victor Balada Diaz a écrit : > >Hello, > > > >I got various machines[1] at hetzner.de and I've been having problems > >with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've > >been trying to narrow the problem so someone more knowledgeable than me > >is able to fix it. This mail is an other attempt to ask a question > >with regards ATA code to see if this time i got something. > > > >[...] > > Sorry I didn't take the time to read all the thread, but I got similar > problem with the same IXP600 chipset. > Only it was'nt with a Realtek NIC (re) but with a Ralink wireless one. > The simptoms where similar : interrupt 22 was shared between the sata > controler and the wireless card. And I got Interrupt Storms at random > times when using the wireless network. > > No problem since I removed the ral(4) NIC (got a real access point now). > You might not want to point the finger at the re(4) driver too fast. > > Arnaud Houdelette Hello Arnaud, I didn't say the problem was just because of re(4). Actually i think the there were two problems, one with re(4) and other with ata(4). The reason why i talked about both of them in the same mail is because i thought that as two drivers were affected, maybe the problem was in other part of the operating system and that could help the developers to debug the problem. My re(4) card isn't sharing the interrupt with IXP600, it's sharing the interrupt with USB controller. In this case i think the problem is fixed with the advices from Pyun YongHyeon (backporting the driver from HEAD and using MSI for interrupts). I think the problems with ata(4) code will appear again after a few days of load, as they always do, so i'll keep trying to debug them. Regards. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 14:59:27 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5790D106564A for ; Wed, 10 Dec 2008 14:59:27 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by mx1.freebsd.org (Postfix) with ESMTP id 2236B8FC1F for ; Wed, 10 Dec 2008 14:59:27 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by yw-out-2324.google.com with SMTP id 9so235301ywe.13 for ; Wed, 10 Dec 2008 06:59:26 -0800 (PST) Received: by 10.151.143.3 with SMTP id v3mr2300746ybn.40.1228921166216; Wed, 10 Dec 2008 06:59:26 -0800 (PST) Received: by 10.151.68.11 with HTTP; Wed, 10 Dec 2008 06:59:26 -0800 (PST) Message-ID: Date: Wed, 10 Dec 2008 16:59:26 +0200 From: "Vlad GALU" To: freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org, freebsd-performance@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: bce(4) and rx errors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Dec 2008 14:59:27 -0000 Hello. Sorry for crossposting, but I wasn't sure which mailing list was the most appropriate for this email. I have an application pulling about 220Kpps from a bce(4) card (details below). At what seems to be random times, errors start showing up on that interface (I'm watching it with netstat -w1 -I), so about 10% of the initial 220Kpps is reported as errors. Bringing the interface down and then back up clears the errors, but they do reappear at a later time. Before they reappear, the systems manages to pull the full 220Kpps as before. This is a temporary setup, we'll very soon use an Intel fiber card, but I thought this issue was worth mentioning, as I don't think it's a hardware problem (the switch also reports no errors). The system is running a fresh (yesterday's) RELENG_7. The card is onboard, on a HP DL380 G5. Here's the pciconf output: -- cut here -- pcib13@pci0:2:0:0: class=0x060400 card=0x00000000 chip=0x01031166 rev=0xc3 hdr=0x01 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'BCM5715 Broadcom dual gigabit, pci bridge' class = bridge subclass = PCI-PCI bce0@pci0:3:0:0: class=0x020000 card=0x7038103c chip=0x164c14e4 rev=0x12 hdr=0x00 vendor = 'Broadcom Corporation' device = '5708C Broadcom NetXtreme II Gigabit Ethernet Adapter' class = network subclass = ethernet -- and here -- Regards, Vlad -- ~/.signature: no such file or directory From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 15:05:10 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A161F106564A; Wed, 10 Dec 2008 15:05:10 +0000 (UTC) (envelope-from prvs=12308e1c5a=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id EDEB18FC13; Wed, 10 Dec 2008 15:05:09 +0000 (UTC) (envelope-from prvs=12308e1c5a=killing@multiplay.co.uk) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk; s=Multiplay; t=1228920552; x=1229525352; q=dns/txt; h=Received: Message-ID:From:To:Subject:Date:MIME-Version:Content-Type: Content-Transfer-Encoding; bh=rGttyBfSniE0d99ULXmMihcsuSpGy/XY6A O+1IR2LXw=; b=n/xebX+AKYvikTYaBWzq00hRpdZkSLHr/FfVtZTpTk6M347DR3 CUKC29SpHCLMCylL/m6l8pK6NzYjuSMQqoNRJCYv1XyBje9pD5gPypyzcnaTM3HA FloNj5F9W3HBeY5bmY6YNjDS8k4jNMfC/1XDI+i9KB1x07Wy7rpyp4Hps= X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-14.7 required=6.0 tests=BAYES_00, FORGED_MUA_OUTLOOK, USER_IN_WHITELIST,USER_IN_WHITELIST_TO autolearn=ham version=3.1.8 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v9.6.6) with ESMTP id md50006696587.msg; Wed, 10 Dec 2008 14:49:11 +0000 X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 213.123.247.160 X-Return-Path: prvs=12308e1c5a=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <38D2AA3D46354E8EA3EE2A1056A1BE4A@multiplay.co.uk> From: "Steven Hartland" To: , Date: Wed, 10 Dec 2008 14:49:11 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Spam-Processed: mail1.multiplay.co.uk, Wed, 10 Dec 2008 14:49:11 +0000 X-MDAV-Processed: mail1.multiplay.co.uk, Wed, 10 Dec 2008 14:49:12 +0000 Cc: Subject: 7.0 unusual performance issue - vmdaemon 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: Wed, 10 Dec 2008 15:05:10 -0000 Just had one of hour webservers flag as down here and on investigation the machine seems to be struggling due to a hung vmdaemon process. top is reporting vmdaemon as using a constant 55.57% CPU yet CPU time is not increasing:- last pid: 36492; load averages: 0.04, 0.05, .11 up 89+19:53:21 14:36:08 223 processes: 9 running, 201 sleeping, 13 waiting CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 644M Active, 2780M Inact, 480M Wired, 249M Cache, 214M Buf, 3759M Free Swap: 4096M Total, 537M Used, 3559M Free, 13% Inuse PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 11 root 1 171 ki31 0K 16K CPU7 7 2116.4 100.00% idle: cpu7 12 root 1 171 ki31 0K 16K CPU6 6 2059.5 100.00% idle: cpu6 13 root 1 171 ki31 0K 16K CPU5 5 2029.3 100.00% idle: cpu5 14 root 1 171 ki31 0K 16K CPU4 4 1977.8 100.00% idle: cpu4 15 root 1 171 ki31 0K 16K CPU3 3 1912.0 100.00% idle: cpu3 16 root 1 171 ki31 0K 16K CPU2 2 1835.2 100.00% idle: cpu2 17 root 1 171 ki31 0K 16K CPU1 1 1763.1 100.00% idle: cpu1 18 root 1 171 ki31 0K 16K RUN 0 1727.6 100.00% idle: cpu0 37 root 1 20 - 0K 16K psleep 5 0:56 55.57% vmdaemon 60198 www 1 4 0 98M 13516K sbwait 2 35:21 1.46% httpd 60264 www 1 4 0 133M 9248K sbwait 0 21:21 0.39% httpd 30 root 1 -68 - 0K 16K - 7 18.3H 0.00% em1 taskq 29 root 1 -68 - 0K 16K - 6 330:21 0.00% em0 taskq 41 root 1 20 - 0K 16K syncer 1 212:42 0.00% syncer 21 root 1 -44 - 0K 16K WAIT 0 201:02 0.00% swi1: net 19 root 1 -32 - 0K 16K WAIT 0 120:15 0.00% swi4: clock 22 root 1 44 - 0K 16K - 5 73:00 0.00% yarrow I've tried to ktrace the process and it produced nothing, also tried gdb and it failed to attach. Is there anything else I can try before we reboot the machine to help determine what the problem is? Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 15:28:55 2008 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 A9FFF1065676; Wed, 10 Dec 2008 15:28:55 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id 6821A8FC19; Wed, 10 Dec 2008 15:28:55 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1LAQze-0005kh-92; Wed, 10 Dec 2008 17:28:54 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: stable@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Dec 2008 17:28:54 +0200 From: Danny Braniss Message-ID: Cc: hackers@FreeBSD.org Subject: zfs panics X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Dec 2008 15:28:55 -0000 hi, from a solaris or linux client, doing a ls(1) of a nfs exported zfs file, for example: ls /net/zfs-server/h/.zfs/snapshot, panics the server. The server is running latest 7.1-prerelease. when client is freebsd, it mostly works, but in a few cases the server just goes into comma. btw, the server is running vanilla zfs, no tunning, and the server is 64bit with 8gb of memory and quad core (dell-pe2950) Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x168 fault code = supervisor write data, page not present instruction pointer = 0x8:0xffffffff804a9175 stack pointer = 0x10:0xffffffffb71fc550 frame pointer = 0x10:0xffffffffb71fc560 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 802 (nfsd) [thread pid 802 tid 100185 ] Stopped at _mtx_lock_flags+0x15: lock cmpxchgq %rsi,0x50(%rdi) db> tr Tracing pid 802 tid 100185 td 0xffffff0004d576e0 _mtx_lock_flags() at _mtx_lock_flags+0x15 vput() at vput+0x45 nfsrv_readdirplus() at nfsrv_readdirplus+0x83e nfssvc() at nfssvc+0x400 syscall() at syscall+0x1bb Xfast_syscall() at Xfast_syscall+0xab --- syscall (155, FreeBSD ELF64, nfssvc), rip = 0x8006885cc, rsp = 0x7fffffffea2 From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 16:18:20 2008 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 58541106564A; Wed, 10 Dec 2008 16:18:20 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from emh03.mail.saunalahti.fi (emh03.mail.saunalahti.fi [62.142.5.109]) by mx1.freebsd.org (Postfix) with ESMTP id 157A88FC16; Wed, 10 Dec 2008 16:18:20 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from saunalahti-vams (vs3-10.mail.saunalahti.fi [62.142.5.94]) by emh03-2.mail.saunalahti.fi (Postfix) with SMTP id A5F68EBD63; Wed, 10 Dec 2008 18:01:03 +0200 (EET) Received: from emh07.mail.saunalahti.fi ([62.142.5.117]) by vs3-10.mail.saunalahti.fi ([62.142.5.94]) with SMTP (gateway) id A03FAAA0F94; Wed, 10 Dec 2008 18:01:03 +0200 Received: from a91-153-125-115.elisa-laajakaista.fi (a91-153-125-115.elisa-laajakaista.fi [91.153.125.115]) by emh07.mail.saunalahti.fi (Postfix) with SMTP id 20F781C63AC; Wed, 10 Dec 2008 18:00:59 +0200 (EET) Date: Wed, 10 Dec 2008 18:00:59 +0200 From: Jaakko Heinonen To: Danny Braniss Message-ID: <20081210160059.GA3495@a91-153-125-115.elisa-laajakaista.fi> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-Antivirus: VAMS Cc: stable@FreeBSD.org, hackers@FreeBSD.org Subject: Re: zfs panics X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Dec 2008 16:18:20 -0000 Hi, On 2008-12-10, Danny Braniss wrote: > from a solaris or linux client, doing a ls(1) of a nfs exported zfs file, > for example: ls /net/zfs-server/h/.zfs/snapshot, > panics the server. The server is running latest 7.1-prerelease. This has been reported as PR kern/125149. I have described the problem in this message: http://lists.freebsd.org/pipermail/freebsd-fs/2008-October/005217.html See the PR for RELENG_7 patches. (http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/125149) -- Jaakko From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 16:20:18 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 144EA10656D3; Wed, 10 Dec 2008 16:20:18 +0000 (UTC) (envelope-from jfb@mr-paradox.net) Received: from vexbert.mr-paradox.net (vexbert.mr-paradox.net [198.145.180.174]) by mx1.freebsd.org (Postfix) with ESMTP id EFC758FC12; Wed, 10 Dec 2008 16:20:17 +0000 (UTC) (envelope-from jfb@mr-paradox.net) Received: by vexbert.mr-paradox.net (Postfix, from userid 16139) id 781588450D; Wed, 10 Dec 2008 11:03:26 -0500 (EST) Date: Wed, 10 Dec 2008 11:03:25 -0500 From: Jeff Blank To: freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org, freebsd-performance@freebsd.org Message-ID: <20081210160325.GA72838@mr-happy.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Face: #0jV*~a}VtKS-&E/!EJpH('H1Va}24dxF0oT&+.R3Gu8C; xhSC+<|+H84&YLbMvphuRT4cp3.|8EN_(2Eix/6{.Up~u`a^}0Ln&b+9Fw|BPig@-{y\pL_46d&ZwA]5%_AU?}DezfE&1!>H?3E$!Yve7.O<+..Jnb4:'6Ey_]FtFzU9=*l$1p/@gA,Ze>^5<]+r(XJ+m7`/vMDc$'wy|`e Cc: Subject: Re: bce(4) and rx errors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Dec 2008 16:20:18 -0000 On Wed, Dec 10, 2008 at 04:59:26PM +0200, Vlad GALU wrote: > I have an application pulling about 220Kpps from a bce(4) card > (details below). At what seems to be random times, errors start > showing up on that interface (I'm watching it with netstat -w1 -I), so > about 10% of the initial 220Kpps is reported as errors. I'm also seeing a pretty steady stream of errors on both bce interfaces in a Dell PowerEdge 2950 III. In my case, the source is RELENG_7_1 from ~14:00 UTC yesterday (9 Dec). Throughput does not seem to be affected. "sysctl -a | egrep -i 'bce.*err'" yields all zeroes, for whatever that's worth. hostb0@pci0:0:0:0: class=0x060000 card=0x80868086 chip=0x25c08086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000X Chipset Memory Controller Hub' class = bridge subclass = HOST-PCI pcib1@pci0:0:2:0: class=0x060400 card=0x00000000 chip=0x25e28086 rev=0x12 hdr=0x01 vendor = 'Intel Corporation' device = '5000 Series Chipset PCIe x4 Port 2' class = bridge subclass = PCI-PCI pcib7@pci0:0:3:0: class=0x060400 card=0x00000000 chip=0x25e38086 rev=0x12 hdr=0x01 vendor = 'Intel Corporation' device = '5000 Series Chipset PCIe x4 Port 3' class = bridge subclass = PCI-PCI pcib8@pci0:0:4:0: class=0x060400 card=0x00000000 chip=0x25f88086 rev=0x12 hdr=0x01 vendor = 'Intel Corporation' device = '5000 Series Chipset PCIe x8 Port 4-5' class = bridge subclass = PCI-PCI pcib12@pci0:0:5:0: class=0x060400 card=0x00000000 chip=0x25e58086 rev=0x12 hdr=0x01 vendor = 'Intel Corporation' device = '5000 Series Chipset PCIe x4 Port 5' class = bridge subclass = PCI-PCI pcib13@pci0:0:6:0: class=0x060400 card=0x00000000 chip=0x25f98086 rev=0x12 hdr=0x01 vendor = 'Intel Corporation' device = '5000 Series Chipset PCIe x8 Port 6-7' class = bridge subclass = PCI-PCI pcib16@pci0:0:7:0: class=0x060400 card=0x00000000 chip=0x25e78086 rev=0x12 hdr=0x01 vendor = 'Intel Corporation' device = '5000 Series Chipset PCIe x4 Port 7' class = bridge subclass = PCI-PCI hostb1@pci0:0:16:0: class=0x060000 card=0x01b21028 chip=0x25f08086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset Error Reporting Registers' class = bridge subclass = HOST-PCI hostb2@pci0:0:16:1: class=0x060000 card=0x01b21028 chip=0x25f08086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset Error Reporting Registers' class = bridge subclass = HOST-PCI hostb3@pci0:0:16:2: class=0x060000 card=0x01b21028 chip=0x25f08086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset Error Reporting Registers' class = bridge subclass = HOST-PCI hostb4@pci0:0:17:0: class=0x060000 card=0x80868086 chip=0x25f18086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset Reserved Registers' class = bridge subclass = HOST-PCI hostb5@pci0:0:19:0: class=0x060000 card=0x80868086 chip=0x25f38086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset Reserved Registers' class = bridge subclass = HOST-PCI hostb6@pci0:0:21:0: class=0x060000 card=0x80868086 chip=0x25f58086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset FBD Registers' class = bridge subclass = HOST-PCI hostb7@pci0:0:22:0: class=0x060000 card=0x80868086 chip=0x25f68086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset FBD Registers' class = bridge subclass = HOST-PCI pcib17@pci0:0:28:0: class=0x060400 card=0x01b21028 chip=0x26908086 rev=0x09 hdr=0x01 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 PCIe Root Port 1' class = bridge subclass = PCI-PCI uhci0@pci0:0:29:0: class=0x0c0300 card=0x01b21028 chip=0x26888086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset USB Universal Host Controller' class = serial bus subclass = USB uhci1@pci0:0:29:1: class=0x0c0300 card=0x01b21028 chip=0x26898086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset USB Universal Host Controller' class = serial bus subclass = USB uhci2@pci0:0:29:2: class=0x0c0300 card=0x01b21028 chip=0x268a8086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset USB Universal Host Controller' class = serial bus subclass = USB uhci3@pci0:0:29:3: class=0x0c0300 card=0x01b21028 chip=0x268b8086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset USB Universal Host Controller' class = serial bus subclass = USB ehci0@pci0:0:29:7: class=0x0c0320 card=0x01b21028 chip=0x268c8086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset USB2 Enhanced Host Controller' class = serial bus subclass = USB pcib19@pci0:0:30:0: class=0x060401 card=0x00000000 chip=0x244e8086 rev=0xd9 hdr=0x01 vendor = 'Intel Corporation' device = '82801 Family (ICH2/3/4/4/5/5/6/7/8/9,63xxESB) Hub Interface to PCI Bridge' class = bridge subclass = PCI-PCI isab0@pci0:0:31:0: class=0x060100 card=0x00000000 chip=0x26708086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 LPC Interface Controller' class = bridge subclass = PCI-ISA atapci0@pci0:0:31:1: class=0x01018a card=0x01b21028 chip=0x269e8086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Ultra ATA Storage Controller' class = mass storage subclass = ATA pcib2@pci0:4:0:0: class=0x060400 card=0x00000000 chip=0x35008086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '631xESB/632xESB PCIe Upstream Port' class = bridge subclass = PCI-PCI pcib6@pci0:4:0:3: class=0x060400 card=0x00000000 chip=0x350c8086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '631xESB/632xESB PCIe to PCI-X Bridge' class = bridge subclass = PCI-PCI pcib3@pci0:5:0:0: class=0x060400 card=0x00000000 chip=0x35108086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '631xESB/632xESB PCIe Downstream Port E1' class = bridge subclass = PCI-PCI pcib5@pci0:5:1:0: class=0x060400 card=0x00000000 chip=0x35148086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '631xESB/632xESB PCIe Downstream Port E2' class = bridge subclass = PCI-PCI pcib4@pci0:6:0:0: class=0x060400 card=0x00000000 chip=0x01031166 rev=0xc3 hdr=0x01 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'BCM5715 Broadcom dual gigabit, pci bridge' class = bridge subclass = PCI-PCI bce0@pci0:7:0:0: class=0x020000 card=0x01b21028 chip=0x164c14e4 rev=0x12 hdr=0x00 vendor = 'Broadcom Corporation' device = '5708C Broadcom NetXtreme II Gigabit Ethernet Adapter' class = network subclass = ethernet mpt0@pci0:1:0:0: class=0x010000 card=0x1f101028 chip=0x00581000 rev=0x08 hdr=0x00 vendor = 'LSI Logic (Was: Symbios Logic, NCR)' device = 'SAS 3000 series, 8-port with 1068E -StorPort' class = mass storage subclass = SCSI pcib9@pci0:10:0:0: class=0x060400 card=0x00000000 chip=0x8018111d rev=0x0e hdr=0x01 vendor = 'Integrated Device Technology Inc.' class = bridge subclass = PCI-PCI pcib10@pci0:11:2:0: class=0x060400 card=0x00000000 chip=0x8018111d rev=0x0e hdr=0x01 vendor = 'Integrated Device Technology Inc.' class = bridge subclass = PCI-PCI pcib11@pci0:11:4:0: class=0x060400 card=0x00000000 chip=0x8018111d rev=0x0e hdr=0x01 vendor = 'Integrated Device Technology Inc.' class = bridge subclass = PCI-PCI igb0@pci0:12:0:0: class=0x020000 card=0x145a8086 chip=0x10d68086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb1@pci0:12:0:1: class=0x020000 card=0x145a8086 chip=0x10d68086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb2@pci0:13:0:0: class=0x020000 card=0x145a8086 chip=0x10d68086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb3@pci0:13:0:1: class=0x020000 card=0x145a8086 chip=0x10d68086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet pcib14@pci0:15:0:0: class=0x060400 card=0x00000000 chip=0x03298086 rev=0x09 hdr=0x01 vendor = 'Intel Corporation' device = '6700PXH PCI Express-to-PCI Express Bridge A' class = bridge subclass = PCI-PCI pcib15@pci0:15:0:2: class=0x060400 card=0x00000000 chip=0x032a8086 rev=0x09 hdr=0x01 vendor = 'Intel Corporation' device = '6700PXH PCI Express-to-PCI Express Bridge B' class = bridge subclass = PCI-PCI pcib18@pci0:2:0:0: class=0x060400 card=0x00000000 chip=0x01031166 rev=0xc3 hdr=0x01 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'BCM5715 Broadcom dual gigabit, pci bridge' class = bridge subclass = PCI-PCI bce1@pci0:3:0:0: class=0x020000 card=0x01b21028 chip=0x164c14e4 rev=0x12 hdr=0x00 vendor = 'Broadcom Corporation' device = '5708C Broadcom NetXtreme II Gigabit Ethernet Adapter' class = network subclass = ethernet vgapci0@pci0:19:13:0: class=0x030000 card=0x01b21028 chip=0x515e1002 rev=0x02 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'Radeon ES1000 Radeon ES1000' class = display subclass = VGA From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 16:59:52 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18FCD106564A for ; Wed, 10 Dec 2008 16:59:52 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp108.rog.mail.re2.yahoo.com (smtp108.rog.mail.re2.yahoo.com [68.142.225.206]) by mx1.freebsd.org (Postfix) with SMTP id B0A558FC08 for ; Wed, 10 Dec 2008 16:59:51 +0000 (UTC) (envelope-from mikej@rogers.com) Received: (qmail 23105 invoked from network); 10 Dec 2008 16:59:50 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Received:Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:Importance; b=xRKwdo9ElSFYd+8B9Lka2lUw3Zu/qzz/3x6nnYRy6VxnXyRP8jMivAHtPEzT+heLbuq1aHlZqGOSLNDE9rWCv0Rpiui1dJ0LU+XjaP11z37B2vxAXZ4WKW2n0RIU8eB/Xq74KnbhK/VVldGe4sqPx+Fj301YRvtv12QMUBzFqUs= ; Received: from unknown (HELO wettoast.dyndns.org) (mikej@99.227.98.203 with login) by smtp108.rog.mail.re2.yahoo.com with SMTP; 10 Dec 2008 16:59:47 -0000 X-YMail-OSG: CAzb5CkVM1leqscWvQNywZF5R5TCTy7YLApp0xogXsfNykOg8QatI8UmaA6OcKTKAw-- X-Yahoo-Newman-Property: ymail-3 Received: from 38.99.187.34 (SquirrelMail authenticated user mikej) by wettoast.dyndns.org with HTTP; Wed, 10 Dec 2008 12:00:13 -0500 (EST) Message-ID: <56272b131067237ccabd23de5f669458.squirrel@wettoast.dyndns.org> In-Reply-To: <4fe0419b44a3a4c4a28b1e60fbb3a3c8.squirrel@wettoast.dyndns.org> References: <4935069A.8060209@ec-marseille.fr> <49357BD0.4000008@delphij.net> <4935944A.9090509@ec-marseille.fr> <4935C453.8070301@delphij.net> <4935D67E.4070204@delphij.net> <4936F8C4.6090006@ec-marseille.fr> <49399FA6.3060108@delphij.net> <493CE8F7.5010204@yandex-team.ru> <3a6fb7145a0a6c8af136ea1a0824e5ed.squirrel@wettoast.dyndns.org> <493D9BC6.8050902@delphij.net> <4fe0419b44a3a4c4a28b1e60fbb3a3c8.squirrel@wettoast.dyndns.org> Date: Wed, 10 Dec 2008 12:00:13 -0500 (EST) From: "Mike Jakubik" To: d@delphij.net User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-stable@freebsd.org Subject: Re: RELENG_7_1: bce driver change generating too much interrupts ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Dec 2008 16:59:52 -0000 On Mon, December 8, 2008 5:22 pm, Mike Jakubik wrote: > On Mon, December 8, 2008 5:12 pm, Xin LI wrote: > >> Which version are you currently using? My previous commit only fixes >> the excessive interrupt issue, I think this could be a different >> problem, I'm taking a look at the code to see if I can have something >> for you. > > I was running on the version just prior to the latest interrupt commit. I > have now updated to the one with the interrupt fix. Will let you know if > things change. > > Thank You. The interrupt rate has decreased significantly, however i am still having having problem with applications that hold stateful connections. The rx errors are also still showing, i suspect this is related to the problem. How can i roll back this driver to the last known good version? Thanks. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 17:01:13 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB6FF1065675 for ; Wed, 10 Dec 2008 17:01:13 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp130.rog.mail.re2.yahoo.com (smtp130.rog.mail.re2.yahoo.com [206.190.53.35]) by mx1.freebsd.org (Postfix) with SMTP id 793B98FC13 for ; Wed, 10 Dec 2008 17:01:13 +0000 (UTC) (envelope-from mikej@rogers.com) Received: (qmail 28548 invoked from network); 10 Dec 2008 17:01:12 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Received:Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:Importance; b=4VWlLwOP4yVTNqgeYuqPkpbjlDw7956UnjaECj+UvFEmDrHkgrzT9BGvgWRyhtfiohb3qM07WlE/E3DKyXFODrvm6p57JFy+aPBZ+sqob+d4aepCEsH0WWKc1zvux69Ck1iT1ttG939QZgZUi65iLRnON+0sxu0suG4IY+8l328= ; Received: from unknown (HELO wettoast.dyndns.org) (mikej@99.227.98.203 with login) by smtp130.rog.mail.re2.yahoo.com with SMTP; 10 Dec 2008 17:01:09 -0000 X-YMail-OSG: v58eFMUVM1kXEAnX8tnMBnxNZDU4dzHMFKP.Nd0wwhgwnVDEXv_xjkLYyaK3ZiRKOg-- X-Yahoo-Newman-Property: ymail-3 Received: from 38.99.187.34 (SquirrelMail authenticated user mikej) by wettoast.dyndns.org with HTTP; Wed, 10 Dec 2008 12:01:35 -0500 (EST) Message-ID: In-Reply-To: <20081210160325.GA72838@mr-happy.com> References: <20081210160325.GA72838@mr-happy.com> Date: Wed, 10 Dec 2008 12:01:35 -0500 (EST) From: "Mike Jakubik" To: "Jeff Blank" User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-stable@freebsd.org Subject: Re: bce(4) and rx errors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Dec 2008 17:01:14 -0000 On Wed, December 10, 2008 11:03 am, Jeff Blank wrote: > On Wed, Dec 10, 2008 at 04:59:26PM +0200, Vlad GALU wrote: >> I have an application pulling about 220Kpps from a bce(4) card >> (details below). At what seems to be random times, errors start >> showing up on that interface (I'm watching it with netstat -w1 -I), so >> about 10% of the initial 220Kpps is reported as errors. > > I'm also seeing a pretty steady stream of errors on both bce > interfaces in a Dell PowerEdge 2950 III. In my case, the source > is RELENG_7_1 from ~14:00 UTC yesterday (9 Dec). Throughput does not > seem to be affected. "sysctl -a | egrep -i 'bce.*err'" yields all > zeroes, for whatever that's worth. See the "RELENG_7_1: bce driver change generating too much interrupts ?" thread. This problem as surfaced since the recent bce driver changes. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 17:47:31 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B860A1065676 for ; Wed, 10 Dec 2008 17:47:31 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5E8F58FC1D for ; Wed, 10 Dec 2008 17:47:31 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id 53E3E28449 for ; Thu, 11 Dec 2008 01:47:30 +0800 (CST) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id C98CEEC2FF4; Thu, 11 Dec 2008 01:47:29 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id QVvV2OhuuLIr; Thu, 11 Dec 2008 01:47:24 +0800 (CST) Received: from charlie.delphij.net (adsl-76-237-33-62.dsl.pltn13.sbcglobal.net [76.237.33.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id EFD82EC3055; Thu, 11 Dec 2008 01:47:22 +0800 (CST) Message-ID: <494000A5.2050107@delphij.net> Date: Wed, 10 Dec 2008 09:47:17 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 To: Mike Jakubik References: <4935069A.8060209@ec-marseille.fr> <49357BD0.4000008@delphij.net> <4935944A.9090509@ec-marseille.fr> <4935C453.8070301@delphij.net> <4935D67E.4070204@delphij.net> <4936F8C4.6090006@ec-marseille.fr> <49399FA6.3060108@delphij.net> <493CE8F7.5010204@yandex-team.ru> <3a6fb7145a0a6c8af136ea1a0824e5ed.squirrel@wettoast.dyndns.org> <493D9BC6.8050902@delphij.net> <4fe0419b44a3a4c4a28b1e60fbb3a3c8.squirrel@wettoast.dyndns.org> <56272b131067237ccabd23de5f669458.squirrel@wettoast.dyndns.org> In-Reply-To: <56272b131067237ccabd23de5f669458.squirrel@wettoast.dyndns.org> X-Enigmail-Version: 0.95.7 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, d@delphij.net Subject: Re: RELENG_7_1: bce driver change generating too much interrupts ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 17:47:31 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mike Jakubik wrote: > On Mon, December 8, 2008 5:22 pm, Mike Jakubik wrote: >> On Mon, December 8, 2008 5:12 pm, Xin LI wrote: >> >>> Which version are you currently using? My previous commit only fixes >>> the excessive interrupt issue, I think this could be a different >>> problem, I'm taking a look at the code to see if I can have something >>> for you. >> I was running on the version just prior to the latest interrupt commit. I >> have now updated to the one with the interrupt fix. Will let you know if >> things change. >> >> Thank You. > > The interrupt rate has decreased significantly, however i am still having > having problem with applications that hold stateful connections. The rx > errors are also still showing, i suspect this is related to the problem. > How can i roll back this driver to the last known good version? If you are using CVS to track the -stable tree: cd /usr/src/sys/dev/bce cvs -q up -rRELENG_7 -D2008/11/01 If not, then the process would be a bit complicated. You need to checkout from anoncvs, e.g.: cvs -q -d anoncvs@anoncvs.freebsd.org:/home/ncvs login cvs -q -d anoncvs@anoncvs.freebsd.org:/home/ncvs co -rRELENG_7 - -D2008/11/01 sys/dev/bce cd sys/dev/bce cp * /sys/dev/bce Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAklAAKUACgkQi+vbBBjt66AhrwCfXI5aPX3q/E26KcW7HovtPSct LnoAn0QNK/l65eYMiUvGBDUfHDyeXJ9Z =r8So -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 18:06:03 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34E6A1065678; Wed, 10 Dec 2008 18:06:03 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail15.syd.optusnet.com.au (mail15.syd.optusnet.com.au [211.29.132.196]) by mx1.freebsd.org (Postfix) with ESMTP id BB3748FC13; Wed, 10 Dec 2008 18:06:02 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail15.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id mBAI60oL032389 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Dec 2008 05:06:00 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id mBAI5xGx007515; Thu, 11 Dec 2008 05:05:59 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id mBAI5x3h007514; Thu, 11 Dec 2008 05:05:59 +1100 (EST) (envelope-from peter) Date: Thu, 11 Dec 2008 05:05:59 +1100 From: Peter Jeremy To: =?iso-8859-1?Q?S=F8ren?= Schmidt Message-ID: <20081210180559.GC58682@server.vk2pj.dyndns.org> References: <20081209185236.GA1320@alf.bsdes.net> <493F84A4.1080308@yandex.ru> <20081210091107.GC1320@alf.bsdes.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="L9fXoLhVbEF7eqMD" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 18:06:03 -0000 --L9fXoLhVbEF7eqMD Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Dec-10 10:55:35 +0100, S=F8ren Schmidt wrote: >And you will not use 64bit DMA even if the chipset supports it. =20 >However I have not seen any chipsets supporting this fail, YMMV as =20 >usual :) There's a reference in wikipedia pointing to http://www.mail-archive.com/linux-ide@vger.kernel.org/msg06694.html that claims the AMD/ATI SB600 lies about supporting 64-bit DMA in AHCI mode. I have a SB600 but it doesn't have >4GB to test on. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --L9fXoLhVbEF7eqMD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAklABQcACgkQ/opHv/APuIe93QCfVomKQ7lkv9N/vjy3nkE5nSW5 Ot0An295JWo0uNF+4T48Dn41o5rfUFSR =+Jwp -----END PGP SIGNATURE----- --L9fXoLhVbEF7eqMD-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 18:52:58 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A58F81065673 for ; Wed, 10 Dec 2008 18:52:58 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mail-gx0-f19.google.com (mail-gx0-f19.google.com [209.85.217.19]) by mx1.freebsd.org (Postfix) with ESMTP id 69BCD8FC13 for ; Wed, 10 Dec 2008 18:52:58 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by gxk12 with SMTP id 12so654506gxk.7 for ; Wed, 10 Dec 2008 10:52:57 -0800 (PST) Received: by 10.151.51.18 with SMTP id d18mr2568296ybk.236.1228935164405; Wed, 10 Dec 2008 10:52:44 -0800 (PST) Received: by 10.151.68.11 with HTTP; Wed, 10 Dec 2008 10:52:44 -0800 (PST) Message-ID: Date: Wed, 10 Dec 2008 20:52:44 +0200 From: "Vlad GALU" To: "Mike Jakubik" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081210160325.GA72838@mr-happy.com> Cc: Jeff Blank , freebsd-stable@freebsd.org Subject: Re: bce(4) and rx errors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Dec 2008 18:52:58 -0000 On 12/10/08, Mike Jakubik wrote: > On Wed, December 10, 2008 11:03 am, Jeff Blank wrote: > > On Wed, Dec 10, 2008 at 04:59:26PM +0200, Vlad GALU wrote: > >> I have an application pulling about 220Kpps from a bce(4) card > >> (details below). At what seems to be random times, errors start > >> showing up on that interface (I'm watching it with netstat -w1 -I), so > >> about 10% of the initial 220Kpps is reported as errors. > > > > I'm also seeing a pretty steady stream of errors on both bce > > interfaces in a Dell PowerEdge 2950 III. In my case, the source > > is RELENG_7_1 from ~14:00 UTC yesterday (9 Dec). Throughput does not > > seem to be affected. "sysctl -a | egrep -i 'bce.*err'" yields all > > zeroes, for whatever that's worth. > > > See the "RELENG_7_1: bce driver change generating too much interrupts ?" > thread. This problem as surfaced since the recent bce driver changes. Thanks Mike, I'll give it a shot. -- ~/.signature: no such file or directory From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 19:27:50 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F1421065675 for ; Wed, 10 Dec 2008 19:27:50 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by mx1.freebsd.org (Postfix) with ESMTP id 3CC848FC1A for ; Wed, 10 Dec 2008 19:27:50 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by yx-out-2324.google.com with SMTP id 8so298699yxb.13 for ; Wed, 10 Dec 2008 11:27:49 -0800 (PST) Received: by 10.150.219.18 with SMTP id r18mr2670255ybg.89.1228937269337; Wed, 10 Dec 2008 11:27:49 -0800 (PST) Received: by 10.151.68.11 with HTTP; Wed, 10 Dec 2008 11:27:49 -0800 (PST) Message-ID: Date: Wed, 10 Dec 2008 21:27:49 +0200 From: "Vlad GALU" To: "Mike Jakubik" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081210160325.GA72838@mr-happy.com> Cc: Jeff Blank , freebsd-stable@freebsd.org Subject: Re: bce(4) and rx errors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Dec 2008 19:27:50 -0000 On 12/10/08, Vlad GALU wrote: > On 12/10/08, Mike Jakubik wrote: > > On Wed, December 10, 2008 11:03 am, Jeff Blank wrote: > > > On Wed, Dec 10, 2008 at 04:59:26PM +0200, Vlad GALU wrote: > > >> I have an application pulling about 220Kpps from a bce(4) card > > >> (details below). At what seems to be random times, errors start > > >> showing up on that interface (I'm watching it with netstat -w1 -I), so > > >> about 10% of the initial 220Kpps is reported as errors. > > > > > > I'm also seeing a pretty steady stream of errors on both bce > > > interfaces in a Dell PowerEdge 2950 III. In my case, the source > > > is RELENG_7_1 from ~14:00 UTC yesterday (9 Dec). Throughput does not > > > seem to be affected. "sysctl -a | egrep -i 'bce.*err'" yields all > > > zeroes, for whatever that's worth. > > > > > > See the "RELENG_7_1: bce driver change generating too much interrupts ?" > > thread. This problem as surfaced since the recent bce driver changes. > > > Thanks Mike, I'll give it a shot. Indeed, the errors seem to have gone away after rolling back the driver, as Xin Li suggested in another thread. Sorry for the noise! -- ~/.signature: no such file or directory From owner-freebsd-stable@FreeBSD.ORG Wed Dec 10 21:15:10 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EED9F106564A for ; Wed, 10 Dec 2008 21:15:10 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.190]) by mx1.freebsd.org (Postfix) with ESMTP id 9C37F8FC14 for ; Wed, 10 Dec 2008 21:15:10 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: by rn-out-0910.google.com with SMTP id j71so766765rne.12 for ; Wed, 10 Dec 2008 13:15:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=nWPoOyfB4SU89sDooHChEmA+6rEYniufgAFRlYcjgbQ=; b=RBgqHucgZd6SPDhAZzyXL8MDZ8xFzVKHu4HPIoGaqurTv6DwF+eMfD+fKaDwsChFul VaDBO6khA8AfUBv2ePAW9HX4DGY+nOq66gHa2uWjKe0N59IrWmtxfh7MOiST8JCftbSD ymyFaoeJfSrEMZJLrkCZS/0By14oHyv5WxOPY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=c5fChRCgObqjEy6gqoDpSNZM0kpcXW8FUCF6zr3Jt+eBspze2uDz/AzBF8oJsV+gQO wEU6FW4iED/qBf2C2h6vsTjYTG4esY1qjwJjhM/hhF4ODXxnLSgEF1dhsOfn34RIW8x5 78d7E810aYsr2e37dFw1yCtZWRgfucdeaEQTI= Received: by 10.100.138.10 with SMTP id l10mr1453110and.25.1228942117445; Wed, 10 Dec 2008 12:48:37 -0800 (PST) Received: by 10.100.209.20 with HTTP; Wed, 10 Dec 2008 12:48:37 -0800 (PST) Message-ID: <539c60b90812101248x2a964288w4e310a536c8b0fc@mail.gmail.com> Date: Wed, 10 Dec 2008 13:48:37 -0700 From: "Steve Franks" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: why can't multiple programs listen to cuaXYZ anymore? (7-stable) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 21:15:11 -0000 Before my last cvsup, I could have cutecom & a custom configuration app (i.e gpsd) running at the same time on the same serial port. Any incoming data, both would echo it, and as long as only one was outputting data, that worked fine too. Now it's 'broke'. I hear noise about TTY changes, I assume that changed the underlying devices, as well? This used to be a major perk over windows for embedded systems guys like me....makes debugging serial devices a snap. Steve From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 02:49:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3BD51065670 for ; Thu, 11 Dec 2008 02:49:43 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.225]) by mx1.freebsd.org (Postfix) with ESMTP id 8733F8FC08 for ; Thu, 11 Dec 2008 02:49:43 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so661666rvf.43 for ; Wed, 10 Dec 2008 18:49:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=ZDL0+brdl8NPk/hPUXGSk9wTWrqna+0ABjjaQ36I5X0=; b=nWFfaJIoEtYuqDWsqflgJINXk4P6wYblN/qsSSgZN7vQgh+xaOCbyLTlqq5D3GjC0P kuuopX1TH0R4cJ7qRGftzvStq5OV6kSWabEi7HxliDMYPnmbngWk+oEDWz5Rhh8jp9Dw jsRxsRoKQ9kMi5B9PrbFNR/SKsQQr3GU9JtlQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=dBQt46uEpURgX1ebra5eGC1vd/9H5+SQ6ZqGMoyQsnevbxMWCPo7Ndk0xDKlXVaOnU 82UEgdd1PW8oD3p13D0Y6yeGG8ShtmefAlt4hCKmty/BeU32ZKutxw5ONse2rCx1RzXu ntBHWb3jKnAgDue9VFVy2cUEDivZAMzkoP8Uw= Received: by 10.141.153.17 with SMTP id f17mr1008284rvo.99.1228963782994; Wed, 10 Dec 2008 18:49:42 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id b39sm2176657rvf.0.2008.12.10.18.49.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 10 Dec 2008 18:49:40 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id mBB2nZqj042955 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Dec 2008 11:49:35 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id mBB2nWeN042953; Thu, 11 Dec 2008 11:49:32 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 11 Dec 2008 11:49:32 +0900 From: Pyun YongHyeon To: Victor Balada Diaz Message-ID: <20081211024932.GC42370@cdnetworks.co.kr> References: <20081209185236.GA1320@alf.bsdes.net> <20081210061226.GC37837@cdnetworks.co.kr> <20081210085934.GB1320@alf.bsdes.net> <20081210102800.GH37837@cdnetworks.co.kr> <20081210113225.GD1320@alf.bsdes.net> <20081210120719.GK37837@cdnetworks.co.kr> <20081210140823.GF1320@alf.bsdes.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081210140823.GF1320@alf.bsdes.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2008 02:49:43 -0000 On Wed, Dec 10, 2008 at 03:08:24PM +0100, Victor Balada Diaz wrote: > On Wed, Dec 10, 2008 at 09:07:19PM +0900, Pyun YongHyeon wrote: [...] > > > > > > It seems that your controller supports MSI so you can set a tunable > > > > > > hw.re.msi_disable to 0 to enable MSI. With MSI you can remove > > > > > > interrupt sharing(e.g. add hw.re.msi_disable="0" to > > > > > > /boot/loader.conf file.) However there were several issues on re(4) > > > > > > w.r.t MSI so it was off by default. > > > > > > > > > > This is undocumented and with sysctl -a i can't find the tunable. Is this > > > > > a HEAD feature or it's also in 7.1 -BETA2? Should i add > > > > > > > > Yeah it's an undocmented feature. But most drivers written by me > > > > have similar kobs. Both HEAD and stable/7 including 7.1 BETA2 have > > > > the tunable. > > > > > > I think it could be great if you could document it or at least > > > show it by default when you do sysctl -ad with a small description. > > > > > > > If MSI worked as expected I would have documented it as I did > > in msk(4)/nfe(4)/ale(4)/age(4)/jme(4) etc. > > Using MSI on RealTek does not seem to stable. I tried hard to fix > > that but some users still reported watchdog timeouts. Working > > without documentation and hardware also made it hard to complete > > the work. This was the main reason why MSI was disabled on re(4). > > What do you think about adding a note in the man page telling that > it's experimental and in some cases it could improve the situation > but in others it will give errors? Based on the your testing I have idea how to mitigate the missing Tx completion interrupt. If all goes well re(4) could reliably take advantage of MSI on RealTek controllers. If that miserably fail I would do as you suggested. > > > > I think re(4) in HEAD needs more testing. As you might know RealTek > > produced too many chipsets. :-( > > Ok, i'll use the backported driver as it works better for me :-) > > If i can help you testing any patches i'm more than welcome to do it. > > Thanks a lot for your help Pyun YongHyeon. > You're welcome. -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 03:21:41 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82AAB1065676 for ; Thu, 11 Dec 2008 03:21:41 +0000 (UTC) (envelope-from tom.hurst@clara.net) Received: from ita.aagh.net (ita.aagh.net [208.86.225.114]) by mx1.freebsd.org (Postfix) with ESMTP id 53DD98FC16 for ; Thu, 11 Dec 2008 03:21:41 +0000 (UTC) (envelope-from tom.hurst@clara.net) Received: from cpc2-hart4-0-0-cust795.midd.cable.ntl.com ([81.104.123.28] helo=voi.aagh.net ident=mailnull) by ita.aagh.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LAbj9-000Hqq-8q; Thu, 11 Dec 2008 02:56:35 +0000 Received: from freaky by voi.aagh.net with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LAbj6-000Iaw-S4; Thu, 11 Dec 2008 02:56:32 +0000 Date: Thu, 11 Dec 2008 02:56:32 +0000 From: Thomas Hurst To: Patrick =?iso-8859-1?Q?Lamaizi=E8re?= Message-ID: <20081211025632.GA69815@voi.aagh.net> Mail-Followup-To: Patrick =?iso-8859-1?Q?Lamaizi=E8re?= , freebsd-stable Stable References: <20081208182112.GW58682@server.vk2pj.dyndns.org> <02D7BFFB-7B09-42DB-BBDF-F83AFDE45BD3@verweg.com> <20081209205806.6e3f0c5e@baby-jane> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20081209205806.6e3f0c5e@baby-jane> Organization: Not much. User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable Stable Subject: Re: visibility of release process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Dec 2008 03:21:41 -0000 * Patrick Lamaizière (patfbsd@davenulle.org) wrote: > Ruben van Staveren a écrit : > > Though experimental, I'm greatly enjoying > > http://www.secnetix.de/olli/FreeBSD/svnews/?p=/stable/7 > > Nice. There is also http://freshbsd.org/ (really cool IMHO). Thanks; I write/run that. I'm currently developing version 2, which should bring much better performance and more powerful filtering; e.g. by filename, multiple committers, branches, etc, as well as history all the way back to r1. Since it's working off a local SVN mirror rather than commit emails, it's also feasable to support things like local copies of diffs. Of course, now I need to generalize it back to the other BSD's -- Thomas 'Freaky' Hurst http://hur.st/ From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 07:57:10 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DAD0106564A; Thu, 11 Dec 2008 07:57:10 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.bsdes.net (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.freebsd.org (Postfix) with ESMTP id C99558FC17; Thu, 11 Dec 2008 07:57:09 +0000 (UTC) (envelope-from victor@bsdes.net) Received: by alf.bsdes.net (Postfix, from userid 1001) id DEDBC119CF7; Thu, 11 Dec 2008 08:57:07 +0100 (CET) Date: Thu, 11 Dec 2008 08:57:07 +0100 From: Victor Balada Diaz To: Pyun YongHyeon Message-ID: <20081211075707.GH1320@alf.bsdes.net> References: <20081209185236.GA1320@alf.bsdes.net> <20081210061226.GC37837@cdnetworks.co.kr> <20081210085934.GB1320@alf.bsdes.net> <20081210102800.GH37837@cdnetworks.co.kr> <20081210113225.GD1320@alf.bsdes.net> <20081210120719.GK37837@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20081210120719.GK37837@cdnetworks.co.kr> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2008 07:57:10 -0000 On Wed, Dec 10, 2008 at 09:07:19PM +0900, Pyun YongHyeon wrote: > On Wed, Dec 10, 2008 at 12:32:25PM +0100, Victor Balada Diaz wrote: > > Also i didn't see any problem with interfaces going up and down, > > but that usually happen after some hours of uptime, so i'll let > > you know if the error happens again. > > After writing to the HD with dd for a few hours and using stress -i 10 -d 10 the machine lost connectivity. I waited until today to be sure if the machine hung, paniced or just lost network connectivity. I don't have local access or serial access, so this is the only way i could do it. I've seen in the logs during the night various messages of: Dec 10 00:33:49 yac kernel: re0: watchdog timeout Dec 10 00:33:49 yac kernel: re0: link state changed to DOWN Dec 10 00:33:52 yac kernel: re0: link state changed to UP The interface never recovered and i wasn't able to ping the machine until i rebooted. Nagios was checking all the time and no recovery happened. The netstat -i in daily scripts shows just one Oerrs. I'm used to have a lot of them, but seems this time the card didn't recover from the only one. I also want to say that this is not a regression, as it happened before with 7.1 -BETA 2 code. Is there anything more i can try? Regards. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 08:00:27 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE4821065678; Thu, 11 Dec 2008 08:00:27 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.bsdes.net (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.freebsd.org (Postfix) with ESMTP id 7A0728FC12; Thu, 11 Dec 2008 08:00:27 +0000 (UTC) (envelope-from victor@bsdes.net) Received: by alf.bsdes.net (Postfix, from userid 1001) id 8143B119CF7; Thu, 11 Dec 2008 09:00:26 +0100 (CET) Date: Thu, 11 Dec 2008 09:00:26 +0100 From: Victor Balada Diaz To: Peter Jeremy Message-ID: <20081211080026.GI1320@alf.bsdes.net> References: <20081209185236.GA1320@alf.bsdes.net> <493F84A4.1080308@yandex.ru> <20081210091107.GC1320@alf.bsdes.net> <20081210180559.GC58682@server.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20081210180559.GC58682@server.vk2pj.dyndns.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org, =?iso-8859-1?Q?S=F8ren?= Schmidt Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2008 08:00:27 -0000 On Thu, Dec 11, 2008 at 05:05:59AM +1100, Peter Jeremy wrote: > On 2008-Dec-10 10:55:35 +0100, Søren Schmidt wrote: > >And you will not use 64bit DMA even if the chipset supports it. > >However I have not seen any chipsets supporting this fail, YMMV as > >usual :) > > There's a reference in wikipedia pointing to > http://www.mail-archive.com/linux-ide@vger.kernel.org/msg06694.html > that claims the AMD/ATI SB600 lies about supporting 64-bit DMA in AHCI > mode. I have a SB600 but it doesn't have >4GB to test on. I have 6 GB of RAM and can test patches, so once i'm done with the re(4) side of things i'll try commenting the code Soren's suggested and see if that improves the situation. Regards. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 08:10:47 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D19D1065677; Thu, 11 Dec 2008 08:10:47 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.bsdes.net (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.freebsd.org (Postfix) with ESMTP id E36558FC1D; Thu, 11 Dec 2008 08:10:46 +0000 (UTC) (envelope-from victor@bsdes.net) Received: by alf.bsdes.net (Postfix, from userid 1001) id A7D6D119CF7; Thu, 11 Dec 2008 09:10:45 +0100 (CET) Date: Thu, 11 Dec 2008 09:10:45 +0100 From: Victor Balada Diaz To: Pyun YongHyeon Message-ID: <20081211081045.GJ1320@alf.bsdes.net> References: <20081209185236.GA1320@alf.bsdes.net> <20081210061226.GC37837@cdnetworks.co.kr> <20081210085934.GB1320@alf.bsdes.net> <20081210102800.GH37837@cdnetworks.co.kr> <20081210113225.GD1320@alf.bsdes.net> <20081210120719.GK37837@cdnetworks.co.kr> <20081211075707.GH1320@alf.bsdes.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20081211075707.GH1320@alf.bsdes.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2008 08:10:47 -0000 On Thu, Dec 11, 2008 at 08:57:07AM +0100, Victor Balada Diaz wrote: > On Wed, Dec 10, 2008 at 09:07:19PM +0900, Pyun YongHyeon wrote: > > On Wed, Dec 10, 2008 at 12:32:25PM +0100, Victor Balada Diaz wrote: > > > Also i didn't see any problem with interfaces going up and down, > > > but that usually happen after some hours of uptime, so i'll let > > > you know if the error happens again. > > > > > After writing to the HD with dd for a few hours and using > stress -i 10 -d 10 the machine lost connectivity. I waited until > today to be sure if the machine hung, paniced or just lost network > connectivity. I don't have local access or serial access, so this > is the only way i could do it. I've seen in the logs during the > night various messages of: > > > Dec 10 00:33:49 yac kernel: re0: watchdog timeout > Dec 10 00:33:49 yac kernel: re0: link state changed to DOWN > Dec 10 00:33:52 yac kernel: re0: link state changed to UP > > The interface never recovered and i wasn't able to ping the machine > until i rebooted. Nagios was checking all the time and no recovery > happened. > > The netstat -i in daily scripts shows just one Oerrs. I'm used to > have a lot of them, but seems this time the card didn't recover from > the only one. I also want to say that this is not a regression, as > it happened before with 7.1 -BETA 2 code. > > Is there anything more i can try? Sorry it's too early in the morning and i thought today was 10 instead of 11. I don't even know the day i'm today. Looking at today's log i see no link state changed messages but i see this other messages that started happening more or less at the same time i lost connectivity to the server: Dec 10 18:20:32 yac kernel: re0: link state changed to DOWN Dec 10 18:20:32 yac kernel: re0: PHY read failed Sorry for the noise. Regards. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 09:01:08 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD8AE106567B for ; Thu, 11 Dec 2008 09:01:08 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by mx1.freebsd.org (Postfix) with ESMTP id 761368FC18 for ; Thu, 11 Dec 2008 09:01:08 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so770116rvf.43 for ; Thu, 11 Dec 2008 01:01:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=fLbw/t3tzJee0Th9UJhwQrBVybeNZsoUm95H7eiAEwo=; b=Qi6VC7q68J8pz+PYbRI9wuNjZeE2lJWFRqz5Nt3cCFAb91j12Rq22srgtNj/627DX9 2HsCKO4LcS+pjk2tNa1+mHapmS55dv1PbMcD9WEtJSNOef2za1V6P/Abnp+/1w68hPRs idNoTBaHXZc5tbQ59yFWgk1Sr/4EnLQEYgAWE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=QCqNST3sj4l5NzB0RciDraSzuoeAAFy1sAxWX1lyjlhGRAUlnjjfe3Wmi/vh4PKtpC Si+4XABobnxippxtCqD6fj3ivtb6GVTEYqCKxN8D97/XEQbFGiiuMCIPV30nSCfrTlk5 Qo1ZjM6AqCSQnFDhVkQjsPUDylA43s2qCYBA8= Received: by 10.141.42.10 with SMTP id u10mr1170696rvj.61.1228986068217; Thu, 11 Dec 2008 01:01:08 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id k2sm1250855rvb.8.2008.12.11.01.01.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 11 Dec 2008 01:01:07 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id mBB9106u044122 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Dec 2008 18:01:00 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id mBB90uHg044121; Thu, 11 Dec 2008 18:00:56 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 11 Dec 2008 18:00:56 +0900 From: Pyun YongHyeon To: Victor Balada Diaz Message-ID: <20081211090056.GH42370@cdnetworks.co.kr> References: <20081209185236.GA1320@alf.bsdes.net> <20081210061226.GC37837@cdnetworks.co.kr> <20081210085934.GB1320@alf.bsdes.net> <20081210102800.GH37837@cdnetworks.co.kr> <20081210113225.GD1320@alf.bsdes.net> <20081210120719.GK37837@cdnetworks.co.kr> <20081211075707.GH1320@alf.bsdes.net> <20081211081045.GJ1320@alf.bsdes.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081211081045.GJ1320@alf.bsdes.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2008 09:01:08 -0000 On Thu, Dec 11, 2008 at 09:10:45AM +0100, Victor Balada Diaz wrote: > On Thu, Dec 11, 2008 at 08:57:07AM +0100, Victor Balada Diaz wrote: > > On Wed, Dec 10, 2008 at 09:07:19PM +0900, Pyun YongHyeon wrote: > > > On Wed, Dec 10, 2008 at 12:32:25PM +0100, Victor Balada Diaz wrote: > > > > Also i didn't see any problem with interfaces going up and down, > > > > but that usually happen after some hours of uptime, so i'll let > > > > you know if the error happens again. > > > > > > > > After writing to the HD with dd for a few hours and using > > stress -i 10 -d 10 the machine lost connectivity. I waited until > > today to be sure if the machine hung, paniced or just lost network > > connectivity. I don't have local access or serial access, so this > > is the only way i could do it. I've seen in the logs during the > > night various messages of: > > > > > > Dec 10 00:33:49 yac kernel: re0: watchdog timeout > > Dec 10 00:33:49 yac kernel: re0: link state changed to DOWN > > Dec 10 00:33:52 yac kernel: re0: link state changed to UP > > > > The interface never recovered and i wasn't able to ping the machine > > until i rebooted. Nagios was checking all the time and no recovery > > happened. > > > > The netstat -i in daily scripts shows just one Oerrs. I'm used to > > have a lot of them, but seems this time the card didn't recover from > > the only one. I also want to say that this is not a regression, as > > it happened before with 7.1 -BETA 2 code. > > > > Is there anything more i can try? > > Sorry it's too early in the morning and i thought today was 10 > instead of 11. I don't even know the day i'm today. > > Looking at today's log i see no link state changed messages > but i see this other messages that started happening more or > less at the same time i lost connectivity to the server: > > Dec 10 18:20:32 yac kernel: re0: link state changed to DOWN > Dec 10 18:20:32 yac kernel: re0: PHY read failed > I've reverted r185756 which caused GMII access issues on some controllers. If you are brave enough to try beta code, you can get latest re(4) in the following URL. Note, I don't have PCIe based RealTek controllers so the code was not tested at all. http://people.freebsd.org/~yongari/re/if_re.c http://people.freebsd.org/~yongari/re/if_rlreg.h -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 09:08:56 2008 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 265B11065673; Thu, 11 Dec 2008 09:08:56 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id D381E8FC16; Thu, 11 Dec 2008 09:08:55 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1LAhXS-000GQW-BW; Thu, 11 Dec 2008 11:08:54 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Jaakko Heinonen In-reply-to: <20081210160059.GA3495@a91-153-125-115.elisa-laajakaista.fi> References: <20081210160059.GA3495@a91-153-125-115.elisa-laajakaista.fi> Comments: In-reply-to Jaakko Heinonen message dated "Wed, 10 Dec 2008 18:00:59 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Dec 2008 11:08:54 +0200 From: Danny Braniss Message-ID: Cc: Jeremy Chadwick , hackers@FreeBSD.org, stable@FreeBSD.org Subject: Re: zfs panics X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Dec 2008 09:08:56 -0000 > > Hi, > > On 2008-12-10, Danny Braniss wrote: > > from a solaris or linux client, doing a ls(1) of a nfs exported zfs file, > > for example: ls /net/zfs-server/h/.zfs/snapshot, > > panics the server. The server is running latest 7.1-prerelease. > > This has been reported as PR kern/125149. I have described the problem > in this message: > > http://lists.freebsd.org/pipermail/freebsd-fs/2008-October/005217.html > > See the PR for RELENG_7 patches. > (http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/125149) > > -- > Jaakko Hi Jaakko, did you apply the patches and it solved the problem? and, btw, which patch? To Jeremy, How about adding a line explaining that it would be prudent to 'zfs set snapdir=hidden' ..., or, of cource fix the bug :-) I will apply the patch/es and see what happens. cheers, danny From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 09:50:23 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A8C71065672; Thu, 11 Dec 2008 09:50:23 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.bsdes.net (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.freebsd.org (Postfix) with ESMTP id 3386C8FC19; Thu, 11 Dec 2008 09:50:22 +0000 (UTC) (envelope-from victor@bsdes.net) Received: by alf.bsdes.net (Postfix, from userid 1001) id C8AAD119CF7; Thu, 11 Dec 2008 10:50:21 +0100 (CET) Date: Thu, 11 Dec 2008 10:50:21 +0100 From: Victor Balada Diaz To: Pyun YongHyeon Message-ID: <20081211095021.GL1320@alf.bsdes.net> References: <20081209185236.GA1320@alf.bsdes.net> <20081210061226.GC37837@cdnetworks.co.kr> <20081210085934.GB1320@alf.bsdes.net> <20081210102800.GH37837@cdnetworks.co.kr> <20081210113225.GD1320@alf.bsdes.net> <20081210120719.GK37837@cdnetworks.co.kr> <20081211075707.GH1320@alf.bsdes.net> <20081211081045.GJ1320@alf.bsdes.net> <20081211090056.GH42370@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20081211090056.GH42370@cdnetworks.co.kr> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2008 09:50:23 -0000 On Thu, Dec 11, 2008 at 06:00:56PM +0900, Pyun YongHyeon wrote: > On Thu, Dec 11, 2008 at 09:10:45AM +0100, Victor Balada Diaz wrote: > > On Thu, Dec 11, 2008 at 08:57:07AM +0100, Victor Balada Diaz wrote: > > > On Wed, Dec 10, 2008 at 09:07:19PM +0900, Pyun YongHyeon wrote: > > > > On Wed, Dec 10, 2008 at 12:32:25PM +0100, Victor Balada Diaz wrote: > > > > > Also i didn't see any problem with interfaces going up and down, > > > > > but that usually happen after some hours of uptime, so i'll let > > > > > you know if the error happens again. > > > > > > > > > > > After writing to the HD with dd for a few hours and using > > > stress -i 10 -d 10 the machine lost connectivity. I waited until > > > today to be sure if the machine hung, paniced or just lost network > > > connectivity. I don't have local access or serial access, so this > > > is the only way i could do it. I've seen in the logs during the > > > night various messages of: > > > > > > > > > Dec 10 00:33:49 yac kernel: re0: watchdog timeout > > > Dec 10 00:33:49 yac kernel: re0: link state changed to DOWN > > > Dec 10 00:33:52 yac kernel: re0: link state changed to UP > > > > > > The interface never recovered and i wasn't able to ping the machine > > > until i rebooted. Nagios was checking all the time and no recovery > > > happened. > > > > > > The netstat -i in daily scripts shows just one Oerrs. I'm used to > > > have a lot of them, but seems this time the card didn't recover from > > > the only one. I also want to say that this is not a regression, as > > > it happened before with 7.1 -BETA 2 code. > > > > > > Is there anything more i can try? > > > > Sorry it's too early in the morning and i thought today was 10 > > instead of 11. I don't even know the day i'm today. > > > > Looking at today's log i see no link state changed messages > > but i see this other messages that started happening more or > > less at the same time i lost connectivity to the server: > > > > Dec 10 18:20:32 yac kernel: re0: link state changed to DOWN > > Dec 10 18:20:32 yac kernel: re0: PHY read failed > > > > I've reverted r185756 which caused GMII access issues on some > controllers. If you are brave enough to try beta code, you can > get latest re(4) in the following URL. Note, I don't have PCIe > based RealTek controllers so the code was not tested at all. > > http://people.freebsd.org/~yongari/re/if_re.c > http://people.freebsd.org/~yongari/re/if_rlreg.h I've recompiled the kernel with the first file in sys/dev/re/ and the second one in sys/pci/. I'm still testing with MSI enabled. So far tried rebooting using nextboot(8) (just in case i lost the network card i could boot again) and the card seems to work but i'll continue stress testing the machine with stress + dd + iperf and see if i can take it down. I'll let you know how it goes. Regards. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 10:28:34 2008 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 74BC5106564A; Thu, 11 Dec 2008 10:28:34 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id 2DEBE8FC13; Thu, 11 Dec 2008 10:28:34 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1LAimW-000HTT-JN; Thu, 11 Dec 2008 12:28:32 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Jaakko Heinonen In-reply-to: References: <20081210160059.GA3495@a91-153-125-115.elisa-laajakaista.fi> Comments: In-reply-to Danny Braniss message dated "Thu, 11 Dec 2008 11:08:54 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Dec 2008 12:28:32 +0200 From: Danny Braniss Message-ID: Cc: stable@FreeBSD.org, hackers@FreeBSD.org Subject: Re: zfs panics X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Dec 2008 10:28:34 -0000 > > > > Hi, > > > > On 2008-12-10, Danny Braniss wrote: > > > from a solaris or linux client, doing a ls(1) of a nfs exported zfs file, > > > for example: ls /net/zfs-server/h/.zfs/snapshot, > > > panics the server. The server is running latest 7.1-prerelease. > > > > This has been reported as PR kern/125149. I have described the problem > > in this message: > > > > http://lists.freebsd.org/pipermail/freebsd-fs/2008-October/005217.html > > > > See the PR for RELENG_7 patches. > > (http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/125149) > > > > -- > > Jaakko > > Hi Jaakko, > did you apply the patches and it solved the problem? > and, btw, which patch? > > To Jeremy, > How about adding a line explaining that it would be > prudent to 'zfs set snapdir=hidden' ..., or, of cource > fix the bug :-) > I will apply the patch/es and see what happens. > > cheers, > danny the patch to nfs_server.c does indeed prevent the panics. danny From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 23:16:52 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0C4B106564A for ; Thu, 11 Dec 2008 23:16:52 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id 82EB78FC23 for ; Thu, 11 Dec 2008 23:16:52 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.14.3/jtpda-5.4) with ESMTP id mBBN1UrF077657 for ; Fri, 12 Dec 2008 00:01:31 +0100 (CET) X-Ids: 166 Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.13.3/jtpda-5.2) with ESMTP id mBBN1TaI094216 for ; Fri, 12 Dec 2008 00:01:29 +0100 (MET) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.13.3/8.13.1/Submit) id mBBN1TJH094213; Fri, 12 Dec 2008 00:01:29 +0100 (MET) (envelope-from arno) To: freebsd-stable@freebsd.org From: "Arno J. Klaassen" Date: 12 Dec 2008 00:01:29 +0100 Message-ID: Lines: 60 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (shiva.jussieu.fr [134.157.0.166]); Fri, 12 Dec 2008 00:01:31 +0100 (CET) X-Virus-Scanned: ClamAV 0.94.2/8747/Thu Dec 11 20:22:53 2008 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at jchkmail.jussieu.fr with ID 49419BCA.008 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 49419BCA.008/134.157.184.22/heho.snv.jussieu.fr/heho.snv.jussieu.fr/ X-j-chkmail-Score: MSGID : 49419BCA.008 on jchkmail.jussieu.fr : j-chkmail score : . : R=. U=. O=. B=0.009 -> S=0.009 X-j-chkmail-Status: Ham Subject: 7.1-PRERELEASE: asus M3A / Phenom X4 / powerd freeze X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Dec 2008 23:16:53 -0000 hello, yet another powerd SOS : on an ASUS M3A78-EM MB with Phenom 9750 and 8 gig memory, starting powerd freezes the box after slowing down a bit cpu frequency. [IMHO] usefull bit of info : FreeBSD m34.scito.local 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Thu Dec 11 14:24:39 CET 2008 root@m34.scito.local:/usr/obj/raid1/bsd/src7/sys/M3A78-EM amd64 CPU: AMD Phenom(tm) 9750 Quad-Core Processor (2410.66-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x100f23 Stepping = 3 Features=0x178bfbff Features2=0x802009> AMD Features=0xee500800 AMD Features2=0x7ff,,,Prefetch,,> Cores per package: 4 usable memory = 8547172352 (8151 MB) avail memory = 8268722176 (7885 MB) ACPI APIC Table: <102408 APIC2239> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: <102408 XSDT2239> on motherboard ... cpu0: on acpi0 acpi_throttle0: on cpu0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 dev.cpu.0.freq_levels: 2398/-1 2098/-1 1798/-1 1498/-1 1199/-1 899/-1 599/-1 299/-1 further : - I set debug.cpufreq.lowest superior to 1500 : system remains up but only when pushing really slightly - I set debug.cpufreq.lowest inferior to 1100 : freeze garantueed - I define hint.acpi_throttle.0.disabled="1" in loader.conf then no dev.cpu.0.freq is showing up ... (as if only acpi_throttle is attaching and not powernow) Let me know what I can test further. Best, Arno From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 23:18:34 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 227FB1065670 for ; Thu, 11 Dec 2008 23:18:34 +0000 (UTC) (envelope-from ghelmer@palisadesys.com) Received: from cetus.palisadesys.com (cetus.palisadesys.com [205.237.115.21]) by mx1.freebsd.org (Postfix) with ESMTP id AFB358FC12 for ; Thu, 11 Dec 2008 23:18:33 +0000 (UTC) (envelope-from ghelmer@palisadesys.com) Received: from magellan.palisadesys.com (serverwatch [172.16.1.98]) by cetus.palisadesys.com (8.14.1/8.14.1) with ESMTP id mBBN22td060427 for ; Thu, 11 Dec 2008 17:02:02 -0600 (CST) (envelope-from ghelmer@palisadesys.com) Received: from [172.16.2.242] (cetus.palisadesys.com [205.237.115.21]) (authenticated bits=0) by magellan.palisadesys.com (8.14.2/8.14.2) with ESMTP id mBBN1ri0063696 for ; Thu, 11 Dec 2008 17:01:53 -0600 (CST) (envelope-from ghelmer@palisadesys.com) Message-ID: <49419BE0.2070502@palisadesys.com> Date: Thu, 11 Dec 2008 17:01:52 -0600 From: Guy Helmer User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (magellan.palisadesys.com [205.237.115.20]); Thu, 11 Dec 2008 17:01:53 -0600 (CST) X-Palisade-MailScanner-Information: Please contact the ISP for more information X-Palisade-MailScanner: Found to be clean X-Palisade-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (not cached, score=-3.799, required 6, ALL_TRUSTED -1.80, BAYES_00 -2.60, J_CHICKENPOX_33 0.60) X-Palisade-MailScanner-From: ghelmer@palisadesys.com Subject: 7.1RC1: system 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: Thu, 11 Dec 2008 23:18:34 -0000 I have a recurring hang on FreeBSD 7.1 roughly-RC1 (releng_7_1 checkout as of 2008-12-08) on a dual-CPU hyperthreaded Xeon i386. I've dropped into the kernel debugger on the VGA console and transcribed the following information (if I omit anything critical, let me know -- the machine is still sitting at the debugger prompt) : > where pid 20 tid 100018 td 0xc45008c0 kdb_enter_why scgetc sckdbevent kdbmux_intr kdbmux_kdb_intr taskqueue_run taskqueue_swi_giant_run ithread_loop fork_exit(c063cce0, c44ac590, e4a36d38) at 0xc063a624 = fork_exit+0x94 fork_trampoline() at 0xc07e41a0 = fork_trampoline+0x8 > show allpcpu cpuid 0 in idle cpuid 1: proc 23457 cpuid 2: idle cpuid 3: swi6 proc 20 > show alllocks pid 23708 vmstat: shared sx allproc, exclusive sx sysctl pid 23675 php: exclusive sx user map pid 4630 tcsh: shared sx proctree pid 3838 sshd: shared sx proctree pid 2139 icapd: shared sx proctree pid 1425 postgres: shared sx proctree pid 20 swi6: exclusive sleep mtx Giant > show sleepchain 23708 thread 100050 (pid 23708, vmstat) blocked on sx "user map" XLOCK thread 100056 (pid 23675, initial thread) is on a run queue > show sleepchain 4630 thread 100093 (pid 4630, tcsh) blocked on sx "allproc" SLOCK (count 1) > show sleepchain 3838 thread 100065 (pid 3838, sshd) blocked on sx "allproc" SLOCK (count 1) > show sleepchain 2139 thread 100136 (pid 2139, icapd) blocked on sx "allproc" SLOCK (count 1) > show sleepchain 1425 thread 100140 (pid 1425, initial thread) blocked on sx "allproc" SLOCK (count 1) > where 23708 ... syscall 202 sysctl > where 23675 ... trap 0xc > where 4630 ... syscall 66 vfork > where 3838 ... syscall 2 fork > where 2139 ... syscall 2 fork > where 1425 ... syscall 2 fork Kernel configuration file: ident PALISADE-DEBUG options MUTEX_DEBUG options WITNESS options WITNESS_KDB options WITNESS_SKIPSPIN options KDB options KDB_TRACE options DDB options DDB_NUMSYM options GDB cpu I686_CPU # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking #options INET6 # IPv6 communications protocols #options SCTP # Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL # Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY # BSD 4.3 TTY compat [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options SHMMAXPGS=4096 # max shared mem pages (4k on i386) options SHMSEG=256 # max shared mem segments per process options SEMMNI=256 # number of semaphore identifiers options SEMMNS=512 # number of semaphores options SEMMNU=256 # number of undo structures options SEMMAP=256 # entries in semaphore map options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. options STOP_NMI # Stop CPUS using NMI instead of IPI options AUDIT # Security event auditing options DEVICE_POLLING options MAXDSIZ=(1024UL*1024*1024) # See /sys/conf/NOTES for info options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #enable logging to syslogd(8) options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity options IPFIREWALL_FORWARD #packet destination changes options DUMMYNET #Packet shaping # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel device apic # I/O APIC # CPU frequency control device cpufreq # Bus support. device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI Controllers #device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. device ahd # AHA39320/29320 and onboard AIC79xx devices options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. #device amd # AMD 53C974 (Tekram DC-390(T)) #device hptiop # Highpoint RocketRaid 3xxx series #device isp # Qlogic family #device ispfw # Firmware for QLogic HBAs- normally a module device mpt # LSI-Logic MPT-Fusion #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') #device trm # Tekram DC395U/UW/F DC315U adapters #device adv # Advansys SCSI adapters #device adw # Advansys wide SCSI adapters #device aha # Adaptec 154x SCSI adapters #device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. #device bt # Buslogic/Mylex MultiMaster SCSI adapters #device ncv # NCR 53C500 #device nsp # Workbit Ninja SCSI-3 #device stg # TMC 18C30/18C50 # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers interfaced to the SCSI subsystem #device amr # AMI MegaRAID #device arcmsr # Areca SATA II RAID #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID #device ciss # Compaq Smart RAID 5* #device dpt # DPT Smartcache III, IV - See NOTES for options #device hptmv # Highpoint RocketRAID 182x #device hptrr # Highpoint RocketRAID 17xx, 22xx, 23xx, 25xx #device iir # Intel Integrated RAID #device ips # IBM (Adaptec) ServeRAID #device mly # Mylex AcceleRAID/eXtremeRAID device twa # 3ware 9000 series PATA/SATA RAID # RAID controllers device aac # Adaptec FSA RAID #device aacp # SCSI passthrough for aac (requires CAM) #device ida # Compaq Smart RAID device mfi # LSI MegaRAID SAS #device mlx # Mylex DAC960 family #device pst # Promise Supertrak SX6000 device twe # 3ware ATA RAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device kbdmux # keyboard multiplexer device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. device pmtimer # PCCARD (PCMCIA) support # PCMCIA and cardbus bridge support device cbb # cardbus (yenta) bridge device pccard # PC Card (16-bit) bus device cardbus # CardBus (32-bit) bus # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports device uart # Generic UART driver # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # If you've got a "dumb" serial or parallel PCI card that is # supported by the puc(4) glue driver, uncomment the following # line to enable it (connects to sio, uart and/or ppc drivers): #device puc # PCI Ethernet NICs. device de # DEC/Intel DC21x4x (``Tulip'') device em # Intel PRO/1000 adapter Gigabit Ethernet Card device ixgb # Intel PRO/10GbE Ethernet Card device le # AMD Am7900 LANCE and Am79C9xx PCnet device txp # 3Com 3cR990 (``Typhoon'') device vx # 3Com 3c590, 3c595 (``Vortex'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device bce # Broadcom BCM5706/BCM5708 Gigabit Ethernet device bfe # Broadcom BCM440x 10/100 Ethernet device bge # Broadcom BCM570xx Gigabit Ethernet device dc # DEC/Intel 21143 and various workalikes device fxp # Intel EtherExpress PRO/100B (82557, 82558) device lge # Level 1 LXT1001 gigabit Ethernet device msk # Marvell/SysKonnect Yukon II Gigabit Ethernet device nfe # nVidia nForce MCP on-board Ethernet device nge # NatSemi DP83820 gigabit Ethernet #device nve # nVidia nForce MCP on-board Ethernet Networking #device pcn # AMD Am79C97x PCI 10/100(precedence over 'lnc') device re # RealTek 8139C+/8169/8169S/8110S device rl # RealTek 8129/8139 #device sf # Adaptec AIC-6915 (``Starfire'') device sis # Silicon Integrated Systems SiS 900/SiS 7016 device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet #device ste # Sundance ST201 (D-Link DFE-550TX) #device stge # Sundance/Tamarack TC9021 gigabit Ethernet #device ti # Alteon Networks Tigon I/II gigabit Ethernet #device tl # Texas Instruments ThunderLAN #device tx # SMC EtherPower II (83c170 ``EPIC'') device vge # VIA VT612x gigabit Ethernet #device vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. pccard NICs included. #device cs # Crystal Semiconductor CS89x0 NIC # 'device ed' requires 'device miibus' #device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards #device ex # Intel EtherExpress Pro/10 and Pro/10+ #device ep # Etherlink III based cards #device fe # Fujitsu MB8696x based cards #device ie # EtherExpress 8/16, 3C507, StarLAN 10 etc. #device lnc # NE2100, NE32-VL Lance Ethernet cards #device sn # SMC's 9000 series of Ethernet chips #device xe # Xircom pccard Ethernet # Wireless NIC cards #device wlan # 802.11 support #device wlan_wep # 802.11 WEP support #device wlan_ccmp # 802.11 CCMP support #device wlan_tkip # 802.11 TKIP support #device wlan_amrr # AMRR transmit rate control algorithm #device wlan_scan_ap # 802.11 AP mode scanning #device wlan_scan_sta # 802.11 STA mode scanning #device an # Aironet 4500/4800 802.11 wireless NICs. #device ath # Atheros pci/cardbus NIC's #device ath_hal # Atheros HAL (Hardware Access Layer) #device ath_rate_sample # SampleRate tx rate control for ath #device awi # BayStack 660 and others #device ral # Ralink Technology RT2500 wireless NICs. #device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. #device wl # Older non 802.11 Wavelan wireless NIC. # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support #device sl # Kernel SLIP #device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" #device gif # IPv6 and IPv4 tunneling #device faith # IPv6-to-IPv4 relaying (translation) device firmware # firmware assist module # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer #device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse #device ural # Ralink Technology RT2500USB wireless NICs #device rum # Ralink Technology RT2501USB wireless NICs #device urio # Diamond Rio 500 MP3 player #device uscanner # Scanners # USB Ethernet, requires miibus device aue # ADMtek USB Ethernet device axe # ASIX Electronics USB Ethernet device cdce # Generic USB over Ethernet device cue # CATC USB Ethernet device kue # Kawasaki LSI USB Ethernet device rue # RealTek RTL8150 USB Ethernet # FireWire support #device firewire # FireWire bus code #device sbp # SCSI over FireWire (Requires scbus and da) #device fwe # Ethernet over FireWire (non-standard!) #device fwip # IP over FireWire (RFC 2734,3146) #device dcons # Dumb console driver #device dcons_crom # Configuration ROM for dcons From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 00:22:33 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E18DA106564A for ; Fri, 12 Dec 2008 00:22:33 +0000 (UTC) (envelope-from m4gicite@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.187]) by mx1.freebsd.org (Postfix) with ESMTP id 7BCF38FC12 for ; Fri, 12 Dec 2008 00:22:33 +0000 (UTC) (envelope-from m4gicite@gmail.com) Received: by fk-out-0910.google.com with SMTP id k31so1222793fkk.11 for ; Thu, 11 Dec 2008 16:22:32 -0800 (PST) Received: by 10.181.21.2 with SMTP id y2mr971810bki.144.1229022790837; Thu, 11 Dec 2008 11:13:10 -0800 (PST) Received: by 10.180.214.7 with HTTP; Thu, 11 Dec 2008 11:13:10 -0800 (PST) Message-ID: Date: Thu, 11 Dec 2008 19:13:10 +0000 From: Ryan To: "Joel Dahl" In-Reply-To: <49103869.3080709@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <490F40CB.8040605@FreeBSD.org> <49103869.3080709@FreeBSD.org> Cc: freebsd-stable@freebsd.org Subject: Re: Install issues with 7.x X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Dec 2008 00:22:34 -0000 Finally had time to understand some how release works and made some new cds. Some new updates to the situation since as I am still having issues. I was not able to figure out how to make release with a custom kernel, would always fail that step so I had to stick with GENERIC. To simulate taking out firewire support I just deleted the corresponding kernel modules in /boot/kernel and remade the iso. Stable as of 12-07-2008 is giving the same feedback as 7.1-B2 but actually gives a panic screen. panic: run_interrupt_driven_config_hooks: waited too long cpuid = 0 KDB: enter: panic [thread pid 0 tid 100000 ] Stopped at kdb_enter+0x3a: movl $0,kdb_why db> There has been a bios update recently and have applied it, but there has been no change in any of the tests by a quick glance. If it makes a difference the cds I create with cdrecord generate the added errors acd0: FAILURE - READ BIG timed out. I don't think that has anything to do with it, just saying it for full disclosure. Disregard if irrelevant. That error applies to only the stable builds I made. On Tue, Nov 4, 2008 at 11:56 AM, Joel Dahl wrote: > Ryan skrev: >> >> Sadly with the quality of BIOS recently, that is not an option. Not >> much to offer. Attached is a picture of what I have to change. Other >> and XP are the same, Vista unlocks AHCI. >> >> Another way of accomplishing disabling firewire is to remake the >> install CD with a different kernel and not quite sure how to do that. > > Take a look at the release(7) manpage for information about building your > own customized release CD. > > -- > Joel > > From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 01:31:17 2008 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 8378F1065670 for ; Fri, 12 Dec 2008 01:31:17 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by mx1.freebsd.org (Postfix) with ESMTP id 490588FC16 for ; Fri, 12 Dec 2008 01:31:17 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1134700rvf.43 for ; Thu, 11 Dec 2008 17:31:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=wtTvQypJ4UVzCmmQTk/p8+cZuK9iiOHU+OVpu+8TIaM=; b=r+RKeMjI2gW6IE9ZCOUZhokPvMvIbWKoB4KHOTWVFnKbVPqoev2nWEueaVPpeG7xpL lnvPYACAIdDU0won300B95K9d4EleX1GX2kQHjsDxsH9jAT0urARhngfAy8RexfXFc3f g0z+LMnQrSyirjKo3ReCFLIYcmsDR8gyYQR9E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=Z5QdkWH5aaCwf0qxUq0EMwfTbO1OXgrSsIuz3Lau9APtT7Xxdj/BngNwxjSGgXVztg gCEAYsdfUDaX7Y2dVj86LlEAtRp4Mjq5dmmbL908+sDiAyUp2cObAMuN9Qkjipd/PRrJ 1q6/1GbkjBZ5TIQwFabxNShlwu1U81Q3CYqGY= Received: by 10.140.125.1 with SMTP id x1mr1612845rvc.73.1229045476873; Thu, 11 Dec 2008 17:31:16 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id c20sm1681757rvf.5.2008.12.11.17.31.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 11 Dec 2008 17:31:15 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id mBC1VARI047150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Dec 2008 10:31:10 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id mBC1VAgf047149; Fri, 12 Dec 2008 10:31:10 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 12 Dec 2008 10:31:10 +0900 From: Pyun YongHyeon To: Goran Lowkrantz Message-ID: <20081212013110.GF46707@cdnetworks.co.kr> References: <20081209114723.GE33723@cdnetworks.co.kr> <80D07D8C17DAC73D69DCDC9A@[172.16.2.124]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: Regression in vr - not receiveing multicast X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2008 01:31:17 -0000 On Wed, Dec 10, 2008 at 08:06:16AM +0100, Goran Lowkrantz wrote: > --On December 9, 2008 12:53:05 +0100 Goran Lowkrantz > wrote: > > >--On December 9, 2008 20:47:23 +0900 Pyun YongHyeon > >wrote: > > > >>On Tue, Dec 09, 2008 at 10:40:17AM +0100, Goran Lowkrantz wrote: > >> > Hi, > >> > > >> > in July, vr had this problem and was fixed: > >> > > >> > > >> > > >> > but now it's back again! > >> > > >> > >>There was just one bug fix since then and I guess the fix is not > >>related with your issue. > >> > >> > On a system with the following: > >> > 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Thu Oct 16 12:31:04 UTC 2008 > >> > > >> > I have to set all vr interfaces in promisc to get routing info. > >> > > >> > Using Quagga > >> > # pkg_info -Ix uagga > >> > quagga-0.99.10_3 Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route > >>software > > >> > on an inner network using RIPv2 > >> > # ifmcstat -i vr0 > >> > vr0: > >> > inet xxx.xxx.xxx.xxx > >> > group 224.0.0.9 > >> > igmpv2 > >> > mcast-macaddr 01:00:5e:00:00:09 refcnt 1 > >> > group 224.0.0.1 > >> > mcast-macaddr 01:00:5e:00:00:01 refcnt 1 > >> > > >> > > >> > On the same box, we have some em devices also and they work without > >>any > problems. > >> > > >> > >>There is fundamental differences between em(4) and vr(4). The > >>vr(4) for VT6105M takes advantage of perfect multicast filtering > >>feature which is not present on all em(4) interface. Perfect > >>multicast filtering can reduce unwanted multicast traffics such > >>that it could save a lot of CPU cycles. The downside is that vr(4) > >>cannot accept multicast frames for a multicast group without > >>joining the multicast group first. > >>For multicast routing purpose I guess 'options MROUTING' kernel > >>option should be enabled to accept all multicast frames. > >>Does your kernel have that option? > > > >No it has not. I will create such a beast and return with stories. > > > > > I have tried with 'options MROUTING' and it didn't work. > > Did I miss something? Do I have to install and run mrouted also? > > It seems like maybe the first two packages are accepted after registration > as I don't lose the routes until after about 6 min uptime. But to get > further updates, I need the interfaces in promisc. > > So, next step? FYI: I've disabled multicast perfect filtering(r185962). -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 03:00:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 739D51065677 for ; Fri, 12 Dec 2008 03:00:43 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by mx1.freebsd.org (Postfix) with ESMTP id 2829D8FC17 for ; Fri, 12 Dec 2008 03:00:43 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so586461ywe.13 for ; Thu, 11 Dec 2008 19:00:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=OIuwbQLGBbjhXN7SLYimNRdWxtwqYruLQzzORMkoL5Q=; b=f6I6utLOWDT4E8jLvvi3y0i73dMJKk1MsIfpsp3azzINR4c8OdSVzhpj9PTj23122S YfxOjmowBKtworBRs4RZujKTaAmqHDJSZeeBs6/Y6Ghn49+rx7eWNh4ASChuvmcmcMDX 8p7PJ2hrAJhzUYmYMncS4ne8TkA20yBrFab04= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=gDicGcp4bSmU6YcWim0n6HXgiX9UebmFO57cIy1VLbA/UWAdNefu1kvZcjrIcvMXqU yr0s147PgKuSdg4Va0/WpAa/E9yjEKZAkhb/axaOewroHpRVdu/naNc1I7+DraWSqb1A zfTSx+R9Xe4FybcJkEDmGcZ68WTJd18NBHIVs= Received: by 10.231.20.1 with SMTP id d1mr41201ibb.19.1229050841802; Thu, 11 Dec 2008 19:00:41 -0800 (PST) Received: by 10.231.18.139 with HTTP; Thu, 11 Dec 2008 19:00:41 -0800 (PST) Message-ID: <3a142e750812111900u1d9264bh27d39092f5dcc4bf@mail.gmail.com> Date: Fri, 12 Dec 2008 04:00:41 +0100 From: "Paul B. Mahol" To: "Guy Helmer" In-Reply-To: <49419BE0.2070502@palisadesys.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <49419BE0.2070502@palisadesys.com> Cc: freebsd-stable@freebsd.org Subject: Re: 7.1RC1: system 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: Fri, 12 Dec 2008 03:00:43 -0000 On 12/12/08, Guy Helmer wrote: > I have a recurring hang on FreeBSD 7.1 roughly-RC1 (releng_7_1 checkout > as of 2008-12-08) on a dual-CPU hyperthreaded Xeon i386. I've dropped > into the kernel debugger on the VGA console and transcribed the > following information (if I omit anything critical, let me know -- the > machine is still sitting at the debugger prompt) : > > > where > pid 20 tid 100018 td 0xc45008c0 > kdb_enter_why > scgetc > sckdbevent > kdbmux_intr > kdbmux_kdb_intr > taskqueue_run > taskqueue_swi_giant_run > ithread_loop > fork_exit(c063cce0, c44ac590, e4a36d38) at 0xc063a624 = fork_exit+0x94 > fork_trampoline() at 0xc07e41a0 = fork_trampoline+0x8 > > > show allpcpu > cpuid 0 in idle > cpuid 1: proc 23457 > cpuid 2: idle > cpuid 3: swi6 proc 20 what is proc 23457? -- Paul From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 09:27:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CFF71065670 for ; Fri, 12 Dec 2008 09:27:43 +0000 (UTC) (envelope-from rebehn@ant.uni-bremen.de) Received: from antsrv1.ant.uni-bremen.de (antsrv1.ant.uni-bremen.de [134.102.176.16]) by mx1.freebsd.org (Postfix) with ESMTP id 2C5CF8FC13 for ; Fri, 12 Dec 2008 09:27:43 +0000 (UTC) (envelope-from rebehn@ant.uni-bremen.de) Received: from bremerhaven.ant.uni-bremen.de ([134.102.176.10]) by antsrv1.ant.uni-bremen.de with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1LB4JB-000PR3-Qu; Fri, 12 Dec 2008 10:27:41 +0100 Message-Id: <903DEF0D-724B-4A56-95DC-A557F203E5E1@ant.uni-bremen.de> From: Heinrich Rebehn To: Heinrich Rebehn In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Fri, 12 Dec 2008 10:27:41 +0100 References: X-Mailer: Apple Mail (2.919.2) Cc: freebsd-stable@freebsd.org Subject: Re: iir(4) support under 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2008 09:27:43 -0000 On Dec 10, 2008, at 2:54 PM, Heinrich Rebehn wrote: > Hi list, > > i am planning to upgrade our main server from 6.1 to 7.1. > The machine has a ICP Vortex GDT8524RZ raid controller which is > handled buy the iir(4) driver. > > Since i have seen various discussions in the past about Adaptec no > longer supporting these controllers, driver reaching EOE, data > corruption in 64bit configurtions with > 4G RAM and so on, i just > wanted to ask what the current state of the driver is. > > Thanks for your help, > Hmmm? nobody using this stuff anymore??? -Heinrich From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 09:49:05 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1B1610656DC for ; Fri, 12 Dec 2008 09:49:05 +0000 (UTC) (envelope-from rink@rink.nu) Received: from mx1.rink.nu (gloom.rink.nu [213.34.49.2]) by mx1.freebsd.org (Postfix) with ESMTP id 924EE8FC24 for ; Fri, 12 Dec 2008 09:49:05 +0000 (UTC) (envelope-from rink@rink.nu) Received: from localhost (localhost [127.0.0.1]) by mx1.rink.nu (Postfix) with ESMTP id 7CFA16D42B; Fri, 12 Dec 2008 10:49:15 +0100 (CET) X-Virus-Scanned: amavisd-new at rink.nu Received: from mx1.rink.nu ([213.34.49.2]) by localhost (gloom.rink.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PpdEvPRDu60i; Fri, 12 Dec 2008 10:49:12 +0100 (CET) Received: by mx1.rink.nu (Postfix, from userid 1000) id 575866D423; Fri, 12 Dec 2008 10:49:12 +0100 (CET) Date: Fri, 12 Dec 2008 10:49:12 +0100 From: Rink Springer To: Heinrich Rebehn Message-ID: <20081212094912.GA54988@rink.nu> References: <903DEF0D-724B-4A56-95DC-A557F203E5E1@ant.uni-bremen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <903DEF0D-724B-4A56-95DC-A557F203E5E1@ant.uni-bremen.de> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: iir(4) support under 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2008 09:49:05 -0000 Hi Heinrich, On Fri, Dec 12, 2008 at 10:27:41AM +0100, Heinrich Rebehn wrote: > Hmmm? nobody using this stuff anymore??? FWIW, we have some IBM servers which feature an iir(4) too and they are unusuable on >=7.0 - the iir(4) does not initialize correctly anymore. I don't have details since I am seldomly near the machines, but if anyone is willing to aid, I'm willing to look into it. Regards, -- Rink P.W. Springer - http://rink.nu "Anyway boys, this is America. Just because you get more votes doesn't mean you win." - Fox Mulder From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 12:13:12 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9796E1065672; Fri, 12 Dec 2008 12:13:12 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.bsdes.net (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.freebsd.org (Postfix) with ESMTP id 38A148FC16; Fri, 12 Dec 2008 12:13:11 +0000 (UTC) (envelope-from victor@bsdes.net) Received: by alf.bsdes.net (Postfix, from userid 1001) id 00184119CF7; Fri, 12 Dec 2008 13:13:09 +0100 (CET) Date: Fri, 12 Dec 2008 13:13:09 +0100 From: Victor Balada Diaz To: Pyun YongHyeon Message-ID: <20081212121309.GM1320@alf.bsdes.net> References: <20081209185236.GA1320@alf.bsdes.net> <20081210061226.GC37837@cdnetworks.co.kr> <20081210085934.GB1320@alf.bsdes.net> <20081210102800.GH37837@cdnetworks.co.kr> <20081210113225.GD1320@alf.bsdes.net> <20081210120719.GK37837@cdnetworks.co.kr> <20081211075707.GH1320@alf.bsdes.net> <20081211081045.GJ1320@alf.bsdes.net> <20081211090056.GH42370@cdnetworks.co.kr> <20081211095021.GL1320@alf.bsdes.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20081211095021.GL1320@alf.bsdes.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2008 12:13:12 -0000 On Thu, Dec 11, 2008 at 10:50:21AM +0100, Victor Balada Diaz wrote: > On Thu, Dec 11, 2008 at 06:00:56PM +0900, Pyun YongHyeon wrote: > > > > I've reverted r185756 which caused GMII access issues on some > > controllers. If you are brave enough to try beta code, you can > > get latest re(4) in the following URL. Note, I don't have PCIe > > based RealTek controllers so the code was not tested at all. > > > > http://people.freebsd.org/~yongari/re/if_re.c > > http://people.freebsd.org/~yongari/re/if_rlreg.h > > I've recompiled the kernel with the first file in sys/dev/re/ > and the second one in sys/pci/. I'm still testing with MSI enabled. > > So far tried rebooting using nextboot(8) (just in case i lost the > network card i could boot again) and the card seems to work > but i'll continue stress testing the machine with stress + dd + > iperf and see if i can take it down. I'll let you know how it goes. After a day of stress testing the machine haven't got errors, interrupt storms or interface up/down problems. Everything seems fine. I'll continue stress testing the machine during the weekend, but i would say that this time it's fixed. Seems lately there have been a lot of testing of this driver. Is there any chance of it being on 7.1 or being MFCed after the release to RELENG_7? Thanks a lot. Regards. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 13:00:32 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4774F1065675 for ; Fri, 12 Dec 2008 13:00:32 +0000 (UTC) (envelope-from rebehn@ant.uni-bremen.de) Received: from antsrv1.ant.uni-bremen.de (antsrv1.ant.uni-bremen.de [134.102.176.16]) by mx1.freebsd.org (Postfix) with ESMTP id 0663B8FC12 for ; Fri, 12 Dec 2008 13:00:31 +0000 (UTC) (envelope-from rebehn@ant.uni-bremen.de) Received: from bremerhaven.ant.uni-bremen.de ([134.102.176.10]) by antsrv1.ant.uni-bremen.de with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1LB7d8-0000MH-K4; Fri, 12 Dec 2008 14:00:30 +0100 From: Heinrich Rebehn To: Rink Springer In-Reply-To: <20081212094912.GA54988@rink.nu> References: <903DEF0D-724B-4A56-95DC-A557F203E5E1@ant.uni-bremen.de> <20081212094912.GA54988@rink.nu> Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Fri, 12 Dec 2008 14:00:30 +0100 X-Mailer: Apple Mail (2.919.2) Cc: freebsd-stable@freebsd.org Subject: Re: iir(4) support under 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2008 13:00:32 -0000 On Dec 12, 2008, at 10:49 AM, Rink Springer wrote: > Hi Heinrich, > > On Fri, Dec 12, 2008 at 10:27:41AM +0100, Heinrich Rebehn wrote: >> Hmmm? nobody using this stuff anymore??? > > FWIW, we have some IBM servers which feature an iir(4) too and they > are > unusuable on >=7.0 - the iir(4) does not initialize correctly anymore. > > I don't have details since I am seldomly near the machines, but if > anyone is willing to aid, I'm willing to look into it. > Huh, that does sound like a showstopper :-( But thanks for that warning anyway! -Heinrich From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 13:07:56 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C27B21065678; Fri, 12 Dec 2008 13:07:56 +0000 (UTC) (envelope-from bengta@P142.sics.se) Received: from sink.sics.se (sink.sics.se [193.10.64.88]) by mx1.freebsd.org (Postfix) with ESMTP id 548C48FC0C; Fri, 12 Dec 2008 13:07:56 +0000 (UTC) (envelope-from bengta@P142.sics.se) Received: from P142.sics.se (P142.sics.se [193.10.66.253]) by sink.sics.se (8.14.2/8.14.2) with ESMTP id mBCCZurn012523 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 12 Dec 2008 13:35:57 +0100 (CET) (envelope-from bengta@P142.sics.se) Received: from P142.sics.se (localhost [127.0.0.1]) by P142.sics.se (8.14.2/8.14.2) with ESMTP id mBCCbQ7C002899; Fri, 12 Dec 2008 13:37:26 +0100 (CET) (envelope-from bengta@P142.sics.se) Received: (from bengta@localhost) by P142.sics.se (8.14.2/8.14.2/Submit) id mBCCbPuA002898; Fri, 12 Dec 2008 13:37:25 +0100 (CET) (envelope-from bengta@P142.sics.se) To: freebsd-stable@freebsd.org From: Bengt Ahlgren User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (berkeley-unix) Date: Fri, 12 Dec 2008 13:37:25 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-emulation@freebsd.org Subject: Proper use of LD_LIBRARY_PATH for Linux progs? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Dec 2008 13:07:56 -0000 Hi! I ran into a problem with programs exec:ed by print/acroread8 picking up Linux libraries and thus failed to run. This includes the print program in the print dialogue and the browser configured in edit/preferences/internet. The reason is that the acroread launch script sets LD_LIBRARY_PATH which is propagated to its childs. See this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/129553 Question 1: anybody else that sees this problem? Question 2: what is the "proper" way to fix this problem? (specifically for acroread8, but also in general.) Bengt Ps. Sorry for cross-posting - don't know which list to use for this issue. From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 13:34:58 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74F4B106564A for ; Fri, 12 Dec 2008 13:34:58 +0000 (UTC) (envelope-from ghelmer@palisadesys.com) Received: from cetus.palisadesys.com (cetus.palisadesys.com [205.237.115.21]) by mx1.freebsd.org (Postfix) with ESMTP id 39A5D8FC1F for ; Fri, 12 Dec 2008 13:34:57 +0000 (UTC) (envelope-from ghelmer@palisadesys.com) Received: from magellan.palisadesys.com (serverwatch [172.16.1.98]) by cetus.palisadesys.com (8.14.1/8.14.1) with ESMTP id mBCDYvnX066391; Fri, 12 Dec 2008 07:34:57 -0600 (CST) (envelope-from ghelmer@palisadesys.com) Received: from [172.16.2.242] (cetus.palisadesys.com [205.237.115.21]) (authenticated bits=0) by magellan.palisadesys.com (8.14.2/8.14.2) with ESMTP id mBCDYt1T082836; Fri, 12 Dec 2008 07:34:55 -0600 (CST) (envelope-from ghelmer@palisadesys.com) Message-ID: <49426880.40302@palisadesys.com> Date: Fri, 12 Dec 2008 07:34:56 -0600 From: Guy Helmer User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: "Paul B. Mahol" References: <49419BE0.2070502@palisadesys.com> <3a142e750812111900u1d9264bh27d39092f5dcc4bf@mail.gmail.com> In-Reply-To: <3a142e750812111900u1d9264bh27d39092f5dcc4bf@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (magellan.palisadesys.com [205.237.115.20]); Fri, 12 Dec 2008 07:34:55 -0600 (CST) X-Palisade-MailScanner-Information: Please contact the ISP for more information X-Palisade-MailScanner: Found to be clean X-Palisade-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (not cached, score=-4.399, required 6, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60) X-Palisade-MailScanner-From: ghelmer@palisadesys.com Cc: freebsd-stable@freebsd.org Subject: Re: 7.1RC1: system 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: Fri, 12 Dec 2008 13:34:58 -0000 Paul B. Mahol wrote: > On 12/12/08, Guy Helmer wrote: > >> I have a recurring hang on FreeBSD 7.1 roughly-RC1 (releng_7_1 checkout >> as of 2008-12-08) on a dual-CPU hyperthreaded Xeon i386. I've dropped >> into the kernel debugger on the VGA console and transcribed the >> following information (if I omit anything critical, let me know -- the >> machine is still sitting at the debugger prompt) : >> >> > where >> pid 20 tid 100018 td 0xc45008c0 >> kdb_enter_why >> scgetc >> sckdbevent >> kdbmux_intr >> kdbmux_kdb_intr >> taskqueue_run >> taskqueue_swi_giant_run >> ithread_loop >> fork_exit(c063cce0, c44ac590, e4a36d38) at 0xc063a624 = fork_exit+0x94 >> fork_trampoline() at 0xc07e41a0 = fork_trampoline+0x8 >> >> > show allpcpu >> cpuid 0 in idle >> cpuid 1: proc 23457 >> cpuid 2: idle >> cpuid 3: swi6 proc 20 >> > > > what is proc 23457? > proc 23457 is "filter", an Autonomy KeyView Filter API program (extracts text out of various document formats) that is being run using FreeBSD 6 compatibility libraries. Guy From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 13:54:08 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A05481065670; Fri, 12 Dec 2008 13:54:08 +0000 (UTC) (envelope-from rink@rink.nu) Received: from mx1.rink.nu (gloom.rink.nu [213.34.49.2]) by mx1.freebsd.org (Postfix) with ESMTP id 60AE98FC1B; Fri, 12 Dec 2008 13:54:08 +0000 (UTC) (envelope-from rink@rink.nu) Received: from localhost (localhost [127.0.0.1]) by mx1.rink.nu (Postfix) with ESMTP id C45266D42B; Fri, 12 Dec 2008 14:54:18 +0100 (CET) X-Virus-Scanned: amavisd-new at rink.nu Received: from mx1.rink.nu ([213.34.49.2]) by localhost (gloom.rink.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HJ5rJoXBfAhN; Fri, 12 Dec 2008 14:54:15 +0100 (CET) Received: by mx1.rink.nu (Postfix, from userid 1000) id CF98D6D423; Fri, 12 Dec 2008 14:54:15 +0100 (CET) Date: Fri, 12 Dec 2008 14:54:15 +0100 From: Rink Springer To: Rink Springer Message-ID: <20081212135415.GB26330@rink.nu> References: <903DEF0D-724B-4A56-95DC-A557F203E5E1@ant.uni-bremen.de> <20081212094912.GA54988@rink.nu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081212094912.GA54988@rink.nu> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Heinrich Rebehn , freebsd-stable@freebsd.org Subject: Re: iir(4) support under 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2008 13:54:08 -0000 On Fri, Dec 12, 2008 at 10:49:12AM +0100, Rink Springer wrote: > Hi Heinrich, > > On Fri, Dec 12, 2008 at 10:27:41AM +0100, Heinrich Rebehn wrote: > > Hmmm? nobody using this stuff anymore??? > > FWIW, we have some IBM servers which feature an iir(4) too and they are > unusuable on >=7.0 - the iir(4) does not initialize correctly anymore. Err, I meant "Intel" servers... -- Rink P.W. Springer - http://rink.nu "Anyway boys, this is America. Just because you get more votes doesn't mean you win." - Fox Mulder From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 15:29:32 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DAB431065670 for ; Fri, 12 Dec 2008 15:29:32 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by mx1.freebsd.org (Postfix) with ESMTP id 5C8018FC19 for ; Fri, 12 Dec 2008 15:29:32 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so663100ywe.13 for ; Fri, 12 Dec 2008 07:29:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=RC6RqTqT+qUrU1LgfyxVHAJjl2I7gMCK1b3bpRtngio=; b=BAykiCG3GpH4zjoBu5+7PiFHMgcoUHXt0bcTBTbDmP/jBhX728D3iW2WxY6pA5XCvH R5m+NkDp2ndZ/A8oJ/77E8bbae5UnEwATUzrnE7xAh5VPI7SJECilRvl7waRdjBpkKHE wDp64DwWg86Zf85HT/xXfNsZyqVSvgDociaZE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=S7S/Rk9d/TkII/itTLOy/bOr9bJuSMMv8XcXzX39uxZGuvPWFCuyQb5IR0hNvbBGR2 /ySxMJgXGFnXOkS3R4lEP7yKv1Pwtu3ImSvrWfGMBX+D38MCGahoSrYKOpsegz6K4nkT Vc274sMhpivCIHFM+CM3GDGsD8ftuWbKlW+Ac= Received: by 10.231.16.75 with SMTP id n11mr46788iba.45.1229095771095; Fri, 12 Dec 2008 07:29:31 -0800 (PST) Received: by 10.231.18.139 with HTTP; Fri, 12 Dec 2008 07:29:30 -0800 (PST) Message-ID: <3a142e750812120729v478d850do93e31e5d8502ef68@mail.gmail.com> Date: Fri, 12 Dec 2008 16:29:30 +0100 From: "Paul B. Mahol" To: "Guy Helmer" In-Reply-To: <49426880.40302@palisadesys.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <49419BE0.2070502@palisadesys.com> <3a142e750812111900u1d9264bh27d39092f5dcc4bf@mail.gmail.com> <49426880.40302@palisadesys.com> Cc: freebsd-stable@freebsd.org Subject: Re: 7.1RC1: system 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: Fri, 12 Dec 2008 15:29:32 -0000 On 12/12/08, Guy Helmer wrote: > Paul B. Mahol wrote: >> On 12/12/08, Guy Helmer wrote: >> >>> I have a recurring hang on FreeBSD 7.1 roughly-RC1 (releng_7_1 checkout >>> as of 2008-12-08) on a dual-CPU hyperthreaded Xeon i386. I've dropped >>> into the kernel debugger on the VGA console and transcribed the >>> following information (if I omit anything critical, let me know -- the >>> machine is still sitting at the debugger prompt) : >>> >>> > where >>> pid 20 tid 100018 td 0xc45008c0 >>> kdb_enter_why >>> scgetc >>> sckdbevent >>> kdbmux_intr >>> kdbmux_kdb_intr >>> taskqueue_run >>> taskqueue_swi_giant_run >>> ithread_loop >>> fork_exit(c063cce0, c44ac590, e4a36d38) at 0xc063a624 = fork_exit+0x94 >>> fork_trampoline() at 0xc07e41a0 = fork_trampoline+0x8 >>> >>> > show allpcpu >>> cpuid 0 in idle >>> cpuid 1: proc 23457 >>> cpuid 2: idle >>> cpuid 3: swi6 proc 20 >>> >> >> >> what is proc 23457? >> > proc 23457 is "filter", an Autonomy KeyView Filter API program (extracts > text out of various document formats) that is being run using FreeBSD 6 > compatibility libraries. > > Guy > > Could you give most interesting part of "ps" output. -- Paul From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 16:12:51 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24035106564A for ; Fri, 12 Dec 2008 16:12:51 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42]) by mx1.freebsd.org (Postfix) with ESMTP id AB7C98FC1E for ; Fri, 12 Dec 2008 16:12:50 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from phenom.cordula.ws (phenom [192.168.254.60]) by fw.farid-hajji.net (Postfix) with ESMTP id 11EF7365B2; Fri, 12 Dec 2008 17:12:48 +0100 (CET) Date: Fri, 12 Dec 2008 17:12:48 +0100 From: cpghost To: "Arno J. Klaassen" Message-ID: <20081212161248.GA5905@phenom.cordula.ws> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: 7.1-PRERELEASE: asus M3A / Phenom X4 / powerd freeze X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Dec 2008 16:12:51 -0000 On Fri, Dec 12, 2008 at 12:01:29AM +0100, Arno J. Klaassen wrote: > yet another powerd SOS : on an ASUS M3A78-EM MB with > Phenom 9750 and 8 gig memory, starting powerd freezes > the box after slowing down a bit cpu frequency. (... snip ...) > dev.cpu.0.freq_levels: 2398/-1 2098/-1 1798/-1 1498/-1 1199/-1 899/-1 599/-1 299/-1 > > further : > > - I set debug.cpufreq.lowest superior to 1500 : system remains > up but only when pushing really slightly > > - I set debug.cpufreq.lowest inferior to 1100 : freeze > garantueed Same here. Running with debug.cpufreq.lowest="1240" in /boot/loader.conf to prevent freezes. This is a FreeBSD 7.1-PRERELEASE #0: Sat Nov 8 14:18:05 CET 2008 root@textbox:/usr/obj/usr/src/sys/GENERIC running in amd64 and i386 mode with ACPI enabled (default): CPU: AMD Phenom(tm) 9350e Quad-Core Processor (2000.08-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x100f23 Stepping = 3 Features=0x178bfbff Features2=0x802009> AMD Features=0xee500800 AMD Features2=0x7ff,,, Prefetch,,> Cores per package: 4 using an MSI board with SB600 chipset and newest BIOS. No idea why the system freezes below approx 1200 MHz. But apparently, this bug is quite common and affects a lot of systems with Phenoms. :( > - I define hint.acpi_throttle.0.disabled="1" in loader.conf > then no dev.cpu.0.freq is showing up ... (as if > only acpi_throttle is attaching and not powernow) > > Let me know what I can test further. > > Best, Arno Regards, -cpghost. -- Cordula's Web. http://www.cordula.ws/ From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 18:17:32 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72CDD1065670 for ; Fri, 12 Dec 2008 18:17:32 +0000 (UTC) (envelope-from njaguar@d2jsp.org) Received: from mx1.d2jsp.org (mx1.d2jsp.org [208.110.65.134]) by mx1.freebsd.org (Postfix) with ESMTP id 582958FC17 for ; Fri, 12 Dec 2008 18:17:32 +0000 (UTC) (envelope-from njaguar@d2jsp.org) Date: Fri, 12 Dec 2008 12:16:26 -0600 (CST) From: Paul Taulborg To: freebsd-stable@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Subject: Adaptec AIC-9410 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Dec 2008 18:17:32 -0000 Hello, I just recently purchased two new Supermicro servers: SYS-6025B-3R SYS-6015B-3R Both of these have an Adaptec AIC-9410 SAS controller in them, that is apparently not detected (or supported?) by FreeBSD (amd64) (7.0 or 7.1 RC1) Is there any way to get FreeBSD to detect this controller (and drives on it)? I found some conversations from 2006 about this, but no updates since. Thanks in advance, and hoping to be able to get this working. From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 19:54:36 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C234106568C for ; Fri, 12 Dec 2008 19:54:36 +0000 (UTC) (envelope-from ghelmer@palisadesys.com) Received: from cetus.palisadesys.com (cetus.palisadesys.com [205.237.115.21]) by mx1.freebsd.org (Postfix) with ESMTP id C59398FC2E for ; Fri, 12 Dec 2008 19:54:35 +0000 (UTC) (envelope-from ghelmer@palisadesys.com) Received: from magellan.palisadesys.com (serverwatch [172.16.1.98]) by cetus.palisadesys.com (8.14.1/8.14.1) with ESMTP id mBCJsYxA068606; Fri, 12 Dec 2008 13:54:34 -0600 (CST) (envelope-from ghelmer@palisadesys.com) Received: from [172.16.2.242] (cetus.palisadesys.com [205.237.115.21]) (authenticated bits=0) by magellan.palisadesys.com (8.14.2/8.14.2) with ESMTP id mBCJsW6l001273; Fri, 12 Dec 2008 13:54:32 -0600 (CST) (envelope-from ghelmer@palisadesys.com) Message-ID: <4942C178.2030206@palisadesys.com> Date: Fri, 12 Dec 2008 13:54:32 -0600 From: Guy Helmer User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: "Paul B. Mahol" References: <49419BE0.2070502@palisadesys.com> <3a142e750812111900u1d9264bh27d39092f5dcc4bf@mail.gmail.com> <49426880.40302@palisadesys.com> <3a142e750812120729v478d850do93e31e5d8502ef68@mail.gmail.com> In-Reply-To: <3a142e750812120729v478d850do93e31e5d8502ef68@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (magellan.palisadesys.com [205.237.115.20]); Fri, 12 Dec 2008 13:54:32 -0600 (CST) X-Palisade-MailScanner-Information: Please contact the ISP for more information X-Palisade-MailScanner: Found to be clean X-Palisade-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (not cached, score=-4.399, required 6, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60) X-Palisade-MailScanner-From: ghelmer@palisadesys.com Cc: freebsd-stable@freebsd.org Subject: Re: 7.1RC1: system 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: Fri, 12 Dec 2008 19:54:38 -0000 Paul B. Mahol wrote: > On 12/12/08, Guy Helmer wrote: > >> Paul B. Mahol wrote: >> >>> On 12/12/08, Guy Helmer wrote: >>> >>> >>>> I have a recurring hang on FreeBSD 7.1 roughly-RC1 (releng_7_1 checkout >>>> as of 2008-12-08) on a dual-CPU hyperthreaded Xeon i386. I've dropped >>>> into the kernel debugger on the VGA console and transcribed the >>>> following information (if I omit anything critical, let me know -- the >>>> machine is still sitting at the debugger prompt) : >>>> >>>> > where >>>> pid 20 tid 100018 td 0xc45008c0 >>>> kdb_enter_why >>>> scgetc >>>> sckdbevent >>>> kdbmux_intr >>>> kdbmux_kdb_intr >>>> taskqueue_run >>>> taskqueue_swi_giant_run >>>> ithread_loop >>>> fork_exit(c063cce0, c44ac590, e4a36d38) at 0xc063a624 = fork_exit+0x94 >>>> fork_trampoline() at 0xc07e41a0 = fork_trampoline+0x8 >>>> >>>> > show allpcpu >>>> cpuid 0 in idle >>>> cpuid 1: proc 23457 >>>> cpuid 2: idle >>>> cpuid 3: swi6 proc 20 >>>> >>>> >>> what is proc 23457? >>> >>> >> proc 23457 is "filter", an Autonomy KeyView Filter API program (extracts >> text out of various document formats) that is being run using FreeBSD 6 >> compatibility libraries. >> >> Guy >> >> >> > > Could you give most interesting part of "ps" output. > I've hooked up a serial console and I'll wait for the problem to occur again to to get the "ps" output -- there's about 70 active processes on the system, and transcribing from the VGA console is taking forever... Guy From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 19:56:46 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3E081065675; Fri, 12 Dec 2008 19:56:46 +0000 (UTC) (envelope-from pepe@rdc.cl) Received: from idcmail-mo2no.shaw.ca (idcmail-mo2no.shaw.ca [64.59.134.9]) by mx1.freebsd.org (Postfix) with ESMTP id B4B048FC26; Fri, 12 Dec 2008 19:56:46 +0000 (UTC) (envelope-from pepe@rdc.cl) Received: from pd5ml1no-ssvc.prod.shaw.ca ([10.0.153.166]) by pd5mo1no-svcs.prod.shaw.ca with ESMTP; 12 Dec 2008 12:28:27 -0700 X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.0 c=0 a=9Nrw9E724bfn_BPZYB0A:9 a=gifaEEmyllv5SJTp8GcA:7 a=DpiGdSiJH3GlFcHHdeFM_MpXWEUA:4 a=MNGfemgVX2cA:10 a=YoyaIb6G14kA:10 Received: from unknown (HELO [192.168.1.150]) ([96.49.96.182]) by pd5ml1no-dmz.prod.shaw.ca with ESMTP; 12 Dec 2008 12:28:27 -0700 Message-Id: From: Jose Amengual M To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Fri, 12 Dec 2008 11:28:26 -0800 X-Mailer: Apple Mail (2.929.2) Subject: intel dp45sg and Intel Matrix Raid 5 problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Dec 2008 19:56:47 -0000 Hi guys. I'm not pretty sure is this is the correct list but here we go. I have a intel dp45sg with RAID 5 on 4 hard drives of 160 gb each and FreeBSD 7.0-p5. It was working fine until two hours ago, the last message on the console after the server got frozen was "ad8 Detached" or something like that and "ar0 in Degraded mode". So, the server was not responding so I reboot it then I enter to the Intel Matrix console menu ( ctrl + I ) and the Raid was degraded, so I identify the disk I turn off the server then connect the new hard drive and then boot up again, after that in the Intel MAtrix console ask me that the new hard drive was not in the RAID so I I want to add to it, I sat "Yes" and then in the status tab appear "Rebuild". Before rebooting again I took a look to the documentation of intel matrix and they say that after the boot of the operating system, the rebuild process will start, So I reboot it again and I saw the "FreeBSD F1" menu and then I got "No boot loader". no /boot/loader After that I boot from the cd and I realize that the partition and the Slices are there, but the serve does not boot. I found a link about "Vital intel ICH7 patches for freebsd 6 and 7", but how can I apply the patches is I can boot ? Can some one help me please!!!! Thanks a lot. From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 20:36:48 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9BD5E1065679 for ; Fri, 12 Dec 2008 20:36:48 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id 4A9768FC21 for ; Fri, 12 Dec 2008 20:36:48 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.14.3/jtpda-5.4) with ESMTP id mBCKafeo008547 ; Fri, 12 Dec 2008 21:36:42 +0100 (CET) X-Ids: 168 Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.13.3/jtpda-5.2) with ESMTP id mBCKaeDO002381 ; Fri, 12 Dec 2008 21:36:40 +0100 (MET) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.13.3/8.13.1/Submit) id mBCKadal002378; Fri, 12 Dec 2008 21:36:39 +0100 (MET) (envelope-from arno) To: cpghost References: <20081212161248.GA5905@phenom.cordula.ws> From: "Arno J. Klaassen" Date: 12 Dec 2008 21:36:39 +0100 In-Reply-To: <20081212161248.GA5905@phenom.cordula.ws> Message-ID: Lines: 119 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (shiva.jussieu.fr [134.157.0.168]); Fri, 12 Dec 2008 21:36:42 +0100 (CET) X-Virus-Scanned: ClamAV 0.94.2/8749/Fri Dec 12 17:00:00 2008 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at jchkmail.jussieu.fr with ID 4942CB59.015 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 4942CB59.015/134.157.184.22/heho.snv.jussieu.fr/heho.snv.jussieu.fr/ X-j-chkmail-Score: MSGID : 4942CB59.015 on jchkmail.jussieu.fr : j-chkmail score : . : R=. U=. O=. B=0.008 -> S=0.008 X-j-chkmail-Status: Ham Cc: freebsd-stable@freebsd.org Subject: Re: 7.1-PRERELEASE: asus M3A / Phenom X4 / powerd freeze X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Dec 2008 20:36:48 -0000 cpghost writes: > On Fri, Dec 12, 2008 at 12:01:29AM +0100, Arno J. Klaassen wrote: > > yet another powerd SOS : on an ASUS M3A78-EM MB with > > Phenom 9750 and 8 gig memory, starting powerd freezes > > the box after slowing down a bit cpu frequency. > > (... snip ...) > > > dev.cpu.0.freq_levels: 2398/-1 2098/-1 1798/-1 1498/-1 1199/-1 899/-1 599/-1 299/-1 > > > > further : > > > > - I set debug.cpufreq.lowest superior to 1500 : system remains > > up but only when pushing really slightly > > > > - I set debug.cpufreq.lowest inferior to 1100 : freeze > > garantueed > > Same here. Running with > debug.cpufreq.lowest="1240" > in /boot/loader.conf to prevent freezes. > > This is a FreeBSD 7.1-PRERELEASE #0: Sat Nov 8 14:18:05 CET 2008 > root@textbox:/usr/obj/usr/src/sys/GENERIC > running in amd64 and i386 mode with ACPI enabled (default): > > CPU: AMD Phenom(tm) 9350e Quad-Core Processor (2000.08-MHz K8-class CPU) > Origin = "AuthenticAMD" Id = 0x100f23 Stepping = 3 > Features=0x178bfbff PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> > Features2=0x802009> > AMD Features=0xee500800 3DNow!+,3DNow!> > AMD Features2=0x7ff,,, > Prefetch,,> > Cores per package: 4 > > using an MSI board with SB600 chipset and newest BIOS. > > No idea why the system freezes below approx 1200 MHz. But apparently, > this bug is quite common and affects a lot of systems with Phenoms. :( do Phenoms not support powernow? I am a bit puzzled by the differnce with two X2 boards I have around here : FreeBSD 7.1-PRERELEASE #0: Tue Dec 2 20:09:28 ... CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ (2992.52-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40f33 Stepping = 3 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1f Cores per package: 2 ... cpu0: on acpi0 powernow0: on cpu0 cpu1: on acpi0 powernow1: on cpu1 FreeBSD 7.1-PRERELEASE #1: Mon Nov 17 14:40:26 ... CPU: AMD Turion(tm) 64 X2 Mobile Technology TL-62 (2109.70-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x60f82 Stepping = 2 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x11f Cores per package: 2 ... cpu0: on acpi0 acpi_throttle0: on cpu0 powernow0: on cpu0 cpu1: on acpi0 acpi_throttle1: on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 powernow1: on cpu1 whereas the Phenom says : CPU: AMD Phenom(tm) 9750 Quad-Core Processor (2410.66-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x100f23 Stepping = 3 Features=0x178bfbff Features2=0x802009> AMD Features=0xee500800 AMD Features2=0x7ff,,,Prefetch,,> ... cpu0: on acpi0 acpi_throttle0: on cpu0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 my conclusion : acpi_throttle attaches a X4 (why not) and not at X2 (thought the Turion seems to detect it but fails to attach), powernow does not seem to attach to X4 ... Best regards, Arno > > - I define hint.acpi_throttle.0.disabled="1" in loader.conf > > then no dev.cpu.0.freq is showing up ... (as if > > only acpi_throttle is attaching and not powernow) > > > > Let me know what I can test further. > > > > Best, Arno > > Regards, > -cpghost. > > -- > Cordula's Web. http://www.cordula.ws/ From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 21:27:08 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id C69AB1065673; Fri, 12 Dec 2008 21:27:06 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Fri, 12 Dec 2008 16:26:54 -0500 User-Agent: KMail/1.6.2 References: <20081212161248.GA5905@phenom.cordula.ws> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200812121626.56590.jkim@FreeBSD.org> Cc: cpghost Subject: Re: 7.1-PRERELEASE: asus M3A / Phenom X4 / powerd freeze X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Dec 2008 21:27:08 -0000 On Friday 12 December 2008 03:36 pm, Arno J. Klaassen wrote: > cpghost writes: > > On Fri, Dec 12, 2008 at 12:01:29AM +0100, Arno J. Klaassen wrote: > > > yet another powerd SOS : on an ASUS M3A78-EM MB with > > > Phenom 9750 and 8 gig memory, starting powerd freezes > > > the box after slowing down a bit cpu frequency. > > > > (... snip ...) > > > > > dev.cpu.0.freq_levels: 2398/-1 2098/-1 1798/-1 1498/-1 1199/-1 > > > 899/-1 599/-1 299/-1 > > > > > > further : > > > > > > - I set debug.cpufreq.lowest superior to 1500 : system remains > > > up but only when pushing really slightly > > > > > > - I set debug.cpufreq.lowest inferior to 1100 : freeze > > > garantueed > > > > Same here. Running with > > debug.cpufreq.lowest="1240" > > in /boot/loader.conf to prevent freezes. > > > > This is a FreeBSD 7.1-PRERELEASE #0: Sat Nov 8 14:18:05 CET 2008 > > root@textbox:/usr/obj/usr/src/sys/GENERIC > > running in amd64 and i386 mode with ACPI enabled (default): > > > > CPU: AMD Phenom(tm) 9350e Quad-Core Processor (2000.08-MHz > > K8-class CPU) Origin = "AuthenticAMD" Id = 0x100f23 Stepping = > > 3 > > > > Features=0x178bfbff >TRR, PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> > > Features2=0x802009> > > AMD > > Features=0xee500800 > 3DNow!+,3DNow!> > > AMD Features2=0x7ff,,, > > Prefetch,,> > > Cores per package: 4 > > > > using an MSI board with SB600 chipset and newest BIOS. > > > > No idea why the system freezes below approx 1200 MHz. But > > apparently, this bug is quite common and affects a lot of systems > > with Phenoms. :( > > do Phenoms not support powernow? [SNIP] "Phenom" is 10H family processor and it has Cool`n'Quiet 2.0. Someone wrote a driver for it and it was posted on freebsd-current in September: http://lists.freebsd.org/pipermail/freebsd-current/2008-September/088330.html http://lists.freebsd.org/pipermail/freebsd-current/2008-September/088803.html http://lists.freebsd.org/pipermail/freebsd-current/2008-September/088806.html Jung-uk Kim From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 21:39:15 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 120901065673; Fri, 12 Dec 2008 21:39:15 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Fri, 12 Dec 2008 16:39:04 -0500 User-Agent: KMail/1.6.2 References: <200812121626.56590.jkim@FreeBSD.org> In-Reply-To: <200812121626.56590.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200812121639.06698.jkim@FreeBSD.org> Cc: cpghost Subject: Re: 7.1-PRERELEASE: asus M3A / Phenom X4 / powerd freeze X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Dec 2008 21:39:15 -0000 On Friday 12 December 2008 04:26 pm, Jung-uk Kim wrote: > On Friday 12 December 2008 03:36 pm, Arno J. Klaassen wrote: > > cpghost writes: > > > On Fri, Dec 12, 2008 at 12:01:29AM +0100, Arno J. Klaassen wrote: > > > > yet another powerd SOS : on an ASUS M3A78-EM MB with > > > > Phenom 9750 and 8 gig memory, starting powerd freezes > > > > the box after slowing down a bit cpu frequency. > > > > > > (... snip ...) > > > > > > > dev.cpu.0.freq_levels: 2398/-1 2098/-1 1798/-1 1498/-1 > > > > 1199/-1 899/-1 599/-1 299/-1 > > > > > > > > further : > > > > > > > > - I set debug.cpufreq.lowest superior to 1500 : system > > > > remains up but only when pushing really slightly > > > > > > > > - I set debug.cpufreq.lowest inferior to 1100 : freeze > > > > garantueed > > > > > > Same here. Running with > > > debug.cpufreq.lowest="1240" > > > in /boot/loader.conf to prevent freezes. > > > > > > This is a FreeBSD 7.1-PRERELEASE #0: Sat Nov 8 14:18:05 CET > > > 2008 root@textbox:/usr/obj/usr/src/sys/GENERIC > > > running in amd64 and i386 mode with ACPI enabled (default): > > > > > > CPU: AMD Phenom(tm) 9350e Quad-Core Processor (2000.08-MHz > > > K8-class CPU) Origin = "AuthenticAMD" Id = 0x100f23 Stepping > > > = 3 > > > > > > Features=0x178bfbff > >,M TRR, PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> > > > Features2=0x802009> > > > AMD > > > Features=0xee500800 > > 3DNow!+,3DNow!> > > > AMD Features2=0x7ff,,, > > > Prefetch,,> > > > Cores per package: 4 > > > > > > using an MSI board with SB600 chipset and newest BIOS. > > > > > > No idea why the system freezes below approx 1200 MHz. But > > > apparently, this bug is quite common and affects a lot of > > > systems with Phenoms. :( > > > > do Phenoms not support powernow? > > [SNIP] > > "Phenom" is 10H family processor and it has Cool`n'Quiet 2.0. > Someone wrote a driver for it and it was posted on freebsd-current > in September: > > http://lists.freebsd.org/pipermail/freebsd-current/2008-September/0 >88330.html > http://lists.freebsd.org/pipermail/freebsd-current/2008-September/0 >88803.html > http://lists.freebsd.org/pipermail/freebsd-current/2008-September/0 >88806.html I forgot there is a PR with the latest driver: http://www.freebsd.org/cgi/query-pr.cgi?pr=128575 Jung-uk Kim From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 21:49:44 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E47061065679 for ; Fri, 12 Dec 2008 21:49:44 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id 756F58FC1A for ; Fri, 12 Dec 2008 21:49:44 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.14.3/jtpda-5.4) with ESMTP id mBCLncVK079265 ; Fri, 12 Dec 2008 22:49:38 +0100 (CET) X-Ids: 166 Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.13.3/jtpda-5.2) with ESMTP id mBCLnaV0000489 ; Fri, 12 Dec 2008 22:49:37 +0100 (MET) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.13.3/8.13.1/Submit) id mBCLnZoJ000486; Fri, 12 Dec 2008 22:49:35 +0100 (MET) (envelope-from arno) To: Jung-uk Kim References: <200812121626.56590.jkim@FreeBSD.org> <200812121639.06698.jkim@FreeBSD.org> From: "Arno J. Klaassen" Date: 12 Dec 2008 22:49:34 +0100 In-Reply-To: <200812121639.06698.jkim@FreeBSD.org> Message-ID: Lines: 33 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (shiva.jussieu.fr [134.157.0.166]); Fri, 12 Dec 2008 22:49:39 +0100 (CET) X-Virus-Scanned: ClamAV 0.94.2/8750/Fri Dec 12 20:17:14 2008 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at jchkmail.jussieu.fr with ID 4942DC72.005 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 4942DC72.005/134.157.184.22/heho.snv.jussieu.fr/heho.snv.jussieu.fr/ X-j-chkmail-Score: MSGID : 4942DC72.005 on jchkmail.jussieu.fr : j-chkmail score : . : R=. U=. O=. B=0.012 -> S=0.012 X-j-chkmail-Status: Ham Cc: cpghost , freebsd-stable@FreeBSD.org Subject: Re: 7.1-PRERELEASE: asus M3A / Phenom X4 / powerd freeze X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Dec 2008 21:49:45 -0000 Jung-uk Kim writes: > On Friday 12 December 2008 04:26 pm, Jung-uk Kim wrote: > > On Friday 12 December 2008 03:36 pm, Arno J. Klaassen wrote: > > > cpghost writes: > > > > On Fri, Dec 12, 2008 at 12:01:29AM +0100, Arno J. Klaassen > wrote: > > > > > > > > [ .. stuff deleted .. ] > > > > > > > do Phenoms not support powernow? > > > > [SNIP] > > > > "Phenom" is 10H family processor and it has Cool`n'Quiet 2.0. > > Someone wrote a driver for it and it was posted on freebsd-current > > in September: > > > > http://lists.freebsd.org/pipermail/freebsd-current/2008-September/0 > >88330.html > > http://lists.freebsd.org/pipermail/freebsd-current/2008-September/0 > >88803.html > > http://lists.freebsd.org/pipermail/freebsd-current/2008-September/0 > >88806.html > > I forgot there is a PR with the latest driver: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=128575 ah, I see. Thank you very much. I'll give it a try this WE Best, Arno From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 01:42:40 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D8861065676 for ; Sat, 13 Dec 2008 01:42:40 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.231]) by mx1.freebsd.org (Postfix) with ESMTP id 106738FC14 for ; Sat, 13 Dec 2008 01:42:39 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1622647rvf.43 for ; Fri, 12 Dec 2008 17:42:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=lVP4K4mXRj3wQLrmGNDMdHgijB5umrLbVef9/DBwrbo=; b=AS3cnxPahX7V5u6igX6dOfZs9gompVp8FIRRNb2nWHNiXfjh/XncqBgfp87/0VZDvC QatoP58PevhhDYwfqS48t0vs1cUIVc5V0lrzj0d/U5qvFneSX6nnNKc/xC+33imNovSs mdIUjT93tDzh62rONluab1yUB7iHOk2USk7Fc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=h1ZF1/cgJt7A2O/Ql/B9h6CjKyGSoyTodrYygjAbGCZqA6cweoEn2BT/mDlT+boYnx yakClJgZLGIQth+L7+mlCvJuBrSE2cEOQipWWRiuqlx/n4erGMntGmGwzNHCDZBeveI6 zLKCyDlQMVUmvqqo+aE9hoRen2ijUW35GnwxM= Received: by 10.141.162.1 with SMTP id p1mr2219273rvo.190.1229132559724; Fri, 12 Dec 2008 17:42:39 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id k41sm1776841rvb.6.2008.12.12.17.42.36 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 12 Dec 2008 17:42:38 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id mBD1gWgT051540 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 13 Dec 2008 10:42:32 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id mBD1gT3E051539; Sat, 13 Dec 2008 10:42:29 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Sat, 13 Dec 2008 10:42:29 +0900 From: Pyun YongHyeon To: Victor Balada Diaz Message-ID: <20081213014229.GC51320@cdnetworks.co.kr> References: <20081210061226.GC37837@cdnetworks.co.kr> <20081210085934.GB1320@alf.bsdes.net> <20081210102800.GH37837@cdnetworks.co.kr> <20081210113225.GD1320@alf.bsdes.net> <20081210120719.GK37837@cdnetworks.co.kr> <20081211075707.GH1320@alf.bsdes.net> <20081211081045.GJ1320@alf.bsdes.net> <20081211090056.GH42370@cdnetworks.co.kr> <20081211095021.GL1320@alf.bsdes.net> <20081212121309.GM1320@alf.bsdes.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081212121309.GM1320@alf.bsdes.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [ATA] and re(4) stability issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2008 01:42:40 -0000 On Fri, Dec 12, 2008 at 01:13:09PM +0100, Victor Balada Diaz wrote: > On Thu, Dec 11, 2008 at 10:50:21AM +0100, Victor Balada Diaz wrote: > > On Thu, Dec 11, 2008 at 06:00:56PM +0900, Pyun YongHyeon wrote: > > > > > > I've reverted r185756 which caused GMII access issues on some > > > controllers. If you are brave enough to try beta code, you can > > > get latest re(4) in the following URL. Note, I don't have PCIe > > > based RealTek controllers so the code was not tested at all. > > > > > > http://people.freebsd.org/~yongari/re/if_re.c > > > http://people.freebsd.org/~yongari/re/if_rlreg.h > > > > I've recompiled the kernel with the first file in sys/dev/re/ > > and the second one in sys/pci/. I'm still testing with MSI enabled. > > > > So far tried rebooting using nextboot(8) (just in case i lost the > > network card i could boot again) and the card seems to work > > but i'll continue stress testing the machine with stress + dd + > > iperf and see if i can take it down. I'll let you know how it goes. > > After a day of stress testing the machine haven't got errors, interrupt > storms or interface up/down problems. Everything seems fine. > I'll continue stress testing the machine during the weekend, but > i would say that this time it's fixed. > Thanks for testing! > Seems lately there have been a lot of testing of this driver. Is > there any chance of it being on 7.1 or being MFCed after the release > to RELENG_7? > It's too early to say MFC but I think MFC would be done after releasing 7.1-RELEASE if all goes well. -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 14:26:53 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50D6E1065670; Sat, 13 Dec 2008 14:26:53 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id F0E9F8FC17; Sat, 13 Dec 2008 14:26:52 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.14.3/jtpda-5.4) with ESMTP id mBDEQijB088212 ; Sat, 13 Dec 2008 15:26:45 +0100 (CET) X-Ids: 165 Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.13.3/jtpda-5.2) with ESMTP id mBDEQhik006790 ; Sat, 13 Dec 2008 15:26:43 +0100 (MET) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.13.3/8.13.1/Submit) id mBDEQhYc006787; Sat, 13 Dec 2008 15:26:43 +0100 (MET) (envelope-from arno) To: Jung-uk Kim References: <200812121626.56590.jkim@FreeBSD.org> <200812121639.06698.jkim@FreeBSD.org> From: "Arno J. Klaassen" Date: 13 Dec 2008 15:26:42 +0100 In-Reply-To: <200812121639.06698.jkim@FreeBSD.org> Message-ID: Lines: 77 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (shiva.jussieu.fr [134.157.0.165]); Sat, 13 Dec 2008 15:26:45 +0100 (CET) X-Virus-Scanned: ClamAV 0.94.2/8751/Sat Dec 13 04:47:53 2008 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at jchkmail2.jussieu.fr with ID 4943AA28.00C by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 4943AA28.00C/134.157.184.22/heho.snv.jussieu.fr/heho.snv.jussieu.fr/ X-j-chkmail-Score: MSGID : 4943AA28.00C on jchkmail2.jussieu.fr : j-chkmail score : . : R=. U=. O=. B=0.013 -> S=0.013 X-j-chkmail-Status: Ham Cc: annona2@gmail.com, freebsd-stable@FreeBSD.org, cpghost Subject: Re: 7.1-PRERELEASE: asus M3A / Phenom X4 / powerd freeze X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Dec 2008 14:26:53 -0000 Jung-uk Kim writes: > On Friday 12 December 2008 04:26 pm, Jung-uk Kim wrote: > > On Friday 12 December 2008 03:36 pm, Arno J. Klaassen wrote: > > > cpghost writes: > > > > On Fri, Dec 12, 2008 at 12:01:29AM +0100, Arno J. Klaassen > wrote: > > > > > yet another powerd SOS : on an ASUS M3A78-EM MB with > > > > > Phenom 9750 and 8 gig memory, starting powerd freezes > > > > > the box after slowing down a bit cpu frequency. > > > > > > > > (... snip ...) > > > > > I forgot there is a PR with the latest driver: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=128575 yes, this works better : kldload cpufreq : hwpstate0: on cpu0 hwpstate0: SVI mode hwpstate0: you have 2 P-state. hwpstate0: freq=2400MHz volts=1300mV hwpstate0: freq=1200MHz volts=1050mV hwpstate0: Now P0-state. hwpstate1: on cpu1 hwpstate1: SVI mode hwpstate1: you have 2 P-state. hwpstate1: freq=2400MHz volts=1300mV hwpstate1: freq=1200MHz volts=1050mV hwpstate1: Now P0-state. hwpstate2: on cpu2 hwpstate2: SVI mode hwpstate2: you have 2 P-state. hwpstate2: freq=2400MHz volts=1300mV hwpstate2: freq=1200MHz volts=1050mV hwpstate2: Now P0-state. hwpstate3: on cpu3 hwpstate3: SVI mode hwpstate3: you have 2 P-state. hwpstate3: freq=2400MHz volts=1300mV hwpstate3: freq=1200MHz volts=1050mV hwpstate3: Now P0-state. however, I need to disable acpi_throttle; standard, I get : [root@m34 ~]# sysctl dev.cpu.0.freq_levels dev.cpu.0.freq_levels: 2398/-1 2098/-1 1798/-1 1498/-1 1199/-1 899/-1 599/-1 299/-1 [root@m34 ~]# kldload cpufreq [root@m34 ~]# sysctl dev.cpu.0.freq_levels dev.cpu.0.freq_levels: 2400/-1 2100/-1 1800/-1 1500/-1 1200/-1 1050/-1 900/-1 750/-1 600/-1 450/-1 300/-1 150/-1 [root@m34 ~]# powerd -v powerd: unable to determine AC line status idle time > 90%, decreasing clock speed from 2398 MHz to -1 MHz powerd: error setting CPU frequency -1: Invalid argument idle time > 90%, decreasing clock speed from 2398 MHz to -1 MHz powerd: error setting CPU frequency -1: Invalid argument rebooting with hint.acpi_throttle.0.disabled="1" gives : [root@m34 ~]# sysctl dev.cpu.0.freq_levels sysctl: unknown oid 'dev.cpu.0.freq_levels' [root@m34 ~]# kldload cpufreq [root@m34 ~]# sysctl dev.cpu.0.freq_levels dev.cpu.0.freq_levels: 2400/-1 1200/-1 [root@m34 ~]# powerd -v powerd: unable to determine AC line status idle time > 90%, decreasing clock speed from 2400 MHz to 1200 MHz Thanx, Arno From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 17:43:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40FBF106564A; Sat, 13 Dec 2008 17:43:30 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 0F7B78FC26; Sat, 13 Dec 2008 17:43:29 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 6F2B21E6A70; Sat, 13 Dec 2008 12:43:29 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Sat, 13 Dec 2008 12:43:29 -0500 X-Sasl-enc: Dyb7IEaCqv/DJrY/agJKk4V7+1R07s91nUAWxmq0LoLq 1229190209 Received: from anglepoise.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id A90103A240; Sat, 13 Dec 2008 12:43:28 -0500 (EST) Message-ID: <4943F43B.4060105@incunabulum.net> Date: Sat, 13 Dec 2008 17:43:23 +0000 From: Bruce Simpson User-Agent: Thunderbird 2.0.0.18 (X11/20081204) MIME-Version: 1.0 To: "Paul B. Mahol" References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> <200812041747.09040.gnemmi@gmail.com> <4938FE44.9090608@FreeBSD.org> <4939133E.2000701@FreeBSD.org> <493CEE90.7050104@FreeBSD.org> <3a142e750812090553l564bff84pe1f02cd1b03090ff@mail.gmail.com> In-Reply-To: <3a142e750812090553l564bff84pe1f02cd1b03090ff@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org, "Bruce M. Simpson" Subject: Re: ext2fuse: user-space ext2 implementation X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2008 17:43:30 -0000 Paul B. Mahol wrote: > On 12/8/08, Bruce M. Simpson wrote: > >> I have rolled a port for ext2fuse: >> http://people.freebsd.org/~bms/dump/fusefs-ext2fs.tar >> > > Ignoring fact that is buggy, slooow and port doesnt have any cache implemented > and port leaves files behind in share/doc/ext2fuse when package > deleted it looks fine. > Can you please relay this feedback to the authors of ext2fuse? As mentioned earlier in the thread, the ext2fuse code could benefit from UBLIO-ization. Are you or any other volunteers happy to help out here? Can you elaborate further on the files being left behind by the port? I didn't see this issue in my own testing. thank you BMS From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 17:55:37 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4AC441065672 for ; Sat, 13 Dec 2008 17:55:37 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 210108FC18 for ; Sat, 13 Dec 2008 17:55:37 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id A3F891E75D9; Sat, 13 Dec 2008 12:55:36 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sat, 13 Dec 2008 12:55:36 -0500 X-Sasl-enc: u/U2xEyP3+3rlrGjW4KWazKuHxXsOi9t4mmJ1QL8h4sE 1229190936 Received: from anglepoise.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 147664DA3; Sat, 13 Dec 2008 12:55:35 -0500 (EST) Message-ID: <4943F715.9030008@incunabulum.net> Date: Sat, 13 Dec 2008 17:55:33 +0000 From: Bruce Simpson User-Agent: Thunderbird 2.0.0.18 (X11/20081204) MIME-Version: 1.0 To: Ken Smith References: <1228876766.35416.23.camel@bauer.cse.buffalo.edu> <1228877345.35416.27.camel@bauer.cse.buffalo.edu> In-Reply-To: <1228877345.35416.27.camel@bauer.cse.buffalo.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable Subject: Re: FreeBSD 7.1-RC1 Available... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Dec 2008 17:55:37 -0000 I've been tracking 7.1 on 3 separate machines since around September without any issues (1 server, 1 desktop, 1 laptop). Thank you for all your hard work on this. cheers BMS From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 18:01:25 2008 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 EE6C31065675 for ; Sat, 13 Dec 2008 18:01:25 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id C2A178FC25 for ; Sat, 13 Dec 2008 18:01:25 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 71FC81E6226; Sat, 13 Dec 2008 13:01:25 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Sat, 13 Dec 2008 13:01:25 -0500 X-Sasl-enc: AqhsXIsAzco9sHVAsSddrdtPyrVrYggsOIgn6MVjpnRo 1229191285 Received: from anglepoise.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 9C6AA1EAF8; Sat, 13 Dec 2008 13:01:24 -0500 (EST) Message-ID: <4943F872.9080009@incunabulum.net> Date: Sat, 13 Dec 2008 18:01:22 +0000 From: Bruce Simpson User-Agent: Thunderbird 2.0.0.18 (X11/20081204) MIME-Version: 1.0 To: Goran Lowkrantz References: <20081209114723.GE33723@cdnetworks.co.kr> <80D07D8C17DAC73D69DCDC9A@[172.16.2.124]> <20081210071932.GD37837@cdnetworks.co.kr> <47381931A80CB93CADD10DC7@[172.16.2.128]> In-Reply-To: <47381931A80CB93CADD10DC7@[172.16.2.128]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: pyunyh@gmail.com, stable@freebsd.org Subject: Re: Regression in vr - not receiveing multicast X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Dec 2008 18:01:26 -0000 Goran Lowkrantz wrote: >> >> Can you see ALLMULTI flag from the output of "ifconfig vr0"? >> > No -> > # ifconfig vr0 > vr0: flags=8943 metric > 0 mtu 1500 > options=284b > ether 00:00:24:c8:e0:9c > inet xxx.xxx.xxx.xxx netmask 0xfffffff8 broadcast xxx.xxx.xxx.yyy > media: Ethernet autoselect (100baseTX ) > status: active Only a client of the MROUTING socket-level API (e.g. mrouted, XORP, pimdd, pimsd) is able to cause the kernel to enable ALLMULTI on an interface by itself. You will need to get a multicast routing daemon of some kind running to test this. mrouted is OK for testing very simple configurations, although it has been de-orbitted as far as the 'Net itself is concerned. thanks BMS From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 20:26:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36CB5106564A for ; Sat, 13 Dec 2008 20:26:54 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.freebsd.org (Postfix) with ESMTP id D4B878FC17 for ; Sat, 13 Dec 2008 20:26:53 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (pD9E2E4FD.dip.t-dialin.net [217.226.228.253]) by redbull.bpaserver.net (Postfix) with ESMTP id 871A32E0BA; Sat, 13 Dec 2008 21:17:57 +0100 (CET) Received: from webmail.leidinger.net (webmail.leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id C85E2182335; Sat, 13 Dec 2008 21:17:53 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1229199473; bh=6DhWy6eQWcGAcOsNpclDv6w/eI4PfMfRi CYroEatgBA=; h=Message-ID:Date:From:To:Cc:Subject:References: In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=o+D1NsClh6psftwK2xC6eKbyUk5X22WddRoLQXHIVy82zjKTmrs4evxQJk2RNOz1l ThXOUzppypN8sTDNfD5cXFcsARbcwe/uS2oAEVlnfVRA0fF61UWHB9AAIqSo4qsYrmI u3K5MIJa/h/TAf7XisvfsCAAqHBBSq/+O8MeM/bNMSdb7PsZprbTNWRiJIaXfNs1dmG wyES4G1ewjUciQsCiHZT9rabW/64yF5UYVFvGJwnATL0AZwIBoO8robOxfvD1tkHlo9 3TLPJPd952SuewZr6cGEgEQX7kTe+v7c6M8cAiJv9FlHISy8mbKPdeJaemX0oOTn4ys A70Thzizw== Received: (from www@localhost) by webmail.leidinger.net (8.14.3/8.13.8/Submit) id mBDKHr3r018988; Sat, 13 Dec 2008 21:17:53 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Luna.Leidinger.net (Luna.Leidinger.net [192.168.2.100]) by webmail.leidinger.net (Horde Framework) with HTTP; Sat, 13 Dec 2008 21:17:53 +0100 Message-ID: <20081213211753.172124oke0p9oqdc@webmail.leidinger.net> X-Priority: 3 (Normal) Date: Sat, 13 Dec 2008 21:17:53 +0100 From: Alexander Leidinger To: Bengt Ahlgren References: <20081213211115.1274360bbklovuas@webmail.leidinger.net> In-Reply-To: <20081213211115.1274360bbklovuas@webmail.leidinger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.3) / FreeBSD-8.0 X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: 871A32E0BA.4E8A0 X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, ORDB-RBL, SpamAssassin (not cached, score=-15.4, required 6, autolearn=not spam, BAYES_00 -15.00, DKIM_SIGNED 0.00, DKIM_VERIFIED -0.00, RDNS_DYNAMIC 0.10, SMILEY -0.50) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No Cc: freebsd-emulation@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Proper use of LD_LIBRARY_PATH for Linux progs? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Dec 2008 20:26:54 -0000 Quoting Alexander Leidinger (from Sat, 13 =20 Dec 2008 21:11:15 +0100): > Quoting Bengt Ahlgren (from Fri, 12 Dec 2008 =20 > 13:37:25 +0100): > >> The reason is that the acroread launch script sets LD_LIBRARY_PATH >> which is propagated to its childs. See this PR: >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/129553 > >> Question 2: what is the "proper" way to fix this problem? >> (specifically for acroread8, but also in general.) > > Search the archive for the ports mailinglist, in the mail =20 > "print/acroread8: LD_LIBRARY_PATH breaks helper programs" is a fix =20 > for the problem. ROTFL... this mail on ports@ is from you... :-) I suggest to contact the port maintainer with the fix. If he doesn't =20 answer, send a PR. As soon as someone (maintainer / other committer in =20 the PR case) has time and motivation, the fix will get committed. Bye, Alexander (ENOTIME ATM, else I would have taken care about this already). --=20 Gordon's first law: =09If a research project is not worth doing, it is not worth doing =09well. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 20:26:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A8941065672 for ; Sat, 13 Dec 2008 20:26:54 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.freebsd.org (Postfix) with ESMTP id D77B58FC1A for ; Sat, 13 Dec 2008 20:26:53 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (pD9E2E4FD.dip.t-dialin.net [217.226.228.253]) by redbull.bpaserver.net (Postfix) with ESMTP id 3F1842E0BA; Sat, 13 Dec 2008 21:11:21 +0100 (CET) Received: from webmail.leidinger.net (webmail.leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id 3446118204A; Sat, 13 Dec 2008 21:11:16 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1229199076; bh=ZBTDQ6tCRSqAITL7vtfjN4wCfyqxpd68E a3Yxg3jpSA=; h=Message-ID:Date:From:To:Cc:Subject:References: In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=vOaSIsR8XPjQG7zXoYgvNYJi606MQAPtvWkb0Z3Cu3KTYWRTHHbMRf80bSpijbZvK XsmSl3l8sWfdcoS2GP8USVtj3bmFVP6UM6dlNtfz2PmgSuYIDX6b6/witWSs/8D+Tmc tVsI0lmvM5HDPFdyJc7TyTuY49JJSI6T4+h6m9VXhBohEc36nFTOT3qwVIW7yqGX/Wy CcgPgji6NY07nhxiwMvpjAorM8emJMDkA6qkseoPjRJGujjuqcG/+xtExvHuWjUa4K1 F4bDEIWAJEJ8ilodFCuH8yokIvozdly8OAsWYvyoX7IvkuxdRnSJnVQi64+o36wyQVN uGvFff/2w== Received: (from www@localhost) by webmail.leidinger.net (8.14.3/8.13.8/Submit) id mBDKBFsA017830; Sat, 13 Dec 2008 21:11:15 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Luna.Leidinger.net (Luna.Leidinger.net [192.168.2.100]) by webmail.leidinger.net (Horde Framework) with HTTP; Sat, 13 Dec 2008 21:11:15 +0100 Message-ID: <20081213211115.1274360bbklovuas@webmail.leidinger.net> X-Priority: 3 (Normal) Date: Sat, 13 Dec 2008 21:11:15 +0100 From: Alexander Leidinger To: Bengt Ahlgren References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.3) / FreeBSD-8.0 X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: 3F1842E0BA.68E6F X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, ORDB-RBL, SpamAssassin (not cached, score=-13.504, required 6, BAYES_00 -15.00, DKIM_SIGNED 0.00, DKIM_VERIFIED -0.00, MIME_QP_LONG_LINE 1.40, RDNS_DYNAMIC 0.10) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No Cc: freebsd-emulation@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Proper use of LD_LIBRARY_PATH for Linux progs? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Dec 2008 20:26:54 -0000 Quoting Bengt Ahlgren (from Fri, 12 Dec 2008 13:37:25 +0100= ): > The reason is that the acroread launch script sets LD_LIBRARY_PATH > which is propagated to its childs. See this PR: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/129553 > Question 2: what is the "proper" way to fix this problem? > (specifically for acroread8, but also in general.) Search the archive for the ports mailinglist, in the mail =20 "print/acroread8: LD_LIBRARY_PATH breaks helper programs" is a fix for =20 the problem. In general: there's no general fix. It all depends why LD_LIBRARY_PATH =20 is used and what is done. There are multiple ways, some are =20 workarounds ("env LD_LIBRARY_PATH=3D'' lpr ..." ), some (like the one =20 for acroread in the mail) are good fixes. Bye, Alexander. --=20 Disclose classified information only when a NEED TO KNOW exists. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 From owner-freebsd-stable@FreeBSD.ORG Sat Dec 13 22:03:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBDC71065672; Sat, 13 Dec 2008 22:03:54 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.242]) by mx1.freebsd.org (Postfix) with ESMTP id 467CE8FC1F; Sat, 13 Dec 2008 22:03:54 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by an-out-0708.google.com with SMTP id c2so725379anc.13 for ; Sat, 13 Dec 2008 14:03:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=LGUxq6doJDnxefYUw+NSRuTz+HZkjBGPK7TXD/3K4+w=; b=PbzDKCnJVeOH06zl7f+4u2c0KatVvx0I25+I52jyV2c9ZZM7S4SAugMHV/M/1Uw5MJ u362QwY5RGUb8btz4Ge8tjQoXzpK0GH9jPPQyD56wGhjlpAA4qg4w4qjI2w9w3iIwSRH Hc+BVVtbElBqDeDfgiVj7/tGBLSbVSA1M7Jm0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=X8KrkbNZ/AdzLBz29JLeoj84i+8DfEqS2rRXn0071LnmomF5Qx1gNES9iQb2OVaX0d yJfp5wmlcAcAFtgHdwpgr+lZXMtqjblaEyUnQlAaebrCLMTgri+7FPGTAfKsvy6fkqNv 86iAY3uksmmS5to1T9U9l8gHIcBdC2vUgni8Q= Received: by 10.231.18.130 with SMTP id w2mr62605iba.11.1229205833060; Sat, 13 Dec 2008 14:03:53 -0800 (PST) Received: by 10.231.11.72 with HTTP; Sat, 13 Dec 2008 14:03:53 -0800 (PST) Message-ID: <3a142e750812131403p31841403ub9d5693278c74111@mail.gmail.com> Date: Sat, 13 Dec 2008 23:03:53 +0100 From: "Paul B. Mahol" To: "Bruce Simpson" In-Reply-To: <4943F43B.4060105@incunabulum.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> <200812041747.09040.gnemmi@gmail.com> <4938FE44.9090608@FreeBSD.org> <4939133E.2000701@FreeBSD.org> <493CEE90.7050104@FreeBSD.org> <3a142e750812090553l564bff84pe1f02cd1b03090ff@mail.gmail.com> <4943F43B.4060105@incunabulum.net> Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org, "Bruce M. Simpson" Subject: Re: ext2fuse: user-space ext2 implementation X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2008 22:03:54 -0000 On 12/13/08, Bruce Simpson wrote: > Paul B. Mahol wrote: >> On 12/8/08, Bruce M. Simpson wrote: >> >>> I have rolled a port for ext2fuse: >>> http://people.freebsd.org/~bms/dump/fusefs-ext2fs.tar >>> >> >> Ignoring fact that is buggy, slooow and port doesnt have any cache >> implemented >> and port leaves files behind in share/doc/ext2fuse when package >> deleted it looks fine. >> > > Can you please relay this feedback to the authors of ext2fuse? > > As mentioned earlier in the thread, the ext2fuse code could benefit from > UBLIO-ization. Are you or any other volunteers happy to help out here? Well, first higher priority would be to fix existing bugs. It would be very little gain with user cache, because it is already too much IMHO slow and adding user cache will not make it faster, but that is not port problem. > Can you elaborate further on the files being left behind by the port? I > didn't see this issue in my own testing. It install files in this way: test -z "/usr/local/share/doc/ext2fuse" || ./install-sh -c -d "/usr/local/share/doc/ext2fuse" make deinstall and pkg_delete doesnt not remove that files/dir, -- Paul