From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 00:28:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 378ED16A4CE; Sun, 21 Nov 2004 00:28:33 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8077143D49; Sun, 21 Nov 2004 00:28:32 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAL0RJ13013360; Sat, 20 Nov 2004 17:27:26 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 20 Nov 2004 17:27:38 -0700 (MST) Message-Id: <20041120.172738.38711956.imp@bsdimp.com> To: le@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <20041120104224.E566@korben.prv.univie.ac.at> References: <20041119184422.K578@korben.in.tern> <20041120.000624.122832691.imp@bsdimp.com> <20041120104224.E566@korben.prv.univie.ac.at> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@FreeBSD.org Subject: Re: Problem with HP DL380 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 00:28:33 -0000 In message: <20041120104224.E566@korben.prv.univie.ac.at> Lukas Ertl writes: : On Sat, 20 Nov 2004, M. Warner Losh wrote: : : > : Setting hw.pci.do_powerstate=0 in /boot/loader.conf fixes this problem. : > : > Dang. I missed the earlier part of this thread. You shouldn't need : > to do this if I coded things up right. But, alas, you do. Can you : > send me the details? : : No, I think you did everything right. If I understand it correctly, then : hw.pci.do_powerstate puts a device into C3 state if no driver attaches. : That's just what happens here. That iLO service processor of the DL380s : shows up as normal PCI device, but exports the console to the network even : without specific driver (as there is none for FreeBSD), so that it works : independent of the OS. : : So, since there is no driver, the device gets powered down as soon as the : kernel initializes its ACPI parts, and then the iLO console stops working. It may be the case that the base device class needs a 'dummy' driver to prevent things like this from happening. We have a hack in the code right now for displays until the situation there is straightened out. Warner From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 00:42:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 908A316A4CE for ; Sun, 21 Nov 2004 00:42:58 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id B118C43D31 for ; Sun, 21 Nov 2004 00:42:56 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAL0fvZg029929 for ; Sun, 21 Nov 2004 11:11:57 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Sun, 21 Nov 2004 11:12:48 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAL0dth08494 for ; Sun, 21 Nov 2004 11:09:55 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RZJDVYLS; Sun, 21 Nov 2004 11:09:41 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAL0e2Lb007503 for ; Sun, 21 Nov 2004 11:10:02 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAL0e2UO007502 for freebsd-current@freebsd.org; Sun, 21 Nov 2004 11:10:02 +1030 (CST) (envelope-from wilkinsa) Date: Sun, 21 Nov 2004 11:10:02 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20041121004001.GB7395@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org References: <20041116170615.K92983@pcle2.cc.univie.ac.at> <20041120.000624.122832691.imp@bsdimp.com> <20041120104224.E566@korben.prv.univie.ac.at> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20041120104224.E566@korben.prv.univie.ac.at> User-Agent: Mutt/1.5.6i Subject: Re: Problem with HP DL380 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 00:42:58 -0000 what is meant by 'C3 state' ? - aW 0n Sat, Nov 20, 2004 at 10:46:25AM +0100, Lukas Ertl wrote: > On Sat, 20 Nov 2004, M. Warner Losh wrote: > > >: Setting hw.pci.do_powerstate=0 in /boot/loader.conf fixes this problem. > > > >Dang. I missed the earlier part of this thread. You shouldn't need > >to do this if I coded things up right. But, alas, you do. Can you > >send me the details? > > No, I think you did everything right. If I understand it correctly, then > hw.pci.do_powerstate puts a device into C3 state if no driver attaches. > That's just what happens here. That iLO service processor of the DL380s > shows up as normal PCI device, but exports the console to the network even > without specific driver (as there is none for FreeBSD), so that it works > independent of the OS. > > So, since there is no driver, the device gets powered down as soon as the > kernel initializes its ACPI parts, and then the iLO console stops working. > > cheers, > le > > -- > Lukas Ertl http://homepage.univie.ac.at/l.ertl/ > le@FreeBSD.org http://people.freebsd.org/~le/ > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 02:00:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D52CD16A4CE for ; Sun, 21 Nov 2004 02:00:56 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EA9443D5A for ; Sun, 21 Nov 2004 02:00:56 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iAL20oLs075552; Sat, 20 Nov 2004 20:00:50 -0600 (CST) (envelope-from dan) Date: Sat, 20 Nov 2004 20:00:50 -0600 From: Dan Nelson To: "Bjoern A. Zeeb" Message-ID: <20041121020050.GB94473@dan.emsphone.com> References: <20041119114233.C43B.SHINO@fornext.org> <20041119185315.C43D.SHINO@fornext.org> <20041119120102.GM69710@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: Shunsuke SHINOMIYA cc: freebsd-current@freebsd.org cc: Jeremie Le Hen Subject: Re: interrupt moderation for if_* [was: serious networking (em) ...] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 02:00:57 -0000 In the last episode (Nov 20), Bjoern A. Zeeb said: > On Fri, 19 Nov 2004, Jeremie Le Hen wrote: > > > Hi, Jeremie, how is this? To disable Interrupt Moderation, > > > sysctl hw.em?.int_throttle_valve=0. > > > > Great, I would have called it "int_throttle_ceil", but that's a > > detail and my opinion is totally subjective. > > > > > However, because this patch is just made now, it is not fully tested. > > > > I'll give it a try this weekend although I won't be able to make > > performance mesurements. > > when thinking about this could there be some "global" way for > interrupt moderation; For if_sk there is this PR: > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/41220 > > something 'unique' to all NIC drivers would be good I guess ? You need NIC support for it, just like checksum offloading. And other drivers offer more sysctls; fxp lets you choose the maximum delay and maximum packets to hold before firing an interrupt. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 02:07:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9789C16A4CE for ; Sun, 21 Nov 2004 02:07:46 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FEAF43D31 for ; Sun, 21 Nov 2004 02:07:46 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iAL27jtu085754; Sat, 20 Nov 2004 20:07:45 -0600 (CST) (envelope-from dan) Date: Sat, 20 Nov 2004 20:07:45 -0600 From: Dan Nelson To: Dick Davies Message-ID: <20041121020745.GC94473@dan.emsphone.com> References: <419CD314.80900@fer.hr> <20041118171012.GB19265@dan.emsphone.com> <20041120222325.GC17297@lb.tenfour> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041120222325.GC17297@lb.tenfour> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: FreeBSD Current Users Subject: Re: Replacing passwd? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 02:07:46 -0000 In the last episode (Nov 20), Dick Davies said: > * Dan Nelson [1110 17:10]: > > In the last episode (Nov 18), Ivan Voras said: > > > I've setup pam_ldap and nss_ldap and samba3 and smbldap, and it works > > > fine, but it would be nice to replace /usr/bin/passwd with > > > smbldap-passwd (which changes both NTLM and Unix password fields in > > > LDAP, while passwd is unaware of LDAP, at least according to man > > > page). Is there a clean way of doing it so I don't have to replace > > > it by hand after each installworld? > > > > passwd just uses PAM to set passwords > > When did that come in? I can't get passwd(1) to change an ldap password, I get: > > rasputnik@eris:rasputnik$ passwd > passwd: Sorry, `passwd' can only change passwords for local or NIS users. > rasputnik@eris:rasputnik$ uname -a > FreeBSD eris 5.3-STABLE FreeBSD 5.3-STABLE #4: Mon Oct 25 18:03:11 BST 2004 root@eris:/usr/obj/usr/src/sys/ERIS i386 > rasputnik@eris:rasputnik$ > > - this is an nss_ldap nsswitched account, logged in over ssh (pam_ldap auth). Weird. There's definitely a lot of PAM code in passwd.c. What happens if you comment out the errx() function that prints that error (line 124)? -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 12:00:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 087D016A4CE for ; Sun, 21 Nov 2004 12:00:40 +0000 (GMT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30CBA43D31 for ; Sun, 21 Nov 2004 12:00:39 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id iALC0UEn045442; Sun, 21 Nov 2004 13:00:33 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <41A0835B.9040404@DeepCore.dk> Date: Sun, 21 Nov 2004 13:00:27 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: m.kucenski@computer.org References: <20041119171236.DNZH20678.lakermmtao09.cox.net@smtp.east.cox.net> In-Reply-To: <20041119171236.DNZH20678.lakermmtao09.cox.net@smtp.east.cox.net> Content-Type: multipart/mixed; boundary="------------060904080909000102080101" X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: freebsd-current@freebsd.org Subject: Re: ATAng support for reading from register on ATAREQUEST command? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 12:00:40 -0000 This is a multi-part message in MIME format. --------------060904080909000102080101 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Matt Kucenski wrote: > I am trying to develop a program that will allow modifications to the H= ost Protected Area settings and one of the commands (READ NATIVE MAX ADDR= ESS) returns the native max address back in the register (LBA high, low, = mid). >=20 > I have been looking at the smartmontools project for pointers on how to= write this code and according to that source, this is not possible yet w= ith ATAng. There is a comment in their code that another command (ATA_CM= D_READ_REG) patch has been submitted to ATAng, but it does not appear to = have made it into any of the latest sources. >=20 > Can anyone offer any information on this? The following patch returns the register values in the request you sent=20 through ioctl call. That should do the trick without any new calls.. --=20 -S=F8ren --------------060904080909000102080101 Content-Type: text/plain; name="ata-smart-patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ata-smart-patch" Index: ata-all.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v retrieving revision 1.233 diff -u -r1.233 ata-all.c --- ata-all.c 19 Oct 2004 20:13:38 -0000 1.233 +++ ata-all.c 19 Nov 2004 18:59:55 -0000 @@ -546,10 +546,10 @@ bcopy(iocmd->u.request.u.atapi.ccb, request->u.atapi.ccb, 16); } else { - request->u.ata.command = iocmd->u.request.u.ata.command; - request->u.ata.feature = iocmd->u.request.u.ata.feature; - request->u.ata.lba = iocmd->u.request.u.ata.lba; - request->u.ata.count = iocmd->u.request.u.ata.count; + request->u.ata.command = iocmd->u.request.u.ata.command; + request->u.ata.feature = iocmd->u.request.u.ata.feature; + request->u.ata.lba = iocmd->u.request.u.ata.lba; + request->u.ata.count = iocmd->u.request.u.ata.count; } request->timeout = iocmd->u.request.timeout; @@ -566,6 +566,10 @@ ata_queue_request(request); + iocmd->u.request.u.ata.command = request->u.ata.command; + iocmd->u.request.u.ata.feature = request->u.ata.feature; + iocmd->u.request.u.ata.lba = request->u.ata.lba; + iocmd->u.request.u.ata.count = request->u.ata.count; if (request->result) iocmd->u.request.error = request->result; else { --------------060904080909000102080101-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 12:27:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C70816A4CE; Sun, 21 Nov 2004 12:27:11 +0000 (GMT) Received: from juniper.fornext.org (53.35.138.210.xn.2iij.net [210.138.35.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 541A943D49; Sun, 21 Nov 2004 12:27:10 +0000 (GMT) (envelope-from shino@fornext.org) Received: from [127.0.0.1] (thyme.fornext.org [192.168.3.32]) by juniper.fornext.org (Postfix) with ESMTP id B03342A; Sun, 21 Nov 2004 21:27:08 +0900 (JST) Date: Sun, 21 Nov 2004 21:27:08 +0900 From: Shunsuke SHINOMIYA To: Jeremie Le Hen In-Reply-To: <20041119120102.GM69710@obiwan.tataz.chchile.org> References: <20041119185315.C43D.SHINO@fornext.org> <20041119120102.GM69710@obiwan.tataz.chchile.org> Message-Id: <20041121205158.45CE.SHINO@fornext.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.11.02 [ja] cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re[2]: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 12:27:11 -0000 Jeremie, thank you for your comment. I did simple benchmark at some settings. I used two boxes which are single Xeon 2.4GHz with on-boarded em. I measured a TCP throughput by iperf. These results show that the throughput of TCP increased if Interrupt Moderation is turned OFF. At least, adjusting these parameters affected TCP performance. Other appropriate combination of parameter may exist. The settings are some combinations of hw.em0.rx_int_delay hw.em0.tx_int_delay hw.em0.rx_abs_int_delay hw.em0.tx_abs_int_delay hw.em0.int_throttle_ceil. In this mail, A setting, hw.em0.rx_int_delay: 0 hw.em0.tx_int_delay: 66 hw.em0.rx_abs_int_delay: 66 hw.em0.tx_abs_int_delay: 66 hw.em0.int_throttle_ceil: 8000 is abbreviated to (0, 66, 66, 66, 8000). TCP window size was not adjusted by iperf's options. It mean that iperf is used by default setting. sender : default(0, 66, 66, 66, 8000), receiver : default(0, 66, 66, 66, 8000) 1st trial 852Mbps 2nd trial 861Mbps 3rd trial 822Mbps 4th trial 791Mbps 5th trial 826Mbps average 830.4Mbps, std. dev. 27.6Mbps sender : (0, 0, 0, 0, 8000), receiver : (0, 0, 0, 0, 8000) 1st trial 787Mbps 2nd trial 793Mbps 3rd trial 843Mbps 4th trial 771Mbps 5th trial 848Mbps average 808.4Mbps, std. dev. 34.9Mbps sender : off(0, 0, 0, 0, 0), receiver : off(0, 0, 0, 0, 0) 1st trial 902Mbps 2nd trial 901Mbps 3rd trial 899Mbps 4th trial 894Mbps 5th trial 900Mbps average 899.2Mbps, std. dev. 3.1Mbps -- Shunsuke SHINOMIYA From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 12:47:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81DB116A4CE for ; Sun, 21 Nov 2004 12:47:56 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3059343D1F for ; Sun, 21 Nov 2004 12:47:56 +0000 (GMT) (envelope-from radovanovic@gmail.com) Received: by rproxy.gmail.com with SMTP id b11so183719rne for ; Sun, 21 Nov 2004 04:47:55 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=AVBTwrh3akE+YZq/+9JjMboefgW9mqDr35/hCxNx2pgRedfGI3v1ooHq/DyUkXI5wrRpCLss+EniSEVFatAKFJ6WPr3VwpgvBRy04TUgehfo3WPHQUzXXYfSUZAwLFl+2kaXeCKXgPz10EJ03tyxXTWCA1N96AcfwDJg4omQt4Q= Received: by 10.39.1.66 with SMTP id d66mr443836rni; Sun, 21 Nov 2004 04:47:55 -0800 (PST) Received: by 10.38.151.49 with HTTP; Sun, 21 Nov 2004 04:47:55 -0800 (PST) Message-ID: <8a2be41b041121044755a4baaf@mail.gmail.com> Date: Sun, 21 Nov 2004 13:47:55 +0100 From: Ivan Radovanovic To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: 5.3-Release Lucent modem, ppp or kernel problem? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Ivan Radovanovic List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 12:47:56 -0000 I recently upgraded from FreeBSD 5.1 to FreeBSD 5.3-Release, after that I am experiencing problem with my Lucent modem. Modem refuses to connect to my isp, and after using term command in ppp I discovered that after trying to connect modem displays CONNECT 43300 NoEC and after that print some garbage characters (not only one character repeating but looks like random characters). I thought there could be problem with ppp program (since modem driver is same version as in 5.1), so I used ppp program from 5.1 (it is 3.1 version), but results are the same. Problem is not in modem hardware or line since same modem still works in FreeBSD 5.1. However I would like to get this modem working in 5.3 so I could completely migrate to FreeBSD 5.3. I also tried using generic kernel instead of my custom kernel but situation is the same. Any ideas what could be causing problems? Regards, Ivan From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 13:00:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DADB716A4CE for ; Sun, 21 Nov 2004 13:00:09 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13DAB43D58 for ; Sun, 21 Nov 2004 13:00:09 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 388391FF9AC; Sun, 21 Nov 2004 14:00:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 144B51FF9A8; Sun, 21 Nov 2004 14:00:05 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id DC58F155D0; Sun, 21 Nov 2004 12:55:59 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id D95161538C; Sun, 21 Nov 2004 12:55:59 +0000 (UTC) Date: Sun, 21 Nov 2004 12:55:59 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Dan Nelson In-Reply-To: <20041121020050.GB94473@dan.emsphone.com> Message-ID: References: <20041119114233.C43B.SHINO@fornext.org> <20041119185315.C43D.SHINO@fornext.org> <20041119120102.GM69710@obiwan.tataz.chchile.org> <20041121020050.GB94473@dan.emsphone.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: Shunsuke SHINOMIYA cc: freebsd-current@freebsd.org cc: Jeremie Le Hen Subject: Re: interrupt moderation for if_* [was: serious networking (em) ...] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 13:00:10 -0000 On Sat, 20 Nov 2004, Dan Nelson wrote: > In the last episode (Nov 20), Bjoern A. Zeeb said: > > On Fri, 19 Nov 2004, Jeremie Le Hen wrote: > > > > Hi, Jeremie, how is this? To disable Interrupt Moderation, > > > > sysctl hw.em?.int_throttle_valve=0. > > > > > > Great, I would have called it "int_throttle_ceil", but that's a > > > detail and my opinion is totally subjective. > > > > > > > However, because this patch is just made now, it is not fully tested. > > > > > > I'll give it a try this weekend although I won't be able to make > > > performance mesurements. > > > > when thinking about this could there be some "global" way for > > interrupt moderation; For if_sk there is this PR: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/41220 > > > > something 'unique' to all NIC drivers would be good I guess ? > > You need NIC support for it, just like checksum offloading. And other good example;) We do have [-,]{rxcsum, txcsum} in ifconfig for turning this on/off if supported. What I meant is to have common names for the interface (sysctl) for all NICs supporting this - "on grep finds all" and not to start home-brewed names for each driver. There might be some different names needed because int_delay, int_throttle_ceil or sk_interrupt_mod might or might not achieve the same but if they do names should be same. > drivers offer more sysctls; fxp lets you choose the maximum delay and > maximum packets to hold before firing an interrupt. great; someone should improve fxp.4 I guess ;) -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 00:35:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78AAC16A4CE; Sun, 21 Nov 2004 00:35:27 +0000 (GMT) Received: from mail.agala.net (Ib21d.i.pppool.de [85.73.178.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA2C543D48; Sun, 21 Nov 2004 00:35:22 +0000 (GMT) (envelope-from frank@barda.agala.net) Received: from mail.agala.net (mail.agala.net [192.168.20.1]) by mail.agala.net (8.13.1/8.13.1) with ESMTP id iAL0XQMa024593; Sun, 21 Nov 2004 01:33:28 +0100 (CET) (envelope-from frank@barda.agala.net) From: "Frank J. Beckmann" Organization: agala naga doron To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Date: Sun, 21 Nov 2004 01:32:44 +0100 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411210133.14396.frank@barda.agala.net> X-Scanned-By: MIMEDefang 2.44 X-Mailman-Approved-At: Sun, 21 Nov 2004 13:17:08 +0000 Subject: ppp trouble with 5.3-stable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 00:35:27 -0000 Hi, a few days ago a did an upgrade from something pre 5.3-rc7 to the latest 5.3-stable. Since then I have only trouble with ppp. My computer is connectet to the internet via pppoe (FreeNet in Germany). My provider closes the connection once every 24 ours, but ppp now fails to redial. /var/log/ppp.log says: Nov 20 12:25:36 kairo ppp[234]: tun0: LCP: deflink: LayerDown Nov 20 12:25:36 kairo ppp[234]: tun0: LCP: deflink: SendTerminateAck(22) state = Opened Nov 20 12:25:36 kairo ppp[234]: tun0: LCP: deflink: State change Opened --> Stopping Nov 20 12:25:36 kairo ppp[234]: tun0: CCP: deflink: State change Stopped --> Closed Nov 20 12:25:36 kairo ppp[234]: tun0: CCP: deflink: State change Closed --> Initial Nov 20 12:25:36 kairo ppp[234]: tun0: Phase: deflink: open -> lcp Nov 20 12:25:36 kairo ppp[234]: tun0: IPCP: deflink: LayerDown: 85.73.146.248 Nov 20 12:25:37 kairo ppp[234]: tun0: IPCP: Using trigger address 0.0.0.0 Nov 20 12:25:37 kairo ppp[234]: tun0: IPCP: deflink: State change Opened --> Starting Nov 20 12:25:37 kairo ppp[234]: tun0: IPCP: deflink: LayerFinish. Nov 20 12:25:37 kairo ppp[234]: tun0: IPCP: Connect time: 86402 secs: 76176788 octets in, 19528684 octets out Nov 20 12:25:37 kairo ppp[234]: tun0: IPCP: 128374 packets in, 133857 packets out Nov 20 12:25:37 kairo ppp[234]: tun0: IPCP: total 1107 bytes/sec, peak 131717 bytes/sec on Sat Nov 20 02:26:02 2004 Nov 20 12:25:37 kairo ppp[234]: tun0: IPCP: deflink: State change Starting --> Initial Nov 20 12:25:37 kairo ppp[234]: tun0: Phase: Received NGM_PPPOE_CLOSE Nov 20 12:25:37 kairo ppp[234]: tun0: Phase: deflink: Device disconnected Nov 20 12:25:37 kairo ppp[234]: tun0: LCP: deflink: State change Stopping --> Starting Nov 20 12:25:37 kairo ppp[234]: tun0: LCP: deflink: LayerFinish Nov 20 12:25:37 kairo ppp[234]: tun0: LCP: deflink: State change Starting --> Initial Nov 20 12:25:37 kairo ppp[234]: tun0: Phase: deflink: Disconnected! Nov 20 12:25:37 kairo ppp[234]: tun0: Phase: deflink: lcp -> logout Nov 20 12:25:37 kairo ppp[234]: tun0: Phase: deflink: Disconnected! Nov 20 12:25:37 kairo ppp[234]: tun0: Phase: deflink: logout -> hangup Nov 20 12:25:37 kairo ppp[234]: tun0: Phase: deflink: Connect time: 86412 secs: 75971965 octets in, 19848728 octets out Nov 20 12:25:37 kairo ppp[234]: tun0: Phase: deflink: 131260 packets in, 136754 packets out Nov 20 12:25:37 kairo ppp[234]: tun0: Phase: total 1108 bytes/sec, peak 131659 bytes/sec on Sat Nov 20 02:26:02 2004 Nov 20 12:25:37 kairo ppp[234]: tun0: Phase: deflink: hangup -> opening Nov 20 12:25:37 kairo ppp[234]: tun0: Phase: deflink: Enter pause (3) for redialing. Nov 20 12:25:37 kairo ppp[234]: tun0: Chat: deflink: Reconnect try 1 of 0 Nov 20 12:25:40 kairo ppp[234]: tun0: Chat: deflink: Redial timer expired. Nov 20 12:25:40 kairo ppp[234]: tun0: Phase: deflink: Connected! Nov 20 12:25:40 kairo ppp[234]: tun0: Phase: deflink: opening -> dial Nov 20 12:25:40 kairo ppp[234]: tun0: Phase: deflink: dial -> carrier Nov 20 12:25:41 kairo ppp[234]: tun0: Phase: deflink: Disconnected! Nov 20 12:25:41 kairo ppp[234]: tun0: Phase: deflink: carrier -> hangup Nov 20 12:25:41 kairo ppp[234]: tun0: Phase: deflink: Connect time: 1 secs: 0 octets in, 0 octets out Nov 20 12:25:41 kairo ppp[234]: tun0: Phase: deflink: 131260 packets in, 136754 packets out Nov 20 12:25:41 kairo ppp[234]: tun0: Phase: total 0 bytes/sec, peak 0 bytes/sec on Sat Nov 20 12:25:40 2004 Nov 20 12:25:41 kairo ppp[234]: tun0: Phase: deflink: hangup -> opening Nov 20 12:25:41 kairo ppp[234]: tun0: Phase: deflink: Enter pause (0) for redialing. Nov 20 12:25:41 kairo ppp[234]: tun0: Chat: deflink: Redial timer expired. Nov 20 12:25:41 kairo ppp[234]: tun0: Phase: deflink: Connected! Nov 20 12:25:41 kairo ppp[234]: tun0: Phase: deflink: opening -> dial Nov 20 12:25:41 kairo ppp[234]: tun0: Phase: deflink: dial -> carrier Nov 20 12:25:43 kairo ppp[234]: tun0: Phase: deflink: Disconnected! ... Even killing and restarting ppp only worked once. The other times I had to reboot. The interactive interface of ppp is broken, too: kairo:~# pppctl /var/run/tun0.socket Password: PPP ON kairo> show Use ``show ?'' to get a list. PPP ON kairo> show ? (o) = Optional context, (c) = Context required Connection closed kairo:~# Almost every command behaves that way. -- Bye Frank From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 14:49:17 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 165F016A4CE for ; Sun, 21 Nov 2004 14:49:17 +0000 (GMT) Received: from mail.evip.pl (mail.evip.com.pl [212.244.157.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1938C43D60 for ; Sun, 21 Nov 2004 14:49:16 +0000 (GMT) (envelope-from w@evip.pl) Received: from drwebc by mail.evip.pl with drweb-scanned (Exim 4.22) id 1CVt1V-000NwR-DM; Sun, 21 Nov 2004 15:49:05 +0100 Received: from w by mail.evip.pl with local (Exim 4.22) id 1CVt1V-000NwL-9w; Sun, 21 Nov 2004 15:49:05 +0100 Date: Sun, 21 Nov 2004 15:49:05 +0100 From: Wiktor Niesiobedzki To: Dan Nelson Message-ID: <20041121144905.GE3584@mail.evip.pl> References: <419CD314.80900@fer.hr> <20041118171012.GB19265@dan.emsphone.com> <20041120222325.GC17297@lb.tenfour> <20041121020745.GC94473@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041121020745.GC94473@dan.emsphone.com> User-Agent: Mutt/1.5.6i cc: FreeBSD Current Users cc: Dick Davies Subject: Re: Replacing passwd? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 14:49:17 -0000 On Sat, Nov 20, 2004 at 08:07:45PM -0600, Dan Nelson wrote: > > When did that come in? I can't get passwd(1) to change an ldap password, I get: > > > > rasputnik@eris:rasputnik$ passwd > > passwd: Sorry, `passwd' can only change passwords for local or NIS users. > > rasputnik@eris:rasputnik$ uname -a > > FreeBSD eris 5.3-STABLE FreeBSD 5.3-STABLE #4: Mon Oct 25 18:03:11 BST 2004 root@eris:/usr/obj/usr/src/sys/ERIS i386 > > rasputnik@eris:rasputnik$ > > > > - this is an nss_ldap nsswitched account, logged in over ssh (pam_ldap auth). > > Weird. There's definitely a lot of PAM code in passwd.c. What happens > if you comment out the errx() function that prints that error (line > 124)? > I was playing with it today and removing errx function allows passwd to change the password, but the other problem I step on is: How to properly configure /etc/pam.d/passwd The configuration, which I have now is simply: password sufficient /usr/local/lib/pam_ldap.so password sufficient pam_unix.so no_warn try_first_pass nullok But it will give strange results, for example: % ./passwd Enter login(LDAP) password: New password: Password too short New password: Password too short New password: Password too short New Password: Retype New Password: As we may see, after three failures to get the new password we switch to pam_unix, which tries to change the user, which does not exists in /etc/master.passwd. Or: % ./passwd Changing 0 password Enter login(LDAP) password: LDAP Password incorrect: try again Enter login(LDAP) password: LDAP Password incorrect: try again Enter login(LDAP) password: LDAP Password incorrect: try again Old Password: New Password: Retype New Password: Which obviously does not result in any password change, as pam_unix tries to change the password. My goal is to have some local users, and some users coming from LDAP, and it would be the best, when all could have change their password through passwd. Does this behaviour of passwd shows the problem within pam_unix (as it does not check, whether the user exists in master.passwd - only by _PWF_SOURCE) Maybe there is a need, to implement is_user_of_this_auth_method or something like that? Cheers, Wiktor Niesiobedzki From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 16:58:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04E3316A4CE for ; Sun, 21 Nov 2004 16:58:53 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A67643D41 for ; Sun, 21 Nov 2004 16:58:52 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iALGwUcN023690; Sun, 21 Nov 2004 09:58:37 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 21 Nov 2004 09:53:33 -0700 (MST) Message-Id: <20041121.095333.34759989.imp@bsdimp.com> To: alex.wilkinson@dsto.defence.gov.au From: "M. Warner Losh" In-Reply-To: <20041121004001.GB7395@squash.dsto.defence.gov.au> References: <20041120.000624.122832691.imp@bsdimp.com> <20041120104224.E566@korben.prv.univie.ac.at> <20041121004001.GB7395@squash.dsto.defence.gov.au> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Problem with HP DL380 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 16:58:53 -0000 In message: <20041121004001.GB7395@squash.dsto.defence.gov.au> "Wilkinson, Alex" writes: : what is meant by 'C3 state' ? It is a typo for D3. D3 state is a state where the power is bascially off to the device, but in such a way that it can be powered back on as needed. This is typically referred to as D3hot in the pci standards and related documentation. Warner From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 17:27:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BCDEF16A4CE; Sun, 21 Nov 2004 17:27:31 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94F6543D31; Sun, 21 Nov 2004 17:27:31 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 3C3BBF20E4; Sun, 21 Nov 2004 09:27:31 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11614-01; Sun, 21 Nov 2004 09:27:29 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 88FBDF20A3; Sun, 21 Nov 2004 09:27:29 -0800 (PST) From: Sean McNeil To: Shunsuke SHINOMIYA In-Reply-To: <20041121205158.45CE.SHINO@fornext.org> References: <20041119185315.C43D.SHINO@fornext.org> <20041119120102.GM69710@obiwan.tataz.chchile.org> <20041121205158.45CE.SHINO@fornext.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-+MwiF7b73TDd4FXZ8OfL" Date: Sun, 21 Nov 2004 09:27:29 -0800 Message-Id: <1101058049.12022.5.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-stable@freebsd.org cc: freebsd-current@freebsd.org cc: Jeremie Le Hen Subject: Re: Re[2]: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 17:27:31 -0000 --=-+MwiF7b73TDd4FXZ8OfL Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2004-11-21 at 21:27 +0900, Shunsuke SHINOMIYA wrote: > Jeremie, thank you for your comment. >=20 > I did simple benchmark at some settings. >=20 > I used two boxes which are single Xeon 2.4GHz with on-boarded em. > I measured a TCP throughput by iperf. >=20 > These results show that the throughput of TCP increased if Interrupt > Moderation is turned OFF. At least, adjusting these parameters affected > TCP performance. Other appropriate combination of parameter may exist. I have found interrupt moderation to seriously kill gigE performance. Another test you can make is to have the driver always defrag packets in em_encap(). Something like m_head =3D m_defrag(*m_headp, M_DONTWAIT); if (m_head =3D=3D NULL) return ENOBUFS; --=-+MwiF7b73TDd4FXZ8OfL Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBoNAByQsGN30uGE4RAhSXAKDEgYADxq+/EmcCYap8FGRlCgI8/ACeLxz/ w7l/SkoYwwZfQMVn4w/KTpI= =CGLu -----END PGP SIGNATURE----- --=-+MwiF7b73TDd4FXZ8OfL-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 17:40:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EDDD16A4CE for ; Sun, 21 Nov 2004 17:40:35 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4FFD43D48 for ; Sun, 21 Nov 2004 17:40:34 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iALHeXXT014279; Sun, 21 Nov 2004 11:40:33 -0600 (CST) (envelope-from dan) Date: Sun, 21 Nov 2004 11:40:33 -0600 From: Dan Nelson To: Wiktor Niesiobedzki Message-ID: <20041121174033.GA3019@dan.emsphone.com> References: <419CD314.80900@fer.hr> <20041118171012.GB19265@dan.emsphone.com> <20041120222325.GC17297@lb.tenfour> <20041121020745.GC94473@dan.emsphone.com> <20041121144905.GE3584@mail.evip.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041121144905.GE3584@mail.evip.pl> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: FreeBSD Current Users cc: Dick Davies Subject: Re: Replacing passwd? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 17:40:35 -0000 In the last episode (Nov 21), Wiktor Niesiobedzki said: > I was playing with it today and removing errx function allows passwd > to change the password, but the other problem I step on is: How to > properly configure /etc/pam.d/passwd > > The configuration, which I have now is simply: > password sufficient /usr/local/lib/pam_ldap.so > password sufficient pam_unix.so no_warn try_first_pass nullok You probably don't need pam_unix in there at all, since there's no way it'll work (no local passwd entry). -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 18:09:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1F0416A4CE for ; Sun, 21 Nov 2004 18:09:30 +0000 (GMT) Received: from mx.res.lt (mx.res.lt [84.32.72.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 328AC43D54 for ; Sun, 21 Nov 2004 18:09:26 +0000 (GMT) (envelope-from rwd@res.lt) Received: from localhost (localhost [127.0.0.1]) by mx.res.lt (Postfix) with ESMTP id 988512E02A for ; Sun, 21 Nov 2004 20:04:19 +0200 (EET) Received: from mx.res.lt ([127.0.0.1]) by localhost (mx.res.lt [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 59207-09 for ; Sun, 21 Nov 2004 20:04:18 +0200 (EET) Received: from localhost (rwd.res.lt [84.32.72.90]) by mx.res.lt (Postfix) with ESMTP id E96DE2E029 for ; Sun, 21 Nov 2004 20:04:18 +0200 (EET) Date: Sun, 21 Nov 2004 20:09:17 -0800 From: Arturas X-Mailer: The Bat! (v3.0.1.33) Professional Organization: Radijo Elektonines Sistemos X-Priority: 3 (Normal) Message-ID: <1136755651.20041121200917@res.lt> To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at res.lt Subject: disk timeout - system hangs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Arturas List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 18:09:30 -0000 Hello, I have a problem when i remove sata data cable on working system, then disk timeout and system hangs with error that disk timeout. Disk is not a system disk, when second disk is not mounted, i can remove data cable, and system won't hangs, but when i mount it, and remove data cable, system after few seconds will write that disk adX timeout, and system hangs. This happens even thereis no mirror raid or i create with 2 disks two different arrays. dmesg: Copyright (c) 1992-2004 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 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (2992.51-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf33 Stepping = 3 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 1072889856 (1023 MB) avail memory = 1040273408 (992 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xfa000000-0xfbffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 3.0 on pci0 pci2: on pcib2 em0: port 0x9c00-0x9c1f mem 0xfc5e0000-0xfc5fffff irq 18 at device 1 .0 on pci2 em0: Ethernet address: 00:0c:f1:ed:a8:a5 em0: Speed:N/A Duplex:N/A uhci0: port 0xcc00-0xcc1f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd000-0xd01f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xd400-0xd41f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xd800-0xd81f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pcib3: at device 30.0 on pci0 pci3: on pcib3 fxp0: port 0xbc00-0xbc3f mem 0xfe900000-0xfe9fffff,0xfeafe000-0xfeafefff irq 17 at device 2.0 on pci3 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:90:27:aa:7e:11 pci3: at device 6.0 (no driver attached) atapci0: port 0xac00-0xac7f,0xb000-0xb00f,0xb400-0xb43f mem 0xfeaa0000-0xfeabffff,0xfea fd000-0xfeafdfff irq 17 at device 7.0 on pci3 atapci0: failed: rid 0x20 is memory, requested 4 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 ata4: channel #2 on atapci0 ata5: channel #3 on atapci0 fxp1: port 0xa800-0xa83f mem 0xfeafc000-0xfeafcfff irq 20 at device 8.0 on pci3 miibus1: on fxp1 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: Ethernet address: 00:0c:f1:ed:a8:a7 isab0: at device 31.0 on pci0 isa0: on isab0 atapci1: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci1 ata1: channel #1 on atapci1 atapci2: port 0xdc00-0xdc0f,0xe000-0xe003,0xe400-0xe407,0xe800-0xe803,0xec00-0xec07 irq 18 at device 31.2 on pci0 ata6: channel #0 on atapci2 ata7: channel #1 on atapci2 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3,0x3f0-0x3f1 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xd0800-0xd17ff,0xc8000-0xc8fff,0xc0000-0xc7fff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 2992514647 Hz quality 800 Timecounters tick every 10.000 msec acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% ad4: 78167MB [158816/16/63] at ata2-master SATA150 ad6: 78167MB [158816/16/63] at ata3-master SATA150 ad8: 70911MB [144073/16/63] at ata4-master SATA150 ad10: 70911MB [144073/16/63] at ata5-master SATA150 ar0: 77247MB [9847/255/63] status: READY subdisks: disk0 READY on ad4 at ata2-master disk1 READY on ad6 at ata3-master ar1: 70571MB [8996/255/63] status: READY subdisks: disk0 READY on ad8 at ata4-master disk1 READY on ad10 at ata5-master Mounting root from ufs:/dev/ar0s1a em0: Link is up 100 Mbps Full Duplex -- Best regards, Arturas mailto:rwd@res.lt From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 18:29:08 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B198B16A4CE for ; Sun, 21 Nov 2004 18:29:08 +0000 (GMT) Received: from bombadil.mebtel.net (bombadil.mebtel.net [64.40.67.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F52143D45 for ; Sun, 21 Nov 2004 18:29:08 +0000 (GMT) (envelope-from dlt@mebtel.net) Received: from localhost (localhost [127.0.0.1]) by bombadil.mebtel.net (Postfix) with ESMTP id BFAE0208686 for ; Sun, 21 Nov 2004 13:29:07 -0500 (EST) Received: from bombadil.mebtel.net ([127.0.0.1]) by localhost (bombadil [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19453-08 for ; Sun, 21 Nov 2004 13:29:07 -0500 (EST) Received: from lorne.arm.org (66-79-79-177.dsl.mebtel.net [66.79.79.177]) by bombadil.mebtel.net (Postfix) with ESMTP id 4C48D208684 for ; Sun, 21 Nov 2004 13:29:07 -0500 (EST) Received: from lorne.arm.org (localhost [127.0.0.1]) by lorne.arm.org (8.13.1/8.12.9) with ESMTP id iALIT67p001027 for ; Sun, 21 Nov 2004 13:29:07 -0500 (EST) (envelope-from dlt@lorne.arm.org) Received: (from dlt@localhost) by lorne.arm.org (8.13.1/8.13.1/Submit) id iALIT6Vi001024; Sun, 21 Nov 2004 13:29:06 -0500 (EST) (envelope-from dlt) Date: Sun, 21 Nov 2004 13:29:06 -0500 (EST) Message-Id: <200411211829.iALIT6Vi001024@lorne.arm.org> From: Derek Tattersall To: current@FreeBSD.org X-Virus-Scanned: by amavisd-new at mebtel.net Subject: Error in write to named pipe X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: dlt@mebtel.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 18:29:08 -0000 I have an application that reads a file and writes some lines to a named pipe. It's just a sigmonster. On a current kernel/world from 11/11 the signature gets created and written to the pipe quite nicely. On a kernel/world from this morning (1600 GMT) the app fails to write the signature. The pipe and write portion of the ktrace is as follows: 929 signature CALL fork 929 signature RET fork 930/0x3a2 929 signature CALL exit(0) 931 signature RET open 3 931 signature CALL pipe 931 signature RET pipe 4 931 signature CALL fork 931 signature RET fork 959/0x3bf 931 signature CALL wait4(0x3bf,0,0,0) 931 signature RET wait4 959/0x3bf 931 signature CALL close(0x5) 931 signature RET close 0 931 signature CALL read(0x4,0xbfbfdbd4,0x200) 931 signature GIO fd 4 read 64 bytes "Don't abandon hope: your Tom Mix decoder ring arrives tomorrow. " 931 signature RET read 64/0x40 931 signature CALL close(0x4) 931 signature RET close 0 931 signature CALL __sysctl(0xbfbfd1f0,0x2,0xbfbfd630,0xbfbfd1ec,0,0) 931 signature RET __sysctl 0 931 signature CALL __sysctl(0xbfbfd1f0,0x2,0xbfbfd730,0xbfbfd1ec,0,0) 931 signature RET __sysctl 0 931 signature CALL __sysctl(0xbfbfd1f0,0x2,0xbfbfd830,0xbfbfd1ec,0,0) 931 signature RET __sysctl 0 931 signature CALL __sysctl(0xbfbfd1f0,0x2,0xbfbfd930,0xbfbfd1ec,0,0) 931 signature RET __sysctl 0 931 signature CALL __sysctl(0xbfbfd1f0,0x2,0xbfbfda30,0xbfbfd1ec,0,0) 931 signature RET __sysctl 0 931 signature CALL write(0x3,0xbfbfe3d4,0xad) 931 signature RET write -1 errno 45 Operation not supported 931 signature CALL close(0x3) 931 signature RET close 0 931 signature CALL nanosleep(0xbfbfdb38,0xbfbfdb30) 931 signature RET nanosleep 0 931 signature CALL access(0x804b220,0) 931 signature NAMI "/home/dlt/.signature" 931 signature RET access 0 931 signature CALL open(0x804b220,0x1,0x400) 931 signature NAMI "/home/dlt/.signature" Why would write suddenly be returning "operation not supported" when it's to a pipe? -- Derek Tattersall dlt@mebtel.net dlt666@yahoo.com From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 19:56:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58B9D16A4CE for ; Sun, 21 Nov 2004 19:56:28 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id CECE143D45 for ; Sun, 21 Nov 2004 19:56:27 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iALJuQ7W011820; Sun, 21 Nov 2004 13:56:26 -0600 (CST) (envelope-from dan) Date: Sun, 21 Nov 2004 13:56:26 -0600 From: Dan Nelson To: Wiktor Niesiobedzki Message-ID: <20041121195626.GA8805@dan.emsphone.com> References: <419CD314.80900@fer.hr> <20041118171012.GB19265@dan.emsphone.com> <20041120222325.GC17297@lb.tenfour> <20041121020745.GC94473@dan.emsphone.com> <20041121144905.GE3584@mail.evip.pl> <20041121174033.GA3019@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041121174033.GA3019@dan.emsphone.com> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: FreeBSD Current Users cc: Dick Davies Subject: Re: Replacing passwd? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 19:56:28 -0000 In the last episode (Nov 21), Dan Nelson said: > In the last episode (Nov 21), Wiktor Niesiobedzki said: > > I was playing with it today and removing errx function allows passwd > > to change the password, but the other problem I step on is: How to > > properly configure /etc/pam.d/passwd > > > > The configuration, which I have now is simply: > > password sufficient /usr/local/lib/pam_ldap.so > > password sufficient pam_unix.so no_warn try_first_pass nullok > > You probably don't need pam_unix in there at all, since there's no way > it'll work (no local passwd entry). I take that back; you do want it, so you can change root's password. But you need to make it "required", not sufficient. It's a quirk of how pam works, I think, but the last entry cannot be marked "sufficient". -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 20:04:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2EC216A4CE for ; Sun, 21 Nov 2004 20:04:15 +0000 (GMT) Received: from ms-smtp-04.nyroc.rr.com (ms-smtp-04.nyroc.rr.com [24.24.2.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3552E43D46 for ; Sun, 21 Nov 2004 20:04:15 +0000 (GMT) (envelope-from martines@rochester.rr.com) Received: from domain.crafts4life.com (roc-66-66-65-30.rochester.rr.com [66.66.65.30])iALK40OW001787; Sun, 21 Nov 2004 15:04:00 -0500 (EST) Received: from localhost.crafts4life.com (localhost [127.0.0.1]) by domain.crafts4life.com (Postfix) with ESMTP id 6518A3FC5; Sun, 21 Nov 2004 15:04:00 -0500 (EST) Received: from domain.crafts4life.com (localhost.crafts4life.com [127.0.0.1]) by localhost.crafts4life.com (AvMailGate-2.0.1.16) id 69662-5A2D7059; Sun, 21 Nov 2004 15:04:00 -0500 Received: from sauron.crafts4life.com (sauron.crafts4life.com [192.168.1.247]) by domain.crafts4life.com (Postfix) with ESMTP id E21393F9A; Sun, 21 Nov 2004 15:03:59 -0500 (EST) From: Eduard Martinescu To: =?ISO-8859-1?Q?S=F8ren?= Schmidt In-Reply-To: <41A0835B.9040404@DeepCore.dk> References: <20041119171236.DNZH20678.lakermmtao09.cox.net@smtp.east.cox.net> <41A0835B.9040404@DeepCore.dk> Content-Type: text/plain; charset=ISO-8859-1 Date: Sun, 21 Nov 2004 15:03:59 -0500 Message-Id: <1101067439.10224.3.camel@sauron.crafts4life.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 Content-Transfer-Encoding: quoted-printable X-AntiVirus: checked by AntiVir MailGate (version: 2.0.1.16; AVE: 6.28.0.18; VDF: 6.28.0.83; host: domain.crafts4life.com) X-Virus-Scanned: Symantec AntiVirus Scan Engine cc: m.kucenski@computer.org cc: freebsd-current@freebsd.org Subject: Re: ATAng support for reading from register on ATAREQUEST command? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 20:04:16 -0000 Matt/S=F8ren, I did send S=F8ren a patch to implement an optional READ parameter to the IOCTL, but he decided instead to ALWAYS read back the registers on any ATA_R_CONTROL command. Smartmontools has been updated to take this into account, and the next stable version should be more accurate. Ed On Sun, 2004-11-21 at 13:00 +0100, S=F8ren Schmidt wrote: > Matt Kucenski wrote: > > I am trying to develop a program that will allow modifications to the= Host Protected Area settings and one of the commands (READ NATIVE MAX AD= DRESS) returns the native max address back in the register (LBA high, low= , mid). > >=20 > > I have been looking at the smartmontools project for pointers on how = to write this code and according to that source, this is not possible yet= with ATAng. There is a comment in their code that another command (ATA_= CMD_READ_REG) patch has been submitted to ATAng, but it does not appear t= o have made it into any of the latest sources. > >=20 > > Can anyone offer any information on this? >=20 > The following patch returns the register values in the request you sent= =20 > through ioctl call. That should do the trick without any new calls.. >=20 >=20 > Plain text document attachment (ata-smart-patch) > Index: ata-all.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v > retrieving revision 1.233 > diff -u -r1.233 ata-all.c > --- ata-all.c 19 Oct 2004 20:13:38 -0000 1.233 > +++ ata-all.c 19 Nov 2004 18:59:55 -0000 > @@ -546,10 +546,10 @@ > bcopy(iocmd->u.request.u.atapi.ccb, request->u.atapi.ccb, 16); > } > else { > - request->u.ata.command =3D iocmd->u.request.u.ata.command; > - request->u.ata.feature =3D iocmd->u.request.u.ata.feature; > - request->u.ata.lba =3D iocmd->u.request.u.ata.lba; > - request->u.ata.count =3D iocmd->u.request.u.ata.count; > + request->u.ata.command =3D iocmd->u.request.u.ata.command; > + request->u.ata.feature =3D iocmd->u.request.u.ata.feature; > + request->u.ata.lba =3D iocmd->u.request.u.ata.lba; > + request->u.ata.count =3D iocmd->u.request.u.ata.count; > } > =20 > request->timeout =3D iocmd->u.request.timeout; > @@ -566,6 +566,10 @@ > =20 > ata_queue_request(request); > =20 > + iocmd->u.request.u.ata.command =3D request->u.ata.command; > + iocmd->u.request.u.ata.feature =3D request->u.ata.feature; > + iocmd->u.request.u.ata.lba =3D request->u.ata.lba; > + iocmd->u.request.u.ata.count =3D request->u.ata.count; > if (request->result) > iocmd->u.request.error =3D request->result; > else { > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" --=20 Eduard Martinescu From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 20:37:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8498716A4CE for ; Sun, 21 Nov 2004 20:37:38 +0000 (GMT) Received: from mail.evip.pl (mail.evip.com.pl [212.244.157.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B74943D49 for ; Sun, 21 Nov 2004 20:37:37 +0000 (GMT) (envelope-from w@evip.pl) Received: from drwebc by mail.evip.pl with drweb-scanned (Exim 4.22) id 1CVySj-000OtU-U4; Sun, 21 Nov 2004 21:37:33 +0100 Received: from w by mail.evip.pl with local (Exim 4.22) id 1CVySj-000OtO-Qh; Sun, 21 Nov 2004 21:37:33 +0100 Date: Sun, 21 Nov 2004 21:37:33 +0100 From: Wiktor Niesiobedzki To: Dan Nelson Message-ID: <20041121203733.GF3584@mail.evip.pl> References: <419CD314.80900@fer.hr> <20041118171012.GB19265@dan.emsphone.com> <20041120222325.GC17297@lb.tenfour> <20041121020745.GC94473@dan.emsphone.com> <20041121144905.GE3584@mail.evip.pl> <20041121174033.GA3019@dan.emsphone.com> <20041121195626.GA8805@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041121195626.GA8805@dan.emsphone.com> User-Agent: Mutt/1.5.6i cc: FreeBSD Current Users Subject: Re: Replacing passwd? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 20:37:38 -0000 On Sun, Nov 21, 2004 at 01:56:26PM -0600, Dan Nelson wrote: > In the last episode (Nov 21), Dan Nelson said: > > In the last episode (Nov 21), Wiktor Niesiobedzki said: > > > I was playing with it today and removing errx function allows passwd > > > to change the password, but the other problem I step on is: How to > > > properly configure /etc/pam.d/passwd > > > > > > The configuration, which I have now is simply: > > > password sufficient /usr/local/lib/pam_ldap.so > > > password sufficient pam_unix.so no_warn try_first_pass nullok > > > > You probably don't need pam_unix in there at all, since there's no way > > it'll work (no local passwd entry). > > I take that back; you do want it, so you can change root's password. > But you need to make it "required", not sufficient. It's a quirk of > how pam works, I think, but the last entry cannot be marked > "sufficient". That was my first try, but then I got: % ./passwd Enter login(LDAP) password: passwd: sorry: pam_chauthtok - permission denied (The error message from passwd I added by myself in pam_check macro, so in case of pam_err == PAM_AUTH_ERR || pam_err == PAM_PERM_DENIED || pam_err == PAM_AUTHTOK_RECOVERY_ERR it also prints the func, as well as error message) Is this a bug in pam? (After checking token in module marked sufficient and returing with no error, we go to required module?). In this configuration I just don't quite follow, what happens, because as far as I have debuged pam_ldap.so, it returns from pam_sm_chauthtok with no error... Cheers, Wiktor Niesiobedzki From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 22:45:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3025B16A4CE for ; Sun, 21 Nov 2004 22:45:03 +0000 (GMT) Received: from corwin.easynet.fr (smarthost160.mail.easynet.fr [212.180.1.160]) by mx1.FreeBSD.org (Postfix) with ESMTP id 205AF43D49 for ; Sun, 21 Nov 2004 22:45:02 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from [212.180.127.72] (helo=tatooine.tataz.chchile.org) by corwin.easynet.fr with esmtp (Exim 4.34) id 1CW0S1-0007rV-Cd; Sun, 21 Nov 2004 23:44:58 +0100 Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 0AC1B408E; Sun, 21 Nov 2004 23:44:47 +0100 (CET) Date: Sun, 21 Nov 2004 23:44:46 +0100 From: Jeremie Le Hen To: "Bjoern A. Zeeb" Message-ID: <20041121224446.GT69710@obiwan.tataz.chchile.org> References: <20041119114233.C43B.SHINO@fornext.org> <20041119185315.C43D.SHINO@fornext.org> <20041119120102.GM69710@obiwan.tataz.chchile.org> <20041121020050.GB94473@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i X-Broken-Reverse-DNS: no host name found for IP address 212.180.127.72 cc: Jeremie Le Hen cc: freebsd-current@freebsd.org cc: Dan Nelson cc: Shunsuke SHINOMIYA Subject: Re: interrupt moderation for if_* [was: serious networking (em) ...] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 22:45:03 -0000 > > > when thinking about this could there be some "global" way for > > > interrupt moderation; For if_sk there is this PR: > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/41220 > > > > > > something 'unique' to all NIC drivers would be good I guess ? > > > > You need NIC support for it, just like checksum offloading. And other > > good example;) We do have [-,]{rxcsum, txcsum} in ifconfig for > turning this on/off if supported. > > What I meant is to have common names for the interface (sysctl) for > all NICs supporting this - "on grep finds all" and not to start > home-brewed names for each driver. > > There might be some different names needed because int_delay, > int_throttle_ceil or sk_interrupt_mod might or might not achieve the > same but if they do names should be same. This is a great idea, it would be very user-friendly to have such a flag in ifconfig(8) but there is a non-trivial problem to achieve this. Although the Interrupt Moderation implementation among theses chipsets is based on the same principle, the way we can control its behaviour diverges very much. o sk(4) cards have this feature, but according to the product white paper [1] and the Linux sk98lin(4) driver manual page [2], there are two Interrupt Moderation modes (the static one and dynamic one), but we may only adjust the maximum interrupts per seconds. Note that, as far as I understood, both the "Moderation" and the "IntsPerSec" may be set at run-time. o fxp(4) cards have what is called "CPU cycle saver" which also gathers multiple packets before generating an interrupt. There are two parameters to control the behaviour of this feature : maximum delay and maximum number of packets to be bundled before generating the interrupt [3]. These parameters may be changed only by loading a microcode into the chip, run-time modification is impossible. o em(4) have the most flexible configuration scheme for Interrupt Moderation, IHMO. You may set the absolute timer and the packet timer as well as the interrupt throttle ceil which is the origin of this subthread [4]. I didn't manage to know whether these may be set at run-time, but I assume it's possible. What I tried to demonstrate is that it does not seem to be possible to find a common denominator for configurable parameters of this feature. Furthermore it appears that some chips may be configured at run-time while others requires uploading a microcode, it would be harm to restrict the formers to fit with the latters capacities. [1] http://www.syskonnect.com/syskonnect/technology/SK-NET_GE.PDF (see section 3.2.1) [2] http://www.frech.ch/man/man4/sk98lin.4.html (see "Moderation" and "IntsPerSec" parameters) [3] http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/fxp/if_fxpvar.h?rev=1.32&content-type=text/x-cvsweb-markup (see TUNABLE_INT_DELAY and TUNABLE_BUNDLE_MAX defines) [4] http://www.intel.com/design/network/applnots/ap450.pdf Best regards, -- Jeremie Le Hen jeremie@le-hen.org From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 23:41:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E39C16A4CE for ; Sun, 21 Nov 2004 23:41:30 +0000 (GMT) Received: from mxsf11.cluster1.charter.net (mxsf11.cluster1.charter.net [209.225.28.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D43E43D2D for ; Sun, 21 Nov 2004 23:41:27 +0000 (GMT) (envelope-from wardcinnamon@charter.net) Received: from mxip18.cluster1.charter.net (mxip18a.cluster1.charter.net [209.225.28.148])iALNfQpO016247 for ; Sun, 21 Nov 2004 18:41:26 -0500 Received: from ky-24-159-159-183.midtn.chartertn.net (HELO 192.168.1.100) (24.159.159.183) by mxip18.cluster1.charter.net with ESMTP; 21 Nov 2004 18:41:25 -0500 X-Ironport-AV: i="3.87,103,1099285200"; d="scan'208"; a="578460309:sNHT16228476" From: Ward Cinnamon To: freebsd-current@freebsd.org In-Reply-To: <20041121120114.5BA6B16A4F2@hub.freebsd.org> References: <20041121120114.5BA6B16A4F2@hub.freebsd.org> Content-Type: text/plain Date: Sun, 21 Nov 2004 18:43:34 -0500 Message-Id: <1101080614.5334.0.camel@linux> Mime-Version: 1.0 X-Mailer: Evolution 2.0.1 Content-Transfer-Encoding: 7bit Subject: Re: freebsd-current Digest, Vol 79, Issue 14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 23:41:30 -0000 Unsubscribe me. On Sun, 2004-11-21 at 12:01 +0000, freebsd-current-request@freebsd.org wrote: > Send freebsd-current mailing list submissions to > freebsd-current@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-current > or, via email, send a message with subject or body 'help' to > freebsd-current-request@freebsd.org > > You can reach the person managing the list at > freebsd-current-owner@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-current digest..." > > > Today's Topics: > > 1. Giantless VFS. (Jeff Roberson) > 2. Floppy Boot ?? (Ege M?kan) > 3. Re: Floppy Boot ?? (Lowell Gilbert) > 4. Re: Replacing passwd? (Dick Davies) > 5. Re: Floppy Boot ?? (Michael C. Shultz) > 6. Re: Problem with HP DL380 (M. Warner Losh) > 7. Re: Problem with HP DL380 (Wilkinson, Alex) > 8. Re: interrupt moderation for if_* [was: serious networking > (em) ...] (Dan Nelson) > 9. Re: Replacing passwd? (Dan Nelson) > 10. Re: ATAng support for reading from register on ATAREQUEST > command? (S?ren Schmidt) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 20 Nov 2004 00:24:10 -0500 (EST) > From: Jeff Roberson > Subject: Giantless VFS. > To: current@freebsd.org > Message-ID: <20041120000743.G18094@mail.chesapeake.net> > Content-Type: TEXT/PLAIN; charset=US-ASCII > > I have a patch that I would like people to test and review. It's > available here: > > http://www.chesapeake.net/~jroberson/smpffs.diff > > The short description: > This patch removes Giant from the read(), write(), and fstat() syscalls, > as well as page faults, and bufdone (io interrupts) when using FFS. It > adds a considerable amount of locking to FFS and softupdates. You may > also use non ffs filesystems concurrently, but they will be protected by > Giant. If you are using quotas you should not yet run this patch. I have > done some buildworlds, but any heavy filesystem activity would be > appreciated. > > Long description: > There is now a per mount-point mutex in struct ufsmount that covers ffs's > struct fs related allocation routines. The rest of the filesystem was > already covered by the buffer locks on cgs, indirs, etc, as well as a few > mutexes that were already in place. I made great attempts to minimize the > number of lock operations for the common cases which resulted in a couple > of functions which may be entered with the UFS lock held, but return > without it held. Where this is not already done, it will be documented in > comments. > > The softupdate lk lock has been turned into a mutex, and it now protects > all global worklists, inode and page dep hash buckets, etc. > interlocked_sleep() is gone now that BUF_LOCK() and msleep() take > interlock arguments. getdirtybuf() has been slightly changed to solve > some sleep related races that I disucssed with Kirk. For now there is a > single softupdates mutex, but eventually it will be made per-mountpoint > and potentially merged with the ufsmount lock. > > On the infrastructure side, the buffer cache was locked some time ago, and > now the vm is safe to run without Giant, so there are simply a lot of > removed GIANT_REQUIRED lines. I added some locking to vn_start_write() > and friends, and made some changes for LORs there. There is a pair of new > macros called VFS_(UN)LOCK_GIANT(mp) which inspects a new flag on the > mount-point to determine if we have to acquire giant. This is done very > early in the syscall path before we call any VOPs. The mountpoints should > be safe to inspect as we always own a reference to the vnode in the cases > that I have unwound for now. > > Cheers, > Jeff > > ------------------------------ > > Message: 2 > Date: Sat, 20 Nov 2004 23:11:24 +0200 > From: Ege M?kan > Subject: Floppy Boot ?? > To: > Message-ID: <003801c4cf45$86860680$9590aec3@redbaron> > Content-Type: text/plain; charset="iso-8859-9" > > Hi, > > Is there way to install FreeBSD 5.3 without install boot loader to HDD but with creating boot floppies to start your system which is installed on your HDD ?? > > Thanx > > Ege. > > ------------------------------ > > Message: 3 > Date: 20 Nov 2004 17:13:13 -0500 > From: Lowell Gilbert > Subject: Re: Floppy Boot ?? > To: Ege M?kan > Cc: freebsd-current@freebsd.org > Message-ID: <444qjkkw3q.fsf@be-well.ilk.org> > Content-Type: text/plain; charset=iso-8859-1 > > Ege Mkan writes: > > > Is there way to install FreeBSD 5.3 without install boot loader to HDD but with creating boot floppies to start your system which is installed on your HDD ?? > > This question would be more appropriate on freebsd-questions, but the > answer would be the same on a -CURRENT system. I think you can just > take the installation boot floppy and set up the boot.config file to > boot the appropriate disk and the appropriate kernel. > > There are many "boot manager" programs that can be installed to > floppies, as well. > > ------------------------------ > > Message: 4 > Date: Sat, 20 Nov 2004 22:23:25 +0000 > From: Dick Davies > Subject: Re: Replacing passwd? > To: Dan Nelson > Cc: FreeBSD Current Users > Message-ID: <20041120222325.GC17297@lb.tenfour> > Content-Type: text/plain; charset=us-ascii > > * Dan Nelson [1110 17:10]: > > In the last episode (Nov 18), Ivan Voras said: > > > I've setup pam_ldap and nss_ldap and samba3 and smbldap, and it works > > > fine, but it would be nice to replace /usr/bin/passwd with > > > smbldap-passwd (which changes both NTLM and Unix password fields in > > > LDAP, while passwd is unaware of LDAP, at least according to man > > > page). Is there a clean way of doing it so I don't have to replace > > > it by hand after each installworld? > > > > passwd just uses PAM to set passwords > > When did that come in? I can't get passwd(1) to change an ldap password, I get: > > rasputnik@eris:rasputnik$ passwd > passwd: Sorry, `passwd' can only change passwords for local or NIS users. > rasputnik@eris:rasputnik$ uname -a > FreeBSD eris 5.3-STABLE FreeBSD 5.3-STABLE #4: Mon Oct 25 18:03:11 BST 2004 root@eris:/usr/obj/usr/src/sys/ERIS i386 > rasputnik@eris:rasputnik$ > > - this is an nss_ldap nsswitched account, logged in over ssh (pam_ldap auth). > > -- > This must be Thursday. I never could get the hang of Thursdays. - Arthur Dent > Rasputin :: Jack of All Trades - Master of Nuns > > ------------------------------ > > Message: 5 > Date: Sat, 20 Nov 2004 14:23:20 -0800 > From: "Michael C. Shultz" > Subject: Re: Floppy Boot ?? > To: freebsd-current@freebsd.org > Message-ID: <200411201423.20426.ringworm@inbox.lv> > Content-Type: text/plain; charset="iso-8859-9" > > On Saturday 20 November 2004 01:11 pm, Ege Mkan wrote: > > Hi, > > > > Is there way to install FreeBSD 5.3 without install boot loader to > > HDD but with creating boot floppies to start your system which is > > installed on your HDD ?? > > > > Thanx > > > > Ege. > > Take a look at /usr/ports/sysutils/grub. It lets you boot a variety > of OS's using a floppy as a bootloader. > > -Mike > > ------------------------------ > > Message: 6 > Date: Sat, 20 Nov 2004 17:27:38 -0700 (MST) > From: "M. Warner Losh" > Subject: Re: Problem with HP DL380 > To: le@FreeBSD.org > Cc: freebsd-current@FreeBSD.org > Message-ID: <20041120.172738.38711956.imp@bsdimp.com> > Content-Type: Text/Plain; charset=us-ascii > > In message: <20041120104224.E566@korben.prv.univie.ac.at> > Lukas Ertl writes: > : On Sat, 20 Nov 2004, M. Warner Losh wrote: > : > : > : Setting hw.pci.do_powerstate=0 in /boot/loader.conf fixes this problem. > : > > : > Dang. I missed the earlier part of this thread. You shouldn't need > : > to do this if I coded things up right. But, alas, you do. Can you > : > send me the details? > : > : No, I think you did everything right. If I understand it correctly, then > : hw.pci.do_powerstate puts a device into C3 state if no driver attaches. > : That's just what happens here. That iLO service processor of the DL380s > : shows up as normal PCI device, but exports the console to the network even > : without specific driver (as there is none for FreeBSD), so that it works > : independent of the OS. > : > : So, since there is no driver, the device gets powered down as soon as the > : kernel initializes its ACPI parts, and then the iLO console stops working. > > It may be the case that the base device class needs a 'dummy' driver > to prevent things like this from happening. We have a hack in the > code right now for displays until the situation there is straightened > out. > > Warner > > ------------------------------ > > Message: 7 > Date: Sun, 21 Nov 2004 11:10:02 +1030 > From: "Wilkinson, Alex" > Subject: Re: Problem with HP DL380 > To: freebsd-current@freebsd.org > Message-ID: <20041121004001.GB7395@squash.dsto.defence.gov.au> > Content-Type: text/plain; charset="us-ascii" > > what is meant by 'C3 state' ? > > - aW > > > 0n Sat, Nov 20, 2004 at 10:46:25AM +0100, Lukas Ertl wrote: > > > On Sat, 20 Nov 2004, M. Warner Losh wrote: > > > > >: Setting hw.pci.do_powerstate=0 in /boot/loader.conf fixes this problem. > > > > > >Dang. I missed the earlier part of this thread. You shouldn't need > > >to do this if I coded things up right. But, alas, you do. Can you > > >send me the details? > > > > No, I think you did everything right. If I understand it correctly, then > > hw.pci.do_powerstate puts a device into C3 state if no driver attaches. > > That's just what happens here. That iLO service processor of the DL380s > > shows up as normal PCI device, but exports the console to the network even > > without specific driver (as there is none for FreeBSD), so that it works > > independent of the OS. > > > > So, since there is no driver, the device gets powered down as soon as the > > kernel initializes its ACPI parts, and then the iLO console stops working. > > > > cheers, > > le > > > > -- > > Lukas Ertl http://homepage.univie.ac.at/l.ertl/ > > le@FreeBSD.org http://people.freebsd.org/~le/ > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > ------------------------------ > > Message: 8 > Date: Sat, 20 Nov 2004 20:00:50 -0600 > From: Dan Nelson > Subject: Re: interrupt moderation for if_* [was: serious networking > (em) ...] > To: "Bjoern A. Zeeb" > Cc: Shunsuke SHINOMIYA > Message-ID: <20041121020050.GB94473@dan.emsphone.com> > Content-Type: text/plain; charset=us-ascii > > In the last episode (Nov 20), Bjoern A. Zeeb said: > > On Fri, 19 Nov 2004, Jeremie Le Hen wrote: > > > > Hi, Jeremie, how is this? To disable Interrupt Moderation, > > > > sysctl hw.em?.int_throttle_valve=0. > > > > > > Great, I would have called it "int_throttle_ceil", but that's a > > > detail and my opinion is totally subjective. > > > > > > > However, because this patch is just made now, it is not fully tested. > > > > > > I'll give it a try this weekend although I won't be able to make > > > performance mesurements. > > > > when thinking about this could there be some "global" way for > > interrupt moderation; For if_sk there is this PR: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/41220 > > > > something 'unique' to all NIC drivers would be good I guess ? > > You need NIC support for it, just like checksum offloading. And other > drivers offer more sysctls; fxp lets you choose the maximum delay and > maximum packets to hold before firing an interrupt. > > -- > Dan Nelson > dnelson@allantgroup.com > > ------------------------------ > > Message: 9 > Date: Sat, 20 Nov 2004 20:07:45 -0600 > From: Dan Nelson > Subject: Re: Replacing passwd? > To: Dick Davies > Cc: FreeBSD Current Users > Message-ID: <20041121020745.GC94473@dan.emsphone.com> > Content-Type: text/plain; charset=us-ascii > > In the last episode (Nov 20), Dick Davies said: > > * Dan Nelson [1110 17:10]: > > > In the last episode (Nov 18), Ivan Voras said: > > > > I've setup pam_ldap and nss_ldap and samba3 and smbldap, and it works > > > > fine, but it would be nice to replace /usr/bin/passwd with > > > > smbldap-passwd (which changes both NTLM and Unix password fields in > > > > LDAP, while passwd is unaware of LDAP, at least according to man > > > > page). Is there a clean way of doing it so I don't have to replace > > > > it by hand after each installworld? > > > > > > passwd just uses PAM to set passwords > > > > When did that come in? I can't get passwd(1) to change an ldap password, I get: > > > > rasputnik@eris:rasputnik$ passwd > > passwd: Sorry, `passwd' can only change passwords for local or NIS users. > > rasputnik@eris:rasputnik$ uname -a > > FreeBSD eris 5.3-STABLE FreeBSD 5.3-STABLE #4: Mon Oct 25 18:03:11 BST 2004 root@eris:/usr/obj/usr/src/sys/ERIS i386 > > rasputnik@eris:rasputnik$ > > > > - this is an nss_ldap nsswitched account, logged in over ssh (pam_ldap auth). > > Weird. There's definitely a lot of PAM code in passwd.c. What happens > if you comment out the errx() function that prints that error (line > 124)? > > -- > Dan Nelson > dnelson@allantgroup.com > > ------------------------------ > > Message: 10 > Date: Sun, 21 Nov 2004 13:00:27 +0100 > From: S?ren Schmidt > Subject: Re: ATAng support for reading from register on ATAREQUEST > command? > To: m.kucenski@computer.org > Cc: freebsd-current@freebsd.org > Message-ID: <41A0835B.9040404@DeepCore.dk> > Content-Type: text/plain; charset="iso-8859-1" > > Matt Kucenski wrote: > > I am trying to develop a program that will allow modifications to the Host Protected Area settings and one of the commands (READ NATIVE MAX ADDRESS) returns the native max address back in the register (LBA high, low, mid). > > > > I have been looking at the smartmontools project for pointers on how to write this code and according to that source, this is not possible yet with ATAng. There is a comment in their code that another command (ATA_CMD_READ_REG) patch has been submitted to ATAng, but it does not appear to have made it into any of the latest sources. > > > > Can anyone offer any information on this? > > The following patch returns the register values in the request you sent > through ioctl call. That should do the trick without any new calls.. > > From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 00:33:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E16216A4CE; Mon, 22 Nov 2004 00:33:11 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23E1743D45; Mon, 22 Nov 2004 00:33:11 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iAM0XAwm025777; Sun, 21 Nov 2004 19:33:10 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id iAM0X9pv080164; Sun, 21 Nov 2004 19:33:09 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id A82897306E; Sun, 21 Nov 2004 19:33:09 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041122003309.A82897306E@freebsd-current.sentex.ca> Date: Sun, 21 Nov 2004 19:33:09 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner2 X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner2 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [releng_5 tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 00:33:11 -0000 TB --- 2004-11-21 23:14:21 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-21 23:14:21 - starting RELENG_5 tinderbox run for amd64/amd64 TB --- 2004-11-21 23:14:21 - checking out the source tree TB --- 2004-11-21 23:14:21 - cd /home/tinderbox/RELENG_5/amd64/amd64 TB --- 2004-11-21 23:14:21 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2004-11-21 23:23:22 - building world (CFLAGS=-O -pipe) TB --- 2004-11-21 23:23:22 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2004-11-21 23:23:22 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-11-22 00:15:22 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2004-11-22 00:15:22 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2004-11-22 00:15:22 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Mon Nov 22 00:15:22 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Mon Nov 22 00:24:29 UTC 2004 TB --- 2004-11-22 00:24:29 - generating LINT kernel config TB --- 2004-11-22 00:24:29 - cd /home/tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/conf TB --- 2004-11-22 00:24:29 - /usr/bin/make -B LINT TB --- 2004-11-22 00:24:29 - building LINT kernel (COPTFLAGS=-O -pipe) TB --- 2004-11-22 00:24:29 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2004-11-22 00:24:29 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Nov 22 00:24:29 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/amd64/busdma_machdep.c: In function `bus_dmamap_load': /tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/amd64/busdma_machdep.c:720: error: `KTR_BUSDMA' undeclared (first use in this function) /tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/amd64/busdma_machdep.c: In function `bus_dmamap_load_mbuf': /tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/amd64/busdma_machdep.c:777: error: `KTR_BUSDMA' undeclared (first use in this function) /tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/amd64/busdma_machdep.c: In function `bus_dmamap_load_uio': /tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/amd64/busdma_machdep.c:837: error: `KTR_BUSDMA' undeclared (first use in this function) /tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/amd64/busdma_machdep.c: In function `_bus_dmamap_sync': /tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/amd64/busdma_machdep.c:868: error: `KTR_BUSDMA' undeclared (first use in this function) *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/obj/amd64/tinderbox/RELENG_5/amd64/amd64/src/sys/LINT. *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/src. TB --- 2004-11-22 00:33:09 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-22 00:33:09 - ERROR: failed to build lint kernel TB --- 2004-11-22 00:33:09 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 00:38:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7426D16A4CE; Mon, 22 Nov 2004 00:38:12 +0000 (GMT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2772143D2F; Mon, 22 Nov 2004 00:38:12 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) iAM0c8cW052590; Sun, 21 Nov 2004 16:38:08 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.9p2/8.12.9/Submit) id iAM0c7JQ052589; Sun, 21 Nov 2004 16:38:07 -0800 (PST) (envelope-from dillon) Date: Sun, 21 Nov 2004 16:38:07 -0800 (PST) From: Matthew Dillon Message-Id: <200411220038.iAM0c7JQ052589@apollo.backplane.com> To: Shunsuke SHINOMIYA References: <20041119185315.C43D.SHINO@fornext.org> <20041121205158.45CE.SHINO@fornext.org> cc: freebsd-stable@freebsd.org cc: freebsd-current@freebsd.org cc: Jeremie Le Hen Subject: Re: Re[2]: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 00:38:12 -0000 : I did simple benchmark at some settings. : : I used two boxes which are single Xeon 2.4GHz with on-boarded em. : I measured a TCP throughput by iperf. : : These results show that the throughput of TCP increased if Interrupt :Moderation is turned OFF. At least, adjusting these parameters affected :TCP performance. Other appropriate combination of parameter may exist. Very interesting, but the only reason you get lower results is simply because the TCP window is not big enough. That's it. 8000 ints/sec = ~15KB of backlogged traffic. x 2 (sender, receiver) Multiply by two (both the sender's reception of acks and the receiver's reception of data) and you get ~30KB. This is awefully close to the default 32.5KB window size that iperf uses. Other then window sizing issues I can think of no rational reason why throughput would be lower. Can you? And, in fact, when I do the same tests on DragonFly and play with the interrupt throttle rate I get nearly the results I expect. * Shuttle Athlon 64 3200+ box, EM card in 32 bit PCI slot * 2 machines connected through a GiGE switch * All other hw.em0 delays set to 0 on both sides * throttle settings set on both sides * -w option set on iperf client AND server for 63.5KB window * software interrupt throttling has been turned off for these tests throttle result result freq (32.5KB win) (63.5KB win) (default) -------- -------------- ----------- maxrate 481 MBit/s 533 MBit/s (not sure what's going on here) 120000 518 MBit/s 558 MBit/s (not sure what's going on here) 100000 613 MBit/s 667 MBit/s (not sure what's going on here) 70000 679 MBit/s 691 MBit/s 60000 668 MBit/s 694 MBit/s 50000 678 MBit/s 684 MBit/s 40000 694 MBit/s 696 MBit/s 30000 694 MBit/s 696 MBit/s 20000 698 MBit/s 703 MBit/s 10000 707 MBit/s 716 MBit/s 9000 708 MBit/s 716 MBit/s 8000 710 MBit/s 717 MBit/s <--- drop off pt 32.5KB win 7000 683 MBit/s 716 MBit/s 6000 680 MBit/s 720 MBit/s 5000 652 MBit/s 718 MBit/s <--- drop off pt 63.5KB win 4000 555 Mbit/s 695 MBit/s 3000 522 MBit/s 533 MBit/s <--- GiGE throttling likely 2000 449 MBit/s 384 MBit/s (256 ring descriptors = 1000 260 MBit/s 193 MBit/s 2500 hz minimum) Unless you are in a situation where you need to route small packets flying around a cluster where low latency is important, it doesn't really make any sense to turn off interrupt throttling. It might make sense to change the default from 8000 to 10000 to handle typical default TCP window sizes (at least in a LAN situation), but it certainly should not be turned off. I got some weird results when I increased the frequency past 100KHz, and when I turned throttling off entirely. I'm not sure why. Maybe setting the ITR register to 0 is a bad idea. If I set it to 1 (i.e. 3906250 Hz) then I get 625 MBit/s. Setting the ITR to 1 (i.e. 256ns delay) should amount to the same thing as setting it to 0 but it doesn't. Very odd. The maximum interrupt rate as reported by systat is only ~46000 ints/sec so all the values above 50KHz should read about the same... and they do until we hit around 100Khz (10uS delay). Then everything goes to hell in a handbasket. Conclusion: 10000 hz would probably be a better default then 8000 hz. -Matt Matthew Dillon From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 01:54:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B52816A4CE; Mon, 22 Nov 2004 01:54:40 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 108E843D1D; Mon, 22 Nov 2004 01:54:40 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iAM1sdDu041402; Sun, 21 Nov 2004 20:54:39 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.12.11/8.12.11) with ESMTP id iAM1sdqE031982; Sun, 21 Nov 2004 20:54:39 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 120367306E; Sun, 21 Nov 2004 20:54:39 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041122015439.120367306E@freebsd-current.sentex.ca> Date: Sun, 21 Nov 2004 20:54:39 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner2 X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on avscan2 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [releng_5 tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 01:54:40 -0000 TB --- 2004-11-22 00:33:09 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-22 00:33:09 - starting RELENG_5 tinderbox run for i386/i386 TB --- 2004-11-22 00:33:09 - checking out the source tree TB --- 2004-11-22 00:33:09 - cd /home/tinderbox/RELENG_5/i386/i386 TB --- 2004-11-22 00:33:09 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2004-11-22 00:42:06 - building world (CFLAGS=-O -pipe) TB --- 2004-11-22 00:42:06 - cd /home/tinderbox/RELENG_5/i386/i386/src TB --- 2004-11-22 00:42:06 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-11-22 01:33:01 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2004-11-22 01:33:01 - cd /home/tinderbox/RELENG_5/i386/i386/src TB --- 2004-11-22 01:33:01 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Mon Nov 22 01:33:01 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Mon Nov 22 01:44:29 UTC 2004 TB --- 2004-11-22 01:44:29 - generating LINT kernel config TB --- 2004-11-22 01:44:29 - cd /home/tinderbox/RELENG_5/i386/i386/src/sys/i386/conf TB --- 2004-11-22 01:44:29 - /usr/bin/make -B LINT TB --- 2004-11-22 01:44:29 - building LINT kernel (COPTFLAGS=-O -pipe) TB --- 2004-11-22 01:44:29 - cd /home/tinderbox/RELENG_5/i386/i386/src TB --- 2004-11-22 01:44:29 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Nov 22 01:44:29 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /tinderbox/RELENG_5/i386/i386/src/sys/i386/i386/busdma_machdep.c: In function `bus_dmamap_load': /tinderbox/RELENG_5/i386/i386/src/sys/i386/i386/busdma_machdep.c:720: error: `KTR_BUSDMA' undeclared (first use in this function) /tinderbox/RELENG_5/i386/i386/src/sys/i386/i386/busdma_machdep.c: In function `bus_dmamap_load_mbuf': /tinderbox/RELENG_5/i386/i386/src/sys/i386/i386/busdma_machdep.c:777: error: `KTR_BUSDMA' undeclared (first use in this function) /tinderbox/RELENG_5/i386/i386/src/sys/i386/i386/busdma_machdep.c: In function `bus_dmamap_load_uio': /tinderbox/RELENG_5/i386/i386/src/sys/i386/i386/busdma_machdep.c:837: error: `KTR_BUSDMA' undeclared (first use in this function) /tinderbox/RELENG_5/i386/i386/src/sys/i386/i386/busdma_machdep.c: In function `_bus_dmamap_sync': /tinderbox/RELENG_5/i386/i386/src/sys/i386/i386/busdma_machdep.c:868: error: `KTR_BUSDMA' undeclared (first use in this function) *** Error code 1 Stop in /tinderbox/RELENG_5/i386/i386/obj/tinderbox/RELENG_5/i386/i386/src/sys/LINT. *** Error code 1 Stop in /tinderbox/RELENG_5/i386/i386/src. *** Error code 1 Stop in /tinderbox/RELENG_5/i386/i386/src. TB --- 2004-11-22 01:54:38 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-22 01:54:38 - ERROR: failed to build lint kernel TB --- 2004-11-22 01:54:38 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 03:12:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D13916A4CE; Mon, 22 Nov 2004 03:12:57 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC70043D31; Mon, 22 Nov 2004 03:12:56 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iAM3CtGS054777; Sun, 21 Nov 2004 22:12:55 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id iAM3Cs9G037591; Sun, 21 Nov 2004 22:12:54 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 427357306E; Sun, 21 Nov 2004 22:12:55 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041122031255.427357306E@freebsd-current.sentex.ca> Date: Sun, 21 Nov 2004 22:12:55 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner2 X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner2 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [releng_5 tinderbox] failure on i386/pc98 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 03:12:57 -0000 TB --- 2004-11-22 01:54:39 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-22 01:54:39 - starting RELENG_5 tinderbox run for i386/pc98 TB --- 2004-11-22 01:54:39 - checking out the source tree TB --- 2004-11-22 01:54:39 - cd /home/tinderbox/RELENG_5/i386/pc98 TB --- 2004-11-22 01:54:39 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2004-11-22 02:03:31 - building world (CFLAGS=-O -pipe) TB --- 2004-11-22 02:03:31 - cd /home/tinderbox/RELENG_5/i386/pc98/src TB --- 2004-11-22 02:03:31 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-11-22 02:54:46 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2004-11-22 02:54:46 - cd /home/tinderbox/RELENG_5/i386/pc98/src TB --- 2004-11-22 02:54:46 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Mon Nov 22 02:54:47 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Mon Nov 22 03:04:26 UTC 2004 TB --- 2004-11-22 03:04:26 - generating LINT kernel config TB --- 2004-11-22 03:04:26 - cd /home/tinderbox/RELENG_5/i386/pc98/src/sys/pc98/conf TB --- 2004-11-22 03:04:26 - /usr/bin/make -B LINT TB --- 2004-11-22 03:04:26 - building LINT kernel (COPTFLAGS=-O -pipe) TB --- 2004-11-22 03:04:26 - cd /home/tinderbox/RELENG_5/i386/pc98/src TB --- 2004-11-22 03:04:26 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Nov 22 03:04:26 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /tinderbox/RELENG_5/i386/pc98/src/sys/i386/i386/busdma_machdep.c: In function `bus_dmamap_load': /tinderbox/RELENG_5/i386/pc98/src/sys/i386/i386/busdma_machdep.c:720: error: `KTR_BUSDMA' undeclared (first use in this function) /tinderbox/RELENG_5/i386/pc98/src/sys/i386/i386/busdma_machdep.c: In function `bus_dmamap_load_mbuf': /tinderbox/RELENG_5/i386/pc98/src/sys/i386/i386/busdma_machdep.c:777: error: `KTR_BUSDMA' undeclared (first use in this function) /tinderbox/RELENG_5/i386/pc98/src/sys/i386/i386/busdma_machdep.c: In function `bus_dmamap_load_uio': /tinderbox/RELENG_5/i386/pc98/src/sys/i386/i386/busdma_machdep.c:837: error: `KTR_BUSDMA' undeclared (first use in this function) /tinderbox/RELENG_5/i386/pc98/src/sys/i386/i386/busdma_machdep.c: In function `_bus_dmamap_sync': /tinderbox/RELENG_5/i386/pc98/src/sys/i386/i386/busdma_machdep.c:868: error: `KTR_BUSDMA' undeclared (first use in this function) *** Error code 1 Stop in /tinderbox/RELENG_5/i386/pc98/obj/pc98/tinderbox/RELENG_5/i386/pc98/src/sys/LINT. *** Error code 1 Stop in /tinderbox/RELENG_5/i386/pc98/src. *** Error code 1 Stop in /tinderbox/RELENG_5/i386/pc98/src. TB --- 2004-11-22 03:12:55 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-22 03:12:55 - ERROR: failed to build lint kernel TB --- 2004-11-22 03:12:55 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 03:37:14 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42A2F16A4CE; Mon, 22 Nov 2004 03:37:14 +0000 (GMT) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70F9343D49; Mon, 22 Nov 2004 03:37:11 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.43 (FreeBSD)) id 1CW50x-000EPE-CM; Mon, 22 Nov 2004 11:37:19 +0800 Message-Id: <6.2.0.14.2.20041122110822.0305eeb0@202.179.0.80> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Mon, 22 Nov 2004 11:36:55 +0800 To: freebsd-current@freebsd.org From: Ganbold Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: mhunter@ack.Berkeley.EDU cc: scottl@freebsd.org cc: cguttesen@yahoo.dk Subject: Page fault in FreeBSD 5.3 on IBM e325, Dual AMD64 2.2GHz, 4GB RAM, ServeRAID 6M X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 03:37:14 -0000 Hi all, I got following page fault in FreeBSD 5.3 on IBM e325 with Dual AMD64 2.2GHz, 4GB RAM and ServeRAID 6M SCSI controller. FreeBSD publicc.ub.mng.net 5.3-STABLE FreeBSD 5.3-STABLE #10: Mon Nov 22 09:19:35 ULAT 2004 root@publica.ub.mng.net:/usr/obj/usr/src/sys/AMD amd64 I compiled kernel with following options: # SMP support options SMP options MAXDSIZ=(1024UL*1024*1024) options MAXSSIZ=(128UL*1024*1024) options DFLDSIZ=(1024UL*1024*1024) options PREEMPTION I'm using apache+mod_ssl-1.3.33+2.8.22, clamav-0.80, exim-4.43+28 and mysql-server-4.0.22. It is web mail server with mysql database backend. It seems like following page fault occurs when people accesses web intensively. ----------------------------------------------------------------------------------------------------------------------------- Fatal trap: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x18 fault code = supervisor read, page not present instruction pointer = 0x8:0xffffffff8026d693 stack pointer = 0x10:0xffffffffb36ab850 frame pointer = 0x10:0x0 code segment = base 0x0, limit 0xfffff, type 0x1b DPL 0, press 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 44 (swi1: net) trap number = 12 panic: page fault cpuid = 1 boot() called on cpu#1 Uptime: 17m8s Cannot dump. No dump device defined ----------------------------------------------------------------------------------------------------------------------------- Is it known problem or should I post it to freebsd-bugs list? How to solve this problem? Is it related to ips driver? If somebody wants to make closer look into the problem I can give an shell account on this server. thanks in advance, Ganbold From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 03:40:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E495A16A4CF; Mon, 22 Nov 2004 03:40:53 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56BE243D58; Mon, 22 Nov 2004 03:40:53 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAM3hWoD051279; Sun, 21 Nov 2004 20:43:32 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41A15FE7.4010403@freebsd.org> Date: Sun, 21 Nov 2004 20:41:27 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ganbold References: <6.2.0.14.2.20041122110822.0305eeb0@202.179.0.80> In-Reply-To: <6.2.0.14.2.20041122110822.0305eeb0@202.179.0.80> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: mhunter@ack.Berkeley.EDU cc: freebsd-current@freebsd.org cc: cguttesen@yahoo.dk Subject: Re: Page fault in FreeBSD 5.3 on IBM e325, Dual AMD64 2.2GHz, 4GB RAM, ServeRAID 6M X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 03:40:54 -0000 Hi, A couple things to try: 1) Add the following to /boot/loader.conf and reboot: debug.mpsafenet=0 2) Can you send me the dmesg output? 3) Recompile your kernel with the following options: options DDB options KDB If you can enable the serial console and log it, please do. Then when the fault happens, send me the output. Scott Ganbold wrote: > Hi all, > > I got following page fault in FreeBSD 5.3 on IBM e325 with Dual AMD64 > 2.2GHz, 4GB RAM and ServeRAID 6M SCSI > controller. > > FreeBSD publicc.ub.mng.net 5.3-STABLE FreeBSD 5.3-STABLE #10: Mon Nov 22 > 09:19:35 ULAT 2004 root@publica.ub.mng.net:/usr/obj/usr/src/sys/AMD > amd64 > > I compiled kernel with following options: > > # SMP support > options SMP > options MAXDSIZ=(1024UL*1024*1024) > options MAXSSIZ=(128UL*1024*1024) > options DFLDSIZ=(1024UL*1024*1024) > options PREEMPTION > > I'm using apache+mod_ssl-1.3.33+2.8.22, clamav-0.80, exim-4.43+28 and > mysql-server-4.0.22. > It is web mail server with mysql database backend. > > It seems like following page fault occurs when people accesses web > intensively. > ----------------------------------------------------------------------------------------------------------------------------- > > Fatal trap: page fault while in kernel mode > cpuid = 1; apic id = 01 > fault virtual address = 0x18 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xffffffff8026d693 > stack pointer = 0x10:0xffffffffb36ab850 > frame pointer = 0x10:0x0 > code segment = base 0x0, limit 0xfffff, type 0x1b > DPL 0, press 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 44 (swi1: net) > trap number = 12 > panic: page fault > cpuid = 1 > boot() called on cpu#1 > Uptime: 17m8s > Cannot dump. No dump device defined > ----------------------------------------------------------------------------------------------------------------------------- > > > Is it known problem or should I post it to freebsd-bugs list? How to > solve this problem? > Is it related to ips driver? > If somebody wants to make closer look into the problem I can give an > shell account on this server. > > thanks in advance, > > Ganbold > > > > From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 03:55:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1FAF16A4CE; Mon, 22 Nov 2004 03:55:27 +0000 (GMT) Received: from juniper.fornext.org (53.35.138.210.xn.2iij.net [210.138.35.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6771E43D58; Mon, 22 Nov 2004 03:55:26 +0000 (GMT) (envelope-from shino@fornext.org) Received: from [127.0.0.1] (ariel.net.ss.titech.ac.jp [131.112.21.25]) by juniper.fornext.org (Postfix) with ESMTP id D26E72A; Mon, 22 Nov 2004 12:55:24 +0900 (JST) Date: Mon, 22 Nov 2004 12:55:24 +0900 From: Shunsuke SHINOMIYA To: Matthew Dillon In-Reply-To: <200411220038.iAM0c7JQ052589@apollo.backplane.com> References: <20041121205158.45CE.SHINO@fornext.org> <200411220038.iAM0c7JQ052589@apollo.backplane.com> Message-Id: <20041122104527.5204.SHINO@fornext.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.12 [ja] cc: freebsd-stable@freebsd.org cc: freebsd-current@freebsd.org cc: Jeremie Le Hen Subject: Re[4]: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 03:55:27 -0000 Thank you, Matt. > > Very interesting, but the only reason you get lower results is simply > because the TCP window is not big enough. That's it. > Yes, I knew that adjusting TCP window size is important to use up a link. However I wanted to show adjusting the parameters of Interrupt Moderation affects network performance. And I think a packet loss was occured by enabled Interrupt Moderation. The mechanism of a packet loss in this case is not cleared, but I think inappropriate TCP window size is not the only reason. I found TCP throuput improvement at disabled Interrupt Moderation is related to congestion avoidance phase of TCP. Because these standard deviations are decreased when Interrupt Moderation is disabled. The following two results are outputs of `iperf -P 10'. without TCP window size adjustment too. I think, the difference of each throughput at same measurement shows congestion avoidance worked. o with default setting of Interrupt Moderation. > [ ID] Interval Transfer Bandwidth > [ 13] 0.0-10.0 sec 80.1 MBytes 67.2 Mbits/sec > [ 11] 0.0-10.0 sec 121 MBytes 102 Mbits/sec > [ 12] 0.0-10.0 sec 98.9 MBytes 83.0 Mbits/sec > [ 4] 0.0-10.0 sec 91.8 MBytes 76.9 Mbits/sec > [ 7] 0.0-10.0 sec 127 MBytes 106 Mbits/sec > [ 5] 0.0-10.0 sec 106 MBytes 88.8 Mbits/sec > [ 6] 0.0-10.0 sec 113 MBytes 94.4 Mbits/sec > [ 10] 0.0-10.0 sec 117 MBytes 98.2 Mbits/sec > [ 9] 0.0-10.0 sec 113 MBytes 95.0 Mbits/sec > [ 8] 0.0-10.0 sec 93.0 MBytes 78.0 Mbits/sec > [SUM] 0.0-10.0 sec 1.04 GBytes 889 Mbits/sec o with disabled Interrupt Moderation. > [ ID] Interval Transfer Bandwidth > [ 7] 0.0-10.0 sec 106 MBytes 88.9 Mbits/sec > [ 10] 0.0-10.0 sec 107 MBytes 89.7 Mbits/sec > [ 8] 0.0-10.0 sec 107 MBytes 89.4 Mbits/sec > [ 9] 0.0-10.0 sec 107 MBytes 90.0 Mbits/sec > [ 11] 0.0-10.0 sec 106 MBytes 89.2 Mbits/sec > [ 12] 0.0-10.0 sec 104 MBytes 87.6 Mbits/sec > [ 4] 0.0-10.0 sec 106 MBytes 88.7 Mbits/sec > [ 13] 0.0-10.0 sec 106 MBytes 88.9 Mbits/sec > [ 5] 0.0-10.0 sec 106 MBytes 88.9 Mbits/sec > [ 6] 0.0-10.0 sec 107 MBytes 89.9 Mbits/sec > [SUM] 0.0-10.0 sec 1.04 GBytes 891 Mbits/sec But, By decreasing TCP windows size, it could avoid. o with default setting of Interrupt Moderation and iperf -P 10 -w 28.3k > [ ID] Interval Transfer Bandwidth > [ 12] 0.0-10.0 sec 111 MBytes 93.0 Mbits/sec > [ 4] 0.0-10.0 sec 106 MBytes 88.8 Mbits/sec > [ 11] 0.0-10.0 sec 107 MBytes 89.9 Mbits/sec > [ 9] 0.0-10.0 sec 109 MBytes 91.6 Mbits/sec > [ 5] 0.0-10.0 sec 109 MBytes 91.5 Mbits/sec > [ 13] 0.0-10.0 sec 108 MBytes 90.8 Mbits/sec > [ 10] 0.0-10.0 sec 107 MBytes 89.7 Mbits/sec > [ 8] 0.0-10.0 sec 110 MBytes 92.3 Mbits/sec > [ 6] 0.0-10.0 sec 111 MBytes 93.2 Mbits/sec > [ 7] 0.0-10.0 sec 108 MBytes 90.6 Mbits/sec > [SUM] 0.0-10.0 sec 1.06 GBytes 911 Mbits/sec Measureing TCP throughput was not appropriate way to indicate an effect of Interrupt Moderation clearly. It's my mistake. TCP is too complicated. :) -- Shunsuke SHINOMIYA From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 03:58:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 956F616A4CE; Mon, 22 Nov 2004 03:58:27 +0000 (GMT) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id D844743D2F; Mon, 22 Nov 2004 03:58:23 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.43 (FreeBSD)) id 1CW5LW-000Ear-PE; Mon, 22 Nov 2004 11:58:35 +0800 Message-Id: <6.2.0.14.2.20041122114643.0305ccb0@202.179.0.80> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Mon, 22 Nov 2004 11:58:11 +0800 To: Scott Long From: Ganbold In-Reply-To: <41A15FE7.4010403@freebsd.org> References: <6.2.0.14.2.20041122110822.0305eeb0@202.179.0.80> <41A15FE7.4010403@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: mhunter@ack.Berkeley.EDU cc: freebsd-current@freebsd.org cc: cguttesen@yahoo.dk Subject: Re: Page fault in FreeBSD 5.3 on IBM e325, Dual AMD64 2.2GHz, 4GB RAM, ServeRAID 6M X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 03:58:27 -0000 Scott, At 11:41 AM 11/22/2004, you wrote: >Hi, > >A couple things to try: > >1) Add the following to /boot/loader.conf and reboot: > debug.mpsafenet=0 > >2) Can you send me the dmesg output? Here is normal boot dmesg output: Copyright (c) 1992-2004 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 5.3-STABLE #10: Mon Nov 22 09:19:35 ULAT 2004 root@publica.ub.mng.net:/usr/obj/usr/src/sys/AMD Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 248 (2193.17-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 Features=0x78bfbff AMD Features=0xe0500800 real memory = 4227268608 (4031 MB) avail memory = 4083224576 (3894 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0x8080-0x80ff,0x8000-0x807f,0xcf8-0xcff iomem 0xd8000-0xdbfff on acpi0 pci0: on pcib0 pcib1: at device 6.0 on pci0 pci1: on pcib1 ohci0: mem 0xfc100000-0xfc100fff irq 19 at device 0.0 on pci1 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfc101000-0xfc101fff irq 19 at device 0.1 on pci1 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ukbd0: Silitek IBM USB Keyboard, rev 1.10/1.00, addr 2, iclass 3/1 kbd0 at ukbd0 uhid0: Silitek IBM USB Keyboard, rev 1.10/1.00, addr 2, iclass 3/1 pci1: at device 5.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at device 7.1 (no driver attached) pci0: at device 7.3 (no driver attached) pcib2: at device 10.0 on pci0 pci2: on pcib2 bge0: mem 0xfe000000-0xfe00ffff,0xfe010000-0xfe01ffff irq 24 at de vice 1.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:0d:60:14:cc:9e bge1: mem 0xfe020000-0xfe02ffff,0xfe030000-0xfe03ffff irq 25 at de vice 1.1 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:0d:60:14:cc:9f pci2: at device 2.0 (no driver attached) pci0: at device 10.1 (no driver attached) pcib3: at device 11.0 on pci0 pci3: on pcib3 pcib4: at device 3.0 on pci3 pci4: on pcib4 ips0: mem 0xfe100000-0xfe100fff irq 28 at device 8.0 on pci4 ips0: [GIANT-LOCKED] pci0: at device 11.1 (no driver attached) sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A orm0: at iomem 0xcb000-0xcb7ff,0xc9800-0xcafff,0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 atkbdc0: at port 0x64,0x60 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 0.976 msec ips0: adapter type: ServeRAID 6M (marco) ips0: logical drives: 1 ips0: Logical Drive 0: RAID5 sectors: 355481600, state OK ipsd0: on ips0 ipsd0: Logical Drive (173575MB) SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ipsd0s1a >3) Recompile your kernel with the following options: > > options DDB > options KDB > >If you can enable the serial console and log it, please do. Then >when the fault happens, send me the output. I just moved web mail server back to old Dell server with FreeBSD 4.9 where it was before. Since this web mail server is production server I couldn't still hold it in IBM e325. Now probably I have to reproduce this error again in IBM e325 which doesn't have any load now. I will try to make some loads on this server until I can get page fault error again and I will send you the debug output logs. Ganbold >Scott From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 04:42:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE2C116A4CE; Mon, 22 Nov 2004 04:42:43 +0000 (GMT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88DE443D54; Mon, 22 Nov 2004 04:42:43 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) iAM4gecW053765; Sun, 21 Nov 2004 20:42:40 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.9p2/8.12.9/Submit) id iAM4gduM053764; Sun, 21 Nov 2004 20:42:39 -0800 (PST) (envelope-from dillon) Date: Sun, 21 Nov 2004 20:42:39 -0800 (PST) From: Matthew Dillon Message-Id: <200411220442.iAM4gduM053764@apollo.backplane.com> To: Shunsuke SHINOMIYA References: <20041121205158.45CE.SHINO@fornext.org> <200411220038.iAM0c7JQ052589@apollo.backplane.com> <20041122104527.5204.SHINO@fornext.org> cc: freebsd-stable@freebsd.org cc: freebsd-current@freebsd.org cc: Jeremie Le Hen Subject: Re: Re[4]: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 04:42:44 -0000 : Yes, I knew that adjusting TCP window size is important to use up a link. : However I wanted to show adjusting the parameters of Interrupt : Moderation affects network performance. : : And I think a packet loss was occured by enabled Interrupt Moderation. : The mechanism of a packet loss in this case is not cleared, but I think : inappropriate TCP window size is not the only reason. Packet loss is not likely, at least not for the contrived tests we are doing because GiGE links have hardware flow control (I'm fairly sure). One could calculate the worst case small-packet build up in the receive ring. I'm not sure what the minimum pad for GiGE is, but lets say it's 64 bytes. Then the packet rate would be around 1.9M pps or 244 packets per interrupt at a moderation frequency of 8000 hz. The ring is 256 packets. But, don't forget the hardware flow control! The switch has some buffering too. hmm... me thinks I now understand why 8000 was chosen as the default :-) I would say that this means packet loss due to the interrupt moderation is highly unlikely, at least in theory, but if one were paranoid one might want to use a higher moderation frequency, say 16000 hz, to be sure. : I found TCP throuput improvement at disabled Interrupt Moderation is related : to congestion avoidance phase of TCP. Because these standard deviations are : decreased when Interrupt Moderation is disabled. : : The following two results are outputs of `iperf -P 10'. without TCP : window size adjustment too. I think, the difference of each throughput : at same measurement shows congestion avoidance worked. : :o with default setting of Interrupt Moderation. :> [ ID] Interval Transfer Bandwidth :> [ 13] 0.0-10.0 sec 80.1 MBytes 67.2 Mbits/sec :> [ 11] 0.0-10.0 sec 121 MBytes 102 Mbits/sec :> [ 12] 0.0-10.0 sec 98.9 MBytes 83.0 Mbits/sec :> [ 4] 0.0-10.0 sec 91.8 MBytes 76.9 Mbits/sec :> [ 7] 0.0-10.0 sec 127 MBytes 106 Mbits/sec :> [ 5] 0.0-10.0 sec 106 MBytes 88.8 Mbits/sec :> [ 6] 0.0-10.0 sec 113 MBytes 94.4 Mbits/sec :> [ 10] 0.0-10.0 sec 117 MBytes 98.2 Mbits/sec :> [ 9] 0.0-10.0 sec 113 MBytes 95.0 Mbits/sec :> [ 8] 0.0-10.0 sec 93.0 MBytes 78.0 Mbits/sec :> [SUM] 0.0-10.0 sec 1.04 GBytes 889 Mbits/sec Certainly overall send/response latency will be effected by up to 1/freq, e.g. 1/8000 = 125 uS (x2 hosts == 250 uS worst case), which is readily observable by running ping: [intrate] [set on both boxes] max: 64 bytes from 216.240.41.62: icmp_seq=2 ttl=64 time=0.057 ms 100000: 64 bytes from 216.240.41.62: icmp_seq=8 ttl=64 time=0.061 ms 30000: 64 bytes from 216.240.41.62: icmp_seq=5 ttl=64 time=0.078 ms 8000: 64 bytes from 216.240.41.62: icmp_seq=3 ttl=64 time=0.176 ms (large stddev too, e.g. 0.188, 0.166, etc). But this is only relevant for applications that require that sort of response time == not very many applications. Note that a large packet will turn the best case 57 uS round trip into a 140 uS round trip with the EM card. It might be interesting to see how interrupt moderation effects a buildworld over NFS as that certainly results in a huge amount of synchronous transactional traffic. : Measureing TCP throughput was not appropriate way to indicate an effect : of Interrupt Moderation clearly. It's my mistake. TCP is too : complicated. :) : :-- :Shunsuke SHINOMIYA It really just comes down to how sensitive a production system is to round trip times within the range of effect of the moderation frequency. Usually the answer is: not very. That is, the benefit is not sufficient to warrent the additional interrupt load that turning moderation off would create. And even if low latency is desired it is not actually necessary to turn off moderation. It could be set fairly high, e.g. 20000, to reap most of the benefit. Processing overheads are also important. If the network is loaded down you will wind up eating a significant chunk of cpu with moderation turned off. This is readily observable by running vmstat during an iperf test. iperf test ~700 MBits/sec reported for all tested moderation frequencies. using iperf -w 63.5K on DragonFly. I would be interesting in knowing how FreeBSD fares, though SMP might skew the reality too much to be meaningful. moderation cpu frequency %idle 100000 2% idle 30000 7% idle 20000 35% idle 10000 60% idle 8000 66% idle In otherwords, if you are doing more then just shoving bits around the network, for example if you need to read or write the disk or do some sort of computation or other activity that requires cpu, turning off moderation could wind up being a very, very bad idea. In fact, even if you are just routing packets I would argue that turning off moderation might not be a good choice... it might make more sense to set it to some high frequency like 40000 Hz. But, of course, it depends on what other things the machine might be running and what sort of processing (e.g. firewall lists) the machine has to do on the packets. -Matt Matthew Dillon From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 05:21:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA99E16A4CE; Mon, 22 Nov 2004 05:21:18 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85B7C43D5E; Mon, 22 Nov 2004 05:21:18 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 2F609F20B7; Sun, 21 Nov 2004 21:21:16 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13998-03; Sun, 21 Nov 2004 21:21:10 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 5F4EAF1837; Sun, 21 Nov 2004 21:21:10 -0800 (PST) From: Sean McNeil To: Matthew Dillon In-Reply-To: <200411220442.iAM4gduM053764@apollo.backplane.com> References: <20041121205158.45CE.SHINO@fornext.org> <200411220038.iAM0c7JQ052589@apollo.backplane.com> <20041122104527.5204.SHINO@fornext.org> <200411220442.iAM4gduM053764@apollo.backplane.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-ak8TFvWEot9EfT6qjJ5l" Date: Sun, 21 Nov 2004 21:21:10 -0800 Message-Id: <1101100870.16086.16.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com cc: Jeremie Le Hen cc: freebsd-stable@freebsd.org cc: freebsd-current@freebsd.org cc: Shunsuke SHINOMIYA Subject: Re: Re[4]: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 05:21:19 -0000 --=-ak8TFvWEot9EfT6qjJ5l Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2004-11-21 at 20:42 -0800, Matthew Dillon wrote: > : Yes, I knew that adjusting TCP window size is important to use up a lin= k. > : However I wanted to show adjusting the parameters of Interrupt > : Moderation affects network performance. > : > : And I think a packet loss was occured by enabled Interrupt Moderation. > : The mechanism of a packet loss in this case is not cleared, but I think > : inappropriate TCP window size is not the only reason. >=20 > Packet loss is not likely, at least not for the contrived tests we > are doing because GiGE links have hardware flow control (I'm fairly > sure). I have to disagree. Packet loss is likely according to some of my tests. With the re driver, no change except placing a 100BT setup with no packet loss to a gigE setup (both linksys switches) will cause serious packet loss at 20Mbps data rates. I have discovered the only way to get good performance with no packet loss was to 1) Remove interrupt moderation 2) defrag each mbuf that comes in to the driver. Doing both of these, I get excellent performance without any packet loss. All my testing has been with UDP packets, however, and nothing was checked for TCP. > One could calculate the worst case small-packet build up in the recei= ve > ring. I'm not sure what the minimum pad for GiGE is, but lets say it= 's > 64 bytes. Then the packet rate would be around 1.9M pps or 244 packe= ts > per interrupt at a moderation frequency of 8000 hz. The ring is 256 > packets. But, don't forget the hardware flow control! The switch > has some buffering too. >=20 > hmm... me thinks I now understand why 8000 was chosen as the default = :-) >=20 > I would say that this means packet loss due to the interrupt moderati= on > is highly unlikely, at least in theory, but if one were paranoid one > might want to use a higher moderation frequency, say 16000 hz, to be = sure. Your calculations are based on the mbufs being a particular size, no? What happens if they are seriously defragmented? Is this what you mean by "small-packet"? Are you assuming the mbufs are as small as they get? How small can they go? 1 byte? 1 MTU? Increasing the interrupt moderation frequency worked on the re driver, but it only made it marginally better. Even without moderation, however, I could lose packets without m_defrag. I suspect that there is something in the higher level layers that is causing the packet loss. I have no explanation why m_defrag makes such a big difference for me, but it does. I also have no idea why a 20Mbps UDP stream can lose data over gigE phy and not lose anything over 100BT... without the above mentioned changes that is. --=-ak8TFvWEot9EfT6qjJ5l Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBoXdGyQsGN30uGE4RAmV0AKCW9MeUkuqtCuvyfD9J5ryRMCW2dACfbGA3 /SNWm1+5hpl2j+Z2dcIQ9QM= =dDLI -----END PGP SIGNATURE----- --=-ak8TFvWEot9EfT6qjJ5l-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 07:29:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64B3616A4CE; Mon, 22 Nov 2004 07:29:06 +0000 (GMT) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABC8743D58; Mon, 22 Nov 2004 07:28:19 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.43 (FreeBSD)) id 1CW8cc-000G7I-Up; Mon, 22 Nov 2004 15:28:27 +0800 Message-Id: <6.2.0.14.2.20041122151958.0303be20@202.179.0.80> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Mon, 22 Nov 2004 15:27:56 +0800 To: Scott Long From: Ganbold Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable cc: tomaz.borstnar@over.net cc: cguttesen@yahoo.dk cc: freebsd-current@freebsd.org cc: mhunter@ack.Berkeley.EDU cc: rwatson@freebsd.org Subject: Re: Page fault in FreeBSD 5.3 on IBM e325, Dual AMD64 2.2GHz, 4GB RAM, ServeRAID 6M - debug logs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 07:29:06 -0000 Scott, I didn't put debug.mpsafenet=3D0 to /boot/loader.conf. I compiled kernel= with: options DDB options KDB Here is crash time debug output and dmesg: ----------------------------------------------------------------------------= ---------------------------- Console: serial port BIOS drive C: is disk0 BIOS 614kB/4127168kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 (root@publica.ub.mng.net, Sun Nov 21 18:24:58 ULAT 2004) Loading /boot/defaults/loader.conf /boot/kernel/kernel text=3D0x2fa370 data=3D0x7a920+0x3b9d0=20 -syms=3D[0x8+0x58278-+0x8+0x4b956| KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2004 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 5.3-STABLE #12: Mon Nov 22 12:04:57 ULAT 2004 tsgan@publicc.ub.mng.net:/usr/obj/usr/src/sys/AMD Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 248 (2193.17-MHz K8-class CPU) Origin =3D "AuthenticAMD" Id =3D 0xf58 Stepping =3D 8 = Features=3D0x78bfbff AMD Features=3D0xe0500800 real memory =3D 4227268608 (4031 MB) avail memory =3D 4083208192 (3894 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0x8080-0x80ff,0x8000-0x807f,0xcf8-0xcff= =20 iomem 0xd8000-0xdbfff on acpi0 pci0: on pcib0 pcib1: at device 6.0 on pci0 pci1: on pcib1 ohci0: mem 0xfc100000-0xfc100fff irq 19 at= =20 device 0.0 on pci1 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfc101000-0xfc101fff irq 19 at= =20 device 0.1 on pci1 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ukbd0: Silitek IBM USB Keyboard, rev 1.10/1.00, addr 2, iclass 3/1 kbd1 at ukbd0 uhid0: Silitek IBM USB Keyboard, rev 1.10/1.00, addr 2, iclass 3/1 pci1: at device 5.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at device 7.1 (no driver attached) pci0: at device 7.3 (no driver attached) pcib2: at device 10.0 on pci0 pci2: on pcib2 bge0: mem=20 0xfe000000-0xfe00ffff,0xfe010000-0xfe01ffff irq 24 at device 1.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX,=20 1000baseTX-FDX, auto bge0: Ethernet address: 00:0d:60:14:cc:9e bge1: mem=20 0xfe020000-0xfe02ffff,0xfe030000-0xfe03ffff irq 25 at device 1.1 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX,=20 1000baseTX-FDX, auto bge1: Ethernet address: 00:0d:60:14:cc:9f pci2: at device 2.0 (no driver attached) pci0: at device 10.1 (no driver=20 attached) pcib3: at device 11.0 on pci0 pci3: on pcib3 pcib4: at device 3.0 on pci3 pci4: on pcib4 ips0: mem 0xfe100000-0xfe100fff irq 28 at=20 device 8.0 on pci4 ips0: [GIANT-LOCKED] pci0: at device 11.1 (no driver=20 attached) sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on= acpi0 sio0: type 16550A, console orm0: at iomem=20 0xcb000-0xcb7ff,0xc9800-0xcafff,0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 device_attach: atkbd0 attach returned 6 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x100> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 0.976 msec ips0: adapter type: ServeRAID 6M (marco) ips0: logical drives: 1 ips0: Logical Drive 0: RAID5 sectors: 355481600, state OK ipsd0: on ips0 ipsd0: Logical Drive (173575MB) SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ipsd0s1a Pre-seeding PRNG: kickstart. Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point kickstart. swapon: adding /dev/ipsd0s1b as swap device Starting file system checks: /dev/ipsd0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ipsd0s1a: clean, 507157 free (7565 frags, 62449 blocks, 0.7%=20 fragmentation) /dev/ipsd0s1f: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ipsd0s1f: clean, 1012200 free (40 frags, 126520 blocks, 0.0%=20 fragmentation) /dev/ipsd0s1d: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ipsd0s1d: clean, 4876181 free (45669 frags, 603814 blocks, 0.4%=20 fragmentation) /dev/ipsd0s1e: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ipsd0s1e: clean, 4965575 free (1087 frags, 620561 blocks, 0.0%=20 fragmentation) /dev/ipsd0s1g: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ipsd0s1g: clean, 53622407 free (671 frags, 6702717 blocks, 0.0%=20 fragmentation) Setting hostname: publica.ub.mng.net. bge0: flags=3D8843 mtu 1500 options=3D1a inet 202.179.0.80 netmask 0xffffffe0 broadcast 202.179.0.95 ether 00:0d:60:14:cc:9e media: Ethernet 100baseTX status: active lo0: flags=3D8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 add net default: gateway 202.179.0.65 Additional routing options:. Starting devd. kbdcontrol: cannot open /dev/kbd1: Device busy Mounting NFS file systems:. Starting syslogd. Nov 22 13:49:36 publica syslogd: kernel boot file is /boot/kernel/kernel ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/X11R6/lib= /usr/local/lib Starting usbd. Starting local daemons:. Updating motd. Configuring syscons: blanktime. Starting sshd. Initial amd64 initialization:. Additional ABI support:. Starting cron. Local package initialization:Starting apache. Starting clamav_clamd. Starting clamav_freshclam. Starting exim. Starting mysql. Starting spamd. . Additional TCP options:. Starting inetd. Starting background file system checks in 60 seconds. Mon Nov 22 13:49:41 ULAT 2004 =E0=E0=E0=E0=E0=E0N=E0=E0=E0=E0=E0=E0N=E0Nov =E0=E0N=E0=E0=E0=E0No=E0N=E0Nov= 22 14:08:=E0N=E0=E0=E0=E0=E0=E0=E0=E0=E0=E0=E0=E0=E0=E0=E0=E0=E0=E0=E0=E0= =E0=E0=E0=E0=E0=E0=E0=E0 Fatal trap 12: page fault while in kernel mode cpuid =3D 1; apic id =3D 01 fault virtual address =3D 0x18 fault code =3D supervisor read, page not present instruction pointer =3D 0x8:0xffffffff80277fc0 stack pointer =3D 0x10:0xffffffffb36ab830 frame pointer =3D 0x10:0xffffffffb36ab890 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 44 (swi1: net) [thread 100044] Stopped at m_copym+0x190: incl %ecx db> bt No such command db> help print p examine x search set = write w delete d break dwatch watch = dhwatch hwatch step s continue c until next match trace where call show ps gdb reset kill watchdog thread panic db> trace m_copym() at m_copym+0x190 tcp_output() at tcp_output+0xe91 tcp_input() at tcp_input+0x2f80 ip_input() at ip_input+0xff netisr_processqueue() at netisr_processqueue+0x79 swi_net() at swi_net+0x14d ithread_loop() at ithread_loop+0xde fork_exit() at fork_exit+0x8f fork_trampoline() at fork_trampoline+0xe --- trap 0, rip =3D 0, rsp =3D 0xffffffffb36abd00, rbp =3D 0 --- db> trace m_copym() at m_copym+0x190 tcp_output() at tcp_output+0xe91 tcp_input() at tcp_input+0x2f80 ip_input() at ip_input+0xff netisr_processqueue() at netisr_processqueue+0x79 swi_net() at swi_net+0x14d ithread_loop() at ithread_loop+0xde fork_exit() at fork_exit+0x8f fork_trampoline() at fork_trampoline+0xe --- trap 0, rip =3D 0, rsp =3D 0xffffffffb36abd00, rbp =3D 0 --- db> ----------------------------------------------------------------------------= ---------------------------- It seems to me the problem is related to network stack and threading. Am I right? How to solve this problem? thanks in advance, Ganbold From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 07:31:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4885116A4CE; Mon, 22 Nov 2004 07:31:38 +0000 (GMT) Received: from mail12.syd.optusnet.com.au (mail12.syd.optusnet.com.au [211.29.132.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FCF043D1F; Mon, 22 Nov 2004 07:31:37 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) iAM7VX79030785 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 22 Nov 2004 18:31:35 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])iAM7VXxP047030; Mon, 22 Nov 2004 18:31:33 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)iAM7VWvw047029; Mon, 22 Nov 2004 18:31:32 +1100 (EST) (envelope-from pjeremy) Date: Mon, 22 Nov 2004 18:31:32 +1100 From: Peter Jeremy To: Poul-Henning Kamp Message-ID: <20041122073132.GW79646@cirb503493.alcatel.com.au> References: <76633.1100857077@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <76633.1100857077@critter.freebsd.dk> User-Agent: Mutt/1.4.2i cc: arch@freebsd.org cc: current@freebsd.org Subject: Re: [REVIEW/TEST] nanodelay() vs DELAY() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 07:31:38 -0000 On Fri, 2004-Nov-19 10:37:57 +0100, Poul-Henning Kamp wrote: > http://phk.freebsd.dk/patch/nanodelay.patch One buglet. In: +static void +initnanodelay(void *dummy) +{ + int i; + + for (i = 0; i < N_NANODELAY_BUCKETS; i++) { + nanodelay_funcs[i] = tc_nanodelay; + nanodelay_args[i] = i; + } The 2nd last line should be: + nanodelay_args[i] = i * (1 << N_NANODELAY_SHIFT); because the argument to tc_nanodelay() is in nsec. The fact that this doesn't show up in the graph suggests that you're not using tc_nanodelay() at all within the 0..8usec range. >Here is a plot which shows how DELAY() and nanodelay() perform on two >of my test-machines: > > http://phk.freebsd.dk/misc/nanodelay.png nanodelay() definitely looks much healthier than DELAY(). >A default routine spins on the timecounter using nanouptime(). How >well this works depends on which timecounter we use, but in general >we can trust it to be OK above a few microseconds. Your graph suggests that it's fairly good above about 200nsec even on equipment that is not blazingly fast. Have you looked at the granularity of tc_nanodelay() (and the likely granularity required by callers)? Is 8nsec reasonable given the inner loop of of tc_nanodelay()? Do you have any idea where the transition points between the various delay functions are? >The array takes up 9000 bytes on 32 bit and 17000 on 64 bit. AFAIK, all the FreeBSD architectures have 32-bit ints, so that should be 13,000 bytes for 64bit architectures. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 08:45:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C987D16A4CE for ; Mon, 22 Nov 2004 08:45:36 +0000 (GMT) Received: from mail.bonivet.net (mail.bonivet.net [81.56.185.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96E0B43D5C for ; Mon, 22 Nov 2004 08:45:35 +0000 (GMT) (envelope-from gstewart@bonivet.net) X-ConnectingHost: 192.168.1.254 Received: from dragonfly.bonivet.net (dragonfly.bonivet.net [192.168.1.254]) by mail.bonivet.net (8.13.1/8.13.1) with SMTP id iAM8jQmJ021486 for ; Mon, 22 Nov 2004 09:45:26 +0100 Date: Mon, 22 Nov 2004 09:45:26 +0100 From: Godwin Stewart To: freebsd-current@freebsd.org Message-Id: <20041122094526.58437cc6.gstewart@bonivet.net> In-Reply-To: <1101080614.5334.0.camel@linux> References: <20041121120114.5BA6B16A4F2@hub.freebsd.org> <1101080614.5334.0.camel@linux> Organization: Nope, none here, it's a mess ;o) X-Mailer: Sylpheed version 1.0.0beta3 (GTK+ 1.2.10; i386-unknown-freebsd5.3) X-MS-SUX: As if we didn't know... X-Curious: You just *HAD* to look at these headers, didn't you! X-Face: #T;eJks=B[`71qrwp`l6BW8xI&hP8S*4Kd%e?8o"rL02ZYf"rWa41l83a)L,*; S).Ukq$U% II{-z#5%i&X8"%{$)ZWmE7WBDF)?wK1^7]u9T;@jqdZo?IT!d-L`!@&vW)F_1 Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: freebsd-current Digest, Vol 79, Issue 14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 08:45:36 -0000 On Sun, 21 Nov 2004 18:43:34 -0500, Ward Cinnamon wrote: > Unsubscribe me. Why do you think writing to the list is going to achieve that? How about looking in the headers of list mails for unsubscribe instructions... -- Any surviving best shots are ruined when someone inadvertently open the darkroom door and all of the dark leaks out. From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 10:45:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04A2716A4CE; Mon, 22 Nov 2004 10:45:29 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98B3E43D5E; Mon, 22 Nov 2004 10:45:28 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAMAhjsw024954; Mon, 22 Nov 2004 05:43:45 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iAMAhhFj024951; Mon, 22 Nov 2004 10:43:44 GMT (envelope-from robert@fledge.watson.org) Date: Mon, 22 Nov 2004 10:43:43 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Ganbold In-Reply-To: <6.2.0.14.2.20041122151958.0303be20@202.179.0.80> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: tomaz.borstnar@over.net cc: cguttesen@yahoo.dk cc: freebsd-current@freebsd.org cc: Scott Long cc: mhunter@ack.Berkeley.EDU Subject: Re: Page fault in FreeBSD 5.3 on IBM e325, Dual AMD64 2.2GHz, 4GB RAM, ServeRAID 6M - debug logs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 10:45:29 -0000 On Mon, 22 Nov 2004, Ganbold wrote: > Fatal trap 12: page fault while in kernel mode > cpuid = 1; apic id = 01 > fault virtual address = 0x18 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xffffffff80277fc0 > stack pointer = 0x10:0xffffffffb36ab830 > frame pointer = 0x10:0xffffffffb36ab890 > 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 = 44 (swi1: net) > [thread 100044] > Stopped at m_copym+0x190: incl %ecx <...> > -------------------------------------------------------------------------------------------------------- > > It seems to me the problem is related to network stack and threading. > Am I right? How to solve this problem? I've seen reports of this problem with and without debug.mpsafenet=1, which suggests it is a network stack bug but not specific to locking. I've also seen reports that disabling TCP SACK will make the problem go away, which would be good to confirm. I spent the weekend building up some more expertise in TCP and reading a lot of TCP code, and hope to look at this problem in more detail today. You may want to try turning off TCP sack using net.inet.tcp.sack.enable=0 in sysctl.conf (or loader.conf). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 10:47:32 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62BAE16A4CE for ; Mon, 22 Nov 2004 10:47:32 +0000 (GMT) Received: from lara.cc.fer.hr (lara.cc.fer.hr [161.53.72.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61F0743D48 for ; Mon, 22 Nov 2004 10:47:31 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [127.0.0.1] (localhost.cc.fer.hr [127.0.0.1]) by lara.cc.fer.hr (8.13.1/8.13.1) with ESMTP id iAMAlPXs001466; Mon, 22 Nov 2004 11:47:26 +0100 (CET) (envelope-from ivoras@fer.hr) Message-ID: <41A1C3BD.4010903@fer.hr> Date: Mon, 22 Nov 2004 11:47:25 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 0.9 (X11/20041111) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jeff Roberson , current@freebsd.org References: <20041120000743.G18094@mail.chesapeake.net> In-Reply-To: <20041120000743.G18094@mail.chesapeake.net> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 10:47:32 -0000 Jeff Roberson wrote: > The short description: > This patch removes Giant from the read(), write(), and fstat() syscalls, > as well as page faults, and bufdone (io interrupts) when using FFS. It What is the plan re: RELENG_5? Will things like this (giantless vm, fs) be merged into it? From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 11:35:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC3FD16A4CE; Mon, 22 Nov 2004 11:35:59 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35F8943D45; Mon, 22 Nov 2004 11:35:59 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAMBYFXR043477; Mon, 22 Nov 2004 06:34:15 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iAMBYElG043474; Mon, 22 Nov 2004 11:34:14 GMT (envelope-from robert@fledge.watson.org) Date: Mon, 22 Nov 2004 11:34:13 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Sean McNeil In-Reply-To: <1101100870.16086.16.camel@server.mcneil.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org cc: freebsd-current@freebsd.org cc: Jeremie Le Hen Subject: Re: Re[4]: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 11:35:59 -0000 On Sun, 21 Nov 2004, Sean McNeil wrote: > I have to disagree. Packet loss is likely according to some of my > tests. With the re driver, no change except placing a 100BT setup with > no packet loss to a gigE setup (both linksys switches) will cause > serious packet loss at 20Mbps data rates. I have discovered the only > way to get good performance with no packet loss was to > > 1) Remove interrupt moderation > 2) defrag each mbuf that comes in to the driver. Sounds like you're bumping into a queue limit that is made worse by interrupting less frequently, resulting in bursts of packets that are relatively large, rather than a trickle of packets at a higher rate. Perhaps a limit on the number of outstanding descriptors in the driver or hardware and/or a limit in the netisr/ifqueue queue depth. You might try changing the default IFQ_MAXLEN from 50 to 128 to increase the size of the ifnet and netisr queues. You could also try setting net.isr.enable=1 to enable direct dispatch, which in the in-bound direction would reduce the number of context switches and queueing. It sounds like the device driver has a limit of 256 receive and transmit descriptors, which one supposes is probably derived from the hardware limit, but I have no documentation on hand so can't confirm that. It would be interesting on the send and receive sides to inspect the counters for drops at various points in the network stack; i.e., are we dropping packets at the ifq handoff because we're overfilling the descriptors in the driver, are packets dropped on the inbound path going into the netisr due to over-filling before the netisr is scheduled, etc. And, it's probably interesting to look at stats on filling the socket buffers for the same reason: if bursts of packets come up the stack, the socket buffers could well be being over-filled before the user thread can run. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 11:46:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D5E416A4D0 for ; Mon, 22 Nov 2004 11:46:59 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id A41E443D49 for ; Mon, 22 Nov 2004 11:46:58 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id iAMBkoPV034466; Mon, 22 Nov 2004 06:46:50 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)iAMBkodi034461; Mon, 22 Nov 2004 06:46:50 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Mon, 22 Nov 2004 06:46:50 -0500 (EST) From: Jeff Roberson To: Ivan Voras In-Reply-To: <41A1C3BD.4010903@fer.hr> Message-ID: <20041122064318.Y18094@mail.chesapeake.net> References: <20041120000743.G18094@mail.chesapeake.net> <41A1C3BD.4010903@fer.hr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 11:46:59 -0000 On Mon, 22 Nov 2004, Ivan Voras wrote: > Jeff Roberson wrote: > > > The short description: > > This patch removes Giant from the read(), write(), and fstat() syscalls, > > as well as page faults, and bufdone (io interrupts) when using FFS. It > > What is the plan re: RELENG_5? Will things like this (giantless vm, fs) > be merged into it? The giantless vm was already merged back to RELENG_5 and enabled on amd64, and i386. I hope to merge the giantless vfs back after a month or so of no problems on -current. I hope to commit it to -current this week. I haven't received any feedback from the list though. I hope people are testing it. Perhaps the silence indicates universal success? :-) > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 12:49:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18F8E16A4CF for ; Mon, 22 Nov 2004 12:49:39 +0000 (GMT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91E1E43D6D for ; Mon, 22 Nov 2004 12:49:38 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from mailnull by anduin.net with dspam-scanned (Exim 4.43 (FreeBSD)) id 1CWDa7-0009QD-Hq for current@freebsd.org; Mon, 22 Nov 2004 13:46:11 +0100 Received: from mailnull by anduin.net with spamassassin-scanned (Exim 4.43 (FreeBSD)) id 1CWDa3-0009Pz-V2 for current@freebsd.org; Mon, 22 Nov 2004 13:46:11 +0100 Received: from eirik.unicore.no ([213.225.74.166]) by anduin.net with esmtp (Exim 4.43 (FreeBSD)) id 1CWDa0-0009Pd-Ik; Mon, 22 Nov 2004 13:46:04 +0100 From: Eirik =?ISO-8859-1?Q?=D8verby?= To: Jeff Roberson In-Reply-To: <20041120000743.G18094@mail.chesapeake.net> References: <20041120000743.G18094@mail.chesapeake.net> Content-Type: text/plain Date: Mon, 22 Nov 2004 13:50:22 +0100 Message-Id: <1101127822.19053.13.camel@eirik.unicore.no> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on anduin.net X-Spam-Level: X-Spam-Status: No, hits=-4.7 required=7.5 tests=AWL,BAYES_00 autolearn=no version=2.64 cc: current@freebsd.org Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 12:49:39 -0000 On Sat, 2004-11-20 at 00:24 -0500, Jeff Roberson wrote: > I have a patch that I would like people to test and review. It's > available here: > > http://www.chesapeake.net/~jroberson/smpffs.diff > > The short description: > This patch removes Giant from the read(), write(), and fstat() syscalls, > as well as page faults, and bufdone (io interrupts) when using FFS. It > adds a considerable amount of locking to FFS and softupdates. You may > also use non ffs filesystems concurrently, but they will be protected by > Giant. If you are using quotas you should not yet run this patch. I have > done some buildworlds, but any heavy filesystem activity would be > appreciated. Hoi, what consequences can be expected from this - from a user point of view? Better performance? Better scalability? (even) More stability? New functionality? All of the above? /Eirik > Long description: > There is now a per mount-point mutex in struct ufsmount that covers ffs's > struct fs related allocation routines. The rest of the filesystem was > already covered by the buffer locks on cgs, indirs, etc, as well as a few > mutexes that were already in place. I made great attempts to minimize the > number of lock operations for the common cases which resulted in a couple > of functions which may be entered with the UFS lock held, but return > without it held. Where this is not already done, it will be documented in > comments. > > The softupdate lk lock has been turned into a mutex, and it now protects > all global worklists, inode and page dep hash buckets, etc. > interlocked_sleep() is gone now that BUF_LOCK() and msleep() take > interlock arguments. getdirtybuf() has been slightly changed to solve > some sleep related races that I disucssed with Kirk. For now there is a > single softupdates mutex, but eventually it will be made per-mountpoint > and potentially merged with the ufsmount lock. > > On the infrastructure side, the buffer cache was locked some time ago, and > now the vm is safe to run without Giant, so there are simply a lot of > removed GIANT_REQUIRED lines. I added some locking to vn_start_write() > and friends, and made some changes for LORs there. There is a pair of new > macros called VFS_(UN)LOCK_GIANT(mp) which inspects a new flag on the > mount-point to determine if we have to acquire giant. This is done very > early in the syscall path before we call any VOPs. The mountpoints should > be safe to inspect as we always own a reference to the vnode in the cases > that I have unwound for now. > > Cheers, > Jeff > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 12:53:14 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5441316A4CE for ; Mon, 22 Nov 2004 12:53:14 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7624A43D46 for ; Mon, 22 Nov 2004 12:53:13 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAMCr58d021957; Mon, 22 Nov 2004 13:53:05 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Eirik =?ISO-8859-1?Q?=D8verby?= From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 22 Nov 2004 13:50:22 +0100." <1101127822.19053.13.camel@eirik.unicore.no> Date: Mon, 22 Nov 2004 13:53:05 +0100 Message-ID: <21956.1101127985@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: Jeff Roberson cc: current@freebsd.org Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 12:53:14 -0000 In message <1101127822.19053.13.camel@eirik.unicore.no>, Eirik =?ISO-8859-1?Q?= D8verby?= writes: >Hoi, >what consequences can be expected from this - from a user point of view? >Better performance? Better scalability? (even) More stability? New >functionality? All of the above? >/Eirik That's the goal. That his how we want to reach our goal. Hopefully. No. Almost. :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sun Nov 21 16:01:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89ACD16A4D4 for ; Sun, 21 Nov 2004 16:01:18 +0000 (GMT) Received: from www.kukulies.org (www.kukulies.org [213.146.112.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA28F43D93 for ; Sun, 21 Nov 2004 15:44:06 +0000 (GMT) (envelope-from kuku@www.kukulies.org) Received: from www.kukulies.org (localhost [127.0.0.1]) by www.kukulies.org (8.13.1/8.12.10) with ESMTP id iALFi4IN055539 for ; Sun, 21 Nov 2004 16:44:04 +0100 (CET) (envelope-from kuku@www.kukulies.org) Received: (from kuku@localhost) by www.kukulies.org (8.13.1/8.12.10/Submit) id iALFi3Ys055538 for freebsd-current@freebsd.org; Sun, 21 Nov 2004 16:44:03 +0100 (CET) (envelope-from kuku) Date: Sun, 21 Nov 2004 16:44:03 +0100 (CET) From: Christoph Kukulies Message-Id: <200411211544.iALFi3Ys055538@www.kukulies.org> To: freebsd-current@freebsd.org X-Mailman-Approved-At: Mon, 22 Nov 2004 13:31:31 +0000 Subject: so cuaa0 devices are gone - why? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 16:01:18 -0000 Just curious, why are cua serial devices now gone in 6.0? Is it correct to switch to ttyd0 then? Chris Christoph P. U. Kukulies kuku_at_kukulies.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 03:00:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7963216A4CE for ; Mon, 22 Nov 2004 03:00:52 +0000 (GMT) Received: from mirapoint2.tis.cwru.edu (mirapoint2.TIS.CWRU.Edu [129.22.104.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EBAA43D4C for ; Mon, 22 Nov 2004 03:00:48 +0000 (GMT) (envelope-from jrh29@po.cwru.edu) Received: from [192.168.1.100] (oh-clevelandheights-cdnt1-bg1b-147.clvdoh.adelphia.net [68.170.192.147]) by mirapoint2.tis.cwru.edu (MOS 3.5.4-GR) with ESMTP id CSU84753 (AUTH jrh29); Sun, 21 Nov 2004 22:00:46 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v619) To: freebsd-current@freebsd.org Message-Id: Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-6-378674242" From: Justin Hibbits Date: Sun, 21 Nov 2004 22:00:41 -0500 Content-Transfer-Encoding: 7bit X-Pgp-Agent: GPGMail 1.0.2 X-Mailer: Apple Mail (2.619) X-Mailman-Approved-At: Mon, 22 Nov 2004 13:31:31 +0000 Subject: ATI TV Wonder support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 03:00:52 -0000 --Apple-Mail-6-378674242 Content-Type: multipart/mixed; boundary=Apple-Mail-5-378674181 --Apple-Mail-5-378674181 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed This patch gives more or less full ATI TV Wonder support to the bktr driver. The sound doesn't mute at close, but that might be xawtv's fault, but I don't know which to accuse or look at. But, other than that, it seems pretty good. -Justin -- "And now, if you'll excuse me, I'm in the middle of 15 things, all annoying" -- Lt. Cmdr Susan Ivanova, Babylon 5 --Apple-Mail-5-378674181 Content-Transfer-Encoding: 7bit Content-Type: application/octet-stream; x-unix-mode=0644; name="bktr.patch" Content-Disposition: attachment; filename=bktr.patch --- bktr_card.c Thu Aug 12 11:17:06 2004 +++ /local/src/sys/dev/bktr/bktr_card.c Thu Aug 12 09:15:58 2004 @@ -32,7 +32,7 @@ */ #include -__FBSDID("$FreeBSD: /repoman/r/ncvs/src/sys/dev/bktr/bktr_card.c,v 1.24 2004/08/08 01:23:39 sanpei Exp $"); +__FBSDID("$FreeBSD: src/sys/dev/bktr/bktr_card.c,v 1.23 2003/12/08 07:59:18 obrien Exp $"); /* * This is part of the Driver for Video Capture Cards (Frame grabbers) @@ -368,6 +368,20 @@ { 0x02, 0x00, 0x00, 0x00, 1 }, /* audio MUX values */ 0x18e0 }, /* GPIO mask */ + { CARD_TVWONDER, /* the card id */ + "ATI TV Wonder", /* the 'name' */ + NULL, /* the tuner */ + 0, /* the tuner i2c address */ + 0, /* dbx is optional */ + 0, + 0, + 0, /* EEProm type */ + 0, /* EEProm size */ + /* Tuner, Extern, Intern, Mute, Enabled */ +// { 0x1002, 0x1002, 0x3003, 0x3003, 0x3003 }, /* audio MUX values */ +// 0x300f }, /* GPIO mask */ + { 0x1002, 0x1002, 0x3003, 0x3003, 0x3003 }, /* audio MUX values */ + 0x300f }, /* GPIO mask */ }; struct bt848_card_sig bt848_card_signature[1]= { @@ -569,6 +583,7 @@ #define PCI_VENDOR_FLYVIDEO_2 0x1852 #define PCI_VENDOR_PINNACLE_ALT 0xBD11 #define PCI_VENDOR_IODATA 0x10fc +#define PCI_VENDOR_ATI 0x1002 #define MODEL_IODATA_GV_BCTV3_PCI 0x4020 @@ -713,6 +728,12 @@ bktr->card.eepromSize = (u_char)(256 / EEPROMBLOCKSIZE); goto checkTuner; } + if (subsystem_vendor_id == PCI_VENDOR_ATI) { + bktr->card = cards[ (card = CARD_TVWONDER) ]; + bktr->card.eepromAddr = eeprom_i2c_address; + bktr->card.eepromSize = (u_char)(256 / EEPROMBLOCKSIZE); + goto checkTuner; + } /* Vendor is unknown. We will use the standard probe code */ /* which may not give best results */ @@ -1131,6 +1152,11 @@ goto checkDBX; break; + case CARD_TVWONDER: + select_tuner( bktr, PHILIPS_NTSC ); /* ALPS_TSCH6, in fact. */ + goto checkDBX; + break; + } /* end switch(card) */ @@ -1274,6 +1300,10 @@ /* Enable PLL mode for Video Highway Xtreme users */ if (card == CARD_VIDEO_HIGHWAY_XTREME) + bktr->xtal_pll_mode = BT848_USE_PLL; + + /* Enable PLL mode for Video Highway Xtreme users */ + if (card == CARD_TVWONDER) bktr->xtal_pll_mode = BT848_USE_PLL; --- bktr_card.h Thu Aug 12 11:17:06 2004 +++ /local/src/sys/dev/bktr/bktr_card.h Thu Aug 12 08:41:55 2004 @@ -1,4 +1,4 @@ -/* $FreeBSD: /repoman/r/ncvs/src/sys/dev/bktr/bktr_card.h,v 1.7 2004/08/08 01:23:39 sanpei Exp $ */ +/* $FreeBSD: src/sys/dev/bktr/bktr_card.h,v 1.6 2003/02/02 17:46:00 orion Exp $ */ /* * This is part of the Driver for Video Capture Cards (Frame grabbers) @@ -76,9 +76,10 @@ #define CARD_ASKEY_DYNALINK_MAGIC_TVIEW 14 #define CARD_LEADTEK 15 #define CARD_TERRATVPLUS 16 -#define CARD_IO_BCTV3 17 -#define CARD_AOPEN_VA1000 18 -#define Bt848_MAX_CARD 19 +#define CARD_IO_BCTV3 17 +#define CARD_AOPEN_VA1000 18 +#define CARD_TVWONDER 19 +#define Bt848_MAX_CARD 20 #define CARD_IO_GV CARD_IO_BCTV2 --Apple-Mail-5-378674181-- --Apple-Mail-6-378674242 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.2.4 (Darwin) iD8DBQFBoVZlqt29EJDZlM4RAqorAKCc/wgQ/4a8dWq/0Ug6Tiv3F2pbCQCeOg0U fXk3VCrlREZY3lDOFwN/ML8= =Uod7 -----END PGP SIGNATURE----- --Apple-Mail-6-378674242-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 03:29:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76E0516A4CE; Mon, 22 Nov 2004 03:29:51 +0000 (GMT) Received: from corp.netease.com (corp.netease.com [202.106.186.34]) by mx1.FreeBSD.org (Postfix) with SMTP id 95F6A43D31; Mon, 22 Nov 2004 03:29:48 +0000 (GMT) (envelope-from zdou@corp.netease.com) Received: from zhedou (unknown [218.106.169.195]) by mail (Coremail) with SMTP id J0CUEDNdoUEeAKnD.2 for ; Mon, 22 Nov 2004 11:29:56 +0800 (CST) X-Originating-IP: [218.106.169.195] Date: Mon, 22 Nov 2004 11:29:42 +0800 From: "=?GB2312?B?8bzV3A==?=" To: "freebsd-questions" Organization: =?gb2312?B?zfjS1w==?= X-mailer: Foxmail 5.0 beta2 [cn] Mime-Version: 1.0 Message-Id: <20041122032948.95F6A43D31@mx1.FreeBSD.org> X-Mailman-Approved-At: Mon, 22 Nov 2004 13:31:31 +0000 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: buildadm cc: freebsd-current Subject: how to build duplex.iso? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 03:29:51 -0000 hi there, May i want to know how to make a cd_rom installation disk ISO image included both 4.10 and 5.3 in one disk like the FreeBSD/i386 duplex installation CD-ROM (about 550MB) disk in http://current.freebsd.org/. Thanks. From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 03:34:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F18EF16A4CE for ; Mon, 22 Nov 2004 03:34:38 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 852ED43D4C for ; Mon, 22 Nov 2004 03:34:38 +0000 (GMT) (envelope-from zhedou@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so174436rnf for ; Sun, 21 Nov 2004 19:34:38 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=EK7l/b62IWO7qJlHuPmBpyxt05cO8Tk7QjQxiUw4Mj8kRTX3b3w72QYDefO6YWao/tJd4YA/1RJmZ0irodbl0qsk7Fpr+rSkKEC8UJIIngf94xyNhb8R7leWhytzlSWm9OU+GWcyyfdM9JoIVvg8wZpWKT5Nz+sfhjF9f1/0+N4= Received: by 10.38.163.31 with SMTP id l31mr653915rne; Sun, 21 Nov 2004 19:34:37 -0800 (PST) Received: by 10.38.99.71 with HTTP; Sun, 21 Nov 2004 19:34:37 -0800 (PST) Message-ID: <64191124041121193463af35a@mail.gmail.com> Date: Mon, 22 Nov 2004 11:34:37 +0800 From: zhe dou To: freebsd-questions@freebsd.org, freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 22 Nov 2004 13:31:31 +0000 Subject: how to build duplex.iso? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: zhe dou List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 03:34:39 -0000 hi there, May i want to know how to make a cd_rom installation disk ISO image included both 4.10 and 5.3 in one disk like the FreeBSD/i386 duplex installation CD-ROM (about 550MB) disk in http://current.freebsd.org/. Thanks. From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 13:41:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 589E816A4CE for ; Mon, 22 Nov 2004 13:41:18 +0000 (GMT) Received: from peedub.jennejohn.org (J8164.j.pppool.de [85.74.129.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76C2643D3F for ; Mon, 22 Nov 2004 13:41:17 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.1/8.11.6) with ESMTP id iAMDfEcL004537; Mon, 22 Nov 2004 14:41:15 +0100 (CET) (envelope-from garyj@jennejohn.org) Message-Id: <200411221341.iAMDfEcL004537@peedub.jennejohn.org> X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Christoph Kukulies In-reply-to: Your message of "Sun, 21 Nov 2004 16:44:03 +0100." <200411211544.iALFi3Ys055538@www.kukulies.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Nov 2004 14:41:14 +0100 From: Gary Jennejohn cc: freebsd-current@freebsd.org Subject: Re: so cuaa0 devices are gone - why? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gary Jennejohn List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 13:41:18 -0000 Christoph Kukulies writes: > Just curious, why are cua serial devices now gone in 6.0? > Is it correct to switch to ttyd0 then? > They're now called cuad*. You really ought to read the list more often ;-) --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org garyj[at]denx.de From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 14:16:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F8A016A4CE for ; Mon, 22 Nov 2004 14:16:03 +0000 (GMT) Received: from corwin.easynet.fr (smarthost160.mail.easynet.fr [212.180.1.160]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF55B43D2F for ; Mon, 22 Nov 2004 14:16:01 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from [212.180.127.72] (helo=tatooine.tataz.chchile.org) by corwin.easynet.fr with esmtp (Exim 4.34) id 1CWEz0-0000cZ-8U; Mon, 22 Nov 2004 15:15:58 +0100 Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 66263412D; Mon, 22 Nov 2004 15:15:53 +0100 (CET) Date: Mon, 22 Nov 2004 15:15:52 +0100 From: Jeremie Le Hen To: Jeff Roberson Message-ID: <20041122141552.GC960@obiwan.tataz.chchile.org> References: <20041120000743.G18094@mail.chesapeake.net> <41A1C3BD.4010903@fer.hr> <20041122064318.Y18094@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041122064318.Y18094@mail.chesapeake.net> User-Agent: Mutt/1.5.6i X-Broken-Reverse-DNS: no host name found for IP address 212.180.127.72 cc: current@freebsd.org Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 14:16:03 -0000 > I haven't received any feedback from the list though. I hope people are > testing it. Perhaps the silence indicates universal success? :-) Would it be interesting to try your patch on a UP system ? To anticipate an hypotetical affirmative answer, I'm already recompiling my UP kernel with it. -- Jeremie Le Hen jeremie@le-hen.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 14:17:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48BD716A4CE; Mon, 22 Nov 2004 14:17:33 +0000 (GMT) Received: from juniper.fornext.org (53.35.138.210.xn.2iij.net [210.138.35.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7146743D46; Mon, 22 Nov 2004 14:17:32 +0000 (GMT) (envelope-from shino@fornext.org) Received: from [127.0.0.1] (thyme.fornext.org [192.168.3.32]) by juniper.fornext.org (Postfix) with ESMTP id BB5FB2A; Mon, 22 Nov 2004 23:17:30 +0900 (JST) Date: Mon, 22 Nov 2004 23:17:36 +0900 From: Shunsuke SHINOMIYA To: Matthew Dillon In-Reply-To: <20041122104527.5204.SHINO@fornext.org> References: <200411220038.iAM0c7JQ052589@apollo.backplane.com> <20041122104527.5204.SHINO@fornext.org> Message-Id: <20041122221011.CFF4.SHINO@fornext.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.12 [ja] cc: Jeremie Le Hen cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re[5]: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 14:17:33 -0000 I did FastEthernet throughput test by Smartbits with SmartApp. It's simpler than TCP throughput measurement. :) This Smartbits has some FastEthernet ports, has no GbE ports. The router is consist of single Xeon 2.4GHz which is HTT enabled and two on-boarded em interfaces. The kernel is 5.3-RELEASE with option SMP. if_em.c is version 1.44.2.3 with the sysctl-able patch. kern.random.sys.harvest.ethernet is set to 0. `Interrupt Moderation on' means the combination of parameters, hw.em?.rx_int_delay: 0 hw.em?.tx_int_delay: 66 hw.em?.rx_abs_int_delay: 66 hw.em?.tx_abs_int_delay: 66 hw.em?.int_throttle_ceil: 8000. `Interrupt Moderation off' means the combination of parameters, hw.em?.rx_int_delay: 0 hw.em?.tx_int_delay: 0 hw.em?.rx_abs_int_delay: 0 hw.em?.tx_abs_int_delay: 0 hw.em?.int_throttle_ceil: 0. `on/off' means input side interface(em0)'s moderation is `on' and output side interface(em1)'s moderation is `off'. hmm ..., the results of off/on are unstable. (A) ... Passed Rate(%) (B) ... Passed Rate(pps) Interrupt Moderation on/on Frame 1st Trial 2nd Trial 3rd Trial Size (A) (B) (A) (B) (A) (B) 64 28.14 41876 28.14 41876 28.14 41876 128 50.08 42301 49.50 41805 49.50 41806 256 93.24 42229 92.00 41666 92.62 41946 512 100.00 23496 100.00 23496 100.00 23496 1024 100.00 11973 100.00 11973 100.00 11973 1280 100.00 9615 100.00 9615 100.00 9615 1518 100.00 8127 100.00 8127 100.00 8127 Interrupt Moderation on/off Frame 1st Trial 2nd Trial 3rd Trial Size (A) (B) (A) (B) (A) (B) 64 28.14 41876 27.50 40916 28.14 41876 128 50.08 42301 48.85 41254 49.50 41806 256 93.24 42229 92.00 41666 92.62 41946 512 100.00 23496 100.00 23496 100.00 23496 1024 100.00 11973 100.00 11973 100.00 11973 1280 100.00 9615 100.00 9615 100.00 9615 1518 100.00 8127 100.00 8127 100.00 8127 Interrupt Moderation off/on Frame 1st Trial 2nd Trial 3rd Trial Size (B) (C) (B) (C) (B) (C) 64 100.00 148807 100.00 148807 99.41 147927 128 100.00 84458 55.74 47080 61.41 51867 256 100.00 45289 98.75 44722 100.00 45289 512 100.00 23496 100.00 23496 100.00 23496 1024 100.00 11973 100.00 11973 100.00 11973 1280 100.00 9615 100.00 9615 100.00 9615 1518 100.00 8127 100.00 8127 100.00 8127 Interrupt Moderation off/off Frame 1st Trial 2nd Trial 3rd Trial Size (B) (C) (B) (C) (B) (C) 64 81.55 121358 81.55 121358 82.35 122547 128 100.00 84458 100.00 84458 100.00 84458 256 100.00 45289 100.00 45289 100.00 45289 512 100.00 23496 100.00 23496 100.00 23496 1024 100.00 11973 100.00 11973 100.00 11973 1280 100.00 9615 100.00 9615 100.00 9615 1518 100.00 8127 100.00 8127 100.00 8127 -- Shunsuke SHINOMIYA From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 14:31:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 544A616A4CE for ; Mon, 22 Nov 2004 14:31:37 +0000 (GMT) Received: from avout3.midco.net (avout3.midco.net [24.220.0.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id C626543D54 for ; Mon, 22 Nov 2004 14:31:36 +0000 (GMT) (envelope-from pmes@bis.midco.net) Received: (qmail 23350 invoked by uid 1009); 22 Nov 2004 14:31:36 -0000 Received: from pmes@bis.midco.net by avout3 by uid 1003 with qmail-scanner-1.22 (f-prot: 4.4.2/3.14.11. Clear:RC:1(24.220.219.219):. Processed in 0.011838 secs); 22 Nov 2004 14:31:36 -0000 X-Qmail-Scanner-Mail-From: pmes@bis.midco.net via avout3 X-Qmail-Scanner: 1.22 (Clear:RC:1(24.220.219.219):. Processed in 0.011838 secs) Received: from host-219-219-220-24.midco.net (HELO [24.220.219.219]) ([24.220.219.219]) (envelope-sender ) by avout3.midco.net (qmail-ldap-1.03) with SMTP for ; 22 Nov 2004 14:31:36 -0000 In-Reply-To: <20041122141552.GC960@obiwan.tataz.chchile.org> References: <20041120000743.G18094@mail.chesapeake.net> <41A1C3BD.4010903@fer.hr> <20041122064318.Y18094@mail.chesapeake.net> <20041122141552.GC960@obiwan.tataz.chchile.org> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <3457D9D4-3C93-11D9-BAB4-000D936BE398@bis.midco.net> Content-Transfer-Encoding: 7bit From: Peter Schultz Date: Mon, 22 Nov 2004 08:31:32 -0600 To: Jeremie Le Hen X-Mailer: Apple Mail (2.619) cc: Jeff Roberson cc: current@freebsd.org Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 14:31:37 -0000 On Nov 22, 2004, at 8:15 AM, Jeremie Le Hen wrote: >> I haven't received any feedback from the list though. I hope people >> are >> testing it. Perhaps the silence indicates universal success? :-) > > Would it be interesting to try your patch on a UP system ? To > anticipate an hypotetical affirmative answer, I'm already recompiling > my > UP kernel with it. > > Reducing contention over the kernel is beneficial for any number of processors. Pete... From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 14:38:08 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE22C16A4CE for ; Mon, 22 Nov 2004 14:38:07 +0000 (GMT) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.FreeBSD.org (Postfix) with SMTP id 54B9843D2D for ; Mon, 22 Nov 2004 14:38:07 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 94531 invoked from network); 22 Nov 2004 14:38:06 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 22 Nov 2004 14:38:06 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iAMEc4eG036664 for ; Mon, 22 Nov 2004 15:38:05 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iAMEc4L4036663 for current@freebsd.org; Mon, 22 Nov 2004 15:38:04 +0100 (CET) (envelope-from pho) Date: Mon, 22 Nov 2004 15:38:04 +0100 From: Peter Holm To: current@freebsd.org Message-ID: <20041122143804.GA36649@peter.osted.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: panic: sleeping thread owns a non-sleepable lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 14:38:08 -0000 During stress test with GENERIC HEAD from Nov 20 08:40 UTC I got: Sleeping on "fdesc" with the following non-sleepable locks held: exclusive sleep mutex fdesc r = 0 (0xc08d15a0) locked @ kern/kern_descrip.c:2425 and then panic: sleeping thread (pid 92279) owns a non-sleepable lock http://www.holm.cc/stress/log/cons89.html -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 15:12:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 403F116A4CE; Mon, 22 Nov 2004 15:12:46 +0000 (GMT) Received: from castle.jp.FreeBSD.org (castle.jp.FreeBSD.org [210.226.20.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59C1C43D54; Mon, 22 Nov 2004 15:12:45 +0000 (GMT) (envelope-from matusita@jp.FreeBSD.org) Received: from galtvalion.matatabi.or.jp (localhost [127.0.0.1]) iAMFC9865002; Tue, 23 Nov 2004 00:12:09 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Date: Tue, 23 Nov 2004 00:12:08 +0900 Message-ID: From: Makoto Matsushita To: zhe dou In-Reply-To: <64191124041121193463af35a@mail.gmail.com> References: <64191124041121193463af35a@mail.gmail.com> User-Agent: Wanderlust/2.10.1 MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII cc: freebsd-current@freebsd.org cc: freebsd-questions@freebsd.org Subject: Re: how to build duplex.iso? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 15:12:46 -0000 > May i want to know how to make a cd_rom installation disk ISO image > included both 4.10 and 5.3 in one disk like the FreeBSD/i386 duplex > installation CD-ROM (about 550MB) disk in http://current.freebsd.org/. It's simple: include both distributions in one CD-ROM, and select which kernel to boot via loader(8). -- Makoto `MAR' MATSUSHITA From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 15:52:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 40FB616A4CE for ; Mon, 22 Nov 2004 15:52:20 +0000 (GMT) Received: from lakermmtao10.cox.net (lakermmtao10.cox.net [68.230.240.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F93043D2D for ; Mon, 22 Nov 2004 15:52:19 +0000 (GMT) (envelope-from mkucenski@cox.net) Received: from smtp.east.cox.net ([172.18.52.53]) by lakermmtao10.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with SMTP <20041122155219.FXMV13256.lakermmtao10.cox.net@smtp.east.cox.net>; Mon, 22 Nov 2004 10:52:19 -0500 X-Mailer: Openwave WebEngine, version 2.8.15 (webedge20-101-1103-20040528) From: Matt Kucenski To: =?ISO-8859-1?B?U/hyZW4=?= Schmidt Date: Mon, 22 Nov 2004 10:52:18 -0500 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=____1101138738449_jKBLwFxi+K" Message-Id: <20041122155219.FXMV13256.lakermmtao10.cox.net@smtp.east.cox.net> cc: freebsd-current@freebsd.org Subject: Re: Re: ATAng support for reading from register on ATAREQUEST command? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: m.kucenski@computer.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 15:52:20 -0000 This is a multi-part message in MIME format. ------=____1101138738449_jKBLwFxi+K Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Thanks, I was able to get those changes into my source and they work fine. Unfortunately, I overlooked the fact that Read Native Max Address returns part of the address in the Device register as well as the three lba registers. Evidently bits 27:24 of the native address come back in the bottom 4 bits of the device register. Is that register easily accessible somewhere? -Matt > > From: Søren Schmidt > Date: 2004/11/21 Sun AM 07:00:27 EST > To: m.kucenski@computer.org > CC: freebsd-current@freebsd.org > Subject: Re: ATAng support for reading from register on ATAREQUEST command? > > Matt Kucenski wrote: > > I am trying to develop a program that will allow modifications to the Host Protected Area settings and one of the commands (READ NATIVE MAX ADDRESS) returns the native max address back in the register (LBA high, low, mid). > > > > I have been looking at the smartmontools project for pointers on how to write this code and according to that source, this is not possible yet with ATAng. There is a comment in their code that another command (ATA_CMD_READ_REG) patch has been submitted to ATAng, but it does not appear to have made it into any of the latest sources. > > > > Can anyone offer any information on this? > > The following patch returns the register values in the request you sent > through ioctl call. That should do the trick without any new calls.. > > > -- > > -Søren > > > ------=____1101138738449_jKBLwFxi+K Content-Type: text/plain; name="ata-smart-patch" Content-Disposition: inline; filename="ata-smart-patch" Index: ata-all.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v retrieving revision 1.233 diff -u -r1.233 ata-all.c --- ata-all.c 19 Oct 2004 20:13:38 -0000 1.233 +++ ata-all.c 19 Nov 2004 18:59:55 -0000 @@ -546,10 +546,10 @@ bcopy(iocmd->u.request.u.atapi.ccb, request->u.atapi.ccb, 16); } else { - request->u.ata.command = iocmd->u.request.u.ata.command; - request->u.ata.feature = iocmd->u.request.u.ata.feature; - request->u.ata.lba = iocmd->u.request.u.ata.lba; - request->u.ata.count = iocmd->u.request.u.ata.count; + request->u.ata.command = iocmd->u.request.u.ata.command; + request->u.ata.feature = iocmd->u.request.u.ata.feature; + request->u.ata.lba = iocmd->u.request.u.ata.lba; + request->u.ata.count = iocmd->u.request.u.ata.count; } request->timeout = iocmd->u.request.timeout; @@ -566,6 +566,10 @@ ata_queue_request(request); + iocmd->u.request.u.ata.command = request->u.ata.command; + iocmd->u.request.u.ata.feature = request->u.ata.feature; + iocmd->u.request.u.ata.lba = request->u.ata.lba; + iocmd->u.request.u.ata.count = request->u.ata.count; if (request->result) iocmd->u.request.error = request->result; else { ------=____1101138738449_jKBLwFxi+K-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 18:27:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 079E916A4CE for ; Mon, 22 Nov 2004 18:27:43 +0000 (GMT) Received: from peedub.jennejohn.org (Ja3df.j.pppool.de [85.74.163.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39F9843D48 for ; Mon, 22 Nov 2004 18:27:42 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.1/8.11.6) with ESMTP id iAMIRaq4009545; Mon, 22 Nov 2004 19:27:37 +0100 (CET) (envelope-from garyj@jennejohn.org) Message-Id: <200411221827.iAMIRaq4009545@peedub.jennejohn.org> X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: current@freebsd.org In-reply-to: Your message of "Mon, 22 Nov 2004 08:31:32 CST." <3457D9D4-3C93-11D9-BAB4-000D936BE398@bis.midco.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Nov 2004 19:27:36 +0100 From: Gary Jennejohn cc: jroberson@chesapeake.net Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gary Jennejohn List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 18:27:43 -0000 Peter Schultz writes: > On Nov 22, 2004, at 8:15 AM, Jeremie Le Hen wrote: > > >> I haven't received any feedback from the list though. I hope people > >> are > >> testing it. Perhaps the silence indicates universal success? :-) > > > > Would it be interesting to try your patch on a UP system ? To > > anticipate an hypotetical affirmative answer, I'm already recompiling > > my > > UP kernel with it. > > > > > Reducing contention over the kernel is beneficial for any number of > processors. > With a tree just updated per cvsup about 30 minutes ago: root:peedub:sys:bash:8> patch < ~/freebsd/smpffs.diff root:peedub:sys:bash:7> find . -type f -name \*.rej | xargs ls -l -rw-r--r-- 1 root wheel 539 Nov 22 19:22 ./kern/init_sysent.c.rej -rw-r--r-- 1 root wheel 522 Nov 22 19:22 ./kern/syscalls.c.rej -rw-r--r-- 1 root wheel 524 Nov 22 19:22 ./sys/syscall.h.rej -rw-r--r-- 1 root wheel 557 Nov 22 19:22 ./sys/syscall.mk.rej -rw-r--r-- 1 root wheel 531 Nov 22 19:22 ./sys/sysproto.h.rej :-( I have the latest (only?) vesion of the patch. --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org garyj[at]denx.de From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 19:01:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DF4216A4CE for ; Mon, 22 Nov 2004 19:01:48 +0000 (GMT) Received: from corwin.easynet.fr (smarthost160.mail.easynet.fr [212.180.1.160]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC7E543D5E for ; Mon, 22 Nov 2004 19:01:47 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from [212.180.127.72] (helo=tatooine.tataz.chchile.org) by corwin.easynet.fr with esmtp (Exim 4.34) id 1CWJRY-0005yS-1Q; Mon, 22 Nov 2004 20:01:44 +0100 Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 9B2CB412D; Mon, 22 Nov 2004 20:01:37 +0100 (CET) Date: Mon, 22 Nov 2004 20:01:37 +0100 From: Jeremie Le Hen To: Gary Jennejohn Message-ID: <20041122190137.GE960@obiwan.tataz.chchile.org> References: <3457D9D4-3C93-11D9-BAB4-000D936BE398@bis.midco.net> <200411221827.iAMIRaq4009545@peedub.jennejohn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200411221827.iAMIRaq4009545@peedub.jennejohn.org> User-Agent: Mutt/1.5.6i X-Broken-Reverse-DNS: no host name found for IP address 212.180.127.72 cc: jroberson@chesapeake.net cc: current@freebsd.org Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 19:01:48 -0000 > root:peedub:sys:bash:8> patch < ~/freebsd/smpffs.diff > root:peedub:sys:bash:7> find . -type f -name \*.rej | xargs ls -l > -rw-r--r-- 1 root wheel 539 Nov 22 19:22 ./kern/init_sysent.c.rej > -rw-r--r-- 1 root wheel 522 Nov 22 19:22 ./kern/syscalls.c.rej > -rw-r--r-- 1 root wheel 524 Nov 22 19:22 ./sys/syscall.h.rej > -rw-r--r-- 1 root wheel 557 Nov 22 19:22 ./sys/syscall.mk.rej > -rw-r--r-- 1 root wheel 531 Nov 22 19:22 ./sys/sysproto.h.rej You should not take care of these conflicts ; if you have a look at them, this is just a problem with the "$FreeBSD$" RCS keyword. Good luck :-). Regards, -- Jeremie Le Hen jeremie@le-hen.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 19:39:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC5BE16A4CE for ; Mon, 22 Nov 2004 19:39:20 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8102243D41 for ; Mon, 22 Nov 2004 19:39:20 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iAMJdIC7085069; Mon, 22 Nov 2004 11:39:18 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iAMJdI1L085068; Mon, 22 Nov 2004 11:39:18 -0800 (PST) (envelope-from sgk) Date: Mon, 22 Nov 2004 11:39:18 -0800 From: Steve Kargl To: Gary Jennejohn Message-ID: <20041122193917.GA85040@troutmask.apl.washington.edu> References: <3457D9D4-3C93-11D9-BAB4-000D936BE398@bis.midco.net> <200411221827.iAMIRaq4009545@peedub.jennejohn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200411221827.iAMIRaq4009545@peedub.jennejohn.org> User-Agent: Mutt/1.4.1i cc: jroberson@chesapeake.net cc: current@freebsd.org Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 19:39:20 -0000 On Mon, Nov 22, 2004 at 07:27:36PM +0100, Gary Jennejohn wrote: > Peter Schultz writes: > > On Nov 22, 2004, at 8:15 AM, Jeremie Le Hen wrote: > > > > >> I haven't received any feedback from the list though. I hope people > > >> are > > >> testing it. Perhaps the silence indicates universal success? :-) > > > > > > Would it be interesting to try your patch on a UP system ? To > > > anticipate an hypotetical affirmative answer, I'm already recompiling > > > my > > > UP kernel with it. > > > > > > > > Reducing contention over the kernel is beneficial for any number of > > processors. > > > > With a tree just updated per cvsup about 30 minutes ago: > > root:peedub:sys:bash:8> patch < ~/freebsd/smpffs.diff > root:peedub:sys:bash:7> find . -type f -name \*.rej | xargs ls -l > -rw-r--r-- 1 root wheel 539 Nov 22 19:22 ./kern/init_sysent.c.rej > -rw-r--r-- 1 root wheel 522 Nov 22 19:22 ./kern/syscalls.c.rej > -rw-r--r-- 1 root wheel 524 Nov 22 19:22 ./sys/syscall.h.rej > -rw-r--r-- 1 root wheel 557 Nov 22 19:22 ./sys/syscall.mk.rej > -rw-r--r-- 1 root wheel 531 Nov 22 19:22 ./sys/sysproto.h.rej > > :-( > > I have the latest (only?) vesion of the patch. > The rejected portions do not effect the patch. It appears to be differences in the expansion of $FreeBSD$. I've been running a kernel with this patch on a UP system. It has exhibited no problems during a "make -j 2 buildworld", a re-installation of all ports on the system, and a build and make check of the GCC cvs source tree. -- Steve From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 20:14:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7944316A4CF for ; Mon, 22 Nov 2004 20:14:10 +0000 (GMT) Received: from lara.cc.fer.hr (lara.cc.fer.hr [161.53.72.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9B9443D41 for ; Mon, 22 Nov 2004 20:14:09 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [127.0.0.1] (localhost.cc.fer.hr [127.0.0.1]) by lara.cc.fer.hr (8.13.1/8.13.1) with ESMTP id iAMKE7qq001762 for ; Mon, 22 Nov 2004 21:14:08 +0100 (CET) (envelope-from ivoras@fer.hr) Message-ID: <41A2488F.8030802@fer.hr> Date: Mon, 22 Nov 2004 21:14:07 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 0.9 (X11/20041111) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: gvinum panic? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 20:14:10 -0000 I'm consistently getting a system panic, trap #12 in process g_event when I try: # gvinum create vinumconf where vinumconf contains: drive ad4 device /dev/ad4a drive ad5 device /dev/ad5a drive ad6 device /dev/ad6a volume homes plex org raid5 336k sd length 50g drive ad4 sd length 50g drive ad5 sd length 50g drive ad6 volume services plex org raid5 336k sd length 20g drive ad4 sd length 20g drive ad5 sd length 20g drive ad6 volume storage plex org raid5 336k sd length 0 drive ad4 sd length 0 drive ad5 sd length 0 drive ad6 The same works ok with regular vinum. I'm totally new to (g)vinum, so I could very well be doing something wrong here :) (ad4,5,6 are 80GB discs) I'm running 5-STABLE from few hours ago. From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 20:14:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6140616A4CE; Mon, 22 Nov 2004 20:14:11 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05C4D43D1D; Mon, 22 Nov 2004 20:14:11 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 94354F2102; Mon, 22 Nov 2004 12:14:08 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 77020-04; Mon, 22 Nov 2004 12:14:06 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id B03CFF20DF; Mon, 22 Nov 2004 12:14:06 -0800 (PST) From: Sean McNeil To: Robert Watson In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-5JFyiJ/y9VFBOBUn+7tM" Date: Mon, 22 Nov 2004 12:14:06 -0800 Message-Id: <1101154446.79991.13.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-stable@freebsd.org cc: freebsd-current@freebsd.org cc: Jeremie Le Hen Subject: Re: Re[4]: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 20:14:11 -0000 --=-5JFyiJ/y9VFBOBUn+7tM Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2004-11-22 at 11:34 +0000, Robert Watson wrote: > On Sun, 21 Nov 2004, Sean McNeil wrote: >=20 > > I have to disagree. Packet loss is likely according to some of my > > tests. With the re driver, no change except placing a 100BT setup with > > no packet loss to a gigE setup (both linksys switches) will cause > > serious packet loss at 20Mbps data rates. I have discovered the only > > way to get good performance with no packet loss was to > >=20 > > 1) Remove interrupt moderation > > 2) defrag each mbuf that comes in to the driver. >=20 > Sounds like you're bumping into a queue limit that is made worse by > interrupting less frequently, resulting in bursts of packets that are > relatively large, rather than a trickle of packets at a higher rate. > Perhaps a limit on the number of outstanding descriptors in the driver or > hardware and/or a limit in the netisr/ifqueue queue depth. You might try > changing the default IFQ_MAXLEN from 50 to 128 to increase the size of th= e > ifnet and netisr queues. You could also try setting net.isr.enable=3D1 t= o > enable direct dispatch, which in the in-bound direction would reduce the > number of context switches and queueing. It sounds like the device drive= r > has a limit of 256 receive and transmit descriptors, which one supposes i= s > probably derived from the hardware limit, but I have no documentation on > hand so can't confirm that. I've tried bumping IFQ_MAXLEN and it made no difference. I could rerun this test to be 100% certain I suppose. It was done a while back. I haven't tried net.isr.enable=3D1, but packet loss is in the transmission direction. The device driver has been modified to have 1024 transmit and receive descriptors each as that is the hardware limitation. That didn't matter either. With 1024 descriptors I still lost packets without the m_defrag. The most difficult thing for me to understand is: if this is some sort of resource limitation why will it work with a slower phy layer perfectly and not with the gigE? The only thing I could think of was that the old driver was doing m_defrag calls when it filled the transmit descriptor queues up to a certain point. Understanding the effects of m_defrag would be helpful in figuring this out I suppose. > It would be interesting on the send and receive sides to inspect the > counters for drops at various points in the network stack; i.e., are we > dropping packets at the ifq handoff because we're overfilling the > descriptors in the driver, are packets dropped on the inbound path going > into the netisr due to over-filling before the netisr is scheduled, etc.=20 > And, it's probably interesting to look at stats on filling the socket > buffers for the same reason: if bursts of packets come up the stack, the > socket buffers could well be being over-filled before the user thread can > run. Yes, this would be very interesting and should point out the problem. I would do such a thing if I had enough knowledge of the network pathways. Alas, I am very green in this area. The receive side has no issues, though, so I would focus on transmit counters (with assistance). --=-5JFyiJ/y9VFBOBUn+7tM Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBokiOyQsGN30uGE4RAtJzAJ9rx309a8+iQkElTKKX/GsS+26kuACg6plM uFItZxBt9UmaClVTPWVq89U= =yhZ0 -----END PGP SIGNATURE----- --=-5JFyiJ/y9VFBOBUn+7tM-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 20:43:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CEA016A4CE for ; Mon, 22 Nov 2004 20:43:46 +0000 (GMT) Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4525443D31 for ; Mon, 22 Nov 2004 20:43:46 +0000 (GMT) (envelope-from robin.blanchard@gactr.uga.edu) Received: from localhost (localhost [127.0.0.1]) by mail.gactr.uga.edu (Postfix) with ESMTP id C1B77DA927 for ; Mon, 22 Nov 2004 15:43:43 -0500 (EST) Received: from mail.gactr.uga.edu ([127.0.0.1]) by localhost (mail.gactr.uga.edu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 03968-01-10 for ; Mon, 22 Nov 2004 15:43:43 -0500 (EST) Received: from EBE1.gc.nat (E2K1.gc.nat [10.10.11.21]) by mail.gactr.uga.edu (Postfix) with ESMTP id 52FB6DA924 for ; Mon, 22 Nov 2004 15:43:43 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Mon, 22 Nov 2004 15:43:42 -0500 Message-ID: <9B5C1FCAFB35084787C21EFFFA78DD9E7D6517@EBE1.gc.nat> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: udp_usrreq.c,v 1.162.2.4 Thread-Index: AcTQ0/RGk6yMCMV4Sb+yFFoEKWJE9g== From: "Robin P. Blanchard" To: X-Virus-Scanned: by amavisd-new at gactr.uga.edu Subject: udp_usrreq.c,v 1.162.2.4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 20:43:46 -0000 Cannot build releng_5 with said file... cc -c -O2 -pipe -fno-strict-aliasing -fno-strict-aliasing = -march=3Dpentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=3Dc99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=3D8000 --param inline-unit-growth=3D100 --param large-function-growth=3D1000 -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=3D2 -ffreestanding -Werror /usr/src/sys/netinet/udp_usrreq.c /usr/src/sys/netinet/udp_usrreq.c: In function `udp_append': /usr/src/sys/netinet/udp_usrreq.c:421: warning: unused variable = `udp_in6' *** Error code 1 --------------------------------------- Robin P. Blanchard Systems Integration Specialist Georgia Center for Continuing Education fon: 706.542.2404 < > fax: 706.542.6546 --------------------------------------- From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 20:53:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6271216A4CE for ; Mon, 22 Nov 2004 20:53:04 +0000 (GMT) Received: from imap.univie.ac.at (mailbox-lmtp.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DC7C43D31 for ; Mon, 22 Nov 2004 20:53:03 +0000 (GMT) (envelope-from le@FreeBSD.org) Received: from korben.prv.univie.ac.at (korben.prv.univie.ac.at [131.130.7.98]) by imap.univie.ac.at (8.12.10/8.12.10) with ESMTP id iAMKqt6u163138; Mon, 22 Nov 2004 21:52:57 +0100 Date: Mon, 22 Nov 2004 21:52:57 +0100 (CET) From: Lukas Ertl To: Ivan Voras In-Reply-To: <41A2488F.8030802@fer.hr> Message-ID: <20041122215228.J568@korben.in.tern> References: <41A2488F.8030802@fer.hr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-DCC-ZID-Univie-Metrics: mx7.univie.ac.at 4248; Body=2 Fuz1=2 Fuz2=2 cc: current@FreeBSD.org Subject: Re: gvinum panic? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 20:53:04 -0000 On Mon, 22 Nov 2004, Ivan Voras wrote: > I'm consistently getting a system panic, trap #12 in process g_event when I > try: Are you sure that kernel (modules) and userland are in sync? cheers, le -- Lukas Ertl http://homepage.univie.ac.at/l.ertl/ le@FreeBSD.org http://people.freebsd.org/~le/ From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 21:31:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E344716A4CE for ; Mon, 22 Nov 2004 21:31:10 +0000 (GMT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 970AB43D55 for ; Mon, 22 Nov 2004 21:31:10 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 15864 invoked from network); 22 Nov 2004 21:31:10 -0000 Received: from gate.funkthat.com (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 22 Nov 2004 21:31:10 -0000 Received: from hydrogen.funkthat.com (zebixs@localhost.funkthat.com [127.0.0.1])iAMLV9B6005705; Mon, 22 Nov 2004 13:31:09 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id iAMLV8en005704; Mon, 22 Nov 2004 13:31:08 -0800 (PST) Date: Mon, 22 Nov 2004 13:31:08 -0800 From: John-Mark Gurney To: Sean McNeil Message-ID: <20041122213108.GY57546@funkthat.com> Mail-Followup-To: Sean McNeil , Robert Watson , freebsd-stable@freebsd.org, freebsd-current@freebsd.org, Jeremie Le Hen References: <1101154446.79991.13.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1101154446.79991.13.camel@server.mcneil.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: Jeremie Le Hen cc: freebsd-stable@freebsd.org cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: Re[4]: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 21:31:11 -0000 Sean McNeil wrote this message on Mon, Nov 22, 2004 at 12:14 -0800: > On Mon, 2004-11-22 at 11:34 +0000, Robert Watson wrote: > > On Sun, 21 Nov 2004, Sean McNeil wrote: > > > > > I have to disagree. Packet loss is likely according to some of my > > > tests. With the re driver, no change except placing a 100BT setup with > > > no packet loss to a gigE setup (both linksys switches) will cause > > > serious packet loss at 20Mbps data rates. I have discovered the only > > > way to get good performance with no packet loss was to > > > > > > 1) Remove interrupt moderation > > > 2) defrag each mbuf that comes in to the driver. > > > > Sounds like you're bumping into a queue limit that is made worse by > > interrupting less frequently, resulting in bursts of packets that are > > relatively large, rather than a trickle of packets at a higher rate. > > Perhaps a limit on the number of outstanding descriptors in the driver or > > hardware and/or a limit in the netisr/ifqueue queue depth. You might try > > changing the default IFQ_MAXLEN from 50 to 128 to increase the size of the > > ifnet and netisr queues. You could also try setting net.isr.enable=1 to > > enable direct dispatch, which in the in-bound direction would reduce the > > number of context switches and queueing. It sounds like the device driver > > has a limit of 256 receive and transmit descriptors, which one supposes is > > probably derived from the hardware limit, but I have no documentation on > > hand so can't confirm that. > > I've tried bumping IFQ_MAXLEN and it made no difference. I could rerun And the default for if_re is RL_IFQ_MAXLEN which is already 512... As is mentioned below, the card can do 64 segments (which usually means 32 packets since each packet usually has a header + payload in seperate packets)... > this test to be 100% certain I suppose. It was done a while back. I > haven't tried net.isr.enable=1, but packet loss is in the transmission > direction. The device driver has been modified to have 1024 transmit > and receive descriptors each as that is the hardware limitation. That > didn't matter either. With 1024 descriptors I still lost packets > without the m_defrag. hmmm... you know, I wonder if this is a problem with the if_re not pulling enough data from memory before starting the transmit... Though we currently have it set for unlimited... so, that doesn't seem like it would be it.. > The most difficult thing for me to understand is: if this is some sort > of resource limitation why will it work with a slower phy layer > perfectly and not with the gigE? The only thing I could think of was > that the old driver was doing m_defrag calls when it filled the transmit > descriptor queues up to a certain point. Understanding the effects of > m_defrag would be helpful in figuring this out I suppose. maybe the chip just can't keep the transmit fifo loaded at the higher speeds... is it possible vls is doing a writev for multisegmented UDP packet? I'll have to look at this again... > > It would be interesting on the send and receive sides to inspect the > > counters for drops at various points in the network stack; i.e., are we > > dropping packets at the ifq handoff because we're overfilling the > > descriptors in the driver, are packets dropped on the inbound path going > > into the netisr due to over-filling before the netisr is scheduled, etc. > > And, it's probably interesting to look at stats on filling the socket > > buffers for the same reason: if bursts of packets come up the stack, the > > socket buffers could well be being over-filled before the user thread can > > run. > > Yes, this would be very interesting and should point out the problem. I > would do such a thing if I had enough knowledge of the network pathways. > Alas, I am very green in this area. The receive side has no issues, > though, so I would focus on transmit counters (with assistance). -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 21:51:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE97916A4CE for ; Mon, 22 Nov 2004 21:51:44 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 494D543D46 for ; Mon, 22 Nov 2004 21:51:43 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAMLnusl069891; Mon, 22 Nov 2004 16:49:56 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iAMLntff069888; Mon, 22 Nov 2004 21:49:55 GMT (envelope-from robert@fledge.watson.org) Date: Mon, 22 Nov 2004 21:49:55 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Robin P. Blanchard" In-Reply-To: <9B5C1FCAFB35084787C21EFFFA78DD9E7D6517@EBE1.gc.nat> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: udp_usrreq.c,v 1.162.2.4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 21:51:44 -0000 On Mon, 22 Nov 2004, Robin P. Blanchard wrote: > Cannot build releng_5 with said file... This is because you're building without INET6 in your kernel config, and that commit contains a bug wherein there's an unused variable in the event that INET6 isn't compiled in. I did a follow up commit shortly afterwards to merge the commit that fixed that in the original (and that I accidentally didn't merge), so you likely just caught the bad window. Try cvsuping again? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research > > cc -c -O2 -pipe -fno-strict-aliasing -fno-strict-aliasing -march=pentiumpro > -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys > -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/altq > -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf > -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd > -I/usr/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common > -finline-limit=8000 --param inline-unit-growth=100 --param > large-function-growth=1000 -fno-builtin -mno-align-long-strings > -mpreferred-stack-boundary=2 -ffreestanding -Werror > /usr/src/sys/netinet/udp_usrreq.c > /usr/src/sys/netinet/udp_usrreq.c: In function `udp_append': > /usr/src/sys/netinet/udp_usrreq.c:421: warning: unused variable `udp_in6' > *** Error code 1 > > > > --------------------------------------- > Robin P. Blanchard > Systems Integration Specialist > Georgia Center for Continuing Education > fon: 706.542.2404 < > fax: 706.542.6546 > --------------------------------------- > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 22:00:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25CA016A4CE for ; Mon, 22 Nov 2004 22:00:00 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCF7743D2D for ; Mon, 22 Nov 2004 21:59:59 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 11288 invoked from network); 22 Nov 2004 21:59:59 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 22 Nov 2004 21:59:59 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAMLxdYi030036; Mon, 22 Nov 2004 16:59:48 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Mon, 22 Nov 2004 16:44:57 -0500 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411221644.57047.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: "Bjoern A. Zeeb" cc: FreeBSD current mailing list Subject: Re: mem leak in mii ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 22:00:00 -0000 On Friday 19 November 2004 06:49 pm, Bjoern A. Zeeb wrote: > Hi, > > in sys/dev/mii/mii.c there are two calls to malloc for ivars; > see for example mii_phy_probe: > > v = malloc(sizeof(vm_offset_t) * 2, M_DEVBUF, M_NOWAIT); > if (v == 0) { > return (ENOMEM); > } > v[0] = ifmedia_upd; > v[1] = ifmedia_sts; > *child = device_add_child(dev, "miibus", -1); > device_set_ivars(*child, v); > > Where is the free for this malloc ? I cannot find it. > > analogous: miibus_probe ? It's a leak. It should be free'd when the miibus device is destroyed. Here's a possible fix: Index: dev/mii/mii.c =================================================================== RCS file: /usr/cvs/src/sys/dev/mii/mii.c,v retrieving revision 1.20 diff -u -r1.20 mii.c --- dev/mii/mii.c 15 Aug 2004 06:24:40 -0000 1.20 +++ dev/mii/mii.c 22 Nov 2004 21:43:40 -0000 @@ -186,11 +186,15 @@ device_t dev; { struct mii_data *mii; + void **v; bus_generic_detach(dev); mii = device_get_softc(dev); ifmedia_removeall(&mii->mii_media); mii->mii_ifp = NULL; + v = device_get_ivars(dev); + device_set_ivars(dev, NULL); + free(v, M_DEVBUF); return(0); } @@ -325,6 +329,7 @@ if (i == MII_NPHY) { device_delete_child(dev, *child); + free(v, M_DEVBUF); *child = NULL; return(ENXIO); } -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 22:00:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E5ED16A4CE for ; Mon, 22 Nov 2004 22:00:00 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FABA43D41 for ; Mon, 22 Nov 2004 22:00:00 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 11288 invoked from network); 22 Nov 2004 21:59:59 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 22 Nov 2004 21:59:59 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAMLxdYi030036; Mon, 22 Nov 2004 16:59:48 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Mon, 22 Nov 2004 16:44:57 -0500 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411221644.57047.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: "Bjoern A. Zeeb" cc: FreeBSD current mailing list Subject: Re: mem leak in mii ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 22:00:00 -0000 On Friday 19 November 2004 06:49 pm, Bjoern A. Zeeb wrote: > Hi, > > in sys/dev/mii/mii.c there are two calls to malloc for ivars; > see for example mii_phy_probe: > > v = malloc(sizeof(vm_offset_t) * 2, M_DEVBUF, M_NOWAIT); > if (v == 0) { > return (ENOMEM); > } > v[0] = ifmedia_upd; > v[1] = ifmedia_sts; > *child = device_add_child(dev, "miibus", -1); > device_set_ivars(*child, v); > > Where is the free for this malloc ? I cannot find it. > > analogous: miibus_probe ? It's a leak. It should be free'd when the miibus device is destroyed. Here's a possible fix: Index: dev/mii/mii.c =================================================================== RCS file: /usr/cvs/src/sys/dev/mii/mii.c,v retrieving revision 1.20 diff -u -r1.20 mii.c --- dev/mii/mii.c 15 Aug 2004 06:24:40 -0000 1.20 +++ dev/mii/mii.c 22 Nov 2004 21:43:40 -0000 @@ -186,11 +186,15 @@ device_t dev; { struct mii_data *mii; + void **v; bus_generic_detach(dev); mii = device_get_softc(dev); ifmedia_removeall(&mii->mii_media); mii->mii_ifp = NULL; + v = device_get_ivars(dev); + device_set_ivars(dev, NULL); + free(v, M_DEVBUF); return(0); } @@ -325,6 +329,7 @@ if (i == MII_NPHY) { device_delete_child(dev, *child); + free(v, M_DEVBUF); *child = NULL; return(ENXIO); } -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 22:00:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94EAD16A4CF for ; Mon, 22 Nov 2004 22:00:02 +0000 (GMT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4381743D1F for ; Mon, 22 Nov 2004 22:00:02 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 20559 invoked from network); 22 Nov 2004 22:00:02 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 22 Nov 2004 22:00:01 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAMLxdYj030036; Mon, 22 Nov 2004 16:59:58 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Peter Holm Date: Mon, 22 Nov 2004 16:57:36 -0500 User-Agent: KMail/1.6.2 References: <20041122143804.GA36649@peter.osted.lan> In-Reply-To: <20041122143804.GA36649@peter.osted.lan> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200411221657.36659.jhb@FreeBSD.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: current@FreeBSD.org cc: phk@FreeBSD.org Subject: Re: panic: sleeping thread owns a non-sleepable lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 22:00:02 -0000 On Monday 22 November 2004 09:38 am, Peter Holm wrote: > During stress test with GENERIC HEAD from Nov 20 08:40 UTC I got: > Sleeping on "fdesc" with the following non-sleepable locks held: > exclusive sleep mutex fdesc r = 0 (0xc08d15a0) locked @ > kern/kern_descrip.c:2425 and then > panic: sleeping thread (pid 92279) owns a non-sleepable lock > > http://www.holm.cc/stress/log/cons89.html Yes, the panic is a result of the earlier warning. Poul-Henning touched this code last, so it is probably something for him to look at. I'm unsure how msleep() is getting called, however. The turnstile panic is not important, can you find the thread that went to sleep (should be pid 92279) and get stack trace for that? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 22:07:50 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0F1516A4CE; Mon, 22 Nov 2004 22:07:50 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DC5743D45; Mon, 22 Nov 2004 22:07:50 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 2CAE7F20C8; Mon, 22 Nov 2004 14:07:48 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02658-03; Mon, 22 Nov 2004 14:07:46 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 53B63F1802; Mon, 22 Nov 2004 14:07:46 -0800 (PST) From: Sean McNeil To: John-Mark Gurney In-Reply-To: <20041122213108.GY57546@funkthat.com> References: <1101154446.79991.13.camel@server.mcneil.com> <20041122213108.GY57546@funkthat.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Neck75QEDKh+GjKidRwQ" Date: Mon, 22 Nov 2004 14:07:45 -0800 Message-Id: <1101161265.3317.9.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com cc: Jeremie Le Hen cc: freebsd-stable@freebsd.org cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: Re[4]: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 22:07:51 -0000 --=-Neck75QEDKh+GjKidRwQ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi John-Mark, On Mon, 2004-11-22 at 13:31 -0800, John-Mark Gurney wrote: > Sean McNeil wrote this message on Mon, Nov 22, 2004 at 12:14 -0800: > > On Mon, 2004-11-22 at 11:34 +0000, Robert Watson wrote: > > > On Sun, 21 Nov 2004, Sean McNeil wrote: > > >=20 > > > > I have to disagree. Packet loss is likely according to some of my > > > > tests. With the re driver, no change except placing a 100BT setup = with > > > > no packet loss to a gigE setup (both linksys switches) will cause > > > > serious packet loss at 20Mbps data rates. I have discovered the on= ly > > > > way to get good performance with no packet loss was to > > > >=20 > > > > 1) Remove interrupt moderation > > > > 2) defrag each mbuf that comes in to the driver. > > >=20 > > > Sounds like you're bumping into a queue limit that is made worse by > > > interrupting less frequently, resulting in bursts of packets that are > > > relatively large, rather than a trickle of packets at a higher rate. > > > Perhaps a limit on the number of outstanding descriptors in the drive= r or > > > hardware and/or a limit in the netisr/ifqueue queue depth. You might= try > > > changing the default IFQ_MAXLEN from 50 to 128 to increase the size o= f the > > > ifnet and netisr queues. You could also try setting net.isr.enable= =3D1 to > > > enable direct dispatch, which in the in-bound direction would reduce = the > > > number of context switches and queueing. It sounds like the device d= river > > > has a limit of 256 receive and transmit descriptors, which one suppos= es is > > > probably derived from the hardware limit, but I have no documentation= on > > > hand so can't confirm that. > >=20 > > I've tried bumping IFQ_MAXLEN and it made no difference. I could rerun >=20 > And the default for if_re is RL_IFQ_MAXLEN which is already 512... As > is mentioned below, the card can do 64 segments (which usually means 32 > packets since each packet usually has a header + payload in seperate > packets)... It sounds like you believe this is an if_re-only problem. I had the feeling that the if_em driver performance problems were related in some way. I noticed that if_em does not do anything with m_defrag and thought it might be a little more than coincidence. > > this test to be 100% certain I suppose. It was done a while back. I > > haven't tried net.isr.enable=3D1, but packet loss is in the transmissio= n > > direction. The device driver has been modified to have 1024 transmit > > and receive descriptors each as that is the hardware limitation. That > > didn't matter either. With 1024 descriptors I still lost packets > > without the m_defrag. >=20 > hmmm... you know, I wonder if this is a problem with the if_re not > pulling enough data from memory before starting the transmit... Though > we currently have it set for unlimited... so, that doesn't seem like it > would be it.. Right. Plus it now has 1024 descriptors on my machine and, like I said, made little difference. > > The most difficult thing for me to understand is: if this is some sort > > of resource limitation why will it work with a slower phy layer > > perfectly and not with the gigE? The only thing I could think of was > > that the old driver was doing m_defrag calls when it filled the transmi= t > > descriptor queues up to a certain point. Understanding the effects of > > m_defrag would be helpful in figuring this out I suppose. >=20 > maybe the chip just can't keep the transmit fifo loaded at the higher > speeds... is it possible vls is doing a writev for multisegmented UDP > packet? I'll have to look at this again... I suppose. As I understand it, though, it should be sending out 1316-byte data packets at a metered pace. Also, wouldn't it behave the same for 100BT vs. gigE? Shouldn't I see packet loss with 100BT if this is the case? > > > It would be interesting on the send and receive sides to inspect the > > > counters for drops at various points in the network stack; i.e., are = we > > > dropping packets at the ifq handoff because we're overfilling the > > > descriptors in the driver, are packets dropped on the inbound path go= ing > > > into the netisr due to over-filling before the netisr is scheduled, e= tc.=20 > > > And, it's probably interesting to look at stats on filling the socket > > > buffers for the same reason: if bursts of packets come up the stack, = the > > > socket buffers could well be being over-filled before the user thread= can > > > run. > >=20 > > Yes, this would be very interesting and should point out the problem. = I > > would do such a thing if I had enough knowledge of the network pathways= . > > Alas, I am very green in this area. The receive side has no issues, > > though, so I would focus on transmit counters (with assistance). >=20 --=-Neck75QEDKh+GjKidRwQ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBomMxyQsGN30uGE4RAlqhAJ9TrsixxX3K64+oIOUibWB6sb8hzgCdGTqN CwnP4Vx2F7UK7Bzn+8HlRWA= =/Ax1 -----END PGP SIGNATURE----- --=-Neck75QEDKh+GjKidRwQ-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 22:10:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 57F1E16A4CE; Mon, 22 Nov 2004 22:10:10 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 800E743D2D; Mon, 22 Nov 2004 22:10:09 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id B8A981FFACA; Mon, 22 Nov 2004 23:10:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id D4F981FF9AD; Mon, 22 Nov 2004 23:10:05 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 0F53C15712; Mon, 22 Nov 2004 22:08:24 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 04C94156F3; Mon, 22 Nov 2004 22:08:24 +0000 (UTC) Date: Mon, 22 Nov 2004 22:08:24 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: John Baldwin In-Reply-To: <200411221644.57047.jhb@FreeBSD.org> Message-ID: References: <200411221644.57047.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: freebsd-current@FreeBSD.org Subject: Re: mem leak in mii ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 22:10:10 -0000 On Mon, 22 Nov 2004, John Baldwin wrote: > On Friday 19 November 2004 06:49 pm, Bjoern A. Zeeb wrote: > > Hi, > > > > in sys/dev/mii/mii.c there are two calls to malloc for ivars; > > see for example mii_phy_probe: ... > > Where is the free for this malloc ? I cannot find it. > > > > analogous: miibus_probe ? > > It's a leak. It should be free'd when the miibus device is destroyed. Here's > a possible fix: this does only catch about 75% of what may happen I think. mii isn't very error checking at all and I have run into even more problems while remotely debugging other problems with someone. I am currently working on a hopefully more complete fix (there are two leaks actually). -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 22:12:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B862016A4CE for ; Mon, 22 Nov 2004 22:12:22 +0000 (GMT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A20D43D39 for ; Mon, 22 Nov 2004 22:12:22 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 9747 invoked from network); 22 Nov 2004 22:12:22 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 22 Nov 2004 22:12:21 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAMMCGQi030184; Mon, 22 Nov 2004 17:12:17 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Mon, 22 Nov 2004 17:02:35 -0500 User-Agent: KMail/1.6.2 References: <200411091747.iA9Hl81Q075289@marlena.vvi.at> <200411151429.56336.jhb@FreeBSD.org> <200411181441.09471.benlutz@datacomm.ch> In-Reply-To: <200411181441.09471.benlutz@datacomm.ch> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411221702.35131.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Benjamin Lutz Subject: Re: FreeBSD 5.3-RELEASE boot failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 22:12:22 -0000 On Thursday 18 November 2004 08:41 am, Benjamin Lutz wrote: > On Monday 15 November 2004 20:29, John Baldwin wrote: > > On Tuesday 09 November 2004 12:47 pm, ALeine wrote: > > > I installed FreeBSD 5.3-RELEASE from the ISO CD image, but it won't > > > boot: > > > > > > F1 DOS > > > F2 Linux > > > F3 FreeBSD > > > > > > Default: F3 > > > > > > _ > > > int=00000006 err=00000000 efl=00000282 eip=000947cf > > > eax=000000c1 ebx=0000273b ecx=fe510821 edx=00000000 > > > esi=00000006 edi=00098db6 ebp=00090000 esp=00000000 > > > cs=002b ds=0033 es=0033 fs=0033 gs=0033 ss=0033 > > > cs:eip=f0 2b 92 00 00 00 00 bc-89 00 00 af f1 e6 f8 00 > > > 00 00 00 00 00 00 00 00-00 54 3d 00 00 00 00 00 > > > ss:esp=2b 00 00 01 1b f6 13 50-08 19 f6 f4 f7 f3 c3 f9 > > > 6f 91 6c 2c f8 ef 0d 6c-10 f2 7b 77 08 59 2e f9 > > > BTX halted > > > > > > This was with the HDD as ad0. I changed it to ad2 and used my > > > other drive with FreeBSD 4.10 as ad0 to see what was going on. > > > Here's the beef: > > > > Your BIOS is in lala land perhaps. Note that the stack pointer is 0, > > so it's hard to tell how it got into such a funk. I'm not sure how you > > can debug this, except perhaps to try turning off things like network > > cards as boot devices and turning off DMA mode in the BIOS for your > > hard drives. > > I got an error like this when I accidentally tried to use FreeBSD/amd64 on > an i386-only machine. That type of dump would have different instructions at cs:eip (probably an amd64-specific instruction). > Maybe the BIOS is broken, but the chance that using vmware instead of his > native hardware would produce the same error is low, isn't it? I don't know how vmware is implemented, but it would probably not have the same problem since it probably has a much simpler BIOS. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 22:25:55 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C638816A4CF for ; Mon, 22 Nov 2004 22:25:55 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9508943D1F for ; Mon, 22 Nov 2004 22:25:55 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 55C6AF20C2 for ; Mon, 22 Nov 2004 14:25:55 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02658-05 for ; Mon, 22 Nov 2004 14:25:52 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id AD83EF2089 for ; Mon, 22 Nov 2004 14:25:52 -0800 (PST) From: Sean McNeil To: current@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-gwhv2x8OxtN81Or9wkAY" Date: Mon, 22 Nov 2004 14:25:52 -0800 Message-Id: <1101162352.4774.7.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com Subject: crash in natd again X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 22:25:55 -0000 --=-gwhv2x8OxtN81Or9wkAY Content-Type: text/plain Content-Transfer-Encoding: quoted-printable This is on an amd64 machine. I though that setting dumpdev=3D"AUTO" in /etc/rc.conf was sufficient to get a crash dump, but it didn't work. I'm adding dumpon_enable=3D"YES" savecore_enable=3D"YES" now. Please let me know if there is anything else I need to set. The information I can get is: Nov 22 13:47:27 server kernel: Fatal trap 12: page fault while in kernel mo= de Nov 22 13:47:27 server kernel: fault virtual address =3D 0x18 Nov 22 13:47:27 server kernel: fault code =3D supervisor read= , page not present Nov 22 13:47:27 server kernel: instruction pointer =3D 0x8:0xffffffff8= 0357980Nov 22 13:47:27 server kernel: stack pointer =3D 0x10:0xf= fffffffb41c5620 Nov 22 13:47:27 server kernel: frame pointer =3D 0x10:0xffffffff= b41c5680 Nov 22 13:47:27 server kernel: code segment =3D base 0x0, limit= 0xfffff, type 0x1b Nov 22 13:47:27 server kernel: =3D DPL 0, pres 1, long 1, def32 0, gran 1 Nov 22 13:47:27 server kernel: processor eflags =3D interrupt enabled, resu= me, IOPL =3D 0 Nov 22 13:47:27 server kernel: current process =3D 215 (natd) Nov 22 13:47:27 server kernel: trap number =3D 12 Nov 22 13:47:27 server kernel: panic: page fault Nov 22 13:47:27 server kernel: KDB: enter: panic uname is FreeBSD server.mcneil.com 6.0-CURRENT FreeBSD 6.0-CURRENT #5: Sun Nov 21 00:33:27 PST 2004 root@server.mcneil.com:/usr/obj/usr/src/sys/AMD64 amd64 (gdb) l *0xffffffff80357980 0xffffffff80357980 is in m_copym (/usr/src/sys/kern/uipc_mbuf.c:373). 368 MBUF_CHECKSLEEP(wait); 369 if (off =3D=3D 0 && m->m_flags & M_PKTHDR) 370 copyhdr =3D 1; 371 while (off > 0) { 372 KASSERT(m !=3D NULL, ("m_copym, offset > size of mbuf chain")); 373 if (off < m->m_len) 374 break; 375 off -=3D m->m_len; 376 m =3D m->m_next; 377 } --=-gwhv2x8OxtN81Or9wkAY Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBomdwyQsGN30uGE4RAposAKC29NEtQsX1nhYQbKub29s/WT3E6gCffXhP i8q07M6trwQVDNNUdjU5UZY= =3xCz -----END PGP SIGNATURE----- --=-gwhv2x8OxtN81Or9wkAY-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 22:36:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D496F16A4CE for ; Mon, 22 Nov 2004 22:36:34 +0000 (GMT) Received: from corwin.easynet.fr (smarthost160.mail.easynet.fr [212.180.1.160]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E73843D2D for ; Mon, 22 Nov 2004 22:36:34 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from [212.180.127.72] (helo=tatooine.tataz.chchile.org) by corwin.easynet.fr with esmtp (Exim 4.34) id 1CWMnM-0007MX-VW; Mon, 22 Nov 2004 23:36:29 +0100 Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id DB6A4412D; Mon, 22 Nov 2004 23:36:22 +0100 (CET) Date: Mon, 22 Nov 2004 23:36:21 +0100 From: Jeremie Le Hen To: Jeff Roberson Message-ID: <20041122223621.GG960@obiwan.tataz.chchile.org> References: <20041120000743.G18094@mail.chesapeake.net> <41A1C3BD.4010903@fer.hr> <20041122064318.Y18094@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041122064318.Y18094@mail.chesapeake.net> User-Agent: Mutt/1.5.6i X-Broken-Reverse-DNS: no host name found for IP address 212.180.127.72 cc: current@freebsd.org cc: Ivan Voras Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 22:36:35 -0000 Hi Jeff, > I haven't received any feedback from the list though. I hope people are > testing it. Perhaps the silence indicates universal success? :-) I have just tested your patch. It compiles like a charm. FYI, my kernel have MUTEX_DEBUG, INVARIANTS and WITNESS enabled, but no PREEMPTION. While using my system with debug.mpsavevfs=1, I encountered two different panics. (Sorry, I do not have a serial cable plugged into my laptop and manual writing of hexadecimal addresses is very annoying.) The first one seems to be related to union mounts as when I use Tobias Roth's profile.sh (which union mounts a vnode md(4) device over /etc) `ls /etc' panics the system but when I don't have the mount, everything seems to work : panic: mutex Giant not owned at ../../../kern/vfs_vnops.c:962 db> trace kdb_enter() panic() _mtx_assert() vn_write_suspend_wait() ufs_inactive() ufs_vnoperate() vput() getdirentries() syscall() The second one appeared just when I ask bash(1) to complete a command name : it has to scan all directories from $HOME and stat(2) every files in them. Here is the panic() : Memory modified after free 0xc1ddc300 (252) val=c1df59c4 @ 0xc1ddc374 panic: Most recently used by UFS mount kdb_enter() panic() mtrash_ctor() uma_zalloc_arg() malloc() fdinit() fdcopy() fork1() fork() syscall() I hope this will help. Best regads, -- Jeremie Le Hen jeremie@le-hen.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 22:39:17 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B21416A4CE for ; Mon, 22 Nov 2004 22:39:17 +0000 (GMT) Received: from caine.easynet.fr (smarthost161.mail.easynet.fr [212.180.1.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id D73F643D41 for ; Mon, 22 Nov 2004 22:39:16 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from [212.180.127.72] (helo=tatooine.tataz.chchile.org) by caine.easynet.fr with esmtp (Exim 4.34) id 1CWMq2-0002ev-1W; Mon, 22 Nov 2004 23:39:14 +0100 Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 66C05412D; Mon, 22 Nov 2004 23:39:07 +0100 (CET) Date: Mon, 22 Nov 2004 23:39:06 +0100 From: Jeremie Le Hen To: Jeff Roberson Message-ID: <20041122223906.GH960@obiwan.tataz.chchile.org> References: <20041120000743.G18094@mail.chesapeake.net> <41A1C3BD.4010903@fer.hr> <20041122064318.Y18094@mail.chesapeake.net> <20041122223621.GG960@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041122223621.GG960@obiwan.tataz.chchile.org> User-Agent: Mutt/1.5.6i X-Broken-Reverse-DNS: no host name found for IP address 212.180.127.72 cc: current@freebsd.org cc: Ivan Voras Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 22:39:17 -0000 > I have just tested your patch. It compiles like a charm. FYI, my > kernel have MUTEX_DEBUG, INVARIANTS and WITNESS enabled, but no > PREEMPTION. Althouth I asked in previous mail if testing the patch on a UP system would be interesting or not, I forgot to mention that may kernel is indeed UP. -- Jeremie Le Hen jeremie@le-hen.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 22:44:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F8DD16A4CE for ; Mon, 22 Nov 2004 22:44:25 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A4B143D5D for ; Mon, 22 Nov 2004 22:44:25 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 28382F20C3 for ; Mon, 22 Nov 2004 14:44:25 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02089-01 for ; Mon, 22 Nov 2004 14:44:23 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 1951CF1800 for ; Mon, 22 Nov 2004 14:44:23 -0800 (PST) From: Sean McNeil To: current@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-A4oQPiA7L3dYiQIO+oO2" Date: Mon, 22 Nov 2004 14:44:22 -0800 Message-Id: <1101163462.2758.3.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com Subject: strange fsck behavior X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 22:44:25 -0000 --=-A4oQPiA7L3dYiQIO+oO2 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On the occasional crash, by system reboots and goes into background checking of my software raid: ar0: 117246MB [14946/255/63] status: READY subdisks: disk0 READY on ad0 at ata0-master disk1 READY on ad1 at ata0-slave It would appear to complete correctly, but the next time I reboot (cleanly) it does a complete check. Never finds anything wrong, but takes forever. It also sometimes doesn't see things on the disk correctly until I do the reboot. It would seem that it gets into a peculiar state after completing the background fsck. Cheers, Sean --=-A4oQPiA7L3dYiQIO+oO2 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBomvGyQsGN30uGE4RApc9AJ4+0FiX7qbNmfZVeoprmaBgkFw9uACfW9QW xw8DDiDhzGRjAIg51k7LaJE= =b4t8 -----END PGP SIGNATURE----- --=-A4oQPiA7L3dYiQIO+oO2-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 23:08:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88CC116A4CE; Mon, 22 Nov 2004 23:08:54 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id C93BA43D46; Mon, 22 Nov 2004 23:08:53 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAMN8qLT031188; Tue, 23 Nov 2004 00:08:52 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Baldwin From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 22 Nov 2004 16:57:36 EST." <200411221657.36659.jhb@FreeBSD.org> Date: Tue, 23 Nov 2004 00:08:52 +0100 Message-ID: <31187.1101164932@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@FreeBSD.org Subject: Re: panic: sleeping thread owns a non-sleepable lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 23:08:54 -0000 In message <200411221657.36659.jhb@FreeBSD.org>, John Baldwin writes: >On Monday 22 November 2004 09:38 am, Peter Holm wrote: >> During stress test with GENERIC HEAD from Nov 20 08:40 UTC I got: >> Sleeping on "fdesc" with the following non-sleepable locks held: >> exclusive sleep mutex fdesc r = 0 (0xc08d15a0) locked @ >> kern/kern_descrip.c:2425 and then >> panic: sleeping thread (pid 92279) owns a non-sleepable lock >> >> http://www.holm.cc/stress/log/cons89.html > >Yes, the panic is a result of the earlier warning. Poul-Henning touched this >code last, so it is probably something for him to look at. I'm unsure how >msleep() is getting called, however. The turnstile panic is not important, >can you find the thread that went to sleep (should be pid 92279) and get >stack trace for that? This one is a known trouble-spot but I don't know how to solve it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 23:23:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CF7D16A4CE for ; Mon, 22 Nov 2004 23:23:29 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1491D43D54 for ; Mon, 22 Nov 2004 23:23:27 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAMNMKZg013128 for ; Tue, 23 Nov 2004 09:52:20 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Tue, 23 Nov 2004 09:53:13 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAMNJJh14219 for ; Tue, 23 Nov 2004 09:49:19 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id XM1D78MQ; Tue, 23 Nov 2004 09:49:17 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAMNJXpU014529 for ; Tue, 23 Nov 2004 09:49:33 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAMNJX0j014528 for current@freebsd.org; Tue, 23 Nov 2004 09:49:33 +1030 (CST) (envelope-from wilkinsa) Date: Tue, 23 Nov 2004 09:49:33 +1030 From: "Wilkinson, Alex" To: current@freebsd.org Message-ID: <20041122231933.GC14425@squash.dsto.defence.gov.au> Mail-Followup-To: current@freebsd.org References: <1101162352.4774.7.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <1101162352.4774.7.camel@server.mcneil.com> User-Agent: Mutt/1.5.6i Subject: Re: crash in natd again X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 23:23:29 -0000 I've always used something like: dumpdev="/dev/ad0s3b" i.e. s3b being swap. -aW 0n Tue, Nov 23, 2004 at 08:55:52AM +1030, Sean McNeil wrote: > This is on an amd64 machine. I though that setting > > dumpdev="AUTO" > > in /etc/rc.conf was sufficient to get a crash dump, but it didn't work. > I'm adding > > dumpon_enable="YES" > savecore_enable="YES" > > now. Please let me know if there is anything else I need to set. > > The information I can get is: > > Nov 22 13:47:27 server kernel: Fatal trap 12: page fault while in kernel > mode > Nov 22 13:47:27 server kernel: fault virtual address = 0x18 > Nov 22 13:47:27 server kernel: fault code = supervisor > read, page > not present > Nov 22 13:47:27 server kernel: instruction pointer = > 0x8:0xffffffff80357980Nov 22 13:47:27 server kernel: stack pointer > = 0x10:0xffffffffb41c5620 > Nov 22 13:47:27 server kernel: frame pointer = > 0x10:0xffffffffb41c5680 > Nov 22 13:47:27 server kernel: code segment = base 0x0, > limit 0xfffff, type 0x1b > Nov 22 13:47:27 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 > Nov 22 13:47:27 server kernel: processor eflags = interrupt enabled, > resume, IOPL = 0 > Nov 22 13:47:27 server kernel: current process = 215 (natd) > Nov 22 13:47:27 server kernel: trap number = 12 > Nov 22 13:47:27 server kernel: panic: page fault > Nov 22 13:47:27 server kernel: KDB: enter: panic > > uname is > > FreeBSD server.mcneil.com 6.0-CURRENT FreeBSD 6.0-CURRENT #5: Sun Nov 21 > 00:33:27 PST 2004 root@server.mcneil.com:/usr/obj/usr/src/sys/AMD64 > amd64 > > (gdb) l *0xffffffff80357980 > 0xffffffff80357980 is in m_copym (/usr/src/sys/kern/uipc_mbuf.c:373). > 368 MBUF_CHECKSLEEP(wait); > 369 if (off == 0 && m->m_flags & M_PKTHDR) > 370 copyhdr = 1; > 371 while (off > 0) { > 372 KASSERT(m != NULL, ("m_copym, offset > size of > mbuf chain")); > 373 if (off < m->m_len) > 374 break; > 375 off -= m->m_len; > 376 m = m->m_next; > 377 } > From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 23:43:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3638F16A4CE for ; Mon, 22 Nov 2004 23:43:07 +0000 (GMT) Received: from corwin.easynet.fr (smarthost160.mail.easynet.fr [212.180.1.160]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5E2C43D2F for ; Mon, 22 Nov 2004 23:43:06 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from [212.180.127.72] (helo=tatooine.tataz.chchile.org) by corwin.easynet.fr with esmtp (Exim 4.34) id 1CWNpn-00055z-Lq; Tue, 23 Nov 2004 00:43:04 +0100 Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 0C5C7412C; Tue, 23 Nov 2004 00:42:56 +0100 (CET) Date: Tue, 23 Nov 2004 00:42:55 +0100 From: Jeremie Le Hen To: Jeff Roberson Message-ID: <20041122234255.GI960@obiwan.tataz.chchile.org> References: <20041120000743.G18094@mail.chesapeake.net> <41A1C3BD.4010903@fer.hr> <20041122064318.Y18094@mail.chesapeake.net> <20041122223621.GG960@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041122223621.GG960@obiwan.tataz.chchile.org> User-Agent: Mutt/1.5.6i X-Broken-Reverse-DNS: no host name found for IP address 212.180.127.72 cc: current@freebsd.org cc: Ivan Voras Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 23:43:07 -0000 > The second one appeared just when I ask bash(1) to complete a command > name : it has to scan all directories from $HOME and stat(2) every files > in them. Here is the panic() : Sorry for the flood guys :-/. It seems I'm more tired than I though. s/HOME/PATH/ -- Jeremie Le Hen jeremie@le-hen.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 00:14:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E38D316A4CE; Tue, 23 Nov 2004 00:14:21 +0000 (GMT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64BBD43D49; Tue, 23 Nov 2004 00:14:20 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) iAN0EFcW058710; Mon, 22 Nov 2004 16:14:16 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.9p2/8.12.9/Submit) id iAN0EFZn058709; Mon, 22 Nov 2004 16:14:15 -0800 (PST) (envelope-from dillon) Date: Mon, 22 Nov 2004 16:14:15 -0800 (PST) From: Matthew Dillon Message-Id: <200411230014.iAN0EFZn058709@apollo.backplane.com> To: Sean McNeil References: <20041121205158.45CE.SHINO@fornext.org> <200411220038.iAM0c7JQ052589@apollo.backplane.com> <20041122104527.5204.SHINO@fornext.org> <1101100870.16086.16.camel@server.mcneil.com> cc: Jeremie Le Hen cc: freebsd-stable@freebsd.org cc: freebsd-current@freebsd.org cc: Shunsuke SHINOMIYA Subject: Re: Re[4]: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 00:14:22 -0000 :Increasing the interrupt moderation frequency worked on the re driver, :but it only made it marginally better. Even without moderation, :however, I could lose packets without m_defrag. I suspect that there is :something in the higher level layers that is causing the packet loss. I :have no explanation why m_defrag makes such a big difference for me, but :it does. I also have no idea why a 20Mbps UDP stream can lose data over :gigE phy and not lose anything over 100BT... without the above mentioned :changes that is. It kinda sounds like the receiver's UDP buffer is not large enough to handle the burst traffic. 100BT is a much slower transport and the receiver (userland process) was likely able drain its buffer before new packets arrived. Use netstat -s to observe the drop statistics for udp on both the sender and receiver sides. You may also be able to get some useful information looking at the ip stats on both sides too. Try bumping up net.inet.udp.recvspace and see if that helps. In anycase, you should be able to figure out where the drops are occuring by observing netstat -s output. -Matt Matthew Dillon From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 01:13:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC15A16A4CF for ; Tue, 23 Nov 2004 01:13:10 +0000 (GMT) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.FreeBSD.org (Postfix) with SMTP id 0ADB443D62 for ; Tue, 23 Nov 2004 01:13:10 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 83603 invoked from network); 23 Nov 2004 01:13:08 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 23 Nov 2004 01:13:08 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iAN1D7mu038636; Tue, 23 Nov 2004 02:13:07 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iAN1D7mE038635; Tue, 23 Nov 2004 02:13:07 +0100 (CET) (envelope-from pho) Date: Tue, 23 Nov 2004 02:13:07 +0100 From: Peter Holm To: John Baldwin Message-ID: <20041123011307.GA38559@peter.osted.lan> References: <20041122143804.GA36649@peter.osted.lan> <200411221657.36659.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200411221657.36659.jhb@FreeBSD.org> User-Agent: Mutt/1.4.2.1i cc: current@FreeBSD.org cc: phk@FreeBSD.org Subject: Re: panic: sleeping thread owns a non-sleepable lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 01:13:10 -0000 On Mon, Nov 22, 2004 at 04:57:36PM -0500, John Baldwin wrote: > On Monday 22 November 2004 09:38 am, Peter Holm wrote: > > During stress test with GENERIC HEAD from Nov 20 08:40 UTC I got: > > Sleeping on "fdesc" with the following non-sleepable locks held: > > exclusive sleep mutex fdesc r = 0 (0xc08d15a0) locked @ > > kern/kern_descrip.c:2425 and then > > panic: sleeping thread (pid 92279) owns a non-sleepable lock > > > > http://www.holm.cc/stress/log/cons89.html > > Yes, the panic is a result of the earlier warning. Poul-Henning touched this > code last, so it is probably something for him to look at. I'm unsure how > msleep() is getting called, however. The turnstile panic is not important, > can you find the thread that went to sleep (should be pid 92279) and get > stack trace for that? > The ddb trace is in the log, just before call doadump. Let me know if you need any gdb output. -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 01:30:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E869C16A4CF for ; Tue, 23 Nov 2004 01:30:56 +0000 (GMT) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id 6BD7C43D54 for ; Tue, 23 Nov 2004 01:30:56 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 48577 invoked from network); 23 Nov 2004 01:30:55 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 23 Nov 2004 01:30:55 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iAN1Usc4038860; Tue, 23 Nov 2004 02:30:54 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iAN1Usx0038859; Tue, 23 Nov 2004 02:30:54 +0100 (CET) (envelope-from pho) Date: Tue, 23 Nov 2004 02:30:54 +0100 From: Peter Holm To: Jeff Roberson Message-ID: <20041123013054.GA38804@peter.osted.lan> References: <20041120000743.G18094@mail.chesapeake.net> <41A1C3BD.4010903@fer.hr> <20041122064318.Y18094@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041122064318.Y18094@mail.chesapeake.net> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org cc: Ivan Voras Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 01:30:57 -0000 On Mon, Nov 22, 2004 at 06:46:50AM -0500, Jeff Roberson wrote: > On Mon, 22 Nov 2004, Ivan Voras wrote: > > > Jeff Roberson wrote: > > > > > The short description: > > > This patch removes Giant from the read(), write(), and fstat() syscalls, > > > as well as page faults, and bufdone (io interrupts) when using FFS. It > > > > What is the plan re: RELENG_5? Will things like this (giantless vm, fs) > > be merged into it? > > The giantless vm was already merged back to RELENG_5 and enabled on amd64, > and i386. I hope to merge the giantless vfs back after a month or so of > no problems on -current. I hope to commit it to -current this week. > > I haven't received any feedback from the list though. I hope people are > testing it. Perhaps the silence indicates universal success? :-) > Here's a problem I ran into during stress test: http://www.holm.cc/stress/log/jeff01.html Let me know if you need more gdb output. - Peter > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 02:19:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06A9216A4CE for ; Tue, 23 Nov 2004 02:19:30 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71E5E43D2D for ; Tue, 23 Nov 2004 02:19:29 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.0.5] (adsl-68-250-184-205.dsl.wotnoh.ameritech.net [68.250.184.205]) (authenticated bits=0)iAN1xZUJ062830 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 22 Nov 2004 20:59:36 -0500 (EST) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-current@freebsd.org Date: Mon, 22 Nov 2004 21:22:02 -0500 User-Agent: KMail/1.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart7981619.judgAm51r5"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411222122.22452.mistry.7@osu.edu> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on crumpet.united-ware.com cc: Justin Hibbits Subject: Re: ATI TV Wonder support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 02:19:30 -0000 --nextPart7981619.judgAm51r5 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 21 November 2004 10:00 pm, Justin Hibbits wrote: > This patch gives more or less full ATI TV Wonder support to the bktr > driver. > Awesome. > The sound doesn't mute at close, but that might be xawtv's fault, but I > don't know which to accuse or look at. But, other than that, it seems > pretty good. > I've having some trouble using it though, the sound doesn't seem to work=20 just as before. Is there something extra I need to add to my kernel=20 besides bktr? On boot: bktr0: mem 0xe3101000-0xe3101fff irq 11 at device 8.0 on=20 pci0 bktr0: [GIANT-LOCKED] bktr0: Detected a MSP3445G-B8 at 0x80 bktr0: ATI TV Wonder, Philips NTSC tuner, msp3400c stereo. pci0: at device 8.1 (no driver attached) And when I start it: bktr0: Detected a MSP3445G-B8 at 0x80 You should also send-pr this if you haven't already. Thanks, =2D-=20 Anish Mistry --nextPart7981619.judgAm51r5 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBop7exqA5ziudZT0RApTrAKCzeX3/r58Ou56ZW7s+R1GlrxucTwCbBYE6 nqeyqYQu/+orgNs90GhxRLk= =IOww -----END PGP SIGNATURE----- --nextPart7981619.judgAm51r5-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 02:31:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CC3B16A4CE; Tue, 23 Nov 2004 02:31:16 +0000 (GMT) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id C641543D2F; Tue, 23 Nov 2004 02:31:14 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.43 (FreeBSD)) id 1CWQSn-0008M8-0H; Tue, 23 Nov 2004 10:31:29 +0800 Message-Id: <6.2.0.14.2.20041123102644.03040770@202.179.0.80> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Tue, 23 Nov 2004 10:31:02 +0800 To: Robert Watson From: Ganbold In-Reply-To: References: <6.2.0.14.2.20041122151958.0303be20@202.179.0.80> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: tomaz.borstnar@over.net cc: cguttesen@yahoo.dk cc: scottl@freebsd.org cc: mhunter@ack.Berkeley.EDU cc: freebsd-current@freebsd.org Subject: Re: Page fault in FreeBSD 5.3 on IBM e325, Dual AMD64 2.2GHz, 4GB RAM, ServeRAID 6M - debug logs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 02:31:16 -0000 At 06:43 PM 11/22/2004, you wrote: >On Mon, 22 Nov 2004, Ganbold wrote: > > > Fatal trap 12: page fault while in kernel mode > > cpuid = 1; apic id = 01 > > fault virtual address = 0x18 > > fault code = supervisor read, page not present > > instruction pointer = 0x8:0xffffffff80277fc0 > > stack pointer = 0x10:0xffffffffb36ab830 > > frame pointer = 0x10:0xffffffffb36ab890 > > 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 = 44 (swi1: net) > > [thread 100044] > > Stopped at m_copym+0x190: incl %ecx ><...> > > > -------------------------------------------------------------------------------------------------------- > > > > It seems to me the problem is related to network stack and threading. > > Am I right? How to solve this problem? > >I've seen reports of this problem with and without debug.mpsafenet=1, >which suggests it is a network stack bug but not specific to locking. I've >also seen reports that disabling TCP SACK will make the problem go away, >which would be good to confirm. I spent the weekend building up some more >expertise in TCP and reading a lot of TCP code, and hope to look at this >problem in more detail today. You may want to try turning off TCP sack >using net.inet.tcp.sack.enable=0 in sysctl.conf (or loader.conf). Thanks Robert. I will try as you suggested and let you know. Please let me know if you find the fix to this problem later on. thanks, Ganbold >Robert N M Watson FreeBSD Core Team, TrustedBSD Projects >robert@fledge.watson.org Principal Research Scientist, McAfee Research > > >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 04:05:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81C4B16A4CF for ; Tue, 23 Nov 2004 04:05:00 +0000 (GMT) Received: from www.mmlab.cse.yzu.edu.tw (www.mmlab.cse.yzu.edu.tw [140.138.150.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9036743D1F for ; Tue, 23 Nov 2004 04:04:59 +0000 (GMT) (envelope-from avatar@mmlab.cse.yzu.edu.tw) Received: by www.mmlab.cse.yzu.edu.tw (qmail, from userid 1000) id 671C74EFCD3; Tue, 23 Nov 2004 12:04:55 +0800 (CST) Received: from localhost (localhost [127.0.0.1]) by www.mmlab.cse.yzu.edu.tw (qmail) with ESMTP id 5E2214EFCD0; Tue, 23 Nov 2004 12:04:55 +0800 (CST) Date: Tue, 23 Nov 2004 12:04:55 +0800 (CST) From: Tai-hwa Liang To: Sam Leffler In-Reply-To: <41780961.3040808@errno.com> Message-ID: <04112312005318.8132@www.mmlab.cse.yzu.edu.tw> References: <415C59C7.7090408@pythonemproject.com> <200410210901.09392.fcash@ocis.net><41780961.3040808@errno.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: doug@polands.org cc: rob@pythonemproject.com cc: current@freebsd.org cc: Freddie Cash Subject: Re: wifi on 5.3, sort of OT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 04:05:00 -0000 On Thu, 21 Oct 2004, Sam Leffler wrote: > doug@polands.org wrote: >> On Thu, Oct 21, 2004 at 09:01:09AM -0700, Freddie Cash wrote: >>> On September 30, 2004 12:08 pm, Rob wrote: >>>> Problem seems to be right now that my Netgear WG511T cardbus card >>>> doesn't seem to be reconginized. >>> >>> I have the same card at home. In order to get it to work with BETA7 I had >>> to install a new Atheros HAL. This can be downloaded from the >>> people.freebsd.org/internal/ website, although I forget the name of the >>> person who did the patchset. You download the patchset, patch the source >>> tree, and rebuild the Atheros modules. After that, everything worked just >>> tickety-boo. >>> >> Have these patches made it into RC1? If not, are they planned for >> 5.3-RELEASE? >> > I cannot commit any of the changes because other drivers need to be updated > and noone has stepped up to help do that. Until then the code in the tree > will remain ~1 year behind my current work. > > Sam Hi Sam, I'm curious about what those "other drivers" are and what kind of update they may require to cooperate with the latest 802.11 stack? A short grep of 80211 on sys/dev shows following hits: sys/dev/an/if_aironet_ieee.h sys/dev/an/if_an.c sys/dev/an/if_anreg.h sys/dev/arl/if_arl.c sys/dev/awi/am79c930reg.h sys/dev/awi/awi.c sys/dev/awi/awireg.h sys/dev/awi/awivar.h sys/dev/awi/if_awi_pccard.c sys/dev/if_ndis/if_ndis_pccard.c sys/dev/if_ndis/if_ndis.c sys/dev/if_ndis/if_ndis_pci.c sys/dev/if_ndis/if_ndisvar.h sys/dev/owi/if_ieee80211.h sys/dev/owi/if_owi.c sys/dev/owi/if_owi_pccard.c sys/dev/ray/if_ray.c sys/dev/ray/if_raymib.h sys/dev/wi/if_wavelan_ieee.h sys/dev/wi/if_wi.c sys/dev/wi/if_wi_pccard.c sys/dev/wi/if_wi_pci.c sys/dev/wi/if_wireg.h sys/dev/wi/if_wivar.h It also appears that net80211+ath-20041015.tgz had already dealt with the following files: sys/dev/awi/awi.c sys/dev/awi/awivar.h sys/dev/if_ndis/if_ndis.c sys/dev/if_ndis/if_ndisvar.h sys/dev/ray/if_ray.c sys/dev/wi/if_wi.c sys/dev/wi/if_wi_pci.c sys/dev/wi/if_wivar.h Though I don't have the real hardware to test; however, after a quick glance at arl, owi and ray, I guess that they should just work with the latest 802.11 stack since they didn't seem too much depend on net80211 to complete their tasks. I've applied your patch and tested them with Linksys WPC55AG pccard(if_ath), IBM High Rate Wireless LAN Mini PCI adapter(if_wi) and Cisco Aironet Mini PCI adapter(if_an). Here are my testing result on a Thinkpad R40: Infrastructure Adhoc(with another if_wi) if_an able to associate(1) able to associate(1) if_ath somewhat works(2) freeze if "too many" frames were sent/received(3) if_wi works works (1) Despite the "an0: device timeout" starts to appear after 4 ~ 5 ping packets were sent, the card can associate with AP or other adhoc station. I'm still trying to figure out what's really going on with this timeout since it also happens *before* the patch was applied. The timeout would occupy an0 a lot of time to do the device re-init and thus render the card almost unusable -- taking "ping" as an example, there would be one "device timeout" every 4 ping packets, which raises the RTT to 1xxx ms per ping packet. (2) Interactive ssh session to/from another host works okay; however, if there're packets burst, the connection would hang. For example, ssh from if_ath to another host and issue a dmesg(about 8 Kbytes of data), the connection will hang. Meanwhile, this box is still repsonse to remote ping, and is still able to ssh to another host. (3) If I issue a ping from each other at the same time(10.0.0.2 -> 10.0.0.5 and 10.0.0.5 -> 10.0.0.2), the system froze; that is, it didn't response to ping and keyboard input anymore. However, if I manually eject the pccard, the laptop would response again. I'm not sure whether this is correlated to the "an0: device timeout" aforementioned in (1) since according to systat -vm, there're only about 20 interrupts per second on cbb0 during the packet transmission. In addition to that, sometime if the device didn't freeze but timeout'ed(ath0: device timeout), the ssid will be cleared. BTW, Following is the patch to make device awi compile after applying net80211+ath-20041015.patch. I would be very appreciate it if anyone who happens to get this card to test this. --- /sys/dev/awi/awi.c.bak Mon Nov 22 17:54:16 2004 +++ /sys/dev/awi/awi.c Mon Nov 22 17:54:54 2004 @@ -663,7 +663,7 @@ ni->ni_intval = ic->ic_lintval; ni->ni_rssi = 0; ni->ni_rstamp = 0; - memset(ni->ni_tstamp, 0, sizeof(ni->ni_tstamp)); + ni->ni_tstamp.tsf = 0; ni->ni_rates = ic->ic_sup_rates[ieee80211_chan2mode(ic, ni->ni_chan)]; IEEE80211_ADDR_COPY(ni->ni_macaddr, ic->ic_myaddr); @@ -2048,14 +2048,14 @@ awi_write_2(sc, AWI_CA_SYNC_DWELL, 0); } if (ic->ic_flags & IEEE80211_F_SIBSS) { - memset(ni->ni_tstamp, 0, sizeof(ni->ni_tstamp)); + ni->ni_tstamp.tsf = 0; ni->ni_rstamp = 0; awi_write_1(sc, AWI_CA_SYNC_STARTBSS, 1); } else awi_write_1(sc, AWI_CA_SYNC_STARTBSS, 0); awi_write_2(sc, AWI_CA_SYNC_MBZ, 0); awi_write_bytes(sc, AWI_CA_SYNC_TIMESTAMP, - ni->ni_tstamp, 8); + ni->ni_tstamp.data, 8); awi_write_4(sc, AWI_CA_SYNC_REFTIME, ni->ni_rstamp); sc->sc_cur_chan = ieee80211_chan2ieee(ic, ni->ni_chan); if ((error = awi_cmd(sc, AWI_CMD_SYNC, AWI_NOWAIT)) ---------- Related system information after applying the patch ---------- ath_rate: ath_hal: version 0.9.12.13 found-> vendor=0x168c, dev=0x0013, revid=0x01 bus=3, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0xa8 (5040 ns), mingnt=0x0a (2500 ns), maxlat=0x1c (7000 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 pcib2: device cardbus0 requested decoded memory range 0xd0200000-0xdfffffff pcib2: device cardbus0 requested decoded memory range 0xd0200000-0xdfffffff ath0: mem 0xd0210000-0xd021ffff irq 11 at device 0.0 on cardbus0 pcib2: device ath0 requested decoded memory range 0xd0210000-0xd021ffff ath0: [MPSAFE] ath0: bpf attached ath0: Ethernet address: 00:0c:41:fc:6c:54 ath0: bpf attached ath0: bpf attached ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: mac 5.6 phy 4.1 5ghz radio 3.6 ath0: Use hw queue 1 for WME_AC_BE traffic ath0: Use hw queue 0 for WME_AC_BK traffic ath0: Use hw queue 2 for WME_AC_VI traffic ath0: Use hw queue 3 for WME_AC_VO traffic pci0: driver added found-> vendor=0x8086, dev=0x24c3, revid=0x03 bus=0, slot=31, func=3 class=0c-05-00, hdrtype=0x00, mfdev=0 cmdreg=0x0001, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 pci0:31:3: reprobing on driver added pci0:31:3: Transition from D0 to D3 found-> vendor=0x8086, dev=0x24c5, revid=0x03 bus=0, slot=31, func=5 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 powerspec 2 supports D0 D3 current D3 pci0:31:5: reprobing on driver added pci0:31:5: Transition from D3 to D0 pci0:31:5: Transition from D0 to D3 found-> vendor=0x8086, dev=0x24c6, revid=0x03 bus=0, slot=31, func=6 class=07-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 powerspec 2 supports D0 D3 current D3 pci0:31:6: reprobing on driver added pci0:31:6: Transition from D3 to D0 pci0:31:6: Transition from D0 to D3 pci1: driver added pci2: driver added interrupt total rate irq0: clk 828213 999 irq1: atkbd0 3126 3 irq8: rtc 105994 127 irq9: acpi0 97 0 irq11: cbb0 fwohci+ 30616 36 irq12: psm0 51 0 irq13: npx0 1 0 irq14: ata0 2637 3 irq15: ata1 53 0 Total 970788 1171 From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 06:19:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9020F16A4CE for ; Tue, 23 Nov 2004 06:19:42 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FF5E43D54 for ; Tue, 23 Nov 2004 06:19:41 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAN6IeZg005270 for ; Tue, 23 Nov 2004 16:48:40 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Tue, 23 Nov 2004 16:43:04 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAN68Kh04385 for ; Tue, 23 Nov 2004 16:38:20 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id XM1D84YW; Tue, 23 Nov 2004 16:38:18 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAN68Zsk016684 for ; Tue, 23 Nov 2004 16:38:35 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAN68ZH6016683 for freebsd-current@freebsd.org; Tue, 23 Nov 2004 16:38:35 +1030 (CST) (envelope-from wilkinsa) Date: Tue, 23 Nov 2004 16:38:35 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20041123060835.GB16547@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: ACPI/USB Buffer @ Top of memory .... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 06:19:42 -0000 Hi all, I noticed this setting was disabled in my BIOS today. Is it better to enable this setting ? What does the setting actually do ? Will FreeBSD take into account this setting ? - aW From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 08:36:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB30C16A4CE for ; Tue, 23 Nov 2004 08:36:12 +0000 (GMT) Received: from corwin.easynet.fr (smarthost160.mail.easynet.fr [212.180.1.160]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7863D43D58 for ; Tue, 23 Nov 2004 08:36:12 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from [212.180.127.72] (helo=tatooine.tataz.chchile.org) by corwin.easynet.fr with esmtp (Exim 4.34) id 1CWW9i-0003Vu-2h for freebsd-current@freebsd.org; Tue, 23 Nov 2004 09:36:10 +0100 Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 7EB4E412C; Tue, 23 Nov 2004 09:36:00 +0100 (CET) Date: Tue, 23 Nov 2004 09:36:00 +0100 From: Jeremie Le Hen To: freebsd-current@freebsd.org Message-ID: <20041123083600.GM960@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i X-Broken-Reverse-DNS: no host name found for IP address 212.180.127.72 Subject: [LOR] ESS Maestro-2E and ACPI power methods X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 08:36:13 -0000 Hi, I built a -CURRENT kernel dated from this weekend, I simply re-used my old kernel configuration file without any modification. There is a LOR at boot time that I looked for in the known LOR database, but I didn't find it. Here is the kernel message without hexadecimal values since I wrote it manually. If further debugging informations are needed, just ask and I would be glad to provide them. lock order reversal 1st 0xc1b3a428 ESS Technology Maestro-2E (hardware status lock) @ dev/sound/pci/maestro.c:270 2nd 0xc0af5920 ACPI PCI power methods (ACPI PCI power methods) @ dev/acpia/acpi_pci.c:215 KDB: stack backtrace kdb_backtrace() witness_checkorder() _sx_lock() acpi_pci_set_powerstate_method() agg_power() agg_attach() device_attach() device_probe_and_attach() bus_generic_method() acpi_pci_attach() device_attach() device_probe_and_attach() bus_generic_method() acpi_pcib_attach() device_attach() device_probe_and_attach() bus_generic_attach() acpi_probe_children() acpi_attach() device_attach() device_probe_and_attach() bus_generic_attach() nexus_attach() device_attach() device_probe_and_attach() root_bus_configure() configure() mi_startup() begin() Regards, -- Jeremie Le Hen jeremie@le-hen.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 08:38:08 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2A9016A4CE for ; Tue, 23 Nov 2004 08:38:08 +0000 (GMT) Received: from relay.pair.com (relay00.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 275E043D58 for ; Tue, 23 Nov 2004 08:38:08 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 41927 invoked from network); 23 Nov 2004 08:38:04 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 23 Nov 2004 08:38:04 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iAN8c2Jq040469; Tue, 23 Nov 2004 09:38:02 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iAN8c1Hs040468; Tue, 23 Nov 2004 09:38:01 +0100 (CET) (envelope-from pho) Date: Tue, 23 Nov 2004 09:38:01 +0100 From: Peter Holm To: Jeff Roberson Message-ID: <20041123083801.GA40401@peter.osted.lan> References: <20041120000743.G18094@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041120000743.G18094@mail.chesapeake.net> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 08:38:09 -0000 On Sat, Nov 20, 2004 at 12:24:10AM -0500, Jeff Roberson wrote: > I have a patch that I would like people to test and review. It's > available here: > > http://www.chesapeake.net/~jroberson/smpffs.diff > I have a panic at http://www.holm.cc/stress/log/jeff02.html with GENERIC HEAD from Nov 22 14:40 UTC + your Giantless VFS patch. But the fault does not seem to related to your changes? -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 10:33:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDECB16A4CE for ; Tue, 23 Nov 2004 10:33:53 +0000 (GMT) Received: from ausc60pc101.us.dell.com (ausc60pc101.us.dell.com [143.166.85.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 804DA43D41 for ; Tue, 23 Nov 2004 10:33:53 +0000 (GMT) (envelope-from Muthu_T@Dell.com) Received: from ausx2kcpc115.aus.amer.dell.com (10.166.84.69) by ausc60pc101.us.dell.com with ESMTP; 23 Nov 2004 04:33:54 -0600 X-Ironport-AV: i="3.87,106,1099288800"; d="scan'208"; a="139446203:sNHT20328372" X-MimeOLE: Produced By Microsoft Exchange V6.0.6527.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 23 Nov 2004 04:33:47 -0600 Message-ID: <71F713C5E3CB7F4F9ACCBBB8E9BE318A39E348@blrx2kmbgl101.blr.amer.dell.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: supported new Dell PERC cards - need to add to the Hardware notes Thread-Index: AcTRR+oKUP7dxda2SsCd80ujKKj5pg== From: To: X-OriginalArrivalTime: 23 Nov 2004 10:33:48.0145 (UTC) FILETIME=[EA90AE10:01C4D147] Subject: supported new Dell PERC cards - need to add to the Hardware notes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 10:33:54 -0000 Hi Can anybody add the following cards in i386/amd64 Hardware Notes for 5.3 Release? PERC 4e/Si (Found on PE1850 - EMT64) PERC 4e/Di (Found on PE2850 - EMT64) Both cards are supported by amr(4) driver. Thanks. --T. Muthu Mohan From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 10:53:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 228F316A4CE for ; Tue, 23 Nov 2004 10:53:16 +0000 (GMT) Received: from zaphod.nitro.dk (port324.ds1-khk.adsl.cybercity.dk [212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 880C043D48 for ; Tue, 23 Nov 2004 10:53:15 +0000 (GMT) (envelope-from simon@zaphod.nitro.dk) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id 5D3C711BB5; Tue, 23 Nov 2004 11:53:14 +0100 (CET) Date: Tue, 23 Nov 2004 11:53:14 +0100 From: "Simon L. Nielsen" To: Muthu_T@Dell.com Message-ID: <20041123105313.GC753@zaphod.nitro.dk> References: <71F713C5E3CB7F4F9ACCBBB8E9BE318A39E348@blrx2kmbgl101.blr.amer.dell.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="98e8jtXdkpgskNou" Content-Disposition: inline In-Reply-To: <71F713C5E3CB7F4F9ACCBBB8E9BE318A39E348@blrx2kmbgl101.blr.amer.dell.com> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: supported new Dell PERC cards - need to add to the Hardware notes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 10:53:16 -0000 --98e8jtXdkpgskNou Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004.11.23 04:33:47 -0600, Muthu_T@Dell.com wrote: > Hi >=20 > Can anybody add the following cards in i386/amd64 Hardware Notes for > 5.3 Release? >=20 > PERC 4e/Si (Found on PE1850 - EMT64) > PERC 4e/Di (Found on PE2850 - EMT64) >=20 > Both cards are supported by amr(4) driver. I just added them to the -CURRENT amr(4) manual page, which will mean they will be included in the Hardware Notes, and I will merge it to RELENG_5 in a few days. The Hardware Notes for 5.3 are frozen, but the entries will be included in the Hardware Notes for the next FreeBSD releases. Thanks for letting us know! --=20 Simon L. Nielsen FreeBSD Documentation Team --98e8jtXdkpgskNou Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBoxaZh9pcDSc1mlERAp8bAJ4+BPhXlniYXBa8ZwFRoB3YUShlLgCgmLtx nwVwXUI90S5KUa5/lNTo/yM= =/fUy -----END PGP SIGNATURE----- --98e8jtXdkpgskNou-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 14:47:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D5B4F16A4CE; Mon, 22 Nov 2004 14:47:27 +0000 (GMT) Received: from south-station-annex.mit.edu (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6576643D1D; Mon, 22 Nov 2004 14:47:27 +0000 (GMT) (envelope-from simsong@csail.mit.edu) Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76])iAMEkWmu011433; Mon, 22 Nov 2004 09:47:19 -0500 (EST) Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72])iAMEjBGf013500; Mon, 22 Nov 2004 09:45:11 -0500 (EST) Received: from melbourne-city-street.mit.edu (OUTGOING-LEGACY.MIT.EDU [18.7.22.104])iAMEj9NC014767; Mon, 22 Nov 2004 09:45:10 -0500 (EST) Received: from [192.168.1.21] (ip-64-7-15-235.dsl.bos.megapath.net [64.7.15.235]) )iAMEj7jc006870; Mon, 22 Nov 2004 09:45:08 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v619) To: freebsd-current@freebsd.org Message-Id: <1A70D4C2-3C95-11D9-A5BE-000A95DA91E2@csail.mit.edu> Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-15-420939675; protocol="application/pkcs7-signature" From: "Simson L. Garfinkel" Date: Mon, 22 Nov 2004 09:45:07 -0500 X-Mailer: Apple Mail (2.619) X-Scanned-By: MIMEDefang 2.42 X-Mailman-Approved-At: Tue, 23 Nov 2004 13:16:19 +0000 X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: rwatson@freebsd.org cc: robert@fledge.watson.org Subject: Page fault in FreeBSD 5.3 on IBM e325, Dual AMD64 2.2GHz, 4GB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 14:47:28 -0000 --Apple-Mail-15-420939675 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed I had precisely this same problem over the weekend moving from FreeBSD 5.3-RC1 to 5.3_RELENG. Other symptoms: network stack problems at boot (ntpdate didn't work until after the system was fully up.) Reverting to RC1 seems to have solved the problem. On Mon, 22 Nov 2004, Ganbold wrote: > Fatal trap 12: page fault while in kernel mode > cpuid = 1; apic id = 01 > fault virtual address = 0x18 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xffffffff80277fc0 > stack pointer = 0x10:0xffffffffb36ab830 > frame pointer = 0x10:0xffffffffb36ab890 > 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 = 44 (swi1: net) > [thread 100044] > Stopped at m_copym+0x190: incl %ecx <...> > ------------------------------------------------------------------------ -------------------------------- > > It seems to me the problem is related to network stack and threading. > Am I right? How to solve this problem? I've seen reports of this problem with and without debug.mpsafenet=1, which suggests it is a network stack bug but not specific to locking. I've also seen reports that disabling TCP SACK will make the problem go away, which would be good to confirm. I spent the weekend building up some more expertise in TCP and reading a lot of TCP code, and hope to look at this problem in more detail today. You may want to try turning off TCP sack using net.inet.tcp.sack.enable=0 in sysctl.conf (or loader.conf). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert at fledge.watson.org Principal Research Scientist, McAfee Research --Apple-Mail-15-420939675-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 02:29:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4668616A4CE for ; Tue, 23 Nov 2004 02:29:12 +0000 (GMT) Received: from mirapoint1.tis.cwru.edu (mirapoint1.TIS.CWRU.Edu [129.22.104.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3FE143D2F for ; Tue, 23 Nov 2004 02:29:11 +0000 (GMT) (envelope-from jrh29@po.cwru.edu) Received: from [192.168.1.100] (oh-clevelandheights-cdnt1-bg1b-147.clvdoh.adelphia.net [68.170.192.147]) by mirapoint1.tis.cwru.edu (MOS 3.5.4-GR) with ESMTP id DFT13380 (AUTH jrh29); Mon, 22 Nov 2004 21:29:09 -0500 (EST) In-Reply-To: <200411222122.22452.mistry.7@osu.edu> References: <200411222122.22452.mistry.7@osu.edu> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-18-463185603" Message-Id: <76F79122-3CF7-11D9-BA1A-000A95841F44@po.cwru.edu> Content-Transfer-Encoding: 7bit From: Justin Hibbits Date: Mon, 22 Nov 2004 21:29:13 -0500 To: Anish Mistry X-Pgp-Agent: GPGMail 1.0.2 X-Mailer: Apple Mail (2.619) X-Mailman-Approved-At: Tue, 23 Nov 2004 13:16:19 +0000 cc: freebsd-current@freebsd.org Subject: Re: ATI TV Wonder support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 02:29:12 -0000 --Apple-Mail-18-463185603 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed On Nov 22, 2004, at 21:22, Anish Mistry wrote: > On Sunday 21 November 2004 10:00 pm, Justin Hibbits wrote: >> This patch gives more or less full ATI TV Wonder support to the bktr >> driver. >> > Awesome. >> The sound doesn't mute at close, but that might be xawtv's fault, but >> I >> don't know which to accuse or look at. But, other than that, it seems >> pretty good. >> > I've having some trouble using it though, the sound doesn't seem to > work > just as before. Is there something extra I need to add to my kernel > besides bktr? > On boot: > bktr0: mem 0xe3101000-0xe3101fff irq 11 at device 8.0 > on > pci0 > bktr0: [GIANT-LOCKED] > bktr0: Detected a MSP3445G-B8 at 0x80 > bktr0: ATI TV Wonder, Philips NTSC tuner, msp3400c stereo. > pci0: at device 8.1 (no driver attached) > And when I start it: > bktr0: Detected a MSP3445G-B8 at 0x80 > > You should also send-pr this if you haven't already. > > Thanks, > > -- > Anish Mistry > Oh, you need to build it with the msp3400c driver, so add the line: options BKTR_NEW_MSP34XX_DRIVER to your config file. The card doesn't have any mux, only that chip, so you need the driver. I've found a hackish solution to the sound problem, by resetting the card on exit. It's horrible, so I won't include it in the patch, but it works for me. If you want to use this too, add: if (bktr->card.msp3400c ) msp_dpl_reset( bktr, bktr->msp_addr ); to bktr_core.c, at line 1171. I'll resend my previous message as a send-pr later, when I have a little more time to test it. - Justin -- "And now, if you'll excuse me, I'm in the middle of 15 things, all annoying" -- Lt. Cmdr Susan Ivanova, Babylon 5 --Apple-Mail-18-463185603 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.2.4 (Darwin) iD8DBQFBoqB9qt29EJDZlM4RAtqIAJ4rw3d4XMDluavDY7C8+AbWgLa3QACfQDs2 a/LKWNDCdQb3GeU6+ibbGdc= =225h -----END PGP SIGNATURE----- --Apple-Mail-18-463185603-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 04:00:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F9DA16A4CF for ; Tue, 23 Nov 2004 04:00:41 +0000 (GMT) Received: from mirapoint2.tis.cwru.edu (mirapoint2.TIS.CWRU.Edu [129.22.104.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id B55D143D45 for ; Tue, 23 Nov 2004 04:00:40 +0000 (GMT) (envelope-from jrh29@po.cwru.edu) Received: from [192.168.1.100] (oh-clevelandheights-cdnt1-bg1b-147.clvdoh.adelphia.net [68.170.192.147]) by mirapoint2.tis.cwru.edu (MOS 3.5.4-GR) with ESMTP id CTB07401 (AUTH jrh29); Mon, 22 Nov 2004 23:00:38 -0500 (EST) In-Reply-To: <200411222256.41638.mistry.7@osu.edu> References: <200411222122.22452.mistry.7@osu.edu> <76F79122-3CF7-11D9-BA1A-000A95841F44@po.cwru.edu> <200411222256.41638.mistry.7@osu.edu> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-19-468670136" Message-Id: <3C013935-3D04-11D9-BA1A-000A95841F44@po.cwru.edu> Content-Transfer-Encoding: 7bit From: Justin Hibbits Date: Mon, 22 Nov 2004 23:00:37 -0500 To: Anish Mistry X-Pgp-Agent: GPGMail 1.0.2 X-Mailer: Apple Mail (2.619) X-Mailman-Approved-At: Tue, 23 Nov 2004 13:16:19 +0000 cc: freebsd-current@freebsd.org Subject: Re: ATI TV Wonder support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 04:00:41 -0000 --Apple-Mail-19-468670136 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed On Nov 22, 2004, at 22:56, Anish Mistry wrote: > On Monday 22 November 2004 09:29 pm, you wrote: >> On Nov 22, 2004, at 21:22, Anish Mistry wrote: >>> On Sunday 21 November 2004 10:00 pm, Justin Hibbits wrote: >>>> This patch gives more or less full ATI TV Wonder support to the bktr >>>> driver. >>> >>> Awesome. >>> >>>> The sound doesn't mute at close, but that might be xawtv's fault, >>>> but >>>> I >>>> don't know which to accuse or look at. But, other than that, it >>>> seems pretty good. >>> >>> I've having some trouble using it though, the sound doesn't seem to >>> work >>> just as before. Is there something extra I need to add to my kernel >>> besides bktr? >>> On boot: >>> bktr0: mem 0xe3101000-0xe3101fff irq 11 at device 8.0 >>> on >>> pci0 >>> bktr0: [GIANT-LOCKED] >>> bktr0: Detected a MSP3445G-B8 at 0x80 >>> bktr0: ATI TV Wonder, Philips NTSC tuner, msp3400c stereo. >>> pci0: at device 8.1 (no driver attached) >>> And when I start it: >>> bktr0: Detected a MSP3445G-B8 at 0x80 >>> >>> You should also send-pr this if you haven't already. >>> >>> Thanks, >>> >>> -- >>> Anish Mistry >> >> Oh, you need to build it with the msp3400c driver, so add the line: >> >> options BKTR_NEW_MSP34XX_DRIVER >> >> to your config file. The card doesn't have any mux, only that chip, >> so >> you need the driver. I've found a hackish solution to the sound >> problem, by resetting the card on exit. It's horrible, so I won't >> include it in the patch, but it works for me. If you want to use this >> too, add: >> >> if (bktr->card.msp3400c ) >> msp_dpl_reset( bktr, bktr->msp_addr ); >> >> to bktr_core.c, at line 1171. >> >> >> I'll resend my previous message as a send-pr later, when I have a >> little more time to test it. >> > Thanks, but I'm getting a weird panic with 5-STABLE, which I'm > assuming you > aren't seeing. Any ideas? > > panic: sleeping without a mutex > KDB: enter: panic > [thread 100012] > Stopped at kbd_enter+0x2c: leave > db> tr > kbd_enter(c0635ca1,100,c1b6c54c,c1b41320,0) at kbd_enter+0x2c > panic(c06363e5,0,0,0,c1b37c00) at panic+0x10a > msleep(c1b6c54c,0,4c,c064007d,0) at msleep+0x2bf > msp3410d_thread(c1bd8000,d0181d48,c1db8000,c845e1d4,0) at > msp3410d_thread+0x5b > fork_exit(c045e1d4,c1db8000,d0181d48) at fork_exit+0x7e > fork_trampoline() at fork_trampoline+0x8 > --- trap 0x1, eip=0, esp=0xd0181d7c, ebd=0 --- > > dmesg: > http://am-productions.biz/docs/bigguy.txt.gz > kernel config: > http://am-productions.biz/docs/BIGGUY.gz > -- > Anish Mistry Oh yes, you need to compile it without witness support, or invariants (DDB is fine, though). It, of course, cuts out a ton of useful debugging info for other parts, but it's the only way, unfortunately. - Justin -- "And now, if you'll excuse me, I'm in the middle of 15 things, all annoying" -- Lt. Cmdr Susan Ivanova, Babylon 5 --Apple-Mail-19-468670136 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.2.4 (Darwin) iD8DBQFBorXuqt29EJDZlM4RAiNjAJ9yZAyq5Pd1x3JDngJeo5mjqb6PSwCeOxNg 7xLKPN6Czjs4AiehsX/p2/8= =AIEv -----END PGP SIGNATURE----- --Apple-Mail-19-468670136-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 02:41:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE8EE16A4CE for ; Tue, 23 Nov 2004 02:41:48 +0000 (GMT) Received: from master4.yvr1.superb.net (master4.yvr1.superb.net [209.82.78.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFD2A43D1D for ; Tue, 23 Nov 2004 02:41:47 +0000 (GMT) (envelope-from gbaratto@superb.net) Received: from chivas (fw.yvr1.superb.net [209.82.78.2]) iAN2flh7004473 for ; Mon, 22 Nov 2004 18:41:47 -0800 (PST) Message-ID: <008a01c4d105$e99f4f30$9c01a8c0@chivas> From: "Gustavo A. Baratto" To: Date: Mon, 22 Nov 2004 18:41:00 -0800 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.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailman-Approved-At: Tue, 23 Nov 2004 13:18:52 +0000 Subject: module_path X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 02:41:48 -0000 hello there, Since I have seen it in the errata, here it goes: I have upgraded from 5.1 to 5.3, and the newly installed /boot/defaults/loader.conf has this set: module_path="/boot/modules" so, whenever I try to load ipfw or ipf, or even use kldload, I get this error: --- /etc/rc.d/ipfw start kldload: can't load ipfw: No such file or directory /etc/rc.d/ipfw: WARNING: unable to load firewall module. --- # sysctl kern.module_path kern.module_path: /boot/modules I know that I can override that by adding module_path="/boot/kernel" in /boot/loader.conf, but I think the default file should be fixed to add at least /boot/kernel, right? cheers From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 13:20:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FA4316A4CE for ; Tue, 23 Nov 2004 13:20:12 +0000 (GMT) Received: from lara.cc.fer.hr (lara.cc.fer.hr [161.53.72.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3162643D1F for ; Tue, 23 Nov 2004 13:20:11 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [127.0.0.1] (localhost.cc.fer.hr [127.0.0.1]) by lara.cc.fer.hr (8.13.1/8.13.1) with ESMTP id iANDK7m9010291 for ; Tue, 23 Nov 2004 14:20:07 +0100 (CET) (envelope-from ivoras@fer.hr) Message-ID: <41A33907.5020703@fer.hr> Date: Tue, 23 Nov 2004 14:20:07 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 0.9 (X11/20041111) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org References: <41A2488F.8030802@fer.hr> <20041122215228.J568@korben.in.tern> In-Reply-To: <20041122215228.J568@korben.in.tern> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: gvinum panic? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 13:20:12 -0000 Lukas Ertl wrote: > On Mon, 22 Nov 2004, Ivan Voras wrote: > >> I'm consistently getting a system panic, trap #12 in process g_event >> when I try: > > > Are you sure that kernel (modules) and userland are in sync? Thanks, it looks like they've been unsynced for a while :( It's ok now. But, the performance is pretty bad (same with regular vinum). I tried setting up graid3 class with same parameters, and got these results: linear read (1024 MB file, blocks of 32768) ................. 38.5 MB/s linear write (1024 MB file, blocks of 32768) ................ 16.8 MB/s random read (1024 MB file, blocks of 32768) ................. 41.9 MB/s random write (1024 MB file, blocks of 32768) ................ 3.4 MB/s with raid5, gvinum or vinum, I get these: linear read (1024 MB file, blocks of 32768) ................. 27.8 MB/s linear write (1024 MB file, blocks of 32768) ................ 4.2 MB/s random read (1024 MB file, blocks of 32768) ................. 44.2 MB/s random write (1024 MB file, blocks of 32768) ................ 1.9 MB/s (random reads are really random, no clustering or anything). My setup is 2 IDE channels with three discs, so one is a slave (and contains the parity disc in case of raid3). Do these numbers make sense? I'll certainly go with raid3 as it is... From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 13:43:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADFEE16A4CF for ; Tue, 23 Nov 2004 13:43:13 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id D32A843D3F for ; Tue, 23 Nov 2004 13:43:12 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iANDgCZg011509 for ; Wed, 24 Nov 2004 00:12:12 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Wed, 24 Nov 2004 00:13:04 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iANDbHh23883 for ; Wed, 24 Nov 2004 00:07:17 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id XM1D9FXL; Wed, 24 Nov 2004 00:07:15 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iANDbXfX018239 for ; Wed, 24 Nov 2004 00:07:33 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iANDbX0X018238 for freebsd-current@freebsd.org; Wed, 24 Nov 2004 00:07:33 +1030 (CST) (envelope-from wilkinsa) Date: Wed, 24 Nov 2004 00:07:33 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20041123133729.GA18173@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org References: <008a01c4d105$e99f4f30$9c01a8c0@chivas> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <008a01c4d105$e99f4f30$9c01a8c0@chivas> X-Message-Flag: "Beware of Outlook! It Bites " User-Agent: Mutt/1.5.6i Subject: Re: module_path X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 13:43:13 -0000 /usr/src/UPDATING: 20040806: Module loading has been fixed. Some older installations will drop proper module_path initialization and modules will fail to load properly. If you have a line in /boot/loader.rc that says: "initialize drop", do (i386 only): cp /usr/src/sys/boot/i386/loader/loader.rc /boot/loader.rc chown root:wheel /boot/loader.rc chmod 444 /boot/loader.rc - aW 0n Mon, Nov 22, 2004 at 06:41:00PM -0800, Gustavo A. Baratto wrote: > hello there, > > Since I have seen it in the errata, here it goes: > > I have upgraded from 5.1 to 5.3, and the newly installed > /boot/defaults/loader.conf has this set: > module_path="/boot/modules" > > so, whenever I try to load ipfw or ipf, or even use kldload, I get this > error: > --- > /etc/rc.d/ipfw start > kldload: can't load ipfw: No such file or directory > /etc/rc.d/ipfw: WARNING: unable to load firewall module. > --- > > # sysctl kern.module_path > kern.module_path: /boot/modules > > I know that I can override that by adding module_path="/boot/kernel" in > /boot/loader.conf, but I think the default file should be fixed to add at > least /boot/kernel, right? > > cheers > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 17:19:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4EDA516A4CE for ; Tue, 23 Nov 2004 17:19:57 +0000 (GMT) Received: from mail.evip.pl (mail.evip.com.pl [212.244.157.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1145F43D2F for ; Tue, 23 Nov 2004 17:19:56 +0000 (GMT) (envelope-from w@evip.pl) Received: from drwebc by mail.evip.pl with drweb-scanned (Exim 4.22) id 1CWeKV-000Dcs-Rm for current@freebsd.org; Tue, 23 Nov 2004 18:19:51 +0100 Received: from w by mail.evip.pl with local (Exim 4.22) id 1CWeKV-000Dcm-OJ for current@freebsd.org; Tue, 23 Nov 2004 18:19:51 +0100 Date: Tue, 23 Nov 2004 18:19:51 +0100 From: Wiktor Niesiobedzki To: current@freebsd.org Message-ID: <20041123171951.GG3584@mail.evip.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: Putty or libcrypto bug? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 17:19:57 -0000 Hi, When I try to run putty it dumps core. From what I found, it is triggered by having nss_ldap configured to use TLS (ldaps://). The backtrace is folowing w@portal:~$ putty zsh: segmentation fault (core dumped) putty w@portal:~$ gdb =putty putty.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"... Core was generated by `putty'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/X11R6/lib/libgtk12.so.2...done. Loaded symbols for /usr/X11R6/lib/libgtk12.so.2 Reading symbols from /usr/X11R6/lib/libgdk12.so.2...done. Loaded symbols for /usr/X11R6/lib/libgdk12.so.2 Reading symbols from /usr/local/lib/libgmodule12.so.3...done. Loaded symbols for /usr/local/lib/libgmodule12.so.3 Reading symbols from /usr/local/lib/libglib12.so.3...done. Loaded symbols for /usr/local/lib/libglib12.so.3 Reading symbols from /usr/local/lib/libintl.so.6...done. Loaded symbols for /usr/local/lib/libintl.so.6 Reading symbols from /usr/X11R6/lib/libXi.so.6...done. Loaded symbols for /usr/X11R6/lib/libXi.so.6 Reading symbols from /usr/X11R6/lib/libXext.so.6...done. Loaded symbols for /usr/X11R6/lib/libXext.so.6 Reading symbols from /usr/X11R6/lib/libX11.so.6...done. Loaded symbols for /usr/X11R6/lib/libX11.so.6 Reading symbols from /lib/libm.so.3...done. Loaded symbols for /lib/libm.so.3 Reading symbols from /lib/libc.so.6...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/libm.so.2...done. Loaded symbols for /lib/libm.so.2 Reading symbols from /usr/local/lib/libiconv.so.3...done. Loaded symbols for /usr/local/lib/libiconv.so.3 Reading symbols from /usr/local/lib/nss_ldap.so.1...done. Loaded symbols for /usr/local/lib/nss_ldap.so.1 Reading symbols from /usr/local/lib/libldap-2.2.so.7...done. Loaded symbols for /usr/local/lib/libldap-2.2.so.7 Reading symbols from /usr/local/lib/liblber-2.2.so.7...done. Loaded symbols for /usr/local/lib/liblber-2.2.so.7 Reading symbols from /usr/lib/libssl.so.3...done. Loaded symbols for /usr/lib/libssl.so.3 Reading symbols from /lib/libcrypto.so.3...done. Loaded symbols for /lib/libcrypto.so.3 Reading symbols from /usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2...done. Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2 Reading symbols from /lib/libc.so.5...done. Loaded symbols for /lib/libc.so.5 Reading symbols from /usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2...done. Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 sk_new (addr=0x0, port=1215526572, privport=-1077945272, oobinline=1215306875, nodelay=12, keepalive=1215450516, plug=0x80e2614) at ../unix/uxnet.c:421 421 ../unix/uxnet.c: No such file or directory. in ../unix/uxnet.c (gdb) bt #0 sk_new (addr=0x0, port=1215526572, privport=-1077945272, oobinline=1215306875, nodelay=12, keepalive=1215450516, plug=0x80e2614) at ../unix/uxnet.c:421 #1 0x487033de in sk_new_null () from /lib/libcrypto.so.3 #2 0x48701c7b in CRYPTO_set_ex_data_implementation () from /lib/libcrypto.so.3 #3 0x48701fb1 in CRYPTO_set_ex_data_implementation () from /lib/libcrypto.so.3 #4 0x48702682 in CRYPTO_get_ex_new_index () from /lib/libcrypto.so.3 #5 0x48684411 in X509_STORE_CTX_get_ex_new_index () from /lib/libcrypto.so.3 #6 0x48619dae in SSL_get_ex_data_X509_STORE_CTX_idx () from /usr/lib/libssl.so.3 #7 0x4861453d in SSL_CTX_new () from /usr/lib/libssl.so.3 #8 0x485dced3 in ldap_pvt_tls_init_def_ctx () from /usr/local/lib/libldap-2.2.so.7 #9 0x485dd400 in alloc_handle () from /usr/local/lib/libldap-2.2.so.7 #10 0x485ddc6c in ldap_int_tls_connect () from /usr/local/lib/libldap-2.2.so.7 #11 0x485dee8f in ldap_int_tls_start () from /usr/local/lib/libldap-2.2.so.7 #12 0x485bc50c in ldap_int_open_connection () from /usr/local/lib/libldap-2.2.so.7 #13 0x485ce7db in ldap_new_connection () from /usr/local/lib/libldap-2.2.so.7 #14 0x485bbe81 in ldap_open_defconn () from /usr/local/lib/libldap-2.2.so.7 #15 0x485ce297 in ldap_send_initial_request () from /usr/local/lib/libldap-2.2.so.7 #16 0x485c3167 in ldap_sasl_bind () from /usr/local/lib/libldap-2.2.so.7 #17 0x485c3ac5 in ldap_simple_bind () from /usr/local/lib/libldap-2.2.so.7 #18 0x485a1cc0 in _nss_ldap_init () from /usr/local/lib/nss_ldap.so.1 #19 0x485a1a92 in _nss_ldap_init () from /usr/local/lib/nss_ldap.so.1 #20 0x485a2bbc in _nss_ldap_search_s () from /usr/local/lib/nss_ldap.so.1 #21 0x485a3325 in _nss_ldap_getbyname () from /usr/local/lib/nss_ldap.so.1 #22 0x485a4b59 in _nss_ldap_getpwuid_r () from /usr/local/lib/nss_ldap.so.1 #23 0x483e3791 in __nss_compat_getpwuid_r () from /lib/libc.so.6 #24 0x4844c7cb in nsdispatch () from /lib/libc.so.6 #25 0x48422105 in getpwuid_r () from /lib/libc.so.6 #26 0x482b14e0 in g_get_any_init () from /usr/local/lib/libglib12.so.3 #27 0x482b1840 in g_get_home_dir () from /usr/local/lib/libglib12.so.3 #28 0x481d6ad7 in gtk_rc_append_default_module_path () from /usr/X11R6/lib/libgtk12.so.2 #29 0x481d6fc0 in gtk_rc_init () from /usr/X11R6/lib/libgtk12.so.2 #30 0x481a9042 in gtk_init_check () from /usr/X11R6/lib/libgtk12.so.2 #31 0x481a90f6 in gtk_init () from /usr/X11R6/lib/libgtk12.so.2 #32 0x08071fb5 in pt_main (argc=1, argv=0xbfbfecb4) at ../unix/pterm.c:3270 #33 0x080aad69 in main (argc=135144980, argv=0x80e2614) at ../unix/uxputty.c:140 As we may see, putty defines sk_new function and function of the same name exists in libcrypto (in /usr/src/crypto/openssl/crypto/stack/stack.c). And now my question: should the putty change the function name (what sound wired) or there should be done some magic in libcrypto, so such situations would not happen (what sounds tricky)? Cheers, Wiktor Niesiobedzki From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 17:26:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0204F16A4CE for ; Tue, 23 Nov 2004 17:26:43 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79C8B43D49 for ; Tue, 23 Nov 2004 17:26:42 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id iANHQfOk092952 for ; Tue, 23 Nov 2004 12:26:41 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-current@freebsd.org Date: Tue, 23 Nov 2004 12:26:38 -0500 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200411231226.38172.jkim@niksun.com> X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Transparent bridges (a. k. a. HUB-to-PCI bridges)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 17:26:43 -0000 While I was booting Linux, I saw a 'transparent bridge' from dmesg and started digging up because I was fighting against 'interrupt storming' and 'stray IRQ' problems with the latest Intel chipsets recently and I had a feeling that it's somehow related. http://lxr.linux.no/source/drivers/pci/probe.c?v=2.6.8.1#L195 http://lxr.linux.no/source/arch/i386/pci/fixup.c?v=2.6.8.1#L192 http://lxr.linux.no/source/arch/i386/pci/irq.c?v=2.6.8.1#L870 http://lxr.linux.no/source/arch/i386/pci/irq.c?v=2.6.8.1#L1017 But I don't see any special treatment in FreeBSD's PCI driver. 1. Is this relevant for FreeBSD? 2. Is this related to the problems (esp. SMP)? Thanks, Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 17:37:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AB1916A4CE for ; Tue, 23 Nov 2004 17:37:18 +0000 (GMT) Received: from omoikane.mb.skyweb.ca (64-42-246-34.mb.skyweb.ca [64.42.246.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 193EE43D5A for ; Tue, 23 Nov 2004 17:37:18 +0000 (GMT) (envelope-from mark@skyweb.ca) Received: by omoikane.mb.skyweb.ca (Postfix, from userid 1001) id 424EF61DA1; Tue, 23 Nov 2004 11:37:17 -0600 (CST) From: Mark Johnston To: current@freebsd.org, freebsd-cvs-summary@lists.enderunix.org Date: Tue, 23 Nov 2004 11:37:16 -0600 User-Agent: KMail/1.6.1 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200411231137.16215.mjohnston@skyweb.ca> Subject: cvs-src summary for November 15-22 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 17:37:18 -0000 FreeBSD cvs-src summary for 15/11/04 to 22/11/04 ++++++++++++++++++++++++++++++++++++++++++++++++ This is a regular weekly summary of FreeBSD's cutting-edge development. It is intended to help the FreeBSD community keep up with the fast-paced work going on in FreeBSD-CURRENT by distilling the deluge of data from the CVS mailing list into a (hopefully) easy-to-read newsletter. This newsletter is marked up in reStructuredText_, so any odd punctuation that you see is likely intended for the reST parser. .. _reStructuredText: http://docutils.sourceforge.net/rst.html You can get old summaries, and an HTML version of this one, at http://www.xl0.org/FreeBSD/. Please send any comments to Mark Johnston (mark at xl0.org). For Lukasz Dudek and Szymon Roczniak's Polish translations of these summaries, which may lag the English ones slightly, please see http://mocart.pinco.pl/FreeBSD/. .. contents:: ============ New features ============ MAC framework support added for System V IPC -------------------------------------------- Robert Watson (rwatson) committed support to the MAC (Mandatory Access Control) framework for System V IPC objects and operations. Most operations involving System V messages, message queues, semaphores, and shared memory segments can now be protected with MAC. For information and tutorials on FreeBSD's MAC layer, please see `chapter 15 of the Handbook`_. .. _`chapter 15 of the Handbook`: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mac.html This code was submitted by Dandekar Hrishikesh, obtained from the TrustedBSD project, and sponsored by DARPA, SPAWAR, and McAfee Research. http://www.freebsd.org/cgi/mid.cgi?200411171310.iAHDAGBk066415 hme Ethernet driver now MPSAFE ------------------------------ Pyun YongHyeon (yongari) updated hme, the driver for many Sun Ethernet cards, to be MPSAFE. MPSAFE drivers can run without the Giant system lock, allowing better performance. http://www.freebsd.org/cgi/mid.cgi?200411220646.iAM6kVG7018054 =============== Notable changes =============== 386 support removed ------------------- John Baldwin (jhb) made changes to remove support for the 386 processor in FreeBSD 6-CURRENT. He eliminated 386-specific code from the kernel, run-time linker, C library, and system Makefiles. http://www.freebsd.org/cgi/mid.cgi?200411162042.iAGKgWrF095430 ================= Discussion topics ================= Keyboard technologies and drivers --------------------------------- Maksim Yevmenkin (emax) committed support for a virtual AT keyboard driver, called vkbd. Poul-Henning Kamp (phk) asked, "I thought we had one of those already ?" Maksim replied, "when? where? did i miss it?" Poul-Henning replied, "sys/dev/kbd (and various MD stuff all over the place) ?" Maksim responded, "perhaps i'm missing something here. the idea behind vkdb(4) is to create a keyboard [ . . . ] that accepts scan codes from userspace and not from real hardware. [ . . . ] what i want to do is to obtain scan codes from bluetooth keyboard and then feed them into the kernel. [ . . . ] i do not think i can do it with kdb(4), can i?" Brooks Davis (brooks) suggested, "Have you considered making the virtual keyboard an in kernel client of it's child keyboard(s)? If you don't do this, you can't use the virtual keyboard in single user mode or in the debugger." Maksim replied, "in case of bluetooth hid all scan codes have to passed through bluetooth stack. i definitely do not want to use bluetooth keyboard in ddb(4) or in single user mode :)" Brooks responded, "I'm primairly intrested in solving the problem of machines with a AT keyboard controller (which currently attached non-existant keyboards to allow hot-pluging) and a USB keyboard." M. Warner Losh (imp) responded, "I think emax's vkbd isn't the same as the 'many to one' keyboard mux driver that's been talked about to solve [that]." Maksim replied, "that is true, but... you \*could\* obtain scan codes from two or more sources and write them into the \*same\* vkbd. [ . . . ] the only problem is the vkbd state (shifts controls etc)." Philip Paeps (philip) also replied to Brooks's post about AT+USB machines, saying, "My idea would be to feed all 'input events' from hardware drivers into a pseudo-driver, serialize it, and send it on to the higher layers of the system." Brooks responded, "That's basicly what I would like to see. I don't think we need to support people hitting the accent key on one keyboard and then finishing typing on the other, but we do need to support multiple keyboards if only because the users expect it." Philip replied, "I'd like to assume that the fundamental 'event' from a keyboard to reach the console is going to be a 'character'. [ . . . ] Alt on kbd0 followed by 'a' on kbd1 should probably translate to just 'a'." He also noted, "If we're going to let people have multiple keyboards, there will be those who will want to have a US-qwerty and a Belgian azerty side-by-side. Mapping keys will probably need to be handled by the driver (or the input system) on a per-device basis rather than by the console driver. That little headache has been fermenting at the back of my head since I first started thinking about writing an input layer." Brooks replied, "From looking at the atkbd driver, I thought we were fairly character oriented[ . . . . ] The seperate keymap issue is one I hadn't thought of since I'm in US-ASCII land. ;-) It could actually make a fair bit of sense to hook keyboards up that way. On the other hand, getting the single keymap case working and doing it well would be a huge step in the right direction." Marcel Moolenaar (marcel) also replied, saying, "I'm no guru in this regard, but it's probably best to take it one step at a time." He then gave some suggestions for possible implementations. Scott Long (scottl) replied to Maksim's earlier post about the bluetooth stack, saying, "I appreciate the work here, but we are starting to grow too many independent keyboard abstractions that don't seem to work together and don't seem to solve the primary problem that we have right now. What we really need is a single unified keyboard and mouse virtualization layer that allows bluetooth, usb, and at/ps2 devices to plug in at the bottom and talk to the one or more console interfaces at the top. [ . . . ] And yt _does_ need to work in single user mode and in DDB. [ . . . ] Brooks had talked about working on something similar to what I've described above, so please work with him to mold your vkbd work into that model." Maksim responded, "i did sent email to current asking for comments. did not get much feedback." He replied to Scott's suggestion about Brooks's work, saying, "very well. i touched it. might as well try and fix it :) anyone has any ideas? code? anything? oh, one more thing, would you like me to back vkbd(4) out?" Scott replied, "If there is no chance that the BT device could be needed for DDB or single-user mode then I guess that your driver is a good thing, though the 'vkbd' name is a bit misleading since it really only applies to BT." Maksim replied, "bluetooth keyboard definitely not needed in ddb and single mode (imo). but vkbd is not bluetooth specific. you could write an application that will tunnel at scancodes over the network say." Marcel responded to this, saying, "I very strongly disagree with this [that bluetooth is not needed in ddb/single user]. In fact, it's this sentiment that created the PS/2 vs USB keyboard problem for which we need a mux. [ . . . ] I think it's a mistake to treat a PS/2 keyboard different from any other keyboard simply because the interface is primitive. [ . . . ] Other than that. I think vkbd(4) can stay. Between no support and partial or imperfect support, we might as well keep the imperfect support until we're done perfecting things." Warner replied, "If we make it so that vkbd is also useful from whthin the kernel, then we can use it to implement many different things. [ . . . ] If bluetooth keyboards do become common place, we'll have to move bluetooth into the kernel to support them in single user mode or in ddb." Warner also replied to Scott's post about vkbd being Bluetooth-specific, saying, "Having looked at the code, it looks like one could also use it to implment a newton keyboard interface as well." He explained that the Newton keyboard is a small, serially-attached keyboard used with tiny laptops. Brooks responded, "vkbd is probably actually a good place to start working on the mux. The decision to add the functionality to vkbd or to split it out to another driver is a separate issue and I can make it later." Philip replied to Scott's post about a unified virtualization layer, saying, "I sollicited ideas for a 'generic input core' layer on -arch not long ago :-) [ . . . ] My idea/dream/goal/foo is to have a little driver provide an interface to sit between [keyboard, mouse, and touchscreen drivers], and feed events back to syscons in a consistent sort of way." He talked a bit about an implementation that he has been working on. http://www.freebsd.org/cgi/mid.cgi?200411161659.iAGGxNiX087329 =================== Important bug fixes =================== Security vulnerability in fetch fixed ------------------------------------- Colin Percival (cperciva) committed a fix to fetch, which retrieves files via HTTP(S) and FTP. The fix corrects an integer overflow bug that could allow malicious HTTP servers to execute arbitrary code as the user running fetch. He also fixed the bug in 5-STABLE, 4-STABLE, and the security branches for 5.3, 5.2, 5.1, 5.0, 4.10, 4.9, 4.8, and 4.7. This bug was initially found and reported by Colin himself. A security advisory, `FreeBSD-SA-04:16.fetch`_, has been released. .. _`FreeBSD-SA-04:16.fetch`: ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-04:16.fetch.asc http://www.freebsd.org/cgi/mid.cgi?200411181206.iAIC6qbX048177 =============== Other bug fixes =============== Tim J. Robbins (tjr) fixed a bug in the regular expression code within the system libraries that could cause hangs in UTF-8 (Unicode) locales. The bug was found and reported be Jean-Yves Lefort. http://www.freebsd.org/cgi/mid.cgi?200411210314.iAL3EWrN019655 From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 18:36:32 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3662716A4CE for ; Tue, 23 Nov 2004 18:36:32 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5796043D41 for ; Tue, 23 Nov 2004 18:36:31 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iANIYCGn039662; Tue, 23 Nov 2004 11:34:13 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 23 Nov 2004 11:34:52 -0700 (MST) Message-Id: <20041123.113452.85414512.imp@bsdimp.com> To: jkim@niksun.com From: "M. Warner Losh" In-Reply-To: <200411231226.38172.jkim@niksun.com> References: <200411231226.38172.jkim@niksun.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Transparent bridges (a. k. a. HUB-to-PCI bridges)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 18:36:32 -0000 In message: <200411231226.38172.jkim@niksun.com> Jung-uk Kim writes: : While I was booting Linux, I saw a 'transparent bridge' from dmesg and : started digging up because I was fighting against 'interrupt : storming' and 'stray IRQ' problems with the latest Intel chipsets : recently and I had a feeling that it's somehow related. : : http://lxr.linux.no/source/drivers/pci/probe.c?v=2.6.8.1#L195 We do exactly this already in our pci pci bridge code. We allow allocation for all subresources appropriately. From see the PCIB_SUBTRACTIVE if statements in pcib_alloc_resource. : http://lxr.linux.no/source/arch/i386/pci/fixup.c?v=2.6.8.1#L192 We detect fixups correctly here. There's also some toshiba parts that we detect as well. From pci_pci.c: /* * Intel 815, 845 and other chipsets say they are PCI-PCI bridges, * but have a ProgIF of 0x80. The 82801 family (AA, AB, BAM/CAM, * BA/CA/DB and E) PCI bridges are HUB-PCI bridges, in Intelese. * This means they act as if they were subtractively decoding * bridges and pass all transactions. Mark them and real ProgIf 1 * parts as subtractive. */ if ((pci_get_devid(dev) & 0xff00ffff) == 0x24008086 || pci_read_config(dev, PCIR_PROGIF, 1) == 1) sc->flags |= PCIB_SUBTRACTIVE; : http://lxr.linux.no/source/arch/i386/pci/irq.c?v=2.6.8.1#L870 : http://lxr.linux.no/source/arch/i386/pci/irq.c?v=2.6.8.1#L1017 We already do the right kinds of dances for ioapic connected busses, and other busses that have table driven needs (eg pci $PIR and ACPI related stuff). Check out the legacy pci driver and the acpi_pci drivers for details. : But I don't see any special treatment in FreeBSD's PCI driver. I sure do. : 1. Is this relevant for FreeBSD? Yes. We already have the relevant code. : 2. Is this related to the problems (esp. SMP)? I doubt it. Warner From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 18:39:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A49E16A4CF for ; Tue, 23 Nov 2004 18:39:35 +0000 (GMT) Received: from aiolos.otenet.gr (aiolos.otenet.gr [195.170.0.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48F9943D5C for ; Tue, 23 Nov 2004 18:39:33 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226])iANIdVYk031276; Tue, 23 Nov 2004 20:39:31 +0200 Received: from orion.daedalusnetworks.priv (orion [127.0.0.1]) iANIdU54056405; Tue, 23 Nov 2004 20:39:30 +0200 (EET) (envelope-from keramida@linux.gr) Received: (from keramida@localhost)iANIdULA056404; Tue, 23 Nov 2004 20:39:30 +0200 (EET) (envelope-from keramida@linux.gr) Date: Tue, 23 Nov 2004 20:39:30 +0200 From: Giorgos Keramidas To: Wiktor Niesiobedzki Message-ID: <20041123183930.GA56352@orion.daedalusnetworks.priv> References: <20041123171951.GG3584@mail.evip.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041123171951.GG3584@mail.evip.pl> cc: current@freebsd.org Subject: Re: Putty or libcrypto bug? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 18:39:35 -0000 On 2004-11-23 18:19, Wiktor Niesiobedzki wrote: > Hi, > > When I try to run putty it dumps core. From what I found, it is triggered by > having nss_ldap configured to use TLS (ldaps://). The backtrace is folowing > > w@portal:~$ gdb =putty putty.core [...] > #0 sk_new (addr=0x0, port=1215526572, privport=-1077945272, oobinline=1215306875, nodelay=12, > keepalive=1215450516, plug=0x80e2614) at ../unix/uxnet.c:421 > 421 ../unix/uxnet.c: No such file or directory. > in ../unix/uxnet.c > (gdb) bt > #0 sk_new (addr=0x0, port=1215526572, privport=-1077945272, oobinline=1215306875, nodelay=12, > keepalive=1215450516, plug=0x80e2614) at ../unix/uxnet.c:421 > #1 0x487033de in sk_new_null () from /lib/libcrypto.so.3 > #2 0x48701c7b in CRYPTO_set_ex_data_implementation () from /lib/libcrypto.so.3 > #3 0x48701fb1 in CRYPTO_set_ex_data_implementation () from /lib/libcrypto.so.3 > #4 0x48702682 in CRYPTO_get_ex_new_index () from /lib/libcrypto.so.3 > #5 0x48684411 in X509_STORE_CTX_get_ex_new_index () from /lib/libcrypto.so.3 > #6 0x48619dae in SSL_get_ex_data_X509_STORE_CTX_idx () from /usr/lib/libssl.so.3 > #7 0x4861453d in SSL_CTX_new () from /usr/lib/libssl.so.3 > #8 0x485dced3 in ldap_pvt_tls_init_def_ctx () from /usr/local/lib/libldap-2.2.so.7 > #9 0x485dd400 in alloc_handle () from /usr/local/lib/libldap-2.2.so.7 > #10 0x485ddc6c in ldap_int_tls_connect () from /usr/local/lib/libldap-2.2.so.7 > #11 0x485dee8f in ldap_int_tls_start () from /usr/local/lib/libldap-2.2.so.7 > #12 0x485bc50c in ldap_int_open_connection () from /usr/local/lib/libldap-2.2.so.7 > #13 0x485ce7db in ldap_new_connection () from /usr/local/lib/libldap-2.2.so.7 > #14 0x485bbe81 in ldap_open_defconn () from /usr/local/lib/libldap-2.2.so.7 > #15 0x485ce297 in ldap_send_initial_request () from /usr/local/lib/libldap-2.2.so.7 > #16 0x485c3167 in ldap_sasl_bind () from /usr/local/lib/libldap-2.2.so.7 > #17 0x485c3ac5 in ldap_simple_bind () from /usr/local/lib/libldap-2.2.so.7 > #18 0x485a1cc0 in _nss_ldap_init () from /usr/local/lib/nss_ldap.so.1 > #19 0x485a1a92 in _nss_ldap_init () from /usr/local/lib/nss_ldap.so.1 > #20 0x485a2bbc in _nss_ldap_search_s () from /usr/local/lib/nss_ldap.so.1 > #21 0x485a3325 in _nss_ldap_getbyname () from /usr/local/lib/nss_ldap.so.1 > #22 0x485a4b59 in _nss_ldap_getpwuid_r () from /usr/local/lib/nss_ldap.so.1 > #23 0x483e3791 in __nss_compat_getpwuid_r () from /lib/libc.so.6 > #24 0x4844c7cb in nsdispatch () from /lib/libc.so.6 > #25 0x48422105 in getpwuid_r () from /lib/libc.so.6 > #26 0x482b14e0 in g_get_any_init () from /usr/local/lib/libglib12.so.3 > #27 0x482b1840 in g_get_home_dir () from /usr/local/lib/libglib12.so.3 > #28 0x481d6ad7 in gtk_rc_append_default_module_path () from /usr/X11R6/lib/libgtk12.so.2 > #29 0x481d6fc0 in gtk_rc_init () from /usr/X11R6/lib/libgtk12.so.2 > #30 0x481a9042 in gtk_init_check () from /usr/X11R6/lib/libgtk12.so.2 > #31 0x481a90f6 in gtk_init () from /usr/X11R6/lib/libgtk12.so.2 > #32 0x08071fb5 in pt_main (argc=1, argv=0xbfbfecb4) at ../unix/pterm.c:3270 > #33 0x080aad69 in main (argc=135144980, argv=0x80e2614) at ../unix/uxputty.c:140 > > As we may see, putty defines sk_new function and function of the same name > exists in libcrypto (in /usr/src/crypto/openssl/crypto/stack/stack.c). Good catch :-) This is a Bad Idea(TM) most of the time though. The library implements a function that other programs or libraries may depend upon to work in certain ways. Replacing the library function with a hand-rolled version may or may not work -- the latter in this case :-/ > And now my question: should the putty change the function name (what > sound wired) or there should be done some magic in libcrypto, so > such situations would not happen (what sounds tricky)? PuTTY can change the name of a function internal to the application a lot easier than a library. Changing the library affects all the programs linked to it, which is bound to be a lot more painful than changing putty. From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 18:59:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8083716A4CE for ; Tue, 23 Nov 2004 18:59:26 +0000 (GMT) Received: from mail.evip.pl (mail.evip.com.pl [212.244.157.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33BE043D39 for ; Tue, 23 Nov 2004 18:59:25 +0000 (GMT) (envelope-from w@evip.pl) Received: from drwebc by mail.evip.pl with drweb-scanned (Exim 4.22) id 1CWfsp-000E1K-Jq; Tue, 23 Nov 2004 19:59:23 +0100 Received: from w by mail.evip.pl with local (Exim 4.22) id 1CWfsp-000E1E-Gf; Tue, 23 Nov 2004 19:59:23 +0100 Date: Tue, 23 Nov 2004 19:59:23 +0100 From: Wiktor Niesiobedzki To: Giorgos Keramidas Message-ID: <20041123185923.GH3584@mail.evip.pl> References: <20041123171951.GG3584@mail.evip.pl> <20041123183930.GA56352@orion.daedalusnetworks.priv> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041123183930.GA56352@orion.daedalusnetworks.priv> User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: Putty or libcrypto bug? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 18:59:26 -0000 On Tue, Nov 23, 2004 at 08:39:30PM +0200, Giorgos Keramidas wrote: > On 2004-11-23 18:19, Wiktor Niesiobedzki wrote: > > w@portal:~$ gdb =putty putty.core [...] > > As we may see, putty defines sk_new function and function of the same name > > exists in libcrypto (in /usr/src/crypto/openssl/crypto/stack/stack.c). > > Good catch :-) > > This is a Bad Idea(TM) most of the time though. The library > implements a function that other programs or libraries may depend upon > to work in certain ways. Replacing the library function with a > hand-rolled version may or may not work -- the latter in this case :-/ But nobody wants to replace this function, look: this function is 6 libraries away from the main program, i.e.: putty is linked to libglib12 and libc, from libc we load /usr/local/lib/nss_ldap, then libldap, then libssl and finally libcrypto... Should'nt libc load nss_ldap with kind of RTLD_LOCAL, so the libc will load libldap in another symbol-space so symbol lookups will not end in main program (if it is at all possible... I'm not familiar with dynamic linking)? If not, then it is the fact, that programmer of any program should aviod duplicating function names across every library that may eventually be installed and somehow linked to this programm, what sounds rather ridiculous to me. > > > And now my question: should the putty change the function name (what > > sound wired) or there should be done some magic in libcrypto, so > > such situations would not happen (what sounds tricky)? > > PuTTY can change the name of a function internal to the application a > lot easier than a library. Changing the library affects all the > programs linked to it, which is bound to be a lot more painful than > changing putty. But it will not resolve similiar problems in future... Cheers, Wiktor Niesiobedzki From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 19:06:19 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17ACC16A4CE for ; Tue, 23 Nov 2004 19:06:19 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 986C543D1D for ; Tue, 23 Nov 2004 19:06:18 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iANJ3eJG040015 for ; Tue, 23 Nov 2004 12:03:41 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 23 Nov 2004 12:04:20 -0700 (MST) Message-Id: <20041123.120420.118628298.imp@bsdimp.com> To: current@freebsd.org From: "M. Warner Losh" X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Known LoR? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 19:06:19 -0000 Noticed this has startted popping up when I do a ispell-buffer in emacs. Anybody know what's going on with it? Warner malloc(M_WAITOK) of "32", forcing M_NOWAIT with the following non-sleepable locks held: exclusive sleep mutex pipe mutex r = 0 (0xc1d272d8) locked @ kern/sys_pipe.c:1263 KDB: stack backtrace: kdb_backtrace(1,1,1,20,c1045540) at kdb_backtrace+0x29 witness_warn(5,0,c0621990,c0623a84,c06663e0) at witness_warn+0x19a uma_zalloc_arg(c1045540,0,2) at uma_zalloc_arg+0x41 malloc(14,c063ac00,2,c1d27180,80047476) at malloc+0xae fsetown(fffffc88,c1d27214,0,0,80047476) at fsetown+0x32 pipe_ioctl(c206f000,80047476,c1bb1640,c205f080,c1d48c00) at pipe_ioctl+0x11a ioctl(c1d48c00,e6a37d14,3,0,206) at ioctl+0x370 syscall(2f,2f,bfbf002f,bfbfdd28,7) at syscall+0x213 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x284b210b, esp = 0xbfbfdc7c, ebp = 0xbfbfdc98 --- lock order reversal 1st 0xc1d272d8 pipe mutex (pipe mutex) @ kern/sys_pipe.c:1263 2nd 0xc06626c0 proctree (proctree) @ kern/kern_descrip.c:881 KDB: stack backtrace: kdb_backtrace(0,ffffffff,c0668298,c0668338,c063edac) at kdb_backtrace+0x29 witness_checkorder(c06626c0,1,c060ae84,371) at witness_checkorder+0x54c _sx_slock(c06626c0,c060ae7b,371,c205f080) at _sx_slock+0x50 fsetown(fffffc88,c1d27214,0,0,80047476) at fsetown+0x6b pipe_ioctl(c206f000,80047476,c1bb1640,c205f080,c1d48c00) at pipe_ioctl+0x11a ioctl(c1d48c00,e6a37d14,3,0,206) at ioctl+0x370 syscall(2f,2f,bfbf002f,bfbfdd28,7) at syscall+0x213 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x284b210b, esp = 0xbfbfdc7c, ebp = 0xbfbfdc98 --- From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 19:11:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CFBB16A4CE for ; Tue, 23 Nov 2004 19:11:30 +0000 (GMT) Received: from smtp2.linkline.com (smtp2.linkline.com [64.30.215.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id C39D543D2D for ; Tue, 23 Nov 2004 19:11:29 +0000 (GMT) (envelope-from sclements@linkline.com) Received: from samclements (host-66-59-225-129.lcinet.net [66.59.225.129]) by smtp2.linkline.com (Postfix) with SMTP id 6B591D2 for ; Tue, 23 Nov 2004 11:11:27 -0800 (PST) Message-ID: <007201c4d190$3c6bf3a0$d232a8c0@LCI> From: "Samuel Clements" To: References: <71F713C5E3CB7F4F9ACCBBB8E9BE318A39E348@blrx2kmbgl101.blr.amer.dell.com> <20041123105313.GC753@zaphod.nitro.dk> Date: Tue, 23 Nov 2004 11:11:29 -0800 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.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: Re: supported new Dell PERC cards - need to add to the Hardwarenotes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 19:11:30 -0000 For what its worth, it appears the Intel SRCU42X (SCSI RAID) and SRCS16 (SATA RAID) are supported by amr as well: amr0: mem 0xf0000000-0xf000ffff irq 16 at device 1.0 on pci3 amr0: Firmware 713K, BIOS G401, 64MB RAM and amr0: mem 0xfc780000-0xfc7fffff,0xfc2f0000-0xfc2fffff irq 19 at device 0.0 on pci4 amr0: Firmware 413Y, BIOS H420, 128MB RAM I love this re-branding stuff! -Sam From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 19:11:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7819616A4CE for ; Tue, 23 Nov 2004 19:11:35 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0610443D5F for ; Tue, 23 Nov 2004 19:11:35 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iANJ9kO8094138; Tue, 23 Nov 2004 14:09:47 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iANJ9kPD094135; Tue, 23 Nov 2004 19:09:46 GMT (envelope-from robert@fledge.watson.org) Date: Tue, 23 Nov 2004 19:09:46 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "M. Warner Losh" In-Reply-To: <20041123.120420.118628298.imp@bsdimp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Known LoR? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 19:11:35 -0000 On Tue, 23 Nov 2004, M. Warner Losh wrote: > Noticed this has startted popping up when I do a ispell-buffer in emacs. > Anybody know what's going on with it? Looks like it's somewhat Poul-Henning's fault :-). The pipe mutex isn't needed over the call to fsetown(), so you can just PIPE_UNLOCK(mpipe) before calling fsetown (make sure to get both uses) in the ioctl code before jumping to the end. The sigio uses its own mutexes to protect sigio data, and the reference to the pipe is still held by the caller. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research . > > Warner > > malloc(M_WAITOK) of "32", forcing M_NOWAIT with the following non-sleepable locks held: > exclusive sleep mutex pipe mutex r = 0 (0xc1d272d8) locked @ kern/sys_pipe.c:1263 > KDB: stack backtrace: > kdb_backtrace(1,1,1,20,c1045540) at kdb_backtrace+0x29 > witness_warn(5,0,c0621990,c0623a84,c06663e0) at witness_warn+0x19a > uma_zalloc_arg(c1045540,0,2) at uma_zalloc_arg+0x41 > malloc(14,c063ac00,2,c1d27180,80047476) at malloc+0xae > fsetown(fffffc88,c1d27214,0,0,80047476) at fsetown+0x32 > pipe_ioctl(c206f000,80047476,c1bb1640,c205f080,c1d48c00) at pipe_ioctl+0x11a > ioctl(c1d48c00,e6a37d14,3,0,206) at ioctl+0x370 > syscall(2f,2f,bfbf002f,bfbfdd28,7) at syscall+0x213 > Xint0x80_syscall() at Xint0x80_syscall+0x1f > --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x284b210b, esp = 0xbfbfdc7c, ebp = 0xbfbfdc98 --- > lock order reversal > 1st 0xc1d272d8 pipe mutex (pipe mutex) @ kern/sys_pipe.c:1263 > 2nd 0xc06626c0 proctree (proctree) @ kern/kern_descrip.c:881 > KDB: stack backtrace: > kdb_backtrace(0,ffffffff,c0668298,c0668338,c063edac) at kdb_backtrace+0x29 > witness_checkorder(c06626c0,1,c060ae84,371) at witness_checkorder+0x54c > _sx_slock(c06626c0,c060ae7b,371,c205f080) at _sx_slock+0x50 > fsetown(fffffc88,c1d27214,0,0,80047476) at fsetown+0x6b > pipe_ioctl(c206f000,80047476,c1bb1640,c205f080,c1d48c00) at pipe_ioctl+0x11a > ioctl(c1d48c00,e6a37d14,3,0,206) at ioctl+0x370 > syscall(2f,2f,bfbf002f,bfbfdd28,7) at syscall+0x213 > Xint0x80_syscall() at Xint0x80_syscall+0x1f > --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x284b210b, esp = 0xbfbfdc7c, ebp = 0xbfbfdc98 --- > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 19:20:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98B5216A4CE for ; Tue, 23 Nov 2004 19:20:06 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57B7943D45 for ; Tue, 23 Nov 2004 19:20:06 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 24189 invoked from network); 23 Nov 2004 19:20:06 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 23 Nov 2004 19:20:05 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iANJJnrT036800; Tue, 23 Nov 2004 14:20:01 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Tue, 23 Nov 2004 11:34:47 -0500 User-Agent: KMail/1.6.2 References: <200411222256.41638.mistry.7@osu.edu> <3C013935-3D04-11D9-BA1A-000A95841F44@po.cwru.edu> In-Reply-To: <3C013935-3D04-11D9-BA1A-000A95841F44@po.cwru.edu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411231134.47697.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Justin Hibbits Subject: Re: ATI TV Wonder support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 19:20:06 -0000 On Monday 22 November 2004 11:00 pm, Justin Hibbits wrote: > On Nov 22, 2004, at 22:56, Anish Mistry wrote: > > On Monday 22 November 2004 09:29 pm, you wrote: > >> On Nov 22, 2004, at 21:22, Anish Mistry wrote: > >>> On Sunday 21 November 2004 10:00 pm, Justin Hibbits wrote: > >>>> This patch gives more or less full ATI TV Wonder support to the bktr > >>>> driver. > >>> > >>> Awesome. > >>> > >>>> The sound doesn't mute at close, but that might be xawtv's fault, > >>>> but > >>>> I > >>>> don't know which to accuse or look at. But, other than that, it > >>>> seems pretty good. > >>> > >>> I've having some trouble using it though, the sound doesn't seem to > >>> work > >>> just as before. Is there something extra I need to add to my kernel > >>> besides bktr? > >>> On boot: > >>> bktr0: mem 0xe3101000-0xe3101fff irq 11 at device 8.0 > >>> on > >>> pci0 > >>> bktr0: [GIANT-LOCKED] > >>> bktr0: Detected a MSP3445G-B8 at 0x80 > >>> bktr0: ATI TV Wonder, Philips NTSC tuner, msp3400c stereo. > >>> pci0: at device 8.1 (no driver attached) > >>> And when I start it: > >>> bktr0: Detected a MSP3445G-B8 at 0x80 > >>> > >>> You should also send-pr this if you haven't already. > >>> > >>> Thanks, > >>> > >>> -- > >>> Anish Mistry > >> > >> Oh, you need to build it with the msp3400c driver, so add the line: > >> > >> options BKTR_NEW_MSP34XX_DRIVER > >> > >> to your config file. The card doesn't have any mux, only that chip, > >> so > >> you need the driver. I've found a hackish solution to the sound > >> problem, by resetting the card on exit. It's horrible, so I won't > >> include it in the patch, but it works for me. If you want to use this > >> too, add: > >> > >> if (bktr->card.msp3400c ) > >> msp_dpl_reset( bktr, bktr->msp_addr ); > >> > >> to bktr_core.c, at line 1171. > >> > >> > >> I'll resend my previous message as a send-pr later, when I have a > >> little more time to test it. > > > > Thanks, but I'm getting a weird panic with 5-STABLE, which I'm > > assuming you > > aren't seeing. Any ideas? > > > > panic: sleeping without a mutex > > KDB: enter: panic > > [thread 100012] > > Stopped at kbd_enter+0x2c: leave > > db> tr > > kbd_enter(c0635ca1,100,c1b6c54c,c1b41320,0) at kbd_enter+0x2c > > panic(c06363e5,0,0,0,c1b37c00) at panic+0x10a > > msleep(c1b6c54c,0,4c,c064007d,0) at msleep+0x2bf > > msp3410d_thread(c1bd8000,d0181d48,c1db8000,c845e1d4,0) at > > msp3410d_thread+0x5b > > fork_exit(c045e1d4,c1db8000,d0181d48) at fork_exit+0x7e > > fork_trampoline() at fork_trampoline+0x8 > > --- trap 0x1, eip=0, esp=0xd0181d7c, ebd=0 --- > > > > dmesg: > > http://am-productions.biz/docs/bigguy.txt.gz > > kernel config: > > http://am-productions.biz/docs/BIGGUY.gz > > -- > > Anish Mistry > > Oh yes, you need to compile it without witness support, or invariants > (DDB is fine, though). It, of course, cuts out a ton of useful > debugging info for other parts, but it's the only way, unfortunately. That's a bug you'll need to fix or the driver can go to sleep forever and never wake up. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 19:20:08 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E723616A4CE for ; Tue, 23 Nov 2004 19:20:08 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFDFB43D49 for ; Tue, 23 Nov 2004 19:20:08 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 17497 invoked from network); 23 Nov 2004 19:20:08 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 23 Nov 2004 19:20:08 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iANJJnrU036800; Tue, 23 Nov 2004 14:20:04 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Tue, 23 Nov 2004 11:36:49 -0500 User-Agent: KMail/1.6.2 References: <20041122143804.GA36649@peter.osted.lan> <200411221657.36659.jhb@FreeBSD.org> <20041123011307.GA38559@peter.osted.lan> In-Reply-To: <20041123011307.GA38559@peter.osted.lan> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411231136.49362.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: current@FreeBSD.org cc: phk@FreeBSD.org Subject: Re: panic: sleeping thread owns a non-sleepable lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 19:20:09 -0000 On Monday 22 November 2004 08:13 pm, Peter Holm wrote: > On Mon, Nov 22, 2004 at 04:57:36PM -0500, John Baldwin wrote: > > On Monday 22 November 2004 09:38 am, Peter Holm wrote: > > > During stress test with GENERIC HEAD from Nov 20 08:40 UTC I got: > > > Sleeping on "fdesc" with the following non-sleepable locks held: > > > exclusive sleep mutex fdesc r = 0 (0xc08d15a0) locked @ > > > kern/kern_descrip.c:2425 and then > > > panic: sleeping thread (pid 92279) owns a non-sleepable lock > > > > > > http://www.holm.cc/stress/log/cons89.html > > > > Yes, the panic is a result of the earlier warning. Poul-Henning touched > > this code last, so it is probably something for him to look at. I'm > > unsure how msleep() is getting called, however. The turnstile panic is > > not important, can you find the thread that went to sleep (should be pid > > 92279) and get stack trace for that? > > The ddb trace is in the log, just before call doadump. Let me know if you > need any gdb output. Ok, can you use gdb to get the source/file of 'sysctl_kern_file+0x1ae'? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 19:20:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B6AF16A4CF for ; Tue, 23 Nov 2004 19:20:09 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id B437B43D5E for ; Tue, 23 Nov 2004 19:20:08 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 17497 invoked from network); 23 Nov 2004 19:20:08 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 23 Nov 2004 19:20:08 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iANJJnrU036800; Tue, 23 Nov 2004 14:20:04 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Tue, 23 Nov 2004 11:36:49 -0500 User-Agent: KMail/1.6.2 References: <20041122143804.GA36649@peter.osted.lan> <200411221657.36659.jhb@FreeBSD.org> <20041123011307.GA38559@peter.osted.lan> In-Reply-To: <20041123011307.GA38559@peter.osted.lan> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411231136.49362.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: current@FreeBSD.org cc: phk@FreeBSD.org Subject: Re: panic: sleeping thread owns a non-sleepable lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 19:20:09 -0000 On Monday 22 November 2004 08:13 pm, Peter Holm wrote: > On Mon, Nov 22, 2004 at 04:57:36PM -0500, John Baldwin wrote: > > On Monday 22 November 2004 09:38 am, Peter Holm wrote: > > > During stress test with GENERIC HEAD from Nov 20 08:40 UTC I got: > > > Sleeping on "fdesc" with the following non-sleepable locks held: > > > exclusive sleep mutex fdesc r = 0 (0xc08d15a0) locked @ > > > kern/kern_descrip.c:2425 and then > > > panic: sleeping thread (pid 92279) owns a non-sleepable lock > > > > > > http://www.holm.cc/stress/log/cons89.html > > > > Yes, the panic is a result of the earlier warning. Poul-Henning touched > > this code last, so it is probably something for him to look at. I'm > > unsure how msleep() is getting called, however. The turnstile panic is > > not important, can you find the thread that went to sleep (should be pid > > 92279) and get stack trace for that? > > The ddb trace is in the log, just before call doadump. Let me know if you > need any gdb output. Ok, can you use gdb to get the source/file of 'sysctl_kern_file+0x1ae'? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 19:20:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D30E716A4D7 for ; Tue, 23 Nov 2004 19:20:12 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8815A43D5C for ; Tue, 23 Nov 2004 19:20:12 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 4286 invoked from network); 23 Nov 2004 19:20:12 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 23 Nov 2004 19:20:11 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iANJJnrV036800; Tue, 23 Nov 2004 14:20:07 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Tue, 23 Nov 2004 11:40:10 -0500 User-Agent: KMail/1.6.2 References: <20041120000743.G18094@mail.chesapeake.net> <20041123083801.GA40401@peter.osted.lan> In-Reply-To: <20041123083801.GA40401@peter.osted.lan> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411231140.10041.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: current@FreeBSD.org cc: Jeff Roberson Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 19:20:34 -0000 On Tuesday 23 November 2004 03:38 am, Peter Holm wrote: > On Sat, Nov 20, 2004 at 12:24:10AM -0500, Jeff Roberson wrote: > > I have a patch that I would like people to test and review. It's > > available here: > > > > http://www.chesapeake.net/~jroberson/smpffs.diff > > I have a panic at http://www.holm.cc/stress/log/jeff02.html > with GENERIC HEAD from Nov 22 14:40 UTC + your Giantless VFS patch. > > But the fault does not seem to related to your changes? Might be an incorrect parameter to mtx_init() that results in a bogus pointer eventually for the name of a lock? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 19:20:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EED4516A4D4 for ; Tue, 23 Nov 2004 19:20:33 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC27243D5E for ; Tue, 23 Nov 2004 19:20:12 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 4286 invoked from network); 23 Nov 2004 19:20:12 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 23 Nov 2004 19:20:11 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iANJJnrV036800; Tue, 23 Nov 2004 14:20:07 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Tue, 23 Nov 2004 11:40:10 -0500 User-Agent: KMail/1.6.2 References: <20041120000743.G18094@mail.chesapeake.net> <20041123083801.GA40401@peter.osted.lan> In-Reply-To: <20041123083801.GA40401@peter.osted.lan> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411231140.10041.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: current@FreeBSD.org cc: Jeff Roberson Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 19:20:34 -0000 On Tuesday 23 November 2004 03:38 am, Peter Holm wrote: > On Sat, Nov 20, 2004 at 12:24:10AM -0500, Jeff Roberson wrote: > > I have a patch that I would like people to test and review. It's > > available here: > > > > http://www.chesapeake.net/~jroberson/smpffs.diff > > I have a panic at http://www.holm.cc/stress/log/jeff02.html > with GENERIC HEAD from Nov 22 14:40 UTC + your Giantless VFS patch. > > But the fault does not seem to related to your changes? Might be an incorrect parameter to mtx_init() that results in a bogus pointer eventually for the name of a lock? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 19:20:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BA0016A511 for ; Tue, 23 Nov 2004 19:20:36 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F31E43D64 for ; Tue, 23 Nov 2004 19:20:20 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 11424 invoked from network); 23 Nov 2004 19:20:18 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 23 Nov 2004 19:20:18 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iANJJnrX036800; Tue, 23 Nov 2004 14:20:13 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Tue, 23 Nov 2004 13:43:22 -0500 User-Agent: KMail/1.6.2 References: <200411231226.38172.jkim@niksun.com> In-Reply-To: <200411231226.38172.jkim@niksun.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411231343.22760.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Jung-uk Kim Subject: Re: Transparent bridges (a. k. a. HUB-to-PCI bridges)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 19:20:36 -0000 On Tuesday 23 November 2004 12:26 pm, Jung-uk Kim wrote: > While I was booting Linux, I saw a 'transparent bridge' from dmesg and > started digging up because I was fighting against 'interrupt > storming' and 'stray IRQ' problems with the latest Intel chipsets > recently and I had a feeling that it's somehow related. > > http://lxr.linux.no/source/drivers/pci/probe.c?v=2.6.8.1#L195 > http://lxr.linux.no/source/arch/i386/pci/fixup.c?v=2.6.8.1#L192 > http://lxr.linux.no/source/arch/i386/pci/irq.c?v=2.6.8.1#L870 > http://lxr.linux.no/source/arch/i386/pci/irq.c?v=2.6.8.1#L1017 > > But I don't see any special treatment in FreeBSD's PCI driver. > > 1. Is this relevant for FreeBSD? > 2. Is this related to the problems (esp. SMP)? First of all, I have no idea what type of interrupt routing problems you are having, but as for the above: FreeBSD uses a much simpler way of managing PCI interrupt routing. In FreeBSD, each hardware device (including PCI bridges (whether Host-PCI or PCI-PCI) and PCI busses) have an OOPish device object (device_t) associated with them. You can see the tree structure via 'devinfo'. The way FreeBSD implements interrupt routing is that each PCI bridge driver provides a method for determining the IRQ associated with a given bus/device/pin tuple. (The bus is implicit since each bridge only handles requests for its immediate downstream bus.) In order to make use of the several different ways of determining interrupt routing, there are several different PCI bridge drivers for both Host-PCI and PCI-PCI bridges. For example, there are ACPI Host-PCI and PCI-PCI bridge drivers that will route interrupts using the _PRT table objects provided by ACPI for busses in ACPI's namespace. Also, there are PCIBIOS bridge drivers to handle routing for the non-ACPI non-APIC case using the information in the $PIR table. Similarly, for the non-ACPI APIC case, there are MP Table bridge drivers to route interrupts for busses that are listed in the MP Table. If a PCI-PCI bridge is not enumerated in ACPI space on an ACPI system or is not listed in either the $PIR (non-APIC) or MP Table (APIC) on a non-ACPI system, then the bridge will be probed via the simple PCI-PCI bridge driver which does the standard barber-pole swizzle to route interrupts based off the intpins on the bridge device's upstream connection. Thus, for "transparent" bridges not listed in the MP Table, the MP Table driver won't attach and it will fall back to the simple PCI-PCI bridge driver and just work. Now, back to your original problem: what type of interrupt problems are you having? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 19:34:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE19916A4CE; Tue, 23 Nov 2004 19:34:01 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9721343D45; Tue, 23 Nov 2004 19:33:59 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 915831FFACA; Tue, 23 Nov 2004 20:33:57 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 8E9311FF91D; Tue, 23 Nov 2004 20:33:55 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id E893215667; Tue, 23 Nov 2004 19:31:10 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id E526F15621; Tue, 23 Nov 2004 19:31:10 +0000 (UTC) Date: Tue, 23 Nov 2004 19:31:10 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: John Baldwin In-Reply-To: <200411221644.57047.jhb@FreeBSD.org> Message-ID: References: <200411221644.57047.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: "Bjoern A. Zeeb" cc: freebsd-current@FreeBSD.org Subject: Re: mem leak in mii ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 19:34:02 -0000 On Mon, 22 Nov 2004, John Baldwin wrote: Hi, hope you won't get it twice; the first one didn't seem to go out... > On Friday 19 November 2004 06:49 pm, Bjoern A. Zeeb wrote: > > Hi, > > > > in sys/dev/mii/mii.c there are two calls to malloc for ivars; > > see for example mii_phy_probe: .. > > Where is the free for this malloc ? I cannot find it. > > > > analogous: miibus_probe ? > > It's a leak. It should be free'd when the miibus device is destroyed. Here's > a possible fix: could you please review this one ? Should plug both of the memleaks; also for more error cases. notes: * mii doesn't ssem to be very error corrective and reporting; as others currently also seem to be debugging problems with undetectable PHYs I added some error handling in those places that I touched anyway. * in miibus_probe in the loop there is the possibility - and the comment above the functions also talks about this - that we find more than one PHY ? I currrently doubt that but I don't know for sure. As device_add_child may return NULL we cannot check for that; I had seen some inconsistency while debugging the BMSR_MEDIAMASK check so I added the count variable for this to have a reliable state. * all PHY drivers currently seem to use mii_phy_detach for device_detach. If any implements his own function it will be responsible for freeing the ivars allocated in miibus_probe. This should perhaps be documented somewhere ? patch can also be found at http://sources.zabbadoz.net/freebsd/patchset/mii-memleaks.diff Index: mii.c =================================================================== RCS file: /local/mirror/FreeBSD/r/ncvs/src/sys/dev/mii/mii.c,v retrieving revision 1.20 diff -u -p -r1.20 mii.c --- mii.c 15 Aug 2004 06:24:40 -0000 1.20 +++ mii.c 23 Nov 2004 17:08:58 -0000 @@ -111,7 +111,7 @@ miibus_probe(dev) struct mii_attach_args ma, *args; struct mii_data *mii; device_t child = NULL, parent; - int bmsr, capmask = 0xFFFFFFFF; + int count = 0, bmsr, capmask = 0xFFFFFFFF; mii = device_get_softc(dev); parent = device_get_parent(dev); @@ -145,12 +145,26 @@ miibus_probe(dev) args = malloc(sizeof(struct mii_attach_args), M_DEVBUF, M_NOWAIT); + if (args == NULL) { + device_printf(dev, "%s: memory allocation failure, " + "phyno %d", __func__, ma.mii_phyno); + continue; + } bcopy((char *)&ma, (char *)args, sizeof(ma)); child = device_add_child(dev, NULL, -1); + if (child == NULL) { + free(args, M_DEVBUF); + device_printf(dev, "%s: device_add_child failed", + __func__); + continue; + } device_set_ivars(child, args); + count++; + /* XXX should we break here or is it really possible + * to find more then one PHY ? */ } - if (child == NULL) + if (count == 0) return(ENXIO); device_set_desc(dev, "MII bus"); @@ -173,12 +187,15 @@ miibus_attach(dev) */ mii->mii_ifp = device_get_softc(device_get_parent(dev)); v = device_get_ivars(dev); + if (v == NULL) + return (ENXIO); ifmedia_upd = v[0]; ifmedia_sts = v[1]; + device_set_ivars(dev, NULL); + free(v, M_DEVBUF); ifmedia_init(&mii->mii_media, IFM_IMASK, ifmedia_upd, ifmedia_sts); - bus_generic_attach(dev); - return(0); + return (bus_generic_attach(dev)); } int @@ -186,8 +203,14 @@ miibus_detach(dev) device_t dev; { struct mii_data *mii; + void *v; bus_generic_detach(dev); + v = device_get_ivars(dev); + if (v != NULL) { + device_set_ivars(dev, NULL); + free(v, M_DEVBUF); + } mii = device_get_softc(dev); ifmedia_removeall(&mii->mii_media); mii->mii_ifp = NULL; @@ -305,12 +328,15 @@ mii_phy_probe(dev, child, ifmedia_upd, i int bmsr, i; v = malloc(sizeof(vm_offset_t) * 2, M_DEVBUF, M_NOWAIT); - if (v == 0) { + if (v == NULL) return (ENOMEM); - } v[0] = ifmedia_upd; v[1] = ifmedia_sts; *child = device_add_child(dev, "miibus", -1); + if (*child == NULL) { + free(v, M_DEVBUF); + return (ENXIO); + } device_set_ivars(*child, v); for (i = 0; i < MII_NPHY; i++) { @@ -324,14 +350,22 @@ mii_phy_probe(dev, child, ifmedia_upd, i } if (i == MII_NPHY) { + device_set_ivars(dev, NULL); + free(v, M_DEVBUF); device_delete_child(dev, *child); *child = NULL; return(ENXIO); } - bus_generic_attach(dev); + i = bus_generic_attach(dev); - return(0); + v = device_get_ivars(*child); + if (v != NULL) { + device_set_ivars(*child, NULL); + free(v, M_DEVBUF); + } + + return (i); } /* Index: mii_physubr.c =================================================================== RCS file: /local/mirror/FreeBSD/r/ncvs/src/sys/dev/mii/mii_physubr.c,v retrieving revision 1.21 diff -u -p -r1.21 mii_physubr.c --- mii_physubr.c 29 May 2004 18:09:10 -0000 1.21 +++ mii_physubr.c 23 Nov 2004 17:07:30 -0000 @@ -522,7 +522,13 @@ int mii_phy_detach(device_t dev) { struct mii_softc *sc; + void *args; + args = device_get_ivars(dev); + if (args != NULL) { + device_set_ivars(dev, NULL); + free(args, M_DEVBUF); + } sc = device_get_softc(dev); mii_phy_down(sc); sc->mii_dev = NULL; -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 19:40:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2ADAD16A4CE; Tue, 23 Nov 2004 19:40:43 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AF8343D2F; Tue, 23 Nov 2004 19:40:42 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.0.5] (adsl-68-250-184-205.dsl.wotnoh.ameritech.net [68.250.184.205]) (authenticated bits=0)iANJKjeB042629 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 23 Nov 2004 14:20:46 -0500 (EST) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: John Baldwin Date: Tue, 23 Nov 2004 14:43:36 -0500 User-Agent: KMail/1.7 References: <3C013935-3D04-11D9-BA1A-000A95841F44@po.cwru.edu> <200411231134.47697.jhb@FreeBSD.org> In-Reply-To: <200411231134.47697.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart18054545.9P2y6SP2M6"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411231443.37019.mistry.7@osu.edu> X-Spam-Status: No, hits=0.8 required=5.0 tests=BIZ_TLD autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on crumpet.united-ware.com cc: freebsd-current@freebsd.org Subject: Re: ATI TV Wonder support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 19:40:43 -0000 --nextPart18054545.9P2y6SP2M6 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 23 November 2004 11:34 am, you wrote: > On Monday 22 November 2004 11:00 pm, Justin Hibbits wrote: > > On Nov 22, 2004, at 22:56, Anish Mistry wrote: > > > On Monday 22 November 2004 09:29 pm, you wrote: > > >> On Nov 22, 2004, at 21:22, Anish Mistry wrote: > > >>> On Sunday 21 November 2004 10:00 pm, Justin Hibbits wrote: > > >>>> This patch gives more or less full ATI TV Wonder support to the > > >>>> bktr driver. > > >>> > > >>> Awesome. > > >>> > > >>>> The sound doesn't mute at close, but that might be xawtv's fault, > > >>>> but > > >>>> I > > >>>> don't know which to accuse or look at. But, other than that, it > > >>>> seems pretty good. > > >>> > > >>> I've having some trouble using it though, the sound doesn't seem > > >>> to work > > >>> just as before. Is there something extra I need to add to my > > >>> kernel besides bktr? > > >>> On boot: > > >>> bktr0: mem 0xe3101000-0xe3101fff irq 11 at device > > >>> 8.0 on > > >>> pci0 > > >>> bktr0: [GIANT-LOCKED] > > >>> bktr0: Detected a MSP3445G-B8 at 0x80 > > >>> bktr0: ATI TV Wonder, Philips NTSC tuner, msp3400c stereo. > > >>> pci0: at device 8.1 (no driver attached) > > >>> And when I start it: > > >>> bktr0: Detected a MSP3445G-B8 at 0x80 > > >>> > > >>> You should also send-pr this if you haven't already. > > >>> > > >>> Thanks, > > >>> > > >>> -- > > >>> Anish Mistry > > >> > > >> Oh, you need to build it with the msp3400c driver, so add the line: > > >> > > >> options BKTR_NEW_MSP34XX_DRIVER > > >> > > >> to your config file. The card doesn't have any mux, only that > > >> chip, so > > >> you need the driver. I've found a hackish solution to the sound > > >> problem, by resetting the card on exit. It's horrible, so I won't > > >> include it in the patch, but it works for me. If you want to use > > >> this too, add: > > >> > > >> if (bktr->card.msp3400c ) > > >> msp_dpl_reset( bktr, bktr->msp_addr ); > > >> > > >> to bktr_core.c, at line 1171. > > >> > > >> > > >> I'll resend my previous message as a send-pr later, when I have a > > >> little more time to test it. > > > > > > Thanks, but I'm getting a weird panic with 5-STABLE, which I'm > > > assuming you > > > aren't seeing. Any ideas? > > > > > > panic: sleeping without a mutex > > > KDB: enter: panic > > > [thread 100012] > > > Stopped at kbd_enter+0x2c: leave > > > db> tr > > > kbd_enter(c0635ca1,100,c1b6c54c,c1b41320,0) at kbd_enter+0x2c > > > panic(c06363e5,0,0,0,c1b37c00) at panic+0x10a > > > msleep(c1b6c54c,0,4c,c064007d,0) at msleep+0x2bf > > > msp3410d_thread(c1bd8000,d0181d48,c1db8000,c845e1d4,0) at > > > msp3410d_thread+0x5b > > > fork_exit(c045e1d4,c1db8000,d0181d48) at fork_exit+0x7e > > > fork_trampoline() at fork_trampoline+0x8 > > > --- trap 0x1, eip=3D0, esp=3D0xd0181d7c, ebd=3D0 --- > > > > > > dmesg: > > > http://am-productions.biz/docs/bigguy.txt.gz > > > kernel config: > > > http://am-productions.biz/docs/BIGGUY.gz > > > -- > > > Anish Mistry > > > > Oh yes, you need to compile it without witness support, or invariants > > (DDB is fine, though). It, of course, cuts out a ton of useful > > debugging info for other parts, but it's the only way, unfortunately. > > That's a bug you'll need to fix or the driver can go to sleep forever > and never wake up. I figured something like. Do you have any pointers of where to get started= =20 and examples of how things like this have been fixed in other drivers? Thanks, =2D-=20 Anish Mistry --nextPart18054545.9P2y6SP2M6 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBo5LpxqA5ziudZT0RAl17AJ9tZlPolCY/m/bltDrsSeUgrIThEwCdHCTD kX6aBZb0QO+Cv4x29Ml6O/k= =stFP -----END PGP SIGNATURE----- --nextPart18054545.9P2y6SP2M6-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 19:51:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D566916A4CE for ; Tue, 23 Nov 2004 19:51:27 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96F7943D31 for ; Tue, 23 Nov 2004 19:51:27 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 564 invoked from network); 23 Nov 2004 19:51:10 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 23 Nov 2004 19:51:09 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iANJp5JP037078; Tue, 23 Nov 2004 14:51:06 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Anish Mistry Date: Tue, 23 Nov 2004 14:51:03 -0500 User-Agent: KMail/1.6.2 References: <200411231134.47697.jhb@FreeBSD.org> <200411231443.37019.mistry.7@osu.edu> In-Reply-To: <200411231443.37019.mistry.7@osu.edu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411231451.03807.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: freebsd-current@FreeBSD.org Subject: Re: ATI TV Wonder support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 19:51:27 -0000 On Tuesday 23 November 2004 02:43 pm, Anish Mistry wrote: > On Tuesday 23 November 2004 11:34 am, you wrote: > > On Monday 22 November 2004 11:00 pm, Justin Hibbits wrote: > > > On Nov 22, 2004, at 22:56, Anish Mistry wrote: > > > > On Monday 22 November 2004 09:29 pm, you wrote: > > > >> On Nov 22, 2004, at 21:22, Anish Mistry wrote: > > > >>> On Sunday 21 November 2004 10:00 pm, Justin Hibbits wrote: > > > >>>> This patch gives more or less full ATI TV Wonder support to the > > > >>>> bktr driver. > > > >>> > > > >>> Awesome. > > > >>> > > > >>>> The sound doesn't mute at close, but that might be xawtv's fault, > > > >>>> but > > > >>>> I > > > >>>> don't know which to accuse or look at. But, other than that, it > > > >>>> seems pretty good. > > > >>> > > > >>> I've having some trouble using it though, the sound doesn't seem > > > >>> to work > > > >>> just as before. Is there something extra I need to add to my > > > >>> kernel besides bktr? > > > >>> On boot: > > > >>> bktr0: mem 0xe3101000-0xe3101fff irq 11 at device > > > >>> 8.0 on > > > >>> pci0 > > > >>> bktr0: [GIANT-LOCKED] > > > >>> bktr0: Detected a MSP3445G-B8 at 0x80 > > > >>> bktr0: ATI TV Wonder, Philips NTSC tuner, msp3400c stereo. > > > >>> pci0: at device 8.1 (no driver attached) > > > >>> And when I start it: > > > >>> bktr0: Detected a MSP3445G-B8 at 0x80 > > > >>> > > > >>> You should also send-pr this if you haven't already. > > > >>> > > > >>> Thanks, > > > >>> > > > >>> -- > > > >>> Anish Mistry > > > >> > > > >> Oh, you need to build it with the msp3400c driver, so add the line: > > > >> > > > >> options BKTR_NEW_MSP34XX_DRIVER > > > >> > > > >> to your config file. The card doesn't have any mux, only that > > > >> chip, so > > > >> you need the driver. I've found a hackish solution to the sound > > > >> problem, by resetting the card on exit. It's horrible, so I won't > > > >> include it in the patch, but it works for me. If you want to use > > > >> this too, add: > > > >> > > > >> if (bktr->card.msp3400c ) > > > >> msp_dpl_reset( bktr, bktr->msp_addr ); > > > >> > > > >> to bktr_core.c, at line 1171. > > > >> > > > >> > > > >> I'll resend my previous message as a send-pr later, when I have a > > > >> little more time to test it. > > > > > > > > Thanks, but I'm getting a weird panic with 5-STABLE, which I'm > > > > assuming you > > > > aren't seeing. Any ideas? > > > > > > > > panic: sleeping without a mutex > > > > KDB: enter: panic > > > > [thread 100012] > > > > Stopped at kbd_enter+0x2c: leave > > > > db> tr > > > > kbd_enter(c0635ca1,100,c1b6c54c,c1b41320,0) at kbd_enter+0x2c > > > > panic(c06363e5,0,0,0,c1b37c00) at panic+0x10a > > > > msleep(c1b6c54c,0,4c,c064007d,0) at msleep+0x2bf > > > > msp3410d_thread(c1bd8000,d0181d48,c1db8000,c845e1d4,0) at > > > > msp3410d_thread+0x5b > > > > fork_exit(c045e1d4,c1db8000,d0181d48) at fork_exit+0x7e > > > > fork_trampoline() at fork_trampoline+0x8 > > > > --- trap 0x1, eip=0, esp=0xd0181d7c, ebd=0 --- > > > > > > > > dmesg: > > > > http://am-productions.biz/docs/bigguy.txt.gz > > > > kernel config: > > > > http://am-productions.biz/docs/BIGGUY.gz > > > > -- > > > > Anish Mistry > > > > > > Oh yes, you need to compile it without witness support, or invariants > > > (DDB is fine, though). It, of course, cuts out a ton of useful > > > debugging info for other parts, but it's the only way, unfortunately. > > > > That's a bug you'll need to fix or the driver can go to sleep forever > > and never wake up. > > I figured something like. Do you have any pointers of where to get started > and examples of how things like this have been fixed in other drivers? Well, probably the code is not Giant-safe yet, so you'll need to figure out why Giant isn't being held in the driver. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 20:04:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC0EF16A4CE; Tue, 23 Nov 2004 20:04:25 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E90643D1D; Tue, 23 Nov 2004 20:04:25 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.0.5] (adsl-68-250-184-205.dsl.wotnoh.ameritech.net [68.250.184.205]) (authenticated bits=0)iANJiReB042682 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 23 Nov 2004 14:44:28 -0500 (EST) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: John Baldwin Date: Tue, 23 Nov 2004 15:07:19 -0500 User-Agent: KMail/1.7 References: <200411231443.37019.mistry.7@osu.edu> <200411231451.03807.jhb@FreeBSD.org> In-Reply-To: <200411231451.03807.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1849165.gXl6atmF0G"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411231507.19380.mistry.7@osu.edu> X-Spam-Status: No, hits=0.8 required=5.0 tests=BIZ_TLD autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on crumpet.united-ware.com cc: freebsd-current@freebsd.org Subject: Re: ATI TV Wonder support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 20:04:26 -0000 --nextPart1849165.gXl6atmF0G Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 23 November 2004 02:51 pm, John Baldwin wrote: > On Tuesday 23 November 2004 02:43 pm, Anish Mistry wrote: > > On Tuesday 23 November 2004 11:34 am, you wrote: > > > On Monday 22 November 2004 11:00 pm, Justin Hibbits wrote: > > > > On Nov 22, 2004, at 22:56, Anish Mistry wrote: > > > > > On Monday 22 November 2004 09:29 pm, you wrote: > > > > >> On Nov 22, 2004, at 21:22, Anish Mistry wrote: > > > > >>> On Sunday 21 November 2004 10:00 pm, Justin Hibbits wrote: > > > > >>>> This patch gives more or less full ATI TV Wonder support to > > > > >>>> the bktr driver. > > > > >>> > > > > >>> Awesome. > > > > >>> > > > > >>>> The sound doesn't mute at close, but that might be xawtv's > > > > >>>> fault, but > > > > >>>> I > > > > >>>> don't know which to accuse or look at. But, other than that, > > > > >>>> it seems pretty good. > > > > >>> > > > > >>> I've having some trouble using it though, the sound doesn't > > > > >>> seem to work > > > > >>> just as before. Is there something extra I need to add to my > > > > >>> kernel besides bktr? > > > > >>> On boot: > > > > >>> bktr0: mem 0xe3101000-0xe3101fff irq 11 at > > > > >>> device 8.0 on > > > > >>> pci0 > > > > >>> bktr0: [GIANT-LOCKED] > > > > >>> bktr0: Detected a MSP3445G-B8 at 0x80 > > > > >>> bktr0: ATI TV Wonder, Philips NTSC tuner, msp3400c stereo. > > > > >>> pci0: at device 8.1 (no driver attached) > > > > >>> And when I start it: > > > > >>> bktr0: Detected a MSP3445G-B8 at 0x80 > > > > >>> > > > > >>> You should also send-pr this if you haven't already. > > > > >>> > > > > >>> Thanks, > > > > >>> > > > > >>> -- > > > > >>> Anish Mistry > > > > >> > > > > >> Oh, you need to build it with the msp3400c driver, so add the > > > > >> line: > > > > >> > > > > >> options BKTR_NEW_MSP34XX_DRIVER > > > > >> > > > > >> to your config file. The card doesn't have any mux, only that > > > > >> chip, so > > > > >> you need the driver. I've found a hackish solution to the > > > > >> sound problem, by resetting the card on exit. It's horrible, > > > > >> so I won't include it in the patch, but it works for me. If > > > > >> you want to use this too, add: > > > > >> > > > > >> if (bktr->card.msp3400c ) > > > > >> msp_dpl_reset( bktr, bktr->msp_addr ); > > > > >> > > > > >> to bktr_core.c, at line 1171. > > > > >> > > > > >> > > > > >> I'll resend my previous message as a send-pr later, when I have > > > > >> a little more time to test it. > > > > > > > > > > Thanks, but I'm getting a weird panic with 5-STABLE, which I'm > > > > > assuming you > > > > > aren't seeing. Any ideas? > > > > > > > > > > panic: sleeping without a mutex > > > > > KDB: enter: panic > > > > > [thread 100012] > > > > > Stopped at kbd_enter+0x2c: leave > > > > > db> tr > > > > > kbd_enter(c0635ca1,100,c1b6c54c,c1b41320,0) at kbd_enter+0x2c > > > > > panic(c06363e5,0,0,0,c1b37c00) at panic+0x10a > > > > > msleep(c1b6c54c,0,4c,c064007d,0) at msleep+0x2bf > > > > > msp3410d_thread(c1bd8000,d0181d48,c1db8000,c845e1d4,0) at > > > > > msp3410d_thread+0x5b > > > > > fork_exit(c045e1d4,c1db8000,d0181d48) at fork_exit+0x7e > > > > > fork_trampoline() at fork_trampoline+0x8 > > > > > --- trap 0x1, eip=3D0, esp=3D0xd0181d7c, ebd=3D0 --- > > > > > > > > > > dmesg: > > > > > http://am-productions.biz/docs/bigguy.txt.gz > > > > > kernel config: > > > > > http://am-productions.biz/docs/BIGGUY.gz > > > > > -- > > > > > Anish Mistry > > > > > > > > Oh yes, you need to compile it without witness support, or > > > > invariants (DDB is fine, though). It, of course, cuts out a ton > > > > of useful debugging info for other parts, but it's the only way, > > > > unfortunately. > > > > > > That's a bug you'll need to fix or the driver can go to sleep > > > forever and never wake up. > > > > I figured something like. Do you have any pointers of where to get > > started and examples of how things like this have been fixed in other > > drivers? > > Well, probably the code is not Giant-safe yet, so you'll need to figure > out why Giant isn't being held in the driver. Would it be better to first make the code Giant-safe, or just go ahead and= =20 add the locking to make it MP-safe? or are these 2 seperate things? =2D-=20 Anish Mistry --nextPart1849165.gXl6atmF0G Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBo5h3xqA5ziudZT0RArs5AJ9VpOwfRfIRyl5313LCgJQuKCQbqACfduNq dEnpauOiXrU6g5bMn8CE4V8= =n2Xe -----END PGP SIGNATURE----- --nextPart1849165.gXl6atmF0G-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 20:46:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66DCF16A4CE for ; Tue, 23 Nov 2004 20:46:38 +0000 (GMT) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.FreeBSD.org (Postfix) with SMTP id 7D93043D64 for ; Tue, 23 Nov 2004 20:46:37 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 70313 invoked from network); 23 Nov 2004 20:46:36 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 23 Nov 2004 20:46:36 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iANKkZw6042836; Tue, 23 Nov 2004 21:46:35 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iANKkZBf042835; Tue, 23 Nov 2004 21:46:35 +0100 (CET) (envelope-from pho) Date: Tue, 23 Nov 2004 21:46:35 +0100 From: Peter Holm To: John Baldwin Message-ID: <20041123204635.GA42682@peter.osted.lan> References: <20041122143804.GA36649@peter.osted.lan> <200411221657.36659.jhb@FreeBSD.org> <20041123011307.GA38559@peter.osted.lan> <200411231136.49362.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200411231136.49362.jhb@FreeBSD.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org cc: current@freebsd.org Subject: Re: panic: sleeping thread owns a non-sleepable lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 20:46:38 -0000 On Tue, Nov 23, 2004 at 11:36:49AM -0500, John Baldwin wrote: > On Monday 22 November 2004 08:13 pm, Peter Holm wrote: > > On Mon, Nov 22, 2004 at 04:57:36PM -0500, John Baldwin wrote: > > > On Monday 22 November 2004 09:38 am, Peter Holm wrote: > > > > During stress test with GENERIC HEAD from Nov 20 08:40 UTC I got: > > > > Sleeping on "fdesc" with the following non-sleepable locks held: > > > > exclusive sleep mutex fdesc r = 0 (0xc08d15a0) locked @ > > > > kern/kern_descrip.c:2425 and then > > > > panic: sleeping thread (pid 92279) owns a non-sleepable lock > > > > > > > > http://www.holm.cc/stress/log/cons89.html > > > > > > Yes, the panic is a result of the earlier warning. Poul-Henning touched > > > this code last, so it is probably something for him to look at. I'm > > > unsure how msleep() is getting called, however. The turnstile panic is > > > not important, can you find the thread that went to sleep (should be pid > > > 92279) and get stack trace for that? > > > > The ddb trace is in the log, just before call doadump. Let me know if you > > need any gdb output. > > Ok, can you use gdb to get the source/file of 'sysctl_kern_file+0x1ae'? > I've updated to HEAD from Nov 23 08:05 UTC , but was lucky to get the same panic again :-) http://www.holm.cc/stress/log/cons90.html (kgdb) l *sysctl_kern_file+0x1ae 0xc05f3526 is in sysctl_kern_file (../../../kern/kern_descrip.c:2427). 2422 mtx_lock(&fdesc_mtx); 2423 if ((fdp = p->p_fd) == NULL) { 2424 mtx_unlock(&fdesc_mtx); 2425 continue; 2426 } 2427 FILEDESC_LOCK(fdp); 2428 for (n = 0; n < fdp->fd_nfiles; ++n) { 2429 if ((fp = fdp->fd_ofiles[n]) == NULL) 2430 continue; 2431 xf.xf_fd = n; -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 20:46:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DB4316A4CE for ; Tue, 23 Nov 2004 20:46:38 +0000 (GMT) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.FreeBSD.org (Postfix) with SMTP id 7D7B043D5D for ; Tue, 23 Nov 2004 20:46:37 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 70313 invoked from network); 23 Nov 2004 20:46:36 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 23 Nov 2004 20:46:36 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iANKkZw6042836; Tue, 23 Nov 2004 21:46:35 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iANKkZBf042835; Tue, 23 Nov 2004 21:46:35 +0100 (CET) (envelope-from pho) Date: Tue, 23 Nov 2004 21:46:35 +0100 From: Peter Holm To: John Baldwin Message-ID: <20041123204635.GA42682@peter.osted.lan> References: <20041122143804.GA36649@peter.osted.lan> <200411221657.36659.jhb@FreeBSD.org> <20041123011307.GA38559@peter.osted.lan> <200411231136.49362.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200411231136.49362.jhb@FreeBSD.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org cc: current@freebsd.org Subject: Re: panic: sleeping thread owns a non-sleepable lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 20:46:38 -0000 On Tue, Nov 23, 2004 at 11:36:49AM -0500, John Baldwin wrote: > On Monday 22 November 2004 08:13 pm, Peter Holm wrote: > > On Mon, Nov 22, 2004 at 04:57:36PM -0500, John Baldwin wrote: > > > On Monday 22 November 2004 09:38 am, Peter Holm wrote: > > > > During stress test with GENERIC HEAD from Nov 20 08:40 UTC I got: > > > > Sleeping on "fdesc" with the following non-sleepable locks held: > > > > exclusive sleep mutex fdesc r = 0 (0xc08d15a0) locked @ > > > > kern/kern_descrip.c:2425 and then > > > > panic: sleeping thread (pid 92279) owns a non-sleepable lock > > > > > > > > http://www.holm.cc/stress/log/cons89.html > > > > > > Yes, the panic is a result of the earlier warning. Poul-Henning touched > > > this code last, so it is probably something for him to look at. I'm > > > unsure how msleep() is getting called, however. The turnstile panic is > > > not important, can you find the thread that went to sleep (should be pid > > > 92279) and get stack trace for that? > > > > The ddb trace is in the log, just before call doadump. Let me know if you > > need any gdb output. > > Ok, can you use gdb to get the source/file of 'sysctl_kern_file+0x1ae'? > I've updated to HEAD from Nov 23 08:05 UTC , but was lucky to get the same panic again :-) http://www.holm.cc/stress/log/cons90.html (kgdb) l *sysctl_kern_file+0x1ae 0xc05f3526 is in sysctl_kern_file (../../../kern/kern_descrip.c:2427). 2422 mtx_lock(&fdesc_mtx); 2423 if ((fdp = p->p_fd) == NULL) { 2424 mtx_unlock(&fdesc_mtx); 2425 continue; 2426 } 2427 FILEDESC_LOCK(fdp); 2428 for (n = 0; n < fdp->fd_nfiles; ++n) { 2429 if ((fp = fdp->fd_ofiles[n]) == NULL) 2430 continue; 2431 xf.xf_fd = n; -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 21:36:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5092716A4CE for ; Tue, 23 Nov 2004 21:36:48 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A83243D45 for ; Tue, 23 Nov 2004 21:36:48 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 9251 invoked from network); 23 Nov 2004 21:36:47 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 23 Nov 2004 21:36:47 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iANLaXfN037718; Tue, 23 Nov 2004 16:36:43 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Peter Holm Date: Tue, 23 Nov 2004 16:35:40 -0500 User-Agent: KMail/1.6.2 References: <20041122143804.GA36649@peter.osted.lan> <200411231136.49362.jhb@FreeBSD.org> <20041123204635.GA42682@peter.osted.lan> In-Reply-To: <20041123204635.GA42682@peter.osted.lan> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411231635.40567.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: current@FreeBSD.org cc: phk@FreeBSD.org Subject: Re: panic: sleeping thread owns a non-sleepable lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 21:36:48 -0000 On Tuesday 23 November 2004 03:46 pm, Peter Holm wrote: > On Tue, Nov 23, 2004 at 11:36:49AM -0500, John Baldwin wrote: > > On Monday 22 November 2004 08:13 pm, Peter Holm wrote: > > > On Mon, Nov 22, 2004 at 04:57:36PM -0500, John Baldwin wrote: > > > > On Monday 22 November 2004 09:38 am, Peter Holm wrote: > > > > > During stress test with GENERIC HEAD from Nov 20 08:40 UTC I got: > > > > > Sleeping on "fdesc" with the following non-sleepable locks held: > > > > > exclusive sleep mutex fdesc r = 0 (0xc08d15a0) locked @ > > > > > kern/kern_descrip.c:2425 and then > > > > > panic: sleeping thread (pid 92279) owns a non-sleepable lock > > > > > > > > > > http://www.holm.cc/stress/log/cons89.html > > > > > > > > Yes, the panic is a result of the earlier warning. Poul-Henning > > > > touched this code last, so it is probably something for him to look > > > > at. I'm unsure how msleep() is getting called, however. The > > > > turnstile panic is not important, can you find the thread that went > > > > to sleep (should be pid 92279) and get stack trace for that? > > > > > > The ddb trace is in the log, just before call doadump. Let me know if > > > you need any gdb output. > > > > Ok, can you use gdb to get the source/file of 'sysctl_kern_file+0x1ae'? > > I've updated to HEAD from Nov 23 08:05 UTC , but was lucky to get the same > panic again :-) http://www.holm.cc/stress/log/cons90.html > > (kgdb) l *sysctl_kern_file+0x1ae > 0xc05f3526 is in sysctl_kern_file (../../../kern/kern_descrip.c:2427). > 2422 mtx_lock(&fdesc_mtx); > 2423 if ((fdp = p->p_fd) == NULL) { > 2424 mtx_unlock(&fdesc_mtx); > 2425 continue; > 2426 } > 2427 FILEDESC_LOCK(fdp); > 2428 for (n = 0; n < fdp->fd_nfiles; ++n) { > 2429 if ((fp = fdp->fd_ofiles[n]) == NULL) > 2430 continue; > 2431 xf.xf_fd = n; Oh, this is because of phk's home rolled msleep locks. Hmm, the basic problem here is that somehow he needs to drop the fdesc_mtx lock after locking the internal mutex but before doing the sleep. Also, he will need to add a reference count (in case the fdp goes away while he is waiting for the xlock), and bump it before going to sleep and drop it after doing the SYSCTL_OUT(). Kind of like: lock(&fdesc_mtx); fdp = p->p_fd; FILEDESC_LOCK_SMALL(fdp); unlock(&fdesc_mtx); filedesc_hold(fdp); FILEDESC_LOCK_BIG(fdp); ... SYSCTL_OUT(); filedesc_free(fdp); On the other hand, since the SYSCTL_OUT() can't block here, he probably just needs to use the FILEDESC_LOCK_FAST() variants that just lock the mutex instead of using the full-blown sleep lock. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 21:36:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1743516A4CE for ; Tue, 23 Nov 2004 21:36:50 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 769F743D48 for ; Tue, 23 Nov 2004 21:36:50 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 9439 invoked from network); 23 Nov 2004 21:36:50 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 23 Nov 2004 21:36:49 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iANLaXfO037718; Tue, 23 Nov 2004 16:36:46 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Anish Mistry Date: Tue, 23 Nov 2004 16:36:29 -0500 User-Agent: KMail/1.6.2 References: <200411231451.03807.jhb@FreeBSD.org> <200411231507.19380.mistry.7@osu.edu> In-Reply-To: <200411231507.19380.mistry.7@osu.edu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411231636.29953.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: freebsd-current@FreeBSD.org Subject: Re: ATI TV Wonder support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 21:36:51 -0000 On Tuesday 23 November 2004 03:07 pm, Anish Mistry wrote: > On Tuesday 23 November 2004 02:51 pm, John Baldwin wrote: > > On Tuesday 23 November 2004 02:43 pm, Anish Mistry wrote: > > > On Tuesday 23 November 2004 11:34 am, you wrote: > > > > On Monday 22 November 2004 11:00 pm, Justin Hibbits wrote: > > > > > On Nov 22, 2004, at 22:56, Anish Mistry wrote: > > > > > > On Monday 22 November 2004 09:29 pm, you wrote: > > > > > >> On Nov 22, 2004, at 21:22, Anish Mistry wrote: > > > > > >>> On Sunday 21 November 2004 10:00 pm, Justin Hibbits wrote: > > > > > >>>> This patch gives more or less full ATI TV Wonder support to > > > > > >>>> the bktr driver. > > > > > >>> > > > > > >>> Awesome. > > > > > >>> > > > > > >>>> The sound doesn't mute at close, but that might be xawtv's > > > > > >>>> fault, but > > > > > >>>> I > > > > > >>>> don't know which to accuse or look at. But, other than that, > > > > > >>>> it seems pretty good. > > > > > >>> > > > > > >>> I've having some trouble using it though, the sound doesn't > > > > > >>> seem to work > > > > > >>> just as before. Is there something extra I need to add to my > > > > > >>> kernel besides bktr? > > > > > >>> On boot: > > > > > >>> bktr0: mem 0xe3101000-0xe3101fff irq 11 at > > > > > >>> device 8.0 on > > > > > >>> pci0 > > > > > >>> bktr0: [GIANT-LOCKED] > > > > > >>> bktr0: Detected a MSP3445G-B8 at 0x80 > > > > > >>> bktr0: ATI TV Wonder, Philips NTSC tuner, msp3400c stereo. > > > > > >>> pci0: at device 8.1 (no driver attached) > > > > > >>> And when I start it: > > > > > >>> bktr0: Detected a MSP3445G-B8 at 0x80 > > > > > >>> > > > > > >>> You should also send-pr this if you haven't already. > > > > > >>> > > > > > >>> Thanks, > > > > > >>> > > > > > >>> -- > > > > > >>> Anish Mistry > > > > > >> > > > > > >> Oh, you need to build it with the msp3400c driver, so add the > > > > > >> line: > > > > > >> > > > > > >> options BKTR_NEW_MSP34XX_DRIVER > > > > > >> > > > > > >> to your config file. The card doesn't have any mux, only that > > > > > >> chip, so > > > > > >> you need the driver. I've found a hackish solution to the > > > > > >> sound problem, by resetting the card on exit. It's horrible, > > > > > >> so I won't include it in the patch, but it works for me. If > > > > > >> you want to use this too, add: > > > > > >> > > > > > >> if (bktr->card.msp3400c ) > > > > > >> msp_dpl_reset( bktr, bktr->msp_addr ); > > > > > >> > > > > > >> to bktr_core.c, at line 1171. > > > > > >> > > > > > >> > > > > > >> I'll resend my previous message as a send-pr later, when I have > > > > > >> a little more time to test it. > > > > > > > > > > > > Thanks, but I'm getting a weird panic with 5-STABLE, which I'm > > > > > > assuming you > > > > > > aren't seeing. Any ideas? > > > > > > > > > > > > panic: sleeping without a mutex > > > > > > KDB: enter: panic > > > > > > [thread 100012] > > > > > > Stopped at kbd_enter+0x2c: leave > > > > > > db> tr > > > > > > kbd_enter(c0635ca1,100,c1b6c54c,c1b41320,0) at kbd_enter+0x2c > > > > > > panic(c06363e5,0,0,0,c1b37c00) at panic+0x10a > > > > > > msleep(c1b6c54c,0,4c,c064007d,0) at msleep+0x2bf > > > > > > msp3410d_thread(c1bd8000,d0181d48,c1db8000,c845e1d4,0) at > > > > > > msp3410d_thread+0x5b > > > > > > fork_exit(c045e1d4,c1db8000,d0181d48) at fork_exit+0x7e > > > > > > fork_trampoline() at fork_trampoline+0x8 > > > > > > --- trap 0x1, eip=0, esp=0xd0181d7c, ebd=0 --- > > > > > > > > > > > > dmesg: > > > > > > http://am-productions.biz/docs/bigguy.txt.gz > > > > > > kernel config: > > > > > > http://am-productions.biz/docs/BIGGUY.gz > > > > > > -- > > > > > > Anish Mistry > > > > > > > > > > Oh yes, you need to compile it without witness support, or > > > > > invariants (DDB is fine, though). It, of course, cuts out a ton > > > > > of useful debugging info for other parts, but it's the only way, > > > > > unfortunately. > > > > > > > > That's a bug you'll need to fix or the driver can go to sleep > > > > forever and never wake up. > > > > > > I figured something like. Do you have any pointers of where to get > > > started and examples of how things like this have been fixed in other > > > drivers? > > > > Well, probably the code is not Giant-safe yet, so you'll need to figure > > out why Giant isn't being held in the driver. > > Would it be better to first make the code Giant-safe, or just go ahead and > add the locking to make it MP-safe? or are these 2 seperate things? Getting the code to be MP-safe and thus not need Giant is a larger task than just adding some assertions and figuring out why Giant isn't held when it should be. It maybe that it simply needs D_NEEDSGIANT added to the flags in its cdevsw. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 21:44:08 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31AC416A4CE for ; Tue, 23 Nov 2004 21:44:08 +0000 (GMT) Received: from av4-1-sn3.vrr.skanova.net (av4-1-sn3.vrr.skanova.net [81.228.9.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id C933D43D2D for ; Tue, 23 Nov 2004 21:44:07 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av4-1-sn3.vrr.skanova.net (Postfix, from userid 502) id 0686E37F17; Tue, 23 Nov 2004 22:44:07 +0100 (CET) Received: from smtp1-1-sn3.vrr.skanova.net (smtp1-1-sn3.vrr.skanova.net [81.228.9.177]) by av4-1-sn3.vrr.skanova.net (Postfix) with ESMTP id E9F6C37F0E; Tue, 23 Nov 2004 22:44:06 +0100 (CET) Received: from sentinel (h130n1fls11o822.telia.com [213.64.66.130]) by smtp1-1-sn3.vrr.skanova.net (Postfix) with ESMTP id C36D738003; Tue, 23 Nov 2004 22:44:06 +0100 (CET) From: "Daniel Eriksson" To: , =?iso-8859-1?Q?'S=F8ren_Schmidt'?= Date: Tue, 23 Nov 2004 22:43:41 +0100 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-Index: AcTRpX9HQMvPBRkgRQKgu/bmT2sPWQ== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: ataraid and 1TB+ storage? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 21:44:08 -0000 I can't seem to use ataraid to create a 1.2TB array from 6 x 200GB discs. If I only use 5 of the discs it seems to work just fine. This is on CURRENT from today. Is this a known limitation? All 6 discs are located on a HighPoint RocketRAID 454 controller. ad4: 190782MB [387621/16/63] at ata2-master UDMA100 ad5: 190782MB [387621/16/63] at ata2-slave UDMA100 ad6: 190782MB [387621/16/63] at ata3-master UDMA100 ad7: 190782MB [387621/16/63] at ata3-slave UDMA100 ad8: 190782MB [387621/16/63] at ata4-master UDMA100 ad9: 190782MB [387621/16/63] at ata4-slave UDMA100 ERROR: ------ # atacontrol create RAID0 128 ad4 ad5 ad6 ad7 ad8 ad9 ar0: 9007199253788533MB [1499975777/255/63] status: READY subdisks: disk0 READY on ad4 at ata2-master disk1 READY on ad5 at ata2-slave disk2 READY on ad6 at ata3-master disk3 READY on ad7 at ata3-slave disk4 READY on ad8 at ata4-master disk5 READY on ad9 at ata4-slave OK: --- # atacontrol create RAID0 128 ad4 ad5 ad6 ad7 ad8 ar0: 953911MB [121606/255/63] status: READY subdisks: disk0 READY on ad4 at ata2-master disk1 READY on ad5 at ata2-slave disk2 READY on ad6 at ata3-master disk3 READY on ad7 at ata3-slave disk4 READY on ad8 at ata4-master /Daniel Eriksson From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 21:50:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D5D916A4CE for ; Tue, 23 Nov 2004 21:50:09 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0421343D31 for ; Tue, 23 Nov 2004 21:50:09 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 30426 invoked from network); 23 Nov 2004 21:50:08 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 23 Nov 2004 21:50:08 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iANLo40i037842; Tue, 23 Nov 2004 16:50:04 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Tue, 23 Nov 2004 16:48:17 -0500 User-Agent: KMail/1.6.2 References: <200411231507.19380.mistry.7@osu.edu> <200411231636.29953.jhb@FreeBSD.org> In-Reply-To: <200411231636.29953.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411231648.17128.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx Subject: Re: ATI TV Wonder support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 21:50:09 -0000 On Tuesday 23 November 2004 04:36 pm, John Baldwin wrote: > On Tuesday 23 November 2004 03:07 pm, Anish Mistry wrote: > > On Tuesday 23 November 2004 02:51 pm, John Baldwin wrote: > > > On Tuesday 23 November 2004 02:43 pm, Anish Mistry wrote: > > > > On Tuesday 23 November 2004 11:34 am, you wrote: > > > > > On Monday 22 November 2004 11:00 pm, Justin Hibbits wrote: > > > > > > On Nov 22, 2004, at 22:56, Anish Mistry wrote: > > > > > > > On Monday 22 November 2004 09:29 pm, you wrote: > > > > > > >> On Nov 22, 2004, at 21:22, Anish Mistry wrote: > > > > > > >>> On Sunday 21 November 2004 10:00 pm, Justin Hibbits wrote: > > > > > > >>>> This patch gives more or less full ATI TV Wonder support to > > > > > > >>>> the bktr driver. > > > > > > >>> > > > > > > >>> Awesome. > > > > > > >>> > > > > > > >>>> The sound doesn't mute at close, but that might be xawtv's > > > > > > >>>> fault, but > > > > > > >>>> I > > > > > > >>>> don't know which to accuse or look at. But, other than > > > > > > >>>> that, it seems pretty good. > > > > > > >>> > > > > > > >>> I've having some trouble using it though, the sound doesn't > > > > > > >>> seem to work > > > > > > >>> just as before. Is there something extra I need to add to my > > > > > > >>> kernel besides bktr? > > > > > > >>> On boot: > > > > > > >>> bktr0: mem 0xe3101000-0xe3101fff irq 11 at > > > > > > >>> device 8.0 on > > > > > > >>> pci0 > > > > > > >>> bktr0: [GIANT-LOCKED] > > > > > > >>> bktr0: Detected a MSP3445G-B8 at 0x80 > > > > > > >>> bktr0: ATI TV Wonder, Philips NTSC tuner, msp3400c stereo. > > > > > > >>> pci0: at device 8.1 (no driver attached) > > > > > > >>> And when I start it: > > > > > > >>> bktr0: Detected a MSP3445G-B8 at 0x80 > > > > > > >>> > > > > > > >>> You should also send-pr this if you haven't already. > > > > > > >>> > > > > > > >>> Thanks, > > > > > > >>> > > > > > > >>> -- > > > > > > >>> Anish Mistry > > > > > > >> > > > > > > >> Oh, you need to build it with the msp3400c driver, so add the > > > > > > >> line: > > > > > > >> > > > > > > >> options BKTR_NEW_MSP34XX_DRIVER > > > > > > >> > > > > > > >> to your config file. The card doesn't have any mux, only that > > > > > > >> chip, so > > > > > > >> you need the driver. I've found a hackish solution to the > > > > > > >> sound problem, by resetting the card on exit. It's horrible, > > > > > > >> so I won't include it in the patch, but it works for me. If > > > > > > >> you want to use this too, add: > > > > > > >> > > > > > > >> if (bktr->card.msp3400c ) > > > > > > >> msp_dpl_reset( bktr, bktr->msp_addr ); > > > > > > >> > > > > > > >> to bktr_core.c, at line 1171. > > > > > > >> > > > > > > >> > > > > > > >> I'll resend my previous message as a send-pr later, when I > > > > > > >> have a little more time to test it. > > > > > > > > > > > > > > Thanks, but I'm getting a weird panic with 5-STABLE, which I'm > > > > > > > assuming you > > > > > > > aren't seeing. Any ideas? > > > > > > > > > > > > > > panic: sleeping without a mutex > > > > > > > KDB: enter: panic > > > > > > > [thread 100012] > > > > > > > Stopped at kbd_enter+0x2c: leave > > > > > > > db> tr > > > > > > > kbd_enter(c0635ca1,100,c1b6c54c,c1b41320,0) at kbd_enter+0x2c > > > > > > > panic(c06363e5,0,0,0,c1b37c00) at panic+0x10a > > > > > > > msleep(c1b6c54c,0,4c,c064007d,0) at msleep+0x2bf > > > > > > > msp3410d_thread(c1bd8000,d0181d48,c1db8000,c845e1d4,0) at > > > > > > > msp3410d_thread+0x5b > > > > > > > fork_exit(c045e1d4,c1db8000,d0181d48) at fork_exit+0x7e > > > > > > > fork_trampoline() at fork_trampoline+0x8 > > > > > > > --- trap 0x1, eip=0, esp=0xd0181d7c, ebd=0 --- > > > > > > > > > > > > > > dmesg: > > > > > > > http://am-productions.biz/docs/bigguy.txt.gz > > > > > > > kernel config: > > > > > > > http://am-productions.biz/docs/BIGGUY.gz > > > > > > > -- > > > > > > > Anish Mistry > > > > > > > > > > > > Oh yes, you need to compile it without witness support, or > > > > > > invariants (DDB is fine, though). It, of course, cuts out a ton > > > > > > of useful debugging info for other parts, but it's the only way, > > > > > > unfortunately. > > > > > > > > > > That's a bug you'll need to fix or the driver can go to sleep > > > > > forever and never wake up. > > > > > > > > I figured something like. Do you have any pointers of where to get > > > > started and examples of how things like this have been fixed in other > > > > drivers? > > > > > > Well, probably the code is not Giant-safe yet, so you'll need to figure > > > out why Giant isn't being held in the driver. > > > > Would it be better to first make the code Giant-safe, or just go ahead > > and add the locking to make it MP-safe? or are these 2 seperate things? > > Getting the code to be MP-safe and thus not need Giant is a larger task > than just adding some assertions and figuring out why Giant isn't held when > it should be. It maybe that it simply needs D_NEEDSGIANT added to the > flags in its cdevsw. Actually, it looks like the patch changes the code to kick off a new kthread and that new kthread is going to need to acquire Giant at the start of its main() function and drop it before calling kthread_exit() and/or returning. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 21:53:19 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0930716A4CF for ; Tue, 23 Nov 2004 21:53:19 +0000 (GMT) Received: from aiolos.otenet.gr (aiolos.otenet.gr [195.170.0.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id C622C43D1D for ; Tue, 23 Nov 2004 21:53:16 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from gothmog.gr (patr530-a055.otenet.gr [212.205.215.55]) iANLrDg4018524; Tue, 23 Nov 2004 23:53:14 +0200 Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.13.1/8.13.1) with ESMTP id iANKmxxu002054; Tue, 23 Nov 2004 22:48:59 +0200 (EET) (envelope-from keramida@linux.gr) Received: (from giorgos@localhost) by gothmog.gr (8.13.1/8.13.1/Submit) id iANKmx8M002053; Tue, 23 Nov 2004 22:48:59 +0200 (EET) (envelope-from keramida@linux.gr) Date: Tue, 23 Nov 2004 22:48:59 +0200 From: Giorgos Keramidas To: Wiktor Niesiobedzki Message-ID: <20041123204859.GA2002@gothmog.gr> References: <20041123171951.GG3584@mail.evip.pl> <20041123183930.GA56352@orion.daedalusnetworks.priv> <20041123185923.GH3584@mail.evip.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041123185923.GH3584@mail.evip.pl> cc: current@freebsd.org Subject: Re: Putty or libcrypto bug? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 21:53:19 -0000 On 2004-11-23 19:59, Wiktor Niesiobedzki wrote: >On Tue, Nov 23, 2004 at 08:39:30PM +0200, Giorgos Keramidas wrote: >> This is a Bad Idea(TM) most of the time though. The library >> implements a function that other programs or libraries may depend upon >> to work in certain ways. Replacing the library function with a >> hand-rolled version may or may not work -- the latter in this case :-/ > > Should'nt libc load nss_ldap with kind of RTLD_LOCAL, so the libc will load > libldap in another symbol-space so symbol lookups will not end in main > program (if it is at all possible... I'm not familiar with dynamic linking)? What happens if parts of the program want to access symbols from many disjoint namespaces? If a program links to two shared objects: libfoo.so.1 and libmore.2, which in turn depend on other shared objects, for example: program libfoo.so.1 libtest.so.3 libmore.so.2 libtmp.so.4 libthread.so.5 and libmore _does_ want to override thread_create() from libthread.so.5 but libtmp.so.4 wants only the original thread_create() function from libthread.so.5, which function will the runtime linker call when `program' calls thread_create()? > If not, then it is the fact, that programmer of any program should > aviod duplicating function names across every library that may > eventually be installed and somehow linked to this programm, what > sounds rather ridiculous to me. I don't think there is support for multiple symbol namespaces in C. This is probably why most of the utilities in the src/ tree export as few symbols as possible; many times just a main() function. Judicious use of static scope and unique name prefixes like putty_ may avoid such problems without the need for `RTLD_LOCAL'. - Giorgos From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 21:58:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8AC9E16A4CE for ; Tue, 23 Nov 2004 21:58:02 +0000 (GMT) Received: from av4-1-sn3.vrr.skanova.net (av4-1-sn3.vrr.skanova.net [81.228.9.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 236A443D31 for ; Tue, 23 Nov 2004 21:58:02 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av4-1-sn3.vrr.skanova.net (Postfix, from userid 502) id 5475B37F84; Tue, 23 Nov 2004 22:58:01 +0100 (CET) Received: from smtp1-1-sn3.vrr.skanova.net (smtp1-1-sn3.vrr.skanova.net [81.228.9.177]) by av4-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 43FAB37EDC; Tue, 23 Nov 2004 22:58:01 +0100 (CET) Received: from sentinel (h130n1fls11o822.telia.com [213.64.66.130]) by smtp1-1-sn3.vrr.skanova.net (Postfix) with ESMTP id F1CBA38005; Tue, 23 Nov 2004 22:58:00 +0100 (CET) From: "Daniel Eriksson" To: , =?iso-8859-1?Q?'S=F8ren_Schmidt'?= Date: Tue, 23 Nov 2004 22:57:35 +0100 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-Index: AcTRpX9HQMvPBRkgRQKgu/bmT2sPWQAAaIwg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: Subject: RE: ataraid and 1TB+ storage? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 21:58:02 -0000 I wrote: > ERROR: > ------ > # atacontrol create RAID0 128 ad4 ad5 ad6 ad7 ad8 ad9 > ar0: 9007199253788533MB [1499975777/255/63] As can be seen here, the size is not 1.2TB. Trying to create a filesystem on the device fails with a warning about it having a preposterous(sp?) size. Striping the 6 discs using gstripe seems to work just fine. /Daniel Eriksson From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 22:19:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C534F16A4CF; Tue, 23 Nov 2004 22:19:35 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21D2143D6B; Tue, 23 Nov 2004 22:19:35 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.0.5] (adsl-68-250-184-205.dsl.wotnoh.ameritech.net [68.250.184.205]) (authenticated bits=0)iANLxXeB042901 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 23 Nov 2004 16:59:35 -0500 (EST) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: John Baldwin Date: Tue, 23 Nov 2004 17:22:07 -0500 User-Agent: KMail/1.7 References: <200411231636.29953.jhb@FreeBSD.org> <200411231648.17128.jhb@FreeBSD.org> In-Reply-To: <200411231648.17128.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1394750.p0qH7Ocs9P"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411231722.25392.mistry.7@osu.edu> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on crumpet.united-ware.com cc: Justin Hibbits cc: freebsd-current@freebsd.org Subject: Re: ATI TV Wonder support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 22:19:36 -0000 --nextPart1394750.p0qH7Ocs9P Content-Type: multipart/mixed; boundary="Boundary-01=_Pg7oBudYOV4Jn6z" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_Pg7oBudYOV4Jn6z Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 23 November 2004 04:48 pm, John Baldwin wrote: > On Tuesday 23 November 2004 04:36 pm, John Baldwin wrote: > > On Tuesday 23 November 2004 03:07 pm, Anish Mistry wrote: > > > On Tuesday 23 November 2004 02:51 pm, John Baldwin wrote: > > > > On Tuesday 23 November 2004 02:43 pm, Anish Mistry wrote: > > > > > On Tuesday 23 November 2004 11:34 am, you wrote: > > > > > > On Monday 22 November 2004 11:00 pm, Justin Hibbits wrote: > > > > > > > On Nov 22, 2004, at 22:56, Anish Mistry wrote: > > > > > > > > On Monday 22 November 2004 09:29 pm, you wrote: > > > > > > > >> On Nov 22, 2004, at 21:22, Anish Mistry wrote: > > > > > > > >>> On Sunday 21 November 2004 10:00 pm, Justin Hibbits=20 wrote: > > > > > > > >>>> This patch gives more or less full ATI TV Wonder > > > > > > > >>>> support to the bktr driver. > > > > > > > >>> > > > > > > > >>> Awesome. > > > > > > > >>> > > > > > > > >>>> The sound doesn't mute at close, but that might be > > > > > > > >>>> xawtv's fault, but > > > > > > > >>>> I > > > > > > > >>>> don't know which to accuse or look at. But, other than > > > > > > > >>>> that, it seems pretty good. > > > > > > > >>> > > > > > > > >>> I've having some trouble using it though, the sound > > > > > > > >>> doesn't seem to work > > > > > > > >>> just as before. Is there something extra I need to add > > > > > > > >>> to my kernel besides bktr? > > > > > > > >>> On boot: > > > > > > > >>> bktr0: mem 0xe3101000-0xe3101fff irq 11 > > > > > > > >>> at device 8.0 on > > > > > > > >>> pci0 > > > > > > > >>> bktr0: [GIANT-LOCKED] > > > > > > > >>> bktr0: Detected a MSP3445G-B8 at 0x80 > > > > > > > >>> bktr0: ATI TV Wonder, Philips NTSC tuner, msp3400c > > > > > > > >>> stereo. pci0: at device 8.1 (no driver > > > > > > > >>> attached) And when I start it: > > > > > > > >>> bktr0: Detected a MSP3445G-B8 at 0x80 > > > > > > > >>> > > > > > > > >>> You should also send-pr this if you haven't already. > > > > > > > >>> > > > > > > > >>> Thanks, > > > > > > > >>> > > > > > > > >>> -- > > > > > > > >>> Anish Mistry > > > > > > > >> > > > > > > > >> Oh, you need to build it with the msp3400c driver, so add > > > > > > > >> the line: > > > > > > > >> > > > > > > > >> options BKTR_NEW_MSP34XX_DRIVER > > > > > > > >> > > > > > > > >> to your config file. The card doesn't have any mux, only > > > > > > > >> that chip, so > > > > > > > >> you need the driver. I've found a hackish solution to > > > > > > > >> the sound problem, by resetting the card on exit. It's > > > > > > > >> horrible, so I won't include it in the patch, but it > > > > > > > >> works for me. If you want to use this too, add: > > > > > > > >> > > > > > > > >> if (bktr->card.msp3400c ) > > > > > > > >> msp_dpl_reset( bktr, bktr->msp_addr ); > > > > > > > >> > > > > > > > >> to bktr_core.c, at line 1171. > > > > > > > >> > > > > > > > >> > > > > > > > >> I'll resend my previous message as a send-pr later, when > > > > > > > >> I have a little more time to test it. > > > > > > > > > > > > > > > > Thanks, but I'm getting a weird panic with 5-STABLE, which > > > > > > > > I'm assuming you > > > > > > > > aren't seeing. Any ideas? > > > > > > > > > > > > > > > > panic: sleeping without a mutex > > > > > > > > KDB: enter: panic > > > > > > > > [thread 100012] > > > > > > > > Stopped at kbd_enter+0x2c: leave > > > > > > > > db> tr > > > > > > > > kbd_enter(c0635ca1,100,c1b6c54c,c1b41320,0) at > > > > > > > > kbd_enter+0x2c panic(c06363e5,0,0,0,c1b37c00) at > > > > > > > > panic+0x10a > > > > > > > > msleep(c1b6c54c,0,4c,c064007d,0) at msleep+0x2bf > > > > > > > > msp3410d_thread(c1bd8000,d0181d48,c1db8000,c845e1d4,0) at > > > > > > > > msp3410d_thread+0x5b > > > > > > > > fork_exit(c045e1d4,c1db8000,d0181d48) at fork_exit+0x7e > > > > > > > > fork_trampoline() at fork_trampoline+0x8 > > > > > > > > --- trap 0x1, eip=3D0, esp=3D0xd0181d7c, ebd=3D0 --- > > > > > > > > > > > > > > > > dmesg: > > > > > > > > http://am-productions.biz/docs/bigguy.txt.gz > > > > > > > > kernel config: > > > > > > > > http://am-productions.biz/docs/BIGGUY.gz > > > > > > > > -- > > > > > > > > Anish Mistry > > > > > > > > > > > > > > Oh yes, you need to compile it without witness support, or > > > > > > > invariants (DDB is fine, though). It, of course, cuts out a > > > > > > > ton of useful debugging info for other parts, but it's the > > > > > > > only way, unfortunately. > > > > > > > > > > > > That's a bug you'll need to fix or the driver can go to sleep > > > > > > forever and never wake up. > > > > > > > > > > I figured something like. Do you have any pointers of where to > > > > > get started and examples of how things like this have been fixed > > > > > in other drivers? > > > > > > > > Well, probably the code is not Giant-safe yet, so you'll need to > > > > figure out why Giant isn't being held in the driver. > > > > > > Would it be better to first make the code Giant-safe, or just go > > > ahead and add the locking to make it MP-safe? or are these 2 > > > seperate things? > > > > Getting the code to be MP-safe and thus not need Giant is a larger > > task than just adding some assertions and figuring out why Giant isn't > > held when it should be. It maybe that it simply needs D_NEEDSGIANT > > added to the flags in its cdevsw. > > Actually, it looks like the patch changes the code to kick off a new > kthread and that new kthread is going to need to acquire Giant at the > start of its main() function and drop it before calling kthread_exit() > and/or returning. How about the attached patch? http://am-productions.biz/docs/msp34xx-giant-locking.c.diff =2D-=20 Anish Mistry --Boundary-01=_Pg7oBudYOV4Jn6z Content-Type: text/x-diff; charset="iso-8859-1"; name="msp34xx-giant-locking.c.diff" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="msp34xx-giant-locking.c.diff" =2D-- msp34xx.c.orig Mon Nov 22 22:57:42 2004 +++ msp34xx.c Tue Nov 23 17:10:16 2004 @@ -702,6 +702,7 @@ =09 dprintk("msp3400: thread started\n"); =09 + mtx_lock(&Giant); for (;;) { if (msp->rmmod) goto done; @@ -892,6 +893,7 @@ =20 msp->kthread =3D NULL; wakeup(&msp->kthread); + mtx_unlock(&Giant); =20 kthread_exit(0); } @@ -936,6 +938,7 @@ =20 dprintk("msp3410: thread started\n"); =09 + mtx_lock(&Giant); for (;;) { if (msp->rmmod) goto done; @@ -1114,9 +1117,10 @@ done: dprintk("msp3410: thread: exit\n"); msp->active =3D 0; =2D +=09 msp->kthread =3D NULL; wakeup(&msp->kthread); + mtx_unlock(&Giant); =20 kthread_exit(0); } @@ -1213,12 +1217,14 @@ if (msp->kthread)=20 { /* XXX mutex lock required */ + mtx_lock(&Giant); msp->rmmod =3D 1; msp->watch_stereo =3D 0; wakeup(msp->kthread); =20 while (msp->kthread) tsleep(&msp->kthread, PRIBIO, "wait for kthread", hz/10); + mtx_unlock(&Giant); } =20 if (client->msp3400c_info !=3D NULL) { --Boundary-01=_Pg7oBudYOV4Jn6z-- --nextPart1394750.p0qH7Ocs9P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBo7ghxqA5ziudZT0RAoXWAKCJYO6Gem4fEQoUmNdpsjGg/rJ6KwCfZjDs 5IwChxXe8oeIxLxRDg3KGoQ= =k+2L -----END PGP SIGNATURE----- --nextPart1394750.p0qH7Ocs9P-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 22:31:55 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B088416A4CE for ; Tue, 23 Nov 2004 22:31:55 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2934343D5F for ; Tue, 23 Nov 2004 22:31:55 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 6963 invoked from network); 23 Nov 2004 22:31:55 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 23 Nov 2004 22:31:54 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iANMVoRJ038102; Tue, 23 Nov 2004 17:31:50 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Anish Mistry Date: Tue, 23 Nov 2004 17:31:25 -0500 User-Agent: KMail/1.6.2 References: <200411231648.17128.jhb@FreeBSD.org> <200411231722.25392.mistry.7@osu.edu> In-Reply-To: <200411231722.25392.mistry.7@osu.edu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411231731.25019.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Justin Hibbits cc: freebsd-current@FreeBSD.org Subject: Re: ATI TV Wonder support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 22:31:55 -0000 On Tuesday 23 November 2004 05:22 pm, Anish Mistry wrote: > On Tuesday 23 November 2004 04:48 pm, John Baldwin wrote: > > On Tuesday 23 November 2004 04:36 pm, John Baldwin wrote: > > > On Tuesday 23 November 2004 03:07 pm, Anish Mistry wrote: > > > > On Tuesday 23 November 2004 02:51 pm, John Baldwin wrote: > > > > > On Tuesday 23 November 2004 02:43 pm, Anish Mistry wrote: > > > > > > On Tuesday 23 November 2004 11:34 am, you wrote: > > > > > > > On Monday 22 November 2004 11:00 pm, Justin Hibbits wrote: > > > > > > > > On Nov 22, 2004, at 22:56, Anish Mistry wrote: > > > > > > > > > On Monday 22 November 2004 09:29 pm, you wrote: > > > > > > > > >> On Nov 22, 2004, at 21:22, Anish Mistry wrote: > > > > > > > > >>> On Sunday 21 November 2004 10:00 pm, Justin Hibbits > > wrote: > > > > > > > > >>>> This patch gives more or less full ATI TV Wonder > > > > > > > > >>>> support to the bktr driver. > > > > > > > > >>> > > > > > > > > >>> Awesome. > > > > > > > > >>> > > > > > > > > >>>> The sound doesn't mute at close, but that might be > > > > > > > > >>>> xawtv's fault, but > > > > > > > > >>>> I > > > > > > > > >>>> don't know which to accuse or look at. But, other than > > > > > > > > >>>> that, it seems pretty good. > > > > > > > > >>> > > > > > > > > >>> I've having some trouble using it though, the sound > > > > > > > > >>> doesn't seem to work > > > > > > > > >>> just as before. Is there something extra I need to add > > > > > > > > >>> to my kernel besides bktr? > > > > > > > > >>> On boot: > > > > > > > > >>> bktr0: mem 0xe3101000-0xe3101fff irq 11 > > > > > > > > >>> at device 8.0 on > > > > > > > > >>> pci0 > > > > > > > > >>> bktr0: [GIANT-LOCKED] > > > > > > > > >>> bktr0: Detected a MSP3445G-B8 at 0x80 > > > > > > > > >>> bktr0: ATI TV Wonder, Philips NTSC tuner, msp3400c > > > > > > > > >>> stereo. pci0: at device 8.1 (no driver > > > > > > > > >>> attached) And when I start it: > > > > > > > > >>> bktr0: Detected a MSP3445G-B8 at 0x80 > > > > > > > > >>> > > > > > > > > >>> You should also send-pr this if you haven't already. > > > > > > > > >>> > > > > > > > > >>> Thanks, > > > > > > > > >>> > > > > > > > > >>> -- > > > > > > > > >>> Anish Mistry > > > > > > > > >> > > > > > > > > >> Oh, you need to build it with the msp3400c driver, so add > > > > > > > > >> the line: > > > > > > > > >> > > > > > > > > >> options BKTR_NEW_MSP34XX_DRIVER > > > > > > > > >> > > > > > > > > >> to your config file. The card doesn't have any mux, only > > > > > > > > >> that chip, so > > > > > > > > >> you need the driver. I've found a hackish solution to > > > > > > > > >> the sound problem, by resetting the card on exit. It's > > > > > > > > >> horrible, so I won't include it in the patch, but it > > > > > > > > >> works for me. If you want to use this too, add: > > > > > > > > >> > > > > > > > > >> if (bktr->card.msp3400c ) > > > > > > > > >> msp_dpl_reset( bktr, bktr->msp_addr ); > > > > > > > > >> > > > > > > > > >> to bktr_core.c, at line 1171. > > > > > > > > >> > > > > > > > > >> > > > > > > > > >> I'll resend my previous message as a send-pr later, when > > > > > > > > >> I have a little more time to test it. > > > > > > > > > > > > > > > > > > Thanks, but I'm getting a weird panic with 5-STABLE, which > > > > > > > > > I'm assuming you > > > > > > > > > aren't seeing. Any ideas? > > > > > > > > > > > > > > > > > > panic: sleeping without a mutex > > > > > > > > > KDB: enter: panic > > > > > > > > > [thread 100012] > > > > > > > > > Stopped at kbd_enter+0x2c: leave > > > > > > > > > db> tr > > > > > > > > > kbd_enter(c0635ca1,100,c1b6c54c,c1b41320,0) at > > > > > > > > > kbd_enter+0x2c panic(c06363e5,0,0,0,c1b37c00) at > > > > > > > > > panic+0x10a > > > > > > > > > msleep(c1b6c54c,0,4c,c064007d,0) at msleep+0x2bf > > > > > > > > > msp3410d_thread(c1bd8000,d0181d48,c1db8000,c845e1d4,0) at > > > > > > > > > msp3410d_thread+0x5b > > > > > > > > > fork_exit(c045e1d4,c1db8000,d0181d48) at fork_exit+0x7e > > > > > > > > > fork_trampoline() at fork_trampoline+0x8 > > > > > > > > > --- trap 0x1, eip=0, esp=0xd0181d7c, ebd=0 --- > > > > > > > > > > > > > > > > > > dmesg: > > > > > > > > > http://am-productions.biz/docs/bigguy.txt.gz > > > > > > > > > kernel config: > > > > > > > > > http://am-productions.biz/docs/BIGGUY.gz > > > > > > > > > -- > > > > > > > > > Anish Mistry > > > > > > > > > > > > > > > > Oh yes, you need to compile it without witness support, or > > > > > > > > invariants (DDB is fine, though). It, of course, cuts out a > > > > > > > > ton of useful debugging info for other parts, but it's the > > > > > > > > only way, unfortunately. > > > > > > > > > > > > > > That's a bug you'll need to fix or the driver can go to sleep > > > > > > > forever and never wake up. > > > > > > > > > > > > I figured something like. Do you have any pointers of where to > > > > > > get started and examples of how things like this have been fixed > > > > > > in other drivers? > > > > > > > > > > Well, probably the code is not Giant-safe yet, so you'll need to > > > > > figure out why Giant isn't being held in the driver. > > > > > > > > Would it be better to first make the code Giant-safe, or just go > > > > ahead and add the locking to make it MP-safe? or are these 2 > > > > seperate things? > > > > > > Getting the code to be MP-safe and thus not need Giant is a larger > > > task than just adding some assertions and figuring out why Giant isn't > > > held when it should be. It maybe that it simply needs D_NEEDSGIANT > > > added to the flags in its cdevsw. > > > > Actually, it looks like the patch changes the code to kick off a new > > kthread and that new kthread is going to need to acquire Giant at the > > start of its main() function and drop it before calling kthread_exit() > > and/or returning. > > How about the attached patch? > http://am-productions.biz/docs/msp34xx-giant-locking.c.diff Looks like a good candidate to me. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 22:32:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C66CB16A4D0 for ; Tue, 23 Nov 2004 22:32:16 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id B17A243D2D for ; Tue, 23 Nov 2004 22:32:14 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 0D95B8566C; Wed, 24 Nov 2004 09:02:11 +1030 (CST) Date: Wed, 24 Nov 2004 09:02:11 +1030 From: Greg 'groggy' Lehey To: Ivan Voras Message-ID: <20041123223210.GL21905@wantadilla.lemis.com> References: <41A2488F.8030802@fer.hr> <20041122215228.J568@korben.in.tern> <41A33907.5020703@fer.hr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Mit9XoPEfICDqq/V" Content-Disposition: inline In-Reply-To: <41A33907.5020703@fer.hr> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: current@freebsd.org Subject: Re: gvinum panic? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 22:32:16 -0000 --Mit9XoPEfICDqq/V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tuesday, 23 November 2004 at 14:20:07 +0100, Ivan Voras wrote: > Lukas Ertl wrote: >> On Mon, 22 Nov 2004, Ivan Voras wrote: >> >>> I'm consistently getting a system panic, trap #12 in process g_event >>> when I try: >> >> Are you sure that kernel (modules) and userland are in sync? > > Thanks, it looks like they've been unsynced for a while :( > It's ok now. > > But, the performance is pretty bad (same with regular vinum). I tried > setting up graid3 class with same parameters, and got these results: > > linear read (1024 MB file, blocks of 32768) ................. 38.5 MB/s > linear write (1024 MB file, blocks of 32768) ................ 16.8 MB/s > random read (1024 MB file, blocks of 32768) ................. 41.9 MB/s > random write (1024 MB file, blocks of 32768) ................ 3.4 MB/s > > > with raid5, gvinum or vinum, I get these: > > linear read (1024 MB file, blocks of 32768) ................. 27.8 MB/s > linear write (1024 MB file, blocks of 32768) ................ 4.2 MB/s > random read (1024 MB file, blocks of 32768) ................. 44.2 MB/s > random write (1024 MB file, blocks of 32768) ................ 1.9 MB/s > > (random reads are really random, no clustering or anything). > My setup is 2 IDE channels with three discs, so one is a slave (and > contains the parity disc in case of raid3). Do these numbers make > sense? Not without clarifying what you're doing. If you're only doing one request at a time, there's no way that RAID can help you. I find it highly unlikely that all three RAID alternatives generate the same numbers. Greg -- See complete headers for address and phone numbers. --Mit9XoPEfICDqq/V Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBo7pqIubykFB6QiMRAgpJAKCfsG6SCRzYCyfT3pTNG56rC0hlzwCcD0Jj 0YLJz+Kw4ZiJA/gxvq4SjIE= =+Q9O -----END PGP SIGNATURE----- --Mit9XoPEfICDqq/V-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 22:32:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3650216A4CE for ; Tue, 23 Nov 2004 22:32:47 +0000 (GMT) Received: from tensor.xs4all.nl (tensor.xs4all.nl [194.109.160.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA0BA43D1F for ; Tue, 23 Nov 2004 22:32:46 +0000 (GMT) (envelope-from dimitry@andric.com) Received: from kilgore.dim (kilgore.dim [192.168.0.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.xs4all.nl (Postfix) with ESMTP id 7A87F22852; Tue, 23 Nov 2004 23:32:44 +0100 (CET) Date: Tue, 23 Nov 2004 23:32:33 +0100 From: Dimitry Andric X-Mailer: The Bat! (v3.0.2.7) Professional X-Priority: 3 (Normal) Message-ID: <776228597.20041123233233@andric.com> To: "Daniel Eriksson" In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="----------6817D104BDB1059" cc: freebsd-current@freebsd.org cc: =?ISO-8859-1?Q?'S=F8ren_Schmidt'?= Subject: Re: ataraid and 1TB+ storage? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 22:32:47 -0000 ------------6817D104BDB1059 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable On 2004-11-23 at 22:43:41 Daniel Eriksson wrote: > ad4: 190782MB [387621/16/63] at ata2-master UDMA100 > ad5: 190782MB [387621/16/63] at ata2-slave UDMA100 > ad6: 190782MB [387621/16/63] at ata3-master UDMA100 > ad7: 190782MB [387621/16/63] at ata3-slave UDMA100 > ad8: 190782MB [387621/16/63] at ata4-master UDMA100 > ad9: 190782MB [387621/16/63] at ata4-slave UDMA100 [...] > ar0: 9007199253788533MB [1499975777/255/63] status: REA= DY This looks like a wraparound over 2^31 sectors, so the sector count gets negative. And then this is interpreted as a 64-bit unsigned: (2^64 - (6*387621*16*63 - 2^31)) / 2 / 1024 =3D 9007199254644874 MB Not exactly, but close enough to the reported 9007199253788533 MB, I would think... If anyone can explain the difference, please let us know. (I'm guessing that the LBA capacity of the individual drives is a bit different from the 387621/16/63 geometry they're reporting.) Anyway, this is probably some bug in the ataraid driver. :) ------------6817D104BDB1059 Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: GnuPG v1.2.5 (MingW32) iD8DBQFBo7qBsF6jCi4glqMRAjzKAJ0TdjJ/SJLyitxHjOZ9eDK9rTpnmgCeJx+L g7Lh4lpFBVStF9kYT23xt3c= =8zYA -----END PGP MESSAGE----- ------------6817D104BDB1059-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 00:33:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D99016A4CE for ; Wed, 24 Nov 2004 00:33:23 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65FD443D31 for ; Wed, 24 Nov 2004 00:33:22 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAO0WKZg009812 for ; Wed, 24 Nov 2004 11:02:20 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Wed, 24 Nov 2004 11:03:12 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAO0Pjh30212 for ; Wed, 24 Nov 2004 10:55:46 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id XM1D0AHF; Wed, 24 Nov 2004 10:55:42 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAO0Q3gX021012 for ; Wed, 24 Nov 2004 10:56:03 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAO0Q3ka021011 for freebsd-current@freebsd.org; Wed, 24 Nov 2004 10:56:03 +1030 (CST) (envelope-from wilkinsa) Date: Wed, 24 Nov 2004 10:56:03 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20041124002603.GD20881@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org References: <200411231226.38172.jkim@niksun.com> <200411231343.22760.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <200411231343.22760.jhb@FreeBSD.org> User-Agent: Mutt/1.5.6i Subject: Re: Transparent bridges (a. k. a. HUB-to-PCI bridges)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 00:33:23 -0000 Trying to understand your nomenclature John, so that I can follow this thread. Can you please elaborate on the following .... please ;-\ 1. PCI bridges - Host-PCI - PCI-PCI 2. OOPish device object (device_t) ? 3. $PIR table - aW 0n Tue, Nov 23, 2004 at 01:43:22PM -0500, John Baldwin wrote: > On Tuesday 23 November 2004 12:26 pm, Jung-uk Kim wrote: > > While I was booting Linux, I saw a 'transparent bridge' from dmesg and > > started digging up because I was fighting against 'interrupt > > storming' and 'stray IRQ' problems with the latest Intel chipsets > > recently and I had a feeling that it's somehow related. > > > > http://lxr.linux.no/source/drivers/pci/probe.c?v=2.6.8.1#L195 > > http://lxr.linux.no/source/arch/i386/pci/fixup.c?v=2.6.8.1#L192 > > http://lxr.linux.no/source/arch/i386/pci/irq.c?v=2.6.8.1#L870 > > http://lxr.linux.no/source/arch/i386/pci/irq.c?v=2.6.8.1#L1017 > > > > But I don't see any special treatment in FreeBSD's PCI driver. > > > > 1. Is this relevant for FreeBSD? > > 2. Is this related to the problems (esp. SMP)? > > First of all, I have no idea what type of interrupt routing problems you are > having, but as for the above: > > FreeBSD uses a much simpler way of managing PCI interrupt routing. In > FreeBSD, each hardware device (including PCI bridges (whether Host-PCI or > PCI-PCI) and PCI busses) have an OOPish device object (device_t) associated > with them. You can see the tree structure via 'devinfo'. The way FreeBSD > implements interrupt routing is that each PCI bridge driver provides a method > for determining the IRQ associated with a given bus/device/pin tuple. (The > bus is implicit since each bridge only handles requests for its immediate > downstream bus.) In order to make use of the several different ways of > determining interrupt routing, there are several different PCI bridge drivers > for both Host-PCI and PCI-PCI bridges. For example, there are ACPI Host-PCI > and PCI-PCI bridge drivers that will route interrupts using the _PRT table > objects provided by ACPI for busses in ACPI's namespace. Also, there are > PCIBIOS bridge drivers to handle routing for the non-ACPI non-APIC case using > the information in the $PIR table. Similarly, for the non-ACPI APIC case, > there are MP Table bridge drivers to route interrupts for busses that are > listed in the MP Table. If a PCI-PCI bridge is not enumerated in ACPI space > on an ACPI system or is not listed in either the $PIR (non-APIC) or MP Table > (APIC) on a non-ACPI system, then the bridge will be probed via the simple > PCI-PCI bridge driver which does the standard barber-pole swizzle to route > interrupts based off the intpins on the bridge device's upstream connection. > Thus, for "transparent" bridges not listed in the MP Table, the MP Table > driver won't attach and it will fall back to the simple PCI-PCI bridge driver > and just work. > > Now, back to your original problem: what type of interrupt problems are you > having? > > -- > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" = http://www.FreeBSD.org > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 01:22:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C667616A4CE; Wed, 24 Nov 2004 01:22:25 +0000 (GMT) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDEBD43D1D; Wed, 24 Nov 2004 01:22:23 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.43 (FreeBSD)) id 1CWlrm-0001ZV-Nh; Wed, 24 Nov 2004 09:22:43 +0800 Message-Id: <6.2.0.14.2.20041124091640.03064eb0@202.179.0.80> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Wed, 24 Nov 2004 09:22:12 +0800 To: Robert Watson From: Ganbold Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: tomaz.borstnar@over.net cc: cguttesen@yahoo.dk cc: scottl@freebsd.org cc: mhunter@ack.Berkeley.EDU cc: freebsd-current@freebsd.org Subject: Re: Page fault in FreeBSD 5.3 on IBM e325, Dual AMD64 2.2GHz, 4GB RAM, ServeRAID 6M - problem goes away without TCP sack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 01:22:25 -0000 At 06:43 PM 11/22/2004, you wrote: > > > > It seems to me the problem is related to network stack and threading. > > Am I right? How to solve this problem? > >I've seen reports of this problem with and without debug.mpsafenet=1, >which suggests it is a network stack bug but not specific to locking. I've >also seen reports that disabling TCP SACK will make the problem go away, >which would be good to confirm. I spent the weekend building up some more >expertise in TCP and reading a lot of TCP code, and hope to look at this >problem in more detail today. You may want to try turning off TCP sack >using net.inet.tcp.sack.enable=0 in sysctl.conf (or loader.conf). I turned off TCP sack using net.inet.tcp.sack.enable=0 in sysctl.conf and it seems like the problem goes away. It is working for more than 20 hours without any crash. Robert, did you find anything in network stack code? I'm just curious. thanks a lot, Ganbold >Robert N M Watson FreeBSD Core Team, TrustedBSD Projects >robert@fledge.watson.org Principal Research Scientist, McAfee Research > > >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 03:39:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07D4B16A4CE for ; Wed, 24 Nov 2004 03:39:24 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E7AA43D46 for ; Wed, 24 Nov 2004 03:39:19 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iAO3dCik002027; Wed, 24 Nov 2004 14:09:12 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Wed, 24 Nov 2004 14:09:03 +1030 User-Agent: KMail/1.7 References: <71F713C5E3CB7F4F9ACCBBB8E9BE318A39E348@blrx2kmbgl101.blr.amer.dell.com> <20041123105313.GC753@zaphod.nitro.dk> <007201c4d190$3c6bf3a0$d232a8c0@LCI> In-Reply-To: <007201c4d190$3c6bf3a0$d232a8c0@LCI> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1862145.zeytXrVEz4"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411241409.10971.doconnor@gsoft.com.au> X-Spam-Score: -1.7 () IN_REP_TO,PGP_SIGNATURE_2,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: Samuel Clements Subject: Re: supported new Dell PERC cards - need to add to the Hardwarenotes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 03:39:24 -0000 --nextPart1862145.zeytXrVEz4 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 24 Nov 2004 05:41, Samuel Clements wrote: > amr0: mem 0xfc780000-0xfc7fffff,0xfc2f0000-0xfc2fffff > irq 19 at device 0.0 on pci4 > amr0: Firmware 413Y, BIOS H42= 0, > 128MB RAM > > I love this re-branding stuff! The reverse is worse :( ie wireless cards - same name (eg DWL-650) with radically different technol= ogy=20 on the inside. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1862145.zeytXrVEz4 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBpAJe5ZPcIHs/zowRAidLAJ0QNMiKSogyTyDgq9hbCnIzOSjWVwCfc+5H 6Ka1VfMpTkRGq54DT64dJWI= =6Wa0 -----END PGP SIGNATURE----- --nextPart1862145.zeytXrVEz4-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 03:57:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DF6116A4CE for ; Wed, 24 Nov 2004 03:57:31 +0000 (GMT) Received: from crumpler-s1.mel.crumpler.com.au (b20FB.static.pacific.net.au [210.23.137.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D72243D41 for ; Wed, 24 Nov 2004 03:57:30 +0000 (GMT) (envelope-from listsubs@crippy.mel.crumpler.com.au) Received: from [192.168.112.129] ([203.208.117.166]) by crumpler-s1.mel.crumpler.com.au over TLS secured channel with Microsoft SMTPSVC(5.0.2195.6713); Wed, 24 Nov 2004 14:57:28 +1100 Message-ID: <41A3D73E.7040608@crippy.mel.crumpler.com.au> Date: Wed, 24 Nov 2004 11:35:10 +1100 From: Phillip Crumpler User-Agent: Mozilla Thunderbird 0.7.3 (X11/20041004) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <71F713C5E3CB7F4F9ACCBBB8E9BE318A39E348@blrx2kmbgl101.blr.amer.dell.com> <20041123105313.GC753@zaphod.nitro.dk> <007201c4d190$3c6bf3a0$d232a8c0@LCI> <200411241409.10971.doconnor@gsoft.com.au> In-Reply-To: <200411241409.10971.doconnor@gsoft.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 24 Nov 2004 03:57:28.0508 (UTC) FILETIME=[B735C7C0:01C4D1D9] Subject: Re: supported new Dell PERC cards - need to add to the Hardwarenotes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 03:57:31 -0000 Daniel O'Connor wrote: >On Wed, 24 Nov 2004 05:41, Samuel Clements wrote: > > >>amr0: mem 0xfc780000-0xfc7fffff,0xfc2f0000-0xfc2fffff >>irq 19 at device 0.0 on pci4 >>amr0: Firmware 413Y, BIOS H420, >>128MB RAM >> >>I love this re-branding stuff! >> >> > >The reverse is worse :( >ie wireless cards - same name (eg DWL-650) with radically different technology >on the inside. > > > On a somewhat related note: can anyone report any success with the DELL 'CERC 6-Channel SATA RAID Controller'? aac(4) claims to support a DELL CERC SATA RAID 2 but I think that this is an older beast. Phillip From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 05:07:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7389B16A4CE for ; Wed, 24 Nov 2004 05:07:28 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEBA943D46 for ; Wed, 24 Nov 2004 05:07:27 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.250] (pool-68-161-115-118.ny325.east.verizon.net [68.161.115.118]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id iAO57AJH065478 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Nov 2004 00:07:13 -0500 (EST) Message-ID: <41A416E7.4030107@mac.com> Date: Wed, 24 Nov 2004 00:06:47 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Wilkinson, Alex" References: <200411231226.38172.jkim@niksun.com> <200411231343.22760.jhb@FreeBSD.org> <20041124002603.GD20881@squash.dsto.defence.gov.au> In-Reply-To: <20041124002603.GD20881@squash.dsto.defence.gov.au> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-4.5 required=5.5 tests=AWL,BAYES_00 autolearn=ham version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on pi.codefab.com cc: freebsd-current@freebsd.org Subject: Re: Transparent bridges (a. k. a. HUB-to-PCI bridges)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 05:07:28 -0000 Wilkinson, Alex wrote: > Trying to understand your nomenclature John, so that I can follow this thread. I'm no John Kennedy, nor even John Baldwin, but I'll give this a shot. :-) > Can you please elaborate on the following .... please ;-\ > > 1. PCI bridges > - Host-PCI > - PCI-PCI A host-PCI bridge is typically part of the "southbridge" chip of modern motherboards; on Intel motherboards this is also called the ICH chip, such as the 82801AA/BA/CA/etc. VIA Southbridges include the VT8233/8235/8237/etc. A PCI-PCI bridge is commonly found on multifunction PCI cards, an example would be the DEC 21151 chip found on various four-port NICs. > 2. OOPish device object (device_t) ? True OOP involves encapsulation, polymorphism, and inheritence, and requires language support which is not really available in pure C. That being said, careful programming in C lets you create several closely-related structs for different types of "objects" which can all be utilized by a common set of functions. The most common example of this would probably be the protocol-independent struct sockaddr, which can handle IPv4, IPv6, and other types of network address formats using a common structure (or a related group of structures, depending on how you want to look at it). See "man getaddrinfo". > 3. $PIR table Stands for PCI Interrupt Routing table. When your computer boots, the BIOS is responsible for configuring at least the devices required to boot such that they and the BIOS agree as to which IRQ each device ought to use. Blah, I couldn't find a good link outside of Microsoft, but see here: http://www.microsoft.com/whdc/archive/pciirq.mspx -- -Chuck From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 06:54:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A43716A4CE for ; Wed, 24 Nov 2004 06:54:39 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1261543D3F for ; Wed, 24 Nov 2004 06:54:39 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAO6qAnt047245; Tue, 23 Nov 2004 23:52:10 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 23 Nov 2004 23:52:50 -0700 (MST) Message-Id: <20041123.235250.118899687.imp@bsdimp.com> To: cswiger@mac.com From: "M. Warner Losh" In-Reply-To: <41A416E7.4030107@mac.com> References: <200411231343.22760.jhb@FreeBSD.org> <20041124002603.GD20881@squash.dsto.defence.gov.au> <41A416E7.4030107@mac.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: alex.wilkinson@dsto.defence.gov.au Subject: Re: Transparent bridges (a. k. a. HUB-to-PCI bridges)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 06:54:39 -0000 In message: <41A416E7.4030107@mac.com> Chuck Swiger writes: : > Can you please elaborate on the following .... please ;-\ : > : > 1. PCI bridges : > - Host-PCI : > - PCI-PCI : : A host-PCI bridge is typically part of the "southbridge" chip of modern : motherboards; on Intel motherboards this is also called the ICH chip, such as : the 82801AA/BA/CA/etc. VIA Southbridges include the VT8233/8235/8237/etc. : : A PCI-PCI bridge is commonly found on multifunction PCI cards, an example : would be the DEC 21151 chip found on various four-port NICs. Newer laptops (and other machines) typically have a PCI PCI bridge that all the builtin hardware lives behind. Many, but not all, of these bridges are transparent pci pci bridges, maning they act much like a subtractively decoded bridge. Warner From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 07:04:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85E9016A4D0 for ; Wed, 24 Nov 2004 07:04:28 +0000 (GMT) Received: from web14108.mail.yahoo.com (web14108.mail.yahoo.com [216.136.172.138]) by mx1.FreeBSD.org (Postfix) with SMTP id 1157F43D69 for ; Wed, 24 Nov 2004 07:04:28 +0000 (GMT) (envelope-from cguttesen@yahoo.dk) Received: (qmail 5140 invoked by uid 60001); 24 Nov 2004 07:04:27 -0000 Message-ID: <20041124070427.5138.qmail@web14108.mail.yahoo.com> Received: from [194.248.174.50] by web14108.mail.yahoo.com via HTTP; Wed, 24 Nov 2004 08:04:27 CET Date: Wed, 24 Nov 2004 08:04:27 +0100 (CET) From: Claus Guttesen To: Ganbold , Robert Watson In-Reply-To: <6.2.0.14.2.20041124091640.03064eb0@202.179.0.80> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: tomaz.borstnar@over.net cc: cguttesen@yahoo.dk cc: scottl@freebsd.org cc: mhunter@ack.Berkeley.EDU cc: freebsd-current@freebsd.org Subject: Re: Page fault in FreeBSD 5.3 on IBM e325, Dual AMD64 2.2GHz, 4GB RAM, ServeRAID 6M - problem goes away without TCP sack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 07:04:28 -0000 > I turned off TCP sack using > net.inet.tcp.sack.enable=0 in sysctl.conf and > it seems like the problem goes away. > It is working for more than 20 hours without any > crash. Does it also work without hw.physmem in /boot/loader.conf? Claus From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 07:16:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3349516A4CE for ; Wed, 24 Nov 2004 07:16:10 +0000 (GMT) Received: from S4.cableone.net (smtp4.cableone.net [24.116.0.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9600B43D5A for ; Wed, 24 Nov 2004 07:16:09 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from vixen42.24-119-122-191.cpe.cableone.net (unverified [24.119.122.25]) by S4.cableone.net (CableOne SMTP Service S4) with ESMTP id 2242145 for ; Wed, 24 Nov 2004 00:19:30 -0700 Date: Wed, 24 Nov 2004 01:14:52 -0600 From: Vulpes Velox To: freebsd-current@freebsd.org Message-ID: <20041124011452.039741bc@vixen42.24-119-122-191.cpe.cableone.net> X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Abuse-Info: Send abuse complaints to abuse@cableone.net Subject: interrupt storm and atapicam X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 07:16:10 -0000 Just got around to adding a DVD+RW drive to my machine today. I went to add atapicam to the system. When I recompiled the kernel and rebooted I got an error about a interrupt storm on atapci1 and it freezes. dmesg... Copyright (c) 1992-2004 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 5.3-STABLE #1: Wed Nov 24 00:16:44 CST 2004 root@vixen42:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) XP 2000+ (1750.01-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x680 Stepping = 0 Features=0x383f9ff AMD Features=0xc0400000 real memory = 1073676288 (1023 MB) avail memory = 1041117184 (992 MB) ACPI-0277: *** Warning: Invalid checksum in table [FACP] (4e, sum a5 is not zero) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 atapci0: Correcting VIA config for southbridge data corruption bug ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: port 0xb800-0xb81f irq 5 at device 7.2 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered umass0: Eastman Kodak Kodak 6 in 1 Card Reader, rev 2.00/1.25, addr 2 uhci1: port 0xbc00-0xbc1f irq 5 at device 7.3 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at device 7.4 (no driver attached) pci0: at device 7.5 (no driver attached) pci0: at device 10.0 (no driver attached) dc0: port 0xb400-0xb4ff mem 0xdfffbc00-0xdfffbfff irq 11 at device 12.0 on pci0 miibus0: on dc0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:04:5a:7a:1f:b5 dc0: if_start running deferred for Giant dc0: [GIANT-LOCKED] atapci1: port 0xcc00-0xcc0f,0xd000-0xd003,0xd400-0xd407,0xd800-0xd803,0xdc00-0xdc07 mem 0xdfffc000-0xdfffffff irq 10 at device 13.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 ahc0: port 0xb000-0xb0ff mem 0xdfffa000-0xdfffafff irq 5 at device 15.0 on pci0 ahc0: [GIANT-LOCKED] aic7860: Ultra Single Channel A, SCSI Id=7, 3/253 SCBs acpi_button1: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xc0000-0xca7ff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1750011192 Hz quality 800 Timecounters tick every 10.000 msec ahc0: Someone reset channel A acpi_cpu: throttling enabled, 16 steps (100% to 6.2%), currently 100.0% ad0: 78167MB [158816/16/63] at ata0-master UDMA100 ad1: 38166MB [77545/16/63] at ata0-slave UDMA100 ad2: 95396MB [193821/16/63] at ata1-master UDMA100 ad3: 156334MB [317632/16/63] at ata1-slave UDMA100 acd0: DVDR at ata2-master UDMA33 acd1: CDRW at ata2-slave UDMA100 Waiting 15 seconds for SCSI devices to settle cd0 at ahc0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.032MB/s transfers (4.032MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ahc0 bus 0 target 1 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 5.000MB/s transfers (5.000MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present cd2 at ahc0 bus 0 target 2 lun 0 cd2: Removable CD-ROM SCSI-2 device cd2: 3.300MB/s transfers cd2: Attempt to query device size failed: NOT READY, Medium not present From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 07:36:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE32A16A4CE; Wed, 24 Nov 2004 07:36:22 +0000 (GMT) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A36043D45; Wed, 24 Nov 2004 07:36:22 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.43 (FreeBSD)) id 1CWrhj-0004ln-U1; Wed, 24 Nov 2004 15:36:44 +0800 Message-Id: <6.2.0.14.2.20041124153300.0306f070@202.179.0.80> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Wed, 24 Nov 2004 15:36:11 +0800 To: Claus Guttesen From: Ganbold In-Reply-To: <20041124070427.5138.qmail@web14108.mail.yahoo.com> References: <6.2.0.14.2.20041124091640.03064eb0@202.179.0.80> <20041124070427.5138.qmail@web14108.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: tomaz.borstnar@over.net cc: freebsd-current@freebsd.org cc: scottl@freebsd.org cc: mhunter@ack.Berkeley.EDU cc: rwatson@freebsd.org Subject: Re: Page fault in FreeBSD 5.3 on IBM e325, Dual AMD64 2.2GHz, 4GB RAM, ServeRAID 6M - problem goes away without TCP sack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 07:36:23 -0000 At 03:04 PM 11/24/2004, you wrote: > > I turned off TCP sack using > > net.inet.tcp.sack.enable=0 in sysctl.conf and > > it seems like the problem goes away. > > It is working for more than 20 hours without any > > crash. > >Does it also work without hw.physmem in >/boot/loader.conf? I don't any hw.physmem settings in /boot/loader.conf and it still works fine with 4GB RAM. Ganbold >Claus > >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 07:45:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D76FA16A4CF for ; Wed, 24 Nov 2004 07:45:27 +0000 (GMT) Received: from web14125.mail.yahoo.com (web14125.mail.yahoo.com [66.163.171.116]) by mx1.FreeBSD.org (Postfix) with SMTP id 8B38143D5F for ; Wed, 24 Nov 2004 07:45:27 +0000 (GMT) (envelope-from cguttesen@yahoo.dk) Received: (qmail 90987 invoked by uid 60001); 24 Nov 2004 07:45:27 -0000 Message-ID: <20041124074527.90985.qmail@web14125.mail.yahoo.com> Received: from [194.248.174.50] by web14125.mail.yahoo.com via HTTP; Wed, 24 Nov 2004 08:45:27 CET Date: Wed, 24 Nov 2004 08:45:27 +0100 (CET) From: Claus Guttesen To: Ganbold In-Reply-To: <6.2.0.14.2.20041124153300.0306f070@202.179.0.80> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: tomaz.borstnar@over.net cc: freebsd-current@freebsd.org cc: scottl@freebsd.org cc: mhunter@ack.Berkeley.EDU cc: rwatson@freebsd.org Subject: Re: Page fault in FreeBSD 5.3 on IBM e325, Dual AMD64 2.2GHz, 4GB RAM, ServeRAID 6M - problem goes away without TCP sack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 07:45:28 -0000 > >Does it also work without hw.physmem in > >/boot/loader.conf? > > I don't any hw.physmem settings in /boot/loader.conf > and it still works > fine with 4GB RAM. I wonder if the change you performed to the IBM e325 also applies to my Dell PE 2850 with 4 GB RAM, eventhough it's a different controller? Thank you. Claus From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 08:31:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B715216A4CE; Wed, 24 Nov 2004 08:31:42 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15AA543D2F; Wed, 24 Nov 2004 08:31:42 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAO8Vfu8061212; Wed, 24 Nov 2004 09:31:41 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Baldwin From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 22 Nov 2004 16:57:36 EST." <200411221657.36659.jhb@FreeBSD.org> Date: Wed, 24 Nov 2004 09:31:40 +0100 Message-ID: <61211.1101285100@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@FreeBSD.org Subject: Re: panic: sleeping thread owns a non-sleepable lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 08:31:42 -0000 In message <200411221657.36659.jhb@FreeBSD.org>, John Baldwin writes: >On Monday 22 November 2004 09:38 am, Peter Holm wrote: >> During stress test with GENERIC HEAD from Nov 20 08:40 UTC I got: >> Sleeping on "fdesc" with the following non-sleepable locks held: >> exclusive sleep mutex fdesc r = 0 (0xc08d15a0) locked @ >> kern/kern_descrip.c:2425 and then >> panic: sleeping thread (pid 92279) owns a non-sleepable lock >> >> http://www.holm.cc/stress/log/cons89.html > >Yes, the panic is a result of the earlier warning. Poul-Henning touched this >code last, so it is probably something for him to look at. I'm unsure how >msleep() is getting called, however. The turnstile panic is not important, >can you find the thread that went to sleep (should be pid 92279) and get >stack trace for that? There is a patch for this in perforce phk_bufwork::sys/kern/kern_descrip.c now. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 08:40:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 192F516A4CE; Wed, 24 Nov 2004 08:40:54 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6122943D2F; Wed, 24 Nov 2004 08:40:53 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAO8enU5061436; Wed, 24 Nov 2004 09:40:51 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Peter Jeremy From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 22 Nov 2004 18:31:32 +1100." <20041122073132.GW79646@cirb503493.alcatel.com.au> Date: Wed, 24 Nov 2004 09:40:49 +0100 Message-ID: <61435.1101285649@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: arch@freebsd.org cc: current@freebsd.org Subject: Re: [REVIEW/TEST] nanodelay() vs DELAY() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 08:40:54 -0000 In message <20041122073132.GW79646@cirb503493.alcatel.com.au>, Peter Jeremy wri tes: >The fact that this doesn't show up in the graph suggests that you're >not using tc_nanodelay() at all within the 0..8usec range. Right, but I can't trust that to be the case as CPUs get faster. Originally I considered having MD routines registered also, stuff like doing an "inb()" on i386 etc. As it transpired the exponential nature of the nanodelay_loopcall2() function makes this unnecessary. >Your graph suggests that it's fairly good above about 200nsec even on >equipment that is not blazingly fast. Don't let the log-log scale deceive you. being 50% wrong doesn't look like much. >Have you looked at the granularity of tc_nanodelay() (and the likely >granularity required by callers)? Is 8nsec reasonable given the >inner loop of of tc_nanodelay()? I'm actually considering making it 32nsec based on a 33MHz PCI speed. >Do you have any idea where the transition points between the various >delay functions are? If you boot -v it will tell you. >>The array takes up 9000 bytes on 32 bit and 17000 on 64 bit. > >AFAIK, all the FreeBSD architectures have 32-bit ints, so that should >be 13,000 bytes for 64bit architectures. Still, that's an awful lot for an old ass'y programmer like me :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 10:30:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A29716A4CE for ; Wed, 24 Nov 2004 10:30:31 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E80943D58 for ; Wed, 24 Nov 2004 10:30:31 +0000 (GMT) (envelope-from zhedou@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so58350rnf for ; Wed, 24 Nov 2004 02:30:30 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=mAseMJRDcahRSgLEHiGznpXhIc82H6efw+4UyqmofL2vN0W/6LYXZBoRrA/uEq5tScebTVKyyc0Z9E70w/TaTR/F5g3US/Vlv5tc7/maaGVWvJxpiQoJSZrUSJuMr+JdOxlv12U8B4IhfWkQoeayzw9DnCTFTaBPyY22/ZP0Etc= Received: by 10.38.150.9 with SMTP id x9mr280198rnd; Wed, 24 Nov 2004 02:30:30 -0800 (PST) Received: by 10.38.99.56 with HTTP; Wed, 24 Nov 2004 02:30:30 -0800 (PST) Message-ID: <641911240411240230e2fd4ea@mail.gmail.com> Date: Wed, 24 Nov 2004 18:30:30 +0800 From: zhe dou To: freebsd-current@freebsd.org In-Reply-To: <641911240411240203fc3391f@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <64191124041121193463af35a@mail.gmail.com> <641911240411240203fc3391f@mail.gmail.com> Subject: Re: how to build duplex.iso? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: zhe dou List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 10:30:31 -0000 could you explain more about how to do it? i tried before but failure. Thanks On Wed, 24 Nov 2004 18:03:39 +0800, zhe dou wrote: > could you explain more about how to do it? i tried before but failure. Thanks > > > > > On Tue, 23 Nov 2004 00:12:08 +0900, Makoto Matsushita > wrote: > > > > > > > > > May i want to know how to make a cd_rom installation disk ISO image > > > included both 4.10 and 5.3 in one disk like the FreeBSD/i386 duplex > > > installation CD-ROM (about 550MB) disk in http://current.freebsd.org/. > > > > It's simple: include both distributions in one CD-ROM, and select > > which kernel to boot via loader(8). > > > > -- > > Makoto `MAR' MATSUSHITA > > > From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 10:36:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8468916A4CE for ; Wed, 24 Nov 2004 10:36:16 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2188343D45 for ; Wed, 24 Nov 2004 10:36:16 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id 88187ACAEE; Wed, 24 Nov 2004 11:36:13 +0100 (CET) Date: Wed, 24 Nov 2004 11:36:13 +0100 From: Pawel Jakub Dawidek To: Ivan Voras Message-ID: <20041124103613.GL7232@darkness.comp.waw.pl> References: <41A2488F.8030802@fer.hr> <20041122215228.J568@korben.in.tern> <41A33907.5020703@fer.hr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="31zvzas5NXT9fief" Content-Disposition: inline In-Reply-To: <41A33907.5020703@fer.hr> User-Agent: Mutt/1.4.2i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 5.2.1-RC2 i386 cc: current@freebsd.org Subject: Re: gvinum panic? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 10:36:16 -0000 --31zvzas5NXT9fief Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 23, 2004 at 02:20:07PM +0100, Ivan Voras wrote: +> Lukas Ertl wrote: +> >On Mon, 22 Nov 2004, Ivan Voras wrote: +> > +> >>I'm consistently getting a system panic, trap #12 in process g_event= =20 +> >>when I try: +> > +> > +> >Are you sure that kernel (modules) and userland are in sync? +>=20 +> Thanks, it looks like they've been unsynced for a while :( +> It's ok now. +>=20 +> But, the performance is pretty bad (same with regular vinum). I tried=20 +> setting up graid3 class with same parameters, and got these results: +>=20 +> linear read (1024 MB file, blocks of 32768) ................. 38.5 MB/s +> linear write (1024 MB file, blocks of 32768) ................ 16.8 MB/s +> random read (1024 MB file, blocks of 32768) ................. 41.9 MB/s +> random write (1024 MB file, blocks of 32768) ................ 3.4 MB/s Do you use parity component for reading? If no, you can try it (add '-r' option while configuring your raid3 device), it should speed up random reads a lot. --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --31zvzas5NXT9fief Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBpGQdForvXbEpPzQRAuwBAJ9gvBOjIigq0vokvB0PLgkWOj1OvQCcDQTX F+iCmSAx8S9+97dlDt6bOFo= =4d+i -----END PGP SIGNATURE----- --31zvzas5NXT9fief-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 11:14:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D15A16A4CE; Wed, 24 Nov 2004 11:14:44 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB8F143D31; Wed, 24 Nov 2004 11:14:43 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAOBCtfY012136; Wed, 24 Nov 2004 06:12:55 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iAOBCr8a012131; Wed, 24 Nov 2004 11:12:54 GMT (envelope-from robert@fledge.watson.org) Date: Wed, 24 Nov 2004 11:12:53 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Ganbold In-Reply-To: <6.2.0.14.2.20041124091640.03064eb0@202.179.0.80> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: tomaz.borstnar@over.net cc: cguttesen@yahoo.dk cc: scottl@freebsd.org cc: mhunter@ack.Berkeley.EDU cc: freebsd-current@freebsd.org Subject: Re: Page fault in FreeBSD 5.3 on IBM e325, Dual AMD64 2.2GHz, 4GB RAM, ServeRAID 6M - problem goes away without TCP sack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 11:14:44 -0000 On Wed, 24 Nov 2004, Ganbold wrote: > At 06:43 PM 11/22/2004, you wrote: > > > > > > > It seems to me the problem is related to network stack and threading. > > > Am I right? How to solve this problem? > > > >I've seen reports of this problem with and without debug.mpsafenet=1, > >which suggests it is a network stack bug but not specific to locking. I've > >also seen reports that disabling TCP SACK will make the problem go away, > >which would be good to confirm. I spent the weekend building up some more > >expertise in TCP and reading a lot of TCP code, and hope to look at this > >problem in more detail today. You may want to try turning off TCP sack > >using net.inet.tcp.sack.enable=0 in sysctl.conf (or loader.conf). > > I turned off TCP sack using net.inet.tcp.sack.enable=0 in sysctl.conf > and it seems like the problem goes away. It is working for more than 20 > hours without any crash. Robert, did you find anything in network stack > code? I'm just curious. I have not yet identified a (the?) bug, although it seems likely that it has to do with the internal TCP state relating to the SACK blocks. What we need right now, I think, is a core dump, preferably on an i386 kernel since our debugging tools work best with that. My recollection, though, is that you're using an amd64 kernel, but there have been reports from others that likely are on i386. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 11:32:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE39D16A4CE for ; Wed, 24 Nov 2004 11:32:29 +0000 (GMT) Received: from lara.cc.fer.hr (lara.cc.fer.hr [161.53.72.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2295F43D49 for ; Wed, 24 Nov 2004 11:32:29 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [127.0.0.1] (localhost.cc.fer.hr [127.0.0.1]) by lara.cc.fer.hr (8.13.1/8.13.1) with ESMTP id iAOBWNOf017593 for ; Wed, 24 Nov 2004 12:32:23 +0100 (CET) (envelope-from ivoras@fer.hr) Message-ID: <41A47147.7040403@fer.hr> Date: Wed, 24 Nov 2004 12:32:23 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 0.9 (X11/20041111) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org References: <41A2488F.8030802@fer.hr> <20041122215228.J568@korben.in.tern> <41A33907.5020703@fer.hr> <20041124103613.GL7232@darkness.comp.waw.pl> In-Reply-To: <20041124103613.GL7232@darkness.comp.waw.pl> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: gvinum panic? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 11:32:30 -0000 Pawel Jakub Dawidek wrote: > +> linear read (1024 MB file, blocks of 32768) ................. 38.5 MB/s > +> linear write (1024 MB file, blocks of 32768) ................ 16.8 MB/s > +> random read (1024 MB file, blocks of 32768) ................. 41.9 MB/s > +> random write (1024 MB file, blocks of 32768) ................ 3.4 MB/s > In the interests of archives, I must say that the "random read" score above is WRONG. I was surprised myself because it's RAID3, so I rerun the test. Here are the correct numbers: linear read (2048 MB file, blocks of 32768) ................. 40.3 MB/s linear write (2048 MB file, blocks of 32768) ................ 16.8 MB/s random read (2048 MB file, blocks of 32768) ................. 5.1 MB/s random write (2048 MB file, blocks of 32768) ................ 2.9 MB/s (previously, most of the file has fitted into cache) > Do you use parity component for reading? If no, you can try it (add '-r' > option while configuring your raid3 device), it should speed up random > reads a lot. My situation is that there are 3 discs on 2 IDE channels, so two are in master-slave relationship. I've put the parity drive on the slave disc, and without -r it doesn't ever get touched (which speeds up the requests) The tests confirm this was right: (with round-robin/parity reads:) linear read (2048 MB file, blocks of 32768) ................. 32.6 MB/s linear write (2048 MB file, blocks of 32768) ................ 16.8 MB/s random read (2048 MB file, blocks of 32768) ................. 4.0 MB/s random write (2048 MB file, blocks of 32768) ................ 3.1 MB/s From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 11:49:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 366BD16A4CE; Wed, 24 Nov 2004 11:49:12 +0000 (GMT) Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8358B43D55; Wed, 24 Nov 2004 11:49:11 +0000 (GMT) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: from localhost (localhost [127.0.0.1])84DEF499E7; Wed, 24 Nov 2004 12:49:10 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 14921-04; Wed, 24 Nov 2004 12:49:10 +0100 (CET) Received: from m2a2.dyndns.org (p548546B7.dip.t-dialin.net [84.133.70.183]) B8EED498E5; Wed, 24 Nov 2004 12:49:09 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 122B8D3F13; Wed, 24 Nov 2004 12:49:09 +0100 (CET) Received: from merlin.emma.line.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 17611-02; Wed, 24 Nov 2004 12:49:08 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id 5789DCDA72; Wed, 24 Nov 2004 12:49:08 +0100 (CET) To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Mail-Followup-To: freebsd-stable@freebsd.org User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) From: Matthias Andree Date: Wed, 24 Nov 2004 12:49:08 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at dt.e-technik.uni-dortmund.de Subject: 5-STABLE softupdates issue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-stable@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 11:49:12 -0000 Greetings, out of fun and to investigate claims about alleged bgfsck resource hogging (which I could not reproduce) posted to news:de.comp.os.unix.bsd, I pressed the reset button on a live FreeBSD 5-STABLE system. Upon reboot, fsck -p complained about an unexpected softupdates inconsistency on the / file system and put me into single user mode, the manual fsck / then asked me to agree to increasing a link count from 21 to 22 (and later to fix the summary, which I consider a non-issue). A subsequent fsck -p / ended with no abnormality detected. Unfortunately, I haven't copied the details, assuming they would be copied into the log, but they haven't. Is this a situation the current 5-STABLE softupdates code (on a UFS1 FS that I kept from FreeBSD 4) is allowed to cause? Is that a bug in the file system, say, write ordering goofed up? Or is that a bug in the firmware of my disk drive (Western Digital Caviar AC420400D, a rebranded IBM DJNA drive)? I gather that ATA drives are supposed to flush their caches on software (command) and hardware resets (reset line active). I did not power cycle. -- Matthias Andree From owner-freebsd-current@FreeBSD.ORG Tue Nov 23 18:23:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A35A516A4CE for ; Tue, 23 Nov 2004 18:23:21 +0000 (GMT) Received: from united.networks.org (united.networks.org [209.209.49.209]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D57A43D31 for ; Tue, 23 Nov 2004 18:23:21 +0000 (GMT) (envelope-from hogan@ninthgate.net) Received: by united.networks.org (Postfix, from userid 101) id C84D0B744; Tue, 23 Nov 2004 10:22:54 -0800 (PST) Date: Tue, 23 Nov 2004 11:22:54 -0700 From: Hogan Whittall To: freebsd-current@freebsd.org Message-ID: <20041123182254.GB10721@ninthgate.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Header: It's a Jeep thing, you wouldn't understand... X-Mailman-Approved-At: Wed, 24 Nov 2004 13:10:29 +0000 Subject: Random panics with 5.3-REL, SMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: hogan@ninthgate.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 18:23:21 -0000 Hi all, I've been running 5.3-REL for a couple of weeks now and have run into various problems with panics. Initially I had a wireless card that wasn't supported natively, so I made use of the NDIS wrapper. This worked "ok" but was buggy and the card/driver would stop talking on the WLAN randomly, fix was to bounce the interface and it worked fine for a while longer. At one point downing the interface caused a panic, so I swapped out the wireless card with one supported natively. Works like a charm...at least wireless does. I'm still getting random panics, however. Doesn't appear to be related to anything in particular and seems to usually happen after being up for 1-2 days. I've attempted to get a coredump but the last panic wedged while dumping to disk. I'm going to be out of town for a week and won't have access to the box, but if anyone has experienced something like this before and knows of a fix, please let me know. Here are the specs of the machine: Dell PE6450 server, 4xP3-700 Xeon, 4gb ram, system disks reside on a 2 disk RAID1 attached to a MegaRAID controller. Wireless is a D-Link DWL-G520-B, also has Intel Pro/100 ethernet. Large storage is fiber-connected Clariion FC5700 via two QLA2200-C 64-bit PCI cards. Also attached via AIC-7899 controller is a DDS3 tape backup. Any hints or suggestions would be greatly appreciated, I can test and give the results when I get back from Thanksgiving vacation. -- H. Whittall hogan@ninthgate.net From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 13:56:14 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FC1216A4CE for ; Wed, 24 Nov 2004 13:56:14 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id B165943D3F for ; Wed, 24 Nov 2004 13:56:13 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAODwu9p063275; Wed, 24 Nov 2004 06:58:56 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41A49312.5@freebsd.org> Date: Wed, 24 Nov 2004 06:56:34 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chuck Swiger References: <200411231226.38172.jkim@niksun.com> <200411231343.22760.jhb@FreeBSD.org> <20041124002603.GD20881@squash.dsto.defence.gov.au> <41A416E7.4030107@mac.com> In-Reply-To: <41A416E7.4030107@mac.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org cc: "Wilkinson, Alex" Subject: Re: Transparent bridges (a. k. a. HUB-to-PCI bridges)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 13:56:14 -0000 Chuck Swiger wrote: > Wilkinson, Alex wrote: > >> Trying to understand your nomenclature John, so that I can follow this >> thread. > > > I'm no John Kennedy, nor even John Baldwin, but I'll give this a shot. :-) > >> Can you please elaborate on the following .... please ;-\ >> >> 1. PCI bridges - Host-PCI >> - PCI-PCI > > > A host-PCI bridge is typically part of the "southbridge" chip of modern > motherboards; on Intel motherboards this is also called the ICH chip, > such as the 82801AA/BA/CA/etc. VIA Southbridges include the > VT8233/8235/8237/etc. Nope. The southbridge typically holds a PCI-ISA bridge. The host-pci bridge is usually found in the northbridge part of the chipset. The whole point it to bridge the CPU to one or more PCI buses. > > A PCI-PCI bridge is commonly found on multifunction PCI cards, an > example would be the DEC 21151 chip found on various four-port NICs. PCI-PCI bridges are also quite common on motherboards, especially with PCI-X. > >> 2. OOPish device object (device_t) ? > > > True OOP involves encapsulation, polymorphism, and inheritence, and > requires language support which is not really available in pure C. That > being said, careful programming in C lets you create several > closely-related structs for different types of "objects" which can all > be utilized by a common set of functions. > > The most common example of this would probably be the > protocol-independent struct sockaddr, which can handle IPv4, IPv6, and > other types of network address formats using a common structure (or a > related group of structures, depending on how you want to look at it). > See "man getaddrinfo". The particular reference to device_t refers to it's ability to have limited inheritence of methods from it's parent 'class'. > >> 3. $PIR table > > > Stands for PCI Interrupt Routing table. When your computer boots, the > BIOS is responsible for configuring at least the devices required to > boot such that they and the BIOS agree as to which IRQ each device ought > to use. > > Blah, I couldn't find a good link outside of Microsoft, but see here: > > http://www.microsoft.com/whdc/archive/pciirq.mspx > Scott From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 14:01:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AED916A4CE; Wed, 24 Nov 2004 14:01:25 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8E6043D58; Wed, 24 Nov 2004 14:01:24 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAOE4Aiv063294; Wed, 24 Nov 2004 07:04:11 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41A4944C.6030808@freebsd.org> Date: Wed, 24 Nov 2004 07:01:48 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: In-Reply-To: X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org Subject: Re: 5-STABLE softupdates issue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 14:01:25 -0000 Matthias Andree wrote: > Greetings, > > out of fun and to investigate claims about alleged bgfsck resource > hogging (which I could not reproduce) posted to > news:de.comp.os.unix.bsd, I pressed the reset button on a live FreeBSD > 5-STABLE system. > > Upon reboot, fsck -p complained about an unexpected softupdates > inconsistency on the / file system and put me into single user mode, the > manual fsck / then asked me to agree to increasing a link count from 21 > to 22 (and later to fix the summary, which I consider a non-issue). A > subsequent fsck -p / ended with no abnormality detected. > > Unfortunately, I haven't copied the details, assuming they would be > copied into the log, but they haven't. > > Is this a situation the current 5-STABLE softupdates code (on a UFS1 FS > that I kept from FreeBSD 4) is allowed to cause? > > Is that a bug in the file system, say, write ordering goofed up? > > Or is that a bug in the firmware of my disk drive (Western Digital > Caviar AC420400D, a rebranded IBM DJNA drive)? I gather that ATA drives > are supposed to flush their caches on software (command) and hardware > resets (reset line active). > > I did not power cycle. > No, this in theory should not happen. YOu could have caught it right at the instance that it was sending a transaction out to disk, or you could have caught an edge case that isn't understood yet. Unfortunately, ATA drives also cannot be trusted to flush their caches when one would expect, so this leaves open a lot of possible causes for your problem. Scott From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 14:28:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2614216A4CE for ; Wed, 24 Nov 2004 14:28:58 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A35143D1F for ; Wed, 24 Nov 2004 14:28:57 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.250] (pool-68-161-115-118.ny325.east.verizon.net [68.161.115.118]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id iAOESbhC014573 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Nov 2004 09:28:39 -0500 (EST) Message-ID: <41A49A7B.6020009@mac.com> Date: Wed, 24 Nov 2004 09:28:11 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <200411231343.22760.jhb@FreeBSD.org> <20041124002603.GD20881@squash.dsto.defence.gov.au> <41A416E7.4030107@mac.com> <20041123.235250.118899687.imp@bsdimp.com> In-Reply-To: <20041123.235250.118899687.imp@bsdimp.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-4.5 required=5.5 tests=AWL,BAYES_00 autolearn=ham version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on pi.codefab.com cc: freebsd-current@freebsd.org Subject: Re: Transparent bridges (a. k. a. HUB-to-PCI bridges)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 14:28:58 -0000 M. Warner Losh wrote: > In message: <41A416E7.4030107@mac.com> > Chuck Swiger writes: [ ... ] > : A host-PCI bridge is typically part of the "southbridge" chip of modern > : motherboards; on Intel motherboards this is also called the ICH chip, such as > : the 82801AA/BA/CA/etc. VIA Southbridges include the VT8233/8235/8237/etc. > : > : A PCI-PCI bridge is commonly found on multifunction PCI cards, an example > : would be the DEC 21151 chip found on various four-port NICs. > > Newer laptops (and other machines) typically have a PCI PCI bridge > that all the builtin hardware lives behind. Many, but not all, of > these bridges are transparent pci pci bridges, maning they act much > like a subtractively decoded bridge. You are absolutely right; the impression I got was that laptops like to have PCI-PCI bridges in order to make it easier to route interrupts for devices on a docking station or the like. If they don't use such a PCI-PCI bridge chip, then the laptop's BIOS needs to set up a $PIR table which routes interrupts properly for _all_ of the possible docking station configurations and devices to which the laptop might be attached to. Making things work right with a known configuration seems to be hard enough for some vendors, so it's not surprising that pre-planning for possible future configurations is difficult to do without using a PCI-PCI bridge to aggregate the devices lurking behind it. -- -Chuck From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 14:40:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 414AE16A4CE; Wed, 24 Nov 2004 14:40:42 +0000 (GMT) Received: from mail.dt.e-technik.uni-dortmund.de (mail.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63EA143D4C; Wed, 24 Nov 2004 14:40:41 +0000 (GMT) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: from localhost (localhost [127.0.0.1])6B7A849C84; Wed, 24 Nov 2004 15:40:40 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 22608-05-2; Wed, 24 Nov 2004 15:40:39 +0100 (CET) Received: from m2a2.dyndns.org (p548546B7.dip.t-dialin.net [84.133.70.183]) A99F249B17; Wed, 24 Nov 2004 15:40:39 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 55F02D5769; Wed, 24 Nov 2004 15:40:38 +0100 (CET) Received: from merlin.emma.line.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 24215-07-4; Wed, 24 Nov 2004 15:40:37 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id 8B86FD5750; Wed, 24 Nov 2004 15:40:37 +0100 (CET) To: Scott Long In-Reply-To: <41A4944C.6030808@freebsd.org> (Scott Long's message of "Wed, 24 Nov 2004 07:01:48 -0700") References: <41A4944C.6030808@freebsd.org> From: Matthias Andree Date: Wed, 24 Nov 2004 15:40:37 +0100 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at dt.e-technik.uni-dortmund.de cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: 5-STABLE softupdates issue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 14:40:42 -0000 Scott Long writes: > No, this in theory should not happen. YOu could have caught it right at > the instance that it was sending a transaction out to disk, or you could > have caught an edge case that isn't understood yet. Unfortunately, ATA > drives also cannot be trusted to flush their caches when one would > expect, so this leaves open a lot of possible causes for your problem. That's why I added that question about drive cache flushing. I'll see to running with forced hw.ata.wc="0" and see if I can reproduce that problem. May be a while while before I see the problem again, these are very scarce fortunately (actually, the first SOFTDEP issue on this machine at all). OTOH, this is an IBM desktop drive in disguise, so the blatant firmware errors should be known by now. -- Matthias Andree From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 14:47:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E017E16A4CF; Wed, 24 Nov 2004 14:47:44 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6453243D45; Wed, 24 Nov 2004 14:47:44 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.250] (pool-68-161-115-118.ny325.east.verizon.net [68.161.115.118]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id iAOElcIL026980 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Nov 2004 09:47:40 -0500 (EST) Message-ID: <41A49EF1.8030603@mac.com> Date: Wed, 24 Nov 2004 09:47:13 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <200411231226.38172.jkim@niksun.com> <200411231343.22760.jhb@FreeBSD.org> <20041124002603.GD20881@squash.dsto.defence.gov.au> <41A416E7.4030107@mac.com> <41A49312.5@freebsd.org> In-Reply-To: <41A49312.5@freebsd.org> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-4.5 required=5.5 tests=AWL,BAYES_00 autolearn=ham version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on pi.codefab.com cc: freebsd-current@freebsd.org Subject: Re: Transparent bridges (a. k. a. HUB-to-PCI bridges)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 14:47:45 -0000 Scott Long wrote: > Chuck Swiger wrote: [ ... ] >> A host-PCI bridge is typically part of the "southbridge" chip of >> modern motherboards; on Intel motherboards this is also called the ICH >> chip, such as the 82801AA/BA/CA/etc. VIA Southbridges include the >> VT8233/8235/8237/etc. > > Nope. The southbridge typically holds a PCI-ISA bridge. The host-pci > bridge is usually found in the northbridge part of the chipset. The > whole point it to bridge the CPU to one or more PCI buses. I've been wrong before, but please double-check diagrams like: http://www.intel.com/design/chipsets/850/pix/850_800.gif http://www.viatech.com/en/products/chipsets/p4-series/pt880/ The "northbridge", or MCH, connects to the CPU, AGP, RAM, and the southbridge. The "southbridge", or ICH, connects to PCI, ATA, USB, BIOS chip, and the northbridge. Newer southbridge chips may add integrated LAN, 1394/Firewire, integrated AC'97 audio, and such via external codec chips like the VT6103 PHY. -- -Chuck From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 15:25:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47B3116A4CE for ; Wed, 24 Nov 2004 15:25:01 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9BD543D45 for ; Wed, 24 Nov 2004 15:25:00 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAOFLdg4055866; Wed, 24 Nov 2004 08:21:39 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 24 Nov 2004 08:22:20 -0700 (MST) Message-Id: <20041124.082220.29053157.imp@bsdimp.com> To: cswiger@mac.com From: "M. Warner Losh" In-Reply-To: <41A49A7B.6020009@mac.com> References: <41A416E7.4030107@mac.com> <20041123.235250.118899687.imp@bsdimp.com> <41A49A7B.6020009@mac.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Transparent bridges (a. k. a. HUB-to-PCI bridges)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 15:25:01 -0000 In message: <41A49A7B.6020009@mac.com> Chuck Swiger writes: : M. Warner Losh wrote: : > In message: <41A416E7.4030107@mac.com> : > Chuck Swiger writes: : [ ... ] : > : A host-PCI bridge is typically part of the "southbridge" chip of modern : > : motherboards; on Intel motherboards this is also called the ICH chip, such as : > : the 82801AA/BA/CA/etc. VIA Southbridges include the VT8233/8235/8237/etc. : > : : > : A PCI-PCI bridge is commonly found on multifunction PCI cards, an example : > : would be the DEC 21151 chip found on various four-port NICs. : > : > Newer laptops (and other machines) typically have a PCI PCI bridge : > that all the builtin hardware lives behind. Many, but not all, of : > these bridges are transparent pci pci bridges, maning they act much : > like a subtractively decoded bridge. : : You are absolutely right; the impression I got was that laptops like to have : PCI-PCI bridges in order to make it easier to route interrupts for devices on : a docking station or the like. If they don't use such a PCI-PCI bridge chip, : then the laptop's BIOS needs to set up a $PIR table which routes interrupts : properly for _all_ of the possible docking station configurations and devices : to which the laptop might be attached to. : : Making things work right with a known configuration seems to be hard enough : for some vendors, so it's not surprising that pre-planning for possible future : configurations is difficult to do without using a PCI-PCI bridge to aggregate : the devices lurking behind it. Having a pci-pci bridge is no guarantee that the interrupts will be routed correctly. Many laptops route them directly, even in the face of a pci-pci bridge. The $PIR will often lists devices behind the bridge. Warner From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 15:37:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDB5816A4CF for ; Wed, 24 Nov 2004 15:37:01 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A30743D49 for ; Wed, 24 Nov 2004 15:37:01 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAOFZC0F016875; Wed, 24 Nov 2004 10:35:12 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iAOFZCc9016872; Wed, 24 Nov 2004 15:35:12 GMT (envelope-from robert@fledge.watson.org) Date: Wed, 24 Nov 2004 15:35:11 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Hogan Whittall In-Reply-To: <20041123182254.GB10721@ninthgate.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Random panics with 5.3-REL, SMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 15:37:02 -0000 On Tue, 23 Nov 2004, Hogan Whittall wrote: > I'm still getting random panics, however. Doesn't appear to be related > to anything in particular and seems to usually happen after being up for > 1-2 days. I've attempted to get a coredump but the last panic wedged > while dumping to disk. I'm going to be out of town for a week and won't > have access to the box, but if anyone has experienced something like > this before and knows of a fix, please let me know. Here are the specs > of the machine: "Random panics" is a little vague as a starting point, but here are some thoughts to look at when back from your vacation: - Using a serial console to the box, you can reliably gather information without the core dump mechanism working. - "Random panics" could mean "A lot of seemingly different panics happening with relatively frequency", or it might mean "A few similar panics, happening at random intervals". It would be useful to clarify which it is. Recognizing that you may not be familiar with the intimate details of kernel failure modes, the ways in which one might classify failures as being "similar" is by the nature of the panic and the stack trace to reach the panic. Panics usually fall into two forms: an explicit call to panic() by code that has detected a failure of a kernel invariant ("this should never happen"), or a page fault ("the kernel touched some memory it shouldn't have"). Panics typically print a fault description, such as a pointer dereferenced, or the nature of the invariant test that triggered. The same message might indicate the same problem occuring. A stack trace can be generated using the "trace" command in DDB, and is a subset of the information you might get by pointing gdb at a core. If the stack traces look similar (especially with regard to the functions close to the frame where the panic took place), the failure mode might be regarded to be similar also. Regardless, when reporting panics, the panic line or header of the fault report are excellent starting points. - In terms of debugging information, it would be very useful if you could hook up a serial console, and when a panic occurs, send the output of "show pcpu" and "show trace". If an SMP box with an SMP kernel, run "show pcpu" for each cpu, and trace the active threads on each. The output of "ps" is usually pretty valuable, as it will show what the system was doing, and if many threads are waiting fore something, it will show what they are waiting for. With file system related panics or hangs, the output of "show lockedvnods" is often also very useful, as it will show what file system objects were being actively used, and by what threads. If running with WITNESS (see below), "show locks" can be very helpful, as it will assist in understanding and debugging the synchronization state of the kernel. - If a bug leads to an eventual panic, that problem caused by the bug will sometimes be better described if you have some of the kernel debugging kernel enabled. For example, INVARIANTS and/or WITNESS. Depending on the impact to performance you can take on the box, you might want to try some features, then others. Features like INVARIANTS may also help catch the problem earlier, making the problem easier to diagnose. I've found the single most useful tool in debugging failure modes is a serial console, as it provides ready scroll-back to earlier console output, a fairly reliable ability to enter the debugger using a break, as well as functionality like remote DDB, logging of DDB output, etc. I've heard people report very similar benefits and experiences with firewire debugging, but since I don't really live in the world of firewire, I'll point at serial ports :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 15:41:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC7B116A4CE for ; Wed, 24 Nov 2004 15:41:13 +0000 (GMT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67F1643D41 for ; Wed, 24 Nov 2004 15:41:13 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 24169 invoked from network); 24 Nov 2004 15:41:13 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 24 Nov 2004 15:41:12 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAOFf5WV043775; Wed, 24 Nov 2004 10:41:10 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Wed, 24 Nov 2004 10:19:25 -0500 User-Agent: KMail/1.6.2 References: <200411231226.38172.jkim@niksun.com> <41A49312.5@freebsd.org> <41A49EF1.8030603@mac.com> In-Reply-To: <41A49EF1.8030603@mac.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411241019.25271.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Chuck Swiger cc: Scott Long Subject: Re: Transparent bridges (a. k. a. HUB-to-PCI bridges)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 15:41:13 -0000 On Wednesday 24 November 2004 09:47 am, Chuck Swiger wrote: > Scott Long wrote: > > Chuck Swiger wrote: > > [ ... ] > > >> A host-PCI bridge is typically part of the "southbridge" chip of > >> modern motherboards; on Intel motherboards this is also called the ICH > >> chip, such as the 82801AA/BA/CA/etc. VIA Southbridges include the > >> VT8233/8235/8237/etc. > > > > Nope. The southbridge typically holds a PCI-ISA bridge. The host-pci > > bridge is usually found in the northbridge part of the chipset. The > > whole point it to bridge the CPU to one or more PCI buses. > > I've been wrong before, but please double-check diagrams like: > > http://www.intel.com/design/chipsets/850/pix/850_800.gif > http://www.viatech.com/en/products/chipsets/p4-series/pt880/ > > The "northbridge", or MCH, connects to the CPU, AGP, RAM, and the > southbridge. > > The "southbridge", or ICH, connects to PCI, ATA, USB, BIOS chip, and the > northbridge. Newer southbridge chips may add integrated LAN, > 1394/Firewire, integrated AC'97 audio, and such via external codec chips > like the VT6103 PHY. The northbridge is the host-pci bridge. It contains a virtual PCI-PCI bridge/bus that represents AGP. The chipset uses a propietary interconnect to the southbridge such that the devices the north and south bridges connect to show up as one pci bus (bus 0). You could build a system without a southbridge (just PCI-X bridges or some such) and it would still have a host-pci bridge. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 15:41:17 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FA2D16A4CE for ; Wed, 24 Nov 2004 15:41:17 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id F396E43D41 for ; Wed, 24 Nov 2004 15:41:16 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 30517 invoked from network); 24 Nov 2004 15:41:16 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 24 Nov 2004 15:41:15 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAOFf5WW043775; Wed, 24 Nov 2004 10:41:11 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Wed, 24 Nov 2004 10:21:15 -0500 User-Agent: KMail/1.6.2 References: <20041124011452.039741bc@vixen42.24-119-122-191.cpe.cableone.net> In-Reply-To: <20041124011452.039741bc@vixen42.24-119-122-191.cpe.cableone.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411241021.15645.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Vulpes Velox Subject: Re: interrupt storm and atapicam X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 15:41:17 -0000 On Wednesday 24 November 2004 02:14 am, Vulpes Velox wrote: > Just got around to adding a DVD+RW drive to my machine today. I went > to add atapicam to the system. When I recompiled the kernel and > rebooted I got an error about a interrupt storm on atapci1 and it > freezes. > > > > > > dmesg... > Copyright (c) 1992-2004 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 5.3-STABLE #1: Wed Nov 24 00:16:44 CST 2004 > root@vixen42:/usr/obj/usr/src/sys/GENERIC > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Athlon(tm) XP 2000+ (1750.01-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x680 Stepping = 0 > > Features=0x383f9ff A,CMOV,PAT,PSE36,MMX,FXSR,SSE> AMD > Features=0xc0400000 real memory = 1073676288 (1023 > MB) avail memory = 1041117184 (992 MB) > ACPI-0277: *** Warning: Invalid checksum in table [FACP] (4e, sum > a5 is not zero) Try disabling ACPI. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 15:41:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45CC516A4CE for ; Wed, 24 Nov 2004 15:41:18 +0000 (GMT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id E193543D41 for ; Wed, 24 Nov 2004 15:41:17 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 24559 invoked from network); 24 Nov 2004 15:41:17 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 24 Nov 2004 15:41:17 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAOFf5WX043775; Wed, 24 Nov 2004 10:41:14 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org, hogan@ninthgate.net Date: Wed, 24 Nov 2004 10:22:05 -0500 User-Agent: KMail/1.6.2 References: <20041123182254.GB10721@ninthgate.net> In-Reply-To: <20041123182254.GB10721@ninthgate.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411241022.05611.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx Subject: Re: Random panics with 5.3-REL, SMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 15:41:18 -0000 On Tuesday 23 November 2004 01:22 pm, Hogan Whittall wrote: > Hi all, > > I've been running 5.3-REL for a couple of weeks now and have run into > various problems with panics. Initially I had a wireless card that > wasn't supported natively, so I made use of the NDIS wrapper. This > worked "ok" but was buggy and the card/driver would stop talking > on the WLAN randomly, fix was to bounce the interface and it worked > fine for a while longer. At one point downing the interface caused > a panic, so I swapped out the wireless card with one supported > natively. Works like a charm...at least wireless does. > > I'm still getting random panics, however. Doesn't appear to be > related to anything in particular and seems to usually happen > after being up for 1-2 days. I've attempted to get a coredump but > the last panic wedged while dumping to disk. I'm going to be out of > town for a week and won't have access to the box, but if anyone > has experienced something like this before and knows of a fix, please > let me know. Here are the specs of the machine: > > Dell PE6450 server, 4xP3-700 Xeon, 4gb ram, system disks reside on > a 2 disk RAID1 attached to a MegaRAID controller. Wireless is a > D-Link DWL-G520-B, also has Intel Pro/100 ethernet. > > Large storage is fiber-connected Clariion FC5700 via two QLA2200-C > 64-bit PCI cards. > > Also attached via AIC-7899 controller is a DDS3 tape backup. > > Any hints or suggestions would be greatly appreciated, I can test > and give the results when I get back from Thanksgiving vacation. Do you have a panic message? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 16:07:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 647C116A4CF; Wed, 24 Nov 2004 16:07:38 +0000 (GMT) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DD3443D5E; Wed, 24 Nov 2004 16:07:37 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy.york.ac.uk [144.32.226.160]) by mail-gw0.york.ac.uk (8.12.10/8.12.10) with ESMTP id iAOG7Yg5008289; Wed, 24 Nov 2004 16:07:34 GMT Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.1/8.13.1) with ESMTP id iAOG7Yqm057811; Wed, 24 Nov 2004 16:07:34 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.1/8.13.1/Submit) id iAOG7Yf1057810; Wed, 24 Nov 2004 16:07:34 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1101312453.56574.122.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 24 Nov 2004 16:07:34 +0000 X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Subject: Memory modified after free: Most recently used by acpitask X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 16:07:38 -0000 Hi, Just got a panic on a 6-CURRENT (Thu Nov 18 16:36:35 GMT 2004) machine, while copying a large amount of data around. Seems to be an ACPI related reuse-after-free. As far as I can tell, 20 bytes into the acpi_task structure is (int)ta_flags within the embedded struct task, but I can't see use of this field in the ACPI code so ACPI may be a red herring. Sadly, I don't have a core dump as the machine double faulted during the attempt. Gavin # cp -Rp /usr/* /var/usr [about 10 minutes later] Memory modified after free 0xc44a8420(28) val=0 @ 0xc44a8434 panic: Most recently used by acpitask cpuid = 1 KDB: enter: panic [thread 100103] Stopped at kdb_enter+0x2c: leave db> tr kdb_enter(c081145f,100,c3929480,1c,c44a843c) at kdb_enter+0x2c panic(c082b121,c0a312d0,c082b0f2,c44a8420,1c) at panic+0x17f mtrash_ctor(c44a8420,20,0,502) at mtrash_ctor+0x5f uma_zalloc_arg(c1052420,0,502) at uma_zalloc_arg+0x3d8 malloc(20,c08a80c0,502,0,0) at malloc+0x6b softdep_setup_directory_add(d7583cb0,c5379348,28,0,f769f) at softdep_setup_directory_add+0x61 ufs_direnter(c5e9dac8,c58aa78c,ecc95924,ecc95c0c,0,c53e4834,ecc95c0c,ecc95924) at ufs_direnter+0x6ff ufs_makeinode(ecc95bf8,ecc95c0c,ecc95a6c,ecc95b2c,c0668f16) at ufs_makeinode+0x267 ufs_create(ecc95a70) at ufs_create+0x25 vn_open_cred(ecc95be4,ecc95ce4,16d,c3480780,4) at vn_open_cred+0x49a vn_open(ecc95be4,ecc95ce4,16d,4,c08d2040,8,c081a444,3bc) at vn_open+0x1e kern_open(c3929480,804b868,0,602,816d) at kern_open+0xd6 open(c3929480,ecc95d14,3,1015d,286) at open+0x18 syscall(804002f,2f,bfbf002f,804b89d,1) at syscall+0x128 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (5, FreeBSD ELF32, open), eip = 0x280c1bdf, esp = 0xbfbfeb3c, ebp = 0xbfbfeb88 --- Gavin From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 16:13:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 682E816A4CE; Wed, 24 Nov 2004 16:13:47 +0000 (GMT) Received: from S1.cableone.net (smtp1.cableone.net [24.116.0.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B5AA43D3F; Wed, 24 Nov 2004 16:13:47 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from vixen42.24-119-122-191.cpe.cableone.net (unverified [24.119.122.25]) by S1.cableone.net (CableOne SMTP Service S1) with ESMTP id 2280082 for multiple; Wed, 24 Nov 2004 09:20:13 -0700 Date: Wed, 24 Nov 2004 10:12:30 -0600 From: Vulpes Velox To: John Baldwin Message-ID: <20041124101230.1c5c2f57@vixen42.24-119-122-191.cpe.cableone.net> In-Reply-To: <200411241021.15645.jhb@FreeBSD.org> References: <20041124011452.039741bc@vixen42.24-119-122-191.cpe.cableone.net> <200411241021.15645.jhb@FreeBSD.org> X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Abuse-Info: Send abuse complaints to abuse@cableone.net cc: freebsd-current@FreeBSD.org Subject: Re: interrupt storm and atapicam X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 16:13:47 -0000 On Wed, 24 Nov 2004 10:21:15 -0500 John Baldwin wrote: > On Wednesday 24 November 2004 02:14 am, Vulpes Velox wrote: > > Just got around to adding a DVD+RW drive to my machine today. I > > went to add atapicam to the system. When I recompiled the kernel > > and rebooted I got an error about a interrupt storm on atapci1 and > > it freezes. > > > > > > > > > > > > dmesg... > > Copyright (c) 1992-2004 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 5.3-STABLE #1: Wed Nov 24 00:16:44 CST > > 2004 > > root@vixen42:/usr/obj/usr/src/sys/GENERIC > > Timecounter "i8254" frequency 1193182 Hz quality 0 > > CPU: AMD Athlon(tm) XP 2000+ (1750.01-MHz 686-class CPU) > > Origin = "AuthenticAMD" Id = 0x680 Stepping = 0 > > > > Features=0x383f9ff > E,MC A,CMOV,PAT,PSE36,MMX,FXSR,SSE> AMD > > Features=0xc0400000 real memory = 1073676288 > > (1023 MB) avail memory = 1041117184 (992 MB) > > ACPI-0277: *** Warning: Invalid checksum in table [FACP] (4e, > > sum > > a5 is not zero) > > Try disabling ACPI. Tried that, it makes no difference. Also tried it with APIC and without, got it both tmes there too. Got looking around a bit more, appears to be a problem with some promise cards, I found like one or two other occurnces of this mentioned on the mailing list. From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 16:33:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86F0D16A4EC; Wed, 24 Nov 2004 16:33:47 +0000 (GMT) Received: from r1a.corp.servercentral.net (exchange.corp.servercentral.net [66.225.247.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id E69A443D55; Wed, 24 Nov 2004 16:33:46 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from mail pickup service by r1a.corp.servercentral.net with Microsoft SMTPSVC; Wed, 24 Nov 2004 10:33:38 -0600 Received: from demandindustries.net ([161.58.224.124]) by r1a.corp.servercentral.net with Microsoft SMTPSVC(6.0.3790.0); Wed, 24 Nov 2004 08:11:01 -0600 Received: from scanner.servercentral.net (scanner.servercentral.net [66.225.196.47]) by demandindustries.net (8.12.11/8.12.9) with ESMTP id iAOEAvqj092698 for ; Wed, 24 Nov 2004 08:10:58 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by scanner.servercentral.net (Postfix) with ESMTP id 47C3B8700AB for ; Wed, 24 Nov 2004 08:10:52 -0600 (CST) Received: from scanner.servercentral.net ([127.0.0.1]) by localhost (mb [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05287-03 for ; Wed, 24 Nov 2004 08:10:48 -0600 (CST) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by scanner.servercentral.net (Postfix) with ESMTP id 66498870002 for ; Wed, 24 Nov 2004 08:10:48 -0600 (CST) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id E4C6057D0D; Wed, 24 Nov 2004 14:09:12 +0000 (GMT) (envelope-from owner-freebsd-stable@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5DA0916A56A; Wed, 24 Nov 2004 14:08:55 +0000 (GMT) Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AED916A4CE; Wed, 24 Nov 2004 14:01:25 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8E6043D58; Wed, 24 Nov 2004 14:01:24 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAOE4Aiv063294; Wed, 24 Nov 2004 07:04:11 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41A4944C.6030808@freebsd.org> Date: Wed, 24 Nov 2004 07:01:48 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: In-Reply-To: X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Sender: owner-freebsd-stable@freebsd.org Errors-To: owner-freebsd-stable@freebsd.org X-Virus-Scanned: by amavis for cervercentral.net X-OriginalArrivalTime: 24 Nov 2004 14:11:01.0772 (UTC) FILETIME=[6DA014C0:01C4D22F] cc: freebsd-current@freebsd.org Subject: Re: 5-STABLE softupdates issue? X-BeenThere: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 16:33:47 -0000 Matthias Andree wrote: > Greetings, > > out of fun and to investigate claims about alleged bgfsck resource > hogging (which I could not reproduce) posted to > news:de.comp.os.unix.bsd, I pressed the reset button on a live FreeBSD > 5-STABLE system. > > Upon reboot, fsck -p complained about an unexpected softupdates > inconsistency on the / file system and put me into single user mode, the > manual fsck / then asked me to agree to increasing a link count from 21 > to 22 (and later to fix the summary, which I consider a non-issue). A > subsequent fsck -p / ended with no abnormality detected. > > Unfortunately, I haven't copied the details, assuming they would be > copied into the log, but they haven't. > > Is this a situation the current 5-STABLE softupdates code (on a UFS1 FS > that I kept from FreeBSD 4) is allowed to cause? > > Is that a bug in the file system, say, write ordering goofed up? > > Or is that a bug in the firmware of my disk drive (Western Digital > Caviar AC420400D, a rebranded IBM DJNA drive)? I gather that ATA drives > are supposed to flush their caches on software (command) and hardware > resets (reset line active). > > I did not power cycle. > No, this in theory should not happen. YOu could have caught it right at the instance that it was sending a transaction out to disk, or you could have caught an edge case that isn't understood yet. Unfortunately, ATA drives also cannot be trusted to flush their caches when one would expect, so this leaves open a lot of possible causes for your problem. Scott _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 16:34:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E14D16A4D9; Wed, 24 Nov 2004 16:34:11 +0000 (GMT) Received: from r1a.corp.servercentral.net (exchange.corp.servercentral.net [66.225.247.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1FAE43D2D; Wed, 24 Nov 2004 16:34:10 +0000 (GMT) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: from mail pickup service by r1a.corp.servercentral.net with Microsoft SMTPSVC; Wed, 24 Nov 2004 10:34:03 -0600 Received: from demandindustries.net ([161.58.224.124]) by r1a.corp.servercentral.net with Microsoft SMTPSVC(6.0.3790.0); Wed, 24 Nov 2004 08:41:40 -0600 Received: from scanner.servercentral.net (scanner.servercentral.net [66.225.196.47]) by demandindustries.net (8.12.11/8.12.9) with ESMTP id iAOEfdPd001122 for ; Wed, 24 Nov 2004 08:41:39 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by scanner.servercentral.net (Postfix) with ESMTP id 8A2E58700B0 for ; Wed, 24 Nov 2004 08:41:33 -0600 (CST) Received: from scanner.servercentral.net ([127.0.0.1]) by localhost (mb [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05504-10 for ; Wed, 24 Nov 2004 08:41:29 -0600 (CST) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by scanner.servercentral.net (Postfix) with ESMTP id 90FFF8700AB for ; Wed, 24 Nov 2004 08:41:29 -0600 (CST) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 88F1957824; Wed, 24 Nov 2004 14:41:05 +0000 (GMT) (envelope-from owner-freebsd-stable@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 1C49D16A4F8; Wed, 24 Nov 2004 14:40:58 +0000 (GMT) Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 414AE16A4CE; Wed, 24 Nov 2004 14:40:42 +0000 (GMT) Received: from mail.dt.e-technik.uni-dortmund.de (mail.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63EA143D4C; Wed, 24 Nov 2004 14:40:41 +0000 (GMT) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: from localhost (localhost [127.0.0.1])6B7A849C84; Wed, 24 Nov 2004 15:40:40 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 22608-05-2; Wed, 24 Nov 2004 15:40:39 +0100 (CET) Received: from m2a2.dyndns.org (p548546B7.dip.t-dialin.net [84.133.70.183]) A99F249B17; Wed, 24 Nov 2004 15:40:39 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 55F02D5769; Wed, 24 Nov 2004 15:40:38 +0100 (CET) Received: from merlin.emma.line.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 24215-07-4; Wed, 24 Nov 2004 15:40:37 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id 8B86FD5750; Wed, 24 Nov 2004 15:40:37 +0100 (CET) To: Scott Long In-Reply-To: <41A4944C.6030808@freebsd.org> (Scott Long's message of "Wed, 24 Nov 2004 07:01:48 -0700") References: <41A4944C.6030808@freebsd.org> From: Matthias Andree Date: Wed, 24 Nov 2004 15:40:37 +0100 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Sender: owner-freebsd-stable@freebsd.org Errors-To: owner-freebsd-stable@freebsd.org X-Virus-Scanned: by amavis for cervercentral.net X-OriginalArrivalTime: 24 Nov 2004 14:41:45.0049 (UTC) FILETIME=[B84DD490:01C4D233] cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: 5-STABLE softupdates issue? X-BeenThere: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 16:34:11 -0000 Scott Long writes: > No, this in theory should not happen. YOu could have caught it right at > the instance that it was sending a transaction out to disk, or you could > have caught an edge case that isn't understood yet. Unfortunately, ATA > drives also cannot be trusted to flush their caches when one would > expect, so this leaves open a lot of possible causes for your problem. That's why I added that question about drive cache flushing. I'll see to running with forced hw.ata.wc="0" and see if I can reproduce that problem. May be a while while before I see the problem again, these are very scarce fortunately (actually, the first SOFTDEP issue on this machine at all). OTOH, this is an IBM desktop drive in disguise, so the blatant firmware errors should be known by now. -- Matthias Andree _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 16:34:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8970316A57E; Wed, 24 Nov 2004 16:34:26 +0000 (GMT) Received: from r1a.corp.servercentral.net (exchange.corp.servercentral.net [66.225.247.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2360743D2D; Wed, 24 Nov 2004 16:34:26 +0000 (GMT) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: from mail pickup service by r1a.corp.servercentral.net with Microsoft SMTPSVC; Wed, 24 Nov 2004 10:34:18 -0600 Received: from demandindustries.net ([161.58.224.124]) by r1a.corp.servercentral.net with Microsoft SMTPSVC(6.0.3790.0); Wed, 24 Nov 2004 05:51:46 -0600 Received: from scanner.servercentral.net (scanner.servercentral.net [66.225.196.47]) by demandindustries.net (8.12.11/8.12.9) with ESMTP id iAOBpg9p060286 for ; Wed, 24 Nov 2004 05:51:43 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by scanner.servercentral.net (Postfix) with ESMTP id 1B9E28700AC for ; Wed, 24 Nov 2004 05:51:41 -0600 (CST) Received: from scanner.servercentral.net ([127.0.0.1]) by localhost (mb [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 04212-08 for ; Wed, 24 Nov 2004 05:51:40 -0600 (CST) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by scanner.servercentral.net (Postfix) with ESMTP id 4B82B8700AB for ; Wed, 24 Nov 2004 05:51:40 -0600 (CST) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 7DF7857E88; Wed, 24 Nov 2004 11:50:52 +0000 (GMT) (envelope-from owner-freebsd-stable@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 4E0BE16A4E6; Wed, 24 Nov 2004 11:50:38 +0000 (GMT) Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 366BD16A4CE; Wed, 24 Nov 2004 11:49:12 +0000 (GMT) Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8358B43D55; Wed, 24 Nov 2004 11:49:11 +0000 (GMT) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: from localhost (localhost [127.0.0.1])84DEF499E7; Wed, 24 Nov 2004 12:49:10 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 14921-04; Wed, 24 Nov 2004 12:49:10 +0100 (CET) Received: from m2a2.dyndns.org (p548546B7.dip.t-dialin.net [84.133.70.183]) B8EED498E5; Wed, 24 Nov 2004 12:49:09 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 122B8D3F13; Wed, 24 Nov 2004 12:49:09 +0100 (CET) Received: from merlin.emma.line.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 17611-02; Wed, 24 Nov 2004 12:49:08 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id 5789DCDA72; Wed, 24 Nov 2004 12:49:08 +0100 (CET) To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Mail-Followup-To: freebsd-stable@freebsd.org User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) From: Matthias Andree Date: Wed, 24 Nov 2004 12:49:08 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Sender: owner-freebsd-stable@freebsd.org Errors-To: owner-freebsd-stable@freebsd.org X-Virus-Scanned: by amavis for cervercentral.net X-OriginalArrivalTime: 24 Nov 2004 11:51:46.0641 (UTC) FILETIME=[F9944410:01C4D21B] Subject: 5-STABLE softupdates issue? X-BeenThere: freebsd-current@freebsd.org Reply-To: freebsd-stable@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 16:34:26 -0000 Greetings, out of fun and to investigate claims about alleged bgfsck resource hogging (which I could not reproduce) posted to news:de.comp.os.unix.bsd, I pressed the reset button on a live FreeBSD 5-STABLE system. Upon reboot, fsck -p complained about an unexpected softupdates inconsistency on the / file system and put me into single user mode, the manual fsck / then asked me to agree to increasing a link count from 21 to 22 (and later to fix the summary, which I consider a non-issue). A subsequent fsck -p / ended with no abnormality detected. Unfortunately, I haven't copied the details, assuming they would be copied into the log, but they haven't. Is this a situation the current 5-STABLE softupdates code (on a UFS1 FS that I kept from FreeBSD 4) is allowed to cause? Is that a bug in the file system, say, write ordering goofed up? Or is that a bug in the firmware of my disk drive (Western Digital Caviar AC420400D, a rebranded IBM DJNA drive)? I gather that ATA drives are supposed to flush their caches on software (command) and hardware resets (reset line active). I did not power cycle. -- Matthias Andree _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 16:49:08 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A05416A4CE; Wed, 24 Nov 2004 16:49:08 +0000 (GMT) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 214EB43D5A; Wed, 24 Nov 2004 16:49:08 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-186-185.dsl.snfc21.pacbell.net [64.171.186.185])iAOGn9Hr000738; Wed, 24 Nov 2004 11:49:10 -0500 Message-ID: <41A4BB82.2010406@root.org> Date: Wed, 24 Nov 2004 08:49:06 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gavin Atkinson References: <1101312453.56574.122.camel@buffy.york.ac.uk> In-Reply-To: <1101312453.56574.122.camel@buffy.york.ac.uk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Memory modified after free: Most recently used by acpitask X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 16:49:08 -0000 Gavin Atkinson wrote: > Hi, > > Just got a panic on a 6-CURRENT (Thu Nov 18 16:36:35 GMT 2004) machine, > while copying a large amount of data around. > > Seems to be an ACPI related reuse-after-free. As far as I can tell, 20 > bytes into the acpi_task structure is (int)ta_flags within the embedded > struct task, but I can't see use of this field in the ACPI code so ACPI > may be a red herring. > > Sadly, I don't have a core dump as the machine double faulted during the > attempt. > > Gavin > > > # cp -Rp /usr/* /var/usr > [about 10 minutes later] > Memory modified after free 0xc44a8420(28) val=0 @ 0xc44a8434 > panic: Most recently used by acpitask Unfortunately, the panic message doesn't tell you who modified it since someone with a stray pointer (say, who allocated/freed it before acpi) could overwrite it and it was only detected on the next malloc. The way I've found these is to boot -d (into ddb) and type "watch 0xc44a8420". Then hit "c" to continue the boot. Dump a "tr" any time the watchpoint triggers and look for suspicious callers. -Nate From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 17:06:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60BCD16A4CE for ; Wed, 24 Nov 2004 17:06:47 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9ACE43D5C for ; Wed, 24 Nov 2004 17:06:46 +0000 (GMT) (envelope-from soren3@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so421632wra for ; Wed, 24 Nov 2004 09:06:45 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=ASBcL3VFfbYa/mCRTO1xOTVGteTasoWJ5anxGAjuh+Vp698RYcxh+6n1c+tygDsaS40AGaDpKjrwonpTAB4alSeyp0iTtz5vkqzUhxDwY5vz3Zmr4hE5/90jBFwxl9TBaIpAYRDyYEJQL7SYeDPFiRyfYSOw8nqxTev8SwcDWSU= Received: by 10.54.6.79 with SMTP id 79mr63021wrf; Wed, 24 Nov 2004 09:05:35 -0800 (PST) Received: by 10.54.39.7 with HTTP; Wed, 24 Nov 2004 09:05:34 -0800 (PST) Message-ID: Date: Wed, 24 Nov 2004 17:05:34 +0000 From: =?ISO-8859-1?Q?S=F8ren_Lott?= To: freebsd-current Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: cant boot 6-current sesnap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: =?ISO-8859-1?Q?S=F8ren_Lott?= List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 17:06:47 -0000 hi, probably the dumbest question ever, but i'm not being able to boot a sesnap 6-current SESNAP cdrom, the loader keeps asking about a floppy with the kernel image since this machine does not have a floppy disk, i try setting kernel=/kernel.gz.boot (in the cdrom) from the loader cmd. it fail saying that don't know how to load it. cheers. SL. From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 17:18:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA7E216A4CE; Wed, 24 Nov 2004 17:18:56 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 690EB43D3F; Wed, 24 Nov 2004 17:18:56 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iAOHItRo067934; Wed, 24 Nov 2004 11:18:55 -0600 (CST) (envelope-from dan) Date: Wed, 24 Nov 2004 11:18:55 -0600 From: Dan Nelson To: Scott Long Message-ID: <20041124171855.GE95873@dan.emsphone.com> References: <41A4944C.6030808@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41A4944C.6030808@freebsd.org> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: 5-STABLE softupdates issue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 17:18:57 -0000 In the last episode (Nov 24), Scott Long said: > Matthias Andree wrote: > > out of fun and to investigate claims about alleged bgfsck resource > > hogging (which I could not reproduce) posted to > > news:de.comp.os.unix.bsd, I pressed the reset button on a live > > FreeBSD 5-STABLE system. > > > > Upon reboot, fsck -p complained about an unexpected softupdates > > inconsistency on the / file system and put me into single user > > mode, the manual fsck / then asked me to agree to increasing a link > > count from 21 to 22 (and later to fix the summary, which I consider > > a non-issue). A subsequent fsck -p / ended with no abnormality > > detected. > > No, this in theory should not happen. YOu could have caught it right > at the instance that it was sending a transaction out to disk, or you > could have caught an edge case that isn't understood yet. > Unfortunately, ATA drives also cannot be trusted to flush their > caches when one would expect, so this leaves open a lot of possible > causes for your problem. If you just want to test stability in the face of system crashes (and not power failure), you can drop to DDB and run "reboot" to simulate a panic (or run reboot -qn as root). That way your drive doesn't lose power. That said, I get unexpected softupdates inconsistencies pretty regularly on kernel panics. I just let the system run until I can reboot and run a fsck -p. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 17:25:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5616C16A4CE; Wed, 24 Nov 2004 17:25:52 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2D5643D48; Wed, 24 Nov 2004 17:25:51 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAOHSiS2064285; Wed, 24 Nov 2004 10:28:45 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41A4C43D.8020304@freebsd.org> Date: Wed, 24 Nov 2004 10:26:21 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dan Nelson References: <41A4944C.6030808@freebsd.org> <20041124171855.GE95873@dan.emsphone.com> In-Reply-To: <20041124171855.GE95873@dan.emsphone.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: 5-STABLE softupdates issue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 17:25:52 -0000 Dan Nelson wrote: > In the last episode (Nov 24), Scott Long said: > >>Matthias Andree wrote: >> >>>out of fun and to investigate claims about alleged bgfsck resource >>>hogging (which I could not reproduce) posted to >>>news:de.comp.os.unix.bsd, I pressed the reset button on a live >>>FreeBSD 5-STABLE system. >>> >>>Upon reboot, fsck -p complained about an unexpected softupdates >>>inconsistency on the / file system and put me into single user >>>mode, the manual fsck / then asked me to agree to increasing a link >>>count from 21 to 22 (and later to fix the summary, which I consider >>>a non-issue). A subsequent fsck -p / ended with no abnormality >>>detected. >> >>No, this in theory should not happen. YOu could have caught it right >>at the instance that it was sending a transaction out to disk, or you >>could have caught an edge case that isn't understood yet. >>Unfortunately, ATA drives also cannot be trusted to flush their >>caches when one would expect, so this leaves open a lot of possible >>causes for your problem. > > > If you just want to test stability in the face of system crashes (and > not power failure), you can drop to DDB and run "reboot" to simulate a > panic (or run reboot -qn as root). That way your drive doesn't lose > power. > > That said, I get unexpected softupdates inconsistencies pretty > regularly on kernel panics. I just let the system run until I can > reboot and run a fsck -p. > I wonder if this points to dependencies not being pushed out of the buffer/cache correctly. That said, I rarely, if ever, see softupdate problems on my SCSI development systems, but that might just be coincidence. Scott From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 17:27:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA6B316A4CE; Wed, 24 Nov 2004 17:27:07 +0000 (GMT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E0BC43D45; Wed, 24 Nov 2004 17:27:07 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin01-en2 [10.13.10.146]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id iAOHR6Xg010037; Wed, 24 Nov 2004 09:27:07 -0800 (PST) Received: from [10.1.1.245] (nfw2.codefab.com [199.103.21.225] (may be forged)) (authenticated bits=0)iAOHR5cK004798; Wed, 24 Nov 2004 09:27:06 -0800 (PST) In-Reply-To: <200411241019.25271.jhb@FreeBSD.org> References: <200411231226.38172.jkim@niksun.com> <41A49312.5@freebsd.org> <41A49EF1.8030603@mac.com> <200411241019.25271.jhb@FreeBSD.org> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <0F179BC4-3E3E-11D9-BD47-003065ABFD92@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Wed, 24 Nov 2004 12:27:04 -0500 To: John Baldwin X-Mailer: Apple Mail (2.619) cc: freebsd-current@FreeBSD.org cc: Scott Long Subject: Re: Transparent bridges (a. k. a. HUB-to-PCI bridges)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 17:27:08 -0000 On Nov 24, 2004, at 10:19 AM, John Baldwin wrote: >> I've been wrong before, but please double-check diagrams like: >> >> http://www.intel.com/design/chipsets/850/pix/850_800.gif >> http://www.viatech.com/en/products/chipsets/p4-series/pt880/ [ ... ] > The northbridge is the host-pci bridge. It contains a virtual PCI-PCI > bridge/bus that represents AGP. Agreed, although AGP is something of a special case. > The chipset uses a propietary interconnect to the southbridge... Such as VIA's V-link. > ...such that the devices the north and south bridges connect > to show up as one pci bus (bus 0). You could build a system without a > southbridge (just PCI-X bridges or some such) and it would still have a > host-pci bridge. You and Scott are correct. pciconf claims that something like a 440BX northbridge (82443BX) contains both a HOST-PCI and a PCI-PCI bridge, whereas the PIIX4 southbridge (82371AB) has a PCI-ISA bridge, as well as ATA and the other things I'd mentioned. I apologize if I confused the person I was trying to answer. -- -Chuck From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 17:42:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B52C016A4CF for ; Wed, 24 Nov 2004 17:42:45 +0000 (GMT) Received: from smtp.hispeed.ch (mxout.hispeed.ch [62.2.95.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B3E743D5F for ; Wed, 24 Nov 2004 17:42:44 +0000 (GMT) (envelope-from eh-lists-freebsd@critical.ch) Received: from beaver.critical.ch (217-162-254-105.dclient.hispeed.ch [217.162.254.105])iAOHggA3002993 for ; Wed, 24 Nov 2004 18:42:43 +0100 Date: Wed, 24 Nov 2004 18:43:42 +0100 From: Emanuel Haupt To: freebsd-current@freebsd.org Message-Id: <20041124184342.04f0ac32.eh-lists-freebsd@critical.ch> X-Mailer: Sylpheed version 1.0.0beta3 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: merge nwfs code to 5-STABLE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 17:42:46 -0000 hello, nwfs works again on one of my 6.0-CURRENT test boxes. this is also mentioned in german release notes (1). i was wondering if there are plans to merge that code with 5-STABLE or maybe in 5.4-RELEASE? thank you, emanuel (1) http://www.freebsd.org/de/relnotes/CURRENT/relnotes/i386/article.html (sorry, i didn't find the corresponding article in english) > NETNCP und die Unterst=FCtzung f=FCr Netware Dateisysteme (nwfs) > funktionieren wieder. From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 18:07:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5602816A4CE; Wed, 24 Nov 2004 18:07:48 +0000 (GMT) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81B9143D2F; Wed, 24 Nov 2004 18:07:47 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy.york.ac.uk [144.32.226.160]) by mail-gw0.york.ac.uk (8.12.10/8.12.10) with ESMTP id iAOI7hg5024948; Wed, 24 Nov 2004 18:07:43 GMT Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.1/8.13.1) with ESMTP id iAOI7hYC058210; Wed, 24 Nov 2004 18:07:43 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.1/8.13.1/Submit) id iAOI7hkB058209; Wed, 24 Nov 2004 18:07:43 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: Nate Lawson In-Reply-To: <41A4BB82.2010406@root.org> References: <1101312453.56574.122.camel@buffy.york.ac.uk> <41A4BB82.2010406@root.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1101319662.56574.141.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 24 Nov 2004 18:07:43 +0000 X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Memory modified after free: Most recently used by acpitask X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 18:07:48 -0000 On Wed, 2004-11-24 at 16:49, Nate Lawson wrote: > Gavin Atkinson wrote: > > Hi, > > > > Just got a panic on a 6-CURRENT (Thu Nov 18 16:36:35 GMT 2004) machine, > > while copying a large amount of data around. > > > > Seems to be an ACPI related reuse-after-free. As far as I can tell, 20 > > bytes into the acpi_task structure is (int)ta_flags within the embedded > > struct task, but I can't see use of this field in the ACPI code so ACPI > > may be a red herring. > > > > > > # cp -Rp /usr/* /var/usr > > [about 10 minutes later] > > Memory modified after free 0xc44a8420(28) val=0 @ 0xc44a8434 > > panic: Most recently used by acpitask > > Unfortunately, the panic message doesn't tell you who modified it since > someone with a stray pointer (say, who allocated/freed it before acpi) > could overwrite it and it was only detected on the next malloc. The way > I've found these is to boot -d (into ddb) and type "watch 0xc44a8420". > Then hit "c" to continue the boot. Dump a "tr" any time the watchpoint > triggers and look for suspicious callers. Sadly, I suspect it's not going to be that easy. I've just had another panic, same trigger and symptoms but different memory address. Memory modified after free 0xc50441c0(28) val=0 @ 0xc50441d4 panic: Most recently used by acpitask cpuid = 0 KDB: enter: panic [thread 100111] Stopped at kdb_enter+0x2c: leave I'll try taking the box to top-of-tree current in case it has already been fixed - however that will probably have to wait until tomorrow now as this machine cannot reboot without physical help. Surely it seems like quite a coincidence that both times it was 20 bytes into memory once owned by acpitask, though? Gavin From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 18:15:55 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66FDB16A4CE for ; Wed, 24 Nov 2004 18:15:55 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CC0443D46 for ; Wed, 24 Nov 2004 18:15:55 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 28570 invoked from network); 24 Nov 2004 18:15:54 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 24 Nov 2004 18:15:54 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAOIFpP7044903; Wed, 24 Nov 2004 13:15:51 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org, =?iso-8859-1?q?S=F8ren_Lott?= Date: Wed, 24 Nov 2004 13:15:46 -0500 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200411241315.46843.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx Subject: Re: cant boot 6-current sesnap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 18:15:55 -0000 On Wednesday 24 November 2004 12:05 pm, S=F8ren Lott wrote: > hi, > probably the dumbest question ever, > but i'm not being able to boot a sesnap 6-current SESNAP cdrom, > the loader keeps asking about a floppy with the kernel image > since this machine does not have a floppy disk, i try setting > kernel=3D/kernel.gz.boot (in the cdrom) from the loader cmd. it fail > saying that don't know how to load it. kernel.gz.boot is not a full kernel but just the first few kilobytes of a=20 compressed kernel. Is the SESNAP machine not using cdboot to boot? 5.x an= d=20 beyond don't support using floppy images for CD booting anymore, just=20 using /boot/cdboot. =2D-=20 John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 18:28:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC1D116A4CE; Wed, 24 Nov 2004 18:28:13 +0000 (GMT) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E91343D1D; Wed, 24 Nov 2004 18:28:13 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222])iAOISFHr011325; Wed, 24 Nov 2004 13:28:15 -0500 Message-ID: <41A4D2BB.7090400@root.org> Date: Wed, 24 Nov 2004 10:28:11 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gavin Atkinson References: <1101312453.56574.122.camel@buffy.york.ac.uk> <41A4BB82.2010406@root.org> <1101319662.56574.141.camel@buffy.york.ac.uk> In-Reply-To: <1101319662.56574.141.camel@buffy.york.ac.uk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Memory modified after free: Most recently used by acpitask X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 18:28:13 -0000 Gavin Atkinson wrote: > On Wed, 2004-11-24 at 16:49, Nate Lawson wrote: > >>Gavin Atkinson wrote: >>># cp -Rp /usr/* /var/usr >>>[about 10 minutes later] >>>Memory modified after free 0xc44a8420(28) val=0 @ 0xc44a8434 >>>panic: Most recently used by acpitask >> >>Unfortunately, the panic message doesn't tell you who modified it since >>someone with a stray pointer (say, who allocated/freed it before acpi) >>could overwrite it and it was only detected on the next malloc. The way >>I've found these is to boot -d (into ddb) and type "watch 0xc44a8420". >>Then hit "c" to continue the boot. Dump a "tr" any time the watchpoint >>triggers and look for suspicious callers. > > > Sadly, I suspect it's not going to be that easy. I've just had another > panic, same trigger and symptoms but different memory address. > > Memory modified after free 0xc50441c0(28) val=0 @ 0xc50441d4 > panic: Most recently used by acpitask > > cpuid = 0 > KDB: enter: panic > [thread 100111] > Stopped at kdb_enter+0x2c: leave > > I'll try taking the box to top-of-tree current in case it has already > been fixed - however that will probably have to wait until tomorrow now > as this machine cannot reboot without physical help. Surely it seems > like quite a coincidence that both times it was 20 bytes into memory > once owned by acpitask, though? The only coincidence is it's likely the same component causing this problem. acpi is probably only a victim. FYI, in August I fixed an overflow in ATA that had the same symptoms of overwriting an ACPI struct (although that doesn't mean this is caused by ATA). -Nate From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 18:41:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58C2E16A4CE for ; Wed, 24 Nov 2004 18:41:27 +0000 (GMT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F5B243D5C for ; Wed, 24 Nov 2004 18:41:27 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 21811 invoked from network); 24 Nov 2004 18:41:26 -0000 Received: from gate.funkthat.com (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 24 Nov 2004 18:41:26 -0000 Received: from hydrogen.funkthat.com (lwxklm@localhost.funkthat.com [127.0.0.1])iAOIfPGH006231; Wed, 24 Nov 2004 10:41:26 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id iAOIfOKJ006230; Wed, 24 Nov 2004 10:41:24 -0800 (PST) Date: Wed, 24 Nov 2004 10:41:24 -0800 From: John-Mark Gurney To: Chuck Swiger Message-ID: <20041124184124.GA5166@funkthat.com> Mail-Followup-To: Chuck Swiger , "Wilkinson, Alex" , freebsd-current@freebsd.org References: <200411231226.38172.jkim@niksun.com> <200411231343.22760.jhb@FreeBSD.org> <20041124002603.GD20881@squash.dsto.defence.gov.au> <41A416E7.4030107@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41A416E7.4030107@mac.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: freebsd-current@freebsd.org cc: "Wilkinson, Alex" Subject: Re: Transparent bridges (a. k. a. HUB-to-PCI bridges)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 18:41:27 -0000 Chuck Swiger wrote this message on Wed, Nov 24, 2004 at 00:06 -0500: > Wilkinson, Alex wrote: > >2. OOPish device object (device_t) ? > > True OOP involves encapsulation, polymorphism, and inheritence, and > requires language support which is not really available in pure C. That > being said, careful programming in C lets you create several > closely-related structs for different types of "objects" which can all be > utilized by a common set of functions. You should read up on KOBJ's which is how device_t's are implemented in FreeBSD... kobj's are a loop more OOP that you think... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 19:30:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C413E16A4CE for ; Wed, 24 Nov 2004 19:30:59 +0000 (GMT) Received: from sage.ts.co.nz (sage.tasman.net [202.49.92.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1C4543D48 for ; Wed, 24 Nov 2004 19:30:58 +0000 (GMT) (envelope-from marcos@ThePacific.Net) Received: from sage.ts.co.nz ([172.16.21.1]) by sage.ts.co.nz (8.12.11/8.12.10) with ESMTP id iAOJUvSZ019480 for ; Thu, 25 Nov 2004 08:30:57 +1300 Received: from [172.16.20.10] (203-86-192-98.tasman.net [203.86.192.98]) by sage.ts.co.nz (8.12.11/8.12.10) with ESMTP id iAOJU322018374 for ; Thu, 25 Nov 2004 08:30:03 +1300 Message-ID: <41A597C2.7070005@ThePacific.Net> Date: Thu, 25 Nov 2004 08:28:50 +0000 From: "Marcos Biscaysaqu - ThePacific.net" User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040910) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: PF, FTP problems fixed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 19:30:59 -0000 Hi there. somebody know how to make this work on freebsd??? ---------------------------------------------------------------------------- Ok, bleeding edge pf people... I wrote a new FTP proxy called "pftpx" and I'd like to solicit some feedback from the community... Why should you try it? What advantages does pftpx offer? 1) it handles all ftp modes: PORT, PASV, EPRT, EPSV 2) it handles ipv6 3) it should scale: one process handles all sessions using libevent 4) it works with "strict" ftp clients (clients that want data connections to the same IP as the control connection) Quick guide: - you need libevent-0.8 (OpenBSD 3.6 has it) - download http://www.sentia.org/downloads/pftpx-0.3.tar.gz - untar, make - add this to pf.conf in the nat section: nat-anchor "pftpx/*" rdr-anchor "pftpx/*" rdr pass on $if proto tcp from any to any port 21 -> 127.0.0.1 port 8021 - add this to pf.conf in the rule section: anchor "pftpx/*" - run the proxy in debug mode: sudo pftpx -d -D7 - ready to go... Sorry, no manpage yet, this is bleeding edge after all. Don't run this in production if your job depends on it. :-) All feedback welcome, also if you want to suggest a better name. :-) Regards, Cam From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 19:36:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56FFE16A4CE; Wed, 24 Nov 2004 19:36:15 +0000 (GMT) Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9809643D1F; Wed, 24 Nov 2004 19:36:12 +0000 (GMT) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: from localhost (localhost [127.0.0.1])D866D49D38; Wed, 24 Nov 2004 20:36:11 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 31034-02-3; Wed, 24 Nov 2004 20:36:11 +0100 (CET) Received: from m2a2.dyndns.org (p548546B7.dip.t-dialin.net [84.133.70.183]) 12F6649D2F; Wed, 24 Nov 2004 20:36:11 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 5CB35DCAA7; Wed, 24 Nov 2004 20:36:10 +0100 (CET) Received: from merlin.emma.line.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 08619-12-2; Wed, 24 Nov 2004 20:36:09 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id A8B73D4FC2; Wed, 24 Nov 2004 20:36:09 +0100 (CET) To: Scott Long In-Reply-To: <41A4C43D.8020304@freebsd.org> (Scott Long's message of "Wed, 24 Nov 2004 10:26:21 -0700") References: <41A4944C.6030808@freebsd.org> <20041124171855.GE95873@dan.emsphone.com> <41A4C43D.8020304@freebsd.org> From: Matthias Andree Date: Wed, 24 Nov 2004 20:36:09 +0100 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at dt.e-technik.uni-dortmund.de cc: freebsd-stable@freebsd.org cc: freebsd-current@freebsd.org cc: Dan Nelson Subject: Re: 5-STABLE softupdates issue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 19:36:15 -0000 Scott Long writes: > I wonder if this points to dependencies not being pushed out of the > buffer/cache correctly. So do I. Is there a good way to debug this, i. e. more systematic than just trying to trash the FS and see if fsck can recover? > That said, I rarely, if ever, see softupdate > problems on my SCSI development systems, but that might just be > coincidence. I posted about softupdate problems on a SCSI system with DISABLED WRITE CACHE, on a somewhat flakey Micropolis drive that froze and caused massive ffs+softupdates corruption in February 2004 (on FreeBSD 4 though), see for the archived post, including logs. So that makes two for me and some more for Dan. -- Matthias Andree From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 20:29:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9074F16A4CE for ; Wed, 24 Nov 2004 20:29:27 +0000 (GMT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C71843D3F for ; Wed, 24 Nov 2004 20:29:27 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin02-en2 [10.13.10.147]) by smtpout.mac.com (8.12.6/MantshX 2.0) with ESMTP id iAOKTROo008033; Wed, 24 Nov 2004 12:29:27 -0800 (PST) Received: from [10.1.1.245] (nfw2.codefab.com [199.103.21.225] (may be forged)) (authenticated bits=0)iAOKTPRp002935; Wed, 24 Nov 2004 12:29:26 -0800 (PST) In-Reply-To: <20041124184124.GA5166@funkthat.com> References: <200411231226.38172.jkim@niksun.com> <200411231343.22760.jhb@FreeBSD.org> <20041124002603.GD20881@squash.dsto.defence.gov.au> <41A416E7.4030107@mac.com> <20041124184124.GA5166@funkthat.com> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <88534D8A-3E57-11D9-BD47-003065ABFD92@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Wed, 24 Nov 2004 15:29:25 -0500 To: John-Mark Gurney X-Mailer: Apple Mail (2.619) cc: freebsd-current@freebsd.org Subject: Re: Transparent bridges (a. k. a. HUB-to-PCI bridges)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 20:29:27 -0000 On Nov 24, 2004, at 1:41 PM, John-Mark Gurney wrote: >> True OOP involves encapsulation, polymorphism, and inheritence, and >> requires language support which is not really available in pure C. >> That >> being said, careful programming in C lets you create several >> closely-related structs for different types of "objects" which can >> all be >> utilized by a common set of functions. > > You should read up on KOBJ's which is how device_t's are implemented > in FreeBSD... kobj's are a loop more OOP that you think... OK. I've taken a look at sys/kobj.h and sys/kern/subr_kobj.c, is there something else I should read? My take on it, for what it is worth, is that KOBJs implement the class versus instance paradigm, have a dynamic runtime & method dispatch rather similar to the implementation of Objective-C or virtual C++ methods. Yes, this is a lot more object-oriented than what I said about being disciplined using C struct's. :-) Things that one still doesn't have is encapsulation in the sense of data hiding; what Java calls protected or private ivar's. Object memory management for instances via reference counting or GC would also be nice, although I even saw a hint of that in kobj_delete(), as well as a bit of the alloc/init & delete/free seperation. -- -Chuck From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 20:47:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62C1716A4CE for ; Wed, 24 Nov 2004 20:47:03 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1FD943D46 for ; Wed, 24 Nov 2004 20:47:02 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAOKnx84065160; Wed, 24 Nov 2004 13:50:00 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41A4F367.9010002@freebsd.org> Date: Wed, 24 Nov 2004 13:47:35 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Charles Swiger References: <200411231226.38172.jkim@niksun.com> <200411231343.22760.jhb@FreeBSD.org> <20041124002603.GD20881@squash.dsto.defence.gov.au> <41A416E7.4030107@mac.com> <20041124184124.GA5166@funkthat.com> <88534D8A-3E57-11D9-BD47-003065ABFD92@mac.com> In-Reply-To: <88534D8A-3E57-11D9-BD47-003065ABFD92@mac.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: John-Mark Gurney cc: freebsd-current@freebsd.org Subject: Re: Transparent bridges (a. k. a. HUB-to-PCI bridges)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 20:47:03 -0000 Charles Swiger wrote: > On Nov 24, 2004, at 1:41 PM, John-Mark Gurney wrote: > >>> True OOP involves encapsulation, polymorphism, and inheritence, and >>> requires language support which is not really available in pure C. That >>> being said, careful programming in C lets you create several >>> closely-related structs for different types of "objects" which can >>> all be >>> utilized by a common set of functions. >> >> >> You should read up on KOBJ's which is how device_t's are implemented >> in FreeBSD... kobj's are a loop more OOP that you think... > > > OK. I've taken a look at sys/kobj.h and sys/kern/subr_kobj.c, is there > something else I should read? > > My take on it, for what it is worth, is that KOBJs implement the class > versus instance paradigm, have a dynamic runtime & method dispatch > rather similar to the implementation of Objective-C or virtual C++ > methods. Yes, this is a lot more object-oriented than what I said about > being disciplined using C struct's. :-) Right, it's mainly about inheriting and overriding methods from the parent class. There was some work at one time to implement the concept of super(), but that unfortunately didn't go anywhere. It's still quite useful though, especially in the PCI bridge/bus area where there would otherwise be a whole lot of duplicated code. > > Things that one still doesn't have is encapsulation in the sense of data > hiding; what Java calls protected or private ivar's. Object memory > management for instances via reference counting or GC would also be > nice, although I even saw a hint of that in kobj_delete(), as well as a > bit of the alloc/init & delete/free seperation. > The IOKit in Mac OSX uses a stripped-down version of C++ to get real inheritence, polymorphism and public/private/protected data types. It's quite interesting to write a devce driver in this framework; for say a PCI SCSI adapter, you subclass PCI for one class and subclass SCSI for another, then implement the device-specific glue in-between. Scott From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 20:54:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 440E416A4CE for ; Wed, 24 Nov 2004 20:54:28 +0000 (GMT) Received: from wattres.watt.com (wattres.watt.com [66.93.133.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id C713D43D41 for ; Wed, 24 Nov 2004 20:54:26 +0000 (GMT) (envelope-from steve@Watt.COM) Received: from wattres.watt.com (localhost.watt.com [127.0.0.1]) by wattres.watt.com (8.13.1/8.13.1) with ESMTP id iAOKsQQD046060; Wed, 24 Nov 2004 12:54:26 -0800 (PST) (envelope-from steve@wattres.watt.com) Received: (from steve@localhost) by wattres.watt.com (8.13.1/8.13.1/Submit) id iAOKsPQK046058; Wed, 24 Nov 2004 12:54:25 -0800 (PST) (envelope-from steve) Message-Id: <200411242054.iAOKsPQK046058@wattres.watt.com> X-Newsgroups: local.freebsd-current In-Reply-To: <20041123204859.GA2002@gothmog.gr> References: <20041123171951.GG3584@mail.evip.pl> <20041123183930.GA56352@orion.daedalusnetworks.priv> <20041123185923.GH3584@mail.evip.pl> From: steve@Watt.COM (Steve Watt) Date: Wed, 24 Nov 2004 12:54:25 -0800 X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: freebsd-current@freebsd.org, keramida@linux.gr Subject: Re: Putty or libcrypto bug? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 20:54:28 -0000 In <20041123204859.GA2002@gothmog.gr>, keramida@linux.gr wrote: >On 2004-11-23 19:59, Wiktor Niesiobedzki wrote: >>On Tue, Nov 23, 2004 at 08:39:30PM +0200, Giorgos Keramidas wrote: >>> This is a Bad Idea(TM) most of the time though. The library >>> implements a function that other programs or libraries may depend upon >>> to work in certain ways. Replacing the library function with a >>> hand-rolled version may or may not work -- the latter in this case :-/ >> >> Should'nt libc load nss_ldap with kind of RTLD_LOCAL, so the libc will load >> libldap in another symbol-space so symbol lookups will not end in main >> program (if it is at all possible... I'm not familiar with dynamic linking)? > >What happens if parts of the program want to access symbols from many >disjoint namespaces? If a program links to two shared objects: >libfoo.so.1 and libmore.2, which in turn depend on other shared objects, >for example: > > program > libfoo.so.1 > libtest.so.3 > libmore.so.2 > libtmp.so.4 > libthread.so.5 > >and libmore _does_ want to override thread_create() from libthread.so.5 >but libtmp.so.4 wants only the original thread_create() function from >libthread.so.5, which function will the runtime linker call when >`program' calls thread_create()? Then the author of libmore needs to take special steps; overriding standards-described symbols is not something that should be taken lightly, and there's no particular reason to make it trivial, and some good reasons to make it somewhat difficult, so it takes deliberate actions. >> If not, then it is the fact, that programmer of any program should >> aviod duplicating function names across every library that may >> eventually be installed and somehow linked to this programm, what >> sounds rather ridiculous to me. > >I don't think there is support for multiple symbol namespaces in C. >This is probably why most of the utilities in the src/ tree export as >few symbols as possible; many times just a main() function. > >Judicious use of static scope and unique name prefixes like putty_ may >avoid such problems without the need for `RTLD_LOCAL'. Absolutely, but the problem is not in putty. The various UNIX(tm) standards (POSIX and SUS) have quite a bit to say in this area, but the upshot is fairly easily described in two sentences: A library should not use symbol names that are in the user's namespace. A library should declare what names(pace) it uses. For example, POSIX reserves typedefs ending in _t. An application that trips over that has a bug. So, back to the original poster's question: > ... should the putty change the function name ... ? I would vote no. OpenSSL should not pollute the namespace with symbols that it doesn't declare. The sk_* functions are a perfect example of this, they're totally internal to the operation of the ssl library, and not a public interface at all. Now, to convince the OpenSSL maintainers, that's a different challenge. -- Steve Watt KD6GGD PP-ASEL-IA ICBM: 121W 56' 57.8" / 37N 20' 14.9" Internet: steve @ Watt.COM Whois: SW32 Free time? There's no such thing. It just comes in varying prices... From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 21:12:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBE3E16A4CE for ; Wed, 24 Nov 2004 21:12:28 +0000 (GMT) Received: from mail1.webmaster.com (mail1.webmaster.com [216.152.64.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FA9343D46 for ; Wed, 24 Nov 2004 21:12:28 +0000 (GMT) (envelope-from davids@webmaster.com) Received: from however by webmaster.com (MDaemon.PRO.v7.1.0.R) with ESMTP id md50000295952.msg for ; Wed, 24 Nov 2004 12:48:43 -0800 From: "David Schwartz" To: "freebsd-current@FreeBSD. org" Date: Wed, 24 Nov 2004 13:12:28 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-Authenticated-Sender: joelkatz@webmaster.com X-Spam-Processed: mail1.webmaster.com, Wed, 24 Nov 2004 12:48:43 -0800 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 206.171.168.138 X-Return-Path: davids@webmaster.com X-MDaemon-Deliver-To: freebsd-current@FreeBSD.org X-MDAV-Processed: mail1.webmaster.com, Wed, 24 Nov 2004 12:48:47 -0800 Subject: RFC: Add creation time to dynamic firewall rules X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: davids@webmaster.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 21:12:28 -0000 FreeBSD does not keep track of the time a dynamic firewall was created in the structure associated with that rule. It looks like it would take less than an hour to code up a patch to keep this information and add a flag to ipfw to display how many seconds old the rule is instead of the usage time. I want this addition for two reasons: 1) Being able to know how old a connection is gives you important information about its stability. 2) By dividing the number of bytes by the connection age, you can guesstimate the approximate bandwidth usage of the connection. I could easily make this change locally and maintain it as a local patch, but would prefer to see it accepted into the general distribution. Does anyone have any comments as to whether such a patch would be likely to be accepted? The cost is, essentially, an extra 4 bytes for each dynamic firewall rule. A large firewall might have 10,000 dynamic rules, which would be 40Kb. A typical firewall might have 300, which would be 1Kb or so. (It might actually be a bit more or less, I haven't looked at slack space.) Thanks in advance for any comments. DS From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 21:15:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84CD916A4CE for ; Wed, 24 Nov 2004 21:15:33 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id D12F343D39 for ; Wed, 24 Nov 2004 21:15:32 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.160] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CX4U6-0000kI-00; Wed, 24 Nov 2004 22:15:30 +0100 Received: from [84.128.135.252] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1CX4U6-0000qa-00; Wed, 24 Nov 2004 22:15:31 +0100 From: Max Laier To: freebsd-current@freebsd.org Date: Wed, 24 Nov 2004 22:15:52 +0100 User-Agent: KMail/1.7.1 References: <41A597C2.7070005@ThePacific.Net> In-Reply-To: <41A597C2.7070005@ThePacific.Net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1601960.ZaoofOrBhB"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411242216.00848.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 cc: "Marcos Biscaysaqu - ThePacific.net" Subject: Re: PF, FTP problems fixed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 21:15:33 -0000 --nextPart1601960.ZaoofOrBhB Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline [Please fix your systemtime or timezone] On Thursday 25 November 2004 09:28, Marcos Biscaysaqu - ThePacific.net wrot= e: > Hi there. > somebody know how to make this work on freebsd??? > -------------------------------------------------------------------------= =2D- > > Ok, bleeding edge pf people... I wrote a new FTP proxy called "pftpx" and > I'd like to solicit some feedback from the community... > > Why should you try it? What advantages does pftpx offer? > 1) it handles all ftp modes: PORT, PASV, EPRT, EPSV > 2) it handles ipv6 > 3) it should scale: one process handles all sessions using libevent > 4) it works with "strict" ftp clients (clients that want data connections > to the same IP as the control connection) > > > Quick guide: > - you need libevent-0.8 (OpenBSD 3.6 has it) Libevent is in ports (devel/libevent - version 0.9). > - download http://www.sentia.org/downloads/pftpx-0.3.tar.gz > - untar, make > - add this to pf.conf in the nat section: > > nat-anchor "pftpx/*" > rdr-anchor "pftpx/*" That looks not so good. ".../*" anchors are a 3.6 thing, while FreeBSD is=20 en-par with 3.5. From a first look and common sense, I don't think it's a=20 requirement, but you might have to change some code to make it work. > rdr pass on $if proto tcp from any to any port 21 -> 127.0.0.1 port 8021 > > - add this to pf.conf in the rule section: > > anchor "pftpx/*" Same here. > - run the proxy in debug mode: sudo pftpx -d -D7 > - ready to go... > > Sorry, no manpage yet, this is bleeding edge after all. Don't run this in > production if your job depends on it. :-) > > All feedback welcome, also if you want to suggest a better name. :-) I'd be more than happy to see this ported, looks useful! =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1601960.ZaoofOrBhB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBpPoQXyyEoT62BG0RAqdFAJ9AVAxXiP749U/pKeO36k7FmhBLWgCfZxmp fSMZHil6lZQoVFcj6xS4ycU= =gfIy -----END PGP SIGNATURE----- --nextPart1601960.ZaoofOrBhB-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 21:19:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5F1816A4CE; Wed, 24 Nov 2004 21:19:20 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BBCE43D5A; Wed, 24 Nov 2004 21:19:20 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAOLMHMs065225; Wed, 24 Nov 2004 14:22:18 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41A4FAF9.1080704@freebsd.org> Date: Wed, 24 Nov 2004 14:19:53 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Charles Swiger References: <200411231226.38172.jkim@niksun.com> <41A49312.5@freebsd.org> <41A49EF1.8030603@mac.com> <200411241019.25271.jhb@FreeBSD.org> <0F179BC4-3E3E-11D9-BD47-003065ABFD92@mac.com> In-Reply-To: <0F179BC4-3E3E-11D9-BD47-003065ABFD92@mac.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org Subject: Re: Transparent bridges (a. k. a. HUB-to-PCI bridges)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 21:19:20 -0000 Charles Swiger wrote: > On Nov 24, 2004, at 10:19 AM, John Baldwin wrote: > >>> I've been wrong before, but please double-check diagrams like: >>> >>> http://www.intel.com/design/chipsets/850/pix/850_800.gif >>> http://www.viatech.com/en/products/chipsets/p4-series/pt880/ > > [ ... ] > >> The northbridge is the host-pci bridge. It contains a virtual PCI-PCI >> bridge/bus that represents AGP. > > > Agreed, although AGP is something of a special case. > >> The chipset uses a propietary interconnect to the southbridge... > > > Such as VIA's V-link. > >> ...such that the devices the north and south bridges connect >> to show up as one pci bus (bus 0). You could build a system without a >> southbridge (just PCI-X bridges or some such) and it would still have a >> host-pci bridge. > > > You and Scott are correct. pciconf claims that something like a 440BX > northbridge (82443BX) contains both a HOST-PCI and a PCI-PCI bridge, > whereas the PIIX4 southbridge (82371AB) has a PCI-ISA bridge, as well as > ATA and the other things I'd mentioned. > > I apologize if I confused the person I was trying to answer. > Not a problem. The V-Link and ICH buses are really just high-speed tunnels for PCI. Before their invention, the southbridge was directly connected to the northbridge via PCI. Scott From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 21:24:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 061D616A4CE for ; Wed, 24 Nov 2004 21:24:39 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9E3E43D3F for ; Wed, 24 Nov 2004 21:24:38 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 586B15118D; Wed, 24 Nov 2004 13:28:55 -0800 (PST) Date: Wed, 24 Nov 2004 13:28:55 -0800 From: Kris Kennaway To: current@freeBSD.org Message-ID: <20041124212855.GA32463@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sm4nu43k4a2Rpi4c" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Memory modified after free: Most recently used by acpica X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 21:24:39 -0000 --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline This happens on fresh 6.0 if I boot with acpi enabled (but not with acpi compiled out of the kernel). Kris [...] pci_link0: irq 0 on acpi0 Memory modified after free 0xc3587a00(124) val=c3598580 @ 0xc3587a00 panic: Most recently used by acpica cpuid = 0 KDB: enter: panic db> tr Tracing pid 0 tid 0 td 0xc0782900 kdb_enter(c072313d,0,c0738939,c0c22958,c0782900) at kdb_enter+0x32 panic(c0738939,c0713408,7c,c3598580,c3587a00) at panic+0x1b0 mtrash_dtor(c3587a00,80,0,1,0) at mtrash_dtor uma_zalloc_arg(c10526e0,0,1,c1064aa0,c0c22ac0) at uma_zalloc_arg+0x481 malloc(68,c074dec0,1,c0c22a10,c0476f51) at malloc+0x87 AcpiOsAllocate(68,1,c0c22a00,1,0) at AcpiOsAllocate+0x21 AcpiUtInitializeBuffer(c0c22ac0,68,c0c22a3c,68,0) at AcpiUtInitializeBuffer+0x4f AcpiGetObjectInfo(c34d20c0,c0c22ac0,0,c0c22ad4,ffffffff) at AcpiGetObjectInfo+0xd0 acpi_MatchHid(6,c0c22aec,100,c0c22af0,6) at acpi_MatchHid+0x58 acpi_device_id_probe(c34e3e80,c3595700,c074d420,c3467240,c3595700) at acpi_device_id_probe+0x118 acpi_isab_probe(c3595700,0,c0725b19,c359573c,c359573c) at acpi_isab_probe+0x6b device_probe_and_attach(c3595700,c047f02d,c0c22b78,c0c22b80,0) at device_probe_and_attach+0x10f prt_attach_devices(c3595420,c351dc00,c34e3e80,c351dc00,c35848f4) at prt_attach_devices+0xe1 prt_walk_table(c351dc00,c073ae0a,0,c0c22bcc,0) at prt_walk_table+0x30 acpi_pcib_attach(c351dc00,c35848f4,0,c0c22c04,c047e001,c0730ceb,c3467ca0,c0749b78,c34c5ce0) at acpi_pcib_attach+0xe2 acpi_pcib_acpi_attach(c351dc00,c353d04c,c0749b78,c0724d5b,0) at acpi_pcib_acpi_attach+0xf5 device_attach(c351dc00,ffffffff,c0c22cbc,c04802ad,c34e3e80) at device_attach+0x2a7 bus_generic_attach(c34e3e80,fff80000,ffffffff,c34d2448,fff80000) at bus_generic_attach+0x17 acpi_attach(c34e3e80,c355b84c,c0749b78,c0724d5b,0) at acpi_attach+0x78c device_attach(c34e3e80,c351c080,c0c22d18,c06d77b1,c351c080) at device_attach+0x2a7 bus_generic_attach(c351c080) at bus_generic_attach+0x17 nexus_attach(c351c080,c356384c,c0749b78,c0724d5b,0) at nexus_attach+0x1a device_attach(c351c080,c076db90,c0c22d78,c06c580a,c351c800) at device_attach+0x2a7 root_bus_configure(c351c800,c073dbe9,0,c0c22d98,c052615d) at root_bus_configure+0x19 configure(0,0,c0743a70,c1ec00,c1e000) at configure+0x29 mi_startup() at mi_startup+0xb1 begin() at begin+0x2c --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBpP0WWry0BWjoQKURAtHKAJ0cgJ+bcxZWuqabIr08TQizdmlE3ACgiFLr TWD4iNZeFVDFXSIpy9viL4A= =ez7E -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 21:24:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51FAA16A4CF for ; Wed, 24 Nov 2004 21:24:57 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9CB343D2F for ; Wed, 24 Nov 2004 21:24:56 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CX4dE-000Elq-B2; Wed, 24 Nov 2004 13:24:56 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16804.64551.828679.174883@ran.psg.com> Date: Wed, 24 Nov 2004 13:24:55 -0800 To: hogan@ninthgate.net References: <20041123182254.GB10721@ninthgate.net> cc: freebsd-current@freebsd.org Subject: Re: Random panics with 5.3-REL, SMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 21:24:57 -0000 > I'm still getting random panics, however. Doesn't appear to be > related to anything in particular and seems to usually happen > after being up for 1-2 days. I've attempted to get a coredump but > the last panic wedged while dumping to disk. I'm going to be out of > town for a week and won't have access to the box, but if anyone > has experienced something like this before and knows of a fix, please > let me know. well, i can meet half your criteria, random panics on smp with no dumps. but i don't have a fix. RELENG_5 as of Nov 19 06:35 gmt. randy From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 21:31:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4E9616A4CE; Wed, 24 Nov 2004 21:31:02 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2BAE43D2F; Wed, 24 Nov 2004 21:31:02 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CX4j8-000GUq-CN; Wed, 24 Nov 2004 13:31:02 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16804.64917.872924.733444@ran.psg.com> Date: Wed, 24 Nov 2004 13:31:01 -0800 To: Robert Watson References: <20041123182254.GB10721@ninthgate.net> cc: freebsd-current@freebsd.org Subject: Re: Random panics with 5.3-REL, SMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 21:31:03 -0000 > - Using a serial console to the box, you can reliably gather information > without the core dump mechanism working. i caught one, but the rest happened and reboot's beastie wiped the console Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x41959c25 fault code = supervisor write, page not present instruction pointer = 0x8:0xc04e813a stack pointer = 0x10:0xe784d978 frame pointer = 0x10:0xe784d994 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 68301 (sshd) trap number = 12 panic: page fault cpuid = 0 boot() called on cpu#0 Uptime: 9h29m10s Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset called on cpu#0 cpu_reset: Stopping other CPUs since then, i installed a kernel with debugging symbols (blush), but have yet to get a usable savecore and the beastie got me too. > - "Random panics" could mean "A lot of seemingly different panics > happening with relatively frequency", or it might mean "A few similar > panics, happening at random intervals". as i can't really characterize the causes, let's just say they seem random to me. i have not reported this stuff, as i had no good data. but since hogan whined, i thought i should sing the harmony. randy From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 21:39:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B484C16A4E3 for ; Wed, 24 Nov 2004 21:39:32 +0000 (GMT) Received: from sage.ts.co.nz (sage.tasman.net [202.49.92.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03F2343D49 for ; Wed, 24 Nov 2004 21:39:32 +0000 (GMT) (envelope-from marcos@ThePacific.Net) Received: from sage.ts.co.nz ([172.16.21.1]) by sage.ts.co.nz (8.12.11/8.12.10) with ESMTP id iAOLdUkH027097; Thu, 25 Nov 2004 10:39:30 +1300 Received: from [172.16.20.10] (203-86-192-98.tasman.net [203.86.192.98]) by sage.ts.co.nz (8.12.11/8.12.10) with ESMTP id iAOLWcni021853; Thu, 25 Nov 2004 10:32:39 +1300 Message-ID: <41A5B47C.8000706@ThePacific.Net> Date: Thu, 25 Nov 2004 10:31:24 +0000 From: "Marcos Biscaysaqu - ThePacific.net" User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040910) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Max Laier , freebsd-current@freebsd.org References: <41A597C2.7070005@ThePacific.Net> <200411242216.00848.max@love2party.net> In-Reply-To: <200411242216.00848.max@love2party.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: PF, FTP problems fixed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 21:39:34 -0000 If somebody can port this to freebsd will be great, and will make PF so far the best firewall -------------------------------------------------------------------------------------------------------------------------------------------------------- The two most important parts are: - recursive anchors (appeared in OpenBSD 3.6). Maybe Max knows when those when into FreeBSD? - libevent > 0.8 (from ports/devel/libevent) Anything else that crops up should be easily fixable. Max Laier wrote: >[Please fix your systemtime or timezone] > >On Thursday 25 November 2004 09:28, Marcos Biscaysaqu - ThePacific.net wrote: > > >>Hi there. >>somebody know how to make this work on freebsd??? >>--------------------------------------------------------------------------- >> >>Ok, bleeding edge pf people... I wrote a new FTP proxy called "pftpx" and >>I'd like to solicit some feedback from the community... >> >>Why should you try it? What advantages does pftpx offer? >>1) it handles all ftp modes: PORT, PASV, EPRT, EPSV >>2) it handles ipv6 >>3) it should scale: one process handles all sessions using libevent >>4) it works with "strict" ftp clients (clients that want data connections >> to the same IP as the control connection) >> >> >>Quick guide: >>- you need libevent-0.8 (OpenBSD 3.6 has it) >> >> > >Libevent is in ports (devel/libevent - version 0.9). > > > >>- download http://www.sentia.org/downloads/pftpx-0.3.tar.gz >>- untar, make >>- add this to pf.conf in the nat section: >> >>nat-anchor "pftpx/*" >>rdr-anchor "pftpx/*" >> >> > >That looks not so good. ".../*" anchors are a 3.6 thing, while FreeBSD is >en-par with 3.5. From a first look and common sense, I don't think it's a >requirement, but you might have to change some code to make it work. > > > >>rdr pass on $if proto tcp from any to any port 21 -> 127.0.0.1 port 8021 >> >>- add this to pf.conf in the rule section: >> >>anchor "pftpx/*" >> >> > >Same here. > > > >>- run the proxy in debug mode: sudo pftpx -d -D7 >>- ready to go... >> >>Sorry, no manpage yet, this is bleeding edge after all. Don't run this in >>production if your job depends on it. :-) >> >>All feedback welcome, also if you want to suggest a better name. :-) >> >> > >I'd be more than happy to see this ported, looks useful! > > > From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 21:44:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C42A16A4CE for ; Wed, 24 Nov 2004 21:44:43 +0000 (GMT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0D8543D45 for ; Wed, 24 Nov 2004 21:44:42 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 15315 invoked from network); 24 Nov 2004 21:44:42 -0000 Received: from gate.funkthat.com (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail1.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 24 Nov 2004 21:44:42 -0000 Received: from hydrogen.funkthat.com (jqdovs@localhost.funkthat.com [127.0.0.1])iAOLifGH008657; Wed, 24 Nov 2004 13:44:41 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id iAOLie4J008656; Wed, 24 Nov 2004 13:44:40 -0800 (PST) Date: Wed, 24 Nov 2004 13:44:40 -0800 From: John-Mark Gurney To: Charles Swiger Message-ID: <20041124214440.GC5166@funkthat.com> Mail-Followup-To: Charles Swiger , freebsd-current@freebsd.org References: <200411231226.38172.jkim@niksun.com> <200411231343.22760.jhb@FreeBSD.org> <20041124002603.GD20881@squash.dsto.defence.gov.au> <41A416E7.4030107@mac.com> <20041124184124.GA5166@funkthat.com> <88534D8A-3E57-11D9-BD47-003065ABFD92@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <88534D8A-3E57-11D9-BD47-003065ABFD92@mac.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: freebsd-current@freebsd.org Subject: Re: Transparent bridges (a. k. a. HUB-to-PCI bridges)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 21:44:43 -0000 Charles Swiger wrote this message on Wed, Nov 24, 2004 at 15:29 -0500: > On Nov 24, 2004, at 1:41 PM, John-Mark Gurney wrote: > >>True OOP involves encapsulation, polymorphism, and inheritence, and > >>requires language support which is not really available in pure C. > >>That > >>being said, careful programming in C lets you create several > >>closely-related structs for different types of "objects" which can > >>all be > >>utilized by a common set of functions. > > > >You should read up on KOBJ's which is how device_t's are implemented > >in FreeBSD... kobj's are a loop more OOP that you think... > > OK. I've taken a look at sys/kobj.h and sys/kern/subr_kobj.c, is there > something else I should read? There is also a man page, but it's not much more complete... > My take on it, for what it is worth, is that KOBJs implement the class > versus instance paradigm, have a dynamic runtime & method dispatch > rather similar to the implementation of Objective-C or virtual C++ > methods. Yes, this is a lot more object-oriented than what I said > about being disciplined using C struct's. :-) Correct, kobj implements the class side of things, and then if you look at device(9), you'll see the instance implementation part of kobj's.. > Things that one still doesn't have is encapsulation in the sense of > data hiding; what Java calls protected or private ivar's. Object > memory management for instances via reference counting or GC would also > be nice, although I even saw a hint of that in kobj_delete(), as well > as a bit of the alloc/init & delete/free seperation. As part of the device instance API, it provides the abilty to get/set ivars... You can look at the various *.m files for various device API calls. kern/device_if.m is the most common, but then you can also look at sys/dev/iicbus/*.m for a good example of how useful the kobj API is.. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 21:50:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0926C16A4D0; Wed, 24 Nov 2004 21:50:02 +0000 (GMT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id A336D43D45; Wed, 24 Nov 2004 21:50:01 +0000 (GMT) (envelope-from marks@ripe.net) Received: by postman.ripe.net (Postfix, from userid 8) id 187E82602F; Wed, 24 Nov 2004 22:50:01 +0100 (CET) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id A607A26020; Wed, 24 Nov 2004 22:49:57 +0100 (CET) Received: from ripe.net (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id iAOLnvLE017530; Wed, 24 Nov 2004 22:49:57 +0100 Received: (nullmailer pid 1017 invoked by uid 1001); Wed, 24 Nov 2004 21:49:56 -0000 Date: Wed, 24 Nov 2004 22:49:56 +0100 From: Mark Santcroos To: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org Message-ID: <20041124214956.GA829@laptop.6bone.nl> References: <20041115211636.GA1540@laptop.6bone.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041115211636.GA1540@laptop.6bone.nl> User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00 X-RIPE-Spam-Status: N 0.009379 / -5.9 X-RIPE-Signature: 3b05a663b3ef164b232702a2cd660437 Subject: [PATCH] Please test: new ACPI release (20041119) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 21:50:02 -0000 Here [1] is a slightly updated version of the previous patch I posted. It's based on a newer release (20041119). Changes are described in the top of the diff. If there are no regressions, this will be the patch that gets committed. Mark [1] http://www.santcroos.net/mark/freebsd/files/acpi_import_20041119.diff.gz -- RIPE NCC - Delft University of Technology - The FreeBSD Project marks@ripe.net - m.a.santcroos@ewi.tudelft.nl - marks@freebsd.org From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 22:10:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7683616A4CE for ; Wed, 24 Nov 2004 22:10:43 +0000 (GMT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 7537343D48 for ; Wed, 24 Nov 2004 22:10:42 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 17561 invoked by uid 65534); 24 Nov 2004 22:10:40 -0000 Received: from pD95D8F5B.dip.t-dialin.net (EHLO lofi.dyndns.org) (217.93.143.91) by mail.gmx.net (mp022) with SMTP; 24 Nov 2004 23:10:40 +0100 X-Authenticated: #443188 Received: from [192.168.8.4] (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iAOMAR3Q016136 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Nov 2004 23:10:31 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) Message-ID: <41A506D3.6070908@gmx.net> Date: Wed, 24 Nov 2004 23:10:27 +0100 From: Michael Nottebrock User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en, de-de MIME-Version: 1.0 To: Matthias Andree References: <41A4944C.6030808@freebsd.org> <20041124171855.GE95873@dan.emsphone.com> <41A4C43D.8020304@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new cc: freebsd-stable@freebsd.org cc: Dan Nelson cc: freebsd-current@freebsd.org cc: Scott Long Subject: Re: 5-STABLE softupdates issue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 22:10:43 -0000 Matthias Andree wrote: > I posted about softupdate problems on a SCSI system with DISABLED WRITE > CACHE, on a somewhat flakey Micropolis drive that froze and caused > massive ffs+softupdates corruption in February 2004 (on FreeBSD 4 > though), see > for the archived post, including logs. FWIW, I'm used to "UNEXPECTED SOFTUPDATE INCONSISTENCY" erros as well, been getting them every now and then after the occasional system lockup or kernel panic as long as I've been running freebsd and I'm pretty sure with each release since 4.0-R, too. I didn't know those are _literally_ unexpected. If so, then softupdates is a probably lot more flaky than it ought to be. -- ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 22:16:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C518816A4CE; Wed, 24 Nov 2004 22:16:35 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E96043D1F; Wed, 24 Nov 2004 22:16:35 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAOMJRFO065487; Wed, 24 Nov 2004 15:19:27 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41A5085F.9060600@freebsd.org> Date: Wed, 24 Nov 2004 15:17:03 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Nottebrock References: <41A4944C.6030808@freebsd.org> <20041124171855.GE95873@dan.emsphone.com> <41A4C43D.8020304@freebsd.org> <41A506D3.6070908@gmx.net> In-Reply-To: <41A506D3.6070908@gmx.net> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-stable@freebsd.org cc: Dan Nelson cc: freebsd-current@freebsd.org cc: Matthias Andree Subject: Re: 5-STABLE softupdates issue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 22:16:35 -0000 Michael Nottebrock wrote: > Matthias Andree wrote: > > >> I posted about softupdate problems on a SCSI system with DISABLED WRITE >> CACHE, on a somewhat flakey Micropolis drive that froze and caused >> massive ffs+softupdates corruption in February 2004 (on FreeBSD 4 >> though), see >> for the archived post, including logs. > > > FWIW, I'm used to "UNEXPECTED SOFTUPDATE INCONSISTENCY" erros as well, > been getting them every now and then after the occasional system lockup > or kernel panic as long as I've been running freebsd and I'm pretty sure > with each release since 4.0-R, too. I didn't know those are _literally_ > unexpected. If so, then softupdates is a probably lot more flaky than it > ought to be. > It's common (and even expected) for fsck to clean up normal things like unlinked files after a hard shutdown when softupdates is enabled. However, if fsck is bailing out and telling you that there is an unexpected inconsistency that needs to be fixed manually, that is not normal. Unfortunately, most of the evidence is probably long gone by then, so tracking it down is pretty tricky. I've had talks with some filesystem guys at a well-known Unix company who have talked of evil things like extracting dirty buffers from a crashdump file; that may be the level of effort needed to track down these kinds of problems. Scott From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 22:35:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBC7E16A4CF for ; Wed, 24 Nov 2004 22:35:20 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EE8143D5F for ; Wed, 24 Nov 2004 22:35:20 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAOMXU4V025256; Wed, 24 Nov 2004 17:33:30 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iAOMXUgs025253; Wed, 24 Nov 2004 22:33:30 GMT (envelope-from robert@fledge.watson.org) Date: Wed, 24 Nov 2004 22:33:30 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Emanuel Haupt In-Reply-To: <20041124184342.04f0ac32.eh-lists-freebsd@critical.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE cc: freebsd-current@freebsd.org Subject: Re: merge nwfs code to 5-STABLE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 22:35:21 -0000 On Wed, 24 Nov 2004, Emanuel Haupt wrote: > nwfs works again on one of my 6.0-CURRENT test boxes. this is also > mentioned in german release notes (1). i was wondering if there are > plans to merge that code with 5-STABLE or maybe in 5.4-RELEASE?=20 >=20 > thank you, emanuel A quick diff didn't suggest to me that there were substantial changes in either the netncp code or nwfs code between RELENG_5 and HEAD that look like they are related: i.e., there are a few tweaks but they're all part of Poul Henning's buffer cache work. Do you have any more details on the nature of the change? I'd be happy to MFC stuff, but it's not immediately clear to me what to merge. My hope is to keep the network stack pieces of the kernel relatively in synch between RELENG_5 and HEAD as much as possible without breaking the ABI. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research >=20 > (1) > http://www.freebsd.org/de/relnotes/CURRENT/relnotes/i386/article.html > (sorry, i didn't find the corresponding article in english) >=20 > > NETNCP und die Unterst=FCtzung f=FCr Netware Dateisysteme (nwfs) > > funktionieren wieder. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " >=20 From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 22:51:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22C8A16A4CF for ; Wed, 24 Nov 2004 22:51:33 +0000 (GMT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id BEE2043D54 for ; Wed, 24 Nov 2004 22:51:31 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 22072 invoked by uid 65534); 24 Nov 2004 22:51:29 -0000 Received: from pD95D8F5B.dip.t-dialin.net (EHLO lofi.dyndns.org) (217.93.143.91) by mail.gmx.net (mp017) with SMTP; 24 Nov 2004 23:51:29 +0100 X-Authenticated: #443188 Received: from [192.168.8.4] (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iAOMpB3Q016602 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Nov 2004 23:51:11 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) Message-ID: <41A5105E.9050206@gmx.net> Date: Wed, 24 Nov 2004 23:51:10 +0100 From: Michael Nottebrock User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en, de-de MIME-Version: 1.0 To: Scott Long References: <41A4944C.6030808@freebsd.org> <20041124171855.GE95873@dan.emsphone.com> <41A4C43D.8020304@freebsd.org> <41A506D3.6070908@gmx.net> <41A5085F.9060600@freebsd.org> In-Reply-To: <41A5085F.9060600@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new cc: freebsd-stable@freebsd.org cc: Dan Nelson cc: freebsd-current@freebsd.org cc: Matthias Andree Subject: Re: 5-STABLE softupdates issue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 22:51:33 -0000 Scott Long wrote: > Michael Nottebrock wrote: > >> Matthias Andree wrote: >> >> >>> I posted about softupdate problems on a SCSI system with DISABLED WRITE >>> CACHE, on a somewhat flakey Micropolis drive that froze and caused >>> massive ffs+softupdates corruption in February 2004 (on FreeBSD 4 >>> though), see >>> for the archived post, including logs. >> >> >> >> FWIW, I'm used to "UNEXPECTED SOFTUPDATE INCONSISTENCY" erros as well, >> been getting them every now and then after the occasional system >> lockup or kernel panic as long as I've been running freebsd and I'm >> pretty sure with each release since 4.0-R, too. I didn't know those >> are _literally_ unexpected. If so, then softupdates is a probably lot >> more flaky than it ought to be. >> > > It's common (and even expected) for fsck to clean up normal things like > unlinked files after a hard shutdown when softupdates is enabled. > However, if fsck is bailing out and telling you that there is an > unexpected inconsistency that needs to be fixed manually, that is not > normal. Well, I guess the fsck_y_enable knob acknowledges the fact that there are more unexpected things happening than there should be (and FWIW, that knob works fine in getting fsck to finish even despite those inconsistencies - I can't really remember the last time even fsck -y bailed out on something). -- ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 00:38:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51A8216A4CE for ; Thu, 25 Nov 2004 00:38:48 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8A5E43D46 for ; Thu, 25 Nov 2004 00:38:47 +0000 (GMT) (envelope-from soren3@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so470826wra for ; Wed, 24 Nov 2004 16:38:47 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=FCePUb1J+DzofxI4Gq8ufOBjy8VkYecWKN0bwm4DfQUow6HB8cy9kSiN0D7HxAfjlIIZUtn7XN9TGpHcx6JkJplAojdM92b4ywA0w0IErCkYbg9C604dJ89rrG2u2gq3nQv25zIzaLn/iXaLGlRfLCxxeQEOkIBjGP68dw4kSuw= Received: by 10.54.3.13 with SMTP id 13mr357832wrc; Wed, 24 Nov 2004 16:38:40 -0800 (PST) Received: by 10.54.39.7 with HTTP; Wed, 24 Nov 2004 16:38:39 -0800 (PST) Message-ID: Date: Thu, 25 Nov 2004 00:38:39 +0000 From: =?ISO-8859-1?Q?S=F8ren_Lott?= To: freebsd-current In-Reply-To: <200411241315.46843.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200411241315.46843.jhb@FreeBSD.org> Subject: Re: cant boot 6-current sesnap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: =?ISO-8859-1?Q?S=F8ren_Lott?= List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 00:38:48 -0000 On Wed, 24 Nov 2004 13:15:46 -0500, John Baldwin wrote: > > kernel.gz.boot is not a full kernel but just the first few kilobytes of a > compressed kernel. Is the SESNAP machine not using cdboot to boot? 5.x and > beyond don't support using floppy images for CD booting anymore, just > using /boot/cdboot. the 6.0-CURRENT-20041123-SESNAP.iso surely don't have a /boot/cdboot. this looking from the loader cmd, neither display the welcome/boot option menu and goes straight from the btx loader to the "insert floppy" msg. cheers. SL. From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 01:00:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B18616A4CE for ; Thu, 25 Nov 2004 01:00:48 +0000 (GMT) Received: from lakermmtao08.cox.net (lakermmtao08.cox.net [68.230.240.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3F3243D48 for ; Thu, 25 Nov 2004 01:00:47 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.30.24]) by lakermmtao08.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20041125010045.WSYZ29395.lakermmtao08.cox.net@dolphin.local.net> for ; Wed, 24 Nov 2004 20:00:45 -0500 Received: from localhost.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with ESMTP id iAP10kTh001843 for ; Wed, 24 Nov 2004 19:00:46 -0600 (CST) (envelope-from conrads@cox.net) From: "Conrad J. Sabatier" To: freebsd-current@freebsd.org In-Reply-To: <20041120012134.GF20068@dragon.nuxi.com> References: <20041118101356.53ed3f78@dolphin.local.net> <20041120012134.GF20068@dragon.nuxi.com> Content-Type: text/plain Organization: A Rag-Tag Band of Drug-Crazed Hippies Date: Wed, 24 Nov 2004 19:00:41 -0600 Message-Id: <1101344441.1174.8.camel@dolphin.local.net> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Re: usr.bin/lex/lib object files not being placed under MAKEOBJDIRPREFIX X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: conrads@cox.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 01:00:48 -0000 On Fri, 2004-11-19 at 17:21 -0800, David O'Brien wrote: > On Thu, Nov 18, 2004 at 10:13:56AM -0600, Conrad J. Sabatier wrote: > > Noticed this during a cvs update today: > > dolphin:root:/usr/src/usr.bin# cvs -R update > > ? lex/lib/.depend > > ? lex/lib/libln.a > > ? lex/lib/libmain.o > > ? lex/lib/libyywrap.o > > How did you build your system? At one time you maybe cd'ed into > usr.bin/lex and just typed 'make' without 'make obj'? > > The fix is to: > > rm -rf /usr/obj/* > cd /usr/src > make cleandir > make buildworld > cvs -q up > > and you shouldn't see this again. This is very odd. I cleaned up the src tree, and after another buildworld, these files are back again. I have no idea why. -- Conrad J. Sabatier -- conrads@cox.net -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 03:46:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 626C616A4CF for ; Thu, 25 Nov 2004 03:46:21 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5587843D6D for ; Thu, 25 Nov 2004 03:46:17 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: by rproxy.gmail.com with SMTP id 34so56875rns for ; Wed, 24 Nov 2004 19:46:13 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references; b=hViz4knaiCY3ktGw4LAkrloddDO8AB6htjo4wISfd9UWeLRLq7cNJ0SLZkV5m/HiTsRwJvMPgecnmPmV0rkO/Va+kdKDe6kjpDPfTZXtd6KWiGDM+E9TNJHu2/fe6QRChzYhQMSAnt+4pw9ZzQYKbh+vGN/ZaIFS+ARbhelK4kA= Received: by 10.38.179.47 with SMTP id b47mr426756rnf; Wed, 24 Nov 2004 19:46:13 -0800 (PST) Received: by 10.38.8.31 with HTTP; Wed, 24 Nov 2004 19:46:13 -0800 (PST) Message-ID: Date: Thu, 25 Nov 2004 11:46:13 +0800 From: Jiawei Ye To: Kris Kennaway , freebsd-current@freebsd.org In-Reply-To: <20041124212855.GA32463@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_152_4680227.1101354373253" References: <20041124212855.GA32463@xor.obsecurity.org> Subject: Re: Memory modified after free: Most recently used by acpica X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jiawei Ye List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 03:46:21 -0000 ------=_Part_152_4680227.1101354373253 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline On Wed, 24 Nov 2004 13:28:55 -0800, Kris Kennaway wrote: > This happens on fresh 6.0 if I boot with acpi enabled (but not with > acpi compiled out of the kernel). > > Kris Same here, with my acpidump attached. Jiawei -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming ------=_Part_152_4680227.1101354373253 Content-Type: application/octet-stream; name="output.dat" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="output.dat" RFNEVK42AAABe0lOVEVMAEJST0tETEVHABAAAE1TRlQNAAABCEFQSUMKABQNXF9QSUMBcGhBUElD EBNcX1BSX1uDC0NQVTEBEAgAAAYIXF9TMF8SCgQKAAoACgAKAAhcX1MxXxIKBAoBCgAKAAoACFxT UzNfEgoECgUKAAoACgAIXF9TNF8SCgQKBgoACgAKAAhcX1M1XxIKBAoHCgAKAAoAFEEFTUNUSAKg CZWHaIdppAoAcodoCgFgCEJVRjARAmAIQlVGMRECYHBoQlVGMHBpQlVGMaIbYHZgoBKTg4hCVUYw YACDiEJVRjFgAKEDpACkARCDNANcX1NCX1uCGVBXUkIIX0hJRAxB0AwMFAlfU1RBAKQKC1uCjysD UENJMAhfSElEDEHQCgMIX1VJRAoBCF9BRFIKAAhfQkJOCgAUFFVTWEQAoAhPU0ZMpAoCoQSkCgMI Q1JTXxFGCgqiiA0AAgwAAAAAAP8AAAAAAUcB+Az4DAEIiA0AAQwDAAAAAPcMAAD4DIgNAAEMAwAA AA3//wAAAPOHFwAADAMAAAAAAAAKAP//CwAAAAAAAAACAIcXAAAMAwAAAAAAAAwA//8NAAAAAAAA AAIAhxcAAAwDAAAAAAAAACD//9//AAAAAAAA4N+HFwAADAMAAAAAABDg/v//3/8AAAAAAPD/AHkA W4BTS1BEAgreCgJbgRlTS1BEAQAIU1BMVgNXMkZHAgACUlRDWAFbgFRNRU0CCmMKAVuBC1RNRU0B VE9NUggIVE9NXwoAFCxNREVUAKAFVE9NX6EaoBBGTEFHeVRPTVIKGVRPTV+hB6QMAAAAIKRUT01f FBFURkNTAHRNREVUC8B/YKRgCEZMQUcKAQhPU0ZMCgAUTQpfSU5JAFwvA19TQl9QQ0kwSU9EVKAn TUNUSFxfT1NfDU1pY3Jvc29mdCBXaW5kb3dzIE5UAHAKAE9TRkyhTgagJE1DVEhcX09TXw1NaWNy b3NvZnQgV2luZG93cwBwCgFPU0ZMoUYEoDpNQ1RIXF9PU18NTWljcm9zb2Z0IFdpbmRvd3NNRTog TWlsbGVubml1bSBFZGl0aW9uAHAKAk9TRkyhCHAKA09TRkwUEl9SRUcCoAuTaAoCcGlGTEFHFDhf Q1JTAIpDUlNfCnZUTUVNikNSU18KglRMRU5wTURFVFRNRU10DAAAwP5UTUVNVExFTqRDUlNfFBhf UFJUAKAKQVBJQ6RQSUMyoQakUElDMwhQSUMyEkEICRINBAz//x8ACgAKAAoSEg0EDP//HwAKAQoA ChESDQQM//8dAAoACgAKEBINBAz//x0ACgEKAAoTEg0EDP//HQAKAgoAChISDQQM//8dAAoDCgAK FxINBAz//wEACgAKAAoQEg0EDP//AQAKAQoAChESDQQM//8CAAoACgAKEAhQSUMzEkkMCRIVBAz/ /x8ACgBcLl9TQl9MTktDCgASFQQM//8fAAoBXC5fU0JfTE5LQgoAEhUEDP//HQAKAFwuX1NCX0xO S0EKABIVBAz//x0ACgFcLl9TQl9MTktECgASFQQM//8dAAoCXC5fU0JfTE5LQwoAEhUEDP//HQAK A1wuX1NCX0xOS0gKABIVBAz//wEACgBcLl9TQl9MTktBCgASFQQM//8BAAoBXC5fU0JfTE5LQgoA EhUEDP//AgAKAFwuX1NCX0xOS0EKAFuCQQVVU0IxCF9BRFIMAAAdABQUVVNYRACgCE9TRkykCgKh BKQKAwhfUFJXEgYCCgMKAxAfXF9HUEUUGF9MMDMAhlwvA19TQl9QQ0kwVVNCMQoCW4JBBVVTQjII X0FEUgwBAB0AFBRVU1hEAKAIT1NGTKQKAqEEpAoDCF9QUlcSBgIKBAoDEB9cX0dQRRQYX0wwNACG XC8DX1NCX1BDSTBVU0IyCgJbgkEFVVNCMwhfQURSDAIAHQAUFFVTWEQAoAhPU0ZMpAoCoQSkCgMI X1BSVxIGAgoMCgMQH1xfR1BFFBhfTDBDAIZcLwNfU0JfUENJMFVTQjMKAluCO0VIQ0kIX0FEUgwH AB0ACF9QUlcSBgIKDQoDEB9cX0dQRRQYX0wwRACGXC8DX1NCX1BDSTBFSENJCgJbgkRESUNIQghf QURSDAAAHgAUCV9TMUQApAoAFAlVU1hEAKQKABQJX1M0RACkCgMUGF9QUlQAoApBUElDpFBJQzCh BqRQSUMxCFBJQzASRRcbEgsEC///CgAKAAoQEgsEC///CgEKAAoREgsEC///CgIKAAoSEgsEC/// CgMKAAoTEg0EDP//AQAKAAoAChESDQQM//8BAAoBCgAKEhINBAz//wEACgIKAAoTEg0EDP//AQAK AwoAChASDQQM//8CAAoACgAKEhINBAz//wIACgEKAAoTEg0EDP//AgAKAgoAChASDQQM//8CAAoD CgAKERINBAz//wMACgAKAAoTEg0EDP//AwAKAQoAChASDQQM//8DAAoCCgAKERINBAz//wMACgMK AAoSEg0EDP//BQAKAAoAChESDQQM//8FAAoBCgAKEhINBAz//wUACgIKAAoTEg0EDP//BQAKAwoA ChASDQQM//8EAAoACgAKEBINBAz//wQACgEKAAoREg0EDP//BAAKAgoAChISDQQM//8EAAoDCgAK ExINBAz//wgACgAKAAoUEg0EDP//DQAKAAoAChUSDQQM//8NAAoBCgAKFghQSUMxEk0kGxITBAv/ /woAXC5fU0JfTE5LQQoAEhMEC///CgFcLl9TQl9MTktCCgASEwQL//8KAlwuX1NCX0xOS0MKABIT BAv//woDXC5fU0JfTE5LRAoAEhUEDP//AQAKAFwuX1NCX0xOS0IKABIVBAz//wEACgFcLl9TQl9M TktDCgASFQQM//8BAAoCXC5fU0JfTE5LRAoAEhUEDP//AQAKA1wuX1NCX0xOS0EKABIVBAz//wIA CgBcLl9TQl9MTktDCgASFQQM//8CAAoBXC5fU0JfTE5LRAoAEhUEDP//AgAKAlwuX1NCX0xOS0EK ABIVBAz//wIACgNcLl9TQl9MTktCCgASFQQM//8DAAoAXC5fU0JfTE5LRAoAEhUEDP//AwAKAVwu X1NCX0xOS0EKABIVBAz//wMACgJcLl9TQl9MTktCCgASFQQM//8DAAoDXC5fU0JfTE5LQwoAEhUE DP//BQAKAFwuX1NCX0xOS0IKABIVBAz//wUACgFcLl9TQl9MTktDCgASFQQM//8FAAoCXC5fU0Jf TE5LRAoAEhUEDP//BQAKA1wuX1NCX0xOS0EKABIVBAz//wQACgBcLl9TQl9MTktBCgASFQQM//8E AAoBXC5fU0JfTE5LQgoAEhUEDP//BAAKAlwuX1NCX0xOS0MKABIVBAz//wQACgNcLl9TQl9MTktE CgASFQQM//8IAAoAXC5fU0JfTE5LRQoAEhUEDP//DQAKAFwuX1NCX0xOS0YKABIVBAz//w0ACgFc Ll9TQl9MTktHCgAUDl9QUlcApBIGAgoLCgQQH1xfR1BFFBhfTDBCAIZcLwNfU0JfUENJMElDSEIK AluCTa1TQlJHCF9BRFIMAAAfAAhcLl9TQl9JUFJTEQsKCDAj+NwYOHkACFwuX1NCX1BSU0ERCwoI MCP43Bg4eQAIXC5fU0JfUFJTQhELCggwI/jcGDh5AAhcLl9TQl9QUlNDEQsKCDAj+NwYOHkACFwu X1NCX1BSU0QRCwoIMCP43Bg4eQAIXC5fU0JfUFJTRRELCggwI/jcGDh5AAhcLl9TQl9QUlNGEQsK CDAj+NwYOHkACFwuX1NCX1BSU0cRCwoIMCP43Bg4eQAIXC5fU0JfUFJTSBELCggwI/jcGDh5AFuA UElYMAIKYAoEW4BQSVgxAgpoCgRbgExQQzACCuAKCFuATFBDMQIK7AoCEEBnXF9TQl9bgSlcLwRf U0JfUENJMFNCUkdQSVgwAVBJUkEIUElSQghQSVJDCFBJUkQIW4EpXC8EX1NCX1BDSTBTQlJHUElY MQFQSVJFCFBJUkYIUElSRwhQSVJICFuBRAlcLwRfU0JfUENJMFNCUkdMUEMwAUxQQ0EDAAFMUENC AwABTFBMUAIAAkxQRkQBAANMUFNCAgABTFBNRAFMUE1TAgACAAhHRU4xEENBRU4BQ0JFTgFMUEVO AUZERU4BU0JFTgFNREVOAU1TRU4BQURFTgFHTUxFAUdNSEUBS0JFTgFNQ0VOAUNGMUUBQ0YyRQEA AluBGlwvBF9TQl9QQ0kwU0JSR0xQQzEBR0VOMhAIQlVGQREJCgYjAIAYeQCLQlVGQQoBSVJBMAhJ UTA1EQsKCDAjIAAYOHkACElRMTARCwoIMCMABBg4eQAISVExMRELCggwIwAIGDh5AAhJUTEyEQsK CDAjABAYOHkAW4JICExOS0EIX0hJRAxB0AwPCF9VSUQKARQZX1NUQQB7UElSQQqAYKAFYKQKCaEE pAoLFAtfUFJTAKRQUlNBFBFfRElTAH1QSVJBCoBQSVJBFBtfQ1JTAHtQSVJBCg9geQoBYElSQTCk QlVGQRQcX1NSUwGLaAoBSVJBX4JJUkFfYHZgcGBQSVJBW4JICExOS0IIX0hJRAxB0AwPCF9VSUQK AhQZX1NUQQB7UElSQgqAYKAFYKQKCaEEpAoLFAtfUFJTAKRQUlNCFBFfRElTAH1QSVJCCoBQSVJC FBtfQ1JTAHtQSVJCCg9geQoBYElSQTCkQlVGQRQcX1NSUwGLaAoBSVJBX4JJUkFfYHZgcGBQSVJC W4JICExOS0MIX0hJRAxB0AwPCF9VSUQKAxQZX1NUQQB7UElSQwqAYKAFYKQKCaEEpAoLFAtfUFJT AKRQUlNDFBFfRElTAH1QSVJDCoBQSVJDFBtfQ1JTAHtQSVJDCg9geQoBYElSQTCkQlVGQRQcX1NS UwGLaAoBSVJBX4JJUkFfYHZgcGBQSVJDW4JJDUxOS0QIX0hJRAxB0AwPCF9VSUQKBBQZX1NUQQB7 UElSRAqAYKAFYKQKCaEEpAoLFEwFX1BSUwCgFVwvA19TQl9QQ0kwT1NGTKRQUlNEoT6gDZNQSVJE CoWkSVEwNaANk1BJUkQKiqRJUTEwoA2TUElSRAqLpElRMTGgDZNQSVJECoykSVExMqRQUlNEFBFf RElTAH1QSVJECoBQSVJEFBtfQ1JTAHtQSVJECg9geQoBYElSQTCkQlVGQRQcX1NSUwGLaAoBSVJB X4JJUkFfYHZgcGBQSVJEW4JICExOS0UIX0hJRAxB0AwPCF9VSUQKBRQZX1NUQQB7UElSRQqAYKAF YKQKCaEEpAoLFAtfUFJTAKRQUlNFFBFfRElTAH1QSVJFCoBQSVJFFBtfQ1JTAHtQSVJFCg9geQoB YElSQTCkQlVGQRQcX1NSUwGLaAoBSVJBX4JJUkFfYHZgcGBQSVJFW4JICExOS0YIX0hJRAxB0AwP CF9VSUQKBhQZX1NUQQB7UElSRgqAYKAFYKQKCaEEpAoLFAtfUFJTAKRQUlNGFBFfRElTAH1QSVJG CoBQSVJGFBtfQ1JTAHtQSVJGCg9geQoBYElSQTCkQlVGQRQcX1NSUwGLaAoBSVJBX4JJUkFfYHZg cGBQSVJGW4JICExOS0cIX0hJRAxB0AwPCF9VSUQKBxQZX1NUQQB7UElSRwqAYKAFYKQKCaEEpAoL FAtfUFJTAKRQUlNHFBFfRElTAH1QSVJHCoBQSVJHFBtfQ1JTAHtQSVJHCg9geQoBYElSQTCkQlVG QRQcX1NSUwGLaAoBSVJBX4JJUkFfYHZgcGBQSVJHCFBSVTIRCwoIMCMgABg4eQBbgkkNTE5LSAhf SElEDEHQDA8IX1VJRAoIFBlfU1RBAHtQSVJICoBgoAVgpAoJoQSkCgsUTAVfUFJTAKAVXC8DX1NC X1BDSTBPU0ZMpFBSU0ihPqANk1BJUkgKhaRJUTA1oA2TUElSSAqKpElRMTCgDZNQSVJICoukSVEx MaANk1BJUkgKjKRJUTEypFBSU0gUEV9ESVMAfVBJUkgKgFBJUkgUG19DUlMAe1BJUkgKD2B5CgFg SVJBMKRCVUZBFBxfU1JTAYtoCgFJUkFfgklSQV9gdmBwYFBJUkhbgkMJU1lTUghfSElEDEHQDAIU El9TVEEAoAhPU0ZMpAoPpAoACElPUkcRTgUKWksQABBLIgAeS0QAHEtiAAJLZQALS3IADkuAAAFL hAADS4gAAUuMAANLkAAQS6IAHkvgABBLkAIIRwHwA/ADAAJHAdAE0AQAAkcBAAQABABARwEACAAI AIB5ABQLX0NSUwCkSU9SR1uCQA1cLl9TQl9NRU1fCF9ISUQMQdAMARQdX1NUQQCgE1wvA19TQl9Q Q0kwT1NGTKQKD6QKAAhNRU0xEUYGCmKGCQABAAAAAAAACgCGCQABACANAAZgAACGCQAAAAAPAAAA AQCGCQABAAAQAAAA8B+GCQAAAADA/gAQAACGCQAAAADg/gAQAACGCQABAACw/wAAEACGCQAAAADw /wAAEAB5ABQvX0NSUwCKTUVNMQosVE9QMXRcLwNfU0JfUENJME1ERVQMAAAQAFRPUDGkTUVNMVuC NlBJQ18IX0hJRAtB0BQSX1NUQQCgCE9TRkykCg+kCgAIX0NSUxEQCg1LIAACS6AAAiIEAHkAW4I1 RE1BRAhfSElEDEHQAgAIX0NSUxEgCh0qEARLAAAQS4EAA0uHAAFLiQADS48AAUvAACB5AFuCIVRN Ul8IX0hJRAxB0AEACF9DUlMRDAoJS0AABCIBAHkAW4IhUlRDXwhfSElEDEHQCwAIX0NSUxEMCglL cAACIgABeQBbgh5TUEtSCF9ISUQMQdAIAAhfQ1JTEQkKBkthAAF5AFuCIUNPUFIIX0hJRAxB0AwE CF9DUlMRDAoJS/AAECIAIHkAW4BQU1JHAAzC4g8ACgFbgRJQU1JHAVBLMkUBUE0yRQEABluCQgZQ UzJNCF9ISUQMQdAPExQUX1NUQQCgCFBNMkWkCg+hBKQKAAhNMlIwEQgKBSIAEHkACE0yUjEREAoN S2AAAUtkAAEiABB5ABQYX0NSUwCgClBLMkWkTTJSMKEGpE0yUjFbgkUEUFMySwhfSElEDEHQAwMI X0NJRAxB0AMLFBRfU1RBAKAIUEsyRaQKD6EEpAoACF9DUlMREAoNS2AAAUtkAAEiAgB5AAguUFMy S19QUlcSBgIKGAoEECNcX0dQRRQcX0wxOACGXC8EX1NCX1BDSTBTQlJHUFMySwoCCFNQSU8KLluA V0lOMQFTUElPCgJbgRBXSU4xAUlORFgIREFUQQhbhkMLSU5EWERBVEEBABBDRkdfCAAgTEROXwgA QBRBQ1RSAUFDVDEBQUNUMgEABQBIF0lPQUgISU9BTAhJT0VICElPRUwIAEAGSU5UUggACElOVDEI AAhETUNICABIJUdQNDAIAEgPUkdFMAhSR0UxCFJHRTIIUkdFMwhSR0U0CABIBU9QVDEIT1BUMghP UFQzCE9QVDQIT1BUNQhPUFQ2CE9QVDcIT1BUOAhPUFQ5CE9QVEEIW4BIV01UAQuVAgoCW4EQSFdN VAFIV0lOCEhXRFQIW4ZLCkhXSU5IV0RUAQBAIEhXNDAISFc0MQhIVzQyCEhXNDMISFc0NAgACEhX NDYISFc0NwhIVzQ4CEhXNDkISFc0QQhIVzRCCEhXNEMISFc0RAhIVzRFCEhXNEYISFc1MAhIVzUx CEhXNTIISFc1MwhIVzU0CEhXNTUISFc1NghIVzU3CEhXNTgISFc1OQhIVzVBCEhXNUIISFc1QwhI VzVECEhXNUUISFc1RggUFEVORkcAcAqHSU5EWHAKh0lORFgUDUVYRkcAcAqqSU5EWBQMREtQTQBE V0tFCuwUDERNUE0ARFdLRQrcFCZEV0tFAUVORkdwCgpMRE5fe09QVDdoT1BUN3AK/09QVDRFWEZH CExERkQKAAhMRFUxCgIITERVMgoDCExESVIKBghMRExQCgEITERHTQoHCExETUQKB1uCRQlGREMw CF9ISUQMQdAHABQYX1NUQQCgDkZEU1SkR1NUQUxERkSkCgAUJl9ESVMARERJU0xERkRFTkZHcExE RkRMRE5fcAoERE1DSEVYRkcUC19DUlMApEZDUlMUC19QUlMApEZQUlMULF9TUlMBcAFGREVOREVO QkxERkRFTkZHcExERkRMRE5fcAoCRE1DSEVYRkdbgkkLVUFSMQhfSElEDEHQBQEIX1VJRAoBFBhf U1RBAKAOVTFTVKRHU1RBTERVMaQKABQOX0RJUwBERElTTERVMRQTX0NSUwCkUENSU0xEVTEKAQoI FEkFX1NSUwFQU1JTaExEVTFwAUNBRU5FTkZHoCCTSU9BSAoDoA6TSU9BTAr4cABMUENBoQhwCgdM UENBoRmgDpNJT0FMCvhwAUxQQ0GhCHAKBUxQQ0FFWEZHFAtfUFJTAKRDMVBSW4JADlVBUjIUMF9I SUQARU5GR3BMRFUyTEROX3tPUFQyCjhgRVhGR6AIYKQMQdAFEKEHpAxB0AUBCF9VSUQKAhQYX1NU QQCgDlUyU1SkR1NUQUxEVTKkCgAUDl9ESVMARERJU0xEVTIUE19DUlMApFBDUlNMRFUyCgEKCBRJ BV9TUlMBUFNSU2hMRFUycAFDQkVORU5GR6Agk0lPQUgKA6AOk0lPQUwK+HAATFBDQqEIcAoHTFBD QqEZoA6TSU9BTAr4cAFMUENCoQhwCgVMUENCRVhGRxQLX1BSUwCkQzJQUluCTBBJUkRBCF9ISUQM QdAFEBQYX1NUQQCgDklSU1SkR1NUQUxESVKkCgAUDl9ESVMARERJU0xESVIUSwpfQ1JTAAhCVUY2 ERAKDUcBAAAAAAgIIgAAeQCMQlVGNgoCSU9MT4xCVUY2CgNJT0hJjEJVRjYKBElPUkyMQlVGNgoF SU9SSItCVUY2CglJUlFNRU5GR3BMRElSTEROX6ATQUNUUnAKmElPTE9wCgJJT0hJoQ9wCgBJT0xP cAoASU9ISXBJT0xPSU9STHBJT0hJSU9SSHkKAUlOVFJJUlFNRVhGR6RCVUY2FA9fU1JTAVBTUlNo TERJUghfUFJTERIKDzBHAZgCmAIICCIYDjh5AFuCQwxMUFRfCF9ISUQMQdAEABQ7X1NUQQBFTkZH cExETFBMRE5fe09QVDEKAmBFWEZHoBB9YHuATFBTVAAKAQAApAChCqRHU1RBTERMUBQOX0RJUwBE RElTTERMUBQTX0NSUwCkUENSU0xETFAKAQoIFEcEX1NSUwFQU1JTaExETFBwAUxQRU5FTkZHoCCT SU9BSAoDoA6TSU9BTAp4cABMUExQoQhwCgJMUExQoQdwAUxQTFBFWEZHFAtfUFJTAKRMUFBSW4JI C0VDUF8IX0hJRAxB0AQBFDRfU1RBAEVORkdwTERMUExETl97T1BUMQoCYEVYRkegEJBgTFBTVKRH U1RBTERMUKEDpAAUDl9ESVMARERJU0xETFAUD19DUlMApEVDUlNMRExQFEcEX1NSUwFFU1JTaExE TFBwAUxQRU5FTkZHoCCTSU9BSAoDoA6TSU9BTAp4cABMUExQoQhwCgJMUExQoQdwAUxQTFBFWEZH FAtfUFJTAKRFUFJTW4JKGUdBTUUIX0hJRAxB0LAvFD5fU1RBAEVORkdwTERHTUxETl+gDEFDVDFF WEZHpAoPoR1ySU9BSElPQUxgoAlgRVhGR6QKDaEHRVhGR6QAFB1fRElTAEVORkdwTERHTUxETl9w AEFDVDFFWEZHFEUJX0NSUwAIQlVGNhENCgpHAQAAAAAICHkAjEJVRjYKAklPTE+MQlVGNgoDSU9I SYxCVUY2CgRJT1JMjEJVRjYKBUlPUkhFTkZHcExER01MRE5foBaTSU9BTAoAcAoASU9MT3AKAklP SEmhD3AKCElPTE9wCgJJT0hJcElPTE9JT1JMcElPSElJT1JIRVhGR6RCVUY2CF9QUlMRGAoVMEcB AAIAAggIMEcBCAIIAggIOHkAFEgHX1NSUwGMaAoCSU9MT4xoCgNJT0hJRU5GR3BMREdNTEROX6AW k0lPTE8KAHAKAklPQUhwCgBJT0FMoQ9wCgJJT0FIcAoISU9BTKAUk0lPQUwKAHABR01MRXAAR01I RaENcABHTUxFcAFHTUhFcAFBQ1QxRVhGR1uCSBxNSURJCF9ISUQMQdCwBhQ+X1NUQQBFTkZHcExE TURMRE5foAxBQ1QyRVhGR6QKD6EdcklPRUhJT0VMYKAJYEVYRkekCg2hB0VYRkekABQdX0RJUwBF TkZHcExETURMRE5fcABBQ1QyRVhGRxRJCV9DUlMACEJVRjYREAoNRwEAAAAAAgIiAAB5AIxCVUY2 CgJJT0xPjEJVRjYKA0lPSEmMQlVGNgoESU9STIxCVUY2CgVJT1JIi0JVRjYKCUlSUU1FTkZHcExE TURMRE5fcElPRUhJT0hJcElPRUxJT0xPcElPTE9JT1JMcElPSElJT1JIeQoBSU5UUklSUU1FWEZH pEJVRjYIX1BSUxE2CjMwRwEwAzADAgIiuAwwRwEAAwADAgIiuAwwRwEQAxADAgIiuAwwRwEgAyAD AgIiuAw4eQAURAhfU1JTAYxoCgJJT0xPjGgKA0lPSEmLaAoJSVJRTUVORkdwTERNRExETl9wSU9I SUlPRUhwSU9MT0lPRUygLZGTSU9MTwowk0lPTE8KAKAOk0lPTE8KMHAATFBNRKEHcAFMUE1EcAFN REVOgklSUU1gdGAKAUlOVFJwAUFDVDJFWEZHCEZEU1QKAAhVMVNUCgAIVTJTVAoACElSU1QKAAhM UFNUCgAUQAdJT0RUAKAUkpNHU1RBTERGRAoAcAoBRkRTVKAUkpNHU1RBTERVMQoAcAoBVTFTVKAU kpNHU1RBTERVMgoAcAoBVTJTVKAUkpNHU1RBTERJUgoAcAoBSVJTVKAUkpNHU1RBTERMUAoAcAoB TFBTVBQ4R1NUQQFFTkZHcGhMRE5foAlBQ1RScAoPYKEXoA99SU9BSElPQUwAcAoNYKEFcAoAYEVY RkekYBQaRERJUwFFTkZHcGhMRE5fcABBQ1RSRVhGRxQaREVOQgFFTkZHcGhMRE5fcAFBQ1RSRVhG RxRNClBDUlMDjFBCVUYKAklPTE+MUEJVRgoDSU9ISYtQQlVGCgJJT0hMi1BCVUYKBElPUkyMUEJV RgoGQUxNToxQQlVGCgdMRU5HjFBCVUYKCUlSUUxFTkZHcGhMRE5fcElPQUhJT0hJcElPQUxJT0xP cElPSExJT1JMcGlBTE1OoA+TSU9MTwq8cAoETEVOR6EHcGpMRU5HcAFgeWBJTlRSSVJRTEVYRkek UEJVRhRDBVBTUlMCjGgKAlBPTEKMaAoDUE9IQoxoCglQSVJRRU5GR3BpTEROX3BQT0xCSU9BTHBQ T0hCSU9BSIJQSVJRYHRgCgFJTlRScAFBQ1RSRVhGRxRID0VDUlMBjEVCVUYKAkVQTE+MRUJVRgoD RVBISYtFQlVGCgJFUEhMi0VCVUYKBEVQUkyLRUJVRgoGQUxNMYtFQlVGCgpFNExPi0VCVUYKDEU0 UkyLRUJVRgoRRUlSUYtFQlVGChRFRE1BRU5GR3BoTEROX3BJT0FIRVBISXBJT0FMRVBMT3BFUEhM RVBSTHJFUEhMCwAERTRMT3BFNExPRTRSTKARk0VQSEwLvANwCwEEQUxNMaEJcAsBCEFMTTFwAWBw SU5UUmF5YGFFSVJRcERNQ0hhoAyUYQoDcAoARURNQaELcAFgeWBhRURNQUVYRkekRUJVRhRIB0VT UlMCjGgKAkxPRVCMaAoDSElFUItoChFJUlFFi2gKFERNQUVFTkZHcGlMRE5fcExPRVBJT0FMcEhJ RVBJT0FIgklSUUVgdGAKAUlOVFKgE0RNQUWCRE1BRWB0YAoBRE1DSKEIcAoERE1DSHABQUNUUkVY RkcIQ05CRhEFCgL4AxRNBFVBQlMBRU5GR3BoTEROX4xDTkJGCgBJT0xPjENOQkYKAUlPSEmLQ05C RgoASU9BRHBJT0FMSU9MT3BJT0FISU9ISUVYRkekSU9BRAhDU0NQCgBbhDBVUlAxAQAAFAtfU1RB AKRDU0NQFA1fT05fAHAKAUNTQ1AUDV9PRkYAcAoAQ1NDUFuEMFVSUDIBAAAUC19TVEEApENTQ1AU DV9PTl8AcAoBQ1NDUBQNX09GRgBwCgBDU0NQW4QwRkREUAAAABQLX1NUQQCkQ1NDUBQNX09OXwBw CgFDU0NQFA1fT0ZGAHAKAENTQ1BbhDBMUFRQAAAAFAtfU1RBAKRDU0NQFA1fT05fAHAKAUNTQ1AU DV9PRkYAcAoAQ1NDUAhGQ1JTESMKIEcB8gPyAwECRwH0A/QDAQJHAfcD9wMBASJAACoEAHkACFBC VUYREAoNRwEAAAAAAQgiAQB5AAhFQlVGERsKGEcBeAN4AwEIRwF4B3gHAQQigAAqAAB5AAhGUFJT ESYKIzEARwHyA/IDAQJHAfQD9AMBAkcB9wP3AwEBIkAAKgQAOHkACEMxUFIRRAQKQDEARwH4A/gD BAgiEAAwRwH4A/gDBAgiGAwwRwH4AvgCBAgiGAwwRwHoA+gDBAgiGAwwRwHoAugCBAgiGAw4eQAI QzJQUhFEBApAMQBHAfgC+AIECCIIADBHAfgC+AIECCIYDDBHAfgD+AMECCIYDDBHAegD6AMECCIY DDBHAegC6AIECCIYDDh5AAhMUFBSETcKNDEARwF4A3gDAQgigAAwRwF4A3gDAQgioAAwRwF4AngC AQgioAAwRwG8A7wDAQQioAA4eQAIRVBSUxFJCgqlMQBHAXgDeAMBCEcBeAd4BwEEIoAAKgIAMEcB eAN4AwEIRwF4B3gHAQQioAAqCwAwRwF4AngCAQhHAXgGeAYBBCKgACoLADBHAbwDvAMBBEcBvAe8 BwEEIqAAKgsAMEcBeAN4AwEIRwF4B3gHAQQioAAqAAAwRwF4AngCAQhHAXgGeAYBBCKgACoAADBH AbwDvAMBBEcBvAe8BwEEIqAAKgAAOHkACE5BVEESBwEMAQAfAFuCR9JJREUwCF9BRFIMAQAfAAhS RUdGCgEUEl9SRUcCoAuTaAoCcGlSRUdGCFRJTTASSAYIEgsECngKtArwC4QDEgoECiMKIQoQCgAS CgQKCwoJCgQKABIOBgpwCkkKNgonChkKDxIOBgoACgEKAgoBCgIKARIOBgoACgAKAAoBCgEKARIK BAoECgMKAgoAEgoECgIKAQoACgAIVE1EMBEDChSKVE1EMAoAUElPMIpUTUQwCgRETUEwilRNRDAK CFBJTzGKVE1EMAoMRE1BMYpUTUQwChBDSE5GW4BDRkcyAgpACiBbgUgKQ0ZHMgNQTVBUBFBTUFQE UE1SSQYAAlNNUFQEU1NQVARTTVJJBgACUFNSSQRTU1JJBAAYUE0zRQFQUzNFAVNNM0UBU1MzRQEA DFBNVVQCAAJQU1VUAgACU01VVAIAAlNTVVQCAAIAQARQTTZFAVBTNkUBU002RQFTUzZFAVBNQ1IB UFNDUgFTTUNSAVNTQ1IBAARQTUFFAVBTQUUBU01BRQFTU0FFAQhHTVBUCgAIR01VRQoACEdNVVQK AAhHTUNSCgAIR1NQVAoACEdTVUUKAAhHU1VUCgAIR1NDUgoAW4JFJUNITjAIX0FEUgoAFEwHX0dU TQB5UFNDUgoBYX1QTUNSYWB5UE1BRQoCY3lQTTZFCgFkfWNkY31QTTNFY2F5UE1QVAoEY31hY2F5 UFNBRQoCY3lQUzZFCgFkfWNkY31QUzNFY2J5UFNQVAoEY31iY2KkR1RNX1BNUklhUE1VVFBTUkli UFNVVGAUThhfU1RNA3BoWzFwaFRNRDB5UE1BRQoCY3lQTTZFCgFkfWNkY31QTTNFY2B5UE1QVAoE Y31gY2B5UFNBRQoCY3lQUzZFCgFkfWNkY31QUzNFY2F5UFNQVAoEY31hY2FwUE1SSUdNUFRwYEdN VUVwUE1VVEdNVVRwUE1DUkdNQ1JwUFNSSUdTUFRwYUdTVUVwUFNVVEdTVVRwUFNDUkdTQ1JTVE1f cEdNUFRQTVJJcEdNVUVgcEdNVVRQTVVUcEdNQ1JQTUNScEdTVUVhcEdTVVRQU1VUcEdTQ1JQU0NS oA17YAoBAHAKAVBNM0WhCHAKAFBNM0WgDXtgCgIAcAoBUE02RaEIcAoAUE02RaAUe2AKBABwCgFQ TUFFcAoAUE02RaEIcAoAUE1BRaANe2EKAQBwCgFQUzNFoQhwCgBQUzNFoA17YQoCAHAKAVBTNkWh CHAKAFBTNkWgFHthCgQAcAoBUFNBRXAKAFBTNkWhCHAKAFBTQUVwR1RGXwoAaUFUQTBwR1RGXwoB akFUQTFbghxEUlYwCF9BRFIKABQPX0dURgCkUkFUQUFUQTBbghxEUlYxCF9BRFIKARQPX0dURgCk UkFUQUFUQTFbgkUlQ0hOMQhfQURSCgEUTAdfR1RNAHlTU0NSCgFhfVNNQ1JhYHlTTUFFCgJjeVNN NkUKAWR9Y2RjfVNNM0VjYXlTTVBUCgRjfWFjYXlTU0FFCgJjeVNTNkUKAWR9Y2RjfVNTM0VjYnlT U1BUCgRjfWJjYqRHVE1fU01SSWFTTVVUU1NSSWJTU1VUYBROGF9TVE0DcGhbMXBoVE1EMHlTTUFF CgJjeVNNNkUKAWR9Y2RjfVNNM0VjYHlTTVBUCgRjfWBjYHlTU0FFCgJjeVNTNkUKAWR9Y2RjfVNT M0VjYXlTU1BUCgRjfWFjYXBTTVJJR01QVHBgR01VRXBTTVVUR01VVHBTTUNSR01DUnBTU1JJR1NQ VHBhR1NVRXBTU1VUR1NVVHBTU0NSR1NDUlNUTV9wR01QVFNNUklwR01VRWBwR01VVFNNVVRwR01D UlNNQ1JwR1NVRWFwR1NVVFNTVVRwR1NDUlNTQ1KgDXtgCgEAcAoBU00zRaEIcAoAU00zRaANe2AK AgBwCgFTTTZFoQhwCgBTTTZFoBR7YAoEAHAKAVNNQUVwCgBTTTZFoQhwCgBTTUFFoA17YQoBAHAK AVNTM0WhCHAKAFNTM0WgDXthCgIAcAoBU1M2RaEIcAoAU1M2RaAUe2EKBABwCgFTU0FFcAoAU1M2 RaEIcAoAU1NBRXBHVEZfCgBpQVRBMnBHVEZfCgFqQVRBM1uCHERSVjAIX0FEUgoAFA9fR1RGAKRS QVRBQVRBMluCHERSVjEIX0FEUgoBFA9fR1RGAKRSQVRBQVRBMxRNE0dUTV8PcP9QSU8wcP9QSU8x cP9ETUEwcP9ETUExcAoQQ0hORqAFUkVHRqEGpFRNRDCgEXtpCiAAfUNITkYKAkNITkZwiYOIVElN MAoBAAFoAAoACgBmcIOIg4hUSU0wCgAAZgBncGdETUEwcGdQSU8woBF7bAogAH1DSE5GCghDSE5G cImDiFRJTTAKAgABawAKAAoAZnCDiIOIVElNMAoAAGYAZ3BnRE1BMXBnUElPMaA+e2kKBwBwamWg C3tpCgIAcmUKAmWgC3tpCgQAcmUKBGVwg4iDiFRJTTAKAwBlAERNQTB9Q0hORgoBQ0hORqA+e2wK BwBwbWWgC3tsCgIAcmUKAmWgC3tsCgQAcmUKBGVwg4iDiFRJTTAKAwBlAERNQTF9Q0hORgoEQ0hO RnBUTUQwWzGkVE1EMBRAI1NUTV8IoAVSRUdGoQakVE1EMHAKAEdNVUVwCgBHTVVUcAoAR1NVRXAK AEdTVVSgRAd7Q0hORgoBAHCJg4hUSU0wCgMAAkRNQTAACgAKAGCgCZRgCgVwCgVgcIOIg4hUSU0w CgQAYABHTVVUfUdNVUUKAUdNVUWgEJRgCgJ9R01VRQoCR01VRaAblGAKBHtHTVVFCv1HTVVFfUdN VUUKBEdNVUWhN6A1fZNQSU8w/5NQSU8wCgAAoCR7lURNQTD/lERNQTAKAABwRE1BMFBJTzB9R01V RQqAR01VRaBEB3tDSE5GCgQAcImDiFRJTTAKAwACRE1BMQAKAAoAYKAJlGAKBXAKBWBwg4iDiFRJ TTAKBABgAEdTVVR9R1NVRQoBR1NVRaAQlGAKAn1HU1VFCgJHU1VFoBuUYAoEe0dTVUUK/UdTVUV9 R1NVRQoER1NVRaE3oDV9k1BJTzH/k1BJTzEKAACgJHuVRE1BMf+URE1BMQoAAHBETUExUElPMX1H U1VFCoBHU1VFoBR7Q0hORgoCAH1HTVVFCiBHTVVFoBR7Q0hORgoIAH1HU1VFCiBHU1VFe4mDiFRJ TTAKAAAEUElPMAAKAAoACgdgcIOIg4hUSU0wCgEAYABhcGFHTVBUoBCVYAoDfUdNVUUKUEdNVUV7 iYOIVElNMAoAAARQSU8xAAoACgAKB2Bwg4iDiFRJTTAKAgBgAGFwYUdTUFSgEJVgCgN9R1NVRQpQ R1NVRQhBVDAxEQoKBwMAAAAAAO8IQVQwMhEKCgcAAAAAAACQCEFUMDMRCgoHAAAAAAAAxghBVDA0 EQoKBwAAAAAAAJEIQVRBMBEDCh0IQVRBMREDCh0IQVRBMhEDCh0IQVRBMxEDCh0IQVRBQhEDCh2M QVRBQgoAQ01EQxRMBUdURkILd0NNREMKOGByYAoIYVsTQVRBQmEKOENNRFh3Q01EQwoHYIxBVEFC cmAKAgBBMDAxjEFUQUJyYAoGAEEwMDVwaENNRFhwaUEwMDFwakEwMDV1Q01EQxRCJEdURl8KcGlb MXAKAENNREMISUQ0OQsADAhJRDU5CgAISUQ1MwoECElENjMLAA8ISUQ4OAsADwhJUkRZCgEIUElP VAoACERNQVQKAKBNBZOHaQsAAotpCmJJVzQ5cElXNDlJRDQ5i2kKaklXNTNwSVc1M0lENTOLaQp+ SVc2M3BJVzYzSUQ2M4tpCnZJVzU5cElXNTlJRDU5i2kKsElXODhwSVc4OElEODhwCqBnoEgFaHAK sGd7Q0hORgoISVJEWaASe0NITkYKEABwUElPMVBJT1ShCnBQSU8wUElPVKAne0NITkYKBACgEntD SE5GChAAcERNQTFETUFUoQpwRE1BMERNQVShKHtDSE5GCgJJUkRZcFBJTzBQSU9UoBJ7Q0hORgoB AHBETUEwRE1BVKBHBJCQe0lENTMKBAB7SUQ4OAsA/wBETUFUcImDiFRJTTAKAwACRE1BVAAKAAoA YaAJlGEKBXAKBWFHVEZCQVQwMX0KQGEAZ6FGBKBDBJB7SUQ2MwsA/wBQSU9Ue4mDiFRJTTAKAAAE UElPVAAKAAoACgNgfQogg4iDiFRJTTAKBwBgAGFHVEZCQVQwMWFnoDhJUkRZe4mDiFRJTTAKAAAE UElPVAAKAAoACgdgfQoIg4iDiFRJTTAKBgBgAGFHVEZCQVQwMWFnoRegFXtJRDQ5CwAEAEdURkJB VDAxCgFnoCSQe0lENTkLAAEAe0lENTkK/wBHVEZCQVQwM3tJRDU5Cv8AZ3BBVEFCWzGkQVRBQhQs UkFUQQGMaAoAQ01ETndDTUROCjhgWxNoCghgUkVUQnBSRVRCWzGkUkVUQluCD1NNQlMIX0FEUgwD AB8AW4IPQUM5XwhfQURSDAUAHwBbghtNQzlfCF9BRFIMBgAfAAhfUFJXEgYCCgUKBAhTTFBTCgBb gkYFU0xQQghfSElEDEHQDA4UHFNCRVYAoAxTTFBThlNMUEIKAqEIhlNMUEIKgBAcXF9HUEUUFV9M MUMAXC8DX1NCX1NMUEJTQkVWCF9QUlcSBgIKHAoEFEcJX1BUUwFwaERCRzigHZCTaAoEk1wvA19T Ql9QQ0kwT1NGTAoCWyILuAugFpNoCgGiEFdBS1NbIQpQcAoBV0FLU3BoXC8DX1NCX1BDSTBTUExW ohBQUzFTWyEKUHAKAVBTMVNwCgFQUzFFcFwvA19TQl9QQ0kwT1NGTFwvA19TQl9QQ0kwVzJGR3AK AVwuX1NCX1NMUFMUTxBfV0FLAXloCgREQkc4oCOTaAoBXC8DX1NCX1BDSTBES1BNXC8DX1NCX1BD STBETVBNoCaQk2gKAVwvA19TQl9QQ0kwUlRDWIZcLl9TQl9QV1JCCgJbIgp4oC1SVENToCeQk2gK A5JcLwNfU0JfUENJMFJUQ1iGXC5fU0JfUFdSQgoCWyIKeKEShlwuX1NCX1BXUkIKAlsiCnhwCgFQ V0JUcAoAUFMxRXAKAFwvA19TQl9QQ0kwVzJGR3AKAFwvA19TQl9QQ0kwUlRDWHAKAFwuX1NCX1NM UFOgNJGTaAoBk2gKA3AK/1NIU1RwCg1TSENNcAoHU01EMHAKXlNNU1ZwCkhTSENScAr/U0hTVFuA UE1TMAELAAgKBFuBHVBNUzABAApSVENTAQAEV0FLUwEACFBXQlQBAAdbgFNNSUUBCzAICghbgRZT TUlFAQAEUFMxRQEAH1BTMVMBABtbgFNXSUcBC3AICgFbgQ1TV0lHAUkxMkMCAAZbgFNNT1YBCwAM CgdbgSZTTU9WAVNIU1QIAAhTSENSCFNIQ00IU01TVghTTUQwCFNNRDEIW4BURU1QAQqACgFbgQtU RU1QAURCRzgIW4BERUIwAQqQCgJbgQtERUIwAkRCRzkQ ------=_Part_152_4680227.1101354373253-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 07:24:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B603216A4CE for ; Thu, 25 Nov 2004 07:24:43 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96E2A43D49 for ; Thu, 25 Nov 2004 07:24:43 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 8417B72DF4; Wed, 24 Nov 2004 23:24:43 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 8173172DCB; Wed, 24 Nov 2004 23:24:43 -0800 (PST) Date: Wed, 24 Nov 2004 23:24:43 -0800 (PST) From: Doug White To: Hogan Whittall In-Reply-To: <20041123182254.GB10721@ninthgate.net> Message-ID: <20041124231627.I2006@carver.gumbysoft.com> References: <20041123182254.GB10721@ninthgate.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Random panics with 5.3-REL, SMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 07:24:43 -0000 On Tue, 23 Nov 2004, Hogan Whittall wrote: > Dell PE6450 server, 4xP3-700 Xeon, 4gb ram, system disks reside on > a 2 disk RAID1 attached to a MegaRAID controller. Wireless is a > D-Link DWL-G520-B, also has Intel Pro/100 ethernet. For the record, I have a PE6300 (4x500MHz) I'm testing a fix for panics of the form panic: Previous IPI is stuck if thats one of the "random panics" you're seeing. The thread "number of CPUs and IPI panic" in -current has details, and a temporary patch is available from http://people.freebsd.org/~ups/ipi4_patch I believe this patch will apply to both RELENG_5 and -CURRENT, for now. I was having a problem with random resets (no panic, just reset) and traced it to a broken cpu0. Replacing it made the resets go away. If you have room you may want to install RedHat or Windows on another partition, load up the OpenManage tools, and inspect the system event log for anything peculiar. If you've never run this before then you may need to clear the event log for it to log any new events. If you have a DRAC card in the machine you can use that too. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 07:36:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9092216A4CE; Thu, 25 Nov 2004 07:36:02 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7123A43D2D; Thu, 25 Nov 2004 07:36:02 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 63B6F72DD4; Wed, 24 Nov 2004 23:36:02 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 5C01472DCB; Wed, 24 Nov 2004 23:36:02 -0800 (PST) Date: Wed, 24 Nov 2004 23:36:02 -0800 (PST) From: Doug White To: Randy Bush In-Reply-To: <16804.64917.872924.733444@ran.psg.com> Message-ID: <20041124232820.J2006@carver.gumbysoft.com> References: <20041123182254.GB10721@ninthgate.net> <16804.64917.872924.733444@ran.psg.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: Random panics with 5.3-REL, SMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 07:36:02 -0000 On Wed, 24 Nov 2004, Randy Bush wrote: > > - Using a serial console to the box, you can reliably gather information > > without the core dump mechanism working. > > i caught one, but the rest happened and reboot's beastie wiped the console > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x41959c25 Thats a wierd address. If I didn't know better, I'd say that there's a MSB flip in there (4+8=c in hex). A backtrace would be interesting to look at. > fault code = supervisor write, page not present > instruction pointer = 0x8:0xc04e813a > stack pointer = 0x10:0xe784d978 > frame pointer = 0x10:0xe784d994 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 68301 (sshd) > trap number = 12 > panic: page fault > cpuid = 0 > boot() called on cpu#0 > Uptime: 9h29m10s > Cannot dump. No dump device defined. Looks like you just need to set 'dumpdev' in rc.conf. What is your boot device and swap partition(s)? > Automatic reboot in 15 seconds - press a key on the console to abort > Rebooting... > cpu_reset called on cpu#0 > cpu_reset: Stopping other CPUs > > since then, i installed a kernel with debugging symbols (blush), but > have yet to get a usable savecore and the beastie got me too. Set 'beastie_disable="YES"' in /boot/loader.conf to stop that from happening. :) if you turn on session logging in your comm program it should capture the output before it scrolls off. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 07:37:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 372BD16A4CE for ; Thu, 25 Nov 2004 07:37:10 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EB1143D4C for ; Thu, 25 Nov 2004 07:37:10 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 13E6A72DF8; Wed, 24 Nov 2004 23:37:10 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 1208072DD4; Wed, 24 Nov 2004 23:37:10 -0800 (PST) Date: Wed, 24 Nov 2004 23:37:10 -0800 (PST) From: Doug White To: Phillip Crumpler In-Reply-To: <41A3D73E.7040608@crippy.mel.crumpler.com.au> Message-ID: <20041124233636.R2006@carver.gumbysoft.com> References: <71F713C5E3CB7F4F9ACCBBB8E9BE318A39E348@blrx2kmbgl101.blr.amer.dell.com> <007201c4d190$3c6bf3a0$d232a8c0@LCI> <41A3D73E.7040608@crippy.mel.crumpler.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: supported new Dell PERC cards - need to add to the Hardwarenotes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 07:37:10 -0000 On Wed, 24 Nov 2004, Phillip Crumpler wrote: > On a somewhat related note: can anyone report any success with the DELL > 'CERC 6-Channel SATA RAID Controller'? That's an aac(4). -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 07:48:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCCB916A4CE for ; Thu, 25 Nov 2004 07:48:07 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5D4E43D2D for ; Thu, 25 Nov 2004 07:48:07 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 92D5E72DF4; Wed, 24 Nov 2004 23:48:07 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 90F6372DD4; Wed, 24 Nov 2004 23:48:07 -0800 (PST) Date: Wed, 24 Nov 2004 23:48:07 -0800 (PST) From: Doug White To: "Conrad J. Sabatier" In-Reply-To: <1101344441.1174.8.camel@dolphin.local.net> Message-ID: <20041124234748.Q2006@carver.gumbysoft.com> References: <20041118101356.53ed3f78@dolphin.local.net> <1101344441.1174.8.camel@dolphin.local.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: usr.bin/lex/lib object files not being placed under MAKEOBJDIRPREFIX X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 07:48:07 -0000 On Wed, 24 Nov 2004, Conrad J. Sabatier wrote: > On Fri, 2004-11-19 at 17:21 -0800, David O'Brien wrote: > > On Thu, Nov 18, 2004 at 10:13:56AM -0600, Conrad J. Sabatier wrote: > > > Noticed this during a cvs update today: > > > dolphin:root:/usr/src/usr.bin# cvs -R update > > > ? lex/lib/.depend > > > ? lex/lib/libln.a > > > ? lex/lib/libmain.o > > > ? lex/lib/libyywrap.o > > > > How did you build your system? At one time you maybe cd'ed into > > usr.bin/lex and just typed 'make' without 'make obj'? > > > > The fix is to: > > > > rm -rf /usr/obj/* > > cd /usr/src > > make cleandir > > make buildworld > > cvs -q up > > > > and you shouldn't see this again. > > This is very odd. I cleaned up the src tree, and after another > buildworld, these files are back again. I have no idea why. System time is wrong? Files created with wrong timestamp? -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 08:20:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5088016A4CE for ; Thu, 25 Nov 2004 08:20:01 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2CB143D48 for ; Thu, 25 Nov 2004 08:20:00 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CXErA-0001n6-Av; Thu, 25 Nov 2004 00:20:00 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16805.38319.825546.497936@ran.psg.com> Date: Thu, 25 Nov 2004 00:19:59 -0800 To: Doug White References: <20041123182254.GB10721@ninthgate.net> <16804.64917.872924.733444@ran.psg.com> <20041124232820.J2006@carver.gumbysoft.com> cc: freebsd-current@freebsd.org Subject: Re: Random panics with 5.3-REL, SMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 08:20:01 -0000 > A backtrace would be interesting to look at. indeed. but i was lucky to get the screen scrape before the beastie wiped the screen as it auto-rebooted. > Looks like you just need to set 'dumpdev' in rc.conf. What is your boot > device and swap partition(s)? # grep dump /etc/rc.conf dumpdev="/dev/twed0s1b" # Device name to crashdump to (or NO). dumpdir="/var/crash" # Directory where crash dumps are to be stored # grep twed0s1b /etc/fstab /dev/twed0s1b none swap sw 0 0 > if you turn on session logging in your comm program comm program? it's a cisco 2511 term serv being used as a craft port octopus for 16 devices randy From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 08:59:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E200916A4CE for ; Thu, 25 Nov 2004 08:59:31 +0000 (GMT) Received: from jazz.hansabank.lt (jazz.hansabank.lt [193.109.235.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id 961E243D55 for ; Thu, 25 Nov 2004 08:59:30 +0000 (GMT) (envelope-from Putinas.Piliponis@hansa.lt) Received: from localhost (localhost [127.0.0.1]) by jazz.hansabank.lt (Postfix) with ESMTP id B81A8F955 for ; Thu, 25 Nov 2004 10:59:29 +0200 (EET) content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 25 Nov 2004 10:59:28 +0200 Content-Type: multipart/signed; boundary="----=_NextPart_000_000E_01C4D2DD.D3E25F50"; protocol="application/x-pkcs7-signature"; micalg=SHA1 X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 Message-ID: <217202CB5FF8AE439E263CE3D48ECB50757F04@honda.int.hansa.lt> X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: if_pcn & netfinity 5500 Thread-Index: AcTSzRBQfun/HinUShed/7IAIidD4g== From: "Putinas Piliponis" To: Subject: if_pcn & netfinity 5500 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 08:59:32 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_000E_01C4D2DD.D3E25F50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello, Maybe this is not best place to ask, but... I have a problem using amd network card on netfinity 5500 server. If I boot up server with network cable pluged in (very normal situation :) pnc driver recognizes it what supported media is 100BaseTX and thats it. network is not working of course. I look in google and found what same workaround from 4.x times still works ok If I boot up kernel without attached lan cable and attach it later - then it gives correct 100BaseTX . Any patch or more comfortable workaround for this ? ------=_NextPart_000_000E_01C4D2DD.D3E25F50 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIV7jCCAiww ggGVoAMCAQICAxAAADANBgkqhkiG9w0BAQQFADA5MQswCQYDVQQGEwJFRTESMBAGA1UEChMJSGFu c2FwYW5rMRYwFAYDVQQDEw1IYW5zYSBSb290IENBMB4XDTk5MDMxMTA3MTk1M1oXDTA5MDMwODA3 MTk1M1owOTELMAkGA1UEBhMCRUUxEjAQBgNVBAoTCUhhbnNhcGFuazEWMBQGA1UEAxMNSGFuc2Eg Um9vdCBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAy09IBycOA2YSkc0ilg27V8srhWbO MHt3z/8e6y9qXxXYEbLJRaI5cQMAtwjEG+TRym0ViGgVYLU4QPrYXoGitgLtFOgG7urnHTRXjptE e7yOIBMUqUUhMLU/bnqvLTj6hU0U3lkQRdTj+DBEDkVC1RFnTT1LNEExIFIQ3b217ZECAwEAAaNC MEAwHQYDVR0OBBYEFArETktiEtIrt02CpZm0nloulC/YMB8GA1UdIwQYMBaAFArETktiEtIrt02C pZm0nloulC/YMA0GCSqGSIb3DQEBBAUAA4GBAJIH/kuITLXf/CzHSvydCCO0dffp/Z94PC37vEG4 obR1H5x+qQiuqigxhT9sfaCcZE9WoGZWcfYP2l9Q2VT4hHRhKbVKhCuZBh0fats1T36CbtdsLxNH yMOPfaNp9VW2RWyi1hYjTG0tNWFaH0Kd2NDWroQbXGCGHkIlOMcGwQFkMIICXTCCAcagAwIBAgID DVLGMA0GCSqGSIb3DQEBBAUAMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3Vs dGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWlu ZyBDQTAeFw0wNDEwMjgxODIyNDJaFw0wNTEwMjgxODIyNDJaMEwxHzAdBgNVBAMTFlRoYXd0ZSBG cmVlbWFpbCBNZW1iZXIxKTAnBgkqhkiG9w0BCQEWGnB1dGluYXMucGlsaXBvbmlzQGhhbnNhLmx0 MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC73A+48AVvwDxL+RbBL5bXsGF9rABC+znkbRL8 evzGT5P22qyEtAKYxE6drt7eBTS3bnHsnbFfQJog64FTFfsooXuethclBsPgOcfcD6ClxIHp7K5t gL3Hf/JsNdQ8WiCgLn8Td0x5jcmMt2XTvwsLL4fsrpHs8v6R0FtZEqXeLQIDAQABozcwNTAlBgNV HREEHjAcgRpwdXRpbmFzLnBpbGlwb25pc0BoYW5zYS5sdDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3 DQEBBAUAA4GBAELW8v2TeLaGQRjFnmQ6DQ3Y8wPhZ5r6tIhfkBJ2A7spQd7gSOxtTPR8kA69booS yG1UQAJti0vGPrcPdXFEAs1cbAbWj0Q5kAnw9+A8y4/WQGZWgnyi5cFPffJYalem9ULBddLjQ35K D/g6EVjbvbv2gKQROV0JGgQV8xc+jwYCMIIDLTCCApagAwIBAgIBADANBgkqhkiG9w0BAQQFADCB 0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3du MRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2 aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJ KoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTk2MDEwMTAwMDAwMFoX DTIwMTIzMTIzNTk1OVowgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQ BgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0Nl cnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBG cmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTCB nzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA1GnX1LCUZFtx6UfYDFG26nKRsIRefS0Nj3sS34Ul dSh0OkIsYyeflXtL734Zhx2G6qPduc6WZBrCFG5ErHzmj+hND3EfQDimAKOHePb5lIZererAXnbr 2RSjXW56fAylS1V/Bhkpf56aJtVquzgkCGqYx7Hao5iR/Xnb5VrEHLkCAwEAAaMTMBEwDwYDVR0T AQH/BAUwAwEB/zANBgkqhkiG9w0BAQQFAAOBgQDH7JJ+Tvj1lqVnYiqk8E0RYNBvjWBYYawmu1I1 XAjPMPuoSpaKH2JCI4wXD/S6ZJwXrEcp352YXtJsYHFcoqzceePnbgBHH7UNKOgCneSa/RP0ptl8 sfjcXyMmCZGAc9AUG95DqYMl8uacLxXK/qarigd1iwzdUYRr5PjRzneigTCCAz8wggKooAMCAQIC AQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUx EjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsT H0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNv bTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQK ExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065 yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FW y688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5k GXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0 dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQE AwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcN AQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t 4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpb NU1341YheILcIRk13iSx0x1G/11fZU8wggQ3MIIDoKADAgECAgIBBzANBgkqhkiG9w0BAQQFADA5 MQswCQYDVQQGEwJFRTESMBAGA1UEChMJSGFuc2FwYW5rMRYwFAYDVQQDEw1IYW5zYSBSb290IENB MB4XDTAyMDcxNjA4MjY1OFoXDTA5MDIwOTA4MjY1OFowRTELMAkGA1UEBhMCTFQxEjAQBgNVBAoT CUhhbnNhYmFuazEiMCAGA1UEAxMZSGFuc2FiYW5rIExUIGNvcnBvcmF0ZSBDQTCCASIwDQYJKoZI hvcNAQEBBQADggEPADCCAQoCggEBAOywhJxDqmwwPaz2jh36IYl3j8dqyV7CQobdaGarwYINDEBI REvwpJWU+XQMzCjl+f+2Nc6BZVh3TP1L20xnU1h5x9QW54M0h/3MOGnR9+/K0HQytltL9H/shRWL Xn96TKJikjcEHuHBtQXx2bz+8tZxJfuDlINLCrchTHDxXvAzc2vvG8JZKu2v8D4wOnQujQJMvbOz 33FdlI5xZK/Qf1M76wHBKNpo3TznKG41g39Xe7IEJVqMgZ0+51T7jswjiuh50UBIuB29JZeZKlks Yxkw3KlZJuzwFH7eO5MYDjJHRoaExrlT3BqoiYK2nbQN+xqox8kuE6BCchkC8/pscPMCAwEAAaOC AbwwggG4MB0GA1UdDgQWBBSQnWUmeUksJegDA5/wTRWbmR5m/DBjBgNVHSMEXDBagBQKxE5LYhLS K7dNgqWZtJ5aLpQv2KE9pDswOTELMAkGA1UEBhMCRUUxEjAQBgNVBAoTCUhhbnNhcGFuazEWMBQG A1UEAxMNSGFuc2EgUm9vdCBDQYIDEAAAMA8GA1UdEwEB/wQFMAMBAf8wCwYDVR0PBAQDAgFGMIIB EgYDVR0fBIIBCTCCAQUwgc6ggcuggciGgcVsZGFwOi8vL0NOPUhhbnNhJTIwUm9vdCUyY0NOPWFs cGhhJTJjQ049Q0RQJTJjQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMlMmNDTj1TZXJ2aWNlcyUy Y0NOPUNvbmZpZ3VyYXRpb24lMmNEQz1pbnQlMmNEQz1oYW5zYSUyY0RDPWVlP2NlcnRpZmljYXRl UmV2b2NhdGlvbkxpc3Q/YmFzZT9vYmplY3RjbGFzcz1jUkxEaXN0cmlidXRpb25Qb2ludDAyoDCg LoYsaHR0cDovL2F1ZGkuaW50LmhhbnNhLmx0L2NlcnRlbnJvbGwvcm9vdC5jcmwwDQYJKoZIhvcN AQEEBQADgYEAfbgx849ncHuZJ9XLbYT1h3MKazFD3PDu+3w/BAbCY/j1fdODW2qv4OjU/L8w4ffs 5WjofKE6bnZItRBmygvFrfAcJg9MCmBLyMMFWDbix3Nq6fZ/awnC6/YlNsCNIu+TVrVsWJspyC+s iBYR3sXnaU0JErt4vNYhokE37H/ucd4wggaqMIIFkqADAgECAgoguUEuAAEAACHBMA0GCSqGSIb3 DQEBBQUAMEUxCzAJBgNVBAYTAkxUMRIwEAYDVQQKEwlIYW5zYWJhbmsxIjAgBgNVBAMTGUhhbnNh YmFuayBMVCBjb3Jwb3JhdGUgQ0EwHhcNMDQwODExMDYzNDU5WhcNMDYwODExMDYzNDU5WjBHMSkw JwYJKoZIhvcNAQkBFhpQdXRpbmFzLlBpbGlwb25pc0BoYW5zYS5sdDEaMBgGA1UEAxMRUHV0aW5h cyBQaWxpcG9uaXMwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAL9MadCNAF9prlqEM79LnMtU ZUsmjPYVaWxgjYbpNnb1K/YLgt8IKvi1y7orN71HIy6XOLtceuKnJF4UyYu0hnzpX1YCrApj1kmY jttzwUMLmldoMI/+Nw5R5QioXFAJht09OwqEBHxGOwDMt4Gs4f1DdjElUqyEzSFucCedel6vAgMB AAGjggQcMIIEGDALBgNVHQ8EBAMCBaAwKQYDVR0lBCIwIAYIKwYBBQUHAwQGCCsGAQUFBwMCBgor BgEEAYI3FAICMCkGCSsGAQQBgjcUAgQcHhoAUwBtAGEAcgB0AGMAYQByAGQAVQBzAGUAcjAdBgNV HQ4EFgQUtlF3XdHE1kc/hYjvbsBc8Nu4TnMwYgYDVR0jBFswWYAUkJ1lJnlJLCXoAwOf8E0Vm5ke ZvyhPaQ7MDkxCzAJBgNVBAYTAkVFMRIwEAYDVQQKEwlIYW5zYXBhbmsxFjAUBgNVBAMTDUhhbnNh IFJvb3QgQ0GCAgEHMIIBYwYDVR0fBIIBWjCCAVYwgdCggc2ggcqGgcdsZGFwOi8vL0NOPUhhbnNh YmFuayUyMExUJTIwY29ycG9yYXRlJTIwQ0EsQ049YXVkaSxDTj1DRFAsQ049UHVibGljJTIwS2V5 JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1pbnQsREM9aGFuc2Es REM9ZWU/Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlP29iamVjdGNsYXNzPWNSTERpc3Ry aWJ1dGlvblBvaW50ME2gS6BJhkdodHRwOi8vYXVkaS5pbnQuaGFuc2EubHQvQ2VydEVucm9sbC9I YW5zYWJhbmslMjBMVCUyMGNvcnBvcmF0ZSUyMENBLmNybDAyoDCgLoYsaHR0cDovL2F1ZGkuaW50 LmhhbnNhLmx0L2NlcnRlbnJvbGwvcm9vdC5jcmwwggF7BggrBgEFBQcBAQSCAW0wggFpMIHCBggr BgEFBQcwAoaBtWxkYXA6Ly8vQ049SGFuc2FiYW5rJTIwTFQlMjBjb3Jwb3JhdGUlMjBDQSxDTj1B SUEsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlv bixEQz1pbnQsREM9aGFuc2EsREM9ZWU/Y0FDZXJ0aWZpY2F0ZT9iYXNlP29iamVjdGNsYXNzPWNl cnRpZmljYXRpb25BdXRob3JpdHkwaAYIKwYBBQUHMAKGXGh0dHA6Ly9hdWRpLmludC5oYW5zYS5s dC9DZXJ0RW5yb2xsL2F1ZGkuaW50LmhhbnNhLmx0X0hhbnNhYmFuayUyMExUJTIwY29ycG9yYXRl JTIwQ0EoMSkuY3J0MDgGCCsGAQUFBzAChixodHRwOi8vYXVkaS5pbnQuaGFuc2EubHQvY2VydGVu cm9sbC9yb290LmNydDBKBgNVHREEQzBBoCMGCisGAQQBgjcUAgOgFQwTcHV0cGlsQGludC5oYW5z YS5sdIEaUHV0aW5hcy5QaWxpcG9uaXNAaGFuc2EubHQwDQYJKoZIhvcNAQEFBQADggEBAIAG4B0U AGtYXA8Rml8J6bIquNip7aIMMb5tw3Tri00vjY+fo5fRxeqTtyxLp2URhpIzR/2Vfq70nACn1yA9 2rkTIgfdQ11rZ03TrFDW3fOzfZCTdyYLMkm5v3DgaPE8SUcOLbHIQvgJ6l2QqNwIVGgPYT73aYXE D0GT7AwzxpksmyotwroUlLTo7Guw9IJv1WZuYFiQWgrqUrp4eXEwpmbJIfksvVox/Uw4tUwtrn5u Qp1yAkm7FGIo9yrRPd6Pbqwmx+uXtEsBnCKSE2N/9Gmi6MswOoUKx6zsPISj3hdqd6ZcSkUIkBpl ApN1CqiKw5ITKCvppz3LvWPv9SopigMxggKFMIICgQIBATBpMGIxCzAJBgNVBAYTAlpBMSUwIwYD VQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29u YWwgRnJlZW1haWwgSXNzdWluZyBDQQIDDVLGMAkGBSsOAwIaBQCgggFyMBgGCSqGSIb3DQEJAzEL BgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA0MTEyNTA4NTkyNVowIwYJKoZIhvcNAQkEMRYE FE/RoKJFNv8Csjhujr82S7Ox7FhcMEkGCSqGSIb3DQEJDzE8MDowCgYIKoZIhvcNAwcwDgYIKoZI hvcNAwICAgCAMAcGBSsOAwIHMAcGBSsOAwIaMAoGCCqGSIb3DQIFMGIGCSsGAQQBgjcQBDFVMFMw RTELMAkGA1UEBhMCTFQxEjAQBgNVBAoTCUhhbnNhYmFuazEiMCAGA1UEAxMZSGFuc2FiYW5rIExU IGNvcnBvcmF0ZSBDQQIKILlBLgABAAAhwTBkBgsqhkiG9w0BCRACCzFVoFMwRTELMAkGA1UEBhMC TFQxEjAQBgNVBAoTCUhhbnNhYmFuazEiMCAGA1UEAxMZSGFuc2FiYW5rIExUIGNvcnBvcmF0ZSBD QQIKILlBLgABAAAhwTANBgkqhkiG9w0BAQEFAASBgANwye+Jn1RYj/PAbnyYnqF+8b2cvPYxfUS+ FuvyTkfy2/qE+YrDNzwmEp9/tNFnsSLL79aIrJHvRYbj7AkUYQpjSQEMYUiD3ZvMuacUI5Ugxa8L jiLz74gKZlz8uWcETTZD0JI8bQdz1KBYNhoW/pxZRuluuQEpKab3sOBhY1S/AAAAAAAA ------=_NextPart_000_000E_01C4D2DD.D3E25F50-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 14:12:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A87416A4CE for ; Thu, 25 Nov 2004 14:12:43 +0000 (GMT) Received: from relay.bestcom.ru (relay.bestcom.ru [217.72.144.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64A7B43D48 for ; Thu, 25 Nov 2004 14:12:42 +0000 (GMT) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (root@cell.sick.ru [217.72.144.68]) by relay.bestcom.ru (8.13.1/8.12.9) with ESMTP id iAPECed6078628 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 25 Nov 2004 17:12:41 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.11/8.12.8) with ESMTP id iAPECdrl078408 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Nov 2004 17:12:40 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id iAPECdxq078407; Thu, 25 Nov 2004 17:12:39 +0300 (MSK) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Thu, 25 Nov 2004 17:12:38 +0300 From: Gleb Smirnoff To: David Schwartz Message-ID: <20041125141238.GB78210@cell.sick.ru> References: Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i X-Virus-Scanned: clamd / ClamAV version devel-20041013, clamav-milter version 0.75l on 127.0.0.1 X-Virus-Status: Clean cc: "freebsd-current@FreeBSD. org" Subject: Re: RFC: Add creation time to dynamic firewall rules X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 14:12:43 -0000 On Wed, Nov 24, 2004 at 01:12:28PM -0800, David Schwartz wrote: D> FreeBSD does not keep track of the time a dynamic firewall was created in D> the structure associated with that rule. It looks like it would take less D> than an hour to code up a patch to keep this information and add a flag to D> ipfw to display how many seconds old the rule is instead of the usage time. D> D> I want this addition for two reasons: D> D> 1) Being able to know how old a connection is gives you important D> information about its stability. D> D> 2) By dividing the number of bytes by the connection age, you can D> guesstimate the approximate bandwidth usage of the connection. D> D> I could easily make this change locally and maintain it as a local patch, D> but would prefer to see it accepted into the general distribution. Does D> anyone have any comments as to whether such a patch would be likely to be D> accepted? D> D> The cost is, essentially, an extra 4 bytes for each dynamic firewall rule. D> A large firewall might have 10,000 dynamic rules, which would be 40Kb. A D> typical firewall might have 300, which would be 1Kb or so. (It might D> actually be a bit more or less, I haven't looked at slack space.) This is not answer to your question, but you can obtain such information for all running network flows if you run ng_netflow. NetFlow is a standard tool for monitoring. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 17:52:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E98E716A4CE for ; Thu, 25 Nov 2004 17:52:59 +0000 (GMT) Received: from thunderbird.etv.net (thunderbird.etv.net [208.14.190.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6133743D31 for ; Thu, 25 Nov 2004 17:52:59 +0000 (GMT) (envelope-from lists@efinley.com) Received: from [205.161.203.50] (helo=science1) by thunderbird.etv.net with smtp (Exim 4.34 (FreeBSD)) id 1CXNne-0004sT-Mj for freebsd-current@freebsd.org; Thu, 25 Nov 2004 10:52:58 -0700 Message-ID: <067d01c4d317$997cfbb0$32cba1cd@science1> From: "Elliot Finley" To: References: <71F713C5E3CB7F4F9ACCBBB8E9BE318A39E348@blrx2kmbgl101.blr.amer.dell.com><20041123105313.GC753@zaphod.nitro.dk> <007201c4d190$3c6bf3a0$d232a8c0@LCI> <200411241409.10971.doconnor@gsoft.com.au> Date: Thu, 25 Nov 2004 10:52:58 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Subject: Re: supported new Dell PERC cards - need to add to the Hardwarenotes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Elliot Finley List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 17:53:00 -0000 Are these supported on 5.3-R? ----- Original Message ----- From: "Daniel O'Connor" To: Cc: "Samuel Clements" Sent: Tuesday, November 23, 2004 8:39 PM Subject: Re: supported new Dell PERC cards - need to add to the Hardwarenotes From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 18:14:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB87516A4CE for ; Thu, 25 Nov 2004 18:14:09 +0000 (GMT) Received: from 9.hellooperator.net (cpc3-cdif2-3-0-cust202.cdif.cable.ntl.com [81.103.32.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B11443D60 for ; Thu, 25 Nov 2004 18:14:09 +0000 (GMT) (envelope-from rasputin@hellooperator.net) Received: from rasputin by 9.hellooperator.net with local (Exim 4.43) id 1CXO88-0005R7-Ba for freebsd-current@freebsd.org; Thu, 25 Nov 2004 18:14:08 +0000 Date: Thu, 25 Nov 2004 18:14:08 +0000 From: Dick Davies To: FreeBSD Current Users Message-ID: <20041125181408.GW12945@lb.tenfour> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Sender: Rasputin Subject: ata1-slave: FAILURE - ATAPI_IDENTIFY timed out - fixed yet? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Dick Davies List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 18:14:09 -0000 I finally got the DVD/CDRW drive in my laptop RMAed. Fitted the new one and said 'oh, yeah - now I remember'... FreeBSD (releng5 from about 6 weeks back) gets as far as ata1-slave: FAILURE - ATAPI_IDENTIFY timed out ata1-slave: FAILURE - ATAPI_IDENTIFY timed out then locks - I have to pull the battery to reboot into winxp - now I'm trapped. I saw a thread on this back in October, did it ever get fixed? I don't mind pulling the drive to get in if need be, but is there anyway of (for example) disabling ata1* from the loader prompt? -- Blackmail's such an ugly word. I prefer extortion. The x makes it sound cool. - Bender Rasputin :: Jack of All Trades - Master of Nuns From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 18:16:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D1A9C16A4CE for ; Thu, 25 Nov 2004 18:16:36 +0000 (GMT) Received: from fed1rmmtao12.cox.net (fed1rmmtao12.cox.net [68.230.241.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89D6B43D3F for ; Thu, 25 Nov 2004 18:16:36 +0000 (GMT) (envelope-from housel@acm.org) Received: from housel.dyndns.org ([68.4.109.244]) by fed1rmmtao12.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20041125181636.FLSZ3296.fed1rmmtao12.cox.net@housel.dyndns.org> for ; Thu, 25 Nov 2004 13:16:36 -0500 Received: (from housel@localhost) by housel.dyndns.org (8.13.1/8.13.1/Submit) id iAPIGREb018570 for freebsd-current@freebsd.org; Thu, 25 Nov 2004 10:16:27 -0800 (PST) (envelope-from housel@acm.org) X-Authentication-Warning: housel.dyndns.org: housel set sender to housel@acm.org using -f From: "Peter S. Housel" To: freebsd-current@freebsd.org In-Reply-To: <200411022243.02175.mistry.7@osu.edu> References: <20041031161538.GA989@naboo.wanadoo.fr> <200411022243.02175.mistry.7@osu.edu> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 25 Nov 2004 10:16:26 -0800 Message-Id: <1101406586.938.3.camel@housel.dyndns.org> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Subject: Re: panic: Wrong vnode in bufstrategy(bp=0xc5e058c0, vp=0xc1615238) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 18:16:37 -0000 On Tue, 2004-11-02 at 22:43 -0500, Anish Mistry wrote: > On Sunday 31 October 2004 11:15 am, Aurelien Nephtali wrote: > > Hello, > > > > Since the recent commits by phk@, I can't mount any NTFS file system > > without getting a : > > > > panic: Wrong vnode in bufstrategy(bp=0xc5e058c0, vp=0xc1615238) > > > > > > Trace output as well as dmesg output are attached. > > > > Thanks! > Just wanted to add a me too. I can post my back trace too if it would > help. Just wanted to add that I'm still seeing this on my system, cvsupped two days ago. I can mount NTFS, but reading files from it locks up the system hard with nothing but the 1-line panic message. -Peter- From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 18:48:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D20FE16A4CF for ; Thu, 25 Nov 2004 18:48:21 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D652343D64 for ; Thu, 25 Nov 2004 18:48:20 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 73771 invoked from network); 25 Nov 2004 18:40:36 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 25 Nov 2004 18:40:36 -0000 Message-ID: <41A628F3.3000309@freebsd.org> Date: Thu, 25 Nov 2004 19:48:19 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Jeremie Le Hen cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 18:48:21 -0000 Robert Watson wrote: > On Sun, 21 Nov 2004, Sean McNeil wrote: > >>I have to disagree. Packet loss is likely according to some of my >>tests. With the re driver, no change except placing a 100BT setup with >>no packet loss to a gigE setup (both linksys switches) will cause >>serious packet loss at 20Mbps data rates. I have discovered the only >>way to get good performance with no packet loss was to >> >>1) Remove interrupt moderation >>2) defrag each mbuf that comes in to the driver. > > Sounds like you're bumping into a queue limit that is made worse by > interrupting less frequently, resulting in bursts of packets that are > relatively large, rather than a trickle of packets at a higher rate. > Perhaps a limit on the number of outstanding descriptors in the driver or > hardware and/or a limit in the netisr/ifqueue queue depth. You might try > changing the default IFQ_MAXLEN from 50 to 128 to increase the size of the > ifnet and netisr queues. You could also try setting net.isr.enable=1 to > enable direct dispatch, which in the in-bound direction would reduce the > number of context switches and queueing. It sounds like the device driver > has a limit of 256 receive and transmit descriptors, which one supposes is > probably derived from the hardware limit, but I have no documentation on > hand so can't confirm that. > > It would be interesting on the send and receive sides to inspect the > counters for drops at various points in the network stack; i.e., are we > dropping packets at the ifq handoff because we're overfilling the > descriptors in the driver, are packets dropped on the inbound path going > into the netisr due to over-filling before the netisr is scheduled, etc. > And, it's probably interesting to look at stats on filling the socket > buffers for the same reason: if bursts of packets come up the stack, the > socket buffers could well be being over-filled before the user thread can > run. I think it's the tcp_output() path that overflows the transmit side of the card. I take that from the better numbers when he defrags the packets. Once I catch up with my mails I start to put up the code I wrote over the last two weeks. :-) You can call me Mr. TCP now. ;-) -- Andre From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 18:58:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 483BB16A4CE for ; Thu, 25 Nov 2004 18:58:10 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id C106343D49 for ; Thu, 25 Nov 2004 18:58:09 +0000 (GMT) (envelope-from taosecurity@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so195743rnf for ; Thu, 25 Nov 2004 10:58:09 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=XNSzc42/FzptRIiPeDb04voQ+7oYQ9yozuJgBjPavE7bahE+9ruDn3mgT9m+ewjoNa2DhLyo3guHv7Ilj0VeFGIK1CI8h/XKi3iqjch4H3qCHRcwlFUAmRnGme5/yQZunWVloDvW9oRHoPWDZlPhZa+HyU1k4MmETzDw1BOmEA8= Received: by 10.38.209.11 with SMTP id h11mr234936rng; Thu, 25 Nov 2004 10:58:09 -0800 (PST) Received: by 10.38.75.45 with HTTP; Thu, 25 Nov 2004 10:58:09 -0800 (PST) Message-ID: <120ef053041125105878678476@mail.gmail.com> Date: Thu, 25 Nov 2004 13:58:09 -0500 From: Richard Bejtlich To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: supported new Dell PERC cards - need to add to the Hardwarenotes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Richard Bejtlich List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 18:58:10 -0000 Phillip Crumpler wrote: > On a somewhat related note: can anyone report any success with the DELL > 'CERC 6-Channel SATA RAID Controller'? > aac(4) claims to support a DELL CERC SATA RAID 2 but I think that this > is an older beast. > Phillip I think I may have this hardware on my Dell PowerEdge 750. Check out my FreeBSD 5.3 RELEASE dmesg output here: http://nycbug.org/dmesgd/?dmesgid=508#508 I would encourage anyone who gets FreeBSD running on newer hardware to post dmesg output to the NYCBUG site. Sincerely, Richard http://www.taosecurity.com From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 20:50:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6267C16A4CE for ; Thu, 25 Nov 2004 20:50:35 +0000 (GMT) Received: from guzas.devnull.lt (clt-84-32-40-211.ktv.lt [84.32.40.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7839A43D3F for ; Thu, 25 Nov 2004 20:50:32 +0000 (GMT) (envelope-from paulius@devnull.lt) Received: by guzas.devnull.lt (Postfix, from userid 1001) id C5B4B89; Thu, 25 Nov 2004 22:50:25 +0200 (EET) Date: Thu, 25 Nov 2004 22:50:25 +0200 From: Paulius Bulotas To: freebsd-current@freebsd.org Message-ID: <20041125205025.GA972@devnull.lt> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-URL: http://devnull.lt/ Subject: usb problem, triggered by ndis X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 20:50:35 -0000 Hello, upgraded to todays -current and now I'm experiencing little annoying problem with my usb devices. Output from log: kernel: ndis0: mem 0xc0200000-0xc0200fff irq 11 at device 2.0 on pci2 kernel: ndis0: NDIS API version: 5.1 kernel: ndis0: Ethernet address: 00:04:23:72:4a:75 kernel: ndis0: 11b rates: 11Mbps 2Mbps 1Mbps 5.5Mbps kernel: ums0: at uhub1 port 1 (addr 2) disconnected kernel: ums0: detached moused: unable to open /dev/ums0: No such file or directory kernel: ndis0: link up The ports seem to be dead (tested with ums, umass) after I enable ndis. These problems of course could be related to recent changes to usb code? I will try to backout them as soon as possible and see if that helps (if there won't be other suggestions ;) My previous upgrade was on 05 November, so maybe there were other changes as well (and backing usb changes won't help). I'll upload dmesg.boot from verbose boot to http://devnull.lt/files/dmesg.boot BTW, in my kernel config I have such usb related devices: device uhci device ohci device usb device ugen device umass device ums device ucom device uftdi probably I don't need both uhci and ohci? The computer is IBM T40 notebook with 2xUSB 2.0 ports. TIA Paulius From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 20:52:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D537216A4CE; Thu, 25 Nov 2004 20:52:18 +0000 (GMT) Received: from dglawrence.com (c-24-21-223-117.client.comcast.net [24.21.223.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D42443D46; Thu, 25 Nov 2004 20:52:18 +0000 (GMT) (envelope-from dg@dglawrence.com) Received: from opteron.dglawrence.com (localhost [127.0.0.1]) by dglawrence.com (8.13.1/8.13.1) with ESMTP id iAPKqHRD005800; Thu, 25 Nov 2004 12:52:17 -0800 (PST) (envelope-from dg@dglawrence.com) Received: (from dg@localhost) by opteron.dglawrence.com (8.13.1/8.13.1/Submit) id iAPKqAwV005799; Thu, 25 Nov 2004 12:52:10 -0800 (PST) (envelope-from dg@dglawrence.com) Date: Thu, 25 Nov 2004 12:52:10 -0800 From: "David G. Lawrence" To: Andre Oppermann Message-ID: <20041125205210.GA673@opteron.dglawrence.com> References: <41A628F3.3000309@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41A628F3.3000309@freebsd.org> cc: Jeremie Le Hen cc: freebsd-current@freebsd.org cc: Robert Watson cc: freebsd-stable@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 20:52:19 -0000 > >>tests. With the re driver, no change except placing a 100BT setup with > >>no packet loss to a gigE setup (both linksys switches) will cause > >>serious packet loss at 20Mbps data rates. I have discovered the only > >>way to get good performance with no packet loss was to > >> > >>1) Remove interrupt moderation > >>2) defrag each mbuf that comes in to the driver. > > > >Sounds like you're bumping into a queue limit that is made worse by > >interrupting less frequently, resulting in bursts of packets that are > >relatively large, rather than a trickle of packets at a higher rate. > >Perhaps a limit on the number of outstanding descriptors in the driver or > >hardware and/or a limit in the netisr/ifqueue queue depth. You might try > >changing the default IFQ_MAXLEN from 50 to 128 to increase the size of the > >ifnet and netisr queues. You could also try setting net.isr.enable=1 to > >enable direct dispatch, which in the in-bound direction would reduce the > >number of context switches and queueing. It sounds like the device driver > >has a limit of 256 receive and transmit descriptors, which one supposes is > >probably derived from the hardware limit, but I have no documentation on > >hand so can't confirm that. > > > >It would be interesting on the send and receive sides to inspect the > >counters for drops at various points in the network stack; i.e., are we > >dropping packets at the ifq handoff because we're overfilling the > >descriptors in the driver, are packets dropped on the inbound path going > >into the netisr due to over-filling before the netisr is scheduled, etc. > >And, it's probably interesting to look at stats on filling the socket > >buffers for the same reason: if bursts of packets come up the stack, the > >socket buffers could well be being over-filled before the user thread can > >run. > > I think it's the tcp_output() path that overflows the transmit side of > the card. I take that from the better numbers when he defrags the packets. > Once I catch up with my mails I start to put up the code I wrote over the > last two weeks. :-) You can call me Mr. TCP now. ;-) He was doing his test with NFS over TCP, right? ...That would be a single connection, so how is it possible to 'overflow the transmit side of the card'? The TCP window size will prevent more than 64KB to be outstanding. Assuming standard size ethernet frames, that would be a maximum of 45 packets in-flight at any time (65536/1460=45), well below the 256 available transmit descriptors. It is also worth pointing out that 45 full-size packets is 540us at gig-e speeds. Even when you add up typical switch latencies and interrupt overhead and coalesing on both sides, it's hard to imagine that the window size (bandwidth * delay) would be a significant limiting factor across a gig-e LAN. I too am seeing low NFS performance (both TCP and UDP) with non-SMP 5.3, but on the same systems I can measure raw TCP performance (using ttcp) of >850Mbps. It looks to me like there is something wrong with NFS, perhaps caused by delays with scheduling nfsd? -DG David G. Lawrence President Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500 TeraSolutions, Inc. - http://www.terasolutions.com - (888) 346 7175 The FreeBSD Project - http://www.freebsd.org Pave the road of life with opportunities. From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 21:22:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA6BD16A4D0 for ; Thu, 25 Nov 2004 21:22:47 +0000 (GMT) Received: from web14124.mail.yahoo.com (web14124.mail.yahoo.com [66.163.171.115]) by mx1.FreeBSD.org (Postfix) with SMTP id 657DF43D5E for ; Thu, 25 Nov 2004 21:22:47 +0000 (GMT) (envelope-from cguttesen@yahoo.dk) Received: (qmail 61119 invoked by uid 60001); 25 Nov 2004 21:22:47 -0000 Message-ID: <20041125212247.61117.qmail@web14124.mail.yahoo.com> Received: from [194.248.174.50] by web14124.mail.yahoo.com via HTTP; Thu, 25 Nov 2004 22:22:47 CET Date: Thu, 25 Nov 2004 22:22:47 +0100 (CET) From: Claus Guttesen To: "David G. Lawrence" , Andre Oppermann In-Reply-To: <20041125205210.GA673@opteron.dglawrence.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: Robert Watson cc: freebsd-current@freebsd.org cc: Jeremie Le Hen cc: freebsd-stable@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 21:22:47 -0000 > > >ifnet and netisr queues. You could also try > setting net.isr.enable=1 to > > >enable direct dispatch, which in the in-bound > direction would reduce the > > >number of context switches and queueing. It > sounds like the device driver > > >has a limit of 256 receive and transmit > descriptors, which one supposes is > > >probably derived from the hardware limit, but I > have no documentation on > > >hand so can't confirm that. It may not cast much light on the issue but I tried setting net.isr.enable on to 1 on a nfs-server using tcp on 5.3 RC3 copying between three clients. When setting net.isr.enable to 0 the cpu-usage went up. The server is running with this setting now and is being mounted by 11 webservers. Using em-gb-card. Claus From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 23:17:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD2FB16A4CE for ; Thu, 25 Nov 2004 23:17:44 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id B23F543D1F for ; Thu, 25 Nov 2004 23:17:44 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id DC2C1516D1; Thu, 25 Nov 2004 15:22:10 -0800 (PST) Date: Thu, 25 Nov 2004 15:22:10 -0800 From: Kris Kennaway To: current@FreeBSD.org Message-ID: <20041125232210.GA88512@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8t9RHnE3ZwKMSgU+" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Sleeping on "fdesc" with the following non-sleepable locks held: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 23:17:45 -0000 --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Found in 6.0 (with mpsafevm=1, if it matters) Kris Sleeping on "fdesc" with the following non-sleepable locks held: exclusive sleep mutex fdesc r = 0 (0xc0740920) locked @ kern/vfs_mount.c:955 KDB: enter: witness_warn [thread pid 79735 tid 100366 ] Stopped at kdb_enter+0x32: leave db> tr Tracing pid 79735 tid 100366 td 0xc8584900 kdb_enter(c06c48a8,f161bc28,1,1,0) at kdb_enter+0x32 witness_warn(2,c5bae928,c06e4bde,c06e0ca6,c076cbd0) at witness_warn+0x1bb msleep(c5bae94c,c5bae928,64,c06e0ca6,0) at msleep+0x47 checkdirs(c59fa400,f161bca4,c8584900,c8584900,0) at checkdirs+0xe0 dounmount(c59fa400,8080000,c8584900,40d,602ff4f) at dounmount+0x3d6 unmount(c8584900,f161bd14,c06feff6,3ad,2) at unmount+0x1cc syscall(2f,2f,2f,804a618,bfbfe759) at syscall+0x13b Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (22, FreeBSD ELF32, unmount), eip = 0x280c5a63, esp = 0xbfbfe4ec, ebp = 0xbfbfe5a8 --- --8t9RHnE3ZwKMSgU+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBpmkiWry0BWjoQKURAhu2AKDCGns9dkfhpjqyDhzuqI+LPhsHgQCgibOG mh07ftBiP9fh7Y8v0sK0Xcc= =bzdO -----END PGP SIGNATURE----- --8t9RHnE3ZwKMSgU+-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 26 02:36:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C59416A4CE for ; Fri, 26 Nov 2004 02:36:24 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id D291443D1D for ; Fri, 26 Nov 2004 02:36:23 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by bahre.achedra.org (8.12.10/8.12.10) with ESMTP id iAQ2Tus4031935; Thu, 25 Nov 2004 21:29:57 -0500 (EST) (envelope-from ketrien@error404.nls.net) Date: Thu, 25 Nov 2004 21:29:56 -0500 (EST) From: "Ketrien I. Saihr-Kenchedra" X-X-Sender: ketrien@bahre.achedra.org To: Putinas Piliponis In-Reply-To: <217202CB5FF8AE439E263CE3D48ECB50757F04@honda.int.hansa.lt> Message-ID: <20041125212856.I4557@bahre.achedra.org> References: <217202CB5FF8AE439E263CE3D48ECB50757F04@honda.int.hansa.lt> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: if_pcn & netfinity 5500 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 02:36:24 -0000 On Thu, 25 Nov 2004, Putinas Piliponis wrote: > Hello, > > Maybe this is not best place to ask, but... > I have a problem using amd network card on netfinity 5500 server. > If I boot up server with network cable pluged in (very normal situation :) > pnc driver recognizes it what supported media is 100BaseTX and > thats it. > network is not working of course. Is this the IBM-made 'Fault-Tolerant' Netfinity adapter? (I don't have the FRU handy; can't miss it though. It's the one with two ISSI chips on the back edge.) -ksaihr From owner-freebsd-current@FreeBSD.ORG Fri Nov 26 06:04:32 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16B0B16A4CE for ; Fri, 26 Nov 2004 06:04:32 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1FED43D1D for ; Fri, 26 Nov 2004 06:04:31 +0000 (GMT) (envelope-from clint@0lsen.net) Received: from 0lsen.net ([24.20.127.157]) by comcast.net (sccrmhc13) with ESMTP id <20041126060431016001prjpe>; Fri, 26 Nov 2004 06:04:31 +0000 Received: by 0lsen.net (Postfix, from userid 1001) id AF4461789B; Thu, 25 Nov 2004 22:04:30 -0800 (PST) Date: Thu, 25 Nov 2004 22:04:30 -0800 From: Clint Olsen To: current@freebsd.org Message-ID: <20041126060430.GA54114@0lsen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Organization: NULlsen Network X-Disclaimer: Mutt Bites! Subject: Where is pam(8)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 06:04:32 -0000 I manage to run into situations where I need to learn more about how pam works, yet when I do, quite a bit of the documentation is out of date. References are made to manpages that don't exist. This is pretty irritating. Where do I *really* find out about how pam works and all the available modules? -Clint From owner-freebsd-current@FreeBSD.ORG Fri Nov 26 07:08:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5132C16A4CE for ; Fri, 26 Nov 2004 07:08:44 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EEF843D55 for ; Fri, 26 Nov 2004 07:08:44 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id C40A8F20C0 for ; Thu, 25 Nov 2004 23:08:41 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02094-01 for ; Thu, 25 Nov 2004 23:08:40 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id E280DF1849 for ; Thu, 25 Nov 2004 23:08:39 -0800 (PST) From: Sean McNeil To: current@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-POX8HFAycawpHEe++vTc" Date: Thu, 25 Nov 2004 23:08:39 -0800 Message-Id: <1101452919.2478.3.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com Subject: ACPI crashes amd64 kernel built 1 hour ago X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 07:08:44 -0000 --=-POX8HFAycawpHEe++vTc Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I get a panic from ACPI now every time: Page fault accessing 0xc00000023 PC is at AcpiUtAcquireFromCache+0x75 (gdb) l *AcpiUtAcquireFromCache+0x75 0xffffffff80190915 is in AcpiUtAcquireFromCache (/usr/src/sys/contrib/dev/acpica/utalloc.c:224). 219 if (CacheInfo->ListHead) 220 { 221 /* There is an object available, use it */ 222 223 Object =3D CacheInfo->ListHead; 224 CacheInfo->ListHead =3D *(ACPI_CAST_INDIRECT_PTR (char, &(((char *) Object)[CacheInfo->LinkOffset]))); 225 226 ACPI_MEM_TRACKING (CacheInfo->CacheHits++); 227 CacheInfo->CacheDepth--; 228 kernel built Sunday Nov 21 works perfectly. Cheers, Sean --=-POX8HFAycawpHEe++vTc Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBptZ3yQsGN30uGE4RArs4AJ9FgYfo0sGTJDfjnGHM3zPH29CXJACeNQT7 v93ztoW7iebO8mXtdZ/Ia2w= =0iLV -----END PGP SIGNATURE----- --=-POX8HFAycawpHEe++vTc-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 26 08:51:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90B3016A4CE for ; Fri, 26 Nov 2004 08:51:25 +0000 (GMT) Received: from eddie.nitro.dk (port324.ds1-khk.adsl.cybercity.dk [212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id E43A843D54 for ; Fri, 26 Nov 2004 08:51:24 +0000 (GMT) (envelope-from simon@eddie.nitro.dk) Received: by eddie.nitro.dk (Postfix, from userid 1000) id 543D2119CD9; Fri, 26 Nov 2004 09:51:23 +0100 (CET) Date: Fri, 26 Nov 2004 09:51:23 +0100 From: "Simon L. Nielsen" To: Clint Olsen Message-ID: <20041126085122.GA86548@eddie.nitro.dk> References: <20041126060430.GA54114@0lsen.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm" Content-Disposition: inline In-Reply-To: <20041126060430.GA54114@0lsen.net> User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: Where is pam(8)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 08:51:25 -0000 --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004.11.25 22:04:30 -0800, Clint Olsen wrote: > I manage to run into situations where I need to learn more about how > pam works, yet when I do, quite a bit of the documentation is out of date. > References are made to manpages that don't exist. This is pretty > irritating. Where do I *really* find out about how pam works and all the > available modules? At the moment, see the PAM article - http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/pam/index.html . --=20 Simon L. Nielsen --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBpu6Kh9pcDSc1mlERAsVXAKCp2lLfbcYWmJTPpNYu7kwbVrxMRACfeBwa oWHgQcdqb+c1/GuGB6gz1vY= =CJ3F -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 26 09:52:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E47916A4CE for ; Fri, 26 Nov 2004 09:52:41 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D268A43D46 for ; Fri, 26 Nov 2004 09:52:40 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAQ9oipP058209; Fri, 26 Nov 2004 04:50:44 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iAQ9oi7D058206; Fri, 26 Nov 2004 09:50:44 GMT (envelope-from robert@fledge.watson.org) Date: Fri, 26 Nov 2004 09:50:44 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Jeff Roberson In-Reply-To: <20041120000743.G18094@mail.chesapeake.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 09:52:41 -0000 On Sat, 20 Nov 2004, Jeff Roberson wrote: > I have a patch that I would like people to test and review. It's > available here: > > http://www.chesapeake.net/~jroberson/smpffs.diff I built a GENERIC kernel from 6.x of yesterday with this patch, installed it on a box, and hen left it overnight. At some point during the night, the following was generated: login: lock order reversal 1st 0xc28e8bdc vnode interlock (vnode interlock) @ kern/vfs_subr.c:722 2nd 0xc251b044 struct mount mtx (struct mount mtx) @ kern/vfs_vnops.c:997 KDB: stack backtrace: witness_checkorder(c251b044,9,c081bc6e,3e5) at witness_checkorder+0x500 _mtx_lock_flags(c251b044,0,c081bc6e,3e5,c28e8bdc) at _mtx_lock_flags+0x40 vn_finished_write(c251b000,c2afec00,0,c282618c,c251b000) at vn_finished_write+0x21 getnewvnode(c0819ba0,c251b800,c2517500,ef16ea04) at getnewvnode+0x4ff ffs_vget(c251b800,13fb,2,ef16ea88) at ffs_vget+0x74 ufs_lookup(ef16eb38) at ufs_lookup+0x81e vfs_cache_lookup(ef16eba8,8,ef16ec44,c2afec00,0) at vfs_cache_lookup+0x25d lookup(ef16ec30,c2b40228,c2afec00,ef16ec08,c2b40200) at lookup+0x269 namei(ef16ec30,8064da8,0,0,c2762228) at namei+0x2a0 lstat(c2afec00,ef16ed14,2,10e,292) at lstat+0x4a syscall(805002f,805002f,bfbf002f,8064d00,8064d48) at syscall+0x128 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (190, FreeBSD ELF32, lstat), eip = 0x280c7707, esp = 0xbfbfeb9c, ebp = 0xbfbfec38 --- If it's a property of load, it presumably happened during the daily event... Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 15:55:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C578716A4CE for ; Thu, 25 Nov 2004 15:55:46 +0000 (GMT) Received: from firewall.exzodia.net (12-221-73-50.client.insightBB.com [12.221.73.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 899F643D1D for ; Thu, 25 Nov 2004 15:55:46 +0000 (GMT) (envelope-from awallac3@uiuc.edu) Received: from [192.168.0.5] (aaron [192.168.0.5]) by firewall.exzodia.net (Postfix) with ESMTP id 5364F1EF9 for ; Thu, 25 Nov 2004 09:52:05 -0600 (CST) Message-ID: <41A60006.3060708@uiuc.edu> Date: Thu, 25 Nov 2004 09:53:42 -0600 From: Aaron Wallace User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 26 Nov 2004 13:01:56 +0000 Subject: bug report: AMD64, 5.3, sym driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 15:55:46 -0000 I believe that I've found a bug with the sym driver in AMD64. I don't have this problem with 5.3 under i386. I wasn't able to submit this report via web because the anti-spam code wasn't being recognized. The problem occurs during boot up / driver detect. I get the following messages in bootup which I've manually copied: sym0: <810a> port 0x9000-0x90ff mem 0xea094000-0xea0940ff irq 12 at device 7.0 on pci1 __sym_calloc2: failed to allocate HCB[4288] device_attach: sym0 attach returned 6 sym1: <1010-33> port 0x9400-0x94ff mem 0xea090000-0xea091fff,0xea097000-0xea0973ff irq 11 at device 9.0 on pci1 __sym_calloc2: failed to allocate HCB[4288] device_attach: sym1 attach returned 6 sym2: <1010-33> port 0x9800-0x98ff mem 0xea092000-0xea093fff,0xea098000-0xea0983ff irq 15 at device 9.1 on pci1 __sym_calloc2: failed to allocate HCB[4288] device_attach: sym2 attach returned 6 I was using the mini-inst boot CD from the iso images. I had to disable ACPI at bootup to not hang later in the boot sequence (after the detection of the single IDE device installed - a cdrom). This particular machine has a motherboard with an nforce3 chipset. As I mentioned, I don't have this problem with the i386 branch, but I do still have to disable ACPI. I tried an older version of AMD64.. I believe 5.2.1, and got the same result. One other thing to notice is that it also has a problem with my Symbios 810 card. Of course, as a result of this, none of my scsi hard drives are recognized and I can't install. From owner-freebsd-current@FreeBSD.ORG Fri Nov 26 08:14:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A422716A4CE for ; Fri, 26 Nov 2004 08:14:39 +0000 (GMT) Received: from pfepc.post.tele.dk (pfepc.post.tele.dk [195.41.46.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32A1343D1D for ; Fri, 26 Nov 2004 08:14:37 +0000 (GMT) (envelope-from pab@nerdheaven.dk) Received: from [127.0.0.1] (tux.nerdheaven.dk [193.88.12.43]) by pfepc.post.tele.dk (Postfix) with ESMTP id BDEF2262893; Fri, 26 Nov 2004 09:14:33 +0100 (CET) Message-ID: <41A6E5E5.1060109@nerdheaven.dk> Date: Fri, 26 Nov 2004 09:14:29 +0100 From: Jonas Hauge User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Paulius Bulotas , current@freebsd.org References: <20041125205025.GA972@devnull.lt> In-Reply-To: <20041125205025.GA972@devnull.lt> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 26 Nov 2004 13:01:56 +0000 Subject: Re: usb problem, triggered by ndis X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 08:14:39 -0000 Hi Paulius, Paulius Bulotas wrote: > kernel: ndis0: mem 0xc0200000-0xc0200fff irq 11 at device 2.0 on pci2 > kernel: ndis0: NDIS API version: 5.1 > kernel: ndis0: Ethernet address: 00:04:23:72:4a:75 > kernel: ndis0: 11b rates: 11Mbps 2Mbps 1Mbps 5.5Mbps With an Intel Pro/Wireless 2100 3B in the machine I would suggest you to use ipw(4) instead of the ndis-framework. Ipw (and iwi for 2200BG) is located at: http://damien.bergamini.free.fr/ipw/ -- Jonas Hauge From owner-freebsd-current@FreeBSD.ORG Fri Nov 26 13:08:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBEA816A4CE for ; Fri, 26 Nov 2004 13:08:15 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3D0D43D45 for ; Fri, 26 Nov 2004 13:08:15 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CXfpf-0005UQ-7C; Fri, 26 Nov 2004 05:08:15 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16807.10942.710868.490640@ran.psg.com> Date: Fri, 26 Nov 2004 05:08:14 -0800 To: FreeBSD Current Subject: crash on just cvsupped build X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 13:08:15 -0000 6-current just cvsupped crashes within five mins Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x104 fault code = supervisor read, page not present instruction pointer = 0x8:0xc04b417c stack pointer = 0x10:0xe6d9c95c frame pointer = 0x10:0xe6d9c970 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 486 (asterisk) [thread pid 486 tid 100145 ] Stopped at _mtx_lock_sleep+0x9c: cmpl $0x4,0x104(%ebx) db> trace Tracing pid 486 tid 100145 td 0xc2427780 _mtx_lock_sleep(c237e45c,c2427780,0,c25aaedb,6ac) at _mtx_lock_sleep+0x9c _mtx_lock_flags(c237e45c,0,c25aaedb,6ac,2) at _mtx_lock_flags+0x45 zt_clone(0,c23cce00,3,c1f92ac0,c2427780) at zt_clone+0x71 zt_timing_open(c23cce00,3,c2427780,c04e72b5,e6d9ca04) at zt_timing_open+0xbd ztopen(c23cce00,3,2000,c2427780,e6d9ca48) at ztopen+0x6c devfs_open(e6d9ca6c,e6d9ca64,c05f6159,180,c2427780) at devfs_open+0x1d1 vn_open_cred(e6d9cbd8,e6d9ccd8,0,c1e91780,12) at vn_open_cred+0x3f1 vn_open(e6d9cbd8,e6d9ccd8,0,12,0) at vn_open+0x33 kern_open(c2427780,284488b6,0,3,0) at kern_open+0x113 open(c2427780,e6d9cd14,c,c2427780,6) at open+0x30 syscall(2f,2f,2f,80db000,0) at syscall+0x330 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (5, FreeBSD ELF32, open), eip = 0x2830b10f, esp = 0xbfbfe9ec, ebp = 0xbfbfea08 --- From owner-freebsd-current@FreeBSD.ORG Fri Nov 26 16:56:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51B7716A4CE for ; Fri, 26 Nov 2004 16:56:28 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id D259C43D55 for ; Fri, 26 Nov 2004 16:56:27 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) iAQGuMLO075517; Fri, 26 Nov 2004 11:56:22 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)iAQGuMBo075514; Fri, 26 Nov 2004 11:56:22 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Fri, 26 Nov 2004 11:56:22 -0500 (EST) From: Andre Guibert de Bruet To: Samuel Clements In-Reply-To: <007201c4d190$3c6bf3a0$d232a8c0@LCI> Message-ID: <20041126114903.A76729@alpha.siliconlandmark.com> References: <71F713C5E3CB7F4F9ACCBBB8E9BE318A39E348@blrx2kmbgl101.blr.amer.dell.com> <007201c4d190$3c6bf3a0$d232a8c0@LCI> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: freebsd-current@freebsd.org Subject: Re: supported new Dell PERC cards - need to add to the Hardwarenotes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 16:56:28 -0000 On Tue, 23 Nov 2004, Samuel Clements wrote: > For what its worth, it appears the Intel SRCU42X (SCSI RAID) and SRCS16 (SATA > RAID) are supported by amr as well: > > amr0: mem 0xf0000000-0xf000ffff irq 16 at device 1.0 on > pci3 > amr0: Firmware 713K, BIOS G401, > 64MB RAM This looks like a plain old LSI MegaRAID 320-1. > amr0: mem 0xfc780000-0xfc7fffff,0xfc2f0000-0xfc2fffff irq > 19 at device 0.0 on pci4 > amr0: Firmware 413Y, BIOS H420, > 128MB RAM And this beast has the firmware signatures and memory of the 320-4X. > I love this re-branding stuff! This practice is done by just about every server manufacturer out there. If you order SCSI RAID on a server, it is safe to bet that it is either an Adaptec or an LSI controller that you are going to end up with. >From my experiences with Dell, their newer PERC controllers are LSI-based. Regards, Andy | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ > From owner-freebsd-current@FreeBSD.ORG Fri Nov 26 18:05:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83EB716A4CE for ; Fri, 26 Nov 2004 18:05:29 +0000 (GMT) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id C525643D48 for ; Fri, 26 Nov 2004 18:05:28 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.43 (FreeBSD)) id 1CXkTG-0003Hy-P4 for current@freebsd.org; Fri, 26 Nov 2004 21:05:26 +0300 From: Vladimir Grebenschikov To: "current@freebsd.org" Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: SWsoft Date: Fri, 26 Nov 2004 21:05:25 +0300 Message-Id: <1101492325.996.54.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.0FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Subject: ptrace broken on latest CURRENT ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 18:05:29 -0000 Hi % truss ls truss: PIOCBIS: Inappropriate ioctl for device % strace ls PIOCSFL: Inappropriate ioctl for device trouble opening proc file % mount | fgrep proc linprocfs on /usr/compat/linux/proc (linprocfs, local) procfs on /proc (procfs, local) % (2 days old current -CURRENT) preemption enabled in kernel, 4BSD scheduler -- Vladimir B. Grebenchikov vova@fbsd.ru From owner-freebsd-current@FreeBSD.ORG Fri Nov 26 18:46:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82E4C16A4CE for ; Fri, 26 Nov 2004 18:46:51 +0000 (GMT) Received: from zaphod.nitro.dk (port324.ds1-khk.adsl.cybercity.dk [212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED82643D39 for ; Fri, 26 Nov 2004 18:46:50 +0000 (GMT) (envelope-from simon@zaphod.nitro.dk) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id 7D7B611A5B; Fri, 26 Nov 2004 19:46:49 +0100 (CET) Date: Fri, 26 Nov 2004 19:46:49 +0100 From: "Simon L. Nielsen" To: Samuel Clements Message-ID: <20041126184648.GA803@zaphod.nitro.dk> References: <71F713C5E3CB7F4F9ACCBBB8E9BE318A39E348@blrx2kmbgl101.blr.amer.dell.com> <20041123105313.GC753@zaphod.nitro.dk> <007201c4d190$3c6bf3a0$d232a8c0@LCI> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Kj7319i9nmIyA2yE" Content-Disposition: inline In-Reply-To: <007201c4d190$3c6bf3a0$d232a8c0@LCI> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: supported new Dell PERC cards - need to add to the Hardwarenotes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 18:46:51 -0000 --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004.11.23 11:11:29 -0800, Samuel Clements wrote: > For what its worth, it appears the Intel SRCU42X (SCSI RAID) and SRCS16= =20 > (SATA RAID) are supported by amr as well: I just added them to the manual page, thanks! --=20 Simon L. Nielsen --Kj7319i9nmIyA2yE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBp3oYh9pcDSc1mlERAruVAKCJlv0NRgDYP4Km3oxspzHxwwe0SwCgxd/k 6giYB1quwVwqJi8nY/Xy6f8= =3Htu -----END PGP SIGNATURE----- --Kj7319i9nmIyA2yE-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 26 18:57:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8150A16A4CE for ; Fri, 26 Nov 2004 18:57:31 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2C2043D3F for ; Fri, 26 Nov 2004 18:57:30 +0000 (GMT) (envelope-from radovanovic@gmail.com) Received: by rproxy.gmail.com with SMTP id b11so246754rne for ; Fri, 26 Nov 2004 10:57:30 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=urXx16UkrQ51UB76CnzoUH93VMgwDxuG4EOrFQW3Uj5+7ae2UdjQ+RINZn0jTdJyhjIG026VAmOmARaX8rn1QeZZPiVReS1Q2HR6FF7+4Z7Q3uwJQZZEItroRBNDpBl8kzhYPJ89qRnFcY1qalQ5NoWRdmU6Y1Xla8yzOOjIe+A= Received: by 10.38.101.56 with SMTP id y56mr604955rnb; Fri, 26 Nov 2004 10:57:29 -0800 (PST) Received: by 10.38.151.48 with HTTP; Fri, 26 Nov 2004 10:57:29 -0800 (PST) Message-ID: <8a2be41b0411261057599ce021@mail.gmail.com> Date: Fri, 26 Nov 2004 19:57:29 +0100 From: Ivan Radovanovic To: freebsd-current@freebsd.org In-Reply-To: <8a2be41b041121044755a4baaf@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <8a2be41b041121044755a4baaf@mail.gmail.com> Subject: 5.3-Release Lucent modem, ppp or kernel problem? (SOLVED) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Ivan Radovanovic List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 18:57:31 -0000 Problem is solved setting debug.acpi.disabled="timer" in /boot/loader.conf ---------- Forwarded message ---------- From: Ivan Radovanovic Date: Sun, 21 Nov 2004 13:47:55 +0100 Subject: 5.3-Release Lucent modem, ppp or kernel problem? To: freebsd-current@freebsd.org I recently upgraded from FreeBSD 5.1 to FreeBSD 5.3-Release, after that I am experiencing problem with my Lucent modem. Modem refuses to connect to my isp, and after using term command in ppp I discovered that after trying to connect modem displays CONNECT 43300 NoEC and after that print some garbage characters (not only one character repeating but looks like random characters). I thought there could be problem with ppp program (since modem driver is same version as in 5.1), so I used ppp program from 5.1 (it is 3.1 version), but results are the same. Problem is not in modem hardware or line since same modem still works in FreeBSD 5.1. However I would like to get this modem working in 5.3 so I could completely migrate to FreeBSD 5.3. I also tried using generic kernel instead of my custom kernel but situation is the same. Any ideas what could be causing problems? Regards, Ivan From owner-freebsd-current@FreeBSD.ORG Fri Nov 26 19:02:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6666616A4CE for ; Fri, 26 Nov 2004 19:02:37 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id D083E43D68 for ; Fri, 26 Nov 2004 19:02:36 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.0.5] (adsl-68-250-184-205.dsl.wotnoh.ameritech.net [68.250.184.205]) (authenticated bits=0)iAQIgNeB051047 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 26 Nov 2004 13:42:24 -0500 (EST) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: Andre Guibert de Bruet Date: Fri, 26 Nov 2004 14:05:28 -0500 User-Agent: KMail/1.7 References: <200411231731.25019.jhb@FreeBSD.org> <20041126114500.A76729@alpha.siliconlandmark.com> In-Reply-To: <20041126114500.A76729@alpha.siliconlandmark.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2134847.AMDBJWt2rk"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411261405.41221.mistry.7@osu.edu> X-Spam-Status: No, hits=0.8 required=5.0 tests=BIZ_TLD autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on crumpet.united-ware.com cc: freebsd-current@freebsd.org Subject: Re: ATI TV Wonder support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 19:02:37 -0000 --nextPart2134847.AMDBJWt2rk Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 26 November 2004 11:47 am, you wrote: > On Tue, 23 Nov 2004, John Baldwin wrote: > > On Tuesday 23 November 2004 05:22 pm, Anish Mistry wrote: > >> On Tuesday 23 November 2004 04:48 pm, John Baldwin wrote: > >>> Actually, it looks like the patch changes the code to kick off a new > >>> kthread and that new kthread is going to need to acquire Giant at > >>> the start of its main() function and drop it before calling > >>> kthread_exit() and/or returning. > >> > >> How about the attached patch? > >> http://am-productions.biz/docs/msp34xx-giant-locking.c.diff > > > > Looks like a good candidate to me. > > I am interested in this patchset. Could you make the latest version > available somewhere? > > Thanks, > > | Andre Guibert de Bruet | Enterprise Software Consultant > > | Silicon Landmark, LLC. | http://siliconlandmark.com/ > This link is the latest to fix the panic when you have the new msp driver=20 compiled into the kernel. The associated PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D74305 http://am-productions.biz/docs/msp34xx-giant-locking.c.diff This is the patch to enable the ATI TV Wonder to work:(Justin's patch): http://am-productions.biz/docs/bktr.patch =2D-=20 Anish Mistry --nextPart2134847.AMDBJWt2rk Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBp36FxqA5ziudZT0RAponAJ4urC5hL2GwHwXkkuOyaUhBnYjqxQCggu8G kl4ioj0VBv2Jza1pCPeGEsE= =PllS -----END PGP SIGNATURE----- --nextPart2134847.AMDBJWt2rk-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 26 20:17:05 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 048C816A4CE for ; Fri, 26 Nov 2004 20:17:05 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id A286743D49 for ; Fri, 26 Nov 2004 20:17:04 +0000 (GMT) (envelope-from bsdunx@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so503303wri for ; Fri, 26 Nov 2004 12:17:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:mime-version:content-type:content-transfer-encoding; b=TkV3ctRuHKEKTHxnyA1HLPgIvpKjAny/96pbz1B+b2/y43A02gf0sm580U7uYcNGtOOPD0fMYh6OrfyKWeNNucetp0YMYiaGJJwA4WGY20GC+/IPHCleS/bJMldF64JEOkek75jQu05IiM+0uRn3NOfWG7amZ3KXXXEiJ7L7co0= Received: by 10.54.3.53 with SMTP id 53mr1225414wrc; Fri, 26 Nov 2004 12:17:04 -0800 (PST) Received: by 10.54.47.29 with HTTP; Fri, 26 Nov 2004 12:17:03 -0800 (PST) Message-ID: Date: Fri, 26 Nov 2004 15:17:03 -0500 From: Adam Gregoire To: freebsd-current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: rwatson@FreeBSD.org Subject: Re: Page fault in FreeBSD 5.3 on IBM e325, Dual AMD64 2.2GHz, 4GB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Adam Gregoire List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 20:17:05 -0000 Hello, I am also getting this same panic and am able to reproduce at will using gtk-gnutella, I just disabled SACK via sysctl, and will get back to you ASAP and let you know my results. Regards, Adam --- .sig Adam Gregoire "Quemadmodum possums scire utrum vere simus an solum sentiamus nos esse?" From owner-freebsd-current@FreeBSD.ORG Fri Nov 26 21:39:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BCEFE16A4CE for ; Fri, 26 Nov 2004 21:39:03 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DB7C43D45 for ; Fri, 26 Nov 2004 21:39:03 +0000 (GMT) (envelope-from bsdunx@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so508378wri for ; Fri, 26 Nov 2004 13:39:02 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=sn8b63bfjFEeGBT2cToAyipvV9Ow1wU/b4yJJg8VpMIo3O8U8eYh2dk+EcORfvEgIxoQsQuPhWsJHcSVpMrF/LyDKnq85aUcYuVvxP4WG7Szoi1vs6aF2gCzr+BAXHolrydRRpntNYP1W98lTz3IzUIrOIOq3ztqqKKtK7zUBmk= Received: by 10.54.3.53 with SMTP id 53mr1271696wrc; Fri, 26 Nov 2004 13:39:02 -0800 (PST) Received: by 10.54.47.29 with HTTP; Fri, 26 Nov 2004 13:39:02 -0800 (PST) Message-ID: Date: Fri, 26 Nov 2004 16:39:02 -0500 From: Adam Gregoire To: freebsd-current@freebsd.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: cc: rwatson@freebsd.org Subject: Re: Page fault in FreeBSD 5.3 on IBM e325, Dual AMD64 2.2GHz, 4GB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Adam Gregoire List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 21:39:03 -0000 On Fri, 26 Nov 2004 15:17:03 -0500, Adam Gregoire wrote: > I am also getting this same panic and am able to reproduce at will > using gtk-gnutella, I just disabled SACK via sysctl, and will get > back to you ASAP and let you know my results. Previously I could trigger this panic constantly in less then 30 minutes, I have been running for over 120 minutes now and no panic. Disabling SACK does indeed seem to work around the problem. --- .sig Adam Gregoire "Quemadmodum possums scire utrum vere simus an solum sentiamus nos esse?" From owner-freebsd-current@FreeBSD.ORG Fri Nov 26 21:49:32 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BE4616A4CF for ; Fri, 26 Nov 2004 21:49:32 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0D0C43D5C for ; Fri, 26 Nov 2004 21:49:31 +0000 (GMT) (envelope-from bsdunx@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so275684rnf for ; Fri, 26 Nov 2004 13:49:31 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:return-path:subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=kN5cGn6aRBI+U56fqSht+uOUQEzVa9RUKHSeFNjua8sHEQgDYeXxDZcyz3EaJsEkctOphY7irDTDKFGmCKkQjcep67NiFi9ib4rzfNHQ+X9NztaEoVravQdLxGF57WfjKrx0WiNQizZUjxvimvmDuv/6NITZA/wgvi8jBKz6LYU= Received: by 10.39.2.57 with SMTP id e57mr484049rni; Fri, 26 Nov 2004 13:49:31 -0800 (PST) Received: from localhost.localdomain ([24.76.125.169]) by smtp.gmail.com with ESMTP id 70sm11462rnc; Fri, 26 Nov 2004 13:49:31 -0800 (PST) From: Adam Gregoire To: freebsd-current@freebsd.org In-Reply-To: References: Content-Type: text/plain Date: Fri, 26 Nov 2004 16:49:24 -0500 Message-Id: <1101505769.27005.3.camel@S0106defaced0c0de.su.shawcable.net> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Re: Page fault in FreeBSD 5.3 on IBM e325, Dual AMD64 2.2GHz, 4GB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 21:49:32 -0000 If there is anything that I can do to help with this issue further please don't hesitate to contact me and I'll try patches or whatever else is neccessary. Note as previously mentioned by others, this does with both debug.mpsafenet = (0 || 1). Here is a little info about this box: ebola$ uname -a FreeBSD S0106defaced0c0de 6.0-CURRENT FreeBSD 6.0-CURRENT #5: Fri Nov 26 09:42:43 EST 2004 root@S0106defaced0c0de:/usr/obj/usr/src/sys/OPTMZD amd64 On Fri, 2004-11-26 at 16:39 -0500, Adam Gregoire wrote: > On Fri, 26 Nov 2004 15:17:03 -0500, Adam Gregoire wrote: > > > I am also getting this same panic and am able to reproduce at will > > using gtk-gnutella, I just disabled SACK via sysctl, and will get > > back to you ASAP and let you know my results. > > Previously I could trigger this panic constantly in less then 30 > minutes, I have been running for over 120 minutes now and no panic. > > Disabling SACK does indeed seem to work around the problem. -- .sig Adam Gregoire "Quemadmodum possums scire utrum vere simus an solum sentiamus nos esse?" From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 01:26:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4357016A4CE for ; Sat, 27 Nov 2004 01:26:28 +0000 (GMT) Received: from mail.iinet.net.au (mail-03.iinet.net.au [203.59.3.35]) by mx1.FreeBSD.org (Postfix) with SMTP id 0B2BA43D55 for ; Sat, 27 Nov 2004 01:26:27 +0000 (GMT) (envelope-from shinjii@virusinfo.rdksupportinc.com) Received: (qmail 26759 invoked from network); 27 Nov 2004 01:26:25 -0000 Received: from unknown (HELO ?10.100.3.105?) (203.173.42.29) by mail.iinet.net.au with SMTP; 27 Nov 2004 01:26:25 -0000 From: Warren Liddell To: freebsd-current@freebsd.org Date: Sat, 27 Nov 2004 11:26:14 +1000 User-Agent: KMail/1.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411271126.14855.shinjii@virusinfo.rdksupportinc.com> Subject: Mozilla crash on Print X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: shinjii@virusinfo.rdksupportinc.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 01:26:28 -0000 For the last month or so Mozilla Firefox continually crashes every time you goto print either a local or internet webpage. Any ideas/thoughts welcome. -- Yours Sincerely Shinjii http://virusinfo.rdksupportinc.com From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 02:19:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8218F16A4CE; Sat, 27 Nov 2004 02:19:54 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3929543D45; Sat, 27 Nov 2004 02:19:54 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8E946511F7; Fri, 26 Nov 2004 18:24:31 -0800 (PST) Date: Fri, 26 Nov 2004 18:24:31 -0800 From: Kris Kennaway To: phk@freeBSD.org Message-ID: <20041127022431.GA86442@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LQksG6bCIzRHxTLp" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i cc: current@FreeBSD.org Subject: Still getting fdesc sleep warning/lor X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 02:19:54 -0000 --LQksG6bCIzRHxTLp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sleeping on "fdesc" with the following non-sleepable locks held: exclusive sleep mutex fdesc r = 0 (0xc0740a40) locked @ kern/vfs_mount.c:967 KDB: stack backtrace: witness_warn(2,c5bdc528,c06e4cfe,c06e0dc6,c076ccb8) at witness_warn+0x175 msleep(c5bdc54c,c5bdc528,64,c06e0dc6,0) at msleep+0x47 checkdirs(c59eec00,f1599ca4,c7fd3000,c7fd3000,0) at checkdirs+0xe0 dounmount(c59eec00,8080000,c7fd3000,43a,307fffc) at dounmount+0x3fa unmount(c7fd3000,f1599d14,8,3ff,2) at unmount+0x1f4 syscall(2f,2f,2f,804a619,bfbfe74a) at syscall+0x13b Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (22, FreeBSD ELF32, unmount), eip = 0x280c5a63, esp = 0xbfbfe4dc, ebp = 0xbfbfe598 --- lock order reversal 1st 0xc0740a40 fdesc (fdesc) @ kern/vfs_mount.c:967 2nd 0xc07412e0 Giant (Giant) @ kern/kern_synch.c:236 KDB: stack backtrace: witness_checkorder(c07412e0,9,c06e4d0f,ec,c054432e) at witness_checkorder+0x5ed _mtx_lock_flags(c07412e0,0,c06e4d0f,ec,0) at _mtx_lock_flags+0x54 msleep(c5bdc54c,c5bdc528,64,c06e0dc6,0) at msleep+0x291 checkdirs(c59eec00,f1599ca4,c7fd3000,c7fd3000,0) at checkdirs+0xe0 dounmount(c59eec00,8080000,c7fd3000,43a,307fffc) at dounmount+0x3fa unmount(c7fd3000,f1599d14,8,3ff,2) at unmount+0x1f4 syscall(2f,2f,2f,804a619,bfbfe74a) at syscall+0x13b Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (22, FreeBSD ELF32, unmount), eip = 0x280c5a63, esp = 0xbfbfe4dc, ebp = 0xbfbfe598 --- dosirak# cvs -Rq status kern_descrip.c =================================================================== File: kern_descrip.c Status: Up-to-date Working revision: 1.257 Fri Nov 26 08:45:11 2004 Repository revision: 1.257 /c/ncvs/src/sys/kern/kern_descrip.c,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) Kris --LQksG6bCIzRHxTLp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBp+VfWry0BWjoQKURAk49AJ0V5xQKnfsbGcfGHpUQtcRidF1WNgCfcqm0 O87i1CPk90eDIA4wBB+pkUQ= =nGXm -----END PGP SIGNATURE----- --LQksG6bCIzRHxTLp-- From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 03:20:17 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B90C16A4CE for ; Sat, 27 Nov 2004 03:20:17 +0000 (GMT) Received: from mail1.webmaster.com (mail1.webmaster.com [216.152.64.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB28543D2F for ; Sat, 27 Nov 2004 03:20:16 +0000 (GMT) (envelope-from davids@webmaster.com) Received: from however by webmaster.com (MDaemon.PRO.v7.1.0.R) with ESMTP id md50000298868.msg for ; Fri, 26 Nov 2004 18:56:14 -0800 From: "David Schwartz" To: "freebsd-current@FreeBSD. org" Date: Fri, 26 Nov 2004 19:19:51 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Authenticated-Sender: joelkatz@webmaster.com X-Spam-Processed: mail1.webmaster.com, Fri, 26 Nov 2004 18:56:14 -0800 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 206.171.168.138 X-Return-Path: davids@webmaster.com X-MDaemon-Deliver-To: freebsd-current@FreeBSD.org X-MDAV-Processed: mail1.webmaster.com, Fri, 26 Nov 2004 18:56:18 -0800 Subject: RE: Add creation time to dynamic firewall rules X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: davids@webmaster.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 03:20:17 -0000 Below is my first attempt at adding code to keep the creation time for dynamic firewall rules. I also added a '-C' flag to 'ipfw' to show the creation time instead of the expiration time. This code is released under the same license as FreeBSD itself. Patch is against 5_STABLE, versions are in the diff entries. It is not yet tested, though it looks right and it compiles. DS --- ip_fw.h 1.89.2.2 2004/10/03 17:04:40 +++ ip_fw.h Fri Nov 26 18:51:15 2004 @@ -353,6 +353,7 @@ struct _ipfw_dyn_rule { u_int64_t bcnt; /* byte match counter */ struct ipfw_flow_id id; /* (masked) flow id */ u_int32_t expire; /* expire time */ + u_int32_t created; /* creation time */ u_int32_t bucket; /* which bucket in hash table */ u_int32_t state; /* state of this rule (typically a * combination of TCP flags) --- ip_fw2.c 1.54.2.3 2004/09/17 14:49:08 +++ ip_fw2.c Fri Nov 26 18:56:41 2004 @@ -1037,6 +1037,7 @@ add_dyn_rule(struct ipfw_flow_id *id, u_ r->id = *id; r->expire = time_second + dyn_syn_lifetime; + r->created = time_second; r->rule = rule; r->dyn_type = dyn_type; r->pcnt = r->bcnt = 0; @@ -3089,6 +3090,9 @@ ipfw_getrules(struct ip_fw_chain *chain, dst->expire = TIME_LEQ(dst->expire, time_second) ? 0 : dst->expire - time_second ; + dst->created = + TIME_LEQ(dst->created, time_second) ? + 0 : dst->created - time_second ; bp += sizeof(ipfw_dyn_rule); } } --- ipfw.8 1.150.2.4 2004/11/08 19:07:03 +++ ipfw.8 Fri Nov 26 18:59:20 2004 @@ -13,7 +13,7 @@ .Cm add .Ar rule .Nm -.Op Fl acdefnNStT +.Op Fl acCdefnNStT .Brq Cm list | show .Op Ar rule | first-last ... .Nm @@ -223,6 +223,10 @@ Implies When entering or showing rules, print them in compact form, i.e., without the optional "ip from any to any" string when this does not carry any additional information. +.It Fl C +When viewing dynamic firewall rules, print the number of +seconds since the rule was created rather than the number +of seconds until the rule expires. .It Fl d While listing, show dynamic rules in addition to static ones. .It Fl e --- ipfw2.c 1.54.2.3 2004/09/17 14:49:08 +++ ipfw2.c Fri Nov 26 18:57:04 2004 @@ -67,6 +67,7 @@ int show_sets, /* display rule sets */ test_only, /* only check syntax */ comment_only, /* only print action and comment */ + show_created, /* show creation time */ verbose; #define IP_MASK_ALL 0xffffffff @@ -1367,7 +1368,8 @@ show_dyn_ipfw(ipfw_dyn_rule *d, int pcwi if (pcwidth>0 || bcwidth>0) printf(" %*llu %*llu (%ds)", pcwidth, align_uint64(&d->pcnt), bcwidth, - align_uint64(&d->bcnt), d->expire); + align_uint64(&d->bcnt), + show_created ? d->created : d->expire); switch (d->dyn_type) { case O_LIMIT_PARENT: printf(" PARENT %d", d->count); @@ -3906,7 +3908,9 @@ ipfw_main(int oldac, char **oldav) case 'v': /* verbose */ verbose = 1; break; - + case 'C': /* created time */ + show_created = 1; + break; default: free_args(save_ac, save_av); return 1; From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 03:47:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74EDC16A4CE for ; Sat, 27 Nov 2004 03:47:26 +0000 (GMT) Received: from mail1.webmaster.com (mail1.webmaster.com [216.152.64.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4950643D54 for ; Sat, 27 Nov 2004 03:47:26 +0000 (GMT) (envelope-from davids@webmaster.com) Received: from however by webmaster.com (MDaemon.PRO.v7.1.0.R) with ESMTP id md50000298895.msg for ; Fri, 26 Nov 2004 19:23:30 -0800 From: "David Schwartz" To: "freebsd-current@FreeBSD. org" Date: Fri, 26 Nov 2004 19:47:00 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Authenticated-Sender: joelkatz@webmaster.com X-Spam-Processed: mail1.webmaster.com, Fri, 26 Nov 2004 19:23:30 -0800 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 206.171.168.138 X-Return-Path: davids@webmaster.com X-MDaemon-Deliver-To: freebsd-current@FreeBSD.org X-MDAV-Processed: mail1.webmaster.com, Fri, 26 Nov 2004 19:23:33 -0800 Subject: RE: Add creation time to dynamic firewall rules X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: davids@webmaster.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 03:47:26 -0000 Here it is, tested and working. There were two bugs in the previous post, pretty amazing for 7 lines of core. ;) Again, this patch adds the creation time to every dynamic firewall rule. This allows you to see how stable a connection is and to estimate the average bandwidth. A '-C' flag is added to 'ipfw' to display how much time since the rule was created rather than how long until it expires. The cost is 4 bytes per dynamic firewall rule. This is consumed kernel memory and copying when you dump the dynamic firewall rules. It also adds an extra computation when the rules are retrieved (to relativize the time, as is done with the expiration time). This patch is released under the FreeBSD license and I would like it to be considered for inclusion in the kernel. Patch is against 5_STABLE and should easily port to other streams. The version and time stamps are in the diff. Thanks. David Schwartz -- --- ip_fw.h 1.89.2.2 2004/10/03 17:04:40 +++ ip_fw.h Fri Nov 26 18:51:15 2004 @@ -353,6 +353,7 @@ struct _ipfw_dyn_rule { u_int64_t bcnt; /* byte match counter */ struct ipfw_flow_id id; /* (masked) flow id */ u_int32_t expire; /* expire time */ + u_int32_t created; /* creation time */ u_int32_t bucket; /* which bucket in hash table */ u_int32_t state; /* state of this rule (typically a * combination of TCP flags) --- ip_fw2.c 1.54.2.3 2004/09/17 14:49:08 +++ ip_fw2.c Fri Nov 26 18:56:41 2004 @@ -1037,6 +1037,7 @@ add_dyn_rule(struct ipfw_flow_id *id, u_ r->id = *id; r->expire = time_second + dyn_syn_lifetime; + r->created = time_second; r->rule = rule; r->dyn_type = dyn_type; r->pcnt = r->bcnt = 0; @@ -3089,6 +3090,9 @@ ipfw_getrules(struct ip_fw_chain *chain, dst->expire = TIME_LEQ(dst->expire, time_second) ? 0 : dst->expire - time_second ; + dst->created = + TIME_LEQ(time_second, dst->created) ? + 0 : time_second - dst->created; bp += sizeof(ipfw_dyn_rule); } } --- ipfw.8 1.150.2.4 2004/11/08 19:07:03 +++ ipfw.8 Fri Nov 26 18:59:20 2004 @@ -13,7 +13,7 @@ .Cm add .Ar rule .Nm -.Op Fl acdefnNStT +.Op Fl acCdefnNStT .Brq Cm list | show .Op Ar rule | first-last ... .Nm @@ -223,6 +223,10 @@ Implies When entering or showing rules, print them in compact form, i.e., without the optional "ip from any to any" string when this does not carry any additional information. +.It Fl C +When viewing dynamic firewall rules, print the number of +seconds since the rule was created rather than the number +of seconds until the rule expires. .It Fl d While listing, show dynamic rules in addition to static ones. .It Fl e --- ipfw2.c 1.54.2.3 2004/09/17 14:49:08 +++ ipfw2.c Fri Nov 26 18:57:04 2004 @@ -67,6 +67,7 @@ int show_sets, /* display rule sets */ test_only, /* only check syntax */ comment_only, /* only print action and comment */ + show_created, /* show creation time */ verbose; #define IP_MASK_ALL 0xffffffff @@ -1367,7 +1368,8 @@ show_dyn_ipfw(ipfw_dyn_rule *d, int pcwi if (pcwidth>0 || bcwidth>0) printf(" %*llu %*llu (%ds)", pcwidth, align_uint64(&d->pcnt), bcwidth, - align_uint64(&d->bcnt), d->expire); + align_uint64(&d->bcnt), + show_created ? d->created : d->expire); switch (d->dyn_type) { case O_LIMIT_PARENT: printf(" PARENT %d", d->count); @@ -3843,7 +3845,7 @@ ipfw_main(int oldac, char **oldav) save_av = av; optind = optreset = 0; - while ((ch = getopt(ac, av, "abcdefhnNqs:STtv")) != -1) + while ((ch = getopt(ac, av, "abcCdefhnNqs:STtv")) != -1) switch (ch) { case 'a': do_acct = 1; @@ -3906,7 +3908,9 @@ ipfw_main(int oldac, char **oldav) case 'v': /* verbose */ verbose = 1; break; - + case 'C': /* created time */ + show_created = 1; + break; default: free_args(save_ac, save_av); return 1; From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 09:21:05 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7871216A4CE for ; Sat, 27 Nov 2004 09:21:05 +0000 (GMT) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44BE143D41 for ; Sat, 27 Nov 2004 09:21:04 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received-SPF: pass (eva.fit.vutbr.cz: domain of xdivac02@eva.fit.vutbr.cz designates 127.0.0.1 as permitted sender) receiver=eva.fit.vutbr.cz; client_ip=127.0.0.1; envelope-from=xdivac02@eva.fit.vutbr.cz; Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (8.12.11/8.12.11) with ESMTP id iAR9L09W093866 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 27 Nov 2004 10:21:00 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.12.11/8.12.5/Submit) id iAR9L0mE093865 for current@freebsd.org; Sat, 27 Nov 2004 10:21:00 +0100 (CET) Date: Sat, 27 Nov 2004 10:20:59 +0100 From: Divacky Roman To: current@freebsd.org Message-ID: <20041127092059.GA93818@stud.fit.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) Subject: ACPI related panic on early boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 09:21:05 -0000 Hi, after jhb@-s commits to acpi I am getting this panic early on boot, its handwritten so there might be mistakes. I have acpi as a module, and the panic seems to occur after probing fdc wihle I have no fdc attached. I can provide any info you ask for... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x5 fault code = supervisor read, page not present instruction pointer = 0x8:0xc049fb86 stack pointer = 0x10:0xc0820c88 frame pointer = 0x10:0xc0820c8c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) [thread pid 0 tid 0] Stopped at device_get_children+0x10: movl 0x4(%eax),%eax db>trace Tracing pid 0 tid 0 td 0xc05f7de0 device_get_children(c1646100,c0820ca4,c0820ca8,c05d5bc0,101) at device_get_children+0x10 acpi_wake_sysctl_walk(c157bb00,c1670a00,31,c157bb00,c157bb00) at acpi_wake_sysctl_walk+0x17 acpi_wake_sysctl_walk(fee00fff,fee00000,c163a028,3,c07072a0) at acpi_wake_sysctl_walk+0x44 acpi_attach(c157bb00,c157bb00,c1573dc0,c157bc00,c0820d34) at acpi_attach+0x684 device_attach(c157bb00,c157bc00,c0820d48,c058feb3,c157bc00) at device_attach+0x226 bus_generic_attach(c157bc00,c157bc00,c157bc4c,c0820d60,c04a039c) at bus_generic_attach+0x14 nexus_attach(c157bc00,c157bc00,0,825000,c0820d70) at nexus_attach+0x13 device_attach(c157bc00) at device_attach+0x226 root_bus_configure(c15ca300,c05c5eec,0,c0820d98,c0468fab) at root_bus_configure+0x16 configure(0,81ec00,81e000,0,c0429e05) at configure+0x1b mi_startup() at mi_startup+0x86 begin() at begin+0x2c roman From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 09:33:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CED6916A4CE for ; Sat, 27 Nov 2004 09:33:09 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7468B43D49 for ; Sat, 27 Nov 2004 09:33:09 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (ketrien@error404.nls.net [216.144.36.24]) by error404.nls.net (8.13.1/8.13.1) with ESMTP id iAR9X8AE069978; Sat, 27 Nov 2004 04:33:08 -0500 (EST) (envelope-from ketrien@error404.nls.net) Date: Sat, 27 Nov 2004 04:33:08 -0500 (EST) From: "Ketrien I. Saihr-Kenchedra" X-X-Sender: ketrien@bahre.achedra.org To: Divacky Roman In-Reply-To: <20041127092059.GA93818@stud.fit.vutbr.cz> Message-ID: <20041127042132.B57049@bahre.achedra.org> References: <20041127092059.GA93818@stud.fit.vutbr.cz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: current@freebsd.org Subject: Re: ACPI related panic on early boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 09:33:09 -0000 On Sat, 27 Nov 2004, Divacky Roman wrote: > Hi, > > after jhb@-s commits to acpi I am getting this panic early on boot, its > handwritten so there might be mistakes. > I have acpi as a module, and the panic seems to occur after probing fdc wihle I > have no fdc attached. I can provide any info you ask for... I've seen the same trace in a non-fatal LOR with my pcn(4) MPSAFE patches. Had absolutely no luck reproducing it, so I ended up writing it off as a one-time thing. (The same system has rebooted, same kernel, no changes, LOR has not reoccured.) Only thing I can think of that's different is possibly my ACPI tree here; acpi.c 1.193, acpi_pcib.c 1.51, pcib_pci.c 1.10, pci_link.c 1.33. I tried reproducing again just a few minutes ago, still nothing. -Ketrien I. Saihr-Kenchedra Ozzy (Today at 2:52:32AM) -- Ahaha. I quote: "Perhaps I mentioned the experience of SWMBO with Sun's internal support who, upon seeing a request from her that ssh be installed on her machine, replied that there were several shells already installed." From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 11:10:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C108E16A4CE for ; Sat, 27 Nov 2004 11:10:53 +0000 (GMT) Received: from guzas.devnull.lt (clt-84-32-40-211.ktv.lt [84.32.40.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5A0743D6D for ; Sat, 27 Nov 2004 11:10:52 +0000 (GMT) (envelope-from paulius@devnull.lt) Received: by guzas.devnull.lt (Postfix, from userid 1001) id 0DA0E64; Sat, 27 Nov 2004 13:10:52 +0200 (EET) Date: Sat, 27 Nov 2004 13:10:52 +0200 From: Paulius Bulotas To: freebsd-current@freebsd.org Message-ID: <20041127111052.GA751@devnull.lt> Mail-Followup-To: freebsd-current@freebsd.org References: <20041125205025.GA972@devnull.lt> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041125205025.GA972@devnull.lt> X-URL: http://devnull.lt/ Subject: Re: usb problem, triggered by ndis X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 11:10:53 -0000 Hello, On 04 11 25, Paulius Bulotas wrote: > upgraded to todays -current and now I'm experiencing little annoying > problem with my usb devices. Output from log: > > kernel: ndis0: mem 0xc0200000-0xc0200fff irq 11 at device 2.0 on pci2 > kernel: ums0: at uhub1 port 1 (addr 2) disconnected > kernel: ums0: detached > moused: unable to open /dev/ums0: No such file or directory > kernel: ndis0: link up > The ports seem to be dead (tested with ums, umass) after I enable ndis. > These problems of course could be related to recent changes to usb code? strange thing ;) I moved usb support to modules, downgraded uhci.c to revision 1.156 and everything worked as expected ;) then tried upgrading uhci.c until 1.159, ant whats strange, it works now with latest version... At first I thought, that's hardware conflict (since intel wlan uses irq 11, and usb uses 11 and 5), but now it works. Paulius P.S. ipw was behaviour regarding ums was the same, except that it paniced FreeBSD in the end ;) From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 12:01:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B12E16A4CE; Sat, 27 Nov 2004 12:01:52 +0000 (GMT) Received: from insomnia.benzedrine.cx (insomnia.benzedrine.cx [62.65.145.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6292743D5D; Sat, 27 Nov 2004 12:01:51 +0000 (GMT) (envelope-from dhartmei@insomnia.benzedrine.cx) Received: from insomnia.benzedrine.cx (dhartmei@localhost [127.0.0.1]) iARC1nMZ022263 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Sat, 27 Nov 2004 13:01:50 +0100 (MET) Received: (from dhartmei@localhost) by insomnia.benzedrine.cx (8.13.1/8.12.10/Submit) id iARC1n57008056; Sat, 27 Nov 2004 13:01:49 +0100 (MET) Date: Sat, 27 Nov 2004 13:01:49 +0100 From: Daniel Hartmeier To: freebsd-net@freebsd.org, freebsd-current@freebsd.org Message-ID: <20041127120149.GE23786@insomnia.benzedrine.cx> References: <20041126203354.GB81834@astral-on.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041126203354.GB81834@astral-on.net> User-Agent: Mutt/1.4.1i Subject: Re: rsh is malfunctioning due to pf X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 12:01:52 -0000 On Fri, Nov 26, 2004 at 10:33:54PM +0200, Andrew Degtiariov wrote: > I have ipcad installed on 2 PC's running 5.3-RELEASE and 5-STABLE from > Nov 21. ipcad (ports/net-mgmt/ipcad) provides ability to control them > by rsh (ipcad implement rsh server by yourself). While using pf with > primitive rulesets rsh stops its working. It seems like pf drop short > packets. The 'short' reason is a little overloaded, it can have two meanings. The less likely case is where the mbuf didn't contain a complete IP header. More likely, the packet contains IP options, which pf blocks by default. You can isolate the problem by a) enabling debug logging with pfctl -xm and watching the console or /var/log/messages for messages from 'pf: ' b) dumping an entire packet that is being blocked, with tcpdump -s 1600 -nvvvetttSXi pflog0 c) adding 'allow-opts' to all your pass rules and see if the problem goes away Daniel From owner-freebsd-current@FreeBSD.ORG Fri Nov 26 20:34:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61A7616A4CE; Fri, 26 Nov 2004 20:34:06 +0000 (GMT) Received: from therion.astral-on.net (therion.astral-on.net [193.41.4.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7C9343D5A; Fri, 26 Nov 2004 20:34:04 +0000 (GMT) (envelope-from ad@astral-on.net) Received: from odin.astral-on.net (odin.astral-on.net [193.41.4.6]) iAQKXuFs063758; Fri, 26 Nov 2004 22:33:57 +0200 (EET) (envelope-from ad@astral-on.net) Received: from odin.astral-on.net (localhost [127.0.0.1]) by odin.astral-on.net (8.12.8p2/8.12.8) with ESMTP id iAQKXuwk093049; Fri, 26 Nov 2004 22:33:56 +0200 (EET) (envelope-from ad@odin.astral-on.net) Received: (from ad@localhost) by odin.astral-on.net (8.12.8p2/8.12.8/Submit) id iAQKXs5Z093048; Fri, 26 Nov 2004 22:33:55 +0200 (EET) Date: Fri, 26 Nov 2004 22:33:54 +0200 From: Andrew Degtiariov To: freebsd-net@freebsd.org Message-ID: <20041126203354.GB81834@astral-on.net> Mail-Followup-To: freebsd-net@freebsd.org, freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i X-Mailman-Approved-At: Sat, 27 Nov 2004 12:56:27 +0000 cc: freebsd-current@freebsd.org Subject: rsh is malfunctioning due to pf X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ad@astral-on.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 20:34:06 -0000 Hello people. I have ipcad installed on 2 PC's running 5.3-RELEASE and 5-STABLE from Nov 21. ipcad (ports/net-mgmt/ipcad) provides ability to control them by rsh (ipcad implement rsh server by yourself). While using pf with primitive rulesets rsh stops its working. It seems like pf drop short packets. Using tcpdump -n -e -ttt -i pflog0 I see: ... 294896 rule 1/3(short): pass out on lo0: IP 127.0.0.1.514 > 127.0.0.1.680: FP 0:387(387) ack 18 win 35840 ... Some parts from pfctl -sa output FILTER RULES: pass in quick all pass out quick all ... Counters match 1319 8.1/s bad-offset 0 0.0/s fragment 0 0.0/s short 192 1.2/s normalize 0 0.0/s memory 0 0.0/s ... -- Andrew Degtiariov DA-RIPE From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 02:47:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 646D716A4CE for ; Sat, 27 Nov 2004 02:47:10 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 117B443D5E for ; Sat, 27 Nov 2004 02:47:10 +0000 (GMT) (envelope-from matt.thyer@gmail.com) Received: by wproxy.gmail.com with SMTP id 57so438045wri for ; Fri, 26 Nov 2004 18:47:09 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=o9PyCbsP1wf9IzbeMFW8bGS1zQvv60jSOaIiBlqk56uhaHSO8Xmrr5ijhTqeeGQM7GOCU3LV2qFidMQtTwD3bsh8nT6eA9LHxfB0R6mREHzl2XOnZe0hXR5jMkJw0WEtvxWanWuUuCwd/7kMlMa+DRpUn5K0h1fLQp9jGs5v/aI= Received: by 10.54.23.3 with SMTP id 3mr1456014wrw; Fri, 26 Nov 2004 18:47:09 -0800 (PST) Received: by 10.54.18.37 with HTTP; Fri, 26 Nov 2004 18:47:09 -0800 (PST) Message-ID: Date: Sat, 27 Nov 2004 13:17:09 +1030 From: Matt Thyer To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 27 Nov 2004 12:56:27 +0000 Subject: Why don't the packages get built for the runtime dependencies of the package I am building ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Matt Thyer List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 02:47:10 -0000 I have been messing around with making releases and packages. I've been making packages with an alias which expands to the below: (sudo make clean; sudo make BATCH=YES PACKAGES=/home/me/Packages package clean && make describe >> ~/Packages/INDEX) The problem is that packages for the runtime dependencies of what I am building do not get made. Surely there is a simple way to have the runtime dependency packages built as well. Is this possible, or do I have to write my own script to recursively determine the runtime dependencies and build those packages first ? From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 13:33:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B7D916A4CE; Sat, 27 Nov 2004 13:33:33 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59B6A43D2D; Sat, 27 Nov 2004 13:33:32 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iARDXF3d096768; Sun, 28 Nov 2004 00:03:15 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org, Matt Thyer Date: Sun, 28 Nov 2004 00:03:14 +1030 User-Agent: KMail/1.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1339657.1ZdPlqxNeh"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411280003.14594.doconnor@gsoft.com.au> X-Spam-Score: -2.2 () IN_REP_TO,MIME_LONG_LINE_QP,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: current@freebsd.org Subject: Re: Why don't the packages get built for the runtime dependencies of the package I am building ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 13:33:33 -0000 --nextPart1339657.1ZdPlqxNeh Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sat, 27 Nov 2004 13:17, Matt Thyer wrote: > I have been messing around with making releases and packages. > > I've been making packages with an alias which expands to the below: > > (sudo make clean; sudo make BATCH=3DYES PACKAGES=3D/home/me/Packages > package clean && make describe >> ~/Packages/INDEX) > > The problem is that packages for the runtime dependencies of what I am > building do not get made. > > Surely there is a simple way to have the runtime dependency packages > built as well. > > Is this possible, or do I have to write my own script to recursively > determine the runtime dependencies and build those packages first ? Try.. make package DEPENDS_TARGET=3Dpackage Also make sure you build in a chroot so you don't get things not building=20 because the host environment already has them.. Here's a few notes I wrote down on release building if you're interested. http://www.gsoft.com.au/~doconnor/FreeBSD-release-2.html (4.x though) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1339657.1ZdPlqxNeh Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBqIIa5ZPcIHs/zowRAth7AKCGx0EY3RUfFVMHCTD4s8yrqnmn/QCeOq6I jQXUsgydIB42213GUvPMzk0= =0mX9 -----END PGP SIGNATURE----- --nextPart1339657.1ZdPlqxNeh-- From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 13:33:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B7D916A4CE; Sat, 27 Nov 2004 13:33:33 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59B6A43D2D; Sat, 27 Nov 2004 13:33:32 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iARDXF3d096768; Sun, 28 Nov 2004 00:03:15 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org, Matt Thyer Date: Sun, 28 Nov 2004 00:03:14 +1030 User-Agent: KMail/1.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1339657.1ZdPlqxNeh"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411280003.14594.doconnor@gsoft.com.au> X-Spam-Score: -2.2 () IN_REP_TO,MIME_LONG_LINE_QP,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: current@freebsd.org Subject: Re: Why don't the packages get built for the runtime dependencies of the package I am building ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 13:33:33 -0000 --nextPart1339657.1ZdPlqxNeh Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sat, 27 Nov 2004 13:17, Matt Thyer wrote: > I have been messing around with making releases and packages. > > I've been making packages with an alias which expands to the below: > > (sudo make clean; sudo make BATCH=3DYES PACKAGES=3D/home/me/Packages > package clean && make describe >> ~/Packages/INDEX) > > The problem is that packages for the runtime dependencies of what I am > building do not get made. > > Surely there is a simple way to have the runtime dependency packages > built as well. > > Is this possible, or do I have to write my own script to recursively > determine the runtime dependencies and build those packages first ? Try.. make package DEPENDS_TARGET=3Dpackage Also make sure you build in a chroot so you don't get things not building=20 because the host environment already has them.. Here's a few notes I wrote down on release building if you're interested. http://www.gsoft.com.au/~doconnor/FreeBSD-release-2.html (4.x though) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1339657.1ZdPlqxNeh Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBqIIa5ZPcIHs/zowRAth7AKCGx0EY3RUfFVMHCTD4s8yrqnmn/QCeOq6I jQXUsgydIB42213GUvPMzk0= =0mX9 -----END PGP SIGNATURE----- --nextPart1339657.1ZdPlqxNeh-- From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 15:33:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACD3B16A4CE for ; Sat, 27 Nov 2004 15:33:39 +0000 (GMT) Received: from maxlor.mine.nu (c-213-160-32-54.customer.ggaweb.ch [213.160.32.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2978A43D64 for ; Sat, 27 Nov 2004 15:33:39 +0000 (GMT) (envelope-from benlutz@datacomm.ch) Received: from localhost (localhost [127.0.0.1]) by maxlor.mine.nu (Postfix) with ESMTP id A222B1A1; Sat, 27 Nov 2004 16:33:37 +0100 (CET) Received: from maxlor.mine.nu ([127.0.0.1]) by localhost (midgard [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30348-05; Sat, 27 Nov 2004 16:33:35 +0100 (CET) Received: from merlin.intranet (merlin.intranet [10.0.0.16]) by maxlor.mine.nu (Postfix) with ESMTP id C8FC6153; Sat, 27 Nov 2004 16:33:35 +0100 (CET) From: Benjamin Lutz To: shinjii@virusinfo.rdksupportinc.com Date: Sat, 27 Nov 2004 16:33:32 +0100 User-Agent: KMail/1.7.1 References: <200411271126.14855.shinjii@virusinfo.rdksupportinc.com> In-Reply-To: <200411271126.14855.shinjii@virusinfo.rdksupportinc.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart8348798.4sKOAeUnGv"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411271633.35382.benlutz@datacomm.ch> X-Virus-Scanned: by amavisd-new at maxlor.mine.nu cc: freebsd-current@freebsd.org Subject: Re: Mozilla crash on Print X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 15:33:39 -0000 --nextPart8348798.4sKOAeUnGv Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline > For the last month or so Mozilla Firefox continually crashes every time > you goto print either a local or internet webpage. If you use CUPS, the issue's likely been fixed a few days ago. Portupgrade= =20 your firefox to version 1.0_3,1. See http://www.freshports.org/www/firefox for the cvs log entry. Benjamin --nextPart8348798.4sKOAeUnGv Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBqJ5PgShs4qbRdeQRAhU4AJ0QXEGfgmuq/b2RyiUnggzvLNVX8wCfYGZ7 OylkWCRWAV9UAp2u/uYqHsE= =uYHV -----END PGP SIGNATURE----- --nextPart8348798.4sKOAeUnGv-- From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 18:40:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D94416A4D1 for ; Sat, 27 Nov 2004 18:40:21 +0000 (GMT) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4271943D45 for ; Sat, 27 Nov 2004 18:40:21 +0000 (GMT) (envelope-from pbowen25@juno.com) Received: from frontend2.messagingengine.com (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id C7839C3C17B for ; Sat, 27 Nov 2004 13:40:17 -0500 (EST) X-Sasl-enc: agLiVKGqVLeB+5heOyqO1g 1101580815 Received: from juno.com (unknown [204.110.228.254]) by frontend2.messagingengine.com (Postfix) with ESMTP id E641857010A for ; Sat, 27 Nov 2004 13:40:14 -0500 (EST) Message-ID: <41A8C9C3.1020504@juno.com> Date: Sat, 27 Nov 2004 12:38:59 -0600 From: Patrick Bowen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Getting devfs to recognize a hotplugged fd0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 18:40:21 -0000 I'm trying to learn how to get devfs to create an fd0 enty in /dev automatically when I plug a floppy drive into the serial port of a running Dell D600 laptop running 6.0 current. I've looked at 'man devfs/devfs.conf/devfs.rules', searched the lists, searched the web, etc. this is either really simple, and I/m trying to make it complicated (probably), or no one else is trying to do this (probably not). If someone can point me in the right direction, I'd appreciate it. TIA, Patrick From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 18:52:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50E9F16A4CE for ; Sat, 27 Nov 2004 18:52:54 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 142C743D1F for ; Sat, 27 Nov 2004 18:52:53 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id F111851295; Sat, 27 Nov 2004 10:57:32 -0800 (PST) Date: Sat, 27 Nov 2004 10:57:32 -0800 From: Kris Kennaway To: Matt Thyer Message-ID: <20041127185732.GA35366@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5vNYLRcllDrimb99" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: Why don't the packages get built for the runtime dependencies of the package I am building ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 18:52:54 -0000 --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 27, 2004 at 01:17:09PM +1030, Matt Thyer wrote: > I have been messing around with making releases and packages. >=20 > I've been making packages with an alias which expands to the below: >=20 > (sudo make clean; sudo make BATCH=3DYES PACKAGES=3D/home/me/Packages > package clean && make describe >> ~/Packages/INDEX) >=20 > The problem is that packages for the runtime dependencies of what I am > building do not get made. >=20 > Surely there is a simple way to have the runtime dependency packages > built as well. >=20 > Is this possible, or do I have to write my own script to recursively > determine the runtime dependencies and build those packages first ? Does 'make package-recursive' not work? Kris --5vNYLRcllDrimb99 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBqM4cWry0BWjoQKURApXpAJ9QcJE/HOvFmI2/whEdTp2Jo6LvlwCeKGBT 821nrfGjQMwTgAEvTeZLR6o= =W1xc -----END PGP SIGNATURE----- --5vNYLRcllDrimb99-- From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 19:23:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E192016A4CE for ; Sat, 27 Nov 2004 19:23:48 +0000 (GMT) Received: from sukke.il.fontys.nl (sukke.il.fontys.nl [145.85.127.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72D5A43D1F for ; Sat, 27 Nov 2004 19:23:48 +0000 (GMT) (envelope-from ed@il.fontys.nl) Received: from penguin.il.fontys.nl ([145.85.127.3]) by sukke.il.fontys.nl with smtp (Exim 4.42) id 1CY8Ab-0004L6-DL; Sat, 27 Nov 2004 20:23:45 +0100 Received: by penguin.il.fontys.nl (sSMTP sendmail emulation); Sat, 27 Nov 2004 20:22:57 +0100 From: "Ed Schouten" Date: Sat, 27 Nov 2004 20:22:57 +0100 To: Patrick Bowen Message-ID: <20041127192257.GA10638@il.fontys.nl> References: <41A8C9C3.1020504@juno.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fdj2RfSjLxBAspz7" Content-Disposition: inline In-Reply-To: <41A8C9C3.1020504@juno.com> X-Message-Flag: How are you gentlemen? All your flags are belong to us! User-Agent: Mutt/1.5.6i X-Spam-Score: -3.7 (---) X-Spam-Report: Spam detection software, running on the system "sukke.il.fontys.nl", hasmessageblock similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hello Patrick, Patrick Bowen wrote: > I'm trying to learn how to get devfs to create an fd0 enty in /dev > automatically when I plug a floppy drive into the serial port of a > running Dell D600 laptop running 6.0 current. [...] Content analysis details: (-3.7 points, 5.0 required) pts rule name description --------------------------------------------------1% [score: 0.0000] 1.2 AWL AWL: Auto-whitelist adjustment cc: FreeBSD Current Subject: Re: Getting devfs to recognize a hotplugged fd0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: FreeBSD Current List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 19:23:49 -0000 --fdj2RfSjLxBAspz7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello Patrick, Patrick Bowen wrote: > I'm trying to learn how to get devfs to create an fd0 enty in /dev=20 > automatically when I plug a floppy drive into the serial port of a=20 > running Dell D600 laptop running 6.0 current. Are you sure that's possible at all? You know the serial port isn't plug-and-play? How can the operating system tell that there is something on the serial port at all? :) Yours, --=20 Ed Schouten --fdj2RfSjLxBAspz7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFBqNQRyx16ydahrz4RAhfkAJwOSOhHw6sGz1ZdD1TVKvhRqiLWEwCgyCaI EVMNLvNn1Gos1McuWcweOrU= =PXad -----END PGP SIGNATURE----- --fdj2RfSjLxBAspz7-- From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 19:58:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B408A16A4CE for ; Sat, 27 Nov 2004 19:58:20 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88BC143D31 for ; Sat, 27 Nov 2004 19:58:20 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iARJwcCo009870; Sat, 27 Nov 2004 11:58:38 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iARJwckn009869; Sat, 27 Nov 2004 11:58:38 -0800 Date: Sat, 27 Nov 2004 11:58:38 -0800 From: Brooks Davis To: David Schwartz Message-ID: <20041127195838.GA9781@odin.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: "freebsd-current@FreeBSD. org" Subject: Re: Add creation time to dynamic firewall rules X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 19:58:20 -0000 --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 26, 2004 at 07:47:00PM -0800, David Schwartz wrote: >=20 > Here it is, tested and working. There were two bugs in the previous post, > pretty amazing for 7 lines of core. ;) >=20 > Again, this patch adds the creation time to every dynamic firewall rule. > This allows you to see how stable a connection is and to estimate the > average bandwidth. A '-C' flag is added to 'ipfw' to display how much time > since the rule was created rather than how long until it expires. >=20 > The cost is 4 bytes per dynamic firewall rule. This is consumed kernel > memory and copying when you dump the dynamic firewall rules. It also adds= an > extra computation when the rules are retrieved (to relativize the time, as > is done with the expiration time). >=20 > This patch is released under the FreeBSD license and I would like it to = be > considered for inclusion in the kernel. Patch is against 5_STABLE and sho= uld > easily port to other streams. The version and time stamps are in the diff. This seems reasionable to me, but I don't run a large dynamic firewall. You should post this to the freebsd-ipfw list to get more targeted review. -- Brooks --SLDf9lqlvOQaIe6s Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBqNxtXY6L6fI4GtQRAjXrAKCjVuQdBh5Tp0KONBxg16arxzPxGwCg081a DDeXIulv5dLEOFL55Mp1eu0= =C6Go -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s-- From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 19:58:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB60F16A4CE for ; Sat, 27 Nov 2004 19:58:38 +0000 (GMT) Received: from lon-mail-2.gradwell.net (lon-mail-2.gradwell.net [193.111.201.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1539443D66 for ; Sat, 27 Nov 2004 19:58:38 +0000 (GMT) (envelope-from cbh-freebsd-current@groups.chrishedley.com) Received: from cpc3-oxfd4-4-0-cust42.oxfd.cable.ntl.com ([80.3.247.42] helo=mail.cbhnet)1.156) id 41a8dc6c.b03d.4a for freebsd-current@freebsd.org; Sat, 27 Nov 2004 19:58:36 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.cbhnet (Postfix) with ESMTP id E73E531B01C for ; Sat, 27 Nov 2004 19:58:35 +0000 (GMT) Received: from mail.cbhnet ([127.0.0.1]) by localhost (mail.cbhnet [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 35690-04 for ; Sat, 27 Nov 2004 19:58:35 +0000 (GMT) Received: from teapot.cbhnet (teapot.cbhnet [192.168.1.1]) by mail.cbhnet (Postfix) with ESMTP id 98A3C31AFF5 for ; Sat, 27 Nov 2004 19:58:35 +0000 (GMT) Date: Sat, 27 Nov 2004 19:58:35 +0000 (GMT) From: Chris Hedley X-X-Sender: cbh@teapot.cbhnet To: freebsd-current@freebsd.org Message-ID: <20041127193532.X15946@teapot.cbhnet> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: amavisd-new at chrishedley.com Subject: GEOM: gpt partitions on a gmirror array possible? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 19:58:39 -0000 Hi all, A hopefully quick question! I have looked for a solution for (or discussion about) this, if I've just failed to find it, please point me in the right direction. This is what I'm trying to do: I've created a RAID-1 array, m1, using gmirror on two scsi units, da0 and da1, and I'd like to chop it up into logical partitions using gpt, as I understand (correctly, hopefully) there are leanings toward gpt rather than bsdlabel as being the correct way to do things. Now when I initialise and create my gpt partition on mirror/m1, I get no new entries in /dev/mirror but I _do_ get separate /dev/da0p1 and /dev/da1p1 entries appearing. I've probably completely failed to understand the whole concept of GEOM tasting and unprejudiced hierarchy and so on as I decided I may as well try to create my UFS2 filesystem on /dev/da0p1 in /dev/mirror/m1p1's absence and see if /dev/da1p1 magically follows suit. Needless to say it doesn't, I just end up with a dirty RAID-1 disc that needs resynchronising, with da0p1 (un)mysteriously disappearing after the newfs. Is there a correct way to do this, or am I once again guilty of trying to use something that isn't quite ready yet? Perhaps I should do it the other way around and use gpt first and create one gmirror per partition; that solution didn't "feel" right for some reason, but I can't really quantify that particularly as, if I understand the GEOM documentation correctly, multiple gmirrors with their respective paritions on the same set of discs shouldn't compete with each for access. My system is FreeBSD/amd64, 6.0-current (Oct 25th vintage) using ahc for my test scsi discs and aac for my active discs. Cheers, Chris. From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 21:17:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0820616A4CE for ; Sat, 27 Nov 2004 21:17:02 +0000 (GMT) Received: from mail.iinet.net.au (mail-08.iinet.net.au [203.59.3.40]) by mx1.FreeBSD.org (Postfix) with SMTP id 84DA743D49 for ; Sat, 27 Nov 2004 21:17:00 +0000 (GMT) (envelope-from shinjii@virusinfo.rdksupportinc.com) Received: (qmail 16679 invoked from network); 27 Nov 2004 21:16:59 -0000 Received: from unknown (HELO ?10.100.3.105?) (203.173.42.29) by mail.iinet.net.au with SMTP; 27 Nov 2004 21:16:58 -0000 From: Warren Liddell To: Benjamin Lutz Date: Sun, 28 Nov 2004 07:16:48 +1000 User-Agent: KMail/1.7.1 References: <200411271126.14855.shinjii@virusinfo.rdksupportinc.com> <200411271633.35382.benlutz@datacomm.ch> In-Reply-To: <200411271633.35382.benlutz@datacomm.ch> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411280716.48705.shinjii@virusinfo.rdksupportinc.com> cc: freebsd-current@freebsd.org Subject: Re: Mozilla crash on Print X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: shinjii@virusinfo.rdksupportinc.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 21:17:02 -0000 On Sun, 28 Nov 2004 01:33 am, Benjamin Lutz wrote: > > For the last month or so Mozilla Firefox continually crashes every time > > you goto print either a local or internet webpage. > > If you use CUPS, the issue's likely been fixed a few days ago. Portupgrade > your firefox to version 1.0_3,1. > > See http://www.freshports.org/www/firefox for the cvs log entry. > > Benjamin I don tuse CUPS and im usingf the latest version being i only just did a complete portupgrade before sending the original email :) -- Yours Sincerely Shinjii http://virusinfo.rdksupportinc.com From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 21:40:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A96616A4CE; Sat, 27 Nov 2004 21:40:34 +0000 (GMT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E42C43D3F; Sat, 27 Nov 2004 21:40:34 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.1/8.13.1) with ESMTP id iARLeJ15006376; Sat, 27 Nov 2004 13:40:23 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200411272140.iARLeJ15006376@gw.catspoiler.org> Date: Sat, 27 Nov 2004 13:40:19 -0800 (PST) From: Don Lewis To: shinjii@virusinfo.rdksupportinc.com, gnome@FreeBSD.org In-Reply-To: <200411280716.48705.shinjii@virusinfo.rdksupportinc.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: benlutz@datacomm.ch cc: freebsd-current@FreeBSD.org Subject: Re: Mozilla crash on Print X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 21:40:34 -0000 On 28 Nov, Warren Liddell wrote: > On Sun, 28 Nov 2004 01:33 am, Benjamin Lutz wrote: >> > For the last month or so Mozilla Firefox continually crashes every time >> > you goto print either a local or internet webpage. >> >> If you use CUPS, the issue's likely been fixed a few days ago. Portupgrade >> your firefox to version 1.0_3,1. >> >> See http://www.freshports.org/www/firefox for the cvs log entry. >> >> Benjamin > > I don tuse CUPS and im usingf the latest version being i only just did a > complete portupgrade before sending the original email :) I just got a crash with this Firefox 1.0_3,1 running on 4.10-STABLE. I am using CUPS. Here's the stack trace: This GDB was configured as "i386-unknown-freebsd"... (no debugging symbols found)... Core was generated by `firefox-bin'. Program terminated with signal 11, Segmentation fault. [snip] #0 0x2895f360 in kill () from /usr/lib/libc_r.so.4 #1 0x28956770 in raise () from /usr/lib/libc_r.so.4 #2 0x8057c6d in nsProfileLock::FatalSignalHandler () #3 0x28971d60 in _thread_sig_handler () from /usr/lib/libc_r.so.4 #4 0x28971bc3 in _thread_sig_handler () from /usr/lib/libc_r.so.4 #5 0xbfbfffac in ?? () #6 0x29a48601 in X509_check_private_key () from /usr/lib/libcrypto.so.3 #7 0x29a489c0 in EVP_DigestFinal_ex () from /usr/lib/libcrypto.so.3 #8 0x29a38609 in RAND_SSLeay () from /usr/lib/libcrypto.so.3 #9 0x29a3873b in RAND_SSLeay () from /usr/lib/libcrypto.so.3 #10 0x29a381cd in RAND_seed () from /usr/lib/libcrypto.so.3 #11 0x29d813b1 in httpInitialize () from /usr/local/lib/libcups.so.2 #12 0x29d8152b in httpConnectEncrypt () from /usr/local/lib/libcups.so.2 #13 0x29d7ebc9 in cupsGetDests () from /usr/local/lib/libcups.so.2 #14 0x28e18bf6 in GlobalPrinters::InitializeGlobalPrinters () from /usr/X11R6/lib/firefox/components/libgfx_gtk.so #15 0x28e19367 in GlobalPrinters::GetDefaultPrinterName () from /usr/X11R6/lib/firefox/components/libgfx_gtk.so #16 0x28e16f59 in nsPrinterEnumeratorGTK::GetDefaultPrinterName () from /usr/X11R6/lib/firefox/components/libgfx_gtk.so #17 0x28a70367 in nsPrintOptions::GetDefaultPrinterName () from /usr/X11R6/lib/firefox/libgkgfx.so #18 0x281a07a4 in XPTC_InvokeByIndex () from /usr/X11R6/lib/firefox/libxpcom.so #19 0x28bc9f6b in XPCWrappedNative::CallMethod () from /usr/X11R6/lib/firefox/components/libxpconnect.so #20 0x28bd0649 in XPC_WN_GetterSetter () from /usr/X11R6/lib/firefox/components/libxpconnect.so #21 0x280b8a9a in js_Invoke () from /usr/X11R6/lib/firefox/libmozjs.so #22 0x280b8cf6 in js_InternalInvoke () from /usr/X11R6/lib/firefox/libmozjs.so #23 0x280b8e43 in js_InternalGetOrSet () from /usr/X11R6/lib/firefox/libmozjs.so #24 0x280cb243 in js_GetProperty () from /usr/X11R6/lib/firefox/libmozjs.so #25 0x280bf142 in js_Interpret () from /usr/X11R6/lib/firefox/libmozjs.so #26 0x280b8af0 in js_Invoke () from /usr/X11R6/lib/firefox/libmozjs.so #27 0x280b8cf6 in js_InternalInvoke () from /usr/X11R6/lib/firefox/libmozjs.so #28 0x280979ca in JS_CallFunctionValue () from /usr/X11R6/lib/firefox/libmozjs.so #29 0x293eb7f4 in nsJSContext::CallEventHandler () from /usr/X11R6/lib/firefox/components/libgklayout.so #30 0x29426d50 in nsJSEventListener::HandleEvent () from /usr/X11R6/lib/firefox/components/libgklayout.so #31 0x292956bf in nsEventListenerManager::HandleEventSubType () from /usr/X11R6/lib/firefox/components/libgklayout.so #32 0x29295a04 in nsEventListenerManager::HandleEvent () from /usr/X11R6/lib/firefox/components/libgklayout.so #33 0x29455798 in nsXULElement::HandleDOMEvent () from /usr/X11R6/lib/firefox/components/libgklayout.so #34 0x294545c1 in nsXULElement::HandleDOMEvent () from /usr/X11R6/lib/firefox/components/libgklayout.so #35 0x2910b7f1 in PresShell::HandleDOMEventWithTarget () from /usr/X11R6/lib/firefox/components/libgklayout.so #36 0x291d6405 in nsMenuFrame::Execute () from /usr/X11R6/lib/firefox/components/libgklayout.so #37 0x291d02bd in nsMenuFrame::HandleEvent () from /usr/X11R6/lib/firefox/components/libgklayout.so #38 0x2910b6c1 in PresShell::HandleEventInternal () from /usr/X11R6/lib/firefox/components/libgklayout.so #39 0x2910b0da in PresShell::HandleEvent () from /usr/X11R6/lib/firefox/components/libgklayout.so #40 0x293e3751 in nsViewManager::HandleEvent () from /usr/X11R6/lib/firefox/components/libgklayout.so #41 0x293e2c01 in nsViewManager::DispatchEvent () from /usr/X11R6/lib/firefox/components/libgklayout.so #42 0x293db189 in HandleNumbers () from /usr/X11R6/lib/firefox/components/libgklayout.so #43 0x28b070c9 in nsCommonWidget::DispatchEvent () from /usr/X11R6/lib/firefox/components/libwidget_gtk2.so #44 0x28afefd8 in nsWindow::OnButtonReleaseEvent () from /usr/X11R6/lib/firefox/components/libwidget_gtk2.so #45 0x28b03121 in nsWindow::DragInProgress () from /usr/X11R6/lib/firefox/components/libwidget_gtk2.so #46 0x283ec5ef in gtk_marshal_VOID__UINT_STRING () from /usr/X11R6/lib/libgtk-x11-2.0.so.400 #47 0x2880d0c1 in g_closure_invoke () from /usr/local/lib/libgobject-2.0.so.400 #48 0x28822b9a in signal_emit_unlocked_R () from /usr/local/lib/libgobject-2.0.so.400 #49 0x2882134c in g_signal_emit_valist () from /usr/local/lib/libgobject-2.0.so.400 #50 0x28821571 in g_signal_emit () from /usr/local/lib/libgobject-2.0.so.400 #51 0x284ca381 in gtk_widget_send_expose () from /usr/X11R6/lib/libgtk-x11-2.0.so.400 #52 0x284c9eca in gtk_widget_event () from /usr/X11R6/lib/libgtk-x11-2.0.so.400 #53 0x283eb0f1 in gtk_propagate_event () from /usr/X11R6/lib/libgtk-x11-2.0.so.400 #54 0x283e9f9e in gtk_main_do_event () from /usr/X11R6/lib/libgtk-x11-2.0.so.400 #55 0x285c6923 in gdk_x11_register_standard_event_type () from /usr/X11R6/lib/libgdk-x11-2.0.so.400 #56 0x28863ca9 in g_main_dispatch () from /usr/local/lib/libglib-2.0.so.400 #57 0x28864ab9 in g_main_context_dispatch () from /usr/local/lib/libglib-2.0.so.400 #58 0x28864eaa in g_main_context_iterate () from /usr/local/lib/libglib-2.0.so.400 #59 0x288654b7 in g_main_loop_run () from /usr/local/lib/libglib-2.0.so.400 #60 0x283e96eb in gtk_main () from /usr/X11R6/lib/libgtk-x11-2.0.so.400 #61 0x28b0559b in nsAppShell::Run () from /usr/X11R6/lib/firefox/components/libwidget_gtk2.so #62 0x28a43af1 in nsAppShellService::Run () from /usr/X11R6/lib/firefox/components/libnsappshell.so #63 0x805241b in xre_main () #64 0x804d12d in main () #65 0x804d056 in _start () Followups to gnome@ From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 21:45:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1218216A4CE; Sat, 27 Nov 2004 21:45:15 +0000 (GMT) Received: from creme-brulee.marcuscom.com (creme-brulee.marcuscom.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0BF143D49; Sat, 27 Nov 2004 21:45:14 +0000 (GMT) (envelope-from marcus@marcuscom.com) Received: from shumai.marcuscom.com (shumai.marcuscom.com [192.168.1.4]) iARLjLHB096407; Sat, 27 Nov 2004 16:45:21 -0500 (EST) (envelope-from marcus@marcuscom.com) From: Joe Marcus Clarke To: Don Lewis In-Reply-To: <200411272140.iARLeJ15006376@gw.catspoiler.org> References: <200411272140.iARLeJ15006376@gw.catspoiler.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-CMOmyGRMc1PoInha8W4r" Organization: MarcusCom, Inc. Date: Sat, 27 Nov 2004 16:45:03 -0500 Message-Id: <1101591903.49672.1.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port cc: FreeBSD GNOME Users cc: benlutz@datacomm.ch cc: freebsd-current@freebsd.org cc: shinjii@virusinfo.rdksupportinc.com Subject: Re: Mozilla crash on Print X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 21:45:15 -0000 --=-CMOmyGRMc1PoInha8W4r Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2004-11-27 at 13:40 -0800, Don Lewis wrote: > On 28 Nov, Warren Liddell wrote: > > On Sun, 28 Nov 2004 01:33 am, Benjamin Lutz wrote: > >> > For the last month or so Mozilla Firefox continually crashes every t= ime > >> > you goto print either a local or internet webpage. > >> > >> If you use CUPS, the issue's likely been fixed a few days ago. Portupg= rade > >> your firefox to version 1.0_3,1. > >> > >> See http://www.freshports.org/www/firefox for the cvs log entry. > >> > >> Benjamin > >=20 > > I don tuse CUPS and im usingf the latest version being i only just did = a=20 > > complete portupgrade before sending the original email :) >=20 > I just got a crash with this Firefox 1.0_3,1 running on 4.10-STABLE. I > am using CUPS. Here's the stack trace: >=20 I'm not sure what more I can do. The crash ends up in CUPS, then in OpenSSL. I have yet to see a stack trace with those components built with debugging symbols. It looks like a CUPS problem to me, but I don't use CUPS, so I don't really have any other ideas except to uninstall it. Joe >=20 --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-CMOmyGRMc1PoInha8W4r Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBqPVfb2iPiv4Uz4cRAuEpAJ9JaKkDuqdNrQSdOw6ccDQEVJXSmgCgoyaU ElQ6pd/LLfL1p49DXUUKz4g= =XGyh -----END PGP SIGNATURE----- --=-CMOmyGRMc1PoInha8W4r-- From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 22:42:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3EC6016A4CE; Sat, 27 Nov 2004 22:42:35 +0000 (GMT) Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 614FC43D54; Sat, 27 Nov 2004 22:42:34 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from [192.168.1.35] (ti211110a080-3506.bb.online.no [80.212.205.178]) by smtp1.powertech.no (Postfix) with ESMTP id CCB3F8156; Sat, 27 Nov 2004 23:42:32 +0100 (CET) In-Reply-To: <20041126184648.GA803@zaphod.nitro.dk> References: <71F713C5E3CB7F4F9ACCBBB8E9BE318A39E348@blrx2kmbgl101.blr.amer.dell.com> <20041123105313.GC753@zaphod.nitro.dk> <007201c4d190$3c6bf3a0$d232a8c0@LCI> <20041126184648.GA803@zaphod.nitro.dk> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <9F4093B0-40C5-11D9-9A25-000A95A9A574@nordahl.net> Content-Transfer-Encoding: 7bit From: Frode Nordahl Date: Sat, 27 Nov 2004 23:42:30 +0100 To: "Simon L. Nielsen" X-Mailer: Apple Mail (2.619) cc: freebsd-current@freebsd.org cc: Samuel Clements Subject: Re: supported new Dell PERC cards - need to add to the Hardwarenotes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 22:42:35 -0000 Hello, SRCZRCX (SCSI RAID) too. (Not SRCZRC, that one is supported by iir) Mvh, Frode Nordahl On Nov 26, 2004, at 19:46, Simon L. Nielsen wrote: > On 2004.11.23 11:11:29 -0800, Samuel Clements wrote: >> For what its worth, it appears the Intel SRCU42X (SCSI RAID) and >> SRCS16 >> (SATA RAID) are supported by amr as well: > > I just added them to the manual page, thanks! > > -- > Simon L. Nielsen From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 22:52:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E68CD16A4CE; Sat, 27 Nov 2004 22:52:00 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id C167A43D39; Sat, 27 Nov 2004 22:51:59 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A0352511AA; Sat, 27 Nov 2004 14:56:38 -0800 (PST) Date: Sat, 27 Nov 2004 14:56:38 -0800 From: Kris Kennaway To: current@freeBSD.org, phk@freeBSD.org Message-ID: <20041127225638.GA99683@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jI8keyz6grp/JLjh" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: panic: sleeping thread (pid 57200) owns a non-sleepable lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 22:52:01 -0000 --jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Running -current with the latest version of kern_descrip.c that also did not fix my previous sleep warnings and lock order reversals in this code. Kris panic: sleeping thread (pid 57200) owns a non-sleepable lock cpuid = 0 KDB: enter: panic [thread pid 57199 tid 100405 ] Stopped at kdb_enter+0x32: leave db> tr Tracing pid 57199 tid 100405 td 0xc8a31780 kdb_enter(c06e45e8,0,c06e776a,f16dcb7c,c8a31780) at kdb_enter+0x32 panic(c06e776a,df70,c06e7658,a4,c8a31780) at panic+0x1b0 turnstile_wait(c0740a40,c578f480,c06e3a2c,21e,c0740a40) at turnstile_wait+0x574 _mtx_lock_sleep(c0740a40,c8a31780,0,c06e16af,670) at _mtx_lock_sleep+0xc2 _mtx_lock_flags(c0740a40,0,c06e16af,670,c06e7cdf) at _mtx_lock_flags+0xb0 fdfree(c8a31780,8,c06e1d54,e6,252) at fdfree+0x35c exit1(c8a31780,4000,f16dcd40,c06a6fc8,c8a31780) at exit1+0x32a sys_exit(c8a31780,f16dcd14,4,0,1) at sys_exit+0x1d syscall(2f,2f,2f,bfbfe584,4) at syscall+0x13b Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x280bf373, esp = 0xbfbfe4bc, ebp = 0xbfbfe4d8 --- [Hmm, that's not process 57200..] db> tr 57200 Tracing pid 57200 tid 100163 td 0xc578f480 sched_switch(c578f480,0,1,11e,c35984d3) at sched_switch+0xef mi_switch(1,0,c06e70b7,1ab,1) at mi_switch+0x1c2 sleepq_switch(c06e3a2c,18e,1,1,eecbdc50) at sleepq_switch+0x10a sleepq_wait(c5d3b24c,0,c06e4d0f,da,0) at sleepq_wait+0x1a msleep(c5d3b24c,c5d3b228,64,c06e0dc6,0) at msleep+0x4e4 checkdirs(c5853000,eecbdca4,c578f480,c578f480,0) at checkdirs+0xe0 dounmount(c5853000,8080000,c578f480,43a,611ffa4) at dounmount+0x3fa unmount(c578f480,eecbdd14,8,3ff,2) at unmount+0x1f4 syscall(2f,2f,2f,804a618,bfbfe749) at syscall+0x13b Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (22, FreeBSD ELF32, unmount), eip = 0x280c5a63, esp = 0xbfbfe4dc, ebp = 0xbfbfe598 --- db> show locks exclusive sleep mutex Giant r = 0 (0xc07412e0) locked @ kern/vfs_vnops.c:882 db> show pcpu cpuid = 0 curthread = 0xc8a31780: pid 57199 "mkdir" curpcb = 0xf16dcda0 fpcurthread = none idlethread = 0xc563f780: pid 12 "idle: cpu0" APIC ID = 0 currentldt = 0x30 spin locks held: --jI8keyz6grp/JLjh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBqQYmWry0BWjoQKURArESAKCyf6yOGkLh/FaBRuaGEbYcgBl5hQCggHTW MrnAOD7d9BuvxkTKUN2H8Yc= =1ALS -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh--