From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 00:37: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 4577216A4CE for ; Sun, 18 Jul 2004 00:37:35 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id E334943D1F for ; Sun, 18 Jul 2004 00:37:32 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6I0b6LI038470; Sat, 17 Jul 2004 20:37:06 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6I0b6YI038467; Sat, 17 Jul 2004 20:37:06 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sat, 17 Jul 2004 20:37:06 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Harald Schmalzbauer In-Reply-To: <200407180209.36199@harryhomeworkstation> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: kernel build error in cam_periph_mapmem 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, 18 Jul 2004 00:37:35 -0000 On Sun, 18 Jul 2004, Harald Schmalzbauer wrote: > Am Sonntag, 18. Juli 2004 01:06 schrieb Robert Watson: > > On Sun, 18 Jul 2004, Harald Schmalzbauer wrote: > > > Yes, it's "cam_periph.c,v 1.56 2003/11/08 10:56:57 scottl" I didn't any > > > local modification! I just removed my obj directory but that didn't > > > help. CVsup done half an hour ago. Btw, can anybody exlain me what > > > timezone the timestamp is from? Shouldn't it be UTC (or at least include > > > the TZ code)? > > > > Can you check to see if your local copy contains an include of mutex.h? > > The above time stamp looks right, FYI. > > Ok, since nobody else seems to have this problem I started poking int > the dark and found the "error": When I remove #options INVARIANTS from > my kernel.config it doesn't stop at the cam any more. Now I have a pf > show stopper but I'm sure this will be fixed soon. Still odd on the CAM front. The patch I'm building with to get pf working is attached. I also had to remove a reference to "caddr_t sg" from a function prototype in the Linux compat socket code. Seems to be a bad kernel compile day. Index: pf.c =================================================================== RCS file: /data/ncvs/src/sys/contrib/pf/net/pf.c,v retrieving revision 1.13 diff -u -r1.13 pf.c --- pf.c 17 Jul 2004 17:15:15 -0000 1.13 +++ pf.c 17 Jul 2004 23:42:44 -0000 @@ -5161,7 +5161,7 @@ if ((m0 = m_copym2(*m, 0, M_COPYALL, M_NOWAIT)) == NULL) #endif return; - if ((mtag = m_tag_copy(mtag)) == NULL) + if ((mtag = m_tag_copy(mtag, M_DONTWAIT)) == NULL) goto bad; m_tag_prepend(m0, mtag); } else { @@ -5444,7 +5444,7 @@ if ((m0 = m_copym2(*m, 0, M_COPYALL, M_NOWAIT)) == NULL) #endif return; - if ((mtag = m_tag_copy(mtag)) == NULL) + if ((mtag = m_tag_copy(mtag, M_DONTWAIT)) == NULL) goto bad; m_tag_prepend(m0, mtag); } else { From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 00:37: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 3B4B516A4CF for ; Sun, 18 Jul 2004 00:37:58 +0000 (GMT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEEDB43D2F for ; Sun, 18 Jul 2004 00:37:57 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) i6I0bvds004475; Sat, 17 Jul 2004 17:37:57 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.9p2/8.12.9/Submit) id i6I0bvan004474; Sat, 17 Jul 2004 17:37:57 -0700 (PDT) (envelope-from dillon) Date: Sat, 17 Jul 2004 17:37:57 -0700 (PDT) From: Matthew Dillon Message-Id: <200407180037.i6I0bvan004474@apollo.backplane.com> To: Doug White References: <20040717103509.N24726@alpha.siliconlandmark.com> <20040717181026.GA63963@xor.obsecurity.org> <20040717154952.U41727@carver.gumbysoft.com> cc: "current@freebsd.org" cc: Kris Kennaway Subject: Re: panic: APIC: Previous IPI is stuck 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, 18 Jul 2004 00:37:58 -0000 [ tick tock tick tock tick tock... You are getting sleepy... sleepy! You are becoming receptive. You will port DragonFly's IPI messaging subsystem. At the snap of my fingers you will wake up .... 1 .... 2 ..... 3 .... SNAP! ]. -Matt From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 01:07: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 0D64116A4CE for ; Sun, 18 Jul 2004 01:07:20 +0000 (GMT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64F0243D31 for ; Sun, 18 Jul 2004 01:07:19 +0000 (GMT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Sat, 17 Jul 2004 21:07:18 -0400 Message-ID: From: Don Bowman To: 'Matthew Dillon' Date: Sat, 17 Jul 2004 21:07:17 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" cc: current@freebsd.org Subject: RE: panic: APIC: Previous IPI is stuck 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, 18 Jul 2004 01:07:20 -0000 From: Matthew Dillon [mailto:dillon@apollo.backplane.com] > [ tick tock tick tock tick tock... You are getting > sleepy... sleepy! > You are becoming receptive. You will port DragonFly's > IPI messaging > subsystem. At the snap of my fingers you will wake up > .... 1 .... > 2 ..... 3 .... SNAP! ]. > > -Matt :) Although you meant this as a bit of a joke (and it is kind of funny...) what would be involved in this port? Have you done any benchmarks to see how well this performs? --don From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 01:17: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 E84EC16A4CE for ; Sun, 18 Jul 2004 01:17:59 +0000 (GMT) Received: from mx.us.army.mil (mxoutdr1.us.army.mil [143.69.242.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89EB643D48 for ; Sun, 18 Jul 2004 01:17:59 +0000 (GMT) (envelope-from jonathan.michael.stewart@us.army.mil) Received: from mta05.int.dr1.us.army.mil (localhost [127.0.0.1]) by mailrouter.us.army.mil (AKO MTA - mta05 ) with ESMTP id <0I10004RTWWSZZ@mta05.int.dr1.us.army.mil> for freebsd-current@FreeBSD.org; Sun, 18 Jul 2004 01:17:17 +0000 (GMT) Received: from [10.70.2.3] (syr-68-175-151-134.twcny.rr.com [68.175.151.134]) by mailrouter.us.army.mil (AKO MTA - mta05 ) with ESMTPA id <0I1000FEVWWSM9@mta05.int.dr1.us.army.mil> for freebsd-current@FreeBSD.org; Sun, 18 Jul 2004 01:17:16 +0000 (GMT) Date: Sat, 17 Jul 2004 21:17:15 -0400 From: Jonathan In-reply-to: <20040714113019.7be536d5.steve@sohara.org> To: freebsd-current@FreeBSD.org Message-id: <40F9CF9B.4020408@us.army.mil> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 0.7 (Windows/20040616) References: <25787.1089753241@critter.freebsd.dk> <20040714090640.1fe19f2b.steve@sohara.org> <200407141103.10881.michaelnottebrock@gmx.net> <20040714113019.7be536d5.steve@sohara.org> Subject: Re: CVSUP and 5.2.1 RELEASE 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, 18 Jul 2004 01:18:00 -0000 Steve O'Hara-Smith wrote: > On Wed, 14 Jul 2004 11:03:10 +0200 Michael Nottebrock > wrote: > > >> mergemaster -p needs to happen before installworld, earlier than >> that is not required. > > > From man mergemaster: > > -p Pre-buildworld mode. Compares only files known to be > essen- tial to the success of {build|install}world, including > /etc/make.conf. > > I rest my case. > Shouldn't the handbook be fixed then? The handbook says mergemaster -p should be preformed AFTER the reboot... http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html To update your system, you should use the following procedure: # make buildworld # make buildkernel # make installkernel # reboot You should boot in single user mode (using boot -s from loader prompt for example). Then run: # mergemaster -p # make installworld # mergemaster # reboot > >>> A mount -a or thereabouts is usually needed here. >> >> No, you don't need to try and mount your nfs, linux, windows and >> smb filesystems. :) > > > Hence the "or thereabouts" - you may well need the NFS filesystem if > /usr/src is on NFS. > From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 01:46: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 7E35216A4CE for ; Sun, 18 Jul 2004 01:46:48 +0000 (GMT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A15F43D48 for ; Sun, 18 Jul 2004 01:46:46 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) i6I1kids004839; Sat, 17 Jul 2004 18:46:44 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.9p2/8.12.9/Submit) id i6I1kiQ9004838; Sat, 17 Jul 2004 18:46:44 -0700 (PDT) (envelope-from dillon) Date: Sat, 17 Jul 2004 18:46:44 -0700 (PDT) From: Matthew Dillon Message-Id: <200407180146.i6I1kiQ9004838@apollo.backplane.com> To: Don Bowman References: cc: current@freebsd.org Subject: RE: panic: APIC: Previous IPI is stuck 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, 18 Jul 2004 01:46:48 -0000 :Although you meant this as a bit of a joke (and :it is kind of funny...) what would be involved :in this port? : :Have you done any benchmarks to see how well :this performs? : :--don I would expect it to perform about the same as the existing code. The main reasons to use it are that it consolidates the half dozen IPI mechanisms used by FreeBSD-5 into *one* mechanism, it completely solves deadlock issue(s), and it makes a really simple abstraction/API available for the machine independant C code to use, which would lead to greater use of the mechanism and less use of IPI-avoidance hacks (the idle loop halt code and thread scheduling / thread scheduler mutex being prime examples). Examples of APIs that the IPI messaging can replace: clock distribution (hardclock and statclock), signal forwarding/ast, page invalidation (3 kinds), lazy pmap, SMP rendezvous. Examples of APIs that could use IPI messaging instead of mutexes without too much fuss: core thread scheduler, slab allocator, portions of the memory subsystem (well, maybe the core thread scheduler would require some fuss). It requires some assembly work, obviously, but no more then is already required to mess with existing IPI mechanisms. Some per-cpu structural work, and bringing in the code module. The callbacks would operate about the same as a FAST interrupt from the point of view of FreeBSD-5. A critical section should protect against an IPI callback occuring on the current cpu (as it does in DFly). The mechanism would be extremely useful even without implementing any of the other myrid suggestions I've made (1), which is why I recommend it. (1) nobody seems to have taken any of those suggestions seriously, but the last few years of constant instability and continuing, serious code and algorithmic fragility pretty much has proved my point that a major simpification of your MP model is necessary to put FreeBSD-5 back on track. I figure that if I cannot get FreeBSD-5 to adopt the most obviously useful bit, which is the IPI Messaging, that I might as well give up trying. -Matt Matthew Dillon From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 02:15: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 1E06316A4CE for ; Sun, 18 Jul 2004 02:15:01 +0000 (GMT) Received: from moghedien.mukappabeta.net (moghedien.mukappabeta.net [194.145.150.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98DF343D2F for ; Sun, 18 Jul 2004 02:15:00 +0000 (GMT) (envelope-from mkb@mukappabeta.de) Received: from [192.168.2.100] (pD9E68966.dip.t-dialin.net [217.230.137.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by moghedien.mukappabeta.net (Postfix) with ESMTP id 426002D76 for ; Sun, 18 Jul 2004 04:11:45 +0200 (CEST) Message-ID: <40F9DD1B.3050902@mukappabeta.de> Date: Sun, 18 Jul 2004 04:14:51 +0200 From: Matthias Buelow User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040717 X-Accept-Language: de-de, de, en-us, en MIME-Version: 1.0 To: current@freebsd.org References: <200407180146.i6I1kiQ9004838@apollo.backplane.com> In-Reply-To: <200407180146.i6I1kiQ9004838@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: panic: APIC: Previous IPI is stuck 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, 18 Jul 2004 02:15:01 -0000 Matthew Dillon wrote: > I would expect it to perform about the same as the existing code. The > main reasons to use it are that it consolidates the half dozen IPI > mechanisms used by FreeBSD-5 into *one* mechanism, it completely Don't you (and others on this list) think that these things come a bit late now? I have just subscribed to this list since I'm using 5.2.1 and what I expected were discussions like, the last few bugs being ironed out, things getting polished for a stable 5.x tree, and not grass-roots discussions about the basic system architecture. This comes about 2-3 years late, folks. Please get your things together and stabilize the beast now. -- Matthias Buelow; mkb@{mukappabeta,informatik.uni-wuerzburg}.de From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 02: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 5B5BC16A4CE; Sun, 18 Jul 2004 02:29:06 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2D6543D31; Sun, 18 Jul 2004 02:29:05 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i6I2RLKO005811; Sat, 17 Jul 2004 20:27:21 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 17 Jul 2004 20:27:29 -0600 (MDT) Message-Id: <20040717.202729.12970058.imp@bsdimp.com> To: green@freebsd.org From: "M. Warner Losh" In-Reply-To: <20040717191943.GU1626@green.homeunix.org> References: <20040717182841.GR1626@green.homeunix.org> <20040717.124803.33210527.imp@bsdimp.com> <20040717191943.GU1626@green.homeunix.org> 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: current@freebsd.org Subject: Re: pccbb crashes when detaching (unsafe interrupt handler) 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, 18 Jul 2004 02:29:06 -0000 In message: <20040717191943.GU1626@green.homeunix.org> Brian Fundakowski Feldman writes: : On Sat, Jul 17, 2004 at 12:48:03PM -0600, M. Warner Losh wrote: : > In message: <20040717182841.GR1626@green.homeunix.org> : > : FreeBSD 5.x is not based on the spl : > : model anymore, and unless you want to ADD the ability to do something like : > : that, which is certainly quite feasible (that is, add a "blocking" count : > : to the interrupt handler, which the ithread has to ack before you can : > : return with the interrupt "blocked") there will be a specific cost inside : > : the pccbb driver to do things safely and it will involve some sort of : > : synchronization. : > : > I don't assume that things are spl based, I just had never seen the : > race that you found. I don't want to use sx locks to solve this : > because I'd one day like to make the cbb isr a fast interrupt handler : > so that we can restore fast interrupt handlers to pccard and cardbus : > modems. sx locks sleep, and can't be used in a fast interrupt : > handler. : : I'd love it if we could tone down the anger and incredulity. From this : point on, let's start off assuming each one of us knows what the other is : talking about. None of us likes feeling insulted or slighted, so I would : like to publically apologize for being provoked and taking an angry tone : when I am simply interested in fixing this matter (and many others) so : that 5.3 Does Not Suck. I'd also like to appologize for getting my nose out of joint. I have some personal issues hitting finality in my life right now, and I've noticed I have a thinner skin of late as a result. : Okay, using an sx_xlock() (instead of sx_tryxlock()) would certainly prevent : that, but I can understand not wanting to add more weight to the fast : path. It's something no one wants, even if it's the cleanest solution. One thing that I could do, if we *KNOW* that the bridge ISR is run first of all the shared interrupts, is to use atomic ops to clear/set the OK flag. That would prevent me from calling the ISR, while pushing down into kern_intr.c the details of dealing with the issues of inserting/removing from the list. This would also get the priority right, which I currently don't do right in the pccbb code. I'd then register a wrapper for these interrupts that checks the OK flag and neglects to call them if it isn't OK. This does add a little overhead, but not all that much, to the ISR. And it would ensure that pccard/cardbus interrupts have the same semantics as others in the system. The question is do we know this? And are there plans that the ISRs might run on different CPUs in parallel... I also did some research. I likely didn't see this because I grab Giant when attaching/detaching cards and the ISR used to be marked as needing Giant, so the race you've found wouldn't happened. When I removed the Giant flag from the bridge ISR, this race reared its ugly head. : So now that I've had more time to think about it, here's my idea on the : feasibility of an ithread handler critical section. It should cost no : more in the fast path than it does now, other than increasing the amount : of code jumped past by several instructions when it's skipped. : : >From currentish kern_intr.c: : if ((ih->ih_flags & IH_DEAD) != 0) { : mtx_lock(&ithd->it_lock); : TAILQ_REMOVE(&ithd->it_handlers, ih, : ih_next); : wakeup(ih); : mtx_unlock(&ithd->it_lock); : goto restart; : } : We add a flag IH_PIN: : if ((ih->ih_flags & (IH_DEAD | IH_PIN)) != 0) { : if ((ih->ih_flags & IH_DEAD) == 0) { : wakeup(ih); : continue; : } : mtx_lock(&ithd->it_lock); : TAILQ_REMOVE(&ithd->it_handlers, : ih, ih_next); : wakeup(ih); : mtx_unlock(&ithd->it_lock); : goto restart; : } : : The implementation for the caller would look almost the same as the : ithread_remove_handler() function. It would push essentially all of the : cost out to the code actually modifying the specifics of the interrupt : handler, and should provide a sufficient critical section for any such : drivers that want to create their own interrupt sub-handlers. : : So ithread_pin_handler()/ithread_unpin_handler() seem like a reasonable : solution, if a little bit ugly to be calling ithread support code from : drivers directly? I don't know if there's any reason on FreeBSD the : driver should not be able to know for certain that all interrupts are : registered as an intrhand on on ithread. I'm not sure what I think of this, so I'll think about it for a while and reply later. Warner From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 02:30: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 E701C16A4CE for ; Sun, 18 Jul 2004 02:30:46 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52C3E43D3F for ; Sun, 18 Jul 2004 02:30:44 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.0.200] ([192.168.0.200]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6I2aXjp047455; Sat, 17 Jul 2004 20:36:33 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <40F9E0CB.4090106@samsco.org> Date: Sat, 17 Jul 2004 20:30:35 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040702 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthias Buelow References: <200407180146.i6I1kiQ9004838@apollo.backplane.com> <40F9DD1B.3050902@mukappabeta.de> In-Reply-To: <40F9DD1B.3050902@mukappabeta.de> X-Enigmail-Version: 0.84.2.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: current@freebsd.org Subject: Re: panic: APIC: Previous IPI is stuck 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, 18 Jul 2004 02:30:47 -0000 Matthias Buelow wrote: > Matthew Dillon wrote: > >> I would expect it to perform about the same as the existing code. >> The >> main reasons to use it are that it consolidates the half dozen IPI >> mechanisms used by FreeBSD-5 into *one* mechanism, it completely > > > Don't you (and others on this list) think that these things come a bit > late now? I have just subscribed to this list since I'm using 5.2.1 and > what I expected were discussions like, the last few bugs being ironed > out, things getting polished for a stable 5.x tree, and not grass-roots > discussions about the basic system architecture. This comes about 2-3 > years late, folks. Please get your things together and stabilize the > beast now. > The 'fix the bugs' discussions are going on too. However, this is the freebsd-current list, and it's always nice to discuss things that might be suitable further down the road. Scott From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 02:49: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 A9DC716A4CE for ; Sun, 18 Jul 2004 02:49:01 +0000 (GMT) Received: from moghedien.mukappabeta.net (moghedien.mukappabeta.net [194.145.150.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D15343D31 for ; Sun, 18 Jul 2004 02:49:01 +0000 (GMT) (envelope-from mkb@mukappabeta.de) Received: from [192.168.2.100] (pD9E68966.dip.t-dialin.net [217.230.137.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by moghedien.mukappabeta.net (Postfix) with ESMTP id EA0752D76 for ; Sun, 18 Jul 2004 04:45:45 +0200 (CEST) Message-ID: <40F9E518.9050800@mukappabeta.de> Date: Sun, 18 Jul 2004 04:48:56 +0200 From: Matthias Buelow User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040717 X-Accept-Language: de-de, de, en-us, en MIME-Version: 1.0 To: current@freebsd.org References: <200407180146.i6I1kiQ9004838@apollo.backplane.com> <40F9DD1B.3050902@mukappabeta.de> <40F9E0CB.4090106@samsco.org> In-Reply-To: <40F9E0CB.4090106@samsco.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: panic: APIC: Previous IPI is stuck 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, 18 Jul 2004 02:49:01 -0000 Scott Long wrote: > The 'fix the bugs' discussions are going on too. However, this is the > freebsd-current list, and it's always nice to discuss things that might > be suitable further down the road. Yes, I might have gotten this wrong, I thought he was talking specifically about 5.x (which to me, and I guess many other users, means the long awaited stabilization of the 5.x tree). -- Matthias Buelow; mkb@{mukappabeta,informatik.uni-wuerzburg}.de From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 05:32: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 65E2516A4CE; Sun, 18 Jul 2004 05:32:22 +0000 (GMT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 287EB43D58; Sun, 18 Jul 2004 05:32:22 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from h00609772adf0.ne.client2.attbi.com ([66.30.114.143]) by comcast.net (rwcrmhc13) with ESMTP id <20040718053221015003ehv8e>; Sun, 18 Jul 2004 05:32:21 +0000 Received: from h00609772adf0.ne.client2.attbi.com (localhost [127.0.0.1]) i6I5WKfu002031; Sun, 18 Jul 2004 01:32:20 -0400 (EDT) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost)i6I5WKFH002030; Sun, 18 Jul 2004 01:32:20 -0400 (EDT) (envelope-from rodrigc) Date: Sun, 18 Jul 2004 01:32:19 -0400 From: Craig Rodrigues To: freebsd-current@freebsd.org Message-ID: <20040718053219.GA993@crodrigues.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: Creative Nomad MP3 / EHCI problems 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, 18 Jul 2004 05:32:22 -0000 Hi, I updated from CVS about 2 days ago and rebuilt kernel and world. I am having problems with my Creative Nomad MP3 player and EHCI. The Creative Nomad MP3 player is accessed via the ugen driver. I am using the Gnomad2 ( http://gnomad2.sourceforge.net ) program to access the MP3 player and upload files to it. When gnomad2 starts, it tries to scan the songs on the MP3 player, but it never completes. I set the following syctl values: hw.usb.ehci.debug: 1 hw.usb.ugen.debug: 1 I don't know where to look for useful information. I got some of this output from dmesg: ehci_device_clear_toggle: epipe=0xc1b80900 status=0x0 usbd_dump_pipe: pipe=0xc1b80900 usbd_dump_iface: iface=0xc15e9f00 device=0xc15f4800 idesc=0xc15e9f29 index=0 altindex=0 priv=0 usbd_dump_device: dev=0xc15f4800 bus=0xc161c800 default_pipe=0xc15f4780 address=2 config=1 depth=1 speed=3 self_powered=1 power=0 langid=1033 usbd_dump_endpoint: endp=0xc16585e0 edesc=0xc15e9f32 refcnt=1 bEndpointAddress=0x01 (usbd_dump_pipe:) refcnt=1 running=0 aborting=0 intrxfer=0, repeat=0, interval=-1 ehci_device_clear_toggle: epipe=0xc1b80980 status=0x0 usbd_dump_pipe: pipe=0xc1b80980 usbd_dump_iface: iface=0xc15e9f00 device=0xc15f4800 idesc=0xc15e9f29 index=0 altindex=0 priv=0 usbd_dump_device: dev=0xc15f4800 bus=0xc161c800 default_pipe=0xc15f4780 address=2 config=1 depth=1 speed=3 self_powered=1 power=0 langid=1033 usbd_dump_endpoint: endp=0xc16585e8 edesc=0xc15e9f39 refcnt=1 bEndpointAddress=0x82 (usbd_dump_pipe:) refcnt=1 running=0 aborting=0 intrxfer=0, repeat=0, interval=-1 ehci_idone: need toggle update status=00080248 nstatus=80008d80 ehci_idone: error, addr=2, endpt=0x00, status 0x48 ehci_pcd: change=0x40 ehci_device_bulk_close: pipe=0xc1b80900 ehci_intr1: door bell ehci_device_bulk_close: pipe=0xc1b80980 ehci_intr1: door bell ehci_idone: need toggle update status=00080248 nstatus=80028d80 ehci_idone: error, addr=2, endpt=0x00, status 0x48 ugen0: detached ehci_device_ctrl_close: pipe=0xc15f4780 ehci_intr1: door bell Any ideas how I can further debug this problem? Thanks. -- Craig Rodrigues http://crodrigues.org rodrigc@crodrigues.org From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 05:37: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 B812A16A4CE for ; Sun, 18 Jul 2004 05:37:50 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AF1843D31 for ; Sun, 18 Jul 2004 05:37:50 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6I5bKxU017760 for ; Sun, 18 Jul 2004 01:37:21 -0400 (EDT) (envelope-from rwatson@FreeBSD.org) Received: from localhost (robert@localhost)i6I5bKgb017757 for ; Sun, 18 Jul 2004 01:37:20 -0400 (EDT) (envelope-from rwatson@FreeBSD.org) X-Authentication-Warning: fledge.watson.org: robert owned process doing -bs Date: Sun, 18 Jul 2004 01:37:20 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Running the network stack without Giant -- what to try and when X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Robert Watson List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jul 2004 05:37:50 -0000 As many of you have seen from status reports, e-mails, bug reports, etc, the FreeBSD Project has been working for some time on getting the network stack to run in parallel on multiple CPUs. We're now at a point where a substantial amount of functionality appears to run pretty successfully without the Giant lock, and we're ready for more people to start running it that way so we can find and fix problems. Let me start by enumerating a few caveats: - While we've been doing pretty heavy testing in MPSAFE configurations, the nature of multiprocessor development and adapting code for MP safety means that it's unlikely this will "just work" for all takers. However, it may well work for many. - We've focussed primarily on getting mainstream network configurations to run without Giant: this means that less mainstream subsystems (parts of IPv6, some netgraph nodes, IPX, etc) are currently unsafe without the Giant lock turned on. Some less mainstream network devices are also not currently able to operate without Giant. There is active work in all of these area to remedy this issue. - You may run into hard to diagnose problems. We'd like to try to diagnose them anyway, but if you start to experience new problems, you'll want to go read the Handbook chapter on preparing kernel bug reports and diagnosing problems. You'll also want to be prepared to run the system with INVARIANTS and WITNESS turned on. - Not all workloads will experience a performance benefit -- some, for various reasons, will get worse. However, several interesting performance loads get measurably better. If you don't see an improvement, or you see things get worse, please don't be surprised -- you may want to look at some of the suggestions I make below on ways to make the results more predictable. Generally, you shouldn't see substantial performance degradation, if any, but it can't be ruled out, especially due to scheduling issues, etc. - We can and will destroy your data. We don't mean to, because we like your data, and we try not to, but this is, after all, operating system development. With all that in mind, now is in fact a good time to start experimenting with things, as these changes appear to be relatively stable in our initial testing. Note that there is some current instability in the CVS HEAD, and so I'd ask for some caution in reporting problems as being caused by debug.mpsafenet -- it may or may not be our fault :-). I've disabled PREEMPTION locally for thread centric testing, but haven't needed to for other testing. Here's some technical information on how to get started: (1) Determine if all of the stack components you will operate with are MPsafe. For common configurations, answering the following questions will help you decide this: - Are you using IPv6, IPX, ATM, or KAME IPSEC? If you answered yes to any of these questions, it is not yet safe for you to run without Giant. - Are your using Netgraph? If yes, it may be that you are not yet able to run without Giant. It is worth giving it a try, but you may experience panics, etc, especially in MP configurations. - Are you using SLIP or kernel PPP (not to be confused with user ppp, which is what most FreeBSD users use with modems). - Are you using any physical network interfaces other than the following: bge, dc, em, ep, fxp, rl, sis, xl, wi. The following may well work: en, gx, pcn, sf. However, they have not been marked MPSAFE by the driver maintainer. NOTE: Do you maintain a network interface driver? Is it not on this list? Shame on you! Or maybe shame on me for not listing it, even though it should work. Drop me a private e-mail with and questions or comments. Please update the busdma driver status web page with your driver's status. (2) If you are comfortable that you are using an MPSAFE-supported configuration, then you can use the following tunable in loader.conf to disable the Giant lock over the network stack on your system: debug.mpsafenet="1" Note that this is a boot-time only flag; you can inspect the setting with a sysctl, but it cannot currently be changed at runtime. Do a dmesg and confirm that all your probed network interfaces are marked as MPSAFE or not GIANT LOCKED (or whatever we call it now). If you have a network interface that is still GIANT LOCKED, it may not be able to function correctly with debug.mpsafenet=1. However, if you're not actively using it, it probably won't cause a problem. For example, firewire network interfaces can't currently be used with debug.mpsafenet=1. However, if idle, they shouldn't cause any problems. We're currently working to improve compatibility with device drivers that aren't mpsafe, and hope to have a prototype soon. Some notes: On SMP-centric performance measurements, such as local UNIX domain socket use by MySQL on MP systems, I've observed 30%-40% performance improvements by disabling Giant (some details below). My recommended configuration for testing out the impact of disabling Giant on MP systems is: - Set "options ADAPTIVE_MUTEXES" -- this seems to help a lot with contention and load. - Disable HTT. In my workloads, which tended to pound the kernel, this hurt quite a bit. Obviously, the effectiveness of HTT depends on the instruction mix, so this may not be for you. - Pick one of ULE and 4BSD, and then try the other. I found 4BSD helped a lot for MySQL, but I've seen other benchmarks with quite different results. - For stability purposes with MySQL, I currently have to disable PREEMPTION, as the MySQL benchmarks I use are pretty thread-centric and trigger preemption-related bugs with the kernel threading bits. - If you want to measure performance, make sure to disable INVARIANTS, INVARIANTS_SUPPORT, WITNESS, etc. Some notes on bug reporting: - Make sure to identify that you are running with debug.mpsafenet. If the problem is reproduceable, make sure to indicate if it goes away or persists when you disable debug.mpsafenet. - If you appear to be experiencing a hang/deadlock, please try running with WITNESS. I'd actually like to see most people running with WITNESS for a bit to shake out lock order issues, as I've introduced a lot of orders. If experiencing lock order reversals, please include the full console warning including stack trace. - INVARIANTS also considered good. Even if you aren't running with WITNESS, do run with INVARIANTS. - If you experience a hang, see if you can get into DDB -- if you are having problems getting in using a console break, try a serial console. When debugging, at minimum DDB 'ps' output, along with traces of interesting processes. Typically interesting will be processes that appear to be involved in the hang, etc. Obviously, this requires some intuition about what causes the hang and I can't offer hard and fast rules here. - Experimenting with debug.mpsafenet=1 and UP is also interesting, not just SMP. With PREEMPTION turned on, it may result in lower latency and/or lower throughput. Or not. Regardless, it's interesting -- you don't have to have SMP to give it a spin. FYI, while results can and will vary, I was pleased to observe moving from a UP->MP speedup of 1.07 on a dual-processor box to a speedup of 1.42 with the supersmack benchmark using 11 workers and 1000 select transactions with MySQL. For reference, that was with the 4BSD scheduler and adaptive mutexes. For loopback netperf with TCP and UDP, I observed no change in performance (well, 1% better for UDP RR, but basically no change). Note that the MySQL benchmark here is basically a UNIX domain socket IPC test, and so real world databases will give pretty different results since they won't be pure IPC. The results appear to be very sensitive to the choice of scheduler, and for a variety of reasons I've preferred 4BSD during recent testing (not least, better results in terms of throughput). There are a lot of people who have been working on this for quite some time -- I can't thank them all here, but I will point at the netperf web page as a place to look for ongoing patches, change logs, and some credits: http://www.watson.org/~robert/freebsd/netperf/ I try to keep it up to date about once a week or so as I drop new patch sets. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 07:39: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 1BFF016A4CE for ; Sun, 18 Jul 2004 07:39:13 +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 A911C43D1D for ; Sun, 18 Jul 2004 07:39:12 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av4-1-sn3.vrr.skanova.net (Postfix, from userid 502) id DA22B37E4A; Sun, 18 Jul 2004 09:39:11 +0200 (CEST) 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 CC72437E48 for ; Sun, 18 Jul 2004 09:39:11 +0200 (CEST) Received: from gadget (h130n1fls11o822.telia.com [213.64.66.130]) by smtp1-1-sn3.vrr.skanova.net (Postfix) with ESMTP id B114F38008 for ; Sun, 18 Jul 2004 09:39:11 +0200 (CEST) From: "Daniel Eriksson" To: Date: Sun, 18 Jul 2004 09:39:14 +0200 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Subject: World breakage: -O2 and new libthr/libc_r code 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, 18 Jul 2004 07:39:13 -0000 Marcel Moolenaar's latest libthr libc_r commit seems to have broken world for CFLAGS containing -O2. ===> lib/libthread_db cc -O2 -pipe -fno-builtin -march=athlon-xp -I. -I/usr/src/lib/libthread_db -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /u cc -fpic -DPIC -O2 -pipe -fno-builtin -march=athlon-xp -I. -I/usr/src/lib/libthread_db -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uniniti cc -O2 -pipe -fno-builtin -march=athlon-xp -I. -I/usr/src/lib/libthread_db -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /u cc -fpic -DPIC -O2 -pipe -fno-builtin -march=athlon-xp -I. -I/usr/src/lib/libthread_db -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uniniti In file included from libpthread.h:3, from /usr/src/lib/libthread_db/libpthread_db.c:41: /usr/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_kcb_get': /usr/src/lib/libpthread/arch/i386/include/pthread_md.h:162: warning: dereferencing type-punned pointer will break strict-aliasing rules In file included from libpthread.h:3, from /usr/src/lib/libthread_db/libpthread_db.c:41: /usr/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_kcb_get': /usr/src/lib/libpthread/arch/i386/include/pthread_md.h:162: warning: dereferencing type-punned pointer will break strict-aliasing rules /usr/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_kcb_critical_leave': /usr/src/lib/libpthread/arch/i386/include/pthread_md.h:177: warning: dereferencing type-punned pointer will break strict-aliasing rules /usr/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_kcb_in_critical': /usr/src/lib/libpthread/arch/i386/include/pthread_md.h:183: warning: dereferencing type-punned pointer will break strict-aliasing rules /usr/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_tcb_get': /usr/src/lib/libpthread/arch/i386/include/pthread_md.h:195: warning: dereferencing type-punned pointer will break strict-aliasing rules /usr/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_kcb_critical_leave': /usr/src/lib/libpthread/arch/i386/include/pthread_md.h:177: warning: dereferencing type-punned pointer will break strict-aliasing rules /usr/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_kcb_in_critical': /usr/src/lib/libpthread/arch/i386/include/pthread_md.h:183: warning: dereferencing type-punned pointer will break strict-aliasing rules /usr/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_tcb_get': /usr/src/lib/libpthread/arch/i386/include/pthread_md.h:195: warning: dereferencing type-punned pointer will break strict-aliasing rules /usr/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_get_curthread': /usr/src/lib/libpthread/arch/i386/include/pthread_md.h:203: warning: dereferencing type-punned pointer will break strict-aliasing rules /usr/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_get_curthread': /usr/src/lib/libpthread/arch/i386/include/pthread_md.h:203: warning: dereferencing type-punned pointer will break strict-aliasing rules /usr/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_get_curkse': /usr/src/lib/libpthread/arch/i386/include/pthread_md.h:213: warning: dereferencing type-punned pointer will break strict-aliasing rules /usr/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_get_curkse': /usr/src/lib/libpthread/arch/i386/include/pthread_md.h:213: warning: dereferencing type-punned pointer will break strict-aliasing rules *** Error code 1 /Daniel Eriksson From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 08:11: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 0369516A532 for ; Sun, 18 Jul 2004 08:11:08 +0000 (GMT) Received: from numeri.campus.luth.se (numeri.campus.luth.se [130.240.197.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45ED243D1D for ; Sun, 18 Jul 2004 08:11:07 +0000 (GMT) (envelope-from k@numeri.campus.luth.se) Received: from numeri.campus.luth.se (localhost [127.0.0.1]) i6I8AweC025327; Sun, 18 Jul 2004 10:10:58 +0200 (CEST) (envelope-from k@numeri.campus.luth.se) Received: (from k@localhost) by numeri.campus.luth.se (8.12.11/8.12.11/Submit) id i6I8Aw7I025322; Sun, 18 Jul 2004 10:10:58 +0200 (CEST) (envelope-from k) Date: Sun, 18 Jul 2004 10:10:58 +0200 From: Johan Karlsson To: Grover Lines Message-ID: <20040718081058.GA45365@numeri.campus.luth.se> References: <20040717164519.E942343D2F@mx1.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040717164519.E942343D2F@mx1.FreeBSD.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: [current tinderbox] failure on i386/i386 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, 18 Jul 2004 08:11:08 -0000 Hi On Sat, Jul 17, 2004 at 09:45 (-0700), Grover Lines wrote: > I guess no one is reading current, I reported that failure about 16hrs ago. > It's caused from the WARNS?= 2 in I guess you are using -O2 when building. I did not :-( Anyway, I have reverted that part since yesterday evening. Sorry for the breakage. /Johan K -- Johan Karlsson mailto:johan@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 08:32: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 16F3C16A4CE for ; Sun, 18 Jul 2004 08:32:57 +0000 (GMT) Received: from email11.aon.at (WARSL402PIP7.highway.telekom.at [195.3.96.94]) by mx1.FreeBSD.org (Postfix) with SMTP id BB60E43D1F for ; Sun, 18 Jul 2004 08:32:55 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail 172496 invoked from network); 18 Jul 2004 08:32:54 -0000 Received: from m102p007.dipool.highway.telekom.at (HELO ?62.46.2.167?) ([62.46.2.167]) (envelope-sender ) by qmail2rs.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 18 Jul 2004 08:32:54 -0000 From: Stefan Ehmann To: Tomas Randa In-Reply-To: <1090073794.706.5.camel@ares.internetservice.cz> References: <1090073794.706.5.camel@ares.internetservice.cz> Content-Type: text/plain Message-Id: <1090139567.944.6.camel@taxman> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 18 Jul 2004 10:32:47 +0200 Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: sk0 problems 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, 18 Jul 2004 08:32:57 -0000 On Sat, 2004-07-17 at 16:16, Tomas Randa wrote: > Hi, > > i am using network card Marvell Semiconductor 88E1000 with sk driver on > FreeBSD 5.2.1 on two machines, but i have problem with it. > When a high traffic is going through the interface (about 6-9MB/s), the > card stops working, no ping, no answer, no message in log. Sometimes > help do ifconfig sk0 down and up, but sometimes not. Not sure if the problem is related. I got the same problem with an onboard vr card and also similar symptons with an ipfi isdn card. From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 08:33: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 832A316A500; Sun, 18 Jul 2004 08:33:01 +0000 (GMT) Received: from smtp3.sentex.ca (smtp3.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 651DE43D2D; Sun, 18 Jul 2004 08:33:00 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smtp3.sentex.ca (8.12.11/8.12.11) with ESMTP id i6I8Wtmc055455; Sun, 18 Jul 2004 04:32:55 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.12.11/8.12.11) with ESMTP id i6I8WvWm010375; Sun, 18 Jul 2004 04:32:57 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 911237303F; Sun, 18 Jul 2004 04:32:57 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040718083257.911237303F@freebsd-current.sentex.ca> Date: Sun, 18 Jul 2004 04:32:57 -0400 (EDT) Subject: [current tinderbox] failure on alpha/alpha 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: Sun, 18 Jul 2004 08:33:01 -0000 TB --- 2004-07-18 08:00:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-07-18 08:00:00 - starting CURRENT tinderbox run for alpha/alpha TB --- 2004-07-18 08:00:00 - checking out the source tree TB --- 2004-07-18 08:00:00 - cd /home/tinderbox/sandbox/CURRENT/alpha/alpha TB --- 2004-07-18 08:00:00 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-07-18 08:04:52 - building world (CFLAGS=-O2 -pipe) TB --- 2004-07-18 08:04:52 - cd /home/tinderbox/sandbox/CURRENT/alpha/alpha/src TB --- 2004-07-18 08:04:52 - /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 [...] /tinderbox/CURRENT/alpha/alpha/src/lib/libthread_db/arch/alpha/libpthread_md.c:31: warning: its scope is only this definition or declaration, which is probably not what you want /tinderbox/CURRENT/alpha/alpha/src/lib/libthread_db/arch/alpha/libpthread_md.c:36: error: syntax error before '*' token /tinderbox/CURRENT/alpha/alpha/src/lib/libthread_db/arch/alpha/libpthread_md.c:37: warning: return type defaults to `int' /tinderbox/CURRENT/alpha/alpha/src/lib/libthread_db/arch/alpha/libpthread_md.c:41: error: syntax error before "ucontext_t" /tinderbox/CURRENT/alpha/alpha/src/lib/libthread_db/arch/alpha/libpthread_md.c:41: warning: `struct fpreg' declared inside parameter list /tinderbox/CURRENT/alpha/alpha/src/lib/libthread_db/arch/alpha/libpthread_md.c:46: error: syntax error before '*' token /tinderbox/CURRENT/alpha/alpha/src/lib/libthread_db/arch/alpha/libpthread_md.c:47: warning: return type defaults to `int' /tinderbox/CURRENT/alpha/alpha/src/lib/libthread_db/arch/alpha/libpthread_md.c:56: warning: `struct reg' declared inside parameter list *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src/lib/libthread_db. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src/lib. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src. TB --- 2004-07-18 08:32:57 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-07-18 08:32:57 - ERROR: failed to build world TB --- 2004-07-18 08:32:57 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 09:03: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 E181416A4CE; Sun, 18 Jul 2004 09:03:06 +0000 (GMT) Received: from smtp3b.sentex.ca (smtp3b.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C3E443D49; Sun, 18 Jul 2004 09:03:06 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smtp3b.sentex.ca (8.12.11/8.12.11) with ESMTP id i6I936cZ059370; Sun, 18 Jul 2004 05:03:06 -0400 (EDT) (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 i6I9368w018992; Sun, 18 Jul 2004 05:03:06 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id C0FD07303F; Sun, 18 Jul 2004 05:03:05 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040718090305.C0FD07303F@freebsd-current.sentex.ca> Date: Sun, 18 Jul 2004 05:03:05 -0400 (EDT) Subject: [current 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: Sun, 18 Jul 2004 09:03:07 -0000 TB --- 2004-07-18 08:32:57 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-07-18 08:32:57 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-07-18 08:32:57 - checking out the source tree TB --- 2004-07-18 08:32:57 - cd /home/tinderbox/sandbox/CURRENT/amd64/amd64 TB --- 2004-07-18 08:32:57 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-07-18 08:37:27 - building world (CFLAGS=-O2 -pipe) TB --- 2004-07-18 08:37:27 - cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- 2004-07-18 08:37:27 - /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 [...] /tinderbox/CURRENT/amd64/amd64/src/lib/libpthread/arch/amd64/include/pthread_md.h: In function `_kcb_in_critical': /tinderbox/CURRENT/amd64/amd64/src/lib/libpthread/arch/amd64/include/pthread_md.h:179: warning: dereferencing type-punned pointer will break strict-aliasing rules /tinderbox/CURRENT/amd64/amd64/src/lib/libpthread/arch/amd64/include/pthread_md.h: In function `_tcb_get': /tinderbox/CURRENT/amd64/amd64/src/lib/libpthread/arch/amd64/include/pthread_md.h:191: warning: dereferencing type-punned pointer will break strict-aliasing rules /tinderbox/CURRENT/amd64/amd64/src/lib/libpthread/arch/amd64/include/pthread_md.h: In function `_get_curthread': /tinderbox/CURRENT/amd64/amd64/src/lib/libpthread/arch/amd64/include/pthread_md.h:199: warning: dereferencing type-punned pointer will break strict-aliasing rules /tinderbox/CURRENT/amd64/amd64/src/lib/libpthread/arch/amd64/include/pthread_md.h: In function `_get_curkse': /tinderbox/CURRENT/amd64/amd64/src/lib/libpthread/arch/amd64/include/pthread_md.h:209: warning: dereferencing type-punned pointer will break strict-aliasing rules *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/lib/libthread_db. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/lib. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-07-18 09:03:05 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-07-18 09:03:05 - ERROR: failed to build world TB --- 2004-07-18 09:03:05 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 09:18: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 0CC1016A4CE for ; Sun, 18 Jul 2004 09:18:47 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02CC543D49; Sun, 18 Jul 2004 09:18:47 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from freebsd.org (davidxu@localhost [127.0.0.1]) i6I9Ij32044650; Sun, 18 Jul 2004 09:18:46 GMT (envelope-from davidxu@freebsd.org) Message-ID: <40FA3FF2.6070406@freebsd.org> Date: Sun, 18 Jul 2004 17:16:34 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Eriksson References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: World breakage: -O2 and new libthr/libc_r code 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, 18 Jul 2004 09:18:47 -0000 libpthread used to have the warning message when being compiled with -02, it should be fixed. David Xu Daniel Eriksson wrote: >Marcel Moolenaar's latest libthr libc_r commit seems to have broken world >for CFLAGS containing -O2. > > >===> lib/libthread_db >cc -O2 -pipe -fno-builtin -march=athlon-xp -I. -I/usr/src/lib/libthread_db >-Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /u >cc -fpic -DPIC -O2 -pipe -fno-builtin -march=athlon-xp -I. >-I/usr/src/lib/libthread_db -Wsystem-headers -Werror -Wall -Wno-format-y2k >-Wno-uniniti >cc -O2 -pipe -fno-builtin -march=athlon-xp -I. -I/usr/src/lib/libthread_db >-Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /u >cc -fpic -DPIC -O2 -pipe -fno-builtin -march=athlon-xp -I. >-I/usr/src/lib/libthread_db -Wsystem-headers -Werror -Wall -Wno-format-y2k >-Wno-uniniti >In file included from libpthread.h:3, > from /usr/src/lib/libthread_db/libpthread_db.c:41: >/usr/src/lib/libpthread/arch/i386/include/pthread_md.h: In function >`_kcb_get': >/usr/src/lib/libpthread/arch/i386/include/pthread_md.h:162: warning: >dereferencing type-punned pointer will break strict-aliasing rules >In file included from libpthread.h:3, > > From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 09:31: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 9BA5216A4CE; Sun, 18 Jul 2004 09:31:44 +0000 (GMT) Received: from smtp3b.sentex.ca (smtp3b.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4250443D2F; Sun, 18 Jul 2004 09:31:44 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smtp3b.sentex.ca (8.12.11/8.12.11) with ESMTP id i6I9VhLF061550; Sun, 18 Jul 2004 05:31:43 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.12.11/8.12.11) with ESMTP id i6I9VhPk029963; Sun, 18 Jul 2004 05:31:43 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 840F37303F; Sun, 18 Jul 2004 05:31:43 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040718093143.840F37303F@freebsd-current.sentex.ca> Date: Sun, 18 Jul 2004 05:31:43 -0400 (EDT) Subject: [current 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: Sun, 18 Jul 2004 09:31:44 -0000 TB --- 2004-07-18 09:03:06 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-07-18 09:03:06 - starting CURRENT tinderbox run for i386/i386 TB --- 2004-07-18 09:03:06 - checking out the source tree TB --- 2004-07-18 09:03:06 - cd /home/tinderbox/sandbox/CURRENT/i386/i386 TB --- 2004-07-18 09:03:06 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-07-18 09:07:17 - building world (CFLAGS=-O2 -pipe) TB --- 2004-07-18 09:07:17 - cd /home/tinderbox/sandbox/CURRENT/i386/i386/src TB --- 2004-07-18 09:07:17 - /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 [...] /tinderbox/CURRENT/i386/i386/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_kcb_in_critical': /tinderbox/CURRENT/i386/i386/src/lib/libpthread/arch/i386/include/pthread_md.h:183: warning: dereferencing type-punned pointer will break strict-aliasing rules /tinderbox/CURRENT/i386/i386/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_tcb_get': /tinderbox/CURRENT/i386/i386/src/lib/libpthread/arch/i386/include/pthread_md.h:195: warning: dereferencing type-punned pointer will break strict-aliasing rules /tinderbox/CURRENT/i386/i386/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_get_curthread': /tinderbox/CURRENT/i386/i386/src/lib/libpthread/arch/i386/include/pthread_md.h:203: warning: dereferencing type-punned pointer will break strict-aliasing rules /tinderbox/CURRENT/i386/i386/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_get_curkse': /tinderbox/CURRENT/i386/i386/src/lib/libpthread/arch/i386/include/pthread_md.h:213: warning: dereferencing type-punned pointer will break strict-aliasing rules *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src/lib/libthread_db. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src/lib. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. TB --- 2004-07-18 09:31:43 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-07-18 09:31:43 - ERROR: failed to build world TB --- 2004-07-18 09:31:43 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 10:00: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 DA30916A4CE; Sun, 18 Jul 2004 10:00:23 +0000 (GMT) Received: from smtp3.sentex.ca (smtp3.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8167743D1F; Sun, 18 Jul 2004 10:00:23 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smtp3.sentex.ca (8.12.11/8.12.11) with ESMTP id i6IA0MTE064770; Sun, 18 Jul 2004 06:00:22 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.12.11/8.12.11) with ESMTP id i6IA0MJu038547; Sun, 18 Jul 2004 06:00:22 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id B8F7D7303F; Sun, 18 Jul 2004 06:00:22 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040718100022.B8F7D7303F@freebsd-current.sentex.ca> Date: Sun, 18 Jul 2004 06:00:22 -0400 (EDT) Subject: [current 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: Sun, 18 Jul 2004 10:00:24 -0000 TB --- 2004-07-18 09:31:43 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-07-18 09:31:43 - starting CURRENT tinderbox run for i386/pc98 TB --- 2004-07-18 09:31:43 - checking out the source tree TB --- 2004-07-18 09:31:43 - cd /home/tinderbox/sandbox/CURRENT/i386/pc98 TB --- 2004-07-18 09:31:43 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-07-18 09:36:11 - building world (CFLAGS=-O2 -pipe) TB --- 2004-07-18 09:36:11 - cd /home/tinderbox/sandbox/CURRENT/i386/pc98/src TB --- 2004-07-18 09:36:11 - /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 [...] /tinderbox/CURRENT/i386/pc98/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_kcb_in_critical': /tinderbox/CURRENT/i386/pc98/src/lib/libpthread/arch/i386/include/pthread_md.h:183: warning: dereferencing type-punned pointer will break strict-aliasing rules /tinderbox/CURRENT/i386/pc98/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_tcb_get': /tinderbox/CURRENT/i386/pc98/src/lib/libpthread/arch/i386/include/pthread_md.h:195: warning: dereferencing type-punned pointer will break strict-aliasing rules /tinderbox/CURRENT/i386/pc98/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_get_curthread': /tinderbox/CURRENT/i386/pc98/src/lib/libpthread/arch/i386/include/pthread_md.h:203: warning: dereferencing type-punned pointer will break strict-aliasing rules /tinderbox/CURRENT/i386/pc98/src/lib/libpthread/arch/i386/include/pthread_md.h: In function `_get_curkse': /tinderbox/CURRENT/i386/pc98/src/lib/libpthread/arch/i386/include/pthread_md.h:213: warning: dereferencing type-punned pointer will break strict-aliasing rules *** Error code 1 Stop in /tinderbox/CURRENT/i386/pc98/src/lib/libthread_db. *** Error code 1 Stop in /tinderbox/CURRENT/i386/pc98/src/lib. *** Error code 1 Stop in /tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /tinderbox/CURRENT/i386/pc98/src. TB --- 2004-07-18 10:00:22 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-07-18 10:00:22 - ERROR: failed to build world TB --- 2004-07-18 10:00:22 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 10: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 B929C16A4CE for ; Sun, 18 Jul 2004 10:17:33 +0000 (GMT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8798243D46 for ; Sun, 18 Jul 2004 10:17:33 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from mailnull by anduin.net with spam-scanned (Exim 4.34; FreeBSD) id 1Bm8jW-0005hf-VR for current@freebsd.org; Sun, 18 Jul 2004 12:17:32 +0200 Received: from [217.8.136.185] (helo=[192.168.1.10]) by anduin.net with esmtp (Exim 4.34; FreeBSD) id 1Bm8jW-0005gf-KR for current@freebsd.org; Sun, 18 Jul 2004 12:17:26 +0200 Message-ID: <40FA0DA5.90906@anduin.net> Date: Sun, 18 Jul 2004 07:41:57 +0200 From: Eirik Oeverby User-Agent: Mozilla Thunderbird 0.7.1 (X11/20040711) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on anduin.net X-Spam-Level: X-Spam-Status: No, hits=0.7 required=7.5 tests=DATE_IN_PAST_03_06 autolearn=no version=2.63 Subject: Preemption issues 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, 18 Jul 2004 10:17:33 -0000 Hoi all, and in particulars the power-that-be: Any news about the preemption(?) issue? I'm itching to go -CURRENT on some boxen here, but I'm not sure if it's a good idea right now. Thanks, /Eirik From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 10:31: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 13BEB16A4CF; Sun, 18 Jul 2004 10:31:52 +0000 (GMT) Received: from smtp3.sentex.ca (smtp3.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE35043D39; Sun, 18 Jul 2004 10:31:51 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smtp3.sentex.ca (8.12.11/8.12.11) with ESMTP id i6IAVouw070570; Sun, 18 Jul 2004 06:31:50 -0400 (EDT) (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 i6IAVpwZ024546; Sun, 18 Jul 2004 06:31:51 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id D75897303F; Sun, 18 Jul 2004 06:31:50 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040718103150.D75897303F@freebsd-current.sentex.ca> Date: Sun, 18 Jul 2004 06:31:50 -0400 (EDT) Subject: [current tinderbox] failure on ia64/ia64 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: Sun, 18 Jul 2004 10:31:52 -0000 TB --- 2004-07-18 10:00:23 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-07-18 10:00:23 - starting CURRENT tinderbox run for ia64/ia64 TB --- 2004-07-18 10:00:23 - cleaning the sandbox TB --- 2004-07-18 10:01:37 - checking out the source tree TB --- 2004-07-18 10:01:37 - cd /home/tinderbox/sandbox/CURRENT/ia64/ia64 TB --- 2004-07-18 10:01:37 - /usr/bin/cvs -f -R -Q -d/home/ncvs checkout -P -A src TB --- 2004-07-18 10:09:40 - WARNING: /home/tinderbox/sandbox/ia64.diff does not exist TB --- 2004-07-18 10:09:40 - building world (CFLAGS=-O -pipe) TB --- 2004-07-18 10:09:40 - cd /home/tinderbox/sandbox/CURRENT/ia64/ia64/src TB --- 2004-07-18 10:09:40 - /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 [...] /tinderbox/CURRENT/ia64/ia64/src/lib/libthread_db/arch/ia64/libpthread_md.c:31: warning: its scope is only this definition or declaration, which is probably not what you want /tinderbox/CURRENT/ia64/ia64/src/lib/libthread_db/arch/ia64/libpthread_md.c:36: error: syntax error before '*' token /tinderbox/CURRENT/ia64/ia64/src/lib/libthread_db/arch/ia64/libpthread_md.c:37: warning: return type defaults to `int' /tinderbox/CURRENT/ia64/ia64/src/lib/libthread_db/arch/ia64/libpthread_md.c:41: error: syntax error before "ucontext_t" /tinderbox/CURRENT/ia64/ia64/src/lib/libthread_db/arch/ia64/libpthread_md.c:41: warning: `struct fpreg' declared inside parameter list /tinderbox/CURRENT/ia64/ia64/src/lib/libthread_db/arch/ia64/libpthread_md.c:46: error: syntax error before '*' token /tinderbox/CURRENT/ia64/ia64/src/lib/libthread_db/arch/ia64/libpthread_md.c:47: warning: return type defaults to `int' /tinderbox/CURRENT/ia64/ia64/src/lib/libthread_db/arch/ia64/libpthread_md.c:56: warning: `struct reg' declared inside parameter list *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src/lib/libthread_db. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src/lib. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src. TB --- 2004-07-18 10:31:50 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-07-18 10:31:50 - ERROR: failed to build world TB --- 2004-07-18 10:31:50 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 11:03: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 3469016A4CE for ; Sun, 18 Jul 2004 11:03:24 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 0E1D943D41 for ; Sun, 18 Jul 2004 11:03:23 +0000 (GMT) (envelope-from segobi@gmx.de) Received: (qmail 24829 invoked by uid 65534); 18 Jul 2004 11:03:21 -0000 Received: from p508DDAA3.dip0.t-ipconnect.de (HELO LEVELONE) (80.141.218.163) by mail.gmx.net (mp018) with SMTP; 18 Jul 2004 13:03:21 +0200 X-Authenticated: #556937 Message-ID: <005d01c46cb6$bb1ffd20$0100a8c0@LEVELONE> From: "Sebastian Foss" To: Date: Sun, 18 Jul 2004 13:02:34 +0200 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.2096 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2096 Subject: xfce4 help 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, 18 Jul 2004 11:03:24 -0000 Hi! I know this may be a little O.T. but im quite desperate... Maybe someone can help me to find this original desktop wallpaper for freebsd because i like it so much: http://xfce.org/images/screenshots/jimmiejaz_26122003.jpg Thank you very much for any help! Sebastian From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 11:55: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 C759716A4CE; Sun, 18 Jul 2004 11:55:30 +0000 (GMT) Received: from smtp3b.sentex.ca (smtp3b.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E40843D5E; Sun, 18 Jul 2004 11:55:30 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smtp3b.sentex.ca (8.12.11/8.12.11) with ESMTP id i6IBtT1a075026; Sun, 18 Jul 2004 07:55:29 -0400 (EDT) (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 i6IBtTXE090101; Sun, 18 Jul 2004 07:55:29 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 7335A7303F; Sun, 18 Jul 2004 07:55:29 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040718115529.7335A7303F@freebsd-current.sentex.ca> Date: Sun, 18 Jul 2004 07:55:29 -0400 (EDT) Subject: [current tinderbox] failure on sparc64/sparc64 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: Sun, 18 Jul 2004 11:55:31 -0000 TB --- 2004-07-18 11:27:50 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-07-18 11:27:50 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2004-07-18 11:27:50 - cleaning the sandbox TB --- 2004-07-18 11:28:55 - checking out the source tree TB --- 2004-07-18 11:28:55 - cd /home/tinderbox/sandbox/CURRENT/sparc64/sparc64 TB --- 2004-07-18 11:28:55 - /usr/bin/cvs -f -R -Q -d/home/ncvs checkout -P -A src TB --- 2004-07-18 11:36:06 - patching the sources TB --- 2004-07-18 11:36:06 - cd /home/tinderbox/sandbox/CURRENT/sparc64/sparc64/src TB --- 2004-07-18 11:36:06 - /usr/bin/patch -f -s -i/home/tinderbox/sandbox/sparc64.diff TB --- 2004-07-18 11:36:06 - building world (CFLAGS=-O -pipe) TB --- 2004-07-18 11:36:06 - cd /home/tinderbox/sandbox/CURRENT/sparc64/sparc64/src TB --- 2004-07-18 11:36: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 [...] /tinderbox/CURRENT/sparc64/sparc64/src/lib/libthread_db/arch/sparc64/libpthread_md.c:31: warning: its scope is only this definition or declaration, which is probably not what you want /tinderbox/CURRENT/sparc64/sparc64/src/lib/libthread_db/arch/sparc64/libpthread_md.c:36: error: syntax error before '*' token /tinderbox/CURRENT/sparc64/sparc64/src/lib/libthread_db/arch/sparc64/libpthread_md.c:37: warning: return type defaults to `int' /tinderbox/CURRENT/sparc64/sparc64/src/lib/libthread_db/arch/sparc64/libpthread_md.c:41: error: syntax error before "ucontext_t" /tinderbox/CURRENT/sparc64/sparc64/src/lib/libthread_db/arch/sparc64/libpthread_md.c:41: warning: `struct fpreg' declared inside parameter list /tinderbox/CURRENT/sparc64/sparc64/src/lib/libthread_db/arch/sparc64/libpthread_md.c:46: error: syntax error before '*' token /tinderbox/CURRENT/sparc64/sparc64/src/lib/libthread_db/arch/sparc64/libpthread_md.c:47: warning: return type defaults to `int' /tinderbox/CURRENT/sparc64/sparc64/src/lib/libthread_db/arch/sparc64/libpthread_md.c:56: warning: `struct reg' declared inside parameter list *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src/lib/libthread_db. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src/lib. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. TB --- 2004-07-18 11:55:29 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-07-18 11:55:29 - ERROR: failed to build world TB --- 2004-07-18 11:55:29 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 14:07: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 6D1D016A4CE; Sun, 18 Jul 2004 14:07:19 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2829543D2D; Sun, 18 Jul 2004 14:07:18 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6IE5WsD052254; Sun, 18 Jul 2004 16:05:32 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <0f4201c46ccf$61de5f90$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Robert Watson" , References: Date: Sun, 18 Jul 2004 15:59:02 +0200 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.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Subject: panic: Duplicate free of item 0xffffff005c4a8600 from zone 0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 14:07:19 -0000 Started running with debug.mpsafe=1. Not shure if it has anything to do with it.... While running configure over NFS: Slab at 0xffffff005c4a8fb8, freei 6 = 0. panic: Duplicate free of item 0xffffff005c4a8600 from zone 0xffffff007fed4780(Mb uf) cpuid = 1; KDB: stack backtrace: kdb_backtrace() at kdb_backtrace+0x34 panic() at panic+0x1d2 uma_dbg_free() at uma_dbg_free+0x112 uma_zfree_arg() at uma_zfree_arg+0x10a mb_free_ext() at mb_free_ext+0x96 m_freem() at m_freem+0x28 tcp_reass() at tcp_reass+0x1bb tcp_input() at tcp_input+0x2af9 ip_input() at ip_input+0x94c netisr_processqueue() at netisr_processqueue+0x8c swi_net() at swi_net+0xe8 ithread_loop() at ithread_loop+0x18d fork_exit() at fork_exit+0xc9 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffb0bb5d00, rbp = 0 --- KDB: enter: panic [thread 100017] Stopped at kdb_enter+0x2e: nop Coredump available.... 61Mb compressed. system contains a de card, which is correctly identified as GIANT-LOCKED. The card is not connected. Next time I open up the box, I'll remove it. system info available at: http://withagen.dyndns.org/FreeBSD/cores/*.opteron --WjW From owner-freebsd-current@FreeBSD.ORG Sat Jul 17 22:54: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 9166E16A4CE; Sat, 17 Jul 2004 22:54:21 +0000 (GMT) Received: from flintsbach.schmalzbauer.de (flintsbach.schmalzbauer.de [62.245.232.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36A1043D39; Sat, 17 Jul 2004 22:54:20 +0000 (GMT) (envelope-from h@schmalzbauer.de) Received: from korso.flintsbach.schmalzbauer.de (korso.flintsbach.schmalzbauer.de [172.21.2.3])i6HMsFkp093639; Sun, 18 Jul 2004 00:54:15 +0200 (CEST) (envelope-from h@schmalzbauer.de) Received: from cale.flintsbach.schmalzbauer.de (cale.flintsbach.schmalzbauer.de [172.21.1.249]) by korso.flintsbach.schmalzbauer.de (Postfix) with ESMTP id 9A6DE195; Sun, 18 Jul 2004 00:54:15 +0200 (CEST) From: Harald Schmalzbauer To: Robert Watson Date: Sun, 18 Jul 2004 00:54:13 +0200 User-Agent: KMail/1.6.2 References: In-Reply-To: X-OS: FreeBSD 5.3 X-Country: Germany X-Address: Munich, 80686 X-Phone2: +49 (0) 89 18947781 X-Name: Harald Schmalzbauer X-Birthday: 06 Oktober 1972 MIME-Version: 1.0 X-UID: 6 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_W4a+ATiK2KIF3IW"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407180054.14920@harryhomeworkstation> X-Spam-Status: No, hits=0.0 required=3.5 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mailjail.dmz.flintsbach.schmalzbauer.de X-Mailman-Approved-At: Sun, 18 Jul 2004 14:22:13 +0000 cc: freebsd-current@freebsd.org Subject: Re: kernel build error in cam_periph_mapmem 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, 17 Jul 2004 22:54:21 -0000 --Boundary-02=_W4a+ATiK2KIF3IW Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Samstag, 17. Juli 2004 19:48 schrieb Robert Watson: > On Fri, 16 Jul 2004, Harald Schmalzbauer wrote: > > for several cvsups my kernel build fails with the following: > > > > cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs > > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > > -Wcast-qual > > -fformat-extensions -std=3Dc99 -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 -mno-align-long-strings -mpreferred-stack-bounda= ry=3D2 > > -ffreestanding -Werror /usr/src/sys/cam/cam_periph.c > > /usr/src/sys/cam/cam_periph.c: In function `cam_periph_mapmem': > > /usr/src/sys/cam/cam_periph.c:624: warning: implicit declaration of > > function `_mtx_assert' > > /usr/src/sys/cam/cam_periph.c:624: error: `MA_OWNED' undeclared (first > > use in this function) > > It looks like your copy of cam_periph.c doesn't #include mutex.h, which is > where MA_OWNED is defined. Revision 1.56, which is what I have checked > out here, appears to include if. Could you confirm you have revision 1.56 > without any local modifications? Yes, it's "cam_periph.c,v 1.56 2003/11/08 10:56:57 scottl" I didn't any local modification! I just removed my obj directory but that didn't help. CVsup done half an hour ago. Btw, can anybody exlain me what timezone the timestamp is from? Shouldn't i= t=20 be UTC (or at least include the TZ code)? Thanks, =2DHarry > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Principal Research Scientist, McAfee Resear= ch --Boundary-02=_W4a+ATiK2KIF3IW Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA+a4WBylq0S4AzzwRAlVcAJ9L0ACY+5a/8KgGbxhOPpAdpDBYawCghAj3 hnbO1XZYQRuACRa9x+H2m00= =QGxN -----END PGP SIGNATURE----- --Boundary-02=_W4a+ATiK2KIF3IW-- From owner-freebsd-current@FreeBSD.ORG Sat Jul 17 23:12: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 20B8816A4CE; Sat, 17 Jul 2004 23:12:06 +0000 (GMT) Received: from flintsbach.schmalzbauer.de (flintsbach.schmalzbauer.de [62.245.232.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68E7743D75; Sat, 17 Jul 2004 23:12:01 +0000 (GMT) (envelope-from h@schmalzbauer.de) Received: from korso.flintsbach.schmalzbauer.de (korso.flintsbach.schmalzbauer.de [172.21.2.3])i6HNBuPI094056; Sun, 18 Jul 2004 01:11:56 +0200 (CEST) (envelope-from h@schmalzbauer.de) Received: from cale.flintsbach.schmalzbauer.de (cale.flintsbach.schmalzbauer.de [172.21.1.249]) by korso.flintsbach.schmalzbauer.de (Postfix) with ESMTP id 1F03DB4; Sun, 18 Jul 2004 01:11:56 +0200 (CEST) From: Harald Schmalzbauer To: Robert Watson Date: Sun, 18 Jul 2004 01:11:54 +0200 User-Agent: KMail/1.6.2 References: In-Reply-To: X-OS: FreeBSD 5.3 X-Country: Germany X-Address: Munich, 80686 X-Phone2: +49 (0) 89 18947781 X-Name: Harald Schmalzbauer X-Birthday: 06 Oktober 1972 MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_7Ib+AlIJiZ7gsMV"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407180111.55446@harryhomeworkstation> X-Spam-Status: No, hits=0.0 required=3.5 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mailjail.dmz.flintsbach.schmalzbauer.de X-Mailman-Approved-At: Sun, 18 Jul 2004 14:22:13 +0000 cc: freebsd-current@freebsd.org Subject: Re: kernel build error in cam_periph_mapmem 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, 17 Jul 2004 23:12:06 -0000 --Boundary-02=_7Ib+AlIJiZ7gsMV Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Sonntag, 18. Juli 2004 01:06 schrieb Robert Watson: > On Sun, 18 Jul 2004, Harald Schmalzbauer wrote: > > Yes, it's "cam_periph.c,v 1.56 2003/11/08 10:56:57 scottl" I didn't any > > local modification! I just removed my obj directory but that didn't > > help. CVsup done half an hour ago. Btw, can anybody exlain me what > > timezone the timestamp is from? Shouldn't it be UTC (or at least include > > the TZ code)? > > Can you check to see if your local copy contains an include of mutex.h? > The above time stamp looks right, FYI. Sorry, I forgot to mention, of course I checked for #include mutex.h and it= 's=20 in there. =2DHarry > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Principal Research Scientist, McAfee Resear= ch --Boundary-02=_7Ib+AlIJiZ7gsMV Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA+bI7Bylq0S4AzzwRArGOAJ9hBRJTf3m1rDobBQBWhg0q/mHOAQCfWvka +884fw23fwFZFo6PQHGe6fA= =6wOa -----END PGP SIGNATURE----- --Boundary-02=_7Ib+AlIJiZ7gsMV-- From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 00:09: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 56A6516A4CE; Sun, 18 Jul 2004 00:09:45 +0000 (GMT) Received: from flintsbach.schmalzbauer.de (flintsbach.schmalzbauer.de [62.245.232.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31C4D43D2D; Sun, 18 Jul 2004 00:09:42 +0000 (GMT) (envelope-from h@schmalzbauer.de) Received: from korso.flintsbach.schmalzbauer.de (korso.flintsbach.schmalzbauer.de [172.21.2.3])i6I09aac094813; Sun, 18 Jul 2004 02:09:37 +0200 (CEST) (envelope-from h@schmalzbauer.de) Received: from cale.flintsbach.schmalzbauer.de (cale.flintsbach.schmalzbauer.de [172.21.1.249]) by korso.flintsbach.schmalzbauer.de (Postfix) with ESMTP id C6C74B4; Sun, 18 Jul 2004 02:09:36 +0200 (CEST) From: Harald Schmalzbauer To: Robert Watson Date: Sun, 18 Jul 2004 02:09:29 +0200 User-Agent: KMail/1.6.2 References: In-Reply-To: X-OS: FreeBSD 5.3 X-Country: Germany X-Address: Munich, 80686 X-Phone2: +49 (0) 89 18947781 X-Name: Harald Schmalzbauer X-Birthday: 06 Oktober 1972 MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_A/b+Au6pZwVp8Oh"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407180209.36199@harryhomeworkstation> X-Spam-Status: No, hits=0.0 required=3.5 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mailjail.dmz.flintsbach.schmalzbauer.de X-Mailman-Approved-At: Sun, 18 Jul 2004 14:22:13 +0000 cc: freebsd-current@freebsd.org Subject: Re: kernel build error in cam_periph_mapmem 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, 18 Jul 2004 00:09:45 -0000 --Boundary-02=_A/b+Au6pZwVp8Oh Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Sonntag, 18. Juli 2004 01:06 schrieb Robert Watson: > On Sun, 18 Jul 2004, Harald Schmalzbauer wrote: > > Yes, it's "cam_periph.c,v 1.56 2003/11/08 10:56:57 scottl" I didn't any > > local modification! I just removed my obj directory but that didn't > > help. CVsup done half an hour ago. Btw, can anybody exlain me what > > timezone the timestamp is from? Shouldn't it be UTC (or at least include > > the TZ code)? > > Can you check to see if your local copy contains an include of mutex.h? > The above time stamp looks right, FYI. Ok, since nobody else seems to have this problem I started poking int the d= ark=20 and found the "error": When I remove #options INVARIANTS from my kernel.config it doesn't stop at = the=20 cam any more. Now I have a pf show stopper but I'm sure this will be fixed soon. Thanks, =2DHarry > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Principal Research Scientist, McAfee Resear= ch --Boundary-02=_A/b+Au6pZwVp8Oh Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA+b/ABylq0S4AzzwRAnEvAJ9QCiHTaFB06BP/2dvg0k3kpP2ZEACfUI2j np+h1VOSfIcUSSP594D16V4= =H8FR -----END PGP SIGNATURE----- --Boundary-02=_A/b+Au6pZwVp8Oh-- From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 15:03: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 7C61916A4CE for ; Sun, 18 Jul 2004 15:03:21 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1624943D31 for ; Sun, 18 Jul 2004 15:03:21 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6IF2q0o010935; Sun, 18 Jul 2004 11:02:52 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6IF2qwX010932; Sun, 18 Jul 2004 11:02:52 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 18 Jul 2004 11:02:52 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Willem Jan Withagen In-Reply-To: <0f4201c46ccf$61de5f90$471b3dd4@digiware.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone 0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 15:03:21 -0000 On Sun, 18 Jul 2004, Willem Jan Withagen wrote: > Started running with debug.mpsafe=1. Not shure if it has anything to do > with it.... It might well do, but here are some things to try: - See if you can reproduce this with your exact some configuration in a few runs. If you can, then we should try some other configurations. - Try it with debug.mpsafenet=0 and see if the problem "goes away" for a few runs. - Try compiling IPv6 out of your kernel -- this will turn on the inpcb locking assertions, which are compiled out by default because IPv4 and IPv6 share the same underlying pcb code and IPv6 does not yet lock that correctly in CVS. I have patches that do quite a bit of that in Perforce, and sent out an e-mail yesterday to the KAME folk to talk about merging strategies. - If this is a reproduceable problem, could you try disabling SACK and see if it changes at all? I'll do some review of the TCP reassembly and queue bits, it could well be that we're missing some locking here. Nicely configured system, btw. :-) BTW, I noticed that there are some bge0 warnings at the end of the dmesg -- is that indicative of some other problem with the driver on the system, and/or is bge0 used in your active configuration? Thanks for the nice bundling of config information, btw -- it answered a number of my questions up front quite nicely. Thanks, Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research > > While running configure over NFS: > > Slab at 0xffffff005c4a8fb8, freei 6 = 0. > panic: Duplicate free of item 0xffffff005c4a8600 from zone 0xffffff007fed4780(Mb > uf) > > cpuid = 1; > KDB: stack backtrace: > kdb_backtrace() at kdb_backtrace+0x34 > panic() at panic+0x1d2 > uma_dbg_free() at uma_dbg_free+0x112 > uma_zfree_arg() at uma_zfree_arg+0x10a > mb_free_ext() at mb_free_ext+0x96 > m_freem() at m_freem+0x28 > tcp_reass() at tcp_reass+0x1bb > tcp_input() at tcp_input+0x2af9 > ip_input() at ip_input+0x94c > netisr_processqueue() at netisr_processqueue+0x8c > swi_net() at swi_net+0xe8 > ithread_loop() at ithread_loop+0x18d > fork_exit() at fork_exit+0xc9 > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffffffb0bb5d00, rbp = 0 --- > KDB: enter: panic > [thread 100017] > Stopped at kdb_enter+0x2e: nop > > Coredump available.... 61Mb compressed. > > system contains a de card, which is correctly identified as > GIANT-LOCKED. The card is not connected. Next time I open up the box, > I'll remove it. > > system info available at: > http://withagen.dyndns.org/FreeBSD/cores/*.opteron > > --WjW > > From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 15:08: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 46E4016A4CE; Sun, 18 Jul 2004 15:08:47 +0000 (GMT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0346F43D31; Sun, 18 Jul 2004 15:08:47 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 460A165218; Sun, 18 Jul 2004 16:08:46 +0100 (BST) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 85508-04-4; Sun, 18 Jul 2004 16:08:45 +0100 (BST) Received: from empiric.dek.spc.org (82-147-17-88.dsl.uk.rapidplay.com [82.147.17.88]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id A8F3B6520F; Sun, 18 Jul 2004 16:08:45 +0100 (BST) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id 9490C61AA; Sun, 18 Jul 2004 16:08:44 +0100 (BST) Date: Sun, 18 Jul 2004 16:08:44 +0100 From: Bruce M Simpson To: Willem Jan Withagen Message-ID: <20040718150844.GD87575@empiric.dek.spc.org> References: <0f4201c46ccf$61de5f90$471b3dd4@digiware.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0f4201c46ccf$61de5f90$471b3dd4@digiware.nl> cc: Robert Watson cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone 0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 15:08:47 -0000 On Sun, Jul 18, 2004 at 03:59:02PM +0200, Willem Jan Withagen wrote: > Coredump available.... 61Mb compressed. > > system contains a de card, which is correctly identified as GIANT-LOCKED. The > card is not connected. Next time I open up the box, I'll remove it. Well this is no big surprise.... de(4) isn't locked properly and probably never will be. BMS From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 15:12: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 BA65216A4CE for ; Sun, 18 Jul 2004 15:12:09 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7834743D5C for ; Sun, 18 Jul 2004 15:12:09 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6IFBftA012399; Sun, 18 Jul 2004 11:11:41 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6IFBfeJ012396; Sun, 18 Jul 2004 11:11:41 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 18 Jul 2004 11:11:41 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Bruce M Simpson In-Reply-To: <20040718150844.GD87575@empiric.dek.spc.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone 0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 15:12:09 -0000 On Sun, 18 Jul 2004, Bruce M Simpson wrote: > On Sun, Jul 18, 2004 at 03:59:02PM +0200, Willem Jan Withagen wrote: > > Coredump available.... 61Mb compressed. > > > > system contains a de card, which is correctly identified as GIANT-LOCKED. The > > card is not connected. Next time I open up the box, I'll remove it. > > Well this is no big surprise.... de(4) isn't locked properly and > probably never will be. However, locking problems with if_de can't (or shouldn't) explain the panic in question :-). We're probably looking either at a SACK problem, or a TCP locking problem. I need to review the TCP callouts, delivery, and reassembly code and make sure all is well. I also need to make sure that I really did merge all the relevant bits of the netperf patch relating to TCP -- there are some changes left, but I think they are purely layout changes. If you want to give it a spin, given some background in TCP, feel free :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 15:15: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 ECCF216A4CF; Sun, 18 Jul 2004 15:15:18 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 098F443D1F; Sun, 18 Jul 2004 15:15:18 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6IFDWsD053609; Sun, 18 Jul 2004 17:13:32 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <0f6a01c46cd8$e1fd5bf0$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Bruce M Simpson" References: <0f4201c46ccf$61de5f90$471b3dd4@digiware.nl> <20040718150844.GD87575@empiric.dek.spc.org> Date: Sun, 18 Jul 2004 17:07:02 +0200 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.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: Robert Watson cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone 0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 15:15:19 -0000 From: "Bruce M Simpson" > On Sun, Jul 18, 2004 at 03:59:02PM +0200, Willem Jan Withagen wrote: > > Coredump available.... 61Mb compressed. > > > > system contains a de card, which is correctly identified as GIANT-LOCKED. The > > card is not connected. Next time I open up the box, I'll remove it. > > Well this is no big surprise.... de(4) isn't locked properly and probably > never will be. Are you meaning to say that that is the cause of the panic?? Even though it just sits there sucking power and taking a slot, but nothing else?? --WjW From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 15:20: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 BE6B616A5A9; Sun, 18 Jul 2004 15:20:11 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C24243D39; Sun, 18 Jul 2004 15:20:10 +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 0B39C1FF9A6; Sun, 18 Jul 2004 17:20:09 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 1596C1FF90C; Sun, 18 Jul 2004 17:20:07 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id B6742155DD; Sun, 18 Jul 2004 15:11:21 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id B38D11539E; Sun, 18 Jul 2004 15:11:22 +0000 (UTC) Date: Sun, 18 Jul 2004 15:11:22 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: FreeBSD current mailing list Message-ID: 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 amd64 mailing list Subject: kldunload if_sk -> LOR & 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: Sun, 18 Jul 2004 15:20:11 -0000 Hi, tried to unload if_sk for testing the newly built module with dwhite's locking patch (will be loaded after reset now :( ). resulted in this on my amd64: --- cut --- noc# kldunload if_sk e1000phy0: detached miibus0: detached lock order reversal 1st 0xffffff0030ac7870 skc0 (network driver) @ sys/pci/if_sk.c:2604 2nd 0xffffff0000b91af0 radix node head (radix node head) @ sys/netinet/in_rmx.c:391 Stack backtrace: witness_checkorder() at witness_checkorder+0x4a6 _mtx_lock_flags() at _mtx_lock_flags+0x39 in_ifadown() at in_ifadown+0x5b in_control() at in_control+0x81c if_detach() at if_detach+0x50b ether_ifdetach() at ether_ifdetach+0x25 sk_detach() at sk_detach+0x6d (null)() at 0 null_method() at null_method Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x8:0xffffffff802450c6 stack pointer = 0x10:0xffffffffa7c1c9b0 frame pointer = 0x10:0xffffffffa7c1c9d0 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 = 1897 (kldunload) kernel: type 9 trap, code=0 Stopped at device_delete_child+0xa: decl %eax db> where device_delete_child() at device_delete_child+0xa device_delete_child() at device_delete_child+0x20 sk_detach() at sk_detach+0x89 (null)() at 0 null_method() at null_method --- cut --- kernel is from Sat Jul 10 20:16:23 UTC 2004 thus before MOD_QUIESCE etc. --- cut --- bz@noc:/usr/obj/u1/src/HEAD/src/sys/AMD64-20040710-01> nm kernel.debug | grep ffffffff802450 ffffffff80245010 T device_add_child ffffffff80245024 T device_add_child_ordered ffffffff802450bc T device_delete_child bz@noc:/usr/obj/u1/src/HEAD/src/sys/AMD64-20040710-01> addr2line -e kernel.debug 0xffffffff802450c6 /u1/src/HEAD/src/sys/kern/subr_bus.c:1222 bz@noc:/usr/obj/u1/src/HEAD/src/sys/AMD64-20040710-01> head -n 1230 /u1/src/HEAD/src/sys/kern/subr_bus.c | tail -18 int device_delete_child(device_t dev, device_t child) { int error; device_t grandchild; PDEBUG(("%s from %s", DEVICENAME(child), DEVICENAME(dev))); /* remove children first */ while ( (grandchild = TAILQ_FIRST(&child->children)) ) { error = device_delete_child(child, grandchild); if (error) return (error); } if ((error = device_detach(child)) != 0) return (error); if (child->devclass) --- cut --- -- Greetings Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 15:26: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 D085716A4CE for ; Sun, 18 Jul 2004 15:26:18 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60FEC43D48 for ; Sun, 18 Jul 2004 15:26:18 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i6IFP1vj012737; Sun, 18 Jul 2004 09:25:01 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 18 Jul 2004 09:25:02 -0600 (MDT) Message-Id: <20040718.092502.11989808.imp@bsdimp.com> To: dan@langille.org From: "M. Warner Losh" In-Reply-To: <40F9110F.13794.15FF9E60@localhost> References: <20040717153016.GA3805@frontfree.net> <40F9110F.13794.15FF9E60@localhost> 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: current@FreeBSD.ORG Subject: Re: About ISC-cron 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, 18 Jul 2004 15:26:18 -0000 In message: <40F9110F.13794.15FF9E60@localhost> "Dan Langille" writes: : On 17 Jul 2004 at 23:30, Xin LI wrote: : : > /* POLA will be respected :-) */ : : One thing about /etc/crontab which has caught out many people: the : last entry must have an ENTER at the end of the line or it will be : ignored. Actually, it must have a newline at the end of the line. : FWIW, /etc/sysctl.conf has the same issue. This one is a lot harder to fix, because shell will ignore the last line. Warner From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 15:30: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 8D4F916A4CE; Sun, 18 Jul 2004 15:30:46 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC22A43D48; Sun, 18 Jul 2004 15:30:45 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6IFT0sD053910; Sun, 18 Jul 2004 17:29:00 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <0f7001c46cdb$0b23cdf0$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Robert Watson" References: Date: Sun, 18 Jul 2004 17:22:30 +0200 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.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone 0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 15:30:46 -0000 From: "Robert Watson" > On Sun, 18 Jul 2004, Willem Jan Withagen wrote: > > > Started running with debug.mpsafe=1. Not shure if it has anything to do > > with it.... > > It might well do, but here are some things to try: > > - See if you can reproduce this with your exact some configuration in a > few runs. If you can, then we should try some other configurations. Yup, just got almost the same one.... It took a little longer, but perhaps cause I did not untar the port I'm trying to test on amd64. Slab at 0xffffff006624ffa0, freei 29 = 0. panic: Duplicate free of item 0xffffff006624fcb0 from zone 0xffffff007fed4180(Fi les) cpuid = 1; KDB: stack backtrace: kdb_backtrace() at kdb_backtrace+0x34 panic() at panic+0x1d2 uma_dbg_free() at uma_dbg_free+0x112 uma_zfree_arg() at uma_zfree_arg+0x10a ffree() at ffree+0x8e fdrop_locked() at fdrop_locked+0xce fdrop() at fdrop+0x32 getdirentries() at getdirentries+0x2fc syscall() at syscall+0x2fa Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (196, FreeBSD ELF64, getdirentries), rip = 0x2006a2204, rsp = 0x7fff ffffe758, rbp = 0x7fffffffe780 --- KDB: enter: panic [thread 100132] Stopped at kdb_enter+0x2e: nop I'll try one more time. > - Try it with debug.mpsafenet=0 and see if the problem "goes away" for a > few runs. I'll disable mpsafenet for the then next 2 runs... > - Try compiling IPv6 out of your kernel -- this will turn on the inpcb > locking assertions, which are compiled out by default because IPv4 and > IPv6 share the same underlying pcb code and IPv6 does not yet lock that > correctly in CVS. I have patches that do quite a bit of that in > Perforce, and sent out an e-mail yesterday to the KAME folk to talk > about merging strategies. > > - If this is a reproduceable problem, could you try disabling SACK and see > if it changes at all? For future steps. > I'll do some review of the TCP reassembly and queue bits, it could well be > that we're missing some locking here. Nicely configured system, btw. :-) I needed a "big" tax/profit reduction in my company.... Why not spend it on a nice toy. > BTW, I noticed that there are some bge0 warnings at the end of the dmesg > -- is that indicative of some other problem with the driver on the system, > and/or is bge0 used in your active configuration? Thanks for the nice > bundling of config information, btw -- it answered a number of my > questions up front quite nicely. Thanx, I think that is the simpelest way for me to keep this easy available. I'm considering updating this info with a /usr/local/etc/rc.d script... Just timestamp it, and autoremove things older than a few versions. The bge0 device is the active one.... It plugs into a noname switch, and it could be that line-negotiation is not fast enough to be ready for the bge0 to timeout on handshaking to get the line-mode. The watchdog reset gets things straightend out. Not it is a onboard Broadcom BCM5705, which has perhaps some flaws (as was claimed some time ago???) We're up again, but I'll remove the de0 card first. To be continued, --WjW From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 17:04: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 3C22216A4CE for ; Sun, 18 Jul 2004 17:04:56 +0000 (GMT) Received: from smtp.cegetel.net (mf01.sitadelle.com [212.94.174.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A76F43D46 for ; Sun, 18 Jul 2004 17:04:55 +0000 (GMT) (envelope-from tataz@sitadelle.com) Received: from droopy.tech.sitadelle.com (unknown [213.223.184.201]) by smtp.cegetel.net (Postfix) with ESMTP id 7996F379B5 for ; Sun, 18 Jul 2004 19:04:53 +0200 (CEST) Received: by droopy.tech.sitadelle.com (Postfix, from userid 1000) id 6654CFC2F5; Sun, 18 Jul 2004 16:08:56 +0200 (CEST) Date: Sun, 18 Jul 2004 16:08:56 +0200 From: Jeremie Le Hen To: freebsd-current@freebsd.org Message-ID: <20040718140856.GI9548@sitadelle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.5.1+cvs20040105i Subject: Re: Call for PRs: nullfs 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, 18 Jul 2004 17:04:56 -0000 This mail never reached my mailbox back the first time I sent it. Second try. ----- Forwarded message from Jeremie Le Hen ----- Subject: Re: Call for PRs: nullfs From: Jeremie Le Hen To: Mark Linimon Cc: freebsd-current@freebsd.org > kern/51583 (confirmed still a problem in -STABLE, -CURRENT) I tried the attached patch, and it's appear to be only a half-fix. To test it, I made a small server which listens on a named Unix socket and a client sending an hello message through it. Here are the results on a 5-CURRENT (about 50 days ago) (`lower' means the program opens the socket on the lower filesystem while `upper' means it is on the null layer) : Without patch With Dmitry Sivachenko's patch client(lower) / OK OK server(lower) client(upper) / Failed OK server(lower) client(lower) / Failed Failed server(upper) client(upper) / OK OK server(upper) I hope this can help. I tried to understand why it fails, but my programming skills are not good enough. Regards, -- Jeremie LE HEN aka TtZ/TataZ jeremie.le-hen@epita.fr ttz@epita.fr Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 17:04: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 3C8DF16A4CF for ; Sun, 18 Jul 2004 17:04:56 +0000 (GMT) Received: from smtp.cegetel.net (mf01.sitadelle.com [212.94.174.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A8CB43D48 for ; Sun, 18 Jul 2004 17:04:55 +0000 (GMT) (envelope-from tataz@sitadelle.com) Received: from droopy.tech.sitadelle.com (unknown [213.223.184.201]) by smtp.cegetel.net (Postfix) with ESMTP id 79091379B3 for ; Sun, 18 Jul 2004 19:04:53 +0200 (CEST) Received: by droopy.tech.sitadelle.com (Postfix, from userid 1000) id 9EBC9FC321; Fri, 16 Jul 2004 16:00:48 +0200 (CEST) Date: Fri, 16 Jul 2004 16:00:48 +0200 From: Jeremie Le Hen To: Mark Linimon Message-ID: <20040716140048.GF9548@sitadelle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.5.1+cvs20040105i cc: freebsd-current@freebsd.org Subject: Re: Call for PRs: nullfs 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, 18 Jul 2004 17:04:56 -0000 > kern/51583 (confirmed still a problem in -STABLE, -CURRENT) I tried the attached patch, and it's appear to be only a half-fix. To test it, I made a small server which listens on a named Unix socket and a client sending an hello message through it. Here are the results on a 5-CURRENT (about 50 days ago) (`lower' means the program opens the socket on the lower filesystem while `upper' means it is on the null layer) : Without patch With Dmitry Sivachenko's patch client(lower) / OK OK server(lower) client(upper) / Failed OK server(lower) client(lower) / Failed Failed server(upper) client(upper) / OK OK server(upper) I hope this can help. I tried to understand why it fails, but my programming skills are not good enough. Regards, -- Jeremie LE HEN aka TtZ/TataZ jeremie.le-hen@epita.fr ttz@epita.fr Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 17:17: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 3FCD616A4CE for ; Sun, 18 Jul 2004 17:17:16 +0000 (GMT) Received: from apathy.neglect.us (rapture.nine.org [69.17.66.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08FE543D53 for ; Sun, 18 Jul 2004 17:17:16 +0000 (GMT) (envelope-from matt+list.sw.freebsd.current@publicly.neglect.us) Received: from [192.168.1.3] (dsl093-038-016.pdx1.dsl.speakeasy.net [66.93.38.16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by apathy.neglect.us (Postfix) with ESMTP id EB233C6F for ; Sun, 18 Jul 2004 13:17:14 -0400 (EDT) Date: Sun, 18 Jul 2004 10:16:54 -0700 From: Matt White To: freebsd-current@freebsd.org Message-ID: <54364243CABEBD11E5088CB5@[192.168.1.3]> X-Mailer: Mulberry/3.1.3 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: fetch hangs, part 2 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, 18 Jul 2004 17:17:16 -0000 I looked in the archives and saw that a couple of others also had this problem. Fetch is getting distributions for ports and it'll just hang. Killing the build and restarting it will usually cause it to advance. Did any of you guys who saw this problem before come up with a solution? -Matt From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 17:17: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 BA96016A4CE; Sun, 18 Jul 2004 17:17:46 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6A9443D45; Sun, 18 Jul 2004 17:17:45 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6IHFusD056046; Sun, 18 Jul 2004 19:15:56 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <0fe101c46ce9$fba26440$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Willem Jan Withagen" , "Robert Watson" References: <0f7001c46cdb$0b23cdf0$471b3dd4@digiware.nl> Date: Sun, 18 Jul 2004 19:09:27 +0200 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.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 17:17:46 -0000 From: "Willem Jan Withagen" To: "Robert Watson" > > On Sun, 18 Jul 2004, Willem Jan Withagen wrote: > > > > > Started running with debug.mpsafe=1. Not shure if it has anything to do > > > with it.... > > > > It might well do, but here are some things to try: > > > > - See if you can reproduce this with your exact some configuration in a > > few runs. If you can, then we should try some other configurations. > > Yup, just got almost the same one.... > It took a little longer, but perhaps cause I did not untar the port I'm trying > to test on amd64. > > Slab at 0xffffff006624ffa0, freei 29 = 0. > panic: Duplicate free of item 0xffffff006624fcb0 from zone 0xffffff007fed4180(Fi > les) > > cpuid = 1; > KDB: stack backtrace: > kdb_backtrace() at kdb_backtrace+0x34 > panic() at panic+0x1d2 > uma_dbg_free() at uma_dbg_free+0x112 > uma_zfree_arg() at uma_zfree_arg+0x10a > ffree() at ffree+0x8e > fdrop_locked() at fdrop_locked+0xce > fdrop() at fdrop+0x32 > getdirentries() at getdirentries+0x2fc > syscall() at syscall+0x2fa > Xfast_syscall() at Xfast_syscall+0xa8 > --- syscall (196, FreeBSD ELF64, getdirentries), rip = 0x2006a2204, rsp = 0x7fff > ffffe758, rbp = 0x7fffffffe780 --- > KDB: enter: panic > [thread 100132] > Stopped at kdb_enter+0x2e: nop > > I'll try one more time. Well not quite: ---- panic: process 47044(find):2 holds Giant but isn't blocked on a lock cpuid = 1; KDB: enter: panic ---- After which the console froze... I'll try again. --WjW From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 17:33: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 4640116A4CE; Sun, 18 Jul 2004 17:33:20 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id A67FA43D58; Sun, 18 Jul 2004 17:33:19 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6IHVTsD056340; Sun, 18 Jul 2004 19:31:30 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <0ff801c46cec$28681d10$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Willem Jan Withagen" , "Robert Watson" References: <0f7001c46cdb$0b23cdf0$471b3dd4@digiware.nl> <0fe101c46ce9$fba26440$471b3dd4@digiware.nl> Date: Sun, 18 Jul 2004 19:25:01 +0200 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.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 17:33:20 -0000 ----- Original Message ----- From: "Willem Jan Withagen" To: "Willem Jan Withagen" ; "Robert Watson" Slab at 0xffffff005c79dfb8, freei 0 = 0. panic: Duplicate free of item 0xffffff005c79d000 from zone 0xffffff007fed4780(Mbuf) cpuid = 1; KDB: stack backtrace: kdb_backtrace() at kdb_backtrace+0x34 panic() at panic+0x1d2 uma_dbg_free() at uma_dbg_free+0x112 uma_zfree_arg() at uma_zfree_arg+0x10a mb_free_ext() at mb_free_ext+0x96 sbcompress() at sbcompress+0x1b7 sbappendstream_locked() at sbappendstream_locked+0x63 tcp_reass() at tcp_reass+0x300 tcp_input() at tcp_input+0x2af9 ip_input() at ip_input+0x94c netisr_processqueue() at netisr_processqueue+0x8c swi_net() at swi_net+0xe8 ithread_loop() at ithread_loop+0x18d fork_exit() at fork_exit+0xc9 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffb0bb5d00, rbp = 0 --- KDB: enter: panic [thread 100017] Stopped at kdb_enter+0x2e: nop ------ Three stikes and out.... I'll disable mpsafe now.... NOTE: the de0 was already removed from the box.... --WjW From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 17:38: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 E031016A4CE for ; Sun, 18 Jul 2004 17:38:37 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E9A543D41 for ; Sun, 18 Jul 2004 17:38:37 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) i6IHcams073226; Sun, 18 Jul 2004 13:38:36 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i6IHcYRC073223; Sun, 18 Jul 2004 13:38:35 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Sun, 18 Jul 2004 13:38:34 -0400 (EDT) From: Andre Guibert de Bruet To: Matt White In-Reply-To: <54364243CABEBD11E5088CB5@[192.168.1.3]> Message-ID: <20040718132619.I24726@alpha.siliconlandmark.com> References: <54364243CABEBD11E5088CB5@[192.168.1.3]> 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: fetch hangs, part 2 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, 18 Jul 2004 17:38:38 -0000 On Sun, 18 Jul 2004, Matt White wrote: > I looked in the archives and saw that a couple of others also had this > problem. Fetch is getting distributions for ports and it'll just hang. > Killing the build and restarting it will usually cause it to advance. Did > any of you guys who saw this problem before come up with a solution? This report is void of anything that can give a clue as to what the problem could be. What state is the process wedged in? What platform? What NIC are you using? You're running CURRENT as of what date? Is it 100% reproduceable on your system? If so, can you make a ktrace available? Does wget hang in a similar fashion? Regards, Andy > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ > From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 17:44: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 4E25616A4DD for ; Sun, 18 Jul 2004 17:44:01 +0000 (GMT) Received: from blair.epifora.com (blair.epifora.com [207.139.168.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1798843D2F for ; Sun, 18 Jul 2004 17:44:01 +0000 (GMT) (envelope-from drvince@anonymnet.net) Received: from localhost (localhost.epifora.com [127.0.0.1]) by blair.epifora.com (Postfix) with ESMTP id 448C1165960 for ; Sun, 18 Jul 2004 13:44:22 -0400 (EDT) Received: from mail.anonymnet.net ([205.205.52.19]) by localhost (blair.epifora.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06739-08 for ; Sun, 18 Jul 2004 13:44:20 -0400 (EDT) Received: from mail.anonymnet.net (mail.anonymnet.net [205.205.52.19]) by mail.anonymnet.net (Postfix) with ESMTP id 76B70165931 for ; Sun, 18 Jul 2004 13:44:20 -0400 (EDT) From: "DrVince" To: "freebsd-current" Date: Sun, 18 Jul 2004 12:44:20 -0500 Message-Id: <20040718174256.M94141@anonymnet.net> X-Mailer: Open WebMail 2.30 20040131 X-OriginatingIP: 205.205.52.19 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: GEOM 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, 18 Jul 2004 17:44:01 -0000 Hi, howcome, in recent build, I don't see GEOM create disks message at boot time anymore? example: GEOM: create disk ad0 dp=0xc1d00970 DrVince DrVince@anonymnet.net From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 17:51: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 A514D16A4CE for ; Sun, 18 Jul 2004 17:51:03 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AD7443D2D for ; Sun, 18 Jul 2004 17:51:02 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from h00609772adf0.ne.client2.attbi.com ([66.30.114.143]) by comcast.net (sccrmhc12) with ESMTP id <2004071817510001200fkhp2e>; Sun, 18 Jul 2004 17:51:01 +0000 Received: from h00609772adf0.ne.client2.attbi.com (localhost [127.0.0.1]) i6IHox05001272; Sun, 18 Jul 2004 13:51:00 -0400 (EDT) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost)i6IHoxDu001271; Sun, 18 Jul 2004 13:50:59 -0400 (EDT) (envelope-from rodrigc) Date: Sun, 18 Jul 2004 13:50:59 -0400 From: Craig Rodrigues To: DrVince Message-ID: <20040718175059.GA1253@crodrigues.org> References: <20040718174256.M94141@anonymnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040718174256.M94141@anonymnet.net> User-Agent: Mutt/1.4.1i cc: freebsd-current Subject: Re: GEOM 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, 18 Jul 2004 17:51:03 -0000 On Sun, Jul 18, 2004 at 12:44:20PM -0500, DrVince wrote: > Hi, > howcome, in recent build, I don't see GEOM create disks message at boot time > anymore? > > example: GEOM: create disk ad0 dp=0xc1d00970 See: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/geom/geom_disk.c.diff?r1=1.81&r2=1.82 Revision 1.82 / (download) - annotate - [select for diffs], Fri Jan 23 10:56:16 2004 UTC (5 months, 3 weeks ago) by phk Branch: MAIN Changes since 1.81: +0 -6 lines Diff to previous 1.81 (colored) Remove no longer necessary debug printfs -- Craig Rodrigues http://crodrigues.org rodrigc@crodrigues.org From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 17:51: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 CF82F16A4CE; Sun, 18 Jul 2004 17:51:42 +0000 (GMT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C78543D2F; Sun, 18 Jul 2004 17:51:42 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i6IHpfWg029302 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 18 Jul 2004 13:51:42 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i6IHpagI041654; Sun, 18 Jul 2004 13:51:36 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16634.47272.768935.436137@grasshopper.cs.duke.edu> Date: Sun, 18 Jul 2004 13:51:36 -0400 (EDT) To: simokawa@freebsd.org X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: current@freebsd.org Subject: Excellent job on the firewire 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: Sun, 18 Jul 2004 17:51:42 -0000 Hi, I just wanted to say that I used FreeBSD's firewire and sbp-II support for the first time this weekend. It seems to be fast (over 26MB/sec writes, 34MB/sec reads to a LaCie 160GB drive), and robust. It works well on non-i386 platforms -- I'm using it to back up an amd64, and to serve as a root device for a FreeBSD/powerpc machine. All in all, it totally exceeded my expectations. Thank you very much| Drew From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 18:17: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 B532716A4CE; Sun, 18 Jul 2004 18:17:18 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C20843D45; Sun, 18 Jul 2004 18:17:18 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) i6IIHHbi073446; Sun, 18 Jul 2004 14:17:17 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i6IIHG41073443; Sun, 18 Jul 2004 14:17:16 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Sun, 18 Jul 2004 14:17:16 -0400 (EDT) From: Andre Guibert de Bruet To: Daniel Lang In-Reply-To: <20040715193217.GC7804@atrbg11.informatik.tu-muenchen.de> Message-ID: <20040718135510.R24726@alpha.siliconlandmark.com> References: <20040715183415.GA7804@atrbg11.informatik.tu-muenchen.de> <20040715185801.GB7804@atrbg11.informatik.tu-muenchen.de> <20040715193217.GC7804@atrbg11.informatik.tu-muenchen.de> 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: Scott Long cc: current@freebsd.org Subject: Re: tuning hints for PAE 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, 18 Jul 2004 18:17:18 -0000 On Thu, 15 Jul 2004, Daniel Lang wrote: > My values are the following (with adjusted maxvnodes): > [..] > kern.maxvnodes: 64000 > vnodes 35 7K 7K 166 16,32,64,128,256 > kern.minvnodes: 52958 > vm.stats.vm.v_vnodein: 568488 > vm.stats.vm.v_vnodeout: 1 > vm.stats.vm.v_vnodepgsin: 1384470 > vm.stats.vm.v_vnodepgsout: 1 > vfs.numvnodes: 190867 > vfs.wantfreevnodes: 25 > vfs.freevnodes: 135112 > debug.sizeof.vnode: 264 > [..] > > So the actual consumed memory (7k ?) appears neglectible. > However, kern.minvnodes has nearly reached the now upper limit, > so maybe trimming maxvnodes to 64000 was maybe too small, > and the saved space appears not worth the effort? > > I will bump it up a bit more... > > What about the 35 vnodes "In Use" (reported by kern.malloc) but > vfs.numvnodes: 190867, I am not sure how to interpret these > values.... > > As far as I understand it, a vnode is a kernel data-structure > referring to a file-like entity (file, directory, socket, pipe, etc). > So there are obviously much more in use than 35. 190867 appears > too much, for ~ 400 active processes. Even if there are many > filedescriptors open by each process, it is probably much less than 500 > per process. But maybe if these include all cached vnodes, so > all vnodes which have been in use in the past, it could fit. > > Sorry for being not too educated about this really basic > UNIX concept. :-} Daniel, If you are running a lot of dynamically-linked programs, an fd is allocated for every library that is imported. If you really want to find out what's going on where as far as fds on your system, lsof(8) from ports is your friend. Vnodes, are kernel-land structures that can reference any file or directory. Your vnode use count is always going to be greater than the number of open fds on your system. The two are somewhat related because you're guaranteed to have a vnode allocated for every file that is opened and for each process' current working directory (In the case of multiple programs accessing the same file or directory, the kernel increments the given vnode's reference count). The kernel keeps a vnode cache in order to limit the number of expensive lookups that would otherwise have to be performed while heavy I/O is under way. The namei(9) and vnode(9) manpages contain a wealth of information on the matter. I hope this helps. :) Regards, Andy > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ > From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 18:38: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 95D2616A4CE for ; Sun, 18 Jul 2004 18:38:19 +0000 (GMT) Received: from apathy.neglect.us (rapture.nine.org [69.17.66.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47DC343D2D for ; Sun, 18 Jul 2004 18:38:19 +0000 (GMT) (envelope-from matt+list.sw.freebsd.current@publicly.neglect.us) Received: from [192.168.1.3] (dsl093-038-016.pdx1.dsl.speakeasy.net [66.93.38.16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by apathy.neglect.us (Postfix) with ESMTP id 4BA19BB1 for ; Sun, 18 Jul 2004 14:38:18 -0400 (EDT) Date: Sun, 18 Jul 2004 11:37:57 -0700 From: Matt White Cc: freebsd-current@freebsd.org Message-ID: <603030034410753A40738823@[192.168.1.3]> In-Reply-To: <20040718132619.I24726@alpha.siliconlandmark.com> References: <54364243CABEBD11E5088CB5@[192.168.1.3]> <20040718132619.I24726@alpha.siliconlandmark.com> X-Mailer: Mulberry/3.1.3 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: fetch hangs, part 2 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, 18 Jul 2004 18:38:19 -0000 Sorry, I was referring to a previous post which described exactly the problem I was having. I was more asking if those guys had figured out what was going on. In fact, I think that's pretty clear from my message. But as to your questions: Not 100% reproducible, but happens enough that I can't leave a large fetch going and expect it to be done when I get back. Haven't tried wget because the previous posts indicated that they were unable to get it to work with the ports system. This is a 5.2.1 system cvsupped as of 7/17. Device is a RealTek 8139. Processes wedge in sbwait. No ktrace right now because I need to head out, but I should be able to get one this evening. -Matt --On Sunday, July 18, 2004 1:38 PM -0400 Andre Guibert de Bruet wrote: > > On Sun, 18 Jul 2004, Matt White wrote: > >> I looked in the archives and saw that a couple of others also had this >> problem. Fetch is getting distributions for ports and it'll just hang. >> Killing the build and restarting it will usually cause it to advance. >> Did any of you guys who saw this problem before come up with a solution? > > This report is void of anything that can give a clue as to what the > problem could be. What state is the process wedged in? What platform? > What NIC are you using? You're running CURRENT as of what date? Is it > 100% reproduceable on your system? If so, can you make a ktrace > available? Does wget hang in a similar fashion? > > Regards, > Andy > >> Andre Guibert de Bruet | Enterprise Software Consultant > >> Silicon Landmark, LLC. | http://siliconlandmark.com/ > > From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 18:48: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 2566F16A4CE for ; Sun, 18 Jul 2004 18:48:58 +0000 (GMT) Received: from lakermmtao07.cox.net (lakermmtao07.cox.net [68.230.240.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF62043D1F for ; Sun, 18 Jul 2004 18:48:57 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao07.cox.net ESMTP <20040718184856.PQRM16724.lakermmtao07.cox.net@dolphin.local.net>; Sun, 18 Jul 2004 14:48:56 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.12.11/8.12.11) with ESMTP id i6IImuIv041588; Sun, 18 Jul 2004 13:48:56 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.12.11/8.12.11/Submit) id i6IImucB041587; Sun, 18 Jul 2004 13:48:56 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <54364243CABEBD11E5088CB5@[192.168.1.3]> Date: Sun, 18 Jul 2004 13:48:56 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: Matt White cc: freebsd-current@freebsd.org Subject: Re: fetch hangs, part 2 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: Sun, 18 Jul 2004 18:48:58 -0000 On 18-Jul-2004 Matt White wrote: > I looked in the archives and saw that a couple of others also had > this > problem. Fetch is getting distributions for ports and it'll just > hang. > Killing the build and restarting it will usually cause it to advance. > Did > any of you guys who saw this problem before come up with a solution? I found that changing my buffer size settings made all the difference. I had been using the following in /etc/sysctl.conf: net.inet.tcp.recvspace=131072 net.inet.tcp.sendspace=65536 Changing them to: net.inet.tcp.recvspace=65536 net.inet.tcp.sendspace=32768 Solved the problem. -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 18:54: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 2FA4216A4CE for ; Sun, 18 Jul 2004 18:54:41 +0000 (GMT) Received: from lakermmtao11.cox.net (lakermmtao11.cox.net [68.230.240.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id B570743D41 for ; Sun, 18 Jul 2004 18:54:40 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao11.cox.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with ESMTP id <20040718185438.UIEC26822.lakermmtao11.cox.net@dolphin.local.net> for ; Sun, 18 Jul 2004 14:54:38 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.12.11/8.12.11) with ESMTP id i6IIsbN9041642 for ; Sun, 18 Jul 2004 13:54:37 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.12.11/8.12.11/Submit) id i6IIsbEW041641 for freebsd-current@freebsd.org; Sun, 18 Jul 2004 13:54:37 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 18 Jul 2004 13:54:37 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: freebsd-current@freebsd.org Subject: Overriding -Werror in buildworld/buildkernel 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: Sun, 18 Jul 2004 18:54:41 -0000 OK, I understand the developers' desire to catch errors, but didn't we at one time have a means of overriding the -Werror flag? I'm seeing a lot of build failures lately due to warnings, not errors. I thought adding WERROR=-Wno-error would do the trick, but it doesn't. Any ideas? -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 19:05: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 CB4BE16A4CE; Sun, 18 Jul 2004 19:05:45 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D77243D1F; Sun, 18 Jul 2004 19:05:44 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6IJ3qsD058014; Sun, 18 Jul 2004 21:03:52 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <103e01c46cf9$0fdacab0$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Willem Jan Withagen" , "Robert Watson" References: <0f7001c46cdb$0b23cdf0$471b3dd4@digiware.nl> <0fe101c46ce9$fba26440$471b3dd4@digiware.nl> <0ff801c46cec$28681d10$471b3dd4@digiware.nl> Date: Sun, 18 Jul 2004 20:57:23 +0200 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.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 19:05:45 -0000 > Three stikes and out.... > I'll disable mpsafe now.... Does not seem to help.... Not shure if anything should be read in the fact that it is 3 times in [thread 100007]. --WjW panic: Duplicate free of item 0xffffff00614fb800 from zone 0xffffff007fed 4780(Mbuf) cpuid = 1; KDB: stack backtrace: kdb_backtrace() at kdb_backtrace+0x34 panic() at panic+0x1d2 uma_dbg_free() at uma_dbg_free+0x112 uma_zfree_arg() at uma_zfree_arg+0x10a mb_free_ext() at mb_free_ext+0x96 m_freem() at m_freem+0x28 ether_demux() at ether_demux+0x341 ether_input() at ether_input+0x247 bge_rxeof() at bge_rxeof+0x36b bge_intr() at bge_intr+0x15a ithread_loop() at ithread_loop+0x18d fork_exit() at fork_exit+0xc9 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffb0b7cd00, rbp = 0 --- KDB: enter: panic [thread 100007] Stopped at kdb_enter+0x2e: nop And: Slab at 0xffffff00612d7fb8, freei 3 = 0. panic: Duplicate free of item 0xffffff00612d7300 from zone 0xffffff007fed4780(Mbuf) cpuid = 1; KDB: stack backtrace: kdb_backtrace() at kdb_backtrace+0x34 panic() at panic+0x1d2 uma_dbg_free() at uma_dbg_free+0x112 uma_zfree_arg() at uma_zfree_arg+0x10a mb_free_ext() at mb_free_ext+0x96 m_freem() at m_freem+0x28 tcp_input() at tcp_input+0x2b24 ip_input() at ip_input+0x94c netisr_processqueue() at netisr_processqueue+0x8c swi_net() at swi_net+0xaf ithread_loop() at ithread_loop+0x18d fork_exit() at fork_exit+0xc9 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffb0bb5d00, rbp = 0 --- KDB: enter: panic [thread 100017] Stopped at kdb_enter+0x2e: nop And: Slab at 0xffffff005926ffb8, freei 13 = 0. panic: Duplicate free of item 0xffffff005926fd00 from zone 0xffffff007fed4780(Mb uf) cpuid = 1; KDB: stack backtrace: kdb_backtrace() at kdb_backtrace+0x34 panic() at panic+0x1d2 uma_dbg_free() at uma_dbg_free+0x112 uma_zfree_arg() at uma_zfree_arg+0x10a mb_free_ext() at mb_free_ext+0x96 m_freem() at m_freem+0x28 ether_demux() at ether_demux+0x341 ether_input() at ether_input+0x247 bge_rxeof() at bge_rxeof+0x36b bge_intr() at bge_intr+0x15a ithread_loop() at ithread_loop+0x18d fork_exit() at fork_exit+0xc9 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffb0b7cd00, rbp = 0 --- KDB: enter: panic [thread 100007] Stopped at kdb_enter+0x2e: nop From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 19:07: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 0E96C16A4CE; Sun, 18 Jul 2004 19:07:13 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D43B43D46; Sun, 18 Jul 2004 19:07:12 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6IJ5QsD058106; Sun, 18 Jul 2004 21:05:26 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <104401c46cf9$480cee40$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Robert Watson" References: Date: Sun, 18 Jul 2004 20:58:58 +0200 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.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone 0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 19:07:13 -0000 Starting on: > - Try compiling IPv6 out of your kernel -- this will turn on the inpcb > locking assertions, which are compiled out by default because IPv4 and > IPv6 share the same underlying pcb code and IPv6 does not yet lock that > correctly in CVS. I have patches that do quite a bit of that in > Perforce, and sent out an e-mail yesterday to the KAME folk to talk > about merging strategies. > > - If this is a reproduceable problem, could you try disabling SACK and see > if it changes at all? How do I disable SACK?? Probably there's a flag for, but which.... --WjW From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 19:09: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 5703F16A4CE for ; Sun, 18 Jul 2004 19:09:01 +0000 (GMT) Received: from apathy.neglect.us (rapture.nine.org [69.17.66.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F9A543D41 for ; Sun, 18 Jul 2004 19:09:01 +0000 (GMT) (envelope-from matt+list.sw.freebsd.current@publicly.neglect.us) Received: from [192.168.1.3] (dsl093-038-016.pdx1.dsl.speakeasy.net [66.93.38.16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by apathy.neglect.us (Postfix) with ESMTP id 38A9EBA6 for ; Sun, 18 Jul 2004 15:09:00 -0400 (EDT) Date: Sun, 18 Jul 2004 12:08:40 -0700 From: Matt White To: freebsd-current@freebsd.org Message-ID: <2EDF6D54F4853447EB6F9018@[192.168.1.3]> In-Reply-To: References: X-Mailer: Mulberry/3.1.3 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: fetch hangs, part 2 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, 18 Jul 2004 19:09:01 -0000 Conrad: Thanks, but it looks like those are the default settings, so I'm guessing setting that's not going to help me. It's probably better to figure out what's wrong here anyway so we can use whatever settings we want. If I don't hear anything more, I'll try to get a ktrace tonight. -Matt --On Sunday, July 18, 2004 1:48 PM -0500 "Conrad J. Sabatier" wrote: > > On 18-Jul-2004 Matt White wrote: >> I looked in the archives and saw that a couple of others also had >> this >> problem. Fetch is getting distributions for ports and it'll just >> hang. >> Killing the build and restarting it will usually cause it to advance. >> Did >> any of you guys who saw this problem before come up with a solution? > > I found that changing my buffer size settings made all the difference. > I had been using the following in /etc/sysctl.conf: > > net.inet.tcp.recvspace=131072 > net.inet.tcp.sendspace=65536 > > Changing them to: > > net.inet.tcp.recvspace=65536 > net.inet.tcp.sendspace=32768 > > Solved the problem. > > -- > Conrad J. Sabatier -- "In Unix veritas" > _______________________________________________ > 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 Jul 18 19:13:49 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 7331216A4CE for ; Sun, 18 Jul 2004 19:13:49 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31FEB43D49 for ; Sun, 18 Jul 2004 19:13:49 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6IJDKud037781; Sun, 18 Jul 2004 15:13:20 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6IJDK4S037778; Sun, 18 Jul 2004 15:13:20 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 18 Jul 2004 15:13:20 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Willem Jan Withagen In-Reply-To: <104401c46cf9$480cee40$471b3dd4@digiware.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone 0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 19:13:49 -0000 On Sun, 18 Jul 2004, Willem Jan Withagen wrote: > Starting on: > > > - Try compiling IPv6 out of your kernel -- this will turn on the inpcb > > locking assertions, which are compiled out by default because IPv4 and > > IPv6 share the same underlying pcb code and IPv6 does not yet lock that > > correctly in CVS. I have patches that do quite a bit of that in > > Perforce, and sent out an e-mail yesterday to the KAME folk to talk > > about merging strategies. > > > > - If this is a reproduceable problem, could you try disabling SACK and see > > if it changes at all? > > How do I disable SACK?? Probably there's a flag for, but which.... The sysctl net.inet.tcp.sack.enable enables (and disables) SACK. Given some of the other versions of the trace you're reporting, it's seeming less like it's SACK that's causing the problem, but it's definitely worth trying. We could be looking at an issue with the bge driver -- I have some bge cards and will see about sticking one into a machine here for testing. Can you suggest a workload I can try that will reliably generate the panic for you? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 19:15: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 E661F16A4CE for ; Sun, 18 Jul 2004 19:15:47 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D28243D53 for ; Sun, 18 Jul 2004 19:15:47 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6IJFJHU037824; Sun, 18 Jul 2004 15:15:19 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6IJFJGi037821; Sun, 18 Jul 2004 15:15:19 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 18 Jul 2004 15:15:18 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Willem Jan Withagen In-Reply-To: <103e01c46cf9$0fdacab0$471b3dd4@digiware.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 19:15:48 -0000 On Sun, 18 Jul 2004, Willem Jan Withagen wrote: > > Three stikes and out.... > > I'll disable mpsafe now.... > > Does not seem to help.... Not shure if anything should be read in the > fact that it is 3 times in [thread 100007]. Well, the threads involved seem to be the netisr thread and the bge interrupt thread, suggesting we have a problem with mbufs being free'd despite being handed off into the network stack. Up front, it suggests maybe we have an issue with the bge driver freeing or reusing an mbuf inappropriately, or perhaps it's at the TCP layer. Thanks, Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research > > --WjW > > > panic: Duplicate free of item 0xffffff00614fb800 from zone 0xffffff007fed > 4780(Mbuf) > > cpuid = 1; > KDB: stack backtrace: > kdb_backtrace() at kdb_backtrace+0x34 > panic() at panic+0x1d2 > uma_dbg_free() at uma_dbg_free+0x112 > uma_zfree_arg() at uma_zfree_arg+0x10a > mb_free_ext() at mb_free_ext+0x96 > m_freem() at m_freem+0x28 > ether_demux() at ether_demux+0x341 > ether_input() at ether_input+0x247 > bge_rxeof() at bge_rxeof+0x36b > bge_intr() at bge_intr+0x15a > ithread_loop() at ithread_loop+0x18d > fork_exit() at fork_exit+0xc9 > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffffffb0b7cd00, rbp = 0 --- > KDB: enter: panic > [thread 100007] > Stopped at kdb_enter+0x2e: nop > > And: > > Slab at 0xffffff00612d7fb8, freei 3 = 0. > panic: Duplicate free of item 0xffffff00612d7300 from zone > 0xffffff007fed4780(Mbuf) > > cpuid = 1; > KDB: stack backtrace: > kdb_backtrace() at kdb_backtrace+0x34 > panic() at panic+0x1d2 > uma_dbg_free() at uma_dbg_free+0x112 > uma_zfree_arg() at uma_zfree_arg+0x10a > mb_free_ext() at mb_free_ext+0x96 > m_freem() at m_freem+0x28 > tcp_input() at tcp_input+0x2b24 > ip_input() at ip_input+0x94c > netisr_processqueue() at netisr_processqueue+0x8c > swi_net() at swi_net+0xaf > ithread_loop() at ithread_loop+0x18d > fork_exit() at fork_exit+0xc9 > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffffffb0bb5d00, rbp = 0 --- > KDB: enter: panic > [thread 100017] > Stopped at kdb_enter+0x2e: nop > > And: > Slab at 0xffffff005926ffb8, freei 13 = 0. > panic: Duplicate free of item 0xffffff005926fd00 from zone 0xffffff007fed4780(Mb > uf) > > cpuid = 1; > KDB: stack backtrace: > kdb_backtrace() at kdb_backtrace+0x34 > panic() at panic+0x1d2 > uma_dbg_free() at uma_dbg_free+0x112 > uma_zfree_arg() at uma_zfree_arg+0x10a > mb_free_ext() at mb_free_ext+0x96 > m_freem() at m_freem+0x28 > ether_demux() at ether_demux+0x341 > ether_input() at ether_input+0x247 > bge_rxeof() at bge_rxeof+0x36b > bge_intr() at bge_intr+0x15a > ithread_loop() at ithread_loop+0x18d > fork_exit() at fork_exit+0xc9 > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffffffb0b7cd00, rbp = 0 --- > KDB: enter: panic > [thread 100007] > Stopped at kdb_enter+0x2e: nop > > _______________________________________________ > 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 Jul 18 19:25: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 9159816A4CE; Sun, 18 Jul 2004 19:25:06 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id C066643D1F; Sun, 18 Jul 2004 19:25:05 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6IJNJsD058450; Sun, 18 Jul 2004 21:23:19 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <106d01c46cfb$c7d76630$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Robert Watson" References: Date: Sun, 18 Jul 2004 21:16:51 +0200 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.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone 0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 19:25:06 -0000 From: "Robert Watson" > On Sun, 18 Jul 2004, Willem Jan Withagen wrote: > > > Starting on: > > > > > - Try compiling IPv6 out of your kernel -- this will turn on the inpcb > > > locking assertions, which are compiled out by default because IPv4 and > > > IPv6 share the same underlying pcb code and IPv6 does not yet lock that > > > correctly in CVS. I have patches that do quite a bit of that in > > > Perforce, and sent out an e-mail yesterday to the KAME folk to talk > > > about merging strategies. > > > > > > - If this is a reproduceable problem, could you try disabling SACK and see > > > if it changes at all? > > > > How do I disable SACK?? Probably there's a flag for, but which.... > > The sysctl net.inet.tcp.sack.enable enables (and disables) SACK. Given > some of the other versions of the trace you're reporting, it's seeming > less like it's SACK that's causing the problem, but it's definitely worth > trying. We could be looking at an issue with the bge driver -- I have > some bge cards and will see about sticking one into a machine here for > testing. Can you suggest a workload I can try that will reliably generate > the panic for you? Well I could also try this with the em0 interface, and see if the same occurs.... What am I doing to get the panic: In one shell I try to compile /usr/ports/net-mgmt/net-snmp. (Well actually the one I'm working on to get the last tweak out of it when running amd64) And that I keep repeating until it crashes, but unusally one run is enough. In the console I run 'periodic daily', since my box currently always seems to crash during the night when running daily. In a third window I do some work: usually some vi-ing or grepping.... And you write: > > Does not seem to help.... Not shure if anything should be read in the > > fact that it is 3 times in [thread 100007]. > > Well, the threads involved seem to be the netisr thread and the bge > interrupt thread, suggesting we have a problem with mbufs being free'd > despite being handed off into the network stack. Up front, it suggests > maybe we have an issue with the bge driver freeing or reusing an mbuf > inappropriately, or perhaps it's at the TCP layer. Even more reason to do some (ab)using test with the em0 card??? --WjW From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 19:26: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 EED8216A4CE for ; Sun, 18 Jul 2004 19:26:36 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB23243D2F for ; Sun, 18 Jul 2004 19:26:36 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6IJQ8mq037917; Sun, 18 Jul 2004 15:26:08 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6IJQ8iu037914; Sun, 18 Jul 2004 15:26:08 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 18 Jul 2004 15:26:07 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Willem Jan Withagen In-Reply-To: <106d01c46cfb$c7d76630$471b3dd4@digiware.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone 0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 19:26:37 -0000 On Sun, 18 Jul 2004, Willem Jan Withagen wrote: > > Well, the threads involved seem to be the netisr thread and the bge > > interrupt thread, suggesting we have a problem with mbufs being free'd > > despite being handed off into the network stack. Up front, it suggests > > maybe we have an issue with the bge driver freeing or reusing an mbuf > > inappropriately, or perhaps it's at the TCP layer. > > Even more reason to do some (ab)using test with the em0 card??? Yeah, that would be very helpful if you could. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 19:29: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 3DD5016A4CF; Sun, 18 Jul 2004 19:29:30 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E12343D49; Sun, 18 Jul 2004 19:29:29 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6IJRhsD058595; Sun, 18 Jul 2004 21:27:43 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <107101c46cfc$6513a080$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Robert Watson" References: Date: Sun, 18 Jul 2004 21:21:15 +0200 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.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 19:29:30 -0000 > > > Three stikes and out.... > > > I'll disable mpsafe now.... > > > > Does not seem to help.... Not shure if anything should be read in the > > fact that it is 3 times in [thread 100007]. > > Well, the threads involved seem to be the netisr thread and the bge > interrupt thread, suggesting we have a problem with mbufs being free'd > despite being handed off into the network stack. Up front, it suggests > maybe we have an issue with the bge driver freeing or reusing an mbuf > inappropriately, or perhaps it's at the TCP layer. I have the core of the first mpsafe test still here. It's 62 Mb, so that is not to bad, (currently my ADSL is giving 450 Kb/s upstream) so I could make it available....) Or I could do some digging, if you give me pointers. --WjW From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 19:35:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 2237616A4CE; Sun, 18 Jul 2004 19:35:20 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.12.11/8.12.11) with ESMTP id i6IJZJ2F056143; Sun, 18 Jul 2004 15:35:19 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.12.11/8.12.11/Submit) id i6IJZEcF056136; Sun, 18 Jul 2004 15:35:14 -0400 (EDT) (envelope-from green) Date: Sun, 18 Jul 2004 15:35:13 -0400 From: Brian Fundakowski Feldman To: "Bjoern A. Zeeb" Message-ID: <20040718193513.GV1626@green.homeunix.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i cc: FreeBSD current mailing list cc: FreeBSD amd64 mailing list Subject: Re: kldunload if_sk -> LOR & 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: Sun, 18 Jul 2004 19:35:20 -0000 On Sun, Jul 18, 2004 at 03:11:22PM +0000, Bjoern A. Zeeb wrote: > Hi, > > tried to unload if_sk for testing the newly built module with dwhite's > locking patch (will be loaded after reset now :( ). > resulted in this on my amd64: > > --- cut --- > noc# kldunload if_sk > e1000phy0: detached > miibus0: detached > lock order reversal > 1st 0xffffff0030ac7870 skc0 (network driver) @ sys/pci/if_sk.c:2604 > 2nd 0xffffff0000b91af0 radix node head (radix node head) @ sys/netinet/in_rmx.c:391 > Stack backtrace: > witness_checkorder() at witness_checkorder+0x4a6 > _mtx_lock_flags() at _mtx_lock_flags+0x39 > in_ifadown() at in_ifadown+0x5b > in_control() at in_control+0x81c > if_detach() at if_detach+0x50b > ether_ifdetach() at ether_ifdetach+0x25 > sk_detach() at sk_detach+0x6d > (null)() at 0 > null_method() at null_method At the point where it's actually detaching, once it's detached the methods that access its softc, it should drop its softc lock before calling the network-level detach routines. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 19:39: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 E20D016A4CE; Sun, 18 Jul 2004 19:39:29 +0000 (GMT) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4984843D31; Sun, 18 Jul 2004 19:39:29 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from ns0.nlsystems.com (ns0.nlsystems.com [80.177.232.243]) by itchy.rabson.org (8.12.11/8.12.11) with ESMTP id i6IJdG3G050835; Sun, 18 Jul 2004 20:39:16 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-current@freebsd.org Date: Sun, 18 Jul 2004 20:39:10 +0100 User-Agent: KMail/1.6.1 References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> In-Reply-To: <16634.47272.768935.436137@grasshopper.cs.duke.edu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407182039.10773.dfr@nlsystems.com> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on itchy.rabson.org X-Virus-Scanned: clamd / ClamAV version 0.71, clamav-milter version 0.71 X-Virus-Status: Clean cc: simokawa@freebsd.org cc: Andrew Gallatin cc: current@freebsd.org Subject: Re: Excellent job on the firewire 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: Sun, 18 Jul 2004 19:39:30 -0000 On Sunday 18 July 2004 18:51, Andrew Gallatin wrote: > Hi, > > I just wanted to say that I used FreeBSD's firewire and sbp-II > support for the first time this weekend. It seems to be fast (over > 26MB/sec writes, 34MB/sec reads to a LaCie 160GB drive), and robust. > It works well on non-i386 platforms -- I'm using it to back up an > amd64, and to serve as a root device for a FreeBSD/powerpc machine. > > All in all, it totally exceeded my expectations. Thank you very > much| Wait till you try debugging using gdb over firewire with dcons. An all round positive experience :-) From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 19:39: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 E20D016A4CE; Sun, 18 Jul 2004 19:39:29 +0000 (GMT) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4984843D31; Sun, 18 Jul 2004 19:39:29 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from ns0.nlsystems.com (ns0.nlsystems.com [80.177.232.243]) by itchy.rabson.org (8.12.11/8.12.11) with ESMTP id i6IJdG3G050835; Sun, 18 Jul 2004 20:39:16 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-current@freebsd.org Date: Sun, 18 Jul 2004 20:39:10 +0100 User-Agent: KMail/1.6.1 References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> In-Reply-To: <16634.47272.768935.436137@grasshopper.cs.duke.edu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407182039.10773.dfr@nlsystems.com> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on itchy.rabson.org X-Virus-Scanned: clamd / ClamAV version 0.71, clamav-milter version 0.71 X-Virus-Status: Clean cc: simokawa@freebsd.org cc: Andrew Gallatin cc: current@freebsd.org Subject: Re: Excellent job on the firewire 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: Sun, 18 Jul 2004 19:39:30 -0000 On Sunday 18 July 2004 18:51, Andrew Gallatin wrote: > Hi, > > I just wanted to say that I used FreeBSD's firewire and sbp-II > support for the first time this weekend. It seems to be fast (over > 26MB/sec writes, 34MB/sec reads to a LaCie 160GB drive), and robust. > It works well on non-i386 platforms -- I'm using it to back up an > amd64, and to serve as a root device for a FreeBSD/powerpc machine. > > All in all, it totally exceeded my expectations. Thank you very > much| Wait till you try debugging using gdb over firewire with dcons. An all round positive experience :-) From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 19:47: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 BBC4F16A4CE; Sun, 18 Jul 2004 19:47:15 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23B5943D1D; Sun, 18 Jul 2004 19:47:15 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6IJjSsD059041; Sun, 18 Jul 2004 21:45:29 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <108901c46cfe$e02ec130$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Robert Watson" References: Date: Sun, 18 Jul 2004 21:39:00 +0200 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.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone 0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 19:47:15 -0000 From: "Robert Watson" > On Sun, 18 Jul 2004, Willem Jan Withagen wrote: > > > > Well, the threads involved seem to be the netisr thread and the bge > > > interrupt thread, suggesting we have a problem with mbufs being free'd > > > despite being handed off into the network stack. Up front, it suggests > > > maybe we have an issue with the bge driver freeing or reusing an mbuf > > > inappropriately, or perhaps it's at the TCP layer. > > > > Even more reason to do some (ab)using test with the em0 card??? > > Yeah, that would be very helpful if you could. Well uptill now it was less than 30 minutes to get a crash.... No counting the ones where it directly crashed whilest booting. So we could get to > 20 crashes/sunday :) I now got a kernel with no IPv6. First abuse that with bge0. But if it is what you think it is, it'll make no difference. Note that I can get annottated traces with param-values and line numbers if I coredump the panics. But dumping core and saving it, takes almost just as long as causing one. --WjW From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 19:52: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 50FF016A4CE for ; Sun, 18 Jul 2004 19:52:56 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE53043D3F for ; Sun, 18 Jul 2004 19:52:55 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6IJqQ4S038177; Sun, 18 Jul 2004 15:52:27 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6IJqQem038174; Sun, 18 Jul 2004 15:52:26 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 18 Jul 2004 15:52:26 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Willem Jan Withagen In-Reply-To: <108901c46cfe$e02ec130$471b3dd4@digiware.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone 0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 19:52:56 -0000 On Sun, 18 Jul 2004, Willem Jan Withagen wrote: > > > Even more reason to do some (ab)using test with the em0 card??? > > > > Yeah, that would be very helpful if you could. > > Well uptill now it was less than 30 minutes to get a crash.... No > counting the ones where it directly crashed whilest booting. > > So we could get to > 20 crashes/sunday :) Now there's a productivity boost :-). > I now got a kernel with no IPv6. First abuse that with bge0. But if it > is what you think it is, it'll make no difference. Yeah, we'll see -- do you have much IPv6 activity on your network? > Note that I can get annottated traces with param-values and line numbers > if I coredump the panics. But dumping core and saving it, takes almost > just as long as causing one. I should probably go read the if_bge code in some more detail, and the TCP code. With IPv6 disabled, we should be able to use stronger inpcb assertions in TCP, which may help diagnose locking problems. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 19:55: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 C38FB16A4CF; Sun, 18 Jul 2004 19:55:04 +0000 (GMT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CB0A43D5A; Sun, 18 Jul 2004 19:55:04 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i6IJt4Wg008719 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 18 Jul 2004 15:55:04 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i6IJsxh0041773; Sun, 18 Jul 2004 15:54:59 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16634.54674.966908.540880@grasshopper.cs.duke.edu> Date: Sun, 18 Jul 2004 15:54:58 -0400 (EDT) To: Doug Rabson In-Reply-To: <200407182039.10773.dfr@nlsystems.com> References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Excellent job on the firewire 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: Sun, 18 Jul 2004 19:55:04 -0000 Doug Rabson writes: > On Sunday 18 July 2004 18:51, Andrew Gallatin wrote: > > Hi, > > > > I just wanted to say that I used FreeBSD's firewire and sbp-II > > support for the first time this weekend. It seems to be fast (over > > 26MB/sec writes, 34MB/sec reads to a LaCie 160GB drive), and robust. > > It works well on non-i386 platforms -- I'm using it to back up an > > amd64, and to serve as a root device for a FreeBSD/powerpc machine. > > > > All in all, it totally exceeded my expectations. Thank you very > > much| > > Wait till you try debugging using gdb over firewire with dcons. An all > round positive experience :-) It would be nice to remove my Comtrol Rocketport serial card, and the 8 serial cables leading across the middle of the room to my shelf of machines and replace it with one firewire cable leading to a firewire hub. But, as a firewire newbie, I have some questions: 1) Is any firewire PCI adapter just as good as any other in terms of performance, and FreeBSD support? (prices seem to range from $10 to $100) 2) Is dcons usable after a panic (ie, DDB or KDB_TRACE)? Or is it only usable for remote-gdb? 3) Is dcons endian and pointer-size agonstic? Can I run consoles to an amd64 and a powerpc box from an x86? 4) Does the loader know about dcons? Eg, can I do "unload boot kernel.test" using dcons? Thanks, Drew From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 20:00: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 7DEFB16A4CE; Sun, 18 Jul 2004 20:00:11 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0C6643D48; Sun, 18 Jul 2004 20:00:10 +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 925E21FF931; Sun, 18 Jul 2004 22:00:08 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id B209F1FF9A6; Sun, 18 Jul 2004 22:00:06 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 2F7AA155DD; Sun, 18 Jul 2004 19:57:10 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 2486B1539E; Sun, 18 Jul 2004 19:57:11 +0000 (UTC) Date: Sun, 18 Jul 2004 19:57:11 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Brian Fundakowski Feldman In-Reply-To: <20040718193513.GV1626@green.homeunix.org> Message-ID: References: <20040718193513.GV1626@green.homeunix.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 mailing list Subject: Re: kldunload if_sk -> LOR & 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: Sun, 18 Jul 2004 20:00:11 -0000 On Sun, 18 Jul 2004, Brian Fundakowski Feldman wrote: > On Sun, Jul 18, 2004 at 03:11:22PM +0000, Bjoern A. Zeeb wrote: > > Hi, > > > > tried to unload if_sk for testing the newly built module with dwhite's > > locking patch (will be loaded after reset now :( ). > > resulted in this on my amd64: > > > > --- cut --- > > noc# kldunload if_sk > > e1000phy0: detached > > miibus0: detached > > lock order reversal > > 1st 0xffffff0030ac7870 skc0 (network driver) @ sys/pci/if_sk.c:2604 > > 2nd 0xffffff0000b91af0 radix node head (radix node head) @ sys/netinet/in_rmx.c:391 > > Stack backtrace: > > witness_checkorder() at witness_checkorder+0x4a6 > > _mtx_lock_flags() at _mtx_lock_flags+0x39 > > in_ifadown() at in_ifadown+0x5b > > in_control() at in_control+0x81c > > if_detach() at if_detach+0x50b > > ether_ifdetach() at ether_ifdetach+0x25 > > sk_detach() at sk_detach+0x6d > > (null)() at 0 > > null_method() at null_method > > At the point where it's actually detaching, once it's detached the methods > that access its softc, it should drop its softc lock before calling the > network-level detach routines. I think this is handled by dwhite's patch so I should be safe now. Perhaps someone could work towards committing a cleaned up version of this patch ? -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 20:05: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 E750316A4CE; Sun, 18 Jul 2004 20:05:10 +0000 (GMT) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 133DE43D45; Sun, 18 Jul 2004 20:05:10 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from ns0.nlsystems.com (ns0.nlsystems.com [80.177.232.243]) by itchy.rabson.org (8.12.11/8.12.11) with ESMTP id i6IK4wPc051041; Sun, 18 Jul 2004 21:04:59 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: Andrew Gallatin Date: Sun, 18 Jul 2004 21:04:53 +0100 User-Agent: KMail/1.6.1 References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> In-Reply-To: <16634.54674.966908.540880@grasshopper.cs.duke.edu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407182104.53221.dfr@nlsystems.com> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on itchy.rabson.org X-Virus-Scanned: clamd / ClamAV version 0.71, clamav-milter version 0.71 X-Virus-Status: Clean cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Excellent job on the firewire 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: Sun, 18 Jul 2004 20:05:11 -0000 On Sunday 18 July 2004 20:54, Andrew Gallatin wrote: > Doug Rabson writes: > > On Sunday 18 July 2004 18:51, Andrew Gallatin wrote: > > > Hi, > > > > > > I just wanted to say that I used FreeBSD's firewire and sbp-II > > > support for the first time this weekend. It seems to be fast > > > (over 26MB/sec writes, 34MB/sec reads to a LaCie 160GB drive), > > > and robust. It works well on non-i386 platforms -- I'm using it > > > to back up an amd64, and to serve as a root device for a > > > FreeBSD/powerpc machine. > > > > > > All in all, it totally exceeded my expectations. Thank you very > > > much| > > > > Wait till you try debugging using gdb over firewire with dcons. An > > all round positive experience :-) > > It would be nice to remove my Comtrol Rocketport serial card, and the > 8 serial cables leading across the middle of the room to my shelf of > machines and replace it with one firewire cable leading to a firewire > hub. But, as a firewire newbie, I have some questions: > > 1) Is any firewire PCI adapter just as good as any other in terms of > performance, and FreeBSD support? (prices seem to range from $10 > to $100) Any should do about as well as any other. I probably wouldn't want to spend more than ~$50 on one. > > 2) Is dcons usable after a panic (ie, DDB or KDB_TRACE)? Or is it > only usable for remote-gdb? Dcons provides two full duplex streams - one for console and one for gdb. You can use DDB on the console just like normal. > > 3) Is dcons endian and pointer-size agonstic? Can I run consoles to > an amd64 and a powerpc box from an x86? I haven't actually tried that and I imagine that there might be issues here and there. Any problems are likely to be in the dconschat program but that should be pretty easy to fix since its entirely userland. > > 4) Does the loader know about dcons? Eg, can I do "unload boot > kernel.test" using dcons? Actually thats the only downside of dcons. It doesn't cut in until the firewire controller attaches. It relies on the fact that the fwohci driver allows access to physical memory from any node on the bus (implemeted in hardware so you can examine the memory of a hung machine). The dconschat program uses this feature to access the dcons ring buffers in the target machine. I could imagine a dcons driver in the loader which just enabled physical access and used some kind of loader trick to hand off the ring buffers to the kernel dcons driver. It doesn't exist though - say nice things to the author and he might find the time for it :-) From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 20:16: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 CE1B316A4CE; Sun, 18 Jul 2004 20:16:38 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id C451943D5A; Sun, 18 Jul 2004 20:16:37 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6IKElsD059560; Sun, 18 Jul 2004 22:14:47 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <10d401c46d02$f8890cf0$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Willem Jan Withagen" , "Robert Watson" Date: Sun, 18 Jul 2004 22:08:07 +0200 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.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone 0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 20:16:38 -0000 > What am I doing to get the panic: > > In one shell I try to compile /usr/ports/net-mgmt/net-snmp. (Well actually the > one I'm working on to get the last tweak out of it when running amd64) > And that I keep repeating until it crashes, but unusally one run is enough. > > In the console I run 'periodic daily', since my box currently always seems to > crash during the night when running daily. > > In a third window I do some work: usually some vi-ing or grepping.... Eh, forgot to mention an essential part: all the processes work on nfs mounted disks.... And without IPv6 it has been alive already longer than with all previous runs today... But to early to make conclusions. I've now started a backup of my home-dir (>2G) over nfs, to create some more stress. --WjW From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 20:28: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 DEE7816A4CE for ; Sun, 18 Jul 2004 20:28:41 +0000 (GMT) Received: from numeri.campus.luth.se (numeri.campus.luth.se [130.240.197.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D0DA43D48 for ; Sun, 18 Jul 2004 20:28:41 +0000 (GMT) (envelope-from k@numeri.campus.luth.se) Received: from numeri.campus.luth.se (localhost [127.0.0.1]) i6IKSa5H097349; Sun, 18 Jul 2004 22:28:36 +0200 (CEST) (envelope-from k@numeri.campus.luth.se) Received: (from k@localhost) by numeri.campus.luth.se (8.12.11/8.12.11/Submit) id i6IKSaU2097348; Sun, 18 Jul 2004 22:28:36 +0200 (CEST) (envelope-from k) Date: Sun, 18 Jul 2004 22:28:36 +0200 From: Johan Karlsson To: "Conrad J. Sabatier" Message-ID: <20040718202835.GA76629@numeri.campus.luth.se> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: Overriding -Werror in buildworld/buildkernel 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, 18 Jul 2004 20:28:42 -0000 On Sun, Jul 18, 2004 at 13:54 (-0500), Conrad J. Sabatier wrote: > OK, I understand the developers' desire to catch errors, but didn't we > at one time have a means of overriding the -Werror flag? I'm seeing a > lot of build failures lately due to warnings, not errors. > > I thought adding WERROR=-Wno-error would do the trick, but it doesn't. Try adding NO_WERROR=1 instead. /Johan K -- Johan Karlsson mailto:johan@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 20:39: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 815F016A4CE; Sun, 18 Jul 2004 20:39:12 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3F8743D5A; Sun, 18 Jul 2004 20:39:10 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6IKbJsD060054; Sun, 18 Jul 2004 22:37:19 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <112001c46d06$1e4e5d20$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Willem Jan Withagen" , "Robert Watson" References: <10d401c46d02$f8890cf0$471b3dd4@digiware.nl> Date: Sun, 18 Jul 2004 22:30:51 +0200 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.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone 0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 20:39:12 -0000 > > What am I doing to get the panic: > > > > In one shell I try to compile /usr/ports/net-mgmt/net-snmp. (Well actually the > > one I'm working on to get the last tweak out of it when running amd64) > > And that I keep repeating until it crashes, but unusally one run is enough. > > > > In the console I run 'periodic daily', since my box currently always seems to > > crash during the night when running daily. > > > > In a third window I do some work: usually some vi-ing or grepping.... > > Eh, forgot to mention an essential part: > all the processes work on nfs mounted disks.... > > And without IPv6 it has been alive already longer than with all previous runs > today... But to early to make conclusions. > I've now started a backup of my home-dir (>2G) over nfs, to create some more > stress. Not the same, but....... I'll run some more no-IPv6, bge, mpsafe=0 Or let me knwo at else... --WjW Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x8:0xffffffff8026fb78 stack pointer = 0x10:0xffffffffb3571af0 frame pointer = 0x10:0xffffffffb3571b20 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 = 43230 (sh) [thread 100207] Stopped at _mtx_lock_flags+0x44: decl %eax db> trace _mtx_lock_flags() at _mtx_lock_flags+0x44 crfree() at crfree+0x2a cred_update_thread() at cred_update_thread+0x70 syscall() at syscall+0x71 Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (74, FreeBSD ELF64, mprotect), rip = 0x20052e138, rsp = 0x7fffffffea 68, rbp = 0x7fffffffebc0 --- db> ps pid proc uarea uid ppid pgrp flag stat wmesg wchan cmd 43239 ffffff0055f05000 ffffffffb348e000 0 43212 796 0004002 [LOCK Giant ffffff005c1f3280] wc 43237 ffffff005b6e0000 ffffffffb33b7000 0 43235 796 0000002 [SLPQ piperd 0xffffff0052f3c2c0][SLP] sh 43236 ffffff005192b000 ffffffffb3538000 0 43212 796 0004002 [LOCK Giant ffffff005c1f3280] tee 43235 ffffff005bb0a5b0 ffffffffb3481000 0 43212 796 0000002 [SLPQ wait 0xffffff005bb0a5b0][SLP] sh 43234 ffffff005bf3ab60 ffffffffb33ac000 0 43212 796 0004002 [LOCK Giant ffffff005c1f3280] uniq 43233 ffffff005c17d5b0 ffffffffb33af000 0 43212 796 0004002 [LOCK Giant ffffff005c1f3280] sort 43231 ffffff005bf3a000 ffffffffb336c000 0 43223 557 0000100 [CPU 1] sendmail 43230 ffffff003259b000 ffffffffb359c000 1000 43220 43230 0004000 [CPU 0] sh 43223 ffffff0050fc7888 ffffffffb3536000 0 557 557 0000100 [SLPQ select 0xffffffff805fc630][SLP] sendmail 43220 ffffff003161d888 ffffffffb35a4000 0 552 552 0000100 [SLPQ select 0xffffffff805fc630][SLP] sendmail 43212 ffffff005f7125b0 ffffffffb3364000 0 43210 796 0000002 [SLPQ wait 0xffffff005f7125b0][SLP] sh 43210 ffffff00515862d8 ffffffffb34d5000 0 802 796 0004002 [SLPQ piperd 0xffffff004d59b840][SLP] sh 43208 ffffff005bb592d8 ffffffffb3368000 0 1 552 0000100 [SLPQ select 0xffffffff805fc630][SLP] sendmail 43189 ffffff005baa6000 ffffffffb3416000 1000 43188 776 0004002 [SLPQ sbwait 0xffffff00613a8da0][SLP] cc1 43188 ffffff00556842d8 ffffffffb348a000 1000 43059 776 0004002 [SLPQ wait 0xffffff00556842d8][SLP] gcc 43059 ffffff005b6e0888 ffffffffb3414000 1000 43058 776 0004002 [SLPQ wait 0xffffff005b6e0888][SLP] sh 43058 ffffff005b2672d8 ffffffffb341c000 1000 41346 776 0004002 [SLPQ wait 0xffffff005b2672d8][SLP] sh 42245 ffffff0051586000 ffffffffb34d4000 0 0 0 0000204 [SLPQ - 0xffffffff80600888][SLP] nfsiod 5 41346 ffffff007b569b60 ffffffffb0f4b000 1000 41345 776 0004002 [SLPQ wait 0xffffff007b569b60][SLP] make 41345 ffffff0050fc75b0 ffffffffb34db000 1000 41311 776 0004002 [SLPQ wait 0xffffff0050fc75b0][SLP] sh 41311 ffffff005bb595b0 ffffffffb3369000 1000 25766 776 0004002 [SLPQ wait 0xffffff005bb595b0][SLP] make 41310 ffffff005bae92d8 ffffffffb3421000 1000 25766 776 0004002 [SLPQ nanslp 0xffffffff805b3d80][SLP] tail 40868 ffffff005c17db60 ffffffffb33b1000 0 0 0 0000204 [SLPQ - 0xffffffff80600880][SLP] nfsiod 4 25766 ffffff005baa6b60 ffffffffb341a000 1000 776 776 0004002 [SLPQ wait 0xffffff005baa6b60][SLP] sh 19867 ffffff005c17d000 ffffffffb33ad000 1000 19840 19840 0004002 [SLPQ nfsrcvlk 0xffffff00610d2004][SLP] zip 19840 ffffff005b267b60 ffffffffb341f000 1000 6862 19840 0004002 [SLPQ wait 0xffffff005b267b60][SLP] sh 6862 ffffff005bae9000 ffffffffb3420000 1000 6861 6862 0004002 [SLPQ pause 0xffffff005bae9070][SLP] tcsh 6861 ffffff005b9c02d8 ffffffffb33b3000 1000 6840 6840 0000100 [SLPQ select 0xffffffff805fc630][SLP] sshd 6840 ffffff005b9c05b0 ffffffffb33b4000 0 546 6840 0000100 [SLPQ sbwait 0xffffff005c554328][SLP] sshd 805 ffffff005fdda888 ffffffffb32fc000 0 803 796 0004002 [SLPQ piperd 0xffffff0062c64580][SLP] mail 803 ffffff0062e10b60 ffffffffb3299000 0 796 796 0000002 [SLPQ wait 0xffffff0062e10b60][SLP] sh 802 ffffff0062e105b0 ffffffffb3297000 0 796 796 0000002 [SLPQ wait 0xffffff0062e105b0][SLP] sh 796 ffffff0062e10000 ffffffffb3295000 0 715 796 0004002 [SLPQ wait 0xffffff0062e10000][SLP] sh 776 ffffff005f42e888 ffffffffb3360000 1000 771 776 0004002 [SLPQ wait 0xffffff005f42e888][SLP] sh 771 ffffff005fb14888 ffffffffb32f7000 1000 770 771 0004002 [SLPQ ttyin 0xffffff007b6a8410][SLP] tcsh 770 ffffff005f42e5b0 ffffffffb335f000 1000 767 767 0000100 [SLPQ select 0xffffffff805fc630][SLP] sshd 767 ffffff007b6d22d8 ffffffffb0cb7000 0 546 767 0000100 [SLPQ sbwait 0xffffff005f8ea970][SLP] sshd 715 ffffff005fb142d8 ffffffffb32f5000 0 701 715 0004002 [SLPQ ttyin 0xffffff00011c5810][SLP] tcsh 714 ffffff005fb145b0 ffffffffb32f6000 0 1 712 0000000 [SLPQ select 0xffffffff805fc630][SLP] xconsole 705 ffffff0062e2d2d8 ffffffffb3291000 0 700 705 0000000 [SLPQ select 0xffffffff805fc630][SLP] xdm 704 ffffff005fdda5b0 ffffffffb32fb000 0 700 704 0004000 [SLPQ select 0xffffffff805fc630][SLP] XFree86 701 ffffff005efa8b60 ffffffffb3302000 0 1 701 0004102 [SLPQ wait 0xffffff005efa8b60][SLP] login 700 ffffff005fddab60 ffffffffb32fd000 0 1 1 0004001 [SLPQ pause 0xffffff005fddabd0][SLP] xdm 699 ffffff005f42e000 ffffffffb335d000 0 1 699 0004002 [SLPQ ttyin 0xffffff007b67ec10][SLP] getty 698 ffffff005f42e2d8 ffffffffb335e000 0 1 698 0004002 [SLPQ ttyin 0xffffff0000cc0410][SLP] getty 697 ffffff005f712888 ffffffffb3365000 0 1 697 0004002 [SLPQ ttyin 0xffffff007b5ddc10][SLP] getty 696 ffffff005fdda2d8 ffffffffb32fa000 0 1 696 0004002 [SLPQ ttyin 0xffffff007b659c10][SLP] getty 695 ffffff007b6d2888 ffffffffb0cb9000 0 1 695 0004002 [SLPQ ttyin 0xffffff007b67f410][SLP] getty 694 ffffff005efa82d8 ffffffffb32ff000 0 1 694 0004002 [SLPQ ttyin 0xffffff007b5dd010][SLP] getty 693 ffffff005efa8000 ffffffffb32fe000 0 1 693 0004002 [SLPQ ttyin 0xffffff007b67e810][SLP] getty 692 ffffff005f712000 ffffffffb3362000 0 1 692 0004002 [SLPQ ttyin 0xffffff0000cf0c10][SLP] getty 682 ffffff005efa85b0 ffffffffb3300000 0 1 682 0000000 [SLPQ select 0xffffffff805fc630][SLP] inetd 634 ffffff007b569888 ffffffffb0f4a000 0 1 631 0000000 [SLPQ select 0xffffffff805fc630][SLP] snmpd 616 ffffff005f42eb60 ffffffffb3361000 0 1 616 0000100 [SLPQ select 0xffffffff805fc630][SLP] lpd 592 ffffff005fb14b60 ffffffffb32f8000 0 1 592 0000000 [SLPQ nanslp 0xffffffff805b3d80][SLP] cron 571 ffffff005efa8888 ffffffffb3301000 25 1 571 0000100 [SLPQ pause 0xffffff005efa88f8][SLP] sendmail 557 ffffff005f7122d8 ffffffffb3363000 0 1 557 0000100 [SLPQ pause 0xffffff005f712348][SLP] sendmail 552 ffffff0062e10888 ffffffffb3298000 0 1 552 0000100 [SLPQ select 0xffffffff805fc630][SLP] sendmail 546 ffffff005f712b60 ffffffffb3366000 0 1 546 0000100 [SLPQ select 0xffffffff805fc630][SLP] sshd 537 ffffff005fb14000 ffffffffb329a000 1 1 537 0000100 [SLPQ sbwait 0xffffff005fe92970][SLP] rwhod 496 ffffff005fdda000 ffffffffb32f9000 0 1 496 0000000 [SLPQ select 0xffffffff805fc630][SLP] usbd 494 ffffff0062e6cb60 ffffffffb3253000 0 1 494 0000000 [SLPQ select 0xffffffff805fc630][SLP] moused 464 ffffff0062e6c000 ffffffffb324f000 0 460 460 0000000 [SLPQ - 0xffffff00014cc200][SLP] nfsd 463 ffffff0062e2d000 ffffffffb3254000 0 460 460 0000000 [SLPQ - 0xffffff005fca5800][SLP] nfsd 462 ffffff0062e2d5b0 ffffffffb3292000 0 460 460 0000000 [SLPQ - 0xffffff00014cc000][SLP] nfsd 461 ffffff0062e6c5b0 ffffffffb3251000 0 460 460 0000000 [SLPQ - 0xffffff005fca5a00][SLP] nfsd 460 ffffff007b6d25b0 ffffffffb0cb8000 0 1 460 0000000 [SLPQ accept 0xffffff005fe9248e][SLP] nfsd 458 ffffff0062e6c2d8 ffffffffb3250000 0 1 458 0000000 [SLPQ select 0xffffffff805fc630][SLP] mountd 436 ffffff0062e6c888 ffffffffb3252000 0 1 436 0000000 [SLPQ select 0xffffffff805fc630][SLP] rpcbind 327 ffffff0062e2d888 ffffffffb3293000 0 1 327 0000000 [SLPQ select 0xffffffff805fc630][SLP] syslogd 60 ffffff007b6d2b60 ffffffffb0cba000 0 0 0 0000204 [SLPQ - 0xffffffff80600878][SLP] nfsiod 3 59 ffffff007b405000 ffffffffb0f06000 0 0 0 0000204 [SLPQ - 0xffffffff80600870][SLP] nfsiod 2 58 ffffff007b4052d8 ffffffffb0f07000 0 0 0 0000204 [SLPQ - 0xffffffff80600868][SLP] nfsiod 1 57 ffffff007b4055b0 ffffffffb0f08000 0 0 0 0000204 [SLPQ - 0xffffffff80600860][SLP] nfsiod 0 56 ffffff007b405888 ffffffffb0f45000 0 0 0 0000204 [SLPQ syncer 0xffffffff805b3a80][SLP] syncer 55 ffffff007b405b60 ffffffffb0f46000 0 0 0 0000204 [SLPQ vlruwt 0xffffff007b405b60][SLP] vnlru 54 ffffff007b569000 ffffffffb0f47000 0 0 0 0000204 [SLPQ psleep 0xffffffff805fcf5c][SLP] bufdaemon 53 ffffff007b5692d8 ffffffffb0f48000 0 0 0 000020c [SLPQ pgzero 0xffffffff80609228][SLP] pagezero 52 ffffff007b5695b0 ffffffffb0f49000 0 0 0 0000204 [SLPQ psleep 0xffffffff80609294][SLP] vmdaemon 9 ffffff007b68d000 ffffffffb0c70000 0 0 0 0000204 [SLPQ psleep 0xffffffff80609244][SLP] pagedaemon 51 ffffff007b68d2d8 ffffffffb0c71000 0 0 0 0000204 [IWAIT] swi0: sio 50 ffffff007b68d5b0 ffffffffb0c72000 0 0 0 0000204 [SLPQ usbevt 0xffffffff8082c420][SLP] usb2 49 ffffff007b68d888 ffffffffb0c73000 0 0 0 0000204 [SLPQ usbevt 0xffffffff8082a420][SLP] usb1 48 ffffff007b68db60 ffffffffb0c74000 0 0 0 0000204 [SLPQ usbtsk 0xffffffff805a7290][SLP] usbtask 47 ffffff007b64f000 ffffffffb0c75000 0 0 0 0000204 [SLPQ usbevt 0xffffffff80828420][SLP] usb0 46 ffffff007b64f2d8 ffffffffb0cb2000 0 0 0 0000204 [SLPQ tzpoll 0xffffffff805a4a18][SLP] acpi_thermal 8 ffffff007b64f5b0 ffffffffb0cb3000 0 0 0 0000204 [SLPQ actask 0xffffffff805a4a80][SLP] acpi_task2 7 ffffff007b64f888 ffffffffb0cb4000 0 0 0 0000204 [SLPQ actask 0xffffffff805a4a80][SLP] acpi_task1 6 ffffff007b64fb60 ffffffffb0cb5000 0 0 0 0000204 [SLPQ actask 0xffffffff805a4a80][SLP] acpi_task0 45 ffffff007b6d2000 ffffffffb0cb6000 0 0 0 0000204 [IWAIT] swi3: cambio 44 ffffff007b6cb000 ffffffffb0c2a000 0 0 0 0000204 [IWAIT] swi2: camnet 43 ffffff007b6cb2d8 ffffffffb0c2b000 0 0 0 0000204 [IWAIT] swi6: acpitaskq 42 ffffff007b6cb5b0 ffffffffb0c2c000 0 0 0 0000204 [IWAIT] swi6:+ 5 ffffff007b6cb888 ffffffffb0c2d000 0 0 0 0000204 [SLPQ - 0xffffff00009a8d00][SLP] taskqueue 41 ffffff007b6cbb60 ffffffffb0c2e000 0 0 0 0000204 [IWAIT] swi6:+ 40 ffffff007b66f000 ffffffffb0c6b000 0 0 0 0000204 [IWAIT] swi6: task queue 39 ffffff007b66f2d8 ffffffffb0c6c000 0 0 0 0000204 [SLPQ - 0xffffffff805a4fe0][SLP] yarrow 4 ffffff007b66f5b0 ffffffffb0c6d000 0 0 0 0000204 [SLPQ - 0xffffffff805aaf08][SLP] g_down 3 ffffff007b66f888 ffffffffb0c6e000 0 0 0 0000204 [SLPQ - 0xffffffff805aaf00][SLP] g_up 2 ffffff007b66fb60 ffffffffb0c6f000 0 0 0 0000204 [SLPQ - 0xffffffff805aaef0][SLP] g_event 38 ffffff007b6d02d8 ffffffffb0be5000 0 0 0 0000204 [IWAIT] swi1: net 37 ffffff007b6d05b0 ffffffffb0be6000 0 0 0 0000204 [IWAIT] swi4: vm 36 ffffff007b6d0888 ffffffffb0be7000 0 0 0 000020c [IWAIT] swi5: clock sio 35 ffffff007b6d0b60 ffffffffb0be8000 0 0 0 0000204 [IWAIT] irq23: 34 ffffff007b6df000 ffffffffb0c25000 0 0 0 0000204 [IWAIT] irq22: 33 ffffff007b6df2d8 ffffffffb0c26000 0 0 0 0000204 [IWAIT] irq21: uhci0 uhci1+ 32 ffffff007b6df5b0 ffffffffb0c27000 0 0 0 0000204 [IWAIT] irq20: 31 ffffff007b6df888 ffffffffb0c28000 0 0 0 0000204 [IWAIT] irq19: em0 30 ffffff007b6dfb60 ffffffffb0c29000 0 0 0 0000204 [IWAIT] irq18: 29 ffffff007b6c6888 ffffffffb0bbf000 0 0 0 0000204 [IWAIT] irq17: 28 ffffff007b6c6b60 ffffffffb0bc0000 0 0 0 0000204 [IWAIT] irq16: bge0 27 ffffff007b68e000 ffffffffb0bc1000 0 0 0 0000204 [IWAIT] irq15: ata1 26 ffffff007b68e2d8 ffffffffb0be0000 0 0 0 0000204 [IWAIT] irq14: ata0 25 ffffff007b68e5b0 ffffffffb0be1000 0 0 0 0000204 [IWAIT] irq13: 24 ffffff007b68e888 ffffffffb0be2000 0 0 0 0000204 [IWAIT] irq12: 23 ffffff007b68eb60 ffffffffb0be3000 0 0 0 0000204 [IWAIT] irq11: 22 ffffff007b6d0000 ffffffffb0be4000 0 0 0 0000204 [IWAIT] irq10: 21 ffffff007b7172d8 ffffffffb0b9a000 0 0 0 0000204 [IWAIT] irq9: acpi0 20 ffffff007b7175b0 ffffffffb0b9b000 0 0 0 0000204 [IWAIT] irq8: rtc 19 ffffff007b717888 ffffffffb0bba000 0 0 0 0000204 [IWAIT] irq7: ppc0 18 ffffff007b717b60 ffffffffb0bbb000 0 0 0 0000204 [IWAIT] irq6: fdc0 17 ffffff007b6c6000 ffffffffb0bbc000 0 0 0 0000204 [IWAIT] irq5: 16 ffffff007b6c62d8 ffffffffb0bbd000 0 0 0 0000204 [IWAIT] irq4: sio0 15 ffffff007b6c65b0 ffffffffb0bbe000 0 0 0 0000204 [IWAIT] irq3: sio1 14 ffffff007b6ad000 ffffffffb0b58000 0 0 0 0000204 [IWAIT] irq0: clk 13 ffffff007b6ad2d8 ffffffffb0b95000 0 0 0 0000204 [IWAIT] irq1: atkbd0 12 ffffff007b6ad5b0 ffffffffb0b96000 0 0 0 000020c [Can run] idle: cpu0 11 ffffff007b6ad888 ffffffffb0b97000 0 0 0 000020c [Can run] idle: cpu1 1 ffffff007b6adb60 ffffffffb0b98000 0 0 1 0004200 [SLPQ wait 0xffffff007b6adb60][SLP] init 10 ffffff007b717000 ffffffffb0b99000 0 0 0 0000204 [SLPQ ktrace 0xffffffff805b06f0][SLP] ktrace 0 ffffffff805ab080 ffffffff806e6000 0 0 0 0000200 [SLPQ sched 0xffffffff805ab080][SLP] swapper From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 21:09: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 06CBD16A4CE for ; Sun, 18 Jul 2004 21:09:13 +0000 (GMT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9371E43D1F for ; Sun, 18 Jul 2004 21:09:12 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) i6IL9Bds010036; Sun, 18 Jul 2004 14:09:11 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.9p2/8.12.9/Submit) id i6IL99Ea010033; Sun, 18 Jul 2004 14:09:09 -0700 (PDT) (envelope-from dillon) Date: Sun, 18 Jul 2004 14:09:09 -0700 (PDT) From: Matthew Dillon Message-Id: <200407182109.i6IL99Ea010033@apollo.backplane.com> To: Matthias Buelow , Scott Long References: <200407180146.i6I1kiQ9004838@apollo.backplane.com> <40F9E518.9050800@mukappabeta.de> cc: current@freebsd.org Subject: Re: panic: APIC: Previous IPI is stuck 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, 18 Jul 2004 21:09:13 -0000 :Scott Long wrote: : :> The 'fix the bugs' discussions are going on too. However, this is the :> freebsd-current list, and it's always nice to discuss things that might :> be suitable further down the road. : :Yes, I might have gotten this wrong, I thought he was talking :specifically about 5.x (which to me, and I guess many other users, means :the long awaited stabilization of the 5.x tree). : :-- : Matthias Buelow; mkb@{mukappabeta,informatik.uni-wuerzburg}.de I am using "-current" and "5.x" interchangably, since there isn't really much of a distinction between the two, at least not from my point of view. As far as stabilization goes... well, the problem is that you can only stabilize what you have once you have it. The APIs, abstractions, and requirements are so complex in -current/5.x that every time someone codes up something new, major bugs are introduced. Even worse, many of the bugs introduced are difficult to reproduce, track down, and fix. Of course, new bugs are introduced occurs with any OS development... DragonFly is no exception. But there are 'normal occurances' of such things, and then you have the 'its so fragging complex that I couldn't code it right the first time if I tried!'. -current/5.x is definitely in the latter category. The question you have to ask yourself is: Do you want to spend all your time tracking down all the bugs that are constantly being introduced into the codebase, or do you want to simplify your APIs and abstractions to *reduce* the instances of new bugs being introduced so you can spend more of your time implementing neat new things instead? Another question you have to ask yourself is: If you have a kernel whos APIs and abstractions are so complex that even veteran kernel hackers are having to test in perforce for weeks, months, or even longer before daring to bring the code into CVS, and even then wind up with serious bugs, what do you think the situation is going to be for all the other developers out there trying to work on the FreeBSD kernel? I'm not going to repeat all the suggestions I've made in the past. It is obvious to me that FreeBSD development needs to stop *right* *now*, take a step back, and figure out how to simplify the MP requirements for all the major subsystems... then spend 3 months doing it. IPIs are a good example... it needs a complete rewrite. The scheduler pretty much needs a complete rewrite. The memory subsystem is in pretty good shape but would work even better using a DragonFly style cpu localization model. The interrupt subsystem... well, again, you need DFly style preemption instead of heavy-weight-scheduler-integrated-with-priority-borrowing- preemptive-thread-switching-and-preemptive-cpu-migrative-and-oh-yah-don't- forget-to-pin-the-cpu-because-if-you-do-we-will-never-find-the-bugs- you-introduce-otherwise style preemption. -Matt From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 21:14: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 E769316A4CE for ; Sun, 18 Jul 2004 21:14:41 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id F031043D1F for ; Sun, 18 Jul 2004 21:14:40 +0000 (GMT) (envelope-from andreas.kohn@gmx.net) Received: (qmail 23416 invoked by uid 65534); 18 Jul 2004 21:14:39 -0000 Received: from unknown (EHLO [212.204.44.203]) (212.204.44.203) by mail.gmx.net (mp016) with SMTP; 18 Jul 2004 23:14:39 +0200 X-Authenticated: #2431876 From: Andreas Kohn To: Sebastian Foss In-Reply-To: <005d01c46cb6$bb1ffd20$0100a8c0@LEVELONE> References: <005d01c46cb6$bb1ffd20$0100a8c0@LEVELONE> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Up6UZgeEFiimJc4VWnOT" Message-Id: <1090185278.739.10.camel@klamath.syndrom23.de> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 18 Jul 2004 23:14:38 +0200 cc: freebsd-current@freebsd.org Subject: Re: xfce4 help 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, 18 Jul 2004 21:14:42 -0000 --=-Up6UZgeEFiimJc4VWnOT Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2004-07-18 at 13:02, Sebastian Foss wrote: > Hi! >=20 > I know this may be a little O.T. but im quite desperate... > Maybe someone can help me to find this original desktop wallpaper for=20 > freebsd because i like it so much: > http://xfce.org/images/screenshots/jimmiejaz_26122003.jpg >=20 > Thank you very much for any help! >=20 > Sebastian=20 >=20 http://www.rbreb13.com/Pictures/Pictures_1/Pictures_2/Pictures_3/Pictures_4= /pictures_4.html HTH, Andreas --=-Up6UZgeEFiimJc4VWnOT Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA+ug9Yucd7Ow1ygwRAqXzAJ9e+M/6bPUStIxz9+6z+Y253arLlwCeKS3+ 1PesN4EKmGGYEsdoJk9mnag= =ZeZQ -----END PGP SIGNATURE----- --=-Up6UZgeEFiimJc4VWnOT-- From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 22:41: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 2FB6716A4CF for ; Sun, 18 Jul 2004 22:41:08 +0000 (GMT) Received: from mx.x123.info (165.Red-80-37-224.pooles.rima-tde.net [80.37.224.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D2AB43D31 for ; Sun, 18 Jul 2004 22:41:07 +0000 (GMT) (envelope-from esn@x123.info) Received: by mx.x123.info (Postfix, from userid 80) id D83EC17129; Mon, 19 Jul 2004 00:41:03 +0200 (CEST) Received: from 192.168.1.2 ([192.168.1.2]) by www.x123.info (Horde) with HTTP for ; Mon, 19 Jul 2004 00:41:03 +0200 Message-ID: <20040719004103.0og80ookwwsw4gcs@www.x123.info> X-Priority: 3 (Normal) Date: Mon, 19 Jul 2004 00:41:03 +0200 From: "Sebastian Yepes F. [ESN]" To: Mark Santcroos References: <20040715072915.GA10858@laptop.6bone.nl> In-Reply-To: <20040715072915.GA10858@laptop.6bone.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs cc: freebsd-current@freebsd.org Subject: Re: acpi_video users needed 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, 18 Jul 2004 22:41:08 -0000 Here is my files.. it's from my Dell Inspiron 8500 http://www.x123.info/acpiv/acpidump http://www.x123.info/acpiv/devinfo http://www.x123.info/acpiv/dmesg ----- Message from marks@ripe.net --------- Date: Thu, 15 Jul 2004 09:29:15 +0200 From: Mark Santcroos Reply-To: Mark Santcroos Subject: acpi_video users needed To: freebsd-current@freebsd.org > Can some people with a properly attaching acpi_video.ko send me his/her: > > * dmesg (boot_verbose preferred) > * acpidump -dt > * devinfo -v > > Thanks! > > Mark > _______________________________________________ > 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" ----- End message from marks@ripe.net ----- -- if (Better You Treat Them) { return "Worst You Get Treated"; } Love can kill you like a Hammer or a 220 Kv AC line in the head, but it's the most beautiful and strange sensation, I Just Love, Love ; ) /* www: http://www.x123.info Contect: FingerPrint: esn aT x123.info 0D42 F870 F650 6B86 CA9E esn aT freshpkgsrc.org E199 A57D 3824 F8AA A934 sebastian.yepes aT hp.com */ From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 23: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 48DFF16A4CE; Sun, 18 Jul 2004 23:06:47 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24D2843D3F; Sun, 18 Jul 2004 23:06:46 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6IN4wsD062878; Mon, 19 Jul 2004 01:04:59 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <115601c46d1a$bf9f4540$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Robert Watson" References: Date: Mon, 19 Jul 2004 00:58:32 +0200 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.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone0xffffff007fed4780(Mbuf) 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, 18 Jul 2004 23:06:47 -0000 From: "Robert Watson" > On Sun, 18 Jul 2004, Willem Jan Withagen wrote: > > > > Three stikes and out.... > > > I'll disable mpsafe now.... > > > > Does not seem to help.... Not shure if anything should be read in the > > fact that it is 3 times in [thread 100007]. > > Well, the threads involved seem to be the netisr thread and the bge > interrupt thread, suggesting we have a problem with mbufs being free'd > despite being handed off into the network stack. Up front, it suggests > maybe we have an issue with the bge driver freeing or reusing an mbuf > inappropriately, or perhaps it's at the TCP layer. Just as I was writing: ================ I would dare to declare the current running config stable, but it is up for more than 2,5 hours. While taking the abuse that normaly would bring the system on its knees within 30 minutes... I'm now running: bge0 interface No IPv6 debug.mpsafe=0 Which would lead me to believe problems in the IPv6 layer (with bge0?). ================ It got negated by: panic: lock (sleep mutex) UMA pcpu not locked @ /home2 /src/sys/vm/uma_core.c:1654 cpuid = 1; KDB: stack backtrace: kdb_backtrace() at kdb_backtrace+0x34 panic() at panic+0x1d2 witness_unlock() at witness_unlock+0xdd _mtx_unlock_flags() at _mtx_unlock_flags+0x68 uma_zalloc_arg() at uma_zalloc_arg+0x14e tcp_output() at tcp_output+0xce9 tcp_input() at tcp_input+0x27f5 ip_input() at ip_input+0x94c netisr_processqueue() at netisr_processqueue+0x8c swi_net() at swi_net+0xaf ithread_loop() at ithread_loop+0x18d fork_exit() at fork_exit+0xc9 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffb0bb9d00, rbp = 0 --- KDB: enter: panic [thread 100017] Stopped at kdb_enter+0x2e: nop I'll starts some more tests before I'm of to bed. --WjW From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 23: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 B3FEE16A4CE for ; Sun, 18 Jul 2004 23:13:47 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id C995943D3F for ; Sun, 18 Jul 2004 23:13:46 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id 5518FACADB; Mon, 19 Jul 2004 01:13:45 +0200 (CEST) Date: Mon, 19 Jul 2004 01:13:45 +0200 From: Pawel Jakub Dawidek To: freebsd-current@freebsd.org Message-ID: <20040718231345.GE57678@darkness.comp.waw.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Rgf3q3z9SdmXC6oT" Content-Disposition: inline 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 Subject: ADAPTIVE_MUTEXES 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: Sun, 18 Jul 2004 23:13:47 -0000 --Rgf3q3z9SdmXC6oT Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi. Here is copied by hand backtrace from panic on boot: panic: Assertion ts !=3D NULL failed at /usr/src/sys/kern/kern_mutex.c:646 db> tr panic() _mtx_unlock_sleep()+0x58 _mtx_unlock_flags()+0x94 slab_zalloc()+0x2b uma_zone_slab()+0x2b uma_zalloc_bucket()+0x124 uma_zalloc_arg()+0x25f malloc()+0xb2 eventhandler_register()+0x16c vnlru_proc()+0x43 fork_exit() fork_trampoline() Dmesg and kernel config below. BTW. I'm able to reproduce it with 4BSD scheduler as well. =3D=3D=3D> 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.2-CURRENT #5: Sun Jul 18 14:35:10 CEST 2004 root@slayer.hell.invalid:/usr/obj/usr/src/sys/RAGE WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (534.55-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x665 Stepping =3D 5 Features=3D0x183fbff real memory =3D 67108864 (64 MB) avail memory =3D 60248064 (57 MB) MPTable: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Assuming intbase of 0 ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 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 0xf000-0xf00f,0x376,0x170-0x1= 77,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at device 7.2 (no driver attached) piix0: port 0x5000-0x500f at device 7.3 on pci0 Timecounter "PIIX" frequency 3579545 Hz quality 0 atapci1: port 0xc400-0xc43f,0xc000-0xc= 003,0xbc00-0xbc07,0xb800-0xb803,0xb400-0xb407 mem 0xd8200000-0xd821ffff irq= 19 at device 9.0 on pci0 ata2: at 0xb400 on atapci1 ata3: at 0xbc00 on atapci1 fxp0: port 0xc800-0xc83f mem 0xd8000000-0xd8= 0fffff,0xd8221000-0xd8221fff irq 18 at device 11.0 on pci0 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:d0:b7:25:86:ee fxp0: [GIANT-LOCKED] fxp1: port 0xcc00-0xcc3f mem 0xd8100000-0xd8= 1fffff,0xd8220000-0xd8220fff irq 17 at device 13.0 on pci0 miibus1: on fxp1 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: Ethernet address: 00:03:47:af:3a:0b fxp1: [GIANT-LOCKED] tl0: port 0xd000-0xd00f irq 16 at device 15.= 0 on pci0 miibus2: on tl0 mlphy0: on miibus2 mlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto tlphy0: on miibus2 tlphy0: 10base2/BNC, 10base5/AUI tl0: [GIANT-LOCKED] atapci2: port 0xdc00-0xdcff,0xd800-0xd= 803,0xd400-0xd407 irq 18 at device 19.0 on pci0 ata4: at 0xd400 on atapci2 atapci3: port 0xe800-0xe8ff,0xe400-0xe= 403,0xe000-0xe007 irq 18 at device 19.1 on pci0 ata5: at 0xe000 on atapci3 cpu0 on motherboard cpu1 on motherboard orm0: at iomem 0xef000-0xeffff,0xcc000-0xccfff,0xca000-0x= cb7ff,0xc0000-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: at port 0x3f7= ,0x3f0-0x3f5 irq 6 drq 2 on isa0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (port) unknown: can't assign resources (memory) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounters tick every 10.000 msec ad4: 1033MB [2100/16/63] at ata2-master WDMA2 ad5: 1033MB [2100/16/63] at ata2-slave WDMA2 ad8: 19092MB [38792/16/63] at ata4-master UDMA66 SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ad8s1a =3D=3D=3D> Kernel config: machine i386 cpu I486_CPU cpu I586_CPU cpu I686_CPU ident RAGE maxusers 0 #To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" #Default places to look for devices. makeoptions DEBUG=3D-g #Build kernel with gdb(1) debug symbols options SCHED_ULE #ULE scheduler options INET #InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_ACL #Support for access control lists options UFS_DIRHASH #Improve performance on big directories options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 #Compatible with FreeBSD4 options SCSI_DELAY=3D15000 #Delay (in ms) before probing SCSI options KTRACE #ktrace(1) support #options SYSVSHM #SYSV-style shared memory #options SYSVMSG #SYSV-style message queues #options SYSVSEM #SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. # Debugging for use in -current options KDB # Enable kernel debugger support. options DDB # Enable the kernel debugger options INVARIANTS # Enable calls of extra sanity checking options INVARIANT_SUPPORT # Extra sanity checks of internal structures, re= quired by INVARIANTS options WITNESS # Enable checks to detect deadlocks and cycles options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel device apic device isa #device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc # Floating point support - do not disable. device npx # Add suspend/resume support for the i8254. device pmtimer # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) # Pseudo devices - the number indicates how many units to allocate. device random # Entropy device device loop # Network loopback device ether # Ethernet support device pty # Pseudo-ttys (telnet etc) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter options MAC --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --Rgf3q3z9SdmXC6oT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA+wQpForvXbEpPzQRArjNAKCmu6GIAMSQFb8x6QGH7vqp19KztwCfcrux k73rVZigQdbbiYSUYhtsF6k= =j8NA -----END PGP SIGNATURE----- --Rgf3q3z9SdmXC6oT-- From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 23:25: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 36E0E16A4CE; Sun, 18 Jul 2004 23:25:05 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id E034C43D55; Sun, 18 Jul 2004 23:25:04 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id A6830ACAFB; Mon, 19 Jul 2004 01:25:03 +0200 (CEST) Date: Mon, 19 Jul 2004 01:25:03 +0200 From: Pawel Jakub Dawidek To: freebsd-current@freebsd.org Message-ID: <20040718232503.GF57678@darkness.comp.waw.pl> References: <20040718231345.GE57678@darkness.comp.waw.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1Y7d0dPL928TPQbc" Content-Disposition: inline In-Reply-To: <20040718231345.GE57678@darkness.comp.waw.pl> 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: scottl@freebsd.org Subject: Re: ADAPTIVE_MUTEXES 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: Sun, 18 Jul 2004 23:25:05 -0000 --1Y7d0dPL928TPQbc Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 19, 2004 at 01:13:45AM +0200, Pawel Jakub Dawidek wrote: +> Hi. +>=20 +> Here is copied by hand backtrace from panic on boot: +>=20 +> panic: Assertion ts !=3D NULL failed at /usr/src/sys/kern/kern_mutex.c:6= 46 [...] Ok, the problem was one ADAPTIVE_MUTEXES -> NO_ADAPTIVE_MUTEXES change missing. Fix committed. --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --1Y7d0dPL928TPQbc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA+wbPForvXbEpPzQRAiuHAKDW5sNd+ma8++Gp1CeX9QpZXR2deQCgvOLN x01ppR6RSAaMz7FX4XvpUuM= =9Dgo -----END PGP SIGNATURE----- --1Y7d0dPL928TPQbc-- From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 00:04: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 181BD16A4CE for ; Mon, 19 Jul 2004 00:04:46 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4A7743D58 for ; Mon, 19 Jul 2004 00:04:44 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 417F17A4B0; Sun, 18 Jul 2004 17:04:44 -0700 (PDT) Message-ID: <40FB101B.2010807@elischer.org> Date: Sun, 18 Jul 2004 17:04:43 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Matthew Dillon References: <200407180146.i6I1kiQ9004838@apollo.backplane.com> <40F9E518.9050800@mukappabeta.de> <200407182109.i6IL99Ea010033@apollo.backplane.com> In-Reply-To: <200407182109.i6IL99Ea010033@apollo.backplane.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Matthias Buelow cc: current@freebsd.org Subject: Re: panic: APIC: Previous IPI is stuck 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, 19 Jul 2004 00:04:46 -0000 Matthew Dillon wrote: >:Scott Long wrote: >: >:> The 'fix the bugs' discussions are going on too. However, this is the >:> freebsd-current list, and it's always nice to discuss things that might >:> be suitable further down the road. >: >:Yes, I might have gotten this wrong, I thought he was talking >:specifically about 5.x (which to me, and I guess many other users, means >:the long awaited stabilization of the 5.x tree). >: >:-- >: Matthias Buelow; mkb@{mukappabeta,informatik.uni-wuerzburg}.de > > I am using "-current" and "5.x" interchangably, since there isn't really > much of a distinction between the two, at least not from my point of > view. > > As far as stabilization goes... well, the problem is that you can only > stabilize what you have once you have it. The APIs, abstractions, and > requirements are so complex in -current/5.x that every time someone > codes up something new, major bugs are introduced. Even worse, many of > the bugs introduced are difficult to reproduce, track down, and fix. Of > course, new bugs are introduced occurs with any OS development... DragonFly > is no exception. But there are 'normal occurances' of such things, and > then you have the 'its so fragging complex that I couldn't code it right > the first time if I tried!'. -current/5.x is definitely in the latter > category. > > The question you have to ask yourself is: Do you want to spend all your > time tracking down all the bugs that are constantly being introduced into > the codebase, or do you want to simplify your APIs and abstractions to > *reduce* the instances of new bugs being introduced so you can spend more > of your time implementing neat new things instead? > I certianly agree about a lot of this and I'm as guilty as the rest of adding stuff. (I'm now trying to clean some of it up but it's hard after other people entwine your own mistakes into their code. :-) The IPI code is a very likely candidate for merging sooner than later. I tried to add code to allow setrunnable (and friends) to immediatly kick an idle thread (in hlt) to come and get the newly scheduled thread but it wasn't to easy as teh IPI code was not all that general. I haven't looked at Matthew's IPI code (nor ours), since it was written but at that time it seemed to be a pretty straight forward 'drop in' replacement. (not too surprising really). Who IS "Mr IPI"? That's the problem with the system at teh moment... you have to know who "Mr ${module}" is for any given "Module" because there is such a high level of domain knwledge needed for each subsystem. I'm presuming it's jhb with assistance from peter, but I'm not sure.. It's be nice to know what is required to "drop in" teh new IPI code. Then I could retry adding teh code to kickstart idle cpus when work becomes available instead of waiting for the next tick for them to notice.. Drew recently saw a 10-20% increase in throughput by going to not using 'hlt" in idle CPUs on a threaded application. (which itself slows down some things so the real improvement might have been more) So there is really some gain to be had. It''s been in DF for a year now so it's not "untried" code. > > Another question you have to ask yourself is: If you have a kernel whos > APIs and abstractions are so complex that even veteran kernel hackers > are having to test in perforce for weeks, months, or even longer before > daring to bring the code into CVS, and even then wind up with serious bugs, > what do you think the situation is going to be for all the other developers > out there trying to work on the FreeBSD kernel? > > I'm not going to repeat all the suggestions I've made in the past. It is > obvious to me that FreeBSD development needs to stop *right* *now*, take > a step back, and figure out how to simplify the MP requirements for > all the major subsystems... then spend 3 months doing it. IPIs are a good > example... it needs a complete rewrite. The scheduler pretty much needs > a complete rewrite. The memory subsystem is in pretty good shape but > would work even better using a DragonFly style cpu localization model. > The interrupt subsystem... well, again, you need DFly style preemption > instead of heavy-weight-scheduler-integrated-with-priority-borrowing- > preemptive-thread-switching-and-preemptive-cpu-migrative-and-oh-yah-don't- > forget-to-pin-the-cpu-because-if-you-do-we-will-never-find-the-bugs- > you-introduce-otherwise style preemption. > > -Matt > >_______________________________________________ >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 Jul 19 00:43: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 84F1416A4CE for ; Mon, 19 Jul 2004 00:43:51 +0000 (GMT) Received: from av7-2-sn1.fre.skanova.net (av7-2-sn1.fre.skanova.net [81.228.11.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C18743D31 for ; Mon, 19 Jul 2004 00:43:50 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av7-2-sn1.fre.skanova.net (Postfix, from userid 502) id E174637EC4; Mon, 19 Jul 2004 02:43:49 +0200 (CEST) Received: from smtp3-1-sn1.fre.skanova.net (smtp3-1-sn1.fre.skanova.net [81.228.11.163]) by av7-2-sn1.fre.skanova.net (Postfix) with ESMTP id CE98E37E44 for ; Mon, 19 Jul 2004 02:43:49 +0200 (CEST) Received: from gadget (h130n1fls11o822.telia.com [213.64.66.130]) by smtp3-1-sn1.fre.skanova.net (Postfix) with ESMTP id 8C88537E46 for ; Mon, 19 Jul 2004 02:43:49 +0200 (CEST) From: "Daniel Eriksson" To: Date: Mon, 19 Jul 2004 02:43:52 +0200 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_001B_01C46D3A.3DA99070" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal Subject: Kernel preemption leads to SATA instability (how to debug?) 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, 19 Jul 2004 00:43:51 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_001B_01C46D3A.3DA99070 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I'm getting SATA instability on my system with kernel preemption enabled. When accessing the SATA discs at the same time as other discs = (for example during a fsck of all file systems on the machine) it only takes = a few seconds for the SATA discs to start reporting things like this: Interrupt storm detected on "irq20: atapci4"; throttling interrupt = source ad20: FAILURE - already active DMA on this device ad20: setting up DMA failed This is on a recent kernel (2004.07.18.05.00.00), but it's been like = this ever since the kernel preemption stuff was turned on again a few weeks = ago. With preemption disabled (by editing param.h) the system seems to be = stable, but somewhat sluggish (a simple bzip2 compress operation can generate a = load average of 10+). How would I go about debugging this? Any hints would be appreciated. I = do have KDB/DDB and debug symbols compiled in, but the machine is a = production machine so I cannot afford long debugging sessions unfortunately. Attached is the dmesg.boot and kernel config file. Below are some = settings that might be interesting from other files: /etc/sysctl.conf ---------------- kern.ipc.maxsockbuf=3D524288 kern.ipc.somaxconn=3D1024 kern.maxfiles=3D16384 kern.polling.enable=3D1 kern.polling.idle_poll=3D0 kern.polling.burst_max=3D200 kern.polling.each_burst=3D25 kern.polling.poll_in_trap=3D1 net.inet.tcp.sendspace=3D262144 net.inet.tcp.recvspace=3D262144 net.inet.tcp.rfc3390=3D1 net.inet.tcp.inflight_enable=3D1 net.inet.tcp.inflight_min=3D6144 net.inet.tcp.inflight_debug=3D0 net.inet.tcp.sack.enable=3D1 net.inet.ip.intr_queue_maxlen=3D500 /boot/loader.conf ----------------- kern.ipc.nmbclusters=3D"16384" hw.apic.mixed_mode=3D0 hw.intr_storm_threshold=3D5000 /etc/make.conf -------------- CFLAGS=3D -O2 -pipe -fno-builtin COPTFLAGS=3D -O2 -pipe -fno-builtin CPUTYPE?=3Dathlon-xp /Daniel Eriksson ------=_NextPart_000_001B_01C46D3A.3DA99070 Content-Type: application/octet-stream; name="dmesg.boot" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="dmesg.boot" Copyright (c) 1992-2004 The FreeBSD Project.=0A= Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994=0A= The Regents of the University of California. All rights reserved.=0A= FreeBSD 5.2-CURRENT #0: Sun Jul 18 09:29:39 CEST 2004=0A= daniel@fortify.xxx.xxx:/usr/obj/usr/src/sys/FORTIFY=0A= WARNING: Kernel preemption is disabled, expect reduced performance.=0A= Timecounter "i8254" frequency 1193182 Hz quality 0=0A= CPU: AMD Athlon(TM) XP 2500+ (1999.78-MHz 686-class CPU)=0A= Origin =3D "AuthenticAMD" Id =3D 0x6a0 Stepping =3D 0=0A= = Features=3D0x383fbff=0A= AMD Features=3D0xc0400000=0A= real memory =3D 1342156800 (1279 MB)=0A= avail memory =3D 1304948736 (1244 MB)=0A= ACPI APIC Table: =0A= ioapic0: Changing APIC ID to 2=0A= ioapic0 irqs 0-23 on motherboard=0A= npx0: [FAST]=0A= npx0: on motherboard=0A= npx0: INT 16 interface=0A= acpi0: on motherboard=0A= acpi0: [GIANT-LOCKED]=0A= acpi0: Power Button (fixed)=0A= Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000=0A= acpi_timer0: <32-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0=0A= cpu0: on acpi0=0A= acpi_button0: on acpi0=0A= pcib0: port 0xcf8-0xcff on acpi0=0A= pci0: on pcib0=0A= agp0: mem = 0xf8000000-0xfbffffff at device 0.0 on pci0=0A= pcib1: at device 1.0 on pci0=0A= pci1: on pcib1=0A= pci1: at device 0.0 (no driver attached)=0A= atapci0: port = 0xb400-0xb4ff,0xb800-0xb803,0xd000-0xd007,0xd400-0xd403,0xd800-0xd807 = irq 16 at device 10.0 on pci0=0A= ata2: at 0xd800 on atapci0=0A= ata3: at 0xd000 on atapci0=0A= atapci1: port = 0x9800-0x98ff,0xa000-0xa003,0xa400-0xa407,0xa800-0xa803,0xb000-0xb007 = irq 16 at device 10.1 on pci0=0A= ata4: at 0xb000 on atapci1=0A= ata5: at 0xa400 on atapci1=0A= ahc0: port 0x9400-0x94ff mem = 0xed800000-0xed800fff irq 19 at device 12.0 on pci0=0A= ahc0: [GIANT-LOCKED]=0A= aic7892: Ultra160 Wide Channel A, SCSI Id=3D7, 32/253 SCBs=0A= atapci2: port = 0x7800-0x78ff,0x8000-0x8003,0x8400-0x8407,0x8800-0x8803,0x9000-0x9007 = irq 17 at device 14.0 on pci0=0A= ata6: at 0x9000 on atapci2=0A= ata7: at 0x8400 on atapci2=0A= atapci3: port = 0x6000-0x60ff,0x6400-0x6403,0x6800-0x6807,0x7000-0x7003,0x7400-0x7407 = irq 17 at device 14.1 on pci0=0A= ata8: at 0x7400 on atapci3=0A= ata9: at 0x6800 on atapci3=0A= atapci4: port = 0x4000-0x40ff,0x4400-0x440f,0x4800-0x4803,0x5000-0x5007,0x5400-0x5403,0x5= 800-0x5807 irq 20 at device 15.0 on pci0=0A= ata10: at 0x5800 on atapci4=0A= ata11: at 0x5000 on atapci4=0A= atapci5: port = 0x3800-0x380f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 irq 20 at device 15.1 = on pci0=0A= ata0: at 0x1f0 irq 14 on atapci5=0A= ata1: at 0x170 irq 15 on atapci5=0A= uhci0: port 0x3400-0x341f irq 21 at device = 16.0 on pci0=0A= uhci0: [GIANT-LOCKED]=0A= usb0: on uhci0=0A= usb0: USB revision 1.0=0A= uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1=0A= uhub0: 2 ports with 2 removable, self powered=0A= uhci1: port 0x3000-0x301f irq 21 at device = 16.1 on pci0=0A= uhci1: [GIANT-LOCKED]=0A= usb1: on uhci1=0A= usb1: USB revision 1.0=0A= uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1=0A= uhub1: 2 ports with 2 removable, self powered=0A= uhci2: port 0x2800-0x281f irq 21 at device = 16.2 on pci0=0A= uhci2: [GIANT-LOCKED]=0A= usb2: on uhci2=0A= usb2: USB revision 1.0=0A= uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1=0A= uhub2: 2 ports with 2 removable, self powered=0A= uhci3: port 0x2400-0x241f irq 21 at device = 16.3 on pci0=0A= uhci3: [GIANT-LOCKED]=0A= usb3: on uhci3=0A= usb3: USB revision 1.0=0A= uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1=0A= uhub3: 2 ports with 2 removable, self powered=0A= ehci0: mem 0xed000000-0xed0000ff irq = 21 at device 16.4 on pci0=0A= ehci0: [GIANT-LOCKED]=0A= ehci_pci_attach: companion usb0=0A= ehci_pci_attach: companion usb1=0A= ehci_pci_attach: companion usb2=0A= ehci_pci_attach: companion usb3=0A= usb4: EHCI version 1.0=0A= usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3=0A= usb4: on ehci0=0A= usb4: USB revision 2.0=0A= uhub4: (0x1106) EHCI root hub, class 9/0, rev 2.00/1.00, addr 1=0A= uhub4: 8 ports with 8 removable, self powered=0A= isab0: at device 17.0 on pci0=0A= isa0: on isab0=0A= vr0: port 0x2000-0x20ff mem = 0xec800000-0xec8000ff irq 23 at device 18.0 on pci0=0A= miibus0: on vr0=0A= rlphy0: on miibus0=0A= rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto=0A= vr0: Ethernet address: 00:0e:a6:1f:29:1e=0A= vr0: [GIANT-LOCKED]=0A= re0: port 0x1800-0x18ff mem = 0xec000000-0xec0000ff irq 18 at device 19.0 on pci0=0A= miibus1: on re0=0A= rgephy0: on miibus1=0A= rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, = 1000baseTX-FDX, auto=0A= re0: Ethernet address: 00:50:fc:f8:c6:81=0A= re0: [GIANT-LOCKED]=0A= fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on = acpi0=0A= fdc0: FIFO enabled, 8 bytes threshold=0A= fd0: <1440-KB 3.5" drive> on fdc0 drive 0=0A= sio0: configured irq 4 not in bitmap of probed irqs 0=0A= sio0: port may not be enabled=0A= sio0 port 0x3f8-0x3ff irq 4 on acpi0=0A= sio0: type 16550A=0A= atkbdc0: port 0x64,0x60 irq 1 on acpi0=0A= atkbd0: irq 1 on atkbdc0=0A= kbd0 at atkbd0=0A= atkbd0: [GIANT-LOCKED]=0A= orm0: at iomem 0xc0000-0xcafff on isa0=0A= pmtimer0 on isa0=0A= sc0: at flags 0x100 on isa0=0A= sc0: VGA <16 virtual consoles, flags=3D0x300>=0A= sio1: configured irq 3 not in bitmap of probed irqs 0=0A= sio1: port may not be enabled=0A= vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0=0A= Timecounter "TSC" frequency 1999783309 Hz quality 800=0A= Timecounters tick every 1.000 msec=0A= ipfw2 initialized, divert enabled, rule-based forwarding enabled, = default to accept, logging unlimited=0A= ad0: 114473MB [232581/16/63] at ata0-master UDMA100=0A= ad1: 114473MB [232581/16/63] at ata0-slave UDMA100=0A= ad2: 117800MB [239340/16/63] at ata1-master UDMA100=0A= ad3: 117800MB [239340/16/63] at ata1-slave UDMA100=0A= ad4: 238475MB [484521/16/63] at ata2-master UDMA100=0A= ad5: 238475MB [484521/16/63] at ata2-slave UDMA100=0A= ad6: 239372MB [486344/16/63] at ata3-master UDMA133=0A= ad7: 239372MB [486344/16/63] at ata3-slave UDMA133=0A= ad8: 194481MB [395136/16/63] at ata4-master UDMA133=0A= ad9: 194481MB [395136/16/63] at ata4-slave UDMA133=0A= ad10: 194481MB [395136/16/63] at ata5-master UDMA133=0A= ad11: 239372MB [486344/16/63] at ata5-slave UDMA133=0A= ad12: 117800MB [239340/16/63] at ata6-master UDMA100=0A= ad13: 117800MB [239340/16/63] at ata6-slave UDMA100=0A= ad14: 117246MB [238216/16/63] at ata7-master UDMA133=0A= ad15: 117246MB [238216/16/63] at ata7-slave UDMA133=0A= ad16: 114473MB [232581/16/63] at ata8-master = UDMA100=0A= ad18: 26059MB [52946/16/63] at ata9-master UDMA66=0A= ad20: 239372MB [486344/16/63] at ata10-master SATA150=0A= ad22: 238475MB [484521/16/63] at ata11-master = SATA150=0A= ar0: 476950MB [60802/255/63] status: READY subdisks:=0A= disk0 READY on ad4 at ata2-master=0A= disk1 READY on ad5 at ata2-slave=0A= ar1: 478744MB [61031/255/63] status: READY subdisks:=0A= disk0 READY on ad6 at ata3-master=0A= disk1 READY on ad7 at ata3-slave=0A= ar2: 388962MB [49585/255/63] status: READY subdisks:=0A= disk0 READY on ad9 at ata4-slave=0A= disk1 READY on ad8 at ata4-master=0A= Waiting 5 seconds for SCSI devices to settle=0A= sa0 at ahc0 bus 0 target 5 lun 0=0A= sa0: Removable Sequential Access SCSI-2 device =0A= sa0: 10.000MB/s transfers (10.000MHz, offset 15)=0A= da0 at ahc0 bus 0 target 0 lun 0=0A= da0: Fixed Direct Access SCSI-3 device =0A= da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing = Enabled=0A= da0: 8759MB (17938986 512 byte sectors: 255H 63S/T 1116C)=0A= da1 at ahc0 bus 0 target 1 lun 0=0A= da1: Fixed Direct Access SCSI-3 device =0A= da1: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing = Enabled=0A= da1: 8759MB (17938986 512 byte sectors: 255H 63S/T 1116C)=0A= da2 at ahc0 bus 0 target 10 lun 0=0A= da2: Fixed Direct Access SCSI-3 device =0A= da2: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged = Queueing Enabled=0A= da2: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C)=0A= da3 at ahc0 bus 0 target 11 lun 0=0A= da3: Fixed Direct Access SCSI-3 device =0A= da3: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged = Queueing Enabled=0A= da3: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C)=0A= da4 at ahc0 bus 0 target 12 lun 0=0A= da4: Fixed Direct Access SCSI-3 device =0A= da4: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged = Queueing Enabled=0A= da4: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C)=0A= da5 at ahc0 bus 0 target 13 lun 0=0A= da5: Fixed Direct Access SCSI-3 device =0A= da5: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged = Queueing Enabled=0A= da5: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C)=0A= Mounting root from ufs:/dev/ad0s1a=0A= ------=_NextPart_000_001B_01C46D3A.3DA99070 Content-Type: application/octet-stream; name="FORTIFY" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="FORTIFY" =0A= machine i386=0A= cpu I686_CPU=0A= options CPU_ENABLE_SSE=0A= ident FORTIFY=0A= =0A= # Options for the firewall and NAT functionality=0A= options IPFIREWALL=0A= options IPDIVERT=0A= options IPFIREWALL_DEFAULT_TO_ACCEPT=0A= options IPFIREWALL_VERBOSE=0A= =0A= =0A= # To statically compile in device wiring instead of /boot/device.hints=0A= #hints "GENERIC.hints" # Default places to look for devices.=0A= =0A= makeoptions DEBUG=3D-g # Build kernel with gdb(1) debug symbols=0A= =0A= #options SCHED_ULE # ULE scheduler=0A= options SCHED_4BSD # 4BSD scheduler=0A= options INET # InterNETworking=0A= options INET6 # IPv6 communications protocols=0A= options FFS # Berkeley Fast Filesystem=0A= options SOFTUPDATES # Enable FFS soft updates support=0A= options UFS_ACL # Support for access control lists=0A= options UFS_DIRHASH # Improve performance on big directories=0A= options MD_ROOT # MD is a potential root device=0A= options NFSCLIENT # Network Filesystem Client=0A= options NFSSERVER # Network Filesystem Server=0A= options NFS_ROOT # NFS usable as /, requires NFSCLIENT=0A= options MSDOSFS # MSDOS Filesystem=0A= options CD9660 # ISO 9660 Filesystem=0A= options PROCFS # Process filesystem (requires PSEUDOFS)=0A= options PSEUDOFS # Pseudo-filesystem framework=0A= options GEOM_GPT # GUID Partition Tables.=0A= options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!]=0A= options COMPAT_FREEBSD4 # Compatible with FreeBSD4=0A= options SCSI_DELAY=3D5000 # Delay (in ms) before probing SCSI=0A= #options KTRACE # ktrace(1) support=0A= options SYSVSHM # SYSV-style shared memory=0A= options SYSVMSG # SYSV-style message queues=0A= options SYSVSEM # SYSV-style semaphores=0A= options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time = extensions=0A= options KBD_INSTALL_CDEV # install a CDEV entry in /dev=0A= #options AHC_REG_PRETTY_PRINT # Print register bitfields in debug = output. Adds ~128k to driver.=0A= #options AHD_REG_PRETTY_PRINT # Print register bitfields in debug = output. Adds ~215k to driver.=0A= #options PFIL_HOOKS # pfil(9) framework=0A= =0A= =0A= # dakrer=0A= options DEVICE_POLLING=0A= options DUMMYNET=0A= options HZ=3D2000=0A= options ZERO_COPY_SOCKETS # Turn on zero copy send code=0A= =0A= # The aic7xxx driver will attempt to use memory mapped I/O for all PCI=0A= # controllers that have it configured only if this option is set. = Unfortunately,=0A= # this doesn't work on some motherboards, which prevents it from being = the=0A= # default.=0A= options AHC_ALLOW_MEMIO=0A= =0A= =0A= # encrypted filesystem=0A= options GEOM_BDE=0A= =0A= # netgraph(4). Enable the base netgraph code with the NETGRAPH option.=0A= # Individual node types can be enabled with the corresponding option=0A= # listed below; however, this is not strictly necessary as netgraph=0A= # will automatically load the corresponding KLD module if the node type=0A= # is not already compiled into the kernel. Each type below has a=0A= # corresponding man page, e.g., ng_async(8).=0A= options NETGRAPH #netgraph(4) system=0A= #options NETGRAPH_ASYNC=0A= #options NETGRAPH_ATMLLC=0A= #options NETGRAPH_ATM_ATMPIF=0A= #options NETGRAPH_BLUETOOTH # ng_bluetooth(4)=0A= #options NETGRAPH_BLUETOOTH_BT3C # ng_bt3c(4)=0A= #options NETGRAPH_BLUETOOTH_H4 # ng_h4(4)=0A= #options NETGRAPH_BLUETOOTH_HCI # ng_hci(4)=0A= #options NETGRAPH_BLUETOOTH_L2CAP # ng_l2cap(4)=0A= #options NETGRAPH_BLUETOOTH_SOCKET # ng_btsocket(4)=0A= #options NETGRAPH_BLUETOOTH_UBT # ng_ubt(4)=0A= #options NETGRAPH_BLUETOOTH_UBTBCMFW # ubtbcmfw(4)=0A= #options NETGRAPH_BPF=0A= #options NETGRAPH_BRIDGE=0A= #options NETGRAPH_CISCO=0A= #options NETGRAPH_ECHO=0A= #options NETGRAPH_ETHER=0A= #options NETGRAPH_FRAME_RELAY=0A= #options NETGRAPH_GIF=0A= #options NETGRAPH_GIF_DEMUX=0A= #options NETGRAPH_HOLE=0A= #options NETGRAPH_IFACE=0A= #options NETGRAPH_IP_INPUT=0A= #options NETGRAPH_KSOCKET=0A= #options NETGRAPH_L2TP=0A= #options NETGRAPH_LMI=0A= ## MPPC compression requires proprietary files (not included)=0A= ##options NETGRAPH_MPPC_COMPRESSION=0A= #options NETGRAPH_MPPC_ENCRYPTION=0A= #options NETGRAPH_ONE2MANY=0A= #options NETGRAPH_PPP=0A= #options NETGRAPH_PPPOE=0A= #options NETGRAPH_PPTPGRE=0A= #options NETGRAPH_RFC1490=0A= #options NETGRAPH_SOCKET=0A= #options NETGRAPH_SPLIT=0A= #options NETGRAPH_SPPP=0A= #options NETGRAPH_TEE=0A= #options NETGRAPH_TTY=0A= #options NETGRAPH_UI=0A= #options NETGRAPH_VJC=0A= =0A= =0A= # Debugging for use in -current=0A= options KDB # Enable the kernel debugger=0A= options DDB # Enable the kernel debugger=0A= #options INVARIANTS # Enable calls of extra sanity checking=0A= #options INVARIANT_SUPPORT # Extra sanity checks of internal = structures, required by INVARIANTS=0A= #options WITNESS # Enable checks to detect deadlocks and cycles=0A= #options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed=0A= =0A= # To make an SMP kernel, the next two are needed=0A= #options SMP # Symmetric MultiProcessor Kernel=0A= device apic # I/O APIC=0A= #options NO_MIXED_MODE # Don't penalize working chipsets=0A= =0A= =0A= # Bus support. Do not remove isa, even if you have no isa slots=0A= device isa=0A= #device eisa=0A= device pci=0A= =0A= # Floppy drives=0A= device fdc=0A= =0A= # ATA and ATAPI devices=0A= device ata=0A= device atadisk # ATA disk drives=0A= device ataraid # ATA RAID drives=0A= device atapicd # ATAPI CDROM drives=0A= device atapifd # ATAPI floppy drives=0A= device atapist # ATAPI tape drives=0A= options ATA_STATIC_ID # Static device numbering=0A= =0A= # SCSI Controllers=0A= #device ahb # EISA AHA1742 family=0A= device ahc # AHA2940 and onboard AIC7xxx devices=0A= device ahd # AHA39320/29320 and onboard AIC79xx devices=0A= #device amd # AMD 53C974 (Tekram DC-390(T))=0A= #device isp # Qlogic family=0A= #device mpt # LSI-Logic MPT-Fusion=0A= ##device ncr # NCR/Symbios Logic=0A= #device sym # NCR/Symbios Logic (newer chipsets + those of `ncr')=0A= #device trm # Tekram DC395U/UW/F DC315U adapters=0A= =0A= #device adv # Advansys SCSI adapters=0A= #device adw # Advansys wide SCSI adapters=0A= #device aha # Adaptec 154x SCSI adapters=0A= #device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60.=0A= #device bt # Buslogic/Mylex MultiMaster SCSI adapters=0A= =0A= #device ncv # NCR 53C500=0A= #device nsp # Workbit Ninja SCSI-3=0A= #device stg # TMC 18C30/18C50=0A= =0A= # SCSI peripherals=0A= device scbus # SCSI bus (required for SCSI)=0A= device ch # SCSI media changers=0A= device da # Direct Access (disks)=0A= device sa # Sequential Access (tape etc)=0A= device cd # CD=0A= device pass # Passthrough device (direct SCSI access)=0A= device ses # SCSI Environmental Services (and SAF-TE)=0A= =0A= # RAID controllers interfaced to the SCSI subsystem=0A= #device amr # AMI MegaRAID=0A= #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID=0A= #device ciss # Compaq Smart RAID 5*=0A= #device dpt # DPT Smartcache III, IV - See NOTES for options=0A= #device iir # Intel Integrated RAID=0A= #device ips # IBM (Adaptec) ServeRAID=0A= #device mly # Mylex AcceleRAID/eXtremeRAID=0A= #device twa # 3ware 9000 series PATA/SATA RAID=0A= =0A= # RAID controllers=0A= #device aac # Adaptec FSA RAID=0A= #device aacp # SCSI passthrough for aac (requires CAM)=0A= #device ida # Compaq Smart RAID=0A= #device mlx # Mylex DAC960 family=0A= #device pst # Promise Supertrak SX6000=0A= #device twe # 3ware ATA RAID=0A= =0A= # atkbdc0 controls both the keyboard and the PS/2 mouse=0A= device atkbdc # AT keyboard controller=0A= device atkbd # AT keyboard=0A= device psm # PS/2 mouse=0A= =0A= device vga # VGA video card driver=0A= =0A= device splash # Splash screen and screen saver support=0A= =0A= # syscons is the default console driver, resembling an SCO console=0A= device sc=0A= =0A= # Enable this for the pcvt (VT220 compatible) console driver=0A= #device vt=0A= #options XSERVER # support for X server on a vt console=0A= #options FAT_CURSOR # start with block cursor=0A= =0A= device agp # support several AGP chipsets=0A= =0A= # Floating point support - do not disable.=0A= device npx=0A= =0A= # Power management support (see NOTES for more options)=0A= #device apm=0A= # Add suspend/resume support for the i8254.=0A= device pmtimer=0A= =0A= # PCCARD (PCMCIA) support=0A= # PCMCIA and cardbus bridge support=0A= #device cbb # cardbus (yenta) bridge=0A= ##device pcic # ExCA ISA and PCI bridges=0A= #device pccard # PC Card (16-bit) bus=0A= #device cardbus # CardBus (32-bit) bus=0A= =0A= # Serial (COM) ports=0A= device sio # 8250, 16[45]50 based serial ports=0A= =0A= # Parallel port=0A= #device ppc=0A= #device ppbus # Parallel port bus (required)=0A= #device lpt # Printer=0A= #device plip # TCP/IP over parallel=0A= #device ppi # Parallel port interface device=0A= ##device vpo # Requires scbus and da=0A= =0A= # If you've got a "dumb" serial or parallel PCI card that is=0A= # supported by the puc(4) glue driver, uncomment the following=0A= # line to enable it (connects to the sio and/or ppc drivers):=0A= #device puc=0A= =0A= # PCI Ethernet NICs.=0A= #device de # DEC/Intel DC21x4x (``Tulip'')=0A= device em # Intel PRO/1000 adapter Gigabit Ethernet Card=0A= #device txp # 3Com 3cR990 (``Typhoon'')=0A= #device vx # 3Com 3c590, 3c595 (``Vortex'')=0A= =0A= # PCI Ethernet NICs that use the common MII bus controller code.=0A= # NOTE: Be sure to keep the 'device miibus' line in order to use these = NICs!=0A= device miibus # MII bus support=0A= #device bfe # Broadcom BCM440x 10/100 Ethernet=0A= device bge # Broadcom BCM570xx Gigabit Ethernet=0A= #device dc # DEC/Intel 21143 and various workalikes=0A= #device fxp # Intel EtherExpress PRO/100B (82557, 82558)=0A= #device pcn # AMD Am79C97x PCI 10/100 (precedence over 'lnc')=0A= device re # RealTek 8139C+/8169/8169S/8110S=0A= device rl # RealTek 8129/8139=0A= #device sf # Adaptec AIC-6915 (``Starfire'')=0A= #device sis # Silicon Integrated Systems SiS 900/SiS 7016=0A= #device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet=0A= #device ste # Sundance ST201 (D-Link DFE-550TX)=0A= #device ti # Alteon Networks Tigon I/II gigabit Ethernet=0A= #device tl # Texas Instruments ThunderLAN=0A= #device tx # SMC EtherPower II (83c170 ``EPIC'')=0A= device vr # VIA Rhine, Rhine II=0A= #device wb # Winbond W89C840F=0A= device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'')=0A= =0A= # ISA Ethernet NICs. pccard NICs included.=0A= #device cs # Crystal Semiconductor CS89x0 NIC=0A= # 'device ed' requires 'device miibus'=0A= #device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards=0A= #device ex # Intel EtherExpress Pro/10 and Pro/10+=0A= #device ep # Etherlink III based cards=0A= #device fe # Fujitsu MB8696x based cards=0A= #device ie # EtherExpress 8/16, 3C507, StarLAN 10 etc.=0A= #device lnc # NE2100, NE32-VL Lance Ethernet cards=0A= #device sn # SMC's 9000 series of Ethernet chips=0A= #device xe # Xircom pccard Ethernet=0A= =0A= # ISA devices that use the old ISA shims=0A= #device le=0A= =0A= # Wireless NIC cards=0A= #device wlan # 802.11 support=0A= #device an # Aironet 4500/4800 802.11 wireless NICs.=0A= #device awi # BayStack 660 and others=0A= #device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs.=0A= ##device wl # Older non 802.11 Wavelan wireless NIC.=0A= =0A= # Pseudo devices - the number indicates how many units to allocate.=0A= device random # Entropy device=0A= device loop # Network loopback=0A= device ether # Ethernet support=0A= device sl # Kernel SLIP=0A= device ppp # Kernel PPP=0A= device tun # Packet tunnel.=0A= device pty # Pseudo-ttys (telnet etc)=0A= device md # Memory "disks"=0A= device gif # IPv6 and IPv4 tunneling=0A= device faith # IPv6-to-IPv4 relaying (translation)=0A= =0A= # The `bpf' device enables the Berkeley Packet Filter.=0A= # Be aware of the administrative consequences of enabling this!=0A= device bpf # Berkeley packet filter=0A= =0A= # USB support=0A= device uhci # UHCI PCI->USB interface=0A= device ohci # OHCI PCI->USB interface=0A= device ehci # EHCI controller=0A= device usb # USB Bus (required)=0A= #device udbp # USB Double Bulk Pipe devices=0A= device ugen # Generic=0A= device uhid # "Human Interface Devices"=0A= device ukbd # Keyboard=0A= device ulpt # Printer=0A= device umass # Disks/Mass storage - Requires scbus and da=0A= device ums # Mouse=0A= device urio # Diamond Rio 500 MP3 player=0A= device uscanner # Scanners=0A= # USB Ethernet, requires mii=0A= device aue # ADMtek USB Ethernet=0A= device axe # ASIX Electronics USB Ethernet=0A= device cue # CATC USB Ethernet=0A= device kue # Kawasaki LSI USB Ethernet=0A= device rue # RealTek RTL8150 USB Ethernet=0A= =0A= # FireWire support=0A= #device firewire # FireWire bus code=0A= #device sbp # SCSI over FireWire (Requires scbus and da)=0A= #device fwe # Ethernet over FireWire (non-standard!)=0A= =0A= ------=_NextPart_000_001B_01C46D3A.3DA99070-- From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 01:37: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 49D0116A4CE for ; Mon, 19 Jul 2004 01:37:51 +0000 (GMT) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 788DD43D4C for ; Mon, 19 Jul 2004 01:37:50 +0000 (GMT) (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 i6J1bm0q044504 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 19 Jul 2004 05:37:48 +0400 (MSD) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id i6J1bl0b044503 for current@freebsd.org; Mon, 19 Jul 2004 05:37:47 +0400 (MSD) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Mon, 19 Jul 2004 05:37:47 +0400 From: Gleb Smirnoff To: current@freebsd.org Message-ID: <20040719013747.GA44440@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: apm broken 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, 19 Jul 2004 01:37:51 -0000 I have upgraded to recent CURRENT (Jul 15) my IBM Thinkpad T20 notebook and now apm is broken. When notebook resumes after sleep it starts display and freezes with no chance to escape to debugger. My previuos kernel from Jul 9 were resuming/sleeping flawlessly. Anyone has any ideas? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 05:25:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6B6FA16A4CE; Mon, 19 Jul 2004 05:25:36 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.12.11/8.12.11) with ESMTP id i6J5PZ31001137; Mon, 19 Jul 2004 01:25:35 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.12.11/8.12.11/Submit) id i6J5PZ9R001136; Mon, 19 Jul 2004 01:25:35 -0400 (EDT) (envelope-from green) Date: Mon, 19 Jul 2004 01:25:34 -0400 From: Brian Fundakowski Feldman To: current@FreeBSD.org Message-ID: <20040719052534.GA1038@green.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: lockups with src/tools/regression/gaithrstress 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, 19 Jul 2004 05:25:36 -0000 Running with or without kern.smp.disabled, with a very up-to-date kernel, I can easily lock up the system by running gaithrstress -t 50 a few times at once. There is nothing special that has changed in the last few weeks, though I have extensive changes to kqueue and VM which I consider entirely stable at this point. Anything causing a problem like this seems like it's due to changes within the last few weeks. The only clue I have comes from a previous panic() (which promptly just locked up going into "KDB: enter: panic"), "kse/thread mismatch" as generated by choosethread(). The connect() system call was trying to do an mi_switch() inside a mtx_lock() at the time. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 05:47: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 72E2C16A4CE for ; Mon, 19 Jul 2004 05:47:02 +0000 (GMT) Received: from mallard.mail.pas.earthlink.net (mallard.mail.pas.earthlink.net [207.217.120.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F9E243D39 for ; Mon, 19 Jul 2004 05:47:02 +0000 (GMT) (envelope-from andrei@kableu.com) Received: from h-68-164-93-29.snvacaid.dynamic.covad.net ([68.164.93.29] helo=root.kableu.com) by mallard.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1BmQzN-0002C5-00 for freebsd-current@freebsd.org; Sun, 18 Jul 2004 22:47:01 -0700 Received: by root.kableu.com (Postfix, from userid 1001) id 513445C88; Sun, 18 Jul 2004 22:39:22 -0700 (PDT) Date: Sun, 18 Jul 2004 22:39:22 -0700 From: Andrew Konstantinov To: freebsd-current@freebsd.org Message-ID: <20040719053922.GA3333@root.kableu.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZGiS0Q5IWpPtfppv" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: ppp => Phase: deflink: Already in NETWORK phase 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, 19 Jul 2004 05:47:02 -0000 --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, I'm having some difficulties with ppp not being able to renegotiate the connection properly. I've browsed the ppp logs and came to the conclusion t= hat "Phase: deflink: Already in NETWORK phase" is the source of the problem. I'm using ppp to establish/manage my DSL link (PPPoE). Here is the ppp.conf fil= e: default: set server /var/run/internet "" 0177 set device PPPoE:dc0 set mtu 1492 set mru 1492 set cd 5 set authname secret set authkey secret set dial set login add default HISADDR enable dns PPP is running in the 'ddial' mode. Whenever the connection is dropped, the following happens: Phase: deflink: hangup -> opening Phase: deflink: Enter pause (3) for redialing. Phase: deflink: Connected! Phase: deflink: opening -> dial Phase: deflink: dial -> carrier Phase: Received NGM_PPPOE_ACNAME (secret) Phase: Received NGM_PPPOE_SESSIONID Phase: Received NGM_PPPOE_SUCCESS Phase: deflink: carrier -> login Phase: deflink: login -> lcp Phase: deflink: his =3D CHAP 0x05, mine =3D none Phase: Chap Input: CHALLENGE (secret) Phase: Chap Output: RESPONSE (secret) Phase: Chap Input: SUCCESS Phase: deflink: Already in NETWORK phase Phase: deflink: lcp -> open Phase: Clearing choked output queue Phase: deflink: open -> lcp Phase: Received NGM_PPPOE_CLOSE Phase: deflink: Device disconnected Phase: deflink: Disconnected! Phase: deflink: lcp -> logout Phase: deflink: Disconnected! Phase: deflink: logout -> hangup Phase: deflink: Connect time: 121 secs: 393 octets in, 114 octets out The same thing happens every time when the connection drop is followed by p= pp's attempt to renegotiate it. As you can see, it always fails. On the other hand, if I kill ppp entirely and start the connection setup process from scratch, everything goes well and link is established properly. Here is the log: Phase: PPP Started (ddial mode). Phase: bundle: Establish Phase: deflink: closed -> opening Phase: deflink: Connected! Phase: deflink: opening -> dial Phase: deflink: dial -> carrier Phase: Received NGM_PPPOE_ACNAME (secret) Phase: Received NGM_PPPOE_SESSIONID Phase: Received NGM_PPPOE_SUCCESS Phase: deflink: carrier -> login Phase: deflink: login -> lcp Phase: bundle: Authenticate Phase: deflink: his =3D CHAP 0x05, mine =3D none Phase: Chap Input: CHALLENGE (secret) Phase: Chap Output: RESPONSE (secret) Phase: Chap Input: SUCCESS Phase: deflink: lcp -> open Phase: bundle: Network At this point, the link up and I'm able to communicate over it. If I understood everything correctly, the problem is that when the ppp trie= s to renegotiate the connection, it uses old network phase. I guess at this poin= t my link's peer has already abandoned that old network phase and in order for renegotiation to succeed, a new network phase has to be setup. But ppp fail= s to do that and as a result of that my peer doesn't allow any communication to = go through, which in its turn creates the overflow of the output packet queue. So if everything said above is correct, then my question is: How would I fo= rce ppp to reestablish that network phase each time my connection is dropped? I= 've looked at the ppp/pppctl manual pages but didn't find a solution there. In case it's needed, here is my uname -a:=20 FreeBSD secret 5.2.1-RELEASE-p9 FreeBSD 5.2.1-RELEASE-p9 #0: Sat Jul 10 16:47:35 PDT 2004 root@secret:/usr/obj/usr/src/sys/CUSTOM i386 Any help will be greatly appreciated. - Andrew --ZGiS0Q5IWpPtfppv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA+16K5Jhyz2/cFigRArORAJ4vZwbT+On1acTcp/4l0Y6whxpT0ACgw8xA OFCH37f+N1VcENdwj6T7gc4= =GF8d -----END PGP SIGNATURE----- --ZGiS0Q5IWpPtfppv-- From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 06:07: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 C328516A4CE; Mon, 19 Jul 2004 06:07:32 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0180B43D1F; Mon, 19 Jul 2004 06:07:32 +0000 (GMT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.11/8.12.11) with ESMTP id i6J67UjW087888; Mon, 19 Jul 2004 10:07:30 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.11/8.12.11/Submit) id i6J67UoB087887; Mon, 19 Jul 2004 10:07:30 +0400 (MSD) (envelope-from ache) Date: Mon, 19 Jul 2004 10:07:30 +0400 From: Andrey Chernov To: Tim Kientzle Message-ID: <20040719060730.GA87697@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Tim Kientzle , current@FreeBSD.ORG, ports@FreeBSD.ORG References: <40F963D8.6010201@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40F963D8.6010201@freebsd.org> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter 1.1-beta; AVE 6.26.0.5; VDF 6.26.0.32 (host: pobrecita.freebsd.ru) cc: ports@FreeBSD.ORG cc: current@FreeBSD.ORG Subject: Re: NEW TAR 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, 19 Jul 2004 06:07:32 -0000 On Sat, Jul 17, 2004 at 10:37:28AM -0700, Tim Kientzle wrote: > * File format: bsdtar can read gtar files, including > long file names, long link names, and sparse files. > bsdtar can also read many other formats that gtar > does not support. Addition: bsdtar can't write sparse archives (Yet?). -- Andrey Chernov | http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 06:48: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 3507C16A4CE for ; Mon, 19 Jul 2004 06:48:13 +0000 (GMT) Received: from hellhound.ceribus.net (c-24-21-90-79.client.comcast.net [24.21.90.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id B54FC43D45 for ; Mon, 19 Jul 2004 06:48:12 +0000 (GMT) (envelope-from grover@ceribus.net) Received: (qmail 85103 invoked by uid 1002); 19 Jul 2004 06:48:12 -0000 Received: from grover@ceribus.net by hellhound.ceribus.net by uid 89 with qmail-scanner-1.22 (clamscan: 0.73. spamassassin: 2.63. Clear:RC:1(192.168.200.200):. Processed in 1.231428 secs); 19 Jul 2004 06:48:12 -0000 Received: from unknown (HELO purgatory) (192.168.200.200) by 192.168.200.225 with SMTP; 19 Jul 2004 06:48:10 -0000 From: "Grover Lines" To: Date: Sun, 18 Jul 2004 23:48:13 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcRtXFyyoPo8nOrCROO8WtdtUQ9SEg== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2149 X-Qmail-Scanner-Message-ID: <109021969067285097@hellhound.ceribus.net> Message-Id: <20040719064812.B54FC43D45@mx1.FreeBSD.org> Subject: Installworld borked? 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, 19 Jul 2004 06:48:13 -0000 Is it just me or ? Buildworld buildkernel installkernel all worked fine ===> usr.sbin/pkg_install/version install -s -o root -g wheel -m 555 pkg_version /usr/sbin install -o root -g wheel -m 444 pkg_version.1.gz /usr/share/man/man1 ===> usr.sbin/pnpinfo install -s -o root -g wheel -m 555 pnpinfo /usr/sbin install -o root -g wheel -m 444 pnpinfo.8.gz /usr/share/man/man8 ===> usr.sbin/ppp install -s -o root -g network -m 4550 ppp /usr/sbin m4 /usr/src/usr.sbin/ppp/ppp.8.m4 >ppp.8 m4: not found *** Error code 127 Stop in /usr/src/usr.sbin/ppp. *** Error code 1 Stop in /usr/src/usr.sbin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- Grover Lines From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 06:59: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 1F80C16A4CE; Mon, 19 Jul 2004 06:59:58 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1D9F43D4C; Mon, 19 Jul 2004 06:59:55 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6J6w7sD071832; Mon, 19 Jul 2004 08:58:07 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <11e601c46d5c$d9db1910$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Robert Watson" References: <115601c46d1a$bf9f4540$471b3dd4@digiware.nl> Date: Mon, 19 Jul 2004 08:51:42 +0200 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.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 fromzone0xffffff007fed4780(Mbuf) 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, 19 Jul 2004 06:59:58 -0000 > I'll starts some more tests before I'm of to bed. This mornings result: ==== System call getdirentries returning with the following locks held: exclusive sleep mutex bdone lock r = 0 (0xffffffff805fd080) locked @ /home2/src/ sys/kern/vfs_bio.c:3767 panic: witness_warn cpuid = 0; KDB: stack backtrace: kdspin lock sched lock held by 0xffffff007b6cc940 for > 5 seconds panic: spin lock held too long cpuid = 0; KDB: enter: panic ==== But no way to get into the debugger. Does not look like it is much network related??? --WjW From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 07:24: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 EA05F16A4CF for ; Mon, 19 Jul 2004 07:24:41 +0000 (GMT) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3508A43D5D for ; Mon, 19 Jul 2004 07:24:41 +0000 (GMT) (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 i6J7OdG5045803 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 19 Jul 2004 11:24:40 +0400 (MSD) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id i6J7Od9H045802 for current@freebsd.org; Mon, 19 Jul 2004 11:24:39 +0400 (MSD) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Mon, 19 Jul 2004 11:24:39 +0400 From: Gleb Smirnoff To: current@freebsd.org Message-ID: <20040719072439.GD45598@cell.sick.ru> References: <20040719013747.GA44440@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20040719013747.GA44440@cell.sick.ru> User-Agent: Mutt/1.5.6i Subject: Re: apm broken 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, 19 Jul 2004 07:24:42 -0000 On Mon, Jul 19, 2004 at 05:37:47AM +0400, Gleb Smirnoff wrote: T> I have upgraded to recent CURRENT (Jul 15) my IBM Thinkpad T20 notebook T> and now apm is broken. When notebook resumes after sleep it starts T> display and freezes with no chance to escape to debugger. T> T> My previuos kernel from Jul 9 were resuming/sleeping flawlessly. T> T> Anyone has any ideas? I forgot to mention important thing: ACPI is turned off. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 08:15: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 7B46E16A4CE for ; Mon, 19 Jul 2004 08:15:22 +0000 (GMT) Received: from cod.melbpc.org.au (cod.melbpc.org.au [203.12.152.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1388043D49 for ; Mon, 19 Jul 2004 08:15:21 +0000 (GMT) (envelope-from kpeter@melbpc.org.au) Received: from localhost (localhost.melbpc.org.au [127.0.0.1]) by cod.melbpc.org.au (Postfix) with ESMTP id 33C6625DC1 for ; Mon, 19 Jul 2004 18:15:20 +1000 (EST) Received: from cod.melbpc.org.au ([127.0.0.1]) by localhost (cod.melbpc.org.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 76417-08 for ; Mon, 19 Jul 2004 18:15:19 +1000 (EST) Received: from [203.12.158.69] (a1-69.melbpc.org.au [203.12.158.69]) by cod.melbpc.org.au (Postfix) with ESMTP id AD77525DC0 for ; Mon, 19 Jul 2004 18:15:18 +1000 (EST) Message-ID: <40FB8313.5050308@melbpc.org.au> Date: Mon, 19 Jul 2004 18:15:15 +1000 From: Peter Kostouros Organization: Melbourne PC User Group User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8a2) Gecko/20040710 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-Virus-Scanned: by amavisd-new at melbpc.org.au Subject: [panic] setrunqueue X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kpeter@melbpc.org.au List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2004 08:15:22 -0000 Hi I received a fatal error and hope the following is useful: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x54 fault code = supervisor write, page not present instruction pointer = 0x8:0xc0545485 stack pointer = 0x10:0xe0209a8c frame pointer = 0x10:0xe0209aac code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 2397 (xmms) [thread 100180] Stopped at 0xc0545485 = setrunqueue+0x1b5: movl %edi, 0x54(%edx) Trace gave the following: setrunqueue+0x1b5 sched_switch+0xa4 mi_switch+0x2af maybe_preemt+0xde sched_add_interval+0x2b2 sched_add+0x19 setrunqueue+0x1c6 turnstile_unpend+0x2e8 _mtx_unlock_sleep+0x87 _mtx_unlock_flags+0xd1 soo_write+0xb6 dofilewrite+0xcb write+0x6e syscall+0x2a0 Xint0x80_syscall+0x1f --- syscall(4, FreeBSD ELF32, write), eip = 0x2835d8cb, esp = 0xbfbfe7fc, ebp = 0xbfbfe818 Script started on Sun Jul 18 20:33:54 2004 eva# gdb6 -k kernel.debug GNU gdb 20040713 [GDB v6.x for 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-portbld-freebsd5.2"... (kgdb) l *setrunqueue+0x1b5 0xc0545485 is in setrunqueue (/mnt/cvs/FreeBSD/usr/src/sys/kern/kern_switch.c:422). 417 * put the new kse on whatever is next, 418 * which may or may not be us. 419 */ 420 td2 = TAILQ_NEXT(tda, td_runq); 421 kg->kg_last_assigned = td2; 422 td2->td_kse = ke; 423 ke->ke_thread = td2; 424 } 425 sched_add(ke->ke_thread); 426 } (kgdb) q eva# exit exit Script done on Sun Jul 18 20:41:03 2004 1. The system was built after a cvsup on 17JUL2004 (~midday) (nb, I am at GMT+10); 2. Scheduler is SCHED_ULE; 3. UP machine, no hyperthreading; 4. I have had several panics: all in an X session, some under load (building applications) others under light load (mozilla, multimedia applications). -- Regards Peter As always the organisation disavows knowledge of this email _______________________________________________ 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 Jul 19 08:32: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 A4ED916A4CE; Mon, 19 Jul 2004 08:32:42 +0000 (GMT) Received: from smtp3.sentex.ca (smtp3.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46C0B43D3F; Mon, 19 Jul 2004 08:32:42 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smtp3.sentex.ca (8.12.11/8.12.11) with ESMTP id i6J8WcBR045602; Mon, 19 Jul 2004 04:32:39 -0400 (EDT) (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 i6J8We6p057887; Mon, 19 Jul 2004 04:32:41 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 496AD7303F; Mon, 19 Jul 2004 04:32:40 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040719083240.496AD7303F@freebsd-current.sentex.ca> Date: Mon, 19 Jul 2004 04:32:40 -0400 (EDT) Subject: [current tinderbox] failure on alpha/alpha 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, 19 Jul 2004 08:32:42 -0000 TB --- 2004-07-19 08:00:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-07-19 08:00:00 - starting CURRENT tinderbox run for alpha/alpha TB --- 2004-07-19 08:00:00 - checking out the source tree TB --- 2004-07-19 08:00:00 - cd /home/tinderbox/sandbox/CURRENT/alpha/alpha TB --- 2004-07-19 08:00:00 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-07-19 08:04:50 - building world (CFLAGS=-O2 -pipe) TB --- 2004-07-19 08:04:50 - cd /home/tinderbox/sandbox/CURRENT/alpha/alpha/src TB --- 2004-07-19 08:04:50 - /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 [...] /tinderbox/CURRENT/alpha/alpha/src/lib/libthread_db/arch/alpha/libc_r_md.c:60: error: request for member `r_regs' in something not a structure or union /tinderbox/CURRENT/alpha/alpha/src/lib/libthread_db/arch/alpha/libc_r_md.c:61: error: request for member `r_regs' in something not a structure or union /tinderbox/CURRENT/alpha/alpha/src/lib/libthread_db/arch/alpha/libc_r_md.c:62: error: request for member `r_regs' in something not a structure or union /tinderbox/CURRENT/alpha/alpha/src/lib/libthread_db/arch/alpha/libc_r_md.c:63: error: request for member `r_regs' in something not a structure or union /tinderbox/CURRENT/alpha/alpha/src/lib/libthread_db/arch/alpha/libc_r_md.c:64: error: request for member `r_regs' in something not a structure or union /tinderbox/CURRENT/alpha/alpha/src/lib/libthread_db/arch/alpha/libc_r_md.c:65: error: request for member `r_regs' in something not a structure or union /tinderbox/CURRENT/alpha/alpha/src/lib/libthread_db/arch/alpha/libc_r_md.c:66: error: request for member `r_regs' in something not a structure or union /tinderbox/CURRENT/alpha/alpha/src/lib/libthread_db/arch/alpha/libc_r_md.c:67: error: request for member `r_regs' in something not a structure or union *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src/lib/libthread_db. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src/lib. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src. TB --- 2004-07-19 08:32:40 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-07-19 08:32:40 - ERROR: failed to build world TB --- 2004-07-19 08:32:40 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 09:22: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 84B9F16A539 for ; Mon, 19 Jul 2004 09:22:12 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38AE143D41 for ; Mon, 19 Jul 2004 09:22:12 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from pooker.samsco.org (scottl@localhost [127.0.0.1]) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6J9S8NM053125; Mon, 19 Jul 2004 03:28:08 -0600 (MDT) (envelope-from scottl@freebsd.org) Received: from localhost (scottl@localhost)i6J9S80s053122; Mon, 19 Jul 2004 03:28:08 -0600 (MDT) (envelope-from scottl@freebsd.org) X-Authentication-Warning: pooker.samsco.org: scottl owned process doing -bs Date: Mon, 19 Jul 2004 03:28:08 -0600 (MDT) From: Scott Long Sender: scottl@pooker.samsco.org To: Peter Kostouros In-Reply-To: <40FB8313.5050308@melbpc.org.au> Message-ID: <20040719032535.U32601@pooker.samsco.org> References: <40FB8313.5050308@melbpc.org.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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: [panic] setrunqueue 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, 19 Jul 2004 09:22:13 -0000 On Mon, 19 Jul 2004, Peter Kostouros wrote: > Hi > > I received a fatal error and hope the following is useful: This has been observed often recently. There are some suggestions floating around privately on how to fix this, but probably the easiest work-around for now is to undefine PREEMPTION in /sys/i386/include/param.h I'm expecting to get this resolved in some form in the next 24 hours. Scott From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 09:47: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 D419816A4CF; Mon, 19 Jul 2004 09:47:39 +0000 (GMT) Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6509943D2F; Mon, 19 Jul 2004 09:47:39 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from fwd01.aul.t-online.de by mailout02.sul.t-online.com with smtp id 1BmUkD-0004sK-03; Mon, 19 Jul 2004 11:47:37 +0200 Received: from Andro-Beta.Leidinger.net (VT0SliZbrex24sDOaY1tWUgptEWC5UNFgalisPeanLuQ1KYogrupUh@[84.128.202.42]) by fmrl01.sul.t-online.com with esmtp id 1BmUk4-0j5C8u0; Mon, 19 Jul 2004 11:47:28 +0200 Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) i6J9lSuH063569; Mon, 19 Jul 2004 11:47:28 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Date: Mon, 19 Jul 2004 11:47:50 +0200 From: Alexander Leidinger To: Doug Rabson Message-Id: <20040719114750.63c2dd2b@Magellan.Leidinger.net> In-Reply-To: <200407182104.53221.dfr@nlsystems.com> References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> X-Mailer: Sylpheed-Claws 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-ID: VT0SliZbrex24sDOaY1tWUgptEWC5UNFgalisPeanLuQ1KYogrupUh@t-dialin.net cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org cc: Andrew Gallatin Subject: Re: Excellent job on the firewire 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, 19 Jul 2004 09:47:40 -0000 On Sun, 18 Jul 2004 21:04:53 +0100 Doug Rabson wrote: > > It would be nice to remove my Comtrol Rocketport serial card, and the > > 8 serial cables leading across the middle of the room to my shelf of > > machines and replace it with one firewire cable leading to a firewire > > hub. But, as a firewire newbie, I have some questions: > > > > 1) Is any firewire PCI adapter just as good as any other in terms of > > performance, and FreeBSD support? (prices seem to range from $10 > > to $100) > > Any should do about as well as any other. I probably wouldn't want to > spend more than ~$50 on one. I got a 1394a one for ~19 EUR. It has two external connectors, and one internal one (all 3 are 6pin connectors). Included was a cable with 6-6 (the large ones) connectors, and a cable with 6-4 connectors (thats one side with large connectors and one side with small connectors). I only used it with my DVD burner so far, but I can confirm the "it just works" behavior. :-) Bye, Alexander. -- I'm available to get hired (preferred in .lu). http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 15:38: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 2FC1216A4CE for ; Sun, 18 Jul 2004 15:38:23 +0000 (GMT) Received: from asmtp-a063f29.pas.sa.earthlink.net (asmtp-a063f29.pas.sa.earthlink.net [207.217.120.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24EE043D39 for ; Sun, 18 Jul 2004 15:38:23 +0000 (GMT) (envelope-from welchsm@earthlink.net) Received: from [66.173.16.126] (helo=NitroPhys.welchsmnet.net) (TLSv1:AES256-SHA:256) (Exim 4.34) id 1BmDk5-0004st-Ed; Sun, 18 Jul 2004 08:38:22 -0700 Received: from NitroPhys.welchsmnet.net (localhost [127.0.0.1]) i6IFbd2F007245; Sun, 18 Jul 2004 10:37:39 -0500 (CDT) (envelope-from welchsm@localhost.welchsmnet.net) Received: (from welchsm@localhost)i6IFbcPM007244; Sun, 18 Jul 2004 10:37:38 -0500 (CDT) (envelope-from welchsm) Date: Sun, 18 Jul 2004 10:37:38 -0500 From: Sean Welch To: segobi@gmx.de Message-ID: <20040718153738.GA7226@NitroPhys.welchsmnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i X-ELNK-Trace: 15d86f98c8ef8acad780f4a490ca69564776905774d2ac4b70337389433438d2de14f3602745546a350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.173.16.126 X-Mailman-Approved-At: Mon, 19 Jul 2004 11:42:09 +0000 cc: freebsd-current@freebsd.org Subject: Re: xfce4 help X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Sean_Welch@alum.wofford.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jul 2004 15:38:23 -0000 Sebastian, why don't you try contacting the fellow who posted that screenshot? The site attributes it to one Jimmie James who has posted a message here: http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=200401172230.i0HMUI9Y042286%40freefall.freebsd.org.lucky.freebsd.bugs&rnum=10&prev=/groups%3Fq%3Djimmiejaz%26hl%3Den%26lr%3D%26ie%3DUTF-8%26sa%3DN%26tab%3Dwg You should be able to reach him at the address listed there (seems recent enough to be a viable address). If not, you should be able to do some digging in the mail archives to track him down... Good luck! Sean > Hi! > > I know this may be a little O.T. but im quite desperate... > Maybe someone can help me to find this original desktop wallpaper > for > freebsd because i like it so much: > http://xfce.org/images/screenshots/jimmiejaz_26122003.jpg > > Thank you very much for any help! > > Sebastian From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 12:03: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 EB7A116A4CE for ; Mon, 19 Jul 2004 12:03:05 +0000 (GMT) Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA82543D5A for ; Mon, 19 Jul 2004 12:03:05 +0000 (GMT) (envelope-from tlambert2@mindspring.com) Received: from [192.168.167.39] (helo=wamui01.slb.atl.earthlink.net) by granger.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1BmWqj-0005MA-00; Mon, 19 Jul 2004 08:02:29 -0400 Message-ID: <27293807.1090238549091.JavaMail.root@wamui01.slb.atl.earthlink.net> Date: Mon, 19 Jul 2004 05:02:28 -0700 (GMT-07:00) From: Terry Lambert To: Xin LI , current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Earthlink Zoo Mail 1.0 Subject: Re: About ISC-cron X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Terry Lambert List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2004 12:03:06 -0000 Xin LI wrote: > I have Google'd the mailing list and found no discussion explaining why > we have not upgraded our cron and friends. Is there any discussion I > have missed? In other words, should I make these work a port, or a diff > against src/, when I have finished the whole thing? Be careful that you do not bring back a historical Berkley DB problem that used to bite people using cron. The problem was related to the cron program mapping in the database pages, and then returning a pointer to the record itself for getpwent. The mapping didn't expect whar cron then did, which was modify the record in place, not realizing that the passwd database entry being returned was not pointing to a static data area. Technically, this is bogus, and we should probably copy the returned entry to a static save area so that code that tries to out-clever itself won't end up with its foot shot off. Anyway, as a result, run cron long enough, it would stomp a page from the password database on random files occasionally. This was a problem on InterJets for Whistle; since we had a crontab entry that ran "newsyslog" once a second, it was almost always the crontab itself that got stomped. Our "fix" for this on th InterJet was a kludge to rebuild the crontab on reboot, in case it had been corrupted (the underlying VM issue was about impossible to identify, given the circumstances where it would reproduce being so rare). I believe FreeBSD worked around this issue in cron itself; if so, you would need to pull it forward (I'm pretty sure the corruption issue itself was taken care of, but I can't guarantee it). The InterJet approach was a kludge because the first thing you noticed to tell you there was a problem was that your logfiles filld up, and "newsyslog" was/is not smart enough to recreate history and break up huge log files, once they existed. Another issue you might want to deal with is use of numeric user identifiers should be allowed/preferred, with the alpha ones being more of a comment. The issue here is that if you are binding to another server for your password database, cron is started early enough that users not in the local passwd file that come from that server won't be resolved until that server runs. I'm pretty sure that the Samba name services, and also potentially the LDAP name services, are started later than cron itself is started. Generating them from the names after a contab -e would probably fix things transparently enough. -- Terr From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 13: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 B853116A4CE for ; Mon, 19 Jul 2004 13:57:31 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C52B43D54 for ; Mon, 19 Jul 2004 13:57:31 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 21671 invoked from network); 19 Jul 2004 13:57:31 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 19 Jul 2004 13:57:30 -0000 Received: from slimer.baldwin.cx (slimer.baldwin.cx [192.168.0.16]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i6JDv582012229; Mon, 19 Jul 2004 09:57:27 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Bosko Milekic Date: Mon, 19 Jul 2004 09:57:30 -0400 User-Agent: KMail/1.6 References: <20040717193351.GA83772@freefall.freebsd.org> In-Reply-To: <20040717193351.GA83772@freefall.freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407190957.30459.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Brian Fundakowski Feldman cc: current@FreeBSD.org cc: "M. Warner Losh" Subject: Re: pccbb crashes when detaching (unsafe interrupt handler) 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, 19 Jul 2004 13:57:31 -0000 On Saturday 17 July 2004 03:33 pm, Bosko Milekic wrote: > Brian Feldman wrote: > >>From currentish kern_intr.c: > > > > if ((ih->ih_flags & IH_DEAD) != 0) { > > mtx_lock(&ithd->it_lock); > > TAILQ_REMOVE(&ithd->it_handlers, ih, > > ih_next); > > wakeup(ih); > > mtx_unlock(&ithd->it_lock); > > goto restart; > > } > >We add a flag IH_PIN: > > if ((ih->ih_flags & (IH_DEAD | IH_PIN)) != 0) { > > if ((ih->ih_flags & IH_DEAD) == 0) { > > wakeup(ih); > > continue; > > } > > mtx_lock(&ithd->it_lock); > > TAILQ_REMOVE(&ithd->it_handlers, > > ih, ih_next); > > wakeup(ih); > > mtx_unlock(&ithd->it_lock); > > goto restart; > > } > > Neither -current nor your version should be holding the ithd lock > across the wakeup(). Yes, in general there are (low-priority) changes to reduce the assertions for cv and sleep wakeups to not assert that the condition protecting lock is held and to change code like this to not hold the lock across the wakeup. -- 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 Jul 19 13:58: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 6AE6216A4CE for ; Mon, 19 Jul 2004 13:58:54 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1438543D46 for ; Mon, 19 Jul 2004 13:58:54 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6JDwNGo049871; Mon, 19 Jul 2004 09:58:23 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6JDwNaS049868; Mon, 19 Jul 2004 09:58:23 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 19 Jul 2004 09:58:23 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Willem Jan Withagen In-Reply-To: <11e601c46d5c$d9db1910$471b3dd4@digiware.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 fromzone0xffffff007fed4780(Mbuf) 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, 19 Jul 2004 13:58:54 -0000 On Mon, 19 Jul 2004, Willem Jan Withagen wrote: > > I'll starts some more tests before I'm of to bed. > > This mornings result: > ==== > System call getdirentries returning with the following locks held: > exclusive sleep mutex bdone lock r = 0 (0xffffffff805fd080) locked @ /home2/src/ > sys/kern/vfs_bio.c:3767 > panic: witness_warn > cpuid = 0; > KDB: stack backtrace: > kdspin lock sched lock held by 0xffffff007b6cc940 for > 5 seconds > panic: spin lock held too long > cpuid = 0; > KDB: enter: panic > ==== > > But no way to get into the debugger. Does not look like it is much > network related??? Doesn't look very network related, although it could be that increased concurrency and lack of waiting on Giant open up a race of some sort. Can you confirm "options DDB" and "options KDB" are both in your kernel config? You may want to consider commenting out "#define PREEMPTION" in the copy of params.h for the architecture you're running on and see if that helps. Won't help interrupt processing latency, but probably won't hurt server throughput, and your box is a server box so it might be worth trying. 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 Jul 19 14:24: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 ABB8416A4CE; Mon, 19 Jul 2004 14:24:07 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC17F43D45; Mon, 19 Jul 2004 14:24:06 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6JEMHsD080669; Mon, 19 Jul 2004 16:22:17 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <138001c46d9a$e2eadb10$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Robert Watson" References: Date: Mon, 19 Jul 2004 16:15:46 +0200 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.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 fromzone0xffffff007fed4780(Mbuf) 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, 19 Jul 2004 14:24:07 -0000 From: "Robert Watson" > On Mon, 19 Jul 2004, Willem Jan Withagen wrote: > > > > I'll starts some more tests before I'm of to bed. > > > > This mornings result: > > ==== > > System call getdirentries returning with the following locks held: > > exclusive sleep mutex bdone lock r = 0 (0xffffffff805fd080) locked @ /home2/src/ > > sys/kern/vfs_bio.c:3767 > > panic: witness_warn > > cpuid = 0; > > KDB: stack backtrace: > > kdspin lock sched lock held by 0xffffff007b6cc940 for > 5 seconds > > panic: spin lock held too long > > cpuid = 0; > > KDB: enter: panic > > ==== > > > > But no way to get into the debugger. Does not look like it is much > > network related??? > > Doesn't look very network related, although it could be that increased > concurrency and lack of waiting on Giant open up a race of some sort. Can > you confirm "options DDB" and "options KDB" are both in your kernel > config? You may want to consider commenting out "#define PREEMPTION" in > the copy of params.h for the architecture you're running on and see if > that helps. Won't help interrupt processing latency, but probably won't > hurt server throughput, and your box is a server box so it might be worth > trying. Well to box is actually just a toy in my office.... :) And yes it is definitly disk-IO bound.... But I'll take PREEMPTION out if you want. have to think about doing it again it when I cvsup again.. And yes, both DDB and KDB are in... I'm also on the am64 list discussing the fact that 1 out of 3 times I do not get a db> prompt. # Debugging for use in -current options KDB # Enable kernel debugger support. options KDB_TRACE options DDB # Support DDB. options GDB # Support remote GDB. options INVARIANTS # Enable calls of extra sanity checking options INVARIANT_SUPPORT # Extra sanity checks of internal struct options WITNESS # Enable checks to detect deadlocks and options WITNESS_SKIPSPIN # Don't run witness on spinlocks for spe --WjW From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 14:57: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 7E5F616A4CE for ; Mon, 19 Jul 2004 14:57:47 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30FC743D4C for ; Mon, 19 Jul 2004 14:57:47 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id 95966ACAFB; Mon, 19 Jul 2004 16:57:45 +0200 (CEST) Date: Mon, 19 Jul 2004 16:57:45 +0200 From: Pawel Jakub Dawidek To: freebsd-current@freebsd.org Message-ID: <20040719145745.GH57678@darkness.comp.waw.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3ecMC0kzqsE2ddMN" Content-Disposition: inline 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 Subject: Unloading USB driver while device is attached. 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, 19 Jul 2004 14:57:47 -0000 --3ecMC0kzqsE2ddMN Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello. Could someone investigate what's going on for the situation from the subject? This panic is trivial to reproduce: # kldload umass.ko # kldunload umass # kldload umass It is not umass related! I think this problem is in our USB implementation. One more note with could be helpful. When device is already inserted and I load USB driver, _match isn't called, but when driver was unloaded while device was in and it is loaded again (as in my example) _match is called and we have a problem, because there are some stale data, I think (not everything is cleaned up on kldunload?). Ok, one more note. You can also set 'break _match' in DDB and try to compare backtraces when device is removed while driver is loaded and when you unload USB driver. --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --3ecMC0kzqsE2ddMN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA++FpForvXbEpPzQRAtk4AKCB8Y3dJ4lrK6DKCjyhl44nIftJJwCfaLSH PgDklVxfMdW8o9OfFhj7DUM= =ib6s -----END PGP SIGNATURE----- --3ecMC0kzqsE2ddMN-- From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 15:23: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 968B616A4CF for ; Mon, 19 Jul 2004 15:23:12 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E60143D4C for ; Mon, 19 Jul 2004 15:23:12 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 29627 invoked from network); 19 Jul 2004 15:23:12 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 19 Jul 2004 15:23:11 -0000 Received: from 10.50.41.229 (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i6JFN6Cc012734; Mon, 19 Jul 2004 11:23:07 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org, noackjr@alumni.rice.edu User-Agent: KMail/1.6 References: <40F752A1.8020705@alumni.rice.edu> <40F76BF0.1000108@alumni.rice.edu> In-Reply-To: <40F76BF0.1000108@alumni.rice.edu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406301118.33680.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Eric Anderson cc: Robert Watson Subject: Re: ACPI degrading.. ? 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: , Date: Mon, 19 Jul 2004 15:23:12 -0000 X-Original-Date: Wed, 30 Jun 2004 11:18:33 -0400 X-List-Received-Date: Mon, 19 Jul 2004 15:23:12 -0000 On Friday 16 July 2004 01:47 am, Jon Noack wrote: > On 07/15/04 22:59, Jon Noack wrote: > > On 07/15/04 22:49, Robert Watson wrote: > >> On Thu, 15 Jul 2004, Jon Noack wrote: > >>> Come to think of it, all of my hard lockups were when Firefox was > >>> running. I think (some of) the issues native preemption uncovered > >>> are related to threading. In any case, I commented out "#define > >>> PREEMPTION" in src/sys//include/param.h and rebuilt my kernel > >>> so it would stay up for more than 30 minutes. > >> > >> I've also drawn the same conclusion -- to trigger the hangs, I run MySQL > >> with a threaded benchmark. Otherwise, things seem fairly stable on my > >> test boxes. Could you try running with PREEMPTION and using libthr > >> instead of libkse and see if you get the same result? > > > > I'm rebuilding my kernel with PREEMPTION and will add the following > > "global" values to /etc/libmap.conf before I reboot: > > libpthread.so.1 libthr.so.1 > > libpthread.so libthr.so > > > > I'll let you know how things pan out -- shouldn't be too long. > > Worked great with Firefox until I started XMMS. Everything was fine > when I started playing an mp3, but it locked up hard when I switched to > another desktop (had a Firefox window on the desktop I was switching to; > it painted the Firefox widgets but hadn't repainted the webpage I was > viewing before the lockup). > > Looks like it's thread library independent too. Try this patch. It fixed all my lockups with xmms in KDE on Friday: --- //depot/projects/smpng/sys/i386/i386/intr_machdep.c 2004/07/02 20:28:06 +++ //depot/user/jhb/preemption/i386/i386/intr_machdep.c 2004/07/16 20:14:26 @@ -204,6 +204,8 @@ } isrc->is_pic->pic_eoi_source(isrc); error = 0; + /* XXX */ + td->td_pflags &= ~TDP_OWEPREEMPT; critical_exit(); } else { /* -- 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 Jul 19 15:23: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 AB63816A4CE for ; Mon, 19 Jul 2004 15:23:14 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 887A243D54 for ; Mon, 19 Jul 2004 15:23:14 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 29722 invoked from network); 19 Jul 2004 15:23:14 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 19 Jul 2004 15:23:13 -0000 Received: from 10.50.41.229 (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i6JFN6Cd012734; Mon, 19 Jul 2004 11:23:10 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org User-Agent: KMail/1.6 References: <200407152223.i6FMNRV2001315@sakura.ninth-nine.com> <200407152330.i6FNU5NQ003006@sakura.ninth-nine.com> <200407161811.i6GIBlIi095775@sakura.ninth-nine.com> In-Reply-To: <200407161811.i6GIBlIi095775@sakura.ninth-nine.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406301124.22611.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Norikatsu Shigemura cc: current@FreeBSD.org Subject: Re: panic at turnstile_wait (Re: panic at sched_add_internal) 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: , Date: Mon, 19 Jul 2004 15:23:14 -0000 X-Original-Date: Wed, 30 Jun 2004 11:24:22 -0400 X-List-Received-Date: Mon, 19 Jul 2004 15:23:14 -0000 On Friday 16 July 2004 02:11 pm, Norikatsu Shigemura wrote: > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > - - [thread 100124] > > Stopped at turnstile_wait+0x17a: movl %eax,0x10(%edx) > > db> trace > > turnstile_wait(c301e340,c0877f40,c36e4420,c0877f40,f9) at > > turnstile_wait+0x17a _mtx_lock_sleep(c0877f40,0,c07bd610,f9,0) at > > _mtx_lock_sleep+0x125 _mtx_lock_flags(c0877f40,0,c07bd610,f9,0) at > > _mtx_lock_flags+0x64 > > [...] > > > --> LIST_INSERT_HEAD(&ts->ts_free, td->td_turnstile, ts_hash); > > MPASS(owner == ts->ts_owner); > > } > > td->td_turnstile = NULL; > > [...] > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > - - > > Same panic has happend at same place on new current (+1day). Do you have INVARIANTS turned on? Also, can you capture the actual panic message? If you do have INVARIANTS on, then it seems that pointers are magically changing to NULL after the assertion check. I'd be worried about bad memory. -- 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 Jul 19 15:23: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 D85DA16A4CE for ; Mon, 19 Jul 2004 15:23:14 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA5E643D55 for ; Mon, 19 Jul 2004 15:23:14 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 29722 invoked from network); 19 Jul 2004 15:23:14 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 19 Jul 2004 15:23:13 -0000 Received: from 10.50.41.229 (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i6JFN6Cd012734; Mon, 19 Jul 2004 11:23:10 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org User-Agent: KMail/1.6 References: <200407152223.i6FMNRV2001315@sakura.ninth-nine.com> <200407152330.i6FNU5NQ003006@sakura.ninth-nine.com> <200407161811.i6GIBlIi095775@sakura.ninth-nine.com> In-Reply-To: <200407161811.i6GIBlIi095775@sakura.ninth-nine.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406301124.22611.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Norikatsu Shigemura cc: current@FreeBSD.org Subject: Re: panic at turnstile_wait (Re: panic at sched_add_internal) 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: , Date: Mon, 19 Jul 2004 15:23:15 -0000 X-Original-Date: Wed, 30 Jun 2004 11:24:22 -0400 X-List-Received-Date: Mon, 19 Jul 2004 15:23:15 -0000 On Friday 16 July 2004 02:11 pm, Norikatsu Shigemura wrote: > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > - - [thread 100124] > > Stopped at turnstile_wait+0x17a: movl %eax,0x10(%edx) > > db> trace > > turnstile_wait(c301e340,c0877f40,c36e4420,c0877f40,f9) at > > turnstile_wait+0x17a _mtx_lock_sleep(c0877f40,0,c07bd610,f9,0) at > > _mtx_lock_sleep+0x125 _mtx_lock_flags(c0877f40,0,c07bd610,f9,0) at > > _mtx_lock_flags+0x64 > > [...] > > > --> LIST_INSERT_HEAD(&ts->ts_free, td->td_turnstile, ts_hash); > > MPASS(owner == ts->ts_owner); > > } > > td->td_turnstile = NULL; > > [...] > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > - - > > Same panic has happend at same place on new current (+1day). Do you have INVARIANTS turned on? Also, can you capture the actual panic message? If you do have INVARIANTS on, then it seems that pointers are magically changing to NULL after the assertion check. I'd be worried about bad memory. -- 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 Jul 19 15:56: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 0001916A4CE; Mon, 19 Jul 2004 15:56:46 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD34C43D5D; Mon, 19 Jul 2004 15:56:46 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6JFu7wo052218; Mon, 19 Jul 2004 11:56:07 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6JFu7Fe052215; Mon, 19 Jul 2004 11:56:07 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 19 Jul 2004 11:56:06 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: John Baldwin In-Reply-To: <200406301118.33680.jhb@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@FreeBSD.org cc: Eric Anderson Subject: thread+preemption stability improvement (was: Re: ACPI degrading.. ?) 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, 19 Jul 2004 15:56:47 -0000 On Wed, 30 Jun 2004, John Baldwin wrote: > Try this patch. It fixed all my lockups with xmms in KDE on Friday: This patch causes my SMP and UP tests to succeed with PREEMPTION enabled, whereas before they rapidly hung. On SMP I see a small (just under 1%) but consistent improvement in query throughput with MySQL, and on UP I see a small (just under 1%) but inconsistent decrease in query throughput with MySQL. The standard deviation on the UP case is almost the same size as the change, but in the SMP case it's 1/4-1/3 the size of the change, FWIW. Can't speak to the latency as the test I'm currently running isn't very latency sensitive, but was very sensitive to the stability issue. I think this patch is definitely worth committing ASAP :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research > > --- //depot/projects/smpng/sys/i386/i386/intr_machdep.c 2004/07/02 20:28:06 > +++ //depot/user/jhb/preemption/i386/i386/intr_machdep.c 2004/07/16 20:14:26 > @@ -204,6 +204,8 @@ > } > isrc->is_pic->pic_eoi_source(isrc); > error = 0; > + /* XXX */ > + td->td_pflags &= ~TDP_OWEPREEMPT; > critical_exit(); > } else { > /* > > -- > 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 Jul 19 15:58: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 6914116A4CF for ; Mon, 19 Jul 2004 15:58:13 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4188943D1D for ; Mon, 19 Jul 2004 15:58:13 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 32376 invoked from network); 19 Jul 2004 15:58:13 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 19 Jul 2004 15:58:12 -0000 Received: from 10.50.41.229 (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i6JFw7r7012948; Mon, 19 Jul 2004 11:58:08 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org User-Agent: KMail/1.6 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: <200406301130.43121.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Robert Watson Subject: Re: spin lock sched lock held by 0xffffff007b712250 for > 5 seconds 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: , Date: Mon, 19 Jul 2004 15:58:13 -0000 X-Original-Date: Wed, 30 Jun 2004 11:30:43 -0400 X-List-Received-Date: Mon, 19 Jul 2004 15:58:13 -0000 On Friday 16 July 2004 12:21 pm, Robert Watson wrote: > On Fri, 16 Jul 2004, Willem Jan Withagen wrote: > > After todays kernelbuild the system seem to be a lot better... > > It can take quite some buildworld abuse, but still: > > > > spin lock sched lock held by 0xffffff007b712250 for > 5 seconds > > panic: spin lock held too long > > cpuid = 1; > > KDB: enter: panic > > > > But I'm not shure what I could/should do now, since the KDB > > introduction. Normally I'd expect to see: db> > > We have trouble entering the debugger when in a critical section/and or > have sched_lock held -- I think this is because we try to halt the other > CPUs and that gets nastily stuck in some form. We need to fix this. > > This could well be a symptom of some of the other hangs we've been seeing, > and I've seen similar things on my test box with preemption enabled. You can hack sys/i386/include/smptests.h (or smptest.h, whichever it is) and comment out CPUSTOP_ONDDBREAK as a hack. I did that recently for some debugging. -- 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 Jul 19 15:58: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 1372216A517 for ; Mon, 19 Jul 2004 15:58:18 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB2AD43D53 for ; Mon, 19 Jul 2004 15:58:15 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 23393 invoked from network); 19 Jul 2004 15:58:15 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 19 Jul 2004 15:58:15 -0000 Received: from 10.50.41.229 (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i6JFw7r8012948; Mon, 19 Jul 2004 11:58:11 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org User-Agent: KMail/1.6 References: <200407162010.i6GKAlUq005647@corona.sajd.net> In-Reply-To: <200407162010.i6GKAlUq005647@corona.sajd.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406301134.09786.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Pawel Worach cc: njl@FreeBSD.org Subject: Re: acpi_timer broken 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: , Date: Mon, 19 Jul 2004 15:58:18 -0000 X-Original-Date: Wed, 30 Jun 2004 11:34:09 -0400 X-List-Received-Date: Mon, 19 Jul 2004 15:58:18 -0000 On Friday 16 July 2004 04:10 pm, Pawel Worach wrote: > Hi, > > Somewhere in the last few days the acpi timecounter is not detected on > my system anymore, the machine is an IBM xSeries 345. > > When it worked it looked like this: > Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x488-0x48b on acpi0 > > Now it looks like this: > acpi_timer0: couldn't allocate I/O resource (port 0x488) > acpi_timer0 port 0x488-0x48b on acpi0 > > Any ideas? This is probably related to the recent ACPI sysresource changes. Try asking njl@ (cc'd) for pointers. Disabling the "sysresource" driver and seeing if that fixes the problem is a good first step. -- 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 Jul 19 16:19: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 2ACFA16A4CF for ; Mon, 19 Jul 2004 16:19:50 +0000 (GMT) Received: from web11405.mail.yahoo.com (web11405.mail.yahoo.com [216.136.131.235]) by mx1.FreeBSD.org (Postfix) with SMTP id F1C4D43D3F for ; Mon, 19 Jul 2004 16:19:49 +0000 (GMT) (envelope-from shizukakudo_99@yahoo.com) Message-ID: <20040719161949.17114.qmail@web11405.mail.yahoo.com> Received: from [218.103.208.129] by web11405.mail.yahoo.com via HTTP; Mon, 19 Jul 2004 09:19:48 PDT Date: Mon, 19 Jul 2004 09:19:48 -0700 (PDT) From: Shizuka Kudo To: Doug Rabson , Andrew Gallatin In-Reply-To: <200407182104.53221.dfr@nlsystems.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Excellent job on the firewire 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, 19 Jul 2004 16:19:50 -0000 Hi, Anyone has experience with the newly added IP over 1394 support, i.e. fwip? I compiled it in with the latest kernel at 17 July, but the box cannot ping with a M$ & linux box. --- Doug Rabson wrote: > On Sunday 18 July 2004 20:54, Andrew Gallatin wrote: > > Doug Rabson writes: > > > On Sunday 18 July 2004 18:51, Andrew Gallatin wrote: > > > > Hi, > > > > > > > > I just wanted to say that I used FreeBSD's firewire and sbp-II > > > > support for the first time this weekend. It seems to be fast > > > > (over 26MB/sec writes, 34MB/sec reads to a LaCie 160GB drive), > > > > and robust. It works well on non-i386 platforms -- I'm using it > > > > to back up an amd64, and to serve as a root device for a > > > > FreeBSD/powerpc machine. > > > > > > > > All in all, it totally exceeded my expectations. Thank you very > > > > much| > > > > > > Wait till you try debugging using gdb over firewire with dcons. An > > > all round positive experience :-) > > > > It would be nice to remove my Comtrol Rocketport serial card, and the > > 8 serial cables leading across the middle of the room to my shelf of > > machines and replace it with one firewire cable leading to a firewire > > hub. But, as a firewire newbie, I have some questions: > > > > 1) Is any firewire PCI adapter just as good as any other in terms of > > performance, and FreeBSD support? (prices seem to range from $10 > > to $100) > > Any should do about as well as any other. I probably wouldn't want to > spend more than ~$50 on one. > > > > > 2) Is dcons usable after a panic (ie, DDB or KDB_TRACE)? Or is it > > only usable for remote-gdb? > > Dcons provides two full duplex streams - one for console and one for > gdb. You can use DDB on the console just like normal. > > > > > 3) Is dcons endian and pointer-size agonstic? Can I run consoles to > > an amd64 and a powerpc box from an x86? > > I haven't actually tried that and I imagine that there might be issues > here and there. Any problems are likely to be in the dconschat program > but that should be pretty easy to fix since its entirely userland. > > > > > 4) Does the loader know about dcons? Eg, can I do "unload boot > > kernel.test" using dcons? > > Actually thats the only downside of dcons. It doesn't cut in until the > firewire controller attaches. It relies on the fact that the fwohci > driver allows access to physical memory from any node on the bus > (implemeted in hardware so you can examine the memory of a hung > machine). The dconschat program uses this feature to access the dcons > ring buffers in the target machine. > > I could imagine a dcons driver in the loader which just enabled physical > access and used some kind of loader trick to hand off the ring buffers > to the kernel dcons driver. It doesn't exist though - say nice things > to the author and he might find the time for it :-) > > _______________________________________________ > 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" > __________________________________ Do you Yahoo!? Vote for the stars of Yahoo!'s next ad campaign! http://advision.webevents.yahoo.com/yahoo/votelifeengine/ From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 16:49: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 D0E6016A4CE for ; Mon, 19 Jul 2004 16:49:25 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id A155E43D4C for ; Mon, 19 Jul 2004 16:49:25 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 23996 invoked from network); 19 Jul 2004 16:49:25 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 19 Jul 2004 16:49:24 -0000 Received: from 10.50.41.229 (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i6JGnKh0013257; Mon, 19 Jul 2004 12:49:20 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org User-Agent: KMail/1.6 References: <40FB8313.5050308@melbpc.org.au> <20040719032535.U32601@pooker.samsco.org> In-Reply-To: <20040719032535.U32601@pooker.samsco.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406301224.59399.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Scott Long Subject: Re: [panic] setrunqueue 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: , Date: Mon, 19 Jul 2004 16:49:25 -0000 X-Original-Date: Wed, 30 Jun 2004 12:24:59 -0400 X-List-Received-Date: Mon, 19 Jul 2004 16:49:25 -0000 On Monday 19 July 2004 05:28 am, Scott Long wrote: > On Mon, 19 Jul 2004, Peter Kostouros wrote: > > Hi > > > > I received a fatal error and hope the following is useful: > > This has been observed often recently. There are some suggestions > floating around privately on how to fix this, but probably the easiest > work-around for now is to undefine PREEMPTION in /sys/i386/include/param.h > I'm expecting to get this resolved in some form in the next 24 hours. This is a different one, some kind of NULL deref. Peter, can you use addr2line or gdb to determine what the file and line number are for 0xc0545485? -- 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 Jul 19 16:52: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 AFEF816A4CE for ; Mon, 19 Jul 2004 16:52:33 +0000 (GMT) Received: from samuelstringham.com (cs666986-52.satx.rr.com [66.69.86.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0877043D31 for ; Mon, 19 Jul 2004 16:52:33 +0000 (GMT) (envelope-from samuel@samuelstringham.com) Received: by laptop.samuelstringham.com (Postfix, from userid 500) id 1E37A34F0D; Mon, 19 Jul 2004 10:26:43 -0500 (CDT) Date: Mon, 19 Jul 2004 10:26:43 -0500 From: Samuel Stringham To: freebsd-current@freebsd.org Message-ID: <20040719152643.GB1640@linux> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Q68bSM7Ycu6FN28Q" Content-Disposition: inline X-Operating-System: "SuSE Linux" User-Agent: Mutt/1.5.6i Subject: Panic while unloadking if_ndis X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Samuel Stringham List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2004 16:52:33 -0000 --Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Long time troller, first time poster. I have a LinkSYS DWL 520+ wireless B PCI card. This is the card with the Broadcom chipset, rather than the earlier 520s with the prism2 chipset. I am pretty sure it is supposed to use the if_ndis driver. However, I am unable to get the driver to work correctly. Upon loading the module, it does not attatch ndis0 to the pci card (I found this by looking at pciconf -lv). I can load and unload the module with no problems. However, if I run 'ifconfig ndis0', it says something along the lines of: ifconfig: interface ndis0 does not exist If I then run 'kldunload if_ndis' I get the following panic: Fatal trap 10: page fault while in kernel mode fault virtual address = 0xc29f90e1 fault code = supervisor read, page not present instruction pointer = 0x8:0xc29f90e1 stack pointer = 0x10:0xe2ea1d0c frame pointer = 0x10:0xe2ea1d1c 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 = 801 (ndis swi) trap number = 12 panic: page fault syncing disks . . . etc. Please excuse any typing mistakes, but I had to fat-finger the above. The error is replicable on my machine. Attached is a transcript of my loading the module, and looking at pciconf. Also in there is my full dmesg to aid in finding the possible problem. My ndis_driver_data.h was generated with the ndiscvt from -CURRENT as of 1900 CDT yesterday. In fact everything (world and kernel) were both built from the -CURRENT as of 1900 yesterday. The files used for my ndiscvt were WMP11NDS.[sys|inf]. Please help me get this wonderful ndis-based card working correctly. Best regards, Samuel Stringham --Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=transcript Content-Transfer-Encoding: quoted-printable Script started on Sun Jul 18 21:15:53 2004 =0D=1B[31m[root: root]#=1B[00m kldstat=0D Id Refs Address Size Name=0D 1 7 0xc0400000 5acb28 kernel=0D 2 1 0xc09ad000 1b378 linux.ko=0D 3 14 0xc09c9000 50d74 acpi.ko=0D =0D=1B[31m[root: root]#=1B[00m pciconfi=08 =08 -lv=0D agp0@pci0:0:0: class=3D0x060000 card=3D0x00000000 chip=3D0x07301039 rev=3D0= x02 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS 730 Host-to-PCI Bridge'=0D class =3D bridge=0D subclass =3D HOST-PCI=0D atapci0@pci0:0:1: class=3D0x010180 card=3D0x55131039 chip=3D0x55131039 rev= =3D0xd0 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS5513 EIDE Controller (A,B step)'=0D class =3D mass storage=0D subclass =3D ATA=0D isab0@pci0:1:0: class=3D0x060100 card=3D0x00000000 chip=3D0x00081039 rev=3D= 0x00 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS PCI to ISA Bridge (LPC Bridge)'=0D class =3D bridge=0D subclass =3D PCI-ISA=0D sis0@pci0:1:1: class=3D0x020000 card=3D0x09001039 chip=3D0x09001039 rev=3D0= x82 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS900 Fast Ethernet/Home Networking Ctrlr'=0D class =3D network=0D subclass =3D ethernet=0D ohci0@pci0:1:2: class=3D0x0c0310 card=3D0x70011039 chip=3D0x70011039 rev=3D= 0x07 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS5597/8 Universal Serial Bus Controller'=0D class =3D serial bus=0D subclass =3D USB=0D ohci1@pci0:1:3: class=3D0x0c0310 card=3D0x70001039 chip=3D0x70011039 rev=3D= 0x07 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS5597/8 Universal Serial Bus Controller'=0D class =3D serial bus=0D subclass =3D USB=0D pcm0@pci0:1:4: class=3D0x040100 card=3D0x70181039 chip=3D0x70181039 rev=3D0= x02 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS7018 PCI Audio Accelerator'=0D class =3D multimedia=0D subclass =3D audio=0D pcib1@pci0:2:0: class=3D0x060400 card=3D0x00000000 chip=3D0x00011039 rev=3D= 0x00 hdr=3D0x01=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS 530 Virtual PCI-to-PCI bridge (AGP)'=0D class =3D bridge=0D subclass =3D PCI-PCI=0D none0@pci0:9:0: class=3D0x020000 card=3D0x00201737 chip=3D0x212017fe rev=3D= 0x00 hdr=3D0x00=0D vendor =3D 'InProComm Inc'=0D class =3D network=0D subclass =3D ethernet=0D none1@pci0:11:0: class=3D0x040000 card=3D0x00031002 chip=3D0x036e109e rev= =3D0x11 hdr=3D0x00=0D vendor =3D 'Brooktree Corporation'=0D device =3D 'Bt878 MediaStream Controller'=0D class =3D multimedia=0D subclass =3D video=0D none2@pci0:11:1: class=3D0x048000 card=3D0x00031002 chip=3D0x0878109e rev= =3D0x11 hdr=3D0x00=0D vendor =3D 'Brooktree Corporation'=0D device =3D 'Bt878/Fusion878A Video Capture (Audio Section)'=0D class =3D multimedia=0D none3@pci1:0:0: class=3D0x030000 card=3D0x7161174b chip=3D0x51571002 rev=3D= 0x00 hdr=3D0x00=0D vendor =3D 'ATI Technologies Inc.'=0D device =3D 'Radeon 7500 Series (RV200)'=0D class =3D display=0D subclass =3D VGA=0D =0D=1B[31m[root: root]#=1B[00m kldload /boot/ker=07nel/if_n=07dis.ko =0D =0D=1B[31m[root: root]#=1B[00m =1B[Kkldstat=0D Id Refs Address Size Name=0D 1 12 0xc0400000 5acb28 kernel=0D 2 1 0xc09ad000 1b378 linux.ko=0D 3 14 0xc09c9000 50d74 acpi.ko=0D 4 1 0xc291d000 1a000 if_ndis.ko=0D 5 1 0xc2937000 d000 ndis.ko=0D =0D=1B[31m[root: root]#=1B[00m pciconf=08 =08f -v=08 =08lv=0D agp0@pci0:0:0: class=3D0x060000 card=3D0x00000000 chip=3D0x07301039 rev=3D0= x02 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS 730 Host-to-PCI Bridge'=0D class =3D bridge=0D subclass =3D HOST-PCI=0D atapci0@pci0:0:1: class=3D0x010180 card=3D0x55131039 chip=3D0x55131039 rev= =3D0xd0 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS5513 EIDE Controller (A,B step)'=0D class =3D mass storage=0D subclass =3D ATA=0D isab0@pci0:1:0: class=3D0x060100 card=3D0x00000000 chip=3D0x00081039 rev=3D= 0x00 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS PCI to ISA Bridge (LPC Bridge)'=0D class =3D bridge=0D subclass =3D PCI-ISA=0D sis0@pci0:1:1: class=3D0x020000 card=3D0x09001039 chip=3D0x09001039 rev=3D0= x82 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS900 Fast Ethernet/Home Networking Ctrlr'=0D class =3D network=0D subclass =3D ethernet=0D ohci0@pci0:1:2: class=3D0x0c0310 card=3D0x70011039 chip=3D0x70011039 rev=3D= 0x07 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS5597/8 Universal Serial Bus Controller'=0D class =3D serial bus=0D subclass =3D USB=0D ohci1@pci0:1:3: class=3D0x0c0310 card=3D0x70001039 chip=3D0x70011039 rev=3D= 0x07 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS5597/8 Universal Serial Bus Controller'=0D class =3D serial bus=0D subclass =3D USB=0D pcm0@pci0:1:4: class=3D0x040100 card=3D0x70181039 chip=3D0x70181039 rev=3D0= x02 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS7018 PCI Audio Accelerator'=0D class =3D multimedia=0D subclass =3D audio=0D pcib1@pci0:2:0: class=3D0x060400 card=3D0x00000000 chip=3D0x00011039 rev=3D= 0x00 hdr=3D0x01=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS 530 Virtual PCI-to-PCI bridge (AGP)'=0D class =3D bridge=0D subclass =3D PCI-PCI=0D none0@pci0:9:0: class=3D0x020000 card=3D0x00201737 chip=3D0x212017fe rev=3D= 0x00 hdr=3D0x00=0D vendor =3D 'InProComm Inc'=0D class =3D network=0D subclass =3D ethernet=0D none1@pci0:11:0: class=3D0x040000 card=3D0x00031002 chip=3D0x036e109e rev= =3D0x11 hdr=3D0x00=0D vendor =3D 'Brooktree Corporation'=0D device =3D 'Bt878 MediaStream Controller'=0D class =3D multimedia=0D subclass =3D video=0D none2@pci0:11:1: class=3D0x048000 card=3D0x00031002 chip=3D0x0878109e rev= =3D0x11 hdr=3D0x00=0D vendor =3D 'Brooktree Corporation'=0D device =3D 'Bt878/Fusion878A Video Capture (Audio Section)'=0D class =3D multimedia=0D none3@pci1:0:0: class=3D0x030000 card=3D0x7161174b chip=3D0x51571002 rev=3D= 0x00 hdr=3D0x00=0D vendor =3D 'ATI Technologies Inc.'=0D device =3D 'Radeon 7500 Series (RV200)'=0D class =3D display=0D subclass =3D VGA=0D =0D=1B[31m[root: root]#=1B[00m pciconf -lv=08=08=08=08=08=08=08=08=08=08=08= =1B[4Pkldstat=08=08=08=08=08=08=08pciconf -lv=08=08=08=08=08=08=08=08=08=08= =08=1B[K=07kldunload if_ndis=0D =0D=1B[31m[root: root]#=1B[00m =1B[Kkldstat=0D Id Refs Address Size Name=0D 1 7 0xc0400000 5acb28 kernel=0D 2 1 0xc09ad000 1b378 linux.ko=0D 3 14 0xc09c9000 50d74 acpi.ko=0D =0D=1B[31m[root: root]#=1B[00m pciconf -lv=0D agp0@pci0:0:0: class=3D0x060000 card=3D0x00000000 chip=3D0x07301039 rev=3D0= x02 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS 730 Host-to-PCI Bridge'=0D class =3D bridge=0D subclass =3D HOST-PCI=0D atapci0@pci0:0:1: class=3D0x010180 card=3D0x55131039 chip=3D0x55131039 rev= =3D0xd0 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS5513 EIDE Controller (A,B step)'=0D class =3D mass storage=0D subclass =3D ATA=0D isab0@pci0:1:0: class=3D0x060100 card=3D0x00000000 chip=3D0x00081039 rev=3D= 0x00 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS PCI to ISA Bridge (LPC Bridge)'=0D class =3D bridge=0D subclass =3D PCI-ISA=0D sis0@pci0:1:1: class=3D0x020000 card=3D0x09001039 chip=3D0x09001039 rev=3D0= x82 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS900 Fast Ethernet/Home Networking Ctrlr'=0D class =3D network=0D subclass =3D ethernet=0D ohci0@pci0:1:2: class=3D0x0c0310 card=3D0x70011039 chip=3D0x70011039 rev=3D= 0x07 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS5597/8 Universal Serial Bus Controller'=0D class =3D serial bus=0D subclass =3D USB=0D ohci1@pci0:1:3: class=3D0x0c0310 card=3D0x70001039 chip=3D0x70011039 rev=3D= 0x07 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS5597/8 Universal Serial Bus Controller'=0D class =3D serial bus=0D subclass =3D USB=0D pcm0@pci0:1:4: class=3D0x040100 card=3D0x70181039 chip=3D0x70181039 rev=3D0= x02 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS7018 PCI Audio Accelerator'=0D class =3D multimedia=0D subclass =3D audio=0D pcib1@pci0:2:0: class=3D0x060400 card=3D0x00000000 chip=3D0x00011039 rev=3D= 0x00 hdr=3D0x01=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS 530 Virtual PCI-to-PCI bridge (AGP)'=0D class =3D bridge=0D subclass =3D PCI-PCI=0D none0@pci0:9:0: class=3D0x020000 card=3D0x00201737 chip=3D0x212017fe rev=3D= 0x00 hdr=3D0x00=0D vendor =3D 'InProComm Inc'=0D class =3D network=0D subclass =3D ethernet=0D none1@pci0:11:0: class=3D0x040000 card=3D0x00031002 chip=3D0x036e109e rev= =3D0x11 hdr=3D0x00=0D vendor =3D 'Brooktree Corporation'=0D device =3D 'Bt878 MediaStream Controller'=0D class =3D multimedia=0D subclass =3D video=0D none2@pci0:11:1: class=3D0x048000 card=3D0x00031002 chip=3D0x0878109e rev= =3D0x11 hdr=3D0x00=0D vendor =3D 'Brooktree Corporation'=0D device =3D 'Bt878/Fusion878A Video Capture (Audio Section)'=0D class =3D multimedia=0D none3@pci1:0:0: class=3D0x030000 card=3D0x7161174b chip=3D0x51571002 rev=3D= 0x00 hdr=3D0x00=0D vendor =3D 'ATI Technologies Inc.'=0D device =3D 'Radeon 7500 Series (RV200)'=0D class =3D display=0D subclass =3D VGA=0D =0D=1B[31m[root: root]#=1B[00m kldload if_ndis.=08 =08=08 =08=08 =08=08 =08= =08 =08=08 =08=08 =08=08 =08/boot/ker=07nel/if=07_ndis.ko =0D =0D=1B[31m[root: root]#=1B[00m =1B[Kkldstat=0D Id Refs Address Size Name=0D 1 12 0xc0400000 5acb28 kernel=0D 2 1 0xc09ad000 1b378 linux.ko=0D 3 14 0xc09c9000 50d74 acpi.ko=0D 5 1 0xc291d000 1a000 if_ndis.ko=0D 6 1 0xc2937000 d000 ndis.ko=0D =0D=1B[31m[root: root]#=1B[00m pcif=08 =08conf -lv=0D agp0@pci0:0:0: class=3D0x060000 card=3D0x00000000 chip=3D0x07301039 rev=3D0= x02 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS 730 Host-to-PCI Bridge'=0D class =3D bridge=0D subclass =3D HOST-PCI=0D atapci0@pci0:0:1: class=3D0x010180 card=3D0x55131039 chip=3D0x55131039 rev= =3D0xd0 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS5513 EIDE Controller (A,B step)'=0D class =3D mass storage=0D subclass =3D ATA=0D isab0@pci0:1:0: class=3D0x060100 card=3D0x00000000 chip=3D0x00081039 rev=3D= 0x00 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS PCI to ISA Bridge (LPC Bridge)'=0D class =3D bridge=0D subclass =3D PCI-ISA=0D sis0@pci0:1:1: class=3D0x020000 card=3D0x09001039 chip=3D0x09001039 rev=3D0= x82 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS900 Fast Ethernet/Home Networking Ctrlr'=0D class =3D network=0D subclass =3D ethernet=0D ohci0@pci0:1:2: class=3D0x0c0310 card=3D0x70011039 chip=3D0x70011039 rev=3D= 0x07 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS5597/8 Universal Serial Bus Controller'=0D class =3D serial bus=0D subclass =3D USB=0D ohci1@pci0:1:3: class=3D0x0c0310 card=3D0x70001039 chip=3D0x70011039 rev=3D= 0x07 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS5597/8 Universal Serial Bus Controller'=0D class =3D serial bus=0D subclass =3D USB=0D pcm0@pci0:1:4: class=3D0x040100 card=3D0x70181039 chip=3D0x70181039 rev=3D0= x02 hdr=3D0x00=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS7018 PCI Audio Accelerator'=0D class =3D multimedia=0D subclass =3D audio=0D pcib1@pci0:2:0: class=3D0x060400 card=3D0x00000000 chip=3D0x00011039 rev=3D= 0x00 hdr=3D0x01=0D vendor =3D 'Silicon Integrated Systems (SiS)'=0D device =3D 'SiS 530 Virtual PCI-to-PCI bridge (AGP)'=0D class =3D bridge=0D subclass =3D PCI-PCI=0D none0@pci0:9:0: class=3D0x020000 card=3D0x00201737 chip=3D0x212017fe rev=3D= 0x00 hdr=3D0x00=0D vendor =3D 'InProComm Inc'=0D class =3D network=0D subclass =3D ethernet=0D none1@pci0:11:0: class=3D0x040000 card=3D0x00031002 chip=3D0x036e109e rev= =3D0x11 hdr=3D0x00=0D vendor =3D 'Brooktree Corporation'=0D device =3D 'Bt878 MediaStream Controller'=0D class =3D multimedia=0D subclass =3D video=0D none2@pci0:11:1: class=3D0x048000 card=3D0x00031002 chip=3D0x0878109e rev= =3D0x11 hdr=3D0x00=0D vendor =3D 'Brooktree Corporation'=0D device =3D 'Bt878/Fusion878A Video Capture (Audio Section)'=0D class =3D multimedia=0D none3@pci1:0:0: class=3D0x030000 card=3D0x7161174b chip=3D0x51571002 rev=3D= 0x00 hdr=3D0x00=0D vendor =3D 'ATI Technologies Inc.'=0D device =3D 'Radeon 7500 Series (RV200)'=0D class =3D display=0D subclass =3D VGA=0D =0D=1B[31m[root: root]#=1B[00m dmesg =0D Copyright (c) 1992-2004 The FreeBSD Project.=0D Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994=0D The Regents of the University of California. All rights reserved.=0D FreeBSD 5.2-CURRENT #1: Sun Jul 18 15:35:23 CDT 2004=0D root@home.samuelstringham.com:/usr/obj/usr/src/sys/MYKERNEL=0D WARNING: WITNESS option enabled, expect reduced performance.=0D Timecounter "i8254" frequency 1193182 Hz quality 0=0D CPU: AMD Duron(tm) Processor (945.00-MHz 686-class CPU)=0D Origin =3D "AuthenticAMD" Id =3D 0x631 Stepping =3D 1=0D Features=3D0x183f9ff=0D AMD Features=3D0xc0440000=0D real memory =3D 1073676288 (1023 MB)=0D avail memory =3D 1041203200 (992 MB)=0D npx0: [FAST]=0D npx0: on motherboard=0D npx0: INT 16 interface=0D acpi0: on motherboard=0D acpi0: [GIANT-LOCKED]=0D acpi0: Power Button (fixed)=0D Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000=0D acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0=0D cpu0: on acpi0=0D acpi_button0: on acpi0=0D pcib0: port 0xcf8-0xcff on acpi0=0D pci0: on pcib0=0D agp0: mem 0xd0000000-0xd3ffffff at device 0.0 = on pci0=0D atapci0: port 0xff00-0xff0f,0x376,0x170-0x177,= 0x3f6,0x1f0-0x1f7 at device 0.1 on pci0=0D ata0: at 0x1f0 irq 14 on atapci0=0D ata1: at 0x170 irq 15 on atapci0=0D isab0: at device 1.0 on pci0=0D isa0: on isab0=0D sis0: port 0xd400-0xd4ff mem 0xcfffb000-0xcfffbfff i= rq 5 at device 1.1 on pci0=0D miibus0: on sis0=0D ukphy0: on miibus0=0D ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto=0D sis0: Ethernet address: 00:0a:e6:4b:0c:4d=0D sis0: [GIANT-LOCKED]=0D ohci0: mem 0xcfffc000-0xcfffcfff irq 11 at device= 1.2 on pci0=0D ohci0: [GIANT-LOCKED]=0D usb0: OHCI version 1.0, legacy support=0D usb0: on ohci0=0D usb0: USB revision 1.0=0D uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1=0D uhub0: 3 ports with 3 removable, self powered=0D ums0: Logitech USB Receiver, rev 1.10/9.10, addr 2, iclass 3/1=0D ums0: 5 buttons and Z dir.=0D ohci1: mem 0xcfffd000-0xcfffdfff irq 11 at device= 1.3 on pci0=0D ohci1: [GIANT-LOCKED]=0D usb1: OHCI version 1.0, legacy support=0D usb1: on ohci1=0D usb1: USB revision 1.0=0D uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1=0D uhub1: 3 ports with 3 removable, self powered=0D pcm0: port 0xd800-0xd8ff mem 0xcfffe000-0xcfffefff irq 11 at dev= ice 1.4 on pci0=0D pcm0: =0D pcm0: [GIANT-LOCKED]=0D pcib1: at device 2.0 on pci0=0D pci1: on pcib1=0D pci1: at device 0.0 (no driver attached)=0D pci0: at device 9.0 (no driver attached)=0D pci0: at device 11.0 (no driver attached)=0D pci0: at device 11.1 (no driver attached)=0D acpi_button1: on acpi0=0D atkbdc0: port 0x64,0x60 irq 1 on acpi0=0D atkbd0: irq 1 on atkbdc0=0D kbd0 at atkbd0=0D atkbd0: [GIANT-LOCKED]=0D psm0: irq 12 on atkbdc0=0D psm0: [GIANT-LOCKED]=0D psm0: model IntelliMouse, device ID 3=0D fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3 irq 6 dr= q 2 on acpi0=0D fdc0: I/O to control range incorrect=0D device_attach: fdc0 attach returned 6=0D sio0 port 0x3f8-0x3ff irq 4 on acpi0=0D sio0: type 16550A=0D ppc0 port 0x378-0x37f irq 7 on acpi0=0D ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode=0D ppbus0: on ppc0=0D plip0: on ppbus0=0D lpt0: on ppbus0=0D lpt0: Interrupt-driven port=0D ppi0: on ppbus0=0D fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3 irq 6 dr= q 2 on acpi0=0D fdc0: I/O to control range incorrect=0D device_attach: fdc0 attach returned 6=0D orm0: at iomem 0xd0000-0xd7fff,0xc0000-0xcffff on isa0=0D pmtimer0 on isa0=0D sc0: at flags 0x100 on isa0=0D sc0: VGA <16 virtual consoles, flags=3D0x300>=0D sio1: configured irq 3 not in bitmap of probed irqs 0=0D sio1: port may not be enabled=0D vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0=0D Timecounter "TSC" frequency 945003338 Hz quality 800=0D Timecounters tick every 10.000 msec=0D acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0%=0D ata0-master: DMA limited to UDMA33, non-ATA66 cable or device=0D ad0: 57277MB [116374/16/63] at ata0-master UDMA33=0D ata1-slave: FAILURE - ATAPI_RESET no interrupt=0D acd0: CDRW at ata1-slave PIO4=0D Mounting root from ufs:/dev/ad0s1a=0D WARNING: / was not properly dismounted=0D WARNING: /tmp was not properly dismounted=0D WARNING: /usr was not properly dismounted=0D /usr: mount pending error: blocks 4 files 1=0D WARNING: /var was not properly dismounted=0D link_elf: symbol callout_stop undefined=0D =0D=1B[31m[root: root]#=1B[00m exit=0D exit=0D Script done on Sun Jul 18 21:17:44 2004 --Q68bSM7Ycu6FN28Q-- From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 17:13: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 86CEC16A4CE; Mon, 19 Jul 2004 17:13:07 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79E1443D53; Mon, 19 Jul 2004 17:13:07 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 612FF72DF2; Mon, 19 Jul 2004 10:13:07 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 5C27A72DB5; Mon, 19 Jul 2004 10:13:07 -0700 (PDT) Date: Mon, 19 Jul 2004 10:13:07 -0700 (PDT) From: Doug White To: "Bjoern A. Zeeb" In-Reply-To: Message-ID: <20040719100952.H59702@carver.gumbysoft.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: FreeBSD current mailing list Subject: Re: kldunload if_sk -> LOR & 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, 19 Jul 2004 17:13:07 -0000 On Sun, 18 Jul 2004, Bjoern A. Zeeb wrote: > > At the point where it's actually detaching, once it's detached the methods > > that access its softc, it should drop its softc lock before calling the > > network-level detach routines. > > I think this is handled by dwhite's patch so I should be safe now. > Perhaps someone could work towards committing a cleaned up version of > this patch ? The LOR is the harmless part. The panic is caused by device_delete_child() recursing from skc to sk, and sk_detach() calls device_delete_child() in itself again after freeing its structures (or something like that). My patch should fix this, if not then I have it in my working sources. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 17:23: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 0848516A4CE; Mon, 19 Jul 2004 17:23:17 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id F11B843D46; Mon, 19 Jul 2004 17:23:16 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id E345572DF4; Mon, 19 Jul 2004 10:23:16 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id E058A72DF2; Mon, 19 Jul 2004 10:23:16 -0700 (PDT) Date: Mon, 19 Jul 2004 10:23:16 -0700 (PDT) From: Doug White To: Pawel Jakub Dawidek In-Reply-To: <20040719145745.GH57678@darkness.comp.waw.pl> Message-ID: <20040719102139.N59702@carver.gumbysoft.com> References: <20040719145745.GH57678@darkness.comp.waw.pl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Unloading USB driver while device is attached. 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, 19 Jul 2004 17:23:17 -0000 On Mon, 19 Jul 2004, Pawel Jakub Dawidek wrote: > Hello. > > Could someone investigate what's going on for the situation from the > subject? This panic is trivial to reproduce: > > # kldload umass.ko > > # kldunload umass > # kldload umass > > > It is not umass related! I think this problem is in our USB implementation. Theres a discussion going on in -arch about making kldunload a bit more careful about cleaning up before detaching. In the interim adding a method that just vetos any unload request would prevent this from occuring, but also preclude unloading the driver. :) -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 17:38: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 0A64A16A4CE for ; Mon, 19 Jul 2004 17:38:22 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA4CC43D41 for ; Mon, 19 Jul 2004 17:38:21 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id 9EDBEACAE6; Mon, 19 Jul 2004 19:38:19 +0200 (CEST) Date: Mon, 19 Jul 2004 19:38:19 +0200 From: Pawel Jakub Dawidek To: Doug White Message-ID: <20040719173819.GI57678@darkness.comp.waw.pl> References: <20040719145745.GH57678@darkness.comp.waw.pl> <20040719102139.N59702@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BWWlCdgt6QLN7tv3" Content-Disposition: inline In-Reply-To: <20040719102139.N59702@carver.gumbysoft.com> 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: freebsd-current@freebsd.org Subject: Re: Unloading USB driver while device is attached. 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, 19 Jul 2004 17:38:22 -0000 --BWWlCdgt6QLN7tv3 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 19, 2004 at 10:23:16AM -0700, Doug White wrote: +> Theres a discussion going on in -arch about making kldunload a bit more +> careful about cleaning up before detaching. In the interim adding a +> method that just vetos any unload request would prevent this from +> occuring, but also preclude unloading the driver. :) Yeah, but even on 'kldunload -f' it should be possible to clean up and avoid panic on next load. --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --BWWlCdgt6QLN7tv3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/AcLForvXbEpPzQRAhz7AJ45XeMBTck8+0lvqirKrVx/OkKEnwCgy4Jk 22eile/8IW6+yPo2eQICJ3Y= =OHR9 -----END PGP SIGNATURE----- --BWWlCdgt6QLN7tv3-- From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 17:44: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 1BA2316A4CE; Mon, 19 Jul 2004 17:44:24 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4C1843D41; Mon, 19 Jul 2004 17:44:23 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.0.12] (g4.samsco.home [192.168.0.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6JHoMlE054714; Mon, 19 Jul 2004 11:50:22 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40FC0832.3040805@freebsd.org> Date: Mon, 19 Jul 2004 11:43:14 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20040719145745.GH57678@darkness.comp.waw.pl> <20040719102139.N59702@carver.gumbysoft.com> <20040719173819.GI57678@darkness.comp.waw.pl> In-Reply-To: <20040719173819.GI57678@darkness.comp.waw.pl> 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: Unloading USB driver while device is attached. 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, 19 Jul 2004 17:44:24 -0000 Pawel Jakub Dawidek wrote: > On Mon, Jul 19, 2004 at 10:23:16AM -0700, Doug White wrote: > +> Theres a discussion going on in -arch about making kldunload a bit more > +> careful about cleaning up before detaching. In the interim adding a > +> method that just vetos any unload request would prevent this from > +> occuring, but also preclude unloading the driver. :) > > Yeah, but even on 'kldunload -f' it should be possible to clean up > and avoid panic on next load. > What usually happens in that a timeout happens and the driver handler no longer exists (i.e. forgot to call untimeout), or an interrupt happens and the driver forgot to deregister the interrupt. There are also a lot of rase possibilities in here even if the driver attempts to do the right thing. There really isn't a 'one size fits all' way to deal with this kind of thing. The driver author needs to build quiesce and shutdown semantics into the driver design. Scott From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 17:48: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 C6BDB16A4CE for ; Mon, 19 Jul 2004 17:48:35 +0000 (GMT) Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU [128.205.32.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 520AC43D1F for ; Mon, 19 Jul 2004 17:48:35 +0000 (GMT) (envelope-from kensmith@cse.Buffalo.EDU) Received: from electra.cse.Buffalo.EDU (kensmith@localhost [127.0.0.1]) i6JHmYTH013040; Mon, 19 Jul 2004 13:48:34 -0400 (EDT) Received: (from kensmith@localhost) by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id i6JHmYt7013039; Mon, 19 Jul 2004 13:48:34 -0400 (EDT) Date: Mon, 19 Jul 2004 13:48:34 -0400 From: Ken Smith To: Poul-Henning Kamp Message-ID: <20040719174834.GD10699@electra.cse.Buffalo.EDU> References: <7482.1089588386@critter.freebsd.dk> <26867.1089756587@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <26867.1089756587@critter.freebsd.dk> User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: [TEST/REVIEW/HEADSUP] tty drivers mega-patch 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, 19 Jul 2004 17:48:36 -0000 On Wed, Jul 14, 2004 at 12:09:47AM +0200, Poul-Henning Kamp wrote: > > http://phk.freebsd.dk/patch/tty.patch > > This patch removes 2500 lines of copy&paste insanity in tty drivers > and generally tries to get things to be less confused & confusing. > > I need testers for all the different kinds of serial hardware we support. > > Please help test! Ok, this patch causes two problems for sparc64 (so far). - Booting to single-user mode leaves /dev/console with echo turned off, apparently no matter what the underlying console device is (happened on both a serial-port-console Ultra-10 and on an Ultra-60 with Creator-3D console which is syscons based). - The Ultra-60 with Creator-3D console panic's when starting the getty on the console at the end of the boot, message is simply "panic: foo" which I'm assuming means it's tripping over one of the "KASSERT(... "foo")" sections of the drivers. Looked like your patch removed a bunch and added a few... Are either of these known problems and being worked on? Do you need anything (more info, debugging help, ???)? Am I on my own? :-) Just let me know where we go from here, I'm flexible... -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 17:52: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 6A5C216A4CE; Mon, 19 Jul 2004 17:52:40 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2995143D1D; Mon, 19 Jul 2004 17:52:40 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-63-195-111-154.dsl.snfc21.pacbell.net [63.195.111.154]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i6JHqcrb002978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 19 Jul 2004 10:52:39 -0700 Message-ID: <40FC09E1.9040509@root.org> Date: Mon, 19 Jul 2004 10:50:25 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <200407162010.i6GKAlUq005647@corona.sajd.net> <200406301134.09786.jhb@FreeBSD.org> In-Reply-To: <200406301134.09786.jhb@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Pawel Worach cc: freebsd-current@FreeBSD.org Subject: Re: acpi_timer broken 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, 19 Jul 2004 17:52:40 -0000 John Baldwin wrote: > On Friday 16 July 2004 04:10 pm, Pawel Worach wrote: > >>Hi, >> >>Somewhere in the last few days the acpi timecounter is not detected on >>my system anymore, the machine is an IBM xSeries 345. >> >>When it worked it looked like this: >>Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 >>acpi_timer0: <32-bit timer at 3.579545MHz> port 0x488-0x48b on acpi0 >> >>Now it looks like this: >>acpi_timer0: couldn't allocate I/O resource (port 0x488) >>acpi_timer0 port 0x488-0x48b on acpi0 >> >>Any ideas? > > This is probably related to the recent ACPI sysresource changes. Try asking > njl@ (cc'd) for pointers. Disabling the "sysresource" driver and seeing if > that fixes the problem is a good first step. John, your clock is off. Your reply had a date of "June 30". Pawel, send me the output of acpidump -t -d > ibm_xseries_345.asl -- -Nate From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 17:52: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 D0A0916A4DA; Mon, 19 Jul 2004 17:52:43 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CBFC43D5A; Mon, 19 Jul 2004 17:52:43 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id E364EACAE6; Mon, 19 Jul 2004 19:52:41 +0200 (CEST) Date: Mon, 19 Jul 2004 19:52:41 +0200 From: Pawel Jakub Dawidek To: Scott Long Message-ID: <20040719175241.GJ57678@darkness.comp.waw.pl> References: <20040719145745.GH57678@darkness.comp.waw.pl> <20040719102139.N59702@carver.gumbysoft.com> <20040719173819.GI57678@darkness.comp.waw.pl> <40FC0832.3040805@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8tZVdKiiYitVG083" Content-Disposition: inline In-Reply-To: <40FC0832.3040805@freebsd.org> 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: freebsd-current@freebsd.org Subject: Re: Unloading USB driver while device is attached. 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, 19 Jul 2004 17:52:44 -0000 --8tZVdKiiYitVG083 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 19, 2004 at 11:43:14AM -0600, Scott Long wrote: +> >Yeah, but even on 'kldunload -f' it should be possible to clean up +> >and avoid panic on next load. +> > +>=20 +> What usually happens in that a timeout happens and the driver handler no +> longer exists (i.e. forgot to call untimeout), or an interrupt happens +> and the driver forgot to deregister the interrupt. There are also a lot +> of rase possibilities in here even if the driver attempts to do the +> right thing. There really isn't a 'one size fits all' way to deal with +> this kind of thing. The driver author needs to build quiesce and +> shutdown semantics into the driver design. If your device is inserted and you load a driver everything is ok, because no driver is attached to this device. So, as I see it, device should be totally detached before unload and I susspect that something is missing in USB layer, not in all drivers. That's why when I load a driver again, USB thinks it is somehow connected to existing device, but it isn't. --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --8tZVdKiiYitVG083 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/AppForvXbEpPzQRAqhHAJ0UJ+P6oFTC5Z8BoKp/ycG7HZlF3QCeL1Jj +1VQ4BxK1DlWDDDprEsOrCg= =7mHx -----END PGP SIGNATURE----- --8tZVdKiiYitVG083-- From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 18:37: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 AB82E16A4CE; Mon, 19 Jul 2004 18:37:26 +0000 (GMT) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id A85FB43D49; Mon, 19 Jul 2004 18:37:25 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from ns0.nlsystems.com (ns0.nlsystems.com [80.177.232.243]) by itchy.rabson.org (8.12.11/8.12.11) with ESMTP id i6JIb92x060577; Mon, 19 Jul 2004 19:37:09 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: Shizuka Kudo Date: Mon, 19 Jul 2004 19:37:04 +0100 User-Agent: KMail/1.6.1 References: <20040719161949.17114.qmail@web11405.mail.yahoo.com> In-Reply-To: <20040719161949.17114.qmail@web11405.mail.yahoo.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407191937.04398.dfr@nlsystems.com> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on itchy.rabson.org X-Virus-Scanned: clamd / ClamAV version 0.71, clamav-milter version 0.71 X-Virus-Status: Clean cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org cc: Andrew Gallatin Subject: Re: Excellent job on the firewire 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, 19 Jul 2004 18:37:26 -0000 On Monday 19 July 2004 17:19, Shizuka Kudo wrote: > Hi, > > Anyone has experience with the newly added IP over 1394 support, i.e. > fwip? > > I compiled it in with the latest kernel at 17 July, but the box > cannot ping with a M$ & linux box. I have that fixed locally but I want to fix some other problems with the firewire driver - mainly that my freebsd boxes often go haywire when I plug a windows box into the bus. I also want to finish writing the code for freebsd to be a fully functional isochronous bus manager. From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 18:50: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 488B316A4CE; Mon, 19 Jul 2004 18:50:50 +0000 (GMT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 2CE4E43D31; Mon, 19 Jul 2004 18:50:49 +0000 (GMT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 19 Jul 2004 19:50:48 +0100 (BST) To: Pawel Jakub Dawidek In-Reply-To: Your message of "Mon, 19 Jul 2004 19:52:41 +0200." <20040719175241.GJ57678@darkness.comp.waw.pl> Date: Mon, 19 Jul 2004 19:50:48 +0100 From: Ian Dowse Message-ID: <200407191950.aa12733@salmon.maths.tcd.ie> cc: freebsd-current@FreeBSD.org cc: Scott Long Subject: Re: Unloading USB driver while device is attached. 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, 19 Jul 2004 18:50:50 -0000 In message <20040719175241.GJ57678@darkness.comp.waw.pl>, Pawel Jakub Dawidek w rites: >So, as I see it, device should be totally detached before unload and >I susspect that something is missing in USB layer, not in all drivers. >That's why when I load a driver again, USB thinks it is somehow connected >to existing device, but it isn't. I'm not sure if it will help in this particular case, but I have a lot of local cleanups and improvements in the USB code. There's a large patch at http://people.freebsd.org/~iedowse/usb.diff but unfortunately I haven't had time to work on this lately (and there are all the problems of divergence from NetBSD etc. if bits of this get committed). The (small) uhub.c changes look like they might possibly help in your case. With the full patch I was able to `kldunload usb' without crashes a while ago, but there were still memory leaks. Ian From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 19:16: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 CFD0716A4CE; Mon, 19 Jul 2004 19:16:31 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 348B143D2F; Mon, 19 Jul 2004 19:16:31 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6JJEesD086382; Mon, 19 Jul 2004 21:14:40 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <143b01c46dc3$bc7f0db0$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "John Baldwin" , References: <200406301130.43121.jhb@FreeBSD.org> Date: Mon, 19 Jul 2004 21:08:11 +0200 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.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: Robert Watson Subject: Re: spin lock sched lock held by 0xffffff007b712250 for > 5 seconds 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, 19 Jul 2004 19:16:31 -0000 From: "John Baldwin" > On Friday 16 July 2004 12:21 pm, Robert Watson wrote: > > On Fri, 16 Jul 2004, Willem Jan Withagen wrote: > > > After todays kernelbuild the system seem to be a lot better... > > > It can take quite some buildworld abuse, but still: > > > > > > spin lock sched lock held by 0xffffff007b712250 for > 5 seconds > > > panic: spin lock held too long > > > cpuid = 1; > > > KDB: enter: panic > > > > > > But I'm not shure what I could/should do now, since the KDB > > > introduction. Normally I'd expect to see: db> > > > > We have trouble entering the debugger when in a critical section/and or > > have sched_lock held -- I think this is because we try to halt the other > > CPUs and that gets nastily stuck in some form. We need to fix this. > > > > This could well be a symptom of some of the other hangs we've been seeing, > > and I've seen similar things on my test box with preemption enabled. > > You can hack sys/i386/include/smptests.h (or smptest.h, whichever it is) and > comment out CPUSTOP_ONDDBREAK as a hack. I did that recently for some > debugging. This is i386 only ..... I'm running in 84bit mode. But in all this is a nice suggestion, to see if the same thing will cause so many crashes when running in native 32bit-i386 mode. If it does the same there, would that mean a hardware problem?? Or is i386 much more stable? --WjW From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 19:29: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 1BE8E16A4CE; Mon, 19 Jul 2004 19:29:33 +0000 (GMT) Received: from lakermmtao03.cox.net (lakermmtao03.cox.net [68.230.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9629343D53; Mon, 19 Jul 2004 19:29:32 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao03.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP <20040719192928.BQMQ12850.lakermmtao03.cox.net@dolphin.local.net>; Mon, 19 Jul 2004 15:29:28 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.12.11/8.12.11) with ESMTP id i6JJTUge093822; Mon, 19 Jul 2004 14:29:30 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.12.11/8.12.11/Submit) id i6JJTUb2093785; Mon, 19 Jul 2004 14:29:30 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=XFMail.1.5.5.FreeBSD:20040719142929:32170=_" Date: Mon, 19 Jul 2004 14:29:29 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: freebsd-current@freebsd.org cc: freebsd-multimedia@freebsd.org Subject: [amd64] Sound breakage with snd_ich driver 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: Mon, 19 Jul 2004 19:29:33 -0000 This message is in MIME format --_=XFMail.1.5.5.FreeBSD:20040719142929:32170=_ Content-Type: text/plain; charset=us-ascii This problem has persisted for the last several weeks now, close to a month or so, I would say. Playing MP3s using madplay, everything works fine for a while, then suddenly I get an "output: write: Invalid argument" error each time madplay starts up. Any further attempts to use sound via any method or app likewise fail. Sound remains broken until a reboot. Upgraded the system again yesterday, to the new "sound" drivers, same results. I've attached truss output from one of these failed madplay runs. -- Conrad J. Sabatier -- "In Unix veritas" --_=XFMail.1.5.5.FreeBSD:20040719142929:32170=_ Content-Disposition: attachment; filename="madplay.truss" Content-Transfer-Encoding: none Content-Description: madplay.truss Content-Type: text/plain; charset=us-ascii; name=madplay.truss; SizeOnDisk=30309 29458: mmap(0x0,7280,(0x3)PROT_READ|PROT_WRITE,(0x1000)MAP_ANON,4294967295,0x0) = 8595361792 (0x20052d000) 29458: munmap(0x20052d000,0x1c70) = 0 (0x0) 29458: __sysctl(0x7fffffffe460,0x2,0x2006347d0,0x7fffffffe458,0x0,0x0) = 0 (0x0) 29458: mmap(0x0,32768,(0x3)PROT_READ|PROT_WRITE,(0x1002)MAP_ANON|MAP_PRIVATE,429 4967295,0x0) = 8595361792 (0x20052d000) 29458: issetugid() = 0 (0x0) 29458: open("/etc/libmap.conf",0x0,0666) = 4 (0x4) 29458: fstat(4,0x7fffffffdcf0) = 0 (0x0) 29458: munmap(0x200531000,0x4000) = 0 (0x0) 29458: mmap(0x0,53248,(0x3)PROT_READ|PROT_WRITE,(0x1002)MAP_ANON|MAP_PRIVATE,429 4967295,0x0) = 8595378176 (0x200531000) 29458: read(0x4,0x200532000,0x4000) = 41 (0x29) 29458: read(0x4,0x200532000,0x4000) = 0 (0x0) 29458: close(4) = 0 (0x0) 29458: access("/usr/local/lib/libesd.so.2",0) = 0 (0x0) 29458: open("/usr/local/lib/libesd.so.2",0x0,0100024673770) = 4 (0x4) 29458: fstat(4,0x7fffffffe590) = 0 (0x0) 29458: read(0x4,0x2006336a0,0x1000) = 4096 (0x1000) 29458: mmap(0x0,1085440,(0x5)PROT_READ|PROT_EXEC,(0x20002)MAP_NOCORE|MAP_PRIVATE ,4,0x0) = 8596455424 (0x200638000) 29458: mprotect(0x20063e000,4096,(0x7)PROT_READ|PROT_WRITE|PROT_EXEC) = 0 (0x0) 29458: mprotect(0x20063e000,4096,(0x5)PROT_READ|PROT_EXEC) = 0 (0x0) 29458: mmap(0x20073f000,8192,(0x3)PROT_READ|PROT_WRITE,(0x12)MAP_FIXED|MAP_PRIVA TE,4,0x7000) = 8597532672 (0x20073f000) 29458: close(4) = 0 (0x0) 29458: access("/usr/local/lib/libintl.so.6",0) = 0 (0x0) 29458: open("/usr/local/lib/libintl.so.6",0x0,037777777774) = 4 (0x4) 29458: fstat(4,0x7fffffffe590) = 0 (0x0) 29458: read(0x4,0x2006336a0,0x1000) = 4096 (0x1000) 29458: mmap(0x0,1085440,(0x5)PROT_READ|PROT_EXEC,(0x20002)MAP_NOCORE|MAP_PRIVATE ,4,0x0) = 8597540864 (0x200741000) 29458: mprotect(0x200748000,4096,(0x7)PROT_READ|PROT_WRITE|PROT_EXEC) = 0 (0x0) 29458: mprotect(0x200748000,4096,(0x5)PROT_READ|PROT_EXEC) = 0 (0x0) 29458: mmap(0x200848000,8192,(0x3)PROT_READ|PROT_WRITE,(0x12)MAP_FIXED|MAP_PRIVA TE,4,0x7000) = 8598618112 (0x200848000) 29458: close(4) = 0 (0x0) 29458: access("/usr/local/lib/libmad.so.2",0) = 0 (0x0) 29458: open("/usr/local/lib/libmad.so.2",0x0,037777777774) = 4 (0x4) 29458: fstat(4,0x7fffffffe590) = 0 (0x0) 29458: read(0x4,0x2006336a0,0x1000) = 4096 (0x1000) 29458: mmap(0x0,1175552,(0x5)PROT_READ|PROT_EXEC,(0x20002)MAP_NOCORE|MAP_PRIVATE ,4,0x0) = 8598626304 (0x20084a000) 29458: mprotect(0x200866000,4096,(0x7)PROT_READ|PROT_WRITE|PROT_EXEC) = 0 (0x0) 29458: mprotect(0x200866000,4096,(0x5)PROT_READ|PROT_EXEC) = 0 (0x0) 29458: mmap(0x200967000,8192,(0x3)PROT_READ|PROT_WRITE,(0x12)MAP_FIXED|MAP_PRIVA TE,4,0x1d000) = 8599793664 (0x200967000) 29458: close(4) = 0 (0x0) 29458: access("/usr/local/lib/libid3tag.so.2",0) = 0 (0x0) 29458: open("/usr/local/lib/libid3tag.so.2",0x0,04) = 4 (0x4) 29458: fstat(4,0x7fffffffe590) = 0 (0x0) 29458: read(0x4,0x2006336a0,0x1000) = 4096 (0x1000) 29458: mmap(0x0,1142784,(0x5)PROT_READ|PROT_EXEC,(0x20002)MAP_NOCORE|MAP_PRIVATE ,4,0x0) = 8599801856 (0x200969000) 29458: mprotect(0x20097b000,4096,(0x7)PROT_READ|PROT_WRITE|PROT_EXEC) = 0 (0x0) 29458: mprotect(0x20097b000,4096,(0x5)PROT_READ|PROT_EXEC) = 0 (0x0) 29458: mmap(0x200a7c000,16384,(0x3)PROT_READ|PROT_WRITE,(0x12)MAP_FIXED|MAP_PRIV ATE,4,0x13000) = 8600928256 (0x200a7c000) 29458: close(4) = 0 (0x0) 29458: access("/usr/local/lib/libm.so.2",0) ERR#2 'No such file or directory' 29458: open("/var/run/ld-elf.so.hints",0x0,00) = 4 (0x4) 29458: read(0x4,0x7fffffffe580,0x80) = 128 (0x80) 29458: lseek(4,0x80,0x4) = 128 (0x80) 29458: read(0x4,0x200539000,0x6a) = 106 (0x6a) 29458: close(4) = 0 (0x0) 29458: access("/lib/libm.so.2",0) = 0 (0x0) 29458: open("/lib/libm.so.2",0x0,011) = 4 (0x4) 29458: fstat(4,0x7fffffffe590) = 0 (0x0) 29458: read(0x4,0x2006336a0,0x1000) = 4096 (0x1000) 29458: mmap(0x0,1179648,(0x5)PROT_READ|PROT_EXEC,(0x20002)MAP_NOCORE|MAP_PRIVATE ,4,0x0) = 8600944640 (0x200a80000) 29458: mprotect(0x200a99000,4096,(0x7)PROT_READ|PROT_WRITE|PROT_EXEC) = 0 (0x0) 29458: mprotect(0x200a99000,4096,(0x5)PROT_READ|PROT_EXEC) = 0 (0x0) 29458: mmap(0x200b99000,28672,(0x3)PROT_READ|PROT_WRITE,(0x12)MAP_FIXED|MAP_PRIV ATE,4,0x19000) = 8602095616 (0x200b99000) 29458: close(4) = 0 (0x0) 29458: access("/usr/local/lib/libc.so.5",0) ERR#2 'No such file or directory' 29458: access("/lib/libc.so.5",0) = 0 (0x0) 29458: open("/lib/libc.so.5",0x0,012) = 4 (0x4) 29458: fstat(4,0x7fffffffe590) = 0 (0x0) 29458: read(0x4,0x2006336a0,0x1000) = 4096 (0x1000) 29458: mmap(0x0,2056192,(0x5)PROT_READ|PROT_EXEC,(0x20002)MAP_NOCORE|MAP_PRIVATE ,4,0x0) = 8602124288 (0x200ba0000) 29458: mprotect(0x200c5d000,4096,(0x7)PROT_READ|PROT_WRITE|PROT_EXEC) = 0 (0x0) 29458: mprotect(0x200c5d000,4096,(0x5)PROT_READ|PROT_EXEC) = 0 (0x0) 29458: mmap(0x200d5e000,139264,(0x3)PROT_READ|PROT_WRITE,(0x12)MAP_FIXED|MAP_PRI VATE,4,0xbe000) = 8603951104 (0x200d5e000) 29458: mmap(0x200d80000,90112,(0x3)PROT_READ|PROT_WRITE,(0x1012)MAP_ANON|MAP_FIX ED|MAP_PRIVATE,4294967295,0x0) = 8604090368 (0x200d80000) 29458: close(4) = 0 (0x0) 29458: access("/usr/local/lib/libaudiofile.so.0",0) = 0 (0x0) 29458: open("/usr/local/lib/libaudiofile.so.0",0x0,037777777767) = 4 (0x4) 29458: fstat(4,0x7fffffffe590) = 0 (0x0) 29458: read(0x4,0x2006336a0,0x1000) = 4096 (0x1000) 29458: mmap(0x0,1216512,(0x5)PROT_READ|PROT_EXEC,(0x20002)MAP_NOCORE|MAP_PRIVATE ,4,0x0) = 8604180480 (0x200d96000) 29458: mprotect(0x200db6000,4096,(0x7)PROT_READ|PROT_WRITE|PROT_EXEC) = 0 (0x0) 29458: mprotect(0x200db6000,4096,(0x5)PROT_READ|PROT_EXEC) = 0 (0x0) 29458: mmap(0x200eb6000,36864,(0x3)PROT_READ|PROT_WRITE,(0x12)MAP_FIXED|MAP_PRIV ATE,4,0x20000) = 8605360128 (0x200eb6000) 29458: close(4) = 0 (0x0) 29458: access("/usr/local/lib/libm.so.2",0) ERR#2 'No such file or directory' 29458: access("/lib/libm.so.2",0) = 0 (0x0) 29458: access("/usr/local/lib/libiconv.so.3",0) = 0 (0x0) 29458: open("/usr/local/lib/libiconv.so.3",0x0,037777777770) = 4 (0x4) 29458: fstat(4,0x7fffffffe590) = 0 (0x0) 29458: read(0x4,0x2006336a0,0x1000) = 4096 (0x1000) 29458: mmap(0x0,2031616,(0x5)PROT_READ|PROT_EXEC,(0x20002)MAP_NOCORE|MAP_PRIVATE ,4,0x0) = 8605396992 (0x200ebf000) 29458: mprotect(0x200fa9000,4096,(0x7)PROT_READ|PROT_WRITE|PROT_EXEC) = 0 (0x0) 29458: mprotect(0x200fa9000,4096,(0x5)PROT_READ|PROT_EXEC) = 0 (0x0) 29458: mmap(0x2010aa000,20480,(0x3)PROT_READ|PROT_WRITE,(0x12)MAP_FIXED|MAP_PRIV ATE,4,0xeb000) = 8607408128 (0x2010aa000) 29458: close(4) = 0 (0x0) 29458: access("/usr/local/lib/libz.so.2",0) ERR#2 'No such file or directory' 29458: access("/lib/libz.so.2",0) = 0 (0x0) 29458: open("/lib/libz.so.2",0x0,011) = 4 (0x4) 29458: fstat(4,0x7fffffffe590) = 0 (0x0) 29458: read(0x4,0x2006336a0,0x1000) = 4096 (0x1000) 29458: mmap(0x0,1126400,(0x5)PROT_READ|PROT_EXEC,(0x20002)MAP_NOCORE|MAP_PRIVATE ,4,0x0) = 8607428608 (0x2010af000) 29458: mprotect(0x2010bf000,4096,(0x7)PROT_READ|PROT_WRITE|PROT_EXEC) = 0 (0x0) 29458: mprotect(0x2010bf000,4096,(0x5)PROT_READ|PROT_EXEC) = 0 (0x0) 29458: mmap(0x2011c0000,8192,(0x3)PROT_READ|PROT_WRITE,(0x12)MAP_FIXED|MAP_PRIVA TE,4,0x11000) = 8608546816 (0x2011c0000) 29458: close(4) = 0 (0x0) 29458: access("/lib/libm.so.2",0) = 0 (0x0) 29458: mmap(0x0,2112,(0x3)PROT_READ|PROT_WRITE,(0x1000)MAP_ANON,4294967295,0x0) = 8595431424 (0x20053e000) 29458: munmap(0x20053e000,0x840) = 0 (0x0) 29458: mmap(0x0,2544,(0x3)PROT_READ|PROT_WRITE,(0x1000)MAP_ANON,4294967295,0x0) = 8595431424 (0x20053e000) 29458: munmap(0x20053e000,0x9f0) = 0 (0x0) 29458: mmap(0x0,2016,(0x3)PROT_READ|PROT_WRITE,(0x1000)MAP_ANON,4294967295,0x0) = 8595431424 (0x20053e000) 29458: munmap(0x20053e000,0x7e0) = 0 (0x0) 29458: mmap(0x0,1472,(0x3)PROT_READ|PROT_WRITE,(0x1000)MAP_ANON,4294967295,0x0) = 8595431424 (0x20053e000) 29458: munmap(0x20053e000,0x5c0) = 0 (0x0) 29458: mmap(0x0,3152,(0x3)PROT_READ|PROT_WRITE,(0x1000)MAP_ANON,4294967295,0x0) = 8595431424 (0x20053e000) 29458: munmap(0x20053e000,0xc50) = 0 (0x0) 29458: mmap(0x0,4096,(0x3)PROT_READ|PROT_WRITE,(0x1000)MAP_ANON,4294967295,0x0) = 8595431424 (0x20053e000) 29458: munmap(0x20053e000,0x1000) = 0 (0x0) 29458: mmap(0x0,43808,(0x3)PROT_READ|PROT_WRITE,(0x1000)MAP_ANON,4294967295,0x0) = 8595431424 (0x20053e000) 29458: munmap(0x20053e000,0xab20) = 0 (0x0) 29458: mmap(0x0,5760,(0x3)PROT_READ|PROT_WRITE,(0x1000)MAP_ANON,4294967295,0x0) = 8595431424 (0x20053e000) 29458: munmap(0x20053e000,0x1680) = 0 (0x0) 29458: mmap(0x0,1056,(0x3)PROT_READ|PROT_WRITE,(0x1000)MAP_ANON,4294967295,0x0) = 8595431424 (0x20053e000) 29458: munmap(0x20053e000,0x420) = 0 (0x0) 29458: mmap(0x0,1920,(0x3)PROT_READ|PROT_WRITE,(0x1000)MAP_ANON,4294967295,0x0) = 8595431424 (0x20053e000) 29458: munmap(0x20053e000,0x780) = 0 (0x0) 29458: sigprocmask(0x1,0x2006335a0,0x7fffffffe610) = 0 (0x0) 29458: sigprocmask(0x3,0x2006335b0,0x0) = 0 (0x0) 29458: open("/usr/share/locale/en_US.ISO8859-1/LC_COLLATE",0x0,0666) = 4 (0x4) 29458: fstat(4,0x7fffffffdea0) = 0 (0x0) 29458: readlink("/etc/malloc.conf","aj",63) = 2 (0x2) 29458: issetugid() = 0 (0x0) 29458: mmap(0x0,4096,(0x3)PROT_READ|PROT_WRITE,(0x1002)MAP_ANON|MAP_PRIVATE,4294 967295,0x0) = 8595431424 (0x20053e000) 29458: break(0x514000) = 0 (0x0) 29458: break(0x518000) = 0 (0x0) 29458: read(0x4,0x514000,0x4000) = 4642 (0x1222) 29458: break(0x519000) = 0 (0x0) 29458: break(0x51a000) = 0 (0x0) 29458: break(0x51b000) = 0 (0x0) 29458: close(4) = 0 (0x0) 29458: open("/usr/share/locale/en_US.ISO8859-1/LC_CTYPE",0x0,0666) = 4 (0x4) 29458: fstat(4,0x7fffffffdf50) = 0 (0x0) 29458: fstat(4,0x7fffffffdd90) = 0 (0x0) 29458: break(0x51f000) = 0 (0x0) 29458: lseek(4,0x0,0x5954435f434c2f31) = 0 (0x0) 29458: lseek(4,0x0,0x5954435f434c2f31) = 0 (0x0) 29458: read(0x4,0x51b000,0x4000) = 4264 (0x10a8) 29458: close(4) = 0 (0x0) 29458: open("/usr/share/locale/en_US.ISO8859-1/LC_MONETARY",0x0,0377777777775770 0) = 4 (0x4) 29458: fstat(4,0x7fffffffdf40) = 0 (0x0) 29458: read(0x4,0x5130d0,0x22) = 34 (0x22) 29458: close(4) = 0 (0x0) 29458: open("/usr/share/locale/en_US.ISO8859-1/LC_NUMERIC",0x0,03777777777757700 ) = 4 (0x4) 29458: fstat(4,0x7fffffffdf40) = 0 (0x0) 29458: read(0x4,0x51a090,0x8) = 8 (0x8) 29458: close(4) = 0 (0x0) 29458: open("/usr/share/locale/en_US.ISO8859-1/LC_TIME",0x0,03777777777757700) = 4 (0x4) 29458: fstat(4,0x7fffffffdf40) = 0 (0x0) 29458: read(0x4,0x516010,0x179) = 377 (0x179) 29458: close(4) = 0 (0x0) 29458: open("/usr/share/locale/en_US.ISO8859-1/LC_MESSAGES",0x0,0377777777775770 0) = 4 (0x4) 29458: fstat(4,0x7fffffffdf40) = 0 (0x0) 29458: read(0x4,0x513110,0x12) = 18 (0x12) 29458: close(4) = 0 (0x0) 29458: ioctl(0,TIOCGETA,0x7fffffffe450) = 0 (0x0) 29458: getuid() = 1000 (0x3e8) 29458: geteuid() = 1000 (0x3e8) 29458: getgid() = 1000 (0x3e8) 29458: getegid() = 1000 (0x3e8) 29458: open("/usr/local/share/locale/locale.alias",0x0,0666) = 4 (0x4) 29458: fstat(4,0x7fffffffdf30) = 0 (0x0) 29458: read(0x4,0x51b000,0x4000) = 2687 (0xa7f) 29458: break(0x520000) = 0 (0x0) 29458: read(0x4,0x51b000,0x4000) = 0 (0x0) 29458: close(4) = 0 (0x0) 29458: open("/usr/local/share/locale/en_US.ISO8859-1/LC_MESSAGES/madplay.mo",0x0 ,01) ERR#2 'No such file or directory' 29458: open("/usr/local/share/locale/en_US.iso88591/LC_MESSAGES/madplay.mo",0x0, 01777777777777777777777) ERR#2 'No such file or directory' 29458: open("/usr/local/share/locale/en_US/LC_MESSAGES/madplay.mo",0x0,017777777 77777777777777) ERR#2 'No such file or directory' 29458: open("/usr/local/share/locale/en.ISO8859-1/LC_MESSAGES/madplay.mo",0x0,01 777777777777777777777) ERR#2 'No such file or directory' 29458: open("/usr/local/share/locale/en.iso88591/LC_MESSAGES/madplay.mo",0x0,017 77777777777777777777) ERR#2 'No such file or directory' 29458: open("/usr/local/share/locale/en/LC_MESSAGES/madplay.mo",0x0,017777777777 77777777777) = 4 (0x4) 29458: fstat(4,0x7fffffffe1e0) = 0 (0x0) 29458: mmap(0x0,437,(0x1)PROT_READ,(0x2)MAP_PRIVATE,4,0x0) = 8595435520 (0x20053 f000) 29458: close(4) = 0 (0x0) 29458: open("/usr/local/libdata/charset.alias",0x0,0666) = 4 (0x4) 29458: fstat(4,0x7fffffffdf00) = 0 (0x0) 29458: break(0x524000) = 0 (0x0) 29458: read(0x4,0x520000,0x4000) = 641 (0x281) 29458: read(0x4,0x520000,0x4000) = 0 (0x0) 29458: close(4) = 0 (0x0) 29458: write(2,0x7fffffffdb40,78) = 78 (0x4e) 29458: open("/dev/tty",0x0,03777777777763550) = 4 (0x4) 29458: ioctl(4,TIOCGETA,0x512400) = 0 (0x0) 29458: sigaction(SIGTSTP,0x0,{ SIG_DFL 0x0|ONSTACK|RESTART|RESETHAND|NOCLDSTOP|N ODEFER|NOCLDWAIT|SIGINFO ss_t }) = 0 (0x0) 29458: sigaction(SIGINT,0x0,{ SIG_DFL 0x0|ONSTACK|RESTART|RESETHAND|NOCLDSTOP|NO DEFER|NOCLDWAIT|SIGINFO ss_t }) = 0 (0x0) 29458: sigaction(SIGTSTP,{ 0x407fb4 0x0|ONSTACK|RESTART|RESETHAND|NOCLDSTOP|NODE FER|NOCLDWAIT|SIGINFO ss_t },0x0) = 0 (0x0) 29458: sigaction(SIGINT,{ 0x407fb4 0x0|ONSTACK|RESTART|RESETHAND|NOCLDSTOP|NODEF ER|NOCLDWAIT|SIGINFO ss_t },0x0) = 0 (0x0) 29458: ioctl(4,TIOCSETAF,0x7fffffffe3e0) = 0 (0x0) 29458: open("/dev/sound/dsp",0x1,00) ERR#2 'No such file or directory' 29458: open("/dev/dsp",0x1,01777777777777777777777) = 5 (0x5) 29458: open("Ultramarine - A User's Guide - 01 All of A Sudden.mp3",0x0,00) = 6 (0x6) 29458: dup(0x6) = 7 (0x7) 29458: getdtablesize() = 7322 (0x1c9a) 29458: fcntl(7,F_GETFL,0x0) = 0 (0x0) 29458: lseek(7,0x0,0x666f206c6c412031) = 0 (0x0) 29458: fstat(7,0x7fffffffe110) = 0 (0x0) 29458: lseek(7,0x0,0x666f206c6c412031) = 0 (0x0) 29458: lseek(7,0x0,0x666f206c6c412031) = 0 (0x0) 29458: fstat(7,0x7fffffffe200) = 0 (0x0) 29458: lseek(7,0xbefa00,0x666f206c6c412031) = 12515840 (0xbefa00) 29458: read(0x7,0x516400,0x200) = 419 (0x1a3) 29458: lseek(7,0x0,0x666f206c6c412031) = 0 (0x0) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: break(0x53c000) = 0 (0x0) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: read(0x7,0x516400,0x200) = 512 (0x200) 29458: break(0x551000) = 0 (0x0) 29458: break(0x54c000) = 0 (0x0) 29458: break(0x561000) = 0 (0x0) 29458: fstat(7,0x7fffffffe200) = 0 (0x0) 29458: lseek(7,0xbefa00,0x666f206c6c412031) = 12515840 (0xbefa00) 29458: read(0x7,0x516400,0x200) = 419 (0x1a3) 29458: lseek(7,0x0,0x666f206c6c412031) = 0 (0x0) 29458: write(2,0x7fffffffd9a0,28) = 28 (0x1c) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,24) = 24 (0x18) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,13) = 13 (0xd) 29458: write(2,0x7fffffffd9a0,27) = 27 (0x1b) 29458: write(2,0x7fffffffd9a0,17) = 17 (0x11) 29458: write(2,0x7fffffffd9a0,17) = 17 (0x11) 29458: write(2,0x7fffffffd9a0,24) = 24 (0x18) 29458: write(2,0x7fffffffd9a0,40) = 40 (0x28) 29458: close(7) = 0 (0x0) 29458: break(0x530000) = 0 (0x0) 29458: fstat(6,0x7fffffffe2d0) = 0 (0x0) 29458: mmap(0x0,12516259,(0x1)PROT_READ,(0x1)MAP_SHARED,6,0x0) = 8608555008 (0x2 011c2000) 29458: madvise(0x2011c2000,0xbefba3,0x2) = 0 (0x0) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: ioctl(5,SNDCTL_DSP_SYNC,0x0) = 0 (0x0) 29458: ioctl(5,SNDCTL_DSP_SETFMT,0x7fffffffe164) ERR#19 'Operation not supported by device' 29458: ioctl(5,SNDCTL_DSP_SETFMT,0x7fffffffe164) = 0 (0x0) 29458: ioctl(5,SOUND_PCM_WRITE_CHANNELS,0x7fffffffe1a4) = 0 (0x0) 29458: ioctl(5,SNDCTL_DSP_SPEED,0x7fffffffe1a8) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 4608 (0x1200) 29458: read(0x4,0x7fffffffe11f,0x1) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) = 0 (0x0) 29458: write(5,0x7fffffff0970,4608) ERR#22 'Invalid argument' 29458: write(2,0x7fffffffd770,8) = 8 (0x8) 29458: writev(0x2,0x7fffffffd820,0x4) = 24 (0x18) 29458: munmap(0x2011c2000,0xbefba3) = 0 (0x0) 29458: close(6) = 0 (0x0) 29458: close(5) = 0 (0x0) 29458: ioctl(4,TIOCGETA,0x7fffffffe3d0) = 0 (0x0) 29458: ioctl(4,TIOCSETAW,0x512400) = 0 (0x0) 29458: sigaction(SIGINT,0x0,{ 0x407fb4 0x0|ONSTACK|RESTART|RESETHAND|NOCLDSTOP|N ODEFER|NOCLDWAIT|SIGINFO ss_t }) = 0 (0x0) 29458: sigaction(SIGINT,{ SIG_DFL 0x0|ONSTACK|RESTART|RESETHAND|NOCLDSTOP|NODEFE R|NOCLDWAIT|SIGINFO ss_t },0x0) = 0 (0x0) 29458: sigaction(SIGTSTP,0x0,{ 0x407fb4 0x0|ONSTACK|RESTART|RESETHAND|NOCLDSTOP| NODEFER|NOCLDWAIT|SIGINFO ss_t }) = 0 (0x0) 29458: sigaction(SIGTSTP,{ SIG_DFL 0x0|ONSTACK|RESTART|RESETHAND|NOCLDSTOP|NODEF ER|NOCLDWAIT|SIGINFO ss_t },0x0) = 0 (0x0) 29458: close(4) = 0 (0x0) 29458: exit(0x4) process exit, rval = 1024 --_=XFMail.1.5.5.FreeBSD:20040719142929:32170=_-- End of MIME message From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 20:36: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 25AE116A4CE for ; Mon, 19 Jul 2004 20:36:38 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFA9043D41 for ; Mon, 19 Jul 2004 20:36:37 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.0.12] (g4.samsco.home [192.168.0.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6JKgb7m055321 for ; Mon, 19 Jul 2004 14:42:37 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40FC3090.9060305@freebsd.org> Date: Mon, 19 Jul 2004 14:35:28 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: In-Reply-To: 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 Subject: HEADS UP [Re: thread+preemption stability improvement] 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, 19 Jul 2004 20:36:38 -0000 All, Initial testing of this patch looks very promising. For those that aren't comfortable with patching their sources by hand, note that it was committed to CVS a few hours ago and should be showing up on CVSup very shortly (rev 1.8 of sys/i386/i386/intr_machdep.c is what you want if you are running i386). Please go out and test this as much as possible so that we can determine if futher action is needed. Scott Robert Watson wrote: > On Wed, 30 Jun 2004, John Baldwin wrote: > > >>Try this patch. It fixed all my lockups with xmms in KDE on Friday: > > > This patch causes my SMP and UP tests to succeed with PREEMPTION enabled, > whereas before they rapidly hung. On SMP I see a small (just under 1%) > but consistent improvement in query throughput with MySQL, and on UP I see > a small (just under 1%) but inconsistent decrease in query throughput with > MySQL. The standard deviation on the UP case is almost the same size as > the change, but in the SMP case it's 1/4-1/3 the size of the change, FWIW. > > Can't speak to the latency as the test I'm currently running isn't very > latency sensitive, but was very sensitive to the stability issue. I think > this patch is definitely worth committing ASAP :-). > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Principal Research Scientist, McAfee Research > > > >>--- //depot/projects/smpng/sys/i386/i386/intr_machdep.c 2004/07/02 20:28:06 >>+++ //depot/user/jhb/preemption/i386/i386/intr_machdep.c 2004/07/16 20:14:26 >>@@ -204,6 +204,8 @@ >> } >> isrc->is_pic->pic_eoi_source(isrc); >> error = 0; >>+ /* XXX */ >>+ td->td_pflags &= ~TDP_OWEPREEMPT; >> critical_exit(); >> } else { >> /* >> >>-- >>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 Mon Jul 19 21:03: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 7CE7416A4CE for ; Mon, 19 Jul 2004 21:03:13 +0000 (GMT) Received: from melusine.cuivre.fr.eu.org (melusine.cuivre.fr.eu.org [82.225.155.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33EDA43D54 for ; Mon, 19 Jul 2004 21:03:13 +0000 (GMT) (envelope-from thomas@FreeBSD.ORG) Received: by melusine.cuivre.fr.eu.org (Postfix, from userid 1000) id 42FC82C3D4; Mon, 19 Jul 2004 23:03:11 +0200 (CEST) Date: Mon, 19 Jul 2004 23:03:11 +0200 From: Thomas Quinot To: "Oliver B. Fischer" Message-ID: <20040719210311.GA72395@melusine.cuivre.fr.eu.org> References: <40DFDC44.6090101@snafu.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40DFDC44.6090101@snafu.de> X-message-flag: WARNING! Using Outlook can damage your computer. User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: Obtaining a kernel dump is not 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: Mon, 19 Jul 2004 21:03:13 -0000 * Oliver B. Fischer, 2004-06-28 : > my ThinkPad gets a kernel panic if I boot a kernel with atapicam > enabled. So I try to obtain a crash dump to get a backtrace. If dumping does not work, can you try to obtain a backtrace from DDB? Thomas. -- Thomas.Quinot@Cuivre.FR.EU.ORG From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 21:09: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 8FF7416A4CF; Mon, 19 Jul 2004 21:09:21 +0000 (GMT) Received: from lakermmtao11.cox.net (lakermmtao11.cox.net [68.230.240.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id E971843D2F; Mon, 19 Jul 2004 21:09:20 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao11.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP id <20040719210918.CVPA6910.lakermmtao11.cox.net@dolphin.local.net>; Mon, 19 Jul 2004 17:09:18 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.12.11/8.12.11) with ESMTP id i6JL9J5U012070; Mon, 19 Jul 2004 16:09:19 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.12.11/8.12.11/Submit) id i6JL9JbB012069; Mon, 19 Jul 2004 16:09:19 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20040719202802.8E8C35D08@ptavv.es.net> Date: Mon, 19 Jul 2004 16:09:19 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: Kevin Oberman cc: freebsd-current@freebsd.org cc: freebsd-gnome@freebsd.org Subject: [amd64] System lockups still continuing 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: Mon, 19 Jul 2004 21:09:21 -0000 On 19-Jul-2004 Kevin Oberman wrote: >> >> On 18-Jul-2004 Conrad J. Sabatier wrote: >> > I had posted several weeks ago about constant hard lockups of my >> > amd64 box. At first, I attributed the problem to GNOME, then to >> > my kernel config, but now it appears to me that the problem >> > really lies with Mozilla/Firefox. >> >> Well, another theory bites the dust. I tried running GNOME >> yesterday, never touched Mozilla or Firefox, and the system locked >> up while doing some file management chores in Nautilus. >> >> It must be something low-level in GNOME, some shared library, >> probably, but I have yet to track it down. > > I have lost track of the full thread and this mail list is not > tracked by google :-(, so this may have been ruled out. Are you sure > that it's not the preemption problem that is biting you? This applies > to CURRENT systems only, so may not be applicable to what you are > seeing, the symptoms are a match. Hmm, you may be right. Is there any workaround for this? I've tried both SCHED_ULE and SCHED_4BSD, both producing the same results. What's strange is that this only seems to occur when either running a full-blown GNOME desktop or using some GNOME-related app under another environment. I'm currently working under KDE, just for comparison, and no such problems have occurred, unless I try using, say, Mozilla or Firefox. I'll Cc: this to current and see what they think. -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 22:35: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 4E0CE16A4CE; Mon, 19 Jul 2004 22:35:47 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45C5E43D45; Mon, 19 Jul 2004 22:35:46 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i6JMXpLx034796; Mon, 19 Jul 2004 16:33:52 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 19 Jul 2004 16:33:55 -0600 (MDT) Message-Id: <20040719.163355.111547661.imp@bsdimp.com> To: pjd@FreeBSD.ORG From: "M. Warner Losh" In-Reply-To: <20040719145745.GH57678@darkness.comp.waw.pl> References: <20040719145745.GH57678@darkness.comp.waw.pl> 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: Unloading USB driver while device is attached. 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, 19 Jul 2004 22:35:47 -0000 In message: <20040719145745.GH57678@darkness.comp.waw.pl> Pawel Jakub Dawidek writes: : Hello. : : Could someone investigate what's going on for the situation from the : subject? This panic is trivial to reproduce: : : # kldload umass.ko : : # kldunload umass : # kldload umass : : : It is not umass related! I think this problem is in our USB implementation. : : One more note with could be helpful. : When device is already inserted and I load USB driver, _match : isn't called, but when driver was unloaded while device was in and it is : loaded again (as in my example) _match is called and we have : a problem, because there are some stale data, I think (not everything : is cleaned up on kldunload?). : Ok, one more note. : You can also set 'break _match' in DDB and try to compare : backtraces when device is removed while driver is loaded and when you : unload USB driver. I do know that loading the driver won't attach umass unless you remove and insert it again. Warner From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 22:35: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 224A416A4F5; Mon, 19 Jul 2004 22:35:53 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1DFB43D31; Mon, 19 Jul 2004 22:35:52 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i6JMZWXb034803; Mon, 19 Jul 2004 16:35:32 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 19 Jul 2004 16:35:36 -0600 (MDT) Message-Id: <20040719.163536.81896269.imp@bsdimp.com> To: pjd@FreeBSD.ORG From: "M. Warner Losh" In-Reply-To: <20040719173819.GI57678@darkness.comp.waw.pl> References: <20040719145745.GH57678@darkness.comp.waw.pl> <20040719102139.N59702@carver.gumbysoft.com> <20040719173819.GI57678@darkness.comp.waw.pl> 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: Unloading USB driver while device is attached. 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, 19 Jul 2004 22:35:53 -0000 In message: <20040719173819.GI57678@darkness.comp.waw.pl> Pawel Jakub Dawidek writes: : On Mon, Jul 19, 2004 at 10:23:16AM -0700, Doug White wrote: : +> Theres a discussion going on in -arch about making kldunload a bit more : +> careful about cleaning up before detaching. In the interim adding a : +> method that just vetos any unload request would prevent this from : +> occuring, but also preclude unloading the driver. :) : : Yeah, but even on 'kldunload -f' it should be possible to clean up : and avoid panic on next load. kldunload -f isn't supported at this point :-) Or more accurately, there's no hook into the driver system (newbus). And even if there was, usb has been poorly integrated into newbus in the past, so it likely still would do bad things. Eg, -f isn't going to save you. umass should be fixed. Warner From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 22:38: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 43F5D16A4CE; Mon, 19 Jul 2004 22:38:54 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF0F443D53; Mon, 19 Jul 2004 22:38:53 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i6JMat92034848; Mon, 19 Jul 2004 16:36:55 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 19 Jul 2004 16:36:58 -0600 (MDT) Message-Id: <20040719.163658.97851603.imp@bsdimp.com> To: pjd@freebsd.org From: "M. Warner Losh" In-Reply-To: <20040719175241.GJ57678@darkness.comp.waw.pl> References: <20040719173819.GI57678@darkness.comp.waw.pl> <40FC0832.3040805@freebsd.org> <20040719175241.GJ57678@darkness.comp.waw.pl> 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: scottl@freebsd.org Subject: Re: Unloading USB driver while device is attached. 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, 19 Jul 2004 22:38:54 -0000 In message: <20040719175241.GJ57678@darkness.comp.waw.pl> Pawel Jakub Dawidek writes: : On Mon, Jul 19, 2004 at 11:43:14AM -0600, Scott Long wrote: : +> >Yeah, but even on 'kldunload -f' it should be possible to clean up : +> >and avoid panic on next load. : +> > : +> : +> What usually happens in that a timeout happens and the driver handler no : +> longer exists (i.e. forgot to call untimeout), or an interrupt happens : +> and the driver forgot to deregister the interrupt. There are also a lot : +> of rase possibilities in here even if the driver attempts to do the : +> right thing. There really isn't a 'one size fits all' way to deal with : +> this kind of thing. The driver author needs to build quiesce and : +> shutdown semantics into the driver design. : : If your device is inserted and you load a driver everything is ok, : because no driver is attached to this device. : So, as I see it, device should be totally detached before unload and : I susspect that something is missing in USB layer, not in all drivers. : That's why when I load a driver again, USB thinks it is somehow connected : to existing device, but it isn't. Actually, usb won't reattach on kldload. That's definitely missing from the usb layer. This has been noted many times in the past. However, its missing shouldn't cause the panic. That's likely a different bug. Warner From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 22:38: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 1015C16A4CE; Mon, 19 Jul 2004 22:38:55 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABC7543D53; Mon, 19 Jul 2004 22:38:54 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i6JMblZR034849; Mon, 19 Jul 2004 16:37:47 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 19 Jul 2004 16:37:51 -0600 (MDT) Message-Id: <20040719.163751.16873514.imp@bsdimp.com> To: iedowse@maths.tcd.ie From: "M. Warner Losh" In-Reply-To: <200407191950.aa12733@salmon.maths.tcd.ie> References: <20040719175241.GJ57678@darkness.comp.waw.pl> <200407191950.aa12733@salmon.maths.tcd.ie> 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: scottl@freebsd.org cc: freebsd-current@freebsd.org cc: pjd@freebsd.org Subject: Re: Unloading USB driver while device is attached. 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, 19 Jul 2004 22:38:55 -0000 In message: <200407191950.aa12733@salmon.maths.tcd.ie> Ian Dowse writes: : In message <20040719175241.GJ57678@darkness.comp.waw.pl>, Pawel Jakub Dawidek w : rites: : >So, as I see it, device should be totally detached before unload and : >I susspect that something is missing in USB layer, not in all drivers. : >That's why when I load a driver again, USB thinks it is somehow connected : >to existing device, but it isn't. : : I'm not sure if it will help in this particular case, but I have a : lot of local cleanups and improvements in the USB code. There's a : large patch at : : http://people.freebsd.org/~iedowse/usb.diff : : but unfortunately I haven't had time to work on this lately (and : there are all the problems of divergence from NetBSD etc. if bits : of this get committed). The (small) uhub.c changes look like they : might possibly help in your case. With the full patch I was able : to `kldunload usb' without crashes a while ago, but there were still : memory leaks. Personally, I think that divergence from NetBSD is less of a problem than it not working at all. Warner From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 22:42: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 51F2616A4CE; Mon, 19 Jul 2004 22:42:27 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF6B043D39; Mon, 19 Jul 2004 22:42:26 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.0.12] (g4.samsco.home [192.168.0.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6JMmPut055768; Mon, 19 Jul 2004 16:48:26 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40FC4E0C.1040404@freebsd.org> Date: Mon, 19 Jul 2004 16:41:16 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <20040719175241.GJ57678@darkness.comp.waw.pl> <200407191950.aa12733@salmon.maths.tcd.ie> <20040719.163751.16873514.imp@bsdimp.com> In-Reply-To: <20040719.163751.16873514.imp@bsdimp.com> 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: iedowse@maths.tcd.ie cc: freebsd-current@freebsd.org cc: pjd@freebsd.org Subject: Re: Unloading USB driver while device is attached. 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, 19 Jul 2004 22:42:27 -0000 M. Warner Losh wrote: > In message: <200407191950.aa12733@salmon.maths.tcd.ie> > Ian Dowse writes: > : In message <20040719175241.GJ57678@darkness.comp.waw.pl>, Pawel Jakub Dawidek w > : rites: > : >So, as I see it, device should be totally detached before unload and > : >I susspect that something is missing in USB layer, not in all drivers. > : >That's why when I load a driver again, USB thinks it is somehow connected > : >to existing device, but it isn't. > : > : I'm not sure if it will help in this particular case, but I have a > : lot of local cleanups and improvements in the USB code. There's a > : large patch at > : > : http://people.freebsd.org/~iedowse/usb.diff > : > : but unfortunately I haven't had time to work on this lately (and > : there are all the problems of divergence from NetBSD etc. if bits > : of this get committed). The (small) uhub.c changes look like they > : might possibly help in your case. With the full patch I was able > : to `kldunload usb' without crashes a while ago, but there were still > : memory leaks. > > Personally, I think that divergence from NetBSD is less of a problem > than it not working at all. > > Warner We've been fighting the NetBSD divergence issue for a lot of years. I think that we have to start accepting that there are places where divergence gives us large net gains. Probably the best goal to keep going forward is to keep the intra-stack APIs as similar as possible so that new modules can be added without much porting work. Scott From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 22:56:49 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 A347916A4CE for ; Mon, 19 Jul 2004 22:56:49 +0000 (GMT) Received: from mail.corrupt.co.nz (222-152-17-24.jetstream.xtra.co.nz [222.152.17.24]) by mx1.FreeBSD.org (Postfix) with SMTP id 736B343D54 for ; Mon, 19 Jul 2004 22:56:48 +0000 (GMT) (envelope-from drew@corrupt.co.nz) Received: (qmail 74476 invoked by uid 1011); 19 Jul 2004 22:56:52 -0000 Received: from drew@corrupt.co.nz by tweety.lan.corrupt.co.nz by uid 1009 with qmail-scanner-1.22 Clear:RC:0(192.100.53.164):SA:0(0.0/3.8):. Processed in 5.780707 secs); 19 Jul 2004 22:56:52 -0000 X-Spam-Status: No, hits=0.0 required=3.8 Received: from unknown (HELO ?192.168.63.100?) (drew@corrupt.co.nz@192.100.53.164) by mail.corrupt.co.nz with SMTP; 19 Jul 2004 22:56:45 -0000 Message-ID: <40FC50F8.3060403@corrupt.co.nz> Date: Tue, 20 Jul 2004 10:53:44 +1200 From: Drew Broadley User-Agent: Mozilla Thunderbird 0.7.1 (X11/20040714) X-Accept-Language: en-us, en MIME-Version: 1.0 To: conrads@cox.net References: In-Reply-To: X-Enigmail-Version: 0.84.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: freebsd-gnome@freebsd.org Subject: Re: [amd64] System lockups still continuing 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, 19 Jul 2004 22:56:49 -0000 Conrad J. Sabatier wrote: >On 19-Jul-2004 Kevin Oberman wrote: > > >>>On 18-Jul-2004 Conrad J. Sabatier wrote: >>> >>> >>>>I had posted several weeks ago about constant hard lockups of my >>>>amd64 box. At first, I attributed the problem to GNOME, then to >>>>my kernel config, but now it appears to me that the problem >>>>really lies with Mozilla/Firefox. >>>> >>>> >>>Well, another theory bites the dust. I tried running GNOME >>>yesterday, never touched Mozilla or Firefox, and the system locked >>>up while doing some file management chores in Nautilus. >>> >>>It must be something low-level in GNOME, some shared library, >>>probably, but I have yet to track it down. >>> >>> >>I have lost track of the full thread and this mail list is not >>tracked by google :-(, so this may have been ruled out. Are you sure >>that it's not the preemption problem that is biting you? This applies >>to CURRENT systems only, so may not be applicable to what you are >>seeing, the symptoms are a match. >> >> > >Hmm, you may be right. Is there any workaround for this? I've tried >both SCHED_ULE and SCHED_4BSD, both producing the same results. > >What's strange is that this only seems to occur when either running a >full-blown GNOME desktop or using some GNOME-related app under another >environment. > >I'm currently working under KDE, just for comparison, and no such >problems have occurred, unless I try using, say, Mozilla or Firefox. > >I'll Cc: this to current and see what they think. > > My fix (and this doesn't produce a laggy system for my Evon800v Laptop) and hasn't hung since. I stream music/tv and do compiling at the same time and discovered no pops or high CPU usage on the system. Im currently streaming a 128bkps TV stream + various other things: $ uptime 10:51AM up 1:11, 6 users, load averages: 0.27, 0.22, 0.18 $ top | less last pid: 1463; load averages: 0.16, 0.19, 0.17 up 0+01:11:39 10:52:25 115 processes: 1 running, 114 sleeping Mem: 346M Active, 47M Inact, 79M Wired, 20M Cache, 60M Buf, 1096K Free Swap: 998M Total, 998M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 791 drew 20 0 73796K 62696K kserel 1:20 9.81% 9.81% thunderbird-bin 656 drew 96 0 106M 97240K select 1:45 0.93% 0.93% XFree86 926 drew 8 0 18544K 8236K nanslp 1:00 0.73% 0.73% mplayer 772 drew 96 0 15788K 10724K select 0:41 0.05% 0.05% battstat-applet-2 738 drew 96 0 22592K 16060K select 0:33 0.05% 0.05% python 724 drew 96 0 13428K 9232K select 0:10 0.05% 0.05% metacity Here is the FIX: $ cp /usr/src/sys//include/param.h /tmp/param.h && perl -ple 's/#define PREEMPTIVE.+\n$//i' /tmp/param.h > /usr/src/sys//include/param.h /tmp/param.h Add/Update this option in your kernel HZ=2000 $ make buildworld && make buildkernel && make installkernel && make installworld && reboot FWIW - Drew From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 23:02: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 934C016A4CE; Mon, 19 Jul 2004 23:02:39 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2471B43D48; Mon, 19 Jul 2004 23:02:39 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i6JN1So0035319; Mon, 19 Jul 2004 17:01:29 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 19 Jul 2004 17:01:32 -0600 (MDT) Message-Id: <20040719.170132.52458790.imp@bsdimp.com> To: iedowse@maths.tcd.ie From: "M. Warner Losh" In-Reply-To: <200407191950.aa12733@salmon.maths.tcd.ie> References: <20040719175241.GJ57678@darkness.comp.waw.pl> <200407191950.aa12733@salmon.maths.tcd.ie> 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: scottl@freebsd.org cc: freebsd-current@freebsd.org cc: pjd@freebsd.org Subject: Re: Unloading USB driver while device is attached. 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, 19 Jul 2004 23:02:39 -0000 In message: <200407191950.aa12733@salmon.maths.tcd.ie> Ian Dowse writes: : In message <20040719175241.GJ57678@darkness.comp.waw.pl>, Pawel Jakub Dawidek w : rites: : >So, as I see it, device should be totally detached before unload and : >I susspect that something is missing in USB layer, not in all drivers. : >That's why when I load a driver again, USB thinks it is somehow connected : >to existing device, but it isn't. : : I'm not sure if it will help in this particular case, but I have a : lot of local cleanups and improvements in the USB code. There's a : large patch at : : http://people.freebsd.org/~iedowse/usb.diff : : but unfortunately I haven't had time to work on this lately (and : there are all the problems of divergence from NetBSD etc. if bits : of this get committed). The (small) uhub.c changes look like they : might possibly help in your case. With the full patch I was able : to `kldunload usb' without crashes a while ago, but there were still : memory leaks. I'm going to start merging in some of these changes, if you don't mind. Warner From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 23:04: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 1A82016A4CE for ; Mon, 19 Jul 2004 23:04:06 +0000 (GMT) Received: from mail.corrupt.co.nz (222-152-17-24.jetstream.xtra.co.nz [222.152.17.24]) by mx1.FreeBSD.org (Postfix) with SMTP id 32D3343D58 for ; Mon, 19 Jul 2004 23:04:05 +0000 (GMT) (envelope-from drew@corrupt.co.nz) Received: (qmail 74564 invoked by uid 1011); 19 Jul 2004 23:04:11 -0000 Received: from drew@corrupt.co.nz by tweety.lan.corrupt.co.nz by uid 1009 with qmail-scanner-1.22 Clear:RC:0(192.100.53.164):SA:0(0.0/3.8):. Processed in 5.620729 secs); 19 Jul 2004 23:04:11 -0000 X-Spam-Status: No, hits=0.0 required=3.8 Received: from unknown (HELO ?192.168.63.100?) (drew@corrupt.co.nz@192.100.53.164) by mail.corrupt.co.nz with SMTP; 19 Jul 2004 23:04:05 -0000 Message-ID: <40FC52A5.6010803@corrupt.co.nz> Date: Tue, 20 Jul 2004 11:00:53 +1200 From: Drew Broadley User-Agent: Mozilla Thunderbird 0.7.1 (X11/20040714) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Drew Broadley References: <40FC50F8.3060403@corrupt.co.nz> In-Reply-To: <40FC50F8.3060403@corrupt.co.nz> X-Enigmail-Version: 0.84.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: freebsd-gnome@freebsd.org Subject: Re: [amd64] System lockups still continuing 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, 19 Jul 2004 23:04:06 -0000 Sorry this line: >>>>>>>>>>>>> $ cp /usr/src/sys//include/param.h /tmp/param.h && perl -ple 's/#define PREEMPTIVE.+\n$//i' /tmp/param.h > /usr/src/sys//include/param.h /tmp/param.h >>>>>>>>>>>>> Should read: >>>>>>>>>>>>> $ cp /usr/src/sys//include/param.h /tmp/param.h && perl -ple 's/^#define[\t\s]+PREEMPTION//i' /tmp/param.h > /usr/src/sys//include/param.h >>>>>>>>>>>>> - Drew From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 23:22: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 B45DB16A4CE; Mon, 19 Jul 2004 23:22:23 +0000 (GMT) Received: from lakermmtao09.cox.net (lakermmtao09.cox.net [68.230.240.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE1B943D45; Mon, 19 Jul 2004 23:22:22 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao09.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP <20040719232220.ELEB17142.lakermmtao09.cox.net@dolphin.local.net>; Mon, 19 Jul 2004 19:22:20 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.12.11/8.12.11) with ESMTP id i6JNMIHs000793; Mon, 19 Jul 2004 18:22:18 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.12.11/8.12.11/Submit) id i6JNMIte000792; Mon, 19 Jul 2004 18:22:18 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <40FC52A5.6010803@corrupt.co.nz> Date: Mon, 19 Jul 2004 18:22:18 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: Drew Broadley cc: freebsd-current@freebsd.org cc: freebsd-gnome@freebsd.org Subject: Re: [amd64] System lockups still continuing 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: Mon, 19 Jul 2004 23:22:23 -0000 On 19-Jul-2004 Drew Broadley wrote: > Sorry this line: > >>>>>>>>>>>>> > $ cp /usr/src/sys//include/param.h /tmp/param.h && perl -ple > 's/#define PREEMPTIVE.+\n$//i' /tmp/param.h > > /usr/src/sys//include/param.h /tmp/param.h > >>>>>>>>>>>>> > > Should read: > >>>>>>>>>>>>> > $ cp /usr/src/sys//include/param.h /tmp/param.h && perl -ple > 's/^#define[\t\s]+PREEMPTION//i' /tmp/param.h > > /usr/src/sys//include/param.h > >>>>>>>>>>>>> > > - Drew Thanks, I may try that. For now, though, I just noticed a new commit (see the thread "HEADS UP [Re: thread+preemption stability improvement]" in current) that may help with the preemption problems. Running a new kernel with it now, and so far so good. :-) -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 23:33: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 643FA16A4CE; Mon, 19 Jul 2004 23:33:35 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id E916E43D2F; Mon, 19 Jul 2004 23:33:34 +0000 (GMT) (envelope-from burpmaster@truffula.net) Received: from [192.168.0.2] (c-67-169-200-31.client.comcast.net[67.169.200.31]) by comcast.net (sccrmhc13) with ESMTP id <2004071923333301600bjib6e> (Authid: rogers240); Mon, 19 Jul 2004 23:33:34 +0000 Message-ID: <40FC5A41.2070309@truffula.net> Date: Mon, 19 Jul 2004 16:33:21 -0700 From: Brian Rogers User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040719) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brian Fundakowski Feldman References: <40F46007.2010304@truffula.net> <20040713235609.GQ1626@green.homeunix.org> <40F51F8F.9020902@truffula.net> <20040714163845.GS1626@green.homeunix.org> In-Reply-To: <20040714163845.GS1626@green.homeunix.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Hang on boot - "ATAPI_RESET no interrupt" with DVD+RW 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, 19 Jul 2004 23:33:35 -0000 Brian Fundakowski Feldman wrote: >On Wed, Jul 14, 2004 at 04:57:03AM -0700, Brian Rogers wrote: > > >>Brian Fundakowski Feldman wrote: >> >> >>>On Tue, Jul 13, 2004 at 03:19:51PM -0700, Brian Rogers wrote: >>> >>> >>>>Since last night and continuing today, the kernel from -CURRENT usually >>>>hangs during boot. Safe mode worked once, but the second time it didn't >>>>work. I now got in through single-user mode, so it appears to just work >>>>every once in a while, randomly. >>>> >>>>I have a dmesg from the booted system below. When it hangs, it stops >>>>one line after "ata1-slave: FAILURE - ATAPI_RESET no interrupt", in >>>>other words it hangs after detecting ata1-master but before detecting >>>>ata1-slave, my DVD+RW drive. >>>> >>>> >>>> >>>Try using these diffs to src/sys/dev/ata; they fixed it for me. >>> >>> >>I think I stayed a bit too current. That didn't apply cleanly. >> >> >There should be very few changes; it should be relatively easy to >fix the few conflicts. > > I tried that... It doesn't resolve the issue. From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 23:45: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 08E4616A4CE; Mon, 19 Jul 2004 23:45:11 +0000 (GMT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id D29C243D53; Mon, 19 Jul 2004 23:45:09 +0000 (GMT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 20 Jul 2004 00:45:08 +0100 (BST) To: "M. Warner Losh" In-Reply-To: Your message of "Mon, 19 Jul 2004 17:01:32 MDT." <20040719.170132.52458790.imp@bsdimp.com> Date: Tue, 20 Jul 2004 00:45:08 +0100 From: Ian Dowse Message-ID: <200407200045.aa99979@salmon.maths.tcd.ie> cc: scottl@freebsd.org cc: freebsd-current@freebsd.org cc: pjd@freebsd.org cc: mycroft@netbsd.org Subject: Re: Unloading USB driver while device is attached. 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, 19 Jul 2004 23:45:11 -0000 In message <20040719.170132.52458790.imp@bsdimp.com>, "M. Warner Losh" writes: >In message: <200407191950.aa12733@salmon.maths.tcd.ie> > Ian Dowse writes: >: http://people.freebsd.org/~iedowse/usb.diff >: >: but unfortunately I haven't had time to work on this lately (and >: there are all the problems of divergence from NetBSD etc. if bits >: of this get committed). The (small) uhub.c changes look like they >: might possibly help in your case. With the full patch I was able >: to `kldunload usb' without crashes a while ago, but there were still >: memory leaks. > >I'm going to start merging in some of these changes, if you don't >mind. If you have the time that would be great! FYI, here is a rough summary of the changes in no particular order: o Beginnings of interrupt pipe support for EHCI (very little done) o Support for unloading the usb driver (leaks some memory) o Support for removing cardbus USB controllers (also leaks memory) o Avoid most (but not all) uses of contigmalloc and data buffer copies by using bus_dmamap_load() and a new `struct usb_dma_mapping'. A few places marked `XXX' need to be checked for crossing DMA segment boundaries. This is probably the most important change, as it makes USB work much more reliably on low memory machines. o Attempt to follow the correct procedure for synchronising with the BIOS via SMM to take over control of the EHCI controller. This may fix problems when the BIOS is configured to emulate legacy devices, but is untested on any affected machines. o Try to make transfers reusable from the completion callback (some related changes went into NetBSD recently, but I haven't checked the overlap). There are probably a few other changes in there too - let me know if you find any stuff that doesn't make sense. Ian From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 00:34: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 9664816A4CE; Tue, 20 Jul 2004 00:34:30 +0000 (GMT) Received: from TRANG.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78E5643D54; Tue, 20 Jul 2004 00:34:30 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by TRANG.nuxi.com (8.12.11/8.12.11) with ESMTP id i6K0YRIY008944; Mon, 19 Jul 2004 17:34:27 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.11/8.12.11/Submit) id i6K0YQFK008943; Mon, 19 Jul 2004 17:34:26 -0700 (PDT) (envelope-from obrien) Date: Mon, 19 Jul 2004 17:34:26 -0700 From: "David O'Brien" To: Andrew Gallatin Message-ID: <20040720003426.GN1070@dragon.nuxi.com> References: <6.1.2.0.2.20040712142407.02d38a98@64.124.166.215> <16627.56844.22088.901721@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16627.56844.22088.901721@grasshopper.cs.duke.edu> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: alc@freebsd.org cc: freebsd-current@freebsd.org cc: Gary Stanley Subject: Re: sendfile problem (Re: Network related procs hang in unusual sfpbsy state) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@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: Tue, 20 Jul 2004 00:34:30 -0000 On Tue, Jul 13, 2004 at 09:05:16AM -0400, Andrew Gallatin wrote: > still busy. Do you have a gdb which can do kernel debugging? > (apparently ports/dev/gdb53 can..) As can ports/dev/gdb6 -- -- David (obrien@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 01:48: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 65D6A16A4CE for ; Tue, 20 Jul 2004 01:48:16 +0000 (GMT) Received: from omoikane.mb.skyweb.ca (omoikane.mb.skyweb.ca [64.42.246.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id F269F43D55 for ; Tue, 20 Jul 2004 01:47:44 +0000 (GMT) (envelope-from mark@skyweb.ca) Received: by omoikane.mb.skyweb.ca (Postfix, from userid 1001) id 352FB61D2D; Mon, 19 Jul 2004 20:47:49 -0500 (CDT) From: Mark Johnston To: current@freebsd.org Date: Mon, 19 Jul 2004 20:47:48 -0500 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: <200407192047.48729.mjohnston@skyweb.ca> Subject: cvs-src summary for July 12-19 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, 20 Jul 2004 01:48:16 -0000 FreeBSD cvs-src summary for 12/07/04 to 19/07/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 ============ libthread_db thread debugging library added ------------------------------------------- David Xu (davidxu) added libthread_db, a library for debugging threaded processes with GDB. Currently, it supports only libpthread, but Marcel Moolenaar (marcel) will be working to add support for libthr and libc_r, the other threading libraries. http://www.freebsd.org/cgi/mid.cgi?200407150336.i6F3aZIw036415 bsdtar becomes the default system tar ------------------------------------- Tim Kientzle (kientzle) changed the system tar from the old GNU tar to his new bsdtar program. You can use the old GNU tar as gtar, or define WITH_GTAR when building and installing the world to make gtar the default. bsdtar is built on Tim's libarchive, which supports many different streaming archive formats, auto-detecting what format you're trying to extract. It also supports file flags, ACLs, and arbitrary device numbers. For more information on libarchive and bsdtar, you can visit `the libarchive page`_. .. _`the libarchive page`: http://people.freebsd.org/~kientzle/libarchive/ http://www.freebsd.org/cgi/mid.cgi?200407170603.i6H63lkv029158 Adaptive mutexes enabled ------------------------ Scott Long (scottl) enabled the code supporting adaptive mutexes, which improve performance when locking in many circumstances. It has been enabled by default on AMD64, but it is now enabled everywhere. This also removes the kernel option ADAPTIVE_MUTEXES and creates one for NO_ADAPTIVE_MUTEXES in its place. http://www.freebsd.org/cgi/mid.cgi?200407181559.i6IFx42N094234 ACPI support for floppy drives added ------------------------------------ Nate Lawson (njl) committed ACPI support for floppy disk drives. http://www.freebsd.org/cgi/mid.cgi?200407151638.i6FGc7Sb061577 RADIUS accounting support in PPP enhanced ----------------------------------------- Brian Somers (brian) committed a patch to PPP to improve the RADIUS accounting support. There is now a "set rad_alive N" command that enables periodic reports of RADIUS accounting data to the server. The code for this was mostly submitted by alx@sm.ukrtel.net. http://www.freebsd.org/cgi/mid.cgi?200407170107.i6H17rub019304 =============== Notable changes =============== fla driver for M-Systems DiskOnChip removed ------------------------------------------- Poul-Henning Kamp (phk) removed the fla driver for M-Systems DiskOnChip devices. http://www.freebsd.org/cgi/mid.cgi?200407081638.i68GcbMo019165 Biba and MLS MAC _single labels renamed to _effective ----------------------------------------------------- Robert Watson (rwatson) renamed the label _single to _effective in the code implementing the Biba and MLS mandatory access control policies. The new _effective label is similar to the use of "effective" in traditional UNIX access control. http://www.freebsd.org/cgi/mid.cgi?200407160203.i6G23oaR078694 Sound device drivers renamed ---------------------------- Seigo Tanimura (tanimura) renamed the sound drivers to make them more consistent, with "sound" being the generic sound driver, and "snd_*" being device-specific drivers. He has also renamed the "snd_pcm" kernel module to "sound" for consistency. http://www.freebsd.org/cgi/mid.cgi?200407160358.i6G3wPIl082809 make world now requires DESTDIR ------------------------------- Marcel Moolenaar (marcel) committed a patch to the system Makefile that requires a DESTDIR variable, for destination directory, to be specified when using the "make world" command. This is to protect people who unknowingly try to use "make world" to upgrade their system, instead of following the instructions in /usr/src/UPDATING, since make world does not upgrade the kernel and can leave the system in an unusable or unbootable state. http://www.freebsd.org/cgi/mid.cgi?200407160251.i6G2pSts080488 ================= Discussion topics ================= kldunload and Newbus -------------------- Poul-Henning Kamp (phk) made a commit to "Give kldunload a -f(orce) argument." This adds new semantics for modules to be asked whether they can unload (called "quiesce") and then unloaded forcefully. Nate Lawson (njl) replied, "Have you kept up on the newbus discussions? The tentative plan was to add quiesce functionality to it as part of device_detach(). [ . . . ] I think duplicating this at multiple layers is not a good idea and the module level is not the right layer to implement it." Scott Long (scottl) said, " It typically won't be duplicated. This particular work is good for things like GEOM modules that don't fit into newbus." Poul-Henning replied, "I wish I could grasp from where this 'newbus fits all' attiude comes, I certainly see nothing anywhere that could explain it." Scott answered, "NetBSD has most things under newbus." Poul-Henning replied, "It is not realistic to expect us to ever tie netgraph modules, tty linedisciplines, network protocols, filesystems, vm objects, vnodes and geom classes together with newbus. [ . . . ] And since all of these things are involved in loadable modules, I think we should stop wasting time dreaming about the day the world will be one bit tangle of newbus." Scott said, "My original statement was just a hypothetical and nothing more. The newbus cabal/bikeshed/whatever is not about to come crashing down on your head.", to which Poul-Henning answered "I know it isn't, and that's was my point." M. Warner Losh (imp) also replied to Poul-Henning's previous post, saying, "I think you should spent less time attacking newbus." Doug Rabson (dfr) added, "And besides, newbus isn't going to take over the world, kobj is ;-)" In another branch, Warner responded to Poul-Henning's question about "newbus fits all", saying, "Too many years of having weird, odd-ball attachments maybe? [ . . . ] Frankly, I dislike your obstructionist attitudes towards newbus." Poul-Henning answered, "Obstructionist ? That's a pretty harsh word for somebody who has wasted a couple of months trying to write a newbus-ified GEOM." Warner clarified, "It just seems that whenever the topic of newbus comes up, you don't want to use it." Poul-Henning responded, "having tried it out [ . . . ], I appreciate the size of the gap between what newbus can today and what it needs to learn before the fully newbusified kernel can be a realistic dream. That is not obstructionist, that is being realistic." Nate followed up to Poul-Henning's post about the newbus-ified GEOM, saying, "I'll happily help review patches/designs for this." Poul-Henning responded, "No need to. It doesn't work because newbus doesn't support multiple interitance." Some highly-technical discussion of newbus between Poul-Henning and Warner followed, in which they concluded that the multiple inheritance added a few months ago would meet Poul-Henning's needs. Robert Watson (rwatson) added a suggestion at the end that further discussion of the Newbus architecture would be well-suited to the arch@ list. A second, shorter thread also spawned from Nate's original post, with Poul-Henning explaining that the quiesce functionality is needed at the module layer because "one kld can contain multiple modules, and since the modules get to veto an unload with MOD_UNLOAD, I don't really see how you can come up with something that doesn't have a MOD_QUIESCE." Nate answered ,"there doesn't have to be MOD_QUIESCE. The normal MOD_UNLOAD request will trigger (multiple calls to) device_detach via a TBD kernel interface." Poul-Henning replied, "This is not about 'eject ed0', this is about 'evict the ed driver'. There is only one sane way to implement that: Pass the flag to the module and have the module decided if it is possible." Colin Percival (cperciva) observed, "this will be useful from the point of view of security as well. When there is a security advisory concerning an optional module (compat/linux being the most recent example) it would be nice to have a more effective workaround than 'well, you can try `kldunload linux`, but it probably won't work... if it doesn't work, you'll have to reboot the system'." Brian Fundakowski Feldman (green) pointed out, "'Well, you can try 'kldunload -f linux', but it probably won't work... if it doesn't work, I guess a crash isn't really much worse than a reboot.'" http://www.freebsd.org/cgi/mid.cgi?200407131936.i6DJaxrp074391 ================= Committer changes ================= Julian Elischer (julian) introduced Gleb Smirnov (glebius) as a new src committer. http://www.freebsd.org/cgi/mid.cgi?200407140650.i6E6om5m093425 Murray Stokely (murray) retired Valentino Vaschetto (logo)'s commit bit for safekeeping. http://www.freebsd.org/cgi/mid.cgi?200407150845.i6F8j5gH047574 =================== Important bug fixes =================== Several rpc.lockd bugs fixed ---------------------------- Michael Reifenberger (mr) committed a patch from Bjorn Gronvall that fixes some lockups and crashes within rpc.lockd, the NFS locking server. This closes `PR 61718`_. .. _`PR 61718`: http://www.freebsd.org/cgi/query-pr.cgi?pr=61718 http://www.freebsd.org/cgi/mid.cgi?200407161930.16GJUxuw009400 =============== Other bug fixes =============== Christian S. J. Peron (csjp) applied a patch to the file descriptor allocation code to prevent a jailed root user from using up the last few file descriptors, which are reserved for root. http://www.freebsd.org/cgi/mid.cgi?200407141904.i6EJ4VKD016422 Max Laier (mlaier) committed a fix to the pf packet filter, which improves routing loop detection. The fix was written by Daniel Hartmeier (dhartmei) and imported from OpenBSD. http://www.freebsd.org/cgi/mid.cgi?200407171715.i6HHFGXJ052457 Soeren Schmidt (sos) committed a fix for newer VIA IDE hard drive controllers, which would hang when their timing setting was reprogrammed to a higher speed than UDMA33. This close `PR 69180`_, although he didn't use the included patch. .. _`PR 69180`: http://www.freebsd.org/cgi/query-pr.cgi?pr=69180 http://www.freebsd.org/cgi/mid.cgi?200407171448.i6HEmkMp044631 Brian Somers (brian) fixed the "set ifaddr" command, which had previously been doing nothing, in ppp. This closes `PR 62050`_. .. _`PR 62050`: http://www.freebsd.org/cgi/query-pr.cgi?pr=62050 http://www.freebsd.org/cgi/mid.cgi?200407150942.i6F9gH1Y049408 From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 01:53: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 B60F216A4CE; Tue, 20 Jul 2004 01:53:52 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A6B343D2F; Tue, 20 Jul 2004 01:53:50 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i6K1oqnE036786; Mon, 19 Jul 2004 19:50:52 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 19 Jul 2004 19:50:56 -0600 (MDT) Message-Id: <20040719.195056.35662742.imp@bsdimp.com> To: iedowse@maths.tcd.ie From: "M. Warner Losh" In-Reply-To: <200407200045.aa99979@salmon.maths.tcd.ie> References: <20040719.170132.52458790.imp@bsdimp.com> <200407200045.aa99979@salmon.maths.tcd.ie> 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: mycroft@NetBSD.org cc: scottl@freebsd.org cc: freebsd-current@freebsd.org cc: pjd@freebsd.org Subject: Re: Unloading USB driver while device is attached. 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, 20 Jul 2004 01:53:52 -0000 In message: <200407200045.aa99979@salmon.maths.tcd.ie> Ian Dowse writes: : In message <20040719.170132.52458790.imp@bsdimp.com>, "M. Warner Losh" writes: : >In message: <200407191950.aa12733@salmon.maths.tcd.ie> : > Ian Dowse writes: : >: http://people.freebsd.org/~iedowse/usb.diff : >: : >: but unfortunately I haven't had time to work on this lately (and : >: there are all the problems of divergence from NetBSD etc. if bits : >: of this get committed). The (small) uhub.c changes look like they : >: might possibly help in your case. With the full patch I was able : >: to `kldunload usb' without crashes a while ago, but there were still : >: memory leaks. : > : >I'm going to start merging in some of these changes, if you don't : >mind. : : If you have the time that would be great! FYI, here is a rough : summary of the changes in no particular order: : : o Beginnings of interrupt pipe support for EHCI (very little done) cool. : o Support for unloading the usb driver (leaks some memory) : o Support for removing cardbus USB controllers (also leaks memory) These are my biggest goals of the moment. : o Avoid most (but not all) uses of contigmalloc and data buffer : copies by using bus_dmamap_load() and a new `struct usb_dma_mapping'. : A few places marked `XXX' need to be checked for crossing DMA : segment boundaries. This is probably the most important change, : as it makes USB work much more reliably on low memory machines. This would be nice. : o Attempt to follow the correct procedure for synchronising with : the BIOS via SMM to take over control of the EHCI controller. : This may fix problems when the BIOS is configured to emulate : legacy devices, but is untested on any affected machines. Docs on how to do this? I've not seen this info... : o Try to make transfers reusable from the completion callback (some : related changes went into NetBSD recently, but I haven't checked : the overlap). I saw that. : There are probably a few other changes in there too - let me know if : you find any stuff that doesn't make sense. OK. Will do. I think we need to look at radically updating the way we do compatibility between the different systems that the usb code runs on. But that's a good way to freak people out by saying such things in public :-) Warner From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 02:33: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 E18F116A4CE; Tue, 20 Jul 2004 02:33:41 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDF0D43D3F; Tue, 20 Jul 2004 02:33:38 +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 i6K2XHsn087329; Tue, 20 Jul 2004 12:03:18 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Tue, 20 Jul 2004 12:03:17 +0930 User-Agent: KMail/1.6.2 References: <20040719161949.17114.qmail@web11405.mail.yahoo.com> <200407191937.04398.dfr@nlsystems.com> In-Reply-To: <200407191937.04398.dfr@nlsystems.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200407201203.17629.doconnor@gsoft.com.au> X-Spam-Score: -5.2 () CARRIAGE_RETURNS,IN_REP_TO,PGP_SIGNATURE,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_01_02,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: simokawa@freebsd.org cc: Andrew Gallatin Subject: Re: Excellent job on the firewire 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, 20 Jul 2004 02:33:42 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 20 Jul 2004 04:07, Doug Rabson wrote: > > I compiled it in with the latest kernel at 17 July, but the box > > cannot ping with a M$ & linux box. > > I have that fixed locally but I want to fix some other problems with the > firewire driver - mainly that my freebsd boxes often go haywire when I > plug a windows box into the bus. I also want to finish writing the code > for freebsd to be a fully functional isochronous bus manager. I couldn't get fwip to work either, but my FreeBSD box doesn't go nuts when= =20 connected to a Windows PC.. If you need a tester I'd be more than happy :) =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 =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/IRt5ZPcIHs/zowRAheTAJ9DOD9aPAuHTegGzewhhbQS/gX8/ACdEcAv 8O7tE5QbeeNl6lwwIpqazKM=3D =3DJIKw =2D----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 02:41: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 A06EC16A4CE; Tue, 20 Jul 2004 02:41:53 +0000 (GMT) Received: from tora.nunu.org (YahooBB219003182029.bbtec.net [219.3.182.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68E7543D45; Tue, 20 Jul 2004 02:41:53 +0000 (GMT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from tora.nunu.org (unknown [192.168.1.2]) by tora.nunu.org (Postfix) with ESMTP id 591DF4E50A; Tue, 20 Jul 2004 11:41:52 +0900 (JST) Date: Tue, 20 Jul 2004 11:41:52 +0900 Message-ID: <87hds3pfgv.wl@tora.nunu.org> From: Hidetoshi Shimokawa To: Doug Rabson In-Reply-To: <200407182104.53221.dfr@nlsystems.com> References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 14) (Reasonable Discussion) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org cc: Andrew Gallatin Subject: Re: Excellent job on the firewire 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, 20 Jul 2004 02:41:53 -0000 (sorry for resending) At Sun, 18 Jul 2004 21:04:53 +0100, Doug Rabson wrote: > > It would be nice to remove my Comtrol Rocketport serial card, and the > > 8 serial cables leading across the middle of the room to my shelf of > > machines and replace it with one firewire cable leading to a firewire > > hub. But, as a firewire newbie, I have some questions: > > > > 1) Is any firewire PCI adapter just as good as any other in terms of > > performance, and FreeBSD support? (prices seem to range from $10 > > to $100) > > Any should do about as well as any other. I probably wouldn't want to > spend more than ~$50 on one. I got some bad report about Lucent chip(some Mac's have it) but I haven't heard any other compatibility issue. I think the price of the adapter doesn't matter but you may have trouble with some bad cables. If have some problem, use lower speed(S100) or change cables. > > > > 2) Is dcons usable after a panic (ie, DDB or KDB_TRACE)? Or is it > > only usable for remote-gdb? > > Dcons provides two full duplex streams - one for console and one for > gdb. You can use DDB on the console just like normal. It's designed for such panic/debugging situation. Actually, it's rather inefficient for usual situation but the speed of FireWire hide the problem ;-) > > > > 3) Is dcons endian and pointer-size agonstic? Can I run consoles to > > an amd64 and a powerpc box from an x86? > > I haven't actually tried that and I imagine that there might be issues > here and there. Any problems are likely to be in the dconschat program > but that should be pretty easy to fix since its entirely userland. I should have no problem with 64bit arch and big endian. I have tested with sparc64, powerpc and amd64. > > > > 4) Does the loader know about dcons? Eg, can I do "unload boot > > kernel.test" using dcons? > > Actually thats the only downside of dcons. It doesn't cut in until the > firewire controller attaches. It relies on the fact that the fwohci > driver allows access to physical memory from any node on the bus > (implemeted in hardware so you can examine the memory of a hung > machine). The dconschat program uses this feature to access the dcons > ring buffers in the target machine. > > I could imagine a dcons driver in the loader which just enabled physical > access and used some kind of loader trick to hand off the ring buffers > to the kernel dcons driver. It doesn't exist though - say nice things You are right. > to the author and he might find the time for it :-) It is not enough :-< I lack the knowledge of BIOS/PCI(and ACPI?). Once we can access the OHCI register via PCI in the loader, the remaining part is relatively easy as you described. I need some help for this part. I suppose that implementing dcons in the loader is architecture dependent. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 02:42: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 42A4816A4CE; Tue, 20 Jul 2004 02:42:13 +0000 (GMT) Received: from tora.nunu.org (YahooBB219003182029.bbtec.net [219.3.182.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13D0A43D55; Tue, 20 Jul 2004 02:42:13 +0000 (GMT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from tora.nunu.org (unknown [192.168.1.2]) by tora.nunu.org (Postfix) with ESMTP id 672BA4E50E; Tue, 20 Jul 2004 11:42:12 +0900 (JST) Date: Tue, 20 Jul 2004 11:42:12 +0900 Message-ID: <87fz7npfgb.wl@tora.nunu.org> From: Hidetoshi Shimokawa To: Shizuka Kudo In-Reply-To: <200407191937.04398.dfr@nlsystems.com> References: <20040719161949.17114.qmail@web11405.mail.yahoo.com> <200407191937.04398.dfr@nlsystems.com> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 14) (Reasonable Discussion) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org cc: Andrew Gallatin Subject: Re: Excellent job on the firewire 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, 20 Jul 2004 02:42:13 -0000 (sorry for resending) At Mon, 19 Jul 2004 19:37:04 +0100, Doug Rabson wrote: > > On Monday 19 July 2004 17:19, Shizuka Kudo wrote: > > Hi, > > > > Anyone has experience with the newly added IP over 1394 support, i.e. > > fwip? > > > > I compiled it in with the latest kernel at 17 July, but the box > > cannot ping with a M$ & linux box. > > I have that fixed locally but I want to fix some other problems with the > firewire driver - mainly that my freebsd boxes often go haywire when I > plug a windows box into the bus. I also want to finish writing the code > for freebsd to be a fully functional isochronous bus manager. Try this patch for temporary fix. --- //depot/vendor/freebsd/src/sys/dev/firewire/if_fwip.c 2004/06/14 09:36:01 +++ //depot/user/simokawa/firewire/sys/dev/firewire/if_fwip.c 2004/07/11 06:47:39 @@ -91,7 +91,7 @@ static void fwip_unicast_input(struct fw_xfer *); static int fwipdebug = 0; -static int broadcast_channel = 31; /* XXX */ +static int broadcast_channel = 0xc0 | 0x1f; /* tag | channel(XXX) */ static int tx_speed = 2; static int rx_queue_len = FWMAXQUEUE; /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 03: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 451CA16A4CE; Tue, 20 Jul 2004 03:19:30 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC9BE43D49; Tue, 20 Jul 2004 03:19:29 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from h00609772adf0.ne.client2.attbi.com ([66.30.114.143]) by comcast.net (sccrmhc12) with ESMTP id <2004072003192601200frgd1e>; Tue, 20 Jul 2004 03:19:28 +0000 Received: from h00609772adf0.ne.client2.attbi.com (localhost [127.0.0.1]) i6K3JL6h000727; Mon, 19 Jul 2004 23:19:22 -0400 (EDT) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost)i6K3JKTI000726; Mon, 19 Jul 2004 23:19:20 -0400 (EDT) (envelope-from rodrigc) Date: Mon, 19 Jul 2004 23:19:18 -0400 From: Craig Rodrigues To: Ian Dowse Message-ID: <20040720031918.GA692@crodrigues.org> References: <20040719.170132.52458790.imp@bsdimp.com> <200407200045.aa99979@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200407200045.aa99979@salmon.maths.tcd.ie> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org cc: scottl@freebsd.org cc: "M. Warner Losh" Subject: Re: Unloading USB driver while device is attached. 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, 20 Jul 2004 03:19:30 -0000 On Tue, Jul 20, 2004 at 12:45:08AM +0100, Ian Dowse wrote: > In message <20040719.170132.52458790.imp@bsdimp.com>, "M. Warner Losh" writes: > >In message: <200407191950.aa12733@salmon.maths.tcd.ie> > > Ian Dowse writes: > >: http://people.freebsd.org/~iedowse/usb.diff This patch doesn't solve my EHCI problems ( see: http://lists.freebsd.org/pipermail/freebsd-current/2004-July/031838.html ) but it seems like a step in the right direction. For one thing, I don't panic in EHCI when I reboot my system after using my Creative Nomad. I had to change your patch a bit so that it would work against version 1.86 of usbdi.c: Index: usbdi.c =================================================================== RCS file: /home/ncvs/src/sys/dev/usb/usbdi.c,v retrieving revision 1.86 diff -u -r1.86 usbdi.c --- usbdi.c 19 Jul 2004 20:49:02 -0000 1.86 +++ usbdi.c 20 Jul 2004 03:16:46 -0000 @@ -85,6 +85,10 @@ Static usbd_status usbd_open_pipe_ival (usbd_interface_handle, u_int8_t, u_int8_t, usbd_pipe_handle *, int); Static int usbd_xfer_isread(usbd_xfer_handle xfer); +Static void usbd_start_transfer(void *arg, bus_dma_segment_t *segs, int nseg, + int error); +Static void usbd_alloc_callback(void *arg, bus_dma_segment_t *segs, int nseg, + int error); Static int usbd_nbuses = 0; @@ -281,7 +285,7 @@ usbd_transfer(usbd_xfer_handle xfer) { usbd_pipe_handle pipe = xfer->pipe; - usb_dma_t *dmap = &xfer->dmabuf; + struct usb_dma_mapping *dmap = &xfer->dmamap; usbd_status err; u_int size; int s; @@ -300,43 +304,36 @@ size = xfer->length; /* If there is no buffer, allocate one. */ if (!(xfer->rqflags & URQ_DEV_DMABUF) && size != 0) { - struct usbd_bus *bus = pipe->device->bus; + bus_dma_tag_t tag = pipe->device->bus->buffer_dmatag; #ifdef DIAGNOSTIC if (xfer->rqflags & URQ_AUTO_DMABUF) printf("usbd_transfer: has old buffer!\n"); #endif - err = bus->methods->allocm(bus, dmap, size); + err = bus_dmamap_create(tag, 0, &dmap->map); if (err) - return (err); - xfer->rqflags |= URQ_AUTO_DMABUF; - } - - /* Copy data if going out. */ - if (!(xfer->flags & USBD_NO_COPY) && size != 0 && - !usbd_xfer_isread(xfer)) - memcpy(KERNADDR(dmap, 0), xfer->buffer, size); - - err = pipe->methods->transfer(xfer); + return (USBD_NOMEM); - if (err != USBD_IN_PROGRESS && err) { - /* The transfer has not been queued, so free buffer. */ - if (xfer->rqflags & URQ_AUTO_DMABUF) { - struct usbd_bus *bus = pipe->device->bus; - - bus->methods->freem(bus, &xfer->dmabuf); + xfer->rqflags |= URQ_AUTO_DMABUF; + err = bus_dmamap_load(tag, dmap->map, xfer->buffer, size, + usbd_start_transfer, xfer, 0); + if (err != 0 && err != EINPROGRESS) { xfer->rqflags &= ~URQ_AUTO_DMABUF; + bus_dmamap_destroy(tag, dmap->map); + return (USBD_INVAL); } + } else if (size != 0) { + usbd_start_transfer(xfer, dmap->segs, dmap->nsegs, 0); + } else { + usbd_start_transfer(xfer, NULL, 0, 0); } if (!(xfer->flags & USBD_SYNCHRONOUS)) - return (err); + return (xfer->done ? 0 : USBD_IN_PROGRESS); /* Sync transfer, wait for completion. */ - if (err != USBD_IN_PROGRESS) - return (err); s = splusb(); - if (!xfer->done) { + while (!xfer->done) { if (pipe->device->bus->use_polling) panic("usbd_transfer: not done"); tsleep(xfer, PRIBIO, "usbsyn", 0); @@ -345,6 +342,51 @@ return (xfer->status); } +Static void +usbd_start_transfer(void *arg, bus_dma_segment_t *segs, int nseg, int error) +{ + usbd_xfer_handle xfer = arg; + usbd_pipe_handle pipe = xfer->pipe; + struct usb_dma_mapping *dmap = &xfer->dmamap; + bus_dma_tag_t tag = pipe->device->bus->buffer_dmatag; + int err, i; + + if (error != 0) { + KASSERT(xfer->rqflags & URQ_AUTO_DMABUF, + ("usbd_start_transfer: error with non-auto buf")); + if (nseg > 0) + bus_dmamap_unload(tag, dmap->map); + bus_dmamap_destroy(tag, dmap->map); + /* XXX */ + usb_insert_transfer(xfer); + xfer->status = USBD_IOERROR; + usb_transfer_complete(xfer); + return; + } + + if (segs != dmap->segs) { + for (i = 0; i < nseg; i++) + dmap->segs[i] = segs[i]; + dmap->nsegs = nseg; + } + + if (segs > 0 && !usbd_xfer_isread(xfer)) + bus_dmamap_sync(tag, dmap->map, BUS_DMASYNC_PREREAD); + err = pipe->methods->transfer(xfer); + if (err != USBD_IN_PROGRESS && err) { + if (xfer->rqflags & URQ_AUTO_DMABUF) { + bus_dmamap_unload(tag, dmap->map); + bus_dmamap_destroy(tag, dmap->map); + xfer->rqflags &= ~URQ_AUTO_DMABUF; + } + /* XXX */ + usb_insert_transfer(xfer); + xfer->status = err; + usb_transfer_complete(xfer); + return; + } +} + /* Like usbd_transfer(), but waits for completion. */ usbd_status usbd_sync_transfer(usbd_xfer_handle xfer) @@ -353,42 +395,103 @@ return (usbd_transfer(xfer)); } +struct usbd_allocstate { + usbd_xfer_handle xfer; + int done; + int error; + int waiting; +}; + void * usbd_alloc_buffer(usbd_xfer_handle xfer, u_int32_t size) { - struct usbd_bus *bus = xfer->device->bus; + struct usbd_allocstate allocstate; + struct usb_dma_mapping *dmap = &xfer->dmamap; + bus_dma_tag_t tag = xfer->device->bus->buffer_dmatag; + void *buf; usbd_status err; + int error, s; -#ifdef DIAGNOSTIC - if (xfer->rqflags & (URQ_DEV_DMABUF | URQ_AUTO_DMABUF)) - printf("usbd_alloc_buffer: xfer already has a buffer\n"); -#endif - err = bus->methods->allocm(bus, &xfer->dmabuf, size); + KASSERT((xfer->rqflags & (URQ_DEV_DMABUF | URQ_AUTO_DMABUF)) == 0, + ("usbd_alloc_buffer: xfer already has a buffer")); + err = bus_dmamap_create(tag, 0, &dmap->map); if (err) return (NULL); + buf = malloc(size, M_USB, M_WAITOK); + + allocstate.xfer = xfer; + allocstate.done = 0; + allocstate.error = 0; + allocstate.waiting = 0; + error = bus_dmamap_load(tag, dmap->map, buf, size, usbd_alloc_callback, + &allocstate, 0); + if (error && error != EINPROGRESS) { + bus_dmamap_destroy(tag, dmap->map); + free(buf, M_USB); + return (NULL); + } + if (error == EINPROGRESS) { + /* Wait for completion. */ + s = splusb(); + allocstate.waiting = 1; + while (!allocstate.done) + tsleep(&allocstate, PRIBIO, "usbdab", 0); + splx(s); + error = allocstate.error; + } + if (error) { + bus_dmamap_unload(tag, dmap->map); + bus_dmamap_destroy(tag, dmap->map); + free(buf, M_USB); + return (NULL); + } + + xfer->allocbuf = buf; xfer->rqflags |= URQ_DEV_DMABUF; - return (KERNADDR(&xfer->dmabuf, 0)); + return (buf); } void usbd_free_buffer(usbd_xfer_handle xfer) { -#ifdef DIAGNOSTIC - if (!(xfer->rqflags & (URQ_DEV_DMABUF | URQ_AUTO_DMABUF))) { - printf("usbd_free_buffer: no buffer\n"); - return; - } -#endif - xfer->rqflags &= ~(URQ_DEV_DMABUF | URQ_AUTO_DMABUF); - xfer->device->bus->methods->freem(xfer->device->bus, &xfer->dmabuf); + struct usb_dma_mapping *dmap = &xfer->dmamap; + bus_dma_tag_t tag = xfer->device->bus->buffer_dmatag; + + KASSERT((xfer->rqflags & (URQ_DEV_DMABUF | URQ_AUTO_DMABUF)) == + URQ_DEV_DMABUF, ("usbd_free_buffer: no/auto buffer")); + + xfer->rqflags &= ~URQ_DEV_DMABUF; + bus_dmamap_unload(tag, dmap->map); + bus_dmamap_destroy(tag, dmap->map); + free(xfer->allocbuf, M_USB); + xfer->allocbuf = NULL; } void * usbd_get_buffer(usbd_xfer_handle xfer) { if (!(xfer->rqflags & URQ_DEV_DMABUF)) - return (0); - return (KERNADDR(&xfer->dmabuf, 0)); + return (NULL); + return (xfer->allocbuf); +} + +Static void +usbd_alloc_callback(void *arg, bus_dma_segment_t *segs, int nseg, int error) +{ + struct usbd_allocstate *allocstate = arg; + usbd_xfer_handle xfer = allocstate->xfer; + struct usb_dma_mapping *dmap = &xfer->dmamap; + int i; + + allocstate->error = error; + if (error == 0) { + for (i = 0; i < nseg; i++) + dmap->segs[i] = segs[i]; + dmap->nsegs = nseg; + } + allocstate->done = 1; + if (allocstate->waiting) + wakeup(&allocstate); } usbd_xfer_handle @@ -746,6 +849,7 @@ pipe, xfer, pipe->methods)); /* Make the HC abort it (and invoke the callback). */ pipe->methods->abort(xfer); + KASSERT(SIMPLEQ_FIRST(&pipe->queue) != xfer, ("usbd_ar_pipe")); /* XXX only for non-0 usbd_clear_endpoint_stall(pipe); */ } pipe->aborting = 0; @@ -757,12 +861,14 @@ usb_transfer_complete(usbd_xfer_handle xfer) { usbd_pipe_handle pipe = xfer->pipe; - usb_dma_t *dmap = &xfer->dmabuf; + struct usb_dma_mapping *dmap = &xfer->dmamap; + bus_dma_tag_t tag = pipe->device->bus->buffer_dmatag; + usbd_status status; int sync = xfer->flags & USBD_SYNCHRONOUS; int erred = xfer->status == USBD_CANCELLED || - xfer->status == USBD_TIMEOUT; + xfer->status == USBD_TIMEOUT; int repeat = pipe->repeat; - int polling; + int polling, xfer_flags; SPLUSBCHECK; @@ -787,23 +893,14 @@ if (polling) pipe->running = 0; - if (!(xfer->flags & USBD_NO_COPY) && xfer->actlen != 0 && - usbd_xfer_isread(xfer)) { -#ifdef DIAGNOSTIC - if (xfer->actlen > xfer->length) { - printf("usb_transfer_complete: actlen > len %d > %d\n", - xfer->actlen, xfer->length); - xfer->actlen = xfer->length; - } -#endif - memcpy(xfer->buffer, KERNADDR(dmap, 0), xfer->actlen); - } + if (xfer->actlen != 0 && usbd_xfer_isread(xfer)) + bus_dmamap_sync(tag, dmap->map, BUS_DMASYNC_POSTWRITE); - /* if we allocated the buffer in usbd_transfer() we free it here. */ + /* if we mapped the buffer in usbd_transfer() we unmap it here. */ if (xfer->rqflags & URQ_AUTO_DMABUF) { if (!repeat) { - struct usbd_bus *bus = pipe->device->bus; - bus->methods->freem(bus, dmap); + bus_dmamap_unload(tag, dmap->map); + bus_dmamap_destroy(tag, dmap->map); xfer->rqflags &= ~URQ_AUTO_DMABUF; } } @@ -833,28 +930,32 @@ xfer->status = USBD_SHORT_XFER; } - if (xfer->callback) - xfer->callback(xfer, xfer->priv, xfer->status); - -#ifdef DIAGNOSTIC - if (pipe->methods->done != NULL) + /* Copy any xfer fields in case the xfer goes away in the callback. */ + status = xfer->status; + xfer_flags = xfer->flags; + /* + * For repeat operations, call the callback first, as the xfer + * will not go away and the "done" method may modify it. Otherwise + * reverse the order in case the callback wants to free or reuse + * the xfer. + */ + if (repeat) { + if (xfer->callback) + xfer->callback(xfer, xfer->priv, status); pipe->methods->done(xfer); - else - printf("usb_transfer_complete: pipe->methods->done == NULL\n"); -#else - pipe->methods->done(xfer); -#endif - - if (sync && !polling) - wakeup(xfer); + } else { + pipe->methods->done(xfer); + if (xfer->callback) + xfer->callback(xfer, xfer->priv, status); - if (!repeat) { /* XXX should we stop the queue on all errors? */ if (erred && pipe->iface != NULL) /* not control pipe */ pipe->running = 0; else usbd_start_next(pipe); } + if (sync && !polling) + wakeup(xfer); } usbd_status @@ -875,6 +976,7 @@ xfer->busy_free = XFER_ONQU; #endif s = splusb(); + KASSERT(SIMPLEQ_FIRST(&pipe->queue) != xfer, ("usb_insert_transfer")); SIMPLEQ_INSERT_TAIL(&pipe->queue, xfer, next); if (pipe->running) err = USBD_IN_PROGRESS; -- Craig Rodrigues http://crodrigues.org rodrigc@crodrigues.org From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 03:35: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 1531C16A4CE for ; Tue, 20 Jul 2004 03:35:26 +0000 (GMT) Received: from cpanel.ezone.ru (cpanel.ezone.ru [213.85.31.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77D5243D46 for ; Tue, 20 Jul 2004 03:35:24 +0000 (GMT) (envelope-from mcsi@mcsi.pp.ru) Received: from [81.195.16.54] (ppp16-54.pppoe.mtu-net.ru [81.195.16.54]) (authenticated bits=0) by cpanel.ezone.ru (8.12.11/8.12.11) with ESMTP id i6K3YbJS011741 for ; Tue, 20 Jul 2004 07:35:18 +0400 (MSD) (envelope-from mcsi@mcsi.pp.ru) Message-ID: <40FC92C8.50604@mcsi.pp.ru> Date: Tue, 20 Jul 2004 07:34:32 +0400 From: Maxim Maximov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040716 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <40FC3090.9060305@freebsd.org> In-Reply-To: <40FC3090.9060305@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mail3.ezone.ru Subject: Re: HEADS UP [Re: thread+preemption stability improvement] 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, 20 Jul 2004 03:35:26 -0000 Scott Long wrote: > All, > > Initial testing of this patch looks very promising. For those that > aren't comfortable with patching their sources by hand, note that it > was committed to CVS a few hours ago and should be showing up on CVSup > very shortly (rev 1.8 of sys/i386/i386/intr_machdep.c is what you want > if you are running i386). Please go out and test this as much as > possible so that we can determine if futher action is needed. I think it is needed :( Things actually get _much_ better, now I've been able to use my big IMAP folders, but still after applying the patch and working about an hour mozilla freezes with the same sympthoms (cpu fan gets spinning faster and faster as if cpu temperature is raising). Are there any ways I can help track this down further? Preemption is enabled, of course. My kernel's config is latest GENERIC with these additions: ###### device pf device pflog options ALTQ options ALTQ_CBQ # Class Bases Queueing options ALTQ_RED # Random Early Drop options ALTQ_RIO # RED In/Out options ALTQ_HFSC # Hierarchical Packet Scheduler options ALTQ_CDNR # Traffic conditioner options ALTQ_PRIQ # Priority Queueing options ALTQ_NOPCC # Required for SMP build options ALTQ_DEBUG device radeondrm device acpi_asus device sound device snd_ich options ALT_BREAK_TO_DEBUGGER options MSGBUF_SIZE=245760 My system is the notebook ASUS L5Ga. At boot I'm getting many witness messages like these and I turned on debug.mpsafenet=1. Can this be a problem? malloc(M_WAITOK) of "16", forcing M_NOWAIT with the following non-sleepable locks held: exclusive sleep mutex skc0 (network driver) r = 0 (0xc1aa6ec0) locked @ /usr/src/sys/pci/if_sk.c:673 KDB: stack backtrace: kdb_backtrace(c09e225c,c0c2170c,1,c094ba5c,10) at kdb_backtrace+0x2e witness_warn(5,0,c0904908,c08cb429,c094d020) at witness_warn+0x1b5 uma_zalloc_arg(c10352c0,0,2,c10458c0,c1ace74c) at uma_zalloc_arg+0x4c malloc(c,c094d020,2,c1ae7c80,9) at malloc+0xd6 sysctl_ctx_entry_add(c1ace74c,c1ab9a00,2,8,c1ace74c) at sysctl_ctx_entry_add+0x3d sysctl_add_oid(c1ace74c,c1ae7d10,ffffffff,c08ecd32,80000000) at sysctl_add_oid+0x1a6 device_sysctl_init(c1ace700,c1a29430,c19ce6c0,c1ace700,c1ace700) at device_sysctl_init+0x1c0 device_attach(c1ace700,c1ace700,c08f9f99,c1acf7e0,c1ace700) at device_attach+0x13 device_probe_and_attach(c1ace700,c1ace380,c0c21838,c05b5679,c1ace380) at device_probe_and_attach+0xd1 bus_generic_attach(c1ace380,f0000000,c07d2d20,c07d2d60,c1ace380) at bus_generic_attach+0x28 miibus_attach(c1ace380,c1a0b84c,c0916570,c1ace380,c1ace380) at miibus_attach+0x59 device_attach(c1ace380,c1ace380,1,0,c1ace380) at device_attach+0x6a device_probe_and_attach(c1ace380,0,c0c218ac,c05b5adb,c1ace000) at device_probe_and_attach+0xd1 bus_generic_attach(c1ace000,0,1,0,c1ae3000) at bus_generic_attach+0x28 mii_phy_probe(c1ace000,c1ae3220,c07d2d20,c07d2d60,ffffffff) at mii_phy_probe+0x11b sk_attach(c1ace000,c1a3784c,c0916570,c1ace000,c1ace000) at sk_attach+0x3a2 device_attach(c1ace000,c1ace000,c0c2193c,c069c0ef,c1ace000) at device_attach+0x6a device_probe_and_attach(c1ace000,c1aa6680,c0c21978,c07d3ba5,c1aa6780) at device_probe_and_attach+0xd1 bus_generic_attach(c1aa6780,11a,1,c0c21964,ffffffff) at bus_generic_attach+0x28 skc_attach(c1aa6780,c1a3804c,c0916570,c1aa6780,c1aa6780) at skc_attach+0x495 device_attach(c1aa6780,c1aa6780,c1974c00,1,c1aa6780) at device_attach+0x6a device_probe_and_attach(c1aa6780,c1aa6280,c0c21a00,c0b120db,c1aa6680) at device_probe_and_attach+0xd1 bus_generic_attach(c1aa6680,c1974c00,1,c0b11dc0,c1aa6680) at bus_generic_attach+0x28 acpi_pci_attach(c1aa6680,c1aa6680,c19ff100,c1aa6680,c1aa6680) at acpi_pci_attach+0x13b device_attach(c1aa6680,c1aa6680,c1aa0780,c1aa6280,c1aa6680) at device_attach+0x6a device_probe_and_attach(c1aa6680,c1aa0780,c0c21a84,c0b1228e,c1aa6280) at device_probe_and_attach+0xd1 bus_generic_attach(c1aa6280,c1ad4f30,2,c0c21a74,c0c21a7c) at bus_generic_attach+0x28 acpi_pcib_attach(c1aa6280,c1ad4f30,2,c0c21aa0,c1aa6280) at acpi_pcib_attach+0x19e acpi_pcib_pci_attach(c1aa6280,c1aa6280,0,c1aa6280,c1aa6280) at acpi_pcib_pci_attach+0x9f device_attach(c1aa6280,c1aa6280,c1968480,c1aa6100,c1aa6280) at device_attach+0x6a device_probe_and_attach(c1aa6280,c19d2c00,c0c21b38,c0b120db,c1aa0780) at device_probe_and_attach+0xd1 bus_generic_attach(c1aa0780,c1968480,1,c0b11dc0,c1aa0780) at bus_generic_attach+0x28 acpi_pci_attach(c1aa0780,c1a7904c,c0916570,c1aa0780,c1aa0780) at acpi_pci_attach+0x13b device_attach(c1aa0780,c1aa0780,c1a83800,c19d2c00,c1aa0780) at device_attach+0x6a device_probe_and_attach(c1aa0780,c1a83800,c0c21bbc,c0b1228e,c19d2c00) at device_probe_and_attach+0xd1 bus_generic_attach(c19d2c00,c1a92ed4,0,c0c21bac,0) at bus_generic_attach+0x28 acpi_pcib_attach(c19d2c00,c1a92ed4,0,c0c21be4,c0916570) at acpi_pcib_attach+0x19e acpi_pcib_acpi_attach(c19d2c00,c1a7884c,c0916570,c19d2c00,c19d2c00) at acpi_pcib_acpi_attach+0x270 device_attach(c19d2c00,c19d2c00,c0b2a488,c0c21c48,c19d2c00) at device_attach+0x6a device_probe_and_attach(c19d2c00,4,c0c21c74,c0b0e96b,c1a83800) at device_probe_and_attach+0xd1 bus_generic_attach(c1a83800,c1968e40,64,c0b0ea30,c1a83800) at bus_generic_attach+0x28 acpi_probe_children(c1a83800,c0b10f60,c1a83780,0,1a4) at acpi_probe_children+0x9b acpi_attach(c1a83800,c1a6b04c,c0916570,c1a83800,c1a83800) at acpi_attach+0x732 device_attach(c1a83800,c1a83800,c1a295c0,c0c21d08,c1a83800) at device_attach+0x6a device_probe_and_attach(c1a83800,c1a83980,c0c21d18,c087310c,c1a83980) at device_probe_and_attach+0xd1 bus_generic_attach(c1a83980,c1a83980,c0c21d38,c06c039a,c1a83980) at bus_generic_attach+0x28 nexus_attach(c1a83980,c1a5b84c,c0916570,c1a83980,c1a83980) at nexus_attach+0x1c device_attach(c1a83980,c1a83980,c1969af8,c0985050,c1a83980) at device_attach+0x6a device_probe_and_attach(c1a83980,c1969af8,c0c21d80,c0860619,c197ca00) at device_probe_and_attach+0xd1 root_bus_configure(c197ca00,c090a3c2,0,c0c21d98,c067d045) at root_bus_configure+0x28 configure(0,c1e000,c1ec00,c1e000,0) at configure+0x29 mi_startup() at mi_startup+0xb5 begin() at begin+0x2c -- Maxim Maximov From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 03:42: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 486E616A4CE; Tue, 20 Jul 2004 03:42:17 +0000 (GMT) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD20C43D4C; Tue, 20 Jul 2004 03:42:16 +0000 (GMT) (envelope-from nork@FreeBSD.org) Received: from melfina.ninth-nine.com ([IPv6:2002:d312:f91e::1]) (authenticated bits=0) by sakura.ninth-nine.com (8.12.11/8.12.11/NinthNine) with ESMTP id i6K3g7tx052880; Tue, 20 Jul 2004 12:42:07 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Tue, 20 Jul 2004 12:42:00 +0900 From: Norikatsu Shigemura To: freebsd-current@FreeBSD.org Message-Id: <20040720124200.03ce0672.nork@FreeBSD.org> In-Reply-To: <87hds3pfgv.wl@tora.nunu.org> References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> <87hds3pfgv.wl@tora.nunu.org> X-Mailer: Sylpheed version 0.9.12-gtk2-20040622 (GTK+ 2.4.4; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.5.3 (sakura.ninth-nine.com [IPv6:2002:db7f:4a79::1]); Tue, 20 Jul 2004 12:42:07 +0900 (JST) cc: simokawa@FreeBSD.org cc: gallatin@cs.duke.edu Subject: Re: Excellent job on the firewire 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, 20 Jul 2004 03:42:17 -0000 On Tue, 20 Jul 2004 11:41:52 +0900 Hidetoshi Shimokawa wrote: > > to the author and he might find the time for it :-) > It is not enough :-< I lack the knowledge of BIOS/PCI(and ACPI?). > Once we can access the OHCI register via PCI in the loader, > the remaining part is relatively easy as you described. > I need some help for this part. I suppose that implementing dcons > in the loader is architecture dependent. I want it! :-) Anyone, do you try to support dcons on BOOT? If someone do it, we will be able to change serial console - sio to fwohci. From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 03:54: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 0C85816A4CE; Tue, 20 Jul 2004 03:54:59 +0000 (GMT) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7311243D41; Tue, 20 Jul 2004 03:54:58 +0000 (GMT) (envelope-from nork@FreeBSD.org) Received: from melfina.ninth-nine.com ([IPv6:2002:d312:f91e::1]) (authenticated bits=0) by sakura.ninth-nine.com (8.12.11/8.12.11/NinthNine) with ESMTP id i6K3svEd053175; Tue, 20 Jul 2004 12:54:57 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Tue, 20 Jul 2004 12:54:57 +0900 From: Norikatsu Shigemura To: John Baldwin Message-Id: <20040720125457.3a378f6b.nork@FreeBSD.org> In-Reply-To: <200406301124.22611.jhb@FreeBSD.org> References: <200407152223.i6FMNRV2001315@sakura.ninth-nine.com> <200407152330.i6FNU5NQ003006@sakura.ninth-nine.com> <200407161811.i6GIBlIi095775@sakura.ninth-nine.com> <200406301124.22611.jhb@FreeBSD.org> X-Mailer: Sylpheed version 0.9.12-gtk2-20040622 (GTK+ 2.4.4; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.5.3 (sakura.ninth-nine.com [IPv6:2002:db7f:4a79::1]); Tue, 20 Jul 2004 12:54:57 +0900 (JST) cc: freebsd-current@FreeBSD.org Subject: Re: panic at turnstile_wait (Re: panic at sched_add_internal) 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, 20 Jul 2004 03:54:59 -0000 On Wed, 30 Jun 2004 11:24:22 -0400 John Baldwin wrote: > > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > > - - [thread 100124] > > > Stopped at turnstile_wait+0x17a: movl %eax,0x10(%edx) > > > db> trace > > > turnstile_wait(c301e340,c0877f40,c36e4420,c0877f40,f9) at > > > turnstile_wait+0x17a _mtx_lock_sleep(c0877f40,0,c07bd610,f9,0) at > > > _mtx_lock_sleep+0x125 _mtx_lock_flags(c0877f40,0,c07bd610,f9,0) at > > > _mtx_lock_flags+0x64 > > [...] > > > --> LIST_INSERT_HEAD(&ts->ts_free, td->td_turnstile, ts_hash); > > > MPASS(owner == ts->ts_owner); > > > } > > > td->td_turnstile = NULL; > > > [...] > > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > > - - > > Same panic has happend at same place on new current (+1day). > Do you have INVARIANTS turned on? Also, can you capture the actual panic Sorry, I didn't turned on INVARIANTS. So I turned on INVARIANTS and INVARIANT_SUPPORT. And I confirmed this behavior on more newer current. > message? If you do have INVARIANTS on, then it seems that pointers are > magically changing to NULL after the assertion check. I'd be worried about > bad memory. My machine was freezed... I cannot get more than following message:-(. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - panic: kse/thread mismatch cpuid = 1; KDB: enter: panic [thread 100124] Stopped at kdb_enter+0x30: movl %ebp,%esp db> trace kdb_enter(c072a43e,1,c072aa83,e3de1bdc,100) at kdb_enter+0x30 panic(c072aa83,1,c072aa97,c3317420,c2c1ea20) at panic+0x156 choosethread(c2c1ea20,c2c1ea20,c072b93b,46e,c07d0cc0) at choosethread+0x50 sched_switch(c3317420,0,c072ad0c,123,6da69d09) at sched_switch+0x109 mi_switch(1,0,c072d2e1,20b,c07db4e8) at mi_switch+0x2af turnstile_wait(0,c07d0d00,c2c1db00,20e,c3317420) at turnstile_wait+0x351 _mtx_lock_sleep(c07d0d00,0,c074b796,3df,0) at _mtx_lock_sleep+0x195 _mtx_lock_flags(c07d0d00,0,c074b796,3df,4) at _mtx_lock_flags+0xb2 syscall(2f,2f,2f,8076500,8076500) at syscall+0x1bd Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (196, FreeBSD ELF32, getdirentries), eip = 0x6822e9df, esp = 0xbfadce94, ebp = 0xbfadceb0 --- db> gdb Step to enter the remote GDB backend. db> s [freeze] - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 03:59: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 ED28816A4CE; Tue, 20 Jul 2004 03:59:17 +0000 (GMT) Received: from smtp-gw-cl-c.dmv.com (smtp-gw-cl-c.dmv.com [216.240.97.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D0E943D66; Tue, 20 Jul 2004 03:59:17 +0000 (GMT) (envelope-from sven@dmv.com) Received: from mail-gw-cl-b.dmv.com (mail-gw-cl-b.dmv.com [216.240.97.39]) i6K3xG9D019858; Mon, 19 Jul 2004 23:59:16 -0400 (EDT) (envelope-from sven@dmv.com) Received: from [192.168.1.2] (dogpound.dyndns.org [64.45.134.154]) by mail-gw-cl-b.dmv.com (8.12.9/8.12.9) with ESMTP id i6K3xFnq078284; Mon, 19 Jul 2004 23:59:16 -0400 (EDT) (envelope-from sven@dmv.com) Message-ID: <40FC9824.9060003@dmv.com> Date: Mon, 19 Jul 2004 23:57:24 -0400 From: Sven Willenberger User-Agent: Mozilla Thunderbird 0.7+ (Windows/20040715) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <1090016941.32571.22.camel@lanshark.dmv.com> In-Reply-To: <1090016941.32571.22.camel@lanshark.dmv.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.39 cc: current@freebsd.org Subject: Re: edquota -t broken? 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, 20 Jul 2004 03:59:18 -0000 Sven Willenberger wrote: > Having never had to concern myself with changing the grace period on > quota filesystems I never came across this issue before. Using the -t > flag to edquota to change the grace period on the file system in > question has utterly no effect. Whether I take someone who was > overquota, raise their quota and lower it, or cause a new user to go > overquota, the grace period always starts counting down from 7 days. > > This occurs on 4.7 FreeBSD as well as 5.2.1-P8. The odd thing is that I > can go into /usr/src/ufs/ufs/quota.h and change the #DEFINE MAX_DQ_TIME > to equal 30 days instead of 7 days and then recompiling quota.c edquota. > c and so on. > > When I invoke edquota -t -f /usr/home for example it *does* display: > > Time units may be: days, hours, minutes, or seconds > Grace period before enforcing soft limits for users: > /usr/home: block grace period: 30 days, file grace period: 0 days > > But this has utterly no effect on the quota reporting. Just to check if > maybe it was the quota program misreporting it, I wrote a quick c > program to check the value of dqb_btime from the structure defined in > quota.h: > > struct dqblk { > u_int32_t dqb_bhardlimit; /* absolute limit on disk blks > alloc */ > u_int32_t dqb_bsoftlimit; /* preferred limit on disk blks > */ > u_int32_t dqb_curblocks; /* current block count */ > u_int32_t dqb_ihardlimit; /* maximum # allocated inodes + > 1 */ > u_int32_t dqb_isoftlimit; /* preferred inode limit */ > u_int32_t dqb_curinodes; /* current # allocated inodes */ > int32_t dqb_btime; /* time limit for excessive disk > use */ > int32_t dqb_itime; /* time limit for excessive > files */ > }; > > After checking the value of that from a freshly overquota user and > subtracting the current unix time, I was left with 7 days. > > Any ideas on this one? Solved it by editing the quota.h in the source tree, rebuilding and installing the kernel and rebooting. Seems like a worthless flag to the edquota command if one needs to rebuild a kernel to change it. At first I thought that maybe the quota.h #DEFINE was for a maximum grace period, but that didn't hold water as I could not get the system to use a value less than 7 days either. I didn't try to reboot after using edquota -t so I don't know if that would have done anything (but I doubt it as I ran quotacheck after using that command). Anyway, perhaps this could be added as a kernel option (options QUOTA_GRACE or something along those lines?). I realize that most people have gone to virtuser type systems or massive storage where quotas are not an issue, but there are still servers (like some of ours) where we have actual (/etc/passwd) users that we need to put some constraints on (or they will never empty/prune their email boxes for example). Sven From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 04:01: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 1740416A4CE for ; Tue, 20 Jul 2004 04:01:58 +0000 (GMT) Received: from freebsd3.cimlogic.com.au (adsl-20-121.swiftdsl.com.au [218.214.20.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CED143D2F for ; Tue, 20 Jul 2004 04:01:57 +0000 (GMT) (envelope-from jb@cimlogic.com.au) Received: by freebsd3.cimlogic.com.au (Postfix, from userid 102) id ED7B36AC0C; Tue, 20 Jul 2004 14:01:54 +1000 (EST) Date: Tue, 20 Jul 2004 14:01:54 +1000 From: John Birrell To: Maxim Maximov Message-ID: <20040720040153.GA21144@freebsd3.cimlogic.com.au> References: <40FC3090.9060305@freebsd.org> <40FC92C8.50604@mcsi.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40FC92C8.50604@mcsi.pp.ru> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: HEADS UP [Re: thread+preemption stability improvement] 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, 20 Jul 2004 04:01:58 -0000 On Tue, Jul 20, 2004 at 07:34:32AM +0400, Maxim Maximov wrote: > I think it is needed :( Things actually get _much_ better, now I've > been able to use my big IMAP folders, but still after applying the patch > and working about an hour mozilla freezes with the same sympthoms (cpu > fan gets spinning faster and faster as if cpu temperature is raising). > Are there any ways I can help track this down further? > Preemption is enabled, of course. My kernel's config is latest > GENERIC with these additions: Even with PREEMPTION disabled, current freezes for me with a threaded application with lots of sendfiles in progress. I haven't figured out the set of conditions that actually trigger the freeze other than it never freezes if I have no libpthread application running (and loaded to some degree). I wonder if anyone has had current under load and if so, in what situations. It looks like this code base is a long way away from being ready for a stable branch. Grumble. The gap between 4 and 5 is too big. Not happy. At some point people need to concentrate on stability. I would concede API changes for stability any day. Every day. -- John Birrell From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 04:15: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 02ADF16A4CE for ; Tue, 20 Jul 2004 04:15:04 +0000 (GMT) Received: from otter3.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 704FF43D76 for ; Tue, 20 Jul 2004 04:15:03 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.25] ([192.168.42.25]) by otter3.centtech.com (8.12.3/8.12.3) with ESMTP id i6K4ExE8095171; Mon, 19 Jul 2004 23:14:59 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <40FC9C34.7030700@centtech.com> Date: Mon, 19 Jul 2004 23:14:44 -0500 From: Eric Anderson User-Agent: Mozilla Thunderbird 0.7.1 (X11/20040707) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Birrell References: <40FC3090.9060305@freebsd.org> <40FC92C8.50604@mcsi.pp.ru> <20040720040153.GA21144@freebsd3.cimlogic.com.au> In-Reply-To: <20040720040153.GA21144@freebsd3.cimlogic.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Maxim Maximov cc: freebsd-current@freebsd.org Subject: Re: HEADS UP [Re: thread+preemption stability improvement] 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, 20 Jul 2004 04:15:04 -0000 John Birrell wrote: >On Tue, Jul 20, 2004 at 07:34:32AM +0400, Maxim Maximov wrote: > > >> I think it is needed :( Things actually get _much_ better, now I've >>been able to use my big IMAP folders, but still after applying the patch >>and working about an hour mozilla freezes with the same sympthoms (cpu >>fan gets spinning faster and faster as if cpu temperature is raising). >>Are there any ways I can help track this down further? >> Preemption is enabled, of course. My kernel's config is latest >> GENERIC with these additions: >> >> > >Even with PREEMPTION disabled, current freezes for me with a threaded application >with lots of sendfiles in progress. I haven't figured out the set of conditions >that actually trigger the freeze other than it never freezes if I have no >libpthread application running (and loaded to some degree). > >I wonder if anyone has had current under load and if so, in what situations. >It looks like this code base is a long way away from being ready for a stable >branch. Grumble. The gap between 4 and 5 is too big. Not happy. At some point >people need to concentrate on stability. I would concede API changes for >stability any day. Every day. > > I have used it under load - compiling, NFS serving, SQL serving, etc. I'm sure many others have too. -current has never (that I recall) been suggested to be used in production environments, and it is prone to having issues like this, which is why it is important that we DO stress it, test it, and then try to help debug it by giving the most useful information about the problem to those that can help. If it isn't working well for you right now, cvsup back to about 06/01/04 and see if it's any better.. Eric -- ------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Talk sense to a fool and he calls you foolish. ------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 04:30: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 04B6516A4CE; Tue, 20 Jul 2004 04:30:34 +0000 (GMT) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEE8543D31; Tue, 20 Jul 2004 04:30:32 +0000 (GMT) (envelope-from tim@kientzle.com) Received: from kientzle.com (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id i6K4UW90027100; Mon, 19 Jul 2004 21:30:32 -0700 (PDT) (envelope-from tim@kientzle.com) Message-ID: <40FC9FC2.8050400@kientzle.com> Date: Mon, 19 Jul 2004 21:29:54 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrey Chernov References: <40F963D8.6010201@freebsd.org> <20040719060730.GA87697@nagual.pp.ru> In-Reply-To: <20040719060730.GA87697@nagual.pp.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: ports@FreeBSD.ORG cc: Tim Kientzle cc: current@FreeBSD.ORG Subject: Re: NEW TAR 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, 20 Jul 2004 04:30:34 -0000 Andrey Chernov wrote: > On Sat, Jul 17, 2004 at 10:37:28AM -0700, Tim Kientzle wrote: > >> * File format: bsdtar can read gtar files, including >> long file names, long link names, and sparse files. >> bsdtar can also read many other formats that gtar >> does not support. > > Addition: > bsdtar can't write sparse archives (Yet?). gtar has to be better at something! ;-) I have some ideas about sparse file handling, but they're not gtar-compatible. (The gtar approach has a number of drawbacks. The primary one being that on many systems it requires reading the entire file twice, once to find holes and again to actually archive the file. It is possible to do both in one pass if you store the sparse file data in a different fashion.) Tim From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 04:51: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 C01AB16A4CE for ; Tue, 20 Jul 2004 04:51:03 +0000 (GMT) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F69C43D48 for ; Tue, 20 Jul 2004 04:51:03 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (adsl-64-169-104-4.dsl.lsan03.pacbell.net [64.169.104.4])i6K4p2Br019557; Tue, 20 Jul 2004 00:51:02 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 3614751A1C; Mon, 19 Jul 2004 21:50:58 -0700 (PDT) Date: Mon, 19 Jul 2004 21:50:58 -0700 From: Kris Kennaway To: John Birrell Message-ID: <20040720045058.GA65171@xor.obsecurity.org> References: <40FC3090.9060305@freebsd.org> <40FC92C8.50604@mcsi.pp.ru> <20040720040153.GA21144@freebsd3.cimlogic.com.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Kj7319i9nmIyA2yE" Content-Disposition: inline In-Reply-To: <20040720040153.GA21144@freebsd3.cimlogic.com.au> User-Agent: Mutt/1.4.2.1i cc: Maxim Maximov cc: freebsd-current@freebsd.org Subject: Re: HEADS UP [Re: thread+preemption stability improvement] 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, 20 Jul 2004 04:51:03 -0000 --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 20, 2004 at 02:01:54PM +1000, John Birrell wrote: > On Tue, Jul 20, 2004 at 07:34:32AM +0400, Maxim Maximov wrote: > > I think it is needed :( Things actually get _much_ better, now I've=20 > > been able to use my big IMAP folders, but still after applying the patc= h=20 > > and working about an hour mozilla freezes with the same sympthoms (cpu= =20 > > fan gets spinning faster and faster as if cpu temperature is raising).= =20 > > Are there any ways I can help track this down further? > > Preemption is enabled, of course. My kernel's config is latest=20 > > GENERIC with these additions: >=20 > Even with PREEMPTION disabled, current freezes for me with a threaded app= lication > with lots of sendfiles in progress. I haven't figured out the set of cond= itions > that actually trigger the freeze other than it never freezes if I have no > libpthread application running (and loaded to some degree). >=20 > I wonder if anyone has had current under load and if so, in what situatio= ns. > It looks like this code base is a long way away from being ready for a st= able > branch. Grumble. The gap between 4 and 5 is too big. Not happy. At some p= oint > people need to concentrate on stability. I would concede API changes for= =20 > stability any day. Every day. I run ~40 machines of various architectures under heavy load with 5.x (package build clusters)..over the past month or so stability has become significantly worse; see my reply to the 5.3 TODO list from a few days ago for a list of outstanding bugs that I am tracking. A lot of this is apparently due to pre-existing bugs exposed by the preemption changes. Peter mentioned tonight that he thinks he understands the cause of several of these problems though, so expect 5.2 stability to pick up soon. Kris --Kj7319i9nmIyA2yE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/KSxWry0BWjoQKURAm93AKDfjInrkhg6fKz2O3cmn/KhAGBHYQCfSJe/ QkYUxM0FRaH5asDS1ERyGvI= =NVYe -----END PGP SIGNATURE----- --Kj7319i9nmIyA2yE-- From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 04:57: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 028FD16A4CE; Tue, 20 Jul 2004 04:57:24 +0000 (GMT) Received: from valentine.liquidneon.com (valentine.liquidneon.com [216.38.206.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2DD943D31; Tue, 20 Jul 2004 04:57:23 +0000 (GMT) (envelope-from so14k@so14k.com) Received: from localhost (localhost [127.0.0.1]) by valentine.liquidneon.com (Postfix) with ESMTP id D05F48FA; Mon, 19 Jul 2004 22:57:22 -0600 (MDT) Received: from valentine.liquidneon.com ([216.38.206.180]) by localhost (valentine.liquidneon.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 50608-06; Mon, 19 Jul 2004 22:57:22 -0600 (MDT) Received: from webmail.liquidneon.com (valentine.liquidneon.com [216.38.206.180]) by valentine.liquidneon.com (Postfix) with ESMTP id 6859671F; Mon, 19 Jul 2004 22:57:22 -0600 (MDT) Received: from 24.8.51.173 (SquirrelMail authenticated user so14k@so14k.com); by webmail.liquidneon.com with HTTP; Mon, 19 Jul 2004 22:57:22 -0600 (MDT) Message-ID: <58628.24.8.51.173.1090299442.squirrel@24.8.51.173> In-Reply-To: <40FC3090.9060305@freebsd.org> References: <40FC3090.9060305@freebsd.org> Date: Mon, 19 Jul 2004 22:57:22 -0600 (MDT) From: "Brad Davis" To: "Scott Long" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: by amavisd-new at liquidneon.com cc: freebsd-current@freebsd.org Subject: Re: HEADS UP [Re: thread+preemption stability improvement] 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, 20 Jul 2004 04:57:24 -0000 > All, > > Initial testing of this patch looks very promising. For those that > aren't comfortable with patching their sources by hand, note that it > was committed to CVS a few hours ago and should be showing up on CVSup > very shortly (rev 1.8 of sys/i386/i386/intr_machdep.c is what you want > if you are running i386). Please go out and test this as much as > possible so that we can determine if futher action is needed. No luck here. I'm running a GENERIC kernel too. I get a couple of terms open in XFCE, Gvim, and 4 tabs in firefox and it hard locks. Regards, Brad From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 05: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 884D316A4CF; Tue, 20 Jul 2004 05:47:26 +0000 (GMT) Received: from av1-2-sn4.m-sp.skanova.net (av1-2-sn4.m-sp.skanova.net [81.228.10.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3908943D5E; Tue, 20 Jul 2004 05:47:26 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av1-2-sn4.m-sp.skanova.net (Postfix, from userid 502) id 6C0A737ED2; Tue, 20 Jul 2004 07:47:25 +0200 (CEST) Received: from smtp2-2-sn4.m-sp.skanova.net (smtp2-2-sn4.m-sp.skanova.net [81.228.10.182]) by av1-2-sn4.m-sp.skanova.net (Postfix) with ESMTP id 5C6B137E4E; Tue, 20 Jul 2004 07:47:25 +0200 (CEST) Received: from gadget (h130n1fls11o822.telia.com [213.64.66.130]) by smtp2-2-sn4.m-sp.skanova.net (Postfix) with ESMTP id 3E48B37E47; Tue, 20 Jul 2004 07:47:25 +0200 (CEST) From: "Daniel Eriksson" To: "'Scott Long'" , Date: Tue, 20 Jul 2004 07:47:30 +0200 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <40FC3090.9060305@freebsd.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal Subject: RE: HEADS UP [Re: thread+preemption stability improvement] 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, 20 Jul 2004 05:47:26 -0000 Scott Long wrote: > All, > > Initial testing of this patch looks very promising. For those that > aren't comfortable with patching their sources by hand, note that it > was committed to CVS a few hours ago and should be showing up on CVSup > very shortly (rev 1.8 of sys/i386/i386/intr_machdep.c is what you want > if you are running i386). Please go out and test this as much as > possible so that we can determine if futher action is needed. I must unfortunately report that this does not cure my problem with SATA instability when preemption is turned on. I have set aside some time on the server (normally a busy production-type server) to try a few different configs (SHED_ULE instead of SHED_4BSD, turning off apic, removing polling) to see if any of them will have any impact. /Daniel Eriksson From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 06: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 288A716A4CE for ; Tue, 20 Jul 2004 06:49:39 +0000 (GMT) Received: from av1-1-sn4.m-sp.skanova.net (av1-1-sn4.m-sp.skanova.net [81.228.10.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFDA143D62 for ; Tue, 20 Jul 2004 06:49:38 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av1-1-sn4.m-sp.skanova.net (Postfix, from userid 502) id 1D13037E55; Tue, 20 Jul 2004 08:49:38 +0200 (CEST) Received: from smtp2-2-sn4.m-sp.skanova.net (smtp2-2-sn4.m-sp.skanova.net [81.228.10.182]) by av1-1-sn4.m-sp.skanova.net (Postfix) with ESMTP id 0F7D937E4B for ; Tue, 20 Jul 2004 08:49:38 +0200 (CEST) Received: from gadget (h130n1fls11o822.telia.com [213.64.66.130]) by smtp2-2-sn4.m-sp.skanova.net (Postfix) with ESMTP id EC31237E44 for ; Tue, 20 Jul 2004 08:49:37 +0200 (CEST) From: "Daniel Eriksson" To: Date: Tue, 20 Jul 2004 08:49:42 +0200 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Subject: RE: HEADS UP [Re: thread+preemption stability improvement] 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, 20 Jul 2004 06:49:39 -0000 > I have set aside some time on the server (normally a busy=20 > production-type > server) to try a few different configs (SHED_ULE instead of SHED_4BSD, > turning off apic, removing polling) to see if any of them=20 > will have any > impact. I have just tried a number of different combinations of sheduler, acpi, apic, polling, ... No matter what I do, the only way to prevent errors like the one below = seems to be to run with preemption turned off. Interrupt storm detected on "irq20: atapci4"; throttling interrupt = source ad20: FAILURE - already active DMA on this device ad20: setting up DMA failed See my recent mail on this list entitled "Kernel preemption leads to = SATA instability (how to debug?)" for machine configuration and further information. /Daniel Eriksson From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 06:55: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 F2EFC16A4CE for ; Tue, 20 Jul 2004 06:55:43 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9269B43D1D for ; Tue, 20 Jul 2004 06:55:43 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.0.12] (g4.samsco.home [192.168.0.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6K71k7D057227; Tue, 20 Jul 2004 01:01:46 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40FCC1AA.9060609@freebsd.org> Date: Tue, 20 Jul 2004 00:54:34 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Eriksson References: In-Reply-To: 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: HEADS UP [Re: thread+preemption stability improvement] 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, 20 Jul 2004 06:55:44 -0000 Daniel Eriksson wrote: >>I have set aside some time on the server (normally a busy >>production-type >>server) to try a few different configs (SHED_ULE instead of SHED_4BSD, >>turning off apic, removing polling) to see if any of them >>will have any >>impact. > > > I have just tried a number of different combinations of sheduler, acpi, > apic, polling, ... > > No matter what I do, the only way to prevent errors like the one below seems > to be to run with preemption turned off. > > Interrupt storm detected on "irq20: atapci4"; throttling interrupt source > ad20: FAILURE - already active DMA on this device > ad20: setting up DMA failed > > See my recent mail on this list entitled "Kernel preemption leads to SATA > instability (how to debug?)" for machine configuration and further > information. > > /Daniel Eriksson > Thanks for the report. I'm sure that there is a bug of some sort in the ATA driver that is being exposed by PREEMPTION, but I'm also going to consider turning off preemption in the next day or two since this isn't the only lingering problem. Scott From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 07:05: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 7F94B16A4CE for ; Tue, 20 Jul 2004 07:05:09 +0000 (GMT) Received: from mail.newlines.ru (mail.newlines.ru [195.54.211.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1839043D46 for ; Tue, 20 Jul 2004 07:05:06 +0000 (GMT) (envelope-from anton@nikiforov.ru) Received: from mail.newlines.ru (root@localhost) by mail.newlines.ru (8.12.10/8.12.9) with SMTP id i6K74Ydv025760 for ; Tue, 20 Jul 2004 07:04:49 GMT (envelope-from anton@nikiforov.ru) Received: from [192.168.20.3] (florent-mashin.rmt.ru [81.13.8.34]) (authenticated bits=0) by mail.newlines.ru (8.12.10/8.12.9) with ESMTP id i6K73s5b024837 for ; Tue, 20 Jul 2004 07:04:29 GMT (envelope-from anton@nikiforov.ru) Message-ID: <40FCC3C5.8070409@nikiforov.ru> Date: Tue, 20 Jul 2004 11:03:33 +0400 From: Anton Nikiforov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040630 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms090600060202060007030700" Subject: Creative Extegy driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: anton@nikiforov.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jul 2004 07:05:09 -0000 This is a cryptographically signed message in MIME format. --------------ms090600060202060007030700 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Dear All! Does someone have Subj. (Creative Extegy external USB sound) working under -CURRENT? Any help appreciated. When i try to attache the device i got the following: Jul 20 11:02:11 anton kernel: uaudio0: audio descriptors make no sense, error=4 Jul 20 11:02:12 anton kernel: device_attach: uaudio0 attach returned 6 -- Best regards, Anton Nikiforov --------------ms090600060202060007030700 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIII7TCC AtEwggI6oAMCAQICAwvaFTANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UE ChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNv bmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwHhcNMDQwMzA1MjExMjI4WhcNMDUwMzA1MjExMjI4 WjBEMR8wHQYDVQQDExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMSEwHwYJKoZIhvcNAQkBFhJh bnRvbkBuaWtpZm9yb3YucnUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC1Ps7E cf3xTnaY72Aip/U5HeUmGwQ6QmbCjMcqS3XfO6EsA+5ol526JvhQ1XStpDX/kh8R8MDELUJD SVooXFiDInspw5tmPOlXV1C60xH4VWf5Gh+2y3yDGzHyWBAalul7LbhC1p8zDNUA12pAu4Ry 1k1A0Yepomr8CRbh/Z9JryfJcqHYDL+z1qgLzQlpJsao9E3Zld5ZfgJPORcFoRB7Z6jvqVLh pLNmSrvfDbSw6WK/K9EbZT9zlOTlmOnt4uLBy3hKZMcvkaFrYVYTRXLMegJHFPAp3sxLYef2 iW9fEUKgrs4W7d5c8UWlmiGurVt1Xdzc58W8X3vekMLqu9elAgMBAAGjLzAtMB0GA1UdEQQW MBSBEmFudG9uQG5pa2lmb3Jvdi5ydTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GB ABINGnCD0TGnBHqGYbJHSwjFfxEsVS1ygSUVIyb0Q1S0SphgUSeRWIZ4+joWR9TzxFGqLtYM TEQvRTQ7VJcugjn2o2nTgQ4EPhze0O5ki2eUWHE9dViHboQWOWI0r1vurUTkDnmloeM8mpMo CAAtXbjyhz7AVKUwI7vULQKuE+imMIIC0TCCAjqgAwIBAgIDC9oVMA0GCSqGSIb3DQEBBAUA MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQu MSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTAeFw0wNDAz MDUyMTEyMjhaFw0wNTAzMDUyMTEyMjhaMEQxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBN ZW1iZXIxITAfBgkqhkiG9w0BCQEWEmFudG9uQG5pa2lmb3Jvdi5ydTCCASIwDQYJKoZIhvcN AQEBBQADggEPADCCAQoCggEBALU+zsRx/fFOdpjvYCKn9Tkd5SYbBDpCZsKMxypLdd87oSwD 7miXnbom+FDVdK2kNf+SHxHwwMQtQkNJWihcWIMieynDm2Y86VdXULrTEfhVZ/kaH7bLfIMb MfJYEBqW6XstuELWnzMM1QDXakC7hHLWTUDRh6miavwJFuH9n0mvJ8lyodgMv7PWqAvNCWkm xqj0TdmV3ll+Ak85FwWhEHtnqO+pUuGks2ZKu98NtLDpYr8r0RtlP3OU5OWY6e3i4sHLeEpk xy+RoWthVhNFcsx6AkcU8CnezEth5/aJb18RQqCuzhbt3lzxRaWaIa6tW3Vd3Nznxbxfe96Q wuq716UCAwEAAaMvMC0wHQYDVR0RBBYwFIESYW50b25AbmlraWZvcm92LnJ1MAwGA1UdEwEB /wQCMAAwDQYJKoZIhvcNAQEEBQADgYEAEg0acIPRMacEeoZhskdLCMV/ESxVLXKBJRUjJvRD VLRKmGBRJ5FYhnj6OhZH1PPEUaou1gxMRC9FNDtUly6COfajadOBDgQ+HN7Q7mSLZ5RYcT11 WIduhBY5YjSvW+6tROQOeaWh4zyakygIAC1duPKHPsBUpTAju9QtAq4T6KYwggM/MIICqKAD AgECAgENMA0GCSqGSIb3DQEBBQUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVy biBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5n MSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtU aGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZy ZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDMwNzE3MDAwMDAwWhcNMTMwNzE2MjM1OTU5WjBiMQsw CQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoG A1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwgZ8wDQYJKoZIhvcN AQEBBQADgY0AMIGJAoGBAMSmPFVzVftOucqZWh5owHUEcJ3f6f+jHuy9zfVb8hp2vX8MOmHy v1HOAdTlUAow1wJjWiyJFXCO3cnwK4Vaqj9xVsuvPAsH5/EfkTYkKhPPK9Xzgnc9A74r/rsY Pge/QIACZNenprufZdHFKlSFD0gEf6e20TxhBEAeZBlyYLf7AgMBAAGjgZQwgZEwEgYDVR0T AQH/BAgwBgEB/wIBADBDBgNVHR8EPDA6MDigNqA0hjJodHRwOi8vY3JsLnRoYXd0ZS5jb20v VGhhd3RlUGVyc29uYWxGcmVlbWFpbENBLmNybDALBgNVHQ8EBAMCAQYwKQYDVR0RBCIwIKQe MBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDItMTM4MA0GCSqGSIb3DQEBBQUAA4GBAEiM0VCD 6gsuzA2jZqxnD3+vrL7CF6FDlpSdf0whuPg2H6otnzYvwPQcUCCTcDz9reFhYsPZOhl+hLGZ GwDFGguCdJ4lUJRix9sncVcljd2pnDmOjCBPZV+V2vf3h9bGCE6u9uo05RAaWzVNd+NWIXiC 3CEZNd4ksdMdRv9dX2VPMYIDOzCCAzcCAQEwaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMc VGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFs IEZyZWVtYWlsIElzc3VpbmcgQ0ECAwvaFTAJBgUrDgMCGgUAoIIBpzAYBgkqhkiG9w0BCQMx CwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wNDA3MjAwNzAzMzNaMCMGCSqGSIb3DQEJ BDEWBBR8lZoVRRJD7GsHYGPeqLmbqT4C3zBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMH MA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIB KDB4BgkrBgEEAYI3EAQxazBpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29u c3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwg SXNzdWluZyBDQQIDC9oVMHoGCyqGSIb3DQEJEAILMWugaTBiMQswCQYDVQQGEwJaQTElMCMG A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECAwvaFTANBgkqhkiG9w0BAQEFAASCAQAX+xGp lkuObYtzJ8e0XlRdYi4tBw+ECBExaP8iQrNe8VJ2hQBqb0kAa+VTyzPiMKcA9av1i5oDcX1V VBx7B3C8BoyombFkwyks86WXnZhe003bXAuAjrOzgsjsvAT9p0OG21UWJcBcA0QQbIbdn0yu 44+xkfMgUuabJ4XbWAS7fthuXFaV+w2nv0Ttl1HgJOXpeh/qqOk30BaGmFIrtkjBJDha5VfG w6Ho1NppVIGSFV+oXZ+VHF4O/XZfBekQ9ZgcEvqq1k/LfJwTSnzwMGxwexcrbi38wzrGFvMm Wy/k/rwvsBPLDSQDgDhh1Kj9ml9x7EhK9gI5fJv2J2U2ISN8AAAAAAAA --------------ms090600060202060007030700-- From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 07:07: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 0A87416A4CE; Tue, 20 Jul 2004 07:07:09 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10B8443D5F; Tue, 20 Jul 2004 07:07:08 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6K75EsD000848; Tue, 20 Jul 2004 09:05:15 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <15fd01c46e27$02e49050$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Robert Watson" References: Date: Tue, 20 Jul 2004 08:58:49 +0200 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.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 fromzone0xffffff007fed4780(Mbuf) 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, 20 Jul 2004 07:07:09 -0000 From: "Robert Watson" > On Mon, 19 Jul 2004, Willem Jan Withagen wrote: > > > > I'll starts some more tests before I'm of to bed. > > > > This mornings result: > > ==== > > System call getdirentries returning with the following locks held: > > exclusive sleep mutex bdone lock r = 0 (0xffffffff805fd080) locked @ /home2/src/ > > sys/kern/vfs_bio.c:3767 > > panic: witness_warn > > cpuid = 0; > > KDB: stack backtrace: > > kdspin lock sched lock held by 0xffffff007b6cc940 for > 5 seconds > > panic: spin lock held too long > > cpuid = 0; > > KDB: enter: panic > > ==== > > > > But no way to get into the debugger. Does not look like it is much > > network related??? > > Doesn't look very network related, although it could be that increased > concurrency and lack of waiting on Giant open up a race of some sort. Can > you confirm "options DDB" and "options KDB" are both in your kernel > config? You may want to consider commenting out "#define PREEMPTION" in > the copy of params.h for the architecture you're running on and see if > that helps. Won't help interrupt processing latency, but probably won't > hurt server throughput, and your box is a server box so it might be worth > trying. The first time that it made it through the night since quite some days... The real stress test, "make -j32 buildworld" is still too much however. --WjW From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 07:50: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 3DA0916A4CE; Tue, 20 Jul 2004 07:50:38 +0000 (GMT) Received: from av7-1-sn1.fre.skanova.net (av7-1-sn1.fre.skanova.net [81.228.11.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1DA243D1F; Tue, 20 Jul 2004 07:50:37 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av7-1-sn1.fre.skanova.net (Postfix, from userid 502) id 0860D37EF6; Tue, 20 Jul 2004 09:50:37 +0200 (CEST) Received: from smtp3-2-sn1.fre.skanova.net (smtp3-2-sn1.fre.skanova.net [81.228.11.164]) by av7-1-sn1.fre.skanova.net (Postfix) with ESMTP id EE22137E55; Tue, 20 Jul 2004 09:50:36 +0200 (CEST) Received: from gadget (h130n1fls11o822.telia.com [213.64.66.130]) by smtp3-2-sn1.fre.skanova.net (Postfix) with ESMTP id D51A937E4D; Tue, 20 Jul 2004 09:50:36 +0200 (CEST) From: "Daniel Eriksson" To: "'Scott Long'" Date: Tue, 20 Jul 2004 09:50:42 +0200 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal In-Reply-To: <40FCC1AA.9060609@freebsd.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 cc: freebsd-current@freebsd.org Subject: RE: HEADS UP [Re: thread+preemption stability improvement] 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, 20 Jul 2004 07:50:38 -0000 Scott Long wrote: > Thanks for the report. I'm sure that there is a bug of some=20 > sort in the > ATA driver that is being exposed by PREEMPTION, but I'm also going to > consider turning off preemption in the next day or two since=20 > this isn't > the only lingering problem. I don't know if my SATA problems are at all related to the problems I've seen with GBDE, GEOM stripe, GEOM vinum and "old" vinum, but I probably should mention them. They show up with or without preemption turned on. * GEOM BDE disc encryption seems to work, until it's time to tear it = down and reboot the machine. It always claims the device is busy when I try = to unmount the file system, and if I use the -f flag to unmount it panics = the machine. Skipping the unmount results in a panic during shutdown. * GEOM stripe made all discs that were part of ataraid arrays time out = when I tried to create a simple striped array (from two single discs). Since = the system was live, and processes were accessing the ataraid arrays, the machine eventually panicked in some vfs function. * GEOM vinum starts up fine, but as soon as I start accessing arrays = (raid-1 and raid-0) it looses its discs, crashing the arrays. * "old" vinum panics with a dangling vnode (when it starts up) if I run = a normal boot. If I boot single-user and then manually start vinum it = works fine. /Daniel Eriksson From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 07:58: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 61F6D16A4CF; Tue, 20 Jul 2004 07:58:25 +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 5052D43D1F; Tue, 20 Jul 2004 07:58:24 +0000 (GMT) (envelope-from le@FreeBSD.org) Received: from wireless (adslle.cc.univie.ac.at [131.130.102.11]) by imap.univie.ac.at (8.12.10/8.12.10) with ESMTP id i6K7w5xl1338484; Tue, 20 Jul 2004 09:58:17 +0200 Date: Tue, 20 Jul 2004 09:58:05 +0200 (CEST) From: Lukas Ertl To: Daniel Eriksson In-Reply-To: Message-ID: <20040720095710.W554@korben.in.tern> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-DCC-ZID-Univie-Metrics: mx7.univie.ac.at 4248; Body=3 Fuz1=3 Fuz2=3 cc: freebsd-current@FreeBSD.org cc: 'Scott Long' Subject: RE: HEADS UP [Re: thread+preemption stability improvement] 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, 20 Jul 2004 07:58:25 -0000 On Tue, 20 Jul 2004, Daniel Eriksson wrote: > * GEOM vinum starts up fine, but as soon as I start accessing arrays (raid-1 > and raid-0) it looses its discs, crashing the arrays. That's probably because you have the 'a' and 'c' partition at the same offset. I have a fix for that in my queue. 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 Tue Jul 20 08:14: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 6439C16A4CE; Tue, 20 Jul 2004 08:14:00 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17A2E43D45; Tue, 20 Jul 2004 08:14:00 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id 8A529ACAE3; Tue, 20 Jul 2004 10:13:58 +0200 (CEST) Date: Tue, 20 Jul 2004 10:13:58 +0200 From: Pawel Jakub Dawidek To: Daniel Eriksson Message-ID: <20040720081358.GL57678@darkness.comp.waw.pl> References: <40FCC1AA.9060609@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4oF+6Ged69J0+4/e" Content-Disposition: inline In-Reply-To: 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: freebsd-current@freebsd.org cc: 'Scott Long' Subject: Re: HEADS UP [Re: thread+preemption stability improvement] 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, 20 Jul 2004 08:14:00 -0000 --4oF+6Ged69J0+4/e Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 20, 2004 at 09:50:42AM +0200, Daniel Eriksson wrote: +> * GEOM stripe made all discs that were part of ataraid arrays time out w= hen +> I tried to create a simple striped array (from two single discs). Since = the +> system was live, and processes were accessing the ataraid arrays, the +> machine eventually panicked in some vfs function. Could you give me a procedure which I can use to reproduce it? --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --4oF+6Ged69J0+4/e Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/NRGForvXbEpPzQRAgxpAJ9Wia3miVbW7PlaOaHjGsKYhZCgAgCgu1O2 BAB3EWoKEwQ8qPnBspnkn4w= =Q5ex -----END PGP SIGNATURE----- --4oF+6Ged69J0+4/e-- From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 08:24: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 7304A16A4CE; Tue, 20 Jul 2004 08:24:02 +0000 (GMT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 407FE43D41; Tue, 20 Jul 2004 08:24:02 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.11/8.12.11) with ESMTP id i6K8Nrrc041129; Tue, 20 Jul 2004 01:23:56 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200407200823.i6K8Nrrc041129@gw.catspoiler.org> Date: Tue, 20 Jul 2004 01:23:52 -0700 (PDT) From: Don Lewis To: conrads@cox.net In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: freebsd-multimedia@FreeBSD.org cc: freebsd-current@FreeBSD.org Subject: Re: [amd64] Sound breakage with snd_ich 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: Tue, 20 Jul 2004 08:24:02 -0000 On 19 Jul, Conrad J. Sabatier wrote: > This problem has persisted for the last several weeks now, close to a > month or so, I would say. > > Playing MP3s using madplay, everything works fine for a while, then > suddenly I get an "output: write: Invalid argument" error each time > madplay starts up. Any further attempts to use sound via any method or > app likewise fail. Sound remains broken until a reboot. > > Upgraded the system again yesterday, to the new "sound" drivers, same > results. > > I've attached truss output from one of these failed madplay runs. I suspect that the sound driver is getting interrupt timeouts and is marking the channel dead. Do you see the following message in /var/log/messages? play interrupt timeout, channel dead If so, I've seen other reports of this. I think the chn_write() code needs some careful analysis ... From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 08:42: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 0690816A4CE for ; Tue, 20 Jul 2004 08:42:37 +0000 (GMT) Received: from mail009.syd.optusnet.com.au (mail009.syd.optusnet.com.au [211.29.132.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4F3243D48 for ; Tue, 20 Jul 2004 08:42:35 +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]) i6K8gPm16862; Tue, 20 Jul 2004 18:42:25 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])i6K8AqVd006286; Tue, 20 Jul 2004 18:10:52 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)i6K8AqX1006285; Tue, 20 Jul 2004 18:10:52 +1000 (EST) (envelope-from pjeremy) Date: Tue, 20 Jul 2004 18:10:51 +1000 From: Peter Jeremy To: Tim Kientzle Message-ID: <20040720081051.GB3001@cirb503493.alcatel.com.au> References: <40F963D8.6010201@freebsd.org> <20040719060730.GA87697@nagual.pp.ru> <40FC9FC2.8050400@kientzle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40FC9FC2.8050400@kientzle.com> User-Agent: Mutt/1.4.2i cc: Andrey Chernov cc: current@freebsd.org Subject: Re: NEW TAR 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, 20 Jul 2004 08:42:37 -0000 On Mon, 2004-Jul-19 21:29:54 -0700, Tim Kientzle wrote: >I have some ideas about sparse file handling, >but they're not gtar-compatible. (The gtar >approach has a number of drawbacks. The primary >one being that on many systems it requires reading >the entire file twice, once to find holes and again >to actually archive the file. Actually, it's not possible to accurately determine the holes in a file by reading it - you can't differentiate between a hole and a allocated block of zeroes. What you need is a (new) syscall that invokes a new VOP_... and returns a bitmap of allocated blocks. This would be non-trival unfortunately. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 08:58: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 7794316A4CE; Tue, 20 Jul 2004 08:58:01 +0000 (GMT) Received: from av9-1-sn4.m-sp.skanova.net (av9-1-sn4.m-sp.skanova.net [81.228.10.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AEF443D41; Tue, 20 Jul 2004 08:58:01 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av9-1-sn4.m-sp.skanova.net (Postfix, from userid 502) id 6BF2437EAB; Tue, 20 Jul 2004 10:58:00 +0200 (CEST) Received: from smtp2-1-sn4.m-sp.skanova.net (smtp2-1-sn4.m-sp.skanova.net [81.228.10.183]) by av9-1-sn4.m-sp.skanova.net (Postfix) with ESMTP id 5C4C937E6A; Tue, 20 Jul 2004 10:58:00 +0200 (CEST) Received: from gadget (h130n1fls11o822.telia.com [213.64.66.130]) by smtp2-1-sn4.m-sp.skanova.net (Postfix) with ESMTP id 396F037E46; Tue, 20 Jul 2004 10:58:00 +0200 (CEST) From: "Daniel Eriksson" To: "'Lukas Ertl'" Date: Tue, 20 Jul 2004 10:58:05 +0200 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal In-Reply-To: <20040720095710.W554@korben.in.tern> cc: freebsd-current@freebsd.org Subject: RE: HEADS UP [Re: thread+preemption stability improvement] 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, 20 Jul 2004 08:58:01 -0000 Lukas Ertl wrote: > That's probably because you have the 'a' and 'c' partition at=20 > the same=20 > offset. I have a fix for that in my queue. That is very likely. :-) Here's the info for the disc holding my root partition and the mirrored /var, /tmp and /usr partitions (plus a striped partition): # disklabel /dev/ad0s1 # /dev/ad0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 1048576 0 4.2BSD 2048 16384 8=20 b: 1048576 1048576 swap =20 c: 234436482 0 unused 0 0 # "raw" part, = don't edit d: 1048576 2097152 vinum =20 e: 1048576 3145728 vinum =20 f: 20971520 4194304 vinum =20 g: 209270658 25165824 vinum And I have a bunch of other discs the looks like this (more or less): # disklabel /dev/da4s1 # /dev/da4s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 71681967 0 unused 0 0 # "raw" part, = don't edit d: 71681967 0 vinum /Daniel Eriksson From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 09:11: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 219A816A4CE; Tue, 20 Jul 2004 09:11:56 +0000 (GMT) Received: from av5-1-sn3.vrr.skanova.net (av5-1-sn3.vrr.skanova.net [81.228.9.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB70B43D48; Tue, 20 Jul 2004 09:11:55 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av5-1-sn3.vrr.skanova.net (Postfix, from userid 502) id 3C80D37ECF; Tue, 20 Jul 2004 11:11:55 +0200 (CEST) Received: from smtp1-1-sn3.vrr.skanova.net (smtp1-1-sn3.vrr.skanova.net [81.228.9.177]) by av5-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 2DAF737E46; Tue, 20 Jul 2004 11:11:55 +0200 (CEST) Received: from gadget (h130n1fls11o822.telia.com [213.64.66.130]) by smtp1-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 0873F38006; Tue, 20 Jul 2004 11:11:55 +0200 (CEST) From: "Daniel Eriksson" To: "'Pawel Jakub Dawidek'" Date: Tue, 20 Jul 2004 11:12:00 +0200 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal In-Reply-To: <20040720081358.GL57678@darkness.comp.waw.pl> cc: freebsd-current@freebsd.org Subject: RE: HEADS UP [Re: thread+preemption stability improvement] 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, 20 Jul 2004 09:11:56 -0000 Pawel Jakub Dawidek wrote: > Could you give me a procedure which I can use to reproduce it? Not really. The use case is so simple that I really don't think it is a general problem. Otherwise everyone would be complaining about it. I'll = see if I can schedule some more downtime for the server to run some more = tests of this. (I only did it once, and because the machine was live at the = moment the lockup of the ataraid arrays made it quite a mess, so I'm hesitant = to try it again unless I'm in single user mode.) This was the command I issued that resulted in the crash. Nothing = strange about it as far as I can tell (taken directly from the gstripe man = page). gstripe label -v -s 4096 data /dev/da15 /dev/da16 /dev/da15 and /dev/da16 had been labeled and newfs'ed, but were not = mounted at the time. As I said, if I get a chance I'll look at this next time the machine is = down in single user mode. I forgot to do that earlier this morning when I did = a lot of testing to try to get around the SATA vs. preemtion problem I'm seeing. /Daniel Eriksson From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 09:45: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 08CCE16A4CF for ; Tue, 20 Jul 2004 09:45:52 +0000 (GMT) Received: from max.af.czu.cz (max.af.czu.cz [193.84.41.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C3C343D5D for ; Tue, 20 Jul 2004 09:45:50 +0000 (GMT) (envelope-from lists@hosting50.cz) Received: (qmail 42326 invoked by uid 89); 20 Jul 2004 10:02:10 -0000 Received: from unknown (HELO ?193.84.40.30?) (ares@max.af.czu.cz@193.84.40.30) by max.af.czu.cz with AES256-SHA encrypted SMTP; 20 Jul 2004 10:02:10 -0000 From: Tomas Randa To: current@freebsd.org In-Reply-To: References: Content-Type: text/plain Message-Id: <1090316748.788.8.camel@ares.af.czu.cz> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 20 Jul 2004 11:45:48 +0200 Content-Transfer-Encoding: 7bit Subject: sk0 patch 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, 20 Jul 2004 09:45:52 -0000 Hi, is there available a working patch for current "sk" driver? Thanks a lot. Tomas Randa On Sun, 2004-07-11 at 00:34, Bjoern A. Zeeb wrote: > Hi, > > there had been some discussion lately about if_sk and attach locking. > compiled if_sk as module on amd64 and kldloading started a race with > follwoing output: > > --- very short part of console log --- > [some hundred more of the following lines] > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > malloc(M_WAITOK) of "64", forcing M_NOWAIT with the following non-sleepable locks held: > exclusive sleep mutex skc0 (network driver) r = 0 (0xffffff003000b670) locked @ /u1/src/HEAD/src/sys/pci/if_sk.c:1335 > Stack backtrace: > witness_warn() at witness_warn+0x1a7 > uma_zalloc_arg() at uma_zalloc_arg+0x4c > malloc() at malloc+0x9f > scope6_ifattach() at scope6_ifattach+0x20 > in6_domifattach() at in6_domifattach+0x91 > if_attachdomain1() at if_attachdomain1+0xb9 > if_attach() at if_attach+0x465 > ether_ifattach() at ether_ifattach+0x27 > sk_attach() at sk_attach+0x334 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > [some hundred more of these lines] > --- end --- > > > > I solved this problem without further investigation of possible > bad impacts with this patch: > > > Index: if_sk.c > =================================================================== > RCS file: /u2/src/CVS/prefixes/src/sys/pci/if_sk.c,v > retrieving revision 1.83 > diff -u -p -r1.83 if_sk.c > --- if_sk.c 28 Jun 2004 20:07:03 -0000 1.83 > +++ if_sk.c 10 Jul 2004 21:44:53 -0000 > @@ -1332,7 +1332,9 @@ sk_attach(dev) > error = 0; > sc_if = device_get_softc(dev); > sc = device_get_softc(device_get_parent(dev)); > +#if 0 > SK_LOCK(sc); > +#endif > port = *(int *)device_get_ivars(dev); > free(device_get_ivars(dev), M_DEVBUF); > device_set_ivars(dev, NULL); > @@ -1472,7 +1474,9 @@ sk_attach(dev) > } > > fail: > +#if 0 > SK_UNLOCK(sc); > +#endif > if (error) { > /* Access should be ok even though lock has been dropped */ > sc->sk_if[port] = NULL; > --- end --- > > > can someone with some more knowledge about this driver and > general locking of if_* please review this. TIA. -- Tomas Randa From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 09:46: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 3AB5116A4CE for ; Tue, 20 Jul 2004 09:46:31 +0000 (GMT) Received: from max.af.czu.cz (max.af.czu.cz [193.84.41.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70DCB43D5D for ; Tue, 20 Jul 2004 09:46:30 +0000 (GMT) (envelope-from lists@hosting50.cz) Received: (qmail 42369 invoked by uid 89); 20 Jul 2004 10:02:51 -0000 Received: from unknown (HELO ?193.84.40.30?) (ares@max.af.czu.cz@193.84.40.30) by max.af.czu.cz with AES256-SHA encrypted SMTP; 20 Jul 2004 10:02:51 -0000 From: Tomas Randa To: freebsd-current@freebsd.org Content-Type: text/plain Message-Id: <1090316789.788.10.camel@ares.af.czu.cz> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 20 Jul 2004 11:46:29 +0200 Content-Transfer-Encoding: 7bit Subject: sk0 patch 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, 20 Jul 2004 09:46:31 -0000 Hi, is there available a working patch for current "sk" driver? Thanks a lot. Tomas Randa On Sun, 2004-07-11 at 00:34, Bjoern A. Zeeb wrote: > Hi, > > there had been some discussion lately about if_sk and attach locking. > compiled if_sk as module on amd64 and kldloading started a race with > follwoing output: > > --- very short part of console log --- > [some hundred more of the following lines] > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > malloc(M_WAITOK) of "64", forcing M_NOWAIT with the following non-sleepable locks held: > exclusive sleep mutex skc0 (network driver) r = 0 (0xffffff003000b670) locked @ /u1/src/HEAD/src/sys/pci/if_sk.c:1335 > Stack backtrace: > witness_warn() at witness_warn+0x1a7 > uma_zalloc_arg() at uma_zalloc_arg+0x4c > malloc() at malloc+0x9f > scope6_ifattach() at scope6_ifattach+0x20 > in6_domifattach() at in6_domifattach+0x91 > if_attachdomain1() at if_attachdomain1+0xb9 > if_attach() at if_attach+0x465 > ether_ifattach() at ether_ifattach+0x27 > sk_attach() at sk_attach+0x334 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > (null)() at 0 > [some hundred more of these lines] > --- end --- > > > > I solved this problem without further investigation of possible > bad impacts with this patch: > > > Index: if_sk.c > =================================================================== > RCS file: /u2/src/CVS/prefixes/src/sys/pci/if_sk.c,v > retrieving revision 1.83 > diff -u -p -r1.83 if_sk.c > --- if_sk.c 28 Jun 2004 20:07:03 -0000 1.83 > +++ if_sk.c 10 Jul 2004 21:44:53 -0000 > @@ -1332,7 +1332,9 @@ sk_attach(dev) > error = 0; > sc_if = device_get_softc(dev); > sc = device_get_softc(device_get_parent(dev)); > +#if 0 > SK_LOCK(sc); > +#endif > port = *(int *)device_get_ivars(dev); > free(device_get_ivars(dev), M_DEVBUF); > device_set_ivars(dev, NULL); > @@ -1472,7 +1474,9 @@ sk_attach(dev) > } > > fail: > +#if 0 > SK_UNLOCK(sc); > +#endif > if (error) { > /* Access should be ok even though lock has been dropped */ > sc->sk_if[port] = NULL; > --- end --- > > > can someone with some more knowledge about this driver and > general locking of if_* please review this. TIA. -- Tomas Randa -- Tomas Randa From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 10:01: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 1C69B16A4CE for ; Tue, 20 Jul 2004 10:01:00 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51BF343D67 for ; Tue, 20 Jul 2004 10:00: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 5F1F11FF91D; Tue, 20 Jul 2004 12:00:57 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 849021FF90C; Tue, 20 Jul 2004 12:00:55 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 1F81415659; Tue, 20 Jul 2004 10:00:42 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 1C95D155DD; Tue, 20 Jul 2004 10:00:43 +0000 (UTC) Date: Tue, 20 Jul 2004 10:00:43 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Tomas Randa In-Reply-To: <1090316789.788.10.camel@ares.af.czu.cz> Message-ID: References: <1090316789.788.10.camel@ares.af.czu.cz> 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: sk0 patch 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, 20 Jul 2004 10:01:00 -0000 On Tue, 20 Jul 2004, Tomas Randa wrote: > is there available a working patch for current "sk" driver? yes; in the archives: http://lists.freebsd.org/pipermail/freebsd-current/2004-June/028994.html -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 10:35: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 BAE9016A4CE; Tue, 20 Jul 2004 10:35:57 +0000 (GMT) Received: from havoc.eusc.inter.net (havoc.eusc.inter.net [213.73.101.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CCFA43D3F; Tue, 20 Jul 2004 10:35:57 +0000 (GMT) (envelope-from plexus@snafu.de) Received: from pd9e7b330.dip.t-dialin.net ([217.231.179.48] helo=[192.168.1.16]) by havoc.eusc.inter.net with asmtp (Exim 3.36 #3) id 1BmryV-0005Kj-00; Tue, 20 Jul 2004 12:35:55 +0200 Message-ID: <40FCF591.601@snafu.de> Date: Tue, 20 Jul 2004 12:36:01 +0200 From: "Oliver B. Fischer" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040707 X-Accept-Language: de-de, en-us, en MIME-Version: 1.0 To: Thomas Quinot References: <40DFDC44.6090101@snafu.de> <20040719210311.GA72395@melusine.cuivre.fr.eu.org> In-Reply-To: <20040719210311.GA72395@melusine.cuivre.fr.eu.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: Obtaining a kernel dump is not 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: Tue, 20 Jul 2004 10:35:57 -0000 Thomas Quinot wrote: > If dumping does not work, can you try to obtain a backtrace from DDB? How can I get it and save it too? Regards Oliver Fischer From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 10:40: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 E5EA816A4CE for ; Tue, 20 Jul 2004 10:40:58 +0000 (GMT) Received: from gundel.de.clara.net (gundel.de.clara.net [212.82.225.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8089843D2D for ; Tue, 20 Jul 2004 10:40:58 +0000 (GMT) (envelope-from jesk@killall.org) Received: from port-212-202-54-113.dynamic.qsc.de ([212.202.54.113] helo=turbofresse) by gundel.de.clara.net with smtp (Exim 4.30; FreeBSD) id 1BmsCt-000Jkh-Qm for freebsd-current@freebsd.org; Tue, 20 Jul 2004 12:50:47 +0200 Message-ID: <027e01c46e46$04224f60$45fea8c0@turbofresse> From: "jesk" To: References: <20040618143134.4512.qmail@web14101.mail.yahoo.com> Date: Tue, 20 Jul 2004 12:40:46 +0200 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.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: Re: Possible Threading problem with -CURRENT / MySQL? 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, 20 Jul 2004 10:40:59 -0000 i got problems too with mysql under freebsd 5.2.1 and CURRENT. i got these problems on two machines with different hardware, but both are single cpu machines. used scheduler is ULE. problem description: under high i/o load the mysqld isnt responding any more. i tested this with dd if=/dev/urandom of=testfile bs=128k on the hdd an was not able to become any ouput from simple select-statements within a long period of time (above minutes). i dont know if this problem occurs from mysql and its threads or if the i/o subsystem has any problems to deal fast enough with two intensives read and write processes and its priorities. best regards, christian From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 10:42: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 8518C16A4CE for ; Tue, 20 Jul 2004 10:42:26 +0000 (GMT) Received: from gundel.de.clara.net (gundel.de.clara.net [212.82.225.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4ED6343D62 for ; Tue, 20 Jul 2004 10:42:26 +0000 (GMT) (envelope-from jesk@killall.org) Received: from port-212-202-54-113.dynamic.qsc.de ([212.202.54.113] helo=turbofresse) by gundel.de.clara.net with smtp (Exim 4.30; FreeBSD) id 1BmsEK-000JpX-GH for freebsd-current@freebsd.org; Tue, 20 Jul 2004 12:52:16 +0200 Message-ID: <028601c46e46$38fc9560$45fea8c0@turbofresse> From: "jesk" To: Date: Tue, 20 Jul 2004 12:42:15 +0200 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.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: I/O or Threading Suffer 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, 20 Jul 2004 10:42:26 -0000 hello, i got problems with mysql under freebsd 5.2.1 and CURRENT. i got these problems on two machines with different hardware, but both are single cpu machines. used scheduler is ULE. problem description: under high i/o load the mysqld isnt responding any more. i tested this with dd if=/dev/urandom of=testfile bs=128k on the hdd an was not able to become any ouput from simple select-statements within a long period of time (above minutes). i dont know if this problem occurs from mysql and its threads or if the i/o subsystem has any problems to deal fast enough with two intensives read and write processes and its priorities. best regards, christian From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 11:37: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 9B2C416A4CE for ; Tue, 20 Jul 2004 11:37:26 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC37F43D53 for ; Tue, 20 Jul 2004 11:37:23 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.0.200] ([192.168.0.200]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6KBhRKh058415; Tue, 20 Jul 2004 05:43:27 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <40FD03E7.8000300@samsco.org> Date: Tue, 20 Jul 2004 05:37:11 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040702 X-Accept-Language: en-us, en MIME-Version: 1.0 To: jesk References: <028601c46e46$38fc9560$45fea8c0@turbofresse> In-Reply-To: <028601c46e46$38fc9560$45fea8c0@turbofresse> X-Enigmail-Version: 0.84.2.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: I/O or Threading Suffer 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, 20 Jul 2004 11:37:26 -0000 jesk wrote: > hello, > > i got problems with mysql under freebsd 5.2.1 and CURRENT. > > i got these problems on two machines with different hardware, but both are > single cpu machines. > used scheduler is ULE. > > problem description: > under high i/o load the mysqld isnt responding any more. > i tested this with dd if=/dev/urandom of=testfile bs=128k on the hdd an was > not > able to become any ouput from simple select-statements within a long period > of time > (above minutes). > i dont know if this problem occurs from mysql and its threads or if the i/o > subsystem has > any problems to deal fast enough with two intensives read and write > processes and its > priorities. > > best regards, > christian > If you are dd'ing from /dev/random, then you are depleting the entropy pool. Anything else that tries to get random numbers is going to block in strange ways. Trying just dd'ing from /dev/zero and see if that makes a difference. Scott From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 01:53: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 A2E0916A4CE; Tue, 20 Jul 2004 01:53:00 +0000 (GMT) Received: from tora.nunu.org (YahooBB219003182029.bbtec.net [219.3.182.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4141E43D2D; Tue, 20 Jul 2004 01:52:59 +0000 (GMT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from tora.nunu.org (unknown [192.168.1.2]) by tora.nunu.org (Postfix) with ESMTP id CE5A94E50F; Tue, 20 Jul 2004 10:52:57 +0900 (JST) Date: Tue, 20 Jul 2004 10:52:57 +0900 Message-ID: <87llhfphqe.wl@tora.nunu.org> From: Hidetoshi Shimokawa To: Doug Rabson In-Reply-To: <200407182104.53221.dfr@nlsystems.com> References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 14) (Reasonable Discussion) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII X-Mailman-Approved-At: Tue, 20 Jul 2004 11:46:22 +0000 cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org cc: Andrew Gallatin Subject: Re: Excellent job on the firewire 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, 20 Jul 2004 01:53:00 -0000 At Sun, 18 Jul 2004 21:04:53 +0100, Doug Rabson wrote: > > It would be nice to remove my Comtrol Rocketport serial card, and the > > 8 serial cables leading across the middle of the room to my shelf of > > machines and replace it with one firewire cable leading to a firewire > > hub. But, as a firewire newbie, I have some questions: > > > > 1) Is any firewire PCI adapter just as good as any other in terms of > > performance, and FreeBSD support? (prices seem to range from $10 > > to $100) > > Any should do about as well as any other. I probably wouldn't want to > spend more than ~$50 on one. I got some bad report about Lucent chip(some Mac's have it) but I haven't heard any other compatibility issue. I think the price of the adapter doesn't matter but you may have trouble with some bad cables. If have some problem, use lower speed(S100) or change cables. > > > > 2) Is dcons usable after a panic (ie, DDB or KDB_TRACE)? Or is it > > only usable for remote-gdb? > > Dcons provides two full duplex streams - one for console and one for > gdb. You can use DDB on the console just like normal. It's designed for such panic/debugging situation. Actually, it's rather inefficient for usual situation but the speed of FireWire hide the problem ;-) > > > > 3) Is dcons endian and pointer-size agonstic? Can I run consoles to > > an amd64 and a powerpc box from an x86? > > I haven't actually tried that and I imagine that there might be issues > here and there. Any problems are likely to be in the dconschat program > but that should be pretty easy to fix since its entirely userland. I should have no problem with 64bit arch and big endian. I have tested with sparc64, powerpc and amd64. > > > > 4) Does the loader know about dcons? Eg, can I do "unload boot > > kernel.test" using dcons? > > Actually thats the only downside of dcons. It doesn't cut in until the > firewire controller attaches. It relies on the fact that the fwohci > driver allows access to physical memory from any node on the bus > (implemeted in hardware so you can examine the memory of a hung > machine). The dconschat program uses this feature to access the dcons > ring buffers in the target machine. > > I could imagine a dcons driver in the loader which just enabled physical > access and used some kind of loader trick to hand off the ring buffers > to the kernel dcons driver. It doesn't exist though - say nice things You are right. > to the author and he might find the time for it :-) It is not enough :-< I lack the knowledge of BIOS/PCI(and ACPI?). Once we can access the OHCI register via PCI in the loader, the remaining part is relatively easy as you described. I need some help for this part. I suppose that implementing dcons in the loader is architecture dependent. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 01:55:49 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 351ED16A4CE; Tue, 20 Jul 2004 01:55:49 +0000 (GMT) Received: from tora.nunu.org (YahooBB219003182029.bbtec.net [219.3.182.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04C8443D41; Tue, 20 Jul 2004 01:55:49 +0000 (GMT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from tora.nunu.org (unknown [192.168.1.2]) by tora.nunu.org (Postfix) with ESMTP id 4DDD64E50A; Tue, 20 Jul 2004 10:55:45 +0900 (JST) Date: Tue, 20 Jul 2004 10:55:45 +0900 Message-ID: <87k6wzphlq.wl@tora.nunu.org> From: Hidetoshi Shimokawa To: Shizuka Kudo In-Reply-To: <200407191937.04398.dfr@nlsystems.com> References: <20040719161949.17114.qmail@web11405.mail.yahoo.com> <200407191937.04398.dfr@nlsystems.com> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 14) (Reasonable Discussion) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII X-Mailman-Approved-At: Tue, 20 Jul 2004 11:46:22 +0000 cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org cc: Andrew Gallatin Subject: Re: Excellent job on the firewire 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, 20 Jul 2004 01:55:49 -0000 At Mon, 19 Jul 2004 19:37:04 +0100, Doug Rabson wrote: > > On Monday 19 July 2004 17:19, Shizuka Kudo wrote: > > Hi, > > > > Anyone has experience with the newly added IP over 1394 support, i.e. > > fwip? > > > > I compiled it in with the latest kernel at 17 July, but the box > > cannot ping with a M$ & linux box. > > I have that fixed locally but I want to fix some other problems with the > firewire driver - mainly that my freebsd boxes often go haywire when I > plug a windows box into the bus. I also want to finish writing the code > for freebsd to be a fully functional isochronous bus manager. Try this patch for temporary fix. --- //depot/vendor/freebsd/src/sys/dev/firewire/if_fwip.c 2004/06/14 09:36:01 +++ //depot/user/simokawa/firewire/sys/dev/firewire/if_fwip.c 2004/07/11 06:47:39 @@ -91,7 +91,7 @@ static void fwip_unicast_input(struct fw_xfer *); static int fwipdebug = 0; -static int broadcast_channel = 31; /* XXX */ +static int broadcast_channel = 0xc0 | 0x1f; /* tag | channel(XXX) */ static int tx_speed = 2; static int rx_queue_len = FWMAXQUEUE; /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 11:55: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 C352216A4CE; Tue, 20 Jul 2004 11:55:21 +0000 (GMT) Received: from lakermmtao09.cox.net (lakermmtao09.cox.net [68.230.240.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF47143D2D; Tue, 20 Jul 2004 11:55:18 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao09.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP <20040720115505.KODV17142.lakermmtao09.cox.net@dolphin.local.net>; Tue, 20 Jul 2004 07:55:05 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.12.11/8.12.11) with ESMTP id i6KBt2TI001779; Tue, 20 Jul 2004 06:55:02 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.12.11/8.12.11/Submit) id i6KBt2kU001778; Tue, 20 Jul 2004 06:55:02 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200407200823.i6K8Nrrc041129@gw.catspoiler.org> Date: Tue, 20 Jul 2004 06:55:02 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: Don Lewis cc: freebsd-multimedia@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [amd64] Sound breakage with snd_ich driver 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: Tue, 20 Jul 2004 11:55:21 -0000 On 20-Jul-2004 Don Lewis wrote: > On 19 Jul, Conrad J. Sabatier wrote: >> This problem has persisted for the last several weeks now, close to >> a month or so, I would say. >> >> Playing MP3s using madplay, everything works fine for a while, then >> suddenly I get an "output: write: Invalid argument" error each time >> madplay starts up. Any further attempts to use sound via any method >> or app likewise fail. Sound remains broken until a reboot. >> >> Upgraded the system again yesterday, to the new "sound" drivers, >> same results. >> >> I've attached truss output from one of these failed madplay runs. > > I suspect that the sound driver is getting interrupt timeouts and is > marking the channel dead. Do you see the following message in > /var/log/messages? > play interrupt timeout, channel dead > If so, I've seen other reports of this. Yes, that's exactly right. > I think the chn_write() code needs some careful analysis ... That, as well as whatever is still causing these: ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=123971136 -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 11:56: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 1DE7A16A4CE for ; Tue, 20 Jul 2004 11:56:02 +0000 (GMT) Received: from gundel.de.clara.net (gundel.de.clara.net [212.82.225.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id D953843D5A for ; Tue, 20 Jul 2004 11:56:01 +0000 (GMT) (envelope-from jesk@killall.org) Received: from port-212-202-54-113.dynamic.qsc.de ([212.202.54.113] helo=turbofresse) by gundel.de.clara.net with smtp (Exim 4.30; FreeBSD) id 1BmtNY-0008si-24 for freebsd-current@freebsd.org; Tue, 20 Jul 2004 14:05:52 +0200 Message-ID: <037101c46e50$80c3c850$45fea8c0@turbofresse> From: "jesk" To: Date: Tue, 20 Jul 2004 13:55:50 +0200 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.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: Re:I/O or Threading Suffer 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, 20 Jul 2004 11:56:02 -0000 i tested it with /dev/zero and the same happened. i attracted attention to this as iam doing daily mysqldumps over night, and in this time the mysql isnt able to handle any requests from the freeradius server which running on the machines. From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 11:56: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 2DF5416A4CE for ; Tue, 20 Jul 2004 11:56:42 +0000 (GMT) Received: from max.af.czu.cz (max.af.czu.cz [193.84.41.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEA6E43D1F for ; Tue, 20 Jul 2004 11:56:38 +0000 (GMT) (envelope-from lists@hosting50.cz) Received: (qmail 57264 invoked by uid 89); 20 Jul 2004 12:13:00 -0000 Received: from unknown (HELO ?193.84.40.30?) (ares@max.af.czu.cz@193.84.40.30) by max.af.czu.cz with AES256-SHA encrypted SMTP; 20 Jul 2004 12:13:00 -0000 From: Tomas Randa To: current@freebsd.org In-Reply-To: References: <1090316789.788.10.camel@ares.af.czu.cz> Content-Type: text/plain Message-Id: <1090324596.833.1.camel@ares.af.czu.cz> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 20 Jul 2004 13:56:36 +0200 Content-Transfer-Encoding: 7bit Subject: Re: sk0 patch 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, 20 Jul 2004 11:56:42 -0000 Thanks, but patch not working for my skc0@pci2:9:0: class=0x020000 card=0xe0001458 chip=0x432011ab rev=0x13 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = '88E8001 Gigabit 32-bit Ethernet Controller with Integrated PHY' :( Tomas Randa On Tue, 2004-07-20 at 12:00, Bjoern A. Zeeb wrote: > On Tue, 20 Jul 2004, Tomas Randa wrote: > > > is there available a working patch for current "sk" driver? > > yes; in the archives: > > http://lists.freebsd.org/pipermail/freebsd-current/2004-June/028994.html -- Tomas Randa From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 12:20: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 8323716A4CF for ; Tue, 20 Jul 2004 12:20:07 +0000 (GMT) Received: from mirapoint2.brutele.be (mirapoint2.brutele.be [212.68.203.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7790443D1F for ; Tue, 20 Jul 2004 12:20:06 +0000 (GMT) (envelope-from stephane.wirtel@belgacom.net) Received: from brutele.be (213.213.206.16.brutele.be [213.213.206.16]) by mirapoint2.brutele.be (MOS 3.4.7-GR) with SMTP id AQA28844; Tue, 20 Jul 2004 14:15:51 +0200 (CEST) Date: Tue, 20 Jul 2004 14:20:01 +0200 From: Stephane Wirtel To: freebsd-current@freebsd.org Message-ID: <20040720122001.GA25604@laptop.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline User-Agent: Mutt/1.5.6i X-Junkmail-Status: score=12/50, host=mirapoint2.brutele.be Subject: what can i do with a core file ? 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, 20 Jul 2004 12:20:07 -0000 Hi all, I am a new user of FreeBSD, i wanted to unload the linux module, with kldunload, but i have got a core file. What can i do with this file, because, i want to help you. Is there a documentation ? perhaps the handbook ? Best Regards, Stephane From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 12:21: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 130BB16A4CE for ; Tue, 20 Jul 2004 12:21:47 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8153B43D62 for ; Tue, 20 Jul 2004 12:21:46 +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 D56081FF91D; Tue, 20 Jul 2004 14:21:44 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 049631FF90C; Tue, 20 Jul 2004 14:21:43 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 4CE9E1539E; Tue, 20 Jul 2004 12:21:33 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 3E7B515329; Tue, 20 Jul 2004 12:21:34 +0000 (UTC) Date: Tue, 20 Jul 2004 12:21:34 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Tomas Randa In-Reply-To: <1090324596.833.1.camel@ares.af.czu.cz> Message-ID: References: <1090316789.788.10.camel@ares.af.czu.cz> <1090324596.833.1.camel@ares.af.czu.cz> 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 mailing list Subject: Re: sk0 patch 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, 20 Jul 2004 12:21:47 -0000 On Tue, 20 Jul 2004, Tomas Randa wrote: Hi, > Thanks, but patch not working for my > > skc0@pci2:9:0: class=0x020000 card=0xe0001458 chip=0x432011ab rev=0x13 > hdr=0x00 > vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' > device = '88E8001 Gigabit 32-bit Ethernet Controller with > Integrated PHY' so what is your problem then ? -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 12:22: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 2033816A4CE; Tue, 20 Jul 2004 12:22:57 +0000 (GMT) Received: from smtp-out3.blueyonder.co.uk (smtp-out3.blueyonder.co.uk [195.188.213.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 952B643D2F; Tue, 20 Jul 2004 12:22:56 +0000 (GMT) (envelope-from steve@pepcross.dyndns.org) Received: from pepcross.dyndns.org ([82.33.90.59]) by smtp-out3.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Tue, 20 Jul 2004 13:23:13 +0100 Received: (from steve@localhost) by pepcross.dyndns.org (8.12.10/8.12.10/Submit) id i6KCN4aD005360; Tue, 20 Jul 2004 13:23:04 +0100 (BST) (envelope-from steve) Date: Tue, 20 Jul 2004 13:23:04 +0100 From: Steve Roome To: "Conrad J. Sabatier" Message-ID: <20040720122304.GA5158@dylan.home> Mail-Followup-To: Steve Roome , "Conrad J. Sabatier" , freebsd-multimedia@freebsd.org, freebsd-current@freebsd.org References: <200407200823.i6K8Nrrc041129@gw.catspoiler.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-OriginalArrivalTime: 20 Jul 2004 12:23:13.0190 (UTC) FILETIME=[53968C60:01C46E54] X-Mailman-Approved-At: Tue, 20 Jul 2004 12:24:23 +0000 cc: freebsd-multimedia@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [amd64] Sound breakage with snd_ich 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: Tue, 20 Jul 2004 12:22:57 -0000 On Tue, Jul 20, 2004 at 06:55:02AM -0500, Conrad J. Sabatier wrote: > That, as well as whatever is still causing these: > > ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=123971136 Is it a SIL3112 SATA controller ? IIRC someone (not mentioning any names) was claiming it was broken silicon - although to be fair it doesn't "break" the same way under windows xp. Getting it fixed would be nice though. Steve From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 12:32: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 6872816A4CE; Tue, 20 Jul 2004 12:32:26 +0000 (GMT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 559FA43D58; Tue, 20 Jul 2004 12:32:26 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Tue, 20 Jul 2004 05:32:25 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id CBD565D08; Tue, 20 Jul 2004 05:32:20 -0700 (PDT) To: conrads@cox.net In-reply-to: Your message of "Mon, 19 Jul 2004 16:09:19 CDT." Date: Tue, 20 Jul 2004 05:32:20 -0700 From: "Kevin Oberman" Message-Id: <20040720123220.CBD565D08@ptavv.es.net> cc: freebsd-current@freebsd.org cc: freebsd-gnome@freebsd.org Subject: Re: [amd64] System lockups still continuing 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, 20 Jul 2004 12:32:26 -0000 > Date: Mon, 19 Jul 2004 16:09:19 -0500 (CDT) > From: "Conrad J. Sabatier" > > > On 19-Jul-2004 Kevin Oberman wrote: > >> > >> On 18-Jul-2004 Conrad J. Sabatier wrote: > >> > I had posted several weeks ago about constant hard lockups of my > >> > amd64 box. At first, I attributed the problem to GNOME, then to > >> > my kernel config, but now it appears to me that the problem > >> > really lies with Mozilla/Firefox. > >> > >> Well, another theory bites the dust. I tried running GNOME > >> yesterday, never touched Mozilla or Firefox, and the system locked > >> up while doing some file management chores in Nautilus. > >> > >> It must be something low-level in GNOME, some shared library, > >> probably, but I have yet to track it down. > > > > I have lost track of the full thread and this mail list is not > > tracked by google :-(, so this may have been ruled out. Are you sure > > that it's not the preemption problem that is biting you? This applies > > to CURRENT systems only, so may not be applicable to what you are > > seeing, the symptoms are a match. > > Hmm, you may be right. Is there any workaround for this? I've tried > both SCHED_ULE and SCHED_4BSD, both producing the same results. > > What's strange is that this only seems to occur when either running a > full-blown GNOME desktop or using some GNOME-related app under another > environment. > > I'm currently working under KDE, just for comparison, and no such > problems have occurred, unless I try using, say, Mozilla or Firefox. > > I'll Cc: this to current and see what they think. The problem is not specific to ULE or 4BSD. A fix was checked in last night, so cvsup and rebuild might just fix it. Early reports are that the patch resolves the problem, but the author is not sure that this is a complete fix. If that does not work, you will need to back off 4 files to July 2 before jhb committed the preemption code. /sys/i386/i386/intr_machdep.c v 1.6 /sys/kern/sched_ule.c v 1.109 /sys/kern/kern_intr.c v 1.110 /sys/sys/interrupt.h v 1.27 Then apply the one line plus one word patch for the new debugger from /sys/kern/sched_ule.c v 1.115 and you will be OK. I will be rebuilding my system with the patched code this morning, so hopefully this is now a thing of the past. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 12:43: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 ED34A16A537; Tue, 20 Jul 2004 12:43:47 +0000 (GMT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 9AC6943D2F; Tue, 20 Jul 2004 12:43:46 +0000 (GMT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 20 Jul 2004 13:43:45 +0100 (BST) To: "M. Warner Losh" In-Reply-To: Your message of "Mon, 19 Jul 2004 19:50:56 MDT." <20040719.195056.35662742.imp@bsdimp.com> Date: Tue, 20 Jul 2004 13:43:44 +0100 From: Ian Dowse Message-ID: <200407201343.aa92531@salmon.maths.tcd.ie> cc: mycroft@NetBSD.org cc: scottl@freebsd.org cc: freebsd-current@freebsd.org cc: pjd@freebsd.org Subject: Re: Unloading USB driver while device is attached. 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, 20 Jul 2004 12:43:53 -0000 In message <20040719.195056.35662742.imp@bsdimp.com>, "M. Warner Losh" writes: >: o Attempt to follow the correct procedure for synchronising with >: the BIOS via SMM to take over control of the EHCI controller. >: This may fix problems when the BIOS is configured to emulate >: legacy devices, but is untested on any affected machines. > >Docs on how to do this? I've not seen this info... It's in the EHCI spec at: http://developer.intel.com/technology/usb/download/ehci-r10.pdf See sections 5.1 (EHCI Extended Capability: Pre-OS to OS Handoff Synchronization) and 2.1.7 (USBLEGSUP - USB Legacy Support Extended Capability). A quick summary is that if the BIOS implements legacy emulation via SMIs then there is a particular host controller flag that the OS is supposed to set that will cause the BIOS to receive an SMI. The BIOS should recognise this signal and disable the legacy support, giving the OS exclusive access to the host controller. Ian From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 13:32: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 208EE16A4E6 for ; Tue, 20 Jul 2004 13:32:43 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDA3E43D58 for ; Tue, 20 Jul 2004 13:32:42 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6KDW9ET096017; Tue, 20 Jul 2004 09:32:09 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6KDW8Zr096014; Tue, 20 Jul 2004 09:32:09 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 20 Jul 2004 09:32:08 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Scott Long In-Reply-To: <40FD03E7.8000300@samsco.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: jesk cc: freebsd-current@freebsd.org Subject: Re: I/O or Threading Suffer 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, 20 Jul 2004 13:32:43 -0000 On Tue, 20 Jul 2004, Scott Long wrote: > If you are dd'ing from /dev/random, then you are depleting the entropy > pool. Anything else that tries to get random numbers is going to block > in strange ways. Trying just dd'ing from /dev/zero and see if that > makes a difference. With Yarrow, /dev/random should just keep on chugging, so this is unlikely to be the source. However, lots of /dev/random I/O may take a while to yield if it's working hard in kernel, so if that is combined with a scheduling nit of some sort, we could be looking at a starvation issue. Do we know if this is on a UP box or SMP box, and if so, whether it's using HTT? I could try reproducing it here and see if I see the same thing. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 13: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 3A3EF16A4CE; Tue, 20 Jul 2004 13:53:14 +0000 (GMT) Received: from gundel.de.clara.net (gundel.de.clara.net [212.82.225.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE09E43D41; Tue, 20 Jul 2004 13:53:13 +0000 (GMT) (envelope-from jesk@killall.org) Received: from port-212-202-54-113.dynamic.qsc.de ([212.202.54.113] helo=turbofresse) by gundel.de.clara.net with smtp (Exim 4.30; FreeBSD) id 1BmvCx-0008c4-QF; Tue, 20 Jul 2004 16:03:03 +0200 Message-ID: <044201c46e60$dfdb1810$45fea8c0@turbofresse> From: "jesk" To: "Robert Watson" , References: Date: Tue, 20 Jul 2004 15:53:02 +0200 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.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: Re: I/O or Threading Suffer 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, 20 Jul 2004 13:53:14 -0000 > On Tue, 20 Jul 2004, Scott Long wrote: > > > If you are dd'ing from /dev/random, then you are depleting the entropy > > pool. Anything else that tries to get random numbers is going to block > > in strange ways. Trying just dd'ing from /dev/zero and see if that > > makes a difference. > > With Yarrow, /dev/random should just keep on chugging, so this is unlikely > to be the source. However, lots of /dev/random I/O may take a while to > yield if it's working hard in kernel, so if that is combined with a > scheduling nit of some sort, we could be looking at a starvation issue. > > Do we know if this is on a UP box or SMP box, and if so, whether it's > using HTT? I could try reproducing it here and see if I see the same > thing. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Principal Research Scientist, McAfee Research > > > > hi, i have tested it with /dev/zero, /dev/random and /dev/urandom, the same everywhere. as i mentioned i noticed the problem while mysqldump was dumping the mysqldatabase over night. in this timespan the mysqld didnt responsed to anything. after the dump(3minutes of time) the mysqld was back again and everything worked again. i have tested it with 2 UP boxes (i386/pIII) without HTT. From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 14:22: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 7AC2216A4CE; Tue, 20 Jul 2004 14:22:15 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id E502743D5C; Tue, 20 Jul 2004 14:22:14 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6KELeq5096929; Tue, 20 Jul 2004 10:21:40 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6KELefR096926; Tue, 20 Jul 2004 10:21:40 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 20 Jul 2004 10:21:40 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: jesk In-Reply-To: <044201c46e60$dfdb1810$45fea8c0@turbofresse> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: scottl@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: I/O or Threading Suffer 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, 20 Jul 2004 14:22:15 -0000 On Tue, 20 Jul 2004, jesk wrote: > i have tested it with /dev/zero, /dev/random and /dev/urandom, the same > everywhere. as i mentioned i noticed the problem while mysqldump was > dumping the mysqldatabase over night. in this timespan the mysqld didnt > responsed to anything. after the dump(3minutes of time) the mysqld was > back again and everything worked again. i have tested it with 2 UP > boxes (i386/pIII) without HTT. Ok, so here's what I see, and the hardware configuration is somewhat different. I'm running with the network stack Giant-free on a dual-processor Xeon box, with a parallel threaded benchmark against a MySQL server. I'm using libpthread in m:n mode, without the flag for system scope threads, and running with the 4BSD scheduler, which typically yields greater throughput in my benchmark (but is typically thought of as less graceful in elevating interactive-like processes under load). Under "normal" circumstances on this box, the benchmark yields about 7000 transactions a second in this configuration, data set, etc. I ran the benchmark in a loop via sshd on one terminal, and ran dd from /dev/urandom to /dev/null on the serial console. The benchmark is configured to generate a transactions/sec stream for runs of 1000 transactions using 11 clients: 6972.90 7070.46 6971.63 6998.54 7043.21 397.08 <- dd starts about here 357.18 647.10 379.39 So there's certainly a substantial performance impact. I guess the question is how we reach that level of impact, and what performance under these circumstances would be "reasonable". It does seem "undue" by reasonable expectations. I notice that ssh interactivity is also severely hampered in this configuration as well. When I run in a 1 thread configuration, I get about 5100-5800 transactions/sec (much higher variance). When I kick in the dd session, I observe similar problems: 5339.64 5457.56 5044.89 5417.26 35.75 <-- guess what started running about here 21.71 17.22 I suspect a bit of using KTR to trace scheduling would probably elucidate things quite a bit. I'm not sure how you feel about tracing kernel scheduling, but the ktr(9) and ktrdump(8) man pages aren't too terrible. An interesting comparison here is /dev/zero as a source vs /dev/random as a source. In the /dev/zero case, I see some performance hit, but not nearly as much. Here's the 11 client version of the benchmark leading up to "dd if=/dev/zero of=/dev/zero bs=128k": 6993.62 7013.36 7128.19 4505.15 <-- dd starts 3689.62 4349.18 The primary difference between /dev/zero and /dev/random is that /dev/random does a bunch of computation on behalf of the process, and /dev/zero doesn't. /dev/zero does just the copy of data to userspace. So it sounds like when a thread/process is using a lot of CPU in kernel, it's starving other processes more than it should. Mark -- how much computation is being done here -- would it be worth dropping the Giant lock during that computation so that the thread can yield without generating a priority inversion? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 14:33: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 3B4F316A4CF; Tue, 20 Jul 2004 14:33:46 +0000 (GMT) Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.157.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1AEE43D48; Tue, 20 Jul 2004 14:33:45 +0000 (GMT) (envelope-from mark@grondar.org) Received: from storm.FreeBSD.org.uk (Ugrondar@localhost [127.0.0.1]) i6KEXisd021058; Tue, 20 Jul 2004 15:33:44 +0100 (BST) (envelope-from mark@grondar.org) Received: (from Ugrondar@localhost)i6KEXiO8021057; Tue, 20 Jul 2004 15:33:44 +0100 (BST) (envelope-from mark@grondar.org) X-Authentication-Warning: storm.FreeBSD.org.uk: Ugrondar set sender to mark@grondar.org using -f Received: from grondar.org (localhost [127.0.0.1])i6KEJxJX079041; Tue, 20 Jul 2004 15:19:59 +0100 (BST) (envelope-from mark@grondar.org) Message-Id: <200407201419.i6KEJxJX079041@grimreaper.grondar.org> To: Robert Watson From: Mark Murray In-Reply-To: Your message of "Tue, 20 Jul 2004 09:32:08 EDT." Date: Tue, 20 Jul 2004 15:19:59 +0100 Sender: mark@grondar.org cc: jesk cc: freebsd-current@FreeBSD.ORG Subject: Re: I/O or Threading Suffer 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, 20 Jul 2004 14:33:46 -0000 Robert Watson writes: > On Tue, 20 Jul 2004, Scott Long wrote: > > > If you are dd'ing from /dev/random, then you are depleting the entropy > > pool. Anything else that tries to get random numbers is going to block > > in strange ways. Trying just dd'ing from /dev/zero and see if that > > makes a difference. > > With Yarrow, /dev/random should just keep on chugging, so this is unlikely > to be the source. However, lots of /dev/random I/O may take a while to > yield if it's working hard in kernel, so if that is combined with a > scheduling nit of some sort, we could be looking at a starvation issue. When you read /dev/random, you only exercise the output generator, and this is a pretty simple piece of code. Yarrow's kernel thread is used ONLY for the entropy harvesting, and is only indirectly coupled to the output generator. M -- Mark Murray iumop ap!sdn w,I idlaH From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 14:43: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 2EF4016A4CE for ; Tue, 20 Jul 2004 14:43:41 +0000 (GMT) Received: from ai.x25.net (ai.x25.net [204.57.81.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70B5143D3F for ; Tue, 20 Jul 2004 14:43:40 +0000 (GMT) (envelope-from jmarquez@x25.net) Received: from TNI1341 (ppp-132.x25.net [204.57.77.132]) by ai.x25.net (8.11.6/8.11.6) with SMTP id i6KEfen08768 for ; Tue, 20 Jul 2004 09:41:40 -0500 Received: from Unknown (209.163.253.71) by AVG3000 (204.57.77.132) Message-ID: <002501c46e67$efbd1650$47fda3d1@sanmarcos.x25.net> From: "jesse marquez jr" To: Date: Tue, 20 Jul 2004 09:43:35 -0500 MIME-Version: 1.0 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 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Kernel build error, linux module? 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, 20 Jul 2004 14:43:41 -0000 5.2-current july 18th,2004 #cd /usr/src #make buildkernel KERNCONF=3DKERNEL --------- --------- /usr/src/sys/compat/linux/linux_socket.c: In function = `linux_sendto_hdrincl': /usr/src/sys/compat/linux/linux_socket.c:443: warning: declaration of = `sg' shadows a parameter /usr/src/sys/compat/linux/linux_socket.c:458: warning: passing arg 1 of = `stackgap_alloc' from incompatible pointer type /usr/src/sys/compat/linux/linux_socket.c: In function `linux_sendto': /usr/src/sys/compat/linux/linux_socket.c:881: warning: passing arg 2 of = `linux_sendto_hdrincl' from incompatible pointer type /usr/src/sys/compat/linux/linux_socket.c:881: error: too few arguments = to function `linux_sendto_hdrincl' *** Error code 1 Stop in /usr/src/sys/modules/linux. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/CONCEPT. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. ---------- ---------- I've attached my kernel. Any ideas? I may be missing something in my = custome kernel. Thanks for the time. over and out, Jesse From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 14:43: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 D5E8E16A4CE; Tue, 20 Jul 2004 14:43:43 +0000 (GMT) Received: from smtp.cegetel.net (mf00.sitadelle.com [212.94.174.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA83B43D2D; Tue, 20 Jul 2004 14:43:42 +0000 (GMT) (envelope-from tataz@sitadelle.com) Received: from droopy.tech.sitadelle.com (unknown [213.223.184.193]) by smtp.cegetel.net (Postfix) with ESMTP id D32216733F; Tue, 20 Jul 2004 16:43:39 +0200 (CEST) Received: by droopy.tech.sitadelle.com (Postfix, from userid 1000) id 74814FC2F5; Tue, 20 Jul 2004 16:44:34 +0200 (CEST) Date: Tue, 20 Jul 2004 16:44:34 +0200 From: Jeremie Le Hen To: freebsd-current@freebsd.org Message-ID: <20040720144434.GT9548@sitadelle.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="h31gzZEtNLTqOjlF" Content-Disposition: inline User-Agent: Mutt/1.5.5.1+cvs20040105i Subject: mount(8) and /etc/rc.d/jail 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, 20 Jul 2004 14:43:44 -0000 --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello -current, I have a jail running Postfix whose filesystem is mirrored from the host using mount_nullfs(8). The problem is that when I upgrade the Postfix, the port removes /usr/local/libexec/postfix/, which is mount_nullfs'ed on /jail/postfix/usr/local/libexec/postfix/, then recreates it, but the vnode is obsviously not the same and thus the nullfs mount is not valid any longer. Of course, I can simply install Postfix in the jail filesystem and not on the host, but I consider this as a workaround and furthermore I want to run Postfix from the host itself. I was fed up with typing for fs in `mount | awk '/postfix/ {print $3}'` ; do umount $i ; done each time I don't forget to do it. I decided to make the rc(8) jail script manage the mounts for each jail. There was two ways to do it : * either use a tiny awk script to parse fstab(5) file and some magic shell gymnatic to mount/umount when starting/stopping the jail, * or make a new mount(8)/umount(8) option to act only on mount points which match a given prefix. I implemented the second solution, but if someone has a good argument to use the first one instead, I'm ready to listen to him. Two patches are attached. I didn't make a PR since I would like to see what people think before sending it. The first patch adds a `-c' flags to mount(8) and umount(8) whose argument is the prefix to match for (`c' for `cmp', since `p' is already used in mount(8)). I tested it against my system and it seems to work quite well. Nevertheless a friend of mine pointed me that matching against a pathname could be delicate because of symlinks. I don't really know how to overcome this, except I can put some king of warning or advice in the manpage. Suggestions are very welcome. The second patch simply modifies the rc(8) jail script to take advantage of the first one. It works well either. Regards, -- Jeremie LE HEN aka TtZ/TataZ jeremie.le-hen@epita.fr ttz@epita.fr Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="mount-c.patch" Index: sbin/mount/mount.8 =================================================================== RCS file: /home/ncvs/src/sbin/mount/mount.8,v retrieving revision 1.68 diff -u -p -r1.68 mount.8 --- sbin/mount/mount.8 17 May 2004 08:35:42 -0000 1.68 +++ sbin/mount/mount.8 20 Jul 2004 13:00:16 -0000 @@ -37,6 +37,7 @@ .Sh SYNOPSIS .Nm .Op Fl adfpruvw +.Op Fl c Ar prefix .Op Fl F Ar fstab .Op Fl o Ar options .Op Fl t Ar ufs | external_type @@ -80,9 +81,18 @@ Exceptions are those marked as .Dq noauto , excluded by the .Fl t +flag (see below), restricted by the +.Fl c flag (see below), or if they are already mounted (except the root file system which is always remounted to preserve traditional single user mode behavior). +.It Fl c +This flag can be used to indicate that the action should only occur +when the mount point matches +.Pa prefix . +Note that this does only make sense with the +.Fl a +flag. .It Fl d Causes everything to be done except for the actual system call. This option is useful in conjunction with the Index: sbin/mount/mount.c =================================================================== RCS file: /home/ncvs/src/sbin/mount/mount.c,v retrieving revision 1.66 diff -u -p -r1.66 mount.c --- sbin/mount/mount.c 26 Apr 2004 15:13:45 -0000 1.66 +++ sbin/mount/mount.c 20 Jul 2004 13:00:16 -0000 @@ -132,17 +132,21 @@ main(argc, argv) FILE *mountdfp; pid_t pid; int all, ch, i, init_flags, mntsize, rval, have_fstab; - char *cp, *ep, *options; + char *cmp, *cp, *ep, *options; all = init_flags = 0; + cmp = NULL; options = NULL; vfslist = NULL; vfstype = "ufs"; - while ((ch = getopt(argc, argv, "adF:fo:prwt:uv")) != -1) + while ((ch = getopt(argc, argv, "ac:dF:fo:prwt:uv")) != -1) switch (ch) { case 'a': all = 1; break; + case 'c': + cmp = optarg; + break; case 'd': debug = 1; break; @@ -186,6 +190,9 @@ main(argc, argv) argc -= optind; argv += optind; + if (all == 0 && cmp != NULL) + warnx("Warning: use of -c without -a"); + #define BADTYPE(type) \ (strcmp(type, FSTAB_RO) && \ strcmp(type, FSTAB_RW) && strcmp(type, FSTAB_RQ)) @@ -200,6 +207,9 @@ main(argc, argv) if (BADTYPE(fs->fs_type)) continue; if (checkvfsname(fs->fs_vfstype, vfslist)) + continue; + if (cmp != NULL && + strncmp(fs->fs_file, cmp, strlen(cmp))) continue; if (hasopt(fs->fs_mntops, "noauto")) continue; Index: sbin/umount/umount.8 =================================================================== RCS file: /home/ncvs/src/sbin/umount/umount.8,v retrieving revision 1.20 diff -u -p -r1.20 umount.8 --- sbin/umount/umount.8 9 Apr 2004 19:58:40 -0000 1.20 +++ sbin/umount/umount.8 20 Jul 2004 13:00:17 -0000 @@ -40,6 +40,7 @@ .Ar special | node | fsid .Nm .Fl a | A +.Op Fl c Ar prefix .Op Fl F Ar fstab .Op Fl fv .Op Fl h Ar host @@ -68,6 +69,15 @@ are unmounted. .It Fl A All the currently mounted file systems except the root are unmounted. +.It Fl c +This flag can be used to indicate that the action should only occur +when the mount point matches +.Pa prefix . +Note that this does only make sens with the +.Fl a +or +.Fl A +flags. .It Fl F Ar fstab Specify the .Pa fstab Index: sbin/umount/umount.c =================================================================== RCS file: /home/ncvs/src/sbin/umount/umount.c,v retrieving revision 1.44 diff -u -p -r1.44 umount.c --- sbin/umount/umount.c 9 Apr 2004 19:58:40 -0000 1.44 +++ sbin/umount/umount.c 20 Jul 2004 13:00:17 -0000 @@ -66,6 +66,7 @@ typedef enum { FIND, REMOVE, CHECKUNIQUE struct addrinfo *nfshost_ai = NULL; int fflag, vflag; char *nfshost; +char *cmp = NULL; struct statfs *checkmntlist(char *); int checkvfsname (const char *, char **); @@ -94,7 +95,7 @@ main(int argc, char *argv[]) sync(); all = errs = 0; - while ((ch = getopt(argc, argv, "AaF:fh:t:v")) != -1) + while ((ch = getopt(argc, argv, "Aac:F:fh:t:v")) != -1) switch (ch) { case 'A': all = 2; @@ -102,6 +103,9 @@ main(int argc, char *argv[]) case 'a': all = 1; break; + case 'c': + cmp = optarg; + break; case 'F': setfstab(optarg); break; @@ -153,6 +157,9 @@ main(int argc, char *argv[]) sfs = &mntbuf[mntsize]; if (checkvfsname(sfs->f_fstypename, typelist)) continue; + if (cmp != NULL && + strncmp(sfs->f_mntonname, cmp, strlen(cmp))) + continue; if (umountfs(sfs) != 0) errs = 1; } @@ -164,6 +171,8 @@ main(int argc, char *argv[]) errs = umountall(typelist); break; case 0: + if (cmp != NULL) + warnx("Warning: use of -c without -a nor -A"); for (errs = 0; *argv != NULL; ++argv) if (checkname(*argv, typelist) != 0) errs = 1; @@ -203,6 +212,8 @@ umountall(char **typelist) if (getvfsbyname(fs->fs_vfstype, &vfc) == -1) continue; if (checkvfsname(fs->fs_vfstype, typelist)) + continue; + if (cmp != NULL && strncmp(fs->fs_file, cmp, strlen(cmp))) continue; /* --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="jail_mount.patch" Index: etc/defaults/rc.conf =================================================================== RCS file: /home/ncvs/src/etc/defaults/rc.conf,v retrieving revision 1.210 diff -u -p -r1.210 rc.conf --- etc/defaults/rc.conf 30 Jun 2004 15:58:46 -0000 1.210 +++ etc/defaults/rc.conf 20 Jul 2004 12:59:37 -0000 @@ -489,6 +489,7 @@ jail_sysvipc_allow="NO" # Allow SystemV #jail_example_fdescfs_enable="NO" # mount fdescfs in the jail #jail_example_procfs_enable="NO" # mount procfs in jail #jail_example_devfs_ruleset="ruleset_name" # devfs ruleset to apply to jail +#jail_example_mount_enable="NO" # mount jail's fstab entries ############################################################## ### Define source_rc_confs, the mechanism used by /etc/rc.* ## Index: etc/rc.d/jail =================================================================== RCS file: /home/ncvs/src/etc/rc.d/jail,v retrieving revision 1.14 diff -u -p -r1.14 jail --- etc/rc.d/jail 8 Mar 2004 12:25:05 -0000 1.14 +++ etc/rc.d/jail 20 Jul 2004 12:59:37 -0000 @@ -44,12 +44,15 @@ init_variables() [ -z "${jail_fdescfs}" ] && jail_fdescfs="NO" eval jail_procfs=\"\$jail_${_j}_procfs_enable\" [ -z "${jail_procfs}" ] && jail_procfs="NO" + eval jail_mount=\"\$jail_${_j}_mount_enable\" + [ -z "${jail_mount}" ] && jail_mount="NO" # Debugging aid # debug "$_j devfs enable: $jail_devfs" debug "$_j fdescfs enable: $jail_fdescfs" debug "$_j procfs enable: $jail_procfs" + debug "$_j mount enable: $jail_mount" debug "$_j hostname: $jail_hostname" debug "$_j ip: $jail_ip" debug "$_j root: $jail_rootdir" @@ -108,6 +111,10 @@ jail_umount_fs() umount -f ${jail_procdir} >/dev/null 2>&1 fi fi + + if checkyesno jail_mount; then + umount -A -c ${jail_rootdir} >/dev/null 2>&1 + fi } jail_start() @@ -125,6 +132,10 @@ jail_start() for _jail in ${jail_list} do init_variables $_jail + if checkyesno jail_mount; then + info "Mounting jail's fstab entries" + mount -a -c ${jail_rootdir} + fi if checkyesno jail_devfs; then info "Mounting devfs on ${jail_devdir}" devfs_mount_jail "${jail_devdir}" ${jail_ruleset} --h31gzZEtNLTqOjlF-- From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 15:13: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 1937F16A4CF; Tue, 20 Jul 2004 15:13:02 +0000 (GMT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5018643D31; Tue, 20 Jul 2004 15:13:01 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id D2C5E65339; Tue, 20 Jul 2004 16:12:58 +0100 (BST) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 19390-03-2; Tue, 20 Jul 2004 16:12:58 +0100 (BST) Received: from empiric.dek.spc.org (unknown [217.33.132.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id 7CE87651EB; Tue, 20 Jul 2004 16:12:57 +0100 (BST) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id 87024610F; Tue, 20 Jul 2004 04:42:56 +0100 (BST) Date: Tue, 20 Jul 2004 04:42:56 +0100 From: Bruce M Simpson To: Hidetoshi Shimokawa Message-ID: <20040720034256.GA826@empiric.dek.spc.org> Mail-Followup-To: Hidetoshi Shimokawa , Doug Rabson , simokawa@freebsd.org, freebsd-current@freebsd.org, Andrew Gallatin References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> <87hds3pfgv.wl@tora.nunu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87hds3pfgv.wl@tora.nunu.org> cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org cc: Andrew Gallatin Subject: Re: Excellent job on the firewire 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, 20 Jul 2004 15:13:02 -0000 On Tue, Jul 20, 2004 at 11:41:52AM +0900, Hidetoshi Shimokawa wrote: > It is not enough :-< I lack the knowledge of BIOS/PCI(and ACPI?). > Once we can access the OHCI register via PCI in the loader, > the remaining part is relatively easy as you described. > I need some help for this part. I suppose that implementing dcons > in the loader is architecture dependent. Very much so, to begin with. Let's consider the i386 case. libi386/biospci.c wants FireWire device classes added to it for its probe. Some BIOS wrapper functions to manipulate PCI configuration registers need to be added too. Then a fwconsole driver much like comconsole could be written, i.e. fwc_probe(), fwc_init() etc. I believe it's safe to assume that V==P for address space at this point. I guess this could act as a shim before the driver actually gets loaded. kenv could be used to tell dcons where the loader had allocated the buffer before the kernel actually starts. There would have to be a comfortable handover between loader and dcons in the kernel, but because it just uses a ring buffer, I imagine this is somewhat easier than it would be otherwise. I am about to get some long overdue sleep, otherwise I'd begin hacking this myself. ;-) BMS From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 15:20:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0682416A4CE; Tue, 20 Jul 2004 15:20:47 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.12.11/8.12.11) with ESMTP id i6KFKkqd088177; Tue, 20 Jul 2004 11:20:46 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.12.11/8.12.11/Submit) id i6KFKjRG088176; Tue, 20 Jul 2004 11:20:45 -0400 (EDT) (envelope-from green) Date: Tue, 20 Jul 2004 11:20:44 -0400 From: Brian Fundakowski Feldman To: Kevin Oberman Message-ID: <20040720152044.GB1009@green.homeunix.org> References: <20040720123220.CBD565D08@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040720123220.CBD565D08@ptavv.es.net> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: freebsd-gnome@freebsd.org Subject: Re: [amd64] System lockups still continuing 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, 20 Jul 2004 15:20:47 -0000 On Tue, Jul 20, 2004 at 05:32:20AM -0700, Kevin Oberman wrote: > > Date: Mon, 19 Jul 2004 16:09:19 -0500 (CDT) > > From: "Conrad J. Sabatier" > > > > > > On 19-Jul-2004 Kevin Oberman wrote: > > >> > > >> On 18-Jul-2004 Conrad J. Sabatier wrote: > > >> > I had posted several weeks ago about constant hard lockups of my > > >> > amd64 box. At first, I attributed the problem to GNOME, then to > > >> > my kernel config, but now it appears to me that the problem > > >> > really lies with Mozilla/Firefox. > > >> > > >> Well, another theory bites the dust. I tried running GNOME > > >> yesterday, never touched Mozilla or Firefox, and the system locked > > >> up while doing some file management chores in Nautilus. > > >> > > >> It must be something low-level in GNOME, some shared library, > > >> probably, but I have yet to track it down. > > > > > > I have lost track of the full thread and this mail list is not > > > tracked by google :-(, so this may have been ruled out. Are you sure > > > that it's not the preemption problem that is biting you? This applies > > > to CURRENT systems only, so may not be applicable to what you are > > > seeing, the symptoms are a match. > > > > Hmm, you may be right. Is there any workaround for this? I've tried > > both SCHED_ULE and SCHED_4BSD, both producing the same results. > > > > What's strange is that this only seems to occur when either running a > > full-blown GNOME desktop or using some GNOME-related app under another > > environment. > > > > I'm currently working under KDE, just for comparison, and no such > > problems have occurred, unless I try using, say, Mozilla or Firefox. > > > > I'll Cc: this to current and see what they think. > > The problem is not specific to ULE or 4BSD. A fix was checked in last > night, so cvsup and rebuild might just fix it. Early reports are that > the patch resolves the problem, but the author is not sure that this is > a complete fix. It is not a complete fix in i386/SMP, but seems to make it harder to cause the lock-up. I am not able to cause the lock-up at all simply by disabling PREEMPTION in src/sys/param.h. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 15:38: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 031E216A4CE; Tue, 20 Jul 2004 15:38:02 +0000 (GMT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id E278743D54; Tue, 20 Jul 2004 15:38:01 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Tue, 20 Jul 2004 08:38:01 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 4CA0A5D09; Tue, 20 Jul 2004 08:38:00 -0700 (PDT) To: Brian Fundakowski Feldman In-reply-to: Your message of "Tue, 20 Jul 2004 11:20:44 EDT." <20040720152044.GB1009@green.homeunix.org> Date: Tue, 20 Jul 2004 08:38:00 -0700 From: "Kevin Oberman" Message-Id: <20040720153800.4CA0A5D09@ptavv.es.net> cc: freebsd-current@freebsd.org cc: freebsd-gnome@freebsd.org Subject: Re: [amd64] System lockups still continuing 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, 20 Jul 2004 15:38:02 -0000 > Date: Tue, 20 Jul 2004 11:20:44 -0400 > From: Brian Fundakowski Feldman > > On Tue, Jul 20, 2004 at 05:32:20AM -0700, Kevin Oberman wrote: > > > Date: Mon, 19 Jul 2004 16:09:19 -0500 (CDT) > > > From: "Conrad J. Sabatier" > > > > > > > > > On 19-Jul-2004 Kevin Oberman wrote: > > > >> > > > >> On 18-Jul-2004 Conrad J. Sabatier wrote: > > > >> > I had posted several weeks ago about constant hard lockups of my > > > >> > amd64 box. At first, I attributed the problem to GNOME, then to > > > >> > my kernel config, but now it appears to me that the problem > > > >> > really lies with Mozilla/Firefox. > > > >> > > > >> Well, another theory bites the dust. I tried running GNOME > > > >> yesterday, never touched Mozilla or Firefox, and the system locked > > > >> up while doing some file management chores in Nautilus. > > > >> > > > >> It must be something low-level in GNOME, some shared library, > > > >> probably, but I have yet to track it down. > > > > > > > > I have lost track of the full thread and this mail list is not > > > > tracked by google :-(, so this may have been ruled out. Are you sure > > > > that it's not the preemption problem that is biting you? This applies > > > > to CURRENT systems only, so may not be applicable to what you are > > > > seeing, the symptoms are a match. > > > > > > Hmm, you may be right. Is there any workaround for this? I've tried > > > both SCHED_ULE and SCHED_4BSD, both producing the same results. > > > > > > What's strange is that this only seems to occur when either running a > > > full-blown GNOME desktop or using some GNOME-related app under another > > > environment. > > > > > > I'm currently working under KDE, just for comparison, and no such > > > problems have occurred, unless I try using, say, Mozilla or Firefox. > > > > > > I'll Cc: this to current and see what they think. > > > > The problem is not specific to ULE or 4BSD. A fix was checked in last > > night, so cvsup and rebuild might just fix it. Early reports are that > > the patch resolves the problem, but the author is not sure that this is > > a complete fix. > > It is not a complete fix in i386/SMP, but seems to make it harder to > cause the lock-up. I am not able to cause the lock-up at all simply > by disabling PREEMPTION in src/sys/param.h. Brian, Thanks for the information. In my case it's i386/UP. I am currently building a new kernel and will try it out soon. When I had the problem, it showed up reliably in a buildworld, so I will fire off one as soon as the new kernel is up. I tried disabling PREEMPTION, but the system was barely usable whenever it was running anything that was CPU intensive (such as compiling a port), so I backed out the changes instead. While this works, it is something I want to get away from ASAP. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 16:02: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 C57AB16A4CF for ; Tue, 20 Jul 2004 16:02:12 +0000 (GMT) Received: from tara.freenix.org (keltia.freenix.org [82.224.56.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D4D243D41 for ; Tue, 20 Jul 2004 16:02:12 +0000 (GMT) (envelope-from roberto@keltia.freenix.fr) Received: by tara.freenix.org (Postfix/TLS, from userid 101) id 539272E1B; Tue, 20 Jul 2004 18:02:11 +0200 (CEST) Date: Tue, 20 Jul 2004 18:02:11 +0200 From: Ollivier Robert To: Brad Knowles Message-ID: <20040720160211.GA70447@tara.freenix.org> Mail-Followup-To: Brad Knowles , current@freebsd.org References: <20040627145408.GA71410@stud.fit.vutbr.cz> <20040628214659.GA97400@tara.freenix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: MacOS X / PowerBook G4 - FreeBSD 5.0 / 2x PIII/800 SMP User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: HEADSUP: ntpd 4.2.0 committed 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, 20 Jul 2004 16:02:12 -0000 According to Brad Knowles: > > I'm 95% finished with the upgrade to 4.2.0, I just need to test it on out > > Tier-1 architectures. Lots of bug fixes, IPv6 for free and all that. As threatened almost a month ago, I've now committed ntpd 4.2.0 to the 5.2-CURRENT tree. It has been tested on all our Tier-1 platforms and IA-64. Please report any problem to me or through Gnats. 64 bits cleanliness is not confirmed for the asynchronous resolver (arlib) so if anyone can confirm it works (or not) on our 64 bits platforms, I'd like to get feedback. What's in doc/ has not been updated so if anyone feels an urge to do so, please step in. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr Darwin snuadh.freenix.org Kernel Version 7.4.0: Wed May 12 16:58:24 PDT 2004 From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 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 AE2F716A4CE for ; Tue, 20 Jul 2004 16:07:38 +0000 (GMT) Received: from parati.mdbrasil.com.br (parati.mdbrasil.com.br [200.210.70.4]) by mx1.FreeBSD.org (Postfix) with SMTP id 5DB0143D54 for ; Tue, 20 Jul 2004 16:07:37 +0000 (GMT) (envelope-from jmelo-lists@freebsdbrasil.com.br) Received: (qmail 74343 invoked by uid 0); 20 Jul 2004 15:40:03 -0000 Received: from jmelo-lists@freebsdbrasil.com.br by parati.mdbrasil.com.br by uid 82 with qmail-scanner-1.20rc1 (uvscan: v4.1.60/v4288. Clear:RC:1:. Processed in 3.845519 secs); 20 Jul 2004 15:40:03 -0000 Received: from unknown (HELO ?192.168.1.2?) (200.167.244.39) by parati.mdbrasil.com.br with SMTP; 20 Jul 2004 12:39:59 -0300 From: Jean Milanez Melo To: current@freebsd.org Content-Type: multipart/mixed; boundary="=-Vc74wGK27wp5eDYMr4KI" Organization: FreeBSD Brasil LTDA Message-Id: <1090338524.783.3.camel@offset.freebsdbrasil.com.br> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 20 Jul 2004 12:48:44 -0300 Subject: FreeBSD embedded: TinyBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jmelo-lists@freebsdbrasil.com.br List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jul 2004 16:07:38 -0000 --=-Vc74wGK27wp5eDYMr4KI Content-Type: text/plain Content-Transfer-Encoding: 7bit Hello current, Please allow me to introduce myself, I'm one of the coordinators of the Brazilian FreeBSD Users group, coordinator of the official FreeBSD documentation's translation group and have been working with embedded FreeBSD systems since year 2000. I've been studying NanoBSD ever since Poul-Henning posted about it on one of the mailling lists, and I have been following this project closely. It really is a great project. However, I think it sometimes creates unnecessary partitions, takes too long to build the system due to make world and it copies lots of unneeded binaries, taking a lot of precious space. So me and Patrick Tracanelli (another active member of the Brazilian FreeBSD community) decided to write a new set of scripts to build embedded systems. We've named it TinyBSD, and its goal is to be faster at building-time, occupy less space on the target device and to ease customization like PicoBSD does. Untar/gzip the tinybsd.tgz file under /usr/src/release. # ls TINYBSD TODO tinybsd.basefiles tinybsd.sh We first take the file TINYBSD, which like in PicoBSD we can use to define or remove all kernel options to the new system. Then we have tinybsd.basefiles, where we define all binaries necessary to get the system running and anyone can edit it as they will. Finally we have the script itself, tinybsd.sh. It's a simple script, yet functional. We based it on NanoBSD's and its idea is to create a temporary work directory where the new system's directory tree will be created. Then it'll copy all files listed on tinybsd.basefiles to this tree. This copying process is essential to the speed of the building process, as we eliminate the recompiling phase. The reason for this is FreeBSD 5.1' dynamically-linked base system, which take much less space than the old statically-linked ones. This way we can also do the copying without affecting the production system in any way. After all this, we compile the kernel using the TINYBSD file and then we install the necessary libs using the dependencies' output from the binaries. We populate the /etc directory on the temp work directory and put in a few important default settings in /etc/rc.conf, like: hostname="tinybsd.freebsd.org" sendmail_enable="NONE" sshd_enable="YES" usbd_enable="NO" inetd_enable="NO" portmap_enable="NO" update_motd="NO" varsize="8192" diskless_mount="/etc/rc.d/diskless" Lastly, we create the empty image according to the specifications for the device passed in as a parameter and copy the entire temp directory to the new image. After that, the user can use dd to write the final image to the target device. Booting the system works as embedded systems do, mounting /var and /tmp as MFS filesystems. The most interesting point is the space used by default, only 19MB. As you can see, it's pretty simple. But since PicoBSD is practically unusable with the 5.x series, TinyBSD could be an interesting alternative along with NanoBSD to be put on the base system in future versions. Patrick and I have been thinking of enhancing the script and adding end-user helping tools such dialog-based menus and the likes, for more details see our TODO file. In case the FreeBSD project has any interest in our project, we can perfectly maintain TinyBSD as an embedded option for FreeBSD users. We would like that the interested parties make tests and then report bug, sends sugestions to improve the TinyBSD. Thank you for your attention Jean Milanez Melo --=-Vc74wGK27wp5eDYMr4KI Content-Type: APPLICATION/OCTET-STREAM; NAME="tinybsd.tgz" Content-ID: <20040720122920.H1332@offset.freebsdbrasil.com.br> Content-Description: Content-Disposition: ATTACHMENT; FILENAME="tinybsd.tgz" Content-Transfer-Encoding: base64 H4sIAOc5/UAAA+w6a3PbOJL5Kv2KHtm3sW9H1sOSHWfjVMmSnOgS2ypJzuzU7JRCkaCEEV9DkLKU TO63XzdAEqAfyVzVzG7dQ1U20UB3o9EvNEAmPNgthNN49if+ms1O87TbxWezddptmc/896zVbJ6e ttunzWb7WbPV6h4fP4PunylU/ktFYsUAz37xmRd+Be9b4/9Df0lm/+x5tLAEc7nHxB84RxONe9Lp PGX/0xO0eUs+WyfHrVPE7zZPO8+g+QfK8OTv/7j998AOg4QFiYDQhf3PP9xM3g1Gky+NRRgmVfon W03dbOlmWzUd5lqpl4iGF1oOi4+Qo5uPbLjNjlYc+asehWK2jzrJqgSvmBeVOmJbgf4iIxRpFIVx IimrT67A4wu2ZXY1ezY8p84890iER62XqYgbj/R/hduCB1X8a/z0kv4nTCQStK3suXI9aymyNg+z hh86qhWph1gpcmzIDsdKmGooPMdVj9C3eBBYvhpk9koxZI4kj5nCZtsolo1VKJICe809Tza8QGJ7 PFgrWInnrx2uyPyNfETWVj3VeHSnuMfM8iIrUYLGvuSVBgW32M/ZZGsRHmNqmSJJdqqxC+yv6FSQ Uulfw3J+WbM4SD4p0A59IolDT8HOyvY4MihDdWHHPMo7uVh71oLlFD4TS9V0LZGQ27wUalXSs4uR leVlI9TK+oW91q156oqXGnJd8eRY56iNSVQNc5figGdC8IBnzHnk3qnW2nNMFATJ4QsAE1NSAKj4 YqxM5jvdvFHqXgehkw/4ucx+mOZalM05Rmi+AtXhOkzYJfSHOOgDURx+C+t3oIjEMceD1PPKFKlv Rfd6Ao6rzLoCK2cQsLuiM/TCZe5YQSjqSZoBEQ8y7cR2GFMeUkCYYhQK5cpp4oR3Gb7wrCSx7FUG 3VlRmI/shJ1krpYqpT7t5pRspKtTQ3p78lI3f328O/Yf619YCYpTDNytq3pEMJkCio40+MSjtib9 RLnq6VGEilF7ZaBiagteaiCyhHhqTKyMkWUcaWgtUr0g22NWrCHfwAv9KGZCFDzTIO/SOBGm1wKI UefWQsNp0XQwFHQ7LinH0WhM97JlzKJiapegJ8bKQ8GmaLuWJzRDl5nmcnngmMCSaSW4Mto1RImz gBI911LaTctRMuqDQW4QfsLNroBWzHIMYOukhhG4U7C4W4WWz40RSsI5RBuNhXtNDnuYTjVgWtEP Yz23x32eaHN6ob0uAa4BLU0dqbA2oJJJZcIvAMy3peX7a5e7oQEmzFixL5ZaoIAlJWMEWMJoIFyl mi5c/OKGsW8ghxELhNA6oWi506qOYiyF9AJjVmKObs5UrMvEkiBUjAk7Mtpy3ytApicQprOIlRFm QqqvMIkwYlVgMaWByOMGJFb1NdstmVa80LGTWNwzAD1ZYkRVwrzAWEhiSphww4JJaAyEqRE5SZQa DIxp4tQgx6JDpw3TNdKI5tFOrQcEi7Xh09RhdugYdCkLSh0bHQobv+Qkd2YgYNSYba6nuIt5otnt mPi924aqkrKMKgFZltvuUvdglXgXmGBMlY6GMVVqiDvoi6F2tjgh2BhHmzkGGBbLzaoY3G6M8fXC ySu2oo/ygY5ZtYcz/wGan8SZt2R7us+ce+BRzGT586CXDm+GVIFjGwC7w20aBTC6lrRrG+AqDNcG jNjhOo3MnjSSNbruSe51RDaXBx7dEUUloDQlwqRIYfTcmW1njuX5QvdgCsDwM2CvbAeMT0Mtar1G R2JHjr1alzv8oogouvL0rzpiy2aqKCr6NvyhfTfclH0TZOVn0XNXnueOP+AQ2bYVmzZTHc43oiI/ 2RltqpjSoNSDecYpdSxZniLyHulG9a2bbTJ5NyXROqaGzb1+lcnKTBM5zTeiGPNwpktq4e4kiFns 21ZU/dee/+/f/4jVHz8H3f9k93/yru/+/U+n28nu/46bnc4J4h932u1/8v0P5cqv4f1vvf/5LqsU oI4+3A+jXcyXqwQO7ENoN5sd+A9mBXDFPStgn+AKdQDVvUoF6DfGmOP2GmaYL3DY83h1D5nsX2I+ v5gOqnuYvKC+3VT7t5PJ8HqG8XCu4iG2sdbBQ4BgueNVs4BRCFhX5QOLlHtO9d1wct2/ub48n42u fyTeg+Hl6Ho6603eTM9r9RCaUF/SPx+63W6tOh32Z7fXo9n5fqs6m/T67/o/vj/fb4McIPh8/7g6 unpzvt+pVrkLP0Ftf68GdS+BY/i5mqyw3gGgexeo/RCGkfgOQbgV1pK9hP0mvMK8wS3BPzHgAQhm J2EsXsMrqqsFWDYdL7HAhyQEl8f+HUb9ayAWrzLcp3B+epWtG7iPkwFlqNc/V4l0uLX8yFPzn7S7 Z23owHFbDk3SAOgChAduePDiEOobsJYWD0QCuzCNoX8J6iqOJsM0iMkqjlEQIAKqX/FMTXysBWZ9 RULsjmqkhC1PoFV1ebVqr5i9nlteMue+LL4PDuFztSL1V/+EWQ81+gXVV5H6q1RIwbXiZpkHNexT Ou15mP7w9M43zFgoBGGCykz+BtmVYqae5waP58gEZflSrcbMDzdsfhfGdKGlRMmu4aA+QV4Cz6BG Kq6quesB1CZESsxr5nDsQz12H1LUwAkDhsrASat4FqUZ1XRlESrVirxbg3pkMiEqO2ZYNMyp0lGU inGfukkOpJJ+sYMVZ7EV26vd0dER4FpldQR1h91C3YUGHihVwdTAKDiipHWElkruTfl1KoywR4go 8L5BuLEeJcRutUjMHnM0kRVzJuQy8wRQQS8Deq1A0fIRj6xIrpPCl4dvH+A3oCM2OXIN4/I3+Ae6 jo2+WXdbKF3tJfWlAf/1I6CzhIVfUQKTdm3sfyZGX2rkP4aV834gfsjfjaDoegTrb9UK2V4u5K+4 EFqmb63ZnG4rmWfa8oISFc1t45YS+pgaHKB1wQLzXMIZKJLMrDR3dE8L+5/zNPcFijyJJV2DH784 acgis2I7v2cI7YhCgsydalooMqgxS7VCZ2Sonz3K049QBaZQDcUKAx4TC553UHwjDT8u81NMjpaY LzJ1y6NM1t94kjt6APzOKfzQSdGJSsh5n2VHXP87WoeKMTwqjRamtMV0Oh0oa7/xZng9nIz66lXH PV6ltyBFoGABGT8SKbPBcHw5ej88r31UlxRQTzAdRuJjrSptXPKZRyLr27FUiqOPWfx4jkMRX/u3 6B9BTcfE69c4YS4TxgPsUTJ8ngDmPMxWYQBRHGLCXTCGeZXyt7PDVM7tWhY5UkBcqxH5ml0Ww4+H 8P5nJHsQwKpXR6+C4T5CEbmQ/VTA5ceHRmT5//7IscLYI27lqw4pidoa3I0peyklZOkds2W2DRlR SimUzsq+xcm7ZWC6mFHJRrZbNEW68HmCPdWH5BkVpd6YL1LarWEwnMqCysj6eSYih2tYTlO0LGhA 6gqIQ2hBqwavDTcnxnTruEDx0SzS0IU6aDC25Zs8ePUKhjeTPoVWNX/RpLf1XP4wXtaq+TrnLLAW HmJd31wPsRsPqUXXj8NpDc9CC8dAqlXldUOph97w+VZU6lOH8bkfJo7qwK2HirDz2ovWWbtWlS+B mBBzeSV/XsvX4TTykVq1WAsZTux8svIjuxX/bwSUhIxYmt7cTvrDuQzjj9Im+xzRrLs11C8JET4/ lzeBsN96/uUjUlCOG85+F0VbUajbHcNmoG5FAxRLUPwaQlB4GDN8eWRTyzxY1mJSGdWKVAfbYuvD 9Q2lYpJN56RMLSgLlnlX1zM95pSGcTIsZt1z6ZWfGLpi6KLXFjy/YDFKxkKJs6KdPPlqgPyyF1pQ t4jjJggdRjmqRFzfgqKkqh7BHa01q/i/yNmzupjMJWXY/3w1oClcGoH6yOzNOkt4+UUb1C+gvrj/ jlzdw0FdYITh1tCCjBGuXb6OhPodEWqOolWtyLdVUL9pQ/22NGThfNJ3y72qtEYlkzwHIHeBwu5/ +QvQmwU4wgQnXQQzfMRxvXSroynhEH77DeSNKSrFNVhW1Bus0iSGzaQQymjlakVW+wtxftJZV1WK 3JSNk5XUm9Jk2qroJ2mmLpxy78kfniljPOAkuIEuRV6APzyMmEV2uRY1S7Z7m2+RAYwcXgoGdYql MPkX39T8Ob/8/ic7V/8pc3z9+59W97grv/85aR0ft7stuv9pd0+7///9zz/j51s2hhWrVKiUrdpR iqf2zouTeX98m0HdEnSSQfJNYKVy3bu+oeuY6t4sBLqZ5jZWyzvIqnLaQ7OLhzseUy1F9TSzHLok faQ43pOPSqVWKqdrlcreQF0IQORZNu7AWBPSVT3QTq04iCMUguI8jKg+EpXB8OL2zXl9icTyaJad v1CQZAVLZ3HQOkTSRboETAGL0BPVakYKlWn/7XAw7+DKkJoeIDDd0AEi1kij6+GsguOjIGExtikr 0QcGBcLl5ZTGL1i8Zh7bwSWeA+GSKogdKsE3pru5nN2OB73ZEAn2hrLgAaQGEboJqKJHQPbVkya7 vZzOe/33NMdUjUl9WDZqQ0B22Y61t0DNlogwf7/tTd+S7D6W7xsGEYvlRVCAlsLicsH1lQQlyYL6 ajCf3NzIZV8NgAuwIArp2ptbHsiCRFlDU4wnN32lh3EcSsHcQgNwELNfU5xHwHg6vB3cXE4PDcqs i0gFS52wblC6MWZ8uQ8U+P2bq3FvNu8cI0Ef/Q+dkfQo7U0m7Bwdw0/vhsMxzN6Opt/9/IDycjIc ImLnEfrsSrOjad5RkTGkda3l+xJypwcWmv44/TB9eyUthM26SHbIUb4EcMBnfhjvyshX0zf3kH1U Gd2P/Zqy1LSEZD18wJphybwKYxNz/m58Mx39fT6ejG4mo9mPc+ndt+9H129gbxwKvoUxpt/jeesC 6JuvOr0sBbZFswriYKz5YjCXB/L37+f9wfBDZQ/y87EF1AHoCXgqxKinuNaEvbf9+WT4BkUYzlAA lOR6hsRjWa7EbIkuymL0usTlzHOEShsYmljn0gIhTOkN8BFAz8HR/2y1X6wpBTgx37D4yJxn8EfO 0251H5+HjoDztzc378g5IUK/PDg7NHwSK5YB8V1SyqOYTIXMhXU7jWP6hGKvYDUYXFR00Cer/J5I CUafP+wZGedDbzLqXc+MNEH5Vr5zQoPFFggr4AnmXyqOKBk9Qjyf3o7HNxNUzPABieTEA3k562FC j1M7SdGbvocsUh1Y7EDLYfD/YTS7Hk6nxmIyjqRAltBts4OZn77wwLSB9aq9szGcH3KYT9+NxtPx 6BqzvrxqoOIPozCg5IHJSUQ8UFxIsyJiTL5/ww1InpKtAKZX40yL30uNBqgbSO5CwLhDgDlIoadF bGn86c73Gb3RgCu6es7SFU7xThWOKrNVKlbEbUkwatxAbzzqV4shLqyizUwgsjnJeOmFUbRT/iSK QdeRH0n2Zj2pF3yOR/mupmdNLLNNxxQpBFHJM0vGdM9Aii3uFEiT3mjwGBKupkDCefuDyc3VfQkl mmuiuY+uROKJxMDDDpZj6TCd9eaYRWaj/nxEO+xUFg55pRCk/oJRsUBKsRL6sqCZ72YCFiGmYxUm u0VoxY7UGXWMp4024ElGMEMeolbSaIKMF23mJcR7eNp4wqchg38xtFlaNPThTQ82WBKFQK+vs3yh sQRWLWIlfUy2sJqI6b6MJM+awkKKYgPBhdMXhqQs3GNpcdkLEZJdhF6m0pjCElP+wqM8Q47fv8kx 9OTSuYr8wlXYEM/I3iRw8GHWbjdlwaY2vMN7c2hn2Zh56+/T4eTDcCJNLYzq4++gXpxTpFqwKSQ2 SC9xr8WT5PRmIonpEw61yy4orAFzJEad1p61jMxJBEPumJx6b8aYYeg7lERksaXepUQhZfscvQ5O KN8rYZCQCo4KvkG0JbpxeIfSYumDu6zPDMoDwRhc32BRJhdG37BBtoZDI4Iin2IXz8sixVwUOPQV V4obqKkU0jZ/0e529OyRT9tsLCXo93uTARyM+1f9UU+XEThi+za3VLZEx1qk6P8xd5YF94KdvVhI U+RoBztcinWYoWtx6WsViTjc9nswmqqUM+6PMkxhpCziJXHHfeiTXx+0Tuq4eSLXVONlM0pEwrqg 2Y/bGhHXMcV4RpMdYKF1CCS3JscSgyhROc3voXXyU6f7c7cJdNfmkCcRmSJANiOX3k0+x3p1iQa1 oOZgqqjlaKjnCFMexrUnFyRDMVlZCcZQtfAftYNJ90/tg84hLL1Uh5P83FR6AWG4mCTCO7mNYhkd yLen6joSOL0iD4MAtzW5wxE6LoW02SBBIjvjKQ5f5trPr6JpZmX3EQyREHeXBK5HfaG9w2GklMGw 36DThQeDfru17Wzh4OPHWerx6PnzQ73RyOyk8LDabmAt1wTLsSKqdd7wpYWW0PP0zcyWbGVoHWO5 C8f25OysKWfYYQmJO68xx2Zr4HXP0FT06BL2B1LqlpAfW5IyAJU/pCFSLuaFq9GIPMNIxECf2R0h A4q3l3BBDh5Lfa8ZiyTt80yJPudI+1wZBGsq+SE3YWaT4H+a+LtCdkVA8ufz3g+ehSvVfRGHloMi wkX/qtNpbqHVJGUCyxak8ZcP8Lunze32gba1Pe2yPdutVudYht7GijnuKfQ+ZW15fG3WBco6ikKy HG7lp9C5mS/gAOOme/o9hU/3xaERu4HczPCM1vNPz/pnp1tpmmxBB8jFxipInvYoVz/3AtuwdiyX N8GzwIyt4UXr+Kz/18aL1smZ/DfF/63mVGN7Zew2oR2f6Qh3pSzSIW3ojfr1k7OWdB3c92MXi0rT 0wSXpppyjz4Xk4tfxhaF7VSe/AQOTeGs2WzQ87TZOtGka1XGiXcqMGH6rn72AqOG9Czb7S38VzvX 2ps4doY/r3/F2dmVQrZACJPbVNoPBJyMNRAQJp0ZVRVjsAneMRhhM4R/3+d5j2+EkFaqWlWt3w+T TM7xubz3m/2UkOiAqFhcHt8sXQmD7VGzca4qnVrXX35XnTuzdnnZGH3JTxr7cq8g9nDOBy8mBSM1 8p947DOw2tGtYsHYyHt2IlyQXvZCOsdGc2zurbuth4KEyqF6bc0A2lhh7crN++n5dUN9+2bCA90T 1bV4JBY8PmZ2qvoHnslmbCec8dlfTkIg5vPNh/bNReMuG34OCrL+oSFK5zYMYayc5dPJSRV7tuG6 h0svEXpakX09BhUn1kMt/SmjrGmwgc+dq7ep0Li93jF4hHVYkNbuhukG1bZvPjw3uA6WToXec09U lit4oQlyRSge3IP51/Pm36ADq4K2xwAxjqirxvuq6tg376HkeLZczrznY2K2DiEv2kLKr3/KnxHR lNlMHwO9VmK09tfWmuVu84cfRxvVu725+nD1/OpM38tWTPe/OTu/wtHblw2IOIUFnAEZBkNNc1xC dPW1m+e884MJ2/uXruoKE2dk2d8rWiZcdRJRlBpiQj0dRmZP0LfKmUJO98VfU98lxM34OuGBJGTZ V/lh4MpgNPcXhcADDqFBHmQbGG4Kar844jZw5JA3jWb9/PxAZevBlr8OedaLS+iDixtcJJm+LSwM dswf24rQ3jo7oBO+5tWVJm/IqxQ2l1mf4ZMD46Ky15EfnNmSKHx9j/xqW5GffkCztIQuSKZzNdxp 77G62ExJbmXYq+mQVYIgiI7rTyX7Nw+3dFJ3rJhrlwOeTsixnBUgoG4o3oBJw8r4TGfjMqyHofBt oq2YQ11NgIecrYmHjA+J2swZzXhHrqdjYmV3rUFudVarwtBgkI/EGyHXAFthSfyPHSD5c/FORnWS L453cCB1qy05PddsC5HvnqTN4Psh6I3eZYNPvpgZa/DjSiiKXy6SnejAZfLoINBIJ9bisCbzQBFH mg4qUBZLvvYFL1902wi0+DZZzU7S6FT7fzooyzK7ycXufLa10Y2BA+OwoY8SxZmOyzdSoOl1yxtj ImgzGmAtdFxUmt0Qn+WeC/YVbk23WeltZrJNnq5OwRrcWUPzc6vbfWNo3DHvWo/d0XjUH7fabXMw emVyx0JodzjQeez1vj6YhwO3Q6tzb+YhXr6SbbbVIfxiDdg0uVn78e7IU2PTHrzxFLzv9W4Vh9Iq SPu2PTu2kBQC9hfSeX9GZm8eBFe9H7YGH4+PjK27VvuVi2fjkIL+W+N2v/0JCH0RICi+dvvK38Zz JyBXtrufxo+2ObYYU47bra51O2yNrP4DlCgUr+bOqSNVTrpOs7Xmtl3KjxKMsmldIm4qk2m8kcrN xKPqdvNk59G95CCDx7FJq5SKRTHqhfsZKRM6z25fNhucWz/gnHSBVwfsvvlpaNlHHxp/GbW6v79v Xl9B9TeOTxsM7P/N6u2/Dln9t9/p/7v2+Afff7i8aF5L///ldfP6Wvr/m83L/3T///9p/dcIVXto tkamSjoAVGIfFHuk1EfLHLaG7Y9f2WbeCaW99Z9tFmPqcil5mqcwdHX7RlWdTEP2Y9CR4ct38Gl2 cImiOZUQvN6abg5h8O/APYmpsMQ502VDVYmcnWQ9w+CH7FiVnrSoqqSDDw5RIOdx59OVqyeIE1FV Uai2rL2FG3ikUinI33nJislGhDinmGyVs4g7oPgtBOzjz5KjeM+srFKdrhFlMY6Wt/vOdPeI8mOj UOzeRNq854tX9DyXidK0518adk+J6xETtclhJ0wtLfzAkTTHCrES5+oMfJ3dLlU8GPN2W6mXzOFp ciujMEWdqcUskt4Y6SNETCaX0tWQOsLYKKzqXGVyFiwn5RK25IMcRiVc+Xz3PjrBUIAwwDslLhDf 5sf8LVwGu99AOeEF2SzrZ09IxxnGD5gmV6Wtq1KHI9HEcduj4ymzeo5kpwMvLq629qQVgIGzUWFK eCcMpiSC1nnuvKl+6wcBz5c85J7pH0R9gY+VsfdShuQIQXPQI1Qdy4aAtEeq13r4qgZDs0YWt+4f h2YnEx37qz0yezbp15NSlDr2uos0DecHrKotuUjxHvoawlVqAe2EcxtaAgoV+WT+vsDsdZtHSbYk vfrcC4TMgaFRXqznFQQhp2XC13y9ZTOd4y5bZ28me84iA+Q/RFrxVG5ykjqxYpMDtozc+Y6R8Gll E2nHQxPuAGGnfzZ+KiIt/dpMLWmieGsw7Wp6e9JBf+eL6WnAVpNXItdvjx7Z8uWswz2BnRZ15cxf g+YBOIHFy4O38zICSUvLW4hxIFZQT6m6mXhAtx+u66ovbpLgnNSiGhYt7EfRhjwb+c8x6L1+kqwU SBoahf014/16lTGW1mmR8NKrlFcV6hBOY58INIkIVZ1S1Wt9yg1PC0LW6vbv2Ulht4cWIhMgxVIz D9HkZikJYa1wpO9EjIrvek6diEvQBjVeTWZIFduLYl0ac41o5U19uTX4aifKZ+ltqcfWUaJA596S BYakJIWrZ69y6Py+vo7YJcP1ZzOPtXw41+ECzzr6jvzQC6sR+h19TSes7+Jv4ZP6gwIdbZ7ryoZu XMByqS4CwnbH0PNh4O4e72u3w5NIBRiY6vLm/eOdhb+w1zqa+B6smZQOsxtxY7IXvV9+W2NpyKES U1FXH521i2m0ukG4fNIdHqkhEQZYb1hrjKUjQh91wW7bSjLJqLGvWEVbP57OIzEMcpVpGAY/n9Y1 obbCmSQ289jE30szq2uQoVT0852EUghAGBlzV4OXc2CQmD6pvRxVFdlZtkhOB9TUlqd1HIHK8/ue IjRyjUbTg3887Yr8rFrpATTuq5mtgXvi1qS+EEFtprSsa7vsFdwZGpD0Eknei6TYE0vh0QQ3OARO BRtWFwNvxEAf258D1oGd5YsHpbmtoPNZLnHAX2RonCrT4Fqhk8eZEtrmUk0Onodh5CXsGSZqQ5jD SU5OcYOgb+qZ26EVQSrf3z2wMT9rARmM/UDfHi4EZEPag+R9wrnjikC3OnQgEW/fs7uo1++YmjXY VwTkvyDaO7BU7ce7gm6yY29Vm+xqELSVoq4EEaKkZQ/7GrCPkzAiFz+lnVGaG8mISTdg0ndThw3e Tbx9B4V977SySzWZ8ZskorwyNLiQJ96pXgaLJZRQQgkllFBCCSWUUEIJJZRQQgkllFBCCSWUUEIJ JZRQQgkllFBCCSWUUEIJJfx3w98B53/vTwB4AAA= --=-Vc74wGK27wp5eDYMr4KI-- From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 16:39: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 CCA1116A4CE; Tue, 20 Jul 2004 16:39:39 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74E6443D64; Tue, 20 Jul 2004 16:39:39 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6KGd5CL099705; Tue, 20 Jul 2004 12:39:05 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6KGd4E0099701; Tue, 20 Jul 2004 12:39:05 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 20 Jul 2004 12:39:04 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Mark Murray In-Reply-To: <200407201554.i6KFsCtW079782@grimreaper.grondar.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: jesk cc: scottl@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG cc: markm@FreeBSD.ORG Subject: Re: I/O or Threading Suffer 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, 20 Jul 2004 16:39:39 -0000 On Tue, 20 Jul 2004, Mark Murray wrote: > Robert Watson writes: > > Mark -- how much > > computation is being done here -- would it be worth dropping the Giant > > lock during that computation so that the thread can yield without > > generating a priority inversion? > > I'm sure it could. There are some Giant issues related to the UIO stuff > that bit me in the bum when I removed the NEEDS_GIANT flag from the > device, but I'm reasonably sure that with careful work this can be > untangled. UIO shouldn't require Giant. Are you sure it still does? FYI, I'm not even thinking you have to mark the whole device driver as not requiring Giant, just dropping Giant about some of the long running work (and maybe conditional on the amount of work). For a small random read, it's not worth it, but for sustained large reads of randomness, it might be interesting to see what impact it has. We could even consider a yield of some sort. Anyhow, up front, it might be sufficient to drop and reacquire giant and see what impact it has for the test scenario we're currently looking at. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 17:10: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 6EF4916A4CE for ; Tue, 20 Jul 2004 17:10:38 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABCA643D55 for ; Tue, 20 Jul 2004 17:10:35 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.0.200] ([192.168.0.200]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6KHGePR059428; Tue, 20 Jul 2004 11:16:40 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <40FD51FE.2080208@samsco.org> Date: Tue, 20 Jul 2004 11:10:22 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040702 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Maxim Maximov References: <40FC3090.9060305@freebsd.org> <40FC92C8.50604@mcsi.pp.ru> In-Reply-To: <40FC92C8.50604@mcsi.pp.ru> X-Enigmail-Version: 0.84.2.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: HEADS UP [Re: thread+preemption stability improvement] 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, 20 Jul 2004 17:10:38 -0000 Maxim Maximov wrote: > Scott Long wrote: > >> All, >> >> Initial testing of this patch looks very promising. For those that >> aren't comfortable with patching their sources by hand, note that it >> was committed to CVS a few hours ago and should be showing up on CVSup >> very shortly (rev 1.8 of sys/i386/i386/intr_machdep.c is what you want >> if you are running i386). Please go out and test this as much as >> possible so that we can determine if futher action is needed. > > > I think it is needed :( Things actually get _much_ better, now I've > been able to use my big IMAP folders, but still after applying the patch > and working about an hour mozilla freezes with the same sympthoms (cpu > fan gets spinning faster and faster as if cpu temperature is raising). > Are there any ways I can help track this down further? > Preemption is enabled, of course. My kernel's config is latest > GENERIC with these additions: > > ###### > device pf > device pflog > options ALTQ > options ALTQ_CBQ # Class Bases Queueing > options ALTQ_RED # Random Early Drop > options ALTQ_RIO # RED In/Out > options ALTQ_HFSC # Hierarchical Packet Scheduler > options ALTQ_CDNR # Traffic conditioner > options ALTQ_PRIQ # Priority Queueing > options ALTQ_NOPCC # Required for SMP build > options ALTQ_DEBUG > device radeondrm > device acpi_asus > device sound > device snd_ich > options ALT_BREAK_TO_DEBUGGER > options MSGBUF_SIZE=245760 > > My system is the notebook ASUS L5Ga. At boot I'm getting many > witness messages like these and I turned on debug.mpsafenet=1. Can this > be a problem? The problem here is that the sk driver is holding a mutex across a call to mii_phy_probe() which then winds up in bus_probe_and_attach(). The current architecure of the miibus code makes it very hard to lock drivers correctly and efficiently, but this paraticlar case shouldn't affect runtime stability. If you get others messages like this while doing network I/O then I would worry. Scott From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 17:20: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 E5E1416A4CF; Tue, 20 Jul 2004 17:20:53 +0000 (GMT) Received: from smtp3.sentex.ca (smtp3.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86E4243D6A; Tue, 20 Jul 2004 17:20:53 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smtp3.sentex.ca (8.12.11/8.12.11) with ESMTP id i6KHKn7M092086; Tue, 20 Jul 2004 13:20:49 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.12.11/8.12.11) with ESMTP id i6KHKqGX006009; Tue, 20 Jul 2004 13:20:52 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 8E2077303F; Tue, 20 Jul 2004 13:20:52 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040720172052.8E2077303F@freebsd-current.sentex.ca> Date: Tue, 20 Jul 2004 13:20:52 -0400 (EDT) Subject: [current tinderbox] failure on sparc64/sparc64 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: Tue, 20 Jul 2004 17:20:54 -0000 TB --- 2004-07-20 16:49:58 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-07-20 16:49:58 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2004-07-20 16:49:58 - cleaning the sandbox TB --- 2004-07-20 16:51:12 - checking out the source tree TB --- 2004-07-20 16:51:12 - cd /home/tinderbox/sandbox/CURRENT/sparc64/sparc64 TB --- 2004-07-20 16:51:12 - /usr/bin/cvs -f -R -Q -d/home/ncvs checkout -P -A src TB --- 2004-07-20 16:58:38 - patching the sources TB --- 2004-07-20 16:58:38 - cd /home/tinderbox/sandbox/CURRENT/sparc64/sparc64/src TB --- 2004-07-20 16:58:38 - /usr/bin/patch -f -s -i/home/tinderbox/sandbox/sparc64.diff TB --- 2004-07-20 16:58:38 - building world (CFLAGS=-O -pipe) TB --- 2004-07-20 16:58:38 - cd /home/tinderbox/sandbox/CURRENT/sparc64/sparc64/src TB --- 2004-07-20 16:58:38 - /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 [...] echo nslookup: /home/tinderbox/sandbox/CURRENT/sparc64/sparc64/obj/sparc64/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libc.a /tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/tinderbox/CURRENT/sparc64/sparc64/src/usr.sbin/nslookup/../../lib/libbind/libbind.a /home/tinderbox/sandbox/CURRENT/sparc64/sparc64/obj/sparc64/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libl.a /home/tinderbox/sandbox/CURRENT/sparc64/sparc64/obj/sparc64/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libedit.a /home/tinderbox/sandbox/CURRENT/sparc64/sparc64/obj/sparc64/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libtermcap.a >> .depend ===> usr.sbin/nsupdate rm -f .depend mkdep -f .depend -a -I/tinderbox/CURRENT/sparc64/sparc64/src/usr.sbin/nsupdate/../../contrib/bind/port/freebsd/include -I/tinderbox/CURRENT/sparc64/sparc64/src/usr.sbin/nsupdate/../../contrib/bind/bin/named -I/tinderbox/CURRENT/sparc64/sparc64/src/usr.sbin/nsupdate/../../contrib/bind/include -I. /tinderbox/CURRENT/sparc64/sparc64/src/usr.sbin/nsupdate/../../contrib/bind/bin/nsupdate/nsupdate.c echo nsupdate: /home/tinderbox/sandbox/CURRENT/sparc64/sparc64/obj/sparc64/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libc.a /tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/tinderbox/CURRENT/sparc64/sparc64/src/usr.sbin/nsupdate/../../lib/libbind/libbind.a >> .depend ===> usr.sbin/ntp ===> usr.sbin/ntp/libntp make: don't know how to make authencrypt.c. Stop *** Error code 2 Stop in /tinderbox/CURRENT/sparc64/sparc64/src/usr.sbin/ntp. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src/usr.sbin. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. TB --- 2004-07-20 17:20:52 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-07-20 17:20:52 - ERROR: failed to build world TB --- 2004-07-20 17:20:52 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 17:28: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 37EFC16A4CE for ; Tue, 20 Jul 2004 17:28:30 +0000 (GMT) Received: from pimout2-ext.prodigy.net (pimout2-ext.prodigy.net [207.115.63.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EEA843D66 for ; Tue, 20 Jul 2004 17:28:29 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (adsl-68-121-219-69.dsl.snfc21.pacbell.net [68.121.219.69])i6KHSLUK239090; Tue, 20 Jul 2004 13:28:23 -0400 Message-ID: <40FD5634.5040000@elischer.org> Date: Tue, 20 Jul 2004 10:28:20 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030524 X-Accept-Language: en, hu MIME-Version: 1.0 To: Peter Jeremy References: <40F963D8.6010201@freebsd.org> <20040719060730.GA87697@nagual.pp.ru> <40FC9FC2.8050400@kientzle.com> <20040720081051.GB3001@cirb503493.alcatel.com.au> In-Reply-To: <20040720081051.GB3001@cirb503493.alcatel.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org cc: Andrey Chernov Subject: Re: NEW TAR 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, 20 Jul 2004 17:28:30 -0000 Peter Jeremy wrote: >On Mon, 2004-Jul-19 21:29:54 -0700, Tim Kientzle wrote: > > >>I have some ideas about sparse file handling, >>but they're not gtar-compatible. (The gtar >>approach has a number of drawbacks. The primary >>one being that on many systems it requires reading >>the entire file twice, once to find holes and again >>to actually archive the file. >> >> > >Actually, it's not possible to accurately determine the holes in a >file by reading it - you can't differentiate between a hole and a >allocated block of zeroes. What you need is a (new) syscall that >invokes a new VOP_... and returns a bitmap of allocated blocks. This >would be non-trival unfortunately. > OR, given the right flags, note all blocks of zeros as if they were unallocated, and write them that way.. regardless of how it was in the original file. > > > From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 17:39: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 4276316A4CE for ; Tue, 20 Jul 2004 17:39:46 +0000 (GMT) Received: from melusine.cuivre.fr.eu.org (melusine.cuivre.fr.eu.org [82.225.155.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 082B843D69 for ; Tue, 20 Jul 2004 17:39:46 +0000 (GMT) (envelope-from thomas@FreeBSD.ORG) Received: by melusine.cuivre.fr.eu.org (Postfix, from userid 1000) id C7DCC2C3D3; Tue, 20 Jul 2004 19:39:44 +0200 (CEST) Date: Tue, 20 Jul 2004 19:39:44 +0200 From: Thomas Quinot To: "Oliver B. Fischer" Message-ID: <20040720173944.GA4122@melusine.cuivre.fr.eu.org> References: <40DFDC44.6090101@snafu.de> <20040719210311.GA72395@melusine.cuivre.fr.eu.org> <40FCF591.601@snafu.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40FCF591.601@snafu.de> X-message-flag: WARNING! Using Outlook can damage your computer. User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: Obtaining a kernel dump is not 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: Tue, 20 Jul 2004 17:39:46 -0000 * Oliver B. Fischer, 2004-07-20 : > How can I get it and save it too? First you need to configure your kernel with DDB, see: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-online-ddb.html and use the 'trace' command to obtain a backtrace once you get a panic. I think the easiest way to save the trace is to obtain it from a serial console, and save a transcript of the session on the terminal side. Thomas. -- Thomas.Quinot@Cuivre.FR.EU.ORG From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 18:00: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 8F4FE16A4CE for ; Tue, 20 Jul 2004 18:00:59 +0000 (GMT) Received: from moghedien.mukappabeta.net (moghedien.mukappabeta.net [194.145.150.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4159F43D31 for ; Tue, 20 Jul 2004 18:00:59 +0000 (GMT) (envelope-from mkb@moghedien.mukappabeta.net) Received: by moghedien.mukappabeta.net (Postfix, from userid 1000) id 7A7C92D87; Tue, 20 Jul 2004 19:57:40 +0200 (CEST) From: Matthias Buelow MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16637.23827.578767.763759@moghedien.mukappabeta.net> Date: Tue, 20 Jul 2004 19:57:39 +0200 To: Peter Jeremy In-Reply-To: <20040720081051.GB3001@cirb503493.alcatel.com.au> References: <40F963D8.6010201@freebsd.org> <20040719060730.GA87697@nagual.pp.ru> <40FC9FC2.8050400@kientzle.com> <20040720081051.GB3001@cirb503493.alcatel.com.au> X-Mailer: VM 7.18 under Emacs 21.3.1 cc: current@freebsd.org Subject: Re: NEW TAR 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, 20 Jul 2004 18:00:59 -0000 Peter Jeremy writes: >Actually, it's not possible to accurately determine the holes in a >file by reading it - you can't differentiate between a hole and a >allocated block of zeroes. What you need is a (new) syscall that but that's the point, isn't it. if you get a larger block of zeroes, you seek forward that number in the output file, and let the filesystem create (any) holes. >invokes a new VOP_... and returns a bitmap of allocated blocks. This >would be non-trival unfortunately. this is completely unnecessary and wouldn't work across filesystems anyways. -- Matthias Buelow; mkb@{mukappabeta,informatik.uni-wuerzburg}.de From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 18:59: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 DD60616A4CE; Tue, 20 Jul 2004 18:59:12 +0000 (GMT) Received: from smart.eusc.inter.net (smart.eusc.inter.net [213.73.101.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id A329643D48; Tue, 20 Jul 2004 18:59:12 +0000 (GMT) (envelope-from plexus@snafu.de) Received: from pd9e7b330.dip.t-dialin.net ([217.231.179.48] helo=[192.168.1.16]) by smart.eusc.inter.net with asmtp (Exim 3.36 #4) id 1BmzpX-0000DT-00; Tue, 20 Jul 2004 20:59:11 +0200 Message-ID: <40FD6B84.7050702@snafu.de> Date: Tue, 20 Jul 2004 20:59:16 +0200 From: "Oliver B. Fischer" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040707 X-Accept-Language: de-de, en-us, en MIME-Version: 1.0 To: Thomas Quinot References: <40DFDC44.6090101@snafu.de> <20040719210311.GA72395@melusine.cuivre.fr.eu.org> <40FCF591.601@snafu.de> <20040720173944.GA4122@melusine.cuivre.fr.eu.org> In-Reply-To: <20040720173944.GA4122@melusine.cuivre.fr.eu.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: Obtaining a kernel dump is not 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: Tue, 20 Jul 2004 18:59:13 -0000 Thomas Quinot wrote: > I think the easiest way to save the trace is to obtain it from a serial > console, and save a transcript of the session on the terminal side. Well, unfortunately my thinkpas doesn't have an serial port... :( Regards, Oliver Fischer From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 19:10: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 35E1C16A4CE; Tue, 20 Jul 2004 19:10:00 +0000 (GMT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25EB943D31; Tue, 20 Jul 2004 19:10:00 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Tue, 20 Jul 2004 12:09:59 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 0744F5D08; Tue, 20 Jul 2004 12:09:59 -0700 (PDT) To: Scott Long In-reply-to: Your message of "Mon, 19 Jul 2004 14:35:28 MDT." <40FC3090.9060305@freebsd.org> Date: Tue, 20 Jul 2004 12:09:58 -0700 From: "Kevin Oberman" Message-Id: <20040720190959.0744F5D08@ptavv.es.net> cc: freebsd-current@freebsd.org Subject: Re: HEADS UP [Re: thread+preemption stability improvement] 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, 20 Jul 2004 19:10:00 -0000 I just rebuilt my kernel and the problem is back. :-( I sure hope peter or Scott can figure this out soon. The kernel has now changed enough that backing off the 4 files I was backing off is no longer adequate, so I am again running with preemption turned off. System is P4-M 1.8 GHz UP with SCHED_ULE. It reliably dies on a buildworld. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 19:14: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 A9ED016A4CE; Tue, 20 Jul 2004 19:14:03 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CE8643D54; Tue, 20 Jul 2004 19:14:03 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.0.200] ([192.168.0.200]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6KJK6uV059834; Tue, 20 Jul 2004 13:20:06 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <40FD6EEC.3030900@samsco.org> Date: Tue, 20 Jul 2004 13:13:48 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040702 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kevin Oberman References: <20040720190959.0744F5D08@ptavv.es.net> In-Reply-To: <20040720190959.0744F5D08@ptavv.es.net> X-Enigmail-Version: 0.84.2.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: Scott Long Subject: Re: HEADS UP [Re: thread+preemption stability improvement] 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, 20 Jul 2004 19:14:03 -0000 Kevin Oberman wrote: > I just rebuilt my kernel and the problem is back. :-( > > I sure hope peter or Scott can figure this out soon. The kernel has now > changed enough that backing off the 4 files I was backing off is no > longer adequate, so I am again running with preemption turned off. > > System is P4-M 1.8 GHz UP with SCHED_ULE. It reliably dies on a > buildworld. Does it work better if you remove the PREEMPTION define in /sys/i386/include/param.h? Scott From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 19:55: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 D628216A4CE for ; Tue, 20 Jul 2004 19:55:52 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 825A243D5E for ; Tue, 20 Jul 2004 19:55:52 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6KJtIrL008377 for ; Tue, 20 Jul 2004 15:55:18 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6KJtIoM008374 for ; Tue, 20 Jul 2004 15:55:18 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 20 Jul 2004 15:55:17 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Anyone else noticed: bgfsck doesn't bgfsck non-root 'a' partitions? 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, 20 Jul 2004 19:55:52 -0000 fsck has logic to force a full preening fsck of '/', permitting background file system fsck only for non-root file systems. For the past few weeks, I've been wondering why it takes *so* *long* to fsck the root file system of one of my boxes at work, only to find out that the reason is that it's running a non-background fsck on /dev/da1s1a, which is an 'a' partition, but not the root file system (/dev/da0s1a). It successfully uses bgfsck on /var and /usr, but not /local0. So it sounds like the logic in fsck is simply guessing that any 'a' partition needs a foreground fsck. This might be a problem if you wanted to background fsck a multi-terabyte /bigpartition for exactly the reason bgfsck was introduced. :-) Has anyone else run into this, or perhaps want to fix it? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 19:56: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 1849716A504; Tue, 20 Jul 2004 19:56:44 +0000 (GMT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05CC843D55; Tue, 20 Jul 2004 19:56:44 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Tue, 20 Jul 2004 12:56:43 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 89CA85D08; Tue, 20 Jul 2004 12:56:43 -0700 (PDT) To: Scott Long In-reply-to: Your message of "Tue, 20 Jul 2004 13:13:48 MDT." <40FD6EEC.3030900@samsco.org> Date: Tue, 20 Jul 2004 12:56:43 -0700 From: "Kevin Oberman" Message-Id: <20040720195643.89CA85D08@ptavv.es.net> cc: freebsd-current@freebsd.org cc: Scott Long Subject: Re: HEADS UP [Re: thread+preemption stability improvement] 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, 20 Jul 2004 19:56:44 -0000 > Date: Tue, 20 Jul 2004 13:13:48 -0600 > From: Scott Long > > Kevin Oberman wrote: > > I just rebuilt my kernel and the problem is back. :-( > > > > I sure hope peter or Scott can figure this out soon. The kernel has now > > changed enough that backing off the 4 files I was backing off is no > > longer adequate, so I am again running with preemption turned off. > > > > System is P4-M 1.8 GHz UP with SCHED_ULE. It reliably dies on a > > buildworld. > > Does it work better if you remove the PREEMPTION define in > /sys/i386/include/param.h? Scott, That's how I built my current kernel and it's at least fairly painful It does not freeze any longer, but the interactivity is poor. I'm not sure if it's as bad as last time I tried, but my editor freezes for seconds at a time and then catches up once something gets scheduled. (I think it's the X server and not the editor that is the issue.) It's better than the freezes, but it's pretty painful. I can provide configs, logs (nothing there, though) or any other information. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 20:24: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 6801416A4CE for ; Tue, 20 Jul 2004 20:24:13 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AEF143D4C for ; Tue, 20 Jul 2004 20:24:12 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6KKOBsD025628 for ; Tue, 20 Jul 2004 22:24:11 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <021001c46e97$84c05210$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: Date: Tue, 20 Jul 2004 22:24:11 +0200 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: Erros in: make -j 16 buildword 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, 20 Jul 2004 20:24:13 -0000 Hi, One way or another it seems that I can no longer buildworld with -j16. -j8 works perfectly, but -j16 fails consistently at: ===> gnu/usr.bin/texinfo/doc ln -fs /home2/src/gnu/usr.bin/texinfo/doc/../../../../contrib/texinfo/doc/texinf o.txi texinfo.texi makeinfo --no-split -I /home2/src/gnu/usr.bin/texinfo/doc -I /home2/src/gnu/usr. bin/texinfo/doc/../../../../contrib/texinfo/doc texinfo.texi -o texinfo.info makeinfo --no-split -I /home2/src/gnu/usr.bin/texinfo/doc -I /home2/src/gnu/usr. bin/texinfo/doc/../../../../contrib/texinfo/doc /home2/src/gnu/usr.bin/texinfo/d oc/../../../../contrib/texinfo/doc/info.texi -o info.info makeinfo --no-split -I /home2/src/gnu/usr.bin/texinfo/doc -I /home2/src/gnu/usr. bin/texinfo/doc/../../../../contrib/texinfo/doc /home2/src/gnu/usr.bin/texinfo/d oc/../../../../contrib/texinfo/doc/info-stnd.texi -o info-stnd.info gzip -cn info.info > info.info.gz gzip -cn info-stnd.info > info-stnd.info.gz gzip -cn texinfo.info > texinfo.info.gz 1 error *** Error code 2 1 error *** Error code 2 1 error I have not tried any values in between, but there was I time I could build at -j32 and get loads of around 25 in some parts. Given the sparseness of info here, I'm at a loss where to go and look. Since it could stem from any of up to 16 make threads some more error infor is needed. Unless anybody has suggestions of which programs generate these tearse messages??? Or a way to get make to be more informative??? --WjW From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 20:25: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 D712916A4CE for ; Tue, 20 Jul 2004 20:25:39 +0000 (GMT) Received: from mail.corrupt.co.nz (222-152-17-24.jetstream.xtra.co.nz [222.152.17.24]) by mx1.FreeBSD.org (Postfix) with SMTP id ADAE843D48 for ; Tue, 20 Jul 2004 20:25:38 +0000 (GMT) (envelope-from drew@corrupt.co.nz) Received: (qmail 86894 invoked by uid 1011); 20 Jul 2004 20:25:45 -0000 Received: from drew@corrupt.co.nz by tweety.lan.corrupt.co.nz by uid 1009 with qmail-scanner-1.22 Clear:RC:0(10.10.69.146):SA:0(0.0/3.8):. Processed in 5.576494 secs); 20 Jul 2004 20:25:45 -0000 X-Spam-Status: No, hits=0.0 required=3.8 Received: from unknown (HELO ?10.10.69.146?) (drew@corrupt.co.nz@10.10.69.146) by mail.corrupt.co.nz with SMTP; 20 Jul 2004 20:25:39 -0000 Message-ID: <40FD7F68.8030601@corrupt.co.nz> Date: Wed, 21 Jul 2004 08:24:08 +1200 From: Drew Broadley User-Agent: Mozilla Thunderbird 0.7.1 (X11/20040714) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kevin Oberman References: <20040720195643.89CA85D08@ptavv.es.net> In-Reply-To: <20040720195643.89CA85D08@ptavv.es.net> X-Enigmail-Version: 0.84.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: Scott Long Subject: Re: HEADS UP [Re: thread+preemption stability improvement] 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, 20 Jul 2004 20:25:40 -0000 Kevin Oberman wrote: >>Date: Tue, 20 Jul 2004 13:13:48 -0600 >>From: Scott Long >> >>Kevin Oberman wrote: >> >> >>>I just rebuilt my kernel and the problem is back. :-( >>> >>>I sure hope peter or Scott can figure this out soon. The kernel has now >>>changed enough that backing off the 4 files I was backing off is no >>>longer adequate, so I am again running with preemption turned off. >>> >>>System is P4-M 1.8 GHz UP with SCHED_ULE. It reliably dies on a >>>buildworld. >>> >>> >>Does it work better if you remove the PREEMPTION define in >>/sys/i386/include/param.h? >> >> > >Scott, > >That's how I built my current kernel and it's at least fairly painful It >does not freeze any longer, but the interactivity is poor. I'm not sure >if it's as bad as last time I tried, but my editor freezes for seconds >at a time and then catches up once something gets scheduled. (I think >it's the X server and not the editor that is the issue.) > >It's better than the freezes, but it's pretty painful. > >I can provide configs, logs (nothing there, though) or any other >information. > > Change the HZ to 2000 in the kernel. This will help handle the backlog introduced by removing PREEMPTION From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 20:48: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 AD15116A4CE for ; Tue, 20 Jul 2004 20:48:27 +0000 (GMT) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77CD043D5D for ; Tue, 20 Jul 2004 20:48:27 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from speck.techno.pagans (c-24-21-241-225.client.comcast.net [24.21.241.225]) by mail.bitfreak.org (Postfix) with ESMTP id B1B3B2A477; Tue, 20 Jul 2004 13:48:26 -0700 (PDT) Received: from spud (spud.techno.pagans [172.21.42.19]) by speck.techno.pagans (Postfix) with ESMTP id 863DFA968; Tue, 20 Jul 2004 13:46:31 -0700 (PDT) From: "Darren Pilgrim" To: "'Matt White'" , Date: Tue, 20 Jul 2004 13:48:10 -0700 Message-ID: <000401c46e9a$e14dd590$132a15ac@spud> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 In-Reply-To: <2EDF6D54F4853447EB6F9018@[192.168.1.3]> Importance: Normal Subject: RE: fetch hangs, part 2 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, 20 Jul 2004 20:48:27 -0000 I've been having the same (or a similar problem). Fetching the distfile = for a port will hang. I poked some more at this and found that all the = sites fetch is hanging on successfully negotiate the TCP connection then go = dead without closing the connection. My workaround has been to edit the = Makefile and remove the offending site from MASTER_SITES or manually fetch from ftp.freebsd.org. > From: Matt White >=20 > Thanks, but it looks like those are the default settings, so I'm = guessing=20 > setting that's not going to help me. It's probably better to figure = out=20 > what's wrong here anyway so we can use whatever settings we want. If = I=20 > don't hear anything more, I'll try to get a ktrace tonight. >=20 >=20 > -Matt >=20 > --On Sunday, July 18, 2004 1:48 PM -0500 "Conrad J. Sabatier"=20 > wrote: >=20 > > > > On 18-Jul-2004 Matt White wrote: > >> I looked in the archives and saw that a couple of others also had > >> this > >> problem. Fetch is getting distributions for ports and it'll just > >> hang. > >> Killing the build and restarting it will usually cause it to = advance. > >> Did > >> any of you guys who saw this problem before come up with a = solution? > > > > I found that changing my buffer size settings made all the = difference. > > I had been using the following in /etc/sysctl.conf: > > > > net.inet.tcp.recvspace=3D131072 > > net.inet.tcp.sendspace=3D65536 > > > > Changing them to: > > > > net.inet.tcp.recvspace=3D65536 > > net.inet.tcp.sendspace=3D32768 > > > > Solved the problem. From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 21: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 2D43716A4CE for ; Tue, 20 Jul 2004 21:14:09 +0000 (GMT) Received: from schlepper.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4551A43D45 for ; Tue, 20 Jul 2004 21:14:07 +0000 (GMT) (envelope-from stb@lassitu.de) Received: from [IPv6:::1] (schlepper [212.12.50.230]) by schlepper.zs64.net (8.12.11/8.11.1) with ESMTP id i6KLE083067499; Tue, 20 Jul 2004 23:14:01 +0200 (CEST) (envelope-from stb@lassitu.de) In-Reply-To: <20040720081051.GB3001@cirb503493.alcatel.com.au> References: <40F963D8.6010201@freebsd.org> <20040719060730.GA87697@nagual.pp.ru> <40FC9FC2.8050400@kientzle.com> <20040720081051.GB3001@cirb503493.alcatel.com.au> Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Stefan Bethke Date: Tue, 20 Jul 2004 23:14:00 +0200 To: Peter Jeremy X-Mailer: Apple Mail (2.618) cc: current@freebsd.org Subject: Re: NEW TAR 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, 20 Jul 2004 21:14:09 -0000 Am 20.07.2004 um 10:10 schrieb Peter Jeremy: > Actually, it's not possible to accurately determine the holes in a > file by reading it - you can't differentiate between a hole and a > allocated block of zeroes. What you need is a (new) syscall that > invokes a new VOP_... and returns a bitmap of allocated blocks. This > would be non-trival unfortunately. This one point that has been made a number of times in the past, and one I don't understand: There are no sparse files as far as the userland is concerned; it's an optimization that remains invisible, apart from space and/or performance savings. For the extraction process, it should be sufficient to seek over any extended range of zeros. When packaging files that might have holes in them, it'll certainly be nice if there was a way to skip reading all those zeros in, but that's just an optimization. The way you describe it (and others have before), it sounds like the holes were an attribute of the file that should be preserved by tar (or any other archiver); I believe it's not. Preserving them in the way your post can be read is problematic: what if the block/allocation/cluster/fragment size of the extraction target differs from the source? How far would you need to acertain compatible allocation semantics between both filesystems? Since this has come up multiple times in the past, I feel I'm missing some important detail, and I'd appreciate if someone would enlighten me. Stefan -- Stefan Bethke Fon +49 170 346 0140 From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 22:02: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 7AE2816A4CE; Tue, 20 Jul 2004 22:02:06 +0000 (GMT) Received: from tara.freenix.org (keltia.freenix.org [82.224.56.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01F8E43D2D; Tue, 20 Jul 2004 22:02:06 +0000 (GMT) (envelope-from roberto@keltia.freenix.fr) Received: by tara.freenix.org (Postfix/TLS, from userid 101) id 45B742E1B; Wed, 21 Jul 2004 00:02:05 +0200 (CEST) Date: Wed, 21 Jul 2004 00:02:05 +0200 From: Ollivier Robert To: current@freebsd.org, sparc64@freebsd.org Message-ID: <20040720220205.GA72249@tara.freenix.org> Mail-Followup-To: current@freebsd.org, sparc64@freebsd.org References: <20040720172052.8E2077303F@freebsd-current.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040720172052.8E2077303F@freebsd-current.sentex.ca> X-Operating-System: MacOS X / PowerBook G4 - FreeBSD 5.0 / 2x PIII/800 SMP User-Agent: Mutt/1.5.6i Subject: Re: [current tinderbox] failure on sparc64/sparc64 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, 20 Jul 2004 22:02:06 -0000 According to FreeBSD Tinderbox: > ===> usr.sbin/ntp > ===> usr.sbin/ntp/libntp > make: don't know how to make authencrypt.c. Stop > *** Error code 2 > > Stop in /tinderbox/CURRENT/sparc64/sparc64/src/usr.sbin/ntp. > *** Error code 1 I can't reproduce on panther.freebsd.org :( Has anyone an idea of what's going on? authencrypt.c doesn't even exist on 4.2.0. Stale .depend? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr Darwin snuadh.freenix.org Kernel Version 7.4.0: Wed May 12 16:58:24 PDT 2004 From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 22:20: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 F0FC716A4CE for ; Tue, 20 Jul 2004 22:20:13 +0000 (GMT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5225343D5D for ; Tue, 20 Jul 2004 22:20:13 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1Bn2y3-0005I9-00 for ; Wed, 21 Jul 2004 00:20:11 +0200 Received: from anyanka.rfc1149.net ([81.56.47.149]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 21 Jul 2004 00:20:11 +0200 Received: from sam by anyanka.rfc1149.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 21 Jul 2004 00:20:11 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Samuel Tardieu Date: 21 Jul 2004 00:18:50 +0200 Organization: Avian Carrier & Friends Lines: 16 Message-ID: <87fz7m1fw5.fsf@beeblebrox.rfc1149.net> References: <40F46007.2010304@truffula.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: anyanka.rfc1149.net User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 X-Leafnode-NNTP-Posting-Host: 81.56.171.13 Sender: news Subject: Re: Hang on boot - "ATAPI_RESET no interrupt" with DVD+RW 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, 20 Jul 2004 22:20:14 -0000 >>>>> "Brian" == Brian Rogers writes: Brian> Since last night and continuing today, the kernel from -CURRENT Brian> usually hangs during boot. Safe mode worked once, but the Brian> second time it didn't work. I now got in through single-user Brian> mode, so it appears to just work every once in a while, Brian> randomly. Same from me with a kernel/world from Thu Jul 15 20:37:42 CEST 2004. With or without CD in the reader/writer. I have to remove the device (I cannot test at another place on the bus at this is in a laptop) to make the laptop boot. It was working fine with 5.2.1. Sam -- Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/sam From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 22:55: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 E2E3316A4CE for ; Tue, 20 Jul 2004 22:55:29 +0000 (GMT) Received: from mta10-svc.ntlworld.com (mta10-svc.ntlworld.com [62.253.162.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E81E43D45 for ; Tue, 20 Jul 2004 22:55:29 +0000 (GMT) (envelope-from ben@spooty.net) Received: from m91-mp1.cvx3-b.pop.dial.ntli.net ([80.1.84.91]) by mta10-svc.ntlworld.comESMTP <20040720225418.IVTC1220.mta10-svc.ntlworld.com@m91-mp1.cvx3-b.pop.dial.ntli.net> for ; Tue, 20 Jul 2004 23:54:18 +0100 From: Ben Paley To: "freebsd -current@" Date: Tue, 20 Jul 2004 23:55:41 +0100 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: <200407202355.41867.ben@spooty.net> Subject: vmnet.ko missing - but it's there! - vmware and crashes 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, 20 Jul 2004 22:55:30 -0000 Hello, I'm getting a total crash every time I try to run vmware. This is my system: bash-2.05b$ uname -a FreeBSD potato.hogsedge.net 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Tue Jun 22 07:07:08 BST 2004 root@potato.hogsedge.net:/usr/obj/usr/src/sys/POTATO i386 bash-2.05b$ pkg_info | grep vmware vmware3-3.2.1.2242_7,1 A virtual machine emulator - a full PC in a window For a while I was getting some sort of network error: vmware would start as long as all the network stuff was disabled, but if I tried to have a host-only connection (I haven't even bothered trying a bridged connection) it wouldn't run (that is, vmware itself would run fine, but the virtual machine wouldn't boot, and I'd get an error message about networking - sorry I didn't make a note of it). So I did portupgrade -fR vmware3 and after a lot of waiting around I tried again: now I get a complete crash (can't even change to another terminal and kill x) whenever I try to start vmware. On boot, I get this message: kldload: can't load /usr/local/lib/vmware/modules/vmnet.ko: No such file or directory in amongst all the other system stuff, but I also get this: -bash-2.05b# locate vmnet.ko /usr/local/lib/vmware/modules/vmnet.ko even after updating the locate database. Any ideas what's going wrong? Thanks a lot, Ben From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 23:01: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 C6FCC16A50C for ; Tue, 20 Jul 2004 23:01:00 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C09143D5E for ; Tue, 20 Jul 2004 23:00:46 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.0.12] (g4.samsco.home [192.168.0.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6KN6qEA060490; Tue, 20 Jul 2004 17:06:53 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40FDA3D9.7070806@freebsd.org> Date: Tue, 20 Jul 2004 16:59:37 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ben Paley References: <200407202355.41867.ben@spooty.net> In-Reply-To: <200407202355.41867.ben@spooty.net> 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@" Subject: Re: vmnet.ko missing - but it's there! - vmware and crashes 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, 20 Jul 2004 23:01:02 -0000 Ben Paley wrote: > Hello, > > I'm getting a total crash every time I try to run vmware. This is my system: > > bash-2.05b$ uname -a > FreeBSD potato.hogsedge.net 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Tue Jun 22 > 07:07:08 BST 2004 root@potato.hogsedge.net:/usr/obj/usr/src/sys/POTATO > i386 > bash-2.05b$ pkg_info | grep vmware > vmware3-3.2.1.2242_7,1 A virtual machine emulator - a full PC in a window > > For a while I was getting some sort of network error: vmware would start as > long as all the network stuff was disabled, but if I tried to have a > host-only connection (I haven't even bothered trying a bridged connection) it > wouldn't run (that is, vmware itself would run fine, but the virtual machine > wouldn't boot, and I'd get an error message about networking - sorry I didn't > make a note of it). > > So I did > > portupgrade -fR vmware3 > > and after a lot of waiting around I tried again: now I get a complete crash > (can't even change to another terminal and kill x) whenever I try to start > vmware. > > On boot, I get this message: > > kldload: can't load /usr/local/lib/vmware/modules/vmnet.ko: No such file or > directory This message is misleading. It likely means that the vmnet.ko binary failed to link successfully into the kernel due to missing symbols. Look on the system console when this happens and see what it says. > > in amongst all the other system stuff, but I also get this: > > -bash-2.05b# locate vmnet.ko > /usr/local/lib/vmware/modules/vmnet.ko > > even after updating the locate database. > > Any ideas what's going wrong? Recompile the vmnet.ko binary from source and see if that helps. Scott From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 23:02: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 CA7E616A4CE for ; Tue, 20 Jul 2004 23:02:47 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id AA6B143D5A for ; Tue, 20 Jul 2004 23:02:46 +0000 (GMT) (envelope-from andreas.kohn@gmx.net) Received: (qmail 13273 invoked by uid 65534); 20 Jul 2004 23:02:44 -0000 Received: from unknown (EHLO [212.204.44.203]) (212.204.44.203) by mail.gmx.net (mp025) with SMTP; 21 Jul 2004 01:02:44 +0200 X-Authenticated: #2431876 From: Andreas Kohn To: freebsd-current@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-iSVkRj+DmW3D7fTzvac1" Message-Id: <1090364563.728.3.camel@klamath.syndrom23.de> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 21 Jul 2004 01:02:43 +0200 Subject: FAILURE - ATAPI_RESET no interrupt in newer current 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, 20 Jul 2004 23:02:47 -0000 --=-iSVkRj+DmW3D7fTzvac1 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi, today I updated my -CURRENT from ~July 5 to July 20 sources. After reboot with the new kernel, I saw this: ata1-master: FAILURE - ATAPI_RESET no interrupt acd0: CDRW at ata1-master WDMA2 With the old kernel, die FAILURE message was not there, but the acd0 was running in WDMA2 mode as well. This is a=20 atapci0: port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0 controller. Is this message to be expected, or should I worry about anything? Regards, Andreas Kohn --=-iSVkRj+DmW3D7fTzvac1 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA/aSTYucd7Ow1ygwRAqgIAJ0Z90z5TVEMZwn0G9Dlu/7RCbwTTQCcDwbY atIWInVDVT3frW8ZuDmorVk= =6lWM -----END PGP SIGNATURE----- --=-iSVkRj+DmW3D7fTzvac1-- From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 23:19: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 E6BDD16A4CE for ; Tue, 20 Jul 2004 23:19:05 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8891343D1F for ; Tue, 20 Jul 2004 23:19:05 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6KNIRDW011842; Tue, 20 Jul 2004 19:18:27 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6KNIQiD011839; Tue, 20 Jul 2004 19:18:26 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 20 Jul 2004 19:18:26 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Darren Pilgrim In-Reply-To: <000401c46e9a$e14dd590$132a15ac@spud> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: 'Matt White' cc: freebsd-current@freebsd.org Subject: RE: fetch hangs, part 2 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, 20 Jul 2004 23:19:06 -0000 On Tue, 20 Jul 2004, Darren Pilgrim wrote: > I've been having the same (or a similar problem). Fetching the distfile > for a port will hang. I poked some more at this and found that all the > sites fetch is hanging on successfully negotiate the TCP connection then > go dead without closing the connection. My workaround has been to edit > the Makefile and remove the offending site from MASTER_SITES or manually > fetch from ftp.freebsd.org. Could you try disabling TCP SACK and see if things "get better"? It's one of the things that has changed in the TCP code recently. This could well be a user space fetch issue, but it would be worth trying it to see, if only to rule it out. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research > > > From: Matt White > > > > Thanks, but it looks like those are the default settings, so I'm guessing > > setting that's not going to help me. It's probably better to figure out > > what's wrong here anyway so we can use whatever settings we want. If I > > don't hear anything more, I'll try to get a ktrace tonight. > > > > > > -Matt > > > > --On Sunday, July 18, 2004 1:48 PM -0500 "Conrad J. Sabatier" > > wrote: > > > > > > > > On 18-Jul-2004 Matt White wrote: > > >> I looked in the archives and saw that a couple of others also had > > >> this > > >> problem. Fetch is getting distributions for ports and it'll just > > >> hang. > > >> Killing the build and restarting it will usually cause it to advance. > > >> Did > > >> any of you guys who saw this problem before come up with a solution? > > > > > > I found that changing my buffer size settings made all the difference. > > > I had been using the following in /etc/sysctl.conf: > > > > > > net.inet.tcp.recvspace=131072 > > > net.inet.tcp.sendspace=65536 > > > > > > Changing them to: > > > > > > net.inet.tcp.recvspace=65536 > > > net.inet.tcp.sendspace=32768 > > > > > > Solved the problem. > > > _______________________________________________ > 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 Jul 20 23:22: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 69F2D16A4CE for ; Tue, 20 Jul 2004 23:22:31 +0000 (GMT) Received: from lakermmtao07.cox.net (lakermmtao07.cox.net [68.230.240.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id F00DB43D2F for ; Tue, 20 Jul 2004 23:22:30 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao07.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP id <20040720232230.GJDK4320.lakermmtao07.cox.net@dolphin.local.net>; Tue, 20 Jul 2004 19:22:30 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.12.11/8.12.11) with ESMTP id i6KNMT3E004174; Tue, 20 Jul 2004 18:22:29 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.12.11/8.12.11/Submit) id i6KNMT8o004173; Tue, 20 Jul 2004 18:22:29 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <1090364563.728.3.camel@klamath.syndrom23.de> Date: Tue, 20 Jul 2004 18:22:29 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: Andreas Kohn cc: freebsd-current@freebsd.org Subject: Re: FAILURE - ATAPI_RESET no interrupt in newer current 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: Tue, 20 Jul 2004 23:22:31 -0000 On 20-Jul-2004 Andreas Kohn wrote: > Hi, > > today I updated my -CURRENT from ~July 5 to July 20 sources. After > reboot with the new kernel, I saw this: > > ata1-master: FAILURE - ATAPI_RESET no interrupt > acd0: CDRW at ata1-master WDMA2 > > With the old kernel, die FAILURE message was not there, but the acd0 > was running in WDMA2 mode as well. The mode seems to have no bearing on this issue; I get the same in either PIO4 or WDMA2 modes. > This is a > atapci0: port > 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on > pci0 controller. > > Is this message to be expected, or should I worry about anything? I'm seeing the same (and this is not the first time someone has reported this, either). The drive works normally, it seems, at least for a while. Last night, I tried playing a DVD in mplayer, and it worked fine until the whole machine suddenly hung. Hard to say whether or not this is an ata/atapi issue, or maybe due to the other, well-known preemption problem that's being discussed here lately. -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 23:28: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 D03D216A4CE; Tue, 20 Jul 2004 23:28:09 +0000 (GMT) Received: from lakermmtao11.cox.net (lakermmtao11.cox.net [68.230.240.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 402C543D2D; Tue, 20 Jul 2004 23:28:09 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao11.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP id <20040720232739.GLCS9104.lakermmtao11.cox.net@dolphin.local.net>; Tue, 20 Jul 2004 19:27:39 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.12.11/8.12.11) with ESMTP id i6KNRdht006659; Tue, 20 Jul 2004 18:27:39 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.12.11/8.12.11/Submit) id i6KNRdV7006658; Tue, 20 Jul 2004 18:27:39 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20040720123220.CBD565D08@ptavv.es.net> Date: Tue, 20 Jul 2004 18:27:39 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: Kevin Oberman cc: freebsd-current@freebsd.org cc: freebsd-gnome@freebsd.org Subject: Re: [amd64] System lockups still continuing 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: Tue, 20 Jul 2004 23:28:09 -0000 On 20-Jul-2004 Kevin Oberman wrote: [ re: lockup problem ] > The problem is not specific to ULE or 4BSD. A fix was checked in last > night, so cvsup and rebuild might just fix it. Early reports are that > the patch resolves the problem, but the author is not sure that this > is a complete fix. Yes, I updated the kernel as soon as I saw the commit. Had one lockup since, while playing a DVD in mplayer. This may or may not be related, as I'm seeing the weirdness re: ata interrupt timeouts here still. On the plus side, I've had no other lockups, and sound hasn't gone buggo, either (pcm timeout, channel dead), like it was before (at least, not yet). So, I'd say the patch does seem to help, but not sure yet if it's a 100% solution. -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 23:32: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 B71A316A4CE; Tue, 20 Jul 2004 23:32:09 +0000 (GMT) Received: from lakermmtao05.cox.net (lakermmtao05.cox.net [68.230.240.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36D3D43D5D; Tue, 20 Jul 2004 23:32:09 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao05.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP <20040720233207.GEKQ27302.lakermmtao05.cox.net@dolphin.local.net>; Tue, 20 Jul 2004 19:32:07 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.12.11/8.12.11) with ESMTP id i6KNW8BQ007570; Tue, 20 Jul 2004 18:32:08 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.12.11/8.12.11/Submit) id i6KNW7Z3007569; Tue, 20 Jul 2004 18:32:07 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20040720122304.GA5158@dylan.home> Date: Tue, 20 Jul 2004 18:32:07 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: Steve Roome cc: freebsd-multimedia@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [amd64] Sound breakage with snd_ich driver 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: Tue, 20 Jul 2004 23:32:09 -0000 On 20-Jul-2004 Steve Roome wrote: > On Tue, Jul 20, 2004 at 06:55:02AM -0500, Conrad J. Sabatier wrote: >> That, as well as whatever is still causing these: >> >> ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=123971136 > > Is it a SIL3112 SATA controller ? IIRC someone (not mentioning any > names) was claiming it was broken silicon - although to be fair it > doesn't "break" the same way under windows xp. No, mine uses the nVidia nForce3 chipset: atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 8.0 on pci0 One oddity that I hadn't previously mentioned is that I can't get UDMA higher than 100 on this machine. Don't know if that's a limitation of the drive, or the cable, or what: ad0: 190782MB [387621/16/63] at ata0-master UDMA100 > Getting it fixed would be nice though. Yes, it would be. :-) -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 23:33: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 EEA0016A4CE; Tue, 20 Jul 2004 23:33:13 +0000 (GMT) Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F95643D46; Tue, 20 Jul 2004 23:33:13 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from [192.168.1.33] (ti211110a080-0003.bb.online.no [80.212.192.3]) by smtp1.powertech.no (Postfix) with ESMTP id 9C02E809C; Wed, 21 Jul 2004 01:33:11 +0200 (CEST) In-Reply-To: <20040716111719.198dde57@bg.sics.se> References: <200407151424.i6FEOdoq060881@fledge.watson.org> <40F75738.2000604@alumni.rice.edu> <20040716111719.198dde57@bg.sics.se> Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <297F948A-DAA5-11D8-B5B9-000A95A9A574@nordahl.net> Content-Transfer-Encoding: quoted-printable From: Frode Nordahl Date: Wed, 21 Jul 2004 01:33:10 +0200 To: =?ISO-8859-1?Q?Bj=F6rn_Gr=F6nvall?= X-Mailer: Apple Mail (2.618) cc: re@freebsd.org cc: current@freebsd.org Subject: Re: 5.3-RELEASE TODO 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, 20 Jul 2004 23:33:14 -0000 On Jul 16, 2004, at 11:17, Bj=F6rn Gr=F6nvall wrote: > PR bin/61718 fixes a bunch of bugs in rpc.lockd, please try it. Yes, rpc.lockd is useless without this patch. Can someone please commit it? Mvh, Frode= From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 23:46: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 4BE5316A4CE; Tue, 20 Jul 2004 23:46:28 +0000 (GMT) Received: from gundel.de.clara.net (gundel.de.clara.net [212.82.225.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FC3F43D41; Tue, 20 Jul 2004 23:46:27 +0000 (GMT) (envelope-from jesk@killall.org) Received: from port-212-202-54-113.dynamic.qsc.de ([212.202.54.113] helo=turbofresse) by gundel.de.clara.net with smtp (Exim 4.30; FreeBSD) id 1Bn4T0-000MdI-T0; Wed, 21 Jul 2004 01:56:14 +0200 Message-ID: <056801c46eb3$bd0e2a40$45fea8c0@turbofresse> From: "jesk" To: Date: Wed, 21 Jul 2004 01:46:12 +0200 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.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 cc: Robert Watson Subject: Re: I/O or Threading Suffer 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, 20 Jul 2004 23:46:28 -0000 hi, i figured out that the performanceloss only really occur if the process is heavily writing on the filesystem. dd if=/dev/zero of=/dev/null bs=128k doesnt hurt much in responsetime of parallel processes, but when dd operates on the filesystem with of=foo every process will be affect in executiontime. a simple ps or ls meanwhile dding onto the disk will be hang for dozen of seconds. i tested it with 4BSD and ULE with and without Preemption. From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 23:47: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 0522A16A4CE for ; Tue, 20 Jul 2004 23:47:17 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 2390B43D41 for ; Tue, 20 Jul 2004 23:47:16 +0000 (GMT) (envelope-from andreas.kohn@gmx.net) Received: (qmail 4161 invoked by uid 65534); 20 Jul 2004 23:47:14 -0000 Received: from unknown (EHLO [212.204.44.203]) (212.204.44.203) by mail.gmx.net (mp001) with SMTP; 21 Jul 2004 01:47:14 +0200 X-Authenticated: #2431876 From: Andreas Kohn To: conrads@cox.net In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-xkqUgx3NAVE8SDv9rbm4" Message-Id: <1090367228.728.7.camel@klamath.syndrom23.de> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 21 Jul 2004 01:47:08 +0200 cc: freebsd-current@freebsd.org Subject: Re: FAILURE - ATAPI_RESET no interrupt in newer current 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, 20 Jul 2004 23:47:17 -0000 --=-xkqUgx3NAVE8SDv9rbm4 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2004-07-21 at 01:22, Conrad J. Sabatier wrote: > On 20-Jul-2004 Andreas Kohn wrote: > > Hi, > >=20 > > today I updated my -CURRENT from ~July 5 to July 20 sources. After > > reboot with the new kernel, I saw this: > >=20 > > ata1-master: FAILURE - ATAPI_RESET no interrupt > > acd0: CDRW at ata1-master WDMA2 > >=20 > > With the old kernel, die FAILURE message was not there, but the acd0 > > was running in WDMA2 mode as well. >=20 > The mode seems to have no bearing on this issue; I get the same in > either PIO4 or WDMA2 modes. >=20 > > This is a=20 > > atapci0: port > > 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on > > pci0 controller. > >=20 > > Is this message to be expected, or should I worry about anything? >=20 > I'm seeing the same (and this is not the first time someone has > reported this, either). >=20 > The drive works normally, it seems, at least for a while. Last night, > I tried playing a DVD in mplayer, and it worked fine until the whole > machine suddenly hung. Hard to say whether or not this is an > ata/atapi issue, or maybe due to the other, well-known preemption > problem that's being discussed here lately. Thank you. The thing is, I have absolutely no problems with this drive. It's just that this message is new, and so made me wonder a little :) Regards, -- Andreas --=-xkqUgx3NAVE8SDv9rbm4 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA/a78Yucd7Ow1ygwRAjkXAJ9vSmxjNWC4evZxlDWKaizWRJNX3wCgiJ9B vSte4u7PdlYGWOTAkxAAuQA= =A9LF -----END PGP SIGNATURE----- --=-xkqUgx3NAVE8SDv9rbm4-- From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 23:56: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 A535A16A4CE; Tue, 20 Jul 2004 23:56:44 +0000 (GMT) Received: from mr01.hansenet.de (mr01.hansenet.de [213.191.74.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C285F43D5E; Tue, 20 Jul 2004 23:56:42 +0000 (GMT) (envelope-from db@nipsi.de) Received: from mail.nipsi.de (213.39.145.70) by mr01.hansenet.de (6.7.010) id 40E529390003D4E5; Wed, 21 Jul 2004 01:56:41 +0200 Received: from localhost (localhost [127.0.0.1]) (uid 1001) by mail.nipsi.de with local; Wed, 21 Jul 2004 01:56:42 +0200 Date: Wed, 21 Jul 2004 01:56:42 +0200 From: Dennis Berger To: jesk Message-ID: <20040720235642.GA42120@nipsi.home.net> References: <056801c46eb3$bd0e2a40$45fea8c0@turbofresse> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: <056801c46eb3$bd0e2a40$45fea8c0@turbofresse> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: I/O or Threading Suffer 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, 20 Jul 2004 23:56:44 -0000 On Wed, Jul 21, 2004 at 01:46:12AM +0200, jesk wrote: > hi, > i figured out that the performanceloss only really occur if the process is > heavily writing on the filesystem. > dd if=/dev/zero of=/dev/null bs=128k doesnt hurt much in responsetime > of parallel processes, but when dd operates on the filesystem with of=foo > every process will be affect in executiontime. > a simple ps or ls meanwhile dding onto the disk will be hang for dozen of > seconds. > > i tested it with 4BSD and ULE with and without Preemption. yep same thing here, it seems the process ( the "ps" one) doesn't get cputime or something strange. -db > > > _______________________________________________ > 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 Jul 21 00:19: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 B921A16A4CE; Wed, 21 Jul 2004 00:19:15 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D57143D5C; Wed, 21 Jul 2004 00:19:14 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6L0Icu3012715; Tue, 20 Jul 2004 20:18:38 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6L0IcUF012712; Tue, 20 Jul 2004 20:18:38 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 20 Jul 2004 20:18:38 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Frode Nordahl In-Reply-To: <297F948A-DAA5-11D8-B5B9-000A95A9A574@nordahl.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE cc: =?ISO-8859-1?Q?Bj=F6rn_Gr=F6nvall?= cc: re@freebsd.org cc: current@freebsd.org Subject: Re: 5.3-RELEASE TODO 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, 21 Jul 2004 00:19:15 -0000 On Wed, 21 Jul 2004, Frode Nordahl wrote: > On Jul 16, 2004, at 11:17, Bj=F6rn Gr=F6nvall wrote: >=20 > > PR bin/61718 fixes a bunch of bugs in rpc.lockd, please try it. >=20 > Yes, rpc.lockd is useless without this patch. >=20 > Can someone please commit it? It looks like much if not all of it was committed on 20040716; commit message below. Are any specific things that appear to be missing that weren't merged? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research revision 1.17 date: 2004/07/16 12:50:10; author: mr; state: Exp; lines: +1 -1 After talking to Colin, apply the patch of bin/61718 (which should include/elimatate kern/61122 also). It seems to fix a few annoying bugs. PR: bin/61718, kern/61122 Submitted by: bg@sics.se ohartman@mail.physik.uni-mainz.de ---------------------------- revision 1.18 date: 2004/07/16 19:30:59; author: mr; state: Exp; lines: +0 -0 Forced commit to actually list the changes of bin/61718, as requested by sam. The attached patch fixes a number of problems present in rpc.lockd. 1) Nfslocklist_head.lf_first is overwritten because of an off-by-one-bug that happens when clnt_cache_next_to_use is incorrectly incremented. 2) 'struct sockaddr *addr' inside 'struct file_lock' is set to point to the result from svc_getrpccaller(). This value is malloc:ed inside the rpc libraries and is free:ed when clnt_destroy() is called. Fix, maintain a copy of the result. 3) The loop inside retry_blockingfilelocklist() that uses 3 pointers ifl, nfl, and pfl thrashes the list pointed to by blockedlocklist_head.lf_first. Fix, use a simpler loop. The new loop does not preserve list order but the order is immaterial anyways. See also revison 1.6-1.7 and kern/61122. 4) struct file_lock char client_name[SM_MAXSTRLEN]; and struct host char name[SM_MAXSTRLEN]; Be careful to not create open (non 0 terminated) C strings and later passing them to e.g syslog. Fix, make sure that the strings are always terminated with 0. When at it, move the strings to the end of the structs and make them variable length. This saves about 1000 bytes for every malloc:ed struct. 5) The newfl =3D malloc(sizeof(struct file_lock)) memory was never properly bzero:ed. Minor changes: A) Nlmtonlm4(0) made assumptions about struct layouts. B) Don't close stdout and stderr when debugging (-d option). C) Remove unused pid_t locker and int fd in struct file_lock. D) s/printf/debuglog/ E) Remove redundant sleep(1) and call to debuglog(). Cheers, Bjrn From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 00:32: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 331B816A4CE; Wed, 21 Jul 2004 00:32:43 +0000 (GMT) Received: from CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com (CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com [69.193.41.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id E16FC43D39; Wed, 21 Jul 2004 00:32:42 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from localhost (localhost [127.0.0.1]) with ESMTP id AE55D2954C4; Tue, 20 Jul 2004 20:32:44 -0400 (EDT) Received: from CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com ([127.0.0.1])10024) with ESMTP id 00508-02; Tue, 20 Jul 2004 20:32:42 -0400 (EDT) Received: from 192.168.0.1 (localhost [127.0.0.1]) with ESMTP id 869422954C3; Tue, 20 Jul 2004 20:32:42 -0400 (EDT) Received: from 192.168.0.200 (SquirrelMail authenticated user mikej); by 192.168.0.1 with HTTP; Tue, 20 Jul 2004 20:32:42 -0400 (EDT) Message-ID: <1407.192.168.0.200.1090369962.squirrel@192.168.0.200> Date: Tue, 20 Jul 2004 20:32:42 -0400 (EDT) From: "Mike Jakubik" To: freebsd-current@freebsd.org, freebsd-net@freebsd.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: by amavisd-new at fbsd.wettoast.net Subject: NATD no longer works for outgoing PPTP VPN? 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, 21 Jul 2004 00:32:43 -0000 Hello, I have recently discovered, after long periods of trying to debug a VPN server, that i can not establish PPTP VPN connections any more. The culprit seems to be natd not forwarding GRE properly. I have tried adding a 'redirect_proto gre' option to natd, but same behaviour occurs. I could swear that not too long ago all my PPTP connection worked fine, as i have a few clients defined in my windows pc. I have tried 3 different VPN server, ranging from Windows 2000 server to FBSD with MPD, none work. Plugging Internet directly to my PC works fine. Here is what the setup looks like: Me (Windows XP) FreeBSD 5-C w/ NATD Internet VPN server 192.168.0.200 192.168.0.1 69.193.41.53 66.11.183.182 Here is rc.conf --- gateway_enable="YES" natd_enable="YES" natd_interface="xl0" natd_flags="-f /etc/natd.conf" Here is natd.conf: --- interface xl0 dynamic yes use_sockets yes same_ports yes redirect_port tcp win2000:3389 3389 #redirect_proto gre win2000 And here is a log from natd -v when trying to estabish a VPN connection (it looks like GRE is not being aliased correctly, windows pc just sits at 'Verifying username...'): --- natd[32158]: Aliasing to 69.193.41.53, mtu 1500 bytes Out {default} 0000ffff[TCP] [TCP] 192.168.0.200:1108 -> 66.11.183.182:1723 aliased to [TCP] 69.193.41.53:1108 -> 66.11.183.182:1723 In {default} 0000ffff[TCP] [TCP] 66.11.183.182:1723 -> 69.193.41.53:1108 aliased to [TCP] 66.11.183.182:1723 -> 192.168.0.200:1108 Out {default} 0000ffff[TCP] [TCP] 192.168.0.200:1108 -> 66.11.183.182:1723 aliased to [TCP] 69.193.41.53:1108 -> 66.11.183.182:1723 In {default} 0000ffff[TCP] [TCP] 66.11.183.182:1723 -> 69.193.41.53:1108 aliased to [TCP] 66.11.183.182:1723 -> 192.168.0.200:1108 Out {default} 0000ffff[TCP] [TCP] 192.168.0.200:1108 -> 66.11.183.182:1723 aliased to [TCP] 69.193.41.53:1108 -> 66.11.183.182:1723 In {default} 0000ffff[TCP] [TCP] 66.11.183.182:1723 -> 69.193.41.53:1108 aliased to [TCP] 66.11.183.182:1723 -> 192.168.0.200:1108 In {default} 0000ffff[47] [47] 66.11.183.182 -> 69.193.41.53 aliased to [47] 66.11.183.182 -> 69.193.41.53 Out {default} 0000ffff[TCP] [TCP] 192.168.0.200:1108 -> 66.11.183.182:1723 aliased to [TCP] 69.193.41.53:1108 -> 66.11.183.182:1723 Out {default} 0000ffff[47] [47] 192.168.0.200 -> 66.11.183.182 aliased to [47] 192.168.0.200 -> 66.11.183.182 In {default} 0000ffff[TCP] [TCP] 66.11.183.182:1723 -> 69.193.41.53:1108 aliased to [TCP] 66.11.183.182:1723 -> 192.168.0.200:1108 Out {default} 0000ffff[47] [47] 192.168.0.200 -> 66.11.183.182 aliased to [47] 192.168.0.200 -> 66.11.183.182 In {default} 0000ffff[47] [47] 66.11.183.182 -> 69.193.41.53 aliased to [47] 66.11.183.182 -> 69.193.41.53 In {default} 0000ffff[47] [47] 66.11.183.182 -> 69.193.41.53 aliased to [47] 66.11.183.182 -> 69.193.41.53 Out {default} 0000ffff[47] [47] 192.168.0.200 -> 66.11.183.182 aliased to [47] 192.168.0.200 -> 66.11.183.182 In {default} 0000ffff[47] [47] 66.11.183.182 -> 69.193.41.53 aliased to [47] 66.11.183.182 -> 69.193.41.53 In {default} 0000ffff[47] [47] 66.11.183.182 -> 69.193.41.53 aliased to [47] 66.11.183.182 -> 69.193.41.53 Out {default} 0000ffff[47] [47] 192.168.0.200 -> 66.11.183.182 aliased to [47] 192.168.0.200 -> 66.11.183.182 In {default} 0000ffff[47] [47] 66.11.183.182 -> 69.193.41.53 aliased to [47] 66.11.183.182 -> 69.193.41.53 In {default} 0000ffff[47] [47] 66.11.183.182 -> 69.193.41.53 aliased to [47] 66.11.183.182 -> 69.193.41.53 Out {default} 0000ffff[47] [47] 192.168.0.200 -> 66.11.183.182 aliased to [47] 192.168.0.200 -> 66.11.183.182 In {default} 0000ffff[47] [47] 66.11.183.182 -> 69.193.41.53 aliased to [47] 66.11.183.182 -> 69.193.41.53 In {default} 0000ffff[47] [47] 66.11.183.182 -> 69.193.41.53 aliased to [47] 66.11.183.182 -> 69.193.41.53 Out {default} 0000ffff[47] [47] 192.168.0.200 -> 66.11.183.182 aliased to [47] 192.168.0.200 -> 66.11.183.182 In {default} 0000ffff[47] [47] 66.11.183.182 -> 69.193.41.53 aliased to [47] 66.11.183.182 -> 69.193.41.53 In {default} 0000ffff[TCP] [TCP] 66.11.183.182:1723 -> 69.193.41.53:1108 aliased to [TCP] 66.11.183.182:1723 -> 192.168.0.200:1108 Out {default} 0000ffff[TCP] [TCP] 192.168.0.200:1108 -> 66.11.183.182:1723 aliased to [TCP] 69.193.41.53:1108 -> 66.11.183.182:1723 In {default} 0000ffff[TCP] [TCP] 66.11.183.182:1723 -> 69.193.41.53:1108 aliased to [TCP] 66.11.183.182:1723 -> 192.168.0.200:1108 In {default} 0000ffff[TCP] [TCP] 66.11.183.182:1723 -> 69.193.41.53:1108 aliased to [TCP] 66.11.183.182:1723 -> 192.168.0.200:1108 Out {default} 0000ffff[TCP] [TCP] 192.168.0.200:1108 -> 66.11.183.182:1723 aliased to [TCP] 69.193.41.53:1108 -> 66.11.183.182:1723 In {default} 0000ffff[TCP] [TCP] 66.11.183.182:1723 -> 69.193.41.53:1108 aliased to [TCP] 66.11.183.182:1723 -> 192.168.0.200:1108 Thank You. From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 00:38: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 02B4916A4CE; Wed, 21 Jul 2004 00:38:55 +0000 (GMT) Received: from ozlabs.org (ozlabs.org [203.10.76.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74B0943D41; Wed, 21 Jul 2004 00:38:54 +0000 (GMT) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (blackwater.lemis.com [192.109.197.80]) by ozlabs.org (Postfix) with ESMTP id 563E12BDEC; Wed, 21 Jul 2004 10:38:52 +1000 (EST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 37668511FE; Wed, 21 Jul 2004 10:08:50 +0930 (CST) Date: Wed, 21 Jul 2004 10:08:50 +0930 From: Greg 'groggy' Lehey To: Hidetoshi Shimokawa Message-ID: <20040721003850.GD78419@wantadilla.lemis.com> References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> <87hds3pfgv.wl@tora.nunu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DrWhICOqskFTAXiy" Content-Disposition: inline In-Reply-To: <87hds3pfgv.wl@tora.nunu.org> User-Agent: Mutt/1.4.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: simokawa@freebsd.org cc: freebsd-current@freebsd.org cc: Andrew Gallatin Subject: Re: Excellent job on the firewire 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: Wed, 21 Jul 2004 00:38:55 -0000 --DrWhICOqskFTAXiy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tuesday, 20 July 2004 at 11:41:52 +0900, Hidetoshi Shimokawa wrote: > (sorry for resending) > > At Sun, 18 Jul 2004 21:04:53 +0100, > Doug Rabson wrote: >>> 2) Is dcons usable after a panic (ie, DDB or KDB_TRACE)? Or is it >>> only usable for remote-gdb? >> >> Dcons provides two full duplex streams - one for console and one for >> gdb. You can use DDB on the console just like normal. > > It's designed for such panic/debugging situation. > Actually, it's rather inefficient for usual situation > but the speed of FireWire hide the problem ;-) I think that the most spectacular use of firewire is debugging a completely hung system. If you've already attached, the debugger can still access the memory of a system which isn't reacting *at all*. Obviously you can't continue execution, but just seeing what's in memory is a great advantage. On the other hand, it was my understanding that marcel's new kernel debugging framework broke firewire debugging. What's the current status there? Greg -- Note: I discard all HTML mail unseen. Finger grog@FreeBSD.org for PGP public key. See complete headers for address and phone numbers. --DrWhICOqskFTAXiy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQFA/bsaIubykFB6QiMRApDgAJ9lCKg1HM81MoE7wra4iQqboXYYfgCdHqm8 PdGC6ir+/b6BnWMT0emAIQ4= =iHPh -----END PGP SIGNATURE----- --DrWhICOqskFTAXiy-- From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 00:58: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 1828416A4CE; Wed, 21 Jul 2004 00:58:40 +0000 (GMT) Received: from tora.nunu.org (YahooBB219003182029.bbtec.net [219.3.182.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5357643D2D; Wed, 21 Jul 2004 00:58:39 +0000 (GMT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from tora.nunu.org (unknown [192.168.1.2]) by tora.nunu.org (Postfix) with ESMTP id A9B6D4E57D; Wed, 21 Jul 2004 09:58:37 +0900 (JST) Date: Wed, 21 Jul 2004 09:58:37 +0900 Message-ID: <877jsyp45e.wl@tora.nunu.org> From: Hidetoshi Shimokawa To: "Greg 'groggy' Lehey" In-Reply-To: <20040721003850.GD78419@wantadilla.lemis.com> References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> <87hds3pfgv.wl@tora.nunu.org> <20040721003850.GD78419@wantadilla.lemis.com> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 14) (Reasonable Discussion) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: simokawa@freebsd.org cc: marcel@freebsd.org cc: Andrew Gallatin cc: freebsd-current@freebsd.org Subject: Re: Excellent job on the firewire 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: Wed, 21 Jul 2004 00:58:40 -0000 At Wed, 21 Jul 2004 10:08:50 +0930, Greg 'groggy' Lehey wrote: > On the other hand, it was my understanding that marcel's new kernel > debugging framework broke firewire debugging. What's the current > status there? I've already adjust the interface for remote gdb. See rev 1.14 of /sys/dev/dcons.c. For the debugging with /dev/fwmem(or /dev/mem), it seems that you need to use gdb in ports or "remote gdb wrapper" which marcel posted freebsd-arch@. I don't know whether the default gdb will support /dev/(k)mem debugging or not. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 01:04: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 2533616A4CE for ; Wed, 21 Jul 2004 01:04:10 +0000 (GMT) Received: from pimout3-ext.prodigy.net (pimout3-ext.prodigy.net [207.115.63.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0D3C43D3F for ; Wed, 21 Jul 2004 01:04:09 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (adsl-68-121-219-69.dsl.snfc21.pacbell.net [68.121.219.69])i6L140lM154576; Tue, 20 Jul 2004 21:04:00 -0400 Message-ID: <40FDC0FF.30901@elischer.org> Date: Tue, 20 Jul 2004 18:03:59 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030524 X-Accept-Language: en, hu MIME-Version: 1.0 To: "Greg 'groggy' Lehey" References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> <87hds3pfgv.wl@tora.nunu.org> <20040721003850.GD78419@wantadilla.lemis.com> In-Reply-To: <20040721003850.GD78419@wantadilla.lemis.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: simokawa@freebsd.org cc: Hidetoshi Shimokawa cc: freebsd-current@freebsd.org cc: Andrew Gallatin Subject: Re: Excellent job on the firewire 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: Wed, 21 Jul 2004 01:04:10 -0000 Greg 'groggy' Lehey wrote: >On Tuesday, 20 July 2004 at 11:41:52 +0900, Hidetoshi Shimokawa wrote: > > >>(sorry for resending) >> >>At Sun, 18 Jul 2004 21:04:53 +0100, >>Doug Rabson wrote: >> >> >>>>2) Is dcons usable after a panic (ie, DDB or KDB_TRACE)? Or is it >>>> only usable for remote-gdb? >>>> >>>> >>>Dcons provides two full duplex streams - one for console and one for >>>gdb. You can use DDB on the console just like normal. >>> >>> >>It's designed for such panic/debugging situation. >>Actually, it's rather inefficient for usual situation >>but the speed of FireWire hide the problem ;-) >> >> > >I think that the most spectacular use of firewire is debugging a >completely hung system. If you've already attached, the debugger can >still access the memory of a system which isn't reacting *at all*. >Obviously you can't continue execution, but just seeing what's in >memory is a great advantage. > >On the other hand, it was my understanding that marcel's new kernel >debugging framework broke firewire debugging. What's the current >status there? > He helped "Mr Firewire" get it going again the next day... > >Greg >-- >Note: I discard all HTML mail unseen. >Finger grog@FreeBSD.org for PGP public key. >See complete headers for address and phone numbers. > > From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 01:06: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 620DC16A4CE for ; Wed, 21 Jul 2004 01:06:23 +0000 (GMT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2576943D41 for ; Wed, 21 Jul 2004 01:06:23 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i6L16MR0001853 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Jul 2004 21:06:22 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i6L16HgZ045354; Tue, 20 Jul 2004 21:06:17 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16637.49545.42904.484648@grasshopper.cs.duke.edu> Date: Tue, 20 Jul 2004 21:06:17 -0400 (EDT) To: Martin Blapp In-Reply-To: <20040326001705.W34892@cvs.imp.ch> References: <20040326001705.W34892@cvs.imp.ch> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: Mike Silbersack cc: current@freebsd.org Subject: Re: Ok, who broke interface autoconfiguration? 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, 21 Jul 2004 01:06:23 -0000 Martin Blapp writes: > > Hi all, > > >From my side, nothing has changed. The last commit to dhclient > happened about 2 1/2 month ago. > > I can cvsup to the lastest current tomorrow and try > dhcp out on my wi0 card. This is still happening to me.. I filed a PR so that it does not get lost. http://www.freebsd.org/cgi/query-pr.cgi?pr=69361 I think the key might be the dhcp server message: " unknown lease 0.0.0.0." Thanks, Drew From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 01:36: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 EA4A616A4CF for ; Wed, 21 Jul 2004 01:36:07 +0000 (GMT) Received: from out010.verizon.net (out010pub.verizon.net [206.46.170.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8525243D1F for ; Wed, 21 Jul 2004 01:36:07 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] ([68.161.84.3]) by out010.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040721013606.YGVY15848.out010.verizon.net@[192.168.1.3]>; Tue, 20 Jul 2004 20:36:06 -0500 Message-ID: <40FDC87E.7070602@mac.com> Date: Tue, 20 Jul 2004 21:35:58 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.1) Gecko/20040707 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Gallatin References: <20040326001705.W34892@cvs.imp.ch> <16637.49545.42904.484648@grasshopper.cs.duke.edu> In-Reply-To: <16637.49545.42904.484648@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out010.verizon.net from [68.161.84.3] at Tue, 20 Jul 2004 20:36:06 -0500 cc: current@freebsd.org Subject: Re: Ok, who broke interface autoconfiguration? 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, 21 Jul 2004 01:36:08 -0000 Andrew Gallatin wrote: [ ... ] > I think the key might be the dhcp server message: " unknown lease 0.0.0.0." If memory serves, the ISC DHCP software can become petulant and confused by its own leases file if/when internal structures change in size. Perhaps try "rm /var/db/dhc*.leases" and see whether that fixes things. -- -Chuck From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 01:39: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 3B9DA16A4CE; Wed, 21 Jul 2004 01:39:32 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE1E743D2F; Wed, 21 Jul 2004 01:39:31 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from dhcp50.pn.xcllnt.net (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.12.11/8.12.11) with ESMTP id i6L1dOph029301; Tue, 20 Jul 2004 18:39:24 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp50.pn.xcllnt.net (localhost [127.0.0.1]) i6L1dO9r039151; Tue, 20 Jul 2004 18:39:24 -0700 (PDT) (envelope-from marcel@dhcp50.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp50.pn.xcllnt.net (8.12.11/8.12.11/Submit) id i6L1dNsj039150; Tue, 20 Jul 2004 18:39:23 -0700 (PDT) (envelope-from marcel) Date: Tue, 20 Jul 2004 18:39:22 -0700 From: Marcel Moolenaar To: Hidetoshi Shimokawa Message-ID: <20040721013922.GA39137@dhcp50.pn.xcllnt.net> References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> <87hds3pfgv.wl@tora.nunu.org> <20040721003850.GD78419@wantadilla.lemis.com> <877jsyp45e.wl@tora.nunu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <877jsyp45e.wl@tora.nunu.org> User-Agent: Mutt/1.4.2.1i cc: Greg 'groggy' Lehey cc: simokawa@FreeBSD.org cc: freebsd-current@FreeBSD.org cc: Andrew Gallatin Subject: Re: Excellent job on the firewire 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: Wed, 21 Jul 2004 01:39:32 -0000 On Wed, Jul 21, 2004 at 09:58:37AM +0900, Hidetoshi Shimokawa wrote: > At Wed, 21 Jul 2004 10:08:50 +0930, > Greg 'groggy' Lehey wrote: > > On the other hand, it was my understanding that marcel's new kernel > > debugging framework broke firewire debugging. What's the current > > status there? > > I've already adjust the interface for remote gdb. > See rev 1.14 of /sys/dev/dcons.c. > > For the debugging with /dev/fwmem(or /dev/mem), it seems that > you need to use gdb in ports or "remote gdb wrapper" which marcel > posted freebsd-arch@. I don't know whether the default gdb will > support /dev/(k)mem debugging or not. Yes, it will. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 01:40: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 6D2C416A4CE for ; Wed, 21 Jul 2004 01:40:28 +0000 (GMT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0498B43D45 for ; Wed, 21 Jul 2004 01:40:28 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i6L1eRR0004867 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Jul 2004 21:40:27 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i6L1eLYw045389; Tue, 20 Jul 2004 21:40:21 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16637.51589.728466.696044@grasshopper.cs.duke.edu> Date: Tue, 20 Jul 2004 21:40:21 -0400 (EDT) To: Chuck Swiger In-Reply-To: <40FDC87E.7070602@mac.com> References: <20040326001705.W34892@cvs.imp.ch> <16637.49545.42904.484648@grasshopper.cs.duke.edu> <40FDC87E.7070602@mac.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: current@freebsd.org Subject: Re: Ok, who broke interface autoconfiguration? 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, 21 Jul 2004 01:40:28 -0000 Chuck Swiger writes: > Andrew Gallatin wrote: > [ ... ] > > I think the key might be the dhcp server message: " unknown lease 0.0.0.0." > > If memory serves, the ISC DHCP software can become petulant and confused by > its own leases file if/when internal structures change in size. Perhaps try > "rm /var/db/dhc*.leases" and see whether that fixes things. > Yes, it does. But I haven't build world on the amd64 in weeks, so nothing has changed size there. Drew From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 02:01: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 052A016A4CE for ; Wed, 21 Jul 2004 02:01:23 +0000 (GMT) Received: from lakermmtao08.cox.net (lakermmtao08.cox.net [68.230.240.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8746243D1D for ; Wed, 21 Jul 2004 02:01:22 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao08.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP id <20040721020120.JOSX1332.lakermmtao08.cox.net@dolphin.local.net> for ; Tue, 20 Jul 2004 22:01:20 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.12.11/8.12.11) with ESMTP id i6L21LYW075652 for ; Tue, 20 Jul 2004 21:01:21 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.12.11/8.12.11/Submit) id i6L21L2l075593 for freebsd-current@freebsd.org; Tue, 20 Jul 2004 21:01:21 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 20 Jul 2004 21:01:21 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: freebsd-current@freebsd.org Subject: Re: [amd64] System lockups still continuing 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: Wed, 21 Jul 2004 02:01:23 -0000 On 20-Jul-2004 Conrad J. Sabatier wrote: > > [ re: lockup problem ] > > Yes, I updated the kernel as soon as I saw the commit. Had one > lockup since, while playing a DVD in mplayer. This may or may not be > related, as I'm seeing the weirdness re: ata interrupt timeouts here > still. > > On the plus side, I've had no other lockups, and sound hasn't gone > buggo, either (pcm timeout, channel dead), like it was before (at > least, not yet). Oh well, sound just croaked again. :-( Looks like the pcm timeout really is probably a completely separate issue. Time for another reboot. :-) -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 04:43: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 4119816A4CE; Wed, 21 Jul 2004 04:43:16 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35EF743D2D; Wed, 21 Jul 2004 04:43:13 +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 i6L4gsCJ034822; Wed, 21 Jul 2004 14:12:55 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Wed, 21 Jul 2004 14:12:54 +0930 User-Agent: KMail/1.6.2 References: <20040326001705.W34892@cvs.imp.ch> <16637.49545.42904.484648@grasshopper.cs.duke.edu> <40FDC87E.7070602@mac.com> In-Reply-To: <40FDC87E.7070602@mac.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200407211412.54225.doconnor@gsoft.com.au> X-Spam-Score: -4.9 () CARRIAGE_RETURNS,IN_REP_TO,PGP_SIGNATURE,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: Chuck Swiger cc: Andrew Gallatin cc: current@freebsd.org Subject: Re: Ok, who broke interface autoconfiguration? 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, 21 Jul 2004 04:43:16 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 21 Jul 2004 11:05, Chuck Swiger wrote: > Andrew Gallatin wrote: > [ ... ] > > > I think the key might be the dhcp server message: " unknown lease > > 0.0.0.0." > > If memory serves, the ISC DHCP software can become petulant and confused = by > its own leases file if/when internal structures change in size. Perhaps > try "rm /var/db/dhc*.leases" and see whether that fixes things. I see it get confused when nothing gets changed. It sits there for $longtime (might be forever, not sure). The only fix I ha= ve=20 found is to kill it, delete dhclient.leases and re-run it.. (This is on IA32) =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 =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/fRO5ZPcIHs/zowRAlWhAKCZ1rN9aY5Gs4b3D+19ETjIgW/i/QCeMvRp kC9+ABfRn9B+drWsnNOjcOY=3D =3DV5WA =2D----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 04:43: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 4119816A4CE; Wed, 21 Jul 2004 04:43:16 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35EF743D2D; Wed, 21 Jul 2004 04:43:13 +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 i6L4gsCJ034822; Wed, 21 Jul 2004 14:12:55 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Wed, 21 Jul 2004 14:12:54 +0930 User-Agent: KMail/1.6.2 References: <20040326001705.W34892@cvs.imp.ch> <16637.49545.42904.484648@grasshopper.cs.duke.edu> <40FDC87E.7070602@mac.com> In-Reply-To: <40FDC87E.7070602@mac.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200407211412.54225.doconnor@gsoft.com.au> X-Spam-Score: -4.9 () CARRIAGE_RETURNS,IN_REP_TO,PGP_SIGNATURE,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: Chuck Swiger cc: Andrew Gallatin cc: current@freebsd.org Subject: Re: Ok, who broke interface autoconfiguration? 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, 21 Jul 2004 04:43:16 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 21 Jul 2004 11:05, Chuck Swiger wrote: > Andrew Gallatin wrote: > [ ... ] > > > I think the key might be the dhcp server message: " unknown lease > > 0.0.0.0." > > If memory serves, the ISC DHCP software can become petulant and confused = by > its own leases file if/when internal structures change in size. Perhaps > try "rm /var/db/dhc*.leases" and see whether that fixes things. I see it get confused when nothing gets changed. It sits there for $longtime (might be forever, not sure). The only fix I ha= ve=20 found is to kill it, delete dhclient.leases and re-run it.. (This is on IA32) =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 =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/fRO5ZPcIHs/zowRAlWhAKCZ1rN9aY5Gs4b3D+19ETjIgW/i/QCeMvRp kC9+ABfRn9B+drWsnNOjcOY=3D =3DV5WA =2D----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 04:48: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 09A7316A4CF; Wed, 21 Jul 2004 04:48:18 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D80743D4C; Wed, 21 Jul 2004 04:48:18 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i6L4mHKI090936; Tue, 20 Jul 2004 23:48:17 -0500 (CDT) (envelope-from dan) Date: Tue, 20 Jul 2004 23:48:17 -0500 From: Dan Nelson To: jesk Message-ID: <20040721044816.GA56020@dan.emsphone.com> References: <056801c46eb3$bd0e2a40$45fea8c0@turbofresse> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <056801c46eb3$bd0e2a40$45fea8c0@turbofresse> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: I/O or Threading Suffer 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, 21 Jul 2004 04:48:19 -0000 In the last episode (Jul 21), jesk said: > i figured out that the performanceloss only really occur if the > process is heavily writing on the filesystem. dd if=/dev/zero > of=/dev/null bs=128k doesnt hurt much in responsetime of parallel > processes, but when dd operates on the filesystem with of=foo every > process will be affect in executiontime. a simple ps or ls meanwhile > dding onto the disk will be hang for dozen of seconds. Ah. now that's a different story. You're out of the control of the process scheduler and into the disk. I don't suppose you're using an IDE/ATA disk with no tagged queueing? :) Run "dmesg | grep depth.queue" to see how many requests can be queued up on your disk at once. That dd is stuffing lots of dirty data into the disk cache, and all the other processes have to wait in line to get their I/Os done. You'll see much better results from a SCSI disk (with usual queue depths between 32 and 64), and even better results from a multi-disk hardware RAID array (which will have a large write cache). -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 04:54: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 265D616A4CE for ; Wed, 21 Jul 2004 04:54:45 +0000 (GMT) Received: from black3.imgsrc.co.jp (black3.imgsrc.co.jp [210.226.20.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D7CD43D2F for ; Wed, 21 Jul 2004 04:54:42 +0000 (GMT) (envelope-from kuriyama@imgsrc.co.jp) Received: from localhost (localhost [127.0.0.1]) by black3.imgsrc.co.jp (Postfix) with ESMTP id A021950B1B for ; Wed, 21 Jul 2004 13:54:41 +0900 (JST) Received: from black3.imgsrc.co.jp (black3.imgsrc.co.jp [IPv6:2001:218:422:2::9999]) by black3.imgsrc.co.jp (Postfix) with ESMTP id 47F6B50B33 for ; Wed, 21 Jul 2004 13:54:40 +0900 (JST) Date: Wed, 21 Jul 2004 13:54:40 +0900 Message-ID: <7m4qo29cz3.wl@black3.imgsrc.co.jp> From: Jun Kuriyama To: Current User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd 0.1 Subject: Fatal double fault 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, 21 Jul 2004 04:54:45 -0000 # I've reinstalled on fresh HDD. On recent (yesterday's) kernel+world with GENERIC kernel. Fatal double fault: eip = 0xc063c457 esp = 0xde421fec ebp = 0xde4221c0 cpuid = 1; apic id = 01 panic: double fault cpuid = 1; KDB: enter: panic [thread 100040] Stopped at kdb_enter+0x2b: nop db> trace kdb_enter(c07d25ef) at kdb_enter+0x2b panic(c07f151f,c07f16c0,1,0,0) at panic+0x131 dblfault_handler(c086dfec,1,60,c34d5000,c088f7c8) at dblfault_handler+0x7a -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 06:39: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 A224216A4CE for ; Wed, 21 Jul 2004 06:39:57 +0000 (GMT) Received: from 1002-17.Lowesthosting.com (1002-17.lowesthosting.com [207.44.234.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 1CB2A43D41 for ; Wed, 21 Jul 2004 06:39:55 +0000 (GMT) (envelope-from jhamby@anobject.com) Received: (qmail 23007 invoked from network); 21 Jul 2004 06:33:03 -0000 Received: from ar39.lsanca2-4.16.240.155.lsanca2.elnk.dsl.genuity.net (HELO ?192.168.0.13?) (4.16.240.155) by 1002-17.lowesthosting.com with SMTP; 21 Jul 2004 06:33:03 -0000 Message-ID: <40FE0DF3.4030008@anobject.com> Date: Tue, 20 Jul 2004 23:32:19 -0700 From: Jake Hamby User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040719) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-mobile@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Using -current on a Fujitsu Lifebook N5010 (no Atheros 802.11, no Ethernet, + hard freezes) 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, 21 Jul 2004 06:39:57 -0000 I recently purchased a new notebook (a Fujitsu Lifebook N5010, a model which I can highly recommend as a desktop replacement) and decided to try installing FreeBSD-CURRENT on it instead of Gentoo Linux, which is the UNIX that I would normally install. Here are some of the issues I faced in terms of missing kernel support for this laptop. 1) Ethernet chipset not recognized. This laptop uses the SiS 648 chipset and includes a 10/100 Ethernet port with a Realtek 8139-compatible interface. More specifically, it is vendor id 0x10EC (Realtek), device id 0x8139 on PCI device 00:07.0, recognized as type 'RTL-8100B/8139D' by the Linux 8139too driver. What is even stranger is that this card shows up in a DOS-based hardware scan (using AIDA from the Ultimate Boot CD), but not in the output of pciconf. Nor does it show up in the dmesg output, even as an unknown device. 2) Version of Atheron 802.11a/b/g driver is too old. With the version of the ath driver in CURRENT, I get this output: ath0: [GIANT-LOCKED] ath0: mac 5.6 phy 4.1 5ghz radio 3.6 ath0: unable to collect channel list from hal device_attach: ath0 attach returned 22 ath0: mem 0xec010000-0xec01ffff irq 11 at device 10.0 on pci0 The problem is inside of the portion of the code which is delivered only in binary form. Fortunately for you all, I spent the last five or six days hacking on it and was able to integrate the latest version of the Linux Atheros hal code from http://madwifi.sourceforge.net/, as well as the necessary changes to the driver code provided as source. You can download my merged version from here: http://www.anobject.com/jehamby/atheros_driver.tar.bz2 If anyone else has a WiFi adapter with an Atheros AR5210, AR5211, or AR5212 chip, please download it and check it out (the replacement files will go in the right places if extracted into /usr/src). In addition to offering support for the newer cards, the updated version of the driver has these changes compared to the version in -current. * New tunables: hw.ath.xchanmode (enable extended channels, default enabled) hw.ath.rateinterval (rate ctl interval in ms, default 1 second) hw.ath.ctlpkt_type (control pkt type to filter, which only has an effect in terms of handling control packets which would otherwise be rejected as too short, and which I've never seen but added the code from the Linux version anyway) * Added automatic rate control adjustment. For 802.11b, starts at the highest negotiated rate, otherwise, for 11g and 11a, starts "in the middle" at 24Mb or 36Mb, then steps up or down over time using the error/retry count for feedback. * Now uses four transmission queues of varying priority instead of one: WME_AC_BE (highest), WME_AC_BK, WME_AC_VI, and WME_AC_VO (lowest). There is code in the Linux version to support QOS and insert outgoing packets into queue by priority, but I couldn't find the equivalent of the priority field from Linux's sk_buff struct in FreeBSD's equivalent ieee80211_frame struct. Currently all outgoing packets go to WME_AC_BE, except packets of type IEEE80211_FC0_TYPE_MGT, which go to WME_AC_VO. * Enabled multi-rate retry if the MAC supports it. * Added a mutex lock around several ath_*() functions that did not have one before. The Linux version only uses locks around the xmit buffer and the xmit queues, while the current FreeBSD version also uses a global mutex around several functions. I am getting random hard freezes (see bug #3) and I don't know if there are any additional locking issues that might be causing this. This driver is relatively complex, consisting of several callouts that run at various intervals (normally, calibration every 30 seconds and rate control every second) as well as interrupt handling and other entry points, so I couldn't find any other driver to use as an example. * changed the format of the structures returned by the SIOCGATHSTATS and SIOCGATHDIAG ioctls. You will have to recompile "athstats" from /usr/src/tools/tools/ath if you use that utility for debugging. 3) Random freezes After an average of 30-40 minutes of heavy usage, I get random system freezes. I am typically running XFree86 and downloading something or reading web pages at the time it happens. More disturbingly, I am occasionally seeing files get renamed, for example /usr/src/UPDATING.64BIT became /usr/src/UPDATING.64BTT. This happens with or without WITNESS, with INVARIANTS enabled, with or without ACPI, and with or without SMP. I am using SCHED_ULE and no PREEMPTION. I had been hoping that I could dump the memory to a partition and get some debugging information from the core using gdb, but it doesn't work. I have a dumpdev setting in my /etc/rc.conf but when the system hangs, it hangs. I recently read about FireWire remote debugging, which sounds pretty cool. I have a desktop PC with FireWire currently running Gentoo Linux. Can someone point me to information about how to do this? I assume that I would need to set up a FreeBSD installation on that machine first? How likely is it that this will provide any useful information for a random system hard lockup? 4) ACPI is not working correctly. ACPI support is incomplete. I can suspend the system with "zzz", but then there is no way to wake it back up. The power button turns the machine on but then it hangs in a CPU loop (I can tell b/c the cooling fan goes on) with a blank screen. Sometimes the output of "apm" gives correct results (good enough for the GNOME battery status applet, although suspending through APM gives a hard freeze), while other times I get this output (giving an empty battery icon for GNOME): APM version: 1.2 APM Management: Disabled AC Line status: on-line Battery Status: charging Remaining battery life: invalid value (0xffffffff) Remaining battery time: unknown Number of batteries: 1 Battery 0: not present 5) DRI is not working. This laptop has a Radeon Mobility 9600 (M10) NP chip (ChipID = 0x4e50), which runs XFree86 using the vesa driver, or with the radeon driver in the XFree86 4.3.99.15 snapshot, which gives me this error: (WW) RADEON(0): Direct rendering not yet supported on Radeon 9500/9700 and newer cards I get no error when loading the radeon kernel module, but no output either, and no drm0 message in dmesg. Is there any possibility that the 9600 will be supported by a future version of XFree86? I have already written ATI suggesting they release a FreeBSD version of their proprietary Linux driver, but they probably won't. Attached output: --------------- Here is the output from /usr/sbin/pciconf -lv: agp0@pci0:0:0: class=0x060000 card=0x122710cf chip=0x06481039 rev=0x51 hdr=0x00 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS648 Host-to-PCI Bridge' class = bridge subclass = HOST-PCI pcib1@pci0:1:0: class=0x060400 card=0x00000000 chip=0x00031039 rev=0x00 hdr=0x01 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS648FX Virtual PCI to PCI Bridge (AGP)' class = bridge subclass = PCI-PCI isab0@pci0:2:0: class=0x060100 card=0x00000000 chip=0x00081039 rev=0x25 hdr=0x00 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS PCI to ISA Bridge (LPC Bridge)' class = bridge subclass = PCI-ISA atapci0@pci0:2:5: class=0x01018a card=0x122b10cf chip=0x55131039 rev=0x00 hdr=0x00 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS5513 EIDE Controller (A,B step)' class = mass storage subclass = ATA none0@pci0:2:6: class=0x070300 card=0x122910cf chip=0x70131039 rev=0xa0 hdr=0x00 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS7013 HSP56 MR, PCtel Serial Wave Device (Modem Riser)' class = simple comms pcm0@pci0:2:7: class=0x040100 card=0x122a10cf chip=0x70121039 rev=0xa0 hdr=0x00 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS7012 PCI Audio Accelerator' class = multimedia subclass = audio ohci0@pci0:3:0: class=0x0c0310 card=0x122b10cf chip=0x70011039 rev=0x0f hdr=0x00 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS5597/8 Universal Serial Bus Controller' class = serial bus subclass = USB ohci1@pci0:3:1: class=0x0c0310 card=0x122b10cf chip=0x70011039 rev=0x0f hdr=0x00 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS5597/8 Universal Serial Bus Controller' class = serial bus subclass = USB none1@pci0:3:2: class=0x0c0320 card=0x122b10cf chip=0x70021039 rev=0x00 hdr=0x00 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS7002 USB 2.0 Enhanced Host Controller' class = serial bus subclass = USB cbb0@pci0:9:0: class=0x060700 card=0x122c10cf chip=0xac8e104c rev=0x00 hdr=0x02 vendor = 'Texas Instruments (TI)' class = bridge subclass = PCI-CardBus cbb1@pci0:9:1: class=0x060700 card=0x122c10cf chip=0xac8e104c rev=0x00 hdr=0x02 vendor = 'Texas Instruments (TI)' class = bridge subclass = PCI-CardBus fwohci0@pci0:9:2: class=0x0c0010 card=0x122d10cf chip=0x802e104c rev=0x00 hdr=0x00 vendor = 'Texas Instruments (TI)' class = serial bus subclass = FireWire none2@pci0:9:3: class=0x018000 card=0x122e10cf chip=0xac8f104c rev=0x00 hdr=0x00 vendor = 'Texas Instruments (TI)' class = mass storage ath0@pci0:10:0: class=0x020000 card=0x123410cf chip=0x0013168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5213 802.11a/b/g Wireless Adapter' class = network subclass = ethernet none3@pci1:0:0: class=0x030000 card=0x122810cf chip=0x4e501002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc.' device = 'Radeon Mobility M10 NP (RV350)' class = display subclass = VGA And here is the boot output from 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.2-CURRENT #2: Tue Jul 20 22:51:21 PDT 2004 root@atheros:/usr/obj/ATHEROS WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (3000.12-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 534708224 (509 MB) avail memory = 517746688 (493 MB) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: [GIANT-LOCKED] acpi0: Power Button (fixed) unknown: I/O range not supported unknown: I/O range not supported acpi_ec0: port 0x66,0x62 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 acpi_tz0: on acpi0 acpi_tz1: on acpi0 acpi_button0: on acpi0 acpi_lid0: on acpi0 acpi_acad0: on acpi0 acpi_cmbat0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe8000000-0xebffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.AGP_ - AE_NOT_FOUND pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 2.0 on pci0 isa0: on isab0 atapci0: port 0x1000-0x100f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 2.5 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at device 2.6 (no driver attached) pcm0: port 0x1800-0x187f,0x1c00-0x1cff irq 11 at device 2.7 on pci0 pcm0: [GIANT-LOCKED] pcm0: ohci0: mem 0xec000000-0xec000fff irq 11 at device 3.0 on pci0 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: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xec001000-0xec001fff irq 11 at device 3.1 on pci0 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: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered pci0: at device 3.2 (no driver attached) cbb0: irq 11 at device 9.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb1: irq 11 at device 9.1 on pci0 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 fwohci0: <1394 Open Host Controller Interface> mem 0xec004000-0xec007fff,0xec003800-0xec003fff irq 11 at device 9.2 on pci0 fwohci0: [GIANT-LOCKED] fwohci0: OHCI version 1.10 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:00:0e:10:00:08:cb:47 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, Not found IRM capable node pci0: at device 9.3 (no driver attached) pci0: at device 10.0 (no driver attached) 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 GlidePoint, device ID 0 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 pmtimer0 on isa0 orm0: at iomem 0xdc000-0xdffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled Timecounter "TSC" frequency 3000117916 Hz quality 800 Timecounters tick every 10.000 msec ad0: 57231MB [116280/16/63] at ata0-master UDMA100 ata1-master: FAILURE - ATAPI_RESET no interrupt acd0: DVDR at ata1-master UDMA33 Mounting root from ufs:/dev/ad0s3a -- Jake Hamby From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 06:43: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 4239716A4CF; Wed, 21 Jul 2004 06:43:14 +0000 (GMT) Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 969EB43D41; Wed, 21 Jul 2004 06:43:13 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from [195.159.6.24] (ws24.ns5.powertech.no [195.159.6.24]) by smtp1.powertech.no (Postfix) with ESMTP id 76FCB809A; Wed, 21 Jul 2004 08:43:12 +0200 (CEST) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <3C1E0353-DAE1-11D8-B5B9-000A95A9A574@nordahl.net> Content-Transfer-Encoding: quoted-printable From: Frode Nordahl Date: Wed, 21 Jul 2004 08:43:11 +0200 To: Robert Watson X-Mailer: Apple Mail (2.618) cc: =?ISO-8859-1?Q?Bj=F6rn_Gr=F6nvall?= cc: re@freebsd.org cc: current@freebsd.org Subject: Re: 5.3-RELEASE TODO 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, 21 Jul 2004 06:43:14 -0000 On Jul 21, 2004, at 02:18, Robert Watson wrote: > > On Wed, 21 Jul 2004, Frode Nordahl wrote: > >> On Jul 16, 2004, at 11:17, Bj=F6rn Gr=F6nvall wrote: >> >>> PR bin/61718 fixes a bunch of bugs in rpc.lockd, please try it. >> >> Yes, rpc.lockd is useless without this patch. >> >> Can someone please commit it? > > It looks like much if not all of it was committed on 20040716; commit > message below. Are any specific things that appear to be missing that > weren't merged? It seems like I jumped the gun here and missed the fact that it was=20 committed not long ago. Sorry about the noise :-/ Mvh, Frode Nordahl > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Principal Research Scientist, McAfee=20 > Research From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 06:48: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 303B116A4D4 for ; Wed, 21 Jul 2004 06:48:37 +0000 (GMT) Received: from max.af.czu.cz (max.af.czu.cz [193.84.41.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8660443D5F for ; Wed, 21 Jul 2004 06:48:35 +0000 (GMT) (envelope-from lists@hosting50.cz) Received: (qmail 66960 invoked by uid 89); 21 Jul 2004 07:05:05 -0000 Received: from unknown (HELO ?193.84.40.30?) (ares@max.af.czu.cz@193.84.40.30) by max.af.czu.cz with AES256-SHA encrypted SMTP; 21 Jul 2004 07:05:05 -0000 From: Tomas Randa To: current@freebsd.org In-Reply-To: References: <1090316789.788.10.camel@ares.af.czu.cz> <1090324596.833.1.camel@ares.af.czu.cz> Content-Type: text/plain Message-Id: <1090392514.2407.18.camel@ares.af.czu.cz> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 21 Jul 2004 08:48:35 +0200 Content-Transfer-Encoding: 7bit Subject: Re: sk0 patch 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, 21 Jul 2004 06:48:37 -0000 Problem is the same, if there is a high load on interface, net card stop working... :( On Tue, 2004-07-20 at 14:21, Bjoern A. Zeeb wrote: > On Tue, 20 Jul 2004, Tomas Randa wrote: > > Hi, > > > Thanks, but patch not working for my > > > > skc0@pci2:9:0: class=0x020000 card=0xe0001458 chip=0x432011ab rev=0x13 > > hdr=0x00 > > vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' > > device = '88E8001 Gigabit 32-bit Ethernet Controller with > > Integrated PHY' > > so what is your problem then ? -- Tomas Randa From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 06:58: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 7D53A16A4CE; Wed, 21 Jul 2004 06:58:40 +0000 (GMT) Received: from mta07-svc.ntlworld.com (mta07-svc.ntlworld.com [62.253.162.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 790C143D31; Wed, 21 Jul 2004 06:58:39 +0000 (GMT) (envelope-from ben@spooty.net) Received: from m52-mp1.cvx3-b.pop.dial.ntli.net ([80.1.84.52]) by mta07-svc.ntlworld.comESMTP <20040721065856.NDTQ20214.mta07-svc.ntlworld.com@m52-mp1.cvx3-b.pop.dial.ntli.net>; Wed, 21 Jul 2004 07:58:56 +0100 From: Ben Paley To: Scott Long Date: Wed, 21 Jul 2004 07:58:53 +0100 User-Agent: KMail/1.6.1 References: <200407202355.41867.ben@spooty.net> <40FDA3D9.7070806@freebsd.org> In-Reply-To: <40FDA3D9.7070806@freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407210758.53856.ben@spooty.net> cc: "freebsd -current@" cc: Robert Watson Subject: Re: vmnet.ko missing - but it's there! - vmware and crashes 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, 21 Jul 2004 06:58:40 -0000 On Tuesday 20 July 2004 23:59, Scott Long wrote: > Recompile the vmnet.ko binary from source and see if that helps. I remade the whole thing, in the end, and now at least I'm not getting crashes (at least, I think I remade the module... I did make and make install and so on in /usr/ports/emulators/vmware3/ , but I couldn't see how to compile vmnet.ko on its own). On boot I still get this: Additional ABI support: linux. Starting cron. Local package initialization:link_elf: symbol linux_ioctl_register_handler undefined kldload: can't load /usr/local/lib/vmware/modules/vmnet.ko: No such file or directory Jul 21 07:41:04 potato kernel: vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-570 (3.2.x mvm) $ vmnet1: Ethernet address: 00:bd:51:0a:00:01 Jul 21 07:41:04 potato kernel: vmmon: Module vmmon: initialized VMwareStarting apache2. mysqld rtc. I guess the link_elf line doesn't look good, is it connected?Vmware starts ok, then when I try to boot the vm I get this: Could not query bridging status on /dev/vmnet1: Invalid argument Failed to configure ethernet0. in a dialog, and this from the console: linux: pid 718 (vmware): ioctl fd=10, cmd=0x8940 ('\x89',64) is not implemented linux: pid 718 (vmware): ioctl fd=10, cmd=0x89f9 ('\x89',249) is not implemented Jul 21 07:43:59 potato kernel: vmmon: Vmx86_ReleaseVM: unlocked pages: 0, unlock ed dirty pages: 0 Thanks a lot for your help, Ben From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 07:04: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 9553416A4CE; Wed, 21 Jul 2004 07:04:27 +0000 (GMT) Received: from pimout3-ext.prodigy.net (pimout3-ext.prodigy.net [207.115.63.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEFFD43D2F; Wed, 21 Jul 2004 07:04:26 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (adsl-68-121-219-69.dsl.snfc21.pacbell.net [68.121.219.69])i6L74MlM184858; Wed, 21 Jul 2004 03:04:24 -0400 Message-ID: <40FE1576.10206@elischer.org> Date: Wed, 21 Jul 2004 00:04:22 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030524 X-Accept-Language: en, hu MIME-Version: 1.0 To: Jake Hamby References: <40FE0DF3.4030008@anobject.com> In-Reply-To: <40FE0DF3.4030008@anobject.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: Using -current on a Fujitsu Lifebook N5010 (no Atheros 802.11, no Ethernet, + hard freezes) 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, 21 Jul 2004 07:04:27 -0000 Jake Hamby wrote: > I recently purchased a new notebook (a Fujitsu Lifebook N5010, a > model which I can highly recommend as a desktop replacement) and > decided to try installing FreeBSD-CURRENT on it instead of Gentoo > Linux, which is the UNIX that I would normally install. Here are > some of the issues I faced in terms of missing kernel support for > this laptop. > > 1) Ethernet chipset not recognized. > > This laptop uses the SiS 648 chipset and includes a 10/100 Ethernet > port with a Realtek 8139-compatible interface. More specifically, it > is vendor id 0x10EC (Realtek), device id 0x8139 on PCI device > 00:07.0, recognized as type 'RTL-8100B/8139D' by the Linux 8139too > driver. > > What is even stranger is that this card shows up in a DOS-based > hardware scan (using AIDA from the Ultimate Boot CD), but not in the > output of pciconf. Nor does it show up in the dmesg output, even as > an unknown device. probably an unsupported bridge between it and the CPU.. I'll let the bus enumeration types handle that.. > > 2) Version of Atheron 802.11a/b/g driver is too old. This is something for sam@freebsd.org. give him a ping. > > With the version of the ath driver in CURRENT, I get this output: > > ath0: [GIANT-LOCKED] ath0: mac 5.6 phy 4.1 5ghz radio 3.6 ath0: > unable to collect channel list from hal device_attach: ath0 attach > returned 22 ath0: mem 0xec010000-0xec01ffff irq 11 at > device 10.0 on pci0 > > The problem is inside of the portion of the code which is delivered > only in binary form. Fortunately for you all, I spent the last five > or six days hacking on it and was able to integrate the latest > version of the Linux Atheros hal code from > http://madwifi.sourceforge.net/, as well as the necessary changes to > the driver code provided as source. You can download my merged > version from here: > > http://www.anobject.com/jehamby/atheros_driver.tar.bz2 > [...] > > * Now uses four transmission queues of varying priority instead of > one: WME_AC_BE (highest), WME_AC_BK, WME_AC_VI, and WME_AC_VO > (lowest). There is code in the Linux version to support QOS and > insert outgoing packets into queue by priority, but I couldn't find > the equivalent of the priority field from Linux's sk_buff struct in > FreeBSD's equivalent ieee80211_frame struct. Currently all outgoing > packets go to WME_AC_BE, except packets of type > IEEE80211_FC0_TYPE_MGT, which go to WME_AC_VO. FreeBSD would store that information in what is called an mbuf tag. A separate small chunk of ram tagged onto teh first mbuf of the packet. This is relatively new and there is only just starting to be some use of it.. Official QOS support in the kernel does not exist yet. (though there are some sporadic users of priority tags here and there it is not general yet.) > [...] > > 3) Random freezes > > After an average of 30-40 minutes of heavy usage, I get random system > freezes. I am typically running XFree86 and downloading something > or reading web pages at the time it happens. More disturbingly, I am > occasionally seeing files get renamed, for example > /usr/src/UPDATING.64BIT became /usr/src/UPDATING.64BTT. This happens > with or without WITNESS, with INVARIANTS enabled, with or without > ACPI, and with or without SMP. I am using SCHED_ULE and no > PREEMPTION. you are not alone.. I think you just chose a bad moment to jump into -current :-/ > > I had been hoping that I could dump the memory to a partition and get > some debugging information from the core using gdb, but it doesn't > work. I have a dumpdev setting in my /etc/rc.conf but when the system > hangs, it hangs. I recently read about FireWire remote debugging, > which sounds pretty cool. I have a desktop PC with FireWire > currently running Gentoo Linux. Can someone point me to information > about how to do this? I assume that I would need to set up a FreeBSD > installation on that machine first? How likely is it that this will > provide any useful information for a random system hard lockup? it's not impossible that it could but it'd behard to knw for sure. Yes youd need a matching FreeBSD system with sources and the debug version of the kernel to use as a source of symbols. > > 4) ACPI is not working correctly. > > ACPI support is incomplete. I can suspend the system with "zzz", but > then there is no way to wake it back up. The power button turns the > machine on but then it hangs in a CPU loop (I can tell b/c the > cooling fan goes on) with a blank screen. Sometimes the output of > "apm" gives correct results (good enough for the GNOME battery status > applet, although suspending through APM gives a hard freeze), while > other times I get this output (giving an empty battery icon for > GNOME): > > APM version: 1.2 APM Management: Disabled AC Line status: on-line > Battery Status: charging Remaining battery life: invalid value > (0xffffffff) Remaining battery time: unknown Number of batteries: 1 > Battery 0: not present > > 5) DRI is not working. > > This laptop has a Radeon Mobility 9600 (M10) NP chip (ChipID = > 0x4e50), which runs XFree86 using the vesa driver, or with the radeon > driver in the XFree86 4.3.99.15 snapshot, which gives me this error: > > (WW) RADEON(0): Direct rendering not yet supported on Radeon > 9500/9700 and newer cards yeah Well that isn't freeBSD specific.. looked at X.org? > > I get no error when loading the radeon kernel module, but no output > either, and no drm0 message in dmesg. Is there any possibility that > the 9600 will be supported by a future version of XFree86? I have > already written ATI suggesting they release a FreeBSD version of > their proprietary Linux driver, but they probably won't. interstingly, if it is a XFree86 "driver" it may work as they are supposed to not use any services outside of the XF86 server. If it is a kernel device driver the, yes the'd need to do a lot of work.. From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 07:05: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 2419A16A4CE; Wed, 21 Jul 2004 07:05:54 +0000 (GMT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10DBB43D46; Wed, 21 Jul 2004 07:05:54 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from [192.168.0.103] (c-24-21-18-195.client.comcast.net[24.21.18.195]) by comcast.net (rwcrmhc12) with SMTP id <2004072107055301400392a2e>; Wed, 21 Jul 2004 07:05:53 +0000 From: Eric Anholt To: Jake Hamby In-Reply-To: <40FE0DF3.4030008@anobject.com> References: <40FE0DF3.4030008@anobject.com> Content-Type: text/plain Message-Id: <1090393551.898.274.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 21 Jul 2004 00:05:52 -0700 Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: Using -current on a Fujitsu Lifebook N5010 (no Atheros 802.11, no Ethernet, + hard freezes) 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, 21 Jul 2004 07:05:54 -0000 On Tue, 2004-07-20 at 23:32, Jake Hamby wrote: > 5) DRI is not working. > > This laptop has a Radeon Mobility 9600 (M10) NP chip (ChipID = 0x4e50), > which runs XFree86 using the vesa driver, or with the radeon driver in > the XFree86 4.3.99.15 snapshot, which gives me this error: > > (WW) RADEON(0): Direct rendering not yet supported on Radeon 9500/9700 > and newer cards > > I get no error when loading the radeon kernel module, but no output > either, and no drm0 message in dmesg. Is there any possibility that the > 9600 will be supported by a future version of XFree86? I have already > written ATI suggesting they release a FreeBSD version of their > proprietary Linux driver, but they probably won't. No r300-series (9500+) Radeons are supported by open-source DRI drivers. Though there's certainly enough will in the community to do it, I'd say, ATI is not yet releasing documentation for these chipsets. ATI has said that they'd work with a FreeBSD developer to help get the driver ported, but I don't know anybody with the motivation to do it. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 07:22:49 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 891FB16A4CE for ; Wed, 21 Jul 2004 07:22:49 +0000 (GMT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0986B43D1F for ; Wed, 21 Jul 2004 07:22:49 +0000 (GMT) (envelope-from marks@dell-laptop.6bone.nl) Received: by postman.ripe.net (Postfix, from userid 8) id 48CB155E59; Wed, 21 Jul 2004 09:21:00 +0200 (CEST) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id DF3F555D1E; Wed, 21 Jul 2004 09:20:59 +0200 (CEST) Received: from dell-laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id i6L7Kx4c003172; Wed, 21 Jul 2004 09:20:59 +0200 Received: (nullmailer pid 896 invoked by uid 1001); Wed, 21 Jul 2004 05:51:59 -0000 Date: Wed, 21 Jul 2004 07:51:58 +0200 From: Mark Santcroos To: Ben Paley Message-ID: <20040721055158.GA791@laptop.6bone.nl> References: <200407202355.41867.ben@spooty.net> <40FDA3D9.7070806@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40FDA3D9.7070806@freebsd.org> User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Status: N 0.000000 / 0.0 / 0.0 / disabled X-RIPE-Signature: 5a2cbd50dedd1691b0b195ec78490612 cc: "freebsd -current@" Subject: Re: vmnet.ko missing - but it's there! - vmware and crashes 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, 21 Jul 2004 07:22:49 -0000 On Tue, Jul 20, 2004 at 04:59:37PM -0600, Scott Long wrote: > >bash-2.05b$ pkg_info | grep vmware > >vmware3-3.2.1.2242_7,1 A virtual machine emulator - a full PC in a window vmware3-3.2.1.2242_8,1 is the latest. So upgrade first (vmware & -current), as the last update was to bring vmware3 in sync with -current again. Mark From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 08:13: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 6540716A4CE for ; Wed, 21 Jul 2004 08:13:13 +0000 (GMT) Received: from freebsd3.cimlogic.com.au (adsl-20-121.swiftdsl.com.au [218.214.20.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 932FF43D2D for ; Wed, 21 Jul 2004 08:13:12 +0000 (GMT) (envelope-from jb@cimlogic.com.au) Received: by freebsd3.cimlogic.com.au (Postfix, from userid 102) id 110256AC0E; Wed, 21 Jul 2004 18:13:11 +1000 (EST) Date: Wed, 21 Jul 2004 18:13:10 +1000 From: John Birrell To: current@freebsd.org Message-ID: <20040721081310.GJ22160@freebsd3.cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: nanosleep returning early 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, 21 Jul 2004 08:13:13 -0000 Today I increased HZ in a current kernel to 1000 when adding dummynet. Now I find that nanosleep regularly comes back a little early. Can anyone explain why? I would have expected that the *overrun* beyond the required time to vary, but never that it would come back early. ------------------ #include #include #include #include int main(int argc,char *argv[]) { struct timespec rmt; struct timespec rqt; struct timeval abstime; struct timeval curtime; gettimeofday(&curtime,NULL); rqt.tv_sec = 5; rqt.tv_nsec = 50000000; abstime.tv_sec = curtime.tv_sec + rqt.tv_sec; abstime.tv_usec = curtime.tv_usec + rqt.tv_nsec / 1000; if (abstime.tv_usec >= 1000000) { abstime.tv_sec += 1; abstime.tv_usec -= 1000000; } printf("curtime %ld.%06ld\n",curtime.tv_sec,curtime.tv_usec); printf("rqt %ld.%09ld\n",(long) rqt.tv_sec,rqt.tv_nsec); if (nanosleep(&rqt,&rmt) != 0) { } else if (gettimeofday(&curtime,NULL) != 0) { } else if (curtime.tv_sec < abstime.tv_sec || (curtime.tv_sec == abstime.tv_sec && curtime.tv_usec < abstime.tv_usec)) { printf("Early: curtime %ld.%06ld abstime %ld.%06ld\n",curtime.tv_sec,curtime.tv_usec,abstime.tv_sec,abstime.tv_usec); } return(0); } ------------------ -- John Birrell From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 08:21: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 7DCAC16A4CE for ; Wed, 21 Jul 2004 08:21:24 +0000 (GMT) Received: from mail018.syd.optusnet.com.au (mail018.syd.optusnet.com.au [211.29.132.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E7B543D46 for ; Wed, 21 Jul 2004 08:21:23 +0000 (GMT) (envelope-from matti@optusnet.com.au) Received: from localhost (c211-30-241-209.rivrw5.nsw.optusnet.com.au [211.30.241.209])i6L8LBD07618 for ; Wed, 21 Jul 2004 18:21:21 +1000 Date: Wed, 21 Jul 2004 18:20:15 +1000 From: matti k To: freebsd-current@freebsd.org Message-Id: <20040721182015.1e00641d.matti@optusnet.com.au> In-Reply-To: References: <1090364563.728.3.camel@klamath.syndrom23.de> X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: FAILURE - ATAPI_RESET no interrupt in newer current 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, 21 Jul 2004 08:21:24 -0000 On Tue, 20 Jul 2004 18:22:29 -0500 (CDT) "Conrad J. Sabatier" wrote: > > The drive works normally, it seems, at least for a while. Last > night, I tried playing a DVD in mplayer, and it worked fine until > the whole machine suddenly hung. Hard to say whether or not this is > an ata/atapi issue, or maybe due to the other, well-known preemption > problem that's being discussed here lately. > I get this "playing a DVD in mplayer" hang on a machine running -current from Sat Jun 19 17:36:01 EST 2004, which I believe pre-dates the preemption stuff. From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 08:23: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 96CDB16A4CE; Wed, 21 Jul 2004 08:23:40 +0000 (GMT) Received: from thekla.de.clara.net (thekla.de.clara.net [212.82.225.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A5E143D2D; Wed, 21 Jul 2004 08:23:37 +0000 (GMT) (envelope-from michael.riexinger@de.clara.net) Received: from localhost.de.clara.net ([127.0.0.1] helo=localhost) by thekla.de.clara.net with esmtp (Exim 4.30; FreeBSD) id 1BnCNo-000INN-9E; Wed, 21 Jul 2004 10:23:24 +0200 Received: from box.int.de.clara.net ([192.168.0.226]) by thekla.de.clara.net with esmtp (Exim 4.30; FreeBSD) id 1BnCNZ-000IH9-Jx; Wed, 21 Jul 2004 10:23:09 +0200 Received: from box.int.de.clara.net (localhost [127.0.0.1]) i6L8NqwU002784; Wed, 21 Jul 2004 10:23:52 +0200 (CEST) (envelope-from michael.riexinger@de.clara.net) Received: (from mriexi@localhost) by box.int.de.clara.net (8.12.11/8.12.10/Submit) id i6L8NqZv002783; Wed, 21 Jul 2004 10:23:52 +0200 (CEST) (envelope-from michael.riexinger@de.clara.net) X-Authentication-Warning: box.int.de.clara.net: mriexi set sender to michael.riexinger@de.clara.net using -f Date: Wed, 21 Jul 2004 10:23:52 +0200 From: Michael Riexinger To: Dan Nelson Message-ID: <20040721082352.GA2005@box.int.de.clara.net> References: <056801c46eb3$bd0e2a40$45fea8c0@turbofresse> <20040721044816.GA56020@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040721044816.GA56020@dan.emsphone.com> User-Agent: Mutt/1.5.6i cc: jesk cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: I/O or Threading Suffer 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, 21 Jul 2004 08:23:40 -0000 On Tue Jul 20 23:48:17 2004, Dan Nelson wrote: > In the last episode (Jul 21), jesk said: > > i figured out that the performanceloss only really occur if the > > process is heavily writing on the filesystem. dd if=/dev/zero > > of=/dev/null bs=128k doesnt hurt much in responsetime of parallel > > processes, but when dd operates on the filesystem with of=foo every > > process will be affect in executiontime. a simple ps or ls meanwhile > > dding onto the disk will be hang for dozen of seconds. > > Ah. now that's a different story. You're out of the control of the > process scheduler and into the disk. I don't suppose you're using an > IDE/ATA disk with no tagged queueing? :) Run "dmesg | grep depth.queue" > to see how many requests can be queued up on your disk at once. > > That dd is stuffing lots of dirty data into the disk cache, and all the > other processes have to wait in line to get their I/Os done. You'll > see much better results from a SCSI disk (with usual queue depths > between 32 and 64), and even better results from a multi-disk hardware > RAID array (which will have a large write cache). Same here. I tried both with IDE and SCSI. With IDE it's terrible, ps for example takes seconds to execute. With an 2 cpu machine with scsi hdd's, it's better but there's some delay, too. I tested on a FreeBSD 4.9 machine with ide disks and there is no delay, it works perfect. That makes FreeBSD-5 really unusable for me. Best regards, Michael Riexinger systems engineer -- claranet gmbh internet service provider tel +49 (0) 69 - 40 80 18 - 300 email: michael.riexinger@de.clara.net http://www.claranet.de/ From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 09:46: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 7442D16A4CF for ; Wed, 21 Jul 2004 09:46:09 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.192]) by mx1.FreeBSD.org (Postfix) with SMTP id 2501B43D5C for ; Wed, 21 Jul 2004 09:46:09 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: by mproxy.gmail.com with SMTP id d19so4594rnf for ; Wed, 21 Jul 2004 02:46:08 -0700 (PDT) Received: by 10.38.59.25 with SMTP id h25mr43648rna; Wed, 21 Jul 2004 02:46:08 -0700 (PDT) Message-ID: Date: Wed, 21 Jul 2004 17:46:08 +0800 From: Jiawei Ye To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Over the top CPU usage with 4BSD scheduler 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, 21 Jul 2004 09:46:09 -0000 last pid: 30765; load averages: 0.89, 0.93, 1.04 up 0+04:06:13 17:43:24 59 processes: 1 running, 58 sleeping CPU states: 13.6% user, 0.0% nice, 10.1% system, 2.3% interrupt, 73.9% idle Mem: 66M Active, 121M Inact, 46M Wired, 9352K Cache, 34M Buf, 648K Free Swap: 512M Total, 69M Used, 442M Free, 13% Inuse PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 30765 root 20 0 175M 13496K kserel 0:29 132.15% 110.35% jar This is a very current kernel (less than 10 hrs old) and also the first time I've seen >100% cpu usage. Is there anything I can help diagnose this? I was compiling jdk14 with native compiler when this happened. Jiawei Ye From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 10:01: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 6D5FD16A4CE for ; Wed, 21 Jul 2004 10:01:50 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.192]) by mx1.FreeBSD.org (Postfix) with SMTP id 1810E43D41 for ; Wed, 21 Jul 2004 10:01:50 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: by mproxy.gmail.com with SMTP id d5so827379rng for ; Wed, 21 Jul 2004 03:01:49 -0700 (PDT) Received: by 10.38.71.36 with SMTP id t36mr87767rna; Wed, 21 Jul 2004 03:01:49 -0700 (PDT) Message-ID: Date: Wed, 21 Jul 2004 18:01:49 +0800 From: Jiawei Ye To: freebsd-java@freebsd.org, freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: weird memory and cpu usage running jdk14 on -current 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, 21 Jul 2004 10:01:50 -0000 I am running a fairly recent -current(Jul21). Just recompiled jdk1.4 and tried to run snipsnap (snipsnap.org). Using top, I see the following numbers: last pid: 34048; load averages: 0.49, 0.25, 0.50 up 0+04:21:12 17:58:23 53 processes: 1 running, 52 sleeping CPU states: 0.0% user, 0.0% nice, 0.8% system, 0.8% interrupt, 98.4% idle Mem: 134M Active, 15M Inact, 63M Wired, 11M Cache, 34M Buf, 20M Free Swap: 512M Total, 54M Used, 458M Free, 10% Inuse PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 34048 leafy 20 0 1644M 114M kserel 0:26 235.72% 231.20% java 1644M is "a lot", but I doubt if it's actually using that much. And the CPU time is just not right. Could anybody shed some light on this? Jiawei Ye From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 10:24:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 874FB16A4CE; Wed, 21 Jul 2004 10:24:24 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.12.11/8.12.11) with ESMTP id i6LAONsP094971; Wed, 21 Jul 2004 06:24:23 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.12.11/8.12.11/Submit) id i6LAOKVw094970; Wed, 21 Jul 2004 06:24:20 -0400 (EDT) (envelope-from green) Date: Wed, 21 Jul 2004 06:24:20 -0400 From: Brian Fundakowski Feldman To: Julian Elischer Message-ID: <20040721102420.GE1009@green.homeunix.org> References: <40FE0DF3.4030008@anobject.com> <40FE1576.10206@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40FE1576.10206@elischer.org> User-Agent: Mutt/1.5.6i cc: Jake Hamby cc: freebsd-mobile@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Using -current on a Fujitsu Lifebook N5010 (no Atheros 802.11, no Ethernet, + hard freezes) 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, 21 Jul 2004 10:24:25 -0000 On Wed, Jul 21, 2004 at 12:04:22AM -0700, Julian Elischer wrote: > Jake Hamby wrote: > > 3) Random freezes > > > > > After an average of 30-40 minutes of heavy usage, I get random system > > freezes. I am typically running XFree86 and downloading something > > or reading web pages at the time it happens. More disturbingly, I am > > occasionally seeing files get renamed, for example > > /usr/src/UPDATING.64BIT became /usr/src/UPDATING.64BTT. This happens > > with or without WITNESS, with INVARIANTS enabled, with or without > > ACPI, and with or without SMP. I am using SCHED_ULE and no > > PREEMPTION. > > you are not alone.. I think you just chose a bad moment to > jump into -current > :-/ Who else is getting random memory corruption? I've only ever seen it in my life with bad RAM/bad cooling, but this could be bad anything, including something spamming random addresses with DMA. The characters 'I' and 'T' are far enough apart such that I wouldn't expect a simple memory error which usually seems to appear as a single bit flip. I don't think this is normal at all. Try burning memtest86 to a floppy or CD to ascertain a a bit more about your hardware, first. If it's a piece of hardware randomly DMAing around, taht's certainly pretty terrible. It would be awesome if someone had a utility to map all of the memory in a running system out into a format showing who allocated it, and what it's doing (contigmalloc, malloc, zone, user, free, cached memory information). I would think if you knew the memory getting corrupted and what was reasonably close to it, you could make some guesses as to what's doing it. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 10:26:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id EDAE916A4CE; Wed, 21 Jul 2004 10:26:23 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.12.11/8.12.11) with ESMTP id i6LAQMMT095008; Wed, 21 Jul 2004 06:26:22 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.12.11/8.12.11/Submit) id i6LAQLfL095007; Wed, 21 Jul 2004 06:26:21 -0400 (EDT) (envelope-from green) Date: Wed, 21 Jul 2004 06:26:20 -0400 From: Brian Fundakowski Feldman To: John Birrell Message-ID: <20040721102620.GF1009@green.homeunix.org> References: <20040721081310.GJ22160@freebsd3.cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040721081310.GJ22160@freebsd3.cimlogic.com.au> User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: nanosleep returning early 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, 21 Jul 2004 10:26:24 -0000 On Wed, Jul 21, 2004 at 06:13:10PM +1000, John Birrell wrote: > > Today I increased HZ in a current kernel to 1000 when adding dummynet. > Now I find that nanosleep regularly comes back a little early. > Can anyone explain why? > > I would have expected that the *overrun* beyond the required time to vary, > but never that it would come back early. Is this a difference from clock_gettime(CLOCK_MONOTONIC)? You really shouldn't be using gettimeofday() foor internal timing since the system clock can be adjusted by NTP. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 10:43: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 A048216A4CE for ; Wed, 21 Jul 2004 10:43:03 +0000 (GMT) Received: from spmler1.mail.eds.com (spmler1.mail.eds.com [194.128.225.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 179CE43D58 for ; Wed, 21 Jul 2004 10:43:03 +0000 (GMT) (envelope-from thomas.sparrevohn@eds.com) Received: from spmlir2.mail.eds.com (spmlir2.mail.eds.com [205.191.69.42] (may be forged))i6LAh1X0015914 for ; Wed, 21 Jul 2004 11:43:01 +0100 Received: from spmlir2.mail.eds.com (localhost [127.0.0.1]) by spmlir2.mail.eds.com (8.12.10/8.12.10) with ESMTP id i6LAg65X010011 for ; Wed, 21 Jul 2004 11:42:06 +0100 Received: from ukspm104.exemhub.exch.eds.com ([204.230.90.155]) by spmlir2.mail.eds.com (8.12.10/8.12.10) with ESMTP id i6LAg6vG009992 for ; Wed, 21 Jul 2004 11:42:06 +0100 Received: by ukspm104.exemhub.exch.eds.com with Internet Mail Service (5.5.2657.72) id <3FT95GFR>; Wed, 21 Jul 2004 11:42:07 +0100 Message-ID: <2946E9F05C8DD511A7DC0002A5608CE401233FCC@gbchm201.exgb01.exch.eds.com> From: "Sparrevohn, Thomas" To: current@freebsd.org Date: Wed, 21 Jul 2004 11:42:03 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain Subject: HP PSC 2510 Scanning 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, 21 Jul 2004 10:43:03 -0000 Hi Does anybody have any idea whether it is possibly to get the HP PSC 2510 (Multi-function Device - FAX/Scanner/Printer) scanner to be recognised from FreeBSD - Under nasty XP is seems to be identified as a USB device but not under FreeBSD - However the printer is identified? From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 10:54: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 810BA16A4CE; Wed, 21 Jul 2004 10:54:46 +0000 (GMT) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A4D743D58; Wed, 21 Jul 2004 10:54:46 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from speck.techno.pagans (c-24-21-241-225.client.comcast.net [24.21.241.225]) by mail.bitfreak.org (Postfix) with ESMTP id 00B9F2A477; Wed, 21 Jul 2004 03:54:45 -0700 (PDT) Received: from spud (spud.techno.pagans [172.21.42.19]) by speck.techno.pagans (Postfix) with ESMTP id 88CB0A968; Wed, 21 Jul 2004 03:52:55 -0700 (PDT) From: "Darren Pilgrim" To: "'Robert Watson'" Date: Wed, 21 Jul 2004 03:54:34 -0700 Message-ID: <000001c46f11$1f53a880$132a15ac@spud> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 cc: 'Matt White' cc: freebsd-current@freebsd.org Subject: RE: fetch hangs, part 2 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, 21 Jul 2004 10:54:46 -0000 > From: Robert Watson [mailto:rwatson@freebsd.org]=20 >=20 >=20 > On Tue, 20 Jul 2004, Darren Pilgrim wrote: >=20 > > I've been having the same (or a similar problem). Fetching the = distfile > > for a port will hang. I poked some more at this and found that all = the > > sites fetch is hanging on successfully negotiate the TCP connection = then > > go dead without closing the connection. My workaround has been to = edit > > the Makefile and remove the offending site from MASTER_SITES or = manually > > fetch from ftp.freebsd.org.=20 >=20 > Could you try disabling TCP SACK Set net.inet.tcp.delayed_ack=3D0? > and see if things "get better"? It's one > of the things that has changed in the TCP code recently. This could = well > be a user space fetch issue, but it would be worth trying it to see, = if > only to rule it out. It didn't change. The connections still hung. From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 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 C09C816A4CE for ; Wed, 21 Jul 2004 11:32:29 +0000 (GMT) Received: from mail.FreeBSD.org.cn (dns3.freebsd.org.cn [61.129.66.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F24A43D5E for ; Wed, 21 Jul 2004 11:32:28 +0000 (GMT) (envelope-from delphij@frontfree.net) Received: (qmail 89902 invoked by uid 0); 21 Jul 2004 11:30:31 -0000 Received: from unknown (HELO beastie.frontfree.net) (219.239.98.7) by mail.FreeBSD.org.cn with AES256-SHA encrypted SMTP; 21 Jul 2004 11:30:31 -0000 Received: from localhost (localhost.frontfree.net [127.0.0.1]) by beastie.frontfree.net (Postfix) with ESMTP id A177511B68; Wed, 21 Jul 2004 19:32:22 +0800 (CST) Received: from beastie.frontfree.net ([127.0.0.1]) by localhost (beastie.frontfree.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01959-01; Wed, 21 Jul 2004 19:32:12 +0800 (CST) Received: by beastie.frontfree.net (Postfix, from userid 1001) id 6564311B3B; Wed, 21 Jul 2004 19:32:11 +0800 (CST) Date: Wed, 21 Jul 2004 19:32:11 +0800 From: Xin LI To: current@FreeBSD.org, phk@FreeBSD.org Message-ID: <20040721113211.GA1899@frontfree.net> 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 X-GPG-key-ID/Fingerprint: 0xCAEEB8C0 / 43B8 B703 B8DD 0231 B333 DC28 39FB 93A0 CAEE B8C0 X-GPG-Public-Key: http://www.delphij.net/delphij.asc X-Operating-System: FreeBSD beastie.frontfree.net 5.2-delphij FreeBSD 5.2-delphij #80: Thu Jun 24 17:30:33 CST 2004 delphij@beastie.frontfree.net:/usr/obj/usr/src/sys/BEASTIE i386 X-URL: http://www.delphij.net X-By: delphij@beastie.frontfree.net X-Location: Beijing, China X-Virus-Scanned: by amavisd-new at frontfree.net Subject: Any idea why timespec* is _KERNEL stuff only? 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, 21 Jul 2004 11:32:29 -0000 --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, Poul-Henning, It seems that rev. 1.23 of sys/sys/time.h has constrained timespec* macros to be _KERNEL (KERNEL in the old days) only. Is this intended? (NetBSD and OpenBSD don't expect _KERNEL for these macros, e.g. timespeccmp, and I personally think that these macros will be better for more generic use, as timespec structure is not _KERNEL protected :-) The _KERNEL related ifdef's could be found in -HEAD's sys/sys/time.h on line 142 and 181. Thanks in advance! Cheers --=20 Xin LI http://www.delphij.net/ See complete headers for GPG key and other information. --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/lQ7OfuToMruuMARAkhhAJ932UN3C75iezkfdZk5oiT9KNzPYgCaA6o+ 64V3dLyt/NlI2ngHT/Dh0fI= =HYqC -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c-- From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 11: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 CB5D416A4D0 for ; Wed, 21 Jul 2004 11:36:51 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 219ED43D48 for ; Wed, 21 Jul 2004 11:36:51 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i6LBajpR082158; Wed, 21 Jul 2004 13:36:46 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Xin LI From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 21 Jul 2004 19:32:11 +0800." <20040721113211.GA1899@frontfree.net> Date: Wed, 21 Jul 2004 13:36:45 +0200 Message-ID: <82157.1090409805@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@FreeBSD.org Subject: Re: Any idea why timespec* is _KERNEL stuff only? 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, 21 Jul 2004 11:36:52 -0000 In message <20040721113211.GA1899@frontfree.net>, Xin LI writes: >Hi, Poul-Henning, > >It seems that rev. 1.23 of sys/sys/time.h has constrained timespec* macros >to be _KERNEL (KERNEL in the old days) only. Is this intended? (NetBSD and >OpenBSD don't expect _KERNEL for these macros, e.g. timespeccmp, and I >personally think that these macros will be better for more generic use, >as timespec structure is not _KERNEL protected :-) I agree. I belive I made the _KERNEL only due to pressure from the standards people or possibly bde@, can't remember to be honest. -- 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 Tue Jul 20 12:33: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 5E7A516A4CE for ; Tue, 20 Jul 2004 12:33:50 +0000 (GMT) Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.157.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id D584C43D45 for ; Tue, 20 Jul 2004 12:33:49 +0000 (GMT) (envelope-from mark@grondar.org) Received: from storm.FreeBSD.org.uk (Ugrondar@localhost [127.0.0.1]) i6KCXmEr019565; Tue, 20 Jul 2004 13:33:48 +0100 (BST) (envelope-from mark@grondar.org) Received: (from Ugrondar@localhost)i6KCXmIg019564; Tue, 20 Jul 2004 13:33:48 +0100 (BST) (envelope-from mark@grondar.org) X-Authentication-Warning: storm.FreeBSD.org.uk: Ugrondar set sender to mark@grondar.org using -f Received: from grondar.org (localhost [127.0.0.1])i6KCNRjo078221; Tue, 20 Jul 2004 13:23:27 +0100 (BST) (envelope-from mark@grondar.org) From: Mark Murray Message-Id: <200407201223.i6KCNRjo078221@grimreaper.grondar.org> To: Scott Long In-Reply-To: Your message of "Tue, 20 Jul 2004 05:37:11 MDT." <40FD03E7.8000300@samsco.org> Date: Tue, 20 Jul 2004 13:23:27 +0100 Sender: mark@grondar.org X-Mailman-Approved-At: Wed, 21 Jul 2004 11:38:15 +0000 cc: jesk cc: freebsd-current@FreeBSD.ORG Subject: Re: I/O or Threading Suffer 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, 20 Jul 2004 12:33:50 -0000 Scott Long writes: > If you are dd'ing from /dev/random, then you are depleting the entropy > pool. Anything else that tries to get random numbers is going to block > in strange ways. Trying just dd'ing from /dev/zero and see if that > makes a difference. For current, there is no such thing as "depleting the entropy pool". At worst, this will make the output generator work hard, consuming CPU cycles. M -- Mark Murray iumop ap!sdn w,I idlaH From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 16:03: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 572D016A4CE; Tue, 20 Jul 2004 16:03:48 +0000 (GMT) Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.157.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id C942843D2F; Tue, 20 Jul 2004 16:03:47 +0000 (GMT) (envelope-from mark@grondar.org) Received: from storm.FreeBSD.org.uk (Ugrondar@localhost [127.0.0.1]) i6KG3kaD022671; Tue, 20 Jul 2004 17:03:46 +0100 (BST) (envelope-from mark@grondar.org) Received: (from Ugrondar@localhost)i6KG3ko9022670; Tue, 20 Jul 2004 17:03:46 +0100 (BST) (envelope-from mark@grondar.org) X-Authentication-Warning: storm.FreeBSD.org.uk: Ugrondar set sender to mark@grondar.org using -f Received: from grondar.org (localhost [127.0.0.1])i6KFsCtW079782; Tue, 20 Jul 2004 16:54:13 +0100 (BST) (envelope-from mark@grondar.org) From: Mark Murray Message-Id: <200407201554.i6KFsCtW079782@grimreaper.grondar.org> To: Robert Watson In-Reply-To: Your message of "Tue, 20 Jul 2004 10:21:40 EDT." Date: Tue, 20 Jul 2004 16:54:12 +0100 Sender: mark@grondar.org X-Mailman-Approved-At: Wed, 21 Jul 2004 11:38:15 +0000 cc: jesk cc: scottl@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG cc: markm@FreeBSD.ORG Subject: Re: I/O or Threading Suffer 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, 20 Jul 2004 16:03:48 -0000 Robert Watson writes: > Mark -- how much > computation is being done here -- would it be worth dropping the Giant > lock during that computation so that the thread can yield without > generating a priority inversion? I'm sure it could. There are some Giant issues related to the UIO stuff that bit me in the bum when I removed the NEEDS_GIANT flag from the device, but I'm reasonably sure that with careful work this can be untangled. M -- Mark Murray iumop ap!sdn w,I idlaH From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 17:03:49 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 BD4CB16A4CE; Tue, 20 Jul 2004 17:03:49 +0000 (GMT) Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.157.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B26443D6A; Tue, 20 Jul 2004 17:03:49 +0000 (GMT) (envelope-from mark@grondar.org) Received: from storm.FreeBSD.org.uk (Ugrondar@localhost [127.0.0.1]) i6KH3mko023420; Tue, 20 Jul 2004 18:03:48 +0100 (BST) (envelope-from mark@grondar.org) Received: (from Ugrondar@localhost)i6KH3l0I023419; Tue, 20 Jul 2004 18:03:47 +0100 (BST) (envelope-from mark@grondar.org) X-Authentication-Warning: storm.FreeBSD.org.uk: Ugrondar set sender to mark@grondar.org using -f Received: from grondar.org (localhost [127.0.0.1])i6KH3J0l080390; Tue, 20 Jul 2004 18:03:19 +0100 (BST) (envelope-from mark@grondar.org) From: Mark Murray Message-Id: <200407201703.i6KH3J0l080390@grimreaper.grondar.org> To: Robert Watson In-Reply-To: Your message of "Tue, 20 Jul 2004 12:39:04 EDT." Date: Tue, 20 Jul 2004 18:03:19 +0100 Sender: mark@grondar.org X-Mailman-Approved-At: Wed, 21 Jul 2004 11:38:15 +0000 cc: jesk cc: freebsd-current@FreeBSD.ORG cc: scottl@FreeBSD.ORG Subject: Re: I/O or Threading Suffer 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, 20 Jul 2004 17:03:49 -0000 Robert Watson writes: > > I'm sure it could. There are some Giant issues related to the UIO stuff > > that bit me in the bum when I removed the NEEDS_GIANT flag from the > > device, but I'm reasonably sure that with careful work this can be > > untangled. > > UIO shouldn't require Giant. Are you sure it still does? EMEMORY It was an issue over (t)sleeping with(out?) a lock held, and replacing the tsleep with a msleep+mutex gave another problem where uiomove() was called with(out?) a mutex held and that was Very Bad(tm). Warner and PHK knew why it was bad; I'm hazy on details. > Are you sure it still does? FYI, I'm not > even thinking you have to mark the whole device driver as not requiring > Giant, just dropping Giant about some of the long running work (and maybe > conditional on the amount of work). For a small random read, it's not > worth it, but for sustained large reads of randomness, it might be > interesting to see what impact it has. We could even consider a yield of > some sort. That sounds easy enough. It may take me a bit of time to get a machine stable enough for testing. Please nag! > Anyhow, up front, it might be sufficient to drop and reacquire giant and > see what impact it has for the test scenario we're currently looking at. Sure. Modulo instability, I'll do it ASAP. M -- Mark Murray iumop ap!sdn w,I idlaH From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 02:12: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 D337616A4CE for ; Wed, 21 Jul 2004 02:12:58 +0000 (GMT) Received: from mailserver.coqui.net (mailserver.coqui.net [196.28.61.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59F1343D2D for ; Wed, 21 Jul 2004 02:12:58 +0000 (GMT) (envelope-from agscontador@coqui.net) Received: (qmail 1074 invoked from network); 21 Jul 2004 02:24:51 +0000 Received: from unknown (HELO mail.coqui.net) ([196.28.61.10]) (envelope-sender ) by mailserver.coqui.net (qmail-ldap-1.03) with SMTP for ; 21 Jul 2004 02:24:51 +0000 Received: from 66-50-95-57.prtc.net(66.50.95.57) by mail.coqui.net via csmap id 7a226764_daba_11d8_827b_00304811b46f_15151; Tue, 20 Jul 2004 22:05:46 -0400 (AST) Message-ID: <000601c46ec8$393dea10$395f3242@AGSContador> From: "Abad Gonzalez Sagardia" To: Date: Tue, 20 Jul 2004 22:12:49 -0400 MIME-Version: 1.0 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 X-NAI-Spam-Score: 0.6 X-Mailman-Approved-At: Wed, 21 Jul 2004 11:38:15 +0000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: BTX Halted (AMD 5x86 133MHz) 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, 21 Jul 2004 02:12:58 -0000 Help me find the configuration for amd 5x86 133 MHz From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 08:40: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 376C016A4CE; Wed, 21 Jul 2004 08:40:13 +0000 (GMT) Received: from mx2.mail.ru (mx2.mail.ru [194.67.23.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEF2B43D4C; Wed, 21 Jul 2004 08:40:12 +0000 (GMT) (envelope-from metal_man@mail.ru) Received: from [217.118.66.254] (port=12894 helo=METALLER) by mx2.mail.ru with smtp id 1BnCe0-0009yj-00; Wed, 21 Jul 2004 12:40:10 +0400 Message-ID: <000501c46efe$56ce0f70$928114ac@METALLER> From: "Dmitriy Startsev" To: References: Date: Wed, 21 Jul 2004 12:40:05 +0400 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.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 FL-Build: Fidolook 2004 (HL) 6.0.2600.32000 - 17/4/2004 06:54:21 X-Spam: Not detected X-Mailman-Approved-At: Wed, 21 Jul 2004 11:38:15 +0000 cc: freebsd-multimedia@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [amd64] Sound breakage with snd_ich 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: Wed, 21 Jul 2004 08:40:13 -0000 Hello, Conrad! You wrote to "Steve Roome" on Tue, 20 Jul 2004 18:32:07 -0500 (CDT): CJS> No, mine uses the nVidia nForce3 chipset: CJS> atapci0: port CJS> 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 8.0 on CJS> pci0 CJS> One oddity that I hadn't previously mentioned is that I can't get UDMA CJS> higher than 100 on this machine. Don't know if that's a limitation of CJS> the drive, or the cable, or what: CJS> ad0: 190782MB [387621/16/63] at ata0-master UDMA100 I have VIA KT400 chipset (which supports UDMA133) and Samsung SP1203N HDD, but can't get UDMA higher than 100 too. It seems to me this is a problem of FreeBSD drivers, not a hardware (under Windows UDMA133 supported without problems). With best regards, Dmitriy Startsev. From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 10:19: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 382CC16A4CE for ; Wed, 21 Jul 2004 10:19:44 +0000 (GMT) Received: from unimail.uni-dortmund.de (mx1.HRZ.Uni-Dortmund.DE [129.217.128.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 742A543D45 for ; Wed, 21 Jul 2004 10:19:43 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from m2a2.myip.org (87pcjf2mc1oaa28t@p5487CA3B.dip.t-dialin.net [84.135.202.59]) (authenticated bits=0)i6LAHu64004286 for ; Wed, 21 Jul 2004 12:18:01 +0200 (CEST) Received: by merlin.emma.line.org (Postfix, from userid 1001) id C3B211B206; Wed, 21 Jul 2004 12:17:55 +0200 (CEST) Date: Wed, 21 Jul 2004 12:17:55 +0200 From: Matthias Andree To: freebsd-current@freebsd.org Message-ID: <20040721101755.GA78370@merlin.emma.line.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-MailScanner-Information: UniDo-UniMail X-MailScanner: Found to be clean X-MailScanner-SpamCheck: not spam, SpamAssassin (Wertung=-4.9, benoetigt 5, BAYES_00, UPPERCASE_25_50) X-MailScanner-From: matthias.andree@gmx.de X-Mailman-Approved-At: Wed, 21 Jul 2004 11:38:15 +0000 Subject: compile failure without WITNESS -- sys/sys/mbuf.h lacks #ifdef WITNESS 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, 21 Jul 2004 10:19:44 -0000 Hi, I've had a kernel compile problem recently, WITNESS_WARN implicitly declared and WARN_GIANTOK and WARN_SLEEPOK undefined. I don't have the WITNESS option enabled for my kernel. I've tracked this down to lines 311ff in sys/sys/mbuf.h, #define MBUF_CHECKSLEEP(how)... Changing these lines to: #ifdef WITNESS #define MBUF_CHECKSLEEP(how) do { \ if (how == M_WAITOK) \ WITNESS_WARN(WARN_GIANTOK | WARN_SLEEPOK, NULL, \ "Sleeping in \"%s\"", __func__); \ } while(0) #else #define MBUF_CHECKSLEEP(how) #endif fixed my problem. -- Matthias Andree From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 11:11: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 3392516A4CE for ; Wed, 21 Jul 2004 11:11:47 +0000 (GMT) Received: from mail.fireshade.net (fireshade.net [195.131.116.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3DA443D2F for ; Wed, 21 Jul 2004 11:11:46 +0000 (GMT) (envelope-from senna@mail.fireshade.net) Received: from misato ([10.0.0.3] ident=Senna) by mail.fireshade.net with esmtp (Exim 4.34; FreeBSD) id 1BkWYN-000Euh-P3 for freebsd-current@freebsd.org; Wed, 14 Jul 2004 03:19:15 +0400 Date: Thu, 15 Jul 2004 03:19:15 +0400 From: Alhov Gennadiy Organization: Fireshade studios X-Priority: 3 (Normal) Message-ID: <189476446828.20040715031915@mail.fireshade.net> To: freebsd-current@freebsd.org In-Reply-To: References: <26075.1089753893@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 21 Jul 2004 11:38:15 +0000 Subject: Re[2]: CVSUP and 5.2.1 RELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: senna List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2004 11:11:47 -0000 Hello Garance, Wednesday, July 14, 2004, 2:23:38 AM, you wrote: GAD> a) how about if we print a warning and exit if DESTDIR is GAD> not defined? Are there "important" uses of `make world' GAD> which do not use DESTDIR? GAD> b) I still don't see how this would be hurt if the target had GAD> a different name. Yes, there is an issue of documentation, GAD> but I still think the following point is important: Wouldn't it be the best to fix 'make world' so it would do exactly what it's expected to? Sorry for my english. -- Good luck, S. mailto:senna@mail.fireshade.net From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 11:46: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 D1D4D16A4CE for ; Wed, 21 Jul 2004 11:46:05 +0000 (GMT) Received: from melusine.cuivre.fr.eu.org (melusine.cuivre.fr.eu.org [82.225.155.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9ADF443D46 for ; Wed, 21 Jul 2004 11:46:05 +0000 (GMT) (envelope-from thomas@FreeBSD.ORG) Received: by melusine.cuivre.fr.eu.org (Postfix, from userid 1000) id B16652C3D1; Wed, 21 Jul 2004 13:46:03 +0200 (CEST) Date: Wed, 21 Jul 2004 13:46:03 +0200 From: Thomas Quinot To: "Oliver B. Fischer" Message-ID: <20040721114603.GA26359@melusine.cuivre.fr.eu.org> References: <40DFDC44.6090101@snafu.de> <20040719210311.GA72395@melusine.cuivre.fr.eu.org> <40FCF591.601@snafu.de> <20040720173944.GA4122@melusine.cuivre.fr.eu.org> <40FD6B84.7050702@snafu.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40FD6B84.7050702@snafu.de> X-message-flag: WARNING! Using Outlook can damage your computer. User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: Obtaining a kernel dump is not 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: Wed, 21 Jul 2004 11:46:05 -0000 * Oliver B. Fischer, 2004-07-20 : > Well, unfortunately my thinkpas doesn't have an serial port... :( Hmmm, OK. One kludgy solution I already saw used in such a case involves a digital camera and taking a snap of the backtrace... -- Thomas.Quinot@Cuivre.FR.EU.ORG From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 12: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 8FCAD16A4D0 for ; Wed, 21 Jul 2004 12:12:22 +0000 (GMT) Received: from mail.FreeBSD.org.cn (dns3.freebsd.org.cn [61.129.66.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D94F43D39 for ; Wed, 21 Jul 2004 12:12:21 +0000 (GMT) (envelope-from delphij@frontfree.net) Received: (qmail 90540 invoked by uid 0); 21 Jul 2004 12:10:27 -0000 Received: from unknown (HELO beastie.frontfree.net) (219.239.98.7) by mail.FreeBSD.org.cn with AES256-SHA encrypted SMTP; 21 Jul 2004 12:10:27 -0000 Received: from localhost (localhost.frontfree.net [127.0.0.1]) by beastie.frontfree.net (Postfix) with ESMTP id 82A8511CA9; Wed, 21 Jul 2004 20:12:18 +0800 (CST) Received: from beastie.frontfree.net ([127.0.0.1]) by localhost (beastie.frontfree.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00982-07; Wed, 21 Jul 2004 20:12:07 +0800 (CST) Received: by beastie.frontfree.net (Postfix, from userid 1001) id 3AB3011C28; Wed, 21 Jul 2004 20:12:07 +0800 (CST) Date: Wed, 21 Jul 2004 20:12:06 +0800 From: Xin LI To: Poul-Henning Kamp Message-ID: <20040721121206.GA746@frontfree.net> References: <20040721113211.GA1899@frontfree.net> <82157.1090409805@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK" Content-Disposition: inline In-Reply-To: <82157.1090409805@critter.freebsd.dk> User-Agent: Mutt/1.4.2.1i X-GPG-key-ID/Fingerprint: 0xCAEEB8C0 / 43B8 B703 B8DD 0231 B333 DC28 39FB 93A0 CAEE B8C0 X-GPG-Public-Key: http://www.delphij.net/delphij.asc X-Operating-System: FreeBSD beastie.frontfree.net 5.2-delphij FreeBSD 5.2-delphij #80: Thu Jun 24 17:30:33 CST 2004 delphij@beastie.frontfree.net:/usr/obj/usr/src/sys/BEASTIE i386 X-URL: http://www.delphij.net X-By: delphij@beastie.frontfree.net X-Location: Beijing, China X-Virus-Scanned: by amavisd-new at frontfree.net cc: freebsd-current@FreeBSD.org Subject: Re: Any idea why timespec* is _KERNEL stuff only? 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, 21 Jul 2004 12:12:22 -0000 --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 21, 2004 at 01:36:45PM +0200, Poul-Henning Kamp wrote: > >Hi, Poul-Henning, > > > >It seems that rev. 1.23 of sys/sys/time.h has constrained timespec* macr= os > >to be _KERNEL (KERNEL in the old days) only. Is this intended? (NetBSD a= nd > >OpenBSD don't expect _KERNEL for these macros, e.g. timespeccmp, and I > >personally think that these macros will be better for more generic use, > >as timespec structure is not _KERNEL protected :-) >=20 > I agree. I belive I made the _KERNEL only due to pressure from the > standards people or possibly bde@, can't remember to be honest. Oh... Shall I ask for a review for a change of the current behavior, or hav= e my own version of timespec* macros in my program, for compability reasons? Cheers, --=20 Xin LI http://www.delphij.net/ See complete headers for GPG key and other information. --YZ5djTAD1cGYuMQK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/l2WOfuToMruuMARAuIjAJ9EHxmhdQwR0cH78mv65XAD/j+wDQCdEj2G Z+OWreaNxhPYi8rQO/81Tgo= =tme3 -----END PGP SIGNATURE----- --YZ5djTAD1cGYuMQK-- From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 12:19: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 66A4216A4CE for ; Wed, 21 Jul 2004 12:19:06 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB92043D58 for ; Wed, 21 Jul 2004 12:19:05 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i6LCJ3Hl082976; Wed, 21 Jul 2004 14:19:03 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Xin LI From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 21 Jul 2004 20:12:06 +0800." <20040721121206.GA746@frontfree.net> Date: Wed, 21 Jul 2004 14:19:03 +0200 Message-ID: <82975.1090412343@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org Subject: Re: Any idea why timespec* is _KERNEL stuff only? 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, 21 Jul 2004 12:19:06 -0000 In message <20040721121206.GA746@frontfree.net>, Xin LI writes: >Oh... Shall I ask for a review for a change of the current behavior, or hav= >e my >own version of timespec* macros in my program, for compability reasons? I belive this is a question for our standards people... I belive they have a mail-list of their own, probably standards@freebsd.org -- 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 Jul 21 12:25: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 1902216A4CE; Wed, 21 Jul 2004 12:25:45 +0000 (GMT) Received: from zombie.ezone.ru (zombie.ezone.ru [195.128.162.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id B992543D3F; Wed, 21 Jul 2004 12:25:41 +0000 (GMT) (envelope-from mcsi@mcsi.pp.ru) Received: from [172.16.4.26] (ultra.domain [172.16.4.26] (may be forged)) by zombie.ezone.ru (8.12.11/8.12.11) with ESMTP id i6LBImvK063531; Wed, 21 Jul 2004 15:18:49 +0400 (MSD) (envelope-from mcsi@mcsi.pp.ru) Message-ID: <40FE5118.3040900@mcsi.pp.ru> Date: Wed, 21 Jul 2004 15:18:48 +0400 From: Maxim Maximov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: Brian Fundakowski Feldman References: <40FE0DF3.4030008@anobject.com> <40FE1576.10206@elischer.org> <20040721102420.GE1009@green.homeunix.org> In-Reply-To: <20040721102420.GE1009@green.homeunix.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Jake Hamby cc: Julian Elischer cc: freebsd-current@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: Using -current on a Fujitsu Lifebook N5010 (no Atheros 802.11, no Ethernet, + hard freezes) 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, 21 Jul 2004 12:25:45 -0000 Brian Fundakowski Feldman wrote: > On Wed, Jul 21, 2004 at 12:04:22AM -0700, Julian Elischer wrote: > >>Jake Hamby wrote: >> >>>3) Random freezes >> >>>After an average of 30-40 minutes of heavy usage, I get random system >>>freezes. I am typically running XFree86 and downloading something >>>or reading web pages at the time it happens. More disturbingly, I am >>>occasionally seeing files get renamed, for example >>>/usr/src/UPDATING.64BIT became /usr/src/UPDATING.64BTT. This happens >>>with or without WITNESS, with INVARIANTS enabled, with or without >>>ACPI, and with or without SMP. I am using SCHED_ULE and no >>>PREEMPTION. >> >>you are not alone.. I think you just chose a bad moment to >>jump into -current >>:-/ > > > Who else is getting random memory corruption? I've only ever seen it > in my life with bad RAM/bad cooling, but this could be bad anything, > including something spamming random addresses with DMA. The characters > 'I' and 'T' are far enough apart such that I wouldn't expect a simple > memory error which usually seems to appear as a single bit flip. What are you guys all smoking? 64BTT stands for "64 bit time_t" http://www.freebsd.org/cgi/cvsweb.cgi/src/UPDATING.64BTT -- Maxim Maximov From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 12:36: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 7F83016A4CE for ; Wed, 21 Jul 2004 12:36:11 +0000 (GMT) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EC9843D62 for ; Wed, 21 Jul 2004 12:36:10 +0000 (GMT) (envelope-from xdivac02@stud.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 i6LCa6p6090537 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 21 Jul 2004 14:36:06 +0200 (CEST) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.12.11/8.12.5/Submit) id i6LCa6B8090536; Wed, 21 Jul 2004 14:36:06 +0200 (CEST) Date: Wed, 21 Jul 2004 14:36:06 +0200 From: Divacky Roman To: Andreas Kohn Message-ID: <20040721123606.GA90043@stud.fit.vutbr.cz> References: <1090364563.728.3.camel@klamath.syndrom23.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1090364563.728.3.camel@klamath.syndrom23.de> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: freebsd-current@freebsd.org Subject: Re: FAILURE - ATAPI_RESET no interrupt in newer current 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, 21 Jul 2004 12:36:11 -0000 On Wed, Jul 21, 2004 at 01:02:43AM +0200, Andreas Kohn wrote: > Hi, > > today I updated my -CURRENT from ~July 5 to July 20 sources. After > reboot with the new kernel, I saw this: > > ata1-master: FAILURE - ATAPI_RESET no interrupt > acd0: CDRW at ata1-master WDMA2 > > With the old kernel, die FAILURE message was not there, but the acd0 was > running in WDMA2 mode as well. > > This is a > atapci0: port > 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0 > controller. > > Is this message to be expected, or should I worry about anything? > > Regards, > Andreas Kohn via8235 ata controller was marked as AST broken and doesnt not get timing set anymore... I am not sure whtere this is correct - linux does so... anyway - if its bening dont worry ;) roman From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 12:43: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 8FFDA16A4CE for ; Wed, 21 Jul 2004 12:43:26 +0000 (GMT) Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57CA443D1F for ; Wed, 21 Jul 2004 12:43:26 +0000 (GMT) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (localhost [127.0.0.1]) i6LChQSn007783 for ; Wed, 21 Jul 2004 05:43:26 -0700 (PDT) (envelope-from david@bunrab.catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.12.11/8.12.11/Submit) id i6LChPdo007782 for freebsd-current@freebsd.org; Wed, 21 Jul 2004 05:43:26 -0700 (PDT) (envelope-from david) Date: Wed, 21 Jul 2004 05:43:26 -0700 (PDT) From: David Wolfskill Message-Id: <200407211243.i6LChPdo007782@bunrab.catwhisker.org> Cc: freebsd-current@freebsd.org In-Reply-To: <82975.1090412343@critter.freebsd.dk> Subject: Re: Any idea why timespec* is _KERNEL stuff only? 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, 21 Jul 2004 12:43:26 -0000 >To: Xin LI >From: "Poul-Henning Kamp" >Date: Wed, 21 Jul 2004 14:19:03 +0200 >Cc: freebsd-current@freebsd.org >Subject: Re: Any idea why timespec* is _KERNEL stuff only? >Sender: owner-freebsd-current@freebsd.org >>Oh... Shall I ask for a review for a change of the current behavior, or hav= >>e my >>own version of timespec* macros in my program, for compability reasons? >I belive this is a question for our standards people... I belive they >have a mail-list of their own, probably standards@freebsd.org Correct. Peace, david (current hat: postmaster@freebsd.org) -- David H. Wolfskill david@catwhisker.org I do not "unsubscribe" from email "services" to which I have not explicitly subscribed. Rather, I block spammers' access to SMTP servers I control, and encourage others who are in a position to do so to do likewise. From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 12:49: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 66E5516A4D7 for ; Wed, 21 Jul 2004 12:49:11 +0000 (GMT) Received: from kayjay.xs4all.nl (kayjay.xs4all.nl [80.126.33.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7246E43D68 for ; Wed, 21 Jul 2004 12:49:10 +0000 (GMT) (envelope-from karelj@kayjay.xs4all.nl) Received: from kayjay.xs4all.nl (localhost.kayjay.xs4all.nl [127.0.0.1]) by kayjay.xs4all.nl (8.12.11/8.12.11) with ESMTP id i6LCn83x069137 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Wed, 21 Jul 2004 14:49:08 +0200 (CEST) (envelope-from karelj@kayjay.xs4all.nl) Received: (from karelj@localhost) by kayjay.xs4all.nl (8.12.11/8.12.11/Submit) id i6LCn8nn069136 for freebsd-current@freebsd.org; Wed, 21 Jul 2004 14:49:08 +0200 (CEST) (envelope-from karelj) Date: Wed, 21 Jul 2004 14:49:08 +0200 From: "Karel J. Bosschaart" To: freebsd-current@freebsd.org Message-ID: <20040721124907.GA69115@kayjay.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.4.2.1i Subject: panic: sched_rem: KSE not on run queue 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, 21 Jul 2004 12:49:11 -0000 Hi, Running -current as of yesterday (07/20), GENERIC kernel. Hangs happen frequently on this machine (about 5 times a day). I got a crash dump, would= =20 it be useful to someone? Karel. Script started on Wed Jul 21 14:31:57 2004 phys9911# gdb6 -k /=08=1B[Kkernel.debug /usr/crash/vmcore.8=0D=0D GNU gdb 20040720 [GDB v6.x for FreeBSD]=0D Copyright 2004 Free Software Foundation, Inc.=0D GDB is free software, covered by the GNU General Public License, and you ar= e=0D welcome to change it and/or distribute copies of it under certain condition= s.=0D Type "show copying" to see the conditions.=0D There is absolutely no warranty for GDB. Type "show warranty" for details.= =0D This GDB was configured as "i386-portbld-freebsd5.2"...=0D panic: sched_rem: KSE not on run queue=0D panic messages:=0D ---=0D panic: sched_rem: KSE not on run queue=0D cpuid =3D 0; =0D KDB: enter: panic=0D panic: from debugger=0D cpuid =3D 0; =0D Uptime: 2h31m58s=0D Dumping 247 MB=0D 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240=0D ---=0D #0 doadump () at pcpu.h:159=0D 159 __asm __volatile("movl %%fs:0,%0" : "=3Dr" (td));=0D doadump () at pcpu.h:159=0D 159 __asm __volatile("movl %%fs:0,%0" : "=3Dr" (td));=0D Ready to go. Enter 'tr' to connect to the remote target=0D with /dev/cuaa0, 'tr /dev/cuaa1' to connect to a different port=0D or 'trf portno' to connect to the remote target with the firewire=0D interface. portno defaults to 5556.=0D =0D Type 'getsyms' after connection to load kld symbols.=0D =0D If you're debugging a local system, you can use 'kldsyms' instead=0D to load the kld symbols. That's a less obnoxious interface.=0D (kgdb) bt=0D #0 doadump () at pcpu.h:159=0D During symbol reading, Incomplete CFI data; unspecified registers at 0xc05e= fc28.=0D #1 0xc05f0154 in boot (howto=3D0x104) at /usr/src/sys/kern/kern_shutdown.c= :392=0D #2 0xc05f046b in panic (fmt=3D0xc079ef47 "from debugger") at /usr/src/sys/= kern/kern_shutdown.c:554=0D #3 0xc045eb71 in db_panic (addr=3D0xc0606c3f, have_addr=3D0x0, count=3D0xf= fffffff, modif=3D0xd4f84a78 "")=0D at /usr/src/sys/ddb/db_command.c:434=0D #4 0xc045eb08 in db_command (last_cmdp=3D0xc0875724, cmd_table=3D0x0, aux_= cmd_tablep=3D0xc07f6c34, =0D aux_cmd_tablep_end=3D0xc07f6c4c) at /usr/src/sys/ddb/db_command.c:348=0D #5 0xc045ebd0 in db_command_loop () at /usr/src/sys/ddb/db_command.c:454=0D #6 0xc04604a5 in db_trap (type=3D0x3, code=3D0x0) at /usr/src/sys/ddb/db_m= ain.c:219=0D #7 0xc0606e99 in kdb_trap (type=3D0x3, code=3D0x0, tf=3D0xd4f84bbc) at /us= r/src/sys/kern/subr_kdb.c:387=0D #8 0xc076ad04 in trap (frame=3D=0D {tf_fs =3D 0xd4f80018, tf_es =3D 0xc0600010, tf_ds =3D 0xc07d0010, tf= _edi =3D 0xc07d3b55, tf_esi =3D 0x1, tf_ebp =3D 0xd4f84bfc, tf_isp =3D 0xd4= f84be8, tf_ebx =3D 0xd4f84c28, tf_edx =3D 0x0, tf_ecx =3D 0xc1014000, tf_ea= x =3D 0x12, tf_trapno =3D 0x3, tf_err =3D 0x0, tf_eip =3D 0xc0606c3f, tf_cs= =3D 0x8, tf_eflags =3D 0x86, tf_esp =3D 0xd4f84c1c, tf_ss =3D 0xc05f041d})= =0D at /usr/src/sys/i386/i386/trap.c:576=0D #9 0xc0759a7a in calltrap () at /usr/src/sys/i386/i386/exception.s:140=0D #10 0xd4f80018 in ?? ()=0D #11 0xc0600010 in sched_runnable () at /usr/src/sys/kern/sched_ule.c:1492=0D #12 0xc05f041d in panic (fmt=3D0xc07d3b55 "sched_rem: KSE not on run queue"= ) at /usr/src/sys/kern/kern_shutdown.c:538=0D #13 0xc060045a in sched_rem (td=3D0x0) at /usr/src/sys/kern/sched_ule.c:166= 8=0D #14 0xc05f5671 in setrunqueue (td=3D0xc2056b00) at /usr/src/sys/kern/kern_s= witch.c:362=0D #15 0xc05ffb1e in sched_wakeup (td=3D0xc2056b00) at /usr/src/sys/kern/sched= _ule.c:1251=0D #16 0xc05f68b8 in setrunnable (td=3D0xc2056b00) at /usr/src/sys/kern/kern_s= ynch.c:408=0D #17 0xc060c45a in sleepq_resume_thread (td=3D0xc2056b00, pri=3D0xffffffff) = at /usr/src/sys/kern/subr_sleepqueue.c:632=0D #18 0xc060c4f4 in sleepq_signal (wchan=3D0xc18ee7dc, flags=3D0xc2056b00, pr= i=3D0xffffffff)=0D at /usr/src/sys/kern/subr_sleepqueue.c:662=0D #19 0xc05f65a7 in wakeup_one (ident=3D0xc18ee7dc) at /usr/src/sys/kern/kern= _synch.c:278=0D #20 0xc05e167b in thread_userret (td=3D0xc1efa000, frame=3D0xd4f84d48) at /= usr/src/sys/kern/kern_kse.c:1191=0D #21 0xc060d410 in userret (td=3D0xc1efa000, frame=3D0xd4f84d48, oticks=3D0x= 0) at /usr/src/sys/kern/subr_trap.c:118=0D #22 0xc076ad9c in trap (frame=3D=0D {tf_fs =3D 0xbfbf002f, tf_es =3D 0x280c002f, tf_ds =3D 0xbfbf002f, tf= _edi =3D 0x280bbf00, tf_esi =3D 0x2c4c0ae0, tf_ebp =3D 0xbfbfd424, tf_isp = =3D 0xd4f84d74, tf_ebx =3D 0x2c4c0bac, tf_edx =3D 0x13, tf_ecx =3D 0x292c02= 2c, tf_eax =3D 0x2c2c233c, tf_trapno =3D 0xc, tf_err =3D 0x4, tf_eip =3D 0x= 2c2c1fe0, tf_cs =3D 0x1f, tf_eflags =3D 0x10286, tf_esp =3D 0xbfbfd408, tf_= ss =3D 0x2f})=0D at /usr/src/sys/i386/i386/trap.c:635=0D #23 0xc0759a7a in calltrap () at /usr/src/sys/i386/i386/exception.s:140=0D #24 0xbfbf002f in ?? ()=0D #25 0x280c002f in ?? ()=0D #26 0xbfbf002f in ?? ()=0D #27 0x280bbf00 in ?? ()=0D #28 0x2c4c0ae0 in ?? ()=0D #29 0xbfbfd424 in ?? ()=0D #30 0xd4f84d74 in ?? ()=0D #31 0x2c4c0bac in ?? ()=0D #32 0x00000013 in ?? ()=0D #33 0x292c022c in ?? ()=0D #34 0x2c2c233c in ?? ()=0D #35 0x0000000c in ?? ()=0D #36 0x00000004 in ?? ()=0D #37 0x2c2c1fe0 in ?? ()=0D #38 0x0000001f in ?? ()=0D #39 0x00010286 in ?? ()=0D #40 0xbfbfd408 in ?? ()=0D #41 0x0000002f in ?? ()=0D #42 0x00046a3c in ?? ()=0D #43 0x00000008 in ?? ()=0D #44 0x00046a44 in ?? ()=0D #45 0x00000008 in ?? ()=0D #46 0x08a8e000 in ?? ()=0D #47 0xc150a580 in ?? ()=0D #48 0xc18e9ba0 in ?? ()=0D #49 0xd4f84ae8 in ?? ()=0D #50 0xd4f84ad0 in ?? ()=0D #51 0xc1efa000 in ?? ()=0D #52 0xc05ff943 in sched_switch (td=3D0x2c4c0bac, newtd=3D0x280bbf00) at /us= r/src/sys/kern/sched_ule.c:1172=0D Previous frame inner to this frame (corrupt stack?)=0D (kgdb) quit=0D phys9911# exit=0D=0D exit=0D Script done on Wed Jul 21 14:32:34 2004 From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 13: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 A2CFD16A4CE; Wed, 21 Jul 2004 13:01:25 +0000 (GMT) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 254AC43D53; Wed, 21 Jul 2004 13:01:25 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86])i6LD1N4u010287; Wed, 21 Jul 2004 23:01:23 +1000 Received: from epsplex.bde.org (katana.zip.com.au [61.8.7.246]) i6LD1Kao015911; Wed, 21 Jul 2004 23:01:21 +1000 Date: Wed, 21 Jul 2004 23:01:20 +1000 (EST) From: Bruce Evans X-X-Sender: bde@epsplex.bde.org To: Brian Fundakowski Feldman In-Reply-To: <20040721102620.GF1009@green.homeunix.org> Message-ID: <20040721220405.Y2346@epsplex.bde.org> References: <20040721081310.GJ22160@freebsd3.cimlogic.com.au> <20040721102620.GF1009@green.homeunix.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: nanosleep returning early 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, 21 Jul 2004 13:01:25 -0000 On Wed, 21 Jul 2004, Brian Fundakowski Feldman wrote: > On Wed, Jul 21, 2004 at 06:13:10PM +1000, John Birrell wrote: > > > > Today I increased HZ in a current kernel to 1000 when adding dummynet. > > Now I find that nanosleep regularly comes back a little early. > > Can anyone explain why? The most obvious bug is that nanosleep() uses the low-accuracy interface getnanouptime(). I can't see why the the problem is more obvious with large HZ or why it affects short sleeps. From kern_time.c 1.170: % static int % nanosleep1(struct thread *td, struct timespec *rqt, struct timespec *rmt) % { % struct timespec ts, ts2, ts3; % struct timeval tv; % int error; % % if (rqt->tv_nsec < 0 || rqt->tv_nsec >= 1000000000) % return (EINVAL); % if (rqt->tv_sec < 0 || (rqt->tv_sec == 0 && rqt->tv_nsec == 0)) % return (0); % getnanouptime(&ts); This may lag the actual (up)time by 1/HZ seconds. % timespecadd(&ts, rqt); So we get a final time that may be 1/HZ seconds too small. % TIMESPEC_TO_TIMEVAL(&tv, rqt); Rounding to microseconds doesn't make much difference since things take on the order of 1uS. % for (;;) { % error = tsleep(&nanowait, PWAIT | PCATCH, "nanslp", % tvtohz(&tv)); We only converted to a timeval so that we could use tvtohz() here. tvtohz() rounds up to the tick boundary after the next one to allow for the 1/HZ resolution of tsleep(). This should also mask the inaccuracy of getnanouptime() unless the sleep returns early due to a signal -- in the usual case of not very long sleeps that are not killed by a signal, the tsleep() guarantees sleeping long enough and sleeps (1/2*1/HZ) extra on average. % getnanouptime(&ts2); % if (error != EWOULDBLOCK) { % if (error == ERESTART) % error = EINTR; % if (rmt != NULL) { % timespecsub(&ts, &ts2); % if (ts.tv_sec < 0) % timespecclear(&ts); % *rmt = ts; This handles the case of being killed by a signal. Then we always return early, and the bug is just that returned time-not-slept is innacurate. % } % return (error); % } % if (timespeccmp(&ts2, &ts, >=)) % return (0); This handles the case where the timeout expires. We check that the specified sleep time has expired, not just that some number of ticks expired, since the latter may be too short for long sleeps even after rounding it up. % ts3 = ts; % timespecsub(&ts3, &ts2); % TIMESPEC_TO_TIMEVAL(&tv, &ts3); Errors may accumulate (or cancel?) for the next iteration. % } % } > > I would have expected that the *overrun* beyond the required time to vary, > > but never that it would come back early. > > Is this a difference from clock_gettime(CLOCK_MONOTONIC)? You really > shouldn't be using gettimeofday() foor internal timing since the > system clock can be adjusted by NTP. The monotonic clock can also be adjusted by NTP, and normally is if there are any NTP adjustments at all (the uptime and the time use the same timecounter which is adjusted by NTP). NTP's adjustments are only limited to CLOCK_REALTIME when NTP steps the clock for initialization. Stepping the clock causes other time warps and should never be used. Bruce From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 13:37: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 0CEEF16A4CE; Wed, 21 Jul 2004 13:37:45 +0000 (GMT) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77A4B43D54; Wed, 21 Jul 2004 13:37:44 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86])i6LDbg4u014338; Wed, 21 Jul 2004 23:37:42 +1000 Received: from epsplex.bde.org (katana.zip.com.au [61.8.7.246]) i6LDbeao018604; Wed, 21 Jul 2004 23:37:41 +1000 Date: Wed, 21 Jul 2004 23:37:40 +1000 (EST) From: Bruce Evans X-X-Sender: bde@epsplex.bde.org To: Xin LI In-Reply-To: <20040721113211.GA1899@frontfree.net> Message-ID: <20040721232310.Y2587@epsplex.bde.org> References: <20040721113211.GA1899@frontfree.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Any idea why timespec* is _KERNEL stuff only? 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, 21 Jul 2004 13:37:45 -0000 On Wed, 21 Jul 2004, Xin LI wrote: > Hi, Poul-Henning, > > It seems that rev. 1.23 of sys/sys/time.h has constrained timespec* macros > to be _KERNEL (KERNEL in the old days) only. Is this intended? (NetBSD and Yes, this is intended. The timeval and timespec interfaces are optimized for handling times in code that can't use 64-bit integers or floating point (mainly in 20 year old kernels). New interfaces to manipulate them should not be added 20 years after the interfaces should have been deprecated. > OpenBSD don't expect _KERNEL for these macros, e.g. timespeccmp, and I > personally think that these macros will be better for more generic use, NetBSD and OpenBSD originally only had timeval*(), and FreeBSD unfortunately had to add them to be compatible. timespec*() seem to be even less needed in userland than timeval*(), since no ports are broken by not having them. > as timespec structure is not _KERNEL protected :-) The timespec struct is POSIX standard. POSIX has the correct number of functions for operating on timespec structs (none). Bruce From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 13:45: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 5709F16A4CE for ; Wed, 21 Jul 2004 13:45:53 +0000 (GMT) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29FE743D49 for ; Wed, 21 Jul 2004 13:45:53 +0000 (GMT) (envelope-from Jan.Grant@bristol.ac.uk) Received: from mail.ilrt.bris.ac.uk ([137.222.16.62]) by dirg.bris.ac.uk with esmtp (Exim 4.34) id 1BnHPo-0004vI-Hz; Wed, 21 Jul 2004 14:45:49 +0100 Received: from cmjg (helo=localhost) by mail.ilrt.bris.ac.uk with local-esmtp (Exim 4.34) id 1BnHOk-0004RA-HY; Wed, 21 Jul 2004 14:44:42 +0100 Date: Wed, 21 Jul 2004 14:44:42 +0100 (BST) From: Jan Grant X-X-Sender: cmjg@mail.ilrt.bris.ac.uk To: Stefan Bethke In-Reply-To: Message-ID: References: <40F963D8.6010201@freebsd.org> <20040719060730.GA87697@nagual.pp.ru> <20040720081051.GB3001@cirb503493.alcatel.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: Jan Grant X-Spam-Score: 0.0 X-Spam-Level: / cc: Peter Jeremy cc: current@freebsd.org Subject: Re: NEW TAR 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, 21 Jul 2004 13:45:53 -0000 On Tue, 20 Jul 2004, Stefan Bethke wrote: > Am 20.07.2004 um 10:10 schrieb Peter Jeremy: > >> Actually, it's not possible to accurately determine the holes in a >> file by reading it - you can't differentiate between a hole and a >> allocated block of zeroes. What you need is a (new) syscall that >> invokes a new VOP_... and returns a bitmap of allocated blocks. This >> would be non-trival unfortunately. > > This one point that has been made a number of times in the past, and one I > don't understand: > > There are no sparse files as far as the userland is concerned; it's an > optimization that remains invisible, apart from space and/or performance > savings. > > For the extraction process, it should be sufficient to seek over any extended > range of zeros. When packaging files that might have holes in them, it'll > certainly be nice if there was a way to skip reading all those zeros in, but > that's just an optimization. > > The way you describe it (and others have before), it sounds like the holes > were an attribute of the file that should be preserved by tar (or any other > archiver); I believe it's not. Preserving them in the way your post can be > read is problematic: what if the block/allocation/cluster/fragment size of > the extraction target differs from the source? How far would you need to > acertain compatible allocation semantics between both filesystems? > > Since this has come up multiple times in the past, I feel I'm missing some > important detail, and I'd appreciate if someone would enlighten me. You're correct, in that filesystem semantics don't require an archiver to recreate holes. There are storage efficiency gains to be made in identifying holes, that's true - particularly in the case of absolutely whopping but extremely sparse files. In those cases, a simple userland-view-of-the-filesystem-semantics approach to ideentifying areas that _might_ be holes (just for archive efficiency) can still be expensive and might involve the scanning of multiple gigabytes of "virtual" zeroes. Solaris offers an fcntl to identify holes (IIRC) for just this purpose. If the underlying filesystem can't be made to support it, there's an efficiency loss but otherwise it's no great shakes. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/ Prolog in JavaScript: http://ioctl.org/logic/prolog-latest From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 14:14: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 3327716A4CE for ; Wed, 21 Jul 2004 14:14:29 +0000 (GMT) Received: from mail.FreeBSD.org.cn (dns3.freebsd.org.cn [61.129.66.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EE0643D46 for ; Wed, 21 Jul 2004 14:14:26 +0000 (GMT) (envelope-from delphij@frontfree.net) Received: (qmail 92394 invoked by uid 0); 21 Jul 2004 14:12:28 -0000 Received: from unknown (HELO beastie.frontfree.net) (219.239.98.7) by mail.FreeBSD.org.cn with AES256-SHA encrypted SMTP; 21 Jul 2004 14:12:28 -0000 Received: from localhost (localhost.frontfree.net [127.0.0.1]) by beastie.frontfree.net (Postfix) with ESMTP id BD29011C50; Wed, 21 Jul 2004 22:14:19 +0800 (CST) Received: from beastie.frontfree.net ([127.0.0.1]) by localhost (beastie.frontfree.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00139-04; Wed, 21 Jul 2004 22:14:09 +0800 (CST) Received: by beastie.frontfree.net (Postfix, from userid 1001) id 5B92E11941; Wed, 21 Jul 2004 22:14:08 +0800 (CST) Date: Wed, 21 Jul 2004 22:14:08 +0800 From: Xin LI To: Terry Lambert Message-ID: <20040721141408.GB1965@frontfree.net> References: <27293807.1090238549091.JavaMail.root@wamui01.slb.atl.earthlink.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UHN/qo2QbUvPLonB" Content-Disposition: inline In-Reply-To: <27293807.1090238549091.JavaMail.root@wamui01.slb.atl.earthlink.net> User-Agent: Mutt/1.4.2.1i X-GPG-key-ID/Fingerprint: 0xCAEEB8C0 / 43B8 B703 B8DD 0231 B333 DC28 39FB 93A0 CAEE B8C0 X-GPG-Public-Key: http://www.delphij.net/delphij.asc X-Operating-System: FreeBSD beastie.frontfree.net 5.2-delphij FreeBSD 5.2-delphij #80: Thu Jun 24 17:30:33 CST 2004 delphij@beastie.frontfree.net:/usr/obj/usr/src/sys/BEASTIE i386 X-URL: http://www.delphij.net X-By: delphij@beastie.frontfree.net X-Location: Beijing, China X-Virus-Scanned: by amavisd-new at frontfree.net cc: current@FreeBSD.org Subject: Re: About ISC-cron 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, 21 Jul 2004 14:14:29 -0000 --UHN/qo2QbUvPLonB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, Terry, On Mon, Jul 19, 2004 at 05:02:28AM -0700, Terry Lambert wrote: > Xin LI wrote: > > I have Google'd the mailing list and found no discussion explaining why > > we have not upgraded our cron and friends. Is there any discussion I > > have missed? In other words, should I make these work a port, or a diff > > against src/, when I have finished the whole thing? >=20 > Be careful that you do not bring back a historical Berkley DB > problem that used to bite people using cron. Is this in the ncvs tree, or was corrected even earlier? If the former I think I will be able to take good care for that. Also, a regression test case which can reproduce the bug would be helpful, too :-) Thanks for taking the issue into my attention! Cheers, --=20 Xin LI http://www.delphij.net/ See complete headers for GPG key and other information. --UHN/qo2QbUvPLonB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/nowOfuToMruuMARAqCVAJ0bjmOV1qJx4ALTG8ojtT6r4Rb0zQCeK069 qp25d1A7IN51TVr29s4bbvg= =uwl4 -----END PGP SIGNATURE----- --UHN/qo2QbUvPLonB-- From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 14:41: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 7424516A4CE for ; Wed, 21 Jul 2004 14:41:04 +0000 (GMT) Received: from parati.mdbrasil.com.br (parati.mdbrasil.com.br [200.210.70.4]) by mx1.FreeBSD.org (Postfix) with SMTP id 2EEAB43D55 for ; Wed, 21 Jul 2004 14:41:03 +0000 (GMT) (envelope-from jmelo-lists@freebsdbrasil.com.br) Received: (qmail 24649 invoked by uid 0); 21 Jul 2004 14:41:49 -0000 Received: from jmelo-lists@freebsdbrasil.com.br by parati.mdbrasil.com.br by uid 82 with qmail-scanner-1.20rc1 (uvscan: v4.1.60/v4288. Clear:RC:1:. Processed in 0.075842 secs); 21 Jul 2004 14:41:49 -0000 Received: from unknown (HELO ?192.168.1.2?) (200.167.244.39) by parati.mdbrasil.com.br with SMTP; 21 Jul 2004 11:41:48 -0300 From: Jean Milanez Melo To: Patrick Gardella In-Reply-To: <560B44B6-DB0D-11D8-9966-000A95CE1ECE@intothewind.cx> References: <1090338524.783.3.camel@offset.freebsdbrasil.com.br> <560B44B6-DB0D-11D8-9966-000A95CE1ECE@intothewind.cx> Content-Type: text/plain Organization: FreeBSD Brasil LTDA Message-Id: <1090421434.593.3.camel@offset.freebsdbrasil.com.br> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 21 Jul 2004 11:50:34 -0300 Content-Transfer-Encoding: 7bit cc: "current@freebsd.org" Subject: Re: FreeBSD embedded: TinyBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jmelo-lists@freebsdbrasil.com.br List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2004 14:41:04 -0000 On Wed, 2004-07-21 at 08:58, Patrick Gardella wrote: > Is there a web page for TinyBSD? > > patrick Not yet, but we're going to make one if people like the project and it gets well accepted by the community. We're definatelly putting up a lot of documentation on that page, though. We haven't done so yet because currently it's way too simple, as you can run it knowing only the information regarding the target device. For example, assuming a 32MB flash memory, one could use the following parameters to create an embedded system: ./tinybsd.sh 62592 4 32 Or optionally the name of the output image you want: ./tinybsd.sh 62592 4 32 myimage.bin - Jean Milanez Melo > > On Jul 20, 2004, at 11:48 AM, Jean Milanez Melo wrote: > > > Hello current, > > > > Please allow me to introduce myself, I'm one of the coordinators of > > the Brazilian FreeBSD Users group, coordinator of the official > > FreeBSD documentation's translation group and have been working with > > embedded FreeBSD systems since year 2000. > > > > I've been studying NanoBSD ever since Poul-Henning posted about it > > on one of > > the mailling lists, and I have been following this project closely. > > It > > really is a great project. > > > > However, I think it sometimes creates unnecessary partitions, takes > > too long to build the system due to make world and it copies lots of > > unneeded binaries, taking a lot of precious space. > > > > So me and Patrick Tracanelli (another active member of the Brazilian > > FreeBSD community) decided to write a new set of scripts to build > > embedded systems. We've named it TinyBSD, and its goal is to be > > faster > > at building-time, occupy less space on the target device and to ease > > customization like PicoBSD does. > > > > Untar/gzip the tinybsd.tgz file under /usr/src/release. > > > > # ls > > TINYBSD TODO tinybsd.basefiles tinybsd.sh > > > > We first take the file TINYBSD, which like in PicoBSD we can use to > > define or remove all kernel options to the new system. > > > > Then we have tinybsd.basefiles, where we define all binaries > > necessary > > to get the system running and anyone can edit it as they will. > > > > Finally we have the script itself, tinybsd.sh. It's a simple script, > > yet functional. We based it on NanoBSD's and its idea is to create a > > temporary work directory where the new system's directory tree will > > be > > created. Then it'll copy all files listed on tinybsd.basefiles to > > this > > tree. This copying process is essential to the speed of the building > > process, as we eliminate the recompiling phase. The reason for this > > is > > FreeBSD 5.1' dynamically-linked base system, which take much less > > space than the old statically-linked ones. This way we can also do > > the > > copying without affecting the production system in any way. > > > > After all this, we compile the kernel using the TINYBSD file and then > > we install the necessary libs using the dependencies' output from the > > binaries. We populate the /etc directory on the temp work directory > > and put in a few important default settings in /etc/rc.conf, like: > > > > hostname="tinybsd.freebsd.org" > > sendmail_enable="NONE" > > sshd_enable="YES" > > usbd_enable="NO" > > inetd_enable="NO" > > portmap_enable="NO" > > update_motd="NO" > > varsize="8192" > > diskless_mount="/etc/rc.d/diskless" > > > > Lastly, we create the empty image according to the specifications for > > the device passed in as a parameter and copy the entire temp > > directory > > to the new image. After that, the user can use dd to write the final > > image to the target device. > > > > Booting the system works as embedded systems do, mounting /var and > > /tmp as MFS filesystems. > > > > The most interesting point is the space used by default, only 19MB. > > > > As you can see, it's pretty simple. But since PicoBSD is practically > > unusable with the 5.x series, TinyBSD could be an interesting > > alternative along with NanoBSD to be put on the base system in future > > versions. > > > > Patrick and I have been thinking of enhancing the script and adding > > end-user helping tools such dialog-based menus and the likes, for > > more > > details see our TODO file. In case the FreeBSD project has any > > interest > > in our project, we can perfectly maintain TinyBSD as an embedded > > option > > for FreeBSD users. > > > > We would like that the interested parties make tests and then > > report bug, sends sugestions to improve the TinyBSD. > > > > Thank you for your attention > > Jean Milanez Melo > > _______________________________________________ > > 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 Jul 21 14:41: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 6ADCC16A4CE; Wed, 21 Jul 2004 14:41:29 +0000 (GMT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 136E543D5A; Wed, 21 Jul 2004 14:41:29 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i6LEfSR0018374 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Jul 2004 10:41:28 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i6LEfMlQ046520; Wed, 21 Jul 2004 10:41:22 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16638.32914.509773.486468@grasshopper.cs.duke.edu> Date: Wed, 21 Jul 2004 10:41:22 -0400 (EDT) To: Doug Rabson In-Reply-To: <200407182104.53221.dfr@nlsystems.com> References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Excellent job on the firewire 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: Wed, 21 Jul 2004 14:41:29 -0000 Doug Rabson writes: > Actually thats the only downside of dcons. It doesn't cut in until the > firewire controller attaches. It relies on the fact that the fwohci > driver allows access to physical memory from any node on the bus > (implemeted in hardware so you can examine the memory of a hung > machine). The dconschat program uses this feature to access the dcons > ring buffers in the target machine. Does remote access to physical memory require dcons to be loaded on the target? If no, assuming I had a Windows or Linux box on the firewire bus, would it be possible to access physical memory from a different OS? Thanks, Drew From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 14:53: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 070CF16A4CE for ; Wed, 21 Jul 2004 14:53:55 +0000 (GMT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id E494243D46 for ; Wed, 21 Jul 2004 14:53:54 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Wed, 21 Jul 2004 07:53:54 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 86C7E5D09; Wed, 21 Jul 2004 07:53:53 -0700 (PDT) To: matti k In-reply-to: Your message of "Wed, 21 Jul 2004 18:20:15 +1000." <20040721182015.1e00641d.matti@optusnet.com.au> Date: Wed, 21 Jul 2004 07:53:53 -0700 From: "Kevin Oberman" Message-Id: <20040721145353.86C7E5D09@ptavv.es.net> cc: freebsd-current@freebsd.org Subject: Re: FAILURE - ATAPI_RESET no interrupt in newer current 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, 21 Jul 2004 14:53:55 -0000 > Date: Wed, 21 Jul 2004 18:20:15 +1000 > From: matti k > Sender: owner-freebsd-current@freebsd.org > > On Tue, 20 Jul 2004 18:22:29 -0500 (CDT) > "Conrad J. Sabatier" wrote: > > > > The drive works normally, it seems, at least for a while. Last > > night, I tried playing a DVD in mplayer, and it worked fine until > > the whole machine suddenly hung. Hard to say whether or not this is > > an ata/atapi issue, or maybe due to the other, well-known preemption > > problem that's being discussed here lately. > > > > I get this "playing a DVD in mplayer" hang on a machine running > -current from Sat Jun 19 17:36:01 EST 2004, which I believe pre-dates > the preemption stuff. This problem definitely pre-dates the preemption issues. I have been seeing it since mid-June. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 14:59: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 0EEE816A4CE; Wed, 21 Jul 2004 14:59:10 +0000 (GMT) Received: from mail.qubesoft.com (gate.qubesoft.com [217.169.36.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F70943D49; Wed, 21 Jul 2004 14:59:09 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from bluebottle.qubesoft.com (bluebottle.qubesoft.com [192.168.1.2]) by mail.qubesoft.com (8.12.9/8.12.9) with ESMTP id i6LEx2kM079932; Wed, 21 Jul 2004 15:59:02 +0100 (BST) (envelope-from dfr@nlsystems.com) Received: from builder02.qubesoft.com (builder02.qubesoft.com [192.168.1.8]) i6LEx1ON072888; Wed, 21 Jul 2004 15:59:01 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: Andrew Gallatin In-Reply-To: <16638.32914.509773.486468@grasshopper.cs.duke.edu> References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> <16638.32914.509773.486468@grasshopper.cs.duke.edu> Content-Type: text/plain Message-Id: <1090421941.7114.26.camel@builder02.qubesoft.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 21 Jul 2004 15:59:01 +0100 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 'clamd / ClamAV version 0.65', clamav-milter version '0.60p' cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Excellent job on the firewire 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: Wed, 21 Jul 2004 14:59:10 -0000 On Wed, 2004-07-21 at 15:41, Andrew Gallatin wrote: > Doug Rabson writes: > > Actually thats the only downside of dcons. It doesn't cut in until the > > firewire controller attaches. It relies on the fact that the fwohci > > driver allows access to physical memory from any node on the bus > > (implemeted in hardware so you can examine the memory of a hung > > machine). The dconschat program uses this feature to access the dcons > > ring buffers in the target machine. > > Does remote access to physical memory require dcons to be loaded > on the target? No. The remote access to physical memory is a hardware-implemented feature of the firewire ohci hardware. Its enabled in fwohci_attach(). In the long term, I would like to restrict this a bit but right now all you have to have is fwohci loaded on the target machine. > > If no, assuming I had a Windows or Linux box on the firewire bus, would it be > possible to access physical memory from a different OS? Windows XP has some kind of firewire debug driver that you might have to load (I haven't read the docs on that). I don't think the linux driver enables physical access by default but it would be easy to hack it in (just write all ones to the right fwohci register). From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 15:03: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 87F6916A4CE; Wed, 21 Jul 2004 15:03:02 +0000 (GMT) Received: from mailout1.informatik.tu-muenchen.de (mailout1.informatik.tu-muenchen.de [131.159.0.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id B623043D62; Wed, 21 Jul 2004 15:02:59 +0000 (GMT) (envelope-from langd@informatik.tu-muenchen.de) Date: Wed, 21 Jul 2004 17:02:58 +0200 From: Daniel Lang To: Darren Pilgrim Message-ID: <20040721150258.GB54664@atrbg11.informatik.tu-muenchen.de> References: <000001c46f11$1f53a880$132a15ac@spud> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000001c46f11$1f53a880$132a15ac@spud> X-Geek: GCS/CC d-- s: a- C++$ UBS++++$ P+++$ L- E-(---) W+++(--) N++ o K w--- O? M? V? PS+(++) PE--(+) Y+ PGP+ t++ 5+++ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r+++ y+ User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at informatik.tu-muenchen.de cc: 'Matt White' cc: freebsd-current@freebsd.org cc: 'Robert Watson' Subject: Re: fetch hangs, part 2 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, 21 Jul 2004 15:03:02 -0000 Hi Darren, Darren Pilgrim wrote on Wed, Jul 21, 2004 at 03:54:34AM -0700: [..] > > Could you try disabling TCP SACK > > Set net.inet.tcp.delayed_ack=0? No, the correct one is: net.inet.tcp.sack.enable=0 However, a bug was fixed in the SACK code just recently. I think the commit went in yesterday, or the day before. However, it is possible that there are more issues around... HTH, Daniel -- IRCnet: Mr-Spock - In dieser Mail ist ein Geist, der Dich in den Hintern beisst - Daniel Lang * dl@leo.org * +49 89 289 18532 * http://www.leo.org/~dl/ From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 15:04: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 77C3A16A4CE; Wed, 21 Jul 2004 15:04:23 +0000 (GMT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2995B43D31; Wed, 21 Jul 2004 15:04:23 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i6LF4MR0020272 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Jul 2004 11:04:22 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i6LF4HMO046542; Wed, 21 Jul 2004 11:04:17 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16638.34289.507068.283775@grasshopper.cs.duke.edu> Date: Wed, 21 Jul 2004 11:04:17 -0400 (EDT) To: Doug Rabson In-Reply-To: <1090421941.7114.26.camel@builder02.qubesoft.com> References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> <16638.32914.509773.486468@grasshopper.cs.duke.edu> <1090421941.7114.26.camel@builder02.qubesoft.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Excellent job on the firewire 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: Wed, 21 Jul 2004 15:04:23 -0000 Doug Rabson writes: > On Wed, 2004-07-21 at 15:41, Andrew Gallatin wrote: > > Doug Rabson writes: > > > Actually thats the only downside of dcons. It doesn't cut in until the > > > firewire controller attaches. It relies on the fact that the fwohci > > > driver allows access to physical memory from any node on the bus > > > (implemeted in hardware so you can examine the memory of a hung > > > machine). The dconschat program uses this feature to access the dcons > > > ring buffers in the target machine. > > > > Does remote access to physical memory require dcons to be loaded > > on the target? > > No. The remote access to physical memory is a hardware-implemented > feature of the firewire ohci hardware. Its enabled in fwohci_attach(). > In the long term, I would like to restrict this a bit but right now all > you have to have is fwohci loaded on the target machine. Yes, it seems like turning it off by default would be a good idea. Its very handy for debugging, but the security implications are rather alarming.. Thanks for the info! Drew From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 15:10:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 13BAD16A4CE; Wed, 21 Jul 2004 15:10:04 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.12.11/8.12.11) with ESMTP id i6LFA3Tg096694; Wed, 21 Jul 2004 11:10:03 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.12.11/8.12.11/Submit) id i6LFA2C7096693; Wed, 21 Jul 2004 11:10:02 -0400 (EDT) (envelope-from green) Date: Wed, 21 Jul 2004 11:10:01 -0400 From: Brian Fundakowski Feldman To: Maxim Maximov Message-ID: <20040721151001.GH1009@green.homeunix.org> References: <40FE0DF3.4030008@anobject.com> <40FE1576.10206@elischer.org> <20040721102420.GE1009@green.homeunix.org> <40FE5118.3040900@mcsi.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40FE5118.3040900@mcsi.pp.ru> User-Agent: Mutt/1.5.6i cc: Jake Hamby cc: Julian Elischer cc: freebsd-current@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: Using -current on a Fujitsu Lifebook N5010 (no Atheros 802.11, no Ethernet, + hard freezes) 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, 21 Jul 2004 15:10:04 -0000 On Wed, Jul 21, 2004 at 03:18:48PM +0400, Maxim Maximov wrote: > Brian Fundakowski Feldman wrote: > > >On Wed, Jul 21, 2004 at 12:04:22AM -0700, Julian Elischer wrote: > > > >>Jake Hamby wrote: > >> > >>>3) Random freezes > >> > >>>After an average of 30-40 minutes of heavy usage, I get random system > >>>freezes. I am typically running XFree86 and downloading something > >>>or reading web pages at the time it happens. More disturbingly, I am > >>>occasionally seeing files get renamed, for example > >>>/usr/src/UPDATING.64BIT became /usr/src/UPDATING.64BTT. This happens > >>>with or without WITNESS, with INVARIANTS enabled, with or without > >>>ACPI, and with or without SMP. I am using SCHED_ULE and no > >>>PREEMPTION. > >> > >>you are not alone.. I think you just chose a bad moment to > >>jump into -current > >>:-/ > > > > > >Who else is getting random memory corruption? I've only ever seen it > >in my life with bad RAM/bad cooling, but this could be bad anything, > >including something spamming random addresses with DMA. The characters > >'I' and 'T' are far enough apart such that I wouldn't expect a simple > >memory error which usually seems to appear as a single bit flip. > > What are you guys all smoking? 64BTT stands for "64 bit time_t" > http://www.freebsd.org/cgi/cvsweb.cgi/src/UPDATING.64BTT Haha; never believe everything you read I suppose. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 15:14: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 C1A0916A4CE for ; Wed, 21 Jul 2004 15:14:20 +0000 (GMT) Received: from mail.FreeBSD.org.cn (dns3.freebsd.org.cn [61.129.66.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id D39C043D54 for ; Wed, 21 Jul 2004 15:14:15 +0000 (GMT) (envelope-from delphij@frontfree.net) Received: (qmail 93278 invoked by uid 0); 21 Jul 2004 15:12:21 -0000 Received: from unknown (HELO beastie.frontfree.net) (219.239.98.7) by mail.FreeBSD.org.cn with AES256-SHA encrypted SMTP; 21 Jul 2004 15:12:21 -0000 Received: from localhost (localhost.frontfree.net [127.0.0.1]) by beastie.frontfree.net (Postfix) with ESMTP id 55D9D11524; Wed, 21 Jul 2004 23:14:13 +0800 (CST) Received: from beastie.frontfree.net ([127.0.0.1]) by localhost (beastie.frontfree.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02660-06; Wed, 21 Jul 2004 23:14:02 +0800 (CST) Received: by beastie.frontfree.net (Postfix, from userid 1001) id C501811DBA; Wed, 21 Jul 2004 23:14:01 +0800 (CST) Date: Wed, 21 Jul 2004 23:14:01 +0800 From: Xin LI To: Bruce Evans Message-ID: <20040721151401.GA2458@frontfree.net> References: <20040721113211.GA1899@frontfree.net> <20040721232310.Y2587@epsplex.bde.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9amGYk9869ThD9tj" Content-Disposition: inline In-Reply-To: <20040721232310.Y2587@epsplex.bde.org> User-Agent: Mutt/1.4.2.1i X-GPG-key-ID/Fingerprint: 0xCAEEB8C0 / 43B8 B703 B8DD 0231 B333 DC28 39FB 93A0 CAEE B8C0 X-GPG-Public-Key: http://www.delphij.net/delphij.asc X-Operating-System: FreeBSD beastie.frontfree.net 5.2-delphij FreeBSD 5.2-delphij #80: Thu Jun 24 17:30:33 CST 2004 delphij@beastie.frontfree.net:/usr/obj/usr/src/sys/BEASTIE i386 X-URL: http://www.delphij.net X-By: delphij@beastie.frontfree.net X-Location: Beijing, China X-Virus-Scanned: by amavisd-new at frontfree.net cc: current@freebsd.org Subject: Re: Any idea why timespec* is _KERNEL stuff only? 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, 21 Jul 2004 15:14:21 -0000 --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, Bruce On Wed, Jul 21, 2004 at 11:37:40PM +1000, Bruce Evans wrote: > On Wed, 21 Jul 2004, Xin LI wrote: >=20 > > Hi, Poul-Henning, > > > > It seems that rev. 1.23 of sys/sys/time.h has constrained timespec* mac= ros > > to be _KERNEL (KERNEL in the old days) only. Is this intended? (NetBSD = and >=20 > Yes, this is intended. The timeval and timespec interfaces are optimized > for handling times in code that can't use 64-bit integers or floating > point (mainly in 20 year old kernels). New interfaces to manipulate them > should not be added 20 years after the interfaces should have been > deprecated. > > > OpenBSD don't expect _KERNEL for these macros, e.g. timespeccmp, and I > > personally think that these macros will be better for more generic use, >=20 > NetBSD and OpenBSD originally only had timeval*(), and FreeBSD unfortunat= ely > had to add them to be compatible. timespec*() seem to be even less needed > in userland than timeval*(), since no ports are broken by not having them. >=20 > > as timespec structure is not _KERNEL protected :-) >=20 > The timespec struct is POSIX standard. POSIX has the correct number of > functions for operating on timespec structs (none). Thanks for the information, Bruce! So this means I should use bintime instead of timespec if it is found in code? For the exact problem I went into: it's OpenBSD's cron which makes use of timespec (because of fstat). I think a _KERNEL || __BSD_VISIBLE might be helpful -- While it is possible to use bintime to represent what can be done with a timespeccmp macro. Cheers, --=20 Xin LI http://www.delphij.net/ See complete headers for GPG key and other information. --9amGYk9869ThD9tj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/og5OfuToMruuMARAtxOAJ9ECSsiSmizfpStEGqlEUXH40EFiACfXuSe 05C9NccCIE45jgc1VWpuUWg= =77mn -----END PGP SIGNATURE----- --9amGYk9869ThD9tj-- From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 15:14: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 24FEA16A4CE for ; Wed, 21 Jul 2004 15:14:29 +0000 (GMT) Received: from mailout1.informatik.tu-muenchen.de (mailout1.informatik.tu-muenchen.de [131.159.0.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id D26CA43D49 for ; Wed, 21 Jul 2004 15:14:28 +0000 (GMT) (envelope-from langd@informatik.tu-muenchen.de) Date: Wed, 21 Jul 2004 17:14:27 +0200 From: Daniel Lang To: Jan Grant Message-ID: <20040721151427.GC54664@atrbg11.informatik.tu-muenchen.de> References: <40F963D8.6010201@freebsd.org> <20040719060730.GA87697@nagual.pp.ru> <20040720081051.GB3001@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Geek: GCS/CC d-- s: a- C++$ UBS++++$ P+++$ L- E-(---) W+++(--) N++ o K w--- O? M? V? PS+(++) PE--(+) Y+ PGP+ t++ 5+++ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r+++ y+ User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at informatik.tu-muenchen.de cc: Peter Jeremy cc: Stefan Bethke cc: current@freebsd.org Subject: Re: NEW TAR 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, 21 Jul 2004 15:14:29 -0000 Hi, Jan Grant wrote on Wed, Jul 21, 2004 at 02:44:42PM +0100: [..] > You're correct, in that filesystem semantics don't require an archiver > to recreate holes. There are storage efficiency gains to be made in > identifying holes, that's true - particularly in the case of absolutely > whopping but extremely sparse files. In those cases, a simple > userland-view-of-the-filesystem-semantics approach to ideentifying areas > that _might_ be holes (just for archive efficiency) can still be > expensive and might involve the scanning of multiple gigabytes of > "virtual" zeroes. > > Solaris offers an fcntl to identify holes (IIRC) for just this purpose. > If the underlying filesystem can't be made to support it, there's an > efficiency loss but otherwise it's no great shakes. I don't get it. I assume, that for any consumer it is totally transparent if possibly existing chunks of 0-bytes are actually blocks full of zeroes or just non-allocated blocks, correct? Second, it is true, that there is a gain in terms of occupied disk space, if chunks of zeroes are not allocated at all, correct? So, from my point of view it is totally irrelevant, if a sparse file is archived and then extracted, if the areas, which contain zeroes are exactly in the same manner consisting of unallocated blocks or not. So, all I guess an archiver must do is: - read the file - scan the file for consecutive blocks of zeroes - archive these blocks in an efficient way - on extraction, create a sparse file with the previously identified empty blocks, regardless if these blocks have been 'sparse' blocks in the original file or not. I do not see, why it is important if the original file was sparse at all or maybe in different places. Cheers, Daniel -- IRCnet: Mr-Spock - My name is Pentium of Borg, division is futile, you will be approximated. - Daniel Lang * dl@leo.org * +49 89 289 18532 * http://www.leo.org/~dl/ From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 15:31: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 4BA4916A4CE for ; Wed, 21 Jul 2004 15:31:00 +0000 (GMT) Received: from n33.kp.t-systems-sfr.com (n33.kp.t-systems-sfr.com [129.247.16.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 682BF43D5E for ; Wed, 21 Jul 2004 15:30:57 +0000 (GMT) (envelope-from harti@freebsd.org) Received: from n81.sp.op.dlr.de (n81g.sp.op.dlr.de [129.247.163.1]) i6LFUkX530862; Wed, 21 Jul 2004 17:30:46 +0200 Received: from zeus.nt.op.dlr.de (zeus.nt.op.dlr.de [129.247.173.3]) i6LFUkf348648; Wed, 21 Jul 2004 17:30:46 +0200 Received: from beagle.kn.op.dlr.de (opkndnwsbsd178 [129.247.173.178]) by zeus.nt.op.dlr.de (8.11.7+Sun/8.9.1) with ESMTP id i6LFUiV19856; Wed, 21 Jul 2004 17:30:45 +0200 (MET DST) Date: Wed, 21 Jul 2004 17:30:45 +0200 (CEST) From: Harti Brandt X-X-Sender: brandt@beagle.kn.op.dlr.de To: Daniel Lang In-Reply-To: <20040721151427.GC54664@atrbg11.informatik.tu-muenchen.de> Message-ID: <20040721172047.C99248@beagle.kn.op.dlr.de> References: <40F963D8.6010201@freebsd.org> <20040719060730.GA87697@nagual.pp.ru> <20040720081051.GB3001@cirb503493.alcatel.com.au> <20040721151427.GC54664@atrbg11.informatik.tu-muenchen.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Jan Grant cc: current@freebsd.org cc: Peter Jeremy Subject: Re: NEW TAR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Harti Brandt List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2004 15:31:00 -0000 On Wed, 21 Jul 2004, Daniel Lang wrote: DL>Hi, DL> DL>Jan Grant wrote on Wed, Jul 21, 2004 at 02:44:42PM +0100: DL>[..] DL>> You're correct, in that filesystem semantics don't require an archiver DL>> to recreate holes. There are storage efficiency gains to be made in DL>> identifying holes, that's true - particularly in the case of absolutely DL>> whopping but extremely sparse files. In those cases, a simple DL>> userland-view-of-the-filesystem-semantics approach to ideentifying areas DL>> that _might_ be holes (just for archive efficiency) can still be DL>> expensive and might involve the scanning of multiple gigabytes of DL>> "virtual" zeroes. DL>> DL>> Solaris offers an fcntl to identify holes (IIRC) for just this purpose. DL>> If the underlying filesystem can't be made to support it, there's an DL>> efficiency loss but otherwise it's no great shakes. DL> DL>I don't get it. DL> DL>I assume, that for any consumer it is totally transparent if DL>possibly existing chunks of 0-bytes are actually blocks full of DL>zeroes or just non-allocated blocks, correct? DL> DL>Second, it is true, that there is a gain in terms of occupied disk DL>space, if chunks of zeroes are not allocated at all, correct? DL> DL>So, from my point of view it is totally irrelevant, if a sparse file DL>is archived and then extracted, if the areas, which contain zeroes DL>are exactly in the same manner consisting of unallocated blocks DL>or not. DL> DL>So, all I guess an archiver must do is: DL> DL> - read the file DL> - scan the file for consecutive blocks of zeroes DL> - archive these blocks in an efficient way DL> - on extraction, create a sparse file with the previously DL> identified empty blocks, regardless if these blocks DL> have been 'sparse' blocks in the original file or not. DL> DL>I do not see, why it is important if the original file was sparse DL>at all or maybe in different places. It just may be a good deal faster just to take existing hole information (if it exists) than to scan the file. Also there is a difference between holes and actual zeroes: it's like overcommitting memory. Yoy may have a 1TB file consisting of a large hole on a 10GB disk. Just as you write something to it you will get an error at some time even when writing into the middle of the file, just because the FS needs to allocate blocks. I could imagine an application knowing its access pattern to a large sparse file allocating zeroed blocks in advance while skipping blocks that it knows it'll not write, just to make sure the blocks are there when it will write later on. But that's a rather hypothetical application. harti From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 15:33: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 E5E0A16A4CE for ; Wed, 21 Jul 2004 15:33:16 +0000 (GMT) Received: from mail.abitab.com.uy (r200-40-59-195.adinet.com.uy [200.40.59.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF16143D46 for ; Wed, 21 Jul 2004 15:33:11 +0000 (GMT) (envelope-from pablo.morales@abitab.com.uy) Received: from webmail.abitab.com.uy (www.abitab.com.uy [200.40.59.201]) 7E9E623FBD; Wed, 21 Jul 2004 12:32:59 -0300 (UYT) Received: from 172.16.1.150 (auth. user pablo.morales@104.abitab.com.uy) by webmail.abitab.com.uy with HTTP; Wed, 21 Jul 2004 15:32:59 +0000 To: "jmelo-lists@freebsdbrasil.com.br" , "Patrick Gardella" Date: Wed, 21 Jul 2004 15:32:58 +0000 X-Mailer: IlohaMail/0.9.0 (On: webmail.abitab.com.uy) In-Reply-To: <1090421434.593.3.camel@offset.freebsdbrasil.com.br> From: Bounce-To: Errors-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Message-Id: <20040721153259.7E9E623FBD@mail.abitab.com.uy> cc: "current@freebsd.org" Subject: Re: FreeBSD embedded: TinyBSD 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, 21 Jul 2004 15:33:17 -0000 HI there boys. I'm writing to Uruguay I'm interested in TinyBSD, I'd like to know if the term ebeded refers only to the *size* or if you have been tweking the kernel code. I'm working with Some GEODE stuff, using linux, I'm using the terminals just like that, remote PXE booting with nfs-root. I'd like to have access to your project to give it a try with this enviroment. Thanx. On 21/7/2004, "Jean Milanez Melo" wrote: >On Wed, 2004-07-21 at 08:58, Patrick Gardella wrote: >> Is there a web page for TinyBSD? >> >> patrick > > >Not yet, but we're going to make one if people like the project and it > gets well accepted by the community. We're definatelly putting up a >lot > of documentation on that page, though. We haven't done so yet because > currently it's way too simple, as you can run it knowing only the > information regarding the target device. > > For example, assuming a 32MB flash memory, one could use the following > parameters to create an embedded system: > > ./tinybsd.sh 62592 4 32 > > Or optionally the name of the output image you want: > > ./tinybsd.sh 62592 4 32 myimage.bin > >- Jean Milanez Melo > >> >> On Jul 20, 2004, at 11:48 AM, Jean Milanez Melo wrote: >> >> > Hello current, >> > >> > Please allow me to introduce myself, I'm one of the coordinators of >> > the Brazilian FreeBSD Users group, coordinator of the official >> > FreeBSD documentation's translation group and have been working with >> > embedded FreeBSD systems since year 2000. >> > >> > I've been studying NanoBSD ever since Poul-Henning posted about it >> > on one of >> > the mailling lists, and I have been following this project closely. >> > It >> > really is a great project. >> > >> > However, I think it sometimes creates unnecessary partitions, takes >> > too long to build the system due to make world and it copies lots of >> > unneeded binaries, taking a lot of precious space. >> > >> > So me and Patrick Tracanelli (another active member of the Brazilian >> > FreeBSD community) decided to write a new set of scripts to build >> > embedded systems. We've named it TinyBSD, and its goal is to be >> > faster >> > at building-time, occupy less space on the target device and to ease >> > customization like PicoBSD does. >> > >> > Untar/gzip the tinybsd.tgz file under /usr/src/release. >> > >> > # ls >> > TINYBSD TODO tinybsd.basefiles tinybsd.sh >> > >> > We first take the file TINYBSD, which like in PicoBSD we can use to >> > define or remove all kernel options to the new system. >> > >> > Then we have tinybsd.basefiles, where we define all binaries >> > necessary >> > to get the system running and anyone can edit it as they will. >> > >> > Finally we have the script itself, tinybsd.sh. It's a simple script, >> > yet functional. We based it on NanoBSD's and its idea is to create a >> > temporary work directory where the new system's directory tree will >> > be >> > created. Then it'll copy all files listed on tinybsd.basefiles to >> > this >> > tree. This copying process is essential to the speed of the building >> > process, as we eliminate the recompiling phase. The reason for this >> > is >> > FreeBSD 5.1' dynamically-linked base system, which take much less >> > space than the old statically-linked ones. This way we can also do >> > the >> > copying without affecting the production system in any way. >> > >> > After all this, we compile the kernel using the TINYBSD file and then >> > we install the necessary libs using the dependencies' output from the >> > binaries. We populate the /etc directory on the temp work directory >> > and put in a few important default settings in /etc/rc.conf, like: >> > >> > hostname=3D"tinybsd.freebsd.org" >> > sendmail_enable=3D"NONE" >> > sshd_enable=3D"YES" >> > usbd_enable=3D"NO" >> > inetd_enable=3D"NO" >> > portmap_enable=3D"NO" >> > update_motd=3D"NO" >> > varsize=3D"8192" >> > diskless_mount=3D"/etc/rc.d/diskless" >> > >> > Lastly, we create the empty image according to the specifications for >> > the device passed in as a parameter and copy the entire temp >> > directory >> > to the new image. After that, the user can use dd to write the final >> > image to the target device. >> > >> > Booting the system works as embedded systems do, mounting /var and >> > /tmp as MFS filesystems. >> > >> > The most interesting point is the space used by default, only 19MB. >> > >> > As you can see, it's pretty simple. But since PicoBSD is practically >> > unusable with the 5.x series, TinyBSD could be an interesting >> > alternative along with NanoBSD to be put on the base system in future >> > versions. >> > >> > Patrick and I have been thinking of enhancing the script and adding >> > end-user helping tools such dialog-based menus and the likes, for >> > more >> > details see our TODO file. In case the FreeBSD project has any >> > interest >> > in our project, we can perfectly maintain TinyBSD as an embedded >> > option >> > for FreeBSD users. >> > >> > We would like that the interested parties make tests and then >> > report bug, sends sugestions to improve the TinyBSD. >> > >> > Thank you for your attention >> > Jean Milanez Melo >> > _______________________________________________ >> > 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 Wed Jul 21 15:34: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 E3DAC16A4CE for ; Wed, 21 Jul 2004 15:34:35 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3104743D5C for ; Wed, 21 Jul 2004 15:34:35 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 31688 invoked from network); 21 Jul 2004 15:32:18 -0000 Received: from unknown (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 21 Jul 2004 15:32:18 -0000 Message-ID: <40FE8D0A.2030407@freebsd.org> Date: Wed, 21 Jul 2004 17:34:34 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040608 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Darren Pilgrim References: <000001c46f11$1f53a880$132a15ac@spud> In-Reply-To: <000001c46f11$1f53a880$132a15ac@spud> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: 'Matt White' cc: freebsd-current@freebsd.org cc: 'Robert Watson' Subject: Re: fetch hangs, part 2 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, 21 Jul 2004 15:34:36 -0000 Darren Pilgrim wrote: >>From: Robert Watson [mailto:rwatson@freebsd.org] >> >>On Tue, 20 Jul 2004, Darren Pilgrim wrote: >> >>>I've been having the same (or a similar problem). Fetching the distfile >>>for a port will hang. I poked some more at this and found that all the >>>sites fetch is hanging on successfully negotiate the TCP connection then >>>go dead without closing the connection. My workaround has been to edit >>>the Makefile and remove the offending site from MASTER_SITES or manually >>>fetch from ftp.freebsd.org. >> >>Could you try disabling TCP SACK > > Set net.inet.tcp.delayed_ack=0? > >>and see if things "get better"? It's one >>of the things that has changed in the TCP code recently. This could well >>be a user space fetch issue, but it would be worth trying it to see, if >>only to rule it out. > > It didn't change. The connections still hung. Darren sent me a list with sites where he experiences the problem and I have tested them with FreeBSD 5-CURRENT (yesterday's), 4.10-STABLE and Windows 2kSP4. None worked. For FreeBSD fetch waited for the connection timeout and went to the second site to fetch the tarball (successfully). Maybe he was just not patient enough to wait for fetch to move on. -- Andre From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 15:43: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 00EAA16A4CE; Wed, 21 Jul 2004 15:43:27 +0000 (GMT) Received: from smtp3.sentex.ca (smtp3.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54C2B43D45; Wed, 21 Jul 2004 15:43:26 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smtp3.sentex.ca (8.12.11/8.12.11) with ESMTP id i6LFhNdX004126; Wed, 21 Jul 2004 11:43:23 -0400 (EDT) (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 i6LFhPnE050945; Wed, 21 Jul 2004 11:43:25 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 7D4C47303F; Wed, 21 Jul 2004 11:43:25 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040721154325.7D4C47303F@freebsd-current.sentex.ca> Date: Wed, 21 Jul 2004 11:43:25 -0400 (EDT) Subject: [current tinderbox] failure on ia64/ia64 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: Wed, 21 Jul 2004 15:43:27 -0000 TB --- 2004-07-21 14:35:43 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-07-21 14:35:43 - starting CURRENT tinderbox run for ia64/ia64 TB --- 2004-07-21 14:35:43 - cleaning the sandbox TB --- 2004-07-21 14:37:01 - checking out the source tree TB --- 2004-07-21 14:37:01 - cd /home/tinderbox/sandbox/CURRENT/ia64/ia64 TB --- 2004-07-21 14:37:01 - /usr/bin/cvs -f -R -Q -d/home/ncvs checkout -P -A src TB --- 2004-07-21 14:44:55 - WARNING: /home/tinderbox/sandbox/ia64.diff does not exist TB --- 2004-07-21 14:44:55 - building world (CFLAGS=-O -pipe) TB --- 2004-07-21 14:44:55 - cd /home/tinderbox/sandbox/CURRENT/ia64/ia64/src TB --- 2004-07-21 14:44:55 - /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-07-21 15:40:11 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2004-07-21 15:40:11 - cd /home/tinderbox/sandbox/CURRENT/ia64/ia64/src TB --- 2004-07-21 15:40:11 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Wed Jul 21 15:40:11 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/CURRENT/ia64/ia64/src/sys/sys/mbuf.h:372: error: `WARN_GIANTOK' undeclared (first use in this function) /tinderbox/CURRENT/ia64/ia64/src/sys/sys/mbuf.h:372: error: `WARN_SLEEPOK' undeclared (first use in this function) /tinderbox/CURRENT/ia64/ia64/src/sys/sys/mbuf.h: In function `m_getcl': /tinderbox/CURRENT/ia64/ia64/src/sys/sys/mbuf.h:385: error: `WARN_GIANTOK' undeclared (first use in this function) /tinderbox/CURRENT/ia64/ia64/src/sys/sys/mbuf.h:385: error: `WARN_SLEEPOK' undeclared (first use in this function) /tinderbox/CURRENT/ia64/ia64/src/sys/sys/mbuf.h: In function `m_clget': /tinderbox/CURRENT/ia64/ia64/src/sys/sys/mbuf.h:413: error: `WARN_GIANTOK' undeclared (first use in this function) /tinderbox/CURRENT/ia64/ia64/src/sys/sys/mbuf.h:413: error: `WARN_SLEEPOK' undeclared (first use in this function) *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/obj/ia64/tinderbox/CURRENT/ia64/ia64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src. TB --- 2004-07-21 15:43:25 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-07-21 15:43:25 - ERROR: failed to build generic kernel TB --- 2004-07-21 15:43:25 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 15:46: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 06DCF16A4CE; Wed, 21 Jul 2004 15:46:24 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81C0143D45; Wed, 21 Jul 2004 15:46:23 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.0.12] (g4.samsco.home [192.168.0.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6LFqPUl063553; Wed, 21 Jul 2004 09:52:25 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40FE8F81.7040409@freebsd.org> Date: Wed, 21 Jul 2004 09:45:05 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ben Paley References: <200407202355.41867.ben@spooty.net> <40FDA3D9.7070806@freebsd.org> <200407210758.53856.ben@spooty.net> In-Reply-To: <200407210758.53856.ben@spooty.net> 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@" cc: Robert Watson Subject: Re: vmnet.ko missing - but it's there! - vmware and crashes 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, 21 Jul 2004 15:46:24 -0000 Ben Paley wrote: > On Tuesday 20 July 2004 23:59, Scott Long wrote: > > >>Recompile the vmnet.ko binary from source and see if that helps. > > > I remade the whole thing, in the end, and now at least I'm not getting crashes > (at least, I think I remade the module... I did make and make install and so > on in /usr/ports/emulators/vmware3/ , but I couldn't see how to compile > vmnet.ko on its own). > > On boot I still get this: > > Additional ABI support: linux. > Starting cron. > Local package initialization:link_elf: symbol linux_ioctl_register_handler > undefined > kldload: can't load /usr/local/lib/vmware/modules/vmnet.ko: No such file or > directory Is your linux.ko module out of date? You have a mis-match somewhere here. Scott From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 16:02: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 E32EC16A4CF; Wed, 21 Jul 2004 16:02:17 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92DC643D55; Wed, 21 Jul 2004 16:02:17 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6LG1emP057294; Wed, 21 Jul 2004 12:01:40 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6LG1exo057291; Wed, 21 Jul 2004 12:01:40 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 21 Jul 2004 12:01:40 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Scott Long In-Reply-To: <40FE8F81.7040409@freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "freebsd -current@" cc: Ben Paley Subject: Re: vmnet.ko missing - but it's there! - vmware and crashes 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, 21 Jul 2004 16:02:18 -0000 On Wed, 21 Jul 2004, Scott Long wrote: > > Additional ABI support: linux. > > Starting cron. > > Local package initialization:link_elf: symbol linux_ioctl_register_handler > > undefined > > kldload: can't load /usr/local/lib/vmware/modules/vmnet.ko: No such file or > > directory > > Is your linux.ko module out of date? You have a mis-match somewhere > here. Or, alternatively, the symbols exported by the Linux emulation module have changed, and the VMware port hasn't caught up (or the local copy needs updating). Something is definitely out of sync, needless to say, but it could be that the VMware module needs updating in the pseudo-vendor. I've been wondering if we shouldn't bring the VMware modules into the base source tree for some time -- the license is probably an issue, but VMware is a valuable tool for development, and I'm amazed at how frequently and accurately I shoot my feet due to stale versions of the module when I am using it (such as when on travel and I need a debug target). This isn't just a property of failing to rebuild modules, but that the Linux emulation code changes and the VMware modules need to be modified to take that into account... 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 Jul 21 16:04: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 008D016A4CE for ; Wed, 21 Jul 2004 16:04:36 +0000 (GMT) Received: from mage.trollkarl.net (018.216-123-203-0.interbaun.com [216.123.203.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5243643D48 for ; Wed, 21 Jul 2004 16:04:35 +0000 (GMT) (envelope-from skafte@trollkarl.net) Received: from trollkarl.skafte.org (root@trollkarl [192.168.100.16]) by mage.trollkarl.net (8.12.11/8.12.11) with ESMTP id i6LG4YGZ054210 for ; Wed, 21 Jul 2004 10:04:34 -0600 (MDT) (envelope-from skafte@trollkarl.net) Received: from trollkarl.skafte.org (skafte@localhost [127.0.0.1]) i6LG4YLh004523 for ; Wed, 21 Jul 2004 10:04:34 -0600 (MDT) (envelope-from skafte@trollkarl.skafte.org) Received: (from skafte@localhost) by trollkarl.skafte.org (8.12.11/8.12.9/Submit) id i6LG4YaU004522 for freebsd-current@freebsd.org; Wed, 21 Jul 2004 10:04:34 -0600 (MDT) Date: Wed, 21 Jul 2004 10:04:34 -0600 From: Greg Skafte To: freebsd-current@freebsd.org Message-ID: <20040721160434.GA4506@trollkarl.skafte.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Organization: Gregs Hidey Hole Errors-To: skafte@trollkarl.net Subject: panic: mb_init_pack(): Can't deal with failure yet. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: skafte+freebsd-current@trollkarl.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2004 16:04:36 -0000 panic: mb_init_pack(): Can't deal with failure yet. panic messages: --- panic: mb_init_pack(): Can't deal with failure yet. cpuid = 0; boot() called on cpu#0 syncing disks, buffers remaining... kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x24 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0659e39 stack pointer = 0x10:0xe18b6c10 frame pointer = 0x10:0xe18b6c30 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 62 (swi8: tty:sio clock) trap number = 12 panic: page fault cpuid = 0; boot() called on cpu#0 Uptime: 4d23h53m11s backtrace #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:236 236 dumping++; (kgdb) bt #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:236 #1 0xc063621b in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:370 #2 0xc06369e8 in panic (fmt=0xc0830807 "%s") at /usr/src/sys/kern/kern_shutdown.c:548 #3 0xc07e8cc7 in trap_fatal (frame=0xe18b6bd0, eva=0) at /usr/src/sys/i386/i386/trap.c:815 #4 0xc07e87aa in trap (frame= {tf_fs = -983236584, tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = -984090208, tf_ebp = -510956496, tf_isp = -510956548, tf_ebx = -984470080, tf_edx = -983145932, tf_ecx = -984090208, tf_eax = 36, tf_trapno = 12, tf_err = 0, tf_eip = -1067082183, tf_cs = 8, tf_eflags = 65683, tf_esp = 1, tf_ss = 2}) at /usr/src/sys/i386/i386/trap.c:250 #5 0xc0659e39 in propagate_priority (td=0xc5522dc0) at /usr/src/sys/kern/subr_turnstile.c:212 #6 0xc065a58e in turnstile_wait (ts=0xc5d207c0, lock=0xc5666234, owner=0xc5522dc0) at /usr/src/sys/kern/subr_turnstile.c:505 #7 0xc062bd8e in _mtx_lock_sleep (m=0xc5666234, opts=0, file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:541 #8 0xc05296a6 in fxp_tick (xsc=0xc5666000) at /usr/src/sys/dev/fxp/if_fxp.c:1807 #9 0xc0644709 in softclock (dummy=0x0) at /usr/src/sys/kern/kern_timeout.c:255 #10 0xc061d974 in ithread_loop (arg=0xc55aa880) at /usr/src/sys/kern/kern_intr.c:557 #11 0xc061c670 in fork_exit (callout=0xc061d752 , arg=0x0, frame=0x0) at /usr/src/sys/kern/kern_fork.c:816 KERNEL Supdate date=2004.06.25.01.00.00 Quad Xeon, 4Gig Ram, HTT disabled, ADAPTIVE_MUTEXES I'm getting this about every 4 days.... -- Email: skafte@trollkarl.net ICQ: 93234105 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 16:04: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 21F0516A4D8 for ; Wed, 21 Jul 2004 16:04:44 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.200]) by mx1.FreeBSD.org (Postfix) with SMTP id C080F43D2F for ; Wed, 21 Jul 2004 16:04:43 +0000 (GMT) (envelope-from joseph.peterson@gmail.com) Received: by mproxy.gmail.com with SMTP id 72so13339rnf for ; Wed, 21 Jul 2004 09:04:43 -0700 (PDT) Received: by 10.38.209.75 with SMTP id h75mr82457rng; Wed, 21 Jul 2004 09:04:43 -0700 (PDT) Message-ID: <38a23c3604072109046e63cdd9@mail.gmail.com> Date: Wed, 21 Jul 2004 11:04:43 -0500 From: Joseph Peterson To: freebsd-current@freebsd.org In-Reply-To: <1090364563.728.3.camel@klamath.syndrom23.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <1090364563.728.3.camel@klamath.syndrom23.de> Subject: Re: FAILURE - ATAPI_RESET no interrupt in newer current 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, 21 Jul 2004 16:04:44 -0000 I have the same issue, err well similar.... ata1-master: FAILURE - ATAPI_RESET no interrupt acd0: CDRW at ata1-master PIO4 This is on a Toshiba Satelite A25-S279. Do you have any problems with burncd? when I use it, I will sometimes get a lockup. What do you have in your loader.conf? On Wed, 21 Jul 2004 01:02:43 +0200, Andreas Kohn wrote: > Hi, > > today I updated my -CURRENT from ~July 5 to July 20 sources. After > reboot with the new kernel, I saw this: > > ata1-master: FAILURE - ATAPI_RESET no interrupt > acd0: CDRW at ata1-master WDMA2 > > With the old kernel, die FAILURE message was not there, but the acd0 was > running in WDMA2 mode as well. > > This is a > atapci0: port > 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0 > controller. > > Is this message to be expected, or should I worry about anything? > > Regards, > Andreas Kohn > > > From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 16:06: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 94FC016A4CE; Wed, 21 Jul 2004 16:06:00 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 690A543D45; Wed, 21 Jul 2004 16:06:00 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.91] ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id i6LG5vWi005471 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 21 Jul 2004 09:05:57 -0700 (PDT) (envelope-from sam@errno.com) From: Sam Leffler Organization: Errno Consulting To: freebsd-mobile@freebsd.org Date: Wed, 21 Jul 2004 09:06:57 -0700 User-Agent: KMail/1.6.1 References: <40FE0DF3.4030008@anobject.com> <40FE1576.10206@elischer.org> In-Reply-To: <40FE1576.10206@elischer.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407210906.57595.sam@errno.com> cc: Jake Hamby cc: Julian Elischer cc: freebsd-current@freebsd.org Subject: Re: Using -current on a Fujitsu Lifebook N5010 (no Atheros 802.11, no Ethernet, + hard freezes) 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, 21 Jul 2004 16:06:00 -0000 On Wednesday 21 July 2004 12:04 am, Julian Elischer wrote: > Jake Hamby wrote: > > * Now uses four transmission queues of varying priority instead of > > one: WME_AC_BE (highest), WME_AC_BK, WME_AC_VI, and WME_AC_VO > > (lowest). There is code in the Linux version to support QOS and > > insert outgoing packets into queue by priority, but I couldn't find > > the equivalent of the priority field from Linux's sk_buff struct in > > FreeBSD's equivalent ieee80211_frame struct. Currently all outgoing > > packets go to WME_AC_BE, except packets of type > > IEEE80211_FC0_TYPE_MGT, which go to WME_AC_VO. > > FreeBSD would store that information in what is called an mbuf tag. > A separate small chunk of ram tagged onto teh first mbuf of the packet. > This is relatively new and there is only just starting to be some > use of it.. Official QOS support in the kernel does not exist yet. > (though there are some sporadic users of priority tags here and there > it is not general yet.) I backported the madwifi code and handled this with a hack. The net80211 layer parses the IP TOS bits to map to WME AC's. Since there are only 4 AC's to map to and the info is passed directly to the drivers under the net80211 layer I encoded them in the mbuf M_PROTO bits instead of using an m_tag. I've already sent Jake a copy of my (unfinished) work in the hopes he'll see it through to commit-ready form. Sam From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 16: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 2C49116A4D1 for ; Wed, 21 Jul 2004 16:27:11 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECBD343D4C for ; Wed, 21 Jul 2004 16:27:10 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.10/8.12.10) with ESMTP id i6LGR6OF019724; Wed, 21 Jul 2004 09:27:06 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i6LGR6Ba019723; Wed, 21 Jul 2004 09:27:06 -0700 Date: Wed, 21 Jul 2004 09:27:06 -0700 From: Brooks Davis To: Daniel Lang Message-ID: <20040721162706.GA12760@Odin.AC.HMC.Edu> References: <40F963D8.6010201@freebsd.org> <20040719060730.GA87697@nagual.pp.ru> <20040720081051.GB3001@cirb503493.alcatel.com.au> <20040721151427.GC54664@atrbg11.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lrZ03NoBR/3+SXJZ" Content-Disposition: inline In-Reply-To: <20040721151427.GC54664@atrbg11.informatik.tu-muenchen.de> User-Agent: Mutt/1.5.4i cc: current@freebsd.org cc: Jan Grant cc: Stefan Bethke cc: Peter Jeremy Subject: Re: NEW TAR 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, 21 Jul 2004 16:27:11 -0000 --lrZ03NoBR/3+SXJZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 21, 2004 at 05:14:27PM +0200, Daniel Lang wrote: > Hi, >=20 > Jan Grant wrote on Wed, Jul 21, 2004 at 02:44:42PM +0100: > [..] > > You're correct, in that filesystem semantics don't require an archiver= =20 > > to recreate holes. There are storage efficiency gains to be made in=20 > > identifying holes, that's true - particularly in the case of absolutely= =20 > > whopping but extremely sparse files. In those cases, a simple=20 > > userland-view-of-the-filesystem-semantics approach to ideentifying area= s=20 > > that _might_ be holes (just for archive efficiency) can still be=20 > > expensive and might involve the scanning of multiple gigabytes of=20 > > "virtual" zeroes. > >=20 > > Solaris offers an fcntl to identify holes (IIRC) for just this purpose.= =20 > > If the underlying filesystem can't be made to support it, there's an=20 > > efficiency loss but otherwise it's no great shakes. >=20 > I don't get it. >=20 > I assume, that for any consumer it is totally transparent if > possibly existing chunks of 0-bytes are actually blocks full of > zeroes or just non-allocated blocks, correct? >=20 > Second, it is true, that there is a gain in terms of occupied disk > space, if chunks of zeroes are not allocated at all, correct? >=20 > So, from my point of view it is totally irrelevant, if a sparse file > is archived and then extracted, if the areas, which contain zeroes > are exactly in the same manner consisting of unallocated blocks > or not. >=20 > So, all I guess an archiver must do is: >=20 > - read the file=20 > - scan the file for consecutive blocks of zeroes > - archive these blocks in an efficient way > - on extraction, create a sparse file with the previously > identified empty blocks, regardless if these blocks > have been 'sparse' blocks in the original file or not. >=20 > I do not see, why it is important if the original file was sparse > at all or maybe in different places. Since sparse files over commit the disk, they should only be created deliberatly. Otherwise you can easily get in trouble if you try to use reserved space later since it won't actually be reserved. Consider the case of a file system image created with "dd if=3D/dev/zero ...; newfw =2E..". If your archiver decides to be "smart" and restore a copy of that file sparce and then you use up the availble blocks on your disk you're going to be in a world of hurt. I wouldn't be suprised it that resulted in a panic. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --lrZ03NoBR/3+SXJZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFA/plZXY6L6fI4GtQRAvmQAJ4u+YermbOn0uurNfGxp9YABnGhZACePfRU 1RGVXsw5HhIjR5U7iO/seN0= =8BZ4 -----END PGP SIGNATURE----- --lrZ03NoBR/3+SXJZ-- From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 16:33: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 33D2316A4CE for ; Wed, 21 Jul 2004 16:33:18 +0000 (GMT) Received: from pfepa.post.tele.dk (pfepa.post.tele.dk [195.41.46.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2B8143D3F for ; Wed, 21 Jul 2004 16:33:17 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (0x50a07c53.naenxx7.adsl-dhcp.tele.dk [80.160.124.83]) by pfepa.post.tele.dk (Postfix) with ESMTP id 71D9047FE77; Wed, 21 Jul 2004 18:33:12 +0200 (CEST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i6LGWxOw084540; Wed, 21 Jul 2004 18:33:05 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 21 Jul 2004 23:37:40 +1000." <20040721232310.Y2587@epsplex.bde.org> Date: Wed, 21 Jul 2004 18:32:59 +0200 Message-ID: <84539.1090427579@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freebsd.org cc: Xin LI Subject: Re: Any idea why timespec* is _KERNEL stuff only? 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, 21 Jul 2004 16:33:18 -0000 In message <20040721232310.Y2587@epsplex.bde.org>, Bruce Evans writes: >The timespec struct is POSIX standard. POSIX has the correct number of >functions for operating on timespec structs (none). I am not in agreement mere. As much as I hate timespec, we'll have to live with it, and rather than have people make their own mistakes I'd prefer to expose some functions/macros that do it right. -- 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 Jul 21 16:40: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 4758A16A4CE for ; Wed, 21 Jul 2004 16:40:50 +0000 (GMT) Received: from mage.trollkarl.net (018.216-123-203-0.interbaun.com [216.123.203.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7242243D5F for ; Wed, 21 Jul 2004 16:40:49 +0000 (GMT) (envelope-from skafte@trollkarl.net) Received: from trollkarl.skafte.org (root@trollkarl [192.168.100.16]) by mage.trollkarl.net (8.12.11/8.12.11) with ESMTP id i6LGemea054395 for ; Wed, 21 Jul 2004 10:40:48 -0600 (MDT) (envelope-from skafte@trollkarl.net) Received: from trollkarl.skafte.org (skafte@localhost [127.0.0.1]) i6LGemd7004573 for ; Wed, 21 Jul 2004 10:40:48 -0600 (MDT) (envelope-from skafte@trollkarl.skafte.org) Received: (from skafte@localhost) by trollkarl.skafte.org (8.12.11/8.12.9/Submit) id i6LGemLH004572 for freebsd-current@freebsd.org; Wed, 21 Jul 2004 10:40:48 -0600 (MDT) Date: Wed, 21 Jul 2004 10:40:48 -0600 From: Greg Skafte To: freebsd-current@freebsd.org Message-ID: <20040721164048.GC4506@trollkarl.skafte.org> References: <20040721160434.GA4506@trollkarl.skafte.org> <20040721163025.GB4506@trollkarl.skafte.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040721163025.GB4506@trollkarl.skafte.org> User-Agent: Mutt/1.4.2.1i Organization: Gregs Hidey Hole Subject: Re: panic: mb_init_pack(): Can't deal with failure yet. 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, 21 Jul 2004 16:40:50 -0000 Is this maybe related to my panic back here? http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1806225+0+archive/2004/freebsd-current/20040627.freebsd-current Quoting Greg Skafte (skafte+freebsd-current@trollkarl.net) On Subject: panic: mb_init_pack(): Can't deal with failure yet. Date: Wed, Jul 21, 2004 at 10:04:34AM -0600 > panic: mb_init_pack(): Can't deal with failure yet. > panic messages: > --- > panic: mb_init_pack(): Can't deal with failure yet. > cpuid = 0; > boot() called on cpu#0 > > syncing disks, buffers remaining... kernel trap 12 with interrupts disabled > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x24 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc0659e39 > stack pointer = 0x10:0xe18b6c10 > frame pointer = 0x10:0xe18b6c30 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 62 (swi8: tty:sio clock) > trap number = 12 > panic: page fault > cpuid = 0; > boot() called on cpu#0 > Uptime: 4d23h53m11s > > > backtrace > #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:236 > 236 dumping++; > (kgdb) bt > #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:236 > #1 0xc063621b in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:370 > #2 0xc06369e8 in panic (fmt=0xc0830807 "%s") at /usr/src/sys/kern/kern_shutdown.c:548 > #3 0xc07e8cc7 in trap_fatal (frame=0xe18b6bd0, eva=0) at /usr/src/sys/i386/i386/trap.c:815 > #4 0xc07e87aa in trap (frame= > {tf_fs = -983236584, tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = -984090208, tf_ebp = -510956496, tf_isp = -510956548, tf_ebx = -984470080, tf_edx = -983145932, tf_ecx = -984090208, tf_eax = 36, tf_trapno = 12, tf_err = 0, tf_eip = -1067082183, tf_cs = 8, tf_eflags = 65683, tf_esp = 1, tf_ss = 2}) at /usr/src/sys/i386/i386/trap.c:250 > #5 0xc0659e39 in propagate_priority (td=0xc5522dc0) at /usr/src/sys/kern/subr_turnstile.c:212 > #6 0xc065a58e in turnstile_wait (ts=0xc5d207c0, lock=0xc5666234, owner=0xc5522dc0) > at /usr/src/sys/kern/subr_turnstile.c:505 > #7 0xc062bd8e in _mtx_lock_sleep (m=0xc5666234, opts=0, file=0x0, line=0) > at /usr/src/sys/kern/kern_mutex.c:541 > #8 0xc05296a6 in fxp_tick (xsc=0xc5666000) at /usr/src/sys/dev/fxp/if_fxp.c:1807 > #9 0xc0644709 in softclock (dummy=0x0) at /usr/src/sys/kern/kern_timeout.c:255 > #10 0xc061d974 in ithread_loop (arg=0xc55aa880) at /usr/src/sys/kern/kern_intr.c:557 > #11 0xc061c670 in fork_exit (callout=0xc061d752 , arg=0x0, frame=0x0) > at /usr/src/sys/kern/kern_fork.c:816 > > > KERNEL Supdate date=2004.06.25.01.00.00 > > Quad Xeon, 4Gig Ram, HTT disabled, ADAPTIVE_MUTEXES > > I'm getting this about every 4 days.... > > > -- > Email: skafte@trollkarl.net ICQ: 93234105 > -- -- > When things can't get any worse, they simplify themselves by getting a > whole lot worse then complicated. A complete and utter disaster is the > simplest thing in the world; it's preventing one that's complex. > (Janet Morris) > _______________________________________________ > 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" > -- Email: skafte@trollkarl.net ICQ: 93234105 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 16:44: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 4ADC916A4CE for ; Wed, 21 Jul 2004 16:44:52 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC0D943D66 for ; Wed, 21 Jul 2004 16:44:51 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [10.1.1.193] (nfw1.codefab.com [199.103.21.225]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id i6LGillX092419; Wed, 21 Jul 2004 12:44:48 -0400 (EDT) In-Reply-To: <84539.1090427579@critter.freebsd.dk> References: <84539.1090427579@critter.freebsd.dk> Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <4691F91E-DB35-11D8-BD53-003065ABFD92@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Wed, 21 Jul 2004 12:44:47 -0400 To: Poul-Henning Kamp X-Mailer: Apple Mail (2.618) X-Spam-Status: No, hits=0.0 required=5.5 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pi.codefab.com cc: current@freebsd.org Subject: Re: Any idea why timespec* is _KERNEL stuff only? 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, 21 Jul 2004 16:44:52 -0000 On Jul 21, 2004, at 12:32 PM, Poul-Henning Kamp wrote: >> The timespec struct is POSIX standard. POSIX has the correct number >> of >> functions for operating on timespec structs (none). > > I am not in agreement [h]ere. As much as I hate timespec, we'll have > to live with it, and rather than have people make their own mistakes > I'd prefer to expose some functions/macros that do it right. Doesn't Paul Vixie's eventlib expose (struct timespec)s anyway, as well as providing conversion functions to and from (struct timeval)s? -- -Chuck From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 16:46: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 D334F16A4CE; Wed, 21 Jul 2004 16:46:08 +0000 (GMT) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7673443D55; Wed, 21 Jul 2004 16:46:08 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp4.server.rpi.edu (8.13.0/8.13.0) with ESMTP id i6LGk6RH026252; Wed, 21 Jul 2004 12:46:07 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20040720220205.GA72249@tara.freenix.org> References: <20040720172052.8E2077303F@freebsd-current.sentex.ca> <20040720220205.GA72249@tara.freenix.org> Date: Wed, 21 Jul 2004 12:46:05 -0400 To: Ollivier Robert , current@freebsd.org, sparc64@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) Subject: Re: [current tinderbox] failure on sparc64/sparc64 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, 21 Jul 2004 16:46:09 -0000 At 12:02 AM +0200 7/21/04, Ollivier Robert wrote: >According to FreeBSD Tinderbox: >> ===> usr.sbin/ntp >> ===> usr.sbin/ntp/libntp >> make: don't know how to make authencrypt.c. Stop >> *** Error code 2 >> >> Stop in /tinderbox/CURRENT/sparc64/sparc64/src/usr.sbin/ntp. >> *** Error code 1 > >I can't reproduce on panther.freebsd.org :( Has anyone an idea >of what's going on? authencrypt.c doesn't even exist on 4.2.0. >Stale .depend? I do not know what problem there is for the tinderbox, but I have been able to buildworld/buildkernel/installkernel on my own sparc64 box. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 16:47: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 A4B9716A4CE for ; Wed, 21 Jul 2004 16:47:34 +0000 (GMT) Received: from pfepc.post.tele.dk (pfepc.post.tele.dk [195.41.46.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A17C43D31 for ; Wed, 21 Jul 2004 16:47:34 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (0x50a07c53.naenxx7.adsl-dhcp.tele.dk [80.160.124.83]) by pfepc.post.tele.dk (Postfix) with ESMTP id 3ACDF262825; Wed, 21 Jul 2004 18:47:33 +0200 (CEST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i6LGlVZZ085715; Wed, 21 Jul 2004 18:47:32 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Charles Swiger From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 21 Jul 2004 12:44:47 EDT." <4691F91E-DB35-11D8-BD53-003065ABFD92@mac.com> Date: Wed, 21 Jul 2004 18:47:31 +0200 Message-ID: <85714.1090428451@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freebsd.org Subject: Re: Any idea why timespec* is _KERNEL stuff only? 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, 21 Jul 2004 16:47:34 -0000 In message <4691F91E-DB35-11D8-BD53-003065ABFD92@mac.com>, Charles Swiger write s: >> I am not in agreement [h]ere. As much as I hate timespec, we'll have >> to live with it, and rather than have people make their own mistakes >> I'd prefer to expose some functions/macros that do it right. > >Doesn't Paul Vixie's eventlib expose (struct timespec)s anyway, as well >as providing conversion functions to and from (struct timeval)s? Yes, a rather convenient interface btw. -- 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 Jul 21 17:06: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 F2FF316A4CE for ; Wed, 21 Jul 2004 17:06:33 +0000 (GMT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40E6543D54 for ; Wed, 21 Jul 2004 17:06:33 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) i6LH6SaI011713 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK) for ; Wed, 21 Jul 2004 19:06:31 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id i6LH5bUi058045 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 21 Jul 2004 19:05:37 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.11/8.12.11) with ESMTP id i6LH5a3T072822 for ; Wed, 21 Jul 2004 19:05:36 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.11/8.12.11/Submit) id i6LH5axd072821 for current@freebsd.org; Wed, 21 Jul 2004 19:05:36 +0200 (CEST) (envelope-from ticso) Date: Wed, 21 Jul 2004 19:05:36 +0200 From: Bernd Walter To: current@freebsd.org Message-ID: <20040721170534.GF70663@cicely12.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.6i X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.61 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on cicely5.cicely.de Subject: GIANT question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2004 17:06:34 -0000 Say I have a driver that could run without needing GIANT, but makes use of a subsystem that requires GIANT. Removing D_NEEDGIANT in cdevsw seems to be enough to get called from userland without GIANT held. Now I need to aquire GIANT bevor calling the subsystem and release it on return. What I've found so far is DROP_GIANT/PICKUP_GIANT, which has to be paired the other way. What is the prefered way to get/release GIANT in that case? -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 17:07: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 A063616A4CE for ; Wed, 21 Jul 2004 17:07:14 +0000 (GMT) Received: from gundel.de.clara.net (gundel.de.clara.net [212.82.225.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 272B943D55 for ; Wed, 21 Jul 2004 17:07:14 +0000 (GMT) (envelope-from jesk@killall.org) Received: from port-212-202-54-113.dynamic.qsc.de ([212.202.54.113] helo=turbofresse) by gundel.de.clara.net with smtp (Exim 4.30; FreeBSD) id 1BnKiF-0003Mo-GX; Wed, 21 Jul 2004 19:17:03 +0200 Message-ID: <01f201c46f45$231aec10$45fea8c0@turbofresse> From: "jesk" To: "Dan Nelson" References: <056801c46eb3$bd0e2a40$45fea8c0@turbofresse> <20040721044816.GA56020@dan.emsphone.com> Date: Wed, 21 Jul 2004 19:07:00 +0200 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.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 cc: freebsd-current@freebsd.org Subject: Re: I/O or Threading Suffer 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, 21 Jul 2004 17:07:14 -0000 > Ah. now that's a different story. You're out of the control of the > process scheduler and into the disk. I don't suppose you're using an > IDE/ATA disk with no tagged queueing? :) Run "dmesg | grep depth.queue" > to see how many requests can be queued up on your disk at once. > > That dd is stuffing lots of dirty data into the disk cache, and all the > other processes have to wait in line to get their I/Os done. You'll > see much better results from a SCSI disk (with usual queue depths > between 32 and 64), and even better results from a multi-disk hardware > RAID array (which will have a large write cache). > > -- > Dan Nelson > dnelson@allantgroup.com > _______________________________________________ > 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" > > when system doesnt response any more in cause of high write operations on the disk then the reason for this is not looked up in the device device configuration or in non-scsi hardware ;) From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 17:11: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 163D416A4CE; Wed, 21 Jul 2004 17:11:39 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CEB643D1F; Wed, 21 Jul 2004 17:11:36 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 228B67A494; Wed, 21 Jul 2004 10:11:36 -0700 (PDT) Message-ID: <40FEA3C7.7060706@elischer.org> Date: Wed, 21 Jul 2004 10:11:35 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Thomas Quinot References: <40DFDC44.6090101@snafu.de> <20040719210311.GA72395@melusine.cuivre.fr.eu.org> <40FCF591.601@snafu.de> <20040720173944.GA4122@melusine.cuivre.fr.eu.org> <40FD6B84.7050702@snafu.de> <20040721114603.GA26359@melusine.cuivre.fr.eu.org> In-Reply-To: <20040721114603.GA26359@melusine.cuivre.fr.eu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: "Oliver B. Fischer" cc: current@freebsd.org Subject: Re: Obtaining a kernel dump is not 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: Wed, 21 Jul 2004 17:11:39 -0000 Thomas Quinot wrote: >* Oliver B. Fischer, 2004-07-20 : > > > >>Well, unfortunately my thinkpas doesn't have an serial port... :( >> does it have afirewire port? >> >> > >Hmmm, OK. One kludgy solution I already saw used in such a case involves >a digital camera and taking a snap of the backtrace... > > > From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 17:14: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 7745016A4CE for ; Wed, 21 Jul 2004 17:14:02 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27A6143D2F for ; Wed, 21 Jul 2004 17:14:02 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.0.12] (g4.samsco.home [192.168.0.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6LHKAd6063883; Wed, 21 Jul 2004 11:20:11 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40FEA412.3050900@freebsd.org> Date: Wed, 21 Jul 2004 11:12:50 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: ticso@cicely.de References: <20040721170534.GF70663@cicely12.cicely.de> In-Reply-To: <20040721170534.GF70663@cicely12.cicely.de> 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: current@freebsd.org Subject: Re: GIANT question 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, 21 Jul 2004 17:14:02 -0000 Bernd Walter wrote: > Say I have a driver that could run without needing GIANT, but > makes use of a subsystem that requires GIANT. > Removing D_NEEDGIANT in cdevsw seems to be enough to get called > from userland without GIANT held. > Now I need to aquire GIANT bevor calling the subsystem and release > it on return. > What I've found so far is DROP_GIANT/PICKUP_GIANT, which has to be > paired the other way. > What is the prefered way to get/release GIANT in that case? > mtx_lock(&Giant); call_code_needing_giant(); mtx_unlock(&Giant); Note that you must not be holding any locks when you go to aquire Giant. Scott From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 17:16: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 EE1E116A4CF; Wed, 21 Jul 2004 17:16:00 +0000 (GMT) Received: from mta08-svc.ntlworld.com (mta08-svc.ntlworld.com [62.253.162.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B00A43D64; Wed, 21 Jul 2004 17:16:00 +0000 (GMT) (envelope-from ben@spooty.net) Received: from m157-mp1.cvx3-b.pop.dial.ntli.net ([80.1.84.157]) by mta08-svc.ntlworld.comESMTP <20040721171555.WEYO548.mta08-svc.ntlworld.com@m157-mp1.cvx3-b.pop.dial.ntli.net>; Wed, 21 Jul 2004 18:15:55 +0100 From: Ben Paley To: Robert Watson Date: Wed, 21 Jul 2004 18:12:29 +0100 User-Agent: KMail/1.6.1 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: <200407211812.29934.ben@spooty.net> cc: "freebsd -current@" cc: Scott Long Subject: Re: vmnet.ko missing - but it's there! - vmware and crashes 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, 21 Jul 2004 17:16:01 -0000 On Wednesday 21 July 2004 17:01, Robert Watson wrote: > On Wed, 21 Jul 2004, Scott Long wrote: > > > Additional ABI support: linux. > > > Starting cron. > > > Local package initialization:link_elf: symbol > > > linux_ioctl_register_handler undefined > > > kldload: can't load /usr/local/lib/vmware/modules/vmnet.ko: No such > > > file or directory > > > > Is your linux.ko module out of date? You have a mis-match somewhere > > here. > > Or, alternatively, the symbols exported by the Linux emulation module have > changed, and the VMware port hasn't caught up (or the local copy needs > updating). Something is definitely out of sync, needless to say, but it > could be that the VMware module needs updating in the pseudo-vendor. So it looks like I need to update everything (world, kernel, vmware and linux base) before trying any harder on this... bummer. One of the reasons I haven't done that since mid June is that my system was all in sync then (so I thought) and I wanted to get this sorted before I started messing it all around again... Oh well, thanks a lot for your help. I'll get back in touch after I've found the time to do that and it _still_ doesn't work! Thanks a lot, Ben From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 17:20: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 CE4B316A4CE; Wed, 21 Jul 2004 17:20:35 +0000 (GMT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75A1F43D39; Wed, 21 Jul 2004 17:20:35 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.11/8.12.11) with ESMTP id i6LHKOxE045205; Wed, 21 Jul 2004 10:20:28 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200407211720.i6LHKOxE045205@gw.catspoiler.org> Date: Wed, 21 Jul 2004 10:20:24 -0700 (PDT) From: Don Lewis To: dmp@bitfreak.org In-Reply-To: <000001c46f11$1f53a880$132a15ac@spud> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: matt+list.sw.freebsd.current@publicly.neglect.us cc: freebsd-current@FreeBSD.org cc: rwatson@FreeBSD.org Subject: Re: fetch hangs, part 2 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, 21 Jul 2004 17:20:36 -0000 On 21 Jul, Darren Pilgrim wrote: >> From: Robert Watson [mailto:rwatson@freebsd.org] >> >> >> On Tue, 20 Jul 2004, Darren Pilgrim wrote: >> >> > I've been having the same (or a similar problem). Fetching the distfile >> > for a port will hang. I poked some more at this and found that all the >> > sites fetch is hanging on successfully negotiate the TCP connection then >> > go dead without closing the connection. My workaround has been to edit >> > the Makefile and remove the offending site from MASTER_SITES or manually >> > fetch from ftp.freebsd.org. >> >> Could you try disabling TCP SACK > > Set net.inet.tcp.delayed_ack=0? > >> and see if things "get better"? It's one >> of the things that has changed in the TCP code recently. This could well >> be a user space fetch issue, but it would be worth trying it to see, if >> only to rule it out. > > It didn't change. The connections still hung. Smells somewhat like a broken path MTU discovery problem. There might be a hop in the path with a smaller than expected MTU and something between there and the server that is filtering ICMP. An interesting experiment would be to see what happens if a smaller than normal MSS is requested. This would probably be easiest for someone with a PPP connection. From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 17:38: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 5DF5116A4CF; Wed, 21 Jul 2004 17:38:34 +0000 (GMT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id C378943D5C; Wed, 21 Jul 2004 17:38:33 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) i6LHcTaI012875 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Wed, 21 Jul 2004 19:38:32 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id i6LHbhUi058264 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Jul 2004 19:37:44 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.11/8.12.11) with ESMTP id i6LHbhJC072954; Wed, 21 Jul 2004 19:37:43 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.11/8.12.11/Submit) id i6LHbhmP072953; Wed, 21 Jul 2004 19:37:43 +0200 (CEST) (envelope-from ticso) Date: Wed, 21 Jul 2004 19:37:43 +0200 From: Bernd Walter To: Scott Long Message-ID: <20040721173742.GG70663@cicely12.cicely.de> References: <20040721170534.GF70663@cicely12.cicely.de> <40FEA412.3050900@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40FEA412.3050900@freebsd.org> X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.6i X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.61 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on cicely5.cicely.de cc: ticso@cicely.de cc: current@freebsd.org Subject: Re: GIANT question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2004 17:38:34 -0000 On Wed, Jul 21, 2004 at 11:12:50AM -0600, Scott Long wrote: > Bernd Walter wrote: > > >Say I have a driver that could run without needing GIANT, but > >makes use of a subsystem that requires GIANT. > >Removing D_NEEDGIANT in cdevsw seems to be enough to get called > >from userland without GIANT held. > >Now I need to aquire GIANT bevor calling the subsystem and release > >it on return. > >What I've found so far is DROP_GIANT/PICKUP_GIANT, which has to be > >paired the other way. > >What is the prefered way to get/release GIANT in that case? > > > > mtx_lock(&Giant); > call_code_needing_giant(); > mtx_unlock(&Giant); Ah - now I got it - the DROP/PICKUP are just macros to handle recurision level. > Note that you must not be holding any locks when you go to aquire Giant. That's clear. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 17:43: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 47BFC16A4CE for ; Wed, 21 Jul 2004 17:43:25 +0000 (GMT) Received: from apathy.neglect.us (rapture.nine.org [69.17.66.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6978943D55 for ; Wed, 21 Jul 2004 17:43:24 +0000 (GMT) (envelope-from matt+list.sw.freebsd.current@publicly.neglect.us) Received: from [192.168.20.34] (ipffw01-dmz1.ipfabrics.com [4.18.226.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by apathy.neglect.us (Postfix) with ESMTP id 36A44CEE for ; Wed, 21 Jul 2004 13:43:23 -0400 (EDT) Date: Wed, 21 Jul 2004 10:43:20 -0700 From: Matt White To: freebsd-current@freebsd.org Message-ID: <3270557515.1090406600@[192.168.20.34]> In-Reply-To: <000001c46f11$1f53a880$132a15ac@spud> References: <000001c46f11$1f53a880$132a15ac@spud> X-Mailer: Mulberry/3.1.2 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: RE: fetch hangs, part 2 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, 21 Jul 2004 17:43:25 -0000 In my case, I tracked this down to either my netscreen5 or the cable into it going south. It's a bit strange because other software wasn't having an issue, so I'll probably look at this more in the next few days. But for now, removing that box from my network has made fetch happy again, which in turn has made me happy again. -Matt --On Wednesday, July 21, 2004 3:54 AM -0700 Darren Pilgrim wrote: >> From: Robert Watson [mailto:rwatson@freebsd.org] >> >> >> On Tue, 20 Jul 2004, Darren Pilgrim wrote: >> >> > I've been having the same (or a similar problem). Fetching the >> > distfile for a port will hang. I poked some more at this and found >> > that all the sites fetch is hanging on successfully negotiate the TCP >> > connection then go dead without closing the connection. My workaround >> > has been to edit the Makefile and remove the offending site from >> > MASTER_SITES or manually fetch from ftp.freebsd.org. >> >> Could you try disabling TCP SACK > > Set net.inet.tcp.delayed_ack=0? > >> and see if things "get better"? It's one >> of the things that has changed in the TCP code recently. This could well >> be a user space fetch issue, but it would be worth trying it to see, if >> only to rule it out. > > It didn't change. The connections still hung. > > From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 17:50: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 EAF5316A4D0 for ; Wed, 21 Jul 2004 17:50:06 +0000 (GMT) Received: from pimout3-ext.prodigy.net (pimout3-ext.prodigy.net [207.115.63.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6746943D31 for ; Wed, 21 Jul 2004 17:50:06 +0000 (GMT) (envelope-from bob@immure.com) Received: from maul.immure.com (adsl-66-136-206-1.dsl.austtx.swbell.net [66.136.206.1])i6LHnqlM114528; Wed, 21 Jul 2004 13:49:53 -0400 Received: from luke.immure.com (luke.immure.com [10.1.132.3]) by maul.immure.com (8.12.11/8.12.11) with ESMTP id i6LHnoa7043599; Wed, 21 Jul 2004 12:49:50 -0500 (CDT) (envelope-from bob@immure.com) Received: from luke.immure.com (localhost [127.0.0.1]) by luke.immure.com (8.12.11/8.12.11) with ESMTP id i6LHnobp092602; Wed, 21 Jul 2004 12:49:50 -0500 (CDT) (envelope-from bob@luke.immure.com) Received: (from bob@localhost) by luke.immure.com (8.12.11/8.12.11/Submit) id i6LHnoE5092601; Wed, 21 Jul 2004 12:49:50 -0500 (CDT) (envelope-from bob) Date: Wed, 21 Jul 2004 12:49:50 -0500 From: Bob Willcox To: jesk Message-ID: <20040721174950.GE89322@luke.immure.com> References: <056801c46eb3$bd0e2a40$45fea8c0@turbofresse> <20040721044816.GA56020@dan.emsphone.com> <01f201c46f45$231aec10$45fea8c0@turbofresse> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01f201c46f45$231aec10$45fea8c0@turbofresse> User-Agent: Mutt/1.5.6i X-immure-MailScanner-Information: Please contact the ISP for more information X-immure-MailScanner: Found to be clean X-MailScanner-From: bob@immure.com cc: freebsd-current@freebsd.org cc: Dan Nelson Subject: Re: I/O or Threading Suffer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bob Willcox List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2004 17:50:07 -0000 On Wed, Jul 21, 2004 at 07:07:00PM +0200, jesk wrote: > > Ah. now that's a different story. You're out of the control of the > > process scheduler and into the disk. I don't suppose you're using an > > IDE/ATA disk with no tagged queueing? :) Run "dmesg | grep depth.queue" > > to see how many requests can be queued up on your disk at once. > > > > That dd is stuffing lots of dirty data into the disk cache, and all the > > other processes have to wait in line to get their I/Os done. You'll > > see much better results from a SCSI disk (with usual queue depths > > between 32 and 64), and even better results from a multi-disk hardware > > RAID array (which will have a large write cache). > > > > -- > > Dan Nelson > > dnelson@allantgroup.com > > _______________________________________________ > > 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" > > > > > when system doesnt response any more in cause of high write operations > on the disk then the reason for this is not looked up in the device device > configuration or in non-scsi hardware ;) I have to agree with Dan here. I tried the simple dd test on one of my 5-current systems here that has both IDE disks and an LSI 320-2 SCSI RAID controller with 256 MB of writeback cache. When running the dd to one of the IDE drives the delay was _very_ noticable when attempting simultaneous commands that did I/O to that same disk (often the command didn't seem to even run till the dd completed). However, when doing this same thing to a filesystem on the LSI array their was no decernable delay (though the command did take abit longer to run). So, in my case anyway, I was seeing what I'm convinced was I/O starvation on the IDE disk but not on the hardware RAID controller attached disk. Bob -- Bob Willcox Serocki's Stricture: bob@immure.com Marriage is always a bachelor's last option. Austin, TX From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 18:08: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 5933F16A4CE for ; Wed, 21 Jul 2004 18:08:12 +0000 (GMT) Received: from web11408.mail.yahoo.com (web11408.mail.yahoo.com [216.136.131.238]) by mx1.FreeBSD.org (Postfix) with SMTP id 339FE43D3F for ; Wed, 21 Jul 2004 18:08:12 +0000 (GMT) (envelope-from shizukakudo_99@yahoo.com) Message-ID: <20040721180811.89160.qmail@web11408.mail.yahoo.com> Received: from [218.103.236.13] by web11408.mail.yahoo.com via HTTP; Wed, 21 Jul 2004 11:08:11 PDT Date: Wed, 21 Jul 2004 11:08:11 -0700 (PDT) From: Shizuka Kudo To: Hidetoshi Shimokawa In-Reply-To: <87k6wzphlq.wl@tora.nunu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org cc: Andrew Gallatin Subject: Re: Excellent job on the firewire 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: Wed, 21 Jul 2004 18:08:12 -0000 --- Hidetoshi Shimokawa wrote: > At Mon, 19 Jul 2004 19:37:04 +0100, > Doug Rabson wrote: > > > > On Monday 19 July 2004 17:19, Shizuka Kudo wrote: > > > Hi, > > > > > > Anyone has experience with the newly added IP over 1394 support, i.e. > > > fwip? > > > > > > I compiled it in with the latest kernel at 17 July, but the box > > > cannot ping with a M$ & linux box. > > > > I have that fixed locally but I want to fix some other problems with the > > firewire driver - mainly that my freebsd boxes often go haywire when I > > plug a windows box into the bus. I also want to finish writing the code > > for freebsd to be a fully functional isochronous bus manager. > > Try this patch for temporary fix. > > --- //depot/vendor/freebsd/src/sys/dev/firewire/if_fwip.c 2004/06/14 09:36:01 > +++ //depot/user/simokawa/firewire/sys/dev/firewire/if_fwip.c 2004/07/11 06:47:39 > @@ -91,7 +91,7 @@ > static void fwip_unicast_input(struct fw_xfer *); > > static int fwipdebug = 0; > -static int broadcast_channel = 31; /* XXX */ > +static int broadcast_channel = 0xc0 | 0x1f; /* tag | channel(XXX) */ > static int tx_speed = 2; > static int rx_queue_len = FWMAXQUEUE; > > Thanks. It works. I could now setup static IP address in M$ box and ping to my -current. Now, yes, it still hang after a few hours. Once again, thank you for all of you on the effort to develop fireware support. Excellent work! > /\ Hidetoshi Shimokawa > \/ simokawa@sat.t.u-tokyo.ac.jp > PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html > __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 18:13: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 2CF2B16A4CE for ; Wed, 21 Jul 2004 18:13:22 +0000 (GMT) Received: from encontacto.net (dsl-200-95-35-213.prod-infinitum.com.mx [200.95.35.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 559B643D2F for ; Wed, 21 Jul 2004 18:13:21 +0000 (GMT) (envelope-from eculp@encontacto.net) Received: from localhost (localhost [127.0.0.1]) (uid 80) by encontacto.net with local; Wed, 21 Jul 2004 13:19:24 -0500 Received: from dsl-200-95-35-213.prod-infinitum.com.mx (dsl-200-95-35-213.prod-infinitum.com.mx [200.95.35.213]) by mail.encontacto.net (Horde) with HTTP for ; Wed, 21 Jul 2004 13:19:24 -0500 Message-ID: <20040721131924.pk4k0skg0gkckwso@mail.encontacto.net> Date: Wed, 21 Jul 2004 13:19:24 -0500 From: Edwin Culp To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs X-Originating-IP: 200.95.35.213 Subject: device_attach: fdc0 attach returned 6 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, 21 Jul 2004 18:13:22 -0000 Could this be a problem in current or could it be my cheapy AMD 2200+ mk40v/vn Shuttle motherboard that works great in every other respect except the floppy. fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3 irq 6 drq 2 on acpi0 fdc0: I/O to control range incorrect device_attach: fdc0 attach returned 6 I'm running everything in sync from yesterday's cvsup and build. Thanks, ed From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 18:33: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 BE00516A4CE for ; Wed, 21 Jul 2004 18:33:05 +0000 (GMT) Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C11943D54 for ; Wed, 21 Jul 2004 18:33:05 +0000 (GMT) (envelope-from cpghost@cordula.ws) Received: from [192.168.254.3] (bsdbox [192.168.254.3]) by fw.farid-hajji.net (Postfix) with ESMTP id 4733C4B1D3; Wed, 21 Jul 2004 20:33:01 +0200 (CEST) Message-ID: <40FEB7DA.4040601@cordula.ws> Date: Wed, 21 Jul 2004 20:37:14 +0200 From: cpghost User-Agent: Mozilla Thunderbird 0.7.1 (X11/20040710) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pablo.morales@abitab.com.uy References: <20040721153259.7E9E623FBD@mail.abitab.com.uy> In-Reply-To: <20040721153259.7E9E623FBD@mail.abitab.com.uy> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Patrick Gardella cc: "current@freebsd.org" cc: "jmelo-lists@freebsdbrasil.com.br" Subject: Re: FreeBSD embedded: TinyBSD 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, 21 Jul 2004 18:33:05 -0000 pablo.morales@abitab.com.uy wrote: >I'm working with Some GEODE stuff, using linux, I'm using the terminals >just like that, remote PXE booting with nfs-root. > > I'm using nanobsd on Soekris net4801 boards (GEODE CPU): /usr/src/tools/tools/nanobsd (5.X only) It's bigger than tinybsd, but you can customize it further by removing stuff you don't need in a configure script, just before it creates the flash image. Don't forget the CPU_GEODE kernel option. Good luck! -cpghost. -- Cordula's Web. http://www.cordula.ws/ From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 18:49: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 90ABA16A4CE for ; Wed, 21 Jul 2004 18:49:03 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8826C43D1F for ; Wed, 21 Jul 2004 18:49:03 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 78B6472DF2; Wed, 21 Jul 2004 11:49:03 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 763EA72DB5; Wed, 21 Jul 2004 11:49:03 -0700 (PDT) Date: Wed, 21 Jul 2004 11:49:03 -0700 (PDT) From: Doug White To: Willem Jan Withagen In-Reply-To: <021001c46e97$84c05210$471b3dd4@digiware.nl> Message-ID: <20040721114745.X81889@carver.gumbysoft.com> References: <021001c46e97$84c05210$471b3dd4@digiware.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@FreeBSD.ORG Subject: Re: Erros in: make -j 16 buildword 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, 21 Jul 2004 18:49:03 -0000 On Tue, 20 Jul 2004, Willem Jan Withagen wrote: > Hi, > > One way or another it seems that I can no longer buildworld with -j16. > -j8 works perfectly, but -j16 fails consistently at: [...] > > Unless anybody has suggestions of which programs generate these tearse > messages??? > Or a way to get make to be more informative??? You need to capture the entire output since the error is buried in there. Make doesn't abort -j builds until all the subprocesses are finished, and they can run for a long time... -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 18: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 422CA16A4CE for ; Wed, 21 Jul 2004 18:51:33 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32FB343D49 for ; Wed, 21 Jul 2004 18:51:33 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 26CCD72DF2; Wed, 21 Jul 2004 11:51:33 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 243AA72DB5; Wed, 21 Jul 2004 11:51:33 -0700 (PDT) Date: Wed, 21 Jul 2004 11:51:33 -0700 (PDT) From: Doug White To: Matt White In-Reply-To: <3270557515.1090406600@[192.168.20.34]> Message-ID: <20040721115021.J81889@carver.gumbysoft.com> References: <000001c46f11$1f53a880$132a15ac@spud> <3270557515.1090406600@[192.168.20.34]> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: RE: fetch hangs, part 2 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, 21 Jul 2004 18:51:33 -0000 On Wed, 21 Jul 2004, Matt White wrote: > In my case, I tracked this down to either my netscreen5 or the cable into > it going south. It's a bit strange because other software wasn't having an > issue, so I'll probably look at this more in the next few days. But for > now, removing that box from my network has made fetch happy again, which in > turn has made me happy again. It might have been breaking passive-mode FTP. I've noticed this problem coming from certain places. Thankfully not from my workplace or home :) Some older inspective firewalls don't understand passive mode and drop the connection. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 19: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 7A8D816A4CE; Wed, 21 Jul 2004 19:47:32 +0000 (GMT) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CF3943D49; Wed, 21 Jul 2004 19:47:32 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from speck.techno.pagans (c-24-21-241-225.client.comcast.net [24.21.241.225]) by mail.bitfreak.org (Postfix) with ESMTP id 859FD2A477; Wed, 21 Jul 2004 12:47:28 -0700 (PDT) Received: from spud (spud.techno.pagans [172.21.42.19]) by speck.techno.pagans (Postfix) with ESMTP id DBC24A926; Wed, 21 Jul 2004 12:45:35 -0700 (PDT) From: "Darren Pilgrim" To: "'Andre Oppermann'" Date: Wed, 21 Jul 2004 12:47:19 -0700 Message-ID: <000001c46f5b$88eff1f0$132a15ac@spud> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <40FE8D0A.2030407@freebsd.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal cc: 'Matt White' cc: freebsd-current@freebsd.org cc: 'Robert Watson' Subject: RE: fetch hangs, part 2 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, 21 Jul 2004 19:47:32 -0000 > From: Andre Oppermann [mailto:andre@freebsd.org]=20 >=20 > Darren sent me a list with sites where he experiences the=20 > problem and I > have tested them with FreeBSD 5-CURRENT (yesterday's), 4.10-STABLE and > Windows 2kSP4. None worked. For FreeBSD fetch waited for=20 > the connection > timeout and went to the second site to fetch the tarball=20 > (successfully). >=20 > Maybe he was just not patient enough to wait for fetch to move on. Probably not. :) On the machine in question, 1-2 minutes is longer than the time from = extract to package for most ports. I've since set FETCH_CMD=3D/usr/bin/fetch = -ARrT 10 in /etc/make.conf to cycle through sites more quickly. From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 20:05:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E267E16A4CE; Wed, 21 Jul 2004 20:05:25 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.12.11/8.12.11) with ESMTP id i6LK5P5f098394; Wed, 21 Jul 2004 16:05:25 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.12.11/8.12.11/Submit) id i6LK5OLD098393; Wed, 21 Jul 2004 16:05:24 -0400 (EDT) (envelope-from green) Date: Wed, 21 Jul 2004 16:05:24 -0400 From: Brian Fundakowski Feldman To: Greg Skafte Message-ID: <20040721200524.GK1009@green.homeunix.org> References: <20040721160434.GA4506@trollkarl.skafte.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040721160434.GA4506@trollkarl.skafte.org> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: panic: mb_init_pack(): Can't deal with failure yet. 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, 21 Jul 2004 20:05:26 -0000 On Wed, Jul 21, 2004 at 10:04:34AM -0600, Greg Skafte wrote: > panic: mb_init_pack(): Can't deal with failure yet. > panic messages: > --- > panic: mb_init_pack(): Can't deal with failure yet. > cpuid = 0; > boot() called on cpu#0 This is a known problem awaiting more testing before the solution can be committed. Please test this patch and let me know if there's something wrong still; if you can stress-test it hard, that would be great :) -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 20:10: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 1B32C16A4D0 for ; Wed, 21 Jul 2004 20:10:15 +0000 (GMT) Received: from apathy.neglect.us (rapture.nine.org [69.17.66.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2E4943D4C for ; Wed, 21 Jul 2004 20:10:14 +0000 (GMT) (envelope-from matt+list.sw.freebsd.current@publicly.neglect.us) Received: from [192.168.20.34] (ipffw01-dmz1.ipfabrics.com [4.18.226.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by apathy.neglect.us (Postfix) with ESMTP id CB9C5CC3 for ; Wed, 21 Jul 2004 16:10:13 -0400 (EDT) Date: Wed, 21 Jul 2004 13:10:12 -0700 From: Matt White To: freebsd-current@freebsd.org Message-ID: <3279369656.1090415412@[192.168.20.34]> In-Reply-To: <20040721115021.J81889@carver.gumbysoft.com> References: <000001c46f11$1f53a880$132a15ac@spud> <3270557515.1090406600@[192.168.20.34]> <20040721115021.J81889@carver.gumbysoft.com> X-Mailer: Mulberry/3.1.2 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: RE: fetch hangs, part 2 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, 21 Jul 2004 20:10:15 -0000 I don't think so in this case since I was using this same netscreen with a FreeBSD 5.1 box without incident. I'm actually suspicious of the cabling at the moment, but I have higher priorities than to figure that out at the moment. -Matt --On Wednesday, July 21, 2004 11:51 AM -0700 Doug White wrote: > On Wed, 21 Jul 2004, Matt White wrote: > >> In my case, I tracked this down to either my netscreen5 or the cable into >> it going south. It's a bit strange because other software wasn't having >> an issue, so I'll probably look at this more in the next few days. But >> for now, removing that box from my network has made fetch happy again, >> which in turn has made me happy again. > > It might have been breaking passive-mode FTP. I've noticed this problem > coming from certain places. Thankfully not from my workplace or home :) > > Some older inspective firewalls don't understand passive mode and drop the > connection. > > -- > Doug White | FreeBSD: The Power to Serve > dwhite@gumbysoft.com | 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 Jul 21 20:31: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 4A35216A4CE; Wed, 21 Jul 2004 20:31:07 +0000 (GMT) Received: from mailout1.informatik.tu-muenchen.de (mailout1.informatik.tu-muenchen.de [131.159.0.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA87143D41; Wed, 21 Jul 2004 20:31:06 +0000 (GMT) (envelope-from langd@informatik.tu-muenchen.de) Date: Wed, 21 Jul 2004 22:31:05 +0200 From: Daniel Lang To: Brooks Davis , harti@freebsd.org, Garrett Wollman Message-ID: <20040721203105.GA55687@atrbg11.informatik.tu-muenchen.de> References: <20040721151427.GC54664@atrbg11.informatik.tu-muenchen.de> <200407211622.i6LGMZrm040478@khavrinen.lcs.mit.edu> <40F963D8.6010201@freebsd.org> <20040719060730.GA87697@nagual.pp.ru> <20040720081051.GB3001@cirb503493.alcatel.com.au> <20040721151427.GC54664@atrbg11.informatik.tu-muenchen.de> <20040721162706.GA12760@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200407211622.i6LGMZrm040478@khavrinen.lcs.mit.edu> <20040721162706.GA12760@Odin.AC.HMC.Edu> X-Geek: GCS/CC d-- s: a- C++$ UBS++++$ P+++$ L- E-(---) W+++(--) N++ o K w--- O? M? V? PS+(++) PE--(+) Y+ PGP+ t++ 5+++ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r+++ y+ User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at informatik.tu-muenchen.de cc: current@freebsd.org Subject: Re: NEW TAR 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, 21 Jul 2004 20:31:07 -0000 Hi, Brooks Davis wrote on Wed, Jul 21, 2004 at 09:27:06AM -0700: [..] > Since sparse files over commit the disk, they should only be created > deliberatly. Otherwise you can easily get in trouble if you try to use > reserved space later since it won't actually be reserved. Consider the > case of a file system image created with "dd if=/dev/zero ...; newfw > ...". If your archiver decides to be "smart" and restore a copy of that > file sparce and then you use up the availble blocks on your disk you're > going to be in a world of hurt. I wouldn't be suprised it that resulted > in a panic. [Garret writes:] > You've never run out of disk space as a result of a sparse file > becoming non-sparse? That was not my point. I agree, that it should be done deliberately. There should be a non-default command-line switch to enable sparse files or not (as it is common practice now anyway). But if someone chooses to use sparse files upon archive extraction (I believe this is the more important part), it does not matter how the original file layout was in terms of blocks of allocated zeroes and unallocated blocks. To Harti: I admit I don't know for sure, but to my understanding the handling of the sparse file is done in the filesystem layer and not in the application, right? Then all possible performance benefit on reading a sparse file should be gained anyway. Regardless if the application (the archiver) knows about the locations of the gaps or not.... Best regards, Daniel -- IRCnet: Mr-Spock - All your .sigs are belong to us - Daniel Lang * dl@leo.org * +49 89 289 18532 * http://www.leo.org/~dl/ From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 20:34: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 08B4616A4CF for ; Wed, 21 Jul 2004 20:34:58 +0000 (GMT) Received: from mage.trollkarl.net (018.216-123-203-0.interbaun.com [216.123.203.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E80643D39 for ; Wed, 21 Jul 2004 20:34:55 +0000 (GMT) (envelope-from skafte@trollkarl.net) Received: from trollkarl.skafte.org (root@trollkarl [192.168.100.16]) by mage.trollkarl.net (8.12.11/8.12.11) with ESMTP id i6LKYs8D055305 for ; Wed, 21 Jul 2004 14:34:54 -0600 (MDT) (envelope-from skafte@trollkarl.net) Received: from trollkarl.skafte.org (skafte@localhost [127.0.0.1]) i6LKYsp3004749 for ; Wed, 21 Jul 2004 14:34:54 -0600 (MDT) (envelope-from skafte@trollkarl.skafte.org) Received: (from skafte@localhost) by trollkarl.skafte.org (8.12.11/8.12.9/Submit) id i6LKYsrw004748 for freebsd-current@freebsd.org; Wed, 21 Jul 2004 14:34:54 -0600 (MDT) Date: Wed, 21 Jul 2004 14:34:54 -0600 From: Greg Skafte To: freebsd-current@freebsd.org Message-ID: <20040721203453.GA4615@trollkarl.skafte.org> References: <20040721160434.GA4506@trollkarl.skafte.org> <20040721200524.GK1009@green.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040721200524.GK1009@green.homeunix.org> User-Agent: Mutt/1.4.2.1i Organization: Gregs Hidey Hole Errors-To: skafte@trollkarl.net Subject: Re: panic: mb_init_pack(): Can't deal with failure yet. 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, 21 Jul 2004 20:34:58 -0000 should I also be brining my machine upto "latest" stuff, or is my 2004.06.15.01.00.00 Quoting Brian Fundakowski Feldman (green@freebsd.org) On Subject: Re: panic: mb_init_pack(): Can't deal with failure yet. Date: Wed, Jul 21, 2004 at 04:05:24PM -0400 > On Wed, Jul 21, 2004 at 10:04:34AM -0600, Greg Skafte wrote: > > panic: mb_init_pack(): Can't deal with failure yet. > > panic messages: > > --- > > panic: mb_init_pack(): Can't deal with failure yet. > > cpuid = 0; > > boot() called on cpu#0 > > This is a known problem awaiting more testing before the solution can be > committed. Please test this patch and let me know if there's something > wrong still; if you can stress-test it hard, that would be great :) > > > -- > Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ > <> green@FreeBSD.org \ The Power to Serve! \ > Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ > -- Email: skafte@trollkarl.net ICQ: 93234105 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 20:36: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 C780716A4CE for ; Wed, 21 Jul 2004 20:36:20 +0000 (GMT) Received: from web50707.mail.yahoo.com (web50707.mail.yahoo.com [206.190.38.105]) by mx1.FreeBSD.org (Postfix) with SMTP id 84B1343D49 for ; Wed, 21 Jul 2004 20:36:20 +0000 (GMT) (envelope-from w8hdkim@yahoo.com) Message-ID: <20040721203620.72466.qmail@web50707.mail.yahoo.com> Received: from [68.167.120.18] by web50707.mail.yahoo.com via HTTP; Wed, 21 Jul 2004 13:36:20 PDT Date: Wed, 21 Jul 2004 13:36:20 -0700 (PDT) From: Kim Culhan To: freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: laptop for -current 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, 21 Jul 2004 20:36:20 -0000 Anyone know a laptop they think is good for FreeBSd-current? With all the differences in hardware, trying to find one which is mostly compatible is not straightforward. The manufacturers don't make it easier.. tnc -kim __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 20:39: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 3C73C16A4CE for ; Wed, 21 Jul 2004 20:39:04 +0000 (GMT) Received: from pfepa.post.tele.dk (pfepa.post.tele.dk [195.41.46.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC18943D53 for ; Wed, 21 Jul 2004 20:39:03 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (0x50a07c53.naenxx7.adsl-dhcp.tele.dk [80.160.124.83]) by pfepa.post.tele.dk (Postfix) with ESMTP id CADE947FE86; Wed, 21 Jul 2004 22:39:02 +0200 (CEST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i6LKd152092762; Wed, 21 Jul 2004 22:39:02 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Kim Culhan From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 21 Jul 2004 13:36:20 PDT." <20040721203620.72466.qmail@web50707.mail.yahoo.com> Date: Wed, 21 Jul 2004 22:39:01 +0200 Message-ID: <92761.1090442341@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org Subject: Re: laptop for -current 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, 21 Jul 2004 20:39:04 -0000 In message <20040721203620.72466.qmail@web50707.mail.yahoo.com>, Kim Culhan wri tes: >Anyone know a laptop they think is good for FreeBSd-current? I bought a IBM T41p with the IBM wireless (== atheros) and it works great. As long as the CD drive is in the machine ACPI works flawlessly. -- 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 Jul 21 20:51: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 8A07616A4CE for ; Wed, 21 Jul 2004 20:51:58 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.197]) by mx1.FreeBSD.org (Postfix) with SMTP id 224A343D55 for ; Wed, 21 Jul 2004 20:51:58 +0000 (GMT) (envelope-from joseph.peterson@gmail.com) Received: by mproxy.gmail.com with SMTP id 72so29827rnf for ; Wed, 21 Jul 2004 13:51:57 -0700 (PDT) Received: by 10.38.209.75 with SMTP id h75mr181358rng; Wed, 21 Jul 2004 13:51:57 -0700 (PDT) Message-ID: <38a23c3604072113512ee32bcd@mail.gmail.com> Date: Wed, 21 Jul 2004 15:51:57 -0500 From: Joseph Peterson To: freebsd-current@freebsd.org In-Reply-To: <92761.1090442341@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <92761.1090442341@critter.freebsd.dk> Subject: Re: laptop for -current 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, 21 Jul 2004 20:51:58 -0000 I use a Toshiba A25-S279 and it works great, wireless (Atheros) works, CD has some minor issues that I imagine is just a configuration... burncd locks up and the only solution is to power cycle the machine, probably a dma or similar issue, otherwise everything is great! -- sound works, video is 1024x768 On Wed, 21 Jul 2004 22:39:01 +0200, Poul-Henning Kamp wrote: > In message <20040721203620.72466.qmail@web50707.mail.yahoo.com>, Kim Culhan wri > tes: > > >Anyone know a laptop they think is good for FreeBSd-current? > > I bought a IBM T41p with the IBM wireless (== atheros) and it works > great. > > As long as the CD drive is in the machine ACPI works flawlessly. > > -- > 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. > > > _______________________________________________ > 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 Jul 21 21:19: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 1165B16A4CE for ; Wed, 21 Jul 2004 21:19:22 +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 1098A43D41 for ; Wed, 21 Jul 2004 21:19:21 +0000 (GMT) (envelope-from le@FreeBSD.org) Received: from le.vpn.univie.ac.at (le.vpn.univie.ac.at [131.130.222.177]) by imap.univie.ac.at (8.12.10/8.12.10) with ESMTP id i6LLIoVq864060; Wed, 21 Jul 2004 23:18:59 +0200 Date: Wed, 21 Jul 2004 23:18:48 +0200 (CEST) From: Lukas Ertl To: Poul-Henning Kamp In-Reply-To: <92761.1090442341@critter.freebsd.dk> Message-ID: <20040721231723.A601@korben.in.tern> References: <92761.1090442341@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-DCC-ZID-Univie-Metrics: mail 4249; Body=3 Fuz1=3 Fuz2=3 cc: Kim Culhan cc: freebsd-current@FreeBSD.org Subject: Re: laptop for -current 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, 21 Jul 2004 21:19:22 -0000 On Wed, 21 Jul 2004, Poul-Henning Kamp wrote: > In message <20040721203620.72466.qmail@web50707.mail.yahoo.com>, Kim Culhan wri > tes: > >> Anyone know a laptop they think is good for FreeBSd-current? > > I bought a IBM T41p with the IBM wireless (== atheros) and it works > great. I can only second that. I have a T40 and FreeBSD support is really great: ACPI makes no problems, and with the ndisulator I can use the built-in wireless card. 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 Wed Jul 21 21:20: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 00A7A16A4CE; Wed, 21 Jul 2004 21:20:30 +0000 (GMT) Received: from otter3.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 587FE43D46; Wed, 21 Jul 2004 21:20:27 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by otter3.centtech.com (8.12.3/8.12.3) with ESMTP id i6LLKQE8039992; Wed, 21 Jul 2004 16:20:26 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <40FEDE09.1040100@centtech.com> Date: Wed, 21 Jul 2004 16:20:09 -0500 From: Eric Anderson User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040720) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lukas Ertl References: <92761.1090442341@critter.freebsd.dk> <20040721231723.A601@korben.in.tern> In-Reply-To: <20040721231723.A601@korben.in.tern> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Poul-Henning Kamp cc: freebsd-current@freebsd.org cc: Kim Culhan Subject: Re: laptop for -current 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, 21 Jul 2004 21:20:30 -0000 Lukas Ertl wrote: > On Wed, 21 Jul 2004, Poul-Henning Kamp wrote: > >> In message <20040721203620.72466.qmail@web50707.mail.yahoo.com>, Kim >> Culhan wri >> tes: >> >>> Anyone know a laptop they think is good for FreeBSd-current? >> >> >> I bought a IBM T41p with the IBM wireless (== atheros) and it works >> great. > > > I can only second that. I have a T40 and FreeBSD support is really > great: ACPI makes no problems, and with the ndisulator I can use the > built-in wireless card. I'm using a Dell D600, and it's excellent.. Eric -- ------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Talk sense to a fool and he calls you foolish. ------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 21:25: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 1FF7016A4CE for ; Wed, 21 Jul 2004 21:25:10 +0000 (GMT) Received: from parati.mdbrasil.com.br (parati.mdbrasil.com.br [200.210.70.4]) by mx1.FreeBSD.org (Postfix) with SMTP id D0AAE43D58 for ; Wed, 21 Jul 2004 21:25:08 +0000 (GMT) (envelope-from jmelo-lists@freebsdbrasil.com.br) Received: (qmail 96104 invoked by uid 0); 21 Jul 2004 21:25:56 -0000 Received: from jmelo-lists@freebsdbrasil.com.br by parati.mdbrasil.com.br by uid 82 with qmail-scanner-1.20rc1 (uvscan: v4.1.60/v4288. Clear:RC:1:. Processed in 0.175929 secs); 21 Jul 2004 21:25:56 -0000 Received: from unknown (HELO ?192.168.1.2?) (200.167.244.39) by parati.mdbrasil.com.br with SMTP; 21 Jul 2004 18:25:55 -0300 From: Jean Milanez Melo To: pablo.morales@abitab.com.uy In-Reply-To: <20040721153259.7E9E623FBD@mail.abitab.com.uy> References: <20040721153259.7E9E623FBD@mail.abitab.com.uy> Content-Type: text/plain Organization: FreeBSD Brasil LTDA Message-Id: <1090445683.665.28.camel@offset.freebsdbrasil.com.br> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 21 Jul 2004 18:34:43 -0300 Content-Transfer-Encoding: 7bit cc: Patrick Gardella cc: "current@freebsd.org" Subject: Re: FreeBSD embedded: TinyBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jmelo-lists@freebsdbrasil.com.br List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2004 21:25:10 -0000 Hi, Yes, it refers to the image size according to the space of the destination device. You can create a image with GEODE, put GODE cpu options in TINYBSD kernel file and then test your environment. - Jean On Wed, 2004-07-21 at 12:32, pablo.morales@abitab.com.uy wrote: > HI there boys. > I'm writing to Uruguay > I'm interested in TinyBSD, I'd like to know if the term ebeded refers > only to the *size* or if you have been tweking the kernel code. > > I'm working with Some GEODE stuff, using linux, I'm using the terminals > just like that, remote PXE booting with nfs-root. > > I'd like to have access to your project to give it a try with this > enviroment. > > Thanx. > > > > > > > On 21/7/2004, "Jean Milanez Melo" > wrote: > > >On Wed, 2004-07-21 at 08:58, Patrick Gardella wrote: > >> Is there a web page for TinyBSD? > >> > >> patrick > > > > > >Not yet, but we're going to make one if people like the project and it > > gets well accepted by the community. We're definatelly putting up a > >lot > > of documentation on that page, though. We haven't done so yet because > > currently it's way too simple, as you can run it knowing only the > > information regarding the target device. > > > > For example, assuming a 32MB flash memory, one could use the following > > parameters to create an embedded system: > > > > ./tinybsd.sh 62592 4 32 > > > > Or optionally the name of the output image you want: > > > > ./tinybsd.sh 62592 4 32 myimage.bin > > > >- Jean Milanez Melo > > > >> > >> On Jul 20, 2004, at 11:48 AM, Jean Milanez Melo wrote: > >> > >> > Hello current, > >> > > >> > Please allow me to introduce myself, I'm one of the coordinators of > >> > the Brazilian FreeBSD Users group, coordinator of the official > >> > FreeBSD documentation's translation group and have been working with > >> > embedded FreeBSD systems since year 2000. > >> > > >> > I've been studying NanoBSD ever since Poul-Henning posted about it > >> > on one of > >> > the mailling lists, and I have been following this project closely. > >> > It > >> > really is a great project. > >> > > >> > However, I think it sometimes creates unnecessary partitions, takes > >> > too long to build the system due to make world and it copies lots of > >> > unneeded binaries, taking a lot of precious space. > >> > > >> > So me and Patrick Tracanelli (another active member of the Brazilian > >> > FreeBSD community) decided to write a new set of scripts to build > >> > embedded systems. We've named it TinyBSD, and its goal is to be > >> > faster > >> > at building-time, occupy less space on the target device and to ease > >> > customization like PicoBSD does. > >> > > >> > Untar/gzip the tinybsd.tgz file under /usr/src/release. > >> > > >> > # ls > >> > TINYBSD TODO tinybsd.basefiles tinybsd.sh > >> > > >> > We first take the file TINYBSD, which like in PicoBSD we can use to > >> > define or remove all kernel options to the new system. > >> > > >> > Then we have tinybsd.basefiles, where we define all binaries > >> > necessary > >> > to get the system running and anyone can edit it as they will. > >> > > >> > Finally we have the script itself, tinybsd.sh. It's a simple script, > >> > yet functional. We based it on NanoBSD's and its idea is to create a > >> > temporary work directory where the new system's directory tree will > >> > be > >> > created. Then it'll copy all files listed on tinybsd.basefiles to > >> > this > >> > tree. This copying process is essential to the speed of the building > >> > process, as we eliminate the recompiling phase. The reason for this > >> > is > >> > FreeBSD 5.1' dynamically-linked base system, which take much less > >> > space than the old statically-linked ones. This way we can also do > >> > the > >> > copying without affecting the production system in any way. > >> > > >> > After all this, we compile the kernel using the TINYBSD file and then > >> > we install the necessary libs using the dependencies' output from the > >> > binaries. We populate the /etc directory on the temp work directory > >> > and put in a few important default settings in /etc/rc.conf, like: > >> > > >> > hostname="tinybsd.freebsd.org" > >> > sendmail_enable="NONE" > >> > sshd_enable="YES" > >> > usbd_enable="NO" > >> > inetd_enable="NO" > >> > portmap_enable="NO" > >> > update_motd="NO" > >> > varsize="8192" > >> > diskless_mount="/etc/rc.d/diskless" > >> > > >> > Lastly, we create the empty image according to the specifications for > >> > the device passed in as a parameter and copy the entire temp > >> > directory > >> > to the new image. After that, the user can use dd to write the final > >> > image to the target device. > >> > > >> > Booting the system works as embedded systems do, mounting /var and > >> > /tmp as MFS filesystems. > >> > > >> > The most interesting point is the space used by default, only 19MB. > >> > > >> > As you can see, it's pretty simple. But since PicoBSD is practically > >> > unusable with the 5.x series, TinyBSD could be an interesting > >> > alternative along with NanoBSD to be put on the base system in future > >> > versions. > >> > > >> > Patrick and I have been thinking of enhancing the script and adding > >> > end-user helping tools such dialog-based menus and the likes, for > >> > more > >> > details see our TODO file. In case the FreeBSD project has any > >> > interest > >> > in our project, we can perfectly maintain TinyBSD as an embedded > >> > option > >> > for FreeBSD users. > >> > > >> > We would like that the interested parties make tests and then > >> > report bug, sends sugestions to improve the TinyBSD. > >> > > >> > Thank you for your attention > >> > Jean Milanez Melo > >> > _______________________________________________ > >> > 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 Wed Jul 21 21:25: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 B4B3716A4CE for ; Wed, 21 Jul 2004 21:25:11 +0000 (GMT) Received: from parati.mdbrasil.com.br (parati.mdbrasil.com.br [200.210.70.4]) by mx1.FreeBSD.org (Postfix) with SMTP id B045243D58 for ; Wed, 21 Jul 2004 21:25:10 +0000 (GMT) (envelope-from jmelo-lists@freebsdbrasil.com.br) Received: (qmail 96127 invoked by uid 0); 21 Jul 2004 21:25:58 -0000 Received: from jmelo-lists@freebsdbrasil.com.br by parati.mdbrasil.com.br by uid 82 with qmail-scanner-1.20rc1 (uvscan: v4.1.60/v4288. Clear:RC:1:. Processed in 0.15875 secs); 21 Jul 2004 21:25:58 -0000 Received: from unknown (HELO ?192.168.1.2?) (200.167.244.39) by parati.mdbrasil.com.br with SMTP; 21 Jul 2004 18:25:58 -0300 From: Jean Milanez Melo To: cpghost In-Reply-To: <40FEB7DA.4040601@cordula.ws> References: <20040721153259.7E9E623FBD@mail.abitab.com.uy> <40FEB7DA.4040601@cordula.ws> Content-Type: text/plain Organization: FreeBSD Brasil LTDA Message-Id: <1090445685.665.30.camel@offset.freebsdbrasil.com.br> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 21 Jul 2004 18:34:45 -0300 Content-Transfer-Encoding: 7bit cc: pablo.morales@abitab.com.uy cc: Patrick Gardella cc: "current@freebsd.org" Subject: Re: FreeBSD embedded: TinyBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jmelo-lists@freebsdbrasil.com.br List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2004 21:25:11 -0000 On Wed, 2004-07-21 at 15:37, cpghost wrote: > pablo.morales@abitab.com.uy wrote: > > >I'm working with Some GEODE stuff, using linux, I'm using the terminals > >just like that, remote PXE booting with nfs-root. > > > > > I'm using nanobsd on Soekris net4801 boards (GEODE CPU): > /usr/src/tools/tools/nanobsd (5.X only) > > It's bigger than tinybsd, but you can customize it > further by removing stuff you don't need in a > configure script, just before it creates the > flash image. > Really, TinyBSD is smaller than NanoBSD. In TinyBSD's current dir, remove what you dont need in tinybsd.basefiles. So, run again tinybsd.sh and recreate your image, it's quicker and simpler. Please test TinyBSD and send you sugestions to me. Thanks Jean From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 21:37: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 043EB16A4CE for ; Wed, 21 Jul 2004 21:37:17 +0000 (GMT) Received: from mail.evip.pl (mail.evip.com.pl [212.244.157.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1507F43D1D for ; Wed, 21 Jul 2004 21:37:16 +0000 (GMT) (envelope-from w@evip.pl) Received: from drwebc by mail.evip.pl with drweb-scanned (Exim 4.22) id 1BnOm0-0002sT-9o for current@freebsd.org; Wed, 21 Jul 2004 23:37:12 +0200 Received: from w by mail.evip.pl with local (Exim 4.22) id 1BnOm0-0002sN-6r for current@freebsd.org; Wed, 21 Jul 2004 23:37:12 +0200 Date: Wed, 21 Jul 2004 23:37:12 +0200 From: Wiktor Niesiobedzki To: current@freebsd.org Message-ID: <20040721213712.GL8753@mail.evip.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: LORs with 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: Wed, 21 Jul 2004 21:37:17 -0000 Hi, I don't think, it was reported yet, but here it goes: lock order reversal 1st 0xc0632c80 pf task mtx (pf task mtx) @ /usr/src/sys/contrib/pf/net/pf.c:5822 2nd 0xc066638c tcp (tcp) @ /usr/src/sys/contrib/pf/net/pf.c:2420 KDB: stack backtrace: kdb_backtrace(c05f529a,c066638c,c05f4e21,c05f4e21,c05e7e3f) at kdb_backtrace+0x2e witness_checkorder(c066638c,9,c05e7e3f,974,104) at witness_checkorder+0x672 _mtx_lock_flags(c066638c,0,c05e7e3f,974,c1893230) at _mtx_lock_flags+0x80 pf_socket_lookup(cb9659b4,cb9659b8,2,cb965a70,c14fad00) at pf_socket_lookup+0xb4 pf_test_tcp(cb965a20,cb965a18,2,c14fad00,c1475100) at pf_test_tcp+0x529 pf_test(2,c10d8014,cb965b00,c15276a0,c0665ee0) at pf_test+0x4a3 pf_check_out(0,cb965b00,c10d8014,2,c1475100) at pf_check_out+0x5b pfil_run_hooks(c0665ee0,cb965bc0,c10d8014,2,c04e8a70) at pfil_run_hooks+0xca ip_output(c1475100,0,0,1,0) at ip_output+0x66d ip_forward(c1475100,0,0,1,0) at ip_forward+0x37d ip_input(c1475100,0,c05fad20,96,c0665598) at ip_input+0x65d netisr_processqueue(c0665598,0,c05fad20,fe,c10d62c0) at netisr_processqueue+0x8e swi_net(0,0,c05ef737,263,c063ae60) at swi_net+0xa3 ithread_loop(c10dd400,cb965d48,c05ef52e,328,c10dd400) at ithread_loop+0x172 fork_exit(c04ad4c0,c10dd400,cb965d48) at fork_exit+0xc2 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xcb965d7c, ebp = 0 --- Is there anything I can do, to investigate it further? Cheers, Wiktor Niesiobedzki From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 21:51:49 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 8337516A4CE; Wed, 21 Jul 2004 21:51:49 +0000 (GMT) Received: from tora.nunu.org (YahooBB219003182029.bbtec.net [219.3.182.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7777643D41; Wed, 21 Jul 2004 21:51:47 +0000 (GMT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from tora.nunu.org (unknown [192.168.1.2]) by tora.nunu.org (Postfix) with ESMTP id CE9014D1D6; Thu, 22 Jul 2004 06:53:09 +0900 (JST) Date: Thu, 22 Jul 2004 06:53:09 +0900 Message-ID: <87u0w1ni2i.wl@tora.nunu.org> From: Hidetoshi Shimokawa To: Doug Rabson In-Reply-To: <1090421941.7114.26.camel@builder02.qubesoft.com> References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> <16638.32914.509773.486468@grasshopper.cs.duke.edu> <1090421941.7114.26.camel@builder02.qubesoft.com> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 14) (Reasonable Discussion) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org cc: Andrew Gallatin Subject: Re: Excellent job on the firewire 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: Wed, 21 Jul 2004 21:51:49 -0000 At Wed, 21 Jul 2004 15:59:01 +0100, Doug Rabson wrote: > > If no, assuming I had a Windows or Linux box on the firewire bus, would it be > > possible to access physical memory from a different OS? > > Windows XP has some kind of firewire debug driver that you might have to > load (I haven't read the docs on that). I don't think the linux driver > enables physical access by default but it would be easy to hack it in > (just write all ones to the right fwohci register). The physical access is usually used for SBP-2 initiator mode. Without physical access, the performance of SBP-2 should be poorer and we see more load on CPU. The physical access can be restricted by two way. You can restrict it per node-id and by physical memory range(upper bound). As far as I have tried, WindowsXP seems not to allow physical access of usual nodes. But I think you can easily cheat it by a node with sbp target mode(use sbp_targ(4) ;-). In my opinion, it's hard to ensure security with current OHCI specification. https://www.netsecurity.ne.jp/article/2/6202.html This page describes this problem in Japanese. It says that information source is "iDEFENSE Intelligence Operations, June 18, 2002" but I cannot find the original source (in English). /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 21:59: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 E81C216A4CE; Wed, 21 Jul 2004 21:59:42 +0000 (GMT) Received: from freebsd3.cimlogic.com.au (adsl-20-121.swiftdsl.com.au [218.214.20.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12F3043D48; Wed, 21 Jul 2004 21:59:42 +0000 (GMT) (envelope-from jb@cimlogic.com.au) Received: by freebsd3.cimlogic.com.au (Postfix, from userid 102) id 78A386AC0E; Thu, 22 Jul 2004 07:59:40 +1000 (EST) Date: Thu, 22 Jul 2004 07:59:40 +1000 From: John Birrell To: Bruce Evans Message-ID: <20040721215940.GK22160@freebsd3.cimlogic.com.au> References: <20040721081310.GJ22160@freebsd3.cimlogic.com.au> <20040721102620.GF1009@green.homeunix.org> <20040721220405.Y2346@epsplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040721220405.Y2346@epsplex.bde.org> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: nanosleep returning early 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, 21 Jul 2004 21:59:43 -0000 On Wed, Jul 21, 2004 at 11:01:20PM +1000, Bruce Evans wrote: > On Wed, 21 Jul 2004, Brian Fundakowski Feldman wrote: > > On Wed, Jul 21, 2004 at 06:13:10PM +1000, John Birrell wrote: > > > > > > Today I increased HZ in a current kernel to 1000 when adding dummynet. > > > Now I find that nanosleep regularly comes back a little early. > > > Can anyone explain why? > > The most obvious bug is that nanosleep() uses the low-accuracy interface > getnanouptime(). I can't see why the the problem is more obvious with > large HZ or why it affects short sleeps. From kern_time.c 1.170: > > % static int > % nanosleep1(struct thread *td, struct timespec *rqt, struct timespec *rmt) > % { > % struct timespec ts, ts2, ts3; > % struct timeval tv; > % int error; > % > % if (rqt->tv_nsec < 0 || rqt->tv_nsec >= 1000000000) > % return (EINVAL); > % if (rqt->tv_sec < 0 || (rqt->tv_sec == 0 && rqt->tv_nsec == 0)) > % return (0); > % getnanouptime(&ts); > > This may lag the actual (up)time by 1/HZ seconds. For any NTP clock adjustment to have an effect, it must happen between the time when my (crude) test gets the time and when the kernel calls getnanouptime to fill ts. All the rest of the code in nanosleep1() refers back to the value of ts. Any errors involved in the tv and hz conversions would just cause the code to go around the loop and tsleep more than once. So, does increasing HZ expose the lower accuracy of getnanouptime() and is that what I'm seeing? If so, shouldn't the time interface provided by the kernel to userland at least be consistently inaccurate? Or put another way, why should nanosleep be any less accurate than gettimeofday? Bruce, have you seen this document: ? I'm not looking for a critique here. The document talks about the sleep overruns in various operatingg systems. There is a patch that was applied to DragonFly which aplies to the FreeBSD code base too. -- John Birrell From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 22:02: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 1207D16A4CE for ; Wed, 21 Jul 2004 22:02:47 +0000 (GMT) Received: from freebsd3.cimlogic.com.au (adsl-20-121.swiftdsl.com.au [218.214.20.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id B969343D2D for ; Wed, 21 Jul 2004 22:02:46 +0000 (GMT) (envelope-from jb@cimlogic.com.au) Received: by freebsd3.cimlogic.com.au (Postfix, from userid 102) id B833F6AC0E; Thu, 22 Jul 2004 08:02:45 +1000 (EST) Date: Thu, 22 Jul 2004 08:02:45 +1000 From: John Birrell To: Kim Culhan Message-ID: <20040721220245.GL22160@freebsd3.cimlogic.com.au> References: <92761.1090442341@critter.freebsd.dk> <20040721231723.A601@korben.in.tern> <40FEDE09.1040100@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40FEDE09.1040100@centtech.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: laptop for -current 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, 21 Jul 2004 22:02:47 -0000 On Wed, Jul 21, 2004 at 04:20:09PM -0500, Eric Anderson wrote: > Lukas Ertl wrote: > I'm using a Dell D600, and it's excellent.. I have a Dell Inspiron 1150 which works nicely too. -- John Birrell From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 22:19: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 ED68516A4CF; Wed, 21 Jul 2004 22:19:53 +0000 (GMT) Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62A5343D45; Wed, 21 Jul 2004 22:19:53 +0000 (GMT) (envelope-from pierre.weis@inria.fr) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by nez-perce.inria.fr (8.12.10/8.12.10) with ESMTP id i6LMJiEV016547; Thu, 22 Jul 2004 00:19:44 +0200 Received: (from weis@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id AAA18393; Thu, 22 Jul 2004 00:19:43 +0200 (MET DST) From: Pierre Weis Message-Id: <200407212219.AAA18393@pauillac.inria.fr> In-Reply-To: <40FEDE09.1040100@centtech.com> from Eric Anderson at "Jul 21, 104 04:20:09 pm" To: anderson@centtech.com (Eric Anderson) Date: Thu, 22 Jul 2004 00:19:43 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Miltered: at nez-perce with ID 40FEEC00.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! cc: phk@phk.freebsd.dk cc: freebsd-current@freebsd.org cc: w8hdkim@yahoo.com Subject: Re: laptop for -current 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, 21 Jul 2004 22:19:54 -0000 [...] > I'm using a Dell D600, and it's excellent.. > > Eric > > -- > ------------------------------------------------------------------ > Eric Anderson Sr. Systems Administrator Centaur Technology > Talk sense to a fool and he calls you foolish. > ------------------------------------------------------------------ I'm also running -current on a Dell laptop (a Precision M60 with the large (1920x1200 pixels) screen). It works pretty well, although not perfectly: I have not managed to have ACPI working properly and I have problems with the Nvidia driver (I had to revert to the XFree nv driver to get X running). Also, the FireFox port can be compiled and installed but the resulting program core dumps too often to be usable. This may be because I'm using a cutting edge X-server from XFree86 (version 4.4.99.9); anyway, I am now obliged to use Netscape which is not my browser of choice :( On the other hand, the OS is rock solid and all the sub-systems work perfectly: USB1, USB2, FireWire, PC-cards, CD/RW/DVD reader, Bluetooth, the Broadcom NICs (either the 10/100/1000 Mb/s wired ethernet, or the 802.11 a/b/g wireless card)! To my knowledge, this OS is the best fit for this machine :) Also, the machine itself is excellent: it runs fast, has a silent and fast hard disk and the screen is a dream. This laptop is just a bit heavy to carry and it pumps the battery way too quickly (in my case, 2 hours and a half is enough to dry it up). In conclusion: a very good OS/machine combination, that would be excellent if only the ACPI system could slow down the processor and put the machine asleep... Hope this helps, Pierre Weis INRIA, Projet Cristal, Pierre.Weis@inria.fr, http://pauillac.inria.fr/~weis/ From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 22:32: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 232C616A4CE for ; Wed, 21 Jul 2004 22:32:03 +0000 (GMT) Received: from smtp08.web.de (smtp08.web.de [217.72.192.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id A672943D31 for ; Wed, 21 Jul 2004 22:32:02 +0000 (GMT) (envelope-from nakal@web.de) Received: from [217.225.230.147] (helo=[217.225.230.147]) by smtp08.web.de with esmtp (TLSv1:DES-CBC3-SHA:168) (WEB.DE 4.101 #44) id 1BnPd2-0007Eh-00; Thu, 22 Jul 2004 00:32:00 +0200 From: Martin To: Kim Culhan In-Reply-To: <20040721203620.72466.qmail@web50707.mail.yahoo.com> References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> Content-Type: text/plain Message-Id: <1090449108.72182.31.camel@klotz.local> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 22 Jul 2004 00:31:50 +0200 Content-Transfer-Encoding: 7bit Sender: nakal@web.de cc: FreeBSD Current Subject: Re: laptop for -current 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, 21 Jul 2004 22:32:03 -0000 Am Mi, den 21.07.2004 schrieb Kim Culhan um 22:36: > Anyone know a laptop they think is good for FreeBSd-current? My Thinkpad R40 works quite well, too. - ACPI is fine - wireless lan with ndis drivers (for Win XP) - sound ok - graphics ok (without glx or X won't start properly) - LAN is ok - I don't know how to make the internal MC'97 56k work :( Additional hint: options CPU_ENABLE_TCC should be enabled. I measured lower power consumption after compiling kernel with this option. Martin From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 22:54: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 13A6D16A4CE for ; Wed, 21 Jul 2004 22:54:51 +0000 (GMT) Received: from mail.corrupt.co.nz (222-152-17-24.jetstream.xtra.co.nz [222.152.17.24]) by mx1.FreeBSD.org (Postfix) with SMTP id BBF4743D46 for ; Wed, 21 Jul 2004 22:54:47 +0000 (GMT) (envelope-from drew@corrupt.co.nz) Received: (qmail 6329 invoked by uid 1011); 21 Jul 2004 22:54:55 -0000 Received: from drew@corrupt.co.nz by tweety.lan.corrupt.co.nz by uid 1009 with qmail-scanner-1.22 Clear:RC:0(192.100.53.164):SA:0(0.0/4.5):. Processed in 5.429839 secs); 21 Jul 2004 22:54:55 -0000 X-Spam-Status: No, hits=0.0 required=4.5 Received: from 192.100.53.164.dts.net.nz (HELO ?192.168.63.100?) (drew@corrupt.co.nz@192.100.53.164) by mail.corrupt.co.nz with SMTP; 21 Jul 2004 22:54:48 -0000 Message-ID: <40FEF429.4060408@corrupt.co.nz> Date: Thu, 22 Jul 2004 10:54:33 +1200 From: Drew Broadley User-Agent: Mozilla Thunderbird 0.7.1 (X11/20040714) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kim Culhan References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> In-Reply-To: <20040721203620.72466.qmail@web50707.mail.yahoo.com> X-Enigmail-Version: 0.84.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@FreeBSD.org cc: freebsd-mobile@freebsd.org Subject: Re: laptop for -current 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, 21 Jul 2004 22:54:51 -0000 Kim Culhan wrote: >Anyone know a laptop they think is good for FreeBSd-current? > > I have a Compaq Evo n800v. Pros: CPU Stepping works fine XFree86 works fine with the monitor 15": 1400x1050@75 and the aux s-video output. Cons: The CD-RW burns blanks though with 'cdrecord' and 'burncd'. XFree86 doesn't like coming back up when I close the lid and open it Suspend and Resume do not work. Any help is appreciated for the following cons - Drew From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 00:50: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 3119416A4CE for ; Thu, 22 Jul 2004 00:50:29 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id E96F443D49 for ; Thu, 22 Jul 2004 00:50:23 +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 i6M0oJiv066686; Thu, 22 Jul 2004 10:20:19 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Thu, 22 Jul 2004 10:20:18 +0930 User-Agent: KMail/1.6.2 References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> In-Reply-To: <20040721203620.72466.qmail@web50707.mail.yahoo.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200407221020.18967.doconnor@gsoft.com.au> X-Spam-Score: -4.9 () CARRIAGE_RETURNS,IN_REP_TO,PGP_SIGNATURE,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: Kim Culhan Subject: Re: laptop for -current 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, 22 Jul 2004 00:50:29 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 22 Jul 2004 06:06, Kim Culhan wrote: > Anyone know a laptop they think is good for FreeBSd-current? I have a Dell Inspiron 8600 which works very well. It has nVidia Fx5200 Go in it and I use the binary drivers (which means lib= c_r=20 for me) The modem doesn't work. The wireless is Intel Pro 2100 which works with=20 if_ndis. It doesn't suspend below S1 either. =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 =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/w9K5ZPcIHs/zowRAp5qAJ4qk8JR7XnH5mZ3bp6YpY4Rv90Z3ACfd8f0 Z5FnT4BxGKolLzqFqdua6CA=3D =3DG4j2 =2D----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 00:59: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 6D77C16A4CE; Thu, 22 Jul 2004 00:59:27 +0000 (GMT) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2607243D41; Thu, 22 Jul 2004 00:59:27 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp4.server.rpi.edu (8.13.0/8.13.0) with ESMTP id i6M0xPwD005931; Wed, 21 Jul 2004 20:59:26 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Wed, 21 Jul 2004 20:59:24 -0400 To: Robert Watson From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) cc: freebsd-current@freebsd.org Subject: Re: vmnet.ko missing - but it's there! - vmware and crashes 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, 22 Jul 2004 00:59:27 -0000 At 12:01 PM -0400 7/21/04, Robert Watson wrote: > >I've been wondering if we shouldn't bring the VMware modules into >the base source tree for some time -- the license is probably an >issue, but VMware is a valuable tool for development, and I'm >amazed at how frequently and accurately I shoot my feet due to >stale versions of the module ... It would be great to have more reliable support for VMware, as it can be a very helpful tool. I am also hopeful that the guys at http://www.serenityvirtual.com/ will eventually get to their virtual-machine product, which is supposed to run natively under FreeBSD. Right now they're still in the beta-version process, and they have not started to beta-test the product which will run with FreeBSD as the host OS. (perhaps they're waiting for 5.3-stable... :-). Right now my solution is to keep running VMware 2 on my freebsd 4.10-system. Neither of those are changing much, so that works well enough for my purposes. But if I had an option which would reliably work on a 5.x-system, that would be very helpful. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 02:20: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 E48F816A4CE for ; Thu, 22 Jul 2004 02:20:00 +0000 (GMT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D93D43D39 for ; Thu, 22 Jul 2004 02:20:00 +0000 (GMT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i6M2Jwjh005728; Wed, 21 Jul 2004 22:19:58 -0400 (EDT) Date: Wed, 21 Jul 2004 22:19:58 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Martin In-Reply-To: <1090449108.72182.31.camel@klotz.local> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Kim Culhan cc: FreeBSD Current Subject: Re: laptop for -current 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, 22 Jul 2004 02:20:01 -0000 On Thu, 22 Jul 2004, Martin wrote: > Am Mi, den 21.07.2004 schrieb Kim Culhan um 22:36: > > Anyone know a laptop they think is good for FreeBSd-current? > > My Thinkpad R40 works quite well, too. Not mine. My R40 doesn't work well due to bugs with ATA retry handling. I wouldn't recommend any IBM until this is fixed. -- Dan Eischen From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 02:58: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 1A0AA16A4CE for ; Thu, 22 Jul 2004 02:58:29 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id 692FB43D2F for ; Thu, 22 Jul 2004 02:58:28 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.161] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BnTmu-0000jy-00 for freebsd-current@freebsd.org; Thu, 22 Jul 2004 04:58:28 +0200 Received: from [217.83.14.1] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1BnTmt-0006Yo-00 for freebsd-current@freebsd.org; Thu, 22 Jul 2004 04:58:27 +0200 From: Max Laier To: freebsd-current@freebsd.org Date: Thu, 22 Jul 2004 04:56:12 +0200 User-Agent: KMail/1.6.2 References: <20040721213712.GL8753@mail.evip.pl> In-Reply-To: <20040721213712.GL8753@mail.evip.pl> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_Tzy/AjVuxcrYf/F"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407220456.19592.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 Subject: Re: LORs with 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: Thu, 22 Jul 2004 02:58:29 -0000 --Boundary-02=_Tzy/AjVuxcrYf/F Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 21 July 2004 23:37, Wiktor Niesiobedzki wrote: > Hi, > > I don't think, it was reported yet, but here it goes: > > lock order reversal > 1st 0xc0632c80 pf task mtx (pf task mtx) @ > /usr/src/sys/contrib/pf/net/pf.c:5822 2nd 0xc066638c tcp (tcp) @ > /usr/src/sys/contrib/pf/net/pf.c:2420 > KDB: stack backtrace: > kdb_backtrace(c05f529a,c066638c,c05f4e21,c05f4e21,c05e7e3f) at > kdb_backtrace+0x2e witness_checkorder(c066638c,9,c05e7e3f,974,104) at > witness_checkorder+0x672 _mtx_lock_flags(c066638c,0,c05e7e3f,974,c1893230) > at _mtx_lock_flags+0x80 > pf_socket_lookup(cb9659b4,cb9659b8,2,cb965a70,c14fad00) at > pf_socket_lookup+0xb4 pf_test_tcp(cb965a20,cb965a18,2,c14fad00,c1475100) = at > pf_test_tcp+0x529 pf_test(2,c10d8014,cb965b00,c15276a0,c0665ee0) at > pf_test+0x4a3 > pf_check_out(0,cb965b00,c10d8014,2,c1475100) at pf_check_out+0x5b > pfil_run_hooks(c0665ee0,cb965bc0,c10d8014,2,c04e8a70) at > pfil_run_hooks+0xca ip_output(c1475100,0,0,1,0) at ip_output+0x66d > ip_forward(c1475100,0,0,1,0) at ip_forward+0x37d > ip_input(c1475100,0,c05fad20,96,c0665598) at ip_input+0x65d > netisr_processqueue(c0665598,0,c05fad20,fe,c10d62c0) at > netisr_processqueue+0x8e swi_net(0,0,c05ef737,263,c063ae60) at swi_net+0x= a3 > ithread_loop(c10dd400,cb965d48,c05ef52e,328,c10dd400) at ithread_loop+0x1= 72 > fork_exit(c04ad4c0,c10dd400,cb965d48) at fork_exit+0xc2 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0x1, eip =3D 0, esp =3D 0xcb965d7c, ebp =3D 0 --- Ture, this was not reported earlier but is wellknown with ipfw. It exists a= s=20 checking UID/GID in an IP-level firewall is a layer violation. The original= =20 LO comes from the following path: proto_output: lock PCB -> ip_output(... pcb) -> pflil_hooks -> pf: lock = pf vs. the above ip_input -> pfil_hooks -> pf: lock pf -> check socket credentials: lock = PCB It is not possible to drop the pf lock for lookup as this happens during=20 ruleset evaluation (and no other thread should be allowed to modify the=20 rules). I know that people are looking for a solution for ipfw, I have no=20 idea at the moment and hence am very happy for any suggestion. =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 --Boundary-02=_Tzy/AjVuxcrYf/F Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA/yzTXyyEoT62BG0RAvLIAKCCEwZ3O/i4yoH+Ct18ZDyBuohACwCeMKaD PIaMFZ35+5qp/tWgrTq1vHA= =rqVF -----END PGP SIGNATURE----- --Boundary-02=_Tzy/AjVuxcrYf/F-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 03:01: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 401B016A4CE for ; Thu, 22 Jul 2004 03:01:41 +0000 (GMT) Received: from 1002-17.Lowesthosting.com (1002-17.lowesthosting.com [207.44.234.20]) by mx1.FreeBSD.org (Postfix) with SMTP id DE6A943D48 for ; Thu, 22 Jul 2004 03:01:40 +0000 (GMT) (envelope-from jhamby@anobject.com) Received: (qmail 22407 invoked from network); 22 Jul 2004 03:01:30 -0000 Received: from ar39.lsanca2-4.16.240.21.lsanca2.elnk.dsl.genuity.net (HELO ?192.168.0.13?) (4.16.240.21) by 1002-17.lowesthosting.com with SMTP; 22 Jul 2004 03:01:30 -0000 Message-ID: <40FF2E08.2040706@anobject.com> Date: Wed, 21 Jul 2004 20:01:28 -0700 From: Jake Hamby User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040719) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kim Culhan References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> In-Reply-To: <20040721203620.72466.qmail@web50707.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: laptop for -current 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, 22 Jul 2004 03:01:41 -0000 Kim Culhan wrote: > Anyone know a laptop they think is good for FreeBSd-current? I just bought a Fujitsu Lifebook N5010, not specifically to run FreeBSD, but as a desktop replacement for software development (I typically dual-boot between Windows and Linux or FreeBSD). The features unique to Fujitsu notebooks that I appreciated the most were: * exceptionally crisp and bright 16" display visible from all angles * one of the few brands to still include a built-in 3.5" floppy drive * exceptionally fast Radeon 9600 3-D chipset w/ 64MB. (1) * convenient, big rotary volume control knob with LED volume display. * very well-designed keyboard layout and keyboard feel * Built-in Atheros 802.11a/b/g (not yet supported by FreeBSD-current, but I have ported the latest version of the Linux driver). (2) (1) Unfortunately, the Radeon 9600 is not yet supported for 3-D acceleration by the free drivers in XFree86. It is supported by the proprietary ATI drivers for Linux which are not yet available for FreeBSD. (2) You can download it here: http://www.anobject.com/jehamby/atheros_driver.tar.bz2 Other than general instability of the current -current (random hard freezes during moderate to heavy system activity, which doesn't happen with the RELENG_5_2 kernel), the main features not currently supported by FreeBSD on this laptop are: * onboard 10/100 Ethernet not being detected (seems to be an issue with the PCI bus enumerator not seeing the card at all) * the laptop doesn't come back up after an ACPI suspend. If you can live without these two features until they get fixed, and are willing to lug around a 7 pound laptop w/ a 2-hour battery life, I think this is a stylish and high-quality machine for a reasonable price. -- Jake Hamby GoPix, Inc. From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 03:07: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 0C44016A4CE for ; Thu, 22 Jul 2004 03:07:15 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.196]) by mx1.FreeBSD.org (Postfix) with SMTP id B024F43D4C for ; Thu, 22 Jul 2004 03:07:14 +0000 (GMT) (envelope-from mronquillo@gmail.com) Received: by mproxy.gmail.com with SMTP id 55so36768rni for ; Wed, 21 Jul 2004 20:07:14 -0700 (PDT) Received: by 10.38.59.54 with SMTP id h54mr100321rna; Wed, 21 Jul 2004 20:07:14 -0700 (PDT) Message-ID: <874121bf0407212007988e9e2@mail.gmail.com> Date: Wed, 21 Jul 2004 20:07:14 -0700 From: Merill Ronquillo To: Drew Broadley In-Reply-To: <40FEF429.4060408@corrupt.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> <40FEF429.4060408@corrupt.co.nz> cc: Kim Culhan cc: freebsd-current@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: laptop for -current 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, 22 Jul 2004 03:07:15 -0000 On Thu, 22 Jul 2004 10:54:33 +1200, Drew Broadley wrote: > XFree86 doesn't like coming back up when I close the lid and open it > Suspend and Resume do not work. > > Any help is appreciated for the following cons > > - Drew When you open your lid, go to another tty (e.g. hit CTRL+F2). Close then open your lid so your screen comes back. Then hit CTRL+F9 to get back in X. From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 03:28: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 D40C816A4CE; Thu, 22 Jul 2004 03:28:18 +0000 (GMT) Received: from otter3.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 429D043D41; Thu, 22 Jul 2004 03:28:18 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.25] ([192.168.42.25]) by otter3.centtech.com (8.12.3/8.12.3) with ESMTP id i6M3S3E8089898; Wed, 21 Jul 2004 22:28:03 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <40FF3434.2050700@centtech.com> Date: Wed, 21 Jul 2004 22:27:48 -0500 From: Eric Anderson User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040720) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Merill Ronquillo References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> <40FEF429.4060408@corrupt.co.nz> <874121bf0407212007988e9e2@mail.gmail.com> In-Reply-To: <874121bf0407212007988e9e2@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Drew Broadley cc: Kim Culhan cc: freebsd-current@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: laptop for -current 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, 22 Jul 2004 03:28:19 -0000 Merill Ronquillo wrote: >On Thu, 22 Jul 2004 10:54:33 +1200, Drew Broadley wrote: > > >> XFree86 doesn't like coming back up when I close the lid and open it >> Suspend and Resume do not work. >> >>Any help is appreciated for the following cons >> >>- Drew >> >> > >When you open your lid, go to another tty (e.g. hit CTRL+F2). Close >then open your lid so your screen comes back. Then hit CTRL+F9 to get >back in X. > > I use the xfree86 snap version from ports (x11-servers/XFree86-4-Server-snap) and it works perfectly.. Eric -- ------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Talk sense to a fool and he calls you foolish. ------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 03:36: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 0021516A4CE for ; Thu, 22 Jul 2004 03:36:06 +0000 (GMT) Received: from kestrel.alerce.com (kestrel.alerce.com [209.182.219.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB80D43D49 for ; Thu, 22 Jul 2004 03:36:06 +0000 (GMT) (envelope-from hartzell@kestrel.alerce.com) Received: from rosebud.alerce.com (w092.z064001164.sjc-ca.dsl.cnc.net [64.1.164.92]) (authenticated bits=128) by kestrel.alerce.com (8.12.10/8.12.10) with ESMTP id i6M3a50F034132 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Jul 2004 20:36:06 -0700 (PDT) (envelope-from hartzell@kestrel.alerce.com) Received: from rosebud.alerce.com (localhost [127.0.0.1]) by rosebud.alerce.com (8.12.9p2/8.12.9) with ESMTP id i6M3aViW003600 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Jul 2004 20:36:31 -0700 (PDT) (envelope-from hartzell@rosebud.alerce.com) Received: (from hartzell@localhost) by rosebud.alerce.com (8.12.9p2/8.12.9/Submit) id i6M3aUEM003597; Wed, 21 Jul 2004 20:36:30 -0700 (PDT) (envelope-from hartzell) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16639.13886.117931.641180@rosebud.alerce.com> Date: Wed, 21 Jul 2004 20:36:30 -0700 To: Kim Culhan In-Reply-To: <20040721203620.72466.qmail@web50707.mail.yahoo.com> References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> X-Mailer: VM 7.14 under 21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid cc: freebsd-current@freebsd.org Subject: Re: laptop for -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: hartzell@kestrel.alerce.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jul 2004 03:36:07 -0000 Kim Culhan writes: > Anyone know a laptop they think is good for FreeBSd-current? I'd find it really useful if people would include a comment about whether the machines sucessfull suspend/sleep (S3, S3bios, S4, ...) and recover. Thanks! g. From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 03:37: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 BCC9316A4CF for ; Thu, 22 Jul 2004 03:37:53 +0000 (GMT) Received: from mail.corrupt.co.nz (222-152-9-101.jetstream.xtra.co.nz [222.152.9.101]) by mx1.FreeBSD.org (Postfix) with SMTP id 5870C43D45 for ; Thu, 22 Jul 2004 03:37:52 +0000 (GMT) (envelope-from drew@corrupt.co.nz) Received: (qmail 9705 invoked by uid 1011); 22 Jul 2004 03:37:58 -0000 Received: from drew@corrupt.co.nz by tweety.lan.corrupt.co.nz by uid 1009 with qmail-scanner-1.22 Clear:RC:0(192.100.53.164):SA:0(0.0/4.5):. Processed in 5.513464 secs); 22 Jul 2004 03:37:58 -0000 X-Spam-Status: No, hits=0.0 required=4.5 Received: from 192.100.53.164.dts.net.nz (HELO ?192.168.63.100?) (drew@corrupt.co.nz@192.100.53.164) by mail.corrupt.co.nz with SMTP; 22 Jul 2004 03:37:51 -0000 Message-ID: <40FF367E.9000203@corrupt.co.nz> Date: Thu, 22 Jul 2004 15:37:34 +1200 From: Drew Broadley User-Agent: Mozilla Thunderbird 0.7.1 (X11/20040714) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Merill Ronquillo References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> <40FEF429.4060408@corrupt.co.nz> <874121bf0407212007988e9e2@mail.gmail.com> In-Reply-To: <874121bf0407212007988e9e2@mail.gmail.com> X-Enigmail-Version: 0.84.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Kim Culhan cc: freebsd-current@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: laptop for -current 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, 22 Jul 2004 03:37:53 -0000 Merill Ronquillo wrote: >On Thu, 22 Jul 2004 10:54:33 +1200, Drew Broadley wrote: > > >> XFree86 doesn't like coming back up when I close the lid and open it >> Suspend and Resume do not work. >> >>Any help is appreciated for the following cons >> >>- Drew >> >> > >When you open your lid, go to another tty (e.g. hit CTRL+F2). Close >then open your lid so your screen comes back. Then hit CTRL+F9 to get >back in X. > > > Yes, I can get ti back after a few ctrl+alt+f1, ctrl+alt+f2 while holding the lid switch and releasing it. I just find it very very annoying. - Drew From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 05: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 6A4E016A4CE for ; Thu, 22 Jul 2004 05:47:03 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4A3D43D45 for ; Thu, 22 Jul 2004 05:47:00 +0000 (GMT) (envelope-from RoKlein@roklein.de) Received: from [212.227.126.161] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BnWQ0-0002Ce-00 for freebsd-current@freebsd.org; Thu, 22 Jul 2004 07:47:00 +0200 Received: from [80.129.45.11] (helo=localhost.invalid) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1BnWQ0-00087W-00 for freebsd-current@freebsd.org; Thu, 22 Jul 2004 07:47:00 +0200 From: Robert Klein Organization: roklein.de To: freebsd-current@freebsd.org Date: Thu, 22 Jul 2004 07:46:55 +0200 User-Agent: KMail/1.6.1 References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> In-Reply-To: <20040721203620.72466.qmail@web50707.mail.yahoo.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407220746.55870.RoKlein@roklein.de> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:ed18d71deac0f49a40655750752d3db9 Subject: Re: laptop for -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: RoKlein@roklein.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jul 2004 05:47:03 -0000 On Mittwoch, 21. Juli 2004 22:36, Kim Culhan wrote: > Anyone know a laptop they think is good for FreeBSd-current? I have an Acer Travelmate 291LCI which doesn't boot. Stable doesn't find the CD-ROM, all currents I tried had some kinda panic during boot.. :( Robert From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 06:02: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 587D216A4CE for ; Thu, 22 Jul 2004 06:02:04 +0000 (GMT) Received: from out012.verizon.net (out012pub.verizon.net [206.46.170.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB74043D3F for ; Thu, 22 Jul 2004 06:02:03 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] ([68.161.120.54]) by out012.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040722060203.MRDA2198.out012.verizon.net@[192.168.1.3]>; Thu, 22 Jul 2004 01:02:03 -0500 Message-ID: <40FF5851.5080207@mac.com> Date: Thu, 22 Jul 2004 02:01:53 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.1) Gecko/20040707 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Birrell References: <20040721081310.GJ22160@freebsd3.cimlogic.com.au> <20040721102620.GF1009@green.homeunix.org> <20040721220405.Y2346@epsplex.bde.org> <20040721215940.GK22160@freebsd3.cimlogic.com.au> In-Reply-To: <20040721215940.GK22160@freebsd3.cimlogic.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out012.verizon.net from [68.161.120.54] at Thu, 22 Jul 2004 01:02:03 -0500 cc: current@freebsd.org Subject: Re: nanosleep returning early 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, 22 Jul 2004 06:02:04 -0000 John Birrell wrote: [ ... ] > Bruce, have you seen this document: ? > I'm not looking for a critique here. The document talks about the sleep > overruns in various operatingg systems. There is a patch that was applied > to DragonFly which a[p]plies to the FreeBSD code base too. This was a good link, BTW, John: thanks for the pointer. I've created diffs of containing the first part of the changes for -CURRENT and -STABLE at: http://www.pkix.net/~chuck/timer/timer-STABLE.diff http://www.pkix.net/~chuck/timer/timer-CURRENT.diff On a 4.10 P3-grade machine using HZ=1000, I get the following graphs for 200 seconds worth of the "wakeup.c" program: http://www.pkix.net/~chuck/timer/wakeup001.gif ...so the changes reduce the latency seen from around 1.2ms to around 0.46ms. The aliasing problem is still clearly visible since I haven't had a chance to test the second set of changes. Matt's PLL code in i386/isa/clock.c has diverged a fair amount and the Dfly code apparently no longer works on 486-grade hardware due to using 8254 timing modes, if I understand what's going on correctly, but just the improvement above seems quite worthwhile. I'm going to retest using HZ=100, too, to see what's going on under default conditions. Please note that the wakeup interval after the patch can go very slightly negative (by 5-10 us): I'm not sure whether my hardware clock is off or a little flaky in the microsecond range, whether there is some issue with nanosleep() waking things up a little early, or whether the diffs need to be tweaked more. Testing on a few other machines would be good. :-) -- -Chuck From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 06:39: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 25A9416A4CE; Thu, 22 Jul 2004 06:39:22 +0000 (GMT) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 419E443D2F; Thu, 22 Jul 2004 06:39:21 +0000 (GMT) (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 i6M6d8Gl070709 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Jul 2004 10:39:09 +0400 (MSD) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id i6M6d3UN070708; Thu, 22 Jul 2004 10:39:03 +0400 (MSD) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Thu, 22 Jul 2004 10:39:03 +0400 From: Gleb Smirnoff To: Drew Broadley Message-ID: <20040722063903.GA70548@cell.sick.ru> References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> <40FEF429.4060408@corrupt.co.nz> <874121bf0407212007988e9e2@mail.gmail.com> <40FF367E.9000203@corrupt.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <40FF367E.9000203@corrupt.co.nz> User-Agent: Mutt/1.5.6i cc: Kim Culhan cc: Merill Ronquillo cc: freebsd-mobile@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: laptop for -current 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, 22 Jul 2004 06:39:22 -0000 On Thu, Jul 22, 2004 at 03:37:34PM +1200, Drew Broadley wrote: D> >When you open your lid, go to another tty (e.g. hit CTRL+F2). Close D> >then open your lid so your screen comes back. Then hit CTRL+F9 to get D> >back in X. D> > D> > D> > D> Yes, I can get ti back after a few ctrl+alt+f1, ctrl+alt+f2 while D> holding the lid switch and releasing it. D> D> I just find it very very annoying. Put hw.syscons.sc_no_suspend_vtswitch=1 in you /etc/sysctl.conf -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 06:41: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 0836216A4CE for ; Thu, 22 Jul 2004 06:41:15 +0000 (GMT) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C6F143D46 for ; Thu, 22 Jul 2004 06:41:14 +0000 (GMT) (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 i6M6fC1b070761 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Jul 2004 10:41:12 +0400 (MSD) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id i6M6fBTo070760; Thu, 22 Jul 2004 10:41:11 +0400 (MSD) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Thu, 22 Jul 2004 10:41:11 +0400 From: Gleb Smirnoff To: George Hartzell Message-ID: <20040722064111.GB70548@cell.sick.ru> References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> <16639.13886.117931.641180@rosebud.alerce.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <16639.13886.117931.641180@rosebud.alerce.com> User-Agent: Mutt/1.5.6i cc: Kim Culhan cc: freebsd-current@freebsd.org Subject: Re: laptop for -current 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, 22 Jul 2004 06:41:15 -0000 On Wed, Jul 21, 2004 at 08:36:30PM -0700, George Hartzell wrote: G> Kim Culhan writes: G> > Anyone know a laptop they think is good for FreeBSd-current? G> G> I'd find it really useful if people would include a comment about G> whether the machines sucessfull suspend/sleep (S3, S3bios, S4, ...) G> and recover. As I have already posted to CURRENT my IBM T20 was sleeping/resuming perfectly just 2 weeks ago. Now something is broekn in apm o related code. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 06:48: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 73BC516A4CE for ; Thu, 22 Jul 2004 06:48:58 +0000 (GMT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id E27CB43D48 for ; Thu, 22 Jul 2004 06:48:57 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 327E165410; Thu, 22 Jul 2004 07:48:56 +0100 (BST) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 49305-01; Thu, 22 Jul 2004 07:48:55 +0100 (BST) Received: from empiric.dek.spc.org (82-147-17-88.dsl.uk.rapidplay.com [82.147.17.88]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id 590DE6530A; Thu, 22 Jul 2004 07:48:55 +0100 (BST) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id A4EE46180; Thu, 22 Jul 2004 07:48:54 +0100 (BST) Date: Thu, 22 Jul 2004 07:48:54 +0100 From: Bruce M Simpson To: Daniel Eischen Message-ID: <20040722064854.GG775@empiric.dek.spc.org> Mail-Followup-To: Daniel Eischen , Martin , Kim Culhan , FreeBSD Current References: <1090449108.72182.31.camel@klotz.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: cc: Kim Culhan cc: FreeBSD Current cc: Martin Subject: Re: laptop for -current 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, 22 Jul 2004 06:48:58 -0000 On Wed, Jul 21, 2004 at 10:19:58PM -0400, Daniel Eischen wrote: > > My Thinkpad R40 works quite well, too. > > Not mine. My R40 doesn't work well due to bugs with ATA retry > handling. I wouldn't recommend any IBM until this is fixed. This is *definitely a show stopper for 5.3*. Just my 2 pence. BMS From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 07:03: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 5C47316A4CE for ; Thu, 22 Jul 2004 07:03:16 +0000 (GMT) Received: from n33.kp.t-systems-sfr.com (n33.kp.t-systems-sfr.com [129.247.16.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C61343D48 for ; Thu, 22 Jul 2004 07:03:15 +0000 (GMT) (envelope-from harti@freebsd.org) Received: from n81.sp.op.dlr.de (n81g.sp.op.dlr.de [129.247.163.1]) i6M72kX488378; Thu, 22 Jul 2004 09:02:47 +0200 Received: from zeus.nt.op.dlr.de (zeus.nt.op.dlr.de [129.247.173.3]) i6M72kf274538; Thu, 22 Jul 2004 09:02:46 +0200 Received: from beagle.kn.op.dlr.de (opkndnwsbsd178 [129.247.173.178]) by zeus.nt.op.dlr.de (8.11.7+Sun/8.9.1) with ESMTP id i6M72iV27276; Thu, 22 Jul 2004 09:02:44 +0200 (MET DST) Date: Thu, 22 Jul 2004 09:02:44 +0200 (CEST) From: Harti Brandt X-X-Sender: brandt@beagle.kn.op.dlr.de To: Daniel Lang In-Reply-To: <20040721203105.GA55687@atrbg11.informatik.tu-muenchen.de> Message-ID: <20040722085729.O9549@beagle.kn.op.dlr.de> References: <20040721151427.GC54664@atrbg11.informatik.tu-muenchen.de> <40F963D8.6010201@freebsd.org> <20040720081051.GB3001@cirb503493.alcatel.com.au> <20040721151427.GC54664@atrbg11.informatik.tu-muenchen.de> <20040721203105.GA55687@atrbg11.informatik.tu-muenchen.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org cc: Garrett Wollman Subject: Re: NEW TAR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Harti Brandt List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jul 2004 07:03:16 -0000 On Wed, 21 Jul 2004, Daniel Lang wrote: DL>To Harti: DL>I admit I don't know for sure, but to my understanding the handling DL>of the sparse file is done in the filesystem layer and not in the DL>application, right? Then all possible performance benefit on reading DL>a sparse file should be gained anyway. Regardless if the application DL>(the archiver) knows about the locations of the gaps or not.... I know of at least one application that does sparse file handling in the sense that it tries to create sparse file when the underlying FS supports it - that is my PDP11 emulator. I have even a special zcp utility that may re-sparse a file by copying it and looking for 0 blocks. It's not that p11 depends on the file system supporting sparse files - it just tries to use them if they are available. Again, for tar it's a matter of speed. Didn't Tim say that with the current sparse file info layout (gtar) he needs more than one pass over the file? harti From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 07:07: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 F156F16A4CE for ; Thu, 22 Jul 2004 07:07:12 +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 5EFEF43D45 for ; Thu, 22 Jul 2004 07:07:12 +0000 (GMT) (envelope-from le@FreeBSD.org) Received: from le.vpn.univie.ac.at (le.vpn.univie.ac.at [131.130.222.177]) by imap.univie.ac.at (8.12.10/8.12.10) with ESMTP id i6M76aEh1350330; Thu, 22 Jul 2004 09:06:43 +0200 Date: Thu, 22 Jul 2004 09:06:33 +0200 (CEST) From: Lukas Ertl To: George Hartzell In-Reply-To: <16639.13886.117931.641180@rosebud.alerce.com> Message-ID: <20040722090555.G632@korben.in.tern> References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> <16639.13886.117931.641180@rosebud.alerce.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-DCC-ZID-Univie-Metrics: mx7.univie.ac.at 4248; Body=3 Fuz1=3 Fuz2=3 cc: Kim Culhan cc: freebsd-current@FreeBSD.org Subject: Re: laptop for -current 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, 22 Jul 2004 07:07:13 -0000 On Wed, 21 Jul 2004, George Hartzell wrote: > Kim Culhan writes: > > Anyone know a laptop they think is good for FreeBSd-current? > > I'd find it really useful if people would include a comment about > whether the machines sucessfull suspend/sleep (S3, S3bios, S4, ...) > and recover. I'd also like to point to the FreeBSD Laptop Compatibility List . 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 Thu Jul 22 07:19: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 3A63616A4CE; Thu, 22 Jul 2004 07:19:38 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 689C243D48; Thu, 22 Jul 2004 07:19:37 +0000 (GMT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.11/8.12.11) with ESMTP id i6M7JTYo013665; Thu, 22 Jul 2004 11:19:29 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.11/8.12.11/Submit) id i6M7JTxi013664; Thu, 22 Jul 2004 11:19:29 +0400 (MSD) (envelope-from ache) Date: Thu, 22 Jul 2004 11:19:29 +0400 From: Andrey Chernov To: Tim Kientzle Message-ID: <20040722071929.GA13591@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Tim Kientzle , Tim Kientzle , current@FreeBSD.ORG, ports@FreeBSD.ORG References: <40F963D8.6010201@freebsd.org> <20040719060730.GA87697@nagual.pp.ru> <40FC9FC2.8050400@kientzle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40FC9FC2.8050400@kientzle.com> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter 1.1-beta; AVE 6.26.0.8; VDF 6.26.0.37 (host: pobrecita.freebsd.ru) cc: ports@FreeBSD.ORG cc: Tim Kientzle cc: current@FreeBSD.ORG Subject: Re: NEW TAR 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, 22 Jul 2004 07:19:38 -0000 On Mon, Jul 19, 2004 at 09:29:54PM -0700, Tim Kientzle wrote: > but they're not gtar-compatible. (The gtar > approach has a number of drawbacks. The primary > one being that on many systems it requires reading > the entire file twice, once to find holes and again > to actually archive the file. It is possible to > do both in one pass if you store the sparse file > data in a different fashion.) I can't imagine the case when 2 passes are needed. Even if you have normal file in the archive and specify -S only when extracting (it should work as expected), only 1 pass is needed. Just stop on first '\0' and count them until they finished, then do lseek (real case will be a bit harder to implement because of block boundaries). -- Andrey Chernov | http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 07:34: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 CA8C816A4CE for ; Thu, 22 Jul 2004 07:34:37 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4274843D5D for ; Thu, 22 Jul 2004 07:34:37 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny) by cs1.cs.huji.ac.il with esmtp id 1BnY66-000Pdm-RN; Thu, 22 Jul 2004 10:34:34 +0300 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Brooks Davis In-Reply-To: Message from Brooks Davis <20040721162706.GA12760@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Jul 2004 10:34:34 +0300 From: Danny Braniss Message-Id: <20040722073437.4274843D5D@mx1.FreeBSD.org> cc: Jan Grant cc: Peter Jeremy cc: current@freebsd.org cc: Daniel Lang cc: Stefan Bethke Subject: Re: NEW TAR 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, 22 Jul 2004 07:34:38 -0000 > > --lrZ03NoBR/3+SXJZ > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Wed, Jul 21, 2004 at 05:14:27PM +0200, Daniel Lang wrote: > > Hi, > >=20 > > Jan Grant wrote on Wed, Jul 21, 2004 at 02:44:42PM +0100: > > [..] > > > You're correct, in that filesystem semantics don't require an archiver= > =20 > > > to recreate holes. There are storage efficiency gains to be made in=20 > > > identifying holes, that's true - particularly in the case of absolutely= > =20 > > > whopping but extremely sparse files. In those cases, a simple=20 > > > userland-view-of-the-filesystem-semantics approach to ideentifying area= > s=20 > > > that _might_ be holes (just for archive efficiency) can still be=20 > > > expensive and might involve the scanning of multiple gigabytes of=20 > > > "virtual" zeroes. > > >=20 > > > Solaris offers an fcntl to identify holes (IIRC) for just this purpose.= > =20 > > > If the underlying filesystem can't be made to support it, there's an=20 > > > efficiency loss but otherwise it's no great shakes. > >=20 > > I don't get it. > >=20 > > I assume, that for any consumer it is totally transparent if > > possibly existing chunks of 0-bytes are actually blocks full of > > zeroes or just non-allocated blocks, correct? > >=20 > > Second, it is true, that there is a gain in terms of occupied disk > > space, if chunks of zeroes are not allocated at all, correct? > >=20 > > So, from my point of view it is totally irrelevant, if a sparse file > > is archived and then extracted, if the areas, which contain zeroes > > are exactly in the same manner consisting of unallocated blocks > > or not. > >=20 > > So, all I guess an archiver must do is: > >=20 > > - read the file=20 > > - scan the file for consecutive blocks of zeroes > > - archive these blocks in an efficient way > > - on extraction, create a sparse file with the previously > > identified empty blocks, regardless if these blocks > > have been 'sparse' blocks in the original file or not. > >=20 > > I do not see, why it is important if the original file was sparse > > at all or maybe in different places. > > Since sparse files over commit the disk, they should only be created > deliberatly. Otherwise you can easily get in trouble if you try to use > reserved space later since it won't actually be reserved. Consider the > case of a file system image created with "dd if=3D/dev/zero ...; newfw > =2E..". If your archiver decides to be "smart" and restore a copy of that > file sparce and then you use up the availble blocks on your disk you're > going to be in a world of hurt. I wouldn't be suprised it that resulted > in a panic. If the file has 'holes' and they are read as zero, then doesn't compressing the tar file nicely reduce it? dd if=/dev/zero of=junk count=100 tar czf junk.tar.gz junk ls -ls junk* 50 -rw-r--r-- 1 danny wheel 51200 Jul 22 10:28 junk 2 -rw-r--r-- 1 danny wheel 170 Jul 22 10:33 junk.tar.gz danny From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 07:51: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 0A6AE16A4CE for ; Thu, 22 Jul 2004 07:51:29 +0000 (GMT) Received: from files.jawa.at (jawa.at [213.229.17.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78BEC43D1F for ; Thu, 22 Jul 2004 07:51:28 +0000 (GMT) (envelope-from mranner@inode.at) Received: from localhost (localhost [127.0.0.1]) by files.jawa.at (Postfix) with ESMTP id 79660FDF2 for ; Thu, 22 Jul 2004 09:51:27 +0200 (CEST) Received: from files.jawa.at ([127.0.0.1]) by localhost (files.jawa.at [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15850-04 for ; Thu, 22 Jul 2004 09:51:25 +0200 (CEST) Received: by files.jawa.at (Postfix, from userid 60) id 86DC5FDE8; Thu, 22 Jul 2004 09:51:25 +0200 (CEST) Received: from walgrind.jawa.at (walgrind.jawa.at [192.168.200.56]) by files.jawa.at (Postfix) with ESMTP id 66576FDDE for ; Thu, 22 Jul 2004 09:51:15 +0200 (CEST) From: Michael Ranner To: freebsd-current@freebsd.org Date: Thu, 22 Jul 2004 09:51:13 +0200 User-Agent: KMail/1.6.1 References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> In-Reply-To: <20040721203620.72466.qmail@web50707.mail.yahoo.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407220951.13659.mranner@inode.at> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on files.jawa.at X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Level: X-Virus-Scanned: by amavisd-new at jawa.at Subject: Re: laptop for -current 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, 22 Jul 2004 07:51:29 -0000 Am Mittwoch, 21. Juli 2004 22:36 schrieb Kim Culhan: > Anyone know a laptop they think is good for FreeBSd-current? > > With all the differences in hardware, trying to find > one which is mostly compatible is not straightforward. > > The manufacturers don't make it easier.. Hi, running 5.2.1 nicely on HP compaq nx9005. This laptop has onboard LAN, firewire, DVD ROM/CD-Writer, USB 2.0 but also old style serial, parallel and floppy drive. Soundcard works fine, gfx card needs X Server better than XFree86 4.3, I am running 4.3.99. Only the built in wavelan card is not supported, but have not yet tried to use ndisulator (Project Evil). You might use the PowerNow kernel modul from http://poupinou.org/cpufreq/bsd/ because runnung the cpu on highes speed is not preferable (temp, noise, battery life time), but see this bice howto for FreeBSD on this Laptop: http://demira.shopkeeper.de/~sascha/nx9005/ -- /\/\ichael Ranner mranner@inode.at - mranner@jawa.at - mranner@bugat.at ----------------------------------------------------- BSD Usergroup Austria - http://www.bugat.at/ -----BEGIN GEEK CODE BLOCK----- GIT/CS/AT dx(-) s+:(++:) a- C++ UBLVS++++$ P++>+++$ L-(+)$ E--- W+++$ N+(++) o-- K- w--()$ O-(--) M@ V-(--) PS+>++ PE(-) Y+ PGP(-) t+ 5+ X+++(++++) R* tv++ b+(++) DI++ D-(--) G- e h--(*) r++ y? ------END GEEK CODE BLOCK------ From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 07: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 C1B8816A4CE for ; Thu, 22 Jul 2004 07:53:19 +0000 (GMT) Received: from www.cyclades.de (mail.cyclades.de [62.225.173.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 395C843D39 for ; Thu, 22 Jul 2004 07:53:19 +0000 (GMT) (envelope-from mh@kernel32.de) Received: from [192.168.10.114] (helo=kernel32.de) by www.cyclades.de with asmtp (Exim 3.35 #1 (Debian)) id 1BnYOB-0000Va-00 for ; Thu, 22 Jul 2004 09:53:15 +0200 Message-ID: <40FF724C.5080308@kernel32.de> Date: Thu, 22 Jul 2004 09:52:44 +0200 From: Marian Hettwer User-Agent: Mozilla Thunderbird 0.5 (X11/20040414) 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 X-MailScanner: Found to be clean X-MailScanner-SpamCheck: Subject: Intel Pro/Wireless 2011B & FreeBSD 5.2.1 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, 22 Jul 2004 07:53:19 -0000 Hi All, I searched the the pr database and figured out, that support for Intel's 2011B is in progress and that wi(4) actually doesn't support it. I was just wondering wether there's any progress, because the pr entry is from May 2002 ... I would have a 2011B which I could borrow for development purpose. Unluckily it'll probably be only borrowing, not donating. If I could help testing patches for wi(4) to get support for the 2011B just drop me a line :) thanks and best regards, Marian From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 07:59: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 0541C16A4E7 for ; Thu, 22 Jul 2004 07:59:11 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C28EC43D46 for ; Thu, 22 Jul 2004 07:59:09 +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 i6M7x1MR080064; Thu, 22 Jul 2004 17:29:02 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Thu, 22 Jul 2004 17:29:01 +0930 User-Agent: KMail/1.6.2 References: <40FF724C.5080308@kernel32.de> In-Reply-To: <40FF724C.5080308@kernel32.de> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200407221729.01137.doconnor@gsoft.com.au> X-Spam-Score: -4.9 () CARRIAGE_RETURNS,IN_REP_TO,PGP_SIGNATURE,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: Marian Hettwer Subject: Re: Intel Pro/Wireless 2011B & FreeBSD 5.2.1 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, 22 Jul 2004 07:59:11 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 22 Jul 2004 17:22, Marian Hettwer wrote: > I searched the the pr database and figured out, that support for Intel's > 2011B is in progress and that wi(4) actually doesn't support it. > I was just wondering wether there's any progress, because the pr entry > is from May 2002 ... > > I would have a 2011B which I could borrow for development purpose. > Unluckily it'll probably be only borrowing, not donating. > > If I could help testing patches for wi(4) to get support for the 2011B > just drop me a line :) I doubt wi will ever support it. You could try if_ndis.. (If you are running 5.2-CURRENT) =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 =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/3PF5ZPcIHs/zowRAu+JAJ0RuCIK33M/PX+7Oeb+1T7Kw5rXcQCfdHN8 LDSBPyPMiHhajiGRy6o3+Zo=3D =3D8nnr =2D----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 08:00: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 127E016A4D0 for ; Thu, 22 Jul 2004 08:00:11 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DEB543D48 for ; Thu, 22 Jul 2004 08:00:10 +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 BB5531FFDD6; Thu, 22 Jul 2004 10:00:08 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id E13431FFDD4; Thu, 22 Jul 2004 10:00:06 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 6282D15391; Thu, 22 Jul 2004 07:59:07 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 578DA15380; Thu, 22 Jul 2004 07:59:08 +0000 (UTC) Date: Thu, 22 Jul 2004 07:59:08 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Wiktor Niesiobedzki In-Reply-To: <20040721213712.GL8753@mail.evip.pl> Message-ID: References: <20040721213712.GL8753@mail.evip.pl> 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 mailing list Subject: Re: LORs with 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: Thu, 22 Jul 2004 08:00:11 -0000 On Wed, 21 Jul 2004, Wiktor Niesiobedzki wrote: Hi, > I don't think, it was reported yet, but here it goes: > > lock order reversal > 1st 0xc0632c80 pf task mtx (pf task mtx) @ /usr/src/sys/contrib/pf/net/pf.c:5822 > 2nd 0xc066638c tcp (tcp) @ /usr/src/sys/contrib/pf/net/pf.c:2420 for reference: added it to "LOR page" with LOR # 017: http://sources.zabbadoz.net/freebsd/lor.html#017 -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 08:39: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 F1C9B16A4CE; Thu, 22 Jul 2004 08:39:01 +0000 (GMT) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id C550143D46; Thu, 22 Jul 2004 08:39:00 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from ns0.nlsystems.com (ns0.nlsystems.com [80.177.232.243]) by itchy.rabson.org (8.12.11/8.12.11) with ESMTP id i6M8cj1G087146; Thu, 22 Jul 2004 09:38:46 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: Hidetoshi Shimokawa Date: Thu, 22 Jul 2004 09:38:40 +0100 User-Agent: KMail/1.6.1 References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <1090421941.7114.26.camel@builder02.qubesoft.com> <87u0w1ni2i.wl@tora.nunu.org> In-Reply-To: <87u0w1ni2i.wl@tora.nunu.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407220938.40393.dfr@nlsystems.com> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on itchy.rabson.org X-Virus-Scanned: clamd / ClamAV version 0.71, clamav-milter version 0.71 X-Virus-Status: Clean cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org cc: Andrew Gallatin Subject: Re: Excellent job on the firewire 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: Thu, 22 Jul 2004 08:39:02 -0000 On Wednesday 21 July 2004 22:53, Hidetoshi Shimokawa wrote: > At Wed, 21 Jul 2004 15:59:01 +0100, > > Doug Rabson wrote: > > > If no, assuming I had a Windows or Linux box on the firewire bus, > > > would it be possible to access physical memory from a different > > > OS? > > > > Windows XP has some kind of firewire debug driver that you might > > have to load (I haven't read the docs on that). I don't think the > > linux driver enables physical access by default but it would be > > easy to hack it in (just write all ones to the right fwohci > > register). > > The physical access is usually used for SBP-2 initiator mode. > Without physical access, the performance of SBP-2 should be > poorer and we see more load on CPU. > > The physical access can be restricted by two way. You can > restrict it per node-id and by physical memory range(upper bound). My vague plan was for the SBP driver to enable physical access from the SBP node. This could be done on a transaction basis so that we enable it before posting a transaction and disabled it when all current transactions have completed. > > As far as I have tried, WindowsXP seems not to allow physical access > of usual nodes. But I think you can easily cheat it by a node with > sbp target mode(use sbp_targ(4) ;-). If you can avoid enabling access for drives that you are not actually using, this might not be that bad. Defaulting to auto-login means that an attacker would have plenty of opportunity though. > > In my opinion, it's hard to ensure security with current OHCI > specification. In practice, any attacker is likely to be only a few meters away so the best defense is probably to just reach over and hit them :-) From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 08:46:49 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 1943716A4CE for ; Thu, 22 Jul 2004 08:46:49 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id C475E43D39 for ; Thu, 22 Jul 2004 08:46:47 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6M8kjAm020067; Thu, 22 Jul 2004 10:46:45 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <01ea01c46fc8$6d1f32c0$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Doug White" References: <021001c46e97$84c05210$471b3dd4@digiware.nl> <20040721114745.X81889@carver.gumbysoft.com> Date: Thu, 22 Jul 2004 10:46:48 +0200 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 cc: current@FreeBSD.ORG Subject: Re: Erros in: make -j 16 buildword 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, 22 Jul 2004 08:46:49 -0000 From: "Doug White" > On Tue, 20 Jul 2004, Willem Jan Withagen wrote: > > > Hi, > > > > One way or another it seems that I can no longer buildworld with -j16. > > -j8 works perfectly, but -j16 fails consistently at: > [...] > > > > Unless anybody has suggestions of which programs generate these tearse > > messages??? > > Or a way to get make to be more informative??? > > You need to capture the entire output since the error is buried in there. > Make doesn't abort -j builds until all the subprocesses are finished, and > they can run for a long time... You know how long the output of a buildworld is, right?? When the errors are reported, visually it is at the point where it normally looks like it is done. Building ports gives you notice of the directory in which it started to come up from thus telling you which package was in error..... Maybe I'll see if I can put something like this in make of the makefiles.... Thanx --WjW From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 08:48: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 119D916A4CE for ; Thu, 22 Jul 2004 08:48:33 +0000 (GMT) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73B7843D1F for ; Thu, 22 Jul 2004 08:48:32 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from ns0.nlsystems.com (ns0.nlsystems.com [80.177.232.243]) by itchy.rabson.org (8.12.11/8.12.11) with ESMTP id i6M8mS3b087227; Thu, 22 Jul 2004 09:48:28 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-current@freebsd.org Date: Thu, 22 Jul 2004 09:48:23 +0100 User-Agent: KMail/1.6.1 References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> In-Reply-To: <20040721203620.72466.qmail@web50707.mail.yahoo.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407220948.23115.dfr@nlsystems.com> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on itchy.rabson.org X-Virus-Scanned: clamd / ClamAV version 0.71, clamav-milter version 0.71 X-Virus-Status: Clean cc: Kim Culhan Subject: Re: laptop for -current 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, 22 Jul 2004 08:48:33 -0000 On Wednesday 21 July 2004 21:36, Kim Culhan wrote: > Anyone know a laptop they think is good for FreeBSd-current? > > With all the differences in hardware, trying to find > one which is mostly compatible is not straightforward. > > The manufacturers don't make it easier.. I have no idea whether or not it works well with FreeBSD-current but I *really* want a Sony VAIO x505. If someone felt like buying me one, I would fix FreeBSD-current so that it worked :-) From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 09:02:09 2004 Return-Path: Delivered-To: freebsd-current@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2623216A4CE for ; Thu, 22 Jul 2004 09:02:09 +0000 (GMT) Received: from dbmail-mx8.orcon.net.nz (loadbalancer1.orcon.net.nz [219.88.242.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1886743D2D for ; Thu, 22 Jul 2004 09:02:08 +0000 (GMT) (envelope-from pmurray@nevada.net.nz) Received: from [10.58.2.16] (port-222-152-49-103.fastadsl.net.nz [222.152.49.103])i6M91kUF003739 for ; Thu, 22 Jul 2004 21:01:52 +1200 Message-ID: <40FF8283.1030102@nevada.net.nz> Date: Thu, 22 Jul 2004 21:01:55 +1200 From: Philip Murray User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@www.freebsd.org Content-Type: multipart/mixed; boundary="------------080305080505020800050204" X-Virus-Scanned: clamd / ClamAV version 0.72, clamav-milter version 0.72 on dbmail-mx8.orcon.net.nz X-Virus-Status: Clean X-Spam-Status: -4.9, tests=BAYES_00 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on dbmail-mx8.orcon.net.nz Subject: 3Ware 9500 and disklabel 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, 22 Jul 2004 09:02:09 -0000 This is a multi-part message in MIME format. --------------080305080505020800050204 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, I'm trying to test out -CURRENT (22/7/2004) on a dual Opteron (Tyan board) with a 3Ware 9500-8 raid controller and I'm having problems with disklabel. At the moment I have a RAID0 array totalling 600GB. I fdisk'd them to create a single partition using the entire volume, fdisk (from sysinstall) complained about the geometry, I wasn't sure what the correct geometry was, so I forged ahead anyway. Then I went to try and disklabel it. It seemed to work from sysinstall until I went to write the changes out and it complained "ERROR: Unable to write data to disk da0!'. So I tried disklabel on the command line, as so disklabel -e /dev/da0s1 Where it promptly hangs (won't respond to ^C), ps lists it as root 641 0.0 0.0 5600 940 p1 DL+ 8:48PM 0:00.01 disklabel -e /dev/da0s1 Is this something stupid I've done (geometry?) or a bug with the twa driver? I've attached my dmesg FWIW, any other information I can provide on request. Philip --------------080305080505020800050204 Content-Type: text/plain; name="dmesg" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="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.2-CURRENT #2: Thu Jul 22 19:10:14 NZST 2004 root@wildfire.office.open2view.com:/usr/obj/usr/src/sys/WILDFIRE WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 244 (1791.80-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 Features=0x78bfbff AMD Features=0xe0500800 real memory = 2147418112 (2047 MB) avail memory = 2061725696 (1966 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: [GIANT-LOCKED] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 6.0 on pci0 pci3: on pcib1 ohci0: mem 0xfeafc000-0xfeafcfff irq 19 at device 0.0 on pci3 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support 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 0xfeafd000-0xfeafdfff irq 19 at device 0.1 on pci3 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support 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 atapci0: port 0xa800-0xa80f,0xac00-0xac03,0xb000-0xb007,0xb400-0xb403,0xbc00-0xbc07 mem 0xfeafec00-0xfeafefff irq 19 at device 5.0 on pci3 ata2: at 0xfeafec00 on atapci0 ata3: at 0xfeafec00 on atapci0 ata4: at 0xfeafec00 on atapci0 ata5: at 0xfeafec00 on atapci0 pci3: at device 6.0 (no driver attached) fxp0: port 0xa400-0xa43f mem 0xfeaa0000-0xfeabffff,0xfeafb000-0xfeafbfff irq 18 at device 8.0 on pci3 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:e0:81:29:b6:cf fxp0: [GIANT-LOCKED] isab0: at device 7.0 on pci0 isa0: on isab0 atapci1: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 amdpm0: port 0xe0-0xff,0xcc00-0xcc1f irq 19 at device 7.2 on pci0 amdpm0: could not map i/o space device_attach: amdpm0 attach returned 6 pci0: at device 7.3 (no driver attached) pcib2: at device 10.0 on pci0 pci2: on pcib2 bge0: mem 0xfc8b0000-0xfc8bffff,0xfc8c0000-0xfc8cffff irq 24 at device 9.0 on pci2 miibus1: on bge0 brgphy0: on miibus1 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:e0:81:29:f0:14 bge0: [GIANT-LOCKED] bge1: mem 0xfc8e0000-0xfc8effff,0xfc8f0000-0xfc8fffff irq 25 at device 9.1 on pci2 miibus2: on bge1 brgphy1: on miibus2 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:e0:81:29:f0:15 bge1: [GIANT-LOCKED] pci0: at device 10.1 (no driver attached) pcib3: at device 11.0 on pci0 pci1: on pcib3 3ware device driver for 9000 series storage controllers, version: 2.50.00.000 twa0: <3ware 9000 series Storage Controller> port 0x9800-0x98ff mem 0xfb800000-0xfbffffff,0xfc7ffc00-0xfc7ffcff irq 28 at device 3.0 on pci1 twa0: [GIANT-LOCKED] twa0: 8 ports, Firmware FE9X 2.02.00.011, BIOS BE9X 2.02.01.037 pci0: at device 11.1 (no driver attached) acpi_button0: on acpi0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A, console sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 orm0: at iomem 0xcc800-0xcdfff,0xc8000-0xcc7ff,0xc0000-0xc7fff on isa0 atkbdc0: at port 0x64,0x60 on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 0.976 msec acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% ad4: 157066MB [319120/16/63] at ata2-master SATA150 da0 at twa0 bus 0 target 0 lun 0 da0: <3ware Logical Disk 00 1.00> Fixed Direct Access SCSI-0 device da0: 100.000MB/s transfers da0: 610308MB (1249910784 512 byte sectors: 255H 63S/T 77803C) da1 at twa0 bus 0 target 1 lun 0 da1: <3ware Logical Disk 01 1.00> Fixed Direct Access SCSI-0 device da1: 100.000MB/s transfers da1: 610308MB (1249910784 512 byte sectors: 255H 63S/T 77803C) SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ad4s1a --------------080305080505020800050204-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 09:08: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 74CF016A4CE; Thu, 22 Jul 2004 09:08:12 +0000 (GMT) Received: from mail013.syd.optusnet.com.au (mail013.syd.optusnet.com.au [211.29.132.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2022A43D3F; Thu, 22 Jul 2004 09:08:11 +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]) i6M988F18369; Thu, 22 Jul 2004 19:08:09 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])i6M987Vd009392; Thu, 22 Jul 2004 19:08:07 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)i6M986Lj009391; Thu, 22 Jul 2004 19:08:06 +1000 (EST) (envelope-from pjeremy) Date: Thu, 22 Jul 2004 19:08:06 +1000 From: Peter Jeremy To: Robert Watson Message-ID: <20040722090806.GF3001@cirb503493.alcatel.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i cc: current@freebsd.org Subject: Re: Anyone else noticed: bgfsck doesn't bgfsck non-root 'a' partitions? 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, 22 Jul 2004 09:08:12 -0000 On Tue, 2004-Jul-20 15:55:17 -0400, Robert Watson wrote: >fsck has logic to force a full preening fsck of '/', permitting background >file system fsck only for non-root file systems. ... >on /var and /usr, but not /local0. So it sounds like the logic in fsck is >simply guessing that any 'a' partition needs a foreground fsck. I can't quickly find that logic anywhere. The logic I can find is: * "ro" and "noauto" filesystems aren't eligible for background fsck (fsck.c:isok()) * Previous background fsck failed or filesystem doesn't have soft-updates enabled or kernel doesn't have soft-updates support or filesystem already clean forces a foreground fsck ("fsck_ufs -F" from fsck.c:checkfs()). Are you sure /local0 doesn't fall into one of the above categories? The following (untested) patch disables background checking for pass 1 filesystems when fsck is running in "scan fstab" mode. According to fstab(5), only the root filesystem should be in pass 1. Index: fsck.c =================================================================== RCS file: /usr/ncvs/src/sbin/fsck/fsck.c,v retrieving revision 1.17 diff -u -r1.17 fsck.c --- fsck.c 29 Oct 2003 16:09:17 -0000 1.17 +++ fsck.c 22 Jul 2004 08:46:33 -0000 @@ -244,6 +244,8 @@ * by invoking its check program with the -F flag. */ if (flags & DO_BACKGRD) { + if (fs->fs_passno == 1) + return (0); if (!strcmp(fs->fs_type, FSTAB_RO)) return (0); if (getmntpt(fs->fs_spec) == NULL) @@ -261,7 +263,8 @@ * itself to see if it is willing to defer to background * checking by invoking its check program with the -F flag. */ - if ((flags & CHECK_BACKGRD) == 0 || !strcmp(fs->fs_type, FSTAB_RO)) + if ((flags & CHECK_BACKGRD) == 0 || !strcmp(fs->fs_type, FSTAB_RO) || + fs->fs_passno == 1) return (1); for (i = strlen(fs->fs_mntops) - 6; i >= 0; i--) if (!strncmp(&fs->fs_mntops[i], "noauto", 6)) -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 09: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 C8DE616A4CE; Thu, 22 Jul 2004 09:16:35 +0000 (GMT) Received: from mail009.syd.optusnet.com.au (mail009.syd.optusnet.com.au [211.29.132.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E2AB43D46; Thu, 22 Jul 2004 09:16:34 +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]) i6M9GNf23561; Thu, 22 Jul 2004 19:16:23 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])i6M9GMVd009415; Thu, 22 Jul 2004 19:16:22 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)i6M9GMDR009414; Thu, 22 Jul 2004 19:16:22 +1000 (EST) (envelope-from pjeremy) Date: Thu, 22 Jul 2004 19:16:22 +1000 From: Peter Jeremy To: Andrey Chernov , current@FreeBSD.ORG, ports@FreeBSD.ORG Message-ID: <20040722091622.GG3001@cirb503493.alcatel.com.au> References: <40F963D8.6010201@freebsd.org> <20040719060730.GA87697@nagual.pp.ru> <40FC9FC2.8050400@kientzle.com> <20040722071929.GA13591@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040722071929.GA13591@nagual.pp.ru> User-Agent: Mutt/1.4.2i Subject: Re: NEW TAR 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, 22 Jul 2004 09:16:35 -0000 On Thu, 2004-Jul-22 11:19:29 +0400, Andrey Chernov wrote: >On Mon, Jul 19, 2004 at 09:29:54PM -0700, Tim Kientzle wrote: >> but they're not gtar-compatible. (The gtar >> approach has a number of drawbacks. The primary >> one being that on many systems it requires reading >> the entire file twice, once to find holes and again >> to actually archive the file. It is possible to >> do both in one pass if you store the sparse file >> data in a different fashion.) > >I can't imagine the case when 2 passes are needed. Even if you have normal >file in the archive and specify -S only when extracting (it should work as >expected), only 1 pass is needed. Just stop on first '\0' and count them >until they finished, then do lseek (real case will be a bit harder to >implement because of block boundaries). I thought gnutar implemented sparse files by writing a bitmap of used blocks vs holes followed by the actual data. This needs 1 pass to calculate the bitmap and a second pass to write the data. You probably don't want to unnecessarily convert holes to data in your archive. Some Un*x systems generate a core dump by writing the process memory map to a file - holes and all - giving you a sparse file that appears to be several GB in size. Older dbm variants also tended to leave large holes in the .pag file from memory. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 09:20: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 0DEEA16A4CE for ; Thu, 22 Jul 2004 09:20:46 +0000 (GMT) Received: from ioskeha.hittite.isp.9tel.net (ioskeha.hittite.isp.9tel.net [62.62.156.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E0F043D39 for ; Thu, 22 Jul 2004 09:20:45 +0000 (GMT) (envelope-from martin.mato@wanadoo.fr) Received: from [192.168.0.2] (unknown [84.98.0.161]) by ioskeha.hittite.isp.9tel.net (Postfix) with ESMTP id 1E56514B5BD for ; Thu, 22 Jul 2004 11:26:21 +0200 (CEST) Message-ID: <40FF86E8.2090306@wanadoo.fr> Date: Thu, 22 Jul 2004 11:20:40 +0200 From: Martin MATO User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707) X-Accept-Language: fr, en MIME-Version: 1.0 To: current@FreeBSD.ORG Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Buildworld Failure at libntp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: martin.mato@wanadoo.fr List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jul 2004 09:20:46 -0000 since three or four days i get this message systematically at compiling: the buildworld worked perfectly before, and i perform an update of the source tree by before compiling Any clues? ===> usr.sbin/ntp/libntp rm -f .depend mkdep -f .depend -a -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/include -I/usr/src/usr.sbin/ntp/libntp/../ -DSYS_FREEBSD -DPARSE -DHAVE_CONFIG_H /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/a_md5encrypt.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/adjtime.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/atoint.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/atolfp.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/atouint.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/audio.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/authkeys.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/authreadkeys.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/authusekey.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/binio.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/buftvtots.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/caljulian.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/calleapwhen.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/caltontp.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/calyearstart.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/clocktime.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/clocktypes.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/decodenetnum.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/dofptoa.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/dolfptoa.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/emalloc.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/findconfig.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/fptoa.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/fptoms.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/getopt.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/gpstolfp.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/hextoint.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/hextolfp.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/humandate.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/icom.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/ieee754io.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/inttoa.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/iosignal.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/lib_strbuf.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/machines.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/md5c.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/memmove.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/mfp_mul.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/mfptoa.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/mfptoms.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/modetoa.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/mstolfp.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/msutotsf.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/msyslog.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/netof.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/ntp_rfc2553.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/numtoa.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/numtohost.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/octtoint.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/prettydate.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/ranny.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/recvbuff.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/refnumtoa.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/socktoa.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/socktohost.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/strstr.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/systime_s.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/statestr.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/syssignal.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/systime.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/tsftomsu.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/tstotv.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/tvtoa.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/tvtots.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/uglydate.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/uinttoa.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/utvtoa.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/ymd2yd.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libisc/assertions.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libisc/error.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libisc/inet_ntop.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libisc/interfaceiter.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libisc/isc_strerror.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libisc/lib.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libisc/mem.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libisc/msgcat.c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libisc/net.c In file included from /usr/src/contrib/ntp/include/ntp.h:10, from /usr/src/contrib/ntp/libntp/authkeys.c:13: /usr/src/contrib/ntp/include/ntp_crypto.h:5:25: openssl/evp.h: No such file or directory In file included from /usr/src/contrib/ntp/include/ntp.h:10, from /usr/src/contrib/ntp/libntp/authreadkeys.c:8: /usr/src/contrib/ntp/include/ntp_crypto.h:5:25: openssl/evp.h: No such file or directory In file included from /usr/src/contrib/ntp/include/ntp.h:10, from /usr/src/contrib/ntp/libntp/clocktypes.c:7: /usr/src/contrib/ntp/include/ntp_crypto.h:5:25: openssl/evp.h: No such file or directory In file included from /usr/src/contrib/ntp/include/ntp.h:10, from /usr/src/contrib/ntp/include/ntpd.h:7, from /usr/src/contrib/ntp/libntp/iosignal.c:7: /usr/src/contrib/ntp/include/ntp_crypto.h:5:25: openssl/evp.h: No such file or directory In file included from /usr/src/contrib/ntp/include/ntp.h:10, from /usr/src/contrib/ntp/libntp/netof.c:9: /usr/src/contrib/ntp/include/ntp_crypto.h:5:25: openssl/evp.h: No such file or directory In file included from /usr/src/contrib/ntp/include/ntp.h:10, from /usr/src/contrib/ntp/include/ntpd.h:7, from /usr/src/contrib/ntp/libntp/ntp_rfc2553.c:81: /usr/src/contrib/ntp/include/ntp_crypto.h:5:25: openssl/evp.h: No such file or directory In file included from /usr/src/contrib/ntp/include/ntp.h:10, from /usr/src/contrib/ntp/include/recvbuff.h:8, from /usr/src/contrib/ntp/libntp/recvbuff.c:11: /usr/src/contrib/ntp/include/ntp_crypto.h:5:25: openssl/evp.h: No such file or directory In file included from /usr/src/contrib/ntp/include/ntp.h:10, from /usr/src/contrib/ntp/libntp/socktoa.c:23: /usr/src/contrib/ntp/include/ntp_crypto.h:5:25: openssl/evp.h: No such file or directory In file included from /usr/src/contrib/ntp/include/ntp.h:10, from /usr/src/contrib/ntp/libntp/socktohost.c:16: /usr/src/contrib/ntp/include/ntp_crypto.h:5:25: openssl/evp.h: No such file or directory In file included from /usr/src/contrib/ntp/include/ntp.h:10, from /usr/src/contrib/ntp/include/ntpsim.h:14, from /usr/src/contrib/ntp/include/ntp_unixtime.h:9, from /usr/src/contrib/ntp/libntp/systime.c:10, from /usr/src/contrib/ntp/libntp/systime_s.c:2: /usr/src/contrib/ntp/include/ntp_crypto.h:5:25: openssl/evp.h: No such file or directory In file included from /usr/src/contrib/ntp/include/ntp.h:10, from /usr/src/contrib/ntp/libntp/statestr.c:10: /usr/src/contrib/ntp/include/ntp_crypto.h:5:25: openssl/evp.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/usr.sbin/ntp/libntp. *** Error code 1 Stop in /usr/src/usr.sbin/ntp. *** Error code 1 Stop in /usr/src/usr.sbin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 09:23: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 4B86E16A4CE for ; Thu, 22 Jul 2004 09:23:03 +0000 (GMT) Received: from www.cyclades.de (mail.cyclades.de [62.225.173.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA54D43D41 for ; Thu, 22 Jul 2004 09:23:02 +0000 (GMT) (envelope-from mh@kernel32.de) Received: from [192.168.10.114] (helo=kernel32.de) by www.cyclades.de with asmtp (Exim 3.35 #1 (Debian)) id 1BnYvE-0000zY-00; Thu, 22 Jul 2004 10:27:24 +0200 Message-ID: <40FF7A4B.1040506@kernel32.de> Date: Thu, 22 Jul 2004 10:26:51 +0200 From: Marian Hettwer User-Agent: Mozilla Thunderbird 0.5 (X11/20040414) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel O'Connor References: <40FF724C.5080308@kernel32.de> <200407221729.01137.doconnor@gsoft.com.au> In-Reply-To: <200407221729.01137.doconnor@gsoft.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner: Found to be clean X-MailScanner-SpamCheck: cc: freebsd-current@freebsd.org Subject: Re: Intel Pro/Wireless 2011B & FreeBSD 5.2.1 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, 22 Jul 2004 09:23:03 -0000 Hi Daniel, Daniel O'Connor wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thu, 22 Jul 2004 17:22, Marian Hettwer wrote: > >> >>If I could help testing patches for wi(4) to get support for the 2011B >>just drop me a line :) > > > I doubt wi will ever support it. > woops ... > You could try if_ndis.. (If you are running 5.2-CURRENT) > I'm running 5.2.1-release but IIRC if_ndis is already available... I'll give it a try :) thanks anyway. best regards, Marian From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 09:24:24 2004 Return-Path: Delivered-To: freebsd-current@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C52EC16A4CE for ; Thu, 22 Jul 2004 09:24:24 +0000 (GMT) Received: from mailserver1.hrz.tu-darmstadt.de (lnx131.hrz.tu-darmstadt.de [130.83.126.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8091243D2D for ; Thu, 22 Jul 2004 09:24:23 +0000 (GMT) (envelope-from lentferj@bio.tu-darmstadt.de) Received: from amdahl.bio.tu-darmstadt.de (amdahl.bio.tu-darmstadt.de [130.83.207.157])i6M9O4SR000384 for ; Thu, 22 Jul 2004 11:24:07 +0200 Received: from localhost (localhost [127.0.0.1]) by amdahl.bio.tu-darmstadt.de (Postfix) with ESMTP id DC91361B3 for ; Thu, 22 Jul 2004 11:24:08 +0200 (CEST) Received: from amdahl.bio.tu-darmstadt.de ([127.0.0.1])port 10024) with ESMTP id 00922-03 for ; Thu, 22 Jul 2004 11:23:54 +0200 (CEST) Received: from neslonek (neslonek.bio.tu-darmstadt.de [130.83.207.147]) by amdahl.bio.tu-darmstadt.de (Postfix) with ESMTP id 39E4260CE for ; Thu, 22 Jul 2004 11:23:54 +0200 (CEST) From: Jan Lentfer To: freebsd-current@www.freebsd.org Date: Thu, 22 Jul 2004 11:23:53 +0200 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: <200407221123.53863.lentferj@bio.tu-darmstadt.de> X-Virus-Scanned: by amavisd-new at amdahl.bio.tu-darmstadt.de X-TUD-HRZ-MailScanner: Found to be clean X-TUD-HRZ-MailScanner-SpamCheck: Subject: 5.2-CURRENT constantly crashing 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, 22 Jul 2004 09:24:24 -0000 Hi, i am running 5.2-CURRENT on an old 4x PPRO (200) Amdahl EnVista Server. The system is constantly crashing under heavy load for about 2-3 month now. Since all drives are connected to a Mylex Raid Controller, I can't get any kernel dumps :(. The system fails with "panic: page fault. fatal trap 12. fault code = supervisor read, page not present". Since this is old hardware I am not quite sure if this is a hardware or software problem, but the system used to run stable with 5.1-RELEASE. I don't have a serial console either, so i can't copy and paste the panic warning. Any way this can be sent over ssh so I can post the complete kernel panic?? This is the output from systat -vmstat from the last crash (don't know if it helps): 2 users Load 11.96 12.03 10.58 Jul 22 10:23 Mem:KB REAL VIRTUAL VN PAGER SWAP PAGER Tot Share Tot Share Free in out in out Act 226024 12128 585524 18944 27160 count All 482280 43796 3256020 172068 pages 1 1508 zfod Interrupts Proc:r p d s w Csw Trp Sys Int Sof Flt 96 cow 242 total 3 14113 12 2044 1884 1740 350 40 1671 94240 wire 1: atkb 257092 act 5: ahc1 15.8%Sys 1.1%Intr 51.0%User 23.6%Nice 8.4%Idl 130564 inact 6: fdc0 | | | | | | | | | | 1992 cache 129 8: rtc ========>>>>>>>>>>>>>>>>>>>>>>>>>>------------ 25832 free 9: ahc0 daefr 7 10: xl0 Namei Name-cache Dir-cache 1257 prcfr 6 11: mlx Calls hits % hits % react 13: npx 11579 11522 100 pdwak 100 0: clk pdpgs Disks mlxd0 mlxd1 cd0 fd0 pass0 intrn KB/t 5.21 0.00 0.00 0.00 0.00 61888 buf tps 5 0 0 0 0 105 dirtybuf MB/s 0.03 0.00 0.00 0.00 0.00 35957 desiredvnodes % busy 4 0 0 0 0 8989 numvnodes 1193 freevnodes amdahl# uname -a FreeBSD amdahl.bio.tu-darmstadt.de 5.2-CURRENT FreeBSD 5.2-CURRENT #2: Thu Jul 8 12:37:12 CEST 2004 lentferj@amdahl.bio.tu-darmstadt.de:/usr/obj/usr/src/sys/PPRO_SMP i386 amdahl# cat /usr/src/sys/i386/conf/PPRO_SMP machine i386 #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident PPRO_SMP # Turn on Filesystem Quotas options QUOTA # Enable IP Filtering options IPFIREWALL options IPDIVERT options IPFIREWALL_DEFAULT_TO_ACCEPT options DUMMYNET #To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" #Default places to look for devices. #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options SCHED_4BSD #4BSD scheduler options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_ACL #Support for access control lists options UFS_DIRHASH #Improve performance on big directories options MD_ROOT #MD is a potential root device options NFSCLIENT #Network Filesystem Client options NFSSERVER #Network Filesystem Server options NFS_ROOT #NFS usable as root device, requires NFSCLIENT options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem (requires PSEUDOFS) options PSEUDOFS #Pseudo-filesystem framework options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 #Compatible with FreeBSD4 options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. # Debugging for use in -current #options DDB #Enable the kernel debugger #options INVARIANTS #Enable calls of extra sanity checking options INVARIANT_SUPPORT #Extra sanity checks of internal structures, required by INVARIANTS #options WITNESS #Enable checks to detect deadlocks and cycles #options WITNESS_SKIPSPIN #Don't run witness on spinlocks for speed # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O device apic device isa device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering # SCSI Controllers #device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices #device ahd # AHA39320/29320 and onboard AIC79xx devices #device amd # AMD 53C974 (Tekram DC-390(T)) #device isp # Qlogic family #device mpt # LSI-Logic MPT-Fusion #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') #device trm # Tekram DC395U/UW/F DC315U adapters #device adv # Advansys SCSI adapters #device adw # Advansys wide SCSI adapters #device aha # Adaptec 154x SCSI adapters #device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. #device bt # Buslogic/Mylex MultiMaster SCSI adapters #device ncv # NCR 53C500 #device nsp # Workbit Ninja SCSI-3 #device stg # TMC 18C30/18C50 # RAID controllers interfaced to the SCSI subsystem #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID #device ciss # Compaq Smart RAID 5* #device dpt # DPT Smartcache III, IV - See NOTES for options! #device iir # Intel Integrated RAID #device mly # Mylex AcceleRAID/eXtremeRAID # SCSI peripherals device scbus # SCSI bus (required) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers #device aac # Adaptec FSA RAID #device aacp # SCSI passthrough for aac (requires CAM) #device amr # AMI MegaRAID #device ida # Compaq Smart RAID #device ips # IBM (Adaptec) ServeRAID device mlx # Mylex DAC960 family #device pst # Promise Supertrak SX6000 #device twe # 3ware ATA RAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc # Enable this for the pcvt (VT220 compatible) console driver #device vt #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor #device agp # support several AGP chipsets # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. device pmtimer # PCCARD (PCMCIA) support # Pcmcia and cardbus bridge support #device cbb # cardbus (yenta) bridge #device pcic # ExCA ISA and PCI bridges #device pccard # PC Card (16-bit) bus #device cardbus # CardBus (32-bit) bus # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. #device de # DEC/Intel DC21x4x (``Tulip'') #device em # Intel PRO/1000 adapter Gigabit Ethernet Card #device txp # 3Com 3cR990 (``Typhoon'') #device vx # 3Com 3c590, 3c595 (``Vortex'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support #device dc # DEC/Intel 21143 and various workalikes #device fxp # Intel EtherExpress PRO/100B (82557, 82558) #device pcn # AMD Am79C97x PCI 10/100 (precedence over 'lnc') #device rl # RealTek 8129/8139 #device sf # Adaptec AIC-6915 (``Starfire'') #device sis # Silicon Integrated Systems SiS 900/SiS 7016 #device sk # SysKonnect SK-984x and SK-982x gigabit ethernet #device ste # Sundance ST201 (D-Link DFE-550TX) #device ti # Alteon Networks Tigon I/II gigabit ethernet #device tl # Texas Instruments ThunderLAN #device tx # SMC EtherPower II (83c170 ``EPIC'') #device vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') #device bge # Broadcom BCM570xx Gigabit Ethernet # ISA Ethernet NICs. pccard nics included. #device cs # Crystal Semiconductor CS89x0 NIC # 'device ed' requires 'device miibus' #device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards #device ex # Intel EtherExpress Pro/10 and Pro/10+ #device ep # Etherlink III based cards #device fe # Fujitsu MB8696x based cards #device ie # EtherExpress 8/16, 3C507, StarLAN 10 etc. #device lnc # NE2100, NE32-VL Lance Ethernet cards #device sn # SMC's 9000 series of ethernet chips #device xe # Xircom pccard ethernet # ISA devices that use the old ISA shims #device le # Wireless NIC cards #device wlan # 802.11 support #device an # Aironet 4500/4800 802.11 wireless NICs. #device awi # BayStack 660 and others #device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. #device wl # Older non 802.11 Wavelan wireless NIC. # Pseudo devices - the number indicates how many units to allocate. device random # Entropy device device loop # Network loopback device ether # Ethernet support device sl # Kernel SLIP device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter # USB support #device uhci # UHCI PCI->USB interface #device ohci # OHCI PCI->USB interface #device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices #device ugen # Generic #device uhid # "Human Interface Devices" #device ukbd # Keyboard #device ulpt # Printer #device umass # Disks/Mass storage - Requires scbus and da #device ums # Mouse #device urio # Diamond Rio 500 MP3 player #device uscanner # Scanners # USB Ethernet, requires mii #device aue # ADMtek USB ethernet #device axe # ASIX Electronics USB ethernet #device cue # CATC USB ethernet #device kue # Kawasaki LSI USB ethernet # FireWire support #device firewire # FireWire bus code #device sbp # SCSI over FireWire (Requires scbus and da) #device fwe # Ethernet over FireWire (non-standard!) amdahl# 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.2-CURRENT #2: Thu Jul 8 12:37:12 CEST 2004 lentferj@amdahl.bio.tu-darmstadt.de:/usr/obj/usr/src/sys/PPRO_SMP Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium Pro (198.95-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbff real memory = 536870912 (512 MB) avail memory = 519884800 (495 MB) MPTable: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 4 ioapic0: Assuming intbase of 0 ioapic0 irqs 0-15 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xfc80-0xfcff mem 0xfeaffc00-0xfeaffc7f irq 10 at device 13.0 on pci0 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:01:02:a8:b4:cf xl0: [GIANT-LOCKED] eisab0: at device 14.0 on pci0 eisa0: on eisab0 mainboard0: on eisa0 slot 0 isa0: on eisab0 pci0: at device 15.0 (no driver attached) pci0: at device 20.0 (no driver attached) pcib1: at pcibus 1 on motherboard pci1: on pcib1 mlx0: port 0xec80-0xecff mem 0xfe8ffc00-0xfe8ffc7f irq 11 at device 10.0 on pci1 mlx0: [GIANT-LOCKED] mlx0: DAC960P/PD, 2 channels, firmware 3.51-0-04, 32MB RAM mlxd0: on mlx0 mlxd0: 8188MB (16769024 sectors) RAID 0 (online) mlxd1: on mlx0 mlxd1: 20455MB (41891840 sectors) RAID 0 (online) ahc0: port 0xe800-0xe8ff mem 0xfe8fe000-0xfe8fefff irq 9 at device 11.0 on pci1 ahc0: Using left over BIOS settings ahc0: [GIANT-LOCKED] aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs ahc1: port 0xe400-0xe4ff mem 0xfe8fd000-0xfe8fdfff irq 5 at device 12.0 on pci1 ahc1: Using left over BIOS settings ahc1: [GIANT-LOCKED] aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs cpu0 on motherboard cpu1 on motherboard cpu2 on motherboard cpu3 on motherboard orm0: at iomem 0xec000-0xeffff,0xea000-0xebfff,0xcf000-0xcf7ff,0xce800-0xcefff,0xc0000-0xc7fff on isa0 pmtimer0 on isa0 ata0 at port 0x3f6,0x1f0-0x1f7 irq 14 on isa0 ata1 at port 0x376,0x170-0x177 irq 15 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 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 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (port) psmcpnp0: irq resource info is missing; assuming irq 12 unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounters tick every 10.000 msec ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to accept, logging disabled Waiting 15 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! cd0 at ahc1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present Mounting root from ufs:/dev/mlxd0s1a WARNING: / was not properly dismounted WARNING: /tmp was not properly dismounted /tmp: mount pending error: blocks 40 files 10 WARNING: /usr was not properly dismounted /usr: superblock summary recomputed WARNING: /var was not properly dismounted /var: mount pending error: blocks 12 files 0 /var: superblock summary recomputed WARNING: /blast was not properly dismounted Accounting enabled Thanks, Jan From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 09:32: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 6CAA016A529 for ; Thu, 22 Jul 2004 09:32:32 +0000 (GMT) Received: from tara.freenix.org (keltia.freenix.org [82.224.56.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0BA343D1D for ; Thu, 22 Jul 2004 09:32:31 +0000 (GMT) (envelope-from roberto@keltia.freenix.fr) Received: by tara.freenix.org (Postfix/TLS, from userid 101) id EC4392E13; Thu, 22 Jul 2004 11:32:30 +0200 (CEST) Date: Thu, 22 Jul 2004 11:32:30 +0200 From: Ollivier Robert To: Martin MATO Message-ID: <20040722093230.GA1466@tara.freenix.org> Mail-Followup-To: Martin MATO , current@FreeBSD.ORG References: <40FF86E8.2090306@wanadoo.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40FF86E8.2090306@wanadoo.fr> X-Operating-System: MacOS X / PowerBook G4 - FreeBSD 5.0 / 2x PIII/800 SMP User-Agent: Mutt/1.5.6i cc: current@FreeBSD.ORG Subject: Re: Buildworld Failure at libntp 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, 22 Jul 2004 09:32:32 -0000 Martin MATO disait : > since three or four days i get this message systematically at compiling: > the buildworld worked perfectly before, and i perform an update of > the source tree by before compiling Are you building with -DNOCRYPT and/or -DNO_OPENSSL? I believe it to be fixed as I just committed a fix from Marius Strobl about this very problem. I just tested it with NOCRYPT and it worked. Don't forget t includes a patch in contrib/ntp. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr Darwin snuadh.freenix.org Kernel Version 7.4.0: Wed May 12 16:58:24 PDT 2004 From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 09:39: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 2566B16A4CE for ; Thu, 22 Jul 2004 09:39:41 +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 D9CDD43D39 for ; Thu, 22 Jul 2004 09:39:40 +0000 (GMT) (envelope-from simon@eddie.nitro.dk) Received: by eddie.nitro.dk (Postfix, from userid 1000) id 6115F117FE; Thu, 22 Jul 2004 11:39:39 +0200 (CEST) Date: Thu, 22 Jul 2004 11:39:39 +0200 From: "Simon L. Nielsen" To: Marian Hettwer Message-ID: <20040722093938.GC39030@eddie.nitro.dk> References: <40FF724C.5080308@kernel32.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="f0KYrhQ4vYSV2aJu" Content-Disposition: inline In-Reply-To: <40FF724C.5080308@kernel32.de> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: Intel Pro/Wireless 2011B & FreeBSD 5.2.1 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, 22 Jul 2004 09:39:41 -0000 --f0KYrhQ4vYSV2aJu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004.07.22 09:52:44 +0200, Marian Hettwer wrote: > Hi All, >=20 > I searched the the pr database and figured out, that support for Intel's= =20 > 2011B is in progress and that wi(4) actually doesn't support it. If you mean Intel PRO/Wireless 2100 it can be used with the ipw(4) driver or ndis. The ipw(4) driver isn't in the FreeBSD CVS tree yet, but can be found at http://damien.bergamini.free.fr/ipw/. It has worked for me with my IBM R40 "Centrino". --=20 Simon L. Nielsen FreeBSD Documentation Team --f0KYrhQ4vYSV2aJu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/4tah9pcDSc1mlERAk7tAJ9atLTb6KlVKa2LpZn248QU5JhqlACfXi5C P6Wjn9E0D9PF/I/XRmIEn1M= =lIjM -----END PGP SIGNATURE----- --f0KYrhQ4vYSV2aJu-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 09:51: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 CD59A16A4CE for ; Thu, 22 Jul 2004 09:51:54 +0000 (GMT) Received: from ms-dienst.rz.rwth-aachen.de (ms-2.rz.RWTH-Aachen.DE [134.130.3.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D1E543D4C for ; Thu, 22 Jul 2004 09:51:54 +0000 (GMT) (envelope-from chris@unixpages.org) Received: from r220-1 (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by ms-dienst.rz.rwth-aachen.de (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003)) with ESMTP id <0I1800CRDZ88FQ@ms-dienst.rz.rwth-aachen.de> for freebsd-current@freebsd.org; Thu, 22 Jul 2004 11:48:08 +0200 (MEST) Received: from relay.rwth-aachen.de ([134.130.3.1]) by r220-1 (MailMonitor for SMTP v1.2.2 ) ; Thu, 22 Jul 2004 11:48:07 +0200 (MEST) Received: from haakonia.hitnet.rwth-aachen.de (haakonia.hitnet.RWTH-Aachen.DE [137.226.181.92])i6M9m2mH011440; Thu, 22 Jul 2004 11:48:02 +0200 (MEST) Received: from gondor.middleearth (gondor.middleearth [192.168.1.42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))(Postfix) with ESMTP id ED4F32843F; Thu, 22 Jul 2004 11:48:01 +0200 (CEST) Received: by gondor.middleearth (Postfix, from userid 1001) id 8CC126106; Thu, 22 Jul 2004 11:48:01 +0200 (CEST) Date: Thu, 22 Jul 2004 11:48:01 +0200 From: Christian Brueffer In-reply-to: <40FF7A4B.1040506@kernel32.de> To: Marian Hettwer Message-id: <20040722094801.GA6903@unixpages.org> MIME-version: 1.0 Content-type: multipart/signed; boundary=qDbXVdCdHGoSgWSk; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-disposition: inline User-Agent: Mutt/1.5.5.1i X-Operating-System: FreeBSD 5.2-CURRENT X-PGP-Key: http://people.freebsd.org/~brueffer/brueffer.key.asc X-PGP-Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D References: <40FF724C.5080308@kernel32.de> <200407221729.01137.doconnor@gsoft.com.au> <40FF7A4B.1040506@kernel32.de> cc: freebsd-current@freebsd.org Subject: Re: Intel Pro/Wireless 2011B & FreeBSD 5.2.1 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, 22 Jul 2004 09:51:54 -0000 --qDbXVdCdHGoSgWSk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 22, 2004 at 10:26:51AM +0200, Marian Hettwer wrote: > Hi Daniel, >=20 > Daniel O'Connor wrote: > >-----BEGIN PGP SIGNED MESSAGE----- > >Hash: SHA1 > > > >On Thu, 22 Jul 2004 17:22, Marian Hettwer wrote: > > > >> > >>If I could help testing patches for wi(4) to get support for the 2011B > >>just drop me a line :) > > > > > >I doubt wi will ever support it. > > > woops ... >=20 > >You could try if_ndis.. (If you are running 5.2-CURRENT) > > > I'm running 5.2.1-release but IIRC if_ndis is already available... I'll= =20 > give it a try :) >=20 NDIS is not included in 5.2.1, but you can take the sources from -CURRENT. Bill Paul tries to keep the stuff compatible to 5.2.1. - Christian --=20 Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --qDbXVdCdHGoSgWSk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/41RbHYXjKDtmC0RAr0uAKC+uGE31b69n/uPMm9OYia8tTmihgCg0sFo 3An+65HHXOyjL6X/8TmneSo= =9rWj -----END PGP SIGNATURE----- --qDbXVdCdHGoSgWSk-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 10:05: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 8130116A4CE for ; Thu, 22 Jul 2004 10:05:53 +0000 (GMT) Received: from dbmail-mx11.orcon.net.nz (loadbalancer1.orcon.net.nz [219.88.242.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id E64F043D2F for ; Thu, 22 Jul 2004 10:05:52 +0000 (GMT) (envelope-from pmurray@nevada.net.nz) Received: from [10.58.2.16] (port-222-152-49-103.fastadsl.net.nz [222.152.49.103])i6MA5Tkn026349; Thu, 22 Jul 2004 22:05:33 +1200 Message-ID: <40FF9173.1070403@nevada.net.nz> Date: Thu, 22 Jul 2004 22:05:39 +1200 From: Philip Murray User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <40FF8283.1030102@nevada.net.nz> <200407221139.03935@harryhomeworkstation> In-Reply-To: <200407221139.03935@harryhomeworkstation> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamd / ClamAV version 0.73, clamav-milter version 0.73a on dbmail-mx11.orcon.net.nz X-Virus-Status: Clean X-Spam-Status: -4.9, tests=BAYES_00 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on dbmail-mx11.orcon.net.nz cc: Harald Schmalzbauer Subject: Re: 3Ware 9500 and disklabel 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, 22 Jul 2004 10:05:53 -0000 Harald Schmalzbauer wrote: >Am Donnerstag, 22. Juli 2004 11:01 schrieb Philip Murray: > > >>Hi, >> >>I'm trying to test out -CURRENT (22/7/2004) on a dual Opteron (Tyan >>board) with a 3Ware 9500-8 raid controller and I'm having problems with >>disklabel. >> >>At the moment I have a RAID0 array totalling 600GB. I fdisk'd them to >>create a single partition using the entire volume, fdisk (from >>sysinstall) complained about the geometry, I wasn't sure what the >>correct geometry was, so I forged ahead anyway. >> >>Then I went to try and disklabel it. It seemed to work from sysinstall >>until I went to write the changes out and it complained "ERROR: Unable >>to write data to disk da0!'. So I tried disklabel on the command line, as >>so >> >> > >AFAIK geom only prevents you from direct access to disks where your kernel >booted from. In your case it is ad4 and I think da1 shouldn't be affected but >perhaps you want to set the sysctl kern.geom.debugflags to 16. > > > Trying to use disklabel from sysinstall with those geom flags resulted in a panic, I got the following trace from the debugger: panic: spoiling cp->ace = 1 cpuid = 1; KDB: enter: panic [thread 100081] Stopped at kdb_enter+0x2f: nop db> trace kdb_enter() at kdb_enter+0x2f panic() at panic+0x210 g_spoil() at g_spoil+0x7a g_access() at g_access+0x1fb g_dev_open() at g_dev_open+0x11b spec_open() at spec_open+0x330 spec_vnoperate() at spec_vnoperate+0x14 vn_open_cred() at vn_open_cred+0x364 kern_open() at kern_open+0x109 syscall() at syscall+0x40e Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (5, FreeBSD ELF64, open), rip = 0x50ebc0, rsp = 0x7fffffffd838, rbp = 0x7dd780 --- db> I don't know anything more useful I can do than that, so if there is something tell me. However, I have managed to somehow lockup the serial console so I can't do anymore until tomorrow. Cheers Philip From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 13:44: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 0957116A4CE for ; Wed, 21 Jul 2004 13:44:38 +0000 (GMT) Received: from sanne.nlnetlabs.nl (sanne.nlnetlabs.nl [213.154.224.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B77043D5C for ; Wed, 21 Jul 2004 13:44:37 +0000 (GMT) (envelope-from ted@sanne.nlnetlabs.nl) Received: from sanne.nlnetlabs.nl (localhost [127.0.0.1]) by sanne.nlnetlabs.nl (8.12.11/8.12.11) with ESMTP id i6LDiODi028083 for ; Wed, 21 Jul 2004 15:44:25 +0200 (CEST) (envelope-from ted@sanne.nlnetlabs.nl) Received: (from ted@localhost) by sanne.nlnetlabs.nl (8.12.11/8.12.11/Submit) id i6LDiO9k028082 for freebsd-current@freebsd.org; Wed, 21 Jul 2004 15:44:24 +0200 (CEST) (envelope-from ted) Date: Wed, 21 Jul 2004 15:44:24 +0200 (CEST) From: Ted Lindgreen Message-Id: <200407211344.i6LDiO9k028082@sanne.nlnetlabs.nl> To: freebsd-current@freebsd.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on sanne.nlnetlabs.nl X-Mailman-Approved-At: Thu, 22 Jul 2004 11:43:57 +0000 Subject: Problem with SIGILL: EPERM 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, 21 Jul 2004 13:44:38 -0000 Hello, With NSD on FreeBSD 5.2-CURRENT, we found that a SIGILL signal, send from a parent to its own child, under certain circumstances incorrectly triggers an EPERM error. This happens when the parent process is initiated by root (to open the priviledged port 53)), and then go through the setgid, setsid, etc. procedure to become a detached process, owned by an unpriviledged user, and then fork a child. The problem is reproducable on FreeBSD 5.2-CURRENT and MacOS X 10.3.4, but only for SIGILL. For instance, SIGTERM or SIGHUP are handled correctly. The problem does NOT occur with FreeBSD 4.10-STABLE, and also not with various Linux flavors, where all signals are handled the same. Is there some deliberate (but undocumented) special processing with SIGILL in FreeBSD 5.2-CURRENT, or is this a kernel bug? Regards, -- ted From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 14:35: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 4BECC16A4CE; Wed, 21 Jul 2004 14:35:37 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEF8343D5A; Wed, 21 Jul 2004 14:35:36 +0000 (GMT) (envelope-from garycor@comcast.net) Received: from [10.56.78.111] (pcp09118143pcs.union01.nj.comcast.net[69.142.234.88]) by comcast.net (sccrmhc12) with ESMTP id <2004072114353501200fnjs5e> (Authid: garycor); Wed, 21 Jul 2004 14:35:36 +0000 Message-ID: <40FE7F94.5080605@comcast.net> Date: Wed, 21 Jul 2004 10:37:08 -0400 From: Gary Corcoran User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: conrads@cox.net References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 22 Jul 2004 11:43:57 +0000 cc: freebsd-multimedia@freebsd.org cc: freebsd-current@freebsd.org cc: Steve Roome Subject: Re: [amd64] Sound breakage with snd_ich 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: Wed, 21 Jul 2004 14:35:37 -0000 Conrad J. Sabatier wrote: > > No, mine uses the nVidia nForce3 chipset: > > atapci0: port > 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 8.0 on pci0 > > One oddity that I hadn't previously mentioned is that I can't get UDMA > higher than 100 on this machine. Don't know if that's a limitation of > the drive, or the cable, or what: > > ad0: 190782MB [387621/16/63] at ata0-master UDMA100 I believe Maxtor is the only drive maker that supports UDMA133. ST sounds like a Seagate drive, so that will only go up to UDMA100. Gary From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 16:22: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 AC1C916A4CE for ; Wed, 21 Jul 2004 16:22:37 +0000 (GMT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [128.30.28.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B8E543D3F for ; Wed, 21 Jul 2004 16:22:37 +0000 (GMT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id i6LGMZQD040481 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL CN=khavrinen.lcs.mit.edu issuer=SSL+20Client+20CA); Wed, 21 Jul 2004 12:22:36 -0400 (EDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.9/8.12.9/Submit) id i6LGMZrm040478; Wed, 21 Jul 2004 12:22:35 -0400 (EDT) (envelope-from wollman) Date: Wed, 21 Jul 2004 12:22:35 -0400 (EDT) From: Garrett Wollman Message-Id: <200407211622.i6LGMZrm040478@khavrinen.lcs.mit.edu> To: Daniel Lang In-Reply-To: <20040721151427.GC54664@atrbg11.informatik.tu-muenchen.de> References: <40F963D8.6010201@freebsd.org> <20040719060730.GA87697@nagual.pp.ru> <20040720081051.GB3001@cirb503493.alcatel.com.au> <20040721151427.GC54664@atrbg11.informatik.tu-muenchen.de> X-Spam-Score: -19.8 () IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES X-Scanned-By: MIMEDefang 2.37 X-Mailman-Approved-At: Thu, 22 Jul 2004 11:43:57 +0000 cc: current@FreeBSD.ORG Subject: Re: NEW TAR 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, 21 Jul 2004 16:22:37 -0000 < said: > I do not see, why it is important if the original file was sparse > at all or maybe in different places. You've never run out of disk space as a result of a sparse file becoming non-sparse? -GAWollman From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 23:45: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 3BCF216A4CE for ; Wed, 21 Jul 2004 23:45:48 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.248]) by mx1.FreeBSD.org (Postfix) with SMTP id 2AFD943D48 for ; Wed, 21 Jul 2004 23:45:48 +0000 (GMT) (envelope-from dhrider@gmail.com) Received: by mproxy.gmail.com with SMTP id u15so7574cwc for ; Wed, 21 Jul 2004 16:45:43 -0700 (PDT) Received: by 10.11.100.56 with SMTP id x56mr20047cwb; Wed, 21 Jul 2004 16:45:43 -0700 (PDT) Message-ID: <89ceee7040721164550707591@mail.gmail.com> Date: Wed, 21 Jul 2004 16:45:43 -0700 From: Dan Finn To: Drew Broadley In-Reply-To: <40FEF429.4060408@corrupt.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> <40FEF429.4060408@corrupt.co.nz> X-Mailman-Approved-At: Thu, 22 Jul 2004 11:43:57 +0000 cc: Kim Culhan cc: freebsd-current@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: laptop for -current 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, 21 Jul 2004 23:45:48 -0000 On Thu, 22 Jul 2004 10:54:33 +1200, Drew Broadley wrote: > Kim Culhan wrote: > > >Anyone know a laptop they think is good for FreeBSd-current? > > > > > I have a Compaq Evo n800v. > > Pros: > CPU Stepping works fine > XFree86 works fine with the monitor 15": 1400x1050@75 and the aux > s-video output. > > Cons: > The CD-RW burns blanks though with 'cdrecord' and 'burncd'. > XFree86 doesn't like coming back up when I close the lid and open it > Suspend and Resume do not work. > > Any help is appreciated for the following cons > > - Drew > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/ > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" > "XFree86 doesn't like coming back up when I close the lid and open it" I was having this problem on my Dell 2650 so I disabled it by putting : hw.acpi.lid_switch_state=NONE in /etc/sysctl.conf From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 05:36: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 8337E16A4CE for ; Thu, 22 Jul 2004 05:36:59 +0000 (GMT) Received: from ank-pki.ru (mercury.ank-pki.ru [213.170.76.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id D23F843D55 for ; Thu, 22 Jul 2004 05:36:55 +0000 (GMT) (envelope-from toxa@cterra.ru) Received: (qmail 16314 invoked by uid 0); 22 Jul 2004 09:36:53 +0400 Received: from toxa@cterra.ru by mercury.ank-pki.ru by uid 0 with qmail-scanner-1.22 Clear:RC:0(213.182.168.9):SA:0(1.1/7.0):. Processed in 20.797268 secs); 22 Jul 2004 05:36:53 -0000 Received: from unknown (HELO localhost) (toxa@213.182.168.9) by ank.nwudc.ru with SMTP; 22 Jul 2004 09:36:33 +0400 Date: Thu, 22 Jul 2004 09:35:01 +0400 From: Toxa To: freebsd-current@freebsd.org Message-ID: <20040722053501.GA2293@laptoxa.toxa.lan> Mail-Followup-To: freebsd-current@freebsd.org References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> <16639.13886.117931.641180@rosebud.alerce.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <16639.13886.117931.641180@rosebud.alerce.com> User-Agent: Outluck Express 1.5.6i for MS-DOS 6.22-SMP X-Mailer: See User-Agent above :) X-Operating-System: MS-DOS 6.22-CURRENT on Sony VAIO laptop X-PGP-Public-Key: http://toxahost.org/gpg/pubkey.asc X-Useless-Header: Do Androids Dream of Electric Sheep? X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mercury.ank-pki.ru X-Spam-Level: * X-Spam-Status: No, hits=1.1 required=7.0 tests=NO_DNS_FOR_FROM autolearn=no version=2.63 X-Mailman-Approved-At: Thu, 22 Jul 2004 11:43:57 +0000 Subject: Re: laptop for -current 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, 22 Jul 2004 05:36:59 -0000 On Wed, Jul 21, 2004 at 08:36:30PM -0700, George Hartzell wrote: > Kim Culhan writes: > > Anyone know a laptop they think is good for FreeBSd-current? > I'd find it really useful if people would include a comment about > whether the machines sucessfull suspend/sleep (S3, S3bios, S4, ...) > and recover. mine is sony vaio pcg v505-bx, suspend to ram is OK, resume is OK, but video hangs, e.g. i can log in from another pc using ssh but this is not what I want :) the rest works fine except winmodem -- Anton A. Karpov icq: 845923 jabber: toxa@jabber.ru || toxa@toxahost.org email(s): toxa@cterra.ru || postfix@sendmail.ru www: http://www.toxahost.org pgp key: http://www.toxahost.org/pgp/pubkey.asc You can finger me @toxahost.org for my current status #-------------------------------------------------- Contrary to popular belief, Unix is user friendly. It just happens to be very selective about who it decides to make friends with. /* no comment */ #-------------------------------------------------- From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 09:39: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 7629916A4CE for ; Thu, 22 Jul 2004 09:39:13 +0000 (GMT) Received: from flintsbach.schmalzbauer.de (flintsbach.schmalzbauer.de [62.245.232.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C8C143D31 for ; Thu, 22 Jul 2004 09:39:11 +0000 (GMT) (envelope-from h@schmalzbauer.de) Received: from korso.flintsbach.schmalzbauer.de (korso.flintsbach.schmalzbauer.de [172.21.2.3])i6M9d4MB061127; Thu, 22 Jul 2004 11:39:04 +0200 (CEST) (envelope-from h@schmalzbauer.de) Received: from cale.flintsbach.schmalzbauer.de (cale.flintsbach.schmalzbauer.de [172.21.1.249]) by korso.flintsbach.schmalzbauer.de (Postfix) with ESMTP id 942CC13A; Thu, 22 Jul 2004 11:39:04 +0200 (CEST) From: Harald Schmalzbauer To: freebsd-current@freebsd.org Date: Thu, 22 Jul 2004 11:38:57 +0200 User-Agent: KMail/1.6.2 References: <40FF8283.1030102@nevada.net.nz> In-Reply-To: <40FF8283.1030102@nevada.net.nz> X-OS: FreeBSD 5.3 X-Country: Germany X-Address: Munich, 80686 X-Phone2: +49 (0) 89 18947781 X-Name: Harald Schmalzbauer X-Birthday: 06 Oktober 1972 MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_3s4/AAJ9Cph2JGH"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407221139.03935@harryhomeworkstation> X-Spam-Status: No, hits=0.0 required=3.5 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mailjail.dmz.flintsbach.schmalzbauer.de X-Mailman-Approved-At: Thu, 22 Jul 2004 11:43:57 +0000 cc: Philip Murray Subject: Re: 3Ware 9500 and disklabel 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, 22 Jul 2004 09:39:13 -0000 --Boundary-02=_3s4/AAJ9Cph2JGH Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Donnerstag, 22. Juli 2004 11:01 schrieb Philip Murray: > Hi, > > I'm trying to test out -CURRENT (22/7/2004) on a dual Opteron (Tyan > board) with a 3Ware 9500-8 raid controller and I'm having problems with > disklabel. > > At the moment I have a RAID0 array totalling 600GB. I fdisk'd them to > create a single partition using the entire volume, fdisk (from > sysinstall) complained about the geometry, I wasn't sure what the > correct geometry was, so I forged ahead anyway. > > Then I went to try and disklabel it. It seemed to work from sysinstall > until I went to write the changes out and it complained "ERROR: Unable > to write data to disk da0!'. So I tried disklabel on the command line, as > so AFAIK geom only prevents you from direct access to disks where your kernel= =20 booted from. In your case it is ad4 and I think da1 shouldn't be affected b= ut=20 perhaps you want to set the sysctl kern.geom.debugflags to 16. Best regards, =2DHarry > > disklabel -e /dev/da0s1 > > Where it promptly hangs (won't respond to ^C), ps lists it as > > root 641 0.0 0.0 5600 940 p1 DL+ 8:48PM 0:00.01 > disklabel -e /dev/da0s1 > > Is this something stupid I've done (geometry?) or a bug with the twa > driver? > > I've attached my dmesg FWIW, any other information I can provide on > request. > > Philip --Boundary-02=_3s4/AAJ9Cph2JGH Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA/4s3Bylq0S4AzzwRAtVRAJ987hF5GbkYEr7uyC7a4nsZb3qUSQCghJbD mWimosRM3Gjnxrm3DG7Lubk= =5PrK -----END PGP SIGNATURE----- --Boundary-02=_3s4/AAJ9Cph2JGH-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 11:53: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 9A7D916A4CE for ; Thu, 22 Jul 2004 11:53:40 +0000 (GMT) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A86843D53 for ; Thu, 22 Jul 2004 11:53:40 +0000 (GMT) (envelope-from dan@langille.org) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 0FA1D3D34; Thu, 22 Jul 2004 07:53:40 -0400 (EDT) From: "Dan Langille" To: Christian Brueffer Date: Thu, 22 Jul 2004 07:53:39 -0400 MIME-Version: 1.0 Message-ID: <40FF7283.7059.2EECBB41@localhost> Priority: normal In-reply-to: <20040722094801.GA6903@unixpages.org> References: <40FF7A4B.1040506@kernel32.de> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body cc: freebsd-current@freebsd.org Subject: Re: Intel Pro/Wireless 2011B & FreeBSD 5.2.1 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, 22 Jul 2004 11:53:40 -0000 On 22 Jul 2004 at 11:48, Christian Brueffer wrote: > NDIS is not included in 5.2.1, but you can take the sources from -CURRENT. > Bill Paul tries to keep the stuff compatible to 5.2.1. See how I did that at http://www.freebsddiary.org/ibm-thinkpad- t41.php (search for Project Evil on that page). -- Dan Langille : http://www.langille.org/ From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 12:02: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 ADA0A16A4CF for ; Thu, 22 Jul 2004 12:02:03 +0000 (GMT) Received: from blair.epifora.com (blair.epifora.com [207.139.168.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55B7F43D1D for ; Thu, 22 Jul 2004 12:02:03 +0000 (GMT) (envelope-from drvince@anonymnet.net) Received: from localhost (localhost.epifora.com [127.0.0.1]) by blair.epifora.com (Postfix) with ESMTP id 74074165970; Thu, 22 Jul 2004 08:02:35 -0400 (EDT) Received: from mail.anonymnet.net ([205.205.52.19]) by localhost (blair.epifora.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14732-08; Thu, 22 Jul 2004 08:02:32 -0400 (EDT) Received: from mail.anonymnet.net (mail.anonymnet.net [205.205.52.19]) by mail.anonymnet.net (Postfix) with ESMTP id 111AB165979; Thu, 22 Jul 2004 08:02:32 -0400 (EDT) From: "DrVince" To: Jan Lentfer Date: Thu, 22 Jul 2004 07:02:31 -0500 Message-Id: <20040722114646.M69035@anonymnet.net> In-Reply-To: <200407221123.53863.lentferj@bio.tu-darmstadt.de> References: <200407221123.53863.lentferj@bio.tu-darmstadt.de> X-Mailer: Open WebMail 2.30 20040131 X-OriginatingIP: 205.205.52.19 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 cc: freebsd-current Subject: Re: 5.2-CURRENT constantly crashing 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, 22 Jul 2004 12:02:03 -0000 On Thu, 22 Jul 2004 11:23:53 +0200, Jan Lentfer wrote > i am running 5.2-CURRENT on an old 4x PPRO (200) Amdahl EnVista Server. > The system is constantly crashing under heavy load for about 2-3 > month now. Since all drives are connected to a Mylex Raid Controller, > I can't get any kernel dumps :(. I've been reporting this for a while. I have all new hardware and running 2 IDE local drives, nothing's faulty. Everything is working fine now that I have downgraded to 5.2.1. I have no kernel dump either since it's a problem with software disk write buffer. But, at least, you get a message of what could be the problem, I only got dead freezes. For me, it wasn't heavy loads that was crashing it, but only buffers getting full. At the moment, all I can say to help is, if you use dummynet or altq, be sure to have HZ=1000 in your kernel. But that won't help you much because your server was working fine. Good luck, DrVince DrVince@anonymnet.net From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 12:15: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 EB50816A4CE for ; Thu, 22 Jul 2004 12:15:09 +0000 (GMT) Received: from mirrorball.theloosingend.net (m069c.studby.ntnu.no [129.241.130.69]) by mx1.FreeBSD.org (Postfix) with SMTP id 0491C43D39 for ; Thu, 22 Jul 2004 12:15:09 +0000 (GMT) (envelope-from svein-freebsd-current@theloosingend.net) Received: (qmail 98682 invoked by uid 1001); 22 Jul 2004 12:15:08 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 22 Jul 2004 12:15:08 -0000 Date: Thu, 22 Jul 2004 14:15:07 +0200 (CEST) From: Svein Halvor Halvorsen X-X-Sender: sveinhal@mirrorball.theloosingend.net To: current@freebsd.org Message-ID: <20040722141237.O98018@mirrorball.theloosingend.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: if_ndis/5.2.1/smc2602w-r3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: 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: Thu, 22 Jul 2004 12:15:10 -0000 I tried asking on questions to no avail. So I'll try again here, since this is -current code I'm tinkering with here. Copying src/sys/modules/if_ndis src/sys/modules/ndis src/sys/compat/ndis src/sys/dev/if_ndis ... from a current source-tree to my 5.2.1-box, and compiling using a ndis_driver_data.h made from the latest driver found on SMC's website using a ndisctl on my current system, seems to work fine. kldload-ing ndis also seems to work. But when I kldload if_ndis, the system freezes. No error messages, no response. A cold boot is the only thing that seems to fix it. Is this supposed to work, or am I trying to do the impossible here? Any hints would be appreciated. Svein Halvor Btw: ndisctl choked on the inf-file, because of a missing newline at the end. The fact that the syntax error occured on the last line, hinted on a missing newline, but I think ndisctl should either give a more precise error message, or preferable just cope with a missing newline. _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 12: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 81CB916A4CE for ; Thu, 22 Jul 2004 12:23:48 +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 289CB43D39 for ; Thu, 22 Jul 2004 12:23:48 +0000 (GMT) (envelope-from rasputin@hellooperator.net) Received: from rasputin by 9.hellooperator.net with local (Exim 4.34) id 1Bncby-0005UX-Rr for freebsd-current@freebsd.org; Thu, 22 Jul 2004 13:23:46 +0100 Date: Thu, 22 Jul 2004 13:23:46 +0100 From: Dick Davies To: FreeBSD Current list Message-ID: <20040722122346.GB27559@lb.tenfour> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Sender: Rasputin Subject: Re: vmnet.ko missing - but it's there! - vmware and crashes 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, 22 Jul 2004 12:23:48 -0000 * Garance A Drosihn [0759 01:59]: > At 12:01 PM -0400 7/21/04, Robert Watson wrote: > > > >I've been wondering if we shouldn't bring the VMware modules into > >the base source tree for some time -- the license is probably an > >issue, but VMware is a valuable tool for development, and I'm > >amazed at how frequently and accurately I shoot my feet due to > >stale versions of the module ... > > It would be great to have more reliable support for VMware, as > it can be a very helpful tool. I am also hopeful that the guys > at http://www.serenityvirtual.com/ will eventually get to their > virtual-machine product, which is supposed to run natively under > FreeBSD. Right now they're still in the beta-version process, > and they have not started to beta-test the product which will > run with FreeBSD as the host OS. (perhaps they're waiting for > 5.3-stable... :-). > > Right now my solution is to keep running VMware 2 on my > freebsd 4.10-system. Neither of those are changing much, so > that works well enough for my purposes. But if I had an option > which would reliably work on a 5.x-system, that would be very > helpful. I know we're veering OT here, but are there any plans to support Xen? http://www.cl.cam.ac.uk/Research/SRG/netos/xen/ It seems like an promising alternative to vmware or jails for shared hosting environments... -- People often find it easier to be a result of the past than a cause of the future. Rasputin :: Jack of All Trades - Master of Nuns From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 12: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 932F516A4CE for ; Thu, 22 Jul 2004 12:36:48 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BBE243D5C for ; Thu, 22 Jul 2004 12:36:48 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6MCa9p6081357; Thu, 22 Jul 2004 08:36:09 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6MCa8at081352; Thu, 22 Jul 2004 08:36:08 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 22 Jul 2004 08:36:08 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Bjoern A. Zeeb" In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Wiktor Niesiobedzki cc: FreeBSD current mailing list Subject: Re: LORs with 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: Thu, 22 Jul 2004 12:36:48 -0000 On Thu, 22 Jul 2004, Bjoern A. Zeeb wrote: > > I don't think, it was reported yet, but here it goes: > > > > lock order reversal > > 1st 0xc0632c80 pf task mtx (pf task mtx) @ /usr/src/sys/contrib/pf/net/pf.c:5822 > > 2nd 0xc066638c tcp (tcp) @ /usr/src/sys/contrib/pf/net/pf.c:2420 > > for reference: added it to "LOR page" with LOR # 017: > http://sources.zabbadoz.net/freebsd/lor.html#017 I have no immediate fix, but here's an explanation: This likely occurs because calls are made into pf in the outgoing packet path, which may hold protocol layer locks (inpcb and pcbinfo locks). The pf mutex will therefore typically follow the protocol locks in the lock order. However, when pf calls up to the pcb/socket code to find potentially matching pcbs or sockets for a packet, it can't/shouldn't hold the pf lock across that. A similar bug exists in ipfw. FWIW, this is actually symptomatic of a race: technically, that pcb lookup could have a different result between when the firewall looks it up and when the TCP or UDP code looks it up. It's a property of what is generally considered a layering violation, albeit a useful one. The solution I'm looking at for ipfw, but haven't had a chance to prototype yet, is to avoid holding the mutex for the duration of the call to ipfw, but instead use some rule set reference count such that ipfw consumers hold a reference on the rules to prevent them from changing out from under them. Note that this has interesting semantic consideration such as starvation, which are usually remedied using copy-on-write, but that may be expensive for large rule sets. Just something to think about... 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 Jul 22 12:37: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 667A816A4CF for ; Thu, 22 Jul 2004 12:37:42 +0000 (GMT) Received: from hetzner.co.za (lfw.hetzner.co.za [196.7.18.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98FA843D3F for ; Thu, 22 Jul 2004 12:37:41 +0000 (GMT) (envelope-from ianf@hetzner.co.za) Received: from localhost ([127.0.0.1]) by hetzner.co.za with esmtp (Exim 3.36 #1) id 1Bncom-000BdL-00; Thu, 22 Jul 2004 14:37:00 +0200 To: Garrett Wollman From: Ian FREISLICH In-Reply-To: Message from Garrett Wollman <200407211622.i6LGMZrm040478@khavrinen.lcs.mit.edu> Date: Thu, 22 Jul 2004 14:37:00 +0200 Sender: ianf@hetzner.co.za Message-Id: cc: current@FreeBSD.ORG cc: Daniel Lang Subject: Re: NEW TAR 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, 22 Jul 2004 12:37:42 -0000 Garrett Wollman wrote: > < said: > > > I do not see, why it is important if the original file was sparse > > at all or maybe in different places. > > You've never run out of disk space as a result of a sparse file > becoming non-sparse? So, are you arguing for or against tar converting files into sparse files where it can as Daniel proposes? I have heard stories about D.O.S. attacking backups by creating a large sparse file that would be backed up using tar. Daniel's proposal would be a boon in this instance. How does dump handle sparse files? Ian -- Ian Freislich From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 12:38:34 2004 Return-Path: Delivered-To: freebsd-current@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 970DB16A4D0 for ; Thu, 22 Jul 2004 12:38:34 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1482F43D1F for ; Thu, 22 Jul 2004 12:38:34 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6MCbpBr081404; Thu, 22 Jul 2004 08:37:51 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6MCbo5s081401; Thu, 22 Jul 2004 08:37:51 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 22 Jul 2004 08:37:50 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Jan Lentfer In-Reply-To: <200407221123.53863.lentferj@bio.tu-darmstadt.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@www.freebsd.org Subject: Re: 5.2-CURRENT constantly crashing 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, 22 Jul 2004 12:38:34 -0000 On Thu, 22 Jul 2004, Jan Lentfer wrote: > i am running 5.2-CURRENT on an old 4x PPRO (200) Amdahl EnVista Server. > The system is constantly crashing under heavy load for about 2-3 month > now. Since all drives are connected to a Mylex Raid Controller, I can't > get any kernel dumps :(. > > The system fails with "panic: page fault. fatal trap 12. fault code = > supervisor read, page not present". > > Since this is old hardware I am not quite sure if this is a hardware or > software problem, but the system used to run stable with 5.1-RELEASE. > > I don't have a serial console either, so i can't copy and paste the > panic warning. Any way this can be sent over ssh so I can post the > complete kernel panic?? Not easily. The most useful thing up front would be to know what the faulting address is, and to have you turn the instruction pointer in the panic into an address in the kernel. If you can get into DDB and get a stack trace, a list of the names of the symbols (and ideally the offsets) would be good. The best answer would be if you could set up a serial console temporarily, as it will both save you trouble and increase accuracy. Thanks! Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research > > This is the output from systat -vmstat from the last crash (don't know if it > helps): > > 2 users Load 11.96 12.03 10.58 Jul 22 10:23 > > Mem:KB REAL VIRTUAL VN PAGER SWAP PAGER > Tot Share Tot Share Free in out in out > Act 226024 12128 585524 18944 27160 count > All 482280 43796 3256020 172068 pages 1 > 1508 zfod Interrupts > Proc:r p d s w Csw Trp Sys Int Sof Flt 96 cow 242 total > 3 14113 12 2044 1884 1740 350 40 1671 94240 wire 1: atkb > 257092 act 5: ahc1 > 15.8%Sys 1.1%Intr 51.0%User 23.6%Nice 8.4%Idl 130564 inact 6: fdc0 > | | | | | | | | | | 1992 cache 129 8: rtc > ========>>>>>>>>>>>>>>>>>>>>>>>>>>------------ 25832 free 9: ahc0 > daefr 7 10: xl0 > Namei Name-cache Dir-cache 1257 prcfr 6 11: mlx > Calls hits % hits % react 13: npx > 11579 11522 100 pdwak 100 0: clk > pdpgs > Disks mlxd0 mlxd1 cd0 fd0 pass0 intrn > KB/t 5.21 0.00 0.00 0.00 0.00 61888 buf > tps 5 0 0 0 0 105 dirtybuf > MB/s 0.03 0.00 0.00 0.00 0.00 35957 desiredvnodes > % busy 4 0 0 0 0 8989 numvnodes > 1193 freevnodes > > > > > amdahl# uname -a > FreeBSD amdahl.bio.tu-darmstadt.de 5.2-CURRENT FreeBSD 5.2-CURRENT #2: Thu Jul > 8 12:37:12 CEST 2004 > lentferj@amdahl.bio.tu-darmstadt.de:/usr/obj/usr/src/sys/PPRO_SMP i386 > > > > > amdahl# cat /usr/src/sys/i386/conf/PPRO_SMP > > machine i386 > #cpu I486_CPU > #cpu I586_CPU > cpu I686_CPU > ident PPRO_SMP > > # Turn on Filesystem Quotas > options QUOTA > > # Enable IP Filtering > options IPFIREWALL > options IPDIVERT > options IPFIREWALL_DEFAULT_TO_ACCEPT > options DUMMYNET > > #To statically compile in device wiring instead of /boot/device.hints > #hints "GENERIC.hints" #Default places to look for devices. > > #makeoptions DEBUG=-g #Build kernel with gdb(1) debug > symbols > > options SCHED_4BSD #4BSD scheduler > options INET #InterNETworking > options INET6 #IPv6 communications protocols > options FFS #Berkeley Fast Filesystem > options SOFTUPDATES #Enable FFS soft updates support > options UFS_ACL #Support for access control lists > options UFS_DIRHASH #Improve performance on big > directories > options MD_ROOT #MD is a potential root device > options NFSCLIENT #Network Filesystem Client > options NFSSERVER #Network Filesystem Server > options NFS_ROOT #NFS usable as root device, requires > NFSCLIENT > options MSDOSFS #MSDOS Filesystem > options CD9660 #ISO 9660 Filesystem > options PROCFS #Process filesystem (requires > PSEUDOFS) > options PSEUDOFS #Pseudo-filesystem framework > options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] > options COMPAT_FREEBSD4 #Compatible with FreeBSD4 > options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI > options KTRACE #ktrace(1) support > options SYSVSHM #SYSV-style shared memory > options SYSVMSG #SYSV-style message queues > options SYSVSEM #SYSV-style semaphores > options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time > extensions > options KBD_INSTALL_CDEV # install a CDEV entry in /dev > options AHC_REG_PRETTY_PRINT # Print register bitfields in debug > # output. Adds ~128k to driver. > options AHD_REG_PRETTY_PRINT # Print register bitfields in debug > # output. Adds ~215k to driver. > > # Debugging for use in -current > #options DDB #Enable the kernel debugger > #options INVARIANTS #Enable calls of extra sanity checking > options INVARIANT_SUPPORT #Extra sanity checks of internal > structures, required by INVARIANTS > #options WITNESS #Enable checks to detect deadlocks and > cycles > #options WITNESS_SKIPSPIN #Don't run witness on spinlocks for > speed > > # To make an SMP kernel, the next two are needed > options SMP # Symmetric MultiProcessor Kernel > #options APIC_IO # Symmetric (APIC) I/O > device apic > > device isa > device eisa > device pci > > # Floppy drives > device fdc > > # ATA and ATAPI devices > device ata > device atadisk # ATA disk drives > device atapicd # ATAPI CDROM drives > device atapifd # ATAPI floppy drives > device atapist # ATAPI tape drives > options ATA_STATIC_ID #Static device numbering > > # SCSI Controllers > #device ahb # EISA AHA1742 family > device ahc # AHA2940 and onboard AIC7xxx devices > #device ahd # AHA39320/29320 and onboard AIC79xx devices > #device amd # AMD 53C974 (Tekram DC-390(T)) > #device isp # Qlogic family > #device mpt # LSI-Logic MPT-Fusion > #device ncr # NCR/Symbios Logic > #device sym # NCR/Symbios Logic (newer chipsets + those of > `ncr') > #device trm # Tekram DC395U/UW/F DC315U adapters > > #device adv # Advansys SCSI adapters > #device adw # Advansys wide SCSI adapters > #device aha # Adaptec 154x SCSI adapters > #device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. > #device bt # Buslogic/Mylex MultiMaster SCSI adapters > > #device ncv # NCR 53C500 > #device nsp # Workbit Ninja SCSI-3 > #device stg # TMC 18C30/18C50 > > # RAID controllers interfaced to the SCSI subsystem > #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID > #device ciss # Compaq Smart RAID 5* > #device dpt # DPT Smartcache III, IV - See NOTES for > options! > #device iir # Intel Integrated RAID > #device mly # Mylex AcceleRAID/eXtremeRAID > > # SCSI peripherals > device scbus # SCSI bus (required) > device ch # SCSI media changers > device da # Direct Access (disks) > device sa # Sequential Access (tape etc) > device cd # CD > device pass # Passthrough device (direct SCSI access) > device ses # SCSI Environmental Services (and SAF-TE) > > # RAID controllers > #device aac # Adaptec FSA RAID > #device aacp # SCSI passthrough for aac (requires CAM) > #device amr # AMI MegaRAID > #device ida # Compaq Smart RAID > #device ips # IBM (Adaptec) ServeRAID > device mlx # Mylex DAC960 family > #device pst # Promise Supertrak SX6000 > #device twe # 3ware ATA RAID > > # atkbdc0 controls both the keyboard and the PS/2 mouse > device atkbdc # AT keyboard controller > device atkbd # AT keyboard > device psm # PS/2 mouse > > device vga # VGA video card driver > > device splash # Splash screen and screen saver support > > # syscons is the default console driver, resembling an SCO console > device sc > > # Enable this for the pcvt (VT220 compatible) console driver > #device vt > #options XSERVER # support for X server on a vt console > #options FAT_CURSOR # start with block cursor > > #device agp # support several AGP chipsets > > # Floating point support - do not disable. > device npx > > # Power management support (see NOTES for more options) > #device apm > # Add suspend/resume support for the i8254. > device pmtimer > > # PCCARD (PCMCIA) support > # Pcmcia and cardbus bridge support > #device cbb # cardbus (yenta) bridge > #device pcic # ExCA ISA and PCI bridges > #device pccard # PC Card (16-bit) bus > #device cardbus # CardBus (32-bit) bus > > # Serial (COM) ports > device sio # 8250, 16[45]50 based serial ports > > # Parallel port > device ppc > device ppbus # Parallel port bus (required) > device lpt # Printer > device plip # TCP/IP over parallel > device ppi # Parallel port interface device > #device vpo # Requires scbus and da > > > # PCI Ethernet NICs. > #device de # DEC/Intel DC21x4x (``Tulip'') > #device em # Intel PRO/1000 adapter Gigabit Ethernet Card > #device txp # 3Com 3cR990 (``Typhoon'') > #device vx # 3Com 3c590, 3c595 (``Vortex'') > > # PCI Ethernet NICs that use the common MII bus controller code. > # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! > device miibus # MII bus support > #device dc # DEC/Intel 21143 and various workalikes > #device fxp # Intel EtherExpress PRO/100B (82557, 82558) > #device pcn # AMD Am79C97x PCI 10/100 (precedence over > 'lnc') > #device rl # RealTek 8129/8139 > #device sf # Adaptec AIC-6915 (``Starfire'') > #device sis # Silicon Integrated Systems SiS 900/SiS 7016 > #device sk # SysKonnect SK-984x and SK-982x gigabit > ethernet > #device ste # Sundance ST201 (D-Link DFE-550TX) > #device ti # Alteon Networks Tigon I/II gigabit ethernet > #device tl # Texas Instruments ThunderLAN > #device tx # SMC EtherPower II (83c170 ``EPIC'') > #device vr # VIA Rhine, Rhine II > #device wb # Winbond W89C840F > device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') > #device bge # Broadcom BCM570xx Gigabit Ethernet > > # ISA Ethernet NICs. pccard nics included. > #device cs # Crystal Semiconductor CS89x0 NIC > # 'device ed' requires 'device miibus' > #device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards > #device ex # Intel EtherExpress Pro/10 and Pro/10+ > #device ep # Etherlink III based cards > #device fe # Fujitsu MB8696x based cards > #device ie # EtherExpress 8/16, 3C507, StarLAN 10 etc. > #device lnc # NE2100, NE32-VL Lance Ethernet cards > #device sn # SMC's 9000 series of ethernet chips > #device xe # Xircom pccard ethernet > > # ISA devices that use the old ISA shims > #device le > > # Wireless NIC cards > #device wlan # 802.11 support > #device an # Aironet 4500/4800 802.11 wireless NICs. > #device awi # BayStack 660 and others > #device wi # WaveLAN/Intersil/Symbol 802.11 wireless > NICs. > #device wl # Older non 802.11 Wavelan wireless NIC. > > # Pseudo devices - the number indicates how many units to allocate. > device random # Entropy device > device loop # Network loopback > device ether # Ethernet support > device sl # Kernel SLIP > device ppp # Kernel PPP > device tun # Packet tunnel. > device pty # Pseudo-ttys (telnet etc) > device md # Memory "disks" > device gif # IPv6 and IPv4 tunneling > device faith # IPv6-to-IPv4 relaying (translation) > > # The `bpf' device enables the Berkeley Packet Filter. > # Be aware of the administrative consequences of enabling this! > device bpf # Berkeley packet filter > > # USB support > #device uhci # UHCI PCI->USB interface > #device ohci # OHCI PCI->USB interface > #device usb # USB Bus (required) > #device udbp # USB Double Bulk Pipe devices > #device ugen # Generic > #device uhid # "Human Interface Devices" > #device ukbd # Keyboard > #device ulpt # Printer > #device umass # Disks/Mass storage - Requires scbus and da > #device ums # Mouse > #device urio # Diamond Rio 500 MP3 player > #device uscanner # Scanners > # USB Ethernet, requires mii > #device aue # ADMtek USB ethernet > #device axe # ASIX Electronics USB ethernet > #device cue # CATC USB ethernet > #device kue # Kawasaki LSI USB ethernet > > # FireWire support > #device firewire # FireWire bus code > #device sbp # SCSI over FireWire (Requires scbus and da) > #device fwe # Ethernet over FireWire (non-standard!) > > > > > amdahl# 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.2-CURRENT #2: Thu Jul 8 12:37:12 CEST 2004 > lentferj@amdahl.bio.tu-darmstadt.de:/usr/obj/usr/src/sys/PPRO_SMP > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Pentium Pro (198.95-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x619 Stepping = 9 > Features=0xfbff > real memory = 536870912 (512 MB) > avail memory = 519884800 (495 MB) > MPTable: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 4 > ioapic0: Assuming intbase of 0 > ioapic0 irqs 0-15 on motherboard > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > pcib0: at pcibus 0 on > motherboard > pci0: on pcib0 > xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xfc80-0xfcff mem > 0xfeaffc00-0xfeaffc7f irq 10 at device 13.0 on pci0 > miibus0: on xl0 > xlphy0: <3Com internal media interface> on miibus0 > xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > xl0: Ethernet address: 00:01:02:a8:b4:cf > xl0: [GIANT-LOCKED] > eisab0: at device 14.0 on pci0 > eisa0: on eisab0 > mainboard0: on eisa0 slot 0 > isa0: on eisab0 > pci0: at device 15.0 (no driver attached) > pci0: at device 20.0 (no driver attached) > pcib1: at pcibus 1 on > motherboard > pci1: on pcib1 > mlx0: port 0xec80-0xecff mem > 0xfe8ffc00-0xfe8ffc7f irq 11 at device 10.0 on pci1 > mlx0: [GIANT-LOCKED] > mlx0: DAC960P/PD, 2 channels, firmware 3.51-0-04, 32MB RAM > mlxd0: on mlx0 > mlxd0: 8188MB (16769024 sectors) RAID 0 (online) > mlxd1: on mlx0 > mlxd1: 20455MB (41891840 sectors) RAID 0 (online) > ahc0: port 0xe800-0xe8ff mem > 0xfe8fe000-0xfe8fefff irq 9 at device 11.0 on pci1 > ahc0: Using left over BIOS settings > ahc0: [GIANT-LOCKED] > aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs > ahc1: port 0xe400-0xe4ff mem > 0xfe8fd000-0xfe8fdfff irq 5 at device 12.0 on pci1 > ahc1: Using left over BIOS settings > ahc1: [GIANT-LOCKED] > aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs > cpu0 on motherboard > cpu1 on motherboard > cpu2 on motherboard > cpu3 on motherboard > orm0: at iomem > 0xec000-0xeffff,0xea000-0xebfff,0xcf000-0xcf7ff,0xce800-0xcefff,0xc0000-0xc7fff > on isa0 > pmtimer0 on isa0 > ata0 at port 0x3f6,0x1f0-0x1f7 irq 14 on isa0 > ata1 at port 0x376,0x170-0x177 irq 15 on isa0 > atkbdc0: at port 0x64,0x60 on isa0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > fdc0: at port > 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > ppc0: at port 0x378-0x37f irq 7 on isa0 > 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 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > unknown: can't assign resources (port) > psmcpnp0: irq resource info is missing; assuming irq 12 > unknown: can't assign resources (port) > unknown: can't assign resources (port) > unknown: can't assign resources (port) > unknown: can't assign resources (port) > Timecounters tick every 10.000 msec > ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to > accept, logging disabled > Waiting 15 seconds for SCSI devices to settle > SMP: AP CPU #1 Launched! > SMP: AP CPU #2 Launched! > SMP: AP CPU #3 Launched! > cd0 at ahc1 bus 0 target 0 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 10.000MB/s transfers (10.000MHz, offset 8) > cd0: Attempt to query device size failed: NOT READY, Medium not present > Mounting root from ufs:/dev/mlxd0s1a > WARNING: / was not properly dismounted > WARNING: /tmp was not properly dismounted > /tmp: mount pending error: blocks 40 files 10 > WARNING: /usr was not properly dismounted > /usr: superblock summary recomputed > WARNING: /var was not properly dismounted > /var: mount pending error: blocks 12 files 0 > /var: superblock summary recomputed > WARNING: /blast was not properly dismounted > Accounting enabled > > > > Thanks, > > > Jan > _______________________________________________ > 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 Thu Jul 22 12:39: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 B3A3616A4CE for ; Thu, 22 Jul 2004 12:39:29 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E86443D54 for ; Thu, 22 Jul 2004 12:39:29 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6MCcYFL081431; Thu, 22 Jul 2004 08:38:34 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6MCcYl0081428; Thu, 22 Jul 2004 08:38:34 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 22 Jul 2004 08:38:34 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: DrVince In-Reply-To: <20040722114646.M69035@anonymnet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Jan Lentfer cc: freebsd-current Subject: Re: 5.2-CURRENT constantly crashing 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, 22 Jul 2004 12:39:29 -0000 On Thu, 22 Jul 2004, DrVince wrote: > On Thu, 22 Jul 2004 11:23:53 +0200, Jan Lentfer wrote > > i am running 5.2-CURRENT on an old 4x PPRO (200) Amdahl EnVista Server. > > The system is constantly crashing under heavy load for about 2-3 > > month now. Since all drives are connected to a Mylex Raid Controller, > > I can't get any kernel dumps :(. > > I've been reporting this for a while. I have all new hardware and > running 2 IDE local drives, nothing's faulty. Everything is working > fine now that I have downgraded to 5.2.1. I have no kernel dump either > since it's a problem with software disk write buffer. But, at least, you > get a message of what could be the problem, I only got dead freezes. > For me, it wasn't heavy loads that was crashing it, but only buffers > getting full. I recently disabled sync-on-panic, which may increase the reliability of dumping. 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 Jul 22 12:53: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 2F4BC16A4CE; Thu, 22 Jul 2004 12:53:03 +0000 (GMT) Received: from www.cyclades.de (mail.cyclades.de [62.225.173.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id B411D43D45; Thu, 22 Jul 2004 12:53:02 +0000 (GMT) (envelope-from mh@kernel32.de) Received: from [192.168.10.114] (helo=kernel32.de) by www.cyclades.de with asmtp (Exim 3.35 #1 (Debian)) id 1BnbLs-0003SZ-00; Thu, 22 Jul 2004 13:03:04 +0200 Message-ID: <40FF9ECA.6070409@kernel32.de> Date: Thu, 22 Jul 2004 13:02:34 +0200 From: Marian Hettwer User-Agent: Mozilla Thunderbird 0.5 (X11/20040414) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Simon L. Nielsen" References: <40FF724C.5080308@kernel32.de> <20040722093938.GC39030@eddie.nitro.dk> In-Reply-To: <20040722093938.GC39030@eddie.nitro.dk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner: Found to be clean X-MailScanner-SpamCheck: cc: freebsd-current@freebsd.org Subject: Re: Intel Pro/Wireless 2011B & FreeBSD 5.2.1 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, 22 Jul 2004 12:53:03 -0000 Hi Simon, Simon L. Nielsen wrote: > On 2004.07.22 09:52:44 +0200, Marian Hettwer wrote: > >>Hi All, >> >>I searched the the pr database and figured out, that support for Intel's >>2011B is in progress and that wi(4) actually doesn't support it. > > > If you mean Intel PRO/Wireless 2100 it can be used with the ipw(4) no, I meant the Pro/Wireless 2011B ... :) I believe it's a different one ... thanks anyway, Marian From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 13:06: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 8821016A4CE; Thu, 22 Jul 2004 13:06:03 +0000 (GMT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EDED43D1F; Thu, 22 Jul 2004 13:06:03 +0000 (GMT) (envelope-from marks@dell-laptop.6bone.nl) Received: by postman.ripe.net (Postfix, from userid 8) id 6E85A4E32B; Thu, 22 Jul 2004 15:06:02 +0200 (CEST) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id 2D4D84E25C; Thu, 22 Jul 2004 15:06:02 +0200 (CEST) Received: from dell-laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id i6MD624c017249; Thu, 22 Jul 2004 15:06:02 +0200 Received: (nullmailer pid 6722 invoked by uid 1001); Thu, 22 Jul 2004 13:06:01 -0000 Date: Thu, 22 Jul 2004 15:06:01 +0200 From: Mark Santcroos To: Robert Watson Message-ID: <20040722130601.GA2751@laptop.6bone.nl> References: <40FE8F81.7040409@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Status: N 0.021436 / 0.0 / 0.0 / disabled X-RIPE-Signature: 8e89a2dabd2545582b43ba63ad8fd93c cc: "freebsd -current@" Subject: Re: vmnet.ko missing - but it's there! - vmware and crashes 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, 22 Jul 2004 13:06:03 -0000 On Wed, Jul 21, 2004 at 12:01:40PM -0400, Robert Watson wrote: > I've been wondering if we shouldn't bring the VMware modules into the base > source tree for some time -- the license is probably an issue Bringing it simply in the base tree is indeed not an option. What I think that we need is mechanism to connect 3rd party modules to the build. So that when the kernel is rebuild, the 3rd party modules are rebuild too. Of course there is a change that the module won't compile, but we should create a mechanism then where we can disable that module easily until the port gets updated too. IMHO the most important point to reach is that it can't happen anymore that we load an out-of-sync vmware module at boot time and panic. It should either be correctly rebuild or not installed at all (and removed). Mark From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 13:08: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 0EBDB16A4CE; Thu, 22 Jul 2004 13:08:50 +0000 (GMT) Received: from musique.teaser.net (musique.teaser.net [213.91.2.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F85C43D39; Thu, 22 Jul 2004 13:08:49 +0000 (GMT) (envelope-from e-masson@kisoft-services.com) Received: from srvbsdnanssv.interne.kisoft-services.com (nantes.kisoft-services.com [193.56.60.243]) by musique.teaser.net (Postfix) with ESMTP id 4A9907250D; Thu, 22 Jul 2004 15:08:48 +0200 (CEST) Received: by srvbsdnanssv.interne.kisoft-services.com (Postfix, from userid 1001) id E3023C1FC; Thu, 22 Jul 2004 15:08:47 +0200 (CEST) To: Marian Hettwer From: Eric Masson In-Reply-To: <40FF9ECA.6070409@kernel32.de> (Marian Hettwer's message of "Thu, 22 Jul 2004 13:02:34 +0200") References: <40FF724C.5080308@kernel32.de> <20040722093938.GC39030@eddie.nitro.dk> <40FF9ECA.6070409@kernel32.de> X-Operating-System: FreeBSD 5.2.1-RELEASE-p9 i386 Date: Thu, 22 Jul 2004 15:08:47 +0200 Message-ID: <86wu0wxk80.fsf@srvbsdnanssv.interne.kisoft-services.com> User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit cc: freebsd-current@freebsd.org cc: "Simon L. Nielsen" Subject: Re: Intel Pro/Wireless 2011B & FreeBSD 5.2.1 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, 22 Jul 2004 13:08:50 -0000 >>>>> "Marian" == Marian Hettwer writes: Marian> no, I meant the Pro/Wireless 2011B ... :) I believe it's a Marian> different one ... Yes, iirc it's a 2011 with no firmware, you have to upload the firmware to the card to make it work (imp posted about this card a few years ago, so there must be something in Google groups) Eric Masson -- Dis tu nous lâches un peu ? C'est un sujet assez important pour qu'on en parle, peu importe le groupe. C'est à cause de gens comme toi si c'est la merde sur le net. Tes leçons de nétiquéquette, tu peux te les... OK? -+- Ghost in : - Terrorisme neuneulectuel -+- From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 13:22: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 E881B16A4CE for ; Thu, 22 Jul 2004 13:22:56 +0000 (GMT) Received: from hetzner.co.za (lfw.hetzner.co.za [196.7.18.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D79543D41 for ; Thu, 22 Jul 2004 13:22:56 +0000 (GMT) (envelope-from ianf@hetzner.co.za) Received: from localhost ([127.0.0.1]) by hetzner.co.za with esmtp (Exim 3.36 #1) id 1BndWu-000Bqw-00; Thu, 22 Jul 2004 15:22:36 +0200 To: SanD From: Ian FREISLICH In-Reply-To: Message from SanD <200407221325.i6MDPhqL024040@aaz.links.ru> Date: Thu, 22 Jul 2004 15:22:36 +0200 Sender: ianf@hetzner.co.za Message-Id: cc: current@freebsd.org Subject: Re: NEW TAR 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, 22 Jul 2004 13:22:57 -0000 SanD wrote: > Ian wrote: > > How does dump handle sparse files? > Dump handles fine sparse files. Maybe I should have asked how does dump figure out that the files are sparse and if it's any more intelligent than a 2 pass read (I have no idea why 2 passes are required) or just blindly turning successive zeros into a seek offset, is there anything preventing BSD tar from doing the same? Ian -- Ian Freislich From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 13:47: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 DB68316A4CE for ; Thu, 22 Jul 2004 13:47:46 +0000 (GMT) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id A536543D46 for ; Thu, 22 Jul 2004 13:47:46 +0000 (GMT) (envelope-from dan@langille.org) Received: from xeon (xeon.unixathome.org [192.168.0.18]) by bast.unixathome.org (Postfix) with ESMTP id 9C87F3D34 for ; Thu, 22 Jul 2004 09:47:45 -0400 (EDT) Date: Thu, 22 Jul 2004 09:47:45 -0400 (EDT) From: Dan Langille X-X-Sender: dan@xeon.unixathome.org To: current@freebsd.org In-Reply-To: <20040722141237.O98018@mirrorball.theloosingend.net> Message-ID: <20040722094638.C34640@xeon.unixathome.org> References: <20040722141237.O98018@mirrorball.theloosingend.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: if_ndis/5.2.1/smc2602w-r3 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, 22 Jul 2004 13:47:47 -0000 On Thu, 22 Jul 2004, Svein Halvor Halvorsen wrote: > I tried asking on questions to no avail. So I'll try again here, since > this is -current code I'm tinkering with here. > > Copying > > src/sys/modules/if_ndis > src/sys/modules/ndis > src/sys/compat/ndis > src/sys/dev/if_ndis > > ... from a current source-tree to my 5.2.1-box, and compiling using a > ndis_driver_data.h made from the latest driver found on SMC's website > using a ndisctl on my current system, seems to work fine. > > kldload-ing ndis also seems to work. But when I kldload if_ndis, the > system freezes. No error messages, no response. A cold boot is the only > thing that seems to fix it. > > Is this supposed to work, or am I trying to do the impossible here? > Any hints would be appreciated. I don't have time to diagnose your procedure, but my notes are at http://www.freebsddiary.org/ibm-thinkpad-t41.php <== Scroll down to the section titled Project Evil. -- Dan Langille - http://www.langille.org/ From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 13: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 48ED116A4CE for ; Thu, 22 Jul 2004 13:55:27 +0000 (GMT) Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU [128.205.32.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF89543D1F for ; Thu, 22 Jul 2004 13:55:26 +0000 (GMT) (envelope-from kensmith@cse.Buffalo.EDU) Received: from electra.cse.Buffalo.EDU (kensmith@localhost [127.0.0.1]) i6MDtQTH019795; Thu, 22 Jul 2004 09:55:26 -0400 (EDT) Received: (from kensmith@localhost) by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id i6MDtQ1S019794; Thu, 22 Jul 2004 09:55:26 -0400 (EDT) Date: Thu, 22 Jul 2004 09:55:25 -0400 From: Ken Smith To: Garrett Wollman Message-ID: <20040722135525.GA19550@electra.cse.Buffalo.EDU> References: <40F963D8.6010201@freebsd.org> <20040719060730.GA87697@nagual.pp.ru> <20040720081051.GB3001@cirb503493.alcatel.com.au> <20040721151427.GC54664@atrbg11.informatik.tu-muenchen.de> <200407211622.i6LGMZrm040478@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200407211622.i6LGMZrm040478@khavrinen.lcs.mit.edu> User-Agent: Mutt/1.4.1i cc: current@freebsd.org cc: Daniel Lang Subject: Re: NEW TAR 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, 22 Jul 2004 13:55:27 -0000 On Wed, Jul 21, 2004 at 12:22:35PM -0400, Garrett Wollman wrote: > < said: > > > I do not see, why it is important if the original file was sparse > > at all or maybe in different places. > > You've never run out of disk space as a result of a sparse file > becoming non-sparse? > They also effect user quotas. The quota reflects actual disk block allocation, not file size. I've had users' home directories get copied and suddenly they're over quota (or the copy fails...) because of a few core files that became non-sparse... -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 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 6047D16A4CE; Thu, 22 Jul 2004 14:28:58 +0000 (GMT) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9C9843D5A; Thu, 22 Jul 2004 14:28:57 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87])i6MESt4u029345; Fri, 23 Jul 2004 00:28:55 +1000 Received: from epsplex.bde.org (katana.zip.com.au [61.8.7.246]) i6MESqnl011438; Fri, 23 Jul 2004 00:28:53 +1000 Date: Fri, 23 Jul 2004 00:28:52 +1000 (EST) From: Bruce Evans X-X-Sender: bde@epsplex.bde.org To: John Birrell In-Reply-To: <20040721215940.GK22160@freebsd3.cimlogic.com.au> Message-ID: <20040722225952.S1704@epsplex.bde.org> References: <20040721081310.GJ22160@freebsd3.cimlogic.com.au> <20040721220405.Y2346@epsplex.bde.org> <20040721215940.GK22160@freebsd3.cimlogic.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Brian Fundakowski Feldman cc: current@FreeBSD.org Subject: Re: nanosleep returning early 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, 22 Jul 2004 14:28:58 -0000 On Thu, 22 Jul 2004, John Birrell wrote: > On Wed, Jul 21, 2004 at 11:01:20PM +1000, Bruce Evans wrote: > > On Wed, 21 Jul 2004, Brian Fundakowski Feldman wrote: > > > On Wed, Jul 21, 2004 at 06:13:10PM +1000, John Birrell wrote: > > > > > > > > Today I increased HZ in a current kernel to 1000 when adding dummynet. > > > > Now I find that nanosleep regularly comes back a little early. > > > > Can anyone explain why? > > > > The most obvious bug is that nanosleep() uses the low-accuracy interface > > getnanouptime(). I can't see why the the problem is more obvious with > > large HZ or why it affects short sleeps. From kern_time.c 1.170: > > ... > > % getnanouptime(&ts); > > > > This may lag the actual (up)time by 1/HZ seconds. The inaccuracy of the "get" time functions is actually tc_tick/HZ seconds, where tc_tick is 1 for small values of HZ but is scaled to give an inaccuracy of 1 mS for large values of HZ or can be adjusted using sysctl to give almost any inaccuracy that you want. But this makes no difference until HZ exceeds 1000 or you use the sysctl. > For any NTP clock adjustment to have an effect, it must happen between > the time when my (crude) test gets the time and when the kernel calls > getnanouptime to fill ts. All the rest of the code in nanosleep1() > refers back to the value of ts. Any errors involved in the tv and hz > conversions would just cause the code to go around the loop and tsleep > more than once. ts is the uptime, so there is another window (larger) for NTP adjustments to have an affect: most of the sleep time. If ts were perfectly accurate or larger then the correct value, then the sleep interval (measured as the difference between uptimes) is sure to be large enough. However, the sleep interval measured as a difference between real times reported by gettimeofday() may be smaller because NTP adjusts the clocks differently, which it only does for stepping the time. > So, does increasing HZ expose the lower accuracy of getnanouptime() and is > that what I'm seeing? I still don't know the reason. Unfortunately, I deleted your original mail so I can't run the test program in it easily. > If so, shouldn't the time interface provided by the kernel to userland > at least be consistently inaccurate? Or put another way, why should > nanosleep be any less accurate than gettimeofday? I think it can't be consistent if the time is stepped (i.e., set using settimeofday() or clock_settime(CLOCK_REALTIME)). The real time is the best known approximation to the, er, real time, but most other times are for intervals. Having the most accurate times possible for intervals is inconsistent with having the most accurate times possible for real times if the real time is stepped. > Bruce, have you seen this document: ? > I'm not looking for a critique here. The document talks about the sleep > overruns in various operatingg systems. There is a patch that was applied > to DragonFly which aplies to the FreeBSD code base too. I just looked. It doesn't apply to FreeBSD. Adding 1 to the tick count in tvtohz() is necessary in many places in FreeBSD (e.g., for itimers). It happens to be just an optimizatiom in nanosleep1() for the reasons you mentioned above (going around again fixes any underestimate of the tick count, and overestimating by 1 avoids going around again in most cases). It's normal for simple test programs to take 2-epsilon ticks extra for nanosleep(), because they get in sync with clock interrupts. Returns from nanosleep() normally occur epsilon seconds after a clock interrupt. Then the kernel must wait until the next clock interrupt before returning from the next nanosleep() even if the sleep interval is 1 nsec (unless the kernel optimizes this operation and pessimizes others by busy-waiting or checking on other interrupts...). This gives a minimal sleep of 1-epsilon ticks. The FreeBSD implementation adds an extra tick to optimize the calculation of the minimal number of ticks. Without this, it would have use code like that in nanosleep1() after every sleep and itimer interrupt to check that the interval really has expired (underestimate the tick count a little to ensure not wasting an extra tick, at a cost of going around once more in the usual case). I believe dragonflybsd has high resolution timeouts which make the issues different. `tick' could be somthing like 10**6 and tick counts in microseconds would be so large that off by 1 errors in them would be too small to measure. Bruce From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 14:46: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 DE3B616A4CE for ; Thu, 22 Jul 2004 14:46:31 +0000 (GMT) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7364243D5C for ; Thu, 22 Jul 2004 14:46:31 +0000 (GMT) (envelope-from Jan.Grant@bristol.ac.uk) Received: from mail.ilrt.bris.ac.uk ([137.222.16.62]) by dirg.bris.ac.uk with esmtp (Exim 4.34) id 1Bnepy-0002Qd-JC; Thu, 22 Jul 2004 15:46:24 +0100 Received: from cmjg (helo=localhost) by mail.ilrt.bris.ac.uk with local-esmtp (Exim 4.34) id 1Bneon-00013e-6L; Thu, 22 Jul 2004 15:45:09 +0100 Date: Thu, 22 Jul 2004 15:45:09 +0100 (BST) From: Jan Grant X-X-Sender: cmjg@mail.ilrt.bris.ac.uk To: Ian FREISLICH In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: Jan Grant X-Spam-Score: 0.0 X-Spam-Level: / cc: SanD cc: current@freebsd.org Subject: Re: NEW TAR 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, 22 Jul 2004 14:46:32 -0000 On Thu, 22 Jul 2004, Ian FREISLICH wrote: > SanD wrote: >> Ian wrote: >>> How does dump handle sparse files? >> Dump handles fine sparse files. > > Maybe I should have asked how does dump figure out that the files > are sparse and if it's any more intelligent than a 2 pass read (I > have no idea why 2 passes are required) or just blindly turning > successive zeros into a seek offset, is there anything preventing > BSD tar from doing the same? Dump knows about the filesystem format; it talks that directly to the device. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/ Political talk? / What is said can be unsaid / with good old BS -- ASCII haiku From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 15:15: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 9CEF716A4CF for ; Thu, 22 Jul 2004 15:15:05 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 537E143D5A for ; Thu, 22 Jul 2004 15:15:05 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.0.12] (g4.samsco.home [192.168.0.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6MFLLaX067491 for ; Thu, 22 Jul 2004 09:21:22 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40FFD9B3.3040607@freebsd.org> Date: Thu, 22 Jul 2004 09:13:55 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "'current@freebsd.org'" Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-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 Subject: STABILITY [Fwd: cvs commit: src/sys/kern kern_switch.c] 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, 22 Jul 2004 15:15:05 -0000 All, This commit is another hack to try to improve stability some more. Please let me know if it helps or hurts. If it helps then I think that we are getting closer to at least one of the real culprits. Scott -------- Original Message -------- Subject: cvs commit: src/sys/kern kern_switch.c Date: Thu, 22 Jul 2004 14:32:48 +0000 (UTC) From: Scott Long To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org scottl 2004-07-22 14:32:48 UTC FreeBSD src repository Modified files: sys/kern kern_switch.c Log: Disable the PREEMPTION-enabled code in critical_exit() that encourages switching to a different thread. This is just a hack to try to improve stability some more, but likely points closer to the real culprit. Revision Changes Path 1.72 +2 -0 src/sys/kern/kern_switch.c From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 15:23: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 3387116A4CE for ; Thu, 22 Jul 2004 15:23:41 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.198]) by mx1.FreeBSD.org (Postfix) with SMTP id C8BA143D1F for ; Thu, 22 Jul 2004 15:23:40 +0000 (GMT) (envelope-from joseph.peterson@gmail.com) Received: by mproxy.gmail.com with SMTP id c3so41399rnb for ; Thu, 22 Jul 2004 08:23:40 -0700 (PDT) Received: by 10.38.209.75 with SMTP id h75mr160482rng; Thu, 22 Jul 2004 08:23:40 -0700 (PDT) Message-ID: <38a23c360407220823d412ca4@mail.gmail.com> Date: Thu, 22 Jul 2004 10:23:40 -0500 From: Joseph Peterson To: roklein@roklein.de In-Reply-To: <200407220746.55870.RoKlein@roklein.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> <200407220746.55870.RoKlein@roklein.de> cc: freebsd-current@freebsd.org Subject: Re: laptop for -current 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, 22 Jul 2004 15:23:41 -0000 Robert, I'm not sure if this is related to the problem that I had/have (and forgot about) with my Toshiba, but I've found that if Windows was run and I go to boot FreeBSD, I need to go into the BIOS and save it, no changes have to be made, just go into BIOS and save it. This is true of booting from the install CD for the first time, or (as is my case) dual booting back and forth, when I shut down Windows I have to go save the BIOS before FreeBSD will boot. -joe On Thu, 22 Jul 2004 07:46:55 +0200, Robert Klein wrote: > On Mittwoch, 21. Juli 2004 22:36, Kim Culhan wrote: > > Anyone know a laptop they think is good for FreeBSd-current? > > I have an Acer Travelmate 291LCI which doesn't boot. > Stable doesn't find the CD-ROM, all currents I tried had some > kinda panic during boot.. :( > > Robert > > > > _______________________________________________ > 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 Thu Jul 22 15:39:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 250C716A4CE; Thu, 22 Jul 2004 15:39:15 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.12.11/8.12.11) with ESMTP id i6MFdEiQ002469; Thu, 22 Jul 2004 11:39:14 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.12.11/8.12.11/Submit) id i6MFdE7B002468; Thu, 22 Jul 2004 11:39:14 -0400 (EDT) (envelope-from green) Date: Thu, 22 Jul 2004 11:39:13 -0400 From: Brian Fundakowski Feldman To: Scott Long Message-ID: <20040722153913.GA2312@green.homeunix.org> References: <40FFD9B3.3040607@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40FFD9B3.3040607@freebsd.org> User-Agent: Mutt/1.5.6i cc: "'current@freebsd.org'" Subject: INSTABILITY all around (Was: Re: STABILITY [Fwd: cvs commit: src/sys/kern kern_switch.c]) 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, 22 Jul 2004 15:39:15 -0000 On Thu, Jul 22, 2004 at 09:13:55AM -0600, Scott Long wrote: > All, > > This commit is another hack to try to improve stability some > more. Please let me know if it helps or hurts. If it helps > then I think that we are getting closer to at least one of the > real culprits. I am having VERY bad luck with -CURRENT now. As of a few weeks ago, the kernel was perfectly fine on UP and SMP i386. Now, I have had to switch PREEMPTION off on both to gain some stability back. Turning on debug.mpsafenet results in instareboots very quickly for my UP box, but with debug.mpsafenet is off then instareboots take more like a day to happen. On SMP, I haven't tried debug.mpsafenet, but now I'm getting a hang which is probably related to threading programs as it's when using a lot of KDE and Mozilla Firefox and such. Instareboots might be debuggable with serial console, as might hangs, if they are symptomatic of the actual panic() crashing or hanging. I'm not holding my breath; breaking into DDB+KDB from serial console whether in X or not causes the machine to just hang completely on SMP, haven't tried on UP. My machines are always using kern.sync_on_panic=0, net.inet.tcp.sack.enable=1, INVARIANTS, WITNESS, WITNESS_SKIPSPIN, and SCHED_ULE. Now I have debug.debugger_on_panic=1 and both hooked up to serial consoles. On SMP and on UP I have significant modifications to kqueue to make it mp-safe, which showed no evidence of instability hammering on them a month ago. On SMP I have UMA init/ctor-function error checking modifications which should almost never do anything, as I am not remotely running out of memory. On both I have also overhauled the VM wiring capabilities, and I have never tripped any of the many KASSERT()s that I added while doing that. I am willing to run specific stress tests to help pinpoint my issues, but I'm not even thinking it's worth bothering to reenable the PREEMPTION code when there are so many problems without it. It is of course possible that it's now broken in subtle ways to NOT use the PREEMPTION code, but I don't know much about this. I certainly hope DDB+KDB on panic works where DDB+KDB on break does not, or I'll probably get nowhere at all. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 15:47: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 20F5F16A4CE for ; Thu, 22 Jul 2004 15:47:52 +0000 (GMT) Received: from web60701.mail.yahoo.com (web60701.mail.yahoo.com [216.109.117.224]) by mx1.FreeBSD.org (Postfix) with SMTP id CD9C743D2D for ; Thu, 22 Jul 2004 15:47:51 +0000 (GMT) (envelope-from wtgee@yahoo.com) Message-ID: <20040722154749.12658.qmail@web60701.mail.yahoo.com> Received: from [166.70.22.172] by web60701.mail.yahoo.com via HTTP; Thu, 22 Jul 2004 08:47:49 PDT Date: Thu, 22 Jul 2004 08:47:49 -0700 (PDT) From: "W. Tyler Gee" To: freebsd-current@freebsd.org In-Reply-To: <20040722005042.C07E916A4ED@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: laptop for -current 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, 22 Jul 2004 15:47:52 -0000 I have a Gateway 400 series that works fine except for the thermal support when ACPI is running. I tried disabling just thermal but the fan still had a bunch of problems and I would overheat when compiling anything. With disabled ACPI everythings works like a charm. wtgee From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 16:20: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 818E716A4CF for ; Thu, 22 Jul 2004 16:20:59 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.204]) by mx1.FreeBSD.org (Postfix) with SMTP id 0180643D41 for ; Thu, 22 Jul 2004 16:20:59 +0000 (GMT) (envelope-from joseph.peterson@gmail.com) Received: by mproxy.gmail.com with SMTP id m68so39375rne for ; Thu, 22 Jul 2004 09:20:58 -0700 (PDT) Received: by 10.38.90.2 with SMTP id n2mr150545rnb; Thu, 22 Jul 2004 09:20:58 -0700 (PDT) Message-ID: <38a23c360407220920522e5415@mail.gmail.com> Date: Thu, 22 Jul 2004 11:20:58 -0500 From: Joseph Peterson To: anton@nikiforov.ru In-Reply-To: <40FFE1BC.40302@nikiforov.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> <200407220746.55870.RoKlein@roklein.de> <38a23c360407220823d412ca4@mail.gmail.com> <40FFE1BC.40302@nikiforov.ru> cc: freebsd-current@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: laptop for -current 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, 22 Jul 2004 16:20:59 -0000 Anton, A full power cycle was suggested to me, but that didn't work on my Toshiba A25 - and Windows is XP for me as well, I guess Microsoft is getting less well behaved as far as playing with others is concerned =) -joe On Thu, 22 Jul 2004 19:48:12 +0400, Anton Nikiforov wrote: > Joseph Peterson wrote: > > Robert, I'm not sure if this is related to the problem that I had/have > > (and forgot about) with my Toshiba, but I've found that if Windows was > > run and I go to boot FreeBSD, I need to go into the BIOS and save it, > > no changes have to be made, just go into BIOS and save it. This is > > true of booting from the install CD for the first time, or (as is my > > case) dual booting back and forth, when I shut down Windows I have to > > go save the BIOS before FreeBSD will boot. > > > > -joe > I have had the same problem with my Toshiba (tecra 8200) and Compaq > (Presario 2585), but in my case Windows was XP (with W2K it was OK) and > i did not run the BIOS, but just did full power sycle (turn off the > notebook not just reboot from windows) > > Anton > > > > > > On Thu, 22 Jul 2004 07:46:55 +0200, Robert Klein wrote: > > > >>On Mittwoch, 21. Juli 2004 22:36, Kim Culhan wrote: > >> > >>>Anyone know a laptop they think is good for FreeBSd-current? > >> > >>I have an Acer Travelmate 291LCI which doesn't boot. > >>Stable doesn't find the CD-ROM, all currents I tried had some > >>kinda panic during boot.. :( > >> > >>Robert > >> > >> > >> > >>_______________________________________________ > >>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 Thu Jul 22 16:25: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 E905316A4CE; Thu, 22 Jul 2004 16:25:21 +0000 (GMT) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FC7843D31; Thu, 22 Jul 2004 16:25:21 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86])i6MGPJje027923; Fri, 23 Jul 2004 02:25:19 +1000 Received: from epsplex.bde.org (katana.zip.com.au [61.8.7.246]) i6MGPHn4011667; Fri, 23 Jul 2004 02:25:18 +1000 Date: Fri, 23 Jul 2004 02:25:16 +1000 (EST) From: Bruce Evans X-X-Sender: bde@epsplex.bde.org To: John Birrell In-Reply-To: <20040722225952.S1704@epsplex.bde.org> Message-ID: <20040723014517.B2451@epsplex.bde.org> References: <20040721081310.GJ22160@freebsd3.cimlogic.com.au> <20040721215940.GK22160@freebsd3.cimlogic.com.au> <20040722225952.S1704@epsplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: nanosleep returning early 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, 22 Jul 2004 16:25:22 -0000 On Fri, 23 Jul 2004, Bruce Evans wrote: > On Thu, 22 Jul 2004, John Birrell wrote: > > > On Wed, Jul 21, 2004 at 11:01:20PM +1000, Bruce Evans wrote: > > > ... > > > The most obvious bug is that nanosleep() uses the low-accuracy interface > > > getnanouptime(). I can't see why the the problem is more obvious with > > > large HZ or why it affects short sleeps. From kern_time.c 1.170: > > > ... > > > % getnanouptime(&ts); > > > > > > This may lag the actual (up)time by 1/HZ seconds. > > [ (actually tc_tick/HZ seconds) > > So, does increasing HZ expose the lower accuracy of getnanouptime() and is > > that what I'm seeing? > > I still don't know the reason. Unfortunately, I deleted your original > mail so I can't run the test program in it easily. Now I think I know the reason. The interval between clock interrupts is supposed to be 1/HZ seconds = `tick' microseconds, but it cannot be set nearly that precisely, and the imprecision of inversely proportional to HZ. The i8254 counter has a default nominal frequency of 1193182 Hz. Suppose that this is perfectly accurate. Then to implement clock interrupts at HZ hz, we want to program the i8254's maximum count to 1193182/HZ in infinite precision, but counts must be integers so we must round. The loss of precision is quite large for HZ = 1000: 1193182 / 1000.0 = 1193.182; rounding this (to nearest) gives 1193 and an error of 182 in 1193182 = 152 ppm. Also, the extra tick added by tvtohz() is only 1000 uS long, so it only has a chance of about 152/1000 to compensate for the rounding error. Finally, the explicit check that the interval has elapsed cannot compensate for errors larger than tc_tick/HZ because getnanouptime() is fuzzy. Rounding 1193.182 to nearest happens to round down; thus clock ticks are shorter than `tick' microseconds, tvtohz()'s value is too small, and nanosleep() may return too early. The loop limits the error to about 1 tick in this case. The i8254 frequency may be calibrated or set using sysctl to a more (or less) accurate value. Then the rounding may go the other way so that tvtohz()'s value is too large and nanoleep() may return too late. The loop cannot limit the error in this case. The absolute error may be large for long sleeps. E.g., 152 ppm over 1 day is 13 seconds. tvtohz()'s value may also be too large because the i8254 frequency is not known accurately. It's nominal value is wrong by 10-100 Hz on my systems. I minimize errors from this by calibrating all timecounters using a common clock. Bruce From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 17:08: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 6C95316A4CE for ; Thu, 22 Jul 2004 17:08:57 +0000 (GMT) Received: from fornax.vsecurity.com (64-144-2-149.client.dsl.net [64.144.2.149]) by mx1.FreeBSD.org (Postfix) with SMTP id 8582243D1F for ; Thu, 22 Jul 2004 17:08:56 +0000 (GMT) (envelope-from ggal@vsecurity.com) Received: (qmail 16288 invoked from network); 22 Jul 2004 17:12:09 -0000 Received: from unknown (HELO CINDY) (127.0.0.1) by 0 with SMTP; 22 Jul 2004 17:12:09 -0000 Message-ID: <001401c4700e$91b5a470$5001a8c0@CINDY> From: "George D. Gal" To: Date: Thu, 22 Jul 2004 13:08:53 -0400 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: radeon drm code in -current 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, 22 Jul 2004 17:08:57 -0000 Hello I'm wondering if anyone else has experienced problems with the radeon drm driver in -current. It seems that sometime between Jun 22 and the latest -current, I have problems with the radeon drm/dri drivers loading when XFree starts up. The error I get when starting XFree now is: [drm] failed to load kernel module "radeon" (II) RADEON(0): [drm] drmOpen failed (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI. I haven't changed anything in my XF86Config. My hardware is a Dell D600 with the Radeon 9000 video card Regards, George From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 17:26: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 B20E916A4CE for ; Thu, 22 Jul 2004 17:26:26 +0000 (GMT) Received: from psg.com (psg.com [147.28.0.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id A399843D49 for ; Thu, 22 Jul 2004 17:26:26 +0000 (GMT) (envelope-from randy@psg.com) Received: from [127.0.0.1] (helo=roam.psg.com) by psg.com with esmtp (Exim 4.34 (FreeBSD)) id 1BnhKs-0000Fw-AB for freebsd-current@freebsd.org; Thu, 22 Jul 2004 17:26:26 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com.psg.com) by roam.psg.com with esmtp (Exim 4.40 (FreeBSD)) id 1BnhKr-00038S-KB for freebsd-current@freebsd.org; Thu, 22 Jul 2004 07:26:25 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16639.63680.703707.557180@roam.psg.com> Date: Thu, 22 Jul 2004 07:26:24 -1000 To: FreeBSD Current Subject: ath0 associaiton 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: Thu, 22 Jul 2004 17:26:26 -0000 on my freebsd very current thinkpad t40p, every few minutes the ath0 drops out and then, after a few seconds, recovers. the log message is ath0: association failed (reason 1) for 00:0f:66:04:c0:2f my partner, running xp on the same model laptop, against the same base station, sees no similar problems. clues and/or debugging hints sought randy From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 17: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 278D316A4CE for ; Thu, 22 Jul 2004 17:30:31 +0000 (GMT) Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id E698343D3F for ; Thu, 22 Jul 2004 17:30:30 +0000 (GMT) (envelope-from robin.blanchard@gactr.uga.edu) Received: from localhost (unknown [127.0.0.1]) by mail.gactr.uga.edu (Postfix) with ESMTP id 72A05B2451 for ; Thu, 22 Jul 2004 13:30:29 -0400 (EDT) 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 18110-02-2 for ; Thu, 22 Jul 2004 13:30:27 -0400 (EDT) Received: from EBE1.gc.nat (E2K1.gc.nat [10.10.11.21]) by mail.gactr.uga.edu (Postfix) with ESMTP id 0B082B243F for ; Thu, 22 Jul 2004 13:30:27 -0400 (EDT) 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: Thu, 22 Jul 2004 13:30:27 -0400 Message-ID: <9B5C1FCAFB35084787C21EFFFA78DD9EE481@EBE1.gc.nat> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Ntp 4.2.0 Thread-Index: AcRwEZPySXHrAxijSU6nWIxW0GX6eA== From: "Robin P. Blanchard" To: X-Virus-Scanned: by amavisd-new at gactr.uga.edu Subject: Ntp 4.2.0 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, 22 Jul 2004 17:30:31 -0000 Since the ntp update, I'm seeing this: Jul 22 13:27:28 bsdfs5 ntpd[466]: ntpd 4.2.0-a Thu Jul 22 09:47:08 EDT = 2004 (1) Jul 22 13:27:28 bsdfs5 ntpd[466]: mlockall(): Resource temporarily unavailable Jul 22 13:27:28 bsdfs5 kernel: obreak: MAP_WIREFUTURE set What do these message mean ?=20 --------------------------------------- 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 Thu Jul 22 18:01: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 8C1A916A4CE for ; Thu, 22 Jul 2004 18:01:34 +0000 (GMT) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45ABE43D54 for ; Thu, 22 Jul 2004 18:01:34 +0000 (GMT) (envelope-from johnmary@adelphia.net) Received: from 68-169-191-150.losaca.adelphia.net ([68.169.191.150]) by mta9.adelphia.netESMTP <20040722180133.TMWH2023.mta9.adelphia.net@68-169-191-150.losaca.adelphia.net>; Thu, 22 Jul 2004 14:01:33 -0400 Received: by 68-169-191-150.losaca.adelphia.net (Postfix, from userid 1001) id 3E3DB6C3E; Thu, 22 Jul 2004 11:01:33 -0700 (PDT) From: John Merryweather Cooper To: "George D. Gal" In-Reply-To: <001401c4700e$91b5a470$5001a8c0@CINDY> References: <001401c4700e$91b5a470$5001a8c0@CINDY> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-5aVN06poyEephA0+tmGl" Message-Id: <1090519292.35023.15.camel@68-169-191-150.losaca.adelphia.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 22 Jul 2004 11:01:32 -0700 cc: freebsd-current@FreeBSD.org Subject: Re: radeon drm code in -current 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, 22 Jul 2004 18:01:34 -0000 --=-5aVN06poyEephA0+tmGl Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2004-07-22 at 10:08, George D. Gal wrote: > Hello I'm wondering if anyone else has experienced problems with the rade= on > drm driver in -current. It seems that sometime between Jun 22 and the > latest -current, I have problems with the radeon drm/dri drivers loading = when > XFree starts up. >=20 > The error I get when starting XFree now is: >=20 > [drm] failed to load kernel module "radeon" (II) RADEON(0): [drm] drmOpe= n > failed > (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI. >=20 > I haven't changed anything in my XF86Config. >=20 > My hardware is a Dell D600 with the Radeon 9000 video card >=20 > Regards, > George >=20 I've had problems, but not quite like yours. This may be a function of the different adapter (I have a Radeon 7000/VE). I can't run with DRI enabled in XF86Config since about the dates you have mentioned. If I load the DRI module in XF86Config and start X, my machine hard locks shortly after the second icon in the Gnome 2.x startup sequence displays. Thinking that this might be Gnome-specific, I started up with KDE 3.x instead, but it locks up also early in it's startup. I can avoid all this by disabling DRI in XF86Config--but it used to work before mid-June some time. jmc --=-5aVN06poyEephA0+tmGl Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBBAAD7vBSBfjNhsrIRArh5AJ9bLiMEdfBXXh522CgQScoIS1VWRQCePDEC NisNuTJEYsTC06FpjiHxADY= =+kUs -----END PGP SIGNATURE----- --=-5aVN06poyEephA0+tmGl-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 18:09: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 3B44316A4CE for ; Thu, 22 Jul 2004 18:09:53 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.berkeley.edu [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA70D43D1F for ; Thu, 22 Jul 2004 18:09:52 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id i6MI9qT10677 for freebsd-current@freebsd.org; Thu, 22 Jul 2004 11:09:52 -0700 (PDT) Date: Thu, 22 Jul 2004 11:09:52 -0700 From: Mike Hunter To: freebsd-current@freebsd.org Message-ID: <20040722180952.GA10004@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: stray irq9, nvidia binary driver lock weirdness 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, 22 Jul 2004 18:09:53 -0000 Hi, Just thought I'd state for the group that I now see "stray irq9" right before my Dell D800 laptop reboots or shuts down. (I have version A9 of my bios IIRC, and I'm using a custom /boot/DSDT.aml.) Let me know if I can do anything to help debug the problem. I also see (and have been seeing) the following weirdness from the nvidia driver; should I assume this is just caused by that driver not being updated? I must use the nvidia binary driver to use an external monitor. There's no problem with the driver (although it used to freeze the box solid if I tried to use xlock's openGL modes.) This is current from Wednesday, June 21, 2004. Mike malloc(M_WAITOK) of "32", forcing M_NOWAIT with the following non-sleepable locks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc1a50a7c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 KDB: stack backtrace: kdb_backtrace(1,20,c1044540,1,d65727f0) at kdb_backtrace+0x29 witness_warn(5,0,c07d9bf1,c07ad754) at witness_warn+0x18e uma_zalloc_arg(c1044540,0,102) at uma_zalloc_arg+0x38 malloc(14,c0b32ba0,102,0,1) at malloc+0xae nv_alloc_pages(c1a7d700,d6572958,1,0,0) at nv_alloc_pages+0xad __nvsym00191(c2153000,d6572958,1,0,0) at __nvsym00191+0x68 __nvsym00183(c2153000,c1d00011,d6572958,d657295c,d6572904) at __nvsym00183+0x124 __nvsym00195(c1d00011,31415929,31415932,3e,1010) at __nvsym00195+0xc0 __nvsym00714(c2153000,6,0,c08a9138,c1a7d700) at __nvsym00714+0x11d __nvsym00702(c1a7d700,c0b1bb1b,2f1,c1a50a00,c1a7d700) at __nvsym00702+0x172 rm_init_adapter(c1a7d700,c1a50a00,c1a7d700,d6572a00,c0b0483e) at rm_init_adapter+0x11 nvidia_open_dev(c1a50a00,c1a7d700,3,c214f210,d6572a48) at nvidia_open_dev+0x17 nvidia_dev_open(c087dea8,3,2000,c1de3000,d6572a34) at nvidia_dev_open+0x36 spec_open(d6572a6c,d6572b28,c063b86c,d6572a6c,180) at spec_open+0x2a2 spec_vnoperate(d6572a6c) at spec_vnoperate+0x13 vn_open_cred(d6572be4,d6572ce4,ed,c2049300,7) at vn_open_cred+0x3c0 vn_open(d6572be4,d6572ce4,ed,7,c087fd80) at vn_open+0x1e kern_open(c1de3000,83f9a64,0,3,ff) at kern_open+0xd8 open(c1de3000,d6572d14,3,1d,3246) at open+0x18 syscall(2f,2f,2f,bfbfeb81,83f9a64) at syscall+0x217 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (5, FreeBSD ELF32, open), eip = 0x28262a9b, esp = 0xbfbfeacc, ebp = 0xbfbfeae8 --- malloc(M_WAITOK) of "32", forcing M_NOWAIT with the following non-sleepable locks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc1a50a7c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 KDB: stack backtrace: kdb_backtrace(1,20,c1044540,1,d65727c4) at kdb_backtrace+0x29 witness_warn(5,0,c07d9bf1,c07ad754) at witness_warn+0x18e uma_zalloc_arg(c1044540,0,102) at uma_zalloc_arg+0x38 malloc(14,c0b32ba0,102,1000,1) at malloc+0xae nv_alloc_system_pages(c1a7d700,d6572958,1,0,1) at nv_alloc_system_pages+0x2c nv_alloc_pages(c1a7d700,d6572958,1,0,0) at nv_alloc_pages+0xf6 __nvsym00191(c2153000,d6572958,1,0,0) at __nvsym00191+0x68 __nvsym00183(c2153000,c1d00011,d6572958,d657295c,d6572904) at __nvsym00183+0x124 __nvsym00195(c1d00011,31415929,31415932,3e,1010) at __nvsym00195+0xc0 __nvsym00714(c2153000,6,0,c08a9138,c1a7d700) at __nvsym00714+0x11d __nvsym00702(c1a7d700,c0b1bb1b,2f1,c1a50a00,c1a7d700) at __nvsym00702+0x172 rm_init_adapter(c1a7d700,c1a50a00,c1a7d700,d6572a00,c0b0483e) at rm_init_adapter+0x11 nvidia_open_dev(c1a50a00,c1a7d700,3,c214f210,d6572a48) at nvidia_open_dev+0x17 nvidia_dev_open(c087dea8,3,2000,c1de3000,d6572a34) at nvidia_dev_open+0x36 spec_open(d6572a6c,d6572b28,c063b86c,d6572a6c,180) at spec_open+0x2a2 spec_vnoperate(d6572a6c) at spec_vnoperate+0x13 vn_open_cred(d6572be4,d6572ce4,ed,c2049300,7) at vn_open_cred+0x3c0 vn_open(d6572be4,d6572ce4,ed,7,c087fd80) at vn_open+0x1e kern_open(c1de3000,83f9a64,0,3,ff) at kern_open+0xd8 open(c1de3000,d6572d14,3,1d,3246) at open+0x18 syscall(2f,2f,2f,bfbfeb81,83f9a64) at syscall+0x217 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (5, FreeBSD ELF32, open), eip = 0x28262a9b, esp = 0xbfbfeacc, ebp = 0xbfbfeae8 --- ... From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 18:44: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 C1C1316A4CE for ; Thu, 22 Jul 2004 18:44:39 +0000 (GMT) Received: from smtp06.web.de (smtp06.web.de [217.72.192.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F3F743D3F for ; Thu, 22 Jul 2004 18:44:39 +0000 (GMT) (envelope-from nakal@web.de) Received: from [84.135.203.107] (helo=[84.135.203.107]) by smtp06.web.de with esmtp (TLSv1:DES-CBC3-SHA:168) (WEB.DE 4.101 #44) id 1BniY5-00077C-00; Thu, 22 Jul 2004 20:44:09 +0200 From: Martin To: John Merryweather Cooper In-Reply-To: <1090519292.35023.15.camel@68-169-191-150.losaca.adelphia.net> References: <001401c4700e$91b5a470$5001a8c0@CINDY> <1090519292.35023.15.camel@68-169-191-150.losaca.adelphia.net> Content-Type: text/plain Message-Id: <1090521831.34181.34.camel@klotz.local> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 22 Jul 2004 20:44:03 +0200 Content-Transfer-Encoding: 7bit Sender: nakal@web.de X-Sender: nakal@web.de cc: FreeBSD Current cc: "George D. Gal" Subject: Re: radeon drm code in -current 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, 22 Jul 2004 18:44:39 -0000 Am Do, den 22.07.2004 schrieb John Merryweather Cooper um 20:01: > If I > load the DRI module in XF86Config and start X, my machine hard locks > shortly after the second icon in the Gnome 2.x startup sequence > displays. Thinking that this might be Gnome-specific, I started up with > KDE 3.x instead, but it locks up also early in it's startup. I can > avoid all this by disabling DRI in XF86Config--but it used to work > before mid-June some time. I have a similar effect, but I can load DRI and it works fine, when I don't load the glx extension. With glx extension, it does not lock-up the system, it only drives it to 100% load. I can still login using ssh and reboot in this case. Can you check, if this is the same bug? Or is it really a hard lock-up? (Radeon Mobility 7500, Thinkpad R40) Martin From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 18:47: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 5BCAD16A4D0 for ; Thu, 22 Jul 2004 18:47:05 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BF1143D46 for ; Thu, 22 Jul 2004 18:47:05 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 2DAD072DF4; Thu, 22 Jul 2004 11:47:05 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 2B0BA72DF2; Thu, 22 Jul 2004 11:47:05 -0700 (PDT) Date: Thu, 22 Jul 2004 11:47:05 -0700 (PDT) From: Doug White To: Willem Jan Withagen In-Reply-To: <01ea01c46fc8$6d1f32c0$471b3dd4@digiware.nl> Message-ID: <20040722114523.C92369@carver.gumbysoft.com> References: <021001c46e97$84c05210$471b3dd4@digiware.nl> <01ea01c46fc8$6d1f32c0$471b3dd4@digiware.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@FreeBSD.ORG Subject: Re: Erros in: make -j 16 buildword 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, 22 Jul 2004 18:47:05 -0000 On Thu, 22 Jul 2004, Willem Jan Withagen wrote: > From: "Doug White" > > On Tue, 20 Jul 2004, Willem Jan Withagen wrote: > > > > > Hi, > > > > > > One way or another it seems that I can no longer buildworld with -j16. > > > -j8 works perfectly, but -j16 fails consistently at: > > [...] > > > > > > Unless anybody has suggestions of which programs generate these tearse > > > messages??? > > > Or a way to get make to be more informative??? > > > > You need to capture the entire output since the error is buried in there. > > Make doesn't abort -j builds until all the subprocesses are finished, and > > they can run for a long time... > > You know how long the output of a buildworld is, right?? > When the errors are reported, visually it is at the point where it normally > looks like it is done. Its not that bad. There's a large number of people that log their builds, and besides, diskspace is cheap! > Building ports gives you notice of the directory in which it started to come up > from thus telling you which package was in error..... Port builds aren't done in parallel. The error was printed at the point of the error, but it doesn't cause all the other subprocesses to be killed immediately, so they run to completion. > Maybe I'll see if I can put something like this in make of the makefiles.... Good luck... -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 18:57: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 D399016A4CE for ; Thu, 22 Jul 2004 18:57:50 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6A3743D39 for ; Thu, 22 Jul 2004 18:57:50 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 92EF672DF2; Thu, 22 Jul 2004 11:57:50 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 8E0B572DB5; Thu, 22 Jul 2004 11:57:50 -0700 (PDT) Date: Thu, 22 Jul 2004 11:57:50 -0700 (PDT) From: Doug White To: "Robin P. Blanchard" In-Reply-To: <9B5C1FCAFB35084787C21EFFFA78DD9EE481@EBE1.gc.nat> Message-ID: <20040722115631.B92369@carver.gumbysoft.com> References: <9B5C1FCAFB35084787C21EFFFA78DD9EE481@EBE1.gc.nat> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@FreeBSD.org Subject: Re: Ntp 4.2.0 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, 22 Jul 2004 18:57:50 -0000 On Thu, 22 Jul 2004, Robin P. Blanchard wrote: > Since the ntp update, I'm seeing this: > > Jul 22 13:27:28 bsdfs5 ntpd[466]: ntpd 4.2.0-a Thu Jul 22 09:47:08 EDT 2004 > (1) > Jul 22 13:27:28 bsdfs5 ntpd[466]: mlockall(): Resource temporarily > unavailable This is ntpd trying to lock all its pages in memory to keep it from getting swapped out, which tends to mess up its timings. Its harmless but it'd be nice to have the log entry pushed down to debug status. > Jul 22 13:27:28 bsdfs5 kernel: obreak: MAP_WIREFUTURE set I suspect this is related but I didn't get it on my -current boxes at work. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 19:05: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 3841A16A4CE for ; Thu, 22 Jul 2004 19:05:21 +0000 (GMT) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6C5943D2F for ; Thu, 22 Jul 2004 19:05:20 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from [207.41.94.233] (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id i6MJ4EH5030430; Thu, 22 Jul 2004 12:04:15 -0700 From: Kent Stewart To: freebsd-current@freebsd.org Date: Thu, 22 Jul 2004 12:05:18 -0700 User-Agent: KMail/1.6.2 References: <021001c46e97$84c05210$471b3dd4@digiware.nl> <01ea01c46fc8$6d1f32c0$471b3dd4@digiware.nl> <20040722114523.C92369@carver.gumbysoft.com> In-Reply-To: <20040722114523.C92369@carver.gumbysoft.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407221205.18540.kstewart@owt.com> Subject: Re: Erros in: make -j 16 buildword 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, 22 Jul 2004 19:05:21 -0000 On Thursday 22 July 2004 11:47 am, Doug White wrote: > On Thu, 22 Jul 2004, Willem Jan Withagen wrote: > > From: "Doug White" > > > > > On Tue, 20 Jul 2004, Willem Jan Withagen wrote: > > > > Hi, > > > > > > > > One way or another it seems that I can no longer buildworld > > > > with -j16. -j8 works perfectly, but -j16 fails consistently at: > > > > > > [...] > > > > > > > Unless anybody has suggestions of which programs generate these > > > > tearse messages??? > > > > Or a way to get make to be more informative??? > > > > > > You need to capture the entire output since the error is buried > > > in there. Make doesn't abort -j builds until all the subprocesses > > > are finished, and they can run for a long time... > > > > You know how long the output of a buildworld is, right?? > > When the errors are reported, visually it is at the point where it > > normally looks like it is done. > > Its not that bad. There's a large number of people that log their > builds, and besides, diskspace is cheap! I am one of these people. I figure that if you don't log, then you must think your time isn't worth anything because you have to rerun it to log the problem. I created a directory called /var/log/build to hold the logs. I don't have any MP systems and -j* was always slower than no -j. With a no -j log, you don't have to rerun the build to find the problem. I never seem to have enough of "me-time" but the system doesn't care what it does :). Kent > > > Building ports gives you notice of the directory in which it > > started to come up from thus telling you which package was in > > error..... > > Port builds aren't done in parallel. The error was printed at the > point of the error, but it doesn't cause all the other subprocesses > to be killed immediately, so they run to completion. > > > Maybe I'll see if I can put something like this in make of the > > makefiles.... > > Good luck... -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 19:32: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 4A0F616A4CE; Thu, 22 Jul 2004 19:32:23 +0000 (GMT) Received: from mail024.syd.optusnet.com.au (mail024.syd.optusnet.com.au [211.29.132.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F5A243D1F; Thu, 22 Jul 2004 19:32:22 +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]) i6MJWG810936; Fri, 23 Jul 2004 05:32:16 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])i6MJWDVd010313; Fri, 23 Jul 2004 05:32:15 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)i6MJWDYU010312; Fri, 23 Jul 2004 05:32:13 +1000 (EST) (envelope-from pjeremy) Date: Fri, 23 Jul 2004 05:32:13 +1000 From: Peter Jeremy To: Mark Santcroos Message-ID: <20040722193213.GJ3001@cirb503493.alcatel.com.au> References: <40FE8F81.7040409@freebsd.org> <20040722130601.GA2751@laptop.6bone.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040722130601.GA2751@laptop.6bone.nl> User-Agent: Mutt/1.4.2i cc: "freebsd -current@" cc: Robert Watson Subject: Re: vmnet.ko missing - but it's there! - vmware and crashes 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, 22 Jul 2004 19:32:23 -0000 On Thu, 2004-Jul-22 15:06:01 +0200, Mark Santcroos wrote: >IMHO the most important point to reach is that it can't happen anymore that >we load an out-of-sync vmware module at boot time and panic. It should either >be correctly rebuild or not installed at all (and removed). The nicest way to do this would be to add versioning to the kld interface but this isn't practical (there was a thread about this some time ago). There are two other fairly easy approaches to this: 1) Change installkernel so that it does mv /boot/kernel /boot/kernel.old instead of something like cp -p /boot/kernel/* /boot/kernel.old 2) Add a check for old files in /boot/kernel at the end of installkernel and generate a banner message "The following modules are out of date..." -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 20:03: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 4C78E16A4CE for ; Thu, 22 Jul 2004 20:03:05 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.246]) by mx1.FreeBSD.org (Postfix) with SMTP id 2CFE943D41 for ; Thu, 22 Jul 2004 20:03:05 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by mproxy.gmail.com with SMTP id u22so21280cwc for ; Thu, 22 Jul 2004 13:03:01 -0700 (PDT) Received: by 10.11.100.20 with SMTP id x20mr49034cwb; Thu, 22 Jul 2004 13:03:01 -0700 (PDT) Message-ID: <790a9fff040722130326edaed7@mail.gmail.com> Date: Thu, 22 Jul 2004 15:03:01 -0500 From: Scot Hetzel To: Peter Jeremy In-Reply-To: <20040722193213.GJ3001@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <40FE8F81.7040409@freebsd.org> <20040722193213.GJ3001@cirb503493.alcatel.com.au> cc: "freebsd -current@" cc: Robert Watson Subject: Re: vmnet.ko missing - but it's there! - vmware and crashes 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, 22 Jul 2004 20:03:05 -0000 On Fri, 23 Jul 2004 05:32:13 +1000, Peter Jeremy wrote: > On Thu, 2004-Jul-22 15:06:01 +0200, Mark Santcroos wrote: > >IMHO the most important point to reach is that it can't happen anymore that > >we load an out-of-sync vmware module at boot time and panic. It should either > >be correctly rebuild or not installed at all (and removed). > > The nicest way to do this would be to add versioning to the kld interface > but this isn't practical (there was a thread about this some time ago). > There are two other fairly easy approaches to this: > 1) Change installkernel so that it does > mv /boot/kernel /boot/kernel.old > instead of something like > cp -p /boot/kernel/* /boot/kernel.old > 2) Add a check for old files in /boot/kernel at the end of installkernel > and generate a banner message "The following modules are out of date..." > Except that won't work for modules installed by ports. These modules are not installed into a standard location. Some are installed into ${PREFIX}/modules, ${PREFIX}/lib/, /modules, /boot/modules. What should happen is that all modules installed by ports/packages should install into a common location. Then the installkernel target could show out of date port/package modules. Scot From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 20:04: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 0E40C16A4CE for ; Thu, 22 Jul 2004 20:04:41 +0000 (GMT) Received: from mail.evip.pl (mail.evip.com.pl [212.244.157.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0575443D54 for ; Thu, 22 Jul 2004 20:04:40 +0000 (GMT) (envelope-from w@evip.pl) Received: from drwebc by mail.evip.pl with drweb-scanned (Exim 4.22) id 1Bnjnw-000A2H-Qz for current@freebsd.org; Thu, 22 Jul 2004 22:04:36 +0200 Received: from w by mail.evip.pl with local (Exim 4.22) id 1Bnjnw-000A2B-NX for current@freebsd.org; Thu, 22 Jul 2004 22:04:36 +0200 Date: Thu, 22 Jul 2004 22:04:36 +0200 From: Wiktor Niesiobedzki To: current@freebsd.org Message-ID: <20040722200436.GM8753@mail.evip.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: ALTQ and tun 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, 22 Jul 2004 20:04:41 -0000 Hi, Recently I configured my DSL link to use pf+ALTQ instead of ipfw+DUMMYNET, but I encountered following problem: - no single packet wents through the ALTQ I guess, that I miss something very trival, but for checkout: pf.conf: iext_if="tun0 int_if="dc0" altq on $ext_if priq queue {dc, ssh_interactive, ssh_bulk, other} queue dc priority 0 queue ssh_interactive priority 15 queue ssh_bulk priority 3 queue other priority 7 priq(default) pass out on $ext_if proto tcp from any to any port 22 tos 0x10 queue ssh_interactive label ssh_inter pass out log on $ext_if proto tcp from any to any port 22 tos 0x08 queue ssh_bulk label ssh_bulk pass out log on $ext_if proto tcp from any to any port 22 queue ssh_interactive label ssh_inter2 pass out log on $ext_if proto tcp from any to any user dctc queue dc label dc_transfer #pass out on $ext_if inet proto tcp from ($ext_if) port 61412 to any queue dc label dc_transfer_port pass out on $ext_if proto tcp from krz.mine.nu port 61412 to any label dc_transfer_port pass in log on $ext_if proto tcp from any to ($ext_if) port {22,80,113,61412} label pass_in_tcp pass in log on $ext_if proto udp from any to ($ext_if) port 61412 label pass_in_udp pass in on $ext_if proto tcp from any to any port 4662 label pass_in_mule queue dc pass in on $ext_if proto udp from any to any port 4672 label pass_in_kad queue dc pass out log on $ext_if proto { tcp, udp } all keep state label pass_out_all queue other pass out on $ext_if inet proto icmp all icmp-type {0,1,3,4,8,11,12} keep state pass in on $int_if all label pass_in_internal pass out on $int_if all label pass_out_internal queue other And for example: # pfctl -v -s rule [...] pass out log on tun0 proto tcp all keep state label "pass_out_all" queue other [ Evaluations: 25193 Packets: 855303 Bytes: 645597787 States: 13 ] pass out log on tun0 proto udp all keep state label "pass_out_all" queue other [ Evaluations: 3023 Packets: 10152 Bytes: 1222129 States: 2 ] [...] # pfctl -v -s queue queue dc priority 0 [ pkts: 0 bytes: 0 dropped pkts: 0 bytes: 0 ] [ qlength: 0/ 50 ] queue ssh_interactive priority 15 [ pkts: 0 bytes: 0 dropped pkts: 0 bytes: 0 ] [ qlength: 0/ 50 ] queue ssh_bulk priority 3 [ pkts: 0 bytes: 0 dropped pkts: 0 bytes: 0 ] [ qlength: 0/ 50 ] queue other priority 7 priq( default ) [ pkts: 0 bytes: 0 dropped pkts: 0 bytes: 0 ] [ qlength: 0/ 50 ] Nothing. Just like ALTQ was not enabled, but then, how to enable it? Can someone point me out, what I am missing in my configuration? Cheers, Wiktor Niesiobedzki From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 20:05: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 7C93516A4CE for ; Thu, 22 Jul 2004 20:05:36 +0000 (GMT) Received: from md1.swissinfo.org (md1.swissinfo.org [146.159.4.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id E404143D48 for ; Thu, 22 Jul 2004 20:05:35 +0000 (GMT) (envelope-from alecs@swissinfo.org) Received: from mail.swissinfo.org ([194.6.181.33]) by md1.swissinfo.org (md1.swissinfo.org [146.159.6.9]) (MDaemon.PRO.v7.1.1.R) with ESMTP id md50001751398.msg for ; Thu, 22 Jul 2004 22:05:29 +0200 Received: from localhost (210.77.10.198) by mail.swissinfo.org (7.0.020) (authenticated as alecs) id 3F585D660240F463 for freebsd-current@freebsd.org; Thu, 22 Jul 2004 22:05:26 +0200 Date: Fri, 23 Jul 2004 04:06:00 +0800 From: Alecs King To: freebsd-current@freebsd.org Message-ID: <20040722200600.GA1158@localhost> 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 X-Spam-Processed: md1.swissinfo.org, Thu, 22 Jul 2004 22:05:29 +0200 (not processed: message from valid local sender) X-MDRemoteIP: 194.6.181.33 X-Return-Path: alecs@swissinfo.org X-MDaemon-Deliver-To: freebsd-current@freebsd.org X-MDAV-Processed: md1.swissinfo.org, Thu, 22 Jul 2004 22:05:35 +0200 Subject: Sound issue on -current 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, 22 Jul 2004 20:05:36 -0000 Onboard nForce2 audio (Realtek ALC650 AC97Codec). I used to use 'device pcm' without problem. Just cvsup'ed the source and found that -current is now using a new 'sound/snd_*' scheme. I checked the NOTES but couldnt find any snd_* for my case. So i tried just using 'device sound' without any 'device snd_*' but failed. Is there anything i missed? Which snd_* should i use? Any suggestions? TIA. -- Alecs King From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 20:16: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 24C5F16A4CE for ; Thu, 22 Jul 2004 20:16:40 +0000 (GMT) Received: from cpanel.ezone.ru (cpanel.ezone.ru [213.85.31.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id C87BD43D4C for ; Thu, 22 Jul 2004 20:16:38 +0000 (GMT) (envelope-from mcsi@mcsi.pp.ru) Received: from [83.237.28.243] (ppp83-237-28-243.pppoe.mtu-net.ru [83.237.28.243]) (authenticated bits=0) by cpanel.ezone.ru (8.13.0/8.12.11) with ESMTP id i6MKGPki089964; Fri, 23 Jul 2004 00:16:31 +0400 (MSD) (envelope-from mcsi@mcsi.pp.ru) Message-ID: <41002094.8010108@mcsi.pp.ru> Date: Fri, 23 Jul 2004 00:16:20 +0400 From: Maxim Maximov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.1) Gecko/20040720 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: Alecs King References: <20040722200600.GA1158@localhost> In-Reply-To: <20040722200600.GA1158@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mail3.ezone.ru cc: freebsd-current@freebsd.org Subject: Re: Sound issue on -current 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, 22 Jul 2004 20:16:40 -0000 Alecs King wrote: > Onboard nForce2 audio (Realtek ALC650 AC97Codec). I used to use 'device > pcm' without problem. > > Just cvsup'ed the source and found that -current is now using a new > 'sound/snd_*' scheme. I checked the NOTES but couldnt find any snd_* > for my case. So i tried just using 'device sound' without any > 'device snd_*' but failed. > > Is there anything i missed? Which snd_* should i use? Any suggestions? In /boot/loader.conf: sound_load="YES" snd_driver_load="YES" should help you. Second line will load all available drivers. When you'll find out which one is yours, change that string to load appropriate driver. References: sys/conf/NOTES /boot/defaults/loader.conf -- Maxim Maximov From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 20: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 AA0DF16A4CE for ; Thu, 22 Jul 2004 20:35:27 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 269B243D4C for ; Thu, 22 Jul 2004 20:35:27 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.155] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BnkHm-0000JP-00 for freebsd-current@freebsd.org; Thu, 22 Jul 2004 22:35:26 +0200 Received: from [84.128.139.174] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1BnkHl-0007UT-00 for freebsd-current@freebsd.org; Thu, 22 Jul 2004 22:35:26 +0200 From: Max Laier To: freebsd-current@freebsd.org Date: Thu, 22 Jul 2004 22:33:12 +0200 User-Agent: KMail/1.6.2 References: <20040722200436.GM8753@mail.evip.pl> In-Reply-To: <20040722200436.GM8753@mail.evip.pl> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_OSCABvJ9MlRlKPt"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407222233.18787.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 Subject: Re: ALTQ and tun 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, 22 Jul 2004 20:35:27 -0000 --Boundary-02=_OSCABvJ9MlRlKPt Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 22 July 2004 22:04, Wiktor Niesiobedzki wrote: > Hi, > > Recently I configured my DSL link to use pf+ALTQ instead of > ipfw+DUMMYNET, but I encountered following problem: > - no single packet wents through the ALTQ > > I guess, that I miss something very trival, but for checkout: > pf.conf: > iext_if=3D"tun0 > int_if=3D"dc0" > > altq on $ext_if priq queue {dc, ssh_interactive, ssh_bulk, other} > queue dc priority 0 > queue ssh_interactive priority 15 > queue ssh_bulk priority 3 > queue other priority 7 priq(default) > > pass out on $ext_if proto tcp from any to any port 22 tos 0x10 queue > ssh_interactive label ssh_inter pass out log on $ext_if proto tcp from any > to any port 22 tos 0x08 queue ssh_bulk label ssh_bulk pass out log on > $ext_if proto tcp from any to any port 22 queue ssh_interactive label > ssh_inter2 pass out log on $ext_if proto tcp from any to any user dctc > queue dc label dc_transfer #pass out on $ext_if inet proto tcp from > ($ext_if) port 61412 to any queue dc label dc_transfer_port pass out on > $ext_if proto tcp from krz.mine.nu port 61412 to any label dc_transfer_po= rt > pass in log on $ext_if proto tcp from any to ($ext_if) port > {22,80,113,61412} label pass_in_tcp pass in log on $ext_if proto udp from > any to ($ext_if) port 61412 label pass_in_udp pass in on $ext_if proto tcp > from any to any port 4662 label pass_in_mule queue dc pass in on $ext_if > proto udp from any to any port 4672 label pass_in_kad queue dc pass out l= og > on $ext_if proto { tcp, udp } all keep state label pass_out_all queue oth= er > pass out on $ext_if inet proto icmp all icmp-type {0,1,3,4,8,11,12} keep > state pass in on $int_if all label pass_in_internal > pass out on $int_if all label pass_out_internal queue other > > And for example: > # pfctl -v -s rule > [...] > pass out log on tun0 proto tcp all keep state label "pass_out_all" queue > other [ Evaluations: 25193 Packets: 855303 Bytes: 645597787 =20 > States: 13 ] pass out log on tun0 proto udp all keep state label > "pass_out_all" queue other [ Evaluations: 3023 Packets: 10152 =20 > Bytes: 1222129 States: 2 ] [...] > > # pfctl -v -s queue > queue dc priority 0 > [ pkts: 0 bytes: 0 dropped pkts: 0 bytes: = 0 > ] [ qlength: 0/ 50 ] > queue ssh_interactive priority 15 > [ pkts: 0 bytes: 0 dropped pkts: 0 bytes: = 0 > ] [ qlength: 0/ 50 ] > queue ssh_bulk priority 3 > [ pkts: 0 bytes: 0 dropped pkts: 0 bytes: = 0 > ] [ qlength: 0/ 50 ] > queue other priority 7 priq( default ) > [ pkts: 0 bytes: 0 dropped pkts: 0 bytes: = 0 > ] [ qlength: 0/ 50 ] > > > Nothing. Just like ALTQ was not enabled, but then, how to enable it? > Can someone point me out, what I am missing in my configuration? Nothing. This is a problem in ALTQ activation. Please do the following: 1) # pfctl -d; pfctl -Fa; pfctl -ef /etc/pf.conf Your queues should be working now. 2) Make sure to install the updated rc.d/pf script, which will "just do the= =20 right thing"[tm]. 3) A revised ALTQ API (which I haven't found to time to do, yet) will solve= =20 this. If the problem is persistent (which I don't think will be the case), please= =20 report back. =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 --Boundary-02=_OSCABvJ9MlRlKPt Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBBACSOXyyEoT62BG0RAnMoAJ0ePr85Pv787C0C4z+xNnkWxnxB6wCeJRQ9 zhc4pYlw7S7/CdeOuUtqpB0= =hDKY -----END PGP SIGNATURE----- --Boundary-02=_OSCABvJ9MlRlKPt-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 21:08: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 4F20416A4CE for ; Thu, 22 Jul 2004 21:08:41 +0000 (GMT) Received: from gateway.nixsys.be (gateway.nixsys.be [195.144.77.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0AA243D2D for ; Thu, 22 Jul 2004 21:08:40 +0000 (GMT) (envelope-from philip@paeps.cx) Received: from erda.home.paeps.cx (erda.home.paeps.cx [IPv6:2001:838:37f:10::1]) by gateway.nixsys.be (Postfix) with ESMTP id 35B807D for ; Thu, 22 Jul 2004 23:08:38 +0200 (CEST) Received: from fasolt.home.paeps.cx (fasolt.home.paeps.cx [10.0.0.2]) by erda.home.paeps.cx (Postfix) with ESMTP id B1B7D20E3 for ; Thu, 22 Jul 2004 23:08:32 +0200 (CEST) Received: from fasolt.home.paeps.cx (philip@localhost [127.0.0.1]) i6ML8b8e046505; Thu, 22 Jul 2004 23:08:37 +0200 (CEST) (envelope-from philip@fasolt.home.paeps.cx) Received: (from philip@localhost) by fasolt.home.paeps.cx (8.12.11/8.12.11/Submit) id i6ML8aVl046504; Thu, 22 Jul 2004 23:08:36 +0200 (CEST) (envelope-from philip) Date: Thu, 22 Jul 2004 23:08:36 +0200 From: Philip Paeps To: Kim Culhan Message-ID: <20040722210836.GB46371@fasolt.home.paeps.cx> Mail-Followup-To: Kim Culhan , freebsd-current@FreeBSD.org References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040721203620.72466.qmail@web50707.mail.yahoo.com> X-Date-in-Rome: ante diem XI Kalendas Augustas MMDCCLVII ab Urbe Condida X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879 X-Message-Flag: Get a proper mailclient! User-Agent: Mutt/1.5.6i cc: freebsd-current@FreeBSD.org Subject: Re: laptop for -current 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, 22 Jul 2004 21:08:41 -0000 On 2004-07-21 13:36:20 (-0700), Kim Culhan wrote: > Anyone know a laptop they think is good for FreeBSd-current? I've been fairly happy with all kinds of Asus laptops. About the only things not working for me are the winmodems (grmbl) and (only on some models) irda. ACPI is fairly decent, particularly on the more recent models. Stay away from the L3H, that one's a bit of a pain. > With all the differences in hardware, trying to find one which is mostly > compatible is not straightforward. > > The manufacturers don't make it easier.. It's all a conspiracy. - Philip -- Philip Paeps Please don't CC me, I am subscribed to the list. BOFH Excuse #171: NOTICE: alloc: /dev/null: filesystem full From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 21:12: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 D1FC016A4CE; Thu, 22 Jul 2004 21:12:11 +0000 (GMT) Received: from freebsd3.cimlogic.com.au (adsl-20-121.swiftdsl.com.au [218.214.20.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id E90FA43D55; Thu, 22 Jul 2004 21:12:10 +0000 (GMT) (envelope-from jb@cimlogic.com.au) Received: by freebsd3.cimlogic.com.au (Postfix, from userid 102) id 581926AC0E; Fri, 23 Jul 2004 07:12:09 +1000 (EST) Date: Fri, 23 Jul 2004 07:12:09 +1000 From: John Birrell To: Bruce Evans Message-ID: <20040722211209.GB34260@freebsd3.cimlogic.com.au> References: <20040721081310.GJ22160@freebsd3.cimlogic.com.au> <20040721220405.Y2346@epsplex.bde.org> <20040721215940.GK22160@freebsd3.cimlogic.com.au> <20040722225952.S1704@epsplex.bde.org> <20040723014517.B2451@epsplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040723014517.B2451@epsplex.bde.org> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: nanosleep returning early 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, 22 Jul 2004 21:12:12 -0000 On Fri, Jul 23, 2004 at 02:25:16AM +1000, Bruce Evans wrote: > Now I think I know the reason. The interval between clock interrupts > is supposed to be 1/HZ seconds = `tick' microseconds, but it cannot > be set nearly that precisely, and the imprecision of inversely > proportional to HZ. The i8254 counter has a default nominal frequency > of 1193182 Hz. Suppose that this is perfectly accurate. Then to > implement clock interrupts at HZ hz, we want to program the i8254's > maximum count to 1193182/HZ in infinite precision, but counts must be > integers so we must round. The loss of precision is quite large for > HZ = 1000: 1193182 / 1000.0 = 1193.182; rounding this (to nearest) > gives 1193 and an error of 182 in 1193182 = 152 ppm. Also, the extra > tick added by tvtohz() is only 1000 uS long, so it only has a chance > of about 152/1000 to compensate for the rounding error. Finally, the > explicit check that the interval has elapsed cannot compensate for > errors larger than tc_tick/HZ because getnanouptime() is fuzzy. > > Rounding 1193.182 to nearest happens to round down; thus clock ticks > are shorter than `tick' microseconds, tvtohz()'s value is too small, > and nanosleep() may return too early. The loop limits the error to > about 1 tick in this case. The i8254 frequency may be calibrated or > set using sysctl to a more (or less) accurate value. Then the rounding > may go the other way so that tvtohz()'s value is too large and nanoleep() > may return too late. The loop cannot limit the error in this case. > The absolute error may be large for long sleeps. E.g., 152 ppm over > 1 day is 13 seconds. > > tvtohz()'s value may also be too large because the i8254 frequency > is not known accurately. It's nominal value is wrong by 10-100 Hz > on my systems. I minimize errors from this by calibrating all > timecounters using a common clock. Thanks for taking the trouble to explain this. 8-) -- John Birrell From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 21:34: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 CACEC16A4CE for ; Thu, 22 Jul 2004 21:34:56 +0000 (GMT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9831F43D3F for ; Thu, 22 Jul 2004 21:34:56 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BnlDL-0003at-00 for ; Thu, 22 Jul 2004 23:34:55 +0200 Received: from mulder.f5.com ([205.229.151.150]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 22 Jul 2004 23:34:55 +0200 Received: from atkin901 by mulder.f5.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 22 Jul 2004 23:34:55 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: othermark Date: Thu, 22 Jul 2004 14:34:51 -0700 Lines: 22 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: mulder.f5.com User-Agent: KNode/0.7.7 Sender: news Subject: fixing out of order first fragment processing? 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, 22 Jul 2004 21:34:56 -0000 Hi, This is one of those obscure, yet well known issues in FreeBSD, some network stacks, like Linux, send the udp/icmp fragment first (if multiple frags -- in reverse order), then the orginal packet with the header. In -current, we still cannot process this simple fragged icmp-echo request from a Linux host. For example, 'ping -c 1 -s 1500 '. FreeBSD discards the frag(s) and when it sees the initial packet with header waits for the frags. So two questions: 1. is there a gnats pr? I tried various searches with no success. 2. are there workarounds/patches? -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired); From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 22:01: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 7A03316A4CE for ; Thu, 22 Jul 2004 22:01:31 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F7E643D1F for ; Thu, 22 Jul 2004 22:01:31 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.207] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1Bnld4-0000oX-00; Fri, 23 Jul 2004 00:01:30 +0200 Received: from [84.128.139.174] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1Bnld4-00061F-00; Fri, 23 Jul 2004 00:01:30 +0200 From: Max Laier To: freebsd-current@freebsd.org Date: Thu, 22 Jul 2004 23:59:12 +0200 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_7iDABeE2DhapSs4"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407222359.23147.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 cc: othermark Subject: Re: fixing out of order first fragment processing? 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, 22 Jul 2004 22:01:31 -0000 --Boundary-02=_7iDABeE2DhapSs4 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 22 July 2004 23:34, othermark wrote: > Hi, > > This is one of those obscure, yet well known issues in FreeBSD, > some network stacks, like Linux, send the udp/icmp fragment > first (if multiple frags -- in reverse order), then the orginal > packet with the header. > > In -current, we still cannot process this simple fragged icmp-echo > request from a Linux host. For example, 'ping -c 1 -s 1500 '. > > FreeBSD discards the frag(s) and when it sees the initial packet with > header waits for the frags. > > So two questions: > > 1. is there a gnats pr? I tried various searches with no success. > 2. are there workarounds/patches? Activation of pf with a scrub in on fragment reassemble rule works as workaround. In every case you have to decide if you want to=20 invest the required memory to store fragments, which might make you=20 easy/easier prey for DoS-attacks. Usually, for an average gateway the cost = is=20 worth the gain (=3D increased security). =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 --Boundary-02=_7iDABeE2DhapSs4 Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBBADi7XyyEoT62BG0RApMqAJ9W6S1o2XOtEKjYgXBWVzqN9hGFJwCeIMeH Z0txgmJtlI+Bn17E7zLJG+o= =QSmo -----END PGP SIGNATURE----- --Boundary-02=_7iDABeE2DhapSs4-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 22:32: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 760F816A4CE for ; Thu, 22 Jul 2004 22:32:31 +0000 (GMT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id D48F643D49 for ; Thu, 22 Jul 2004 22:32:30 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1Bnm73-0004eg-00 for ; Fri, 23 Jul 2004 00:32:29 +0200 Received: from mulder.f5.com ([205.229.151.150]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 23 Jul 2004 00:32:29 +0200 Received: from atkin901 by mulder.f5.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 23 Jul 2004 00:32:29 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: othermark Date: Thu, 22 Jul 2004 15:32:25 -0700 Lines: 30 Message-ID: References: <200407222359.23147.max@love2party.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: mulder.f5.com User-Agent: KNode/0.7.7 Sender: news Subject: Re: fixing out of order first fragment processing? 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, 22 Jul 2004 22:32:31 -0000 Max Laier wrote: > On Thursday 22 July 2004 23:34, othermark wrote: > Activation of pf with a > scrub in on fragment reassemble > rule works as workaround. Thanks for this suggestion, I have a 'scrub in all fragments reassemble' that I just added and loaded to my /etc/pf.conf, which does not seem to solve the problem. Do I have to specify a scrub for each interface in this case (maybe a better question for the pf list)? > In every case you have to decide if you want to > invest the required memory to store fragments, which might make you > easy/easier prey for DoS-attacks. Usually, for an average gateway the cost > is worth the gain (= increased security). Most of the current systems today are able to handle both types of sequences. It really is a small processing hit, FreeBSD already does some bufferring with proper safeguards/maximums for various traffic patterns. I would suspect some NFS/udp interoperability problems with the way it handles fragments right now. -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired); From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 22:47: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 DA77A16A4CE for ; Thu, 22 Jul 2004 22:47:45 +0000 (GMT) Received: from rader.servnow.com (rader.servnow.com [69.93.129.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id A110B43D41 for ; Thu, 22 Jul 2004 22:47:45 +0000 (GMT) (envelope-from mikes@siralan.org) Received: from 12-202-252-157.client.insightbb.com ([12.202.252.157] helo=familysquires.net) by rader.servnow.com with esmtp (TLSv1:AES256-SHA:256) (Exim 4.34) id 1BnmLe-0000rB-Cm; Thu, 22 Jul 2004 18:47:12 -0400 Date: Thu, 22 Jul 2004 17:47:40 -0500 (EST) From: "Michael L. Squires" X-X-Sender: mikes@familysquires.net To: John Merryweather Cooper In-Reply-To: <1090519292.35023.15.camel@68-169-191-150.losaca.adelphia.net> Message-ID: <20040722174610.H31267@familysquires.net> References: <001401c4700e$91b5a470$5001a8c0@CINDY> <1090519292.35023.15.camel@68-169-191-150.losaca.adelphia.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-PopBeforeSMTPSenders: mikes@siralan.org X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - rader.servnow.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - siralan.org X-Source: X-Source-Args: X-Source-Dir: cc: freebsd-current@freebsd.org cc: "George D. Gal" Subject: Re: radeon drm code in -current 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, 22 Jul 2004 22:47:46 -0000 I'm using an original ATI All-in-Wonder with 5.2-STABLE from July 14 with radeondrm in the kernel and haven't seen this. Mike Squires From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 22:54: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 AA9C316A4CE; Thu, 22 Jul 2004 22:54:00 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EBFD43D3F; Thu, 22 Jul 2004 22:54:00 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.206] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BnmRq-0003kv-00; Fri, 23 Jul 2004 00:53:58 +0200 Received: from [84.128.139.174] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1BnmRq-0007Mb-00; Fri, 23 Jul 2004 00:53:58 +0200 From: Max Laier To: freebsd-current@freebsd.org Date: Fri, 23 Jul 2004 00:51:44 +0200 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_HUEABX694/GxqKJ"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407230051.51939.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 cc: "Bjoern A. Zeeb" cc: Wiktor Niesiobedzki cc: Robert Watson Subject: Re: LORs with 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: Thu, 22 Jul 2004 22:54:00 -0000 --Boundary-02=_HUEABX694/GxqKJ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 22 July 2004 14:36, Robert Watson wrote: > On Thu, 22 Jul 2004, Bjoern A. Zeeb wrote: > > > I don't think, it was reported yet, but here it goes: > > > > > > lock order reversal > > > 1st 0xc0632c80 pf task mtx (pf task mtx) @ > > > /usr/src/sys/contrib/pf/net/pf.c:5822 2nd 0xc066638c tcp (tcp) @ > > > /usr/src/sys/contrib/pf/net/pf.c:2420 > > > > for reference: added it to "LOR page" with LOR # 017: > > http://sources.zabbadoz.net/freebsd/lor.html#017 > > I have no immediate fix, but here's an explanation: > > This likely occurs because calls are made into pf in the outgoing packet > path, which may hold protocol layer locks (inpcb and pcbinfo locks). The > pf mutex will therefore typically follow the protocol locks in the lock > order. However, when pf calls up to the pcb/socket code to find > potentially matching pcbs or sockets for a packet, it can't/shouldn't hold > the pf lock across that. A similar bug exists in ipfw. > > FWIW, this is actually symptomatic of a race: technically, that pcb lookup > could have a different result between when the firewall looks it up and > when the TCP or UDP code looks it up. It's a property of what is > generally considered a layering violation, albeit a useful one. > > The solution I'm looking at for ipfw, but haven't had a chance to > prototype yet, is to avoid holding the mutex for the duration of the call > to ipfw, but instead use some rule set reference count such that ipfw > consumers hold a reference on the rules to prevent them from changing out > from under them. Note that this has interesting semantic consideration > such as starvation, which are usually remedied using copy-on-write, but > that may be expensive for large rule sets. Just something to think > about... This raises the question (at least for me) for a useable sx(9) implementati= on=20 or a busycount of some sort. Somebody suggested atomic refcounts, but I don= 't=20 remember what the outcome was. I know of at least two places where we have= =20 handrolled busycounts: pfil_hooks and MAC Something general with tuneable starvation scheme might be worthwhile? In any case, I must look into something of that kind for pf as well. At the= =20 moment we have a lot of: "drop lock - call back into the stack - reaquire=20 lock". =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 --Boundary-02=_HUEABX694/GxqKJ Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBBAEUHXyyEoT62BG0RAml9AJ9cOycGlCjgSm251O5O704YSlF9BwCcD4lD R34aNh7qFRfkih5l9bTZLnQ= =wLOY -----END PGP SIGNATURE----- --Boundary-02=_HUEABX694/GxqKJ-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 00:11: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 2926216A4CE for ; Fri, 23 Jul 2004 00:11:32 +0000 (GMT) Received: from samuelstringham.com (cs666986-52.satx.rr.com [66.69.86.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1E8943D2D for ; Fri, 23 Jul 2004 00:11:31 +0000 (GMT) (envelope-from samuel@samuelstringham.com) Received: by samuelstringham.com (Postfix, from userid 500) id D7A1435018; Thu, 22 Jul 2004 19:08:19 -0500 (CDT) Date: Thu, 22 Jul 2004 19:08:19 -0500 From: Samuel Stringham To: current@freebsd.org Message-ID: <20040723000819.GA17347@linux> References: <20040722141237.O98018@mirrorball.theloosingend.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040722141237.O98018@mirrorball.theloosingend.net> X-Operating-System: "SuSE Linux" User-Agent: Mutt/1.5.6i Subject: Re: if_ndis/5.2.1/smc2602w-r3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Samuel Stringham List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jul 2004 00:11:32 -0000 On Thu, Jul 22, 2004 at 02:15:07PM +0200, Svein Halvor Halvorsen wrote: > > I tried asking on questions to no avail. So I'll try again here, since > this is -current code I'm tinkering with here. > > Copying > > src/sys/modules/if_ndis > src/sys/modules/ndis > src/sys/compat/ndis > src/sys/dev/if_ndis > > ... from a current source-tree to my 5.2.1-box, and compiling using a > ndis_driver_data.h made from the latest driver found on SMC's website > using a ndisctl on my current system, seems to work fine. > > kldload-ing ndis also seems to work. But when I kldload if_ndis, the > system freezes. No error messages, no response. A cold boot is the only > thing that seems to fix it. > Though I am not sure, it seems that there have been some instabilities in the if_ndis lately. I reported a repeatable panic a couple days ago with -CURRENT which I am unable to get rid of. The author may be busy with real work as of late. Either way, I am hoping to get some of this ndis love so I can get my card ( DWL 520+ ) working as well. > Is this supposed to work, or am I trying to do the impossible here? > Any hints would be appreciated. It is supposed to work. Be patient, and something magical may happen:) > > > Svein Halvor > > > Btw: ndisctl choked on the inf-file, because of a missing newline at the > end. The fact that the syntax error occured on the last line, hinted on a > missing newline, but I think ndisctl should either give a more precise > error message, or preferable just cope with a missing newline. Best regards, Samuel Stringham From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 03:07: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 BFE1416A4CE for ; Fri, 23 Jul 2004 03:07:19 +0000 (GMT) Received: from fornax.vsecurity.com (64-144-2-149.client.dsl.net [64.144.2.149]) by mx1.FreeBSD.org (Postfix) with SMTP id EEA6243D46 for ; Fri, 23 Jul 2004 03:07:18 +0000 (GMT) (envelope-from ggal@vsecurity.com) Received: (qmail 20763 invoked from network); 23 Jul 2004 03:10:31 -0000 Received: from unknown (HELO CINDY) (127.0.0.1) by 0 with SMTP; 23 Jul 2004 03:10:31 -0000 Message-ID: <009101c47062$29afceb0$5001a8c0@CINDY> From: "George D. Gal" To: "Michael L. Squires" , "John Merryweather Cooper" References: <001401c4700e$91b5a470$5001a8c0@CINDY> <1090519292.35023.15.camel@68-169-191-150.losaca.adelphia.net> <20040722174610.H31267@familysquires.net> Date: Thu, 22 Jul 2004 23:07:17 -0400 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 cc: freebsd-current@freebsd.org Subject: Re: radeon drm code in -current 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, 23 Jul 2004 03:07:19 -0000 You wouldn't see this in 5.2 stable only current -george ----- Original Message ----- From: "Michael L. Squires" To: "John Merryweather Cooper" Cc: "George D. Gal" ; Sent: Thursday, July 22, 2004 6:47 PM Subject: Re: radeon drm code in -current > I'm using an original ATI All-in-Wonder with 5.2-STABLE from July 14 with > radeondrm in the kernel and haven't seen this. > > Mike Squires > > > From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 03:22: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 73EBC16A4CE for ; Fri, 23 Jul 2004 03:22:42 +0000 (GMT) Received: from lakermmtao02.cox.net (lakermmtao02.cox.net [68.230.240.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id E05AD43D39 for ; Fri, 23 Jul 2004 03:22:41 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao02.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP <20040723032239.KWBH28298.lakermmtao02.cox.net@dolphin.local.net>; Thu, 22 Jul 2004 23:22:39 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.12.11/8.12.11) with ESMTP id e6N3Md1W039166; Sat, 22 Jul 2000 22:22:39 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.12.11/8.12.11/Submit) id e6N3MdU8039156; Sat, 22 Jul 2000 22:22:39 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20040722200600.GA1158@localhost> Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: Alecs King cc: freebsd-current@freebsd.org Subject: Re: Sound issue on -current 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: , Date: Fri, 23 Jul 2004 03:22:42 -0000 X-Original-Date: Sat, 22 Jul 2000 22:22:38 -0500 (CDT) X-List-Received-Date: Fri, 23 Jul 2004 03:22:42 -0000 On 22-Jul-2004 Alecs King wrote: > Onboard nForce2 audio (Realtek ALC650 AC97Codec). I used to use > 'device > pcm' without problem. > > Just cvsup'ed the source and found that -current is now using a new > 'sound/snd_*' scheme. I checked the NOTES but couldnt find any snd_* > for my case. So i tried just using 'device sound' without any > 'device snd_*' but failed. > > Is there anything i missed? Which snd_* should i use? Any > suggestions? Try the snd_ich driver. Works for me with my nForce3 chipset. -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 03:51: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 A744516A4CE for ; Fri, 23 Jul 2004 03:51:37 +0000 (GMT) Received: from md1.swissinfo.org (md1.swissinfo.org [146.159.4.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07D8343D49 for ; Fri, 23 Jul 2004 03:51:37 +0000 (GMT) (envelope-from alecs@swissinfo.org) Received: from mail.swissinfo.org ([194.6.181.33]) by md1.swissinfo.org (md1.swissinfo.org [146.159.6.9]) (MDaemon.PRO.v7.1.1.R) with ESMTP id md50001782917.msg for ; Fri, 23 Jul 2004 05:51:30 +0200 Received: from localhost (210.77.10.80) by mail.swissinfo.org (7.0.020) (authenticated as alecs) id 3F585D660241EE4D for freebsd-current@freebsd.org; Fri, 23 Jul 2004 05:51:26 +0200 Date: Fri, 23 Jul 2004 11:52:06 +0800 From: Alecs King To: freebsd-current@freebsd.org Message-ID: <20040723035206.GA719@localhost> Mail-Followup-To: freebsd-current@freebsd.org References: <20040722200600.GA1158@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i X-Spam-Processed: md1.swissinfo.org, Fri, 23 Jul 2004 05:51:30 +0200 (not processed: message from valid local sender) X-MDRemoteIP: 194.6.181.33 X-Return-Path: alecs@swissinfo.org X-MDaemon-Deliver-To: freebsd-current@freebsd.org X-MDAV-Processed: md1.swissinfo.org, Fri, 23 Jul 2004 05:51:33 +0200 Subject: Re: Sound issue on -current 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, 23 Jul 2004 03:51:37 -0000 On Sat, Jul 22, 2000 at 10:22:38PM -0500, Conrad J. Sabatier wrote: > > On 22-Jul-2004 Alecs King wrote: > > Onboard nForce2 audio (Realtek ALC650 AC97Codec). I used to use > > 'device > > pcm' without problem. > > > > Just cvsup'ed the source and found that -current is now using a new > > 'sound/snd_*' scheme. I checked the NOTES but couldnt find any snd_* > > for my case. So i tried just using 'device sound' without any > > 'device snd_*' but failed. > > > > Is there anything i missed? Which snd_* should i use? Any > > suggestions? > > Try the snd_ich driver. Works for me with my nForce3 chipset. > Thanks. Works for me. =) Just another question: Can you record sound on your box? Even Back in the 'device pcm' days, i cant record any sound (playing is fine). More light to shed on this? TIA. -- Alecs King From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 04:02: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 1B71416A4CE for ; Fri, 23 Jul 2004 04:02:05 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id D173F43D53 for ; Fri, 23 Jul 2004 04:02:04 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from [192.168.0.103] (c-24-21-18-195.client.comcast.net[24.21.18.195]) by comcast.net (sccrmhc12) with SMTP id <2004072304020301200ngcble>; Fri, 23 Jul 2004 04:02:04 +0000 From: Eric Anholt To: "George D. Gal" In-Reply-To: <001401c4700e$91b5a470$5001a8c0@CINDY> References: <001401c4700e$91b5a470$5001a8c0@CINDY> Content-Type: text/plain Message-Id: <1090555317.899.12.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 22 Jul 2004 21:01:57 -0700 Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: radeon drm code in -current 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, 23 Jul 2004 04:02:05 -0000 On Thu, 2004-07-22 at 10:08, George D. Gal wrote: > Hello I'm wondering if anyone else has experienced problems with the radeon > drm driver in -current. It seems that sometime between Jun 22 and the > latest -current, I have problems with the radeon drm/dri drivers loading when > XFree starts up. > > The error I get when starting XFree now is: > > [drm] failed to load kernel module "radeon" (II) RADEON(0): [drm] drmOpen > failed > (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI. I'd need your whole XFree86.0.log to tell why the drmOpen failed. You might want to also include your dmesg. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 04:02: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 F174F16A4CE; Fri, 23 Jul 2004 04:02:48 +0000 (GMT) Received: from cpanel.ezone.ru (cpanel.ezone.ru [213.85.31.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB88E43D58; Fri, 23 Jul 2004 04:02:47 +0000 (GMT) (envelope-from mcsi@mcsi.pp.ru) Received: from [81.195.3.159] (ppp3-159.pppoe.mtu-net.ru [81.195.3.159]) (authenticated bits=0) by cpanel.ezone.ru (8.13.0/8.12.11) with ESMTP id i6N42eji094538; Fri, 23 Jul 2004 08:02:41 +0400 (MSD) (envelope-from mcsi@mcsi.pp.ru) Message-ID: <41008DDB.6030609@mcsi.pp.ru> Date: Fri, 23 Jul 2004 08:02:35 +0400 From: Maxim Maximov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.1) Gecko/20040720 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: Philip Paeps References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> <20040722210836.GB46371@fasolt.home.paeps.cx> In-Reply-To: <20040722210836.GB46371@fasolt.home.paeps.cx> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mail3.ezone.ru cc: Kim Culhan cc: freebsd-current@freebsd.org Subject: Re: laptop for -current 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, 23 Jul 2004 04:02:49 -0000 Philip Paeps wrote: > On 2004-07-21 13:36:20 (-0700), Kim Culhan wrote: > >>Anyone know a laptop they think is good for FreeBSd-current? > > > I've been fairly happy with all kinds of Asus laptops. About the only things > not working for me are the winmodems (grmbl) and (only on some models) irda. > ACPI is fairly decent, particularly on the more recent models. Stay away from > the L3H, that one's a bit of a pain. My recent model L5Ga panics when suspending to S4 and can't wake up from S3. S1 and other ACPI features (screen brightness control from acpi_asus for example) are working fine though. -- Maxim Maximov From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 04:30:49 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 5465016A4CE for ; Fri, 23 Jul 2004 04:30:49 +0000 (GMT) Received: from smtp08.web.de (smtp08.web.de [217.72.192.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id C282D43D1F for ; Fri, 23 Jul 2004 04:30:48 +0000 (GMT) (envelope-from eugene3@web.de) Received: from [217.83.57.238] (helo=[192.168.0.3]) by smtp08.web.de with asmtp (WEB.DE 4.101 #44) id 1Bnrhn-0001Od-00 for freebsd-current@freebsd.org; Fri, 23 Jul 2004 06:30:47 +0200 Message-ID: <4100947E.30805@web.de> Date: Fri, 23 Jul 2004 06:30:54 +0200 From: Eugene User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.7) Gecko/20040616 X-Accept-Language: de-de, de, en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20040722200612.2685A16A4EF@hub.freebsd.org> In-Reply-To: <20040722200612.2685A16A4EF@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: eugene3@web.de X-Sender: eugene3@web.de Subject: did gbde on swap destroy some boot sectors? (and cdrom did not boot and pppoe broken in xl-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: Fri, 23 Jul 2004 04:30:49 -0000 stability is realy a problem at the moment... as in "Re: INSTABILITY all around (Was: Re: STABILITY [Fwd: cvs commit: src/sys/kern kern_switch.c])" but i knew and i know im running -current and what it means... but now after i got used to the every day crashs and freezes without debugger comming to help, something even more evil happend... what can be more evil than a crash? the system didnt came up again... what i saw was "F1 FreeBSD"... and that it was... at first i guessed my keyboard is ugly, changed it, booted and such actions... nothing... ok... so lets try to fix and boot from cd... -current cd in drive... but after it loaded some kernel it immidately crashed... and i only see some register output... AX=... BX=... the usual stuff... the same as with a -current cd from 10 day ago and 20 days ago... but nothing new im used to boot cds dont like my plextor scsi drive an adaptec controller... even some linux cds dont boot as i tried with knopix (2.4 and 2.6 kernel just to be sure...) seems not realy freebsd relates so... so now i was surprised the boot floppy pack of -current worked fine... congratulations - because we had some trouble with fdc in the past... ok... im in with a fixit floppy and tried to boot the /-partition... doesnt work... to mount /usr works fine... ok... lets try mount -f on /... works fine... ok... but i dint find a way to fix the bootloader or whatever was trashed... so i endet up reinstalling it, lost my disklabels...a nd because it was 6 am and i was tired i did newfs when readding the disklabels *g*... last but not least... the gbde lock file was lost that way, so my other partitions are useless now too... and i have much free hard drive space now :-)) but now what happened? why couldnt it boot again?! the last thing i did was enabling gbde encryption on my swaps... and swap are the first label on each of the 3 drives... i suspect gbde on swap broke something... im i wrong or can someone check this please? now when im finished reinstalling i will be more careful with gbde as long as i dont know if this was the reason... btw: when will the xl-driver be fixed so that pppoe will work again with these 3com cards? i dont have replacement cards to workaround this issue... in another thread it was spotted out this is a xl-problem recently introduced (around 18-jun or so...) sorry for that long bad mail... but of course i wanna use freebsd and help debug it... but what when no debugger omes up in situations like a crash? should i realy try that serial console feature or will it suffer from the same no-debug-issue in such a case? Eugene From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 05:33: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 A9E5E16A4CE for ; Fri, 23 Jul 2004 05:33:57 +0000 (GMT) Received: from lakermmtao08.cox.net (lakermmtao08.cox.net [68.230.240.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3143243D2F for ; Fri, 23 Jul 2004 05:33:57 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao08.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP id <20040723053357.NKR3428.lakermmtao08.cox.net@dolphin.local.net>; Fri, 23 Jul 2004 01:33:57 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.12.11/8.12.11) with ESMTP id i6N4XtHi000951; Fri, 23 Jul 2004 00:33:55 -0400 (EDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.12.11/8.12.11/Submit) id i6N4Xteo000950; Fri, 23 Jul 2004 00:33:55 -0400 (EDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20040723035206.GA719@localhost> Date: Fri, 23 Jul 2004 00:33:55 -0400 (EDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: Alecs King cc: freebsd-current@freebsd.org Subject: Re: Sound issue on -current 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: Fri, 23 Jul 2004 05:33:57 -0000 On 23-Jul-2004 Alecs King wrote: > On Sat, Jul 22, 2000 at 10:22:38PM -0500, Conrad J. Sabatier wrote: >> >> Try the snd_ich driver. Works for me with my nForce3 chipset. >> > > Thanks. Works for me. =) > > Just another question: Can you record sound on your box? Even Back in > the 'device pcm' days, i cant record any sound (playing is fine). > > More light to shed on this? Mmm, no, sorry, I've never tried recording sound here. Try the multimedia list; they can probably offer some advice. -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 06:16: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 2F8BB16A4CE for ; Fri, 23 Jul 2004 06:16:16 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04D5343D58 for ; Fri, 23 Jul 2004 06:16:16 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 30308 invoked from network); 23 Jul 2004 06:16:15 -0000 Received: from gate.funkthat.com (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail2.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 23 Jul 2004 06:16:15 -0000 Received: from hydrogen.funkthat.com (kvenmb@localhost.funkthat.com [127.0.0.1])i6N6GEuU010705; Thu, 22 Jul 2004 23:16:14 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id i6N6GDkl010704; Thu, 22 Jul 2004 23:16:13 -0700 (PDT) Date: Thu, 22 Jul 2004 23:16:13 -0700 From: John-Mark Gurney To: Doug Rabson Message-ID: <20040723061613.GH991@funkthat.com> Mail-Followup-To: Doug Rabson , Andrew Gallatin , simokawa@freebsd.org, freebsd-current@freebsd.org References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200407182104.53221.dfr@nlsystems.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: simokawa@freebsd.org cc: freebsd-current@freebsd.org cc: Andrew Gallatin Subject: Re: Excellent job on the firewire support! 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: Fri, 23 Jul 2004 06:16:16 -0000 Doug Rabson wrote this message on Sun, Jul 18, 2004 at 21:04 +0100: > > 4) Does the loader know about dcons? Eg, can I do "unload boot > > kernel.test" using dcons? > > Actually thats the only downside of dcons. It doesn't cut in until the > firewire controller attaches. It relies on the fact that the fwohci > driver allows access to physical memory from any node on the bus > (implemeted in hardware so you can examine the memory of a hung > machine). The dconschat program uses this feature to access the dcons > ring buffers in the target machine. > > I could imagine a dcons driver in the loader which just enabled physical > access and used some kind of loader trick to hand off the ring buffers > to the kernel dcons driver. It doesn't exist though - say nice things > to the author and he might find the time for it :-) You guys might want to check out nextboot.. it's very nice utility that I've been using in my recent kernel debugging... should do what you need to do w/o loader knowing about dcons... -- 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 Fri Jul 23 08:31: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 F2E2516A4CE; Fri, 23 Jul 2004 08:31:50 +0000 (GMT) Received: from av5-1-sn1.fre.skanova.net (av5-1-sn1.fre.skanova.net [81.228.11.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id B363043D3F; Fri, 23 Jul 2004 08:31:50 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av5-1-sn1.fre.skanova.net (Postfix, from userid 502) id DA9D137E95; Fri, 23 Jul 2004 10:31:49 +0200 (CEST) Received: from smtp3-2-sn1.fre.skanova.net (smtp3-2-sn1.fre.skanova.net [81.228.11.164]) by av5-1-sn1.fre.skanova.net (Postfix) with ESMTP id CD15537E4C; Fri, 23 Jul 2004 10:31:49 +0200 (CEST) Received: from gadget (h130n1fls11o822.telia.com [213.64.66.130]) by smtp3-2-sn1.fre.skanova.net (Postfix) with ESMTP id B60E037E4B; Fri, 23 Jul 2004 10:31:49 +0200 (CEST) From: "Daniel Eriksson" To: "'Scott Long'" , Date: Fri, 23 Jul 2004 10:31:49 +0200 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal In-Reply-To: <40FFD9B3.3040607@freebsd.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Subject: RE: STABILITY [Fwd: cvs commit: src/sys/kern kern_switch.c] 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, 23 Jul 2004 08:31:51 -0000 Scott Long wrote: > This commit is another hack to try to improve stability some > more. Please let me know if it helps or hurts. If it helps > then I think that we are getting closer to at least one of the > real culprits. This commit did not help with my SATA issues unfortunately. /Daniel Eriksson From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 10:34: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 5CDCD16A4CE for ; Fri, 23 Jul 2004 10:34:36 +0000 (GMT) Received: from gateway.nixsys.be (gateway.nixsys.be [195.144.77.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 098EB43D3F for ; Fri, 23 Jul 2004 10:34:36 +0000 (GMT) (envelope-from philip@paeps.cx) Received: from erda.home.paeps.cx (erda.home.paeps.cx [IPv6:2001:838:37f:10::1]) by gateway.nixsys.be (Postfix) with ESMTP id 3A6FA58 for ; Fri, 23 Jul 2004 12:34:34 +0200 (CEST) Received: from fasolt.home.paeps.cx (fasolt.home.paeps.cx [10.0.0.2]) by erda.home.paeps.cx (Postfix) with ESMTP id C08742097 for ; Fri, 23 Jul 2004 12:34:28 +0200 (CEST) Received: from fasolt.home.paeps.cx (philip@localhost [127.0.0.1]) i6NAYX59048725 for ; Fri, 23 Jul 2004 12:34:33 +0200 (CEST) (envelope-from philip@fasolt.home.paeps.cx) Received: (from philip@localhost) by fasolt.home.paeps.cx (8.12.11/8.12.11/Submit) id i6NAYX04048724 for freebsd-current@freebsd.org; Fri, 23 Jul 2004 12:34:33 +0200 (CEST) (envelope-from philip) Date: Fri, 23 Jul 2004 12:34:33 +0200 From: Philip Paeps To: freebsd-current@freebsd.org Message-ID: <20040723103432.GA48650@fasolt.home.paeps.cx> Mail-Followup-To: freebsd-current@freebsd.org References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> <20040722210836.GB46371@fasolt.home.paeps.cx> <41008DDB.6030609@mcsi.pp.ru> <20040723093831.GA1239@laptoxa.toxa.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040723093831.GA1239@laptoxa.toxa.lan> X-Date-in-Rome: ante diem X Kalendas Augustas MMDCCLVII ab Urbe Condida X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879 X-Message-Flag: Get a proper mailclient! User-Agent: Mutt/1.5.6i Subject: Re: laptop for -current 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, 23 Jul 2004 10:34:36 -0000 On 2004-07-23 13:38:31 (+0400), Toxa wrote: > On Fri, Jul 23, 2004 at 08:02:35AM +0400, Maxim Maximov wrote: > > Philip Paeps wrote: > > > On 2004-07-21 13:36:20 (-0700), Kim Culhan wrote: > > > > Anyone know a laptop they think is good for FreeBSd-current? > > > I've been fairly happy with all kinds of Asus laptops. About the only > > > things not working for me are the winmodems (grmbl) and (only on some > > > models) irda. ACPI is fairly decent, particularly on the more recent > > > models. Stay away from the L3H, that one's a bit of a pain. > > not all asus models are supported asus s2n is unsupported, i've to hack > acpi_asus a little bit to make it work very nice laptop btw All patches welcome :-) I've been meaning to sync the supported modules in acpi_asus with the Linux acpi4asus list, but I never seem to get around to it. - Philip -- Philip Paeps Please don't CC me, I am subscribed to the list. BOFH Excuse #148: Insert coin for new game From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 11:09: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 0341B16A4CE for ; Fri, 23 Jul 2004 11:09:35 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id D718043D60 for ; Fri, 23 Jul 2004 11:09:33 +0000 (GMT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.11/8.12.11) with ESMTP id i6NB9VTM041973; Fri, 23 Jul 2004 15:09:31 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.11/8.12.11/Submit) id i6NB9VSc041972; Fri, 23 Jul 2004 15:09:31 +0400 (MSD) (envelope-from ache) Date: Fri, 23 Jul 2004 15:09:31 +0400 From: Andrey Chernov To: Ian FREISLICH Message-ID: <20040723110931.GB41806@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Ian FREISLICH , Garrett Wollman , current@FreeBSD.ORG, Daniel Lang References: <200407211622.i6LGMZrm040478@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter 1.1-beta; AVE 6.26.0.10; VDF 6.26.0.40 (host: pobrecita.freebsd.ru) cc: current@FreeBSD.ORG cc: Daniel Lang cc: Garrett Wollman Subject: Re: NEW TAR 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, 23 Jul 2004 11:09:35 -0000 On Thu, Jul 22, 2004 at 02:37:00PM +0200, Ian FREISLICH wrote: > Garrett Wollman wrote: > > < said: > > > > > I do not see, why it is important if the original file was sparse > > > at all or maybe in different places. > > > > You've never run out of disk space as a result of a sparse file > > becoming non-sparse? > > So, are you arguing for or against tar converting files into sparse > files where it can as Daniel proposes? There is no arguing on that, since tar conversion is non-default, by -S option. > How does dump handle sparse files? dump handle them as sparse by default, no disk overflow. -- Andrey Chernov | http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 17:50: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 66EE016A4CE for ; Thu, 22 Jul 2004 17:50:14 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3703643D39 for ; Thu, 22 Jul 2004 17:50:14 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost02.amcc.com ([192.195.69.49]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id I19LJQ02.K4X; Thu, 22 Jul 2004 10:50:14 -0700 Received: (from vkashyap-pc [10.66.6.61]) by mailhost02.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2004072210513907006 ; Thu, 22 Jul 2004 10:51:39 -0700 From: "Vinod Kashyap" To: Philip Murray , freebsd-current@freebsd.org Date: Thu, 22 Jul 2004 10:50:12 -0700 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: X-Mailman-Approved-At: Fri, 23 Jul 2004 12:03:33 +0000 cc: Harald Schmalzbauer Subject: RE: 3Ware 9500 and disklabel 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, 22 Jul 2004 17:50:14 -0000 Can you try booting off the installation CD/floppies and running sysinstall from there? > -----Original Message----- > From: owner-freebsd-current@freebsd.org > [mailto:owner-freebsd-current@freebsd.org]On Behalf Of Philip Murray > Sent: Thursday, July 22, 2004 3:06 AM > To: freebsd-current@freebsd.org > Cc: Harald Schmalzbauer > Subject: Re: 3Ware 9500 and disklabel > = > = > Harald Schmalzbauer wrote: > = > >Am Donnerstag, 22. Juli 2004 11:01 schrieb Philip Murray: > > = > > > >>Hi, > >> > >>I'm trying to test out -CURRENT (22/7/2004) on a dual Opteron (Tyan > >>board) with a 3Ware 9500-8 raid controller and I'm having = > problems with > >>disklabel. > >> > >>At the moment I have a RAID0 array totalling 600GB. I = > fdisk'd them to > >>create a single partition using the entire volume, fdisk (from > >>sysinstall) complained about the geometry, I wasn't sure what the > >>correct geometry was, so I forged ahead anyway. > >> > >>Then I went to try and disklabel it. It seemed to work from = > sysinstall > >>until I went to write the changes out and it complained = > "ERROR: Unable > >>to write data to disk da0!'. So I tried disklabel on the = > command line, as > >>so > >> = > >> > > > >AFAIK geom only prevents you from direct access to disks = > where your kernel = > >booted from. In your case it is ad4 and I think da1 = > shouldn't be affected but = > >perhaps you want to set the sysctl kern.geom.debugflags to 16. > > > > = > > > Trying to use disklabel from sysinstall with those geom flags = > resulted = > in a panic, I got the following trace from the debugger: > = > panic: spoiling cp->ace =3D 1 > cpuid =3D 1; > KDB: enter: panic > [thread 100081] > Stopped at kdb_enter+0x2f: nop > db> trace > kdb_enter() at kdb_enter+0x2f > panic() at panic+0x210 > g_spoil() at g_spoil+0x7a > g_access() at g_access+0x1fb > g_dev_open() at g_dev_open+0x11b > spec_open() at spec_open+0x330 > spec_vnoperate() at spec_vnoperate+0x14 > vn_open_cred() at vn_open_cred+0x364 > kern_open() at kern_open+0x109 > syscall() at syscall+0x40e > Xfast_syscall() at Xfast_syscall+0xa8 > --- syscall (5, FreeBSD ELF64, open), rip =3D 0x50ebc0, rsp =3D = > 0x7fffffffd838, rbp =3D 0x7dd780 --- > db> > = > I don't know anything more useful I can do than that, so if there is = > something tell me. However, I have managed to somehow lockup = > the serial = > console so I can't do anymore until tomorrow. > = > Cheers > = > Philip > _______________________________________________ > 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 Thu Jul 22 22:58: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 74FF316A4CE for ; Thu, 22 Jul 2004 22:58:08 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18F4F43D39 for ; Thu, 22 Jul 2004 22:58:08 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.209] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BnmVo-0005Ql-00; Fri, 23 Jul 2004 00:58:04 +0200 Received: from [84.128.139.174] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1BnmVn-0007Ig-00; Fri, 23 Jul 2004 00:58:03 +0200 From: Max Laier To: pf4freebsd@freelists.org Date: Fri, 23 Jul 2004 00:55:56 +0200 User-Agent: KMail/1.6.2 References: <200407222359.23147.max@love2party.net> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_9XEAB+OKeZCwhR/"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407230055.57014.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 X-Mailman-Approved-At: Fri, 23 Jul 2004 12:03:33 +0000 cc: othermark Subject: Re: fixing out of order first fragment processing? 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, 22 Jul 2004 22:58:08 -0000 --Boundary-02=_9XEAB+OKeZCwhR/ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 23 July 2004 00:32, othermark wrote: > Max Laier wrote: > > On Thursday 22 July 2004 23:34, othermark wrote: > > Activation of pf with a > > scrub in on fragment reassemble > > rule works as workaround. > > Thanks for this suggestion, > > I have a 'scrub in all fragments reassemble' that I just added and loaded > to my /etc/pf.conf, which does not seem to solve the problem. Do I have = to > specify a scrub for each interface in this case (maybe a better question > for the pf list)? Moved. It actually should. Can you please try to # pfctl -x misc and check = the=20 console? I might well have something wrong, need to cross check. > > In every case you have to decide if you want to > > invest the required memory to store fragments, which might make you > > easy/easier prey for DoS-attacks. Usually, for an average gateway the > > cost is worth the gain (=3D increased security). > > Most of the current systems today are able to handle both types of > sequences. It really is a small processing hit, FreeBSD already does > some bufferring with proper safeguards/maximums for various > traffic patterns. > > I would suspect some NFS/udp interoperability problems with the way it > handles fragments right now. > > -- > othermark > atkin901 at nospam dot yahoo dot com > (!wired)?(coffee++):(wired); > > _______________________________________________ > 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" =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 --Boundary-02=_9XEAB+OKeZCwhR/ Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBBAEX8XyyEoT62BG0RAsSqAJ9Qq6lEDIpsoa23jNz2clVf6smbqACfYu7P WcS5kqjzumnrQnfRl4ve5E8= =ipQP -----END PGP SIGNATURE----- --Boundary-02=_9XEAB+OKeZCwhR/-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 09:40: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 58F4816A4CF for ; Fri, 23 Jul 2004 09:40:15 +0000 (GMT) Received: from ank-pki.ru (mercury.ank-pki.ru [213.170.76.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5139E43D49 for ; Fri, 23 Jul 2004 09:40:12 +0000 (GMT) (envelope-from toxa@cterra.ru) Received: (qmail 74852 invoked by uid 0); 23 Jul 2004 13:40:10 +0400 Received: from toxa@cterra.ru by mercury.ank-pki.ru by uid 0 with qmail-scanner-1.22 (clamscan: 0.74. spamassassin: 2.63. Clear:RC:1(213.170.76.150):. Processed in 0.025516 secs); 23 Jul 2004 09:40:10 -0000 Received: from unknown (HELO localhost) (toxa@213.170.76.150) by ank.nwudc.ru with SMTP; 23 Jul 2004 13:40:10 +0400 Date: Fri, 23 Jul 2004 13:38:31 +0400 From: Toxa To: Philip Paeps , freebsd-current@freebsd.org Message-ID: <20040723093831.GA1239@laptoxa.toxa.lan> Mail-Followup-To: Philip Paeps , freebsd-current@freebsd.org References: <20040721203620.72466.qmail@web50707.mail.yahoo.com> <20040722210836.GB46371@fasolt.home.paeps.cx> <41008DDB.6030609@mcsi.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <41008DDB.6030609@mcsi.pp.ru> User-Agent: Outluck Express 1.5.6i for MS-DOS 6.22-SMP X-Mailer: See User-Agent above :) X-Operating-System: MS-DOS 6.22-CURRENT on Sony VAIO laptop X-PGP-Public-Key: http://toxahost.org/gpg/pubkey.asc X-Useless-Header: Do Androids Dream of Electric Sheep? X-Mailman-Approved-At: Fri, 23 Jul 2004 12:03:33 +0000 Subject: Re: laptop for -current 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, 23 Jul 2004 09:40:15 -0000 On Fri, Jul 23, 2004 at 08:02:35AM +0400, Maxim Maximov wrote: > Philip Paeps wrote: > >On 2004-07-21 13:36:20 (-0700), Kim Culhan wrote: > > > >>Anyone know a laptop they think is good for FreeBSd-current? > > > > > >I've been fairly happy with all kinds of Asus laptops. About the only > >things > >not working for me are the winmodems (grmbl) and (only on some models) > >irda. > >ACPI is fairly decent, particularly on the more recent models. Stay away > >from > >the L3H, that one's a bit of a pain. not all asus models are supported asus s2n is unsupported, i've to hack acpi_asus a little bit to make it work very nice laptop btw -- Anton A. Karpov icq: 845923 jabber: toxa@jabber.ru || toxa@toxahost.org email(s): toxa@cterra.ru || postfix@sendmail.ru www: http://www.toxahost.org pgp key: http://www.toxahost.org/pgp/pubkey.asc You can finger me @toxahost.org for my current status #-------------------------------------------------- Contrary to popular belief, Unix is user friendly. It just happens to be very selective about who it decides to make friends with. /* no comment */ #-------------------------------------------------- From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 12:13: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 0318F16A4CE for ; Fri, 23 Jul 2004 12:13:58 +0000 (GMT) Received: from fornax.vsecurity.com (64-144-2-149.client.dsl.net [64.144.2.149]) by mx1.FreeBSD.org (Postfix) with SMTP id 575C843D39 for ; Fri, 23 Jul 2004 12:13:56 +0000 (GMT) (envelope-from ggal@vsecurity.com) Received: (qmail 24474 invoked from network); 23 Jul 2004 12:17:06 -0000 Received: from unknown (HELO CINDY) (127.0.0.1) by 0 with SMTP; 23 Jul 2004 12:17:06 -0000 Message-ID: <00f401c470ae$84d812b0$5001a8c0@CINDY> From: "George D. Gal" To: "Eric Anholt" References: <001401c4700e$91b5a470$5001a8c0@CINDY> <1090555317.899.12.camel@leguin> Date: Fri, 23 Jul 2004 08:13:48 -0400 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 cc: freebsd-current@freebsd.org Subject: Re: radeon drm code in -current 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, 23 Jul 2004 12:13:58 -0000 >From what I can tell no entry is created in /dev/dri/ for the card. Attached is relevant portion from the XFree86.log -george (II) Primary Device is: PCI 01:00:0 (--) Assigning device section with no busID to primary device (--) Chipset ATI Radeon Mobility 9000 (M9) Lf (AGP) found (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] ...skipping... [31] -1 0 0x0000bf40 - 0x0000bf7f (0x40) IX[B]E [32] -1 0 0x0000bf80 - 0x0000bf9f (0x20) IX[B]E [33] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[B](B) [34] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) [35] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) (==) RADEON(0): Write-combining range (0xfcff0000,0x80000) was already clear (==) RADEON(0): Write-combining range (0xe8000000,0x2000000) (==) RADEON(0): Write-combining range (0xa0000,0x10000) was already clear drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed [drm] failed to load kernel module "radeon" (II) RADEON(0): [drm] drmOpen failed (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI. (II) RADEON(0): Memory manager initialized to (0,0) (1408,5957) (II) RADEON(0): Reserved area from (0,1050) to (1408,1052) ----- Original Message ----- From: "Eric Anholt" To: "George D. Gal" Cc: Sent: Friday, July 23, 2004 12:01 AM Subject: Re: radeon drm code in -current > On Thu, 2004-07-22 at 10:08, George D. Gal wrote: > > Hello I'm wondering if anyone else has experienced problems with the radeon > > drm driver in -current. It seems that sometime between Jun 22 and the > > latest -current, I have problems with the radeon drm/dri drivers loading when > > XFree starts up. > > > > The error I get when starting XFree now is: > > > > [drm] failed to load kernel module "radeon" (II) RADEON(0): [drm] drmOpen > > failed > > (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI. > > I'd need your whole XFree86.0.log to tell why the drmOpen failed. You > might want to also include your dmesg. > > -- > Eric Anholt eta@lclark.edu > http://people.freebsd.org/~anholt/ anholt@FreeBSD.org > > > From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 14:25: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 79D4216A4CE for ; Fri, 23 Jul 2004 14:25:25 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F17843D41 for ; Fri, 23 Jul 2004 14:25:25 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.0.12] (g4.samsco.home [192.168.0.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6NEVlRO071403; Fri, 23 Jul 2004 08:31:47 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <41011F90.2060203@freebsd.org> Date: Fri, 23 Jul 2004 08:24:16 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Eriksson References: In-Reply-To: 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: current@freebsd.org Subject: Re: STABILITY [Fwd: cvs commit: src/sys/kern kern_switch.c] 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, 23 Jul 2004 14:25:25 -0000 Daniel Eriksson wrote: > Scott Long wrote: > > >>This commit is another hack to try to improve stability some >>more. Please let me know if it helps or hurts. If it helps >>then I think that we are getting closer to at least one of the >>real culprits. > > > This commit did not help with my SATA issues unfortunately. > > /Daniel Eriksson > > Does it still exist if you roll back to July 1 sources? Scott From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 14:53: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 13D7916A4CE; Fri, 23 Jul 2004 14:53:05 +0000 (GMT) Received: from web.portaone.com (mail.russia.cz [195.70.151.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C99943D2D; Fri, 23 Jul 2004 14:53:04 +0000 (GMT) (envelope-from sobomax@portaone.com) Received: from [192.168.0.20] (portacare.portaone.com [195.140.247.242]) (authenticated bits=0) by web.portaone.com (8.12.8p2/8.12.8) with ESMTP id i6NEqmNC028658 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 Jul 2004 16:52:49 +0200 (CEST) (envelope-from sobomax@portaone.com) Message-ID: <41012639.3020102@portaone.com> Date: Fri, 23 Jul 2004 17:52:41 +0300 From: Maxim Sobolev Organization: Porta Software Ltd User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug Rabson References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> <16638.32914.509773.486468@grasshopper.cs.duke.edu> <1090421941.7114.26.camel@builder02.qubesoft.com> In-Reply-To: <1090421941.7114.26.camel@builder02.qubesoft.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: simokawa@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG cc: Andrew Gallatin Subject: Re: Excellent job on the firewire 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, 23 Jul 2004 14:53:05 -0000 Doug Rabson wrote: > On Wed, 2004-07-21 at 15:41, Andrew Gallatin wrote: > >>Doug Rabson writes: >> > Actually thats the only downside of dcons. It doesn't cut in until the >> > firewire controller attaches. It relies on the fact that the fwohci >> > driver allows access to physical memory from any node on the bus >> > (implemeted in hardware so you can examine the memory of a hung >> > machine). The dconschat program uses this feature to access the dcons >> > ring buffers in the target machine. >> >>Does remote access to physical memory require dcons to be loaded >>on the target? > > > No. The remote access to physical memory is a hardware-implemented > feature of the firewire ohci hardware. Its enabled in fwohci_attach(). > In the long term, I would like to restrict this a bit but right now all > you have to have is fwohci loaded on the target machine. It would be nice to have some sysctl which to disable such access, since it is BAD THING[tm] from the security POV. -Maxim From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 15:19: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 0BCF316A50C for ; Fri, 23 Jul 2004 15:19:18 +0000 (GMT) Received: from rader.servnow.com (rader.servnow.com [69.93.129.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id B80BC43D54 for ; Fri, 23 Jul 2004 15:19:18 +0000 (GMT) (envelope-from mikes@siralan.org) Received: from 12-202-252-157.client.insightbb.com ([12.202.252.157] helo=familysquires.net) by rader.servnow.com with esmtp (TLSv1:AES256-SHA:256) (Exim 4.34) id 1Bo1pH-00034J-NV; Fri, 23 Jul 2004 11:18:49 -0400 Date: Fri, 23 Jul 2004 10:19:13 -0500 (EST) From: "Michael L. Squires" X-X-Sender: mikes@familysquires.net To: "George D. Gal" In-Reply-To: <009101c47062$29afceb0$5001a8c0@CINDY> Message-ID: <20040723101843.F33942@familysquires.net> References: <001401c4700e$91b5a470$5001a8c0@CINDY> <1090519292.35023.15.camel@68-169-191-150.losaca.adelphia.net> <009101c47062$29afceb0$5001a8c0@CINDY> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-PopBeforeSMTPSenders: mikes@siralan.org X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - rader.servnow.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - siralan.org X-Source: X-Source-Args: X-Source-Dir: cc: freebsd-current@freebsd.org cc: John Merryweather Cooper Subject: Re: radeon drm code in -current 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, 23 Jul 2004 15:19:21 -0000 My mistake - I'm running 5.2-CURRENT. I'm recompiling today so if the problem is post July 12 I'll run into it. Mike Squires From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 15:22: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 005AA16A4D1 for ; Fri, 23 Jul 2004 15:22:01 +0000 (GMT) Received: from hotmail.com (bay8-f101.bay8.hotmail.com [64.4.27.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDC0F43D2F for ; Fri, 23 Jul 2004 15:22:01 +0000 (GMT) (envelope-from evantd@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 23 Jul 2004 08:22:01 -0700 Received: from 67.171.32.75 by by8fd.bay8.hotmail.msn.com with HTTP; Fri, 23 Jul 2004 15:22:00 GMT X-Originating-IP: [67.171.32.75] X-Originating-Email: [evantd@hotmail.com] X-Sender: evantd@hotmail.com From: "Evan Dower" To: conrads@cox.net, alecs@swissinfo.org Date: Fri, 23 Jul 2004 08:22:00 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 23 Jul 2004 15:22:01.0544 (UTC) FILETIME=[CD6CB480:01C470C8] cc: freebsd-current@freebsd.org Subject: Re: Sound issue on -current 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, 23 Jul 2004 15:22:02 -0000 I have a SoundBlaster Live, and while I haven't literally "recorded" anything. Sound input does work. I used it to tune my guitar with gstring until I got a Real guitar tuner. It was a little bit confusing, but I just had to play with the mixer until I figured out which things should be at what levels. I think it works as follows: make sure your recording input is set to mic (or whatever you want to record from) turn up the level on mic turn up the level on record _if_ you want your input played back to you I _think_ that's how it was, but I no longer have it set that way so I'm not really sure. I hope this will be helpful, -- Evan Dower Undergraduate, Computer Science University of Washington Public key: http://students.washington.edu/evantd/pgp-pub-key.txt Key fingerprint = D321 FA24 4BDA F82D 53A9 5B27 7D15 5A4F 033F 887D >From: "Conrad J. Sabatier" >Reply-To: conrads@cox.net >To: Alecs King >CC: freebsd-current@freebsd.org >Subject: Re: Sound issue on -current >Date: Fri, 23 Jul 2004 00:33:55 -0400 (EDT) > > >On 23-Jul-2004 Alecs King wrote: > > On Sat, Jul 22, 2000 at 10:22:38PM -0500, Conrad J. Sabatier wrote: > >> > >> Try the snd_ich driver. Works for me with my nForce3 chipset. > >> > > > > Thanks. Works for me. =) > > > > Just another question: Can you record sound on your box? Even Back in > > the 'device pcm' days, i cant record any sound (playing is fine). > > > > More light to shed on this? > >Mmm, no, sorry, I've never tried recording sound here. Try the >multimedia list; they can probably offer some advice. > >-- >Conrad J. Sabatier -- "In Unix veritas" >_______________________________________________ >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" _________________________________________________________________ Don’t just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 15:29: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 3237316A4CE; Fri, 23 Jul 2004 15:29:56 +0000 (GMT) Received: from hotmail.com (bay8-f106.bay8.hotmail.com [64.4.27.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18E1943D4C; Fri, 23 Jul 2004 15:29:56 +0000 (GMT) (envelope-from evantd@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 23 Jul 2004 08:29:55 -0700 Received: from 67.171.32.75 by by8fd.bay8.hotmail.msn.com with HTTP; Fri, 23 Jul 2004 15:29:55 GMT X-Originating-IP: [67.171.32.75] X-Originating-Email: [evantd@hotmail.com] X-Sender: evantd@hotmail.com From: "Evan Dower" To: scottl@freebsd.org Date: Fri, 23 Jul 2004 08:29:55 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 23 Jul 2004 15:29:55.0938 (UTC) FILETIME=[E82F7C20:01C470C9] cc: current@freebsd.org Subject: Re: STABILITY [Fwd: cvs commit: src/sys/kern kern_switch.c] 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, 23 Jul 2004 15:29:56 -0000 I run -CURRENT on an asus a7m266-d with dual athlon mp 1900s, and the recent stability hacks have not helped me. I do NOT run with full preemption, but if I run "too much stuff" I get a crash within hours. I am usually running X so I don't even see the panic messages unfortunately :-(. Thanks very much for working on tracking them down, -- Evan Dower Undergraduate, Computer Science University of Washington Public key: http://students.washington.edu/evantd/pgp-pub-key.txt Key fingerprint = D321 FA24 4BDA F82D 53A9 5B27 7D15 5A4F 033F 887D _________________________________________________________________ Don’t just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 15:30: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 0599D16A4CE for ; Fri, 23 Jul 2004 15:30:06 +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 515FA43D58 for ; Fri, 23 Jul 2004 15:30:05 +0000 (GMT) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: from m2a2.dyndns.org (krusty.dt.e-technik.uni-dortmund.de [129.217.163.1])7F35935CCA for ; Fri, 23 Jul 2004 17:30:04 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 724E5C18E1 for ; Fri, 23 Jul 2004 17:30:02 +0200 (CEST) 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 07597-03-3 for ; Fri, 23 Jul 2004 17:30:01 +0200 (CEST) Received: by merlin.emma.line.org (Postfix, from userid 500) id 564D3BAEE6; Fri, 23 Jul 2004 17:30:01 +0200 (CEST) To: freebsd-current@freebsd.org From: Matthias Andree Date: Fri, 23 Jul 2004 17:30:01 +0200 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 m2a2.dyndns.org Subject: xl(4) autonegotiation trouble - ng_pppoe related? 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, 23 Jul 2004 15:30:06 -0000 Hi, as of a few weeks ago, there are troubles connecting to T-DSL, the largest ADSL provider in Germany, at least with xl(4) and first "T-DSL" generation Siemens ADSL modems. I've chased this and found some results that I've added to kern/69133. The problem is that outgoing PPPoE packets (user-space ppp) don't seem to appear on the wire whenever the peer does not offer auto-negotiation but the xl interface is set to "media auto" (default). Switching off autonegotiation (ifconfig xl1 media 10baseT/UTP) makes the packets go out to the wire. This may be some incompatibility between xl and ng_pppoe, as xl with rp-pppoe (from ports) works, and vr with ng_pppoe works, too. More details are given in: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/69133 Any insight? -- Matthias Andree Encrypted mail welcome: my GnuPG key ID is 0x052E7D95 (PGP/MIME preferred) From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 15:33: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 EA37016A4FE for ; Fri, 23 Jul 2004 15:33:59 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77DA443D1F for ; Fri, 23 Jul 2004 15:33:59 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.0.12] (g4.samsco.home [192.168.0.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6NFeM9O071559; Fri, 23 Jul 2004 09:40:22 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <41012FA3.4020509@freebsd.org> Date: Fri, 23 Jul 2004 09:32:51 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Evan Dower References: In-Reply-To: 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: current@freebsd.org Subject: Re: STABILITY [Fwd: cvs commit: src/sys/kern kern_switch.c] 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, 23 Jul 2004 15:34:00 -0000 Evan Dower wrote: > I run -CURRENT on an asus a7m266-d with dual athlon mp 1900s, and the > recent stability hacks have not helped me. I do NOT run with full > preemption, What do you mean by this? Do you mean that you have PREEMPTION undefined in /sys/i386/include/param.h, or that you don't have FULL_PREEMPTION defined? Scott From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 15: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 B0B1216A4CE; Fri, 23 Jul 2004 15:50:35 +0000 (GMT) Received: from hotmail.com (bay8-f120.bay8.hotmail.com [64.4.27.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FC0243D31; Fri, 23 Jul 2004 15:50:35 +0000 (GMT) (envelope-from evantd@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 23 Jul 2004 08:50:35 -0700 Received: from 67.171.32.75 by by8fd.bay8.hotmail.msn.com with HTTP; Fri, 23 Jul 2004 15:50:35 GMT X-Originating-IP: [67.171.32.75] X-Originating-Email: [evantd@hotmail.com] X-Sender: evantd@hotmail.com From: "Evan Dower" To: scottl@freebsd.org Date: Fri, 23 Jul 2004 08:50:35 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 23 Jul 2004 15:50:35.0504 (UTC) FILETIME=[CB063F00:01C470CC] cc: current@freebsd.org Subject: Re: STABILITY [Fwd: cvs commit: src/sys/kern kern_switch.c] 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, 23 Jul 2004 15:50:35 -0000 Only that I don't have FULL_PREEMPTION defined in my kernel config. I'm no kernel hacker yet ;-) -- Evan Dower Undergraduate, Computer Science University of Washington Public key: http://students.washington.edu/evantd/pgp-pub-key.txt Key fingerprint = D321 FA24 4BDA F82D 53A9 5B27 7D15 5A4F 033F 887D >From: Scott Long >To: Evan Dower >CC: current@freebsd.org >Subject: Re: STABILITY [Fwd: cvs commit: src/sys/kern kern_switch.c] >Date: Fri, 23 Jul 2004 09:32:51 -0600 > >Evan Dower wrote: > >>I run -CURRENT on an asus a7m266-d with dual athlon mp 1900s, and the >>recent stability hacks have not helped me. I do NOT run with full >>preemption, > >What do you mean by this? Do you mean that you have PREEMPTION >undefined in /sys/i386/include/param.h, or that you don't have >FULL_PREEMPTION defined? > >Scott > _________________________________________________________________ Don’t just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 15:52: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 48A7C16A4CE for ; Fri, 23 Jul 2004 15:52:40 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A8A343D2D for ; Fri, 23 Jul 2004 15:52:39 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.209] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1Bo2Le-0001YR-00 for freebsd-current@freebsd.org; Fri, 23 Jul 2004 17:52:38 +0200 Received: from [217.227.150.246] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1Bo2Le-0005bn-00 for freebsd-current@freebsd.org; Fri, 23 Jul 2004 17:52:38 +0200 From: Max Laier To: freebsd-current@freebsd.org Date: Fri, 23 Jul 2004 17:50:24 +0200 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_IPTABO5tf/GRRNi"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407231750.32302.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 Subject: Re: xl(4) autonegotiation trouble - ng_pppoe related? 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, 23 Jul 2004 15:52:40 -0000 --Boundary-02=_IPTABO5tf/GRRNi Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 23 July 2004 17:30, Matthias Andree wrote: > Hi, > > as of a few weeks ago, there are troubles connecting to T-DSL, the > largest ADSL provider in Germany, at least with xl(4) and first "T-DSL" > generation Siemens ADSL modems. > > I've chased this and found some results that I've added to kern/69133. > > The problem is that outgoing PPPoE packets (user-space ppp) don't seem > to appear on the wire whenever the peer does not offer auto-negotiation > but the xl interface is set to "media auto" (default). Switching off > autonegotiation (ifconfig xl1 media 10baseT/UTP) makes the packets go > out to the wire. Well, if your DSL-modem does not do autonegotiation you have to set the med= ia=20 type manually. It's quite obvious that you can't do pppoEthernet w/o a=20 working ethernet link. Anyhow, from reading the (long) PR audit trail it=20 seems that some of the newer xl(4) changes broke autonegotiation. Would be= =20 very helpful if you could narrow it down somemore i.e. give a last working= =20 version. > This may be some incompatibility between xl and ng_pppoe, as xl with > rp-pppoe (from ports) works, and vr with ng_pppoe works, too. > > More details are given in: > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/69133 > > Any insight? =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 --Boundary-02=_IPTABO5tf/GRRNi Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBBATPIXyyEoT62BG0RApT3AJ9k6FUwUfNAOr9no9wS9c1cLR1nAgCfT7GP gYQraPerNDvid6B/4e7Sgfc= =lHJ3 -----END PGP SIGNATURE----- --Boundary-02=_IPTABO5tf/GRRNi-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 16:01: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 91B6E16A4CE for ; Fri, 23 Jul 2004 16:01:38 +0000 (GMT) Received: from afields.ca (afields.ca [216.194.67.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37FE643D39 for ; Fri, 23 Jul 2004 16:01:38 +0000 (GMT) (envelope-from afields@afields.ca) Received: from afields.ca (localhost.afields.ca [127.0.0.1]) by afields.ca (8.12.11/8.12.11) with ESMTP id i6NG1buO048425; Fri, 23 Jul 2004 12:01:37 -0400 (EDT) (envelope-from afields@afields.ca) Received: (from afields@localhost) by afields.ca (8.12.11/8.12.11/Submit) id i6NG1bxY048424; Fri, 23 Jul 2004 12:01:37 -0400 (EDT) (envelope-from afields) Date: Fri, 23 Jul 2004 12:01:37 -0400 From: Allan Fields To: Eugene Message-ID: <20040723160136.GC31615@afields.ca> References: <20040722200612.2685A16A4EF@hub.freebsd.org> <4100947E.30805@web.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="i9LlY+UWpKt15+FH" Content-Disposition: inline In-Reply-To: <4100947E.30805@web.de> User-Agent: Mutt/1.4i cc: freebsd-current@freebsd.org Subject: Re: did gbde on swap destroy some boot sectors? (and cdrom did not boot and pppoe broken in xl-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: Fri, 23 Jul 2004 16:01:38 -0000 --i9LlY+UWpKt15+FH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 23, 2004 at 06:30:54AM +0200, Eugene wrote: > what can be more evil than a crash? I agree. > the system didnt came up again... what i saw was "F1 FreeBSD"... and=20 > that it was... at first i guessed my keyboard is ugly, changed it,=20 > booted and such actions... nothing... > > ok... so lets try to fix and boot from cd... -current cd in drive... but= =20 > [..]=20 > so now i was surprised the boot floppy pack of -current worked fine...=20 >=20 > ok... im in with a fixit floppy and tried to boot the /-partition...=20 > doesnt work... to mount /usr works fine... ok... lets try mount -f on=20 > /... works fine... ok... >=20 > but i dint find a way to fix the bootloader or whatever was trashed...=20 > so i endet up reinstalling it, lost my disklabels...a nd because it was= =20 Easier done directly with disklabel and/or boot0cfg. > 6 am and i was tired i did newfs when readding the disklabels *g*...=20 > last but not least... the gbde lock file was lost that way, so my other= =20 > partitions are useless now too... and i have much free hard drive space= =20 > now :-)) Unfortunately, you're not alone in having this occur.. :( If anything is currently very important on disk and you haven't newfs'ed the gbde partition, dd to another drive or pull this drive; with faint hope someday you will be able to get it back (but not holding your breath). The more likely case is the lock file still intact, but that may not be so. Read back in lists for similar situation w/ lost lock-file. [Obligatory post-mortem analysis:] The first thing to remember in situations like this is: optimally, don't write to the disk until you spend time dding/dumping specific areas in interest or carefully consider all possible cases. (Probably biggest data loss is the cascading of problems due to being rushed/tired, which has happened to many of us..) It can't be stressed enough how important it is to keep lock-selector file backup on another disk. When one file lost is the whole file system, it makes the case for extra prudence. The other idea is store this on a removable media such as flash, not in root partition. =46rom the Handbook (-- people have fair warning for this): The gbde init command creates a lock file for your gbde partition that in this example is stored as /etc/gbde/ad4s1c. Caution: gbde lock files must be backed up together with the contents of any encrypted partitions. While deleting a lock file alone cannot prevent a determined attacker from decrypting a gbde partition, without the lock file, the legitimate owner will be unable to access the data on the encrypted partition without a significant amount of work that is totally unsupported by gbde(8) and its designer. Perhaps the handbook should now explicitly list making a lock-selector file backup to floppy in procedure for gbde init? > but now what happened? why couldnt it boot again?! the last thing i did= =20 > was enabling gbde encryption on my swaps... and swap are the first label= =20 > on each of the 3 drives... >=20 > i suspect gbde on swap broke something... > > im i wrong or can someone check this please? It's definitely something to look at.. I can't imagine why this should happen, except disklabel issue: where was the swap located and what letter? Did it happen the same on 3 drives? If no, were the disklabels the same? > Eugene --=20 Allan Fields, AFRSL - http://afields.ca 2D4F 6806 D307 0889 6125 C31D F745 0D72 39B4 5541 --i9LlY+UWpKt15+FH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQFBATZf90UNcjm0VUERAlATAJ9fJyq3so/RbWr3LPwnCMu4hzoxLwCgt6Nb oUdNqKVtVCGvHGZ/Ju8gtw0= =IL6m -----END PGP SIGNATURE----- --i9LlY+UWpKt15+FH-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 16:07: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 A438716A4CE for ; Fri, 23 Jul 2004 16:07:17 +0000 (GMT) Received: from rader.servnow.com (rader.servnow.com [69.93.129.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7675243D54 for ; Fri, 23 Jul 2004 16:07:17 +0000 (GMT) (envelope-from mikes@siralan.org) Received: from 12-202-252-157.client.insightbb.com ([12.202.252.157] helo=familysquires.net) by rader.servnow.com with esmtp (TLSv1:AES256-SHA:256) (Exim 4.34) id 1Bo2Zj-0006OF-GB; Fri, 23 Jul 2004 12:06:49 -0400 Date: Fri, 23 Jul 2004 11:07:14 -0500 (EST) From: "Michael L. Squires" X-X-Sender: mikes@familysquires.net To: "George D. Gal" In-Reply-To: <20040723101843.F33942@familysquires.net> Message-ID: <20040723110006.G33942@familysquires.net> References: <001401c4700e$91b5a470$5001a8c0@CINDY> <1090519292.35023.15.camel@68-169-191-150.losaca.adelphia.net> <20040723101843.F33942@familysquires.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-PopBeforeSMTPSenders: mikes@siralan.org X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - rader.servnow.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - siralan.org X-Source: X-Source-Args: X-Source-Dir: cc: freebsd-current@freebsd.org cc: John Merryweather Cooper Subject: Re: radeon drm code in -current 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, 23 Jul 2004 16:07:17 -0000 With 5.2-CURRENT of 5/22 I'm not having problems with radeondrm: drm0: port 0xc800-0xc8ff mem 0xff480000-0xff4fffff,0xe8000000-0xefffffff irq 17 at device 0.0 on pci0 info: [drm] AGP at 0xf8000000 64MB info: [drm] Initialized radeon 1.11.0 20020828 on minor 0 Motherboard is Supermicro P6DGH, dual PII/300, ATI All-in_Wonder (original), motherboard supports only AGP1X or 2X. Kernel config file has options SMP options apic options radeondrm plus others in it, debugging is turned off. Mike Squires From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 16:20: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 3C0DD16A4CE; Fri, 23 Jul 2004 16:20:48 +0000 (GMT) Received: from kayjay.xs4all.nl (kayjay.xs4all.nl [80.126.33.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38DFB43D1F; Fri, 23 Jul 2004 16:20:47 +0000 (GMT) (envelope-from karelj@kayjay.xs4all.nl) Received: from kayjay.xs4all.nl (localhost.kayjay.xs4all.nl [127.0.0.1]) by kayjay.xs4all.nl (8.12.11/8.12.11) with ESMTP id i6NGKjPp055097 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Fri, 23 Jul 2004 18:20:45 +0200 (CEST) (envelope-from karelj@kayjay.xs4all.nl) Received: (from karelj@localhost) by kayjay.xs4all.nl (8.12.11/8.12.11/Submit) id i6NGKiK1055096; Fri, 23 Jul 2004 18:20:44 +0200 (CEST) (envelope-from karelj) Date: Fri, 23 Jul 2004 18:20:44 +0200 From: "Karel J. Bosschaart" To: Scott Long Message-ID: <20040723162044.GA55078@kayjay.xs4all.nl> References: <40FFD9B3.3040607@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40FFD9B3.3040607@freebsd.org> User-Agent: Mutt/1.4.2.1i cc: "'current@freebsd.org'" Subject: Re: STABILITY [Fwd: cvs commit: src/sys/kern kern_switch.c] 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, 23 Jul 2004 16:20:48 -0000 On Thu, Jul 22, 2004 at 09:13:55AM -0600, Scott Long wrote: > All, > > This commit is another hack to try to improve stability some > more. Please let me know if it helps or hurts. If it helps > then I think that we are getting closer to at least one of the > real culprits. Difficult to say after running one day. I have the impression stability is improved somewhat, but nevertheless had some crashes. I got a crash dump that looks very similar to the one I obtained earlier this week. Please let me know what I can do to provide some useful information. Karel. phys9911# gdb53 -k kernel.debug /usr/crash/vmcore.9 GNU gdb 5.3 (FreeBSD) Copyright 2002 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-portbld-freebsd5.2"... panic: sched_rem: KSE not on run queue panic messages: --- panic: sched_rem: KSE not on run queue cpuid = 0; KDB: enter: panic panic: from debugger cpuid = 0; Uptime: 3h28m6s Dumping 247 MB 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 --- #0 doadump () at pcpu.h:159 159 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); Ready to go. Enter 'tr' to connect to the remote target with /dev/cuaa0, 'tr /dev/cuaa1' to connect to a different port or 'trf portno' to connect to the remote target with the firewire interface. portno defaults to 5556. Type 'getsyms' after connection to load kld symbols. If you're debugging a local system, you can use 'kldsyms' instead to load the kld symbols. That's a less obnoxious interface. (kgdb) kldsyms add symbol table from file "/usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/sound/driver/ich/snd_ich.ko.debug" at .text_addr = 0xc09b6800 .data_addr = 0xc09b9040 .bss_addr = 0xc09b92bc add symbol table from file "/usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/sound/sound/sound.ko.debug" at .text_addr = 0xc09c33b4 .data_addr = 0xc09d05a0 .bss_addr = 0xc09d2d40 add symbol table from file "/usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/acpi/acpi/acpi.ko.debug" at .text_addr = 0xc09e8d80 .data_addr = 0xc0a18000 .bss_addr = 0xc0a19aa0 add symbol table from file "/usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/linprocfs/linprocfs.ko.debug" at .text_addr = 0xc1740ff0 .data_addr = 0xc1744020 .bss_addr = 0xc1744280 add symbol table from file "/usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/linux/linux.ko.debug" at .text_addr = 0xc174b660 .data_addr = 0xc1759ae0 .bss_addr = 0xc175ad40 (kgdb) bt #0 doadump () at pcpu.h:159 #1 0xc05f0208 in boot (howto=0x104) at /usr/src/sys/kern/kern_shutdown.c:392 #2 0xc05f051f in panic (fmt=0xc079f247 "from debugger") at /usr/src/sys/kern/kern_shutdown.c:554 #3 0xc045eb71 in db_panic (addr=0xc0606c93, have_addr=0x0, count=0xffffffff, modif=0xd4ee2a78 "") at /usr/src/sys/ddb/db_command.c:435 #4 0xc045eb08 in db_command (last_cmdp=0xc0875a44, cmd_table=0x0, aux_cmd_tablep=0xc07f6f48, aux_cmd_tablep_end=0xc07f6f60) at /usr/src/sys/ddb/db_command.c:349 #5 0xc045ebd0 in db_command_loop () at /usr/src/sys/ddb/db_command.c:455 #6 0xc0460559 in db_trap (type=0x3, code=0x0) at /usr/src/sys/ddb/db_main.c:219 #7 0xc0606f1d in kdb_trap (type=0x3, code=0x0, tf=0xd4ee2bbc) at /usr/src/sys/kern/subr_kdb.c:401 #8 0xc076aed4 in trap (frame= {tf_fs = 0xd4ee0018, tf_es = 0xc0600010, tf_ds = 0xc07d0010, tf_edi = 0xc07d3e6a, tf_esi = 0x1, tf_ebp = 0xd4ee2bfc, tf_isp = 0xd4ee2be8, tf_ebx = 0xd4ee2c28, tf_edx = 0x0, tf_ecx = 0xc1014000, tf_eax = 0x12, tf_trapno = 0x3, tf_err = 0x0, tf_eip = 0xc0606c93, tf_cs = 0x8, tf_eflags = 0x86, tf_esp = 0xd4ee2c1c, tf_ss = 0xc05f04d1}) at /usr/src/sys/i386/i386/trap.c:576 #9 0xc0606c93 in kdb_enter (msg=0x0) at cpufunc.h:56 #10 0xc05f04d1 in panic (fmt=0xc07d3e6a "sched_rem: KSE not on run queue") at /usr/src/sys/kern/kern_shutdown.c:538 #11 0xc06004ae in sched_rem (td=0x0) at /usr/src/sys/kern/sched_ule.c:1668 #12 0xc05f5725 in setrunqueue (td=0xc1f36420) at /usr/src/sys/kern/kern_switch.c:362 #13 0xc05ffb72 in sched_wakeup (td=0xc1f36420) at /usr/src/sys/kern/sched_ule.c:1251 #14 0xc05f690c in setrunnable (td=0xc1f36420) at /usr/src/sys/kern/kern_synch.c:408 #15 0xc060c4de in sleepq_resume_thread (td=0xc1f36420, pri=0xffffffff) at /usr/src/sys/kern/subr_sleepqueue.c:632 #16 0xc060c578 in sleepq_signal (wchan=0xc190d3dc, flags=0xc1f36420, pri=0xffffffff) at /usr/src/sys/kern/subr_sleepqueue.c:662 #17 0xc05f65fb in wakeup_one (ident=0xc190d3dc) at /usr/src/sys/kern/kern_synch.c:278 #18 0xc05e172f in thread_userret (td=0xc18be160, frame=0xd4ee2d48) at /usr/src/sys/kern/kern_kse.c:1191 #19 0xc060d494 in userret (td=0xc18be160, frame=0xd4ee2d48, oticks=0x0) at /usr/src/sys/kern/subr_trap.c:118 #20 0xc076af6c in trap (frame= {tf_fs = 0xbfbf002f, tf_es = 0x280c002f, tf_ds = 0xbfbf002f, tf_edi = 0x82469b4, tf_esi = 0x8246800, tf_ebp = 0xbfbfcd48, tf_isp = 0xd4ee2d74, tf_ebx = 0x2a7bd9f8, tf_edx = 0x80a3090, tf_ecx = 0x0, tf_eax = 0x82cf000, tf_trapno = 0xc, tf_err = 0x4, tf_eip = 0x2a7a9e8b, tf_cs = 0x1f, tf_eflags = 0x10246, tf_esp = 0xbfbfcd1c, tf_ss = 0x2f}) at /usr/src/sys/i386/i386/trap.c:635 (kgdb) From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 16:32: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 9AD8116A4CE for ; Fri, 23 Jul 2004 16:32:55 +0000 (GMT) Received: from gate.multicom.lv (gate.multicom.lv [159.148.36.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3964743D39 for ; Fri, 23 Jul 2004 16:32:54 +0000 (GMT) (envelope-from andris@multicom.lv) Received: from dove (6-181.135.i-net.lv [159.148.181.135] (may be forged)) by gate.multicom.lv (8.12.11/8.12.11) with ESMTP id i6NGWoeO084976 for ; Fri, 23 Jul 2004 19:32:50 +0300 (EEST) (envelope-from andris@multicom.lv) Message-Id: <200407231632.i6NGWoeO084976@gate.multicom.lv> From: "Andris" To: Date: Fri, 23 Jul 2004 19:32:51 +0300 Organization: JSC MultiCOm MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Thread-Index: AcRw0rJcCEvuaEqJSl2DgAJZdhTkIA== X-Spam-Status: No, hits=-3.7 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on gate.multicom.lv Subject: Can't check large FS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: andris@multicom.lv List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jul 2004 16:32:55 -0000 Hi, I have a PC running 5.2.1-p9 with Promise SX6000 RAID and six=9A300Gb = Maxtor HDD's configured as RAID 0+1 so the total FS size is about 850 Gb. After hardware failure and rebuilding array I can't check my FS, fsck = always dump core with the message: cannot alloc 775104816 bytes for inoinfo fsck: /dev/pst0s1d: Segmentation fault Andris From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 16:46: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 5CA7616A4CE for ; Fri, 23 Jul 2004 16:46:02 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02AEE43D39 for ; Fri, 23 Jul 2004 16:46:02 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from [192.168.0.103] (c-24-21-18-195.client.comcast.net[24.21.18.195]) by comcast.net (sccrmhc13) with SMTP id <200407231646000160068ri3e>; Fri, 23 Jul 2004 16:46:01 +0000 From: Eric Anholt To: "George D. Gal" In-Reply-To: <00f401c470ae$84d812b0$5001a8c0@CINDY> References: <001401c4700e$91b5a470$5001a8c0@CINDY> <00f401c470ae$84d812b0$5001a8c0@CINDY> Content-Type: text/plain Message-Id: <1090601159.924.16.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 23 Jul 2004 09:45:59 -0700 Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: radeon drm code in -current 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, 23 Jul 2004 16:46:02 -0000 On Fri, 2004-07-23 at 05:13, George D. Gal wrote: > >From what I can tell no entry is created in /dev/dri/ for the card. Attached > is relevant portion from the XFree86.log > > -george > > > (II) Primary Device is: PCI 01:00:0 > (--) Assigning device section with no busID to primary device > (--) Chipset ATI Radeon Mobility 9000 (M9) Lf (AGP) found > (II) resource ranges after xf86ClaimFixedResources() call: > [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) > [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) > [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] > [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] > ...skipping... > [31] -1 0 0x0000bf40 - 0x0000bf7f (0x40) IX[B]E > [32] -1 0 0x0000bf80 - 0x0000bf9f (0x20) IX[B]E > [33] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[B](B) > [34] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) > [35] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) > (==) RADEON(0): Write-combining range (0xfcff0000,0x80000) was already clear > (==) RADEON(0): Write-combining range (0xe8000000,0x2000000) > (==) RADEON(0): Write-combining range (0xa0000,0x10000) was already clear > drmOpenDevice: minor is 0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is -1, (No such file or directory) > drmOpenDevice: open result is -1, (No such file or directory) > drmOpenDevice: Open failed > drmOpenDevice: minor is 0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is -1, (No such file or directory) > drmOpenDevice: open result is -1, (No such file or directory) > drmOpenDevice: Open failed > [drm] failed to load kernel module "radeon" > (II) RADEON(0): [drm] drmOpen failed > (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI. > (II) RADEON(0): Memory manager initialized to (0,0) (1408,5957) > (II) RADEON(0): Reserved area from (0,1050) to (1408,1052) So, the question is why you couldn't load the radeon module. Does it exist in /boot/kernel/radeon.ko? It should, it's built by default. If it is, do you get any errors in your dmesg about missing symbols, or do you not have AGP successfully loaded? -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 16:48: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 B03A116A4CE; Fri, 23 Jul 2004 16:48:11 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9027543D41; Fri, 23 Jul 2004 16:48:11 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.10/8.12.10) with ESMTP id i6NGm9OF014305; Fri, 23 Jul 2004 09:48:09 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i6NGm9ki014304; Fri, 23 Jul 2004 09:48:09 -0700 Date: Fri, 23 Jul 2004 09:48:09 -0700 From: Brooks Davis To: Maxim Sobolev Message-ID: <20040723164809.GA12747@Odin.AC.HMC.Edu> References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> <16638.32914.509773.486468@grasshopper.cs.duke.edu> <1090421941.7114.26.camel@builder02.qubesoft.com> <41012639.3020102@portaone.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Nq2Wo0NMKNjxTN9z" Content-Disposition: inline In-Reply-To: <41012639.3020102@portaone.com> User-Agent: Mutt/1.5.4i cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org cc: Andrew Gallatin Subject: Re: Excellent job on the firewire 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, 23 Jul 2004 16:48:11 -0000 --Nq2Wo0NMKNjxTN9z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 23, 2004 at 05:52:41PM +0300, Maxim Sobolev wrote: > Doug Rabson wrote: >=20 > >On Wed, 2004-07-21 at 15:41, Andrew Gallatin wrote: > > > >>Doug Rabson writes: > >>> Actually thats the only downside of dcons. It doesn't cut in until th= e=20 > >>> firewire controller attaches. It relies on the fact that the fwohci= =20 > >>> driver allows access to physical memory from any node on the bus=20 > >>> (implemeted in hardware so you can examine the memory of a hung=20 > >>> machine). The dconschat program uses this feature to access the dcons= =20 > >>> ring buffers in the target machine. > >> > >>Does remote access to physical memory require dcons to be loaded > >>on the target? > > > > > >No. The remote access to physical memory is a hardware-implemented > >feature of the firewire ohci hardware. Its enabled in fwohci_attach(). > >In the long term, I would like to restrict this a bit but right now all > >you have to have is fwohci loaded on the target machine. >=20 > It would be nice to have some sysctl which to disable such access, since= =20 > it is BAD THING[tm] from the security POV. In high security environments, they use a tube of epoxy. ;-) -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --Nq2Wo0NMKNjxTN9z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBAUFIXY6L6fI4GtQRAqLWAKC3q1TBDGvA7NMUWgb+q8oTvvtU1gCgy48/ Od+By7myC2GXEvE4ATAIU8w= =8lcY -----END PGP SIGNATURE----- --Nq2Wo0NMKNjxTN9z-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 16: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 C67CB16A4CE for ; Fri, 23 Jul 2004 16:51:44 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AE3F43D39 for ; Fri, 23 Jul 2004 16:51:44 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 7F93472DF2; Fri, 23 Jul 2004 09:51:44 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 7E40C72DB5; Fri, 23 Jul 2004 09:51:44 -0700 (PDT) Date: Fri, 23 Jul 2004 09:51:44 -0700 (PDT) From: Doug White To: Andris In-Reply-To: <200407231632.i6NGWoeO084976@gate.multicom.lv> Message-ID: <20040723095116.K1636@carver.gumbysoft.com> References: <200407231632.i6NGWoeO084976@gate.multicom.lv> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=koi8-r Content-Transfer-Encoding: QUOTED-PRINTABLE cc: freebsd-current@freebsd.org Subject: Re: Can't check large FS 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, 23 Jul 2004 16:51:44 -0000 On Fri, 23 Jul 2004, Andris wrote: > Hi, > > I have a PC running 5.2.1-p9 with Promise SX6000 RAID and six=9A300Gb Max= tor > HDD's configured as RAID 0+1 so the total FS size is about 850 Gb. > > After hardware failure and rebuilding array I can't check my FS, fsck alw= ays > dump core with the message: > > cannot alloc 775104816 bytes for inoinfo > fsck: /dev/pst0s1d: Segmentation fault Have you tried checking an alternate superblock? It looks like the primary one may be corrupted. --=20 Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 17:01: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 9CDF516A4CE for ; Fri, 23 Jul 2004 17:01:46 +0000 (GMT) Received: from fornax.vsecurity.com (64-144-2-149.client.dsl.net [64.144.2.149]) by mx1.FreeBSD.org (Postfix) with SMTP id CAD1643D64 for ; Fri, 23 Jul 2004 17:01:45 +0000 (GMT) (envelope-from ggal@vsecurity.com) Received: (qmail 26999 invoked from network); 23 Jul 2004 17:04:58 -0000 Received: from unknown (HELO CINDY) (127.0.0.1) by 0 with SMTP; 23 Jul 2004 17:04:58 -0000 Message-ID: <029f01c470d6$bb69ec90$5001a8c0@CINDY> From: "George D. Gal" To: "Eric Anholt" References: <001401c4700e$91b5a470$5001a8c0@CINDY> <1090555317.899.12.camel@leguin> <00f401c470ae$84d812b0$5001a8c0@CINDY> <1090601159.924.16.camel@leguin> Date: Fri, 23 Jul 2004 13:01:40 -0400 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 cc: freebsd-current@freebsd.org Subject: Re: radeon drm code in -current 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, 23 Jul 2004 17:01:46 -0000 Well the agp.ko and radeon.ko are both loaded, unfortunately radeon doesn't display any error messages, and reverting back to another -current kernel fixes the issue. I guess I'll have to diff the source that someone modified in the last month or so... AGP is successfully loaded. -george ----- Original Message ----- From: "Eric Anholt" To: "George D. Gal" Cc: Sent: Friday, July 23, 2004 12:45 PM Subject: Re: radeon drm code in -current > On Fri, 2004-07-23 at 05:13, George D. Gal wrote: > > >From what I can tell no entry is created in /dev/dri/ for the card. Attached > > is relevant portion from the XFree86.log > > > > -george > > > > > > (II) Primary Device is: PCI 01:00:0 > > (--) Assigning device section with no busID to primary device > > (--) Chipset ATI Radeon Mobility 9000 (M9) Lf (AGP) found > > (II) resource ranges after xf86ClaimFixedResources() call: > > [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) > > [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) > > [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] > > [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] > > ...skipping... > > [31] -1 0 0x0000bf40 - 0x0000bf7f (0x40) IX[B]E > > [32] -1 0 0x0000bf80 - 0x0000bf9f (0x20) IX[B]E > > [33] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[B](B) > > [34] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) > > [35] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) > > (==) RADEON(0): Write-combining range (0xfcff0000,0x80000) was already clear > > (==) RADEON(0): Write-combining range (0xe8000000,0x2000000) > > (==) RADEON(0): Write-combining range (0xa0000,0x10000) was already clear > > drmOpenDevice: minor is 0 > > drmOpenDevice: node name is /dev/dri/card0 > > drmOpenDevice: open result is -1, (No such file or directory) > > drmOpenDevice: open result is -1, (No such file or directory) > > drmOpenDevice: Open failed > > drmOpenDevice: minor is 0 > > drmOpenDevice: node name is /dev/dri/card0 > > drmOpenDevice: open result is -1, (No such file or directory) > > drmOpenDevice: open result is -1, (No such file or directory) > > drmOpenDevice: Open failed > > [drm] failed to load kernel module "radeon" > > (II) RADEON(0): [drm] drmOpen failed > > (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI. > > (II) RADEON(0): Memory manager initialized to (0,0) (1408,5957) > > (II) RADEON(0): Reserved area from (0,1050) to (1408,1052) > > So, the question is why you couldn't load the radeon module. Does it > exist in /boot/kernel/radeon.ko? It should, it's built by default. If > it is, do you get any errors in your dmesg about missing symbols, or do > you not have AGP successfully loaded? > > -- > Eric Anholt eta@lclark.edu > http://people.freebsd.org/~anholt/ anholt@FreeBSD.org > > > From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 17:05: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 987DD16A4CF; Fri, 23 Jul 2004 17:05:12 +0000 (GMT) Received: from av7-1-sn3.vrr.skanova.net (av7-1-sn3.vrr.skanova.net [81.228.9.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2ADE343D48; Fri, 23 Jul 2004 17:05:12 +0000 (GMT) (envelope-from manlix@demonized.net) Received: by av7-1-sn3.vrr.skanova.net (Postfix, from userid 502) id E6862380C8; Fri, 23 Jul 2004 19:52:51 +0200 (CEST) Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net [81.228.9.102]) by av7-1-sn3.vrr.skanova.net (Postfix) with ESMTP id D644537E6B; Fri, 23 Jul 2004 19:52:51 +0200 (CEST) Received: from fisk.demonized.net (h144n2fls33o834.telia.com [213.66.186.144]) by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 80B1637E4C; Fri, 23 Jul 2004 19:05:10 +0200 (CEST) Received: from beard.demonized.net (beard.demonized.net [192.168.0.2]) by fisk.demonized.net (Postfix) with SMTP id D39F760FA; Fri, 23 Jul 2004 19:05:16 +0200 (CEST) Date: Fri, 23 Jul 2004 19:05:10 +0200 From: Johan Pettersson To: "Evan Dower" Message-Id: <20040723190510.0f996c7f.manlix@demonized.net> In-Reply-To: References: X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: scottl@freebsd.org cc: current@freebsd.org Subject: Re: STABILITY [Fwd: cvs commit: src/sys/kern kern_switch.c] 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, 23 Jul 2004 17:05:12 -0000 On Fri, 23 Jul 2004 08:50:35 -0700 "Evan Dower" wrote: > Only that I don't have FULL_PREEMPTION defined in my kernel config. > I'm no kernel hacker yet ;-) > You don't need to be a kernel hacker. Just change 'define' to 'undef'. :) #define PREEMPTION -> #undef PREEMPTION From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 17:36: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 6B0A616A4CE; Fri, 23 Jul 2004 17:36:55 +0000 (GMT) Received: from hotmail.com (bay8-f42.bay8.hotmail.com [64.4.27.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6164C43D41; Fri, 23 Jul 2004 17:36:55 +0000 (GMT) (envelope-from evantd@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 23 Jul 2004 10:36:55 -0700 Received: from 67.171.32.75 by by8fd.bay8.hotmail.msn.com with HTTP; Fri, 23 Jul 2004 17:36:54 GMT X-Originating-IP: [67.171.32.75] X-Originating-Email: [evantd@hotmail.com] X-Sender: evantd@hotmail.com From: "Evan Dower" To: manlix@demonized.net Date: Fri, 23 Jul 2004 10:36:54 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 23 Jul 2004 17:36:55.0194 (UTC) FILETIME=[A59DAFA0:01C470DB] cc: scottl@freebsd.org cc: current@freebsd.org Subject: Re: STABILITY [Fwd: cvs commit: src/sys/kern kern_switch.c] 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, 23 Jul 2004 17:36:55 -0000 I know I don't have to be a kernel hacker to _do_ it, just to know about it in the first place. Of course, now I know about it, but that's just because y'all told me. And I still don't really know what it does. ;-) Anyway, is there any debugging information that would be useful for these stability issues we're currently facing. I plan on switching to a debugging kernel. What information should I send? A backtrace perhaps? Thanks again, -- Evan Dower Undergraduate, Computer Science University of Washington Public key: http://students.washington.edu/evantd/pgp-pub-key.txt Key fingerprint = D321 FA24 4BDA F82D 53A9 5B27 7D15 5A4F 033F 887D >From: Johan Pettersson >To: "Evan Dower" >CC: scottl@freebsd.org, current@freebsd.org >Subject: Re: STABILITY [Fwd: cvs commit: src/sys/kern kern_switch.c] >Date: Fri, 23 Jul 2004 19:05:10 +0200 > >On Fri, 23 Jul 2004 08:50:35 -0700 >"Evan Dower" wrote: > > > Only that I don't have FULL_PREEMPTION defined in my kernel config. > > I'm no kernel hacker yet ;-) > > > >You don't need to be a kernel hacker. Just change 'define' to 'undef'. >:) > >#define PREEMPTION -> #undef PREEMPTION _________________________________________________________________ FREE pop-up blocking with the new MSN Toolbar – get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 18:16: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 F074416A4CE for ; Fri, 23 Jul 2004 18:16:16 +0000 (GMT) Received: from smtp05.web.de (smtp05.web.de [217.72.192.209]) by mx1.FreeBSD.org (Postfix) with ESMTP id 969D243D4C for ; Fri, 23 Jul 2004 18:16:16 +0000 (GMT) (envelope-from nakal@web.de) Received: from [217.81.253.50] (helo=[217.81.253.50]) by smtp05.web.de with esmtp (TLSv1:DES-CBC3-SHA:168) (WEB.DE 4.101 #44) id 1Bo4ad-0005Tf-00 for freebsd-current@freebsd.org; Fri, 23 Jul 2004 20:16:15 +0200 From: Martin To: FreeBSD Current Content-Type: text/plain Message-Id: <1090606572.2670.15.camel@klotz.local> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 23 Jul 2004 20:16:13 +0200 Content-Transfer-Encoding: 7bit Sender: nakal@web.de X-Sender: nakal@web.de Subject: Problems with interrupts on -CURRENT? 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, 23 Jul 2004 18:16:17 -0000 Hi, I have a kernel from Mon Jul 19 01:06:15 CEST 2004 and it's terribly slow, especially while executing applications in parallel. Following symptoms: - mouse cursor is non-responsive for 3-5 seconds - hard-disk is slow and is unusually active (portupgrade needs about 15 minutes till it arrives compiling first port) - printing is slowed down a single line needs about 10 seconds - syncer is slowly counting vnodes down and needs a few seconds till it arrives at 0 I have also discovered this, after starting the print job: Jul 23 19:35:32 Interrupt storm detected on "irq7: lpt0"; throttling interrupt source Remarks about my -CURRENT kernel: I have played with some kernel settings earlier: - SCHED_4BSD, because UPDATING said so - DEVICE_POLLING is now off in this kernel I'm just reporting it, because it might be related with the instability issues, which you mention here. Any ideas what I should do now? Martin From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 18:27: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 A7D0E16A4CE; Fri, 23 Jul 2004 18:27:01 +0000 (GMT) Received: from web.portaone.com (web.portaone.com [195.70.151.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0535F43D39; Fri, 23 Jul 2004 18:27:01 +0000 (GMT) (envelope-from sobomax@portaone.com) Received: from [192.168.0.20] (portacare.portaone.com [195.140.247.242]) (authenticated bits=0) by web.portaone.com (8.12.8p2/8.12.8) with ESMTP id i6NIQrNC041654 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 Jul 2004 20:26:55 +0200 (CEST) (envelope-from sobomax@portaone.com) Message-ID: <41015865.7010807@portaone.com> Date: Fri, 23 Jul 2004 21:26:45 +0300 From: Maxim Sobolev Organization: Porta Software Ltd User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brooks Davis , phk@freebsd.org References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> <16638.32914.509773.486468@grasshopper.cs.duke.edu> <1090421941.7114.26.camel@builder02.qubesoft.com> <41012639.3020102@portaone.com> <20040723164809.GA12747@Odin.AC.HMC.Edu> In-Reply-To: <20040723164809.GA12747@Odin.AC.HMC.Edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org cc: Andrew Gallatin Subject: Re: Excellent job on the firewire 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, 23 Jul 2004 18:27:01 -0000 Brooks Davis wrote: > On Fri, Jul 23, 2004 at 05:52:41PM +0300, Maxim Sobolev wrote: > >>Doug Rabson wrote: >> >> >>>On Wed, 2004-07-21 at 15:41, Andrew Gallatin wrote: >>> >>> >>>>Doug Rabson writes: >>>> >>>>>Actually thats the only downside of dcons. It doesn't cut in until the >>>>>firewire controller attaches. It relies on the fact that the fwohci >>>>>driver allows access to physical memory from any node on the bus >>>>>(implemeted in hardware so you can examine the memory of a hung >>>>>machine). The dconschat program uses this feature to access the dcons >>>>>ring buffers in the target machine. >>>> >>>>Does remote access to physical memory require dcons to be loaded >>>>on the target? >>> >>> >>>No. The remote access to physical memory is a hardware-implemented >>>feature of the firewire ohci hardware. Its enabled in fwohci_attach(). >>>In the long term, I would like to restrict this a bit but right now all >>>you have to have is fwohci loaded on the target machine. >> >>It would be nice to have some sysctl which to disable such access, since >>it is BAD THING[tm] from the security POV. > > > In high security environments, they use a tube of epoxy. ;-) Heh, I know, Poul in his GBDE talk mentioned that something like that makes a perfect pair for each firewire connector. ;) Actually he painted even more black picture - he way saying that such direct memory access is mandatory for all firewire controllers and that there is no way to turn it off. It is nice to hear that it is off after cold boot and is possible to turn off from the device driver. -Maxim From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 19:11: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 D543816A4CE; Fri, 23 Jul 2004 19:11:10 +0000 (GMT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4EA343D2D; Fri, 23 Jul 2004 19:11:10 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from [192.168.0.103] (c-24-21-18-195.client.comcast.net[24.21.18.195]) by comcast.net (rwcrmhc11) with SMTP id <2004072319111001300kih1fe>; Fri, 23 Jul 2004 19:11:10 +0000 From: Eric Anholt To: current@FreeBSD.org Content-Type: text/plain Message-Id: <1090609869.2748.23.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 23 Jul 2004 12:11:09 -0700 Content-Transfer-Encoding: 7bit cc: ports@FreeBSD.org cc: x11@FreeBSD.org Subject: HEADSUP: X.Org conversion 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, 23 Jul 2004 19:11:11 -0000 OK, the final version of the X.Org conversion patch has hit the tree. No ports appear to be broken by the upgrade at this time. X.Org has been made the default X distribution on -current. Other versions of FreeBSD retain the same default X distribution (XFree86) but can upgrade by setting X_WINDOW_SYSTEM=xorg in /etc/make.conf. To upgrade, you must remove your XFree86 ports and install the xorg ports. It couldn't be done with portupgrade, unfortunately, because we are keeping the XFree86 ports around. To upgrade: pkg_delete -f /var/db/pkg/imake-4* /var/db/pkg/XFree86-* cd /usr/ports/x11/xorg && make install pkgdb -F If you want to keep the old XFree86 on -current, simply set X_WINDOW_SYSTEM=xfree86-4 in make.conf I am currently working on updating -current's sysinstall for X.Org. Until then it will be broken. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 19:14: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 3BE8016A4CE; Fri, 23 Jul 2004 19:14:08 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CAF443D45; Fri, 23 Jul 2004 19:14:08 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 0B8DC7A44F; Fri, 23 Jul 2004 12:14:08 -0700 (PDT) Message-ID: <4101637F.5020906@elischer.org> Date: Fri, 23 Jul 2004 12:14:07 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Maxim Sobolev References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> <16638.32914.509773.486468@grasshopper.cs.duke.edu> <1090421941.7114.26.camel@builder02.qubesoft.com> <41012639.3020102@portaone.com> In-Reply-To: <41012639.3020102@portaone.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org cc: Andrew Gallatin Subject: Re: Excellent job on the firewire 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, 23 Jul 2004 19:14:08 -0000 How about setting it up to read the screen buffer during boot.. Maxim Sobolev wrote: > Doug Rabson wrote: > >> On Wed, 2004-07-21 at 15:41, Andrew Gallatin wrote: >> >>> Doug Rabson writes: >>> > Actually thats the only downside of dcons. It doesn't cut in until >>> the > firewire controller attaches. It relies on the fact that the >>> fwohci > driver allows access to physical memory from any node on >>> the bus > (implemeted in hardware so you can examine the memory of a >>> hung > machine). The dconschat program uses this feature to access >>> the dcons > ring buffers in the target machine. >>> >>> Does remote access to physical memory require dcons to be loaded >>> on the target? >> >> >> >> No. The remote access to physical memory is a hardware-implemented >> feature of the firewire ohci hardware. Its enabled in fwohci_attach(). >> In the long term, I would like to restrict this a bit but right now all >> you have to have is fwohci loaded on the target machine. > > > It would be nice to have some sysctl which to disable such access, > since it is BAD THING[tm] from the security POV. > > -Maxim > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 19:33: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 5FF1616A4CE for ; Fri, 23 Jul 2004 19:33:19 +0000 (GMT) Received: from shockwave.systems.pipex.net (shockwave.systems.pipex.net [62.241.160.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 883F543D1F for ; Fri, 23 Jul 2004 19:33:18 +0000 (GMT) (envelope-from mark.cullen@dsl.pipex.com) Received: from laptop (81-178-70-127.dsl.pipex.com [81.178.70.127]) by shockwave.systems.pipex.net (Postfix) with SMTP id BBA171C000FB; Fri, 23 Jul 2004 20:33:16 +0100 (BST) Message-ID: <000e01c470eb$d5b215e0$f800000a@laptop> From: "Markie" To: "Martin" , "FreeBSD Current" References: <1090606572.2670.15.camel@klotz.local> Date: Fri, 23 Jul 2004 20:32:46 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: Re: Problems with interrupts on -CURRENT? 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, 23 Jul 2004 19:33:19 -0000 ----- Original Message ----- From: "Martin" To: "FreeBSD Current" Sent: Friday, July 23, 2004 7:16 PM Subject: Problems with interrupts on -CURRENT? | | Hi, | | I have a kernel from Mon Jul 19 01:06:15 CEST 2004 and it's | terribly slow, especially while executing applications in | parallel. | | Following symptoms: | - mouse cursor is non-responsive for 3-5 seconds | - hard-disk is slow and is unusually active | (portupgrade needs about 15 minutes till | it arrives compiling first port) | - printing is slowed down a single line needs about | 10 seconds | - syncer is slowly counting vnodes down and needs | a few seconds till it arrives at 0 I think I have roughly the same sort of problems... | | I have also discovered this, after starting the print job: | Jul 23 19:35:32 Interrupt storm detected on "irq7: lpt0"; throttling | interrupt source | | Remarks about my -CURRENT kernel: | I have played with some kernel settings earlier: | - SCHED_4BSD, because UPDATING said so | - DEVICE_POLLING is now off in this kernel | | I'm just reporting it, because it might be related | with the instability issues, which you mention here. | | Any ideas what I should do now? | To get over the printer thing, which has done that interrupt storm thing for rather a long time with me but never this bad, I used polling mode instead with lptcontrol. Something like lptcontrol -p ... | Martin | | | _______________________________________________ | freebsd-current@freebsd.org mailing list | http://lists.freebsd.org/mailman/listinfo/freebsd-current | To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 19:41: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 E905316A4CE for ; Fri, 23 Jul 2004 19:41:45 +0000 (GMT) Received: from psg.com (psg.com [147.28.0.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAC6143D1D for ; Fri, 23 Jul 2004 19:41:45 +0000 (GMT) (envelope-from randy@psg.com) Received: from [127.0.0.1] (helo=roam.psg.com) by psg.com with esmtp (Exim 4.34 (FreeBSD)) id 1Bo5vN-000OZQ-GS for freebsd-current@freebsd.org; Fri, 23 Jul 2004 19:41:45 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com.psg.com) by roam.psg.com with esmtp (Exim 4.40 (FreeBSD)) id 1Bo5mc-000994-Cf for freebsd-current@freebsd.org; Fri, 23 Jul 2004 09:32:42 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16641.26585.367434.326919@roam.psg.com> Date: Fri, 23 Jul 2004 09:32:41 -1000 To: FreeBSD Current Subject: ntpd cores 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, 23 Jul 2004 19:41:46 -0000 i manually run roam.psg.com# netstat -nf inet | grep 123 roam.psg.com# ntpd -g -p /var/run/ntpd.pid Jul 23 09:29:34 roam ntpd[35055]: mlockall(): Resource temporarily unavailable Jul 23 09:29:34 roam ntpd[35055]: no IPv6 interfaces found Jul 23 09:29:34 roam ntpd[35055]: bind() fd 5, family 2, port 123, addr 0.0.0.0, in_classd=0 flags=8 fails: Address already in use Jul 23 09:29:37 roam kernel: pid 35055 (ntpd), uid 0: exited on signal 11 (core dumped) clues? randy From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 19:47: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 2D5D716A4CE for ; Fri, 23 Jul 2004 19:47:19 +0000 (GMT) Received: from smtp05.web.de (smtp05.web.de [217.72.192.209]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9D1B43D41 for ; Fri, 23 Jul 2004 19:47:18 +0000 (GMT) (envelope-from nakal@web.de) Received: from [217.81.253.50] (helo=[217.81.253.50]) by smtp05.web.de with esmtp (TLSv1:DES-CBC3-SHA:168) (WEB.DE 4.101 #44) id 1Bo60j-0007tC-00; Fri, 23 Jul 2004 21:47:17 +0200 From: Martin To: Markie In-Reply-To: <000e01c470eb$d5b215e0$f800000a@laptop> References: <1090606572.2670.15.camel@klotz.local> <000e01c470eb$d5b215e0$f800000a@laptop> Content-Type: text/plain Message-Id: <1090612034.3387.5.camel@klotz.local> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 23 Jul 2004 21:47:15 +0200 Content-Transfer-Encoding: 7bit Sender: nakal@web.de X-Sender: nakal@web.de cc: FreeBSD Current Subject: Re: Problems with interrupts on -CURRENT? 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, 23 Jul 2004 19:47:19 -0000 Am Fr, den 23.07.2004 schrieb Markie um 21:32: > To get over the printer thing, which has done that interrupt storm thing for > rather a long time with me but never this bad, I used polling mode instead with > lptcontrol. Something like lptcontrol -p ... Earlier, when the kernel was more responsive, i've had interrupt storms (lpt irq) when shutting down (only after printer has been used). But printing worked in normal speed (printing a page took a few seconds), but now it takes minutes (10-20 or so). I will try to update now, but I think it can take until tomorrow. Martin From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 19:49: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 0B90616A4CE for ; Fri, 23 Jul 2004 19:49:41 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id C246043D48 for ; Fri, 23 Jul 2004 19:49:40 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from [192.168.0.103] (c-24-21-18-195.client.comcast.net[24.21.18.195]) by comcast.net (sccrmhc13) with SMTP id <20040723194939016006cjg9e>; Fri, 23 Jul 2004 19:49:40 +0000 From: Eric Anholt To: current@FreeBSD.org Content-Type: text/plain Message-Id: <1090612178.2748.39.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 23 Jul 2004 12:49:38 -0700 Content-Transfer-Encoding: 7bit Subject: Please report DRI instability 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, 23 Jul 2004 19:49:41 -0000 If have been having any issues with the DRI causing your machine to hang, please report to me what date your checkout is from, when you get the hang, and attach the following information (don't gzip, just attach the whole output if you can): dmesg your X config file (/etc/X11/xorg.conf, /etc/X11/XF86Config*) your X log file (/var/log/Xorg.0.log, /var/log/XFree86.0.log) X logs are ideally from when you had enabled the DRI, but that's not 100% necessary. Please send it as a private reply to me with Re: this subject so I can keep track. Thanks! -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 19:50: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 7989916A4CE for ; Fri, 23 Jul 2004 19:50:23 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62A6443D2D for ; Fri, 23 Jul 2004 19:50:23 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id B64917A455; Fri, 23 Jul 2004 12:50:20 -0700 (PDT) Message-ID: <41016BFC.5000708@elischer.org> Date: Fri, 23 Jul 2004 12:50:20 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: andris@multicom.lv References: <200407231632.i6NGWoeO084976@gate.multicom.lv> In-Reply-To: <200407231632.i6NGWoeO084976@gate.multicom.lv> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Can't check large FS 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, 23 Jul 2004 19:50:23 -0000 the process needs to be able to allocate more RAM. probably you need to increase its data limit. Andris wrote: >Hi, > >I have a PC running 5.2.1-p9 with Promise SX6000 RAID and six 300Gb Maxtor >HDD's configured as RAID 0+1 so the total FS size is about 850 Gb. > >After hardware failure and rebuilding array I can't check my FS, fsck always >dump core with the message: > >cannot alloc 775104816 bytes for inoinfo >fsck: /dev/pst0s1d: Segmentation fault > > >Andris > > >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 19:55: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 DF63116A4CE for ; Fri, 23 Jul 2004 19:55:32 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C4CD43D4C for ; Fri, 23 Jul 2004 19:55:32 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.0.12] (g4.samsco.home [192.168.0.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6NK1s7h072288; Fri, 23 Jul 2004 14:01:54 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <41016CEE.6060806@freebsd.org> Date: Fri, 23 Jul 2004 13:54:22 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Julian Elischer References: <200407231632.i6NGWoeO084976@gate.multicom.lv> <41016BFC.5000708@elischer.org> In-Reply-To: <41016BFC.5000708@elischer.org> 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: Can't check large FS 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, 23 Jul 2004 19:55:33 -0000 I don't know if I agree with that. I've fsck'd 1.9TB filesystems with no problem. 770MB is quite a bit to be allocating. Doug might be right about checking an alternate superblock. Scott Julian Elischer wrote: > the process needs to be able to allocate more RAM. > probably you need to increase its data limit. > > > Andris wrote: > >> Hi, >> >> I have a PC running 5.2.1-p9 with Promise SX6000 RAID and six 300Gb >> Maxtor >> HDD's configured as RAID 0+1 so the total FS size is about 850 Gb. >> >> After hardware failure and rebuilding array I can't check my FS, fsck >> always >> dump core with the message: >> >> cannot alloc 775104816 bytes for inoinfo >> fsck: /dev/pst0s1d: Segmentation fault >> >> >> Andris >> >> >> _______________________________________________ >> 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 Fri Jul 23 19:59: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 EBDF416A4CE; Fri, 23 Jul 2004 19:59:14 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E241943D2D; Fri, 23 Jul 2004 19:59:13 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id C4E697A43E; Fri, 23 Jul 2004 12:59:13 -0700 (PDT) Message-ID: <41016E11.90809@elischer.org> Date: Fri, 23 Jul 2004 12:59:13 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Scott Long References: <200407231632.i6NGWoeO084976@gate.multicom.lv> <41016BFC.5000708@elischer.org> <41016CEE.6060806@freebsd.org> In-Reply-To: <41016CEE.6060806@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Can't check large FS 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, 23 Jul 2004 19:59:15 -0000 Scott Long wrote: > I don't know if I agree with that. I've fsck'd 1.9TB filesystems with > no problem. > 770MB is quite a bit to be allocating. it's about right.. I've fsck'd 1TB filesystems and I think it depends on what blocksize you use etc. but I think it's about 700MB per TB for 16KB blocksize. it'd be good to set the result of a ulimit command > > > Doug might be right about checking an alternate superblock. > > Scott > > Julian Elischer wrote: > >> the process needs to be able to allocate more RAM. >> probably you need to increase its data limit. >> >> >> Andris wrote: >> >>> Hi, >>> >>> I have a PC running 5.2.1-p9 with Promise SX6000 RAID and six 300Gb >>> Maxtor >>> HDD's configured as RAID 0+1 so the total FS size is about 850 Gb. >>> >>> After hardware failure and rebuilding array I can't check my FS, >>> fsck always >>> dump core with the message: >>> >>> cannot alloc 775104816 bytes for inoinfo >>> fsck: /dev/pst0s1d: Segmentation fault >>> >>> >>> Andris >>> >>> >>> _______________________________________________ >>> 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 Fri Jul 23 20:10: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 84BC816A4CE; Fri, 23 Jul 2004 20:10:19 +0000 (GMT) Received: from toxic.magnesium.net (toxic.magnesium.net [207.154.84.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 745AF43D45; Fri, 23 Jul 2004 20:10:19 +0000 (GMT) (envelope-from adamw@magnesium.net) Received: by toxic.magnesium.net (Postfix, from userid 1252) id 52ABCDA870; Fri, 23 Jul 2004 13:10:19 -0700 (PDT) Date: Fri, 23 Jul 2004 16:10:19 -0400 From: Adam Weinberger To: Eric Anholt Message-ID: <20040723201019.GV14233@toxic.magnesium.net> Mail-Followup-To: Adam Weinberger , Eric Anholt , current@FreeBSD.org, ports@FreeBSD.org, x11@FreeBSD.org References: <1090609869.2748.23.camel@leguin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1090609869.2748.23.camel@leguin> X-Editor: Vim 6.2 http://www.vim.org X-Mailer: Mutt 1.5 http://www.mutt.org X-URL: http://www.vectors.cx X-ASL: 6/m/behind you User-Agent: Mutt/1.5.4i cc: ports@FreeBSD.org cc: x11@FreeBSD.org cc: current@FreeBSD.org Subject: Re: HEADSUP: X.Org conversion 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, 23 Jul 2004 20:10:19 -0000 >> (07.23.2004 @ 1511 PST): Eric Anholt said, in 1.2K: << > OK, the final version of the X.Org conversion patch has hit the tree. >> end of "HEADSUP: X.Org conversion" from Eric Anholt << Yay!! Thanks for all your work on this, Eric! # Adam -- Adam Weinberger adamw@magnesium.net || adamw@FreeBSD.org adamw@vectors.cx || adamw@gnome.org http://www.vectors.cx From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 20:18: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 0818D16A4CF for ; Fri, 23 Jul 2004 20:18:20 +0000 (GMT) Received: from gonzaga.cesar.org.br (gonzaga.cesar.org.br [200.199.23.120]) by mx1.FreeBSD.org (Postfix) with SMTP id BE01143D31 for ; Fri, 23 Jul 2004 20:18:09 +0000 (GMT) (envelope-from rss@cesar.org.br) Received: (qmail 16958 invoked from network); 23 Jul 2004 20:07:24 -0000 Received: from unknown (HELO DaeMoN.InTraNeT.CESAR.OrG.BR) (172.27.73.10) by gonzaga.cesar.org.br with SMTP; 23 Jul 2004 20:07:24 -0000 Date: Fri, 23 Jul 2004 17:20:10 -0300 (BRT) From: Rossam Souza da Silva X-X-Sender: rss@DaeMoN.InTraNeT.CESAR.OrG.BR To: Adam Weinberger In-Reply-To: <20040723201019.GV14233@toxic.magnesium.net> Message-ID: <20040723171841.O30031@DaeMoN.InTraNeT.CESAR.OrG.BR> References: <1090609869.2748.23.camel@leguin> <20040723201019.GV14233@toxic.magnesium.net> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1056890181-1090614010=:30031" cc: ports@FreeBSD.org cc: Eric Anholt cc: x11@FreeBSD.org cc: current@FreeBSD.org Subject: Re: HEADSUP: X.Org conversion 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, 23 Jul 2004 20:18:20 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1056890181-1090614010=:30031 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Hi people, the nvidia-driver package works ok with X.Org? Rossam. ------------------------------------------------------ "Das Leben auf Erden ist ein gemeiner Krieg. Wir spielen, wir k=E4mpfen, wir setzen alles auf Sieg." Megaherz ------------------------------------------------------ On Fri, 23 Jul 2004, Adam Weinberger wrote: >>> (07.23.2004 @ 1511 PST): Eric Anholt said, in 1.2K: << >> OK, the final version of the X.Org conversion patch has hit the tree. >>> end of "HEADSUP: X.Org conversion" from Eric Anholt << > > Yay!! Thanks for all your work on this, Eric! > > # Adam > > > -- > Adam Weinberger > adamw@magnesium.net || adamw@FreeBSD.org > adamw@vectors.cx || adamw@gnome.org > http://www.vectors.cx > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > --0-1056890181-1090614010=:30031-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 20:19: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 9DABA16A4CE; Fri, 23 Jul 2004 20:19:11 +0000 (GMT) Received: from toxic.magnesium.net (toxic.magnesium.net [207.154.84.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86C7E43D41; Fri, 23 Jul 2004 20:19:11 +0000 (GMT) (envelope-from adamw@magnesium.net) Received: by toxic.magnesium.net (Postfix, from userid 1252) id 63892DA849; Fri, 23 Jul 2004 13:19:11 -0700 (PDT) Date: Fri, 23 Jul 2004 16:19:11 -0400 From: Adam Weinberger To: Rossam Souza da Silva Message-ID: <20040723201911.GX14233@toxic.magnesium.net> Mail-Followup-To: Adam Weinberger , Rossam Souza da Silva , Eric Anholt , ports@FreeBSD.org, x11@FreeBSD.org, current@FreeBSD.org References: <1090609869.2748.23.camel@leguin> <20040723201019.GV14233@toxic.magnesium.net> <20040723171841.O30031@DaeMoN.InTraNeT.CESAR.OrG.BR> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040723171841.O30031@DaeMoN.InTraNeT.CESAR.OrG.BR> X-Editor: Vim 6.2 http://www.vim.org X-Mailer: Mutt 1.5 http://www.mutt.org X-URL: http://www.vectors.cx X-ASL: 6/m/behind you User-Agent: Mutt/1.5.4i cc: ports@FreeBSD.org cc: Eric Anholt cc: x11@FreeBSD.org cc: current@FreeBSD.org Subject: Re: HEADSUP: X.Org conversion 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, 23 Jul 2004 20:19:11 -0000 >> (07.23.2004 @ 1620 PST): Rossam Souza da Silva said, in 1.3K: << > > Hi people, the nvidia-driver package works ok with X.Org? > > Rossam. >> end of "Re: HEADSUP: X.Org conversion" from Rossam Souza da Silva << Worked fine for me a couple weeks ago when I did the switchover. I fried my motherboard about 6 hours later, but I maintain it was something unrelated. # Adam -- Adam Weinberger adamw@magnesium.net || adamw@FreeBSD.org adamw@vectors.cx || adamw@gnome.org http://www.vectors.cx From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 20:26: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 5F8AF16A4CE for ; Fri, 23 Jul 2004 20:26:47 +0000 (GMT) Received: from shockwave.systems.pipex.net (shockwave.systems.pipex.net [62.241.160.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E8E343D2D for ; Fri, 23 Jul 2004 20:26:46 +0000 (GMT) (envelope-from mark.cullen@dsl.pipex.com) Received: from laptop (81-178-70-127.dsl.pipex.com [81.178.70.127]) by shockwave.systems.pipex.net (Postfix) with SMTP id ADDE71C0016B; Fri, 23 Jul 2004 21:26:43 +0100 (BST) Message-ID: <003901c470f3$4e05e6f0$f800000a@laptop> From: "Markie" To: "Martin" References: <1090606572.2670.15.camel@klotz.local> <000e01c470eb$d5b215e0$f800000a@laptop> <1090612034.3387.5.camel@klotz.local> Date: Fri, 23 Jul 2004 21:26:13 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 cc: FreeBSD Current Subject: Re: Problems with interrupts on -CURRENT? 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, 23 Jul 2004 20:26:47 -0000 ----- Original Message ----- From: "Martin" To: "Markie" Cc: "FreeBSD Current" Sent: Friday, July 23, 2004 8:47 PM Subject: Re: Problems with interrupts on -CURRENT? | Am Fr, den 23.07.2004 schrieb Markie um 21:32: | | > To get over the printer thing, which has done that interrupt storm thing for | > rather a long time with me but never this bad, I used polling mode instead with | > lptcontrol. Something like lptcontrol -p ... | | Earlier, when the kernel was more responsive, i've had interrupt | storms (lpt irq) when shutting down (only after printer has been used). | But printing worked in normal speed (printing a page took a few | seconds), but now it takes minutes (10-20 or so). Yup, my printer was ok on an older current but I still saw interrupt storm messages. Its running current just before the preemption went in and it takes .... well..... i've never left it to try and print something put it that way. Fortuantly I only really use the box for a print server so putting the printer on polling mode is a quick and easy solution for me :-) | | I will try to update now, but I think it can take until tomorrow. | | Martin | | | _______________________________________________ | freebsd-current@freebsd.org mailing list | http://lists.freebsd.org/mailman/listinfo/freebsd-current | To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 20: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 0052916A4CF for ; Fri, 23 Jul 2004 20:31:10 +0000 (GMT) Received: from gate.multicom.lv (gate.multicom.lv [159.148.36.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD25543D2F for ; Fri, 23 Jul 2004 20:31:08 +0000 (GMT) (envelope-from andris@multicom.lv) Received: from dove (6-181.135.i-net.lv [159.148.181.135] (may be forged)) by gate.multicom.lv (8.12.11/8.12.11) with ESMTP id i6NKUrZF086278; Fri, 23 Jul 2004 23:30:53 +0300 (EEST) (envelope-from andris@multicom.lv) Message-Id: <200407232030.i6NKUrZF086278@gate.multicom.lv> From: "Andris" To: "'Julian Elischer'" Date: Fri, 23 Jul 2004 23:30:52 +0300 Organization: JSC MultiCOm MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Thread-Index: AcRw8/Lf95/aFow3TVWvu69msWYqzA== X-Spam-Status: No, hits=-3.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on gate.multicom.lv cc: freebsd-current@freebsd.org Subject: RE: Can't check large FS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: andris@multicom.lv List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jul 2004 20:31:10 -0000 -su-2.05b# ulimit -a core file size (blocks, -c) unlimited data seg size (kbytes, -d) 524288 file size (blocks, -f) unlimited max locked memory (kbytes, -l) unlimited max memory size (kbytes, -m) unlimited open files (-n) 11095 pipe size (512 bytes, -p) 1 stack size (kbytes, -s) 65536 cpu time (seconds, -t) unlimited max user processes (-u) 5547 virtual memory (kbytes, -v) unlimited the core size is more than 60Mb, but I can send a link to it -----Original Message----- From: Julian Elischer [mailto:julian@elischer.org] Sent: Friday, July 23, 2004 10:59 PM To: Scott Long Cc: andris@multicom.lv; freebsd-current@freebsd.org Subject: Re: Can't check large FS Scott Long wrote: > I don't know if I agree with that. I've fsck'd 1.9TB filesystems with > no problem. > 770MB is quite a bit to be allocating. it's about right.. I've fsck'd 1TB filesystems and I think it depends on what blocksize you use etc. but I think it's about 700MB per TB for 16KB blocksize. it'd be good to set the result of a ulimit command > > > Doug might be right about checking an alternate superblock. > > Scott > > Julian Elischer wrote: > >> the process needs to be able to allocate more RAM. >> probably you need to increase its data limit. >> >> >> Andris wrote: >> >>> Hi, >>> >>> I have a PC running 5.2.1-p9 with Promise SX6000 RAID and six 300Gb >>> Maxtor >>> HDD's configured as RAID 0+1 so the total FS size is about 850 Gb. >>> >>> After hardware failure and rebuilding array I can't check my FS, >>> fsck always >>> dump core with the message: >>> >>> cannot alloc 775104816 bytes for inoinfo >>> fsck: /dev/pst0s1d: Segmentation fault >>> >>> >>> Andris >>> >>> >>> _______________________________________________ >>> 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 Fri Jul 23 20:37: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 E342316A4CE; Fri, 23 Jul 2004 20:37:43 +0000 (GMT) Received: from imf24aec.mail.bellsouth.net (imf24aec.mail.bellsouth.net [205.152.59.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EB0C43D48; Fri, 23 Jul 2004 20:37:43 +0000 (GMT) (envelope-from ahze@ahze.net) Received: from [192.168.1.5] ([68.209.163.3]) by imf24aec.mail.bellsouth.netESMTP <20040723203742.FXC1737.imf24aec.mail.bellsouth.net@[192.168.1.5]>; Fri, 23 Jul 2004 16:37:42 -0400 In-Reply-To: <20040723171841.O30031@DaeMoN.InTraNeT.CESAR.OrG.BR> References: <1090609869.2748.23.camel@leguin> <20040723201019.GV14233@toxic.magnesium.net> <20040723171841.O30031@DaeMoN.InTraNeT.CESAR.OrG.BR> Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <24C1867A-DCE8-11D8-B0E4-000A958C81C6@ahze.net> Content-Transfer-Encoding: quoted-printable From: Michael Johnson Date: Fri, 23 Jul 2004 16:37:41 -0400 To: Rossam Souza da Silva X-Mailer: Apple Mail (2.618) cc: ports@FreeBSD.org cc: Adam Weinberger cc: Eric Anholt cc: x11@FreeBSD.org cc: current@FreeBSD.org Subject: Re: HEADSUP: X.Org conversion 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, 23 Jul 2004 20:37:44 -0000 Works okay for me Michael On Jul 23, 2004, at 4:20 PM, Rossam Souza da Silva wrote: > > Hi people, the nvidia-driver package works ok with X.Org? > > Rossam. > > ------------------------------------------------------ > "Das Leben auf Erden ist ein gemeiner Krieg. > Wir spielen, wir k=E4mpfen, wir setzen alles auf Sieg." > > Megaherz > ------------------------------------------------------ > > On Fri, 23 Jul 2004, Adam Weinberger wrote: > >>>> (07.23.2004 @ 1511 PST): Eric Anholt said, in 1.2K: << >>> OK, the final version of the X.Org conversion patch has hit the = tree. >>>> end of "HEADSUP: X.Org conversion" from Eric Anholt << >> >> Yay!! Thanks for all your work on this, Eric! >> >> # Adam >> >> >> -- >> Adam Weinberger >> adamw@magnesium.net || adamw@FreeBSD.org >> adamw@vectors.cx || adamw@gnome.org >> http://www.vectors.cx >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to=20 >> "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=20 > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 21:02: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 A40A016A4CF for ; Fri, 23 Jul 2004 21:02:24 +0000 (GMT) Received: from mail3.panix.com (mail3.panix.com [166.84.1.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C14243D4C for ; Fri, 23 Jul 2004 21:02:22 +0000 (GMT) (envelope-from jester@panix.com) Received: from panix2.panix.com (panix2.panix.com [166.84.1.2]) by mail3.panix.com (Postfix) with ESMTP id B810E981CE; Fri, 23 Jul 2004 17:02:21 -0400 (EDT) Received: (from jester@localhost) by panix2.panix.com (8.11.6p2-a/8.8.8/PanixN1.1) id i6NL2LH27173; Fri, 23 Jul 2004 17:02:21 -0400 (EDT) Date: Fri, 23 Jul 2004 17:02:21 -0400 From: Jesse Sheidlower To: Eric Anholt Message-ID: <20040723210221.GA17594@panix.com> References: <1090609869.2748.23.camel@leguin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1090609869.2748.23.camel@leguin> User-Agent: Mutt/1.4.2.1i cc: current@FreeBSD.org Subject: Re: HEADSUP: X.Org conversion 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, 23 Jul 2004 21:02:24 -0000 On Fri, Jul 23, 2004 at 12:11:09PM -0700, Eric Anholt wrote: > OK, the final version of the X.Org conversion patch has hit the tree. > No ports appear to be broken by the upgrade at this time. X.Org has > been made the default X distribution on -current. Other versions of > FreeBSD retain the same default X distribution (XFree86) but can upgrade > by setting X_WINDOW_SYSTEM=xorg in /etc/make.conf. Thanks very much! If one has already upgraded to the xorg ports, what is necessary so that dependencies of other modules are switched to the xorg equivalents? That is, right now, every time I upgrade a port that depends on X, I have to pkgdb -F and change XFree86-fontScalable-4.3.0 to xorg-fonts-type1-6.7.0, etc. etc. through all the different ports. Jesse Sheidlower From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 21:18: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 8AF4C16A4CE for ; Fri, 23 Jul 2004 21:18:13 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 452DB43D1D for ; Fri, 23 Jul 2004 21:18:13 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from [192.168.0.103] (c-24-21-18-195.client.comcast.net[24.21.18.195]) by comcast.net (sccrmhc13) with SMTP id <20040723211810016006dgjpe>; Fri, 23 Jul 2004 21:18:12 +0000 From: Eric Anholt To: Jesse Sheidlower In-Reply-To: <20040723210221.GA17594@panix.com> References: <1090609869.2748.23.camel@leguin> <20040723210221.GA17594@panix.com> Content-Type: text/plain Message-Id: <1090617489.2748.42.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 23 Jul 2004 14:18:09 -0700 Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: HEADSUP: X.Org conversion 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, 23 Jul 2004 21:18:13 -0000 On Fri, 2004-07-23 at 14:02, Jesse Sheidlower wrote: > On Fri, Jul 23, 2004 at 12:11:09PM -0700, Eric Anholt wrote: > > OK, the final version of the X.Org conversion patch has hit the tree. > > No ports appear to be broken by the upgrade at this time. X.Org has > > been made the default X distribution on -current. Other versions of > > FreeBSD retain the same default X distribution (XFree86) but can upgrade > > by setting X_WINDOW_SYSTEM=xorg in /etc/make.conf. > > Thanks very much! > > If one has already upgraded to the xorg ports, what is > necessary so that dependencies of other modules are switched > to the xorg equivalents? That is, right now, every time I > upgrade a port that depends on X, I have to pkgdb -F and > change XFree86-fontScalable-4.3.0 to xorg-fonts-type1-6.7.0, > etc. etc. through all the different ports. Nothing. Unless your system defaults to XFree86 (older than -current), in which case you set X_WINDOW_SYSTEM=xorg in make.conf. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 21:31: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 EC49716A4CE; Fri, 23 Jul 2004 21:31:28 +0000 (GMT) Received: from otter3.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B8F743D31; Fri, 23 Jul 2004 21:31:28 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by otter3.centtech.com (8.12.3/8.12.3) with ESMTP id i6NLVRE8030243; Fri, 23 Jul 2004 16:31:27 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4101839D.6030108@centtech.com> Date: Fri, 23 Jul 2004 16:31:09 -0500 From: Eric Anderson User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040720) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anholt References: <1090609869.2748.23.camel@leguin> In-Reply-To: <1090609869.2748.23.camel@leguin> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: ports@freebsd.org cc: x11@freebsd.org cc: current@freebsd.org Subject: Re: HEADSUP: X.Org conversion 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, 23 Jul 2004 21:31:29 -0000 Eric Anholt wrote: >OK, the final version of the X.Org conversion patch has hit the tree. >No ports appear to be broken by the upgrade at this time. X.Org has >been made the default X distribution on -current. Other versions of >FreeBSD retain the same default X distribution (XFree86) but can upgrade >by setting X_WINDOW_SYSTEM=xorg in /etc/make.conf. > Sorry if I'm in the stone age here, but I why is this better than XFree86? Just curious. Eric -- ------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Talk sense to a fool and he calls you foolish. ------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 21:42: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 4790816A4CE; Fri, 23 Jul 2004 21:42:22 +0000 (GMT) Received: from creme-brulee.marcuscom.com (rrcs-midsouth-24-172-16-118.biz.rr.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id E24B743D2D; Fri, 23 Jul 2004 21:42:21 +0000 (GMT) (envelope-from marcus@marcuscom.com) Received: from [192.168.1.4] (shumai.marcuscom.com [192.168.1.4]) i6NLflNC054190; Fri, 23 Jul 2004 17:41:47 -0400 (EDT) (envelope-from marcus@marcuscom.com) From: Joe Marcus Clarke To: Eric Anholt In-Reply-To: <1090609869.2748.23.camel@leguin> References: <1090609869.2748.23.camel@leguin> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-e5MTzB84Y0aCyKhFypj0" Organization: MarcusCom, Inc. Message-Id: <1090618937.65834.1517.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 23 Jul 2004 17:42:17 -0400 X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on creme-brulee.marcuscom.com cc: ports@freebsd.org cc: x11@freebsd.org cc: current@freebsd.org Subject: Re: HEADSUP: X.Org conversion 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, 23 Jul 2004 21:42:22 -0000 --=-e5MTzB84Y0aCyKhFypj0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2004-07-23 at 15:11, Eric Anholt wrote: > OK, the final version of the X.Org conversion patch has hit the tree.=20 > No ports appear to be broken by the upgrade at this time. X.Org has > been made the default X distribution on -current. Other versions of > FreeBSD retain the same default X distribution (XFree86) but can upgrade > by setting X_WINDOW_SYSTEM=3Dxorg in /etc/make.conf. >=20 > To upgrade, you must remove your XFree86 ports and install the xorg > ports. It couldn't be done with portupgrade, unfortunately, because we > are keeping the XFree86 ports around. To upgrade: >=20 > pkg_delete -f /var/db/pkg/imake-4* /var/db/pkg/XFree86-* > cd /usr/ports/x11/xorg && make install > pkgdb -F >=20 > If you want to keep the old XFree86 on -current, simply set > X_WINDOW_SYSTEM=3Dxfree86-4 in make.conf >=20 > I am currently working on updating -current's sysinstall for X.Org.=20 > Until then it will be broken. Please, please, please add the relevant bits to /usr/ports/UPDATING (and any relevant porter bits to /usr/ports/CHANGES). Thanks, and thanks for all your effort on getting this done. Joe --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-e5MTzB84Y0aCyKhFypj0 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBBAYY4b2iPiv4Uz4cRAiC1AKCH6Owc7+4mHb8kXrOybkAv+muDAACgoGQb 6AtLNnzlycXh6zJeo39nakY= =WceH -----END PGP SIGNATURE----- --=-e5MTzB84Y0aCyKhFypj0-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 21:44: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 385B416A4CE for ; Fri, 23 Jul 2004 21:44:29 +0000 (GMT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C87043D1D for ; Fri, 23 Jul 2004 21:44:29 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from [192.168.0.103] (c-24-21-18-195.client.comcast.net[24.21.18.195]) by comcast.net (rwcrmhc13) with SMTP id <2004072321442701500n3ijre>; Fri, 23 Jul 2004 21:44:28 +0000 From: Eric Anholt To: Eric Anderson In-Reply-To: <4101839D.6030108@centtech.com> References: <1090609869.2748.23.camel@leguin> <4101839D.6030108@centtech.com> Content-Type: text/plain Message-Id: <1090619066.2748.46.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 23 Jul 2004 14:44:26 -0700 Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: HEADSUP: X.Org conversion 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, 23 Jul 2004 21:44:29 -0000 On Fri, 2004-07-23 at 14:31, Eric Anderson wrote: > Eric Anholt wrote: > > >OK, the final version of the X.Org conversion patch has hit the tree. > >No ports appear to be broken by the upgrade at this time. X.Org has > >been made the default X distribution on -current. Other versions of > >FreeBSD retain the same default X distribution (XFree86) but can upgrade > >by setting X_WINDOW_SYSTEM=xorg in /etc/make.conf. > > > > Sorry if I'm in the stone age here, but I why is this better than > XFree86? Just curious. It's newer than our old XFree86 4.3 and supports far more hardware. It's also where current X developers are working, so it's where new features will be first. It also doesn't have the new XFree86 license. You could read xc/programs/Xserver/hw/xfree86/CHANGELOG and xc/ChangeLog to see what actually changed. (Hint: a lot.) -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 21:45: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 3771716A4CE; Fri, 23 Jul 2004 21:45:17 +0000 (GMT) Received: from toxic.magnesium.net (toxic.magnesium.net [207.154.84.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20D9643D1D; Fri, 23 Jul 2004 21:45:17 +0000 (GMT) (envelope-from adamw@magnesium.net) Received: by toxic.magnesium.net (Postfix, from userid 1252) id E3A7BDA849; Fri, 23 Jul 2004 14:45:16 -0700 (PDT) Date: Fri, 23 Jul 2004 17:45:16 -0400 From: Adam Weinberger To: Eric Anderson Message-ID: <20040723214516.GD14233@toxic.magnesium.net> Mail-Followup-To: Adam Weinberger , Eric Anderson , Eric Anholt , ports@freebsd.org, x11@freebsd.org, current@freebsd.org References: <1090609869.2748.23.camel@leguin> <4101839D.6030108@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4101839D.6030108@centtech.com> X-Editor: Vim 6.2 http://www.vim.org X-Mailer: Mutt 1.5 http://www.mutt.org X-URL: http://www.vectors.cx X-ASL: 6/m/behind you User-Agent: Mutt/1.5.4i cc: ports@freebsd.org cc: Eric Anholt cc: x11@freebsd.org cc: current@freebsd.org Subject: Re: HEADSUP: X.Org conversion 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, 23 Jul 2004 21:45:17 -0000 >> (07.23.2004 @ 1731 PST): Eric Anderson said, in 0.9K: << > Sorry if I'm in the stone age here, but I why is this better than > XFree86? Just curious. > > Eric >> end of "Re: HEADSUP: X.Org conversion" from Eric Anderson << Xorg's X is simply the next version of XFree86 X. XFree86 went splat, then stuck a feather in their hat and called it Xorg. # Adam -- Adam Weinberger adamw@magnesium.net || adamw@FreeBSD.org adamw@vectors.cx || adamw@gnome.org http://www.vectors.cx From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 21:46: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 DE40D16A4CE for ; Fri, 23 Jul 2004 21:46:41 +0000 (GMT) Received: from otter3.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C7C543D3F for ; Fri, 23 Jul 2004 21:46:41 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by otter3.centtech.com (8.12.3/8.12.3) with ESMTP id i6NLkfE8032465; Fri, 23 Jul 2004 16:46:41 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4101872E.9020604@centtech.com> Date: Fri, 23 Jul 2004 16:46:22 -0500 From: Eric Anderson User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040720) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anholt References: <1090609869.2748.23.camel@leguin> <4101839D.6030108@centtech.com> <1090619066.2748.46.camel@leguin> In-Reply-To: <1090619066.2748.46.camel@leguin> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: HEADSUP: X.Org conversion 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, 23 Jul 2004 21:46:42 -0000 Eric Anholt wrote: >On Fri, 2004-07-23 at 14:31, Eric Anderson wrote: > > >>Eric Anholt wrote: >> >> >> >>>OK, the final version of the X.Org conversion patch has hit the tree. >>>No ports appear to be broken by the upgrade at this time. X.Org has >>>been made the default X distribution on -current. Other versions of >>>FreeBSD retain the same default X distribution (XFree86) but can upgrade >>>by setting X_WINDOW_SYSTEM=xorg in /etc/make.conf. >>> >>> >>> >>Sorry if I'm in the stone age here, but I why is this better than >>XFree86? Just curious. >> >> > >It's newer than our old XFree86 4.3 and supports far more hardware. >It's also where current X developers are working, so it's where new >features will be first. It also doesn't have the new XFree86 license. >You could read xc/programs/Xserver/hw/xfree86/CHANGELOG and xc/ChangeLog >to see what actually changed. (Hint: a lot.) > Cool! So I can expect all the same stuff that works in the -snap version (4.3.99 I think?) of XFree86 to work on X.Org stuff? In particular, I need the laptop/lcd screen turning off feature that works in -snap but not the built in XFree86 with acpi. I'll give it a try and report problems.. Thanks Eric for the hard work! Eric -- ------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Talk sense to a fool and he calls you foolish. ------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 21:58: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 1260116A4CE for ; Fri, 23 Jul 2004 21:58:42 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9D0643D54 for ; Fri, 23 Jul 2004 21:58:41 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from [192.168.0.103] (c-24-21-18-195.client.comcast.net[24.21.18.195]) by comcast.net (sccrmhc13) with SMTP id <20040723215840016006be3se>; Fri, 23 Jul 2004 21:58:40 +0000 From: Eric Anholt To: Eric Anderson In-Reply-To: <4101872E.9020604@centtech.com> References: <1090609869.2748.23.camel@leguin> <4101839D.6030108@centtech.com> <1090619066.2748.46.camel@leguin> <4101872E.9020604@centtech.com> Content-Type: text/plain Message-Id: <1090619918.2748.48.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 23 Jul 2004 14:58:39 -0700 Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: HEADSUP: X.Org conversion 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, 23 Jul 2004 21:58:42 -0000 On Fri, 2004-07-23 at 14:46, Eric Anderson wrote: > Eric Anholt wrote: > > >On Fri, 2004-07-23 at 14:31, Eric Anderson wrote: > > > > > >>Eric Anholt wrote: > >> > >> > >> > >>>OK, the final version of the X.Org conversion patch has hit the tree. > >>>No ports appear to be broken by the upgrade at this time. X.Org has > >>>been made the default X distribution on -current. Other versions of > >>>FreeBSD retain the same default X distribution (XFree86) but can upgrade > >>>by setting X_WINDOW_SYSTEM=xorg in /etc/make.conf. > >>> > >>> > >>> > >>Sorry if I'm in the stone age here, but I why is this better than > >>XFree86? Just curious. > >> > >> > > > >It's newer than our old XFree86 4.3 and supports far more hardware. > >It's also where current X developers are working, so it's where new > >features will be first. It also doesn't have the new XFree86 license. > >You could read xc/programs/Xserver/hw/xfree86/CHANGELOG and xc/ChangeLog > >to see what actually changed. (Hint: a lot.) > > > > Cool! So I can expect all the same stuff that works in the -snap > version (4.3.99 I think?) of XFree86 to work on X.Org stuff? In Yes, and more. The snap is quite out of date. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 22:04: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 0964416A4CE; Fri, 23 Jul 2004 22:04:17 +0000 (GMT) Received: from mailout1.informatik.tu-muenchen.de (mailout1.informatik.tu-muenchen.de [131.159.0.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62E6143D31; Fri, 23 Jul 2004 22:04:16 +0000 (GMT) (envelope-from langd@informatik.tu-muenchen.de) Date: Sat, 24 Jul 2004 00:04:15 +0200 From: Daniel Lang To: Eric Anholt Message-ID: <20040723220415.GA63266@atrbg11.informatik.tu-muenchen.de> References: <1090609869.2748.23.camel@leguin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1090609869.2748.23.camel@leguin> X-Geek: GCS/CC d-- s: a- C++$ UBS++++$ P+++$ L- E-(---) W+++(--) N++ o K w--- O? M? V? PS+(++) PE--(+) Y+ PGP+ t++ 5+++ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r+++ y+ User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at informatik.tu-muenchen.de cc: ports@FreeBSD.org cc: x11@FreeBSD.org cc: current@FreeBSD.org Subject: Re: HEADSUP: X.Org conversion 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, 23 Jul 2004 22:04:17 -0000 Hi Eric, Eric Anholt wrote on Fri, Jul 23, 2004 at 12:11:09PM -0700: > OK, the final version of the X.Org conversion patch has hit the tree. > No ports appear to be broken by the upgrade at this time. X.Org has > been made the default X distribution on -current. Other versions of > FreeBSD retain the same default X distribution (XFree86) but can upgrade > by setting X_WINDOW_SYSTEM=xorg in /etc/make.conf. > > To upgrade, you must remove your XFree86 ports and install the xorg > ports. It couldn't be done with portupgrade, unfortunately, because we > are keeping the XFree86 ports around. To upgrade: [..] Why does "keeping the XFree86 ports around" prevent one from using portupgrade? I can specify a different port to upgrade with with -o, like (simplified): portupgrade -o x11/xorg XFree86-4.3.0_X or are there other reasons why this is not possible? Cheers, Daniel -- IRCnet: Mr-Spock - "Do you love yourself ?" - "Yes!" (Isar 12) - Daniel Lang * dl@leo.org * +49 89 2600 8122 * http://www.leo.org/~dl/ From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 22:10: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 9480C16A4CE; Fri, 23 Jul 2004 22:10:24 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27CCF43D31; Fri, 23 Jul 2004 22:10:24 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from [192.168.0.103] (c-24-21-18-195.client.comcast.net[24.21.18.195]) by comcast.net (sccrmhc12) with SMTP id <2004072322101201200nbj56e>; Fri, 23 Jul 2004 22:10:14 +0000 From: Eric Anholt To: Joe Marcus Clarke In-Reply-To: <1090618937.65834.1517.camel@shumai.marcuscom.com> References: <1090609869.2748.23.camel@leguin> <1090618937.65834.1517.camel@shumai.marcuscom.com> Content-Type: text/plain Message-Id: <1090620611.2748.61.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 23 Jul 2004 15:10:11 -0700 Content-Transfer-Encoding: 7bit cc: ports@freebsd.org cc: x11@freebsd.org cc: current@freebsd.org Subject: Re: HEADSUP: X.Org conversion 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, 23 Jul 2004 22:10:24 -0000 On Fri, 2004-07-23 at 14:42, Joe Marcus Clarke wrote: > On Fri, 2004-07-23 at 15:11, Eric Anholt wrote: > > OK, the final version of the X.Org conversion patch has hit the tree. > > No ports appear to be broken by the upgrade at this time. X.Org has > > been made the default X distribution on -current. Other versions of > > FreeBSD retain the same default X distribution (XFree86) but can upgrade > > by setting X_WINDOW_SYSTEM=xorg in /etc/make.conf. > > > > To upgrade, you must remove your XFree86 ports and install the xorg > > ports. It couldn't be done with portupgrade, unfortunately, because we > > are keeping the XFree86 ports around. To upgrade: > > > > pkg_delete -f /var/db/pkg/imake-4* /var/db/pkg/XFree86-* > > cd /usr/ports/x11/xorg && make install > > pkgdb -F > > > > If you want to keep the old XFree86 on -current, simply set > > X_WINDOW_SYSTEM=xfree86-4 in make.conf > > > > I am currently working on updating -current's sysinstall for X.Org. > > Until then it will be broken. > > Please, please, please add the relevant bits to /usr/ports/UPDATING (and > any relevant porter bits to /usr/ports/CHANGES). Thanks, and thanks for > all your effort on getting this done. Oops, fixed now. Thanks. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 22:14: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 DC86616A4CE; Fri, 23 Jul 2004 22:14:54 +0000 (GMT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9C0643D1F; Fri, 23 Jul 2004 22:14:54 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from [192.168.0.103] (c-24-21-18-195.client.comcast.net[24.21.18.195]) by comcast.net (rwcrmhc12) with SMTP id <2004072322145001400f36v1e>; Fri, 23 Jul 2004 22:14:54 +0000 From: Eric Anholt To: Daniel Lang In-Reply-To: <20040723220415.GA63266@atrbg11.informatik.tu-muenchen.de> References: <1090609869.2748.23.camel@leguin> <20040723220415.GA63266@atrbg11.informatik.tu-muenchen.de> Content-Type: text/plain Message-Id: <1090620888.2748.73.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 23 Jul 2004 15:14:49 -0700 Content-Transfer-Encoding: 7bit cc: ports@FreeBSD.org cc: x11@FreeBSD.org cc: current@FreeBSD.org Subject: Re: HEADSUP: X.Org conversion 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, 23 Jul 2004 22:14:55 -0000 On Fri, 2004-07-23 at 15:04, Daniel Lang wrote: > Hi Eric, > > Eric Anholt wrote on Fri, Jul 23, 2004 at 12:11:09PM -0700: > > OK, the final version of the X.Org conversion patch has hit the tree. > > No ports appear to be broken by the upgrade at this time. X.Org has > > been made the default X distribution on -current. Other versions of > > FreeBSD retain the same default X distribution (XFree86) but can upgrade > > by setting X_WINDOW_SYSTEM=xorg in /etc/make.conf. > > > > To upgrade, you must remove your XFree86 ports and install the xorg > > ports. It couldn't be done with portupgrade, unfortunately, because we > > are keeping the XFree86 ports around. To upgrade: > [..] > > Why does "keeping the XFree86 ports around" prevent one from > using portupgrade? I can specify a different port to > upgrade with with -o, like (simplified): > > portupgrade -o x11/xorg XFree86-4.3.0_X I mean, having portupgrade do the right thing with portupgrade -a for users of both XFree86 and X.Org. The current system seems less painful than all the portupgrade solutions I've heard proposed, as long as we keep XFree86 the default on any platform. If portmgr and re would accept us moving to X.Org on all versions of FreeBSD, and we had a good way of handling that (the repocopy and MOVED solution is pretty messy, but I'd do it if that was all we had), I'd love to see it happen. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 22:48: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 2158116A4CE; Fri, 23 Jul 2004 22:48:38 +0000 (GMT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D350C43D53; Fri, 23 Jul 2004 22:48:37 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) i6NMmYds040931; Fri, 23 Jul 2004 15:48:35 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.9p2/8.12.9/Submit) id i6NMmXtY040928; Fri, 23 Jul 2004 15:48:33 -0700 (PDT) (envelope-from dillon) Date: Fri, 23 Jul 2004 15:48:33 -0700 (PDT) From: Matthew Dillon Message-Id: <200407232248.i6NMmXtY040928@apollo.backplane.com> To: Bruce Evans References: <20040721081310.GJ22160@freebsd3.cimlogic.com.au> <20040721220405.Y2346@epsplex.bde.org> <20040722225952.S1704@epsplex.bde.org> cc: current@freebsd.org Subject: Re: nanosleep returning early 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, 23 Jul 2004 22:48:38 -0000 :> Bruce, have you seen this document: ? :> I'm not looking for a critique here. The document talks about the sleep :> overruns in various operatingg systems. There is a patch that was applied :> to DragonFly which aplies to the FreeBSD code base too. : :I just looked. It doesn't apply to FreeBSD. Adding 1 to the tick :count in tvtohz() is necessary in many places in FreeBSD (e.g., for :itimers). It happens to be just an optimizatiom in nanosleep1() for :the reasons you mentioned above (going around again fixes any :underestimate of the tick count, and overestimating by 1 avoids going :around again in most cases). :... :I believe dragonflybsd has high resolution timeouts which make the :issues different. `tick' could be somthing like 10**6 and tick counts :in microseconds would be so large that off by 1 errors in them would :be too small to measure. : :Bruce :_______________________________________________ That document doesn't really apply to us anymore either, but I keep it up because it's excellent teaching material (esp. the graphs). Yah, DFly's nanosleep now uses our SYSTIMER subsystem and is no longer limited by the granularity of the tick clock. The SYSTIMER subsystem is a general purpose, high resolution, MP-friendly, one-shot and periodic timer module. We use it for nanosleep, interrupt rate limiting, and to distribute the various system clocks (hardclock, statclock, schedclock, and profiling primarily). The callback interface kinda looks like FAST-INT in FreeBSDspeak, though the abstraction is considerably more refined in DFly. The interesting issue we have in regards to nanosleep is where to cut it off and how closely to try to match the requested timeout against the actual timeout based on the overhead of various mechanisms. If the request is too small to be worth the overhead of setting up a systimer, we try a yield instead. It's an interesting issue. I'd recommend that you guys port it, because you desparately need to rewrite your clock distribution code, but its dependant on IPI messaging (as are most DFly subsytems) and so you need the IPI messaging abstraction first. -Matt Matthew Dillon From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 23:02: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 4023716A4CE for ; Fri, 23 Jul 2004 23:02:05 +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 A2DAF43D46 for ; Fri, 23 Jul 2004 23:02:04 +0000 (GMT) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: from m2a2.dyndns.org (pD9E1E87D.dip.t-dialin.net [217.225.232.125]) 70DB435D4E for ; Sat, 24 Jul 2004 01:02:03 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id CDA6CB9E9E for ; Sat, 24 Jul 2004 01:02:02 +0200 (CEST) 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 25617-04 for ; Sat, 24 Jul 2004 01:02:01 +0200 (CEST) Received: by merlin.emma.line.org (Postfix, from userid 51) id 3D59DB8E44; Sat, 24 Jul 2004 02:07:14 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 1715CC5887; Fri, 23 Jul 2004 22:08:14 +0200 (CEST) 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 19465-04-3; Fri, 23 Jul 2004 22:08:13 +0200 (CEST) Received: by merlin.emma.line.org (Postfix, from userid 500) id 3D9B3C5884; Fri, 23 Jul 2004 22:08:13 +0200 (CEST) To: Max Laier In-Reply-To: <200407231750.32302.max@love2party.net> (Max Laier's message of "Fri, 23 Jul 2004 17:50:24 +0200") References: <200407231750.32302.max@love2party.net> From: Matthias Andree Date: Fri, 23 Jul 2004 22:08:13 +0200 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 m2a2.dyndns.org cc: freebsd-current@freebsd.org Subject: Re: xl(4) autonegotiation trouble - ng_pppoe related? 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, 23 Jul 2004 23:02:05 -0000 Max Laier writes: > Well, if your DSL-modem does not do autonegotiation you have to set > the media type manually. No I don't. In the absense of auto-negotiation on one side, the other will "read" the link beat, set the speed accordingly and pick half-duplex. This has always worked and still works, the link followed all speeds I configured on a Linux peer, whether the Linux machine offered autonegotiate or not. > It's quite obvious that you can't do pppoEthernet w/o a working > ethernet link. The link IS working: if I use rp-pppoe, a user-space PPPoE driver, it works on the same interface where ppp (with ng_pppoe) fails. ppp.conf contains these: tdsl: set device PPPoE:xl1 ... tdsl-rp: set device "!/usr/local/sbin/pppoe -U -I xl1" tdsl-rp works, tdsl does not. With disabling autoselect, the speed and duplex reading remains the same in "ifconfig", 10baseT/UTP *without* tag, but without autoselect, tdsl also works. > Anyhow, from reading the (long) PR audit trail it seems that some of > the newer xl(4) changes broke autonegotiation. Would be very helpful > if you could narrow it down somemore i.e. give a last working version. Ah well, the oldest version that compiled for me was if_xl.c 1.170. That one was broken already. The problem need not necessarily be in if_xl.c though, have there been ng_pppoe or ng_ether changes recently? Haven't had the time to check yet as it is a cumbersome process. -- Matthias Andree Encrypted mail welcome: my GnuPG key ID is 0x052E7D95 (PGP/MIME preferred) From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 23:57: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 1223416A4CE for ; Fri, 23 Jul 2004 23:57:38 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E847443D46 for ; Fri, 23 Jul 2004 23:57:37 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 81CE37A3E1 for ; Fri, 23 Jul 2004 16:57:37 -0700 (PDT) Message-ID: <4101A5F1.50407@elischer.org> Date: Fri, 23 Jul 2004 16:57:37 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: crfree/crhold mutex 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, 23 Jul 2004 23:57:38 -0000 It's held for such small times.. shouldn't it be a spinlock? From owner-freebsd-current@FreeBSD.ORG Sat Jul 24 00:07: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 4FD6416A4CE; Sat, 24 Jul 2004 00:07:14 +0000 (GMT) Received: from lakermmtao12.cox.net (lakermmtao12.cox.net [68.230.240.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DD9143D4C; Sat, 24 Jul 2004 00:07:13 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao12.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP <20040724000712.QILK15342.lakermmtao12.cox.net@dolphin.local.net>; Fri, 23 Jul 2004 20:07:12 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.12.11/8.12.11) with ESMTP id i6O07Cor032820; Fri, 23 Jul 2004 19:07:12 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.12.11/8.12.11/Submit) id i6O07Cqa032819; Fri, 23 Jul 2004 19:07:12 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <1090609869.2748.23.camel@leguin> Date: Fri, 23 Jul 2004 19:07:12 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: Eric Anholt cc: ports@freebsd.org cc: x11@freebsd.org cc: current@freebsd.org Subject: Re: HEADSUP: X.Org conversion 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: Sat, 24 Jul 2004 00:07:14 -0000 On 23-Jul-2004 Eric Anholt wrote: > OK, the final version of the X.Org conversion patch has hit the tree. > No ports appear to be broken by the upgrade at this time. X.Org has > been made the default X distribution on -current. Other versions of > FreeBSD retain the same default X distribution (XFree86) but can > upgrade by setting X_WINDOW_SYSTEM=xorg in /etc/make.conf. Hooray! Thank you! Just one question: have the inconsistencies been worked out in translating XFree86 fonts package dependencies to Xorg fonts packages? Have all ports that depend on XFree86 fonts packages been adjusted, and if so, how was this issue resolved? The problem I've seen is that there's some overlap between font package contents going from XFree86 to Xorg, mainly re: TrueType and Type1 fonts. Don't mean to sound like Mr. Rain-On-Your-Parade or anything here. :-) If these problems still need some work, I certainly understand. Just wondering what the current status is. Thanks again! -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Sat Jul 24 00:12: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 A707016A4CE; Sat, 24 Jul 2004 00:12:01 +0000 (GMT) Received: from mail.cableone.net (scanmail3.cableone.net [24.116.0.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 416CD43D58; Sat, 24 Jul 2004 00:12:01 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from vixen42.24-119-122-191.cpe.cableone.net (unverified [24.119.122.85]) by smail3.cableone.net (SurgeMail 1.9b) with ESMTP id 28473097 for multiple; Fri, 23 Jul 2004 16:56:57 -0700 Date: Fri, 23 Jul 2004 19:11:46 -0500 From: Vulpes Velox To: Eric Anderson Message-Id: <20040723191146.6a4d6cd9@vixen42.24-119-122-191.cpe.cableone.net> In-Reply-To: <4101839D.6030108@centtech.com> References: <1090609869.2748.23.camel@leguin> <4101839D.6030108@centtech.com> X-Mailer: Sylpheed-Claws 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd4.10) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Server: High Performance Mail Server - http://surgemail.com cc: ports@freebsd.org cc: Eric Anholt cc: x11@freebsd.org cc: current@freebsd.org Subject: Re: HEADSUP: X.Org conversion 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, 24 Jul 2004 00:12:01 -0000 On Fri, 23 Jul 2004 16:31:09 -0500 Eric Anderson wrote: > Eric Anholt wrote: > > >OK, the final version of the X.Org conversion patch has hit the > >tree. No ports appear to be broken by the upgrade at this time. > >X.Org has been made the default X distribution on -current. Other > >versions of FreeBSD retain the same default X distribution > >(XFree86) but can upgrade by setting X_WINDOW_SYSTEM=xorg in > >/etc/make.conf. > > > > Sorry if I'm in the stone age here, but I why is this better than > XFree86? Just curious. Other than it includes a few bug fixes and a proper acecad driver, it is not. As of currently it is just talk and what will happen with X.org and XFree86 are still up in the air. From owner-freebsd-current@FreeBSD.ORG Sat Jul 24 00:13: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 961D816A4CE for ; Sat, 24 Jul 2004 00:13:33 +0000 (GMT) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51CFE43D49 for ; Sat, 24 Jul 2004 00:13:33 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from [192.168.0.103] (c-24-21-18-195.client.comcast.net[24.21.18.195]) by comcast.net (sccrmhc11) with SMTP id <20040724001332011006f9q0e>; Sat, 24 Jul 2004 00:13:32 +0000 From: Eric Anholt To: conrads@cox.net In-Reply-To: References: Content-Type: text/plain Message-Id: <1090628010.2748.78.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 23 Jul 2004 17:13:31 -0700 Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: HEADSUP: X.Org conversion 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, 24 Jul 2004 00:13:33 -0000 On Fri, 2004-07-23 at 17:07, Conrad J. Sabatier wrote: > On 23-Jul-2004 Eric Anholt wrote: > > OK, the final version of the X.Org conversion patch has hit the tree. > > No ports appear to be broken by the upgrade at this time. X.Org has > > been made the default X distribution on -current. Other versions of > > FreeBSD retain the same default X distribution (XFree86) but can > > upgrade by setting X_WINDOW_SYSTEM=xorg in /etc/make.conf. > > Hooray! Thank you! > > Just one question: have the inconsistencies been worked out in > translating XFree86 fonts package dependencies to Xorg fonts packages? > Have all ports that depend on XFree86 fonts packages been adjusted, and > if so, how was this issue resolved? > > The problem I've seen is that there's some overlap between font package > contents going from XFree86 to Xorg, mainly re: TrueType and Type1 > fonts. > > Don't mean to sound like Mr. Rain-On-Your-Parade or anything here. :-) > If these problems still need some work, I certainly understand. Just > wondering what the current status is. Yes, it was dealt with by making those ports point at the font package that provides truetype fonts. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sat Jul 24 00:14: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 7E34E16A4CE; Sat, 24 Jul 2004 00:14:02 +0000 (GMT) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0C8843D64; Sat, 24 Jul 2004 00:14:01 +0000 (GMT) (envelope-from dantavious@comcast.net) Received: from 204.127.205.150 ([204.127.205.150]) by comcast.net (sccrmhc11) with SMTP id <20040724001400011006i1lbe>; Sat, 24 Jul 2004 00:14:01 +0000 Received: from [68.49.58.89] by 204.127.205.150; Sat, 24 Jul 2004 00:14:00 +0000 From: dantavious@comcast.net To: Michael Johnson , Rossam Souza da Silva Date: Sat, 24 Jul 2004 00:14:00 +0000 Message-Id: <072420040014.26162.4101A9C8000C5C920000663222007511509C9A0107900E9B020E0B@comcast.net> X-Mailer: AT&T Message Center Version 1 (Jun 24 2004) X-Authenticated-Sender: ZGFudGF2aW91c0Bjb21jYXN0Lm5ldA== cc: ports@FreeBSD.org cc: x11@FreeBSD.org cc: Eric Anholt cc: Adam Weinberger cc: current@FreeBSD.org Subject: Re: HEADSUP: X.Org conversion 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, 24 Jul 2004 00:14:02 -0000 Quick question. What is the best way "simplest" to configure the xorg server. r/ Derrick > Works okay for me > Michael > > > On Jul 23, 2004, at 4:20 PM, Rossam Souza da Silva wrote: > > > > > Hi people, the nvidia-driver package works ok with X.Org? > > > > Rossam. > > > > ------------------------------------------------------ > > "Das Leben auf Erden ist ein gemeiner Krieg. > > Wir spielen, wir kämpfen, wir setzen alles auf Sieg." > > > > Megaherz > > ------------------------------------------------------ > > > > On Fri, 23 Jul 2004, Adam Weinberger wrote: > > > >>>> (07.23.2004 @ 1511 PST): Eric Anholt said, in 1.2K: << > >>> OK, the final version of the X.Org conversion patch has hit the tree. > >>>> end of "HEADSUP: X.Org conversion" from Eric Anholt << > >> > >> Yay!! Thanks for all your work on this, Eric! > >> > >> # Adam > >> > >> > >> -- > >> Adam Weinberger > >> adamw@magnesium.net || adamw@FreeBSD.org > >> adamw@vectors.cx || adamw@gnome.org > >> http://www.vectors.cx > >> _______________________________________________ > >> 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" > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sat Jul 24 00:24: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 32C1516A4CE for ; Sat, 24 Jul 2004 00:24:29 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id B626D43D49 for ; Sat, 24 Jul 2004 00:24:28 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from [192.168.0.103] (c-24-21-18-195.client.comcast.net[24.21.18.195]) by comcast.net (sccrmhc12) with SMTP id <20040724002426012009cibne>; Sat, 24 Jul 2004 00:24:27 +0000 From: Eric Anholt To: dantavious@comcast.net In-Reply-To: <072420040014.26162.4101A9C8000C5C920000663222007511509C9A0107900E9B020E0B@comcast.net> References: <072420040014.26162.4101A9C8000C5C920000663222007511509C9A0107900E9B020E0B@comcast.net> Content-Type: text/plain Message-Id: <1090628664.44506.1.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 23 Jul 2004 17:24:25 -0700 Content-Transfer-Encoding: 7bit cc: Michael Johnson cc: Rossam Souza da Silva cc: current@freebsd.org Subject: Re: HEADSUP: X.Org conversion 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, 24 Jul 2004 00:24:29 -0000 On Fri, 2004-07-23 at 17:14, dantavious@comcast.net wrote: > Quick question. What is the best way "simplest" to configure the xorg server. > r/ > Derrick The simplest way is to use the same config that you used for XFree86-4. The other ways are Xorg -configure, xorgconfig, and xorgcfg. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sat Jul 24 00:25: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 4D21D16A4CE for ; Sat, 24 Jul 2004 00:25:30 +0000 (GMT) Received: from lakermmtao08.cox.net (lakermmtao08.cox.net [68.230.240.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2EB743D45 for ; Sat, 24 Jul 2004 00:25:29 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao08.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP id <20040724002529.KVKL3428.lakermmtao08.cox.net@dolphin.local.net>; Fri, 23 Jul 2004 20:25:29 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.12.11/8.12.11) with ESMTP id i6O0PSJ0064993; Fri, 23 Jul 2004 19:25:28 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.12.11/8.12.11/Submit) id i6O0PScB064992; Fri, 23 Jul 2004 19:25:28 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <1090628010.2748.78.camel@leguin> Date: Fri, 23 Jul 2004 19:25:28 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: Eric Anholt cc: current@freebsd.org Subject: Re: HEADSUP: X.Org conversion 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: Sat, 24 Jul 2004 00:25:30 -0000 On 24-Jul-2004 Eric Anholt wrote: > On Fri, 2004-07-23 at 17:07, Conrad J. Sabatier wrote: >> >> Just one question: have the inconsistencies been worked out in >> translating XFree86 fonts package dependencies to Xorg fonts >> packages? Have all ports that depend on XFree86 fonts packages >> been adjusted, and if so, how was this issue resolved? > > Yes, it was dealt with by making those ports point at the font > package that provides truetype fonts. OK, but then what about the dependencies on Type1 fonts? Those have all just been dropped? Might it not be better to ensure that both packages are listed now as dependencies? -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Sat Jul 24 00:33: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 6BDDA16A4CE for ; Sat, 24 Jul 2004 00:33:20 +0000 (GMT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C35443D31 for ; Sat, 24 Jul 2004 00:33:20 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from [192.168.0.103] (c-24-21-18-195.client.comcast.net[24.21.18.195]) by comcast.net (rwcrmhc11) with SMTP id <200407240033190130027lche>; Sat, 24 Jul 2004 00:33:19 +0000 From: Eric Anholt To: conrads@cox.net In-Reply-To: References: Content-Type: text/plain Message-Id: <1090629198.44506.3.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 23 Jul 2004 17:33:18 -0700 Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: HEADSUP: X.Org conversion 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, 24 Jul 2004 00:33:20 -0000 On Fri, 2004-07-23 at 17:25, Conrad J. Sabatier wrote: > On 24-Jul-2004 Eric Anholt wrote: > > On Fri, 2004-07-23 at 17:07, Conrad J. Sabatier wrote: > >> > >> Just one question: have the inconsistencies been worked out in > >> translating XFree86 fonts package dependencies to Xorg fonts > >> packages? Have all ports that depend on XFree86 fonts packages > >> been adjusted, and if so, how was this issue resolved? > > > > Yes, it was dealt with by making those ports point at the font > > package that provides truetype fonts. > > OK, but then what about the dependencies on Type1 fonts? Those have > all just been dropped? Might it not be better to ensure that both > packages are listed now as dependencies? Do those package actually depend on type1 fonts? If so, then they should be fixed to depend on them. I didn't investigate deeply. I'm pretty sure they just want a pretty scalable font. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sat Jul 24 00:37: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 1EAD716A4CE; Sat, 24 Jul 2004 00:37:24 +0000 (GMT) Received: from lakermmtao03.cox.net (lakermmtao03.cox.net [68.230.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DAC343D39; Sat, 24 Jul 2004 00:37:23 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao03.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP <20040724003721.OTRF17122.lakermmtao03.cox.net@dolphin.local.net>; Fri, 23 Jul 2004 20:37:21 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.12.11/8.12.11) with ESMTP id i6O0bMHU079352; Fri, 23 Jul 2004 19:37:22 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.12.11/8.12.11/Submit) id i6O0bMwP079351; Fri, 23 Jul 2004 19:37:22 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 23 Jul 2004 19:37:22 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: "Conrad J. Sabatier" cc: Eric Anholt cc: current@freebsd.org Subject: pkgdb: add dependencies option? (was Re: HEADSUP: X.Org conversion) 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: Sat, 24 Jul 2004 00:37:24 -0000 [ Cc: to portupgrade's author ] On 24-Jul-2004 Conrad J. Sabatier wrote: > > On 24-Jul-2004 Eric Anholt wrote: >> On Fri, 2004-07-23 at 17:07, Conrad J. Sabatier wrote: >>> >>> Just one question: have the inconsistencies been worked out in >>> translating XFree86 fonts package dependencies to Xorg fonts >>> packages? Have all ports that depend on XFree86 fonts packages >>> been adjusted, and if so, how was this issue resolved? >> >> Yes, it was dealt with by making those ports point at the font >> package that provides truetype fonts. > > OK, but then what about the dependencies on Type1 fonts? Those have > all just been dropped? Might it not be better to ensure that both > packages are listed now as dependencies? This just brought to light a potentially useful function that's currently lacking in pkgdb: the ability to add a new dependency to an installed package. Up until now, I've been manually adjusting Xorg font dependencies by translating XFree86-fontScaleable to xorg-fonts-type1 (although I do tend to believe that both xorg-fonts-type1 and xorg-fonts-truetype are needed to fully counterpart the XFree86 package). Unfortunately, there is currently no way to tell pkgdb to add xorg-fonts-truetype as an additional dependency to the installed packages that need it. This would be a nice addition to pkgdb's functionality, I believe. -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Sat Jul 24 00:40: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 2B53B16A4CE; Sat, 24 Jul 2004 00:40:45 +0000 (GMT) Received: from imf18aec.mail.bellsouth.net (imf18aec.mail.bellsouth.net [205.152.59.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72D8243D48; Sat, 24 Jul 2004 00:40:44 +0000 (GMT) (envelope-from ahze@ahze.net) Received: from [192.168.1.5] ([68.209.163.3]) by imf18aec.mail.bellsouth.netESMTP <20040724004044.MPCW1786.imf18aec.mail.bellsouth.net@[192.168.1.5]>; Fri, 23 Jul 2004 20:40:44 -0400 In-Reply-To: <072420040014.26162.4101A9C8000C5C920000663222007511509C9A0107900E9B020E0B@comcast.net> References: <072420040014.26162.4101A9C8000C5C920000663222007511509C9A0107900E9B020E0B@comcast.net> Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <17F97F74-DD0A-11D8-B0E4-000A958C81C6@ahze.net> Content-Transfer-Encoding: quoted-printable From: michael johnson Date: Fri, 23 Jul 2004 20:40:42 -0400 To: dantavious@comcast.net X-Mailer: Apple Mail (2.618) cc: current@FreeBSD.org cc: Eric Anholt cc: Rossam Souza da Silva cc: ports@FreeBSD.org cc: x11@FreeBSD.org cc: Adam Weinberger Subject: Re: HEADSUP: X.Org conversion 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, 24 Jul 2004 00:40:45 -0000 X -configure On Jul 23, 2004, at 8:14 PM, dantavious@comcast.net wrote: > Quick question. What is the best way "simplest" to configure the xorg=20= > server. > r/ > Derrick > > >> Works okay for me >> Michael >> >> >> On Jul 23, 2004, at 4:20 PM, Rossam Souza da Silva wrote: >> >>> >>> Hi people, the nvidia-driver package works ok with X.Org? >>> >>> Rossam. >>> >>> ------------------------------------------------------ >>> "Das Leben auf Erden ist ein gemeiner Krieg. >>> Wir spielen, wir k=E4mpfen, wir setzen alles auf Sieg." >>> >>> Megaherz >>> ------------------------------------------------------ >>> >>> On Fri, 23 Jul 2004, Adam Weinberger wrote: >>> >>>>>> (07.23.2004 @ 1511 PST): Eric Anholt said, in 1.2K: << >>>>> OK, the final version of the X.Org conversion patch has hit the=20 >>>>> tree. >>>>>> end of "HEADSUP: X.Org conversion" from Eric Anholt << >>>> >>>> Yay!! Thanks for all your work on this, Eric! >>>> >>>> # Adam >>>> >>>> >>>> -- >>>> Adam Weinberger >>>> adamw@magnesium.net || adamw@FreeBSD.org >>>> adamw@vectors.cx || adamw@gnome.org >>>> http://www.vectors.cx >>>> _______________________________________________ >>>> 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" >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to=20 >> "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=20 > "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Sat Jul 24 00:40: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 285DB16A504 for ; Sat, 24 Jul 2004 00:40:50 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71A1943D49 for ; Sat, 24 Jul 2004 00:40:49 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6O0e3c5016547; Fri, 23 Jul 2004 20:40:03 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6O0e2jV016544; Fri, 23 Jul 2004 20:40:02 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 23 Jul 2004 20:40:02 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Julian Elischer In-Reply-To: <4101A5F1.50407@elischer.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: crfree/crhold mutex 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, 24 Jul 2004 00:40:50 -0000 On Fri, 23 Jul 2004, Julian Elischer wrote: > It's held for such small times.. shouldn't it be a spinlock? With the recent change to use adaptive mutexes by default, it should effectively be a spin mutex on SMP. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Sat Jul 24 00:41: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 F07BB16A4CE for ; Sat, 24 Jul 2004 00:41:23 +0000 (GMT) Received: from lakermmtao03.cox.net (lakermmtao03.cox.net [68.230.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D70F43D45 for ; Sat, 24 Jul 2004 00:41:23 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao03.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP <20040724004121.OVCJ17122.lakermmtao03.cox.net@dolphin.local.net>; Fri, 23 Jul 2004 20:41:21 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.12.11/8.12.11) with ESMTP id i6O0fM41079388; Fri, 23 Jul 2004 19:41:22 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.12.11/8.12.11/Submit) id i6O0fMna079387; Fri, 23 Jul 2004 19:41:22 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <1090629198.44506.3.camel@leguin> Date: Fri, 23 Jul 2004 19:41:22 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: Eric Anholt cc: current@freebsd.org Subject: Re: HEADSUP: X.Org conversion 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: Sat, 24 Jul 2004 00:41:24 -0000 On 24-Jul-2004 Eric Anholt wrote: > On Fri, 2004-07-23 at 17:25, Conrad J. Sabatier wrote: >> On 24-Jul-2004 Eric Anholt wrote: >> > On Fri, 2004-07-23 at 17:07, Conrad J. Sabatier wrote: >> >> >> >> Just one question: have the inconsistencies been worked out in >> >> translating XFree86 fonts package dependencies to Xorg fonts >> >> packages? Have all ports that depend on XFree86 fonts packages >> >> been adjusted, and if so, how was this issue resolved? >> > >> > Yes, it was dealt with by making those ports point at the font >> > package that provides truetype fonts. >> >> OK, but then what about the dependencies on Type1 fonts? Those have >> all just been dropped? Might it not be better to ensure that both >> packages are listed now as dependencies? > > Do those package actually depend on type1 fonts? If so, then they > should be fixed to depend on them. > > I didn't investigate deeply. I'm pretty sure they just want a pretty > scalable font. Could be. I haven't looked that closely at them, either. :-) Rather unfortunate, isn't it, that the font packages don't have a one-to-one correspondence between the two systems. Ah well, I'm sure this will all work itself out over time. I am just *so* pleased that the transition has finally come about and the tedious running of pkgdb after every portupgrade will no longer be necessary. Thanks once again for the great work! -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Sat Jul 24 00:47: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 B7A4516A4CE for ; Sat, 24 Jul 2004 00:47:08 +0000 (GMT) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id E55E543D5E for ; Sat, 24 Jul 2004 00:47:07 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from speck.techno.pagans (c-24-21-241-225.client.comcast.net [24.21.241.225]) by mail.bitfreak.org (Postfix) with ESMTP id AF9342A477 for ; Fri, 23 Jul 2004 17:47:06 -0700 (PDT) Received: from spud (spud.techno.pagans [172.21.42.19]) by speck.techno.pagans (Postfix) with ESMTP id DDE7417023 for ; Fri, 23 Jul 2004 17:47:05 -0700 (PDT) From: "Darren Pilgrim" To: Date: Fri, 23 Jul 2004 17:46:56 -0700 Message-ID: <000b01c47117$bb62fe30$132a15ac@spud> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_000C_01C470DD.0F042630" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal Subject: Upgraded from 4.9 to 5.2.1, apm no longer works? 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, 24 Jul 2004 00:47:08 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_000C_01C470DD.0F042630 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I had RELENG_4_9 working flawlessly on an older machine. I upgraded to 5.2.1-R by means of wiping and installing from scratch, then = source-upgraded to RELENG_5_2. The computer does not have ACPI support, only APM. The kernel has "device apm" compiled in and hint.apm.0.disable=3D"0" in /boot/loader.conf, but no apm device is detected. Subsequently, `apm -e enable` fails: apm: can't open /dev/apm: No such file or directory The only reason I use APM on this machine is so that `init 0` turns the machine off rather than just halting. How do I get this functionality = back? ------=_NextPart_000_000C_01C470DD.0F042630 Content-Type: application/octet-stream; name="dmesg.output" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="dmesg.output" Copyright (c) 1992-2004 The FreeBSD Project.=0A= Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994=0A= The Regents of the University of California. All rights reserved.=0A= FreeBSD 5.2.1-RELEASE-p9 #0: Tue Jul 20 20:31:46 PDT 2004=0A= root@spud.techno.pagans:/var/speck_build/obj/usr/src/sys/SPECK=0A= Preloaded elf kernel "/boot/kernel/kernel" at 0xc06f6000.=0A= Preloaded elf module "/boot/kernel/if_fxp.ko" at 0xc06f6154.=0A= Preloaded elf module "/boot/kernel/miibus.ko" at 0xc06f6200.=0A= Preloaded elf module "/boot/kernel/fdc.ko" at 0xc06f62ac.=0A= Calibrating clock(s) ... i8254 clock: 1193228 Hz=0A= CLK_USE_I8254_CALIBRATION not specified - using default frequency=0A= Timecounter "i8254" frequency 1193182 Hz quality 0=0A= Calibrating TSC clock ... TSC clock: 332387821 Hz=0A= CPU: Overdrive Pentium II/Pentium II Xeon/Celeron (332.39-MHz 686-class = CPU)=0A= Origin =3D "GenuineIntel" Id =3D 0x1631 Stepping =3D 1=0A= = Features=3D0x183f9ff=0A= real memory =3D 125829120 (120 MB)=0A= Physical memory chunk(s):=0A= 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages)=0A= 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages)=0A= 0x0000000000826000 - 0x00000000075bdfff, 114917376 bytes (28056 pages)=0A= avail memory =3D 116793344 (111 MB)=0A= bios32: Found BIOS32 Service Directory header at 0xc00fd9e0=0A= bios32: Entry =3D 0xfd9f0 (c00fd9f0) Rev =3D 0 Len =3D 1=0A= pcibios: PCI BIOS entry at 0xf0000+0xda11=0A= pnpbios: Found PnP BIOS data at 0xc00fa330=0A= pnpbios: Entry =3D f0000:a430 Rev =3D 1.0=0A= Other BIOS signatures found:=0A= null: =0A= random: =0A= mem: =0A= Pentium Pro MTRR support enabled=0A= npx0: [FAST]=0A= npx0: on motherboard=0A= npx0: INT 16 interface=0A= pci_open(1): mode 1 addr port (0x0cf8) is 0x80000058=0A= pci_open(1a): mode1res=3D0x80000000 (0x80000000)=0A= pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there = (id=3D12378086)=0A= pcibios: BIOS version 2.10=0A= pcib0: at pcibus 0 on motherboard=0A= pci0: on pcib0=0A= pci0: physical bus=3D0=0A= found-> vendor=3D0x8086, dev=3D0x1237, revid=3D0x02=0A= bus=3D0, slot=3D0, func=3D0=0A= class=3D06-00-00, hdrtype=3D0x00, mfdev=3D0=0A= cmdreg=3D0x0106, statreg=3D0x2280, cachelnsz=3D0 (dwords)=0A= lattimer=3D0x20 (960 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0A= found-> vendor=3D0x8086, dev=3D0x7000, revid=3D0x01=0A= bus=3D0, slot=3D7, func=3D0=0A= class=3D06-01-00, hdrtype=3D0x00, mfdev=3D1=0A= cmdreg=3D0x000f, statreg=3D0x0280, cachelnsz=3D0 (dwords)=0A= lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0A= map[20]: type 4, range 32, base 0000ffa0, size 4, enabled=0A= found-> vendor=3D0x8086, dev=3D0x7010, revid=3D0x00=0A= bus=3D0, slot=3D7, func=3D1=0A= class=3D01-01-80, hdrtype=3D0x00, mfdev=3D0=0A= cmdreg=3D0x0005, statreg=3D0x0280, cachelnsz=3D0 (dwords)=0A= lattimer=3D0x20 (960 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0A= map[10]: type 1, range 32, base fb000000, size 24, enabled=0A= map[14]: type 4, range 32, base 0000fc00, size 8, enabled=0A= pci_cfgintr: can't route an interrupt to 0:11 INTA=0A= found-> vendor=3D0x100c, dev=3D0x3208, revid=3D0x14=0A= bus=3D0, slot=3D11, func=3D0=0A= class=3D03-00-00, hdrtype=3D0x00, mfdev=3D0=0A= cmdreg=3D0x0023, statreg=3D0x0400, cachelnsz=3D0 (dwords)=0A= lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0A= intpin=3Da, irq=3D11=0A= map[10]: type 3, range 32, base ffbe7000, size 12, enabled=0A= map[14]: type 4, range 32, base 0000ff40, size 5, enabled=0A= map[18]: type 1, range 32, base ff800000, size 20, enabled=0A= pci_cfgintr: can't route an interrupt to 0:17 INTA=0A= found-> vendor=3D0x8086, dev=3D0x1229, revid=3D0x05=0A= bus=3D0, slot=3D17, func=3D0=0A= class=3D02-00-00, hdrtype=3D0x00, mfdev=3D0=0A= cmdreg=3D0x0117, statreg=3D0x0290, cachelnsz=3D8 (dwords)=0A= lattimer=3D0x48 (2160 ns), mingnt=3D0x08 (2000 ns), maxlat=3D0x38 = (14000 ns)=0A= intpin=3Da, irq=3D9=0A= powerspec 1 supports D0 D1 D2 D3 current D0=0A= isab0: at device 7.0 on pci0=0A= isa0: on isab0=0A= atapci0: port 0xffa0-0xffaf at device 7.1 = on pci0=0A= ata0: reset tp1 mask=3D03 ostat0=3D50 ostat1=3D00=0A= ata0-master: stat=3D0x50 err=3D0x01 lsb=3D0x00 msb=3D0x00=0A= ata0-slave: stat=3D0x00 err=3D0x01 lsb=3D0x00 msb=3D0x00=0A= ata0: reset tp2 mask=3D03 stat0=3D50 stat1=3D00 devices=3D0x1=0A= ata0: at 0x1f0 irq 14 on atapci0=0A= ata0: [MPSAFE]=0A= ata1: reset tp1 mask=3D03 ostat0=3D50 ostat1=3D01=0A= ata1-master: stat=3D0x10 err=3D0x01 lsb=3D0x14 msb=3D0xeb=0A= ata1-slave: stat=3D0x01 err=3D0x04 lsb=3D0x14 msb=3D0xeb=0A= ata1: reset tp2 mask=3D03 stat0=3D10 stat1=3D01 = devices=3D0x4=0A= ata1: at 0x170 irq 15 on atapci0=0A= ata1: [MPSAFE]=0A= pci0: at device 11.0 (no driver attached)=0A= fxp0: port 0xff40-0xff5f mem = 0xff800000-0xff8fffff,0xffbe7000-0xffbe7fff irq 9 at device 17.0 on pci0=0A= fxp0: using memory space register mapping=0A= fxp0: Ethernet address 00:a0:c9:d8:ad:58=0A= fxp0: PCI IDs: 8086 1229 8086 0009 0005=0A= fxp0: Dynamic Standby mode is disabled=0A= miibus0: on fxp0=0A= inphy0: on miibus0=0A= inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto=0A= fxp0: bpf attached=0A= ata: ata0 already exists; skipping it=0A= ata: ata1 already exists; skipping it=0A= pnpbios: 15 devices, largest 247 bytes=0A= PNP0201: adding io range 0-0xf, size=3D0x10, align=3D0x1=0A= PNP0201: adding io range 0x80-0x90, size=3D0x11, align=3D0x1=0A= PNP0201: adding io range 0x94-0x9f, size=3D0xc, align=3D0x1=0A= PNP0201: adding io range 0xc0-0xde, size=3D0x1f, align=3D0x1=0A= PNP0201: adding io range 0x40b-0x40b, size=3D0x1, align=3D0x1=0A= PNP0201: adding io range 0x410-0x43f, size=3D0x30, align=3D0x1=0A= PNP0201: adding io range 0x481-0x483, size=3D0x3, align=3D0x1=0A= PNP0201: adding io range 0x487-0x487, size=3D0x1, align=3D0x1=0A= PNP0201: adding io range 0x489-0x48c, size=3D0x4, align=3D0x1=0A= PNP0201: adding io range 0x4d6-0x4d6, size=3D0x1, align=3D0x1=0A= PNP0201: adding dma mask 0x10=0A= pnpbios: handle 1 device ID PNP0201 (0102d041)=0A= PNP0100: adding io range 0x40-0x43, size=3D0x4, align=3D0x1=0A= PNP0100: adding irq mask 0x1=0A= pnpbios: handle 2 device ID PNP0100 (0001d041)=0A= PNP0b00: adding io range 0x70-0x71, size=3D0x2, align=3D0x1=0A= PNP0b00: adding irq mask 0x100=0A= pnpbios: handle 3 device ID PNP0b00 (000bd041)=0A= PNP0800: adding io range 0x61-0x61, size=3D0x1, align=3D0x1=0A= pnpbios: handle 4 device ID PNP0800 (0008d041)=0A= PNP0c04: adding io range 0xf0-0xff, size=3D0x10, align=3D0x1=0A= PNP0c04: adding irq mask 0x2000=0A= pnpbios: handle 5 device ID PNP0c04 (040cd041)=0A= PNP0303: adding io range 0x60-0x60, size=3D0x1, align=3D0x1=0A= PNP0303: adding io range 0x64-0x64, size=3D0x1, align=3D0x1=0A= PNP0303: adding irq mask 0x2=0A= pnpbios: handle 6 device ID PNP0303 (0303d041)=0A= pnpbios: handle 7 device ID PNP0f13 (130fd041)=0A= PNP0c01: adding fixed memory32 range 0xe8000-0xfffff, size=3D0x18000=0A= PNP0c01: adding fixed memory32 range 0-0x9ffff, size=3D0xa0000=0A= PNP0c01: adding fixed memory32 range 0x100000-0x77fffff, size=3D0x7700000=0A= PNP0c01: adding fixed memory32 range 0xfff80000-0xffffffff, = size=3D0x80000=0A= pnpbios: handle 8 device ID PNP0c01 (010cd041)=0A= PNP0a03: adding io range 0xcf8-0xcff, size=3D0x8, align=3D0x1=0A= pnpbios: handle 9 device ID PNP0a03 (030ad041)=0A= PNP0700: adding io range 0x3f2-0x3f5, size=3D0x4, align=3D0x1=0A= PNP0700: adding irq mask 0x40=0A= PNP0700: adding dma mask 0x4=0A= pnpbios: handle 10 device ID PNP0700 (0007d041)=0A= PNP0401: adding io range 0x378-0x37f, size=3D0x8, align=3D0x1=0A= PNP0401: adding io range 0x778-0x77f, size=3D0x8, align=3D0x1=0A= PNP0401: adding irq mask 0x20=0A= PNP0401: adding dma mask 0x8=0A= pnpbios: handle 11 device ID PNP0401 (0104d041)=0A= PNP0501: adding io range 0x3f8-0x3ff, size=3D0x8, align=3D0x1=0A= PNP0501: adding irq mask 0x10=0A= pnpbios: handle 12 device ID PNP0501 (0105d041)=0A= PNP0501: adding io range 0x2f8-0x2ff, size=3D0x8, align=3D0x1=0A= PNP0501: adding irq mask 0x8=0A= pnpbios: handle 13 device ID PNP0501 (0105d041)=0A= PNP0c02: adding io range 0x78-0x7f, size=3D0x8, align=3D0x1=0A= PNP0c02: adding io range 0x2e-0x2f, size=3D0x2, align=3D0x1=0A= pnpbios: handle 14 device ID PNP0c02 (020cd041)=0A= Trying Read_Port at 203=0A= Trying Read_Port at 243=0A= Trying Read_Port at 283=0A= Trying Read_Port at 2c3=0A= Trying Read_Port at 303=0A= Trying Read_Port at 343=0A= Trying Read_Port at 383=0A= Trying Read_Port at 3c3=0A= sc: sc0 already exists; skipping it=0A= vga: vga0 already exists; skipping it=0A= isa_probe_children: disabling PnP devices=0A= isa_probe_children: probing non-PnP devices=0A= orm0: