From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 00:04:23 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 467E916A479 for ; Sun, 23 Sep 2007 00:04:23 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.178]) by mx1.freebsd.org (Postfix) with ESMTP id 03C5B13C478 for ; Sun, 23 Sep 2007 00:01:50 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so1499247waf for ; Sat, 22 Sep 2007 17:01:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=3n8NS2ab3vGlvcbO1EL0ARFnAJPvZ7SHCTMUAp5Lc3o=; b=qkb8Mpxl/HQOCbJu5/YzYHvZdeTyZ9eh6JrGqPdmAmW9pZbaJa7t2flSbvzWbbzFOHfj5i1y7TosGClOJ9EVT9fSVR+3eNOx4aOyUdMWupLGJ0E7CridlOB7FVEijCgL7codCpAL7puYgAe//weB+Aa7urSvJEFfqG8q+LWpQXA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OLTf0h1HmpewktTzUJVwomwANPdXKOzEx8RwOlGOejUjK77MkclnAB58t/tzgZUoURlAehnPFWpyLGUFG4ptV8Vbsi6S0Cf4oS3KmJGBRJMDX42jVqOAJLHHtjMMfnaz1rwBB0SdxEsYHv++Lyn7WTzZDMQ8MQbkaWOKaki8/gs= Received: by 10.114.75.1 with SMTP id x1mr5135761waa.1190505710348; Sat, 22 Sep 2007 17:01:50 -0700 (PDT) Received: by 10.114.13.15 with HTTP; Sat, 22 Sep 2007 17:01:50 -0700 (PDT) Message-ID: Date: Sat, 22 Sep 2007 17:01:50 -0700 From: "Kip Macy" To: "Jack Vogel" In-Reply-To: <2a41acea0709221656n4aa62776y488c7f2da262c9f6@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0709221656n4aa62776y488c7f2da262c9f6@mail.gmail.com> Cc: "freebsd-net@freebsd.org" , FreeBSD Current Subject: Re: TX Multiqueue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 00:04:23 -0000 My ethng branch supports multiple rx and tx queues. -Kip On 9/22/07, Jack Vogel wrote: > Our newest E1000 nic, the 82575, and the Oplin 10G hardware are capable of > multiple queues both on the receive and the send side. On the receive end for > the Oplin driver the queues actually help distribute interrupts and improve > performance without any special support in the stack. > > I have been asked about multiple queues on the TX side, embedded appliance > type system builders for instance are interested I suppose for > priority queueing. > Is anyone working on this right now, and if not does this sound like something > anyone is interested in doing? > > I would like to see MQ on both TX and RX that drivers could use if able. > > Jack > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 00:04:23 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5955C16A47C for ; Sun, 23 Sep 2007 00:04:23 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.178]) by mx1.freebsd.org (Postfix) with ESMTP id 03BD813C474 for ; Sun, 23 Sep 2007 00:03:15 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so1499536waf for ; Sat, 22 Sep 2007 17:03:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=ZFjjIdFejEDpXOQPrZNxLms/pMse1n4CYRyrniErjbs=; b=QSaAXiV36ARKIn0hNkoY4th5gVLmpM1csVDVTDvF91+CEmJMqPh8A6RDPe4hWSwv9MsTZYB4tuDbuwUe+EXuKdC79XjXiIhEtH0rWQmcHrWwdnoxKa4rIRIsJjOzw0jKkAroypUhHbSqTqv480MX1VjkrX+RMWqmu1C8MfhvoFg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=mPYPk2NFo4CRMFFLrpT88y7nm+e4iG1MyJ3UF6a8gHBxqQLNCYxFZstBMrbO+vPYypnOQGH/Q5DvTBAu0VqBq+0WHfgvcUXDs5oON5n6o1jwLABBkMLZ93OvFywGAu8xjlMlSgyxyV90rf18fCkG146a/YCpO1nZBxZQsDydSxE= Received: by 10.114.197.1 with SMTP id u1mr5180688waf.1190505794113; Sat, 22 Sep 2007 17:03:14 -0700 (PDT) Received: by 10.114.13.15 with HTTP; Sat, 22 Sep 2007 17:03:14 -0700 (PDT) Message-ID: Date: Sat, 22 Sep 2007 17:03:14 -0700 From: "Kip Macy" To: "Jack Vogel" In-Reply-To: <2a41acea0709221647o3cdcb72pf6194c54782c61fb@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <01c801c7fc7a$696ab900$0c00a8c0@Artem> <2a41acea0709211359w37ba779dsec94de504a9f4a9c@mail.gmail.com> <019101c7fd3d$cd15f870$0c00a8c0@Artem> <2a41acea0709221647o3cdcb72pf6194c54782c61fb@mail.gmail.com> Cc: Artem Kuchin , freebsd-current@freebsd.org Subject: Re: TSP on em makes send of streams very slow X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 00:04:23 -0000 On 9/22/07, Jack Vogel wrote: > On 9/22/07, Artem Kuchin wrote: > > > TSO is for some environments, it isn't gonna be useful at 100Mb > > > (which you are), it can be useful at 1Gb but not always, when you get > > > to 10G its > > > a HUGE benefit. > > > > > > Just cuz you can shoot yourself in the foot doesn't mean the gun has a > > > problem :) > > > > But wait, i did not shoot myself. I have been shot by the driver w/o any > > preliminary warning. TSO4 was enabled by DEFAULT (i did not enable it), > > so anybody can be in my place if used the same driver on the similar hardware > > (which is plenty). > > > > So, i think this is a problem which really need to be addressed. > > It is on by default because it the majority of cases its a benefit, you > found it to be a problem and turned it off, your problem is solved. > > I admit, at one point I considered disabling it automatically for anything > under Gig speed, but a large community has used this driver with this > feature for over a year, no one has lobbied to have to disabled, so I > have not. > > If there are others who think this would be a good idea, speak up, and > I will do so. I don't think many people will be hooking it up to 100Mbit. However, disabling TSO if media negotiates 100Mbit seems like an easy enough fix. -Kip From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 00:14:59 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C030A16A419 for ; Sun, 23 Sep 2007 00:14:59 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id D4B4E13C457; Sun, 23 Sep 2007 00:14:54 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F5AFFE.1060508@FreeBSD.org> Date: Sun, 23 Sep 2007 02:14:54 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Jack Vogel References: <01c801c7fc7a$696ab900$0c00a8c0@Artem> <2a41acea0709211359w37ba779dsec94de504a9f4a9c@mail.gmail.com> <019101c7fd3d$cd15f870$0c00a8c0@Artem> <2a41acea0709221647o3cdcb72pf6194c54782c61fb@mail.gmail.com> In-Reply-To: <2a41acea0709221647o3cdcb72pf6194c54782c61fb@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Artem Kuchin , freebsd-current@freebsd.org Subject: Re: TSP on em makes send of streams very slow X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 00:14:59 -0000 Jack Vogel wrote: > On 9/22/07, Artem Kuchin wrote: >>> TSO is for some environments, it isn't gonna be useful at 100Mb >>> (which you are), it can be useful at 1Gb but not always, when you get >>> to 10G its >>> a HUGE benefit. >>> >>> Just cuz you can shoot yourself in the foot doesn't mean the gun has a >>> problem :) >> But wait, i did not shoot myself. I have been shot by the driver w/o any >> preliminary warning. TSO4 was enabled by DEFAULT (i did not enable it), >> so anybody can be in my place if used the same driver on the similar hardware >> (which is plenty). >> >> So, i think this is a problem which really need to be addressed. > > It is on by default because it the majority of cases its a benefit, you > found it to be a problem and turned it off, your problem is solved. > > I admit, at one point I considered disabling it automatically for anything > under Gig speed, but a large community has used this driver with this > feature for over a year, no one has lobbied to have to disabled, so I > have not. > > If there are others who think this would be a good idea, speak up, and > I will do so. > > Cheers, > > Jack > _______________________________________________ > 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" > > Something is clearly going very wrong for performance to be that bad, so I think you need to work out why that is happening. Is it a problem with that particular card model, or what? Kris From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 01:08:41 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CB1516A417; Sun, 23 Sep 2007 01:08:41 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.freebsd.org (Postfix) with ESMTP id EECA013C468; Sun, 23 Sep 2007 01:08:40 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.1/8.14.1) id l8N18dlt031616; Sat, 22 Sep 2007 20:08:39 -0500 (CDT) (envelope-from dan) Date: Sat, 22 Sep 2007 20:08:39 -0500 From: Dan Nelson To: Darren Reed Message-ID: <20070923010839.GL7562@dan.emsphone.com> References: <20070921102946.T11189@borg> <46F415BF.9010500@FreeBSD.org> <20070921140550.D96923@thebighonker.lerctr.org> <46F41CFF.6080108@FreeBSD.org> <46F58799.1030702@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46F58799.1030702@freebsd.org> X-OS: FreeBSD 7.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org, Larry Rosenman Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 01:08:41 -0000 In the last episode (Sep 22), Darren Reed said: > Kris Kennaway wrote: >> Larry Rosenman wrote: >>> On Fri, 21 Sep 2007, Kris Kennaway wrote: >>>> Larry Rosenman wrote: >>>>> I'm a heavy ZFS user, and got the following panic on 2007-09-18 >>>>> source/world: >>>> >>>> This is a FAQ, please see the archives (you need to increase the >>>> vm.kmem_size to provide more memory to ZFS). >>> >>> I thought that was only for i386, and it hadn't been an issue before. >> >> Nope. It is also load-dependent. > > So I just received this courtesy of ZFS: > panic: kmem_malloc(131072): kmem_map too small: 343027712 total allocated > cpuid = 0 > KDB: enter: panic > > This was with these settings in loader.conf: > vm.kmem_size=419430400 > vm.kmem_size_max=419430400 > vfs.zfs.arc_max=409715200 > > (That's 400M, 400M and 40M, respectively.) That's actually 400M, 400M, and 390M; count the digits :) If you want 400M, just put "400M" in loader.conf. Makes it a lot easier to read, and harder to get wrong. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 01:14:46 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F47116A418 for ; Sun, 23 Sep 2007 01:14:46 +0000 (UTC) (envelope-from don@siad.net) Received: from mars.siad.net (mars.siad.net [69.3.214.122]) by mx1.freebsd.org (Postfix) with ESMTP id 0996113C459 for ; Sun, 23 Sep 2007 01:14:46 +0000 (UTC) (envelope-from don@siad.net) Received: from [69.3.214.123] (rover.siad.net [69.3.214.123]) (authenticated bits=0) by mars.siad.net (8.13.8/8.13.1) with ESMTP id l8N0rims048194 for ; Sat, 22 Sep 2007 17:53:45 -0700 (PDT) (envelope-from don@siad.net) Message-ID: <46F5B918.5040804@siad.net> Date: Sat, 22 Sep 2007 17:53:44 -0700 From: "Don L. Belcher" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20070522 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-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-2.0b1 (mars.siad.net [69.3.214.122]); Sat, 22 Sep 2007 17:53:45 -0700 (PDT) Subject: mini-pci card X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 01:14:46 -0000 This worked around about march of this year. It seems to be failing configuration of prefetch decode. 7.0-CURRENT FreeBSD pcib3@pci2:6:0: class=0x060400 card=0x00000000 chip=0x01001668 rev=0x11 hdr=0x01 vendor = 'Actiontec Electronics Inc.' device = '0304 PCI to PCI Bridge' class = bridge subclass = PCI-PCI IS: pcib3: at device 6.0 on pci2 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode 0x3000-0x3fff pcib3: memory decode 0xf0600000-0xf07fffff pcib3: no prefetched decode pci3: on pcib3 pci3: physical bus=3 SHOULD BE: pcib3: at device 6.0 on pci2 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode 0x3000-0x3fff pcib3: memory decode 0xf0600000-0xf07fffff pcib3: prefetched decode 0xfff00000-0xfffff From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 02:28:22 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08BB916A41A for ; Sun, 23 Sep 2007 02:28:22 +0000 (UTC) (envelope-from prvs=17867fa6c9=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 9FBB613C455 for ; Sun, 23 Sep 2007 02:28:21 +0000 (UTC) (envelope-from prvs=17867fa6c9=killing@multiplay.co.uk) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk; s=Multiplay; t=1190513324; x=1191118124; q=dns/txt; h=Received: Message-ID:From:To:Cc:References:Subject:Date:MIME-Version: Content-Type:Content-Transfer-Encoding; bh=Qf2vtK16GT0t0wU/H6iex b0OiUVQ8VcxkMp0WYOLDw8=; b=NZdJOGchSLd9hAhdsbBpbSBMZDNcb4HIYP78q FS1kAfjmy5KvypRrhSpXtOuHpZadGNUj387y6ZtRQbMH/AvTwf0v8FOC5Qxnlm8f 6g/v/sWBMa87h5xt0sY07+vX9ESAperEeKSJlY/TeM2wa/leyainD6GvZ0yfX+I9 N6OKV4= X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on core6.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-14.7 required=6.0 tests=BAYES_00, USER_IN_WHITELIST, USER_IN_WHITELIST_TO autolearn=ham version=3.1.8 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v9.6.0) with ESMTP id md50004235363.msg for ; Sun, 23 Sep 2007 03:08:39 +0100 Message-ID: <027501c7fd86$a13f8c90$b6db87d4@multiplay.co.uk> From: "Steven Hartland" To: "Jack Vogel" , "Artem Kuchin" References: <01c801c7fc7a$696ab900$0c00a8c0@Artem><2a41acea0709211359w37ba779dsec94de504a9f4a9c@mail.gmail.com><019101c7fd3d$cd15f870$0c00a8c0@Artem> <2a41acea0709221647o3cdcb72pf6194c54782c61fb@mail.gmail.com> Date: Sun, 23 Sep 2007 03:08:27 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 212.135.219.182 X-Return-Path: prvs=17867fa6c9=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-current@freebsd.org X-Spam-Processed: mail1.multiplay.co.uk, Sun, 23 Sep 2007 03:08:40 +0100 X-MDAV-Processed: mail1.multiplay.co.uk, Sun, 23 Sep 2007 03:08:44 +0100 Cc: freebsd-current@freebsd.org Subject: Re: TSP on em makes send of streams very slow X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 02:28:22 -0000 ----- Original Message ----- From: "Jack Vogel" > It is on by default because it the majority of cases its a benefit, you > found it to be a problem and turned it off, your problem is solved. I think the issue here is that when we install a machine we expect it to just work TM, we dont go looking at all the possible options for something that "may" cause an issue. Yes he spotted there was a problem, investigated and found a solution but I'd guess this took a fair amount of time and hence is not something we ant others to have to go through. > I admit, at one point I considered disabling it automatically for anything > under Gig speed, but a large community has used this driver with this > feature for over a year, no one has lobbied to have to disabled, so I > have not. Much as this sounds like an option if TSP doesnt provide any real gains at 100Mb, the main question is why should enabling this option have such a massive detrimental effect on performance? Surely this is work investigating and fixing? The issue could be manifesting itself in other ways on 1Gb and 10Gb could it not? So a fix could provide additional benefits. The key issue I suppose is to understand why there should be such a drop in performance, hardware, driver or OS issue? Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 02:49:34 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C10D416A418; Sun, 23 Sep 2007 02:49:34 +0000 (UTC) (envelope-from cnst@FreeBSD.org) Received: from mojo.ru (mojo.ru [84.252.152.63]) by mx1.freebsd.org (Postfix) with ESMTP id 3292413C447; Sun, 23 Sep 2007 02:49:33 +0000 (UTC) (envelope-from cnst@FreeBSD.org) Received: from [192.168.0.16] (nc-76-4-28-21.dhcp.embarqhsd.net [76.4.28.21]) (authenticated bits=0) by mojo.ru (8.12.11.20060308/8.12.10) with ESMTP id l8N2nY0v016657 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 23 Sep 2007 06:49:41 +0400 Message-ID: <46F5D427.9020504@FreeBSD.org> Date: Sat, 22 Sep 2007 22:49:11 -0400 From: "Constantine A. Murenin" Organization: Google Summer of Code 2007 Student @ The FreeBSD Project User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-gb, en-gb-oed, en, en-us, ru, ru-ru, ru-su MIME-Version: 1.0 To: "Constantine A. Murenin" References: <200709132302.l8DN2Tv5076033@repoman.freebsd.org> <46E9FC0C.70607@FreeBSD.org> In-Reply-To: <46E9FC0C.70607@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@FreeBSD.org, Alexander Leidinger , Shteryana Shopova , freebsd-current@FreeBSD.org, "Constantine A. Murenin" Subject: Re: GSoC2007: cnst-sensors.2007-09-13.patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 02:49:34 -0000 Dear freebsd-{current,hardware}@, Let me a give a few guiding comments for potential testers and integrators of this patch. First of all, let's start with a common pitfall: * You have to update your /boot/device.hints, and then reboot. In no other circumstance will the isa-based lm(4) or it(4) be probed. Manually updating the hints with kenv(1) after the system has already been booted has no effect on the isa modules. * Second, since this patch is not only about the framework, but about some Super I/O Hardware Monitoring drivers too, let me once again reiterate on the popularity of the chips that are supported by the lm(4) and it(4) drivers. I have four boxes here, all run FreeBSD and OpenBSD. Let's see what Super I/O chips they have: * AOpen AX4G-N (845G + Intel Pentium 4 Northwood): Winbond W83627HF-AM * ASUS Terminator C3 (VIA CLE266 + VIA C3 Samuel 2): Winbond W83627THF-A * ASUS V3-P5G965 (G965 + Intel Core 2 Duo Allendale): Winbond W83627DHG-A * PCCHIPS V21G (VIA CN700 + VIA C7 Esther): ITE IT8716F-S Out of the above, Winbond W83627* are supported by lm(4), and ITE IT8716F-S by it(4). (Obviously, the drivers support other chips, too. ;) In general, most boards from Taiwanese manufacturers have either a Winbond or ITE Tech Super I/O chips, supported by lm(4) and it(4) respectively; e.g. if you have a Gigabyte or ASUS mainboard, then the probability of you having one of these chips is quite substantial -- consider testing the patch if you are interested. Supermicro boards also feature Winbond chips quite often -- feel free to test. Intel-branded boards, on the other hand, often use an SMBus-interfaced Hardware Monitoring solution. I have none of those boards, so none of the SMBus drivers were ported to FreeBSD yet. Anyhow, I hope this information helps some potential testers and integrators. ;) Cheers, Constantine. On 13/09/2007 23:12, Constantine A. Murenin wrote: > Dear freebsd-{arch,current,hackers}@, > > On this 256th day of 2007, it is my great pleasure to announce the > completion of my GSoC2007 project on porting the sysctl hardware sensors > framework from OpenBSD to FreeBSD. > > All of the things that were planned to be ported from OpenBSD base > system to FreeBSD have now been ported. > > The userland part of the framework is entirely source-code compatible > with OpenBSD. For example, you can take OpenBSD's stock sensorsd(8), > and it'll compile and work on FreeBSD with no modifications. > > The framework is quite self-contained, so I think it is a safe bet to at > least try to get it into the tree even at this point, when the code > freeze is taking place in preparation for RELENG_7 branching. > > Therefore, I hereby request that this patch be considered for immediate > inclusion into FreeBSD's main CVS repository. > > The complete CVS patch is available from: > http://mojo.ru/us/GSoC2007.cnst-sensors.2007-09-13.patch.gz > > For backup purposes, a copy of this CVS patch is also available in my > perforce branch, although it has tainted $P4$ tags in individual files, > so use perforce as a last resort: > http://p4web.freebsd.org//depot/projects/soc2007/cnst-sensors/cnst-sensors.2007-09-13.patch > > > Exact details on how to apply and test the patch are available in my > LiveJournal, along with certain other comments: > > http://cnst.livejournal.com/38421.html#directions > > If you have an Intel Core 2 processor, or a Winbond or ITE Tech Super > I/O chip on your board, then please test and report back on how your > tests went. > > Best regards, > Constantine Aleksandrovich Murenin, > Google Summer of Code 2007 Student @ The FreeBSD Project. ;) > > > On 13/09/2007 19:02, Constantine A. Murenin wrote: > >> http://perforce.freebsd.org/chv.cgi?CH=126384 >> >> Change 126384 by cnst@dale on 2007/09/13 23:01:55 >> >> On this 256th day of 2007, it is my great pleasure to >> present a feature-complete port of the hardware sensors >> framework from OpenBSD to FreeBSD. >> >> Below is a complete `cvs diff` of cnst-sensors GSoC2007 >> project as of 2007-256. >> >> It includes the following components, listed below in >> the very same order as they are appearing in this diff: >> >> * sample configuration file for sensorsd >> * rc(8) script and glue code for sensorsd(8) >> * sysctl(3) doc fixes for CTL_HW tree >> * sysctl(3) documentation for hardware sensors >> * sysctl(8) documentation for hardware sensors >> * assorted KNF and bug-fixes for sysctl(8) >> * support for the sensor structure for sysctl(8) >> * coretemp(4) documentation >> * it(4) documentation >> * lm(4) documentation >> * rc.conf(5) documentation for starting sensorsd(8) >> * sensor_attach(9) et al documentation >> * coretemp(4) conversion to the hw.sensors framework >> * it(4) isa driver ported from OpenBSD >> * lm(4) isa driver ported from OpenBSD >> * /sys/kern/kern_sensors.c >> o sensor_attach(9) API for drivers to register ksensors >> o sensor_task_register(9) API for the update task >> o sysctl(3) glue code >> o hw.sensors shadow tree for sysctl(8) internal magic >> * assorted KNF and bug-fixes for /sys/kern/kern_sysctl.c >> * it(4) module for testing sensor_attach/detach et al >> * lm(4) module for testing sensor_attach/detach et al >> * >> * assorted bug-fixes and HW_SENSORS definition for >> * sensors display for systat(1), including all documentation >> * sensorsd(8) and all applicable documentation >> >> The userland part of the framework is entirely source-code >> compatible with OpenBSD 4.1, 4.2 and -current as of today. >> >> All sensor readings can be viewed with `sysctl hw.sensors`, >> monitored in semi-realtime with `systat -sensors` and also >> logged with `sensorsd`. Third-party tools, for example a >> plug-in for nagios, are also available. A separate patch >> for ports/sysutils/symon will be provided upon request. >> >> Submitted by: cnst@FreeBSD.org (Constantine A. Murenin) >> Obtained from: generated by sensors.cvsdiff.sh from >> //depot/projects/soc2007/cnst-sensors/ >> Sponsored by: Google Summer of Code 2007 >> >> >> Obtained from: >> http://mojo.ru/us/GSoC2007.cnst-sensors.2007-09-13.patch.gz >> >> Details at: http://cnst.livejournal.com/38421.html >> >> Affected files ... >> >> .. >> //depot/projects/soc2007/cnst-sensors/cnst-sensors.2007-09-13.patch#1 add >> >> Differences ... >> > From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 03:52:10 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 721A016A41B for ; Sun, 23 Sep 2007 03:52:10 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with SMTP id 22BCB13C455 for ; Sun, 23 Sep 2007 03:52:09 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 17370 invoked by uid 399); 23 Sep 2007 03:52:09 -0000 Received: from localhost (HELO slave.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 23 Sep 2007 03:52:09 -0000 X-Originating-IP: 127.0.0.1 Date: Sat, 22 Sep 2007 20:52:07 -0700 (PDT) From: Doug Barton To: "David E. Thiel" In-Reply-To: <20070922233709.GG59731@redundancy.redundancy.org> Message-ID: References: <20070916061932.GA93480@underworld.novel.ru> <20070918061806.GA85425@blazingdot.com> <20070918004027.G558@10.0.0.1> <20070922233709.GG59731@redundancy.redundancy.org> X-message-flag: Outlook -- Not just for spreading viruses anymore! X-OpenPGP-Key-ID: 0xD5B2F0FB Organization: http://www.FreeBSD.org/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: SCHED_ULE on desktop system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 03:52:10 -0000 On Sat, 22 Sep 2007, David E. Thiel wrote: > FWIW, Sept 20th's current has gotten rid of the audio stuttering for me. > Redraw and mouse movement still gets some slowdowns (even with X rtprio'd), > but I think I'll wait for the new nvidia driver to come out before I can > blame it on anything scheduler-related. So, something in the recent ULE > commits has worked. Thanks! Do you have witness enabled in your kernel? If so, can you try without it? Doug -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 05:08:26 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D5CB16A41A for ; Sun, 23 Sep 2007 05:08:26 +0000 (UTC) (envelope-from lx@redundancy.redundancy.org) Received: from redundancy.redundancy.org (redundancy.redundancy.org [64.147.160.152]) by mx1.freebsd.org (Postfix) with SMTP id 488C913C458 for ; Sun, 23 Sep 2007 05:08:26 +0000 (UTC) (envelope-from lx@redundancy.redundancy.org) Received: (qmail 83890 invoked by uid 1001); 23 Sep 2007 05:08:48 -0000 Date: Sat, 22 Sep 2007 22:08:48 -0700 From: "David E. Thiel" To: freebsd-current@freebsd.org Message-ID: <20070923050848.GH59731@redundancy.redundancy.org> Mail-Followup-To: freebsd-current@freebsd.org References: <20070916061932.GA93480@underworld.novel.ru> <20070918061806.GA85425@blazingdot.com> <20070918004027.G558@10.0.0.1> <20070922233709.GG59731@redundancy.redundancy.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OpenPGP-Key-fingerprint: 482A 8C46 C844 7E7C 8CBC 2313 96EE BEE5 1F4B CA13 X-OpenPGP-Key-available: http://redundancy.redundancy.org/lx.gpg User-Agent: Mutt/1.5.16 (2007-06-09) Subject: Re: SCHED_ULE on desktop system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 05:08:26 -0000 On Sat, Sep 22, 2007 at 08:52:07PM -0700, Doug Barton wrote: > Do you have witness enabled in your kernel? If so, can you try without it? I do not. I've removed the debug stuff as well as turned off malloc debugging. From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 06:38:26 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6905616A41A for ; Sun, 23 Sep 2007 06:38:26 +0000 (UTC) (envelope-from kpeter@melbpc.org.au) Received: from vscan05.westnet.com.au (vscan05.westnet.com.au [203.10.1.139]) by mx1.freebsd.org (Postfix) with ESMTP id 285D213C455 for ; Sun, 23 Sep 2007 06:38:24 +0000 (UTC) (envelope-from kpeter@melbpc.org.au) Received: from localhost (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id EC1FD24AA52 for ; Sun, 23 Sep 2007 14:38:22 +0800 (WST) Received: from vscan05.westnet.com.au ([127.0.0.1]) by localhost (vscan05.westnet.com.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aKw0wa57B5ei for ; Sun, 23 Sep 2007 14:38:22 +0800 (WST) Received: from baron.from.hell (dsl-220-235-224-10.vic.westnet.com.au [220.235.224.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by vscan05.westnet.com.au (Postfix) with ESMTP id A711124A987 for ; Sun, 23 Sep 2007 14:38:21 +0800 (WST) Message-ID: <46F609DC.3070809@melbpc.org.au> Date: Sun, 23 Sep 2007 16:38:20 +1000 From: Peter Kostouros Organization: Melbourne PC User Group User-Agent: Thunderbird 2.0.0.0 (X11/20070326) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Content-Type: multipart/mixed; boundary="------------060407020408050006000302" Cc: Subject: [panic] sched_priority: invalid interactive priority 124 score -4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 23 Sep 2007 06:38:26 -0000 This is a multi-part message in MIME format. --------------060407020408050006000302 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi I received the abovementioned panic on a system csup'ed and build a few hours ago and have attached a debug session I hope will help. Note that I am using the ULE scheduler: version of sched_ule.c is 1.208 (2007/09/22). Let me know if I can provide further information. -- Regards Peter As always the organisation disavows knowledge of this email --------------060407020408050006000302 Content-Type: text/plain; name="kern.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="kern.diff" --- GENERIC 2007-07-14 10:52:03.000000000 +1000 +++ BARON 2007-09-15 21:52:05.000000000 +1000 @@ -18,17 +18,16 @@ # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.473 2007/07/01 21:47:45 njl Exp $ -cpu I486_CPU -cpu I586_CPU cpu I686_CPU -ident GENERIC +ident BARON # 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 SCHED_4BSD # 4BSD scheduler +options SCHED_ULE options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking options INET6 # IPv6 communications protocols @@ -305,9 +304,46 @@ device rue # RealTek RTL8150 USB Ethernet # FireWire support -device firewire # FireWire bus code -device sbp # SCSI over FireWire (Requires scbus and da) -device fwe # Ethernet over FireWire (non-standard!) -device fwip # IP over FireWire (RFC 2734,3146) -device dcons # Dumb console driver -device dcons_crom # Configuration ROM for dcons +#device firewire # FireWire bus code +#device sbp # SCSI over FireWire (Requires scbus and da) +#device fwe # Ethernet over FireWire (non-standard!) +#device fwip # IP over FireWire (RFC 2734,3146) +#device dcons # Dumb console driver +#device dcons_crom # Configuration ROM for dcons + +# +# BARON +# +device sound +device snd_emu10kx + +# +# Options to enable ATAPI devices access through SCSI subsystem +# +device atapicam +device ata +device scbus +device cd +device pass + +# +# Alternate queuing of network packets +# +options ALTQ +options ALTQ_CBQ +options ALTQ_RED +options ALTQ_RIO +options ALTQ_HFSC +options ALTQ_CDNR +options ALTQ_PRIQ +options ALTQ_NOPCC +options ALTQ_DEBUG + +# +# Kernel tracing +# +options KTR +options ALQ +options KTR_ALQ +options KTR_ENTRIES=131072 +options KTR_COMPILE=(KTR_LOCK|KTR_PROC|KTR_INTR|KTR_CALLOUT|KTR_UMA|KTR_SYSC) --------------060407020408050006000302 Content-Type: application/octet-stream; name="typescript" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="typescript" U2NyaXB0IHN0YXJ0ZWQgb24gU3VuIFNlcCAyMyAxMzozMzozMSAyMDA3CmJhcm9uIyBrZ2Ri IC1jIC92YXIvY2hhCBtbSwgbW0tyYXNoL3ZtCBtbSwgbW0t2bWNvcmUuMTY0IC1mIC9ib290 L2tlcm5lbC9rZXJuZWwKCltHREIgd2lsbCBub3QgYmUgYWJsZSB0byBkZWJ1ZyB1c2VyLW1v ZGUgdGhyZWFkczogL3Vzci9saWIvbGlidGhyZWFkX2RiLnNvOiBVbmRlZmluZWQgc3ltYm9s ICJwc19wZ2xvYmFsX2xvb2t1cCJdCkdOVSBnZGIgNi4xLjEgW0ZyZWVCU0RdCkNvcHlyaWdo dCAyMDA0IEZyZWUgU29mdHdhcmUgRm91bmRhdGlvbiwgSW5jLgpHREIgaXMgZnJlZSBzb2Z0 d2FyZSwgY292ZXJlZCBieSB0aGUgR05VIEdlbmVyYWwgUHVibGljIExpY2Vuc2UsIGFuZCB5 b3UgYXJlCndlbGNvbWUgdG8gY2hhbmdlIGl0IGFuZC9vciBkaXN0cmlidXRlIGNvcGllcyBv ZiBpdCB1bmRlciBjZXJ0YWluIGNvbmRpdGlvbnMuClR5cGUgInNob3cgY29weWluZyIgdG8g c2VlIHRoZSBjb25kaXRpb25zLgpUaGVyZSBpcyBhYnNvbHV0ZWx5IG5vIHdhcnJhbnR5IGZv ciBHREIuICBUeXBlICJzaG93IHdhcnJhbnR5IiBmb3IgZGV0YWlscy4KVGhpcyBHREIgd2Fz IGNvbmZpZ3VyZWQgYXMgImkzODYtbWFyY2VsLWZyZWVic2QiLgoKVW5yZWFkIHBvcnRpb24g b2YgdGhlIGtlcm5lbCBtZXNzYWdlIGJ1ZmZlcjoKcGFuaWM6IHNjaGVkX3ByaW9yaXR5OiBp bnZhbGlkIGludGVyYWN0aXZlIHByaW9yaXR5IDEyNCBzY29yZSAtNApjcHVpZCA9IDAKVXB0 aW1lOiAxMW0xcwpQaHlzaWNhbCBtZW1vcnk6IDEwMDMgTUIKRHVtcGluZyAxMTIgTUI6IChD VFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkg IChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9y dCkgIDk3IChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0 byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwt QyB0byBhYm9ydCkgIDgxIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAg KENUUkwtQyB0byBhYm9ydCkgIDY1IChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFi b3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRv IGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1D IHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RS TC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAo Q1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQp ICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJv cnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIDQ5IChDVFJMLUMg dG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJM LUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChD VFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkg IChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9y dCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBh Ym9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0 byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwt QyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENU UkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAg KENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0 KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFi b3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIDMzIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1D IHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RS TC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAo Q1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQp ICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJv cnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8g YWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMg dG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJM LUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChD VFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkg IChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9y dCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBh Ym9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0 byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwt QyB0byBhYm9ydCkgIDE3IChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAg KENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0 KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFi b3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRv IGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RSTC1D IHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAoQ1RS TC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQpICAo Q1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJvcnQp ICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8gYWJv cnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMgdG8g YWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJMLUMg dG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIChDVFJM LUMgdG8gYWJvcnQpICAoQ1RSTC1DIHRvIGFib3J0KSAgKENUUkwtQyB0byBhYm9ydCkgIDEK CiMwICBkb2FkdW1wICgpIGF0IHBjcHUuaDoxOTUKMTk1CXBjcHUuaDogTm8gc3VjaCBmaWxl IG9yIGRpcmVjdG9yeS4KCWluIHBjcHUuaAooa2dkYikgd2hlcmUKIzAgIGRvYWR1bXAgKCkg YXQgcGNwdS5oOjE5NQojMSAgMHhjMDc4NDA1ZSBpbiBib290IChob3d0bz0yNjApIGF0IC9t bnQvY3ZzL0ZyZWVCU0QvdXNyL3NyYy9zeXMva2Vybi9rZXJuX3NodXRkb3duLmM6NDA5CiMy ICAweGMwNzg0MzIwIGluIHBhbmljIChmbXQ9VmFyaWFibGUgImZtdCIgaXMgbm90IGF2YWls YWJsZS4KKSBhdCAvbW50L2N2cy9GcmVlQlNEL3Vzci9zcmMvc3lzL2tlcm4va2Vybl9zaHV0 ZG93bi5jOjU2MwojMyAgMHhjMDdhMWFmYiBpbiBzY2hlZF9wcmlvcml0eSAodGQ9MHhjNGIy ODg4MCkgYXQgL21udC9jdnMvRnJlZUJTRC91c3Ivc3JjL3N5cy9rZXJuL3NjaGVkX3VsZS5j OjE0MTgKIzQgIDB4YzA3YTM0NTcgaW4gc2NoZWRfbmljZSAocD0weGM0YjI3YWEwLCBuaWNl PTQpIGF0IC9tbnQvY3ZzL0ZyZWVCU0QvdXNyL3NyYy9zeXMva2Vybi9zY2hlZF91bGUuYzox OTA5CiM1ICAweGMwNzgxMjU5IGluIGRvbmljZSAodGQ9MHhjNGIyODg4MCwgcD0weGM0YjI3 YWEwLCBuPTQpIGF0IC9tbnQvY3ZzL0ZyZWVCU0QvdXNyL3NyYy9zeXMva2Vybi9rZXJuX3Jl c291cmNlLmM6MjY3CiM2ICAweGMwNzgxMzEwIGluIHNldHByaW9yaXR5ICh0ZD0weGM0YjI4 ODgwLCB1YXA9MHhlNGU3ZmNmYykgYXQgL21udC9jdnMvRnJlZUJTRC91c3Ivc3JjL3N5cy9r ZXJuL2tlcm5fcmVzb3VyY2UuYzoxODcKIzcgIDB4YzBhNDE5NTMgaW4gc3lzY2FsbCAoZnJh bWU9MHhlNGU3ZmQzOCkgYXQgL21udC9jdnMvRnJlZUJTRC91c3Ivc3JjL3N5cy9pMzg2L2kz ODYvdHJhcC5jOjEwMDgKIzggIDB4YzBhMjgwNzAgaW4gWGludDB4ODBfc3lzY2FsbCAoKSBh dCAvbW50L2N2cy9GcmVlQlNEL3Vzci9zcmMvc3lzL2kzODYvaTM4Ni9leGNlcHRpb24uczox OTYKIzkgIDB4MDAwMDAwMzMgaW4gPz8gKCkKUHJldmlvdXMgZnJhbWUgaW5uZXIgdG8gdGhp cyBmcmFtZSAoY29ycnVwdCBzdGFjaz8pCihrZ2RiKSB1cCAzCiMzICAweGMwN2ExYWZiIGlu IHNjaGVkX3ByaW9yaXR5ICh0ZD0weGM0YjI4ODgwKSBhdCAvbW50L2N2cy9GcmVlQlNEL3Vz ci9zcmMvc3lzL2tlcm4vc2NoZWRfdWxlLmM6MTQxOAoaGi9tbnQvY3ZzL0ZyZWVCU0QvdXNy L3NyYy9zeXMva2Vybi9zY2hlZF91bGUuYzoxNDE4OjM3NzQzOmJlZzoweGMwN2ExYWZiCihr Z2RiKSBsCjE0MTMJCXNjb3JlID0gc2NoZWRfaW50ZXJhY3Rfc2NvcmUodGQpIC0gdGQtPnRk X3Byb2MtPnBfbmljZTsKMTQxNAkJaWYgKHNjb3JlIDwgc2NoZWRfaW50ZXJhY3QpIHsKMTQx NQkJCXByaSA9IFBSSV9NSU5fUkVBTFRJTUU7CjE0MTYJCQlwcmkgKz0gKChQUklfTUFYX1JF QUxUSU1FIC0gUFJJX01JTl9SRUFMVElNRSkgLyBzY2hlZF9pbnRlcmFjdCkKMTQxNwkJCSAg ICAqIHNjb3JlOwoxNDE4CQkJS0FTU0VSVChwcmkgPj0gUFJJX01JTl9SRUFMVElNRSAmJiBw cmkgPD0gUFJJX01BWF9SRUFMVElNRSwKMTQxOQkJCSAgICAoInNjaGVkX3ByaW9yaXR5OiBp bnZhbGlkIGludGVyYWN0aXZlIHByaW9yaXR5ICVkIHNjb3JlICVkIiwKMTQyMAkJCSAgICBw cmksIHNjb3JlKSk7CjE0MjEJCX0gZWxzZSB7CjE0MjIJCQlwcmkgPSBTQ0hFRF9QUklfTUlO Owooa2dkYikgcCB0ZAokMSA9IChzdHJ1Y3QgdGhyZWFkICopIDB4YzRiMjg4ODAKKGtnZGIp IHAgdGQICBtbNGgqG1s0bAokMiA9IHt0ZF9sb2NrID0gMHhjMTI3ZmIwMCwgdGRfcHJvYyA9 IDB4YzRiMjdhYTAsIHRkX3BsaXN0ID0ge3RxZV9uZXh0ID0gMHgwLCB0cWVfcHJldiA9IDB4 YzRiMjdhYTh9LCB0ZF9zbHBxID0ge3RxZV9uZXh0ID0gMHgwLCAKICAgIHRxZV9wcmV2ID0g MHhjNDcwNzMzMH0sIHRkX2xvY2txID0ge3RxZV9uZXh0ID0gMHgwLCB0cWVfcHJldiA9IDB4 ZTcwOGZhMTh9LCB0ZF9zZWxxID0ge3RxaF9maXJzdCA9IDB4MCwgdHFoX2xhc3QgPSAweGM0 YjI4OGEwfSwgCiAgdGRfc2xlZXBxdWV1ZSA9IDB4YzQ3MDczMzAsIHRkX3R1cm5zdGlsZSA9 IDB4YzQ3MTJkNzAsIHRkX3VtdHhxID0gMHhjNGIyYTMwMCwgdGRfdGlkID0gMTAwMDUyLCB0 ZF9zaWdxdWV1ZSA9IHtzcV9zaWduYWxzID0ge19fYml0cyA9IHsKICAgICAgICAwLCAwLCAw LCAwfX0sIHNxX2tpbGwgPSB7X19iaXRzID0gezAsIDAsIDAsIDB9fSwgc3FfbGlzdCA9IHt0 cWhfZmlyc3QgPSAweDAsIHRxaF9sYXN0ID0gMHhjNGIyODhkOH0sIHNxX3Byb2MgPSAweGM0 YjI3YWEwLCAKICAgIHNxX2ZsYWdzID0gMX0sIHRkX2ZsYWdzID0gNjU1NDIsIHRkX2luaGli aXRvcnMgPSAwLCB0ZF9wZmxhZ3MgPSAwLCB0ZF9kdXBmZCA9IDAsIHRkX3NxcXVldWUgPSAw LCB0ZF93Y2hhbiA9IDB4MCwgdGRfd21lc2cgPSAweDAsIAogIHRkX2xhc3RjcHUgPSAwICdc MCcsIHRkX29uY3B1ID0gMCAnXDAnLCB0ZF9vd2VwcmVlbXB0ID0gMCAnXDAnLCB0ZF9sb2Nr cyA9IDEsIHRkX3RzcXVldWUgPSAwICdcMCcsIHRkX2Jsb2NrZWQgPSAweDAsIHRkX2xvY2tu YW1lID0gMHgwLCAKICB0ZF9jb250ZXN0ZWQgPSB7bGhfZmlyc3QgPSAweDB9LCB0ZF9zbGVl cGxvY2tzID0gMHhjMTJjOTEyOCwgdGRfaW50cl9uZXN0aW5nX2xldmVsID0gMCwgdGRfcGlu bmVkID0gMiwgdGRfbWFpbGJveCA9IDB4MCwgCiAgdGRfdWNyZWQgPSAweGM0NmVkNTAwLCB0 ZF9zdGFuZGluID0gMHgwLCB0ZF91cGNhbGwgPSAweDAsIHRkX2VzdGNwdSA9IDAsIHRkX3Ns cHRpY2sgPSAwLCB0ZF9ydSA9IHtydV91dGltZSA9IHt0dl9zZWMgPSAwLCB0dl91c2VjID0g MH0sIAogICAgcnVfc3RpbWUgPSB7dHZfc2VjID0gMCwgdHZfdXNlYyA9IDB9LCBydV9tYXhy c3MgPSAzMTYsIHJ1X2l4cnNzID0gNCwgcnVfaWRyc3MgPSA0LCBydV9pc3JzcyA9IDEyOCwg cnVfbWluZmx0ID0gNzgsIHJ1X21hamZsdCA9IDAsIAogICAgcnVfbnN3YXAgPSAwLCBydV9p bmJsb2NrID0gMCwgcnVfb3VibG9jayA9IDAsIHJ1X21zZ3NuZCA9IDAsIHJ1X21zZ3JjdiA9 IDAsIHJ1X25zaWduYWxzID0gMCwgcnVfbnZjc3cgPSAyLCBydV9uaXZjc3cgPSAwfSwgCiAg dGRfcnVudGltZSA9IDM1NDUyNjgsIHRkX3B0aWNrcyA9IDAsIHRkX3N0aWNrcyA9IDEsIHRk X2l0aWNrcyA9IDAsIHRkX3V0aWNrcyA9IDAsIHRkX3V1dGlja3MgPSAwLCB0ZF91c3RpY2tz ID0gMCwgdGRfaW50cnZhbCA9IDAsIAogIHRkX29sZHNpZ21hc2sgPSB7X19iaXRzID0gezAs IDAsIDAsIDB9fSwgdGRfc2lnbWFzayA9IHtfX2JpdHMgPSB7MCwgMCwgMCwgMH19LCB0ZF9n ZW5lcmF0aW9uID0gMiwgdGRfc2lnc3RrID0ge3NzX3NwID0gMHgwLCAKICAgIHNzX3NpemUg PSAwLCBzc19mbGFncyA9IDR9LCB0ZF9rZmxhZ3MgPSAwLCB0ZF94c2lnID0gMCwgdGRfcHJv ZmlsX2FkZHIgPSAwLCB0ZF9wcm9maWxfdGlja3MgPSAwLCB0ZF9uYW1lID0gJ1wwJyA8cmVw ZWF0cyAxOSB0aW1lcz4sIAogIHRkX2Jhc2VfcHJpID0gMTI4ICdcMjAwJywgdGRfcHJpb3Jp dHkgPSAxMjggJ1wyMDAnLCB0ZF9wcmlfY2xhc3MgPSAzICdcMDAzJywgdGRfdXNlcl9wcmkg PSAxMjggJ1wyMDAnLCB0ZF9iYXNlX3VzZXJfcHJpID0gMTI4ICdcMjAwJywgCiAgdGRfcGNi ID0gMHhlNGU3ZmQ5MCwgdGRfc3RhdGUgPSBURFNfUlVOTklORywgdGRfcmV0dmFsID0gezAs IDEwMn0sIHRkX3NscGNhbGxvdXQgPSB7Y19saW5rcyA9IHtzbGUgPSB7c2xlX25leHQgPSAw eDB9LCB0cWUgPSB7CiAgICAgICAgdHFlX25leHQgPSAweDAsIHRxZV9wcmV2ID0gMHhkODcx NGJlOH19LCBjX3RpbWUgPSA1OTE0NzUsIGNfYXJnID0gMHhjNGIyODg4MCwgY19mdW5jID0g MHhjMDdiNWY4MCA8c2xlZXBxX3RpbWVvdXQ+LCBjX210eCA9IDB4MCwgCiAgICBjX2ZsYWdz ID0gMTh9LCB0ZF9mcmFtZSA9IDB4ZTRlN2ZkMzgsIHRkX2tzdGFja19vYmogPSAweGMxYzVm MmQwLCB0ZF9rc3RhY2sgPSAzODQwNDAxNDA4LCB0ZF9rc3RhY2tfcGFnZXMgPSAyLCAKICB0 ZF9hbHRrc3RhY2tfb2JqID0gMHgwLCB0ZF9hbHRrc3RhY2sgPSAwLCB0ZF9hbHRrc3RhY2tf cGFnZXMgPSAwLCB0ZF9jcml0bmVzdCA9IDIsIHRkX21kID0ge21kX3NwaW5sb2NrX2NvdW50 ID0gMiwgCiAgICBtZF9zYXZlZF9mbGFncyA9IDU4Mn0sIHRkX3NjaGVkID0gMHhjNGIyOGE2 NCwgdGRfYXIgPSAweDAsIHRkX3N5c2NhbGxzID0gNzA3M30KKGtnZGIpIHAgKnRkLT50ZF9w cm9jKQgICAgICAgICAgICBtbNGgoG1s0bAokMyA9IHtwX2xpc3QgPSB7bGVfbmV4dCA9IDB4 YzRiMjcwMDAsIGxlX3ByZXYgPSAweGM0YjI3N2Y4fSwgcF90aHJlYWRzID0ge3RxaF9maXJz dCA9IDB4YzRiMjg4ODAsIHRxaF9sYXN0ID0gMHhjNGIyODg4OH0sIHBfdXBjYWxscyA9IHsK ICAgIHRxaF9maXJzdCA9IDB4MCwgdHFoX2xhc3QgPSAweGM0YjI3YWIwfSwgcF9zbG9jayA9 IHtsb2NrX29iamVjdCA9IHtsb19uYW1lID0gMHhjMGFkY2ZhMSAicHJvY2VzcyBzbG9jayIs IAogICAgICBsb190eXBlID0gMHhjMGFkY2ZhMSAicHJvY2VzcyBzbG9jayIsIGxvX2ZsYWdz ID0gNzIwODk2LCBsb193aXRuZXNzX2RhdGEgPSB7bG9kX2xpc3QgPSB7c3RxZV9uZXh0ID0g MHgwfSwgbG9kX3dpdG5lc3MgPSAweDB9fSwgCiAgICBtdHhfbG9jayA9IDMzMDAwMzQ2ODgs IG10eF9yZWN1cnNlID0gMH0sIHBfdWNyZWQgPSAweGM0NmVkNTAwLCBwX2ZkID0gMHhjNGI5 MTIwMCwgcF9mZHRvbCA9IDB4MCwgcF9zdGF0cyA9IDB4YzRiMWU4MDAsIAogIHBfbGltaXQg PSAweGM1YmY0MjAwLCBwX2xpbWNvID0ge2NfbGlua3MgPSB7c2xlID0ge3NsZV9uZXh0ID0g MHgwfSwgdHFlID0ge3RxZV9uZXh0ID0gMHgwLCB0cWVfcHJldiA9IDB4MH19LCBjX3RpbWUg PSAwLCBjX2FyZyA9IDB4MCwgCiAgICBjX2Z1bmMgPSAwLCBjX210eCA9IDB4YzRiMjdiMzAs IGNfZmxhZ3MgPSAwfSwgcF9zaWdhY3RzID0gMHhjNzEzYjAwMCwgcF9mbGFnID0gMjY4NDUx ODQyLCBwX3N0YXRlID0gUFJTX05PUk1BTCwgcF9waWQgPSAyMjAwMCwgCiAgcF9oYXNoID0g e2xlX25leHQgPSAweDAsIGxlX3ByZXYgPSAweGM0NzAyN2MwfSwgcF9wZ2xpc3QgPSB7bGVf bmV4dCA9IDB4YzRjNDZhYTAsIGxlX3ByZXYgPSAweGM1ZWZjMDc4fSwgcF9wcHRyID0gMHhj NWVmYzAwMCwgCiAgcF9zaWJsaW5nID0ge2xlX25leHQgPSAweDAsIGxlX3ByZXYgPSAweGM1 ZWZjMDhjfSwgcF9jaGlsZHJlbiA9IHtsaF9maXJzdCA9IDB4MH0sIHBfbXR4ID0ge2xvY2tf b2JqZWN0ID0gewogICAgICBsb19uYW1lID0gMHhjMGFkY2Y5NCAicHJvY2VzcyBsb2NrIiwg bG9fdHlwZSA9IDB4YzBhZGNmOTQgInByb2Nlc3MgbG9jayIsIGxvX2ZsYWdzID0gMjExNjgx MjgsIGxvX3dpdG5lc3NfZGF0YSA9IHtsb2RfbGlzdCA9IHsKICAgICAgICAgIHN0cWVfbmV4 dCA9IDB4YzEyOGNhMDB9LCBsb2Rfd2l0bmVzcyA9IDB4YzEyOGNhMDB9fSwgbXR4X2xvY2sg PSAzMzAwMDM0Njg4LCBtdHhfcmVjdXJzZSA9IDB9LCBwX2tzaSA9IDB4YzRhZGRkYzAsIHBf c2lncXVldWUgPSB7CiAgICBzcV9zaWduYWxzID0ge19fYml0cyA9IHswLCAwLCAwLCAwfX0s IHNxX2tpbGwgPSB7X19iaXRzID0gezAsIDAsIDAsIDB9fSwgc3FfbGlzdCA9IHt0cWhfZmly c3QgPSAweDAsIHRxaF9sYXN0ID0gMHhjNGIyN2I2Y30sIAogICAgc3FfcHJvYyA9IDB4YzRi MjdhYTAsIHNxX2ZsYWdzID0gMX0sIHBfb3BwaWQgPSAwLCBwX3Ztc3BhY2UgPSAweGM0NzE2 OWY4LCBwX3N3dGljayA9IDYwMDAxMCwgcF9yZWFsdGltZXIgPSB7aXRfaW50ZXJ2YWwgPSB7 CiAgICAgIHR2X3NlYyA9IDAsIHR2X3VzZWMgPSAwfSwgaXRfdmFsdWUgPSB7dHZfc2VjID0g MCwgdHZfdXNlYyA9IDB9fSwgcF9ydSA9IHtydV91dGltZSA9IHt0dl9zZWMgPSAwLCB0dl91 c2VjID0gMH0sIHJ1X3N0aW1lID0gewogICAgICB0dl9zZWMgPSAwLCB0dl91c2VjID0gMH0s IHJ1X21heHJzcyA9IDAsIHJ1X2l4cnNzID0gMCwgcnVfaWRyc3MgPSAwLCBydV9pc3JzcyA9 IDAsIHJ1X21pbmZsdCA9IDAsIHJ1X21hamZsdCA9IDAsIHJ1X25zd2FwID0gMCwgCiAgICBy dV9pbmJsb2NrID0gMCwgcnVfb3VibG9jayA9IDAsIHJ1X21zZ3NuZCA9IDAsIHJ1X21zZ3Jj diA9IDAsIHJ1X25zaWduYWxzID0gMCwgcnVfbnZjc3cgPSAwLCBydV9uaXZjc3cgPSAwfSwg cF9ydXggPSB7CiAgICBydXhfcnVudGltZSA9IDAsIHJ1eF91dGlja3MgPSAwLCBydXhfc3Rp Y2tzID0gMCwgcnV4X2l0aWNrcyA9IDAsIHJ1eF91dSA9IDAsIHJ1eF9zdSA9IDAsIHJ1eF90 dSA9IDB9LCBwX2NydXggPSB7CiAgICBydXhfcnVudGltZSA9IDY3NzY0MjAsIHJ1eF91dGlj a3MgPSAwLCBydXhfc3RpY2tzID0gMCwgcnV4X2l0aWNrcyA9IDAsIHJ1eF91dSA9IDAsIHJ1 eF9zdSA9IDAsIHJ1eF90dSA9IDB9LCBwX3Byb2Z0aHJlYWRzID0gMCwgCiAgcF9leGl0dGhy ZWFkcyA9IDAsIHBfdHJhY2VmbGFnID0gMCwgcF90cmFjZXZwID0gMHgwLCBwX3RyYWNlY3Jl ZCA9IDB4MCwgcF90ZXh0dnAgPSAweGM2Yzk5MzMwLCBwX2xvY2sgPSAwICdcMCcsIHBfc2ln aW9sc3QgPSB7CiAgICBzbGhfZmlyc3QgPSAweDB9LCBwX3NpZ3BhcmVudCA9IDIwLCBwX3Np ZyA9IDAsIHBfY29kZSA9IDAsIHBfc3RvcHMgPSAwLCBwX3N0eXBlID0gMCwgcF9zdGVwID0g MCAnXDAnLCBwX3Bmc2ZsYWdzID0gMCAnXDAnLCAKICBwX25sbWluZm8gPSAweDAsIHBfYWlv aW5mbyA9IDB4MCwgcF9zaW5nbGV0aHJlYWQgPSAweDAsIHBfc3VzcGNvdW50ID0gMCwgcF94 dGhyZWFkID0gMHgwLCBwX2JvdW5kYXJ5X2NvdW50ID0gMCwgcF9wZW5kaW5nY250ID0gMCwg CiAgcF9pdGltZXJzID0gMHgwLCBwX251bXVwY2FsbHMgPSAwLCBwX3Vwc2xlZXBzID0gMCwg cF9jb21wbGV0ZWQgPSAweDAsIHBfbmV4dHVwY2FsbCA9IDAsIHBfdXBxdWFudHVtID0gMCwg cF9tYWdpYyA9IDMyMDMzOTgzNTAsIAogIHBfY29tbSA9ICJuaWNlXDAwMGVyIiwgJ1wwJyA8 cmVwZWF0cyAxMiB0aW1lcz4sIHBfcGdycCA9IDB4YzVhNzRiNDAsIHBfc3lzZW50ID0gMHhj MGJiZmQyMCwgcF9hcmdzID0gMHhjNTk2YzFhMCwgCiAgcF9jcHVsaW1pdCA9IDkyMjMzNzIw MzY4NTQ3NzU4MDcsIHBfbmljZSA9IDQgJ1wwMDQnLCBwX3hzdGF0ID0gMCwgcF9rbGlzdCA9 IHtrbF9saXN0ID0ge3NsaF9maXJzdCA9IDB4MH0sIAogICAga2xfbG9jayA9IDB4YzA3NWM3 YjAgPGtubGlzdF9tdHhfbG9jaz4sIGtsX3VubG9jayA9IDB4YzA3NWM3ZTAgPGtubGlzdF9t dHhfdW5sb2NrPiwga2xfbG9ja2VkID0gMHhjMDc1ZmJjMCA8a25saXN0X210eF9sb2NrZWQ+ LCAKICAgIGtsX2xvY2thcmcgPSAweGM0YjI3YjMwfSwgcF9udW10aHJlYWRzID0gMSwgcF9t ZCA9IHttZF9sZHQgPSAweDB9LCBwX2l0Y2FsbG91dCA9IHtjX2xpbmtzID0ge3NsZSA9IHtz bGVfbmV4dCA9IDB4MH0sIHRxZSA9IHsKICAgICAgICB0cWVfbmV4dCA9IDB4MCwgdHFlX3By ZXYgPSAweDB9fSwgY190aW1lID0gMCwgY19hcmcgPSAweDAsIGNfZnVuYyA9IDAsIGNfbXR4 ID0gMHgwLCBjX2ZsYWdzID0gMTZ9LCBwX2FjZmxhZyA9IDAsIHBfcGVlcnMgPSAweDAsIAog IHBfbGVhZGVyID0gMHhjNGIyN2FhMCwgcF9lbXVsZGF0YSA9IDB4MCwgcF9sYWJlbCA9IDB4 MCwgcF9zY2hlZCA9IDB4YzRiMjdkNDgsIHBfa3RyID0ge3N0cWhfZmlyc3QgPSAweDAsIHN0 cWhfbGFzdCA9IDB4YzRiMjdkM2N9LCAKICBwX21xbm90aWZpZXIgPSB7bGhfZmlyc3QgPSAw eDB9fQooa2dkYikgcXVpdAo= --------------060407020408050006000302-- From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 07:25:13 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DAD7F16A418 for ; Sun, 23 Sep 2007 07:25:13 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id BCCF613C43E for ; Sun, 23 Sep 2007 07:25:13 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id EB8582F0DF; Sun, 23 Sep 2007 03:24:25 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sun, 23 Sep 2007 03:24:25 -0400 X-Sasl-enc: 2xdGgOmNanCx69GySBMHJThshUtlsXXiKHIonjckJBIE 1190532265 Received: from [192.168.1.235] (64-142-85-108.dsl.dynamic.sonic.net [64.142.85.108]) by mail.messagingengine.com (Postfix) with ESMTP id 508833F31; Sun, 23 Sep 2007 03:24:25 -0400 (EDT) Message-ID: <46F614F2.4050402@freebsd.org> Date: Sun, 23 Sep 2007 00:25:38 -0700 From: Darren Reed User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Kip Macy References: <2a41acea0709221656n4aa62776y488c7f2da262c9f6@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-net@freebsd.org" , FreeBSD Current , Jack Vogel Subject: Re: TX Multiqueue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 07:25:13 -0000 Kip Macy wrote: > My ethng branch supports multiple rx and tx queues. > > -Kip > What are your plans for how we use/manage/interact with the mutiple rx/tx queues? Darren > On 9/22/07, Jack Vogel wrote: > > Our newest E1000 nic, the 82575, and the Oplin 10G hardware are capable of > > multiple queues both on the receive and the send side. On the receive end for > > the Oplin driver the queues actually help distribute interrupts and improve > > performance without any special support in the stack. > > > > I have been asked about multiple queues on the TX side, embedded appliance > > type system builders for instance are interested I suppose for > > priority queueing. > > Is anyone working on this right now, and if not does this sound like something > > anyone is interested in doing? > > > > I would like to see MQ on both TX and RX that drivers could use if able. > > > > Jack > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-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 Sun Sep 23 07:59:12 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C602716A419 for ; Sun, 23 Sep 2007 07:59:12 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id A8B4E13C459 for ; Sun, 23 Sep 2007 07:59:12 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id ECB192EF49; Sun, 23 Sep 2007 03:59:04 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sun, 23 Sep 2007 03:59:04 -0400 X-Sasl-enc: kBVQlhw5z0JSDGdMXFYHmT3F0mqnKqWJrX/6ShED5beD 1190534344 Received: from [192.168.1.235] (64-142-85-108.dsl.dynamic.sonic.net [64.142.85.108]) by mail.messagingengine.com (Postfix) with ESMTP id 7ECA81737; Sun, 23 Sep 2007 03:59:04 -0400 (EDT) Message-ID: <46F61D11.7090403@freebsd.org> Date: Sun, 23 Sep 2007 01:00:17 -0700 From: Darren Reed User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Michiel Boland References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: immediate reboot with ipnat/ipmon on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 07:59:12 -0000 Michiel Boland wrote: > Hi. I wanted to try something out with nat. So I tried this with > ipnat. But my -CURRENT amd64 box instantly reboots if I type > > # ipnat -l > # ipmon -a > > No crash dump, nothing. Just immediate reboot. A fix for this is in the pipeline, awaiting re[gulator] approval. Darren From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 08:37:12 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E8C416A419 for ; Sun, 23 Sep 2007 08:37:12 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.188]) by mx1.freebsd.org (Postfix) with ESMTP id A438E13C447 for ; Sun, 23 Sep 2007 08:37:11 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by mu-out-0910.google.com with SMTP id w9so1565571mue for ; Sun, 23 Sep 2007 01:37:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=l227pavqrKRQ6dTxkmqHvM2WQUC53qDlB4LndqMZ+TQ=; b=XK8T8mF1W0twV94FwTNbERhUKCbBQbbHp4WL8Bd2KEOV5CP7awyFmhOB+ZvAtEPgz5VaSS4+WDMV5ndv+XOnKU3hPEYinUu1JvX+Fj9vSHqlovvIqlpRWBZwaD4VoFIQjMIV/UcxUVK8GZeMXZYtOTqeSxXwRhxKplI8uzquqRM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=q7FaeeFSf3qa0IKYE4zmJ+iivetKiYAp3vxlkE0UVnBzOo8AhY5HbEiga4NTdDKiFCVZDPrW5jXz2miO03NkdsshTHxUe5W7r4h68+Lygbn0/aI4H5rsE9kXAA5gT/T+cVMg8eZo+L3IBMPvj6rjSFflRpFkx6iPh5dMS+ug40E= Received: by 10.78.83.15 with SMTP id g15mr939126hub.1190536629957; Sun, 23 Sep 2007 01:37:09 -0700 (PDT) Received: by 10.78.166.18 with HTTP; Sun, 23 Sep 2007 01:37:09 -0700 (PDT) Message-ID: Date: Sun, 23 Sep 2007 10:37:09 +0200 From: "Claus Guttesen" To: "Darren Reed" In-Reply-To: <46F58799.1030702@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070921102946.T11189@borg> <46F415BF.9010500@FreeBSD.org> <20070921140550.D96923@thebighonker.lerctr.org> <46F41CFF.6080108@FreeBSD.org> <46F58799.1030702@freebsd.org> Cc: freebsd-current@freebsd.org, Larry Rosenman Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 08:37:12 -0000 > So I just received this courtesy of ZFS: > panic: kmem_malloc(131072): kmem_map too small: 343027712 total allocated > cpuid = 0 > KDB: enter: panic > > This was with these settings in loader.conf: > vm.kmem_size=419430400 > vm.kmem_size_max=419430400 > vfs.zfs.arc_max=409715200 How much ram do you have? Is this amd64 or i386? -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 09:31:59 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A534816A41A for ; Sun, 23 Sep 2007 09:31:59 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id E5E4E13C447 for ; Sun, 23 Sep 2007 09:31:58 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 67536 invoked from network); 23 Sep 2007 13:31:56 +0400 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 23 Sep 2007 13:31:56 +0400 X-AntiVirus: Checked by Dr.Web [version: 4.33, engine: 4.33.5.10110, virus records: 254176, updated: 22.09.2007] Message-ID: <003201c7fdc4$948749a0$0c00a8c0@Artem> From: "Artem Kuchin" To: "Jack Vogel" References: <01c801c7fc7a$696ab900$0c00a8c0@Artem><2a41acea0709211359w37ba779dsec94de504a9f4a9c@mail.gmail.com><019101c7fd3d$cd15f870$0c00a8c0@Artem> <2a41acea0709221647o3cdcb72pf6194c54782c61fb@mail.gmail.com> Date: Sun, 23 Sep 2007 13:31:50 +0400 Organization: IT Legion 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.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Cc: freebsd-current@freebsd.org Subject: Re: TSP on em makes send of streams very slow X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 09:31:59 -0000 Jack Vogel wrote: > On 9/22/07, Artem Kuchin wrote: >>> TSO is for some environments, it isn't gonna be useful at 100Mb >>> (which you are), it can be useful at 1Gb but not always, when you >>> get to 10G its >>> a HUGE benefit. >>> >>> Just cuz you can shoot yourself in the foot doesn't mean the gun >>> has a problem :) >> >> But wait, i did not shoot myself. I have been shot by the driver w/o >> any preliminary warning. TSO4 was enabled by DEFAULT (i did not >> enable it), >> so anybody can be in my place if used the same driver on the similar >> hardware (which is plenty). >> >> So, i think this is a problem which really need to be addressed. > > It is on by default because it the majority of cases its a benefit, > you found it to be a problem and turned it off, your problem is > solved. > > I admit, at one point I considered disabling it automatically for > anything under Gig speed, but a large community has used this driver > with this feature for over a year, no one has lobbied to have to > disabled, so I have not. > > If there are others who think this would be a good idea, speak up, and > I will do so. > Disable it by default is not actually the point. There are three points: 1) I have wasted half a work day to figure it all out 2) I expect at least network part of *FREEBSD* OS to work right out of the box 3) Even having it enabled must not cause drop to 800 bytes/second on send. This is clearly a bug. I don;t know if it is hardware of software bug but it must be addressed in the driver anyway. Or, as an option there must be a big waving banner somewhere where noone can miss it saying: "If you have crazy drop in network send perfomance disable TSO on your NIC via ifconfig". -- Regards, Artem From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 09:52:19 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4D6016A41B for ; Sun, 23 Sep 2007 09:52:19 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 7F7F213C494 for ; Sun, 23 Sep 2007 09:52:19 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 103E22E4F8 for ; Sun, 23 Sep 2007 05:52:19 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sun, 23 Sep 2007 05:52:19 -0400 X-Sasl-enc: Opsc9MkKpmUmEN1wXsW/exPiCzAfaBegFn4eoT5nteOh 1190541138 Received: from [192.168.1.235] (64-142-85-108.dsl.dynamic.sonic.net [64.142.85.108]) by mail.messagingengine.com (Postfix) with ESMTP id A775D41F5 for ; Sun, 23 Sep 2007 05:52:18 -0400 (EDT) Message-ID: <46F6379B.9050000@freebsd.org> Date: Sun, 23 Sep 2007 02:53:31 -0700 From: Darren Reed User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: yacc bug in reader.c:end_rule() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 09:52:19 -0000 There's a fairly obvious bug in yacc's reader.c but I'm not sure what the right fix is. Witness: end_rule() { int i; if (!last_was_action && plhs[nrules]->tag) { for (i = nitems - 1; pitem[i]; --i) continue; if (pitem[i + 1] == 0 || pitem[i+1]->tag != plhs[nrules]->tag) ... } ...clearly if pitem[nitems-1] == NULL (and nitems is the size of the array from [0,nitems-1]) then the if() will access beyond the bounds of the array. There's also the question of i being able to run below 0 too here. I don't know if the bug is here or if the bug is elsewhere in yacc, but I doubt that the "fix" is s/i + 1/i/. *Maybe* "i = nitems - 2;"? The bug can be masked by using calloc instead of malloc and similar other tricks, but there is something more fundamentaly wrong here. Has anyone else run into this? Darren From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 11:12:03 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC6BC16A418 for ; Sun, 23 Sep 2007 11:12:03 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id C056E13C43E for ; Sun, 23 Sep 2007 11:12:03 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 40A792ECC6 for ; Sun, 23 Sep 2007 07:12:03 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sun, 23 Sep 2007 07:12:03 -0400 X-Sasl-enc: b07kBZTK+7JOSnxBrNrQpBTidUClwnXrWyKCFnAWwd5c 1190545922 Received: from [192.168.1.235] (64-142-85-108.dsl.dynamic.sonic.net [64.142.85.108]) by mail.messagingengine.com (Postfix) with ESMTP id CA257A66 for ; Sun, 23 Sep 2007 07:12:02 -0400 (EDT) Message-ID: <46F64A4B.8000804@freebsd.org> Date: Sun, 23 Sep 2007 04:13:15 -0700 From: Darren Reed User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: FreeBSD Current References: <46F6379B.9050000@freebsd.org> In-Reply-To: <46F6379B.9050000@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: yacc bug in reader.c:end_rule() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 11:12:04 -0000 Darren Reed wrote: > There's a fairly obvious bug in yacc's reader.c but I'm not sure what > the right fix is. > > Witness: > end_rule() > { > int i; > > if (!last_was_action && plhs[nrules]->tag) > { > for (i = nitems - 1; pitem[i]; --i) continue; > if (pitem[i + 1] == 0 || pitem[i+1]->tag != plhs[nrules]->tag) > ... > } > > ...clearly if pitem[nitems-1] == NULL (and nitems is the size of the > array from [0,nitems-1]) then the if() will access beyond the bounds > of the array. > > There's also the question of i being able to run below 0 too here. > > I don't know if the bug is here or if the bug is elsewhere in yacc, > but I doubt that the "fix" is s/i + 1/i/. *Maybe* "i = nitems - 2;"? > > The bug can be masked by using calloc instead of malloc and similar > other tricks, but there is something more fundamentaly wrong here. > > Has anyone else run into this? The following sample grammar will exercise the bug: %{ %} %union { char *ptr; }; %type test %% test: | $$ = malloc(2); ; %% (The error here is that "test" has an undefined return.) Darren From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 11:34:45 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56DA316A419 for ; Sun, 23 Sep 2007 11:34:45 +0000 (UTC) (envelope-from andrea@webcom.it) Received: from www.webcom.it (gen053.n002.c03.escapebox.net [213.73.82.53]) by mx1.freebsd.org (Postfix) with ESMTP id 11C1C13C4A3 for ; Sun, 23 Sep 2007 11:34:45 +0000 (UTC) (envelope-from andrea@webcom.it) Received: from andrea by webcom.it with local (Exim 3.36 #1) id 1IZPTU-0008Wk-00 for current@freebsd.org; Sun, 23 Sep 2007 11:18:08 +0000 Date: Sun, 23 Sep 2007 11:18:08 +0000 From: Andrea Campi To: current@freebsd.org Message-ID: <20070923111808.GD31406@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Sender: Andrea Campi Cc: Subject: jemalloc malloc_usable_size() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 11:34:45 -0000 Hi all, for a university project, I have been working on a LD_PRELOAD wrapper for the string.h functions, similar in concept to HeapShield [1]. In short, I wrap all functions, determine the size of the usable allocation, then (if available) I translate the original call into a safer one (strcpy becomes strlcpy, and so on). I have been mostly targeting 6.x, where I wrote my own code to figure out the allocation size. On 7.x though, I figured I could use malloc_usable_size(). However, I encountered a few problems. First of all, jemalloc makes no effort (neither here nor in free(3)) to survive being called with non-malloc'ed pointers. If you do that and asserts are on, you will get an abort, but if they are not your process will likely die an horrible death--but there's no explicit guarantee of that. I suppose that's fine (we are talking major WTFs after all) in general, although it would be nice to have more control. phkmalloc had more limit checking, so bad pointers (text / stack) were reliably detected. Worse, malloc_usable_size() fails if you pass it a pointer inside a malloc'ed region. Again, you get an assert if that's enable, otherwise you probably get a random value. The reason for this is in arena_salloc, where the passed pointer is compared to the calculated page, to determine whether we are dealing with a small or large allocation. Unfortunately, I don't see an easy fix for this. Do you have any suggestion, or should I just give up on using malloc_usable_size()? As an aside: regardless of my purely educational exercise, what do you guys think of putting such checks in the libc itself? The performance impact is relatively small, and the benefits in terms of detecing and preventing heap buffer overflows huge. That's all the more important with jemalloc, which is (relatively) less safe that phkmalloc in fact of such attacks. Bye, Andrea 1: http://www.cs.umass.edu/~emery/pubs/06-28.pdf -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 12:52:17 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 856B216A418; Sun, 23 Sep 2007 12:52:17 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 4A8A713C4A8; Sun, 23 Sep 2007 12:52:17 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.8/8.13.8) with ESMTP id l8NCqGPU023645; Sun, 23 Sep 2007 08:52:16 -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.14.1/8.14.1) with ESMTP id l8NCqGQs041544; Sun, 23 Sep 2007 08:52:16 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id C2C3A73039; Sun, 23 Sep 2007 08:50:42 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070923125042.C2C3A73039@freebsd-current.sentex.ca> Date: Sun, 23 Sep 2007 08:50:42 -0400 (EDT) X-Virus-Scanned: ClamAV version devel-20070102, clamav-milter version devel-111206 on clamscanner5 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 12:52:17 -0000 TB --- 2007-09-23 10:49:09 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-09-23 10:49:09 - starting HEAD tinderbox run for ia64/ia64 TB --- 2007-09-23 10:49:09 - cleaning the object tree TB --- 2007-09-23 10:49:43 - checking out the source tree TB --- 2007-09-23 10:49:43 - cd /tinderbox/HEAD/ia64/ia64 TB --- 2007-09-23 10:49:43 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-09-23 10:58:25 - building world (CFLAGS=-O2 -pipe) TB --- 2007-09-23 10:58:25 - cd /src TB --- 2007-09-23 10:58:25 - /usr/bin/make -B buildworld >>> World build started on Sun Sep 23 10:58:27 UTC 2007 >>> 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 >>> World build completed on Sun Sep 23 12:38:31 UTC 2007 TB --- 2007-09-23 12:38:31 - generating LINT kernel config TB --- 2007-09-23 12:38:31 - cd /src/sys/ia64/conf TB --- 2007-09-23 12:38:31 - /usr/bin/make -B LINT TB --- 2007-09-23 12:38:31 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-09-23 12:38:31 - cd /src TB --- 2007-09-23 12:38:31 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Sep 23 12:38:31 UTC 2007 >>> 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 [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/geom/shsec/g_shsec.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/geom/stripe/g_stripe.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/geom/uzip/g_uzip.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/geom/virstor/binstream.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/geom/virstor/g_virstor.c cc1: warnings being treated as errors /src/sys/geom/virstor/g_virstor.c: In function 'g_virstor_destroy_geom': /src/sys/geom/virstor/g_virstor.c:731: warning: format '%d' expects type 'int', but argument 4 has type 'size_t' *** Error code 1 Stop in /obj/ia64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-09-23 12:50:42 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-09-23 12:50:42 - ERROR: failed to build lint kernel TB --- 2007-09-23 12:50:42 - tinderbox aborted TB --- 0.97 user 2.63 system 7292.70 real http://tinderbox.des.no/tinderbox-head-HEAD-ia64-ia64.full From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 14:24:29 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03E7A16A418; Sun, 23 Sep 2007 14:24:29 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id BB65D13C459; Sun, 23 Sep 2007 14:24:28 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.14.1/8.13.8) with ESMTP id l8NEOR5l064484; Sun, 23 Sep 2007 10:24:27 -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.14.1/8.14.1) with ESMTP id l8NEORMC095488; Sun, 23 Sep 2007 10:24:27 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 06E4273039; Sun, 23 Sep 2007 10:22:53 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070923142254.06E4273039@freebsd-current.sentex.ca> Date: Sun, 23 Sep 2007 10:22:53 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.91.1, clamav-milter version 0.91.1 on news X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 14:24:29 -0000 TB --- 2007-09-23 12:50:42 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-09-23 12:50:42 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2007-09-23 12:50:42 - cleaning the object tree TB --- 2007-09-23 12:51:05 - checking out the source tree TB --- 2007-09-23 12:51:05 - cd /tinderbox/HEAD/sparc64/sparc64 TB --- 2007-09-23 12:51:05 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-09-23 13:00:38 - building world (CFLAGS=-O2 -pipe) TB --- 2007-09-23 13:00:38 - cd /src TB --- 2007-09-23 13:00:38 - /usr/bin/make -B buildworld >>> World build started on Sun Sep 23 13:00:39 UTC 2007 >>> 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 >>> World build completed on Sun Sep 23 14:14:30 UTC 2007 TB --- 2007-09-23 14:14:30 - generating LINT kernel config TB --- 2007-09-23 14:14:30 - cd /src/sys/sparc64/conf TB --- 2007-09-23 14:14:30 - /usr/bin/make -B LINT TB --- 2007-09-23 14:14:30 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-09-23 14:14:30 - cd /src TB --- 2007-09-23 14:14:30 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Sep 23 14:14:31 UTC 2007 >>> 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 [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/geom/shsec/g_shsec.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/geom/stripe/g_stripe.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/geom/uzip/g_uzip.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/geom/virstor/binstream.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/geom/virstor/g_virstor.c cc1: warnings being treated as errors /src/sys/geom/virstor/g_virstor.c: In function 'g_virstor_destroy_geom': /src/sys/geom/virstor/g_virstor.c:731: warning: format '%d' expects type 'int', but argument 4 has type 'size_t' *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-09-23 14:22:53 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-09-23 14:22:53 - ERROR: failed to build lint kernel TB --- 2007-09-23 14:22:53 - tinderbox aborted TB --- 0.73 user 2.52 system 5531.16 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 15:07:24 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6419B16A418 for ; Sun, 23 Sep 2007 15:07:24 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id 7CF2A13C48D for ; Sun, 23 Sep 2007 15:07:22 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id D9E3145E90; Sun, 23 Sep 2007 17:07:20 +0200 (CEST) Received: from localhost (154.81.datacomsa.pl [195.34.81.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 105F745684; Sun, 23 Sep 2007 17:07:10 +0200 (CEST) Date: Sun, 23 Sep 2007 17:05:40 +0200 From: Pawel Jakub Dawidek To: FreeBSD Tinderbox Message-ID: <20070923150540.GA1123@garage.freebsd.pl> References: <20070923125042.C2C3A73039@freebsd-current.sentex.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL" Content-Disposition: inline In-Reply-To: <20070923125042.C2C3A73039@freebsd-current.sentex.ca> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: current@freebsd.org, ia64@freebsd.org Subject: Re: [head tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 15:07:24 -0000 --vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 23, 2007 at 08:50:42AM -0400, FreeBSD Tinderbox wrote: > TB --- 2007-09-23 10:49:09 - tinderbox 2.3 running on freebsd-current.sen= tex.ca > TB --- 2007-09-23 10:49:09 - starting HEAD tinderbox run for ia64/ia64 > TB --- 2007-09-23 10:49:09 - cleaning the object tree > TB --- 2007-09-23 10:49:43 - checking out the source tree > TB --- 2007-09-23 10:49:43 - cd /tinderbox/HEAD/ia64/ia64 > TB --- 2007-09-23 10:49:43 - /usr/bin/cvs -f -R -q -d/home/ncvs update -P= d -A src > TB --- 2007-09-23 10:58:25 - building world (CFLAGS=3D-O2 -pipe) > TB --- 2007-09-23 10:58:25 - cd /src > TB --- 2007-09-23 10:58:25 - /usr/bin/make -B buildworld > >>> World build started on Sun Sep 23 10:58:27 UTC 2007 > >>> 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 > >>> World build completed on Sun Sep 23 12:38:31 UTC 2007 > TB --- 2007-09-23 12:38:31 - generating LINT kernel config > TB --- 2007-09-23 12:38:31 - cd /src/sys/ia64/conf > TB --- 2007-09-23 12:38:31 - /usr/bin/make -B LINT > TB --- 2007-09-23 12:38:31 - building LINT kernel (COPTFLAGS=3D-O2 -pipe) > TB --- 2007-09-23 12:38:31 - cd /src > TB --- 2007-09-23 12:38:31 - /usr/bin/make buildkernel KERNCONF=3DLINT > >>> Kernel build for LINT started on Sun Sep 23 12:38:31 UTC 2007 > >>> 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 > [...] > cc -c -O2 -pipe -fno-strict-aliasing -std=3Dc99 -Wall -Wredundant-decls= -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith= -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostd= inc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/= src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-commo= n -finline-limit=3D15000 --param inline-unit-growth=3D100 --param large-fun= ction-growth=3D1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=3D= f32-f127 -fpic -ffreestanding -Werror /src/sys/geom/shsec/g_shsec.c > cc -c -O2 -pipe -fno-strict-aliasing -std=3Dc99 -Wall -Wredundant-decls= -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith= -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostd= inc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/= src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-commo= n -finline-limit=3D15000 --param inline-unit-growth=3D100 --param large-fun= ction-growth=3D1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=3D= f32-f127 -fpic -ffreestanding -Werror /src/sys/geom/stripe/g_stripe.c > cc -c -O2 -pipe -fno-strict-aliasing -std=3Dc99 -Wall -Wredundant-decls= -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith= -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostd= inc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/= src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-commo= n -finline-limit=3D15000 --param inline-unit-growth=3D100 --param large-fun= ction-growth=3D1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=3D= f32-f127 -fpic -ffreestanding -Werror /src/sys/geom/uzip/g_uzip.c > cc -c -O2 -pipe -fno-strict-aliasing -std=3Dc99 -Wall -Wredundant-decls= -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith= -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostd= inc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/= src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-commo= n -finline-limit=3D15000 --param inline-unit-growth=3D100 --param large-fun= ction-growth=3D1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=3D= f32-f127 -fpic -ffreestanding -Werror /src/sys/geom/virstor/binstream.c > cc -c -O2 -pipe -fno-strict-aliasing -std=3Dc99 -Wall -Wredundant-decls= -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith= -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostd= inc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/= src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-commo= n -finline-limit=3D15000 --param inline-unit-growth=3D100 --param large-fun= ction-growth=3D1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=3D= f32-f127 -fpic -ffreestanding -Werror /src/sys/geom/virstor/g_virstor.c > cc1: warnings being treated as errors > /src/sys/geom/virstor/g_virstor.c: In function 'g_virstor_destroy_geom': > /src/sys/geom/virstor/g_virstor.c:731: warning: format '%d' expects type = 'int', but argument 4 has type 'size_t' > *** Error code 1 >=20 > Stop in /obj/ia64/src/sys/LINT. > *** Error code 1 >=20 > Stop in /src. > *** Error code 1 I somehow don't feel guilty at all: -------------------------------------------------------------- >>> Kernel build for LINT completed on Sat Sep 22 02:08:24 UTC 2007 -------------------------------------------------------------- --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --vtzGhvizbBRQ85DL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFG9oDEForvXbEpPzQRAprfAKCSe2gOBZDqUNJLcLy8HqQTjv2FdACg6Cng JWlXqFGP0he6nYImJVibPsk= =Qu9m -----END PGP SIGNATURE----- --vtzGhvizbBRQ85DL-- From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 15:20:16 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A016116A41A; Sun, 23 Sep 2007 15:20:16 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 5F04E13C44B; Sun, 23 Sep 2007 15:20:16 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.8/8.13.8) with ESMTP id l8NFKFGk030413; Sun, 23 Sep 2007 11:20:15 -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.14.1/8.14.1) with ESMTP id l8NFKFjI038919; Sun, 23 Sep 2007 11:20:15 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 3DB7D73039; Sun, 23 Sep 2007 11:18:42 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070923151842.3DB7D73039@freebsd-current.sentex.ca> Date: Sun, 23 Sep 2007 11:18:42 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.91.1, clamav-milter version 0.91.1 on clamscanner4 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on sparc64/sun4v X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 15:20:16 -0000 TB --- 2007-09-23 13:53:58 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-09-23 13:53:58 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2007-09-23 13:53:58 - cleaning the object tree TB --- 2007-09-23 13:54:19 - checking out the source tree TB --- 2007-09-23 13:54:19 - cd /tinderbox/HEAD/sparc64/sun4v TB --- 2007-09-23 13:54:19 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-09-23 14:03:25 - building world (CFLAGS=-O2 -pipe) TB --- 2007-09-23 14:03:25 - cd /src TB --- 2007-09-23 14:03:25 - /usr/bin/make -B buildworld >>> World build started on Sun Sep 23 14:03:27 UTC 2007 >>> 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 >>> World build completed on Sun Sep 23 15:11:06 UTC 2007 TB --- 2007-09-23 15:11:06 - generating LINT kernel config TB --- 2007-09-23 15:11:06 - cd /src/sys/sun4v/conf TB --- 2007-09-23 15:11:06 - /usr/bin/make -B LINT TB --- 2007-09-23 15:11:07 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-09-23 15:11:07 - cd /src TB --- 2007-09-23 15:11:07 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Sep 23 15:11:07 UTC 2007 >>> 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 [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/geom/shsec/g_shsec.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/geom/stripe/g_stripe.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/geom/uzip/g_uzip.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/geom/virstor/binstream.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/geom/virstor/g_virstor.c cc1: warnings being treated as errors /src/sys/geom/virstor/g_virstor.c: In function 'g_virstor_destroy_geom': /src/sys/geom/virstor/g_virstor.c:731: warning: format '%d' expects type 'int', but argument 4 has type 'size_t' *** Error code 1 Stop in /obj/sun4v/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-09-23 15:18:41 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-09-23 15:18:41 - ERROR: failed to build lint kernel TB --- 2007-09-23 15:18:41 - tinderbox aborted TB --- 0.67 user 2.27 system 5083.50 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sun4v.full From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 15:38:26 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F3FB16A418; Sun, 23 Sep 2007 15:38:26 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id 1F92413C4C6; Sun, 23 Sep 2007 15:38:26 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 94F5C45E90; Sun, 23 Sep 2007 17:38:17 +0200 (CEST) Received: from localhost (154.81.datacomsa.pl [195.34.81.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 0A46D45B26; Sun, 23 Sep 2007 17:38:12 +0200 (CEST) Date: Sun, 23 Sep 2007 17:36:45 +0200 From: Pawel Jakub Dawidek To: FreeBSD Tinderbox Message-ID: <20070923153645.GC1123@garage.freebsd.pl> References: <20070923125042.C2C3A73039@freebsd-current.sentex.ca> <20070923150540.GA1123@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8NvZYKFJsRX2Djef" Content-Disposition: inline In-Reply-To: <20070923150540.GA1123@garage.freebsd.pl> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: current@freebsd.org, ia64@freebsd.org Subject: Re: [head tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 15:38:26 -0000 --8NvZYKFJsRX2Djef Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 23, 2007 at 05:05:40PM +0200, Pawel Jakub Dawidek wrote: > > cc1: warnings being treated as errors > > /src/sys/geom/virstor/g_virstor.c: In function 'g_virstor_destroy_geom': > > /src/sys/geom/virstor/g_virstor.c:731: warning: format '%d' expects typ= e 'int', but argument 4 has type 'size_t' > > *** Error code 1 > >=20 > > Stop in /obj/ia64/src/sys/LINT. > > *** Error code 1 > >=20 > > Stop in /src. > > *** Error code 1 >=20 > I somehow don't feel guilty at all: >=20 > -------------------------------------------------------------- > >>> Kernel build for LINT completed on Sat Sep 22 02:08:24 UTC 2007 > -------------------------------------------------------------- Ok, this was my bug. I compiled LINT on 32bit platform only after last changes, so I do feel very guilty after all. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --8NvZYKFJsRX2Djef Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFG9ogNForvXbEpPzQRAuVhAKDsfabv+P37Gy+pi4ZqyTHvQNgMEwCgn2ji blEwY6axRZOFDkSodq6pLzA= =Bk0a -----END PGP SIGNATURE----- --8NvZYKFJsRX2Djef-- From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 17:30:57 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 648BC16A420; Sun, 23 Sep 2007 17:30:57 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 0466513C468; Sun, 23 Sep 2007 17:30:56 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.8/8.13.8) with ESMTP id l8NHUugQ035998; Sun, 23 Sep 2007 13:30:56 -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.14.1/8.14.1) with ESMTP id l8NHUuld002573; Sun, 23 Sep 2007 13:30:56 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id A3ED573039; Sun, 23 Sep 2007 13:29:22 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070923172922.A3ED573039@freebsd-current.sentex.ca> Date: Sun, 23 Sep 2007 13:29:22 -0400 (EDT) X-Virus-Scanned: ClamAV version devel-20070102, clamav-milter version devel-111206 on clamscanner5 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 17:30:57 -0000 TB --- 2007-09-23 15:20:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-09-23 15:20:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2007-09-23 15:20:00 - cleaning the object tree TB --- 2007-09-23 15:20:39 - checking out the source tree TB --- 2007-09-23 15:20:39 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2007-09-23 15:20:39 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-09-23 15:31:36 - building world (CFLAGS=-O2 -pipe) TB --- 2007-09-23 15:31:36 - cd /src TB --- 2007-09-23 15:31:36 - /usr/bin/make -B buildworld >>> World build started on Sun Sep 23 15:31:37 UTC 2007 >>> 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 >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Sun Sep 23 17:19:26 UTC 2007 TB --- 2007-09-23 17:19:26 - generating LINT kernel config TB --- 2007-09-23 17:19:26 - cd /src/sys/amd64/conf TB --- 2007-09-23 17:19:26 - /usr/bin/make -B LINT TB --- 2007-09-23 17:19:26 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-09-23 17:19:26 - cd /src TB --- 2007-09-23 17:19:26 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Sep 23 17:19:26 UTC 2007 >>> 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 [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/geom/shsec/g_shsec.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/geom/stripe/g_stripe.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/geom/uzip/g_uzip.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/geom/virstor/binstream.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/geom/virstor/g_virstor.c cc1: warnings being treated as errors /src/sys/geom/virstor/g_virstor.c: In function 'g_virstor_destroy_geom': /src/sys/geom/virstor/g_virstor.c:731: warning: format '%d' expects type 'int', but argument 4 has type 'size_t' *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-09-23 17:29:22 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-09-23 17:29:22 - ERROR: failed to build lint kernel TB --- 2007-09-23 17:29:22 - tinderbox aborted TB --- 0.95 user 3.69 system 7761.86 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 17:59:31 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B57C16A418 for ; Sun, 23 Sep 2007 17:59:31 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from webaccess-cl.virtdom.com (webaccess-cl.virtdom.com [216.240.101.25]) by mx1.freebsd.org (Postfix) with ESMTP id 4857613C48A for ; Sun, 23 Sep 2007 17:59:31 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from [192.168.1.103] (c-67-160-44-208.hsd1.wa.comcast.net [67.160.44.208]) (authenticated bits=0) by webaccess-cl.virtdom.com (8.13.6/8.13.6) with ESMTP id l8NHxRe3066035 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Sun, 23 Sep 2007 13:59:29 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Sun, 23 Sep 2007 11:02:12 -0700 (PDT) From: Jeff Roberson X-X-Sender: jroberson@10.0.0.1 To: Peter Kostouros In-Reply-To: <46F609DC.3070809@melbpc.org.au> Message-ID: <20070923110135.C547@10.0.0.1> References: <46F609DC.3070809@melbpc.org.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: [panic] sched_priority: invalid interactive priority 124 score -4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 17:59:31 -0000 On Sun, 23 Sep 2007, Peter Kostouros wrote: > Hi > > I received the abovementioned panic on a system csup'ed and build a few hours > ago and have attached a debug session I hope will help. Peter, Thanks for your debugging efforts. The problem was with my most recent commit. You can back out to 1.207 or try this patch, which csjp reports fixes the problem: http://people.freebsd.org/~jeff/ulebugs.diff Thanks, Jeff > > Note that I am using the ULE scheduler: version of sched_ule.c is 1.208 > (2007/09/22). > > Let me know if I can provide further information. > > -- > > Regards > > Peter > > As always the organisation disavows knowledge of this email > > From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 18:13:03 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14AAC16A417 for ; Sun, 23 Sep 2007 18:13:03 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.73]) by mx1.freebsd.org (Postfix) with ESMTP id DC61D13C474 for ; Sun, 23 Sep 2007 18:13:02 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (smtpin03-en2 [10.13.10.148]) by smtpoutm.mac.com (Xserve/smtpout010/MantshX 4.0) with ESMTP id l8NID2eX026242 for ; Sun, 23 Sep 2007 11:13:02 -0700 (PDT) Received: from [172.16.1.6] (209-128-86-226.bayarea.net [209.128.86.226]) (authenticated bits=0) by mac.com (Xserve/smtpin03/MantshX 4.0) with ESMTP id l8NICwKl021293 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Sun, 23 Sep 2007 11:12:59 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: 7bit Message-Id: <043BBA16-A303-438D-97BE-950FEABB71A8@mac.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: FreeBSD Current From: Marcel Moolenaar Date: Sun, 23 Sep 2007 11:11:39 -0700 X-Mailer: Apple Mail (2.752.3) Subject: panic: mtx_lock() of destroyed mutex @ route.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 18:13:03 -0000 All, The following panic happened on pluto1.freebsd.org: login: Sep 20 09:43:20 pluto1 sshd[77174]: fatal: Read from socket failed: Connection reset by peer Sep 20 14:38:20 pluto1 sshd[77835]: fatal: Read from socket failed: Connection reset by peer Sep 20 14:40:10 pluto1 sshd[53908]: error: setsockopt TCP_NODELAY: Connection reset by peer Sep 20 14:40:10 pluto1 last message repeated 2 times Sep 20 14:43:31 pluto1 sshd[53908]: error: setsockopt TCP_NODELAY: Connection reset by peer Sep 20 14:43:38 pluto1 last message repeated 24 times Sep 21 01:23:20 pluto1 sshd[79326]: fatal: Read from socket failed: Connection reset by peer Sep 21 03:13:20 pluto1 sshd[79711]: fatal: Read from socket failed: Connection reset by peer Sep 21 05:11:18 pluto1 sshd[53908]: error: setsockopt TCP_NODELAY: Connection reset by peer Sep 21 05:11:23 pluto1 last message repeated 17 times Sep 22 19:48:21 pluto1 sshd[86444]: fatal: Read from socket failed: Connection reset by peer Sep 22 20:55:15 pluto1 sshd[53908]: error: setsockopt TCP_NODELAY: Connection reset by peer Sep 22 20:55:20 pluto1 last message repeated 8 times Sep 23 01:28:54 pluto1 sshd[53908]: error: setsockopt TCP_NODELAY: Connection reset by peer Sep 23 01:28:59 pluto1 last message repeated 55 times panic: mtx_lock() of destroyed mutex @ /p/7.x/src/sys/net/route.c:1303 cpuid = 1 KDB: enter: panic [thread pid 53908 tid 100111 ] Stopped at kdb_enter+0x81: [F1] nop.f 0x0 db> ps pid ppid pgrp uid state wmesg wchan cmd 53909 53908 53909 618 Ss+ ttyin 0xe000000010433010 tcsh 53908 687 53908 0 Rs CPU 1 sshd 782 1 782 0 Ss+ ttyin 0xe00000001052cc10 getty 781 1 781 0 Ss+ ttyin 0xe000000010536010 getty 764 1 764 0 Ss select 0xe00000000480ce30 inetd 706 1 706 0 Ss nanslp 0xe000000004778b00 cron 699 1 699 25 Ss pause 0xe0000000109576a0 sendmail 693 1 693 0 Ss select 0xe00000000480ce30 sendmail 687 1 687 0 Ss select 0xe00000000480ce30 sshd 678 1 678 1 Ss sbwait 0xe000000010913464 rwhod 665 1 665 0 Ss select 0xe00000000480ce30 ntpd 618 614 614 0 S - 0xe0000000106f3a00 nfsd 617 614 614 0 S - 0xe000000010749600 nfsd 616 614 614 0 S - 0xe000000010747a00 nfsd 615 614 614 0 S - 0xe0000000106f1600 nfsd 614 1 614 0 Ss select 0xe00000000480ce30 nfsd 612 1 612 0 Ss select 0xe00000000480ce30 mountd 555 1 555 0 Ss select 0xe00000000480ce30 ypbind 542 1 542 0 Ss select 0xe00000000480ce30 rpcbind 518 1 518 0 Ss select 0xe00000000480ce30 syslogd 458 1 458 0 Ss select 0xe00000000480ce30 devd 159 1 159 0 Ss pause 0xe0000000106ea520 adjkerntz 46 0 0 0 SL - 0xe000000004778a20 [schedcpu] 45 0 0 0 SL sdflush 0xe000000004779ac8 [softdepflush] 44 0 0 0 SL syncer 0xe000000004778a24 [syncer] 43 0 0 0 SL vlruwt 0xe00000001059cd20 [vnlru] 42 0 0 0 SL psleep 0xe0000000047790d4 [bufdaemon] 41 0 0 0 SL pgzero 0xe000000004779da4 [pagezero] 40 0 0 0 SL psleep 0xe000000004779d50 [vmdaemon] 39 0 0 0 SL psleep 0xe000000004779d64 [pagedaemon] 38 0 0 0 WL [swi0: uart uart+++] 37 0 0 0 RL CPU 0 [irq29: bge0] 36 0 0 0 SL idle 0xa000000000022000 [mpt_recovery1] 35 0 0 0 WL [irq28: mpt1] 34 0 0 0 SL idle 0xa00000000000c000 [mpt_recovery0] 33 0 0 0 WL [irq27: mpt0] 32 0 0 0 WL [irq20: fxp0] 31 0 0 0 WL [irq21: atapci0] 30 0 0 0 SL usbevt 0xe000000010469420 [usb2] 29 0 0 0 WL [irq18: ehci0] 28 0 0 0 SL usbevt 0xe000000010442420 [usb1] 27 0 0 0 WL [irq17: ohci1] 26 0 0 0 SL usbtsk 0xe00000000477fd78 [usbtask-dr] 25 0 0 0 SL usbtsk 0xe00000000477fd50 [usbtask-hc] 24 0 0 0 SL usbevt 0xe0000000103b0420 [usb0] 23 0 0 0 WL [irq16: ohci0] 22 0 0 0 SL tzpoll 0xe000000004778148 [acpi_thermal] 21 0 0 0 WL [irq36: acpi0] 20 0 0 0 WL [swi6: task queue] 19 0 0 0 WL [swi6: Giant taskq] 18 0 0 0 SL - 0xe00000001036ee00 [thread taskq] 17 0 0 0 WL [swi5: +] 16 0 0 0 WL [swi2: cambio] 9 0 0 0 SL ccb_scan 0xe00000000477a020 [xpt_thrd] 8 0 0 0 SL - 0xe00000001036f180 [kqueue taskq] 7 0 0 0 SL - 0xe00000001036f200 [acpi_task_2] 6 0 0 0 SL - 0xe00000001036f200 [acpi_task_1] 5 0 0 0 SL - 0xe00000001036f200 [acpi_task_0] 15 0 0 0 SL - 0xe000000004778a20 [yarrow] 4 0 0 0 SL - 0xe0000000047785b8 [g_down] 3 0 0 0 SL - 0xe0000000047785b0 [g_up] 2 0 0 0 SL - 0xe0000000047785a0 [g_event] 14 0 0 0 WL [swi1: net] 13 0 0 0 WL [swi3: vm] 12 0 0 0 RL [swi4: clock] 11 0 0 0 RL [idle: cpu0] 10 0 0 0 RL [idle: cpu1] 1 0 1 0 SLs wait 0xe000000010372000 [init] 0 0 0 0 WLs [swapper] db> bt Tracing pid 53908 tid 100111 td 0xe000000010959440 kdb_enter(0xe000000004660b20, 0xe0000000042e2ad0, 0x793, 0xa000000033b9f1a8) at kdb_enter+0x81 panic(0xe00000000465f758, 0xe000000004672a18, 0x517, 0x507, 0xe00000000480ccf8) at panic+0x2e0 _mtx_lock_flags(0xe00000002ae49920, 0x0, 0xe000000004672a18, 0x517) at _mtx_lock_flags+0x90 rt_check(0xa000000033b9f1e0, 0xa000000033b9f1f0, 0xe00000002ae49920, 0xe00000002ae49860) at rt_check+0x1e0 arpresolve(0xe000000010351000, 0xe00000001073b770, 0xe000000010754e00, 0xe000000010542ef0, 0xa000000033b9f208) at arpresolve+0x170 ether_output(0xe000000010351000, 0xe000000010754e00, 0xe000000010542ef0, 0xe00000001073b770, 0x0) at ether_output+0x120 ip_output(0xe000000010754e62, 0xe000000010542ef0, 0xa000000033b9f228, 0x0, 0x0, 0xe0000000108f0230, 0xe000000010754e6a) at ip_output+0x19e0 tcp_output(0xe0000000109d10e0, 0xe0000000109d1140, 0xe0000000109d11e8, 0xe00000000480fc20) at tcp_output+0x2ab0 tcp_usr_shutdown(0xe00000407bbd82b8) at tcp_usr_shutdown+0x100 soshutdown(0xe00000407bbd82b8, 0x1, 0xe00000000474bf10, 0xe00000000439d2f0) at soshutdown+0xb0 shutdown(0xe000000010959440, 0xa000000033b9f4e8, 0x0, 0xe00000000461e3e0) at shutdown+0x90 syscall(0xa000000033b9f400, 0x86, 0x20000000401331d0, 0xe000000010959440, 0xe00000001095fa40, 0xe000000004734948, 0x86, 0xa000000033b9f4e8) at syscall+0x3e0 epc_syscall_return() at epc_syscall_return db> thread 100028 [thread pid 37 tid 100028 ] interrupt+0x760: [M0] ld4.acq r14=[r36] db> bt Tracing pid 37 tid 100028 td 0xe0000000103757a0 interrupt(0xa000000031349000) at interrupt+0x760 ivt_External_Interrupt() at ivt_External_Interrupt+0x30 --- trapframe at 0xa000000031349000 _mtx_lock_sleep(0xe00000001073b830, 0xe0000000103757a0, 0x0, 0xe00000001073b850, 0xe000000010959440) at _mtx_lock_sleep+0x221 _mtx_lock_flags(0xe00000001073b830, 0x0, 0xe000000004672a18, 0x524) at _mtx_lock_flags+0x170 rt_check(0xa000000031349260, 0xa000000031349270, 0xe000000004672a18, 0xe0000000120d2000) at rt_check+0x420 arpresolve(0xe000000010351000, 0xe00000001073b770, 0xe000000012faf700, 0xe000000010542ef0, 0xa000000031349288) at arpresolve+0x170 ether_output(0xe000000010351000, 0xe000000012faf700, 0xe000000010542ef0, 0xe00000001073b770, 0x0) at ether_output+0x120 ip_output(0xe000000012faf762, 0xe000000010542ef0, 0xa0000000313492a8, 0x0, 0x0, 0xe0000000143f8c08, 0xe000000012faf76a) at ip_output+0x19e0 tcp_output(0xe0000000108f42d0, 0xe0000000108f4330, 0xe0000000108f43d8, 0xe00000000480fc20, 0xe00000000480fbf8) at tcp_output+0x2ab0 tcp_do_segment(0xe000004078d50e00, 0xe000004048d35024, 0xe000000010913b30, 0xe0000000108f42d0, 0x34, 0x18, 0x0) at tcp_do_segment+0x1560 tcp_input(0xe000004078d50e00, 0x34, 0xe000004078d50e28, 0xe000004048d35026, 0xe0000000143f8c08) at tcp_input+0x1b30 ip_input(0xe000004048d35010, 0x14, 0x0, 0x14) at ip_input+0x13f0 netisr_dispatch(0x2, 0xe000004078d50e00, 0xe00000000440db60, 0x289) at netisr_dispatch+0x190 ether_demux(0xa000000031349530, 0x800, 0xe00000000440e870, 0x30b, 0xe000000004960060) at ether_demux+0x570 ether_input(0xe000000010351000, 0xe000004048d35002, 0x800000000000000, 0xe00000000414e880) at ether_input+0xa50 bge_intr(0xe000004078d50e00, 0xe000004078d50e10, 0xa0000000314e00e0, 0xa000000000038000) at bge_intr+0x1340 ithread_loop(0xe00000001049a8c0, 0xe000000010520a00, 0x0, 0xe00000000465c778) at ithread_loop+0x420 fork_exit(0xe000000004695dc0, 0xe00000001049a8c0, 0xa000000031349550) at fork_exit+0x110 enter_userland() at enter_userland db> show alllocks Process 53908 (sshd) thread 0xe000000010959440 (100111) exclusive sleep mutex rtentry r = 0 (0xe00000001073b830) locked @ /p/ 7.x/src/sys/net/route.c:1287 exclusive sleep mutex inp (tcpinp) r = 0 (0xe0000000108f0318) locked @ /p/7.x/src/sys/netinet/tcp_usrreq.c:695 exclusive sleep mutex tcp r = 0 (0xe00000000480fb40) locked @ /p/7.x/ src/sys/netinet/tcp_usrreq.c:692 Process 678 (rwhod) thread 0xe0000000106ecd80 (100076) exclusive sx so_rcv_sx r = 0 (0xe000000010913408) locked @ /p/7.x/src/ sys/kern/uipc_sockbuf.c:145 Process 37 (irq29: bge0) thread 0xe0000000103757a0 (100028) exclusive sleep mutex rtentry r = 0 (0xe0000000120d20c0) locked @ /p/ 7.x/src/sys/net/route.c:788 exclusive sleep mutex radix node head r = 1 (0xe0000000105520f0) locked @ /p/7.x/src/sys/net/route.c:684 exclusive sleep mutex inp (tcpinp) r = 0 (0xe0000000143f8cf0) locked @ /p/7.x/src/sys/netinet/tcp_input.c:477 db> FYI, -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 19:17:11 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A995F16A421 for ; Sun, 23 Sep 2007 19:17:11 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.freebsd.org (Postfix) with ESMTP id 79E2013C47E for ; Sun, 23 Sep 2007 19:17:06 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.13.6) with ESMTP id l8NJFh9o074532; Sun, 23 Sep 2007 12:15:43 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id l8NJFaQd074531; Sun, 23 Sep 2007 12:15:36 -0700 (PDT) (envelope-from rizzo) Date: Sun, 23 Sep 2007 12:15:36 -0700 From: Luigi Rizzo To: ticso@cicely.de Message-ID: <20070923121536.C74417@xorpc.icir.org> References: <20070921103829.A43801@xorpc.icir.org> <20070922093557.GC32918@cicely12.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20070922093557.GC32918@cicely12.cicely.de>; from ticso@cicely12.cicely.de on Sat, Sep 22, 2007 at 11:35:58AM +0200 Cc: current@freebsd.org Subject: Re: Why USB must be so hard to use ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 19:17:11 -0000 On Sat, Sep 22, 2007 at 11:35:58AM +0200, Bernd Walter wrote: ... > Since it's using an Atmel ARM. > I had to create the following umodem patch to get a pseudo serial > port for accessing the sam-ba CDC for flashing the controller: > Index: umodem.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/usb/umodem.c,v > retrieving revision 1.57 > diff -u -r1.57 umodem.c > --- umodem.c 31 Jan 2005 13:58:10 -0000 1.57 > +++ umodem.c 20 Aug 2006 17:05:34 -0000 > @@ -256,6 +260,15 @@ > id->bInterfaceProtocol == UIPROTO_CDC_AT) > ret = UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO; > > +#if 1 > + if (ret == UMATCH_NONE && > + id->bInterfaceClass == UICLASS_CDC_DATA && > + id->bInterfaceSubClass == UISUBCLASS_DATA && > + id->bInterfaceProtocol == 0x00) > + ret = UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO; > + return ret; > +#endif yes, this is similar to what i did except that i only returned UMATCH_IFACECLASS if the two other fields don't match. ... > We should really have a generic CDC tty driver, since it is used > very often for simple USB projects. i totally agree. cheers luigi From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 19:30:39 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F5B116A419 for ; Sun, 23 Sep 2007 19:30:39 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by mx1.freebsd.org (Postfix) with ESMTP id C9C0513C469 for ; Sun, 23 Sep 2007 19:30:38 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp5-g19.free.fr (localhost.localdomain [127.0.0.1]) by smtp5-g19.free.fr (Postfix) with ESMTP id 5516E8730A; Sun, 23 Sep 2007 21:30:37 +0200 (CEST) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp5-g19.free.fr (Postfix) with ESMTP id 53FA887082; Sun, 23 Sep 2007 21:30:36 +0200 (CEST) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id 8A14F9B497; Sun, 23 Sep 2007 19:28:57 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id 76B5C405B; Sun, 23 Sep 2007 21:28:57 +0200 (CEST) Date: Sun, 23 Sep 2007 21:28:57 +0200 From: Jeremie Le Hen To: Jeff Roberson Message-ID: <20070923192857.GA54681@obiwan.tataz.chchile.org> References: <46F609DC.3070809@melbpc.org.au> <20070923110135.C547@10.0.0.1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070923110135.C547@10.0.0.1> User-Agent: Mutt/1.5.15 (2007-04-06) Cc: freebsd-current@freebsd.org Subject: Re: [panic] sched_priority: invalid interactive priority 124 score -4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 19:30:39 -0000 Hi Jeff, On Sun, Sep 23, 2007 at 11:02:12AM -0700, Jeff Roberson wrote: > Thanks for your debugging efforts. The problem was with my most recent > commit. You can back out to 1.207 or try this patch, which csjp reports > fixes the problem: > > http://people.freebsd.org/~jeff/ulebugs.diff I've undergone this panic too. I can confirm this works for me. Thank you. Best regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 20:00:39 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0157F16A417 for ; Sun, 23 Sep 2007 20:00:39 +0000 (UTC) (envelope-from h.schmalzbauer@omnisec.de) Received: from host.omnisec.de (host.omnisec.de [62.245.232.135]) by mx1.freebsd.org (Postfix) with ESMTP id 4C10113C448 for ; Sun, 23 Sep 2007 20:00:38 +0000 (UTC) (envelope-from h.schmalzbauer@omnisec.de) Received: from tek.flintsbach.schmalzbauer.de (tek.flintsbach.schmalzbauer.de [172.21.2.3]) by host.omnisec.de (8.13.8/8.13.8) with ESMTP id l8NK0VRu053945 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 23 Sep 2007 22:00:37 +0200 (CEST) (envelope-from h.schmalzbauer@omnisec.de) Received: from titan.flintsbach.schmalzbauer.de (titan.flintsbach.schmalzbauer.de [IPv6:fec0::1:0:0:1:1]) by tek.flintsbach.schmalzbauer.de (8.13.8/8.13.8) with ESMTP id l8NK0VCl026390 for ; Sun, 23 Sep 2007 22:00:31 +0200 (CEST) (envelope-from h.schmalzbauer@omnisec.de) Received: by titan.flintsbach.schmalzbauer.de (8.14.1/8.14.1/Submit) id l8NK1unV061073 for freebsd-current@freebsd.org; Sun, 23 Sep 2007 22:01:56 +0200 (CEST) (envelope-from h.schmalzbauer@omnisec.de) X-Authentication-Warning: titan.flintsbach.schmalzbauer.de: harry set sender to h.schmalzbauer@omnisec.de using -f From: Harald Schmalzbauer Organization: OmniSEC To: freebsd-current@freebsd.org Date: Sun, 23 Sep 2007 22:01:50 +0200 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1495033.ZLgmse6FlN"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200709232201.56777.h.schmalzbauer@omnisec.de> Subject: SATA DVD-Drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 20:00:39 -0000 --nextPart1495033.ZLgmse6FlN Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, I was wondering if there's a chance to get a SATA DVD drive working. I have a ich9 controller in AHCI mode and a JMB363 with no fixed mode, but = my=20 drive doesn't get recognized on the ich9 controller in AHCI nor on the=20 JMB363, neither in AHCI nor in IDE/RAID mode. Instead I have a very strange issue when the drive is connected to the JBM3= 63: Xorg stops working with the nvidia driver, it can't find a card anymore...= =20 Very strange, as soon as I unplug the drive xorg works fine again. But that's another matter. Thanks for any hints, =2DHarry --nextPart1495033.ZLgmse6FlN Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBG9sY0LDqVQ9VXb8gRAov0AJwKKoJ7T0zjdBlVm46I+DDqu9xL8gCcCpdG 52oLNayZcYlD5u6SAxeeozA= =HeIg -----END PGP SIGNATURE----- --nextPart1495033.ZLgmse6FlN-- From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 21:16:28 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2AF616A418 for ; Sun, 23 Sep 2007 21:16:28 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.185]) by mx1.freebsd.org (Postfix) with ESMTP id 89E2613C45D for ; Sun, 23 Sep 2007 21:16:28 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so1112255rvb for ; Sun, 23 Sep 2007 14:16:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=UQCQvJH0y5APNGt4c4jzHrQ0U6lBFejXBwSsVd6qXkg=; b=l1hZLTg7eluAcKcrgHF1mF7NDfn9Gi4uub8V3SmjbExHJ6loMPh0uFkifJ1FlXZvtHNwQdX28Gli4mhg6zuj+7X1kxPMdpgxqlLUzLtrub/2tfShcddRjVQRvOpUrvzN+riLq8S4xtX2tjZboUrDTCSfoY1xyViuyz4jxYKaEvw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=uLZIuonTj1EXfId5IK4/neDgvxo7B6eneKuOOU4i/qJRF3xpB9AF38MEjkWctFBO82kyCFsCMfkDpQG20Ami7a2T3lJ5fcb4iuJmxXwqkaxwIG6SlhtyevnfV0/j68aTksBhw9SMSEm75Tc/Lq7Bi2Cm/NAg39v0VfqcXKmOzAA= Received: by 10.141.79.12 with SMTP id g12mr1464594rvl.1190580464964; Sun, 23 Sep 2007 13:47:44 -0700 (PDT) Received: by 10.140.141.10 with HTTP; Sun, 23 Sep 2007 13:47:44 -0700 (PDT) Message-ID: <2e77fc10709231347x1823587ckc24b2d96099f48fb@mail.gmail.com> Date: Sun, 23 Sep 2007 23:47:44 +0300 From: "Niki Denev" Sender: ndenev@gmail.com To: "Harald Schmalzbauer" In-Reply-To: <200709232201.56777.h.schmalzbauer@omnisec.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200709232201.56777.h.schmalzbauer@omnisec.de> X-Google-Sender-Auth: 744a66d63698b305 Cc: current@freebsd.org Subject: Re: SATA DVD-Drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 21:16:28 -0000 2007/9/23, Harald Schmalzbauer : > Hello, > > I was wondering if there's a chance to get a SATA DVD drive working. > I have a ich9 controller in AHCI mode and a JMB363 with no fixed mode, but my > drive doesn't get recognized on the ich9 controller in AHCI nor on the > JMB363, neither in AHCI nor in IDE/RAID mode. > Instead I have a very strange issue when the drive is connected to the JBM363: > Xorg stops working with the nvidia driver, it can't find a card anymore... > Very strange, as soon as I unplug the drive xorg works fine again. > But that's another matter. > > Thanks for any hints, > > -Harry > > Hi, I've had similar problems with ICH8 mobo. Seems like no matter what mode i set for the JMicron controller (ide/raid/ahci) freebsd sees it as ahci and optical drive does not work. However i made my SATA DVD drive work by putting it on a ICH sata port and setting IDE mode. I've also had exacly the same issue with Xorg and Nvidia driver when i have JMicron enabled, and it seems that when i enable the "memory remapping feature" in the BIOS it works again properly. And btw, this is on Asus P5B Deluxe motherboard. hth, Niki From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 21:18:28 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4588E16A419 for ; Sun, 23 Sep 2007 21:18:28 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) by mx1.freebsd.org (Postfix) with ESMTP id 03C8B13C465 for ; Sun, 23 Sep 2007 21:18:27 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org ([192.147.25.65]:58413) by thebighonker.lerctr.org with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IZYqP-000Auk-6Y; Sun, 23 Sep 2007 16:18:26 -0500 Date: Sun, 23 Sep 2007 16:18:20 -0500 (CDT) From: Larry Rosenman To: Claus Guttesen In-Reply-To: Message-ID: <20070923161722.B41582@thebighonker.lerctr.org> References: <20070921102946.T11189@borg> <46F415BF.9010500@FreeBSD.org> <20070921140550.D96923@thebighonker.lerctr.org> <46F41CFF.6080108@FreeBSD.org> <46F58799.1030702@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: -4.4 (----) X-LERCTR-Spam-Score: -4.4 (----) X-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8,BAYES_00=-2.599 X-LERCTR-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8,BAYES_00=-2.599 DomainKey-Status: no signature Cc: Darren Reed , freebsd-current@freebsd.org Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 21:18:28 -0000 On Sun, 23 Sep 2007, Claus Guttesen wrote: >> So I just received this courtesy of ZFS: >> panic: kmem_malloc(131072): kmem_map too small: 343027712 total allocated >> cpuid = 0 >> KDB: enter: panic >> >> This was with these settings in loader.conf: >> vm.kmem_size=419430400 >> vm.kmem_size_max=419430400 >> vfs.zfs.arc_max=409715200 > > How much ram do you have? Is this amd64 or i386? In my case, 4Gig ram, amd64, and I've seen the panic even with 750M vm.kmem_size. Do we have guidelines on what vm.kmem_size(|_max) should be set to? LER > > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 21:45:10 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B56FB16A421; Sun, 23 Sep 2007 21:45:10 +0000 (UTC) (envelope-from louie@transsys.com) Received: from ringworld.transsys.com (ringworld.transsys.com [144.202.0.15]) by mx1.freebsd.org (Postfix) with ESMTP id 58B7E13C4AC; Sun, 23 Sep 2007 21:45:10 +0000 (UTC) (envelope-from louie@transsys.com) Received: from [144.202.1.88] (c-69-141-143-164.hsd1.nj.comcast.net [69.141.143.164]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: louie) by ringworld.transsys.com (Postfix) with ESMTP id 06E925C4C; Sun, 23 Sep 2007 17:12:41 -0400 (EDT) In-Reply-To: <46F614F2.4050402@freebsd.org> References: <2a41acea0709221656n4aa62776y488c7f2da262c9f6@mail.gmail.com> <46F614F2.4050402@freebsd.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Louis Mamakos Date: Sun, 23 Sep 2007 17:12:40 -0400 To: Darren Reed X-Mailer: Apple Mail (2.752.2) Cc: Kip Macy , FreeBSD Current , Jack Vogel , "freebsd-net@freebsd.org" Subject: Re: TX Multiqueue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 21:45:10 -0000 We've seen problems on other OS's where the locking in the device driver around the process of queuing packets to the device was a performance issue when trying to send relatively small packets. As a workaround, we ended up doing a multi-link/bonding thing over multiple interfaces to get the throughput. This was on an SMP system and the application was such that there were multiple execution threads running in parallel. Having multiple queues, even for a single class of traffic may enable enough additional concurrency in the driver to increase throughput. It's up to driver to use some algorithm to spread the load over the queues to ensure that specific "flows" stay in order, same as if you we doing ether- channel bonding. Of course, if the transmit path through the network stack isn't enabling concurrency, a bottleneck there won't be an issue. Louis Mamakos Just something else to consider.. On Sep 23, 2007, at 3:25 AM, Darren Reed wrote: > Kip Macy wrote: >> My ethng branch supports multiple rx and tx queues. >> >> -Kip >> > > What are your plans for how we use/manage/interact with the mutiple > rx/tx queues? > > Darren > > >> On 9/22/07, Jack Vogel wrote: >> > Our newest E1000 nic, the 82575, and the Oplin 10G hardware are >> capable of >> > multiple queues both on the receive and the send side. On the >> receive end for >> > the Oplin driver the queues actually help distribute interrupts >> and improve >> > performance without any special support in the stack. >> > >> > I have been asked about multiple queues on the TX side, embedded >> appliance >> > type system builders for instance are interested I suppose for >> > priority queueing. >> > Is anyone working on this right now, and if not does this sound >> like something >> > anyone is interested in doing? >> > >> > I would like to see MQ on both TX and RX that drivers could use >> if able. >> > >> > Jack >> > _______________________________________________ >> > freebsd-net@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-net >> > To unsubscribe, send any mail to "freebsd-net- >> 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 Sun Sep 23 21:50:00 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65CE916A419 for ; Sun, 23 Sep 2007 21:50:00 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id B222A13C469 for ; Sun, 23 Sep 2007 21:49:59 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (dialup96.ach.sch.gr [81.186.70.96]) (authenticated bits=128) by igloo.linux.gr (8.14.1/8.14.1/Debian-9) with ESMTP id l8NLnOx5025000 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 24 Sep 2007 00:49:36 +0300 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.1/8.14.1) with ESMTP id l8NLnMnb011815; Mon, 24 Sep 2007 00:49:23 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.14.1/8.14.1/Submit) id l8NLnLY7011806; Mon, 24 Sep 2007 00:49:21 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Mon, 24 Sep 2007 00:49:20 +0300 From: Giorgos Keramidas To: Darren Reed Message-ID: <20070923214920.GA11664@kobe.laptop> References: <46F6379B.9050000@freebsd.org> <46F64A4B.8000804@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46F64A4B.8000804@freebsd.org> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.902, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.50, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-current@freebsd.org Subject: Re: yacc bug in reader.c:end_rule() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 21:50:00 -0000 On 2007-09-23 04:13, Darren Reed wrote: > The following sample grammar will exercise the bug: > > %{ > %} > > %union { > char *ptr; > }; > > %type test > %% > > test: | $$ = malloc(2); > ; > > %% There's definitely a bug somewhere in yacc(1), which this triggers. On 7.0-CURRENT #0: Fri Sep 21 19:09:58 EEST 2007, when I use the following Makefile and this sample grammar, I get: % keramida@kobe:/home/keramida/tmp/yt$ cat -n Makefile % 1 PROG= foo % 2 % 3 SRCS= foo.y % 4 % 5 WARNS?= 6 % 6 WFORMAT?= 2 % 7 % 8 .include % keramida@kobe:/home/keramida/tmp/yt$ make % Warning: Object directory not changed from original /home/keramida/tmp/yt % yacc -d -o foo.c foo.y % *** Signal 11 % % Stop in /home/keramida/tmp/yt. % keramida@kobe:/home/keramida/tmp/yt$ I just happened to be running a userland with DEBUG_FLAGS='-g' and the stack trace of yacc(1) is: % (gdb) where % #0 0x080505ba in end_rule () at /home/build/src/usr.bin/yacc/reader.c:1260 % #1 0x08052920 in read_grammar () at /home/build/src/usr.bin/yacc/reader.c:1621 % #2 0x08053b45 in reader () at /home/build/src/usr.bin/yacc/reader.c:1926 % #3 0x0804b792 in main (argc=Cannot access memory at address 0xc % ) at /home/build/src/usr.bin/yacc/main.c:434 % (gdb) list /home/build/src/usr.bin/yacc/reader.c:1260 % 1255 int i; % 1256 % 1257 if (!last_was_action && plhs[nrules]->tag) % 1258 { % 1259 for (i = nitems - 1; pitem[i]; --i) continue; % 1260 if (pitem[i+1] == 0 || pitem[i+1]->tag != plhs[nrules]->tag) % 1261 default_action_warning(); % 1262 } % 1263 % 1264 last_was_action = 0; % (gdb) If there's anything else I can do to help track this down, please feel free to let me know. - Giorgos From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 22:08:15 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F06A516A41B for ; Sun, 23 Sep 2007 22:08:15 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.185]) by mx1.freebsd.org (Postfix) with ESMTP id 5CD1C13C457 for ; Sun, 23 Sep 2007 22:08:14 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: by mu-out-0910.google.com with SMTP id w9so1779719mue for ; Sun, 23 Sep 2007 15:08:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=AYKsqaYVETQTZdF8oU9e0vgMu0eZj1BLqVD9+vZUX0U=; b=Yo2MTbCYgQlpgss0RITRpJDs0rHyH9DlyYzphdneyv7SCNbA7nIx96Dq/IrG+DOSenKHcc+9CiUYLBhqW7lsEvxkFsMFCzff/nCrc/zmZ6bDoP5xR4SlL2eiC8FOUJxVpG3XME7Qzk9f+xxro5xRgennenSqe7s41ITInFVGHmw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=VOyEK9gAEEOTiuGePjEtEBp4fPt21XRVWknVMyhCVZIGQD7gxuMr5gztbAeCX+u08Vxgiz2TyqMHnyX7NNiPvPXotl2kXjxKhN9N3Jv/xebPr0ynjiGyplhs/ShtHOESsbjGd6rXHmkYvutKhVQV7z/Dm6MHWD6oCgQVU1Mxcpk= Received: by 10.86.76.16 with SMTP id y16mr4187833fga.1190585293637; Sun, 23 Sep 2007 15:08:13 -0700 (PDT) Received: by 10.86.2.1 with HTTP; Sun, 23 Sep 2007 15:08:13 -0700 (PDT) Message-ID: <499c70c0709231508o1d57bd36gaf654e33c4a2ad06@mail.gmail.com> Date: Mon, 24 Sep 2007 01:08:13 +0300 From: "Abdullah Ibn Hamad Al-Marri" To: "Jeff Roberson" In-Reply-To: <20070923110135.C547@10.0.0.1> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46F609DC.3070809@melbpc.org.au> <20070923110135.C547@10.0.0.1> Cc: freebsd-current@freebsd.org Subject: Re: [panic] sched_priority: invalid interactive priority 124 score -4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 22:08:16 -0000 On 9/23/07, Jeff Roberson wrote: > On Sun, 23 Sep 2007, Peter Kostouros wrote: > > > Hi > > > > I received the abovementioned panic on a system csup'ed and build a few hours > > ago and have attached a debug session I hope will help. > > Peter, > > Thanks for your debugging efforts. The problem was with my most recent > commit. You can back out to 1.207 or try this patch, which csjp reports > fixes the problem: > > http://people.freebsd.org/~jeff/ulebugs.diff > > Thanks, > Jeff Jeff, fetch http://people.freebsd.org/~jeff/ulebugs.diff && patch < ulebugs.diff ulebugs.diff 100% of 914 B 8767 kBps Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |Index: sched_ule.c |=================================================================== |RCS file: /home/ncvs/src/sys/kern/sched_ule.c,v |retrieving revision 1.208 |diff -u -r1.208 sched_ule.c |--- sched_ule.c 22 Sep 2007 02:20:14 -0000 1.208 |+++ sched_ule.c 23 Sep 2007 17:33:02 -0000 -------------------------- File to patch: No file found--skip this patch? [n] y Skipping patch... Hunk #1 ignored at 1410. Hunk #2 ignored at 1865. 2 out of 2 hunks ignored--saving rejects to sched_ule.c.rej any hints? -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 22:34:37 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64A0216A41A for ; Sun, 23 Sep 2007 22:34:37 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 18BC013C448 for ; Sun, 23 Sep 2007 22:34:37 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 6701A2EBF8; Sun, 23 Sep 2007 18:34:36 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Sun, 23 Sep 2007 18:34:36 -0400 X-Sasl-enc: 5VO3vSQBJCSkMhjHZA8raPMDMcXzHpoOze5mTGATbaFJ 1190586876 Received: from [192.168.1.235] (64-142-85-108.dsl.dynamic.sonic.net [64.142.85.108]) by mail.messagingengine.com (Postfix) with ESMTP id A9B00207D9; Sun, 23 Sep 2007 18:34:35 -0400 (EDT) Message-ID: <46F6EA42.1070401@freebsd.org> Date: Sun, 23 Sep 2007 15:35:46 -0700 From: Darren Reed User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Larry Rosenman References: <20070921102946.T11189@borg> <46F415BF.9010500@FreeBSD.org> <20070921140550.D96923@thebighonker.lerctr.org> <46F41CFF.6080108@FreeBSD.org> <46F58799.1030702@freebsd.org> <20070923161722.B41582@thebighonker.lerctr.org> In-Reply-To: <20070923161722.B41582@thebighonker.lerctr.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Claus Guttesen Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 22:34:37 -0000 Larry Rosenman wrote: > On Sun, 23 Sep 2007, Claus Guttesen wrote: > >>> So I just received this courtesy of ZFS: >>> panic: kmem_malloc(131072): kmem_map too small: 343027712 total >>> allocated >>> cpuid = 0 >>> KDB: enter: panic >>> >>> This was with these settings in loader.conf: >>> vm.kmem_size=419430400 >>> vm.kmem_size_max=419430400 >>> vfs.zfs.arc_max=409715200 >> >> How much ram do you have? Is this amd64 or i386? > > In my case, 4Gig ram, amd64, and I've seen the panic even with > 750M vm.kmem_size. > > Do we have guidelines on what vm.kmem_size(|_max) should be set to? My advice would be to tune the ZFS ARC to be smaller than kmem_size. The above represents a mistake in sizing the ARC. When using ZFS, I'd tune vm.kmem_size to be as much as 80% of RAM, unless you're running *large* applications in user space. Darren From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 22:38:22 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C26CC16A419; Sun, 23 Sep 2007 22:38:22 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 6173113C455; Sun, 23 Sep 2007 22:38:22 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 604882F004; Sun, 23 Sep 2007 18:38:02 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Sun, 23 Sep 2007 18:38:02 -0400 X-Sasl-enc: cDFZ9oVuyYCmZjdT1cSqICDMJ8Rdc03EpCRDvBbpj+h1 1190587082 Received: from [192.168.1.235] (64-142-85-108.dsl.dynamic.sonic.net [64.142.85.108]) by mail.messagingengine.com (Postfix) with ESMTP id 68F0420960; Sun, 23 Sep 2007 18:38:01 -0400 (EDT) Message-ID: <46F6EB10.8060505@freebsd.org> Date: Sun, 23 Sep 2007 15:39:12 -0700 From: Darren Reed User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Louis Mamakos References: <2a41acea0709221656n4aa62776y488c7f2da262c9f6@mail.gmail.com> <46F614F2.4050402@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Kip Macy , FreeBSD Current , Jack Vogel , "freebsd-net@freebsd.org" Subject: Re: TX Multiqueue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 22:38:22 -0000 Louis Mamakos wrote: > We've seen problems on other OS's where the locking in the device driver > around the process of queuing packets to the device was a performance > issue > when trying to send relatively small packets. As a workaround, we > ended up > doing a multi-link/bonding thing over multiple interfaces to get the > throughput. This was on an SMP system and the application was such that > there were multiple execution threads running in parallel. > > Having multiple queues, even for a single class of traffic may enable > enough > additional concurrency in the driver to increase throughput. It's up to > driver to use some algorithm to spread the load over the queues to ensure > that specific "flows" stay in order, same as if you we doing > ether-channel > bonding. Maybe I'm not interested in the driver having its own algorithm. Maybe I want to reserve a tx/rx queue pair for ssh. Maybe I want to dedicate a tx/rx queue pair for my web server. etc. Darren > Of course, if the transmit path through the network stack isn't enabling > concurrency, a bottleneck there won't be an issue. > > Louis Mamakos > > Just something else to consider.. > > On Sep 23, 2007, at 3:25 AM, Darren Reed wrote: > >> Kip Macy wrote: >>> My ethng branch supports multiple rx and tx queues. >>> >>> -Kip >>> >> >> What are your plans for how we use/manage/interact with the mutiple >> rx/tx queues? >> >> Darren >> >> >>> On 9/22/07, Jack Vogel wrote: >>> > Our newest E1000 nic, the 82575, and the Oplin 10G hardware are >>> capable of >>> > multiple queues both on the receive and the send side. On the >>> receive end for >>> > the Oplin driver the queues actually help distribute interrupts >>> and improve >>> > performance without any special support in the stack. >>> > >>> > I have been asked about multiple queues on the TX side, embedded >>> appliance >>> > type system builders for instance are interested I suppose for >>> > priority queueing. >>> > Is anyone working on this right now, and if not does this sound >>> like something >>> > anyone is interested in doing? >>> > >>> > I would like to see MQ on both TX and RX that drivers could use if >>> able. >>> > >>> > Jack >>> > _______________________________________________ >>> > freebsd-net@freebsd.org mailing list >>> > http://lists.freebsd.org/mailman/listinfo/freebsd-net >>> > To unsubscribe, send any mail to >>> "freebsd-net-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 Sun Sep 23 22:47:15 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67C1C16A420 for ; Sun, 23 Sep 2007 22:47:15 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by mx1.freebsd.org (Postfix) with ESMTP id 152E613C46A for ; Sun, 23 Sep 2007 22:47:15 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so1836727waf for ; Sun, 23 Sep 2007 15:47:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=+dZ9SXbne9IFaDmTF24WejRwA1UKRjI9SeSN72hsHjg=; b=paNy7MIOcWIw1hjjbwu6aNaOSFrRlB13h3urFrDG0JF8mq/Uo3L1MaEGBBFOTrBUDrxYMb9xtCBYM2QXu7PbfLmq6cMcAJIs2Kcwc7HaxqwcpkP3U63QOTla+d7MBDuQwhRWufwGseqgOPKxLU9ojpHYSKbIIIPcx/TPGd3KNRU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=d0IazMX2pIvuWuP1DjgA+MpgpP4kIgNDIwDtvqQVSnvDOG9LKac64MTChs604vJFCjL7Err1ZWajZKQ2Ygs+011lVC8/72EX5luCHfpatR7NLh1ezLi272GRS+Egc6qv+v+5gwVcsgwV0XyswBeh46uN6zi6Ej3Ty3cISW0IL2M= Received: by 10.115.55.1 with SMTP id h1mr5616231wak.1190587633970; Sun, 23 Sep 2007 15:47:13 -0700 (PDT) Received: by 10.114.13.15 with HTTP; Sun, 23 Sep 2007 15:47:13 -0700 (PDT) Message-ID: Date: Sun, 23 Sep 2007 15:47:13 -0700 From: "Kip Macy" To: "Darren Reed" In-Reply-To: <46F614F2.4050402@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0709221656n4aa62776y488c7f2da262c9f6@mail.gmail.com> <46F614F2.4050402@freebsd.org> Cc: "freebsd-net@freebsd.org" , FreeBSD Current , Jack Vogel Subject: Re: TX Multiqueue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 22:47:15 -0000 On 9/23/07, Darren Reed wrote: > Kip Macy wrote: > > My ethng branch supports multiple rx and tx queues. > > > > -Kip > > > > What are your plans for how we use/manage/interact with the mutiple > rx/tx queues? The rx hardware queue is determined by the hardware. Different hardware allows for different policies. I just use the stock rss_hash of a crc32 of the 4-tuple in cxgb. I've added a field to the pkthdr which cxgb uses the least significant bits of to determine which outbound queue to use. Its up to the upper layers to determine how to set those bits. One of the changes that is required to take advantaged of this is moving the queues into the driver. I've added a new if_start function to ifnet to take advantage of this. I also have a normal if_start function for backward compatibility. -Kip From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 23:03:04 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CADCD16A417 for ; Sun, 23 Sep 2007 23:03:04 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from webaccess-cl.virtdom.com (webaccess-cl.virtdom.com [216.240.101.25]) by mx1.freebsd.org (Postfix) with ESMTP id 579AC13C461 for ; Sun, 23 Sep 2007 23:03:04 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from [192.168.1.103] (c-67-160-44-208.hsd1.wa.comcast.net [67.160.44.208]) (authenticated bits=0) by webaccess-cl.virtdom.com (8.13.6/8.13.6) with ESMTP id l8NN30KC013002 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Sun, 23 Sep 2007 19:03:01 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Sun, 23 Sep 2007 16:05:44 -0700 (PDT) From: Jeff Roberson X-X-Sender: jroberson@10.0.0.1 To: Abdullah Ibn Hamad Al-Marri In-Reply-To: <499c70c0709231508o1d57bd36gaf654e33c4a2ad06@mail.gmail.com> Message-ID: <20070923160448.I547@10.0.0.1> References: <46F609DC.3070809@melbpc.org.au> <20070923110135.C547@10.0.0.1> <499c70c0709231508o1d57bd36gaf654e33c4a2ad06@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: [panic] sched_priority: invalid interactive priority 124 score -4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 23:03:04 -0000 On Mon, 24 Sep 2007, Abdullah Ibn Hamad Al-Marri wrote: > On 9/23/07, Jeff Roberson wrote: >> On Sun, 23 Sep 2007, Peter Kostouros wrote: >> >>> Hi >>> >>> I received the abovementioned panic on a system csup'ed and build a few hours >>> ago and have attached a debug session I hope will help. >> >> Peter, >> >> Thanks for your debugging efforts. The problem was with my most recent >> commit. You can back out to 1.207 or try this patch, which csjp reports >> fixes the problem: >> >> http://people.freebsd.org/~jeff/ulebugs.diff >> >> Thanks, >> Jeff > > Jeff, > > fetch http://people.freebsd.org/~jeff/ulebugs.diff && patch < ulebugs.diff > ulebugs.diff 100% of 914 B 8767 kBps > Hmm... Looks like a unified diff to me... > The text leading up to this was: > -------------------------- > |Index: sched_ule.c > |=================================================================== > |RCS file: /home/ncvs/src/sys/kern/sched_ule.c,v > |retrieving revision 1.208 > |diff -u -r1.208 sched_ule.c > |--- sched_ule.c 22 Sep 2007 02:20:14 -0000 1.208 > |+++ sched_ule.c 23 Sep 2007 17:33:02 -0000 > -------------------------- > File to patch: > No file found--skip this patch? [n] y > Skipping patch... > Hunk #1 ignored at 1410. > Hunk #2 ignored at 1865. > 2 out of 2 hunks ignored--saving rejects to sched_ule.c.rej If you're not running 1.208 the patch won't apply. On the positive side, that also means you don't have this bug. Thanks, Jeff > > any hints? > -- > Regards, > > -Abdullah Ibn Hamad Al-Marri > Arab Portal > http://www.WeArab.Net/ > _______________________________________________ > 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 Sep 23 23:15:34 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9753B16A417 for ; Sun, 23 Sep 2007 23:15:34 +0000 (UTC) (envelope-from cristi.magherusan@net.utcluj.ro) Received: from bavaria.utcluj.ro (unknown [IPv6:2001:b30:5000:2:20e:cff:fe4b:ca01]) by mx1.freebsd.org (Postfix) with ESMTP id E1FF913C459 for ; Sun, 23 Sep 2007 23:15:33 +0000 (UTC) (envelope-from cristi.magherusan@net.utcluj.ro) Received: from localhost (localhost [127.0.0.1]) by bavaria.utcluj.ro (Postfix) with ESMTP id B061150879 for ; Mon, 24 Sep 2007 02:15:32 +0300 (EEST) X-Virus-Scanned: by the daemon playing with your mail on local.mail.utcluj.ro Received: from bavaria.utcluj.ro ([127.0.0.1]) by localhost (bavaria.utcluj.ro [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JkSd2Bdxq59G for ; Mon, 24 Sep 2007 02:15:25 +0300 (EEST) Received: from [192.168.1.100] (c7.campus.utcluj.ro [193.226.6.226]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by bavaria.utcluj.ro (Postfix) with ESMTP id BA36350888 for ; Mon, 24 Sep 2007 02:15:25 +0300 (EEST) From: Cristi Magherusan To: freebsd-current@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-tMa5bWAi7opIc7J5ndwq" Organization: Universitatea Tehnica din Cluj-Napoca, Centrul de Comunicatii "Pusztai Kalman" Date: Mon, 24 Sep 2007 02:58:59 +0300 Message-Id: <1190591939.14488.25.camel@hyperion> Mime-Version: 1.0 X-Mailer: Evolution 2.10.3 Subject: bge driver causes freeze X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cristi.magherusan@net.utcluj.ro List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 23:15:34 -0000 --=-tMa5bWAi7opIc7J5ndwq Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hello, I tried the latest snapshot on my HP 6710b laptop, and it behaves just like the one from august, as reported in this message: http://lists.freebsd.org/pipermail/freebsd-current/2007-September/076856.ht= ml ACPI reports an error, something about out of range temperature value, then locks the system waiting for some event. By mistake I've found a workaround by unplugging then plugging back the power cable. In 6.2 it reported the same error, but didn't lock. The real problem is the bge driver that seems to have a critical regression from 6.2 and completely freezes the system at boot. Did anyone experienced similar problems of with current bge driver on another hardware, or this bug happens only with this laptop model?=20 Best Regards, cristi --=20 Cristi Magherusan, Universitatea Tehnica din Cluj - Napoca Centrul de Comunicatii "Pusztai Kalman" Tel. 0264/401247 http://cc.utcluj.ro --=-tMa5bWAi7opIc7J5ndwq Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQBG9v3DfwrBISYVZFURAj+XAJ9Pju67W0kZq50LPhLPXpmqiKTlLACfQzcz VQ4joxEr4zlryUyPptUReLg= =NRuE -----END PGP SIGNATURE----- --=-tMa5bWAi7opIc7J5ndwq-- From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 23:33:30 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5733316A418 for ; Sun, 23 Sep 2007 23:33:30 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 5116513C45A; Sun, 23 Sep 2007 23:33:29 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F6F7C9.6030309@FreeBSD.org> Date: Mon, 24 Sep 2007 01:33:29 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Jeff Roberson References: <46F609DC.3070809@melbpc.org.au> <20070923110135.C547@10.0.0.1> <499c70c0709231508o1d57bd36gaf654e33c4a2ad06@mail.gmail.com> <20070923160448.I547@10.0.0.1> In-Reply-To: <20070923160448.I547@10.0.0.1> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Abdullah Ibn Hamad Al-Marri Subject: Re: [panic] sched_priority: invalid interactive priority 124 score -4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 23:33:30 -0000 Jeff Roberson wrote: > On Mon, 24 Sep 2007, Abdullah Ibn Hamad Al-Marri wrote: > >> On 9/23/07, Jeff Roberson wrote: >>> On Sun, 23 Sep 2007, Peter Kostouros wrote: >>> >>>> Hi >>>> >>>> I received the abovementioned panic on a system csup'ed and build a >>>> few hours >>>> ago and have attached a debug session I hope will help. >>> >>> Peter, >>> >>> Thanks for your debugging efforts. The problem was with my most recent >>> commit. You can back out to 1.207 or try this patch, which csjp reports >>> fixes the problem: >>> >>> http://people.freebsd.org/~jeff/ulebugs.diff >>> >>> Thanks, >>> Jeff >> >> Jeff, >> >> fetch http://people.freebsd.org/~jeff/ulebugs.diff && patch < >> ulebugs.diff >> ulebugs.diff 100% of 914 B 8767 kBps >> Hmm... Looks like a unified diff to me... >> The text leading up to this was: >> -------------------------- >> |Index: sched_ule.c >> |=================================================================== >> |RCS file: /home/ncvs/src/sys/kern/sched_ule.c,v >> |retrieving revision 1.208 >> |diff -u -r1.208 sched_ule.c >> |--- sched_ule.c 22 Sep 2007 02:20:14 -0000 1.208 >> |+++ sched_ule.c 23 Sep 2007 17:33:02 -0000 >> -------------------------- >> File to patch: >> No file found--skip this patch? [n] y >> Skipping patch... >> Hunk #1 ignored at 1410. >> Hunk #2 ignored at 1865. >> 2 out of 2 hunks ignored--saving rejects to sched_ule.c.rej > > If you're not running 1.208 the patch won't apply. On the positive > side, that also means you don't have this bug. Looks like he's running patch from the wrong directory, i.e. not sys/kern/ where sched_ule.c is. Kris From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 00:10:11 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6927F16A420 for ; Mon, 24 Sep 2007 00:10:11 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.189]) by mx1.freebsd.org (Postfix) with ESMTP id AFB3F13C45D for ; Mon, 24 Sep 2007 00:10:10 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: by mu-out-0910.google.com with SMTP id w9so1815636mue for ; Sun, 23 Sep 2007 17:10:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=XoUjxFo9zJTzUZtcGyzaMtA8CYYjJVFhJtbmJtlvCNw=; b=HGR+TAA+Cgq7abVVboxhC3X4aE+DzZbMQIPnLzo+mDME91wjJM08FOeOzY0VVW+5RQN4U6dAjlcutMc3r99SnmDT0PeQ1Uq5hl/I1TzjHhOuTeV+nACSoLyJsHpQbqYwsrISKu3paJwHcZ79joPSs/eT0wgEwrmfJpwDOBBFW8Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Hm1neQILy/NdjFKZbx3bIr/P34LqYRO9SMDo4cS2lQC1XT2Xz8vvNWn/52kqsJCLn6LlQE1TC8eqtLkezoHfBoH9lhV/guy2fB4aELvm7BmiIy+ZMVhsntQ7V/UBf2nNdm3lClY+MlxQvaDHY/5ih3nzVUTJzQHqAx73D8qM1zc= Received: by 10.86.28.5 with SMTP id b5mr4276467fgb.1190592608945; Sun, 23 Sep 2007 17:10:08 -0700 (PDT) Received: by 10.86.2.1 with HTTP; Sun, 23 Sep 2007 17:10:05 -0700 (PDT) Message-ID: <499c70c0709231710r228afb76qf740a01e81ef106a@mail.gmail.com> Date: Mon, 24 Sep 2007 03:10:05 +0300 From: "Abdullah Ibn Hamad Al-Marri" To: "Kris Kennaway" In-Reply-To: <46F6F7C9.6030309@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46F609DC.3070809@melbpc.org.au> <20070923110135.C547@10.0.0.1> <499c70c0709231508o1d57bd36gaf654e33c4a2ad06@mail.gmail.com> <20070923160448.I547@10.0.0.1> <46F6F7C9.6030309@FreeBSD.org> Cc: Jeff Roberson , freebsd-current@freebsd.org Subject: Re: [panic] sched_priority: invalid interactive priority 124 score -4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 00:10:11 -0000 On 9/24/07, Kris Kennaway wrote: > Jeff Roberson wrote: > > On Mon, 24 Sep 2007, Abdullah Ibn Hamad Al-Marri wrote: > > > >> On 9/23/07, Jeff Roberson wrote: > >>> On Sun, 23 Sep 2007, Peter Kostouros wrote: > >>> > >>>> Hi > >>>> > >>>> I received the abovementioned panic on a system csup'ed and build a > >>>> few hours > >>>> ago and have attached a debug session I hope will help. > >>> > >>> Peter, > >>> > >>> Thanks for your debugging efforts. The problem was with my most recent > >>> commit. You can back out to 1.207 or try this patch, which csjp reports > >>> fixes the problem: > >>> > >>> http://people.freebsd.org/~jeff/ulebugs.diff > >>> > >>> Thanks, > >>> Jeff > >> > >> Jeff, > >> > >> fetch http://people.freebsd.org/~jeff/ulebugs.diff && patch < > >> ulebugs.diff > >> ulebugs.diff 100% of 914 B 8767 kBps > >> Hmm... Looks like a unified diff to me... > >> The text leading up to this was: > >> -------------------------- > >> |Index: sched_ule.c > >> |=================================================================== > >> |RCS file: /home/ncvs/src/sys/kern/sched_ule.c,v > >> |retrieving revision 1.208 > >> |diff -u -r1.208 sched_ule.c > >> |--- sched_ule.c 22 Sep 2007 02:20:14 -0000 1.208 > >> |+++ sched_ule.c 23 Sep 2007 17:33:02 -0000 > >> -------------------------- > >> File to patch: > >> No file found--skip this patch? [n] y > >> Skipping patch... > >> Hunk #1 ignored at 1410. > >> Hunk #2 ignored at 1865. > >> 2 out of 2 hunks ignored--saving rejects to sched_ule.c.rej > > > > If you're not running 1.208 the patch won't apply. On the positive > > side, that also means you don't have this bug. > > Looks like he's running patch from the wrong directory, i.e. not > sys/kern/ where sched_ule.c is. > > Kris Yup, I corrected it, sorry for the noise. cd /usr/src/sys/kern/ && fetch http://people.freebsd.org/~jeff/ulebugs.diff && patch < ulebugs.diff ulebugs.diff 100% of 2016 B 13 MBps Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |Index: sched_ule.c |=================================================================== |RCS file: /home/ncvs/src/sys/kern/sched_ule.c,v |retrieving revision 1.208 |diff -u -r1.208 sched_ule.c |--- sched_ule.c 22 Sep 2007 02:20:14 -0000 1.208 |+++ sched_ule.c 23 Sep 2007 23:45:36 -0000 -------------------------- Patching file sched_ule.c using Plan A... Hunk #1 failed at 1410. Hunk #2 succeeded at 1858 (offset -7 lines). Hunk #3 succeeded at 1867 (offset -7 lines). Hunk #4 succeeded at 2570 (offset 1 line). Hunk #5 succeeded at 2575 (offset -7 lines). Hunk #6 succeeded at 2612 (offset 1 line). 1 out of 6 hunks failed--saving rejects to sched_ule.c.rej done -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 01:07:12 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42E7D16A41A; Mon, 24 Sep 2007 01:07:12 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from webaccess-cl.virtdom.com (webaccess-cl.virtdom.com [216.240.101.25]) by mx1.freebsd.org (Postfix) with ESMTP id EB32013C448; Mon, 24 Sep 2007 01:07:11 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from [192.168.1.103] (c-67-160-44-208.hsd1.wa.comcast.net [67.160.44.208]) (authenticated bits=0) by webaccess-cl.virtdom.com (8.13.6/8.13.6) with ESMTP id l8O17AdE035033 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Sun, 23 Sep 2007 21:07:11 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Sun, 23 Sep 2007 18:09:53 -0700 (PDT) From: Jeff Roberson X-X-Sender: jroberson@10.0.0.1 To: Abdullah Ibn Hamad Al-Marri In-Reply-To: <499c70c0709231710r228afb76qf740a01e81ef106a@mail.gmail.com> Message-ID: <20070923180909.U547@10.0.0.1> References: <46F609DC.3070809@melbpc.org.au> <20070923110135.C547@10.0.0.1> <499c70c0709231508o1d57bd36gaf654e33c4a2ad06@mail.gmail.com> <20070923160448.I547@10.0.0.1> <46F6F7C9.6030309@FreeBSD.org> <499c70c0709231710r228afb76qf740a01e81ef106a@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: [panic] sched_priority: invalid interactive priority 124 score -4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 01:07:12 -0000 On Mon, 24 Sep 2007, Abdullah Ibn Hamad Al-Marri wrote: > On 9/24/07, Kris Kennaway wrote: >> Jeff Roberson wrote: >>> On Mon, 24 Sep 2007, Abdullah Ibn Hamad Al-Marri wrote: >>> >>>> On 9/23/07, Jeff Roberson wrote: >>>>> On Sun, 23 Sep 2007, Peter Kostouros wrote: >>>>> >>>>>> Hi >>>>>> >>>>>> I received the abovementioned panic on a system csup'ed and build a >>>>>> few hours >>>>>> ago and have attached a debug session I hope will help. >>>>> >>>>> Peter, >>>>> >>>>> Thanks for your debugging efforts. The problem was with my most recent >>>>> commit. You can back out to 1.207 or try this patch, which csjp reports >>>>> fixes the problem: >>>>> >>>>> http://people.freebsd.org/~jeff/ulebugs.diff >>>>> >>>>> Thanks, >>>>> Jeff >>>> >>>> Jeff, >>>> >>>> fetch http://people.freebsd.org/~jeff/ulebugs.diff && patch < >>>> ulebugs.diff >>>> ulebugs.diff 100% of 914 B 8767 kBps >>>> Hmm... Looks like a unified diff to me... >>>> The text leading up to this was: >>>> -------------------------- >>>> |Index: sched_ule.c >>>> |=================================================================== >>>> |RCS file: /home/ncvs/src/sys/kern/sched_ule.c,v >>>> |retrieving revision 1.208 >>>> |diff -u -r1.208 sched_ule.c >>>> |--- sched_ule.c 22 Sep 2007 02:20:14 -0000 1.208 >>>> |+++ sched_ule.c 23 Sep 2007 17:33:02 -0000 >>>> -------------------------- >>>> File to patch: >>>> No file found--skip this patch? [n] y >>>> Skipping patch... >>>> Hunk #1 ignored at 1410. >>>> Hunk #2 ignored at 1865. >>>> 2 out of 2 hunks ignored--saving rejects to sched_ule.c.rej >>> >>> If you're not running 1.208 the patch won't apply. On the positive >>> side, that also means you don't have this bug. >> >> Looks like he's running patch from the wrong directory, i.e. not >> sys/kern/ where sched_ule.c is. >> >> Kris > > Yup, I corrected it, sorry for the noise. > > cd /usr/src/sys/kern/ && fetch > http://people.freebsd.org/~jeff/ulebugs.diff && patch < ulebugs.diff > ulebugs.diff 100% of 2016 B 13 MBps I just committed the nice related portion of this fix. Unless you're Kris you probably don't need to worry about the other bug this fixes. Thanks, Jeff > Hmm... Looks like a unified diff to me... > The text leading up to this was: > -------------------------- > |Index: sched_ule.c > |=================================================================== > |RCS file: /home/ncvs/src/sys/kern/sched_ule.c,v > |retrieving revision 1.208 > |diff -u -r1.208 sched_ule.c > |--- sched_ule.c 22 Sep 2007 02:20:14 -0000 1.208 > |+++ sched_ule.c 23 Sep 2007 23:45:36 -0000 > -------------------------- > Patching file sched_ule.c using Plan A... > Hunk #1 failed at 1410. > Hunk #2 succeeded at 1858 (offset -7 lines). > Hunk #3 succeeded at 1867 (offset -7 lines). > Hunk #4 succeeded at 2570 (offset 1 line). > Hunk #5 succeeded at 2575 (offset -7 lines). > Hunk #6 succeeded at 2612 (offset 1 line). > 1 out of 6 hunks failed--saving rejects to sched_ule.c.rej > done > > > -- > Regards, > > -Abdullah Ibn Hamad Al-Marri > Arab Portal > http://www.WeArab.Net/ > _______________________________________________ > 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 Sep 24 03:38:57 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6EF416A418 for ; Mon, 24 Sep 2007 03:38:57 +0000 (UTC) (envelope-from ulrich@pukruppa.net) Received: from pukruppa.net (pukruppa.net [213.146.114.24]) by mx1.freebsd.org (Postfix) with ESMTP id 986F813C465 for ; Mon, 24 Sep 2007 03:38:56 +0000 (UTC) (envelope-from ulrich@pukruppa.net) Received: from pukruppa.net (localhost [127.0.0.1]) by pukruppa.net (8.14.1/8.14.1) with ESMTP id l8O3Sm5d010018 for ; Mon, 24 Sep 2007 05:28:48 +0200 (CEST) (envelope-from ulrich@pukruppa.net) Received: from localhost (ulrich@localhost) by pukruppa.net (8.14.1/8.14.1/Submit) with ESMTP id l8O3SmhW010015 for ; Mon, 24 Sep 2007 05:28:48 +0200 (CEST) (envelope-from ulrich@pukruppa.net) Date: Mon, 24 Sep 2007 05:28:48 +0200 (CEST) From: "P.U.Kruppa" X-X-Sender: ulrich@small To: freebsd-current@freebsd.org Message-ID: <20070924051118.H9923@small> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 03:38:57 -0000 Hello, I use a HP Deskjet 990 Cxi via parallel port with cups and hpijs driver on FreeBSD pukruppa.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Sep 21 16:52:59 CEST 2007 amd64 When I try to print a little bit more complex documents (OpenOffice, pdf) my System will crash. On my root terminal there will be a long list of lpt0: [ITHREAD] lpt0: [GIANT-LOCKED] lpt0: [ITHREAD] [...] lines, then some dumping activity and a reboot. I upgraded to 7.0 last week, so all I can say is: everything was fine with 6.2 . Please tell me if you need more information. Peter Ulrich Kruppa Wuppertal Germany From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 07:51:22 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD76916A417 for ; Mon, 24 Sep 2007 07:51:22 +0000 (UTC) (envelope-from ulrich@pukruppa.net) Received: from pukruppa.net (pukruppa.net [213.146.114.24]) by mx1.freebsd.org (Postfix) with ESMTP id 2937413C465 for ; Mon, 24 Sep 2007 07:51:21 +0000 (UTC) (envelope-from ulrich@pukruppa.net) Received: from pukruppa.net (localhost [127.0.0.1]) by pukruppa.net (8.14.1/8.14.1) with ESMTP id l8O7pJAY010258 for ; Mon, 24 Sep 2007 09:51:20 +0200 (CEST) (envelope-from ulrich@pukruppa.net) Received: from localhost (ulrich@localhost) by pukruppa.net (8.14.1/8.14.1/Submit) with ESMTP id l8O7pJVr010255 for ; Mon, 24 Sep 2007 09:51:19 +0200 (CEST) (envelope-from ulrich@pukruppa.net) Date: Mon, 24 Sep 2007 09:51:19 +0200 (CEST) From: "P.U.Kruppa" X-X-Sender: ulrich@small To: freebsd-current@freebsd.org In-Reply-To: <20070924051118.H9923@small> Message-ID: <20070924094848.J10251@small> References: <20070924051118.H9923@small> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 07:51:22 -0000 On Mon, 24 Sep 2007, P.U.Kruppa wrote: > Hello, > > I use a HP Deskjet 990 Cxi via parallel port with cups and hpijs driver on > > FreeBSD pukruppa.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Sep 21 16:52:59 > CEST 2007 amd64 > > When I try to print a little bit more complex documents (OpenOffice, pdf) my > System will crash. > > On my root terminal there will be a long list of > lpt0: [ITHREAD] > lpt0: [GIANT-LOCKED] > lpt0: [ITHREAD] > [...] > lines, then some dumping activity and a reboot. > > I upgraded to 7.0 last week, so all I can say is: everything was fine with > 6.2 . > > Please tell me if you need more information. By the way: in the meantime I have found a workaround: I can run my printer via usb port (that didn't work when I tried it 3 or 4 years ago). Regards, Uli. Peter Ulrich Kruppa Wuppertal Germany From owner-freebsd-current@FreeBSD.ORG Fri Sep 21 14:59:17 2007 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D223116A418 for ; Fri, 21 Sep 2007 14:59:17 +0000 (UTC) (envelope-from hopet@ics.muni.cz) Received: from minas.ics.muni.cz (minas.ics.muni.cz [147.251.4.40]) by mx1.freebsd.org (Postfix) with ESMTP id 4579A13C4AA for ; Fri, 21 Sep 2007 14:59:17 +0000 (UTC) (envelope-from hopet@ics.muni.cz) Received: from KLOBOUCEK (holub.ics.muni.cz [147.251.23.83]) (authenticated user=hopet@ICS.MUNI.CZ bits=0) by minas.ics.muni.cz (8.13.8/8.13.8/SuSE Linux 0.8) with ESMTP id l8LExF6e005252 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 21 Sep 2007 16:59:15 +0200 From: "Petr Holub" To: "Jeremy Chadwick" Date: Fri, 21 Sep 2007 16:59:16 +0200 Message-ID: <004901c7fc5f$fb269190$5317fb93@KLOBOUCEK> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 In-Reply-To: <20070921133316.GA63294@eos.sc1.parodius.com> Importance: Normal X-Muni-Spam-TestIP: 147.251.23.83 X-Muni-Envelope-From: hopet@ics.muni.cz X-Muni-Envelope-To: current@FreeBSD.org X-Muni-Virus-Test: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (minas.ics.muni.cz [147.251.4.35]); Fri, 21 Sep 2007 16:59:15 +0200 (CEST) X-Mailman-Approved-At: Mon, 24 Sep 2007 08:18:03 +0000 Cc: current@FreeBSD.org Subject: RE: TCP socket problem on Sept. -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Sep 2007 14:59:17 -0000 > > It occurred from several different addresses and results in being > > unable event to ping that IP until reboot. > > This is "normal" for the current time being, as the output in question > is being used to help track down a TCP-related bug in -CURRENT: Thank you! Actually, the more painful problem is that it made some IP addresses unreachable afterwards: I was unable to ping them, to make any TCP connection, etc. Though I was unable to ping (almost all) other IPs and I was also able to ping/connect those ``stuck'' IPs from another host siting on the same network. So it looks like the problem is actually some per-IP bug... Any reports of this behavior reported before before I start looking into this deeper? Just for reference, I'm using 200709 snapshot of 7.0-CURRENT for amd64, running on Core2 Duo with a custom kernes with WITNESS turned off. Thanks, Petr From owner-freebsd-current@FreeBSD.ORG Fri Sep 21 15:08:28 2007 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69F4716A469 for ; Fri, 21 Sep 2007 15:08:28 +0000 (UTC) (envelope-from hopet@ics.muni.cz) Received: from minas.ics.muni.cz (minas.ics.muni.cz [147.251.4.40]) by mx1.freebsd.org (Postfix) with ESMTP id D104813C4A7 for ; Fri, 21 Sep 2007 15:08:27 +0000 (UTC) (envelope-from hopet@ics.muni.cz) Received: from KLOBOUCEK (holub.ics.muni.cz [147.251.23.83]) (authenticated user=hopet@ICS.MUNI.CZ bits=0) by minas.ics.muni.cz (8.13.8/8.13.8/SuSE Linux 0.8) with ESMTP id l8LF8PQe032013 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 21 Sep 2007 17:08:26 +0200 From: "Petr Holub" To: "Jeremy Chadwick" Date: Fri, 21 Sep 2007 17:08:27 +0200 Message-ID: <004a01c7fc61$43807db0$5317fb93@KLOBOUCEK> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 In-Reply-To: Importance: Normal X-Muni-Spam-TestIP: 147.251.23.83 X-Muni-Envelope-From: hopet@ics.muni.cz X-Muni-Envelope-To: current@FreeBSD.org X-Muni-Virus-Test: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (minas.ics.muni.cz [147.251.4.35]); Fri, 21 Sep 2007 17:08:26 +0200 (CEST) X-Mailman-Approved-At: Mon, 24 Sep 2007 08:18:03 +0000 Cc: current@FreeBSD.org Subject: RE: TCP socket problem on Sept. -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Sep 2007 15:08:28 -0000 > looks like the problem is actually some per-IP bug... Any reports > of this behavior reported before before I start looking into this > deeper? Actually, it might be some nasty behavior of xorg.freedesktop.org (131.252.210.176) - according to tcpdump, echo requests are being sent, but nothing is received in return. While the same ping works from a machine sitting on the same network next to this one. I'm not sure what's happening: if it might be some bug that tcpdump can't reveal or 131.252.210.176 is playing games... Petr From owner-freebsd-current@FreeBSD.ORG Fri Sep 21 18:08:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCEB416A41A for ; Fri, 21 Sep 2007 18:08:18 +0000 (UTC) (envelope-from vigneron@math.polytechnique.fr) Received: from mx-b.polytechnique.fr (mx-b.polytechnique.fr [129.104.30.15]) by mx1.freebsd.org (Postfix) with ESMTP id 38CE613C4A3 for ; Fri, 21 Sep 2007 18:08:18 +0000 (UTC) (envelope-from vigneron@math.polytechnique.fr) Received: from localdomain.polytechnique.fr (hermes.math.polytechnique.fr [129.104.3.6]) by mx-b.polytechnique.fr (tbp 5.3.2/2.0.7) with ESMTP id l8LH8MFv025755 for ; Fri, 21 Sep 2007 19:08:24 +0200 Received: from localhost (localhost.math.polytechnique.fr [127.0.0.1]) by localdomain.polytechnique.fr (Postfix) with ESMTP id 114AE18741A for ; Fri, 21 Sep 2007 19:08:22 +0200 (CEST) X-Virus-Scanned: amavisd-new at math.polytechnique.fr Received: from localdomain.polytechnique.fr ([127.0.0.1]) by localhost (hermes.math.polytechnique.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PSzxnlMptl3K for ; Fri, 21 Sep 2007 19:08:13 +0200 (CEST) Received: from daphne.math.polytechnique.fr (daphne.math.polytechnique.fr [129.104.3.3]) by localdomain.polytechnique.fr (Postfix) with ESMTP id 1176318741C for ; Fri, 21 Sep 2007 19:08:13 +0200 (CEST) Received: by daphne.math.polytechnique.fr (Postfix, from userid 10074) id F351D6D604; Fri, 21 Sep 2007 19:08:12 +0200 (CEST) Date: Fri, 21 Sep 2007 19:08:12 +0200 From: Francois Vigneron To: freebsd-current@freebsd.org Message-ID: <20070921170812.GA14427@math.polytechnique.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Mailman-Approved-At: Mon, 24 Sep 2007 08:18:03 +0000 Subject: csh dumps core on logout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Sep 2007 18:08:18 -0000 Hello. I haven't found this bug on the archive. I just installed the CURRENT-7.0 of 08/2007 and I notice the following error. If a user fills his .logout file with: [ `tty` \> "/dev/ttyv" ] && [ -x /usr/sbin/lptest ] && repeat 3 /usr/sbin/lptest clear (which prints trash if he logs at the console so nobody can reread the previous commands using the ScrollLock in the video memory) than csh dumps core at logout. The problem seem to be the 'repeat' command as I do not have problem if I use lptest && lptest && lptest instead. -- Francois From owner-freebsd-current@FreeBSD.ORG Fri Sep 21 23:16:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0492916A418; Fri, 21 Sep 2007 23:16:18 +0000 (UTC) (envelope-from robert.moore@intel.com) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by mx1.freebsd.org (Postfix) with ESMTP id BC8D413C44B; Fri, 21 Sep 2007 23:16:17 +0000 (UTC) (envelope-from robert.moore@intel.com) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga102.jf.intel.com with ESMTP; 21 Sep 2007 15:47:29 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.20,285,1186383600"; d="scan'208";a="147546736" Received: from orsmsx334.jf.intel.com ([10.22.226.45]) by fmsmga002.fm.intel.com with ESMTP; 21 Sep 2007 15:47:29 -0700 Received: from orsmsx415.amr.corp.intel.com ([10.22.226.49]) by orsmsx334.jf.intel.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 21 Sep 2007 15:47:28 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 21 Sep 2007 15:47:21 -0700 Message-ID: In-Reply-To: <200709211827.29763.jkim@FreeBSD.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [PATCH] OsdSynch.c modernization thread-index: Acf8nqwbRg8q4w5ORsikv2fnT1cQ0wAAonQQ References: <200709181516.11207.jkim@FreeBSD.org><200709211715.17940.jhb@freebsd.org> <200709211827.29763.jkim@FreeBSD.org> From: "Moore, Robert" To: "Jung-uk Kim" , "John Baldwin" X-OriginalArrivalTime: 21 Sep 2007 22:47:28.0406 (UTC) FILETIME=[62FD7360:01C7FCA1] X-Mailman-Approved-At: Mon, 24 Sep 2007 08:18:03 +0000 Cc: freebsd-acpi@FreeBSD.org, freebsd-current@FreeBSD.org Subject: RE: [PATCH] OsdSynch.c modernization X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Sep 2007 23:16:18 -0000 I can look around a bit, but I don't think we'd make any system calls while holding a spinlock.=20 Bob >-----Original Message----- >From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >acpi@freebsd.org] On Behalf Of Jung-uk Kim >Sent: Friday, September 21, 2007 3:27 PM >To: John Baldwin >Cc: freebsd-acpi@FreeBSD.org; freebsd-current@FreeBSD.org >Subject: Re: [PATCH] OsdSynch.c modernization > >On Friday 21 September 2007 05:15 pm, John Baldwin wrote: >> On Tuesday 18 September 2007 03:16:07 pm Jung-uk Kim wrote: >> > I have rewritten sys/dev/acpica/Osd/OsdSynch.c to match the >> > modern ACPI-CA and -CURRENT: >> > >> > http://people.freebsd.org/~jkim/acpica/OsdSynch.diff >> >> Why do you use a loop around tsleep() rather than just use >> sx_xlock() (which will block) for the WAIT_FOREVER case when >> waiting on a semaphore? > >You mean for AcpiOsAcquireMutex()? sx_xlock() cannot be waken up by >the wait channel. > >> Why don't you just use a spin mutex for the spin lock? >> That is a far better fit than the sx lock stuff you are doing. >> Manually doing spinlock_enter() (wrongly btw, you should use >> critical_enter(), not sched_pin() otherwise you can be preempted) >> just to avoid the assertion failure is just going to result in >> obscure hangs. Does ACPI-CA want to malloc() while holding an ACPI >> spin lock or something? > >I thought exactly the same when I started rewriting it (almost half >year ago!). I have tried all of the above, spent numerous sleepless >nights, and miserably failed. :-( > >Spin mutex is too restrictive (e.g., it cannot be used with other >locks gracefully). critical_enter() causes: > >panic: blockable sleep lock (sleep mutex) 32 @ >/usr/src/sys/vm/uma_core.c:1830 cpuid =3D 0 >KDB: enter: panic >[thread pid 21 tid 100013 ] >Stopped at kdb_enter+0x32: leave > >http://docs.freebsd.org/cgi/mid.cgi?200709121927.46465.jkim > >I guess it wants to malloc() while holding spin lock although I >haven't traced it down. > >I intend to investigate and fix further after RELENG_7 is branched and >I really like to hear more ideas from you. > >Thanks, > >Jung-uk Kim >_______________________________________________ >freebsd-acpi@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-acpi >To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sun Sep 23 08:12:23 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D81F16A511; Sun, 23 Sep 2007 08:12:23 +0000 (UTC) (envelope-from wawa@yandex-team.ru) Received: from relanium.yandex.ru (relanium.yandex.ru [213.180.193.88]) by mx1.freebsd.org (Postfix) with ESMTP id 67D5113C459; Sun, 23 Sep 2007 08:12:22 +0000 (UTC) (envelope-from wawa@yandex-team.ru) Received: from [87.250.227.232] (v3-227-232.yandex.net [87.250.227.232]) by relanium.yandex.ru (8.14.1/8.14.1) with ESMTP id l8N7oEgA089771 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 23 Sep 2007 11:50:27 +0400 (MSD) (envelope-from wawa@yandex-team.ru) Message-ID: <46F61AB5.4010207@yandex-team.ru> Date: Sun, 23 Sep 2007 11:50:13 +0400 From: Vladimir Ivanov Organization: Yandex LLC User-Agent: Thunderbird 1.5.0.13 (X11/20070824) MIME-Version: 1.0 To: Kip Macy References: <2a41acea0709221656n4aa62776y488c7f2da262c9f6@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: Dr.Web (R) for Mail Servers on relanium.yandex.ru host X-Antivirus-Code: 100000 X-Mailman-Approved-At: Mon, 24 Sep 2007 08:18:03 +0000 Cc: "freebsd-net@freebsd.org" , FreeBSD Current , Jack Vogel Subject: Re: TX Multiqueue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 08:12:23 -0000 Kip Macy wrote: > My ethng branch supports multiple rx and tx queues. > > -Kip > > On 9/22/07, Jack Vogel wrote: >> Our newest E1000 nic, the 82575, and the Oplin 10G hardware are capable of >> multiple queues both on the receive and the send side. On the receive end for >> the Oplin driver the queues actually help distribute interrupts and improve >> performance without any special support in the stack. I've published SMP versions of em and ixgb drivers several months ago (see http://people.yandex-team.ru/~wawa). Did you have time to see it, Jack ? That drivers use several kthreads to process one RX queue. The main idea is to increase a performance. Vladimir >> >> I have been asked about multiple queues on the TX side, embedded applice >> type system builders for instance are interested I suppose for >> priority queueing. >> Is anyone working on this right now, and if not does this sound like something >> anyone is interested in doing? >> >> I would like to see MQ on both TX and RX that drivers could use if able. >> >> Jack From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 09:24:03 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3D2616A417 for ; Mon, 24 Sep 2007 09:24:03 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.freebsd.org (Postfix) with ESMTP id 5276013C46A for ; Mon, 24 Sep 2007 09:24:03 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1122258nfb for ; Mon, 24 Sep 2007 02:24:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; bh=RoexIoV9GPxx62SHr7C+botl+ryLSHfoUbkjgV/AlFI=; b=AJycrZyu4EJJ6dBh8yxnYf+6i2y9Njjbo1UE6pTg8c+cYxfgCvfitKLzoxSgqfPPuKN6qTH1iICHIa3sohcESO/Fkj7UTWcZf86pFbPRZAUs7825PDoPsa+W1AI/qv9aP/CUpaoz5W48nnwv8GBD00Uo/zAjFdBg1BvEEr6PM30= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; b=KGmK6yKFrIrUNLdIURyO5e/pEdIQeqwrsoS7cOU5VoIiWZzc1lo9E6xEdRyeWz5IokVhdfjr6zsSC+aiYD4njRTOksBm72edoC3CL1t3OwpszYNsBj6e0fSRNBuvkv87bHY9lpammh3xes3M5etR/2nWmXprKUgFHen42CqhCYo= Received: by 10.78.185.15 with SMTP id i15mr3394424huf.1190625842012; Mon, 24 Sep 2007 02:24:02 -0700 (PDT) Received: from orion ( [77.109.32.210]) by mx.google.com with ESMTPS id 39sm2543596hug.2007.09.24.02.23.56 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 24 Sep 2007 02:24:01 -0700 (PDT) From: Nikolay Pavlov To: d@delphij.net Date: Mon, 24 Sep 2007 12:23:48 +0300 User-Agent: KMail/1.9.7 References: <20070917194009.W84177@woozle.rinet.ru> <200709171912.09060.qpadla@gmail.com> <46EEA89F.3060606@delphij.net> In-Reply-To: <46EEA89F.3060606@delphij.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1284893.dvIVtFniiH"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200709241223.52140.qpadla@gmail.com> Cc: MingyanGuo , current@freebsd.org, Dmitry Morozovsky , freebsd-current@freebsd.org, delphij@freebsd.org, Howard Su Subject: Re: tmpfs on contemporary -current: panic: locked against myself X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: qpadla@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 09:24:04 -0000 --nextPart1284893.dvIVtFniiH Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 17 September 2007 19:17:35 LI Xin wrote: > Nikolay Pavlov wrote: > [...] > > > Yes it's still need more fixes. I have send a mail to delphij > > regarding this one panic: > > http://docs.freebsd.org/cgi/mid.cgi?200708201848.22157.qpadla > > But with out any response. May be he is busy :( > > Sorry I am aware of the issue and am busy for $REALJOB these days. I > have cc'ed howardsu@ and mingyanguo@ to see if they have some > suggestions. The problem seems to be a race condition caused by > incorrect VFS related locking, but diagnosing it is relatively hard. > > I'll try to pick up with the development in early October. Before that > I can only do some small scale bugfixes rather than investing more time > into tmpfs stuff... :-( > > Cheers, Just want to be sure that no one lose this. Here is a PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D116600 =2D-=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 =2D Best regards, Nikolay Pavlov. <<<----------------------------------- = =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 --nextPart1284893.dvIVtFniiH Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBG94Io/2R6KvEYGaIRAoD6AJ9uZODV2Jm+jl4TGEI2CceKPLoxTgCfd82l 5qLa8+s65ah6vzsGNiMRZa8= =3XHM -----END PGP SIGNATURE----- --nextPart1284893.dvIVtFniiH-- From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 09:24:04 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 004B716A419 for ; Mon, 24 Sep 2007 09:24:03 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.freebsd.org (Postfix) with ESMTP id 5312D13C46E for ; Mon, 24 Sep 2007 09:24:03 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1122256nfb for ; Mon, 24 Sep 2007 02:24:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; bh=RoexIoV9GPxx62SHr7C+botl+ryLSHfoUbkjgV/AlFI=; b=AJycrZyu4EJJ6dBh8yxnYf+6i2y9Njjbo1UE6pTg8c+cYxfgCvfitKLzoxSgqfPPuKN6qTH1iICHIa3sohcESO/Fkj7UTWcZf86pFbPRZAUs7825PDoPsa+W1AI/qv9aP/CUpaoz5W48nnwv8GBD00Uo/zAjFdBg1BvEEr6PM30= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; b=KGmK6yKFrIrUNLdIURyO5e/pEdIQeqwrsoS7cOU5VoIiWZzc1lo9E6xEdRyeWz5IokVhdfjr6zsSC+aiYD4njRTOksBm72edoC3CL1t3OwpszYNsBj6e0fSRNBuvkv87bHY9lpammh3xes3M5etR/2nWmXprKUgFHen42CqhCYo= Received: by 10.78.185.15 with SMTP id i15mr3394424huf.1190625842012; Mon, 24 Sep 2007 02:24:02 -0700 (PDT) Received: from orion ( [77.109.32.210]) by mx.google.com with ESMTPS id 39sm2543596hug.2007.09.24.02.23.56 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 24 Sep 2007 02:24:01 -0700 (PDT) From: Nikolay Pavlov To: d@delphij.net Date: Mon, 24 Sep 2007 12:23:48 +0300 User-Agent: KMail/1.9.7 References: <20070917194009.W84177@woozle.rinet.ru> <200709171912.09060.qpadla@gmail.com> <46EEA89F.3060606@delphij.net> In-Reply-To: <46EEA89F.3060606@delphij.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1284893.dvIVtFniiH"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200709241223.52140.qpadla@gmail.com> Cc: MingyanGuo , current@freebsd.org, Dmitry Morozovsky , freebsd-current@freebsd.org, delphij@freebsd.org, Howard Su Subject: Re: tmpfs on contemporary -current: panic: locked against myself X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: qpadla@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 09:24:04 -0000 --nextPart1284893.dvIVtFniiH Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 17 September 2007 19:17:35 LI Xin wrote: > Nikolay Pavlov wrote: > [...] > > > Yes it's still need more fixes. I have send a mail to delphij > > regarding this one panic: > > http://docs.freebsd.org/cgi/mid.cgi?200708201848.22157.qpadla > > But with out any response. May be he is busy :( > > Sorry I am aware of the issue and am busy for $REALJOB these days. I > have cc'ed howardsu@ and mingyanguo@ to see if they have some > suggestions. The problem seems to be a race condition caused by > incorrect VFS related locking, but diagnosing it is relatively hard. > > I'll try to pick up with the development in early October. Before that > I can only do some small scale bugfixes rather than investing more time > into tmpfs stuff... :-( > > Cheers, Just want to be sure that no one lose this. Here is a PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D116600 =2D-=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 =2D Best regards, Nikolay Pavlov. <<<----------------------------------- = =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 --nextPart1284893.dvIVtFniiH Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBG94Io/2R6KvEYGaIRAoD6AJ9uZODV2Jm+jl4TGEI2CceKPLoxTgCfd82l 5qLa8+s65ah6vzsGNiMRZa8= =3XHM -----END PGP SIGNATURE----- --nextPart1284893.dvIVtFniiH-- From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 09:37:34 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C7E216A474 for ; Mon, 24 Sep 2007 09:37:34 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.freebsd.org (Postfix) with ESMTP id EBE8013C458 for ; Mon, 24 Sep 2007 09:37:33 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1125157nfb for ; Mon, 24 Sep 2007 02:37:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=Ylssh0EMARYeob2AjOQRB2XdhvYCVAkGN/UAV7nt3Ec=; b=X2adjFmVOXiAuqhvAWcA2z1pesh/jV5Un4dejXgmKXUqkMqMzWQD/EQsiq0z89zc6keNYox7Gq1Ky6al0Us6MLwKK8SI+s7EXoHbpvILFptByoXz/rVDXRuaZTM3ZouVqP/odgtKIyyXb1m/ECoX9Tfs4+OIspwPsrQf+ljVTZY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=poQbzY1ZJqt/LtGCchQ4D8z9xynYTL9zeP23bpvywYwsRkJBLE9WVofNW6htZR2czHFtOlKznuQfCpNoQraWYzQcGR+c/QbDctupAyXBe0vIDp2cfm+G3z7izp7lYlOlmi9akYgdq1ZisGU0u1RfiE4gvbY9CKVV2chL2Ztbunk= Received: by 10.78.165.16 with SMTP id n16mr1524628hue.1190626652049; Mon, 24 Sep 2007 02:37:32 -0700 (PDT) Received: by 10.78.97.18 with HTTP; Mon, 24 Sep 2007 02:37:31 -0700 (PDT) Message-ID: <3bbf2fe10709240237u790de351wddb81b0c511d7435@mail.gmail.com> Date: Mon, 24 Sep 2007 11:37:31 +0200 From: "Attilio Rao" Sender: asmrookie@gmail.com To: "Jung-uk Kim" In-Reply-To: <200709211827.29763.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200709181516.11207.jkim@FreeBSD.org> <200709211715.17940.jhb@freebsd.org> <200709211827.29763.jkim@FreeBSD.org> X-Google-Sender-Auth: 6126d98f5bb3ab44 Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: [PATCH] OsdSynch.c modernization X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 09:37:34 -0000 2007/9/22, Jung-uk Kim : > I thought exactly the same when I started rewriting it (almost half > year ago!). I have tried all of the above, spent numerous sleepless > nights, and miserably failed. :-( > > Spin mutex is too restrictive (e.g., it cannot be used with other > locks gracefully). critical_enter() causes: > > panic: blockable sleep lock (sleep mutex) 32 @ > /usr/src/sys/vm/uma_core.c:1830 cpuid = 0 > KDB: enter: panic > [thread pid 21 tid 100013 ] > Stopped at kdb_enter+0x32: leave UMA uses its own internal locking scheme which includes blocking mutexes so you cannot maintain a spinlock over its functions. You can however use a blocking mutex instead than a sx lock, that with the help of adaptive spinning emulates a lot better spinlocks behaviour. Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 09:39:09 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EAA8416A419 for ; Mon, 24 Sep 2007 09:39:09 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 0EF0113C469; Mon, 24 Sep 2007 09:39:07 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F785BB.9030800@FreeBSD.org> Date: Mon, 24 Sep 2007 11:39:07 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: "P.U.Kruppa" References: <20070924051118.H9923@small> In-Reply-To: <20070924051118.H9923@small> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 09:39:10 -0000 P.U.Kruppa wrote: > Hello, > > I use a HP Deskjet 990 Cxi via parallel port with cups and hpijs driver on > > FreeBSD pukruppa.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Sep 21 > 16:52:59 CEST 2007 amd64 > > When I try to print a little bit more complex documents (OpenOffice, > pdf) my System will crash. > > On my root terminal there will be a long list of > lpt0: [ITHREAD] > lpt0: [GIANT-LOCKED] > lpt0: [ITHREAD] > [...] > lines, then some dumping activity and a reboot. > > I upgraded to 7.0 last week, so all I can say is: everything was fine > with 6.2 . > > Please tell me if you need more information. Well yeah, how about e.g. the actual details from the panic? Kris From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 09:50:40 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E31B216A418; Mon, 24 Sep 2007 09:50:40 +0000 (UTC) (envelope-from ulrich@pukruppa.net) Received: from pukruppa.net (pukruppa.net [213.146.114.24]) by mx1.freebsd.org (Postfix) with ESMTP id 3C49513C45A; Mon, 24 Sep 2007 09:50:39 +0000 (UTC) (envelope-from ulrich@pukruppa.net) Received: from pukruppa.net (localhost [127.0.0.1]) by pukruppa.net (8.14.1/8.14.1) with ESMTP id l8O9ocIM010703; Mon, 24 Sep 2007 11:50:38 +0200 (CEST) (envelope-from ulrich@pukruppa.net) Received: from localhost (ulrich@localhost) by pukruppa.net (8.14.1/8.14.1/Submit) with ESMTP id l8O9obo6010700; Mon, 24 Sep 2007 11:50:38 +0200 (CEST) (envelope-from ulrich@pukruppa.net) Date: Mon, 24 Sep 2007 11:50:37 +0200 (CEST) From: "P.U.Kruppa" X-X-Sender: ulrich@small To: Kris Kennaway In-Reply-To: <46F785BB.9030800@FreeBSD.org> Message-ID: <20070924114923.C10251@small> References: <20070924051118.H9923@small> <46F785BB.9030800@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 09:50:41 -0000 On Mon, 24 Sep 2007, Kris Kennaway wrote: > P.U.Kruppa wrote: >> Hello, >> >> I use a HP Deskjet 990 Cxi via parallel port with cups and hpijs driver on >> >> FreeBSD pukruppa.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Sep 21 >> 16:52:59 CEST 2007 amd64 >> >> When I try to print a little bit more complex documents (OpenOffice, pdf) >> my System will crash. >> >> On my root terminal there will be a long list of >> lpt0: [ITHREAD] >> lpt0: [GIANT-LOCKED] >> lpt0: [ITHREAD] >> [...] >> lines, then some dumping activity and a reboot. >> >> I upgraded to 7.0 last week, so all I can say is: everything was fine with >> 6.2 . >> >> Please tell me if you need more information. > > Well yeah, how about e.g. the actual details from the panic? How do I get them? Do I have to recompile my kernel (I put off debugging and Witness Options)? Uli. > > Kris > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > Peter Ulrich Kruppa Wuppertal Germany From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 09:55:22 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4116E16A41B; Mon, 24 Sep 2007 09:55:22 +0000 (UTC) (envelope-from rermilov@team.vega.ru) Received: from mail.vega.ru (mx1.vega.ru [87.242.77.163]) by mx1.freebsd.org (Postfix) with ESMTP id D238013C45A; Mon, 24 Sep 2007 09:55:21 +0000 (UTC) (envelope-from rermilov@team.vega.ru) Received: from [87.242.97.68] (port=62185 helo=edoofus.dev.vega.ru) by mail.vega.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IZk3Q-0003QQ-Jm; Mon, 24 Sep 2007 09:16:36 +0000 Received: from edoofus.dev.vega.ru (localhost [127.0.0.1]) by edoofus.dev.vega.ru (8.14.1/8.14.1) with ESMTP id l8O9FxKQ048768; Mon, 24 Sep 2007 13:15:59 +0400 (MSD) (envelope-from rermilov@team.vega.ru) Received: (from ru@localhost) by edoofus.dev.vega.ru (8.14.1/8.14.1/Submit) id l8O9Fw4K048767; Mon, 24 Sep 2007 13:15:58 +0400 (MSD) (envelope-from rermilov@team.vega.ru) X-Authentication-Warning: edoofus.dev.vega.ru: ru set sender to rermilov@team.vega.ru using -f Date: Mon, 24 Sep 2007 13:15:58 +0400 From: Ruslan Ermilov To: Kris Kennaway Message-ID: <20070924091558.GB32006@team.vega.ru> References: <20070921102946.T11189@borg> <46F415BF.9010500@FreeBSD.org> <20070921140550.D96923@thebighonker.lerctr.org> <46F41CFF.6080108@FreeBSD.org> <46F58799.1030702@freebsd.org> <46F58B21.8030307@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46F58B21.8030307@FreeBSD.org> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Darren Reed , freebsd-current@FreeBSD.org, Larry Rosenman Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 09:55:22 -0000 On Sat, Sep 22, 2007 at 11:37:37PM +0200, Kris Kennaway wrote: > Darren Reed wrote: >> Kris Kennaway wrote: >>> Larry Rosenman wrote: >>>> On Fri, 21 Sep 2007, Kris Kennaway wrote: >>>> >>>>> Larry Rosenman wrote: >>>>>> I'm a heavy ZFS user, and got the following panic on 2007-09-18 >>>>>> source/world: >>>>> >>>>> This is a FAQ, please see the archives (you need to increase the >>>>> vm.kmem_size to provide more memory to ZFS). >>>> >>>> I thought that was only for i386, and it hadn't been an issue before. >>> >>> Nope. It is also load-dependent. >> So I just received this courtesy of ZFS: >> panic: kmem_malloc(131072): kmem_map too small: 343027712 total allocated >> cpuid = 0 >> KDB: enter: panic >> This was with these settings in loader.conf: >> vm.kmem_size=419430400 >> vm.kmem_size_max=419430400 Setting both doesn't make sense; kmem_size will take over. kmem_size_max only limits the automatically computed value of kmem_size, which is: /* * How many physical pages per KVA page allocated. * min(max(max(VM_KMEM_SIZE, Physical memory/VM_KMEM_SIZE_SCALE), * VM_KMEM_SIZE_MIN), VM_KMEM_SIZE_MAX) * is the total KVA space allocated for kmem_map. */ >> vfs.zfs.arc_max=409715200 >> (That's 400M, 400M and 40M, respectively.) >> Stupid question, perhaps, but is vm.kmem_size/vm.kmem_size_max limited by >> physical RAM? > > Yes. > To be precise, it's actually limited by 2 * sizeof(physical RAM). It's still size of a _virtual_ memory map (kmem_map), after all: : /* : * Limit kmem virtual size to twice the physical memory. : * This allows for kmem map sparseness, but limits the size : * to something sane. Be careful to not overflow the 32bit : * ints while doing the check. : */ : if (((vm_kmem_size / 2) / PAGE_SIZE) > cnt.v_page_count) : vm_kmem_size = 2 * cnt.v_page_count * PAGE_SIZE; Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 10:07:27 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E73B16A418; Mon, 24 Sep 2007 10:07:27 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id C57DB13C465; Mon, 24 Sep 2007 10:07:25 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F78C59.1020801@FreeBSD.org> Date: Mon, 24 Sep 2007 12:07:21 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Ruslan Ermilov References: <20070921102946.T11189@borg> <46F415BF.9010500@FreeBSD.org> <20070921140550.D96923@thebighonker.lerctr.org> <46F41CFF.6080108@FreeBSD.org> <46F58799.1030702@freebsd.org> <46F58B21.8030307@FreeBSD.org> <20070924091558.GB32006@team.vega.ru> In-Reply-To: <20070924091558.GB32006@team.vega.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Darren Reed , freebsd-current@FreeBSD.org, Larry Rosenman Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 10:07:27 -0000 Ruslan Ermilov wrote: > On Sat, Sep 22, 2007 at 11:37:37PM +0200, Kris Kennaway wrote: >> Darren Reed wrote: >>> Kris Kennaway wrote: >>>> Larry Rosenman wrote: >>>>> On Fri, 21 Sep 2007, Kris Kennaway wrote: >>>>> >>>>>> Larry Rosenman wrote: >>>>>>> I'm a heavy ZFS user, and got the following panic on 2007-09-18 >>>>>>> source/world: >>>>>> This is a FAQ, please see the archives (you need to increase the >>>>>> vm.kmem_size to provide more memory to ZFS). >>>>> I thought that was only for i386, and it hadn't been an issue before. >>>> Nope. It is also load-dependent. >>> So I just received this courtesy of ZFS: >>> panic: kmem_malloc(131072): kmem_map too small: 343027712 total allocated >>> cpuid = 0 >>> KDB: enter: panic >>> This was with these settings in loader.conf: >>> vm.kmem_size=419430400 >>> vm.kmem_size_max=419430400 > > Setting both doesn't make sense; kmem_size will take over. > kmem_size_max only limits the automatically computed value > of kmem_size, which is: > > /* > * How many physical pages per KVA page allocated. > * min(max(max(VM_KMEM_SIZE, Physical memory/VM_KMEM_SIZE_SCALE), > * VM_KMEM_SIZE_MIN), VM_KMEM_SIZE_MAX) > * is the total KVA space allocated for kmem_map. > */ > >>> vfs.zfs.arc_max=409715200 >>> (That's 400M, 400M and 40M, respectively.) >>> Stupid question, perhaps, but is vm.kmem_size/vm.kmem_size_max limited by >>> physical RAM? >> Yes. >> > To be precise, it's actually limited by 2 * sizeof(physical RAM). > It's still size of a _virtual_ memory map (kmem_map), after all: > > : /* > : * Limit kmem virtual size to twice the physical memory. > : * This allows for kmem map sparseness, but limits the size > : * to something sane. Be careful to not overflow the 32bit > : * ints while doing the check. > : */ > : if (((vm_kmem_size / 2) / PAGE_SIZE) > cnt.v_page_count) > : vm_kmem_size = 2 * cnt.v_page_count * PAGE_SIZE; Well OK, but that seems pretty dangerous, because it leaves open a pathway to exhaust all of physical memory and presumably panic. Kris From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 10:07:53 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E699616A41A for ; Mon, 24 Sep 2007 10:07:53 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 1977513C455; Mon, 24 Sep 2007 10:07:52 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F78C79.6080701@FreeBSD.org> Date: Mon, 24 Sep 2007 12:07:53 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: "P.U.Kruppa" References: <20070924051118.H9923@small> <46F785BB.9030800@FreeBSD.org> <20070924114923.C10251@small> In-Reply-To: <20070924114923.C10251@small> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 10:07:54 -0000 P.U.Kruppa wrote: > On Mon, 24 Sep 2007, Kris Kennaway wrote: > >> P.U.Kruppa wrote: >>> Hello, >>> >>> I use a HP Deskjet 990 Cxi via parallel port with cups and hpijs >>> driver on >>> >>> FreeBSD pukruppa.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Sep 21 >>> 16:52:59 CEST 2007 amd64 >>> >>> When I try to print a little bit more complex documents (OpenOffice, >>> pdf) my System will crash. >>> >>> On my root terminal there will be a long list of >>> lpt0: [ITHREAD] >>> lpt0: [GIANT-LOCKED] >>> lpt0: [ITHREAD] >>> [...] >>> lines, then some dumping activity and a reboot. >>> >>> I upgraded to 7.0 last week, so all I can say is: everything was fine >>> with 6.2 . >>> >>> Please tell me if you need more information. >> >> Well yeah, how about e.g. the actual details from the panic? > How do I get them? > Do I have to recompile my kernel (I put off debugging and Witness Options)? Read the developers handbook. Kris From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 10:30:26 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A9F916A418 for ; Mon, 24 Sep 2007 10:30:26 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.190]) by mx1.freebsd.org (Postfix) with ESMTP id BCA9C13C478 for ; Mon, 24 Sep 2007 10:30:25 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by fk-out-0910.google.com with SMTP id b27so1978239fka for ; Mon, 24 Sep 2007 03:30:24 -0700 (PDT) Received: by 10.82.152.16 with SMTP id z16mr8762472bud.1190628349377; Mon, 24 Sep 2007 03:05:49 -0700 (PDT) Received: by 10.82.148.14 with HTTP; Mon, 24 Sep 2007 03:05:49 -0700 (PDT) Message-ID: Date: Mon, 24 Sep 2007 13:05:49 +0300 From: "Vlad GALU" To: "FreeBSD Current" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Bogus numbers with rev 1.209 of sched_ule.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 10:30:26 -0000 -- cut here -- PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 34653 root 1 5 0 3136K 1048K ttyin 0 0:00 nan% getty 37990 root 1 8 0 4328K 2272K wait 1 0:00 nan% bash 37915 dapyx 1 8 0 3564K 1540K wait 0 0:00 nan% su 37711 dapyx 1 20 0 4392K 2432K pause 0 0:00 nan% tcsh -- and here -- -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 10:32:50 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DDE616A41B for ; Mon, 24 Sep 2007 10:32:50 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from pobox.codelabs.ru (pobox.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id E0AD313C469 for ; Mon, 24 Sep 2007 10:32:49 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Resent-From:Resent-Date:Resent-Message-ID:Resent-To:Date:From:To:Message-ID:MIME-Version:Content-Type:Content-Disposition:Resent-Sender:Resent-Date:X-Spam-Status:Subject; b=CZGZrTSkHHaW+9r5lQIcAMVZkQ8JaV/3pAk1JG9gcqXOWVGnB3tZz/WjBCyTDRSY/Pto1A65wCFLycG0j6FsL3Ud7VDls+8z1ROd2XwxH7CV6u9KzIdZ7mpMPHHsaBoy3kMCtMSwo6c/T4eR73/8CbPiTUweJ1co0M8cSVI8aas=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by pobox.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1IZlFB-000DiV-40 for freebsd-current@freebsd.org; Mon, 24 Sep 2007 14:32:49 +0400 Resent-From: rea-fbsd@codelabs.ru Resent-Date: Mon, 24 Sep 2007 14:32:44 +0400 Resent-Message-ID: <20070924103244.GF8111@void.codelabs.ru> Resent-To: freebsd-current@freebsd.org Date: Mon, 24 Sep 2007 13:38:37 +0400 From: Eygene Ryabinkin To: freebsd-current@freebsd.org Message-ID: <20070924093837.GE8111@void.codelabs.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Resent-Sender: rea-fbsd@codelabs.ru Resent-Date: Mon, 24 Sep 2007 14:32:49 +0400 X-Spam-Status: No, score=-1.9 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_50 Subject: [RFC] Make /bin/sh's case construct POSIX-2 conformant X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 10:32:50 -0000 Good day. Basically all that I will say here (and more) is said in bin/116559, http://www.freebsd.org/cgi/query-pr.cgi?pr=116559 IEEE 1003.2 specifies that the return value of the 'case' construct that did not matched any patterns shall be zero. It is not the case now, as shown by the simple test: ----- #!/bin/sh false case test in Test) ;; esac && echo ok ----- Now the case that has no patterns matched does not touch the exit value at all. PR has the patch that fixes the issue. Any comments on it? Maybe someone will be so kind to test this patch on his system(s)? Mine are showing no troubles yet ;)) Thank you! -- Eygene From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 10:45:35 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 177F416A419 for ; Mon, 24 Sep 2007 10:45:35 +0000 (UTC) (envelope-from bsd-current@epcdirect.co.uk) Received: from gunfright.epcdirect.co.uk (gunfright.epcdirect.co.uk [195.10.242.32]) by mx1.freebsd.org (Postfix) with ESMTP id C08A913C45A for ; Mon, 24 Sep 2007 10:45:34 +0000 (UTC) (envelope-from bsd-current@epcdirect.co.uk) Received: from localhost (localhost.epcdirect.co.uk [127.0.0.1]) by gunfright.epcdirect.co.uk (Postfix) with ESMTP id DF7F76175; Mon, 24 Sep 2007 11:45:33 +0100 (BST) X-Virus-Scanned: by GunFright.EPCDirect.co.uk Received: from gunfright.epcdirect.co.uk ([127.0.0.1]) by localhost (gunfright.epcdirect.co.uk [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id V1zMICXBPk0Q; Mon, 24 Sep 2007 11:45:33 +0100 (BST) Received: from lfarr (l-farr.int.epcdirect.co.uk [192.168.6.200]) by gunfright.epcdirect.co.uk (Postfix) with ESMTP id A89CA6108; Mon, 24 Sep 2007 11:45:33 +0100 (BST) From: "Lawrence Farr" To: , References: <1190591939.14488.25.camel@hyperion> In-Reply-To: <1190591939.14488.25.camel@hyperion> Date: Mon, 24 Sep 2007 11:45:27 +0100 Message-ID: <011401c7fe98$04cf7f60$0e6e7e20$@co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acf+N8cUASyThtHQQHyWTBqkWpd9CwAYBmFg Content-Language: en-gb Cc: Subject: RE: bge driver causes freeze X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 10:45:35 -0000 > -----Original Message----- > From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd- > current@freebsd.org] On Behalf Of Cristi Magherusan > Sent: 24 September 2007 00:59 > To: freebsd-current@freebsd.org > Subject: bge driver causes freeze > > Hello, > > I tried the latest snapshot on my HP 6710b laptop, and it behaves just > like the one from august, as reported in this message: > http://lists.freebsd.org/pipermail/freebsd-current/2007- > September/076856.html > > ACPI reports an error, something about out of range temperature value, > then locks the system waiting for some event. By mistake I've found a > workaround by unplugging then plugging back the power cable. In 6.2 it > reported the same error, but didn't lock. > > The real problem is the bge driver that seems to have a critical > regression from 6.2 and completely freezes the system at boot. > Did anyone experienced similar problems of with current bge driver on > another hardware, or this bug happens only with this laptop model? > > Best Regards, > cristi > > -- > Cristi Magherusan, > Universitatea Tehnica din Cluj - Napoca > Centrul de Comunicatii "Pusztai Kalman" > Tel. 0264/401247 http://cc.utcluj.ro It sounds a lot like the issue I'm having on server hardware, see http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/116328 From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 11:59:29 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE24016A418; Mon, 24 Sep 2007 11:59:29 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [210.51.165.229]) by mx1.freebsd.org (Postfix) with ESMTP id 49DA213C494; Mon, 24 Sep 2007 11:59:29 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from localhost (tarsier.geekcn.org [210.51.165.229]) by tarsier.geekcn.org (Postfix) with ESMTP id 099B3EBA730; Mon, 24 Sep 2007 19:59:41 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([210.51.165.229]) by localhost (mail.geekcn.org [210.51.165.229]) (amavisd-new, port 10024) with ESMTP id TYYaV2UMwfKC; Mon, 24 Sep 2007 19:59:36 +0800 (CST) Received: from LI-Xins-MacBook.local (adsl-69-104-2-37.dsl.pltn13.pacbell.net [69.104.2.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id 1C5C1EB9DBA; Mon, 24 Sep 2007 19:59:33 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type; b=D2YD6hkKzz6ifMy7aqivKq5RkKpxoj+Qm5qyHGzs269cyzucCqDoQkLPjqbUgYEQs A9bN+PHQgoQljN/VJb3mQ== Message-ID: <46F7A695.7050603@delphij.net> Date: Mon, 24 Sep 2007 04:59:17 -0700 From: LI Xin Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: qpadla@gmail.com References: <20070917194009.W84177@woozle.rinet.ru> <200709171912.09060.qpadla@gmail.com> <46EEA89F.3060606@delphij.net> <200709241223.52140.qpadla@gmail.com> In-Reply-To: <200709241223.52140.qpadla@gmail.com> X-Enigmail-Version: 0.95.3 OpenPGP: url=http://www.delphij.net/delphij.asc Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enig3DC08C9797BC4F252D8AC84B" Cc: MingyanGuo , d@delphij.net, current@freebsd.org, Dmitry Morozovsky , freebsd-current@freebsd.org, delphij@freebsd.org, Howard Su Subject: Re: tmpfs on contemporary -current: panic: locked against myself X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.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, 24 Sep 2007 11:59:29 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig3DC08C9797BC4F252D8AC84B Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Nikolay Pavlov wrote: > On Monday 17 September 2007 19:17:35 LI Xin wrote: >> Nikolay Pavlov wrote: >> [...] >> >>> Yes it's still need more fixes. I have send a mail to delphij >>> regarding this one panic: >>> http://docs.freebsd.org/cgi/mid.cgi?200708201848.22157.qpadla >>> But with out any response. May be he is busy :( >> Sorry I am aware of the issue and am busy for $REALJOB these days. I >> have cc'ed howardsu@ and mingyanguo@ to see if they have some >> suggestions. The problem seems to be a race condition caused by >> incorrect VFS related locking, but diagnosing it is relatively hard. >> >> I'll try to pick up with the development in early October. Before tha= t >> I can only do some small scale bugfixes rather than investing more tim= e >> into tmpfs stuff... :-( >> >> Cheers, >=20 > Just want to be sure that no one lose this. Here is a PR: > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D116600 Thanks, I've claimed it so I get weekly remainder :-) Cheers, --=20 Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! --------------enig3DC08C9797BC4F252D8AC84B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG96aVOfuToMruuMARClX0AJ9FZrAgZSMGDJrIyEOLFkJsf6vAUgCfaGGu r/1P5vRqWP1GgF8AAZgOqD8= =nk35 -----END PGP SIGNATURE----- --------------enig3DC08C9797BC4F252D8AC84B-- From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 11:59:29 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE24016A418; Mon, 24 Sep 2007 11:59:29 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [210.51.165.229]) by mx1.freebsd.org (Postfix) with ESMTP id 49DA213C494; Mon, 24 Sep 2007 11:59:29 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from localhost (tarsier.geekcn.org [210.51.165.229]) by tarsier.geekcn.org (Postfix) with ESMTP id 099B3EBA730; Mon, 24 Sep 2007 19:59:41 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([210.51.165.229]) by localhost (mail.geekcn.org [210.51.165.229]) (amavisd-new, port 10024) with ESMTP id TYYaV2UMwfKC; Mon, 24 Sep 2007 19:59:36 +0800 (CST) Received: from LI-Xins-MacBook.local (adsl-69-104-2-37.dsl.pltn13.pacbell.net [69.104.2.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id 1C5C1EB9DBA; Mon, 24 Sep 2007 19:59:33 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type; b=D2YD6hkKzz6ifMy7aqivKq5RkKpxoj+Qm5qyHGzs269cyzucCqDoQkLPjqbUgYEQs A9bN+PHQgoQljN/VJb3mQ== Message-ID: <46F7A695.7050603@delphij.net> Date: Mon, 24 Sep 2007 04:59:17 -0700 From: LI Xin Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: qpadla@gmail.com References: <20070917194009.W84177@woozle.rinet.ru> <200709171912.09060.qpadla@gmail.com> <46EEA89F.3060606@delphij.net> <200709241223.52140.qpadla@gmail.com> In-Reply-To: <200709241223.52140.qpadla@gmail.com> X-Enigmail-Version: 0.95.3 OpenPGP: url=http://www.delphij.net/delphij.asc Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enig3DC08C9797BC4F252D8AC84B" Cc: MingyanGuo , d@delphij.net, current@freebsd.org, Dmitry Morozovsky , freebsd-current@freebsd.org, delphij@freebsd.org, Howard Su Subject: Re: tmpfs on contemporary -current: panic: locked against myself X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.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, 24 Sep 2007 11:59:29 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig3DC08C9797BC4F252D8AC84B Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Nikolay Pavlov wrote: > On Monday 17 September 2007 19:17:35 LI Xin wrote: >> Nikolay Pavlov wrote: >> [...] >> >>> Yes it's still need more fixes. I have send a mail to delphij >>> regarding this one panic: >>> http://docs.freebsd.org/cgi/mid.cgi?200708201848.22157.qpadla >>> But with out any response. May be he is busy :( >> Sorry I am aware of the issue and am busy for $REALJOB these days. I >> have cc'ed howardsu@ and mingyanguo@ to see if they have some >> suggestions. The problem seems to be a race condition caused by >> incorrect VFS related locking, but diagnosing it is relatively hard. >> >> I'll try to pick up with the development in early October. Before tha= t >> I can only do some small scale bugfixes rather than investing more tim= e >> into tmpfs stuff... :-( >> >> Cheers, >=20 > Just want to be sure that no one lose this. Here is a PR: > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D116600 Thanks, I've claimed it so I get weekly remainder :-) Cheers, --=20 Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! --------------enig3DC08C9797BC4F252D8AC84B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG96aVOfuToMruuMARClX0AJ9FZrAgZSMGDJrIyEOLFkJsf6vAUgCfaGGu r/1P5vRqWP1GgF8AAZgOqD8= =nk35 -----END PGP SIGNATURE----- --------------enig3DC08C9797BC4F252D8AC84B-- From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 13:04:38 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 053A116A419; Mon, 24 Sep 2007 13:04:38 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) by mx1.freebsd.org (Postfix) with ESMTP id C429B13C45B; Mon, 24 Sep 2007 13:04:37 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org ([192.147.25.65]:64353) by thebighonker.lerctr.org with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IZnc3-000Luz-KV; Mon, 24 Sep 2007 08:04:37 -0500 Date: Mon, 24 Sep 2007 08:04:33 -0500 (CDT) From: Larry Rosenman To: Kris Kennaway In-Reply-To: <46F78C59.1020801@FreeBSD.org> Message-ID: <20070924080347.O84223@thebighonker.lerctr.org> References: <20070921102946.T11189@borg> <46F415BF.9010500@FreeBSD.org> <20070921140550.D96923@thebighonker.lerctr.org> <46F41CFF.6080108@FreeBSD.org> <46F58799.1030702@freebsd.org> <46F58B21.8030307@FreeBSD.org> <20070924091558.GB32006@team.vega.ru> <46F78C59.1020801@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: -4.4 (----) X-LERCTR-Spam-Score: -4.4 (----) X-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8,BAYES_00=-2.599 X-LERCTR-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8,BAYES_00=-2.599 DomainKey-Status: no signature Cc: Darren Reed , freebsd-current@FreeBSD.org, Ruslan Ermilov Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 13:04:38 -0000 On Mon, 24 Sep 2007, Kris Kennaway wrote: > Ruslan Ermilov wrote: >> On Sat, Sep 22, 2007 at 11:37:37PM +0200, Kris Kennaway wrote: >>> Darren Reed wrote: >>>> Kris Kennaway wrote: >>>>> Larry Rosenman wrote: >>>>>> On Fri, 21 Sep 2007, Kris Kennaway wrote: >>>>>> >>>>>>> Larry Rosenman wrote: >>>>>>>> I'm a heavy ZFS user, and got the following panic on 2007-09-18 >>>>>>>> source/world: >>>>>>> This is a FAQ, please see the archives (you need to increase the >>>>>>> vm.kmem_size to provide more memory to ZFS). >>>>>> I thought that was only for i386, and it hadn't been an issue before. >>>>> Nope. It is also load-dependent. >>>> So I just received this courtesy of ZFS: >>>> panic: kmem_malloc(131072): kmem_map too small: 343027712 total allocated >>>> cpuid = 0 >>>> KDB: enter: panic >>>> This was with these settings in loader.conf: >>>> vm.kmem_size=419430400 >>>> vm.kmem_size_max=419430400 >> >> Setting both doesn't make sense; kmem_size will take over. >> kmem_size_max only limits the automatically computed value >> of kmem_size, which is: >> >> /* >> * How many physical pages per KVA page allocated. >> * min(max(max(VM_KMEM_SIZE, Physical memory/VM_KMEM_SIZE_SCALE), >> * VM_KMEM_SIZE_MIN), VM_KMEM_SIZE_MAX) >> * is the total KVA space allocated for kmem_map. >> */ >> >>>> vfs.zfs.arc_max=409715200 >>>> (That's 400M, 400M and 40M, respectively.) >>>> Stupid question, perhaps, but is vm.kmem_size/vm.kmem_size_max limited by >>>> physical RAM? >>> Yes. >>> >> To be precise, it's actually limited by 2 * sizeof(physical RAM). >> It's still size of a _virtual_ memory map (kmem_map), after all: >> >> : /* >> : * Limit kmem virtual size to twice the physical memory. >> : * This allows for kmem map sparseness, but limits the size >> : * to something sane. Be careful to not overflow the 32bit >> : * ints while doing the check. >> : */ >> : if (((vm_kmem_size / 2) / PAGE_SIZE) > cnt.v_page_count) >> : vm_kmem_size = 2 * cnt.v_page_count * PAGE_SIZE; > > Well OK, but that seems pretty dangerous, because it leaves open a pathway to > exhaust all of physical memory and presumably panic. is KVA pageable? Is the kmem_map dedicating non-pageable memory? I've set my vm.kmem_max to 1G, (on a 4G amd64 box). Is that reasonable? LER > > Kris > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 14:42:50 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99F3D16A419; Mon, 24 Sep 2007 14:42:50 +0000 (UTC) (envelope-from rermilov@team.vega.ru) Received: from mail.vega.ru (mx1.vega.ru [87.242.77.163]) by mx1.freebsd.org (Postfix) with ESMTP id 56BD713C459; Mon, 24 Sep 2007 14:42:50 +0000 (UTC) (envelope-from rermilov@team.vega.ru) Received: from [87.242.97.68] (port=52302 helo=edoofus.dev.vega.ru) by mail.vega.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IZp96-0009op-0i; Mon, 24 Sep 2007 14:42:48 +0000 Received: from edoofus.dev.vega.ru (localhost [127.0.0.1]) by edoofus.dev.vega.ru (8.14.1/8.14.1) with ESMTP id l8OEgAQY084631; Mon, 24 Sep 2007 18:42:10 +0400 (MSD) (envelope-from rermilov@team.vega.ru) Received: (from ru@localhost) by edoofus.dev.vega.ru (8.14.1/8.14.1/Submit) id l8OEgApl084630; Mon, 24 Sep 2007 18:42:10 +0400 (MSD) (envelope-from rermilov@team.vega.ru) X-Authentication-Warning: edoofus.dev.vega.ru: ru set sender to rermilov@team.vega.ru using -f Date: Mon, 24 Sep 2007 18:42:10 +0400 From: Ruslan Ermilov To: Larry Rosenman Message-ID: <20070924144210.GA82735@team.vega.ru> References: <20070921102946.T11189@borg> <46F415BF.9010500@FreeBSD.org> <20070921140550.D96923@thebighonker.lerctr.org> <46F41CFF.6080108@FreeBSD.org> <46F58799.1030702@freebsd.org> <46F58B21.8030307@FreeBSD.org> <20070924091558.GB32006@team.vega.ru> <46F78C59.1020801@FreeBSD.org> <20070924080347.O84223@thebighonker.lerctr.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070924080347.O84223@thebighonker.lerctr.org> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Darren Reed , Kris Kennaway , freebsd-current@FreeBSD.org Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 14:42:50 -0000 On Mon, Sep 24, 2007 at 08:04:33AM -0500, Larry Rosenman wrote: > On Mon, 24 Sep 2007, Kris Kennaway wrote: > >> Ruslan Ermilov wrote: >>> On Sat, Sep 22, 2007 at 11:37:37PM +0200, Kris Kennaway wrote: >>>> Darren Reed wrote: [...] >>>>> Stupid question, perhaps, but is vm.kmem_size/vm.kmem_size_max limited >>>>> by physical RAM? >>>> Yes. >>> To be precise, it's actually limited by 2 * sizeof(physical RAM). >>> It's still size of a _virtual_ memory map (kmem_map), after all: >>> : /* >>> : * Limit kmem virtual size to twice the physical memory. >>> : * This allows for kmem map sparseness, but limits the size >>> : * to something sane. Be careful to not overflow the 32bit >>> : * ints while doing the check. >>> : */ >>> : if (((vm_kmem_size / 2) / PAGE_SIZE) > cnt.v_page_count) >>> : vm_kmem_size = 2 * cnt.v_page_count * PAGE_SIZE; >> >> Well OK, but that seems pretty dangerous, because it leaves open a pathway >> to exhaust all of physical memory and presumably panic. > > is KVA pageable? Is the kmem_map dedicating non-pageable memory? > kmem_map is used to map memory for the zone allocator, including malloc(9). > I've set my vm.kmem_max to 1G, (on a 4G amd64 box). Is that reasonable? > It just means that your kernel can "malloc" up to 1G of memory. Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 14:50:46 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0971616A418; Mon, 24 Sep 2007 14:50:46 +0000 (UTC) (envelope-from rermilov@team.vega.ru) Received: from mail.vega.ru (mx1.vega.ru [87.242.77.163]) by mx1.freebsd.org (Postfix) with ESMTP id BDC1B13C448; Mon, 24 Sep 2007 14:50:45 +0000 (UTC) (envelope-from rermilov@team.vega.ru) Received: from [87.242.97.68] (port=57267 helo=edoofus.dev.vega.ru) by mail.vega.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IZpGm-000A30-Tn; Mon, 24 Sep 2007 14:50:44 +0000 Received: from edoofus.dev.vega.ru (localhost [127.0.0.1]) by edoofus.dev.vega.ru (8.14.1/8.14.1) with ESMTP id l8OEo7RU084693; Mon, 24 Sep 2007 18:50:07 +0400 (MSD) (envelope-from rermilov@team.vega.ru) Received: (from ru@localhost) by edoofus.dev.vega.ru (8.14.1/8.14.1/Submit) id l8OEo7G0084692; Mon, 24 Sep 2007 18:50:07 +0400 (MSD) (envelope-from rermilov@team.vega.ru) X-Authentication-Warning: edoofus.dev.vega.ru: ru set sender to rermilov@team.vega.ru using -f Date: Mon, 24 Sep 2007 18:50:07 +0400 From: Ruslan Ermilov To: Darren Reed Message-ID: <20070924145007.GB82735@team.vega.ru> References: <46F6379B.9050000@freebsd.org> <46F64A4B.8000804@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46F64A4B.8000804@freebsd.org> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: FreeBSD Current Subject: Re: yacc bug in reader.c:end_rule() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 14:50:46 -0000 On Sun, Sep 23, 2007 at 04:13:15AM -0700, Darren Reed wrote: > Darren Reed wrote: >> There's a fairly obvious bug in yacc's reader.c but I'm not sure what the >> right fix is. >> >> Witness: >> end_rule() >> { >> int i; >> >> if (!last_was_action && plhs[nrules]->tag) >> { >> for (i = nitems - 1; pitem[i]; --i) continue; >> if (pitem[i + 1] == 0 || pitem[i+1]->tag != plhs[nrules]->tag) >> ... >> } >> >> ...clearly if pitem[nitems-1] == NULL (and nitems is the size of the >> array from [0,nitems-1]) then the if() will access beyond the bounds >> of the array. >> >> There's also the question of i being able to run below 0 too here. >> Not possible: first four pitem's are explicitly set to NULL in reader.c:initialize_grammar(). >> I don't know if the bug is here or if the bug is elsewhere in yacc, >> but I doubt that the "fix" is s/i + 1/i/. *Maybe* "i = nitems - 2;"? >> >> The bug can be masked by using calloc instead of malloc and similar >> other tricks, but there is something more fundamentaly wrong here. >> >> Has anyone else run into this? > > The following sample grammar will exercise the bug: > > %{ > %} > > %union { > char *ptr; > }; > > %type test > %% > > test: | $$ = malloc(2); It crashes even when written "correctly" as: test: | { $$ = malloc(2); } > ; > > %% > > (The error here is that "test" has an undefined return.) > Try this patch. It replaces a non-sense with a fix for the bug. %%% Index: reader.c =================================================================== RCS file: /home/ncvs/src/usr.bin/yacc/reader.c,v retrieving revision 1.19 diff -u -p -r1.19 reader.c --- reader.c 25 Aug 2002 13:23:09 -0000 1.19 +++ reader.c 24 Sep 2007 14:16:18 -0000 @@ -1257,7 +1257,7 @@ end_rule() if (!last_was_action && plhs[nrules]->tag) { for (i = nitems - 1; pitem[i]; --i) continue; - if (pitem[i+1] == 0 || pitem[i+1]->tag != plhs[nrules]->tag) + if (i == nitems - 1 || pitem[i+1]->tag != plhs[nrules]->tag) default_action_warning(); } %%% Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 14:59:18 2007 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2ED2F16A417 for ; Mon, 24 Sep 2007 14:59:18 +0000 (UTC) (envelope-from dlt@mebtel.net) Received: from bilbo.mebtel.net (mail3.mebtel.net [64.40.67.42]) by mx1.freebsd.org (Postfix) with ESMTP id 1196E13C448 for ; Mon, 24 Sep 2007 14:59:17 +0000 (UTC) (envelope-from dlt@mebtel.net) Received: from localhost (localhost [127.0.0.1]) by bilbo.mebtel.net (Postfix) with ESMTP id E62857B62; Mon, 24 Sep 2007 10:17:11 -0400 (EDT) Received: from bilbo.mebtel.net ([127.0.0.1]) by localhost (mail3 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16860-02-4; Mon, 24 Sep 2007 10:17:10 -0400 (EDT) Received: from localhost (66-79-79-161.dsl.mebtel.net [66.79.79.161]) by bilbo.mebtel.net (Postfix) with ESMTP id 25AB97B64; Mon, 24 Sep 2007 10:17:10 -0400 (EDT) Date: Mon, 24 Sep 2007 10:17:10 -0400 From: Derek Tattersall To: Eygene Ryabinkin Message-ID: <20070924141710.GA80377@lorne.arm.org> References: <20070924093837.GE8111@void.codelabs.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070924093837.GE8111@void.codelabs.ru> User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Virus-Scanned: by amavisd-new at mebtel.net Cc: current@FreeBSD.org Subject: Re: [RFC] Make /bin/sh's case construct POSIX-2 conformant X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dlt@mebtel.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 14:59:18 -0000 * Eygene Ryabinkin [070924 08:57]: > Good day. > > Basically all that I will say here (and more) is said in bin/116559, > http://www.freebsd.org/cgi/query-pr.cgi?pr=116559 > > IEEE 1003.2 specifies that the return value of the 'case' construct > that did not matched any patterns shall be zero. It is not the > case now, as shown by the simple test: > ----- > #!/bin/sh > > false > case test in > Test) > ;; > esac && echo ok > ----- > Now the case that has no patterns matched does not touch the exit > value at all. PR has the patch that fixes the issue. > > Any comments on it? Maybe someone will be so kind to test this > patch on his system(s)? Mine are showing no troubles yet ;)) > > Thank you! > -- > Eygene > _______________________________________________ > 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" On my amd64 -CURRENT system, cvsuped yesterday, the patch applies cleanly, the build of sh proceeded without error and the test worked perfectly. Thanks very much for the improvement! -- Best regards, Derek Tattersall dlt@mebtel.net dlt666@yahoo.com dtatters@gmail.com From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 15:28:43 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DEE916A418; Mon, 24 Sep 2007 15:28:43 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 1908B13C457; Mon, 24 Sep 2007 15:28:42 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l8OFSdem044869; Mon, 24 Sep 2007 09:28:39 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <46F7D7A4.5090007@samsco.org> Date: Mon, 24 Sep 2007 09:28:36 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4 MIME-Version: 1.0 To: Ruslan Ermilov References: <20070921102946.T11189@borg> <46F415BF.9010500@FreeBSD.org> <20070921140550.D96923@thebighonker.lerctr.org> <46F41CFF.6080108@FreeBSD.org> <46F58799.1030702@freebsd.org> <46F58B21.8030307@FreeBSD.org> <20070924091558.GB32006@team.vega.ru> <46F78C59.1020801@FreeBSD.org> <20070924080347.O84223@thebighonker.lerctr.org> <20070924144210.GA82735@team.vega.ru> In-Reply-To: <20070924144210.GA82735@team.vega.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Mon, 24 Sep 2007 09:28:39 -0600 (MDT) X-Spam-Status: No, score=-1.4 required=5.5 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: Darren Reed , freebsd-current@freebsd.org, Larry Rosenman Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 15:28:43 -0000 Ruslan Ermilov wrote: > On Mon, Sep 24, 2007 at 08:04:33AM -0500, Larry Rosenman wrote: >> On Mon, 24 Sep 2007, Kris Kennaway wrote: >> >>> Ruslan Ermilov wrote: >>>> On Sat, Sep 22, 2007 at 11:37:37PM +0200, Kris Kennaway wrote: >>>>> Darren Reed wrote: > [...] >>>>>> Stupid question, perhaps, but is vm.kmem_size/vm.kmem_size_max limited >>>>>> by physical RAM? >>>>> Yes. >>>> To be precise, it's actually limited by 2 * sizeof(physical RAM). >>>> It's still size of a _virtual_ memory map (kmem_map), after all: >>>> : /* >>>> : * Limit kmem virtual size to twice the physical memory. >>>> : * This allows for kmem map sparseness, but limits the size >>>> : * to something sane. Be careful to not overflow the 32bit >>>> : * ints while doing the check. >>>> : */ >>>> : if (((vm_kmem_size / 2) / PAGE_SIZE) > cnt.v_page_count) >>>> : vm_kmem_size = 2 * cnt.v_page_count * PAGE_SIZE; >>> Well OK, but that seems pretty dangerous, because it leaves open a pathway >>> to exhaust all of physical memory and presumably panic. >> is KVA pageable? Is the kmem_map dedicating non-pageable memory? >> > kmem_map is used to map memory for the zone allocator, including > malloc(9). > >> I've set my vm.kmem_max to 1G, (on a 4G amd64 box). Is that reasonable? >> > It just means that your kernel can "malloc" up to 1G of memory. > You're all missing the point, I hate to say. What happened is that a change was made recently to more accurately account for allocated memory. Now people are getting kmem_map_too_small panics that weren't getting them before. So while the accounting is now more accurate, the outcome is actually harmful. That needs to be fixed before the release. Scott From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 15:32:25 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6439816A41A; Mon, 24 Sep 2007 15:32:25 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) by mx1.freebsd.org (Postfix) with ESMTP id 548DC13C465; Mon, 24 Sep 2007 15:32:25 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org ([192.147.25.65]:55010) by thebighonker.lerctr.org with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IZpv4-000NOH-VD; Mon, 24 Sep 2007 10:32:24 -0500 Date: Mon, 24 Sep 2007 10:32:18 -0500 (CDT) From: Larry Rosenman To: Scott Long In-Reply-To: <46F7D7A4.5090007@samsco.org> Message-ID: <20070924103201.A89893@thebighonker.lerctr.org> References: <20070921102946.T11189@borg> <46F415BF.9010500@FreeBSD.org> <20070921140550.D96923@thebighonker.lerctr.org> <46F41CFF.6080108@FreeBSD.org> <46F58799.1030702@freebsd.org> <46F58B21.8030307@FreeBSD.org> <20070924091558.GB32006@team.vega.ru> <46F78C59.1020801@FreeBSD.org> <20070924080347.O84223@thebighonker.lerctr.org> <20070924144210.GA82735@team.vega.ru> <46F7D7A4.5090007@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: -4.4 (----) X-LERCTR-Spam-Score: -4.4 (----) X-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8,BAYES_00=-2.599 X-LERCTR-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8,BAYES_00=-2.599 DomainKey-Status: no signature Cc: Darren Reed , freebsd-current@freebsd.org Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 15:32:25 -0000 On Mon, 24 Sep 2007, Scott Long wrote: > Ruslan Ermilov wrote: >> On Mon, Sep 24, 2007 at 08:04:33AM -0500, Larry Rosenman wrote: >>> On Mon, 24 Sep 2007, Kris Kennaway wrote: >>> >>>> Ruslan Ermilov wrote: >>>>> On Sat, Sep 22, 2007 at 11:37:37PM +0200, Kris Kennaway wrote: >>>>>> Darren Reed wrote: >> [...] >>>>>>> Stupid question, perhaps, but is vm.kmem_size/vm.kmem_size_max limited >>>>>>> by physical RAM? >>>>>> Yes. >>>>> To be precise, it's actually limited by 2 * sizeof(physical RAM). >>>>> It's still size of a _virtual_ memory map (kmem_map), after all: >>>>> : /* >>>>> : * Limit kmem virtual size to twice the physical memory. >>>>> : * This allows for kmem map sparseness, but limits the size >>>>> : * to something sane. Be careful to not overflow the 32bit >>>>> : * ints while doing the check. >>>>> : */ >>>>> : if (((vm_kmem_size / 2) / PAGE_SIZE) > cnt.v_page_count) >>>>> : vm_kmem_size = 2 * cnt.v_page_count * PAGE_SIZE; >>>> Well OK, but that seems pretty dangerous, because it leaves open a >>>> pathway to exhaust all of physical memory and presumably panic. >>> is KVA pageable? Is the kmem_map dedicating non-pageable memory? >>> >> kmem_map is used to map memory for the zone allocator, including >> malloc(9). >> >>> I've set my vm.kmem_max to 1G, (on a 4G amd64 box). Is that reasonable? >>> >> It just means that your kernel can "malloc" up to 1G of memory. >> > > You're all missing the point, I hate to say. What happened is that a change > was made recently to more accurately account for allocated > memory. Now people are getting kmem_map_too_small panics that weren't > getting them before. So while the accounting is now more accurate, the > outcome is actually harmful. That needs to be fixed before the release. > How can I help, and what's a proposed patch? LER > Scott > > > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 16:03:40 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FD4216A469; Mon, 24 Sep 2007 16:03:40 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id C1A9513C447; Mon, 24 Sep 2007 16:03:39 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (vader.bytemobile.ondsl.gr [83.235.244.135]) (authenticated bits=128) by igloo.linux.gr (8.14.1/8.14.1/Debian-9) with ESMTP id l8OG36h4022115 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 24 Sep 2007 19:03:22 +0300 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.1/8.14.1) with ESMTP id l8OG2ojY005090; Mon, 24 Sep 2007 19:03:06 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.14.1/8.14.1/Submit) id l8OG2oLT005089; Mon, 24 Sep 2007 19:02:50 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Mon, 24 Sep 2007 19:02:50 +0300 From: Giorgos Keramidas To: Ruslan Ermilov Message-ID: <20070924160249.GA4936@kobe.laptop> References: <46F6379B.9050000@freebsd.org> <46F64A4B.8000804@freebsd.org> <20070924145007.GB82735@team.vega.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070924145007.GB82735@team.vega.ru> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.968, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.43, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: Darren Reed , FreeBSD Current Subject: Re: yacc bug in reader.c:end_rule() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 16:03:40 -0000 On 2007-09-24 18:50, Ruslan Ermilov wrote: > On Sun, Sep 23, 2007 at 04:13:15AM -0700, Darren Reed wrote: > > Darren Reed wrote: > >> There's a fairly obvious bug in yacc's reader.c but I'm not sure > >> what the right fix is. > >> > >> Witness: > >> end_rule() > >> { > >> int i; > >> > >> if (!last_was_action && plhs[nrules]->tag) > >> { > >> for (i = nitems - 1; pitem[i]; --i) continue; > >> if (pitem[i + 1] == 0 || pitem[i+1]->tag != plhs[nrules]->tag) > >> ... > >> } > >> > >> ...clearly if pitem[nitems-1] == NULL (and nitems is the size of the > >> array from [0,nitems-1]) then the if() will access beyond the bounds > >> of the array. > >> > >> There's also the question of i being able to run below 0 too here. > > Not possible: first four pitem's are explicitly set to NULL in > reader.c:initialize_grammar(). > > >> I don't know if the bug is here or if the bug is elsewhere in yacc, > >> but I doubt that the "fix" is s/i + 1/i/. *Maybe* "i = nitems - 2;"? > >> > >> The bug can be masked by using calloc instead of malloc and similar > >> other tricks, but there is something more fundamentaly wrong here. > >> > >> Has anyone else run into this? > > > > The following sample grammar will exercise the bug: > > > > %{ > > %} > > > > %union { > > char *ptr; > > }; > > > > %type test > > %% > > > > test: | $$ = malloc(2); > > It crashes even when written "correctly" as: > > test: | { $$ = malloc(2); } > > > ; > > > > %% > > > > (The error here is that "test" has an undefined return.) > > > Try this patch. It replaces a non-sense with a fix for the bug. > > %%% > Index: reader.c > =================================================================== > RCS file: /home/ncvs/src/usr.bin/yacc/reader.c,v > retrieving revision 1.19 > diff -u -p -r1.19 reader.c > --- reader.c 25 Aug 2002 13:23:09 -0000 1.19 > +++ reader.c 24 Sep 2007 14:16:18 -0000 > @@ -1257,7 +1257,7 @@ end_rule() > if (!last_was_action && plhs[nrules]->tag) > { > for (i = nitems - 1; pitem[i]; --i) continue; > - if (pitem[i+1] == 0 || pitem[i+1]->tag != plhs[nrules]->tag) > + if (i == nitems - 1 || pitem[i+1]->tag != plhs[nrules]->tag) > default_action_warning(); > } > > %%% FWIW, I just verified that the fix works fine, using the same test as yesterday: keramida@kobe:/home/keramida/tmp/yt$ make Warning: Object directory not changed from original /home/keramida/tmp/yt yacc -d -o foo.c foo.y yacc: w - line 11 of "foo.y", the default action assigns an undefined value to $$ yacc: w - the symbol $$ is undefined [...] From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 16:13:25 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5990016A41B; Mon, 24 Sep 2007 16:13:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id EF58813C4B0; Mon, 24 Sep 2007 16:13:24 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8p) with ESMTP id 211141663-1834499 for multiple; Mon, 24 Sep 2007 12:11:58 -0400 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l8OGD3hK098542; Mon, 24 Sep 2007 12:13:14 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Jung-uk Kim" Date: Mon, 24 Sep 2007 11:55:56 -0400 User-Agent: KMail/1.9.6 References: <200709181516.11207.jkim@FreeBSD.org> <200709211827.29763.jkim@FreeBSD.org> <3bbf2fe10709240237u790de351wddb81b0c511d7435@mail.gmail.com> In-Reply-To: <3bbf2fe10709240237u790de351wddb81b0c511d7435@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709241155.56926.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Mon, 24 Sep 2007 12:13:14 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/4378/Mon Sep 24 08:25:35 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: [PATCH] OsdSynch.c modernization X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 16:13:25 -0000 2007/9/22, Jung-uk Kim : > I thought exactly the same when I started rewriting it (almost half > year ago!). I have tried all of the above, spent numerous sleepless > nights, and miserably failed. :-( > > Spin mutex is too restrictive (e.g., it cannot be used with other > locks gracefully). critical_enter() causes: > > panic: blockable sleep lock (sleep mutex) 32 @ > /usr/src/sys/vm/uma_core.c:1830 cpuid = 0 > KDB: enter: panic > [thread pid 21 tid 100013 ] > Stopped at kdb_enter+0x32: leave However, disabling interrupts while you block on other locks is just as bad, we just don't assert for it. Better would be to fix ACPI-CA to not try to malloc() while holding a spin lock. You should be able to see where it is doing that via the stack trace. If the malloc is using M_NOWAIT you will be far better off using a plain mutex and just not disabling interrupts. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 16:28:56 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03DD616A41A; Mon, 24 Sep 2007 16:28:56 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id 9CE6013C494; Mon, 24 Sep 2007 16:28:55 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8p) with ESMTP id 211143967-1834499 for multiple; Mon, 24 Sep 2007 12:27:16 -0400 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l8OGSY3q098743; Mon, 24 Sep 2007 12:28:36 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Nate Lawson Date: Mon, 24 Sep 2007 12:28:33 -0400 User-Agent: KMail/1.9.6 References: <200709181516.11207.jkim@FreeBSD.org> <200709241155.56926.jhb@freebsd.org> <46F7E19B.3010603@root.org> In-Reply-To: <46F7E19B.3010603@root.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709241228.34162.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Mon, 24 Sep 2007 12:28:36 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/4378/Mon Sep 24 08:25:35 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org, Jung-uk Kim Subject: Re: [PATCH] OsdSynch.c modernization X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 16:28:56 -0000 On Monday 24 September 2007 12:11:07 pm Nate Lawson wrote: > John Baldwin wrote: > > 2007/9/22, Jung-uk Kim : > >> I thought exactly the same when I started rewriting it (almost half > >> year ago!). I have tried all of the above, spent numerous sleepless > >> nights, and miserably failed. :-( > >> > >> Spin mutex is too restrictive (e.g., it cannot be used with other > >> locks gracefully). critical_enter() causes: > >> > >> panic: blockable sleep lock (sleep mutex) 32 @ > >> /usr/src/sys/vm/uma_core.c:1830 cpuid = 0 > >> KDB: enter: panic > >> [thread pid 21 tid 100013 ] > >> Stopped at kdb_enter+0x32: leave > > > > However, disabling interrupts while you block on other locks is just as bad, > > we just don't assert for it. Better would be to fix ACPI-CA to not try to > > malloc() while holding a spin lock. You should be able to see where it is > > doing that via the stack trace. If the malloc is using M_NOWAIT you will be > > far better off using a plain mutex and just not disabling interrupts. > > For 7.0, we're going with what we have (sx locks) since it's well-tested > and not wrong, maybe just less than optimal. Remember that acpi locks > are acquired a few dozen times every 10 seconds or so, so this is not at > risk of being a performance issue. Disabling interrupts and then calling malloc() is wrong however. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 16:36:59 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3A2816A41A; Mon, 24 Sep 2007 16:36:58 +0000 (UTC) (envelope-from ulrich@pukruppa.net) Received: from pukruppa.net (pukruppa.net [213.146.114.24]) by mx1.freebsd.org (Postfix) with ESMTP id 7E8A113C459; Mon, 24 Sep 2007 16:36:58 +0000 (UTC) (envelope-from ulrich@pukruppa.net) Received: from pukruppa.net (localhost [127.0.0.1]) by pukruppa.net (8.14.1/8.14.1) with ESMTP id l8OGarWj001634; Mon, 24 Sep 2007 18:36:53 +0200 (CEST) (envelope-from ulrich@pukruppa.net) Received: from localhost (ulrich@localhost) by pukruppa.net (8.14.1/8.14.1/Submit) with ESMTP id l8OGarRv001631; Mon, 24 Sep 2007 18:36:53 +0200 (CEST) (envelope-from ulrich@pukruppa.net) Date: Mon, 24 Sep 2007 18:36:53 +0200 (CEST) From: "P.U.Kruppa" X-X-Sender: ulrich@small To: Remko Lodder In-Reply-To: <20070924100607.GC1462@elvandar.org> Message-ID: <20070924183258.J1576@small> References: <20070924051118.H9923@small> <46F785BB.9030800@FreeBSD.org> <20070924114923.C10251@small> <20070924100607.GC1462@elvandar.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 16:36:59 -0000 On Mon, 24 Sep 2007, Remko Lodder wrote: > On Mon, Sep 24, 2007 at 11:50:37AM +0200, P.U.Kruppa wrote: >> On Mon, 24 Sep 2007, Kris Kennaway wrote: >> >>> P.U.Kruppa wrote: >>>> Hello, >>>> I use a HP Deskjet 990 Cxi via parallel port with cups and hpijs driver on >>>> FreeBSD pukruppa.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Sep 21 >>>> 16:52:59 CEST 2007 amd64 >>>> When I try to print a little bit more complex documents (OpenOffice, pdf) >>>> my System will crash. >>>> On my root terminal there will be a long list of >>>> lpt0: [ITHREAD] >>>> lpt0: [GIANT-LOCKED] >>>> lpt0: [ITHREAD] >>>> [...] >>>> lines, then some dumping activity and a reboot. >>>> I upgraded to 7.0 last week, so all I can say is: everything was fine with >>>> 6.2 . >>>> Please tell me if you need more information. >>> >>> Well yeah, how about e.g. the actual details from the panic? >> How do I get them? >> Do I have to recompile my kernel (I put off debugging and Witness Options)? > > Hello, > > Check http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html for > more information. > > Thanks > > -- > Kind regards, > > Remko Lodder ** remko@elvandar.org Sorry, from developer's handbook I guess I should find a vmcore.N file. There isn't any. My parallel printing attempts end up in some kind of single user mode on the root terminal with a db> prompt. Can I do anything with that? Uli. Peter Ulrich Kruppa Wuppertal Germany From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 16:44:47 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2C6416A419 for ; Mon, 24 Sep 2007 16:44:47 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id D89B513C45D for ; Mon, 24 Sep 2007 16:44:47 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 99086 invoked from network); 24 Sep 2007 16:18:07 -0000 Received: from ppp-71-139-1-224.dsl.snfc21.pacbell.net (HELO ?10.0.0.15?) (nate-mail@71.139.1.224) by root.org with ESMTPA; 24 Sep 2007 16:18:07 -0000 Message-ID: <46F7E19B.3010603@root.org> Date: Mon, 24 Sep 2007 09:11:07 -0700 From: Nate Lawson User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: John Baldwin References: <200709181516.11207.jkim@FreeBSD.org> <200709211827.29763.jkim@FreeBSD.org> <3bbf2fe10709240237u790de351wddb81b0c511d7435@mail.gmail.com> <200709241155.56926.jhb@freebsd.org> In-Reply-To: <200709241155.56926.jhb@freebsd.org> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org, Jung-uk Kim Subject: Re: [PATCH] OsdSynch.c modernization X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 16:44:48 -0000 John Baldwin wrote: > 2007/9/22, Jung-uk Kim : >> I thought exactly the same when I started rewriting it (almost half >> year ago!). I have tried all of the above, spent numerous sleepless >> nights, and miserably failed. :-( >> >> Spin mutex is too restrictive (e.g., it cannot be used with other >> locks gracefully). critical_enter() causes: >> >> panic: blockable sleep lock (sleep mutex) 32 @ >> /usr/src/sys/vm/uma_core.c:1830 cpuid = 0 >> KDB: enter: panic >> [thread pid 21 tid 100013 ] >> Stopped at kdb_enter+0x32: leave > > However, disabling interrupts while you block on other locks is just as bad, > we just don't assert for it. Better would be to fix ACPI-CA to not try to > malloc() while holding a spin lock. You should be able to see where it is > doing that via the stack trace. If the malloc is using M_NOWAIT you will be > far better off using a plain mutex and just not disabling interrupts. For 7.0, we're going with what we have (sx locks) since it's well-tested and not wrong, maybe just less than optimal. Remember that acpi locks are acquired a few dozen times every 10 seconds or so, so this is not at risk of being a performance issue. I think it's a good idea to work with Bob Moore to improve things on their side as well. Then we can revisit this and clean it up. -- Nate From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 16:52:45 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B2EE316A419 for ; Mon, 24 Sep 2007 16:52:45 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id AE3FC13C465 for ; Mon, 24 Sep 2007 16:52:45 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 2398 invoked from network); 24 Sep 2007 16:52:46 -0000 Received: from ppp-71-139-1-224.dsl.snfc21.pacbell.net (HELO ?10.0.0.15?) (nate-mail@71.139.1.224) by root.org with ESMTPA; 24 Sep 2007 16:52:46 -0000 Message-ID: <46F7E9BA.3090601@root.org> Date: Mon, 24 Sep 2007 09:45:46 -0700 From: Nate Lawson User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: John Baldwin References: <200709181516.11207.jkim@FreeBSD.org> <200709241155.56926.jhb@freebsd.org> <46F7E19B.3010603@root.org> <200709241228.34162.jhb@freebsd.org> In-Reply-To: <200709241228.34162.jhb@freebsd.org> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org, Jung-uk Kim Subject: Re: [PATCH] OsdSynch.c modernization X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 16:52:45 -0000 John Baldwin wrote: > On Monday 24 September 2007 12:11:07 pm Nate Lawson wrote: >> John Baldwin wrote: >>> 2007/9/22, Jung-uk Kim : >>>> I thought exactly the same when I started rewriting it (almost half >>>> year ago!). I have tried all of the above, spent numerous sleepless >>>> nights, and miserably failed. :-( >>>> >>>> Spin mutex is too restrictive (e.g., it cannot be used with other >>>> locks gracefully). critical_enter() causes: >>>> >>>> panic: blockable sleep lock (sleep mutex) 32 @ >>>> /usr/src/sys/vm/uma_core.c:1830 cpuid = 0 >>>> KDB: enter: panic >>>> [thread pid 21 tid 100013 ] >>>> Stopped at kdb_enter+0x32: leave >>> However, disabling interrupts while you block on other locks is just as > bad, >>> we just don't assert for it. Better would be to fix ACPI-CA to not try to >>> malloc() while holding a spin lock. You should be able to see where it is >>> doing that via the stack trace. If the malloc is using M_NOWAIT you will > be >>> far better off using a plain mutex and just not disabling interrupts. >> >> For 7.0, we're going with what we have (sx locks) since it's well-tested >> and not wrong, maybe just less than optimal. Remember that acpi locks >> are acquired a few dozen times every 10 seconds or so, so this is not at >> risk of being a performance issue. > > Disabling interrupts and then calling malloc() is wrong however. Sure, I guess I thought that part would just be removed and we'd deal with a pure sx lock. Jung-uk, what was the need for critical_enter/intr_disable? The only thing I can think of is that you might want to prevent a thread from migrating while the "spin" lock is held. I don't see that as necessary. I agree that this part should be removed, but I think we should stick with sx locks for now and not re-work acpi-ca (vendor code) so close to a release unless it's something very simple. -- Nate From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 16:59:05 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1AB3716A419; Mon, 24 Sep 2007 16:59:05 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.freebsd.org (Postfix) with ESMTP id B97FA13C45D; Mon, 24 Sep 2007 16:59:04 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.6/8.13.6) with ESMTP id l8OGx2I8001148; Mon, 24 Sep 2007 12:59:03 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-acpi@FreeBSD.org Date: Mon, 24 Sep 2007 12:58:54 -0400 User-Agent: KMail/1.6.2 References: <200709181516.11207.jkim@FreeBSD.org> <46F7E19B.3010603@root.org> <200709241228.34162.jhb@freebsd.org> In-Reply-To: <200709241228.34162.jhb@freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200709241259.01518.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.90.2/4378/Mon Sep 24 08:25:35 2007 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-current@FreeBSD.org, John Baldwin , Nate Lawson Subject: Re: [PATCH] OsdSynch.c modernization X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 16:59:05 -0000 On Monday 24 September 2007 12:28 pm, John Baldwin wrote: > On Monday 24 September 2007 12:11:07 pm Nate Lawson wrote: > > John Baldwin wrote: > > > 2007/9/22, Jung-uk Kim : > > >> I thought exactly the same when I started rewriting it (almost > > >> half year ago!). I have tried all of the above, spent > > >> numerous sleepless nights, and miserably failed. :-( > > >> > > >> Spin mutex is too restrictive (e.g., it cannot be used with > > >> other locks gracefully). critical_enter() causes: > > >> > > >> panic: blockable sleep lock (sleep mutex) 32 @ > > >> /usr/src/sys/vm/uma_core.c:1830 cpuid = 0 > > >> KDB: enter: panic > > >> [thread pid 21 tid 100013 ] > > >> Stopped at kdb_enter+0x32: leave > > > > > > However, disabling interrupts while you block on other locks is > > > just as > > bad, > > > > we just don't assert for it. Better would be to fix ACPI-CA to > > > not try to malloc() while holding a spin lock. You should be > > > able to see where it is doing that via the stack trace. If the > > > malloc is using M_NOWAIT you will > > be > > > > far better off using a plain mutex and just not disabling > > > interrupts. > > > > For 7.0, we're going with what we have (sx locks) since it's > > well-tested and not wrong, maybe just less than optimal. > > Remember that acpi locks are acquired a few dozen times every 10 > > seconds or so, so this is not at risk of being a performance > > issue. > > Disabling interrupts and then calling malloc() is wrong however. Understood. As I said earlier, I really like to fix it correctly. However, the problem is that there are so many different BIOSes out there, taking so different code paths. Whenever I thought it's fixed, someone says 'you broke my laptop' or 'FreeBSD is bad because it doesn't boot on my laptop but Linux and Windows boot fine'. :-( (At least on my laptop) I found the malloc() was called from our code, i.e., AcpiOsExecute() from OsdSched.c. I'll try something shortly cause I was going to rewrite the file anyway. Thanks, Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 17:10:18 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9843816A420 for ; Mon, 24 Sep 2007 17:10:18 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id 965AE13C480 for ; Mon, 24 Sep 2007 17:10:18 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 3350 invoked from network); 24 Sep 2007 17:10:18 -0000 Received: from ppp-71-139-1-224.dsl.snfc21.pacbell.net (HELO ?10.0.0.15?) (nate-mail@71.139.1.224) by root.org with ESMTPA; 24 Sep 2007 17:10:18 -0000 Message-ID: <46F7EDD6.4010508@root.org> Date: Mon, 24 Sep 2007 10:03:18 -0700 From: Nate Lawson User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Jung-uk Kim References: <200709181516.11207.jkim@FreeBSD.org> <46F7E19B.3010603@root.org> <200709241228.34162.jhb@freebsd.org> <200709241259.01518.jkim@FreeBSD.org> In-Reply-To: <200709241259.01518.jkim@FreeBSD.org> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org, freebsd-current@FreeBSD.org, John Baldwin Subject: Re: [PATCH] OsdSynch.c modernization X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 17:10:18 -0000 Jung-uk Kim wrote: > On Monday 24 September 2007 12:28 pm, John Baldwin wrote: >> On Monday 24 September 2007 12:11:07 pm Nate Lawson wrote: >>> John Baldwin wrote: >>>> 2007/9/22, Jung-uk Kim : >>>>> I thought exactly the same when I started rewriting it (almost >>>>> half year ago!). I have tried all of the above, spent >>>>> numerous sleepless nights, and miserably failed. :-( >>>>> >>>>> Spin mutex is too restrictive (e.g., it cannot be used with >>>>> other locks gracefully). critical_enter() causes: >>>>> >>>>> panic: blockable sleep lock (sleep mutex) 32 @ >>>>> /usr/src/sys/vm/uma_core.c:1830 cpuid = 0 >>>>> KDB: enter: panic >>>>> [thread pid 21 tid 100013 ] >>>>> Stopped at kdb_enter+0x32: leave >>>> However, disabling interrupts while you block on other locks is >>>> just as >> bad, >> >>>> we just don't assert for it. Better would be to fix ACPI-CA to >>>> not try to malloc() while holding a spin lock. You should be >>>> able to see where it is doing that via the stack trace. If the >>>> malloc is using M_NOWAIT you will >> be >> >>>> far better off using a plain mutex and just not disabling >>>> interrupts. >>> For 7.0, we're going with what we have (sx locks) since it's >>> well-tested and not wrong, maybe just less than optimal. >>> Remember that acpi locks are acquired a few dozen times every 10 >>> seconds or so, so this is not at risk of being a performance >>> issue. >> Disabling interrupts and then calling malloc() is wrong however. > > Understood. As I said earlier, I really like to fix it correctly. > > > However, the problem is that there are so many different BIOSes out > there, taking so different code paths. Whenever I thought it's > fixed, someone says 'you broke my laptop' or 'FreeBSD is bad because > it doesn't boot on my laptop but Linux and Windows boot fine'. :-( > > > (At least on my laptop) I found the malloc() was called from our code, > i.e., AcpiOsExecute() from OsdSched.c. I'll try something shortly > cause I was going to rewrite the file anyway. Yep, that's because we need a task structure that's different for each call and acpi-ca doesn't like the "pending" argument (see OsdSchedule.c). One fix for this is to just use a hack and cast the fn to discard the extra arg. Not sure this would work. I thought malloc(...NOWAIT) *could* be called with a mutex held? It just checks a list and returns NULL if empty, right? -- Nate From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 17:10:19 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1934916A417 for ; Mon, 24 Sep 2007 17:10:19 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.freebsd.org (Postfix) with ESMTP id BD14813C478 for ; Mon, 24 Sep 2007 17:10:18 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1226031nfb for ; Mon, 24 Sep 2007 10:10:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; bh=SFhAC6xGNN4QRKJ7iq3TmJzQZ4yhjXfqZ4MzeGaJfg4=; b=NUucM3S7B38otJeOqZzEBz0rR2vYjGL4f3A8MbYexTcnAbyUx27Q8i3VlXVZvuk/ORqL9Mn3h3muKsEgHP6QbKxufcpwczKBPqToXxKls9zOy1ef9BkDIbvOXR+LiMFRlbhd4E/lWtotUZc1VSB0Q5TuCrl07HvseHiJPCaxBNE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; b=dEGirxuQSPr4AcXhldC7aQL4MDe1eNx90RCviXUD6u89YAJIdfPhpNlEr4QhJlwpkgMbIA1sjCHpvH+gpXqxs/DBlE18zwkQ+En+EITsvQsFT0lwVC4fX6pR1cHd29lHtz6DoVGqabHDaUzloSM5k3NA6QfEcQoxREhTZjR/EdM= Received: by 10.78.157.19 with SMTP id f19mr3733095hue.1190653816466; Mon, 24 Sep 2007 10:10:16 -0700 (PDT) Received: from orion ( [77.109.34.178]) by mx.google.com with ESMTPS id s34sm1514156hub.2007.09.24.10.10.11 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 24 Sep 2007 10:10:15 -0700 (PDT) From: Nikolay Pavlov To: freebsd-current@freebsd.org Date: Mon, 24 Sep 2007 20:09:59 +0300 User-Agent: KMail/1.9.7 References: <20070924051118.H9923@small> <20070924100607.GC1462@elvandar.org> <20070924183258.J1576@small> In-Reply-To: <20070924183258.J1576@small> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3131174.8QhCsSs208"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200709242010.05222.qpadla@gmail.com> Cc: "P.U.Kruppa" , Remko Lodder Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: qpadla@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 17:10:19 -0000 --nextPart3131174.8QhCsSs208 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 24 September 2007 19:36:53 P.U.Kruppa wrote: > On Mon, 24 Sep 2007, Remko Lodder wrote: > > On Mon, Sep 24, 2007 at 11:50:37AM +0200, P.U.Kruppa wrote: > >> On Mon, 24 Sep 2007, Kris Kennaway wrote: > >>> P.U.Kruppa wrote: > >>>> Hello, > >>>> I use a HP Deskjet 990 Cxi via parallel port with cups and hpijs > >>>> driver on FreeBSD pukruppa.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: > >>>> Fri Sep 21 16:52:59 CEST 2007 amd64 > >>>> When I try to print a little bit more complex documents > >>>> (OpenOffice, pdf) my System will crash. > >>>> On my root terminal there will be a long list of > >>>> lpt0: [ITHREAD] > >>>> lpt0: [GIANT-LOCKED] > >>>> lpt0: [ITHREAD] > >>>> [...] > >>>> lines, then some dumping activity and a reboot. > >>>> I upgraded to 7.0 last week, so all I can say is: everything was > >>>> fine with 6.2 . > >>>> Please tell me if you need more information. > >>> > >>> Well yeah, how about e.g. the actual details from the panic? > >> > >> How do I get them? > >> Do I have to recompile my kernel (I put off debugging and Witness > >> Options)? > > > > Hello, > > > > Check > > http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.ht > >ml for more information. > > > > Thanks > > > > -- > > Kind regards, > > > > Remko Lodder ** remko@elvandar.org > > Sorry, from developer's handbook I guess I should find a vmcore.N > file. There isn't any. My parallel printing attempts end up in > some kind of single user mode on the root terminal with a > db> > prompt. Can I do anything with that? You'll find it in /var/crash/ directory right after the panic Then go to cd /usr/obj/usr/src/sys/KERNCONF where KERNCONF is your kernel configuration name (should be GENERIC for=20 GENERIC kernel) Then execute: kgdb kernel.debug /var/crash/vmcore.0 And you'll get the debugger prompt. You can find more info here: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html =2D-=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 =2D Best regards, Nikolay Pavlov. <<<----------------------------------- = =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 --nextPart3131174.8QhCsSs208 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBG9+9t/2R6KvEYGaIRAr6AAKCtSfLirL4qsL7IifcVFqJ67DBXnQCgpTJZ A9rLmNfpWjrYAxpGLlzrXCs= =IXoL -----END PGP SIGNATURE----- --nextPart3131174.8QhCsSs208-- From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 17:16:14 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A647516A419; Mon, 24 Sep 2007 17:16:14 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id 6830113C465; Mon, 24 Sep 2007 17:16:14 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8p) with ESMTP id 211151065-1834499 for multiple; Mon, 24 Sep 2007 13:14:35 -0400 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l8OHFsUL099059; Mon, 24 Sep 2007 13:15:54 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Nate Lawson Date: Mon, 24 Sep 2007 13:15:52 -0400 User-Agent: KMail/1.9.6 References: <200709181516.11207.jkim@FreeBSD.org> <200709241259.01518.jkim@FreeBSD.org> <46F7EDD6.4010508@root.org> In-Reply-To: <46F7EDD6.4010508@root.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709241315.53665.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Mon, 24 Sep 2007 13:15:54 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/4378/Mon Sep 24 08:25:35 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org, Jung-uk Kim Subject: Re: [PATCH] OsdSynch.c modernization X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 17:16:14 -0000 On Monday 24 September 2007 01:03:18 pm Nate Lawson wrote: > Jung-uk Kim wrote: > > On Monday 24 September 2007 12:28 pm, John Baldwin wrote: > >> On Monday 24 September 2007 12:11:07 pm Nate Lawson wrote: > >>> John Baldwin wrote: > >>>> 2007/9/22, Jung-uk Kim : > >>>>> I thought exactly the same when I started rewriting it (almost > >>>>> half year ago!). I have tried all of the above, spent > >>>>> numerous sleepless nights, and miserably failed. :-( > >>>>> > >>>>> Spin mutex is too restrictive (e.g., it cannot be used with > >>>>> other locks gracefully). critical_enter() causes: > >>>>> > >>>>> panic: blockable sleep lock (sleep mutex) 32 @ > >>>>> /usr/src/sys/vm/uma_core.c:1830 cpuid = 0 > >>>>> KDB: enter: panic > >>>>> [thread pid 21 tid 100013 ] > >>>>> Stopped at kdb_enter+0x32: leave > >>>> However, disabling interrupts while you block on other locks is > >>>> just as > >> bad, > >> > >>>> we just don't assert for it. Better would be to fix ACPI-CA to > >>>> not try to malloc() while holding a spin lock. You should be > >>>> able to see where it is doing that via the stack trace. If the > >>>> malloc is using M_NOWAIT you will > >> be > >> > >>>> far better off using a plain mutex and just not disabling > >>>> interrupts. > >>> For 7.0, we're going with what we have (sx locks) since it's > >>> well-tested and not wrong, maybe just less than optimal. > >>> Remember that acpi locks are acquired a few dozen times every 10 > >>> seconds or so, so this is not at risk of being a performance > >>> issue. > >> Disabling interrupts and then calling malloc() is wrong however. > > > > Understood. As I said earlier, I really like to fix it correctly. > > > > > > However, the problem is that there are so many different BIOSes out > > there, taking so different code paths. Whenever I thought it's > > fixed, someone says 'you broke my laptop' or 'FreeBSD is bad because > > it doesn't boot on my laptop but Linux and Windows boot fine'. :-( > > > > > > (At least on my laptop) I found the malloc() was called from our code, > > i.e., AcpiOsExecute() from OsdSched.c. I'll try something shortly > > cause I was going to rewrite the file anyway. > > Yep, that's because we need a task structure that's different for each > call and acpi-ca doesn't like the "pending" argument (see > OsdSchedule.c). One fix for this is to just use a hack and cast the fn > to discard the extra arg. Not sure this would work. > > I thought malloc(...NOWAIT) *could* be called with a mutex held? It > just checks a list and returns NULL if empty, right? But not a spin mutex.... -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 17:28:02 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3A6B16A418 for ; Mon, 24 Sep 2007 17:28:02 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.freebsd.org (Postfix) with ESMTP id 7180113C459 for ; Mon, 24 Sep 2007 17:28:02 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1230114nfb for ; Mon, 24 Sep 2007 10:28:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=rsLr4qpMF9BYwrS8aFA2s8fFxMOpQA3hEitfOjdyysw=; b=cTU5BvXEUDR2lfAM7iLIJXF7v1ctsG7ymFFCmOnyvsKFp+/D1i4z11G1dBmxW4lWE5SbtafSb1NehVhrcqARgj5kZNt2Upoi/Es+rXnY2sxR0tTXY84v2O8wulEI0qmWchwXbrwsPrmA9q08uOl+qpxiLy2PX9iv5u7nRlfEJ/o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qXeYMVcHrOqnwWYi7eCQ2xRb09s0e+tOgIClVdNQSD35SZdNgezUp/XHvyWV5f5s6Y6B/wo547meBuJap+yON1TM4eGGUd7fS66viwQUiprFPWjWPvcgvYYZWaXFTS9DNIqBRRtYmhBSH3n+iG7zfIg+gw0GMu14Vy4U4HyLNi4= Received: by 10.86.80.5 with SMTP id d5mr4877997fgb.1190654881016; Mon, 24 Sep 2007 10:28:01 -0700 (PDT) Received: by 10.86.100.19 with HTTP; Mon, 24 Sep 2007 10:28:00 -0700 (PDT) Message-ID: <2a41acea0709241028q2503f12fp86eea2d32ac10aa7@mail.gmail.com> Date: Mon, 24 Sep 2007 10:28:00 -0700 From: "Jack Vogel" To: "Kip Macy" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0709221656n4aa62776y488c7f2da262c9f6@mail.gmail.com> <46F614F2.4050402@freebsd.org> Cc: Darren Reed , "freebsd-net@freebsd.org" , FreeBSD Current Subject: Re: TX Multiqueue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 17:28:02 -0000 On 9/23/07, Kip Macy wrote: > On 9/23/07, Darren Reed wrote: > > Kip Macy wrote: > > > My ethng branch supports multiple rx and tx queues. > > > > > > -Kip > > > > > > > What are your plans for how we use/manage/interact with the mutiple > > rx/tx queues? > > The rx hardware queue is determined by the hardware. Different > hardware allows for different policies. I just use the stock rss_hash > of a crc32 of the 4-tuple in cxgb. I've added a field to the pkthdr > which cxgb uses the least significant bits of to determine which > outbound queue to use. Its up to the upper layers to determine how to > set those bits. One of the changes that is required to take advantaged > of this is moving the queues into the driver. I've added a new > if_start function to ifnet to take advantage of this. I also have a > normal if_start function for backward compatibility. Yes, the queues in Oplin and Zoar are also a hardware feature, not just some software infrastructure. There are a number of different ways that it can be configured. I did not have some settled notion of how things should be managed but I would rather not have it be something done under the covers in the driver, a configurable stack option seems better to me. This needs to be done right or it will just be a hack, I don't know who the right parties are, it should not be just a one-person decision, those with a stake in this sort of thing should all be involved. Cheers, Jack From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 17:35:54 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64B3816A417; Mon, 24 Sep 2007 17:35:54 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from pobox.codelabs.ru (pobox.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id 2527E13C45B; Mon, 24 Sep 2007 17:35:53 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:To:From:Reply-To:Cc:X-send-pr-version:X-GNATS-Notify:Message-Id:Date:X-Spam-Status:Subject; b=CDsDVhDgpWAxRGvDp44RzOiGUWPT/PDGkLBi9E9B/fMJs8rq1H+XkXUua352noBI9LbCxb962Yb6yFK9VWLPqR6ix5ofylGWwWoGikluaw+RbASfahwlv6gxaEAt3DY8X20pmt8KjPldmoeWm5uOGh+ZlG5hDzq2XrH2oFj5hQ8=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by pobox.codelabs.ru with esmtps (TLSv1:CAMELLIA256-SHA:256) id 1IZrqZ-000GUH-Ra; Mon, 24 Sep 2007 21:35:52 +0400 To: FreeBSD-gnats-submit@freebsd.org From: Eygene Ryabinkin X-send-pr-version: 3.113 X-GNATS-Notify: Message-Id: <20070924173551.4D5E71AF41C@void.codelabs.ru> Date: Mon, 24 Sep 2007 21:35:51 +0400 (MSD) X-Spam-Status: No, score=-2.2 required=4.0 tests=AWL,BAYES_00 Cc: max@love2party.net, freebsd-current@freebsd.org Subject: [patch] teach tcpdump(1) to cope with the new-style pflog(4) output X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Eygene Ryabinkin List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 17:35:54 -0000 >Submitter-Id: current-users >Originator: Eygene Ryabinkin >Organization: Code Labs >Confidential: no >Synopsis: [patch] teach tcpdump(1) to cope with the new-style pflog(4) output >Severity: serious >Priority: medium >Category: bin >Class: sw-bug >Release: FreeBSD 7.0-CURRENT i386 >Environment: System: FreeBSD XXX 7.0-CURRENT FreeBSD 7.0-CURRENT #10: Wed Sep 12 16:16:49 MSD 2007 root@XXX:/usr/src/sys/i386/compile/XXX i386 >Description: Version 1.9 of /sys/contrib/pf/net/if_pflog.h (Import of pf from OpenBSD 4.1) introduced the backwards-incompatible change to the 'struct pfloghdr': the 'dir' and 'pad' members moved far away from their previous positions. This is not a problem for the pf itself, but tcpdump is no longer able to print the packet direction correctly. >How-To-Repeat: Spawn tcpdump like 'tcpdump -lvvnetti pflog0' on the 7-CURRENT built from the sources later than Tue Jul 3 16:16:07 2007 MSD and see that the link-level header contains weird 'unkn(255)' direction: "rule 14/0(match): block unkn(255) on uplink". >Fix: The following patch will cure the situation. I know that the best thing that can be done is to commit it to the tcpdump itself, but a) this is a long process, since it requires tcpdump team to accept the patch and Someone (TM) to import new tcpdump sources to FreeBSD; b) other eyes should see and criticize this patch. I myself was tested this patch on the 7-CURRENT and 6.2-STABLE. No regressions were seen yet and tcpdump works like a charm with the new pflog0 packets showing 'in' and 'out' ;)) --- tcpdump-pflog-v2.patch begins here --- --- contrib/tcpdump/pf.h.orig 2007-09-24 19:59:29.000000000 +0400 +++ contrib/tcpdump/pf.h 2007-09-24 20:31:40.000000000 +0400 @@ -29,6 +29,9 @@ * @(#) $Header: /tcpdump/master/tcpdump/pf.h,v 1.2 2004/04/02 06:36:25 guy Exp $ (LBL) */ +/* We need offsetof() macro */ +#include + /* from $OpenBSD: pfvar.h,v 1.170 2003/08/22 21:50:34 david Exp $ */ enum { PF_INOUT=0, PF_IN=1, PF_OUT=2 }; @@ -75,3 +78,23 @@ u_int8_t pad[3]; }; #define PFLOG_HDRLEN sizeof(struct pfloghdr) + +/* from $OpenBSD: if_pflog.h,v 1.14 2006/10/25 11:27:01 henning Exp $ */ + +struct pfloghdr_v2 { + u_int8_t length; + sa_family_t af; + u_int8_t action; + u_int8_t reason; + char ifname[IFNAMSIZ]; + char ruleset[PF_RULESET_NAME_SIZE]; + u_int32_t rulenr; + u_int32_t subrulenr; + uid_t uid; + pid_t pid; + uid_t rule_uid; + pid_t rule_pid; + u_int8_t dir; + u_int8_t pad[3]; +}; +#define PFLOG_HDRV2_LEN offsetof(struct pfloghdr_v2, pad) --- contrib/tcpdump/print-pflog.c.orig 2007-09-24 19:10:09.000000000 +0400 +++ contrib/tcpdump/print-pflog.c 2007-09-24 20:30:36.000000000 +0400 @@ -72,25 +72,43 @@ #define OPENBSD_AF_INET 2 #define OPENBSD_AF_INET6 24 +#define __PFLOG_PRINT_HDR(hdr) \ +do { \ + u_int32_t rulenr, subrulenr; \ + \ + rulenr = ntohl((hdr)->rulenr); \ + subrulenr = ntohl((hdr)->subrulenr); \ + if (subrulenr == (u_int32_t)-1) \ + printf("rule %u/", rulenr); \ + else \ + printf("rule %u.%s.%u/", rulenr, (hdr)->ruleset, \ + subrulenr); \ + \ + printf("%s: %s %s on %s: ", \ + tok2str(pf_reasons, "unkn(%u)", (hdr)->reason), \ + tok2str(pf_actions, "unkn(%u)", (hdr)->action), \ + tok2str(pf_directions, "unkn(%u)", (hdr)->dir), \ + (hdr)->ifname); \ +} while (0) + static void pflog_print(const struct pfloghdr *hdr) { - u_int32_t rulenr, subrulenr; + u_int8_t hdr_version; + struct pfloghdr_v2 *v2hdr; - rulenr = ntohl(hdr->rulenr); - subrulenr = ntohl(hdr->subrulenr); - if (subrulenr == (u_int32_t)-1) - printf("rule %u/", rulenr); - else - printf("rule %u.%s.%u/", rulenr, hdr->ruleset, subrulenr); - - printf("%s: %s %s on %s: ", - tok2str(pf_reasons, "unkn(%u)", hdr->reason), - tok2str(pf_actions, "unkn(%u)", hdr->action), - tok2str(pf_directions, "unkn(%u)", hdr->dir), - hdr->ifname); + if (hdr->length == PFLOG_HDRV2_LEN) { + hdr_version = 2; + v2hdr = (struct pfloghdr_v2 *)hdr; + __PFLOG_PRINT_HDR(v2hdr); + } else { + hdr_version = 1; + __PFLOG_PRINT_HDR(hdr); + } } +#undef __PFLOG_PRINT_HDR + u_int pflog_if_print(const struct pcap_pkthdr *h, register const u_char *p) { --- tcpdump-pflog-v2.patch ends here --- From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 17:56:39 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9F6E16A468 for ; Mon, 24 Sep 2007 17:56:39 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id B7D9413C467 for ; Mon, 24 Sep 2007 17:56:39 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id F2FD42F63C; Mon, 24 Sep 2007 13:56:38 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Mon, 24 Sep 2007 13:56:39 -0400 X-Sasl-enc: Wb+3z063vSSdEVZs/GlXcyolzVl1KN3lU9CaZSlvMuR7 1190656598 Received: from [192.168.1.235] (64-142-85-108.dsl.dynamic.sonic.net [64.142.85.108]) by mail.messagingengine.com (Postfix) with ESMTP id 59D5F249D; Mon, 24 Sep 2007 13:56:38 -0400 (EDT) Message-ID: <46F7FA9A.30109@freebsd.org> Date: Mon, 24 Sep 2007 10:57:46 -0700 From: Darren Reed User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Ruslan Ermilov References: <46F6379B.9050000@freebsd.org> <46F64A4B.8000804@freebsd.org> <20070924145007.GB82735@team.vega.ru> In-Reply-To: <20070924145007.GB82735@team.vega.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: yacc bug in reader.c:end_rule() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 17:56:40 -0000 Ruslan Ermilov wrote: > On Sun, Sep 23, 2007 at 04:13:15AM -0700, Darren Reed wrote: > > Darren Reed wrote: > >> There's a fairly obvious bug in yacc's reader.c but I'm not sure what the > >> right fix is. > >> > >> Witness: > >> end_rule() > >> { > >> int i; > >> > >> if (!last_was_action && plhs[nrules]->tag) > >> { > >> for (i = nitems - 1; pitem[i]; --i) continue; > >> if (pitem[i + 1] == 0 || pitem[i+1]->tag != plhs[nrules]->tag) > >> ... > >> } > >> > >> ...clearly if pitem[nitems-1] == NULL (and nitems is the size of the > >> array from [0,nitems-1]) then the if() will access beyond the bounds > >> of the array. > >> > >> There's also the question of i being able to run below 0 too here. > >> > Not possible: first four pitem's are explicitly set to NULL in > reader.c:initialize_grammar(). > > >> I don't know if the bug is here or if the bug is elsewhere in yacc, > >> but I doubt that the "fix" is s/i + 1/i/. *Maybe* "i = nitems - 2;"? > >> > >> The bug can be masked by using calloc instead of malloc and similar > >> other tricks, but there is something more fundamentaly wrong here. > >> > >> Has anyone else run into this? > > > > The following sample grammar will exercise the bug: > > > > %{ > > %} > > > > %union { > > char *ptr; > > }; > > > > %type test > > %% > > > > test: | $$ = malloc(2); > > It crashes even when written "correctly" as: > > test: | { $$ = malloc(2); } > > > ; > > > > %% > > > > (The error here is that "test" has an undefined return.) > > > Try this patch. It replaces a non-sense with a fix for the bug. > It fixes my problem...but does it introduce any problems for correct grammars? Need to test it with a build world.. Darren From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 17:58:22 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2600E16A41A for ; Mon, 24 Sep 2007 17:58:22 +0000 (UTC) (envelope-from brucec@muon.bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [80.68.94.188]) by mx1.freebsd.org (Postfix) with ESMTP id F375F13C481 for ; Mon, 24 Sep 2007 17:58:21 +0000 (UTC) (envelope-from brucec@muon.bluestop.org) Received: by muon.bluestop.org (Postfix, from userid 1000) id 634BD301F6; Mon, 24 Sep 2007 18:32:21 +0100 (BST) Date: Mon, 24 Sep 2007 18:32:21 +0100 From: bruce@cran.org.uk To: "P.U.Kruppa" Message-ID: <20070924173221.GA18292@muon.bluestop.org> References: <20070924051118.H9923@small> <46F785BB.9030800@FreeBSD.org> <20070924114923.C10251@small> <20070924100607.GC1462@elvandar.org> <20070924183258.J1576@small> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070924183258.J1576@small> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: Remko Lodder , freebsd-current@freebsd.org Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 17:58:22 -0000 On Mon, Sep 24, 2007 at 06:36:53PM +0200, P.U.Kruppa wrote: > Sorry, from developer's handbook I guess I should find a vmcore.N > file. There isn't any. My parallel printing attempts end up in > some kind of single user mode on the root terminal with a > db> > prompt. Can I do anything with that? > That's the DDB prompt: from there you need to either get a backtrace or, more usefully, generate a crash dump. See http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-online-ddb.html for details. To generate a crash dump that you can later use with kgdb, type "panic" at the db> prompt. Then, read http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html to find out how to obtain a backtrace that can help diagnose the fault. If using the "panic" command doesn't generate a crash dump, you could also do some diagnostics at the db> prompt by using commands such as "trace" to get a stack trace, but unless you're connected over serial you won't be able to get a copy of the output so it's better to see if you can generate a crash dump first. -- Bruce From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 18:23:59 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6FFFF16A46D for ; Mon, 24 Sep 2007 18:23:59 +0000 (UTC) (envelope-from sysinstall@gmx.net) Received: from mail.webmailerei.de (mx.webmailerei.de [85.214.64.28]) by mx1.freebsd.org (Postfix) with ESMTP id 29AED13C4C6 for ; Mon, 24 Sep 2007 18:23:59 +0000 (UTC) (envelope-from sysinstall@gmx.net) Received: from localhost (localhost [127.0.0.1]) by mail.webmailerei.de (Postfix) with ESMTP id 5BF641F3E for ; Mon, 24 Sep 2007 19:30:03 +0200 (CEST) X-Virus-Scanned: amavisd-new at franzke-online.eu Received: from mail.webmailerei.de ([127.0.0.1]) by localhost (mail.webmailerei.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id VAuf2fM6VZ2X for ; Mon, 24 Sep 2007 19:30:00 +0200 (CEST) Received: from localhost (dslb-084-062-196-222.pools.arcor-ip.net [84.62.196.222]) by mail.webmailerei.de (Postfix) with ESMTP id E84B62046 for ; Mon, 24 Sep 2007 19:29:59 +0200 (CEST) From: Dieter Franzke To: freebsd-current@freebsd.org Date: Mon, 24 Sep 2007 19:51:28 +0200 User-Agent: KMail/1.9.7 References: <20070924051118.H9923@small> In-Reply-To: <20070924051118.H9923@small> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709241951.28762.sysinstall@gmx.net> Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 18:23:59 -0000 Hi, P.U.Kruppa am Montag, 24. September 2007: > Hello, > > I use a HP Deskjet 990 Cxi via parallel port with cups and hpijs > driver on > > FreeBSD pukruppa.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Sep > 21 16:52:59 CEST 2007 amd64 > > When I try to print a little bit more complex documents > (OpenOffice, pdf) my System will crash. > > On my root terminal there will be a long list of > lpt0: [ITHREAD] > lpt0: [GIANT-LOCKED] > lpt0: [ITHREAD] > [...] > lines, then some dumping activity and a reboot. > > I upgraded to 7.0 last week, so all I can say is: everything was > fine with 6.2 . > > Please tell me if you need more information. I've had the same here. Enabling polling via "lptcontrol -p /dev/lpt0" solved the problem. ciao Dieter From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 19:03:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D708316A418 for ; Mon, 24 Sep 2007 19:03:18 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.freebsd.org (Postfix) with ESMTP id 72D6713C46A for ; Mon, 24 Sep 2007 19:03:18 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1252713nfb for ; Mon, 24 Sep 2007 12:03:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=YBR9B0de1n2XOZ9IjnYnwMQPZcrMQahjZhZ2UTnA9EY=; b=DPNfSA+XCbH0FbQFUgyffOdwIFuXWc12rrYoxadXfhVjbuohLBfR0tSQTNQ8gUfdvmJawi4lU2prjkwocmccy2mfYYcNiWV4DIYgiANVmH8AzKnRAD90q4tgVAFTs8blJ1JsaFjBhd3KjjcWg25PT4dSCPE7PAZmHYFW2M9vIWs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=sDYmFzOmojY6bvyojbIxirkS4MJiDtXRmgtHYkic9yHR60ij8LM0FTLVT+L9oJA0inn91XVIo7SbEkAUd9OxxfW2HA0TsPMZgZf2v9KSxssBNleMEKNkHu9riKA5yFGdtijm6dC9Q32Ysk1q8SAz0rdfxdXotLGvNFJoFBgOOPU= Received: by 10.86.50.8 with SMTP id x8mr4940926fgx.1190660596997; Mon, 24 Sep 2007 12:03:16 -0700 (PDT) Received: by 10.86.2.1 with HTTP; Mon, 24 Sep 2007 12:03:17 -0700 (PDT) Message-ID: <499c70c0709241203g1e1dae49r4f51f0cd9086492b@mail.gmail.com> Date: Mon, 24 Sep 2007 22:03:17 +0300 From: "Abdullah Ibn Hamad Al-Marri" To: "FreeBSD Current" , "FreeBSD Questions" MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Help I borke my 7.0 AMD64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 19:03:18 -0000 Hello, I used potsclean, and it broke my GCC enviroment. I can't make buildworld anymore. >>> stage 2.3: build tools -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/sbin:/bin:/usr/sbin:/usr/bin WORLDTMP=/usr/obj/usr/src/tmp MAKEFLAGS="-m /usr/src/tools/build/mk -m /usr/src/share/mk" /usr/obj/usr/src/make.amd64/make -f Makefile.inc1 TARGET=amd64 TARGET_ARCH=amd64 DESTDIR= BOOTSTRAPPING=700052 -DNO_LINT -DNO_CPU_CFLAGS -DNO_WARNS build-tools ===> bin/csh (obj,build-tools) grep 'ERR_' /usr/src/bin/csh/../../contrib/tcsh/sh.err.c | grep '^#define' >> sh.err.h cc -E -O2 -fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include /usr/src/bin/csh/../../contrib/tcsh/tc.const.c /usr/src/bin/csh/../../contrib/tcsh/sh.char.h /usr/src/bin/csh/config.h /usr/src/bin/csh/../../contrib/tcsh/config_f.h /usr/src/bin/csh/../../contrib/tcsh/sh.types.h sh.err.h -D_h_tc_const | grep 'Char STR' | sed -e 's/Char \([a-zA-Z0-9_]*\)\(.*\)/extern Char \1[];/' | sort >> tc.const.h cc -o gethost -L/usr/obj/usr/src/tmp/legacy/usr/lib -O2 -fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include /usr/src/bin/csh/../../contrib/tcsh/gethost.c /usr/bin/ld: cannot find -lgcc_s *** Error code 1 Stop in /usr/src/bin/csh. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 19:04:27 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7BDE416A475; Mon, 24 Sep 2007 19:04:27 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 71EAD13C478; Mon, 24 Sep 2007 19:04:25 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F80A39.3050707@FreeBSD.org> Date: Mon, 24 Sep 2007 21:04:25 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Scott Long References: <20070921102946.T11189@borg> <46F415BF.9010500@FreeBSD.org> <20070921140550.D96923@thebighonker.lerctr.org> <46F41CFF.6080108@FreeBSD.org> <46F58799.1030702@freebsd.org> <46F58B21.8030307@FreeBSD.org> <20070924091558.GB32006@team.vega.ru> <46F78C59.1020801@FreeBSD.org> <20070924080347.O84223@thebighonker.lerctr.org> <20070924144210.GA82735@team.vega.ru> <46F7D7A4.5090007@samsco.org> In-Reply-To: <46F7D7A4.5090007@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Darren Reed , freebsd-current@freebsd.org, Larry Rosenman Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 19:04:27 -0000 Scott Long wrote: > Ruslan Ermilov wrote: >> On Mon, Sep 24, 2007 at 08:04:33AM -0500, Larry Rosenman wrote: >>> On Mon, 24 Sep 2007, Kris Kennaway wrote: >>> >>>> Ruslan Ermilov wrote: >>>>> On Sat, Sep 22, 2007 at 11:37:37PM +0200, Kris Kennaway wrote: >>>>>> Darren Reed wrote: >> [...] >>>>>>> Stupid question, perhaps, but is vm.kmem_size/vm.kmem_size_max >>>>>>> limited by physical RAM? >>>>>> Yes. >>>>> To be precise, it's actually limited by 2 * sizeof(physical RAM). >>>>> It's still size of a _virtual_ memory map (kmem_map), after all: >>>>> : /* >>>>> : * Limit kmem virtual size to twice the physical memory. >>>>> : * This allows for kmem map sparseness, but limits the size >>>>> : * to something sane. Be careful to not overflow the 32bit >>>>> : * ints while doing the check. >>>>> : */ >>>>> : if (((vm_kmem_size / 2) / PAGE_SIZE) > cnt.v_page_count) >>>>> : vm_kmem_size = 2 * cnt.v_page_count * PAGE_SIZE; >>>> Well OK, but that seems pretty dangerous, because it leaves open a >>>> pathway to exhaust all of physical memory and presumably panic. >>> is KVA pageable? Is the kmem_map dedicating non-pageable memory? >>> >> kmem_map is used to map memory for the zone allocator, including >> malloc(9). >> >>> I've set my vm.kmem_max to 1G, (on a 4G amd64 box). Is that reasonable? >>> >> It just means that your kernel can "malloc" up to 1G of memory. >> > > You're all missing the point, I hate to say. What happened is that a > change was made recently to more accurately account for allocated > memory. Now people are getting kmem_map_too_small panics that weren't > getting them before. So while the accounting is now more accurate, the > outcome is actually harmful. That needs to be fixed before the release. Well yes, that is one hypothesis, but the evidence points elsewhere as well. Prior the change you reference, some of my zfs machines would run for weeks before hitting a load pattern that exhausted their kmem_map and triggered the panic. Also unless I have missed it I am not seeing the sudden flood of panic reports that may indicate sudden breakage. It is quite possible that this particular report has nothing to do with the recent change. Kris From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 19:05:16 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECFB916A468 for ; Mon, 24 Sep 2007 19:05:16 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id A921513C481; Mon, 24 Sep 2007 19:05:15 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F80A6C.5020203@FreeBSD.org> Date: Mon, 24 Sep 2007 21:05:16 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: "P.U.Kruppa" References: <20070924051118.H9923@small> <46F785BB.9030800@FreeBSD.org> <20070924114923.C10251@small> <20070924100607.GC1462@elvandar.org> <20070924183258.J1576@small> In-Reply-To: <20070924183258.J1576@small> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Remko Lodder , freebsd-current@freebsd.org Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 19:05:17 -0000 P.U.Kruppa wrote: > On Mon, 24 Sep 2007, Remko Lodder wrote: > >> On Mon, Sep 24, 2007 at 11:50:37AM +0200, P.U.Kruppa wrote: >>> On Mon, 24 Sep 2007, Kris Kennaway wrote: >>> >>>> P.U.Kruppa wrote: >>>>> Hello, >>>>> I use a HP Deskjet 990 Cxi via parallel port with cups and hpijs >>>>> driver on >>>>> FreeBSD pukruppa.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Sep 21 >>>>> 16:52:59 CEST 2007 amd64 >>>>> When I try to print a little bit more complex documents >>>>> (OpenOffice, pdf) >>>>> my System will crash. >>>>> On my root terminal there will be a long list of >>>>> lpt0: [ITHREAD] >>>>> lpt0: [GIANT-LOCKED] >>>>> lpt0: [ITHREAD] >>>>> [...] >>>>> lines, then some dumping activity and a reboot. >>>>> I upgraded to 7.0 last week, so all I can say is: everything was >>>>> fine with >>>>> 6.2 . >>>>> Please tell me if you need more information. >>>> >>>> Well yeah, how about e.g. the actual details from the panic? >>> How do I get them? >>> Do I have to recompile my kernel (I put off debugging and Witness >>> Options)? >> >> Hello, >> >> Check >> http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html >> for >> more information. >> >> Thanks >> >> -- >> Kind regards, >> >> Remko Lodder ** remko@elvandar.org > Sorry, from developer's handbook I guess I should find a vmcore.N file. > There isn't any. My parallel printing attempts end up in some kind of > single user mode on the root terminal with a > db> > prompt. Can I do anything with that? Yes, that's the DDB prompt that the documentation describes. It tells you how to trigger the dump and obtain other important debugging. Kris From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 19:13:51 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1DA7F16A420; Mon, 24 Sep 2007 19:13:51 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 5757D13C448; Mon, 24 Sep 2007 19:13:47 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F80C6C.2030002@FreeBSD.org> Date: Mon, 24 Sep 2007 21:13:48 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Abdullah Ibn Hamad Al-Marri References: <499c70c0709241203g1e1dae49r4f51f0cd9086492b@mail.gmail.com> In-Reply-To: <499c70c0709241203g1e1dae49r4f51f0cd9086492b@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , FreeBSD Questions Subject: Re: Help I borke my 7.0 AMD64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 19:13:51 -0000 Abdullah Ibn Hamad Al-Marri wrote: > Hello, > > I used potsclean, and it broke my GCC enviroment. What is potsclean? > I can't make buildworld anymore. > >>>> stage 2.3: build tools > -------------------------------------------------------------- > cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj INSTALL="sh > /usr/src/tools/install.sh" > PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/sbin:/bin:/usr/sbin:/usr/bin > WORLDTMP=/usr/obj/usr/src/tmp MAKEFLAGS="-m /usr/src/tools/build/mk > -m /usr/src/share/mk" /usr/obj/usr/src/make.amd64/make -f > Makefile.inc1 TARGET=amd64 TARGET_ARCH=amd64 DESTDIR= > BOOTSTRAPPING=700052 -DNO_LINT -DNO_CPU_CFLAGS -DNO_WARNS build-tools > ===> bin/csh (obj,build-tools) > grep 'ERR_' /usr/src/bin/csh/../../contrib/tcsh/sh.err.c | grep > '^#define' >> sh.err.h > cc -E -O2 -fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh > -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' > -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include > /usr/src/bin/csh/../../contrib/tcsh/tc.const.c > /usr/src/bin/csh/../../contrib/tcsh/sh.char.h > /usr/src/bin/csh/config.h > /usr/src/bin/csh/../../contrib/tcsh/config_f.h > /usr/src/bin/csh/../../contrib/tcsh/sh.types.h sh.err.h -D_h_tc_const > | grep 'Char STR' | sed -e 's/Char \([a-zA-Z0-9_]*\)\(.*\)/extern > Char \1[];/' | sort >> tc.const.h > cc -o gethost -L/usr/obj/usr/src/tmp/legacy/usr/lib -O2 > -fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh > -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' > -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include > /usr/src/bin/csh/../../contrib/tcsh/gethost.c > /usr/bin/ld: cannot find -lgcc_s You will need to obtain another copy of this library. Either you could download a 7.0 snapshot and extract it from that, or maybe just reinstall if that is more trouble than you want to deal with. Kris From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 19:16:17 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CC4A16A419 for ; Mon, 24 Sep 2007 19:16:17 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.freebsd.org (Postfix) with ESMTP id 49A4C13C494 for ; Mon, 24 Sep 2007 19:16:15 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1255558nfb for ; Mon, 24 Sep 2007 12:16:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=emZCWrlV1JPZExDSpwwLCKp+hkjQCX/Rgabn32i8LUg=; b=WUaqvIImZ7q0hHO79BtyTJIzn5PUr36XrdSWuQPYaOi98ebsTm8O4K5LmxEKZjAjrqS0BcbB+7Y4Sj3BMjZl5R4cBFxRbLBMMRfs9vo8fOponRir++ZK4+t+vh7OqhumrL7Omwsy/GRe2PBJtZ8DmEn9CZObz0cqmppDUO0K8aQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ah/X8LI4tWdYatx+g4/u9XcJNd8Rrgui6GeJUSpqWeiTJnuvRY0vu1tk4SW44mCYvcGYQeEVVR5ZCE18e3IdbqAwKMgMeiTZfjc31oW2V9DnNln9xB7kc2N1i8H6j8VL2AfBTNPYDuvsiYZeg3Jro7lU1FUxEQTbZeYTScq+BW4= Received: by 10.86.86.12 with SMTP id j12mr370978fgb.1190661374747; Mon, 24 Sep 2007 12:16:14 -0700 (PDT) Received: by 10.86.2.1 with HTTP; Mon, 24 Sep 2007 12:16:14 -0700 (PDT) Message-ID: <499c70c0709241216v2315e4c4pdee0f5375b353864@mail.gmail.com> Date: Mon, 24 Sep 2007 22:16:14 +0300 From: "Abdullah Ibn Hamad Al-Marri" To: "Kris Kennaway" In-Reply-To: <46F80C6C.2030002@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <499c70c0709241203g1e1dae49r4f51f0cd9086492b@mail.gmail.com> <46F80C6C.2030002@FreeBSD.org> Cc: FreeBSD Current , FreeBSD Questions Subject: Re: Help I borke my 7.0 AMD64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 19:16:17 -0000 On 9/24/07, Kris Kennaway wrote: > Abdullah Ibn Hamad Al-Marri wrote: > > Hello, > > > > I used potsclean, and it broke my GCC enviroment. > > What is potsclean? > > > I can't make buildworld anymore. > > > >>>> stage 2.3: build tools > > -------------------------------------------------------------- > > cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj INSTALL="sh > > /usr/src/tools/install.sh" > > PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/sbin:/bin:/usr/sbin:/usr/bin > > WORLDTMP=/usr/obj/usr/src/tmp MAKEFLAGS="-m /usr/src/tools/build/mk > > -m /usr/src/share/mk" /usr/obj/usr/src/make.amd64/make -f > > Makefile.inc1 TARGET=amd64 TARGET_ARCH=amd64 DESTDIR= > > BOOTSTRAPPING=700052 -DNO_LINT -DNO_CPU_CFLAGS -DNO_WARNS build-tools > > ===> bin/csh (obj,build-tools) > > grep 'ERR_' /usr/src/bin/csh/../../contrib/tcsh/sh.err.c | grep > > '^#define' >> sh.err.h > > cc -E -O2 -fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh > > -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' > > -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include > > /usr/src/bin/csh/../../contrib/tcsh/tc.const.c > > /usr/src/bin/csh/../../contrib/tcsh/sh.char.h > > /usr/src/bin/csh/config.h > > /usr/src/bin/csh/../../contrib/tcsh/config_f.h > > /usr/src/bin/csh/../../contrib/tcsh/sh.types.h sh.err.h -D_h_tc_const > > | grep 'Char STR' | sed -e 's/Char \([a-zA-Z0-9_]*\)\(.*\)/extern > > Char \1[];/' | sort >> tc.const.h > > cc -o gethost -L/usr/obj/usr/src/tmp/legacy/usr/lib -O2 > > -fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh > > -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' > > -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include > > /usr/src/bin/csh/../../contrib/tcsh/gethost.c > > /usr/bin/ld: cannot find -lgcc_s > > You will need to obtain another copy of this library. Either you could > download a 7.0 snapshot and extract it from that, or maybe just > reinstall if that is more trouble than you want to deal with. > > Kris Sorry Kris, I meant portsclean, and it deleted stuff it shouldn't for the native GCC environment. -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 19:27:05 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B161016A418; Mon, 24 Sep 2007 19:27:05 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id D564813C45A; Mon, 24 Sep 2007 19:27:04 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F80F89.70703@FreeBSD.org> Date: Mon, 24 Sep 2007 21:27:05 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Abdullah Ibn Hamad Al-Marri References: <499c70c0709241203g1e1dae49r4f51f0cd9086492b@mail.gmail.com> <46F80C6C.2030002@FreeBSD.org> <499c70c0709241216v2315e4c4pdee0f5375b353864@mail.gmail.com> In-Reply-To: <499c70c0709241216v2315e4c4pdee0f5375b353864@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , FreeBSD Questions Subject: Re: Help I borke my 7.0 AMD64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 19:27:05 -0000 Abdullah Ibn Hamad Al-Marri wrote: > On 9/24/07, Kris Kennaway wrote: >> Abdullah Ibn Hamad Al-Marri wrote: >>> Hello, >>> >>> I used potsclean, and it broke my GCC enviroment. >> What is potsclean? >> >>> I can't make buildworld anymore. >>> >>>>>> stage 2.3: build tools >>> -------------------------------------------------------------- >>> cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj INSTALL="sh >>> /usr/src/tools/install.sh" >>> PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/sbin:/bin:/usr/sbin:/usr/bin >>> WORLDTMP=/usr/obj/usr/src/tmp MAKEFLAGS="-m /usr/src/tools/build/mk >>> -m /usr/src/share/mk" /usr/obj/usr/src/make.amd64/make -f >>> Makefile.inc1 TARGET=amd64 TARGET_ARCH=amd64 DESTDIR= >>> BOOTSTRAPPING=700052 -DNO_LINT -DNO_CPU_CFLAGS -DNO_WARNS build-tools >>> ===> bin/csh (obj,build-tools) >>> grep 'ERR_' /usr/src/bin/csh/../../contrib/tcsh/sh.err.c | grep >>> '^#define' >> sh.err.h >>> cc -E -O2 -fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh >>> -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' >>> -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include >>> /usr/src/bin/csh/../../contrib/tcsh/tc.const.c >>> /usr/src/bin/csh/../../contrib/tcsh/sh.char.h >>> /usr/src/bin/csh/config.h >>> /usr/src/bin/csh/../../contrib/tcsh/config_f.h >>> /usr/src/bin/csh/../../contrib/tcsh/sh.types.h sh.err.h -D_h_tc_const >>> | grep 'Char STR' | sed -e 's/Char \([a-zA-Z0-9_]*\)\(.*\)/extern >>> Char \1[];/' | sort >> tc.const.h >>> cc -o gethost -L/usr/obj/usr/src/tmp/legacy/usr/lib -O2 >>> -fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh >>> -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' >>> -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include >>> /usr/src/bin/csh/../../contrib/tcsh/gethost.c >>> /usr/bin/ld: cannot find -lgcc_s >> You will need to obtain another copy of this library. Either you could >> download a 7.0 snapshot and extract it from that, or maybe just >> reinstall if that is more trouble than you want to deal with. >> >> Kris > > Sorry Kris, I meant portsclean, and it deleted stuff it shouldn't for > the native GCC environment. That sounds pretty odd, are you sure you hadn't made changes to your /lib (e.g. symlinking libgcc_s to a port version)? It should not be touching anything under /lib at all. Kris From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 19:32:26 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E919D16A468; Mon, 24 Sep 2007 19:32:26 +0000 (UTC) (envelope-from SRS0=bc760a2c171c29e6a0e00feccd00f957d27e64be=468=es.net=oberman@es.net) Received: from postal1.es.net (postal4.es.net [IPv6:2001:400:6000:1::66]) by mx1.freebsd.org (Postfix) with ESMTP id EB43013C448; Mon, 24 Sep 2007 19:32:25 +0000 (UTC) (envelope-from SRS0=bc760a2c171c29e6a0e00feccd00f957d27e64be=468=es.net=oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal4.es.net (Postal Node 4) with ESMTP (SSL) id DCE10822; Mon, 24 Sep 2007 12:32:22 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id F00F445012; Mon, 24 Sep 2007 12:32:20 -0700 (PDT) To: "P.U.Kruppa" In-Reply-To: Your message of "Mon, 24 Sep 2007 11:50:37 +0200." <20070924114923.C10251@small> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1190662340_32699P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 24 Sep 2007 12:32:20 -0700 From: "Kevin Oberman" Message-Id: <20070924193220.F00F445012@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ; ; ; X-Sender: X-To_Name: P.U.Kruppa X-To_Domain: pukruppa.net X-To: "P.U.Kruppa" X-To_Email: ulrich@pukruppa.net X-To_Alias: ulrich Cc: freebsd-current@freebsd.org Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 19:32:27 -0000 --==_Exmh_1190662340_32699P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Mon, 24 Sep 2007 11:50:37 +0200 (CEST) > From: "P.U.Kruppa" > Sender: owner-freebsd-current@freebsd.org > > On Mon, 24 Sep 2007, Kris Kennaway wrote: > > > P.U.Kruppa wrote: > >> Hello, > >> > >> I use a HP Deskjet 990 Cxi via parallel port with cups and hpijs driver on > >> > >> FreeBSD pukruppa.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Sep 21 > >> 16:52:59 CEST 2007 amd64 > >> > >> When I try to print a little bit more complex documents (OpenOffice, pdf) > >> my System will crash. > >> > >> On my root terminal there will be a long list of > >> lpt0: [ITHREAD] > >> lpt0: [GIANT-LOCKED] > >> lpt0: [ITHREAD] > >> [...] > >> lines, then some dumping activity and a reboot. > >> > >> I upgraded to 7.0 last week, so all I can say is: everything was fine with > >> 6.2 . > >> > >> Please tell me if you need more information. > > > > Well yeah, how about e.g. the actual details from the panic? > How do I get them? > Do I have to recompile my kernel (I put off debugging and Witness > Options)? You probably should look at the section on debug in the handbook. At a minimum, you need a kernel built with "makeoptions DEBUG=-g". Other than a bit of disk space and a few seconds while building the kernel, this costs nothing and should always be in the kernel config; not just when you want to look at a problem. You also want the KDB, DDB, and GDB options in the config. These also have no impact on performance, but do eat some memory. Since this looks locking related, WITNESS is probably a good idea, but it is a big performance hit. I'd also add INVARIANTS and INVARIANT_SUPPORT. The cost of this is much lower than WITNESS, but it's not free, either. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1190662340_32699P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFG+BDEkn3rs5h7N1ERAu6jAJ42/5dvtmKfwbV97iggMTMX3ddsAwCgrd68 wcK6lO9Ko28Hi3/qMhuJN44= =Fdcu -----END PGP SIGNATURE----- --==_Exmh_1190662340_32699P-- From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 19:36:59 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9CFB416A419 for ; Mon, 24 Sep 2007 19:36:59 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.freebsd.org (Postfix) with ESMTP id 2367413C447 for ; Mon, 24 Sep 2007 19:36:58 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1260244nfb for ; Mon, 24 Sep 2007 12:36:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=FUBDl+U3RHsvrXn1geVXN5xiF5ocdLPxKJMg+xza+M4=; b=UJ5rF6KdOLA1QXE6I6ntWeam493E66I1Df59+0789BUoPtpIXTDPHyv5B3vD+RTMrk8om44WsawrR6XN/vXEQS9Tn0CTyoSM09x9pM2RZivUE+VCOX3pXF3JwmLTSm58yRBpkbrYEVpFw/EJsqXivSvOYmp+dUtP9v2nLuK/Tx8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LGpg4RMotnCGvFMl9olytB8PPGL56Goe7XrUIteP3lGgxFyYjST+jjYKTCCTMNczqNyyhkJQuF8QcAWcSeuq2wC0mvMaF33g51uoRww7x2MIV8MPP9qqUGRichKsnBmS+c9GbWzN0GW2VMr44EjLoZEzVAcrGxNyCyOfTtOLwTo= Received: by 10.86.84.5 with SMTP id h5mr4462547fgb.1190662617131; Mon, 24 Sep 2007 12:36:57 -0700 (PDT) Received: by 10.86.2.1 with HTTP; Mon, 24 Sep 2007 12:36:57 -0700 (PDT) Message-ID: <499c70c0709241236q58ee1215ie38f3fb6968d71d2@mail.gmail.com> Date: Mon, 24 Sep 2007 22:36:57 +0300 From: "Abdullah Ibn Hamad Al-Marri" To: "Kris Kennaway" In-Reply-To: <46F80F89.70703@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <499c70c0709241203g1e1dae49r4f51f0cd9086492b@mail.gmail.com> <46F80C6C.2030002@FreeBSD.org> <499c70c0709241216v2315e4c4pdee0f5375b353864@mail.gmail.com> <46F80F89.70703@FreeBSD.org> Cc: FreeBSD Current , FreeBSD Questions Subject: Re: Help I borke my 7.0 AMD64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 19:36:59 -0000 On 9/24/07, Kris Kennaway wrote: > Abdullah Ibn Hamad Al-Marri wrote: > > On 9/24/07, Kris Kennaway wrote: > >> Abdullah Ibn Hamad Al-Marri wrote: > >>> Hello, > >>> > >>> I used potsclean, and it broke my GCC enviroment. > >> What is potsclean? > >> > >>> I can't make buildworld anymore. > >>> > >>>>>> stage 2.3: build tools > >>> -------------------------------------------------------------- > >>> cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj INSTALL="sh > >>> /usr/src/tools/install.sh" > >>> PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/sbin:/bin:/usr/sbin:/usr/bin > >>> WORLDTMP=/usr/obj/usr/src/tmp MAKEFLAGS="-m /usr/src/tools/build/mk > >>> -m /usr/src/share/mk" /usr/obj/usr/src/make.amd64/make -f > >>> Makefile.inc1 TARGET=amd64 TARGET_ARCH=amd64 DESTDIR= > >>> BOOTSTRAPPING=700052 -DNO_LINT -DNO_CPU_CFLAGS -DNO_WARNS build-tools > >>> ===> bin/csh (obj,build-tools) > >>> grep 'ERR_' /usr/src/bin/csh/../../contrib/tcsh/sh.err.c | grep > >>> '^#define' >> sh.err.h > >>> cc -E -O2 -fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh > >>> -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' > >>> -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include > >>> /usr/src/bin/csh/../../contrib/tcsh/tc.const.c > >>> /usr/src/bin/csh/../../contrib/tcsh/sh.char.h > >>> /usr/src/bin/csh/config.h > >>> /usr/src/bin/csh/../../contrib/tcsh/config_f.h > >>> /usr/src/bin/csh/../../contrib/tcsh/sh.types.h sh.err.h -D_h_tc_const > >>> | grep 'Char STR' | sed -e 's/Char \([a-zA-Z0-9_]*\)\(.*\)/extern > >>> Char \1[];/' | sort >> tc.const.h > >>> cc -o gethost -L/usr/obj/usr/src/tmp/legacy/usr/lib -O2 > >>> -fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh > >>> -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' > >>> -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include > >>> /usr/src/bin/csh/../../contrib/tcsh/gethost.c > >>> /usr/bin/ld: cannot find -lgcc_s > >> You will need to obtain another copy of this library. Either you could > >> download a 7.0 snapshot and extract it from that, or maybe just > >> reinstall if that is more trouble than you want to deal with. > >> > >> Kris > > > > Sorry Kris, I meant portsclean, and it deleted stuff it shouldn't for > > the native GCC environment. > > That sounds pretty odd, are you sure you hadn't made changes to your > /lib (e.g. symlinking libgcc_s to a port version)? It should not be > touching anything under /lib at all. > > Kris Yes, I didn't do anything else. ls geom libalias_smedia.so libcrypto.so.5 libmd.so.4 libufs.so.4 libalias.so.6 libatm.so.5 libdevstat.so.6 libncurses.so.7 libumem.so.1 libalias_cuseeme.so libavl.so.1 libedit.so.6 libncursesw.so.7 libutil.so.7 libalias_dummy.so libbegemot.so.3 libgeom.so.4 libnvpair.so.1 libuutil.so.1 libalias_ftp.so libbsdxml.so.3 libipsec.so.3 libpcap.so.5 libz.so.4 libalias_irc.so libbsnmp.so.4 libipx.so.4 libreadline.so.7 libzfs.so.1 libalias_nbt.so libc.so.7 libkiconv.so.3 libsbuf.so.4 libzpool.so.1 libalias_pptp.so libcam.so.4 libkvm.so.4 libssp.so.0 libalias_skinny.so libcrypt.so.4 libm.so.5 libthr.so.3 -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 19:42:25 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DE0016A421; Mon, 24 Sep 2007 19:42:25 +0000 (UTC) (envelope-from SRS0=bc760a2c171c29e6a0e00feccd00f957d27e64be=468=es.net=oberman@es.net) Received: from postal1.es.net (postal2.es.net [IPv6:2001:400:14:3::7]) by mx1.freebsd.org (Postfix) with ESMTP id 39A5E13C48D; Mon, 24 Sep 2007 19:42:23 +0000 (UTC) (envelope-from SRS0=bc760a2c171c29e6a0e00feccd00f957d27e64be=468=es.net=oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id DCO22920; Mon, 24 Sep 2007 12:42:20 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 988EC45012; Mon, 24 Sep 2007 12:42:19 -0700 (PDT) To: "Abdullah Ibn Hamad Al-Marri" In-Reply-To: Your message of "Mon, 24 Sep 2007 22:36:57 +0300." <499c70c0709241236q58ee1215ie38f3fb6968d71d2@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1190662939_32699P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 24 Sep 2007 12:42:19 -0700 From: "Kevin Oberman" Message-Id: <20070924194219.988EC45012@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ; ; ; ; X-Sender: X-To_Name: Abdullah Ibn Hamad Al-Marri X-To_Domain: gmail.com X-To: "Abdullah Ibn Hamad Al-Marri" X-To_Email: almarrie@gmail.com X-To_Alias: almarrie Cc: FreeBSD Current , FreeBSD Questions Subject: Re: Help I borke my 7.0 AMD64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 19:42:25 -0000 --==_Exmh_1190662939_32699P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Mon, 24 Sep 2007 22:36:57 +0300 > From: "Abdullah Ibn Hamad Al-Marri" > Sender: owner-freebsd-current@freebsd.org > > On 9/24/07, Kris Kennaway wrote: > > Abdullah Ibn Hamad Al-Marri wrote: > > > On 9/24/07, Kris Kennaway wrote: > > >> Abdullah Ibn Hamad Al-Marri wrote: > > >>> Hello, > > >>> > > >>> I used potsclean, and it broke my GCC enviroment. > > >> What is potsclean? > > >> > > >>> I can't make buildworld anymore. > > >>> > > >>>>>> stage 2.3: build tools > > >>> -------------------------------------------------------------- > > >>> cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj INSTALL="sh > > >>> /usr/src/tools/install.sh" > > >>> PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/sbin:/bin:/usr/sbin:/usr/bin > > >>> WORLDTMP=/usr/obj/usr/src/tmp MAKEFLAGS="-m /usr/src/tools/build/mk > > >>> -m /usr/src/share/mk" /usr/obj/usr/src/make.amd64/make -f > > >>> Makefile.inc1 TARGET=amd64 TARGET_ARCH=amd64 DESTDIR= > > >>> BOOTSTRAPPING=700052 -DNO_LINT -DNO_CPU_CFLAGS -DNO_WARNS build-tools > > >>> ===> bin/csh (obj,build-tools) > > >>> grep 'ERR_' /usr/src/bin/csh/../../contrib/tcsh/sh.err.c | grep > > >>> '^#define' >> sh.err.h > > >>> cc -E -O2 -fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh > > >>> -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' > > >>> -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include > > >>> /usr/src/bin/csh/../../contrib/tcsh/tc.const.c > > >>> /usr/src/bin/csh/../../contrib/tcsh/sh.char.h > > >>> /usr/src/bin/csh/config.h > > >>> /usr/src/bin/csh/../../contrib/tcsh/config_f.h > > >>> /usr/src/bin/csh/../../contrib/tcsh/sh.types.h sh.err.h -D_h_tc_const > > >>> | grep 'Char STR' | sed -e 's/Char \([a-zA-Z0-9_]*\)\(.*\)/extern > > >>> Char \1[];/' | sort >> tc.const.h > > >>> cc -o gethost -L/usr/obj/usr/src/tmp/legacy/usr/lib -O2 > > >>> -fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh > > >>> -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' > > >>> -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include > > >>> /usr/src/bin/csh/../../contrib/tcsh/gethost.c > > >>> /usr/bin/ld: cannot find -lgcc_s > > >> You will need to obtain another copy of this library. Either you could > > >> download a 7.0 snapshot and extract it from that, or maybe just > > >> reinstall if that is more trouble than you want to deal with. > > >> > > >> Kris > > > > > > Sorry Kris, I meant portsclean, and it deleted stuff it shouldn't for > > > the native GCC environment. > > > > That sounds pretty odd, are you sure you hadn't made changes to your > > /lib (e.g. symlinking libgcc_s to a port version)? It should not be > > touching anything under /lib at all. > > > > Kris > > Yes, I didn't do anything else. > > ls > geom libalias_smedia.so libcrypto.so.5 > libmd.so.4 libufs.so.4 > libalias.so.6 libatm.so.5 libdevstat.so.6 > libncurses.so.7 libumem.so.1 > libalias_cuseeme.so libavl.so.1 libedit.so.6 > libncursesw.so.7 libutil.so.7 > libalias_dummy.so libbegemot.so.3 libgeom.so.4 > libnvpair.so.1 libuutil.so.1 > libalias_ftp.so libbsdxml.so.3 libipsec.so.3 > libpcap.so.5 libz.so.4 > libalias_irc.so libbsnmp.so.4 libipx.so.4 > libreadline.so.7 libzfs.so.1 > libalias_nbt.so libc.so.7 libkiconv.so.3 > libsbuf.so.4 libzpool.so.1 > libalias_pptp.so libcam.so.4 libkvm.so.4 > libssp.so.0 > libalias_skinny.so libcrypt.so.4 libm.so.5 > libthr.so.3 What arguments did you give to portsclean? Specifically, did you tell it to clean libraries (_L or --libclean)? Sounds like you yanked a library out from under gcc. I tend to stick to -DC to avoid the possibility of foot shooting. (I manage to do that too often, in any case.) -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1190662939_32699P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFG+BMbkn3rs5h7N1ERAh7NAKC4Gj4pcHyShtuqQ2uS7FY/mpMzCwCeKA71 E4sloR3QvUrVpAizFhIbpzg= =41nY -----END PGP SIGNATURE----- --==_Exmh_1190662939_32699P-- From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 19:49:14 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A190D16A474 for ; Mon, 24 Sep 2007 19:49:14 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.freebsd.org (Postfix) with ESMTP id 08C4E13C511 for ; Mon, 24 Sep 2007 19:49:13 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1263024nfb for ; Mon, 24 Sep 2007 12:49:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Opf4LQ8N37Iz6L8xk66sKscsKtbnhzXXxHMriaHsJDk=; b=KKIIRqh8WsvXxjzQonJfGhGl63ffjM4VTh0lKU+7wJDU1nomOMsiZfp+HBZwK0XJcyAvC1l0hzNmysKLnGUTiPILE0VywaWwCUZriD9kSVvRSnDYiBWKLUCXXTCDXgi5eWf6mgyul/vsgQ48dG+wghTjZz+uI9EIXnc1V6HA/os= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=IEHEy+8ff789ysXObiDHfIqow0nh+hmQECzKzXqyPmKWW/B+8krmBSKkoBaTtVNDelDsHyQNpbeTTpEYT9Fnuqvo8D+NoeBKOXN3rOwr3oXLHIbpirSBDsvN8S8GqiS4gAXDgGFQsEUIuKCPKvneMG1Da0GSgmj9nUDmFmV4IEY= Received: by 10.86.86.12 with SMTP id j12mr392277fgb.1190663352514; Mon, 24 Sep 2007 12:49:12 -0700 (PDT) Received: by 10.86.2.1 with HTTP; Mon, 24 Sep 2007 12:49:12 -0700 (PDT) Message-ID: <499c70c0709241249m5845e582p752ee52582531a38@mail.gmail.com> Date: Mon, 24 Sep 2007 22:49:12 +0300 From: "Abdullah Ibn Hamad Al-Marri" To: "Kevin Oberman" In-Reply-To: <20070924194219.988EC45012@ptavv.es.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <499c70c0709241236q58ee1215ie38f3fb6968d71d2@mail.gmail.com> <20070924194219.988EC45012@ptavv.es.net> Cc: FreeBSD Current , FreeBSD Questions Subject: Re: Help I borke my 7.0 AMD64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 19:49:14 -0000 On 9/24/07, Kevin Oberman wrote: > > Date: Mon, 24 Sep 2007 22:36:57 +0300 > > From: "Abdullah Ibn Hamad Al-Marri" > > Sender: owner-freebsd-current@freebsd.org > > > > On 9/24/07, Kris Kennaway wrote: > > > Abdullah Ibn Hamad Al-Marri wrote: > > > > On 9/24/07, Kris Kennaway wrote: > > > >> Abdullah Ibn Hamad Al-Marri wrote: > > > >>> Hello, > > > >>> > > > >>> I used potsclean, and it broke my GCC enviroment. > > > >> What is potsclean? > > > >> > > > >>> I can't make buildworld anymore. > > > >>> > > > >>>>>> stage 2.3: build tools > > > >>> -------------------------------------------------------------- > > > >>> cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj INSTALL="sh > > > >>> /usr/src/tools/install.sh" > > > >>> PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/sbin:/bin:/usr/sbin:/usr/bin > > > >>> WORLDTMP=/usr/obj/usr/src/tmp MAKEFLAGS="-m /usr/src/tools/build/mk > > > >>> -m /usr/src/share/mk" /usr/obj/usr/src/make.amd64/make -f > > > >>> Makefile.inc1 TARGET=amd64 TARGET_ARCH=amd64 DESTDIR= > > > >>> BOOTSTRAPPING=700052 -DNO_LINT -DNO_CPU_CFLAGS -DNO_WARNS build-tools > > > >>> ===> bin/csh (obj,build-tools) > > > >>> grep 'ERR_' /usr/src/bin/csh/../../contrib/tcsh/sh.err.c | grep > > > >>> '^#define' >> sh.err.h > > > >>> cc -E -O2 -fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh > > > >>> -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' > > > >>> -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include > > > >>> /usr/src/bin/csh/../../contrib/tcsh/tc.const.c > > > >>> /usr/src/bin/csh/../../contrib/tcsh/sh.char.h > > > >>> /usr/src/bin/csh/config.h > > > >>> /usr/src/bin/csh/../../contrib/tcsh/config_f.h > > > >>> /usr/src/bin/csh/../../contrib/tcsh/sh.types.h sh.err.h -D_h_tc_const > > > >>> | grep 'Char STR' | sed -e 's/Char \([a-zA-Z0-9_]*\)\(.*\)/extern > > > >>> Char \1[];/' | sort >> tc.const.h > > > >>> cc -o gethost -L/usr/obj/usr/src/tmp/legacy/usr/lib -O2 > > > >>> -fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh > > > >>> -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' > > > >>> -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include > > > >>> /usr/src/bin/csh/../../contrib/tcsh/gethost.c > > > >>> /usr/bin/ld: cannot find -lgcc_s > > > >> You will need to obtain another copy of this library. Either you could > > > >> download a 7.0 snapshot and extract it from that, or maybe just > > > >> reinstall if that is more trouble than you want to deal with. > > > >> > > > >> Kris > > > > > > > > Sorry Kris, I meant portsclean, and it deleted stuff it shouldn't for > > > > the native GCC environment. > > > > > > That sounds pretty odd, are you sure you hadn't made changes to your > > > /lib (e.g. symlinking libgcc_s to a port version)? It should not be > > > touching anything under /lib at all. > > > > > > Kris > > > > Yes, I didn't do anything else. > > > > ls > > geom libalias_smedia.so libcrypto.so.5 > > libmd.so.4 libufs.so.4 > > libalias.so.6 libatm.so.5 libdevstat.so.6 > > libncurses.so.7 libumem.so.1 > > libalias_cuseeme.so libavl.so.1 libedit.so.6 > > libncursesw.so.7 libutil.so.7 > > libalias_dummy.so libbegemot.so.3 libgeom.so.4 > > libnvpair.so.1 libuutil.so.1 > > libalias_ftp.so libbsdxml.so.3 libipsec.so.3 > > libpcap.so.5 libz.so.4 > > libalias_irc.so libbsnmp.so.4 libipx.so.4 > > libreadline.so.7 libzfs.so.1 > > libalias_nbt.so libc.so.7 libkiconv.so.3 > > libsbuf.so.4 libzpool.so.1 > > libalias_pptp.so libcam.so.4 libkvm.so.4 > > libssp.so.0 > > libalias_skinny.so libcrypt.so.4 libm.so.5 > > libthr.so.3 > > What arguments did you give to portsclean? Specifically, did you tell it > to clean libraries (_L or --libclean)? Sounds like you yanked a library > out from under gcc. I tend to stick to -DC to avoid the possibility of > foot shooting. (I manage to do that too often, in any case.) > -- > 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 I forced portsclean -L but why on the earth it did remove the gcc lib since it's not installed by the ports? Is there away to recover it now? -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 20:41:15 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B45F916A418; Mon, 24 Sep 2007 20:41:15 +0000 (UTC) (envelope-from SRS0=bc760a2c171c29e6a0e00feccd00f957d27e64be=468=es.net=oberman@es.net) Received: from postal1.es.net (postal4.es.net [IPv6:2001:400:6000:1::66]) by mx1.freebsd.org (Postfix) with ESMTP id B23BD13C448; Mon, 24 Sep 2007 20:41:12 +0000 (UTC) (envelope-from SRS0=bc760a2c171c29e6a0e00feccd00f957d27e64be=468=es.net=oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal4.es.net (Postal Node 4) with ESMTP (SSL) id DDN78710; Mon, 24 Sep 2007 13:41:10 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 6E38545012; Mon, 24 Sep 2007 13:41:09 -0700 (PDT) To: "Abdullah Ibn Hamad Al-Marri" In-Reply-To: Your message of "Mon, 24 Sep 2007 22:49:12 +0300." <499c70c0709241249m5845e582p752ee52582531a38@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1190666469_32699P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 24 Sep 2007 13:41:09 -0700 From: "Kevin Oberman" Message-Id: <20070924204109.6E38545012@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ; ; ; ; X-Sender: X-To_Name: Abdullah Ibn Hamad Al-Marri X-To_Domain: gmail.com X-To: "Abdullah Ibn Hamad Al-Marri" X-To_Email: almarrie@gmail.com X-To_Alias: almarrie Cc: FreeBSD Current , FreeBSD Questions Subject: Re: Help I borke my 7.0 AMD64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 20:41:15 -0000 --==_Exmh_1190666469_32699P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Mon, 24 Sep 2007 22:49:12 +0300 > From: "Abdullah Ibn Hamad Al-Marri" > > On 9/24/07, Kevin Oberman wrote: > > > Date: Mon, 24 Sep 2007 22:36:57 +0300 > > > From: "Abdullah Ibn Hamad Al-Marri" > > > Sender: owner-freebsd-current@freebsd.org > > > > > > On 9/24/07, Kris Kennaway wrote: > > > > Abdullah Ibn Hamad Al-Marri wrote: > > > > > On 9/24/07, Kris Kennaway wrote: > > > > >> Abdullah Ibn Hamad Al-Marri wrote: > > > > >>> Hello, > > > > >>> > > > > >>> I used potsclean, and it broke my GCC enviroment. > > > > >> What is potsclean? > > > > >> > > > > >>> I can't make buildworld anymore. > > > > >>> > > > > >>>>>> stage 2.3: build tools > > > > >>> -------------------------------------------------------------- > > > > >>> cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj INSTALL="sh > > > > >>> /usr/src/tools/install.sh" > > > > >>> PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/sbin:/bin:/usr/sbin:/usr/bin > > > > >>> WORLDTMP=/usr/obj/usr/src/tmp MAKEFLAGS="-m /usr/src/tools/build/mk > > > > >>> -m /usr/src/share/mk" /usr/obj/usr/src/make.amd64/make -f > > > > >>> Makefile.inc1 TARGET=amd64 TARGET_ARCH=amd64 DESTDIR= > > > > >>> BOOTSTRAPPING=700052 -DNO_LINT -DNO_CPU_CFLAGS -DNO_WARNS build-tools > > > > >>> ===> bin/csh (obj,build-tools) > > > > >>> grep 'ERR_' /usr/src/bin/csh/../../contrib/tcsh/sh.err.c | grep > > > > >>> '^#define' >> sh.err.h > > > > >>> cc -E -O2 -fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh > > > > >>> -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' > > > > >>> -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include > > > > >>> /usr/src/bin/csh/../../contrib/tcsh/tc.const.c > > > > >>> /usr/src/bin/csh/../../contrib/tcsh/sh.char.h > > > > >>> /usr/src/bin/csh/config.h > > > > >>> /usr/src/bin/csh/../../contrib/tcsh/config_f.h > > > > >>> /usr/src/bin/csh/../../contrib/tcsh/sh.types.h sh.err.h -D_h_tc_const > > > > >>> | grep 'Char STR' | sed -e 's/Char \([a-zA-Z0-9_]*\)\(.*\)/extern > > > > >>> Char \1[];/' | sort >> tc.const.h > > > > >>> cc -o gethost -L/usr/obj/usr/src/tmp/legacy/usr/lib -O2 > > > > >>> -fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh > > > > >>> -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' > > > > >>> -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include > > > > >>> /usr/src/bin/csh/../../contrib/tcsh/gethost.c > > > > >>> /usr/bin/ld: cannot find -lgcc_s > > > > >> You will need to obtain another copy of this library. Either you could > > > > >> download a 7.0 snapshot and extract it from that, or maybe just > > > > >> reinstall if that is more trouble than you want to deal with. > > > > >> > > > > >> Kris > > > > > > > > > > Sorry Kris, I meant portsclean, and it deleted stuff it shouldn't for > > > > > the native GCC environment. > > > > > > > > That sounds pretty odd, are you sure you hadn't made changes to your > > > > /lib (e.g. symlinking libgcc_s to a port version)? It should not be > > > > touching anything under /lib at all. > > > > > > > > Kris > > > > > > Yes, I didn't do anything else. > > > > > > ls > > > geom libalias_smedia.so libcrypto.so.5 > > > libmd.so.4 libufs.so.4 > > > libalias.so.6 libatm.so.5 libdevstat.so.6 > > > libncurses.so.7 libumem.so.1 > > > libalias_cuseeme.so libavl.so.1 libedit.so.6 > > > libncursesw.so.7 libutil.so.7 > > > libalias_dummy.so libbegemot.so.3 libgeom.so.4 > > > libnvpair.so.1 libuutil.so.1 > > > libalias_ftp.so libbsdxml.so.3 libipsec.so.3 > > > libpcap.so.5 libz.so.4 > > > libalias_irc.so libbsnmp.so.4 libipx.so.4 > > > libreadline.so.7 libzfs.so.1 > > > libalias_nbt.so libc.so.7 libkiconv.so.3 > > > libsbuf.so.4 libzpool.so.1 > > > libalias_pptp.so libcam.so.4 libkvm.so.4 > > > libssp.so.0 > > > libalias_skinny.so libcrypt.so.4 libm.so.5 > > > libthr.so.3 > > > > What arguments did you give to portsclean? Specifically, did you tell it > > to clean libraries (_L or --libclean)? Sounds like you yanked a library > > out from under gcc. I tend to stick to -DC to avoid the possibility of > > foot shooting. (I manage to do that too often, in any case.) > > -- > > 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 > > I forced portsclean -L but why on the earth it did remove the gcc lib > since it's not installed by the ports? > > Is there away to recover it now? portsclean should never touch anything out of /usr/local/and base gcc should not depend on anything in /usr/local. I'd suspect that setting an environmental variable such as PORTSDIR might cause this, but that seem unlikely to have happened without a serious intent. Is it possible that you are not running the base gcc? ('which gcc' and 'gcc -v') It should be in /usr/bin and the version for a recent current should be 4.2.1 20070719. Is it possible that the portsclean was merely coincidental? Could something else have happened at about the same time? As far as recovery goes, what does 'locate libgcc_s.so show? You should have it in /lib, but there might be another copy around. If that fails, you can try finding a copy on some other system; a current system of about the same age as yours so that it will have the same gcc. Good luck! -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1190666469_32699P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFG+CDlkn3rs5h7N1ERAvFNAJ9mJmlZuSy6pqeKq5FhGZYMZbgmqwCfV+b1 i18wPBTqUH2wttaJX3pK12E= =cRfJ -----END PGP SIGNATURE----- --==_Exmh_1190666469_32699P-- From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 20:48:02 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C45CA16A47C for ; Mon, 24 Sep 2007 20:48:02 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by mx1.freebsd.org (Postfix) with ESMTP id 2DA7713C474 for ; Mon, 24 Sep 2007 20:48:01 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1275810nfb for ; Mon, 24 Sep 2007 13:48:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=rJ3aYNCF9ZQEyh4ANn2XchRm3H08+xiHjCERXqzVubc=; b=kM2ImX5J7+GHoNcTLc1mfv9vz/DczjP+bT1Je2fJtutMQEPPbdMftY4YI+C2p9KLwEFaN6JQZy8zI6sz4sc+l68zUr+rdvDS1PeD0OCmBBmzxVDsJymhWaMk9/q8RUXi8zRaswu+5oBzvvQsz3FNvBkO6CLr1n7SN6HT0dg9BnU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dv5FsdMMpeU/nqWD7WwPxH+eI+XcszT+/E5vvMkNnvmIdzI8KsSwANgBqI9yP9Lx5klq1xuORzQvnM2veeXYJZWc+7CZGpv6Rs/tQRh+tqrrQVqbbUMf1LGG59x44oclW0+t4xDWn9Ur9ChuoDPf9J8N+OTk9cAwoW0M6TlXe/A= Received: by 10.86.73.17 with SMTP id v17mr5032168fga.1190666879873; Mon, 24 Sep 2007 13:47:59 -0700 (PDT) Received: by 10.86.2.1 with HTTP; Mon, 24 Sep 2007 13:47:59 -0700 (PDT) Message-ID: <499c70c0709241347g1a8a4129i54aeec084242f96f@mail.gmail.com> Date: Mon, 24 Sep 2007 23:47:59 +0300 From: "Abdullah Ibn Hamad Al-Marri" To: "Kevin Oberman" In-Reply-To: <20070924204109.6E38545012@ptavv.es.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <499c70c0709241249m5845e582p752ee52582531a38@mail.gmail.com> <20070924204109.6E38545012@ptavv.es.net> Cc: FreeBSD Current , FreeBSD Questions Subject: Re: Help I borke my 7.0 AMD64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 20:48:02 -0000 On 9/24/07, Kevin Oberman wrote: > > Date: Mon, 24 Sep 2007 22:49:12 +0300 > > From: "Abdullah Ibn Hamad Al-Marri" > > > > On 9/24/07, Kevin Oberman wrote: > > > > Date: Mon, 24 Sep 2007 22:36:57 +0300 > > > > From: "Abdullah Ibn Hamad Al-Marri" > > > > Sender: owner-freebsd-current@freebsd.org > > > > > > > > On 9/24/07, Kris Kennaway wrote: > > > > > Abdullah Ibn Hamad Al-Marri wrote: > > > > > > On 9/24/07, Kris Kennaway wrote: > > > > > >> Abdullah Ibn Hamad Al-Marri wrote: > > > > > >>> Hello, > > > > > >>> > > > > > >>> I used potsclean, and it broke my GCC enviroment. > > > > > >> What is potsclean? > > > > > >> > > > > > >>> I can't make buildworld anymore. > > > > > >>> > > > > > >>>>>> stage 2.3: build tools > > > > > >>> -------------------------------------------------------------- > > > > > >>> cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj INSTALL="sh > > > > > >>> /usr/src/tools/install.sh" > > > > > >>> PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/sbin:/bin:/usr/sbin:/usr/bin > > > > > >>> WORLDTMP=/usr/obj/usr/src/tmp MAKEFLAGS="-m /usr/src/tools/build/mk > > > > > >>> -m /usr/src/share/mk" /usr/obj/usr/src/make.amd64/make -f > > > > > >>> Makefile.inc1 TARGET=amd64 TARGET_ARCH=amd64 DESTDIR= > > > > > >>> BOOTSTRAPPING=700052 -DNO_LINT -DNO_CPU_CFLAGS -DNO_WARNS build-tools > > > > > >>> ===> bin/csh (obj,build-tools) > > > > > >>> grep 'ERR_' /usr/src/bin/csh/../../contrib/tcsh/sh.err.c | grep > > > > > >>> '^#define' >> sh.err.h > > > > > >>> cc -E -O2 -fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh > > > > > >>> -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' > > > > > >>> -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include > > > > > >>> /usr/src/bin/csh/../../contrib/tcsh/tc.const.c > > > > > >>> /usr/src/bin/csh/../../contrib/tcsh/sh.char.h > > > > > >>> /usr/src/bin/csh/config.h > > > > > >>> /usr/src/bin/csh/../../contrib/tcsh/config_f.h > > > > > >>> /usr/src/bin/csh/../../contrib/tcsh/sh.types.h sh.err.h -D_h_tc_const > > > > > >>> | grep 'Char STR' | sed -e 's/Char \([a-zA-Z0-9_]*\)\(.*\)/extern > > > > > >>> Char \1[];/' | sort >> tc.const.h > > > > > >>> cc -o gethost -L/usr/obj/usr/src/tmp/legacy/usr/lib -O2 > > > > > >>> -fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh > > > > > >>> -I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' > > > > > >>> -DHAVE_ICONV -I/usr/obj/usr/src/tmp/legacy/usr/include > > > > > >>> /usr/src/bin/csh/../../contrib/tcsh/gethost.c > > > > > >>> /usr/bin/ld: cannot find -lgcc_s > > > > > >> You will need to obtain another copy of this library. Either you could > > > > > >> download a 7.0 snapshot and extract it from that, or maybe just > > > > > >> reinstall if that is more trouble than you want to deal with. > > > > > >> > > > > > >> Kris > > > > > > > > > > > > Sorry Kris, I meant portsclean, and it deleted stuff it shouldn't for > > > > > > the native GCC environment. > > > > > > > > > > That sounds pretty odd, are you sure you hadn't made changes to your > > > > > /lib (e.g. symlinking libgcc_s to a port version)? It should not be > > > > > touching anything under /lib at all. > > > > > > > > > > Kris > > > > > > > > Yes, I didn't do anything else. > > > > > > > > ls > > > > geom libalias_smedia.so libcrypto.so.5 > > > > libmd.so.4 libufs.so.4 > > > > libalias.so.6 libatm.so.5 libdevstat.so.6 > > > > libncurses.so.7 libumem.so.1 > > > > libalias_cuseeme.so libavl.so.1 libedit.so.6 > > > > libncursesw.so.7 libutil.so.7 > > > > libalias_dummy.so libbegemot.so.3 libgeom.so.4 > > > > libnvpair.so.1 libuutil.so.1 > > > > libalias_ftp.so libbsdxml.so.3 libipsec.so.3 > > > > libpcap.so.5 libz.so.4 > > > > libalias_irc.so libbsnmp.so.4 libipx.so.4 > > > > libreadline.so.7 libzfs.so.1 > > > > libalias_nbt.so libc.so.7 libkiconv.so.3 > > > > libsbuf.so.4 libzpool.so.1 > > > > libalias_pptp.so libcam.so.4 libkvm.so.4 > > > > libssp.so.0 > > > > libalias_skinny.so libcrypt.so.4 libm.so.5 > > > > libthr.so.3 > > > > > > What arguments did you give to portsclean? Specifically, did you tell it > > > to clean libraries (_L or --libclean)? Sounds like you yanked a library > > > out from under gcc. I tend to stick to -DC to avoid the possibility of > > > foot shooting. (I manage to do that too often, in any case.) > > > -- > > > 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 > > > > I forced portsclean -L but why on the earth it did remove the gcc lib > > since it's not installed by the ports? > > > > Is there away to recover it now? > > portsclean should never touch anything out of /usr/local/and base gcc > should not depend on anything in /usr/local. I'd suspect that setting an > environmental variable such as PORTSDIR might cause this, but that seem > unlikely to have happened without a serious intent. > > Is it possible that you are not running the base gcc? ('which gcc' and 'gcc > -v') It should be in /usr/bin and the version for a recent current > should be 4.2.1 20070719. > > Is it possible that the portsclean was merely coincidental? Could > something else have happened at about the same time? > > As far as recovery goes, what does 'locate libgcc_s.so show? You should > have it in /lib, but there might be another copy around. If that fails, > you can try finding a copy on some other system; a current system of > about the same age as yours so that it will have the same gcc. > > Good luck! > -- > 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 Thank you Kevin! gcc -v Using built-in specs. Target: amd64-undermydesk-freebsd Configured with: FreeBSD/amd64 system compiler Thread model: posix gcc version 4.2.1 20070719 [FreeBSD] locate libgcc_s.so returns nothing, and not in /lib :( Could you please put it somewhere where so that I could fetch it? -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 21:28:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACBE616A418 for ; Mon, 24 Sep 2007 21:28:18 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 660AE13C4AC for ; Mon, 24 Sep 2007 21:28:18 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IZvGB-0001rF-Kb for freebsd-current@freebsd.org; Mon, 24 Sep 2007 21:14:31 +0000 Received: from 78-1-110-138.adsl.net.t-com.hr ([78.1.110.138]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 Sep 2007 21:14:31 +0000 Received: from ivoras by 78-1-110-138.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 Sep 2007 21:14:31 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Mon, 24 Sep 2007 23:01:42 +0200 Lines: 40 Message-ID: References: <043BBA16-A303-438D-97BE-950FEABB71A8@mac.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig16CBCE514D3E73AE9D5D2898" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 78-1-110-138.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) In-Reply-To: <043BBA16-A303-438D-97BE-950FEABB71A8@mac.com> X-Enigmail-Version: 0.95.3 Sender: news Subject: Re: panic: mtx_lock() of destroyed mutex @ route.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 21:28:18 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig16CBCE514D3E73AE9D5D2898 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Marcel Moolenaar wrote: > All, >=20 > The following panic happened on pluto1.freebsd.org: > panic(0xe00000000465f758, 0xe000000004672a18, 0x517, 0x507, > 0xe00000000480ccf8) at panic+0x2e0 > _mtx_lock_flags(0xe00000002ae49920, 0x0, 0xe000000004672a18, 0x517) at > _mtx_lock_flags+0x90 > rt_check(0xa000000033b9f1e0, 0xa000000033b9f1f0, 0xe00000002ae49920, > 0xe00000002ae49860) at rt_check+0x1e0 > arpresolve(0xe000000010351000, 0xe00000001073b770, 0xe000000010754e00, > 0xe000000010542ef0, 0xa000000033b9f208) at arpresolve+0x170 It's well known. ref: http://lists.freebsd.org/pipermail/freebsd-current/2007-September/076932.= html --------------enig16CBCE514D3E73AE9D5D2898 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG+CW8ldnAQVacBcgRAkbDAJ0c89ZZDUIhqx1t9LKWHGGsVA+jgQCgs+oX FVymLRDLyOR7AHPql9v9lCw= =rDcJ -----END PGP SIGNATURE----- --------------enig16CBCE514D3E73AE9D5D2898-- From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 23:09:22 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 945C116A421 for ; Mon, 24 Sep 2007 23:09:22 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from webaccess-cl.virtdom.com (webaccess-cl.virtdom.com [216.240.101.25]) by mx1.freebsd.org (Postfix) with ESMTP id 5AA6813C458 for ; Mon, 24 Sep 2007 23:09:22 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from [192.168.1.103] (c-67-160-44-208.hsd1.wa.comcast.net [67.160.44.208]) (authenticated bits=0) by webaccess-cl.virtdom.com (8.13.6/8.13.6) with ESMTP id l8ON9It8047195 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Mon, 24 Sep 2007 19:09:19 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Mon, 24 Sep 2007 16:11:59 -0700 (PDT) From: Jeff Roberson X-X-Sender: jroberson@10.0.0.1 To: Vlad GALU In-Reply-To: Message-ID: <20070924161054.T547@10.0.0.1> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD Current Subject: Re: Bogus numbers with rev 1.209 of sched_ule.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 23:09:22 -0000 On Mon, 24 Sep 2007, Vlad GALU wrote: > -- cut here -- > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 34653 root 1 5 0 3136K 1048K ttyin 0 0:00 nan% getty > 37990 root 1 8 0 4328K 2272K wait 1 0:00 nan% bash > 37915 dapyx 1 8 0 3564K 1540K wait 0 0:00 nan% su > 37711 dapyx 1 20 0 4392K 2432K pause 0 0:00 nan% tcsh > -- and here -- Try rebuilding world? Or at least libkvm/top/ps? I've never seen this problem but I upgraded my world at the same time that I made several changes that impacted libkvm. Thanks, Jeff > > -- > If it's there, and you can see it, it's real. > If it's not there, and you can see it, it's virtual. > If it's there, and you can't see it, it's transparent. > If it's not there, and you can't see it, you erased 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" > From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 01:20:12 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7209916A418 for ; Tue, 25 Sep 2007 01:20:12 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from smtp02.dentaku.gol.com (smtp02.dentaku.gol.com [203.216.5.72]) by mx1.freebsd.org (Postfix) with ESMTP id 3DAD313C455 for ; Tue, 25 Sep 2007 01:20:11 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from pat.gol.co.jp ([203.216.1.191] helo=[127.0.0.1]) by smtp02.dentaku.gol.com with esmtpa (Dentaku) id 1IZz5t-0007Je-V9 for ; Tue, 25 Sep 2007 10:20:10 +0900 Message-ID: <46F86249.9090800@fusiongol.com> Date: Tue, 25 Sep 2007 10:20:09 +0900 From: Nathan Butcher User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV GOL X-Abuse-Complaints: abuse@gol.com Subject: Re: SATA DVD-Drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 01:20:12 -0000 >Hi, >I've had similar problems with ICH8 mobo. >Seems like no matter what mode i set for the JMicron controller >(ide/raid/ahci) >freebsd sees it as ahci and optical drive does not work. >However i made my SATA DVD drive work by putting it on a ICH sata port >and setting IDE mode. >I've also had exacly the same issue with Xorg and Nvidia driver when i >have JMicron enabled, and it seems that when i enable the "memory >remapping feature" in the BIOS it works again properly. >And btw, this is on Asus P5B Deluxe motherboard. >hth, >Niki I'm getting exactly the same problem with a SATA DVD drive in my Gigabyte GA-G33-DS3R's JMicron controller. It doesn't matter what mode I put the controller in (IDE/AHCI/RAID-IDE), FreeBSD notices the presence of the controller in dmesg, but does not recognize either SATA DVD drives nor hard drives attached to it. They just don't make an appearance in /dev (Unlike the ICH9 drives on this mobo). I think somebody determined that there has been some regression here, because the JMicron controller works on FreeBSD 6.2 apparently. That counts as two SATA chipsets I've noticed regression in with 7.0-CURRENT (Jmicron and Promise SATA 150/300 TX4), which I really hope get fixed before 7.0-RELEASE. I was having issues with Xorg 7.3 crashing and acting erratically on my motherboard as well, although I had no idea that the JMicron controller could have had anything to do with it. From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 01:37:15 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A86F316A418 for ; Tue, 25 Sep 2007 01:37:15 +0000 (UTC) (envelope-from ulrich@pukruppa.net) Received: from pukruppa.net (pukruppa.net [213.146.114.24]) by mx1.freebsd.org (Postfix) with ESMTP id BA9A113C481 for ; Tue, 25 Sep 2007 01:37:14 +0000 (UTC) (envelope-from ulrich@pukruppa.net) Received: from pukruppa.net (localhost [127.0.0.1]) by pukruppa.net (8.14.1/8.14.1) with ESMTP id l8P1b6fp001783; Tue, 25 Sep 2007 03:37:06 +0200 (CEST) (envelope-from ulrich@pukruppa.net) Received: from localhost (ulrich@localhost) by pukruppa.net (8.14.1/8.14.1/Submit) with ESMTP id l8P1b55x001780; Tue, 25 Sep 2007 03:37:06 +0200 (CEST) (envelope-from ulrich@pukruppa.net) Date: Tue, 25 Sep 2007 03:37:05 +0200 (CEST) From: "P.U.Kruppa" X-X-Sender: ulrich@small To: bruce@cran.org.uk In-Reply-To: <20070924173221.GA18292@muon.bluestop.org> Message-ID: <20070925032851.O1634@small> References: <20070924051118.H9923@small> <46F785BB.9030800@FreeBSD.org> <20070924114923.C10251@small> <20070924100607.GC1462@elvandar.org> <20070924183258.J1576@small> <20070924173221.GA18292@muon.bluestop.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Remko Lodder , freebsd-current@freebsd.org Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 01:37:15 -0000 On Mon, 24 Sep 2007, bruce@cran.org.uk wrote: > On Mon, Sep 24, 2007 at 06:36:53PM +0200, P.U.Kruppa wrote: >> Sorry, from developer's handbook I guess I should find a vmcore.N >> file. There isn't any. My parallel printing attempts end up in >> some kind of single user mode on the root terminal with a >> db> >> prompt. Can I do anything with that? >> > > That's the DDB prompt: from there you need to either get a backtrace or, > more usefully, generate a crash dump. > > To generate a crash dump that you can later use with kgdb, type "panic" > at the db> prompt. Ah yes, now I get a nice vmcore.0 (I placed it it /usr , since I didn't know if my /var is big enough) So now: -------------------------------------------- pukruppa# cd /usr/obj/usr/src/sys/SMALLD/ pukruppa# kgdb kernel.debug /usr/vmcore.0 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd". Unread portion of the kernel message buffer: lpt0: [GIANT-LOCKED] lpt0: [ITHREAD] Fatal trap 30: reserved (unknown) fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x8:0xffffffff806e21f3 stack pointer = 0x10:0xffffffffaeb2f840 frame pointer = 0x10:0xffffffffaeb2f860 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, IOPL = 0 current process = 1348 (parallel) panic: from debugger cpuid = 0 Uptime: 8h3m19s Physical memory: 2034 MB Dumping 317 MB: 302 286 270 254 238 222 206 190 174 158 142 126 110 94 78 62 46 30 14 #0 doadump () at pcpu.h:194 194 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); (kgdb) backtrace #0 doadump () at pcpu.h:194 #1 0xffffffff80476b35 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #2 0xffffffff80476fa7 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:563 #3 0xffffffff801ba067 in db_panic (addr=Variable "addr" is not available. ) at /usr/src/sys/ddb/db_command.c:433 #4 0xffffffff801ba94c in db_command_loop () at /usr/src/sys/ddb/db_command.c:401 #5 0xffffffff801bc39f in db_trap (type=Variable "type" is not available. ) at /usr/src/sys/ddb/db_main.c:222 #6 0xffffffff8049de55 in kdb_trap (type=30, code=0, tf=0xffffffffaeb2f790) at /usr/src/sys/kern/subr_kdb.c:502 #7 0xffffffff806f1f7d in trap_fatal (frame=0xffffffffaeb2f790, eva=Variable "eva" is not available. ) at /usr/src/sys/amd64/amd64/trap.c:692 #8 0xffffffff806f2aa0 in trap (frame=0xffffffffaeb2f790) at /usr/src/sys/amd64/amd64/trap.c:499 #9 0xffffffff806d933e in calltrap () at /usr/src/sys/amd64/amd64/exception.S:169 #10 0xffffffff806e21f3 in spinlock_exit () at cpufunc.h:391 #11 0xffffffff806dd135 in ioapic_disable_intr (isrc=0xffffff000104c208) at /usr/src/sys/amd64/amd64/io_apic.c:375 #12 0xffffffff806dc00d in intr_remove_handler (cookie=Variable "cookie" is not available. ) at /usr/src/sys/amd64/amd64/intr_machdep.c:217 #13 0xffffffff8037c49a in ppc_teardown_intr (bus=0xffffff00012aac00, child=0xffffff0001637e00, r=0xffffff000165cd80, ih=0xffffff00121f4780) at bus_if.h:416 #14 0xffffffff8037b81a in ppb_release_bus (bus=0xffffff0001637800, dev=0xffffff0001637e00) at bus_if.h:416 #15 0xffffffff80377635 in lpt_release_ppbus (dev=0xffffff0001637e00) at /usr/src/sys/dev/ppbus/lpt.c:227 #16 0xffffffff8037801c in lptwrite (dev=Variable "dev" is not available. ) at /usr/src/sys/dev/ppbus/lpt.c:826 #17 0xffffffff80448941 in giant_write (dev=0xffffff000165fa00, uio=0xffffffffaeb2faf0, ioflag=0) at /usr/src/sys/kern/kern_conf.c:373 #18 0xffffffff8040e8cc in devfs_write_f (fp=0xffffff003ec6b528, uio=0xffffffffaeb2faf0, cred=Variable "cred" is not available. ) at /usr/src/sys/fs/devfs/devfs_vnops.c:1304 #19 0xffffffff804b02f5 in dofilewrite (td=0xffffff00019bd340, fd=4, fp=0xffffff003ec6b528, auio=0xffffffffaeb2faf0, offset=Variable "offset" is not available. ) at file.h:254 #20 0xffffffff804b058c in kern_writev (td=0xffffff00019bd340, fd=4, auio=0xffffffffaeb2faf0) at /usr/src/sys/kern/sys_generic.c:401 #21 0xffffffff804b0604 in write (td=Variable "td" is not available. ) at /usr/src/sys/kern/sys_generic.c:317 #22 0xffffffff806f24ce in syscall (frame=0xffffffffaeb2fc70) at /usr/src/sys/amd64/amd64/trap.c:822 #23 0xffffffff806d94eb in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:272 #24 0x00000008010bbfbc in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) ----------------------------------------------------- > Then, read > to find out how to obtain a backtrace that can help diagnose the fault. I hope that's it. > -- > Bruce > Greetings, Uli. Peter Ulrich Kruppa Wuppertal Germany From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 02:03:20 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 21BBF16A417 for ; Tue, 25 Sep 2007 02:03:20 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 0494113C448 for ; Tue, 25 Sep 2007 02:03:18 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.57]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id l8P23CwN092543 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Sep 2007 11:33:12 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Tue, 25 Sep 2007 11:33:03 +0930 User-Agent: KMail/1.9.7 References: <46F86249.9090800@fusiongol.com> In-Reply-To: <46F86249.9090800@fusiongol.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5389359.0Yqg79ZK38"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200709251133.12239.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.58 on 203.31.81.10 Cc: Nathan Butcher Subject: Re: SATA DVD-Drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 02:03:20 -0000 --nextPart5389359.0Yqg79ZK38 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 25 Sep 2007, Nathan Butcher wrote: > I think somebody determined that there has been some regression here, > because the JMicron controller works on FreeBSD 6.2 apparently. > That counts as two SATA chipsets I've noticed regression in with > 7.0-CURRENT (Jmicron and Promise SATA 150/300 TX4), which I really > hope get fixed before 7.0-RELEASE. Yes, I have a very similar motherboard, same JMicron controller, it=20 works in 6.2 but not in 7. I haven't checked if "Remap memory" is set on my system though.. I will=20 check soon. > I was having issues with Xorg 7.3 crashing and acting erratically on > my motherboard as well, although I had no idea that the JMicron > controller could have had anything to do with it. I hadn't noticed any problem with video in 6.2 but I haven't used it=20 much (VESA only so it's slow) =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 --nextPart5389359.0Yqg79ZK38 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBG+Gxg5ZPcIHs/zowRAkYYAKCRB5en7Jmh1TQfUz/EPdGbAi/ZGgCbBcH1 3rBWy/+hoLOcNyq+eQG7Km4= =1IG/ -----END PGP SIGNATURE----- --nextPart5389359.0Yqg79ZK38-- From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 02:18:36 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A0EF16A417 for ; Tue, 25 Sep 2007 02:18:36 +0000 (UTC) (envelope-from ulrich@pukruppa.net) Received: from pukruppa.net (pukruppa.net [213.146.114.24]) by mx1.freebsd.org (Postfix) with ESMTP id 6FB0713C45D for ; Tue, 25 Sep 2007 02:18:35 +0000 (UTC) (envelope-from ulrich@pukruppa.net) Received: from pukruppa.net (localhost [127.0.0.1]) by pukruppa.net (8.14.1/8.14.1) with ESMTP id l8P2IX18001667; Tue, 25 Sep 2007 04:18:33 +0200 (CEST) (envelope-from ulrich@pukruppa.net) Received: from localhost (ulrich@localhost) by pukruppa.net (8.14.1/8.14.1/Submit) with ESMTP id l8P2IXDp001664; Tue, 25 Sep 2007 04:18:33 +0200 (CEST) (envelope-from ulrich@pukruppa.net) Date: Tue, 25 Sep 2007 04:18:32 +0200 (CEST) From: "P.U.Kruppa" X-X-Sender: ulrich@small To: Dieter Franzke In-Reply-To: <200709241951.28762.sysinstall@gmx.net> Message-ID: <20070925041717.W1660@small> References: <20070924051118.H9923@small> <200709241951.28762.sysinstall@gmx.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 02:18:36 -0000 On Mon, 24 Sep 2007, Dieter Franzke wrote: > Hi, > > P.U.Kruppa am Montag, 24. September 2007: >> Hello, >> >> I use a HP Deskjet 990 Cxi via parallel port with cups and hpijs >> driver on >> >> FreeBSD pukruppa.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Sep >> 21 16:52:59 CEST 2007 amd64 >> >> When I try to print a little bit more complex documents >> (OpenOffice, pdf) my System will crash. >> >> On my root terminal there will be a long list of >> lpt0: [ITHREAD] >> lpt0: [GIANT-LOCKED] >> lpt0: [ITHREAD] >> [...] >> lines, then some dumping activity and a reboot. >> >> I upgraded to 7.0 last week, so all I can say is: everything was >> fine with 6.2 . >> >> Please tell me if you need more information. > > I've had the same here. > Enabling polling via "lptcontrol -p /dev/lpt0" solved the problem. Indeed! Thanks! Uli. > > > ciao > > Dieter > > _______________________________________________ > 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" > Peter Ulrich Kruppa Wuppertal Germany From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 02:27:27 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF61A16A468 for ; Tue, 25 Sep 2007 02:27:27 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from smtp02.dentaku.gol.com (smtp02.dentaku.gol.com [203.216.5.72]) by mx1.freebsd.org (Postfix) with ESMTP id 85ECF13C457 for ; Tue, 25 Sep 2007 02:27:27 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from pat.gol.co.jp ([203.216.1.191] helo=[127.0.0.1]) by smtp02.dentaku.gol.com with esmtpa (Dentaku) id 1Ia090-0003Vx-HP; Tue, 25 Sep 2007 11:27:26 +0900 Message-ID: <46F8720E.2000108@fusiongol.com> Date: Tue, 25 Sep 2007 11:27:26 +0900 From: Nathan Butcher User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Daniel O'Connor References: <46F86249.9090800@fusiongol.com> <200709251133.12239.doconnor@gsoft.com.au> In-Reply-To: <200709251133.12239.doconnor@gsoft.com.au> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Abuse-Complaints: abuse@gol.com Cc: freebsd-current@freebsd.org Subject: Re: SATA DVD-Drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 02:27:27 -0000 Daniel O'Connor wrote: > On Tue, 25 Sep 2007, Nathan Butcher wrote: >> I think somebody determined that there has been some regression here, >> because the JMicron controller works on FreeBSD 6.2 apparently. >> That counts as two SATA chipsets I've noticed regression in with >> 7.0-CURRENT (Jmicron and Promise SATA 150/300 TX4), which I really >> hope get fixed before 7.0-RELEASE. > > Yes, I have a very similar motherboard, same JMicron controller, it > works in 6.2 but not in 7. > > I haven't checked if "Remap memory" is set on my system though.. I will > check soon. I don't think I have this option on my motherboard's BIOS. BTW, I am running with a Silicon Image 3124 chipset 4 port SATA-II card now (of generic Taiwanese make), and have had no issues with it. Seems like a good chipset for cheap ZFS on CURRENT. Fingers crossed, the driver won't break until RELEASE. >> I was having issues with Xorg 7.3 crashing and acting erratically on >> my motherboard as well, although I had no idea that the JMicron >> controller could have had anything to do with it. > > I hadn't noticed any problem with video in 6.2 but I haven't used it > much (VESA only so it's slow) > The G33 Intel on-board graphics chipset on my motherboard should now be supported in Xorg 7.3 with the latest xorg "intel" driver -- if only I could get xorg to start up in CURRENT without locking up my system. From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 02:36:32 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22DD916A41B for ; Tue, 25 Sep 2007 02:36:32 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 4696513C465 for ; Tue, 25 Sep 2007 02:36:30 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.57]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id l8P2aTQh093325 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Sep 2007 12:06:29 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Nathan Butcher Date: Tue, 25 Sep 2007 12:06:20 +0930 User-Agent: KMail/1.9.7 References: <46F86249.9090800@fusiongol.com> <200709251133.12239.doconnor@gsoft.com.au> <46F8720E.2000108@fusiongol.com> In-Reply-To: <46F8720E.2000108@fusiongol.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3272761.BvLHHXncbE"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200709251206.29176.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.58 on 203.31.81.10 Cc: freebsd-current@freebsd.org Subject: Re: SATA DVD-Drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 02:36:32 -0000 --nextPart3272761.BvLHHXncbE Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 25 Sep 2007, Nathan Butcher wrote: > > I haven't checked if "Remap memory" is set on my system though.. I > > will check soon. > > I don't think I have this option on my motherboard's BIOS. > > BTW, I am running with a Silicon Image 3124 chipset 4 port SATA-II > card now (of generic Taiwanese make), and have had no issues with it. > Seems like a good chipset for cheap ZFS on CURRENT. Fingers crossed, > the driver won't break until RELEASE. Silicon Image leave a bad taste in my mouth after the Sil3112 :) If I get some time I will try a binary search and find when the JMicron=20 stopped working in -current. > > I hadn't noticed any problem with video in 6.2 but I haven't used > > it much (VESA only so it's slow) > > The G33 Intel on-board graphics chipset on my motherboard should now > be supported in Xorg 7.3 with the latest xorg "intel" driver -- if > only I could get xorg to start up in CURRENT without locking up my > system. Ahh.. fun :-/ I have a system which I think needs Xorg 7.3 to work, at the moment it's=20 stuck with VESA. =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 --nextPart3272761.BvLHHXncbE Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBG+HQt5ZPcIHs/zowRAoErAJ9cC4AqDB/XxhLEC5N0mTPJUr+3KQCgkIiM RSlBjgBBgPyOv+4/hGEwHhM= =oXWp -----END PGP SIGNATURE----- --nextPart3272761.BvLHHXncbE-- From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 03:00:02 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B1E016A417 for ; Tue, 25 Sep 2007 03:00:02 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from smtp02.dentaku.gol.com (smtp02.dentaku.gol.com [203.216.5.72]) by mx1.freebsd.org (Postfix) with ESMTP id 36E2F13C45B for ; Tue, 25 Sep 2007 02:59:56 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from pat.gol.co.jp ([203.216.1.191] helo=[127.0.0.1]) by smtp02.dentaku.gol.com with esmtpa (Dentaku) id 1Ia0eR-0000tP-GW; Tue, 25 Sep 2007 11:59:55 +0900 Message-ID: <46F879AB.2030502@fusiongol.com> Date: Tue, 25 Sep 2007 11:59:55 +0900 From: Nathan Butcher User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Daniel O'Connor References: <46F86249.9090800@fusiongol.com> <200709251133.12239.doconnor@gsoft.com.au> <46F8720E.2000108@fusiongol.com> <200709251206.29176.doconnor@gsoft.com.au> In-Reply-To: <200709251206.29176.doconnor@gsoft.com.au> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Abuse-Complaints: abuse@gol.com Cc: freebsd-current@freebsd.org Subject: Re: SATA DVD-Drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 03:00:02 -0000 Daniel O'Connor wrote: > On Tue, 25 Sep 2007, Nathan Butcher wrote: >>> I haven't checked if "Remap memory" is set on my system though.. I >>> will check soon. >> I don't think I have this option on my motherboard's BIOS. >> >> BTW, I am running with a Silicon Image 3124 chipset 4 port SATA-II >> card now (of generic Taiwanese make), and have had no issues with it. >> Seems like a good chipset for cheap ZFS on CURRENT. Fingers crossed, >> the driver won't break until RELEASE. > > Silicon Image leave a bad taste in my mouth after the Sil3112 :) > > If I get some time I will try a binary search and find when the JMicron > stopped working in -current. Actually, now that I think about it, I tried a card with a SiI3114 chipset (the SATA-1 variety) in 7.0-CURRENT a few weeks ago in a SuperMicro server board. The driver for that chipset is broken too, in another weird and wonderful way. I have no idea if it is fixed yet or not in the latest CURRENT, but I doubt it. The FreeBSD ata driver maintainer seems to be MIA. From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 04:55:55 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D886E16A41B; Tue, 25 Sep 2007 04:55:55 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 996CF13C49D; Tue, 25 Sep 2007 04:55:55 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id BD04E2FD1D; Tue, 25 Sep 2007 00:55:54 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 25 Sep 2007 00:55:54 -0400 X-Sasl-enc: 5CuKcbdY4UWTInNW/CXK+W+/m3rHLW/PiOayNGjIttoy 1190696154 Received: from [192.168.1.235] (64-142-85-108.dsl.dynamic.sonic.net [64.142.85.108]) by mail.messagingengine.com (Postfix) with ESMTP id 4ED7C22DC9; Tue, 25 Sep 2007 00:55:53 -0400 (EDT) Message-ID: <46F8951C.50904@freebsd.org> Date: Mon, 24 Sep 2007 21:57:00 -0700 From: Darren Reed User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Kris Kennaway References: <20070921102946.T11189@borg> <46F415BF.9010500@FreeBSD.org> <20070921140550.D96923@thebighonker.lerctr.org> <46F41CFF.6080108@FreeBSD.org> <46F58799.1030702@freebsd.org> <46F58B21.8030307@FreeBSD.org> <20070924091558.GB32006@team.vega.ru> <46F78C59.1020801@FreeBSD.org> <20070924080347.O84223@thebighonker.lerctr.org> <20070924144210.GA82735@team.vega.ru> <46F7D7A4.5090007@samsco.org> <46F80A39.3050707@FreeBSD.org> In-Reply-To: <46F80A39.3050707@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Larry Rosenman Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 04:55:55 -0000 Kris Kennaway wrote: > ... > Well yes, that is one hypothesis, but the evidence points elsewhere as > well. Prior the change you reference, some of my zfs machines would > run for weeks before hitting a load pattern that exhausted their > kmem_map and triggered the panic. Also unless I have missed it I am > not seeing the sudden flood of panic reports that may indicate sudden > breakage. It is quite possible that this particular report has > nothing to do with the recent change. Indeed. But here's something else to ponder... I've been using ZFS since it was internal beta at Sun, at first on i386 and later on amd64. I've never run into this kind of panic on Solaris. System can get very slow, yes, with ZFS hogging lots of memory, but it never panic'd because of it. We need to come up with a strategy here to solve this problem, be it fixing the kmem virtual memory or fixing zfs. Darren From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 07:03:39 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67A9C16A419 for ; Tue, 25 Sep 2007 07:03:39 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.185]) by mx1.freebsd.org (Postfix) with ESMTP id E4EFC13C468 for ; Tue, 25 Sep 2007 07:03:38 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by mu-out-0910.google.com with SMTP id w9so2293204mue for ; Tue, 25 Sep 2007 00:03:37 -0700 (PDT) Received: by 10.82.186.5 with SMTP id j5mr5657402buf.1190703817226; Tue, 25 Sep 2007 00:03:37 -0700 (PDT) Received: by 10.82.148.14 with HTTP; Tue, 25 Sep 2007 00:03:37 -0700 (PDT) Message-ID: Date: Tue, 25 Sep 2007 10:03:37 +0300 From: "Vlad GALU" To: "Jeff Roberson" In-Reply-To: <20070924161054.T547@10.0.0.1> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070924161054.T547@10.0.0.1> Cc: FreeBSD Current Subject: Re: Bogus numbers with rev 1.209 of sched_ule.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 07:03:39 -0000 On 9/25/07, Jeff Roberson wrote: > On Mon, 24 Sep 2007, Vlad GALU wrote: > > > -- cut here -- > > > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > > 34653 root 1 5 0 3136K 1048K ttyin 0 0:00 nan% getty > > 37990 root 1 8 0 4328K 2272K wait 1 0:00 nan% bash > > 37915 dapyx 1 8 0 3564K 1540K wait 0 0:00 nan% su > > 37711 dapyx 1 20 0 4392K 2432K pause 0 0:00 nan% tcsh > > -- and here -- > > Try rebuilding world? Or at least libkvm/top/ps? I've never seen this > problem but I upgraded my world at the same time that I made several > changes that impacted libkvm. > Unfortunately, I've already tried that. > Thanks, > Jeff > > > > > -- > > If it's there, and you can see it, it's real. > > If it's not there, and you can see it, it's virtual. > > If it's there, and you can't see it, it's transparent. > > If it's not there, and you can't see it, you erased 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" > > > -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 07:32:51 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0774C16A41A for ; Tue, 25 Sep 2007 07:32:51 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp3.yandex.ru (smtp3.yandex.ru [213.180.200.14]) by mx1.freebsd.org (Postfix) with ESMTP id 1F33D13C45B for ; Tue, 25 Sep 2007 07:32:49 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from ns.kirov.so-cdu.ru ([77.72.136.145]:40938 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S4747963AbXIYHVd (ORCPT ); Tue, 25 Sep 2007 11:21:33 +0400 X-Comment: RFC 2476 MSA function at smtp3.yandex.ru logged sender identity as: bu7cher Message-ID: <46F8B6E8.4040201@yandex.ru> Date: Tue, 25 Sep 2007 11:21:12 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: Nathan Butcher References: <46F86249.9090800@fusiongol.com> In-Reply-To: <46F86249.9090800@fusiongol.com> Content-Type: multipart/mixed; boundary="------------020100090709050609020004" Cc: Dave Grochowski , freebsd-current@freebsd.org, =?UTF-8?B?U8O4cmVuIFNjaG1pZHQ=?= Subject: Re: SATA DVD-Drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 07:32:51 -0000 This is a multi-part message in MIME format. --------------020100090709050609020004 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Nathan Butcher wrote: > I think somebody determined that there has been some regression here, > because the JMicron controller works on FreeBSD 6.2 apparently. > That counts as two SATA chipsets I've noticed regression in with > 7.0-CURRENT (Jmicron and Promise SATA 150/300 TX4), which I really hope > get fixed before 7.0-RELEASE. Hi, All. Seems only an AHCI controllers affected by this problem. I think the regression was introduced in the rev. 1.187 of ata-chipset.c: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/ata-chipset.c.diff?r1=1.186;r2=1.187 But the cause of problem is not here. I think kern/111699 related to this problem too. The problem in the port signature reading. Before this commit we have the following code: if ((ATA_IDX_INB(ch, ATA_CYL_LSB) == ATAPI_MAGIC_LSB) && (ATA_IDX_INB(ch, ATA_CYL_MSB) == ATAPI_MAGIC_MSB)) ch->devices = ATA_ATAPI_MASTER; else ch->devices = ATA_ATA_MASTER; It works in the FreeBSD-6.x. Now we have: switch (ATA_INL(ctlr->r_res2, ATA_AHCI_P_SIG + offset)) { case 0xeb140101: ch->devices = ATA_ATAPI_MASTER; device_printf(ch->dev, "SATA ATAPI devices not supported yet\n"); ch->devices = 0; break; case 0x96690101: ch->devices = ATA_PORTMULTIPLIER; device_printf(ch->dev, "Portmultipliers not supported yet\n"); ch->devices = 0; break; case 0x00000101: ch->devices = ATA_ATA_MASTER; break; } And it don't work. The returned signature is 0xFFFFFFFF. As a workaround we can add the default: ch->devices = ATA_ATA_MASTER; This code will be similar to 6.x code. But i think this is not right. May be someone can test the attached patch? Patch try to read port signature after starting AHCI engine, like linux do. Maybe this will help.. PS. Sorry, i can't this patch, because i don't have working AHCI controller. -- WBR, Andrey V. Elsukov --------------020100090709050609020004 Content-Type: text/plain; name="ata-chipset.c.diff" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="ata-chipset.c.diff" LS0tIHNyYy9zeXMvZGV2L2F0YS9hdGEtY2hpcHNldC5jLm9yaWcJMjAwNy0wOS0xMCAyMzox NjozOS4wMDAwMDAwMDAgKzA0MDAKKysrIHNyYy9zeXMvZGV2L2F0YS9hdGEtY2hpcHNldC5j CTIwMDctMDktMjUgMDk6MjU6NDcuMDAwMDAwMDAwICswNDAwCkBAIC02NzgsNyArNjc4LDcg QEAgYXRhX2FoY2lfcmVzZXQoZGV2aWNlX3QgZGV2KQogICAgIHN0cnVjdCBhdGFfY2hhbm5l bCAqY2ggPSBkZXZpY2VfZ2V0X3NvZnRjKGRldik7CiAgICAgdV9pbnQzMl90IGNtZDsKICAg ICBpbnQgb2Zmc2V0ID0gY2gtPnVuaXQgPDwgNzsKLSAgICBpbnQgdGltZW91dDsKKyAgICBp bnQgdGltZW91dCwgcmV0OwogCiAgICAgaWYgKCEoQVRBX0lOTChjdGxyLT5yX3JlczIsIEFU QV9BSENJX1BJKSAmICgxIDw8IGNoLT51bml0KSkpIHsKIAlkZXZpY2VfcHJpbnRmKGRldiwg InBvcnQgbm90IGltcGxlbWVudGVkXG4iKTsKQEAgLTcyMCw4ICs3MjAsMjMgQEAgYXRhX2Fo Y2lfcmVzZXQoZGV2aWNlX3QgZGV2KQogICAgIEFUQV9PVVRMKGN0bHItPnJfcmVzMiwgQVRB X0FIQ0lfUF9DTUQgKyBvZmZzZXQsIEFUQV9BSENJX1BfQ01EX1NVRCk7CiAKICAgICAvKiBl bmFibGUgaW50ZXJmYWNlICovCi0gICAgaWYgKGF0YV9zYXRhX3BoeV9yZXNldChkZXYpKSB7 Ci0Jc3dpdGNoIChBVEFfSU5MKGN0bHItPnJfcmVzMiwgQVRBX0FIQ0lfUF9TSUcgKyBvZmZz ZXQpKSB7CisgICAgcmV0ID0gYXRhX3NhdGFfcGh5X3Jlc2V0KGRldik7CisKKyAgICAvKiBj bGVhciBhbnkgaW50ZXJydXB0cyBwZW5kaW5nIG9uIHRoaXMgY2hhbm5lbCAqLworICAgIEFU QV9PVVRMKGN0bHItPnJfcmVzMiwgQVRBX0FIQ0lfUF9JUyArIG9mZnNldCwKKwkgICAgIEFU QV9JTkwoY3Rsci0+cl9yZXMyLCBBVEFfQUhDSV9QX0lTICsgb2Zmc2V0KSk7CisKKyAgICAv KiBzdGFydCBvcGVyYXRpb25zIG9uIHRoaXMgY2hhbm5lbCAqLworICAgIEFUQV9PVVRMKGN0 bHItPnJfcmVzMiwgQVRBX0FIQ0lfUF9DTUQgKyBvZmZzZXQsCisJICAgICAoQVRBX0FIQ0lf UF9DTURfQUNUSVZFIHwgQVRBX0FIQ0lfUF9DTURfRlJFIHwKKwkgICAgICBBVEFfQUhDSV9Q X0NNRF9QT0QgfCBBVEFfQUhDSV9QX0NNRF9TVUQgfCBBVEFfQUhDSV9QX0NNRF9TVCkpOwor CisgICAgLyogUmVhZCBwb3J0IHNpZ25hdHVyZSAqLworICAgIGlmIChyZXQpIHsKKwljbWQg PSBBVEFfSU5MKGN0bHItPnJfcmVzMiwgQVRBX0FIQ0lfUF9TSUcgKyBvZmZzZXQpOworCWlm IChib290dmVyYm9zZSkKKwkgICAgZGV2aWNlX3ByaW50ZihjaC0+ZGV2LCAiUG9ydCBzaWdu YXR1cmU6IDB4JTA4eFxuIiwgY21kKTsKKwlzd2l0Y2ggKGNtZCkgewogCWNhc2UgMHhlYjE0 MDEwMToKIAkgICAgY2gtPmRldmljZXMgPSBBVEFfQVRBUElfTUFTVEVSOwogCSAgICBkZXZp Y2VfcHJpbnRmKGNoLT5kZXYsICJTQVRBIEFUQVBJIGRldmljZXMgbm90IHN1cHBvcnRlZCB5 ZXRcbiIpOwpAQCAtNzM3LDE1ICs3NTIsNiBAQCBhdGFfYWhjaV9yZXNldChkZXZpY2VfdCBk ZXYpCiAJICAgIGJyZWFrOwogCX0KICAgICB9Ci0KLSAgICAvKiBjbGVhciBhbnkgaW50ZXJy dXB0cyBwZW5kaW5nIG9uIHRoaXMgY2hhbm5lbCAqLwotICAgIEFUQV9PVVRMKGN0bHItPnJf cmVzMiwgQVRBX0FIQ0lfUF9JUyArIG9mZnNldCwKLQkgICAgIEFUQV9JTkwoY3Rsci0+cl9y ZXMyLCBBVEFfQUhDSV9QX0lTICsgb2Zmc2V0KSk7Ci0KLSAgICAvKiBzdGFydCBvcGVyYXRp b25zIG9uIHRoaXMgY2hhbm5lbCAqLwotICAgIEFUQV9PVVRMKGN0bHItPnJfcmVzMiwgQVRB X0FIQ0lfUF9DTUQgKyBvZmZzZXQsCi0JICAgICAoQVRBX0FIQ0lfUF9DTURfQUNUSVZFIHwg QVRBX0FIQ0lfUF9DTURfRlJFIHwKLQkgICAgICBBVEFfQUhDSV9QX0NNRF9QT0QgfCBBVEFf QUhDSV9QX0NNRF9TVUQgfCBBVEFfQUhDSV9QX0NNRF9TVCkpOwogfQogCiBzdGF0aWMgdm9p ZAo= --------------020100090709050609020004-- From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 10:06:09 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DC3516A418 for ; Mon, 24 Sep 2007 10:06:09 +0000 (UTC) (envelope-from remko@elvandar.org) Received: from guardian.elvandar.org (evilcoder.xs4all.nl [195.64.94.120]) by mx1.freebsd.org (Postfix) with ESMTP id 07AEF13C46A for ; Mon, 24 Sep 2007 10:06:08 +0000 (UTC) (envelope-from remko@elvandar.org) Received: by guardian.elvandar.org (Postfix, from userid 1001) id 0476B7EDEA6; Mon, 24 Sep 2007 12:06:08 +0200 (CEST) Date: Mon, 24 Sep 2007 12:06:07 +0200 From: Remko Lodder To: "P.U.Kruppa" Message-ID: <20070924100607.GC1462@elvandar.org> References: <20070924051118.H9923@small> <46F785BB.9030800@FreeBSD.org> <20070924114923.C10251@small> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070924114923.C10251@small> User-Agent: Mutt/1.5.15 (2007-04-06) X-Mailman-Approved-At: Tue, 25 Sep 2007 08:28:28 +0000 Cc: freebsd-current@freebsd.org Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 10:06:09 -0000 On Mon, Sep 24, 2007 at 11:50:37AM +0200, P.U.Kruppa wrote: > On Mon, 24 Sep 2007, Kris Kennaway wrote: > > > P.U.Kruppa wrote: > >> Hello, > >> I use a HP Deskjet 990 Cxi via parallel port with cups and hpijs driver on > >> FreeBSD pukruppa.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Sep 21 > >> 16:52:59 CEST 2007 amd64 > >> When I try to print a little bit more complex documents (OpenOffice, pdf) > >> my System will crash. > >> On my root terminal there will be a long list of > >> lpt0: [ITHREAD] > >> lpt0: [GIANT-LOCKED] > >> lpt0: [ITHREAD] > >> [...] > >> lines, then some dumping activity and a reboot. > >> I upgraded to 7.0 last week, so all I can say is: everything was fine with > >> 6.2 . > >> Please tell me if you need more information. > > > > Well yeah, how about e.g. the actual details from the panic? > How do I get them? > Do I have to recompile my kernel (I put off debugging and Witness Options)? > > Uli. > > > > > Kris > > Hello, Check http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html for more information. Thanks -- Kind regards, Remko Lodder ** remko@elvandar.org FreeBSD ** remko@FreeBSD.org /* Quis custodiet ipsos custodes */ From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 10:38:21 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6E6616A419 for ; Mon, 24 Sep 2007 10:38:21 +0000 (UTC) (envelope-from serguey-grigoriev@yandex.ru) Received: from webmail27.mail.yandex.net (webmail27.mail.yandex.net [213.180.200.104]) by mx1.freebsd.org (Postfix) with ESMTP id 2844913C44B for ; Mon, 24 Sep 2007 10:38:21 +0000 (UTC) (envelope-from serguey-grigoriev@yandex.ru) Received: from YAMAIL (webmail27) by mail.yandex.ru id S5567576AbXIXKiM for ; Mon, 24 Sep 2007 14:38:12 +0400 X-Yandex-Spam: 1 Received: from [77.244.18.3] ([77.244.18.3]) by mail.yandex.ru with HTTP; Mon, 24 Sep 2007 14:38:11 +0400 From: "S.N.Grigoriev" To: eric@anholt.net In-Reply-To: 9070000000020153744 References: <105091190304115@webmail34.yandex.ru> 9070000000020153744 MIME-Version: 1.0 Message-Id: <472451190630292@webmail27.yandex.ru> Date: Mon, 24 Sep 2007 14:38:12 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailman-Approved-At: Tue, 25 Sep 2007 08:28:28 +0000 Cc: freebsd-current@freebsd.org Subject: Re: Xorg 7.3 problem on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 10:38:21 -0000 21.09.07, 22:25, Eric Anholt (eric@anholt.net): > This is usually driver-specific, sometimes chipset specific. You should > attach GDB to the X Server from a remote machine and try to reproduce > it, and post a backtrace. Hi, Eric, I thank you for your response. Yes, the problem is driver-specific. When I use the 'vesa' driver my system works fine. Unfortunately this is my home computer and there is not another one 'to attach GDB to the X Server from'. Regards, Serguey. From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 11:15:53 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1621716A420 for ; Mon, 24 Sep 2007 11:15:53 +0000 (UTC) (envelope-from serguey-grigoriev@yandex.ru) Received: from webmail31.mail.yandex.net (webmail31.mail.yandex.net [213.180.223.177]) by mx1.freebsd.org (Postfix) with ESMTP id 50D4313C44B for ; Mon, 24 Sep 2007 11:15:52 +0000 (UTC) (envelope-from serguey-grigoriev@yandex.ru) Received: from YAMAIL (webmail31) by mail.yandex.ru id S6455822AbXIXLPp for ; Mon, 24 Sep 2007 15:15:45 +0400 X-Yandex-Spam: 1 Received: from [77.244.18.3] ([77.244.18.3]) by mail.yandex.ru with HTTP; Mon, 24 Sep 2007 15:15:45 +0400 From: "S.N.Grigoriev" To: freebsd-current@freebsd.org MIME-Version: 1.0 Message-Id: <1291921190632545@webmail31.yandex.ru> Date: Mon, 24 Sep 2007 15:15:45 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailman-Approved-At: Tue, 25 Sep 2007 08:28:28 +0000 Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 11:15:53 -0000 Hi, list, This problem has already been reported this year at least twice. I can confirm it still exists. Probably it has been introduced near the beginning of May because April and earlyer sources handle parallel printing correctly. This problem is dealt with the parallel port interrupt handling. There is a workaround to avoid system crashes during printing: to switch parallel ports to the polling mode. But the system behaviour in this situation is not completely correct. For example the mouse pointer is periodically blocked on the screen for a few seconds. Regards, Serguey. From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 14:57:14 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 392E416A417 for ; Mon, 24 Sep 2007 14:57:14 +0000 (UTC) (envelope-from daniel@dgnetwork.com.br) Received: from mail.mastercabo.com.br (mail.mastercabo.com.br [200.179.179.14]) by mx1.freebsd.org (Postfix) with SMTP id 52C5C13C44B for ; Mon, 24 Sep 2007 14:57:12 +0000 (UTC) (envelope-from daniel@dgnetwork.com.br) Received: (qmail 15139 invoked by uid 1008); 24 Sep 2007 14:30:30 -0000 X-Spam-Checker-Version: SpamAssassin 3.1.7-unknown (2006-10-05) on srvmail2 X-Spam-Level: X-Spam-Status: No, score=-2.3 required=4.7 tests=AWL,BAYES_00 autolearn=ham version=3.1.7-unknown Received: from unknown (HELO ?10.0.0.10?) (daniel@dgnetwork.com.br@200.243.216.34) by mail.mastercabo.com.br with SMTP; 24 Sep 2007 14:30:26 -0000 Message-ID: <46F7C9A3.2080605@dgnetwork.com.br> Date: Mon, 24 Sep 2007 11:28:51 -0300 From: =?ISO-8859-1?Q?Daniel_Dias_Gon=E7alves?= Organization: DGNET Network Solutions User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 25 Sep 2007 08:28:28 +0000 Subject: GEOM_ELI Console Msgs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: daniel@dgnetwork.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: Mon, 24 Sep 2007 14:57:14 -0000 It is possible to disable the messages generated from GEOM_ELI in the console ? Thanks. Daniel From owner-freebsd-current@FreeBSD.ORG Mon Sep 24 14:57:14 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4850816A418 for ; Mon, 24 Sep 2007 14:57:14 +0000 (UTC) (envelope-from daniel@dgnetwork.com.br) Received: from mail.mastercabo.com.br (mail.mastercabo.com.br [200.179.179.14]) by mx1.freebsd.org (Postfix) with SMTP id 56D8C13C468 for ; Mon, 24 Sep 2007 14:57:12 +0000 (UTC) (envelope-from daniel@dgnetwork.com.br) Received: (qmail 15139 invoked by uid 1008); 24 Sep 2007 14:30:30 -0000 X-Spam-Checker-Version: SpamAssassin 3.1.7-unknown (2006-10-05) on srvmail2 X-Spam-Level: X-Spam-Status: No, score=-2.3 required=4.7 tests=AWL,BAYES_00 autolearn=ham version=3.1.7-unknown Received: from unknown (HELO ?10.0.0.10?) (daniel@dgnetwork.com.br@200.243.216.34) by mail.mastercabo.com.br with SMTP; 24 Sep 2007 14:30:26 -0000 Message-ID: <46F7C9A3.2080605@dgnetwork.com.br> Date: Mon, 24 Sep 2007 11:28:51 -0300 From: =?ISO-8859-1?Q?Daniel_Dias_Gon=E7alves?= Organization: DGNET Network Solutions User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 25 Sep 2007 08:28:28 +0000 Subject: GEOM_ELI Console Msgs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: daniel@dgnetwork.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: Mon, 24 Sep 2007 14:57:14 -0000 It is possible to disable the messages generated from GEOM_ELI in the console ? Thanks. Daniel From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 08:33:48 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A8A4116A419 for ; Tue, 25 Sep 2007 08:33:48 +0000 (UTC) (envelope-from jasone@freebsd.org) Received: from canonware.com (canonware.com [64.183.146.166]) by mx1.freebsd.org (Postfix) with ESMTP id 7256513C45A for ; Tue, 25 Sep 2007 08:33:48 +0000 (UTC) (envelope-from jasone@freebsd.org) Received: from [127.0.0.1] (canonware.com [64.183.146.166]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by canonware.com (Postfix) with ESMTP id E4ADA1298D6; Tue, 25 Sep 2007 01:41:09 -0700 (PDT) Message-ID: <46F8C7E9.50703@freebsd.org> Date: Tue, 25 Sep 2007 01:33:45 -0700 From: Jason Evans User-Agent: Thunderbird 1.5.0.13 (X11/20070824) MIME-Version: 1.0 To: Andrea Campi References: <20070923111808.GD31406@webcom.it> In-Reply-To: <20070923111808.GD31406@webcom.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: jemalloc malloc_usable_size() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 08:33:48 -0000 Andrea Campi wrote: > First of all, jemalloc makes no effort (neither here nor in free(3)) > to survive being called with non-malloc'ed pointers. If you do that > and asserts are on, you will get an abort, but if they are not your > process will likely die an horrible death--but there's no explicit > guarantee of that. I suppose that's fine (we are talking major WTFs > after all) in general, although it would be nice to have more control. > phkmalloc had more limit checking, so bad pointers (text / stack) were > reliably detected. > > Worse, malloc_usable_size() fails if you pass it a pointer inside a > malloc'ed region. Again, you get an assert if that's enable, otherwise > you probably get a random value. > The reason for this is in arena_salloc, where the passed pointer is > compared to the calculated page, to determine whether we are dealing > with a small or large allocation. > Unfortunately, I don't see an easy fix for this. For a bogus pointer, you can also get a segmentation fault, because the chunk and/or page may not even be mapped. There are numerous failure modes, and protecting against all of them requires very constraining data structure approaches. > Do you have any suggestion, or should I just give up on using > malloc_usable_size()? You should not call malloc_usable_size() with bogus arguments if you want to avoid undefined behavior. > As an aside: regardless of my purely educational exercise, what do you > guys think of putting such checks in the libc itself? The performance > impact is relatively small, and the benefits in terms of detecing and > preventing heap buffer overflows huge. That's all the more important > with jemalloc, which is (relatively) less safe that phkmalloc in fact > of such attacks. The performance impact of adding such safety nets is *not* small. In order to make arbitrary bogus realloc()/malloc_usable_size()/free() calls "safe", a substantial amount of locking is necessary, and conversion from O(1) to O(lg n) algorithms is necessary, since all pointers must be validated against an out-of-band database of valid pointers. The performance consequences are especially dire for multi-threaded applications. If you want a debugging malloc implementation, use something other than the system malloc. malloc cannot be made "safe" without substantial performance sacrifices. C's memory model is inherently dangerous, and it makes little sense to try to paper over that hard reality in the base system libraries. Jason From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 09:01:28 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7916C16A41A; Tue, 25 Sep 2007 09:01:28 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id CE30413C458; Tue, 25 Sep 2007 09:01:26 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F8CE67.60206@FreeBSD.org> Date: Tue, 25 Sep 2007 11:01:27 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Darren Reed References: <20070921102946.T11189@borg> <46F415BF.9010500@FreeBSD.org> <20070921140550.D96923@thebighonker.lerctr.org> <46F41CFF.6080108@FreeBSD.org> <46F58799.1030702@freebsd.org> <46F58B21.8030307@FreeBSD.org> <20070924091558.GB32006@team.vega.ru> <46F78C59.1020801@FreeBSD.org> <20070924080347.O84223@thebighonker.lerctr.org> <20070924144210.GA82735@team.vega.ru> <46F7D7A4.5090007@samsco.org> <46F80A39.3050707@FreeBSD.org> <46F8951C.50904@freebsd.org> In-Reply-To: <46F8951C.50904@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Larry Rosenman Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 09:01:28 -0000 Darren Reed wrote: > Kris Kennaway wrote: >> ... >> Well yes, that is one hypothesis, but the evidence points elsewhere as >> well. Prior the change you reference, some of my zfs machines would >> run for weeks before hitting a load pattern that exhausted their >> kmem_map and triggered the panic. Also unless I have missed it I am >> not seeing the sudden flood of panic reports that may indicate sudden >> breakage. It is quite possible that this particular report has >> nothing to do with the recent change. > > Indeed. > > But here's something else to ponder... > > I've been using ZFS since it was internal beta at Sun, at first on i386 > and later on amd64. > I've never run into this kind of panic on Solaris. System can get very > slow, yes, with > ZFS hogging lots of memory, but it never panic'd because of it. > > We need to come up with a strategy here to solve this problem, be it > fixing the kmem > virtual memory or fixing zfs. Yes, Solaris does something architecturally different because it is apparently acceptable for zfs to use gigabytes of memory by default. Kris From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 09:07:40 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 804F916A41A for ; Tue, 25 Sep 2007 09:07:40 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id C3D6613C458; Tue, 25 Sep 2007 09:07:39 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F8CFDC.70707@FreeBSD.org> Date: Tue, 25 Sep 2007 11:07:40 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: "S.N.Grigoriev" , "freebsd-current@freebsd.org >> FreeBSD Current" References: <1291921190632545@webmail31.yandex.ru> In-Reply-To: <1291921190632545@webmail31.yandex.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 09:07:40 -0000 S.N.Grigoriev wrote: > Hi, list, > > This problem has already been reported this year at least twice. > I can confirm it still exists. Probably it has been introduced > near the beginning of May because April and earlyer sources > handle parallel printing correctly. So we can cross-reference, what number is your PR? Kris From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 12:42:26 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57D8A16A417 for ; Tue, 25 Sep 2007 12:42:26 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout1.freenet.de (mout1.freenet.de [IPv6:2001:748:100:40::2:3]) by mx1.freebsd.org (Postfix) with ESMTP id 943FC13C43E for ; Tue, 25 Sep 2007 12:42:24 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from [195.4.92.20] (helo=mx10.freenet.de) by mout1.freenet.de with esmtpa (Exim 4.68-dev) (envelope-from ) id 1Ia9k7-0004Xn-9S for freebsd-current@freebsd.org; Tue, 25 Sep 2007 14:42:23 +0200 Received: from x06a5.x.pppool.de ([89.59.6.165]:64447 helo=peedub.jennejohn.org) by mx10.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.68-dev #12) id 1Ia9k5-0007UE-SB for freebsd-current@freebsd.org; Tue, 25 Sep 2007 14:42:22 +0200 Date: Tue, 25 Sep 2007 14:42:22 +0200 From: Gary Jennejohn To: freebsd-current@freebsd.org Message-ID: <20070925144222.33cb0f70@peedub.jennejohn.org> In-Reply-To: <20070925041717.W1660@small> References: <20070924051118.H9923@small> <200709241951.28762.sysinstall@gmx.net> <20070925041717.W1660@small> Organization: DENX Softwre Engineering GmbH X-Mailer: Claws Mail 3.0.0 (GTK+ 2.10.13; amd64-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 12:42:26 -0000 On Tue, 25 Sep 2007 04:18:32 +0200 (CEST) "P.U.Kruppa" wrote: > On Mon, 24 Sep 2007, Dieter Franzke wrote: > > > Hi, > > > > P.U.Kruppa am Montag, 24. September 2007: > >> Hello, > >> > >> I use a HP Deskjet 990 Cxi via parallel port with cups and hpijs > >> driver on > >> > >> FreeBSD pukruppa.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Sep > >> 21 16:52:59 CEST 2007 amd64 > >> > >> When I try to print a little bit more complex documents > >> (OpenOffice, pdf) my System will crash. > >> > >> On my root terminal there will be a long list of > >> lpt0: [ITHREAD] > >> lpt0: [GIANT-LOCKED] > >> lpt0: [ITHREAD] > >> [...] > >> lines, then some dumping activity and a reboot. > >> > >> I upgraded to 7.0 last week, so all I can say is: everything was > >> fine with 6.2 . > >> > >> Please tell me if you need more information. > > > > I've had the same here. > > Enabling polling via "lptcontrol -p /dev/lpt0" solved the problem. > Indeed! > Thanks! > To automate it add hint.ppc.0.flags="0x20" to /boot/device.hints -- Gary Jennejohn From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 13:31:10 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B268016A41B for ; Tue, 25 Sep 2007 13:31:10 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.freebsd.org (Postfix) with ESMTP id 6E88B13C448 for ; Tue, 25 Sep 2007 13:31:10 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from parancell.ongs.co.jp (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id B4E0E244C3A; Tue, 25 Sep 2007 21:58:37 +0900 (JST) Message-ID: <46F905FD.9060208@freebsd.org> Date: Tue, 25 Sep 2007 21:58:37 +0900 From: Daichi GOTO User-Agent: Thunderbird 2.0.0.6 (X11/20070803) MIME-Version: 1.0 To: FreeBSD Current Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Masanori OZAWA Subject: The safety expansion for FreeBSD rm(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 13:31:10 -0000 Hi Guys again Today is not unionfs. Introduction for safety expansion of rm(1). I know that some unix folks have a experience that you remove some files or directories accidentally. Yes, me too. LoL Have you any dreams that rm(1) autonomously judges target should be remove or not? To complexify system base command is objectionable behavior but adding some little and simple mechanism to prevent a issue is acceptable I suppose. We have created safety expansion for rm(1). If you have any interests, please try follow patch. http://people.freebsd.org/~daichi/safety-rm/ Thanks :) -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 13:37:39 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 244A116A417 for ; Tue, 25 Sep 2007 13:37:39 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id 641D913C474 for ; Tue, 25 Sep 2007 13:37:38 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id l8PDaEb9002829; Tue, 25 Sep 2007 15:36:22 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id l8PDaEXN002828; Tue, 25 Sep 2007 15:36:14 +0200 (CEST) (envelope-from olli) Date: Tue, 25 Sep 2007 15:36:14 +0200 (CEST) Message-Id: <200709251336.l8PDaEXN002828@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG, Alexandre Biancalana In-Reply-To: <46F490A8.2010004@freebsd.org> X-Newsgroups: list.freebsd-current User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 25 Sep 2007 15:36:22 +0200 (CEST) Cc: Subject: Re: process size X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@FreeBSD.ORG, Alexandre Biancalana List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 13:37:39 -0000 Jason Evans wrote: > Alexandre Biancalana wrote: > > I agree that this could be the problem... but I´m not running i386. > > > > # uname -a > > FreeBSD 7.0-CURRENT FreeBSD 7.0-CURRENT #2: Fri Sep 21 18:06:33 BRT > > 2007 root@:/usr/obj/usr/src/sys/BACKUP amd64 > > Hmm, okay, so much for that theory. I blame rsync. You could give cpdup a try (from ports/sysutils/cpdup). It grew remote sync support recently, too (tunnelled through ssh). Works fine for me, but I haven't used it for syncing very large file systems so far. However, it always copies the whole file if it detects a difference (it doesn't transfer only the diffs), so it's somewhat less efficient, depending on the usage. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "That's what I love about GUIs: They make simple tasks easier, and complex tasks impossible." -- John William Chambless From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 14:46:24 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE42A16A418 for ; Tue, 25 Sep 2007 14:46:24 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 720FC13C469 for ; Tue, 25 Sep 2007 14:46:24 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IaBTO-000839-Ib for freebsd-current@freebsd.org; Tue, 25 Sep 2007 14:33:14 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 25 Sep 2007 14:33:14 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 25 Sep 2007 14:33:14 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Tue, 25 Sep 2007 16:17:37 +0200 Lines: 37 Message-ID: References: <46F905FD.9060208@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enig41AE300EAFEF1C493188DE6E" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 1.5.0.12 (X11/20060911) In-Reply-To: <46F905FD.9060208@freebsd.org> X-Enigmail-Version: 0.94.4.0 Sender: news Subject: Re: The safety expansion for FreeBSD rm(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 14:46:24 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig41AE300EAFEF1C493188DE6E Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Daichi GOTO wrote: > Hi Guys again >=20 > Today is not unionfs.=20 How is the unionfs patch progressing through re ? :) I hope it gets=20 digested soon :) > We have created safety expansion for rm(1). If you have any interests, > please try follow patch. >=20 > http://people.freebsd.org/~daichi/safety-rm/ This looks useful, but shouldn't this feature be handled more globally,=20 with a MAC policy or something like that? --------------enig41AE300EAFEF1C493188DE6E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG+RiHldnAQVacBcgRAyeZAKDRGofLg1ww1FbheoLvOppKYBqCqgCfS3Y8 G7772IoijDl0vkcQWS+l7s4= =fJ8E -----END PGP SIGNATURE----- --------------enig41AE300EAFEF1C493188DE6E-- From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 15:30:02 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24EFF16A481 for ; Tue, 25 Sep 2007 15:30:02 +0000 (UTC) (envelope-from ravna@nerdshack.com) Received: from karen.lavabit.com (karen.lavabit.com [72.249.41.33]) by mx1.freebsd.org (Postfix) with ESMTP id E818413C468 for ; Tue, 25 Sep 2007 15:30:01 +0000 (UTC) (envelope-from ravna@nerdshack.com) Received: from dispatchd.nerdshack.com (jean.lavabit.com [72.249.41.30]) by karen.lavabit.com (Postfix) with SMTP id 838FAC842F for ; Tue, 25 Sep 2007 09:59:24 -0500 (CDT) Received: from toy.firlefanz.org (p54ABF12B.dip.t-dialin.net [84.171.241.43]) by mail.nerdshack.com with ESMTP Tue, 25 Sep 2007 09:59:24 -0500 Message-ID: <46F921ED.2090901@nerdshack.com> Date: Tue, 25 Sep 2007 16:57:49 +0200 From: Ravna User-Agent: Thunderbird 2.0.0.6 (X11/20070908) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Reboot after mount of already mounted disk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 15:30:02 -0000 I'm running 7-Current built on 09/15 . When accidentially trying to mount a NTFS disk that was already mounted, the system rebooted. The message I got was: "lockmgr locking against itself." I did this several times on purpose, with NTFS and EXT2 disks, with the same result. UFS2 disks seem unaffected. From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 16:33:33 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46B0416A537 for ; Tue, 25 Sep 2007 16:33:33 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.freebsd.org (Postfix) with ESMTP id EB20213C43E for ; Tue, 25 Sep 2007 16:33:32 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from gotou-daichi-nokonpyuta.local (east61-p181.eaccess.hi-ho.ne.jp [219.105.23.182]) by natial.ongs.co.jp (Postfix) with ESMTP id B6BEB244C3A; Wed, 26 Sep 2007 01:33:31 +0900 (JST) Message-ID: <46F9384E.5010409@freebsd.org> Date: Wed, 26 Sep 2007 01:33:18 +0900 From: Daichi GOTO User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Ivan Voras References: <46F905FD.9060208@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: The safety expansion for FreeBSD rm(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 16:33:33 -0000 Ivan Voras wrote: > Daichi GOTO wrote: >> Hi Guys again >> >> Today is not unionfs. > > How is the unionfs patch progressing through re ? :) I hope it gets > digested soon :) I have sent a aprove request to re@ and been waiting for replay. I have a hope to get aproval mail too :) I beleive in that recent unionfs patches bunch is well viewed and working very good. >> We have created safety expansion for rm(1). If you have any interests, >> please try follow patch. >> >> http://people.freebsd.org/~daichi/safety-rm/ > > This looks useful, but shouldn't this feature be handled more globally, > with a MAC policy or something like that? Yes, that is not depending to MAC or other comprehensive access framework. At the beginning, what's important is that I have anyone needs that feature or not ;-) If someone needs that feature, I will get the work of more comprehensive mechanism. From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 17:36:24 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A37416A417 for ; Tue, 25 Sep 2007 17:36:24 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42]) by mx1.freebsd.org (Postfix) with ESMTP id 7EDEF13C45B for ; Tue, 25 Sep 2007 17:36:23 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from epia-2.farid-hajji.net (epia-2 [192.168.254.11]) by fw.farid-hajji.net (Postfix) with ESMTP id AE41FDFDD6; Tue, 25 Sep 2007 19:37:54 +0200 (CEST) Date: Tue, 25 Sep 2007 19:40:08 +0200 From: cpghost To: Daichi GOTO Message-ID: <20070925194008.3c2d7113@epia-2.farid-hajji.net> In-Reply-To: <46F905FD.9060208@freebsd.org> References: <46F905FD.9060208@freebsd.org> Organization: Cordula's Web X-Mailer: Claws Mail 3.0.0 (GTK+ 2.10.14; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , Masanori OZAWA Subject: Re: The safety expansion for FreeBSD rm(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 17:36:24 -0000 On Tue, 25 Sep 2007 21:58:37 +0900 Daichi GOTO wrote: > Today is not unionfs. Introduction for safety expansion of rm(1). > I know that some unix folks have a experience that you remove some > files or directories accidentally. Yes, me too. LoL > > Have you any dreams that rm(1) autonomously judges target should > be remove or not? To complexify system base command is objectionable > behavior but adding some little and simple mechanism to prevent a > issue is acceptable I suppose. > > We have created safety expansion for rm(1). If you have any interests, > please try follow patch. > > http://people.freebsd.org/~daichi/safety-rm/ > > Thanks :) Interesting idea, but isn't that a violation of POLA? Imagine an unsuspecting sysadmin trying to rm something, and forgetting or not knowing about ~/.rm? Isn't it better to protect important system directories with something like: # chflags sunlink /path/to/dir and unprotect them with # chflags nosunlink /path/to/dir to avoid mistakes? Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/ From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 17:52:59 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A374016A46C for ; Tue, 25 Sep 2007 17:52:59 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id DC62B13C45B; Tue, 25 Sep 2007 17:52:58 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F94AFC.1000808@FreeBSD.org> Date: Tue, 25 Sep 2007 19:53:00 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: gary.jennejohn@freenet.de References: <20070924051118.H9923@small> <200709241951.28762.sysinstall@gmx.net> <20070925041717.W1660@small> <20070925144222.33cb0f70@peedub.jennejohn.org> In-Reply-To: <20070925144222.33cb0f70@peedub.jennejohn.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 17:52:59 -0000 Gary Jennejohn wrote: > On Tue, 25 Sep 2007 04:18:32 +0200 (CEST) > "P.U.Kruppa" wrote: > >> On Mon, 24 Sep 2007, Dieter Franzke wrote: >> >>> Hi, >>> >>> P.U.Kruppa am Montag, 24. September 2007: >>>> Hello, >>>> >>>> I use a HP Deskjet 990 Cxi via parallel port with cups and hpijs >>>> driver on >>>> >>>> FreeBSD pukruppa.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Sep >>>> 21 16:52:59 CEST 2007 amd64 >>>> >>>> When I try to print a little bit more complex documents >>>> (OpenOffice, pdf) my System will crash. >>>> >>>> On my root terminal there will be a long list of >>>> lpt0: [ITHREAD] >>>> lpt0: [GIANT-LOCKED] >>>> lpt0: [ITHREAD] >>>> [...] >>>> lines, then some dumping activity and a reboot. >>>> >>>> I upgraded to 7.0 last week, so all I can say is: everything was >>>> fine with 6.2 . >>>> >>>> Please tell me if you need more information. >>> I've had the same here. >>> Enabling polling via "lptcontrol -p /dev/lpt0" solved the problem. >> Indeed! >> Thanks! >> > > To automate it add > hint.ppc.0.flags="0x20" > to /boot/device.hints > Please, can we focus on fixing the problem instead of institutionalizing workarounds? :) Kris From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 18:02:09 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC6A216A419 for ; Tue, 25 Sep 2007 18:02:09 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id 2A66313C459 for ; Tue, 25 Sep 2007 18:02:08 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id l8PI0l13013109; Tue, 25 Sep 2007 20:00:53 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id l8PI0lof013108; Tue, 25 Sep 2007 20:00:47 +0200 (CEST) (envelope-from olli) Date: Tue, 25 Sep 2007 20:00:47 +0200 (CEST) Message-Id: <200709251800.l8PI0lof013108@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG, Masanori OZAWA , Masanori OZAWA In-Reply-To: <46F905FD.9060208@freebsd.org> X-Newsgroups: list.freebsd-current User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 25 Sep 2007 20:00:53 +0200 (CEST) Cc: Subject: Re: The safety expansion for FreeBSD rm(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@FreeBSD.ORG, Masanori OZAWA List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 18:02:09 -0000 Daichi GOTO wrote: > Have you any dreams that rm(1) autonomously judges target should > be remove or not? To complexify system base command is objectionable > behavior but adding some little and simple mechanism to prevent a > issue is acceptable I suppose. I think it could cause confusion for some users or admins. It could also be dangerous. I remember an emergency case when /home was an NFS mount that was dead, i.e. every process that tried to access something in /home just hung forever in state "D" (disk wait). During the emergency actions on the serial console I also needed to use the rm(1) command ... Now if it tried to read ~/.rm, it would have drawn me mouch deeper into trouble than I already were. :-) True, the -f option would have prevented it, _if_ I remembered before to use it. A common precaution against accidental rm is to establish a snapshot rotation system. For example, create hourly snapshots (with a cron job) and delete them automatically after a while. So if you accidentally remove something, you can copy it back from the latest snapshot. NetApp Filers have such a feature built-in. You can also easily set it up yourself with ZFS, or even with UFS snapshots, although the latter are a bit heavyweight, IMHO. And finally, there is chflags(1). If you know in advance that certain files or directories must not be removed, then "chflags schg" or "chflags uchg" them. That's the same effect as creating a ~/.rm file with your patch. Another advantage of chflags(1) is that it also protects against other kinds of damage. For example when using shell redirection ("echo > some/important/file"), cp, dd or other commands. In those cases chflags also offers protection (and a snapshot would offer recovery), while your patch only protects against rm and nothing else. Just my 2 cents. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "It combines all the worst aspects of C and Lisp: a billion different sublanguages in one monolithic executable. It combines the power of C with the readability of PostScript." -- Jamie Zawinski, when asked: "What's wrong with perl?" From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 18:33:20 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E996A16A41B; Tue, 25 Sep 2007 18:33:20 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (cl-162.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:a1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 500B913C494; Tue, 25 Sep 2007 18:33:20 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.13.8/8.13.8) with ESMTP id l8PIXDnu078930; Tue, 25 Sep 2007 13:33:13 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.13.8/8.13.8/Submit) id l8PIXDhe078929; Tue, 25 Sep 2007 13:33:13 -0500 (CDT) (envelope-from brooks) Date: Tue, 25 Sep 2007 13:33:13 -0500 From: Brooks Davis To: cpghost Message-ID: <20070925183313.GB78038@lor.one-eyed-alien.net> References: <46F905FD.9060208@freebsd.org> <20070925194008.3c2d7113@epia-2.farid-hajji.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WYTEVAkct0FjGQmd" Content-Disposition: inline In-Reply-To: <20070925194008.3c2d7113@epia-2.farid-hajji.net> User-Agent: Mutt/1.5.15 (2007-04-06) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Tue, 25 Sep 2007 13:33:13 -0500 (CDT) Cc: Daichi GOTO , Masanori OZAWA , FreeBSD Current Subject: Re: The safety expansion for FreeBSD rm(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 18:33:21 -0000 --WYTEVAkct0FjGQmd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 25, 2007 at 07:40:08PM +0200, cpghost wrote: > On Tue, 25 Sep 2007 21:58:37 +0900 > Daichi GOTO wrote: >=20 > > Today is not unionfs. Introduction for safety expansion of rm(1). > > I know that some unix folks have a experience that you remove some > > files or directories accidentally. Yes, me too. LoL > >=20 > > Have you any dreams that rm(1) autonomously judges target should > > be remove or not? To complexify system base command is objectionable > > behavior but adding some little and simple mechanism to prevent a > > issue is acceptable I suppose. > >=20 > > We have created safety expansion for rm(1). If you have any interests, > > please try follow patch. > >=20 > > http://people.freebsd.org/~daichi/safety-rm/ > >=20 > > Thanks :) >=20 > Interesting idea, but isn't that a violation of POLA? Imagine an > unsuspecting sysadmin trying to rm something, and forgetting > or not knowing about ~/.rm? All they have to do is specify -f and ~/.rm is ignored so I don't think it's that big a deal. It does raise the potential of werid side effects in scri= pts, but since you have to deploy ~/.rm files for anything to happen, I don't se= e it as that big a deal. It might be useful to have the ability to turn off ~/.= rm support via an environmental variable. > Isn't it better to protect important system directories with > something like: > # chflags sunlink /path/to/dir > and unprotect them with > # chflags nosunlink /path/to/dir > to avoid mistakes? The above change means you have to apply the hammer of chflags to do anything. The patch lets you specify certain directories where you're prompted instead. I see that as much more useful. -- Brooks --WYTEVAkct0FjGQmd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFG+VRoXY6L6fI4GtQRAlfpAJ9Exv7yLuGmqFhqqno/DQkLRzspjwCfQwko b7dA8pUxmh1M3p+ZnzqpTCc= =ZlGD -----END PGP SIGNATURE----- --WYTEVAkct0FjGQmd-- From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 18:36:34 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C663616A418 for ; Tue, 25 Sep 2007 18:36:34 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 6759013C459 for ; Tue, 25 Sep 2007 18:36:34 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IaFGY-0005UL-Db for freebsd-current@freebsd.org; Tue, 25 Sep 2007 18:36:14 +0000 Received: from r5j156.net.upc.cz ([86.49.9.156]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 25 Sep 2007 18:36:14 +0000 Received: from gamato by r5j156.net.upc.cz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 25 Sep 2007 18:36:14 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: martinko Date: Tue, 25 Sep 2007 20:35:44 +0200 Lines: 16 Message-ID: References: <200709132302.l8DN2Tv5076033@repoman.freebsd.org> <46E9FC0C.70607@FreeBSD.org> <46F1A96F.2040602@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: r5j156.net.upc.cz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.6) Gecko/20070821 SeaMonkey/1.1.4 In-Reply-To: Sender: news Subject: Re: GSoC2007: cnst-sensors.2007-09-13.patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 18:36:34 -0000 Chuck Swiger wrote: > > The threshold temperature varies depending on the exact part, but is > generally around 65 Celsius-- and is hot enough that you don't really > want to encounter it in normal operation, as it's a sign that cooling is > not adequate for the system to continue to operate safely at full > speed. Most of the Intel CPUs also include a second thermal circuit > called THERMTRIP which fires around 95 Celsius which will shut the CPU > down entirely to prevent a catastrophic failure. > I've got Pentium-M at 2GHz and when fully loaded it heats up to 79 Celsius. Could it be OK or do I have a faulty laptop ? M. From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 18:43:21 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA8EC16A418; Tue, 25 Sep 2007 18:43:21 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (cl-162.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:a1::2]) by mx1.freebsd.org (Postfix) with ESMTP id F0F6913C4A7; Tue, 25 Sep 2007 18:43:20 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.13.8/8.13.8) with ESMTP id l8PIhIJr079038; Tue, 25 Sep 2007 13:43:18 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.13.8/8.13.8/Submit) id l8PIhIQ4079037; Tue, 25 Sep 2007 13:43:18 -0500 (CDT) (envelope-from brooks) Date: Tue, 25 Sep 2007 13:43:18 -0500 From: Brooks Davis To: Daichi GOTO Message-ID: <20070925184318.GC78038@lor.one-eyed-alien.net> References: <46F905FD.9060208@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="O3RTKUHj+75w1tg5" Content-Disposition: inline In-Reply-To: <46F905FD.9060208@freebsd.org> User-Agent: Mutt/1.5.15 (2007-04-06) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Tue, 25 Sep 2007 13:43:20 -0500 (CDT) Cc: FreeBSD Current , Masanori OZAWA Subject: Re: The safety expansion for FreeBSD rm(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 18:43:21 -0000 --O3RTKUHj+75w1tg5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 25, 2007 at 09:58:37PM +0900, Daichi GOTO wrote: > Hi Guys again >=20 > Today is not unionfs. Introduction for safety expansion of rm(1). > I know that some unix folks have a experience that you remove some > files or directories accidentally. Yes, me too. LoL >=20 > Have you any dreams that rm(1) autonomously judges target should > be remove or not? To complexify system base command is objectionable > behavior but adding some little and simple mechanism to prevent a > issue is acceptable I suppose. >=20 > We have created safety expansion for rm(1). If you have any interests, > please try follow patch. >=20 > http://people.freebsd.org/~daichi/safety-rm/ >=20 > Thanks :) This seems like an interesting extension of rm(1) in a fairly harmless mann= er. It seems like a fairly logical extension of the tcsh rmstar variable. The one concern I would have with it is that unlike the rmstar variable, it wou= ld always run even if the rm command is run in a script. What do you think of adding a flag to enable this behavior so users could make rm an alias that uses the flag? That would keep it from effecting scripts. -- Brooks --O3RTKUHj+75w1tg5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFG+VbGXY6L6fI4GtQRAuK6AKDhAjUbKgFp7Gi7/IV5z0GTnbplmQCfVQQA uX1mkIDdV7R15ukGY1SmkKQ= =Eodd -----END PGP SIGNATURE----- --O3RTKUHj+75w1tg5-- From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 18:47:48 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D19516A418 for ; Tue, 25 Sep 2007 18:47:48 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.auburn.protected-networks.net (mail.auburn.protected-networks.net [202.12.127.85]) by mx1.freebsd.org (Postfix) with ESMTP id 2522E13C48D for ; Tue, 25 Sep 2007 18:47:48 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from localhost (localhost.auburn.protected-networks.net [127.0.0.1]) by mail.auburn.protected-networks.net (Postfix) with ESMTP id 6F6A41708D for ; Tue, 25 Sep 2007 14:33:48 -0400 (EDT) Received: from mail.auburn.protected-networks.net (localhost.auburn.protected-networks.net [127.0.0.1]) by mail.auburn.protected-networks.net (Postfix) with ESMTP id 760BE17029 for ; Tue, 25 Sep 2007 14:33:12 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=protected-networks.net; s=200705; t=1190745192; bh=x+3boBERAEJ/53 peV1xBcg/UexOCrYtI/vbdMg/8Ipo=; h=DomainKey-Signature:Message-ID: Date:Subject:From:To:User-Agent:MIME-Version:Content-Type: Content-Transfer-Encoding:X-Priority:Importance; b=mNye0W4GS4viNqx 37S4lbhMiBeFiQ/25H4TFLc40cazlT0hqGSdFgHojZMQwEtXtjxhhH8OIuG31PenPfk wpFL7qn9BbYf7aHFNafkxWmpRyntlHMkwEirHUCSs8MdnM DomainKey-Signature: a=rsa-sha1; s=200509; d=protected-networks.net; c=nofws; q=dns; h=received:message-id:date:subject:from:to:user-agent: mime-version:content-type:content-transfer-encoding:x-priority:importance; b=f6bDeAkXCP0fLmzpvHg+YwpEqnH3TJd67yElpRwRMjsaXuffCQ+aTbFz0dJj4CII9 3BxSoyx79FNt9KfGXTsrqjKAXJbUFDQX5soDELYttIq4PxZKh1oBOqToeFJzrFI Received: from 64.119.130.186 (SquirrelMail authenticated user imb) by mail.auburn.protected-networks.net with HTTP; Tue, 25 Sep 2007 12:33:12 -0600 (MDT) Message-ID: <3161.64.119.130.186.1190745192.squirrel@mail.auburn.protected-networks.net> Date: Tue, 25 Sep 2007 12:33:12 -0600 (MDT) From: "Michael Butler" To: freebsd-current@freebsd.org User-Agent: SquirrelMail/1.4.10a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: 64/128 bucket allocation failures X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 18:47:48 -0000 I'm seeing these allocation failures on a -current box (today's) with more than enough free RAM .. imb@toshi:/home/imb> vmstat -z ITEM SIZE LIMIT USED FREE REQUESTS FAILURES UMA Kegs: 128, 0, 76, 14, 76, 0 UMA Zones: 480, 0, 76, 4, 76, 0 UMA Slabs: 64, 0, 2647, 8, 25743, 0 UMA RCntSlabs: 104, 0, 237, 22, 237, 0 UMA Hash: 128, 0, 5, 25, 8, 0 16 Bucket: 76, 0, 52, 48, 70, 0 32 Bucket: 140, 0, 63, 21, 83, 0 64 Bucket: 268, 0, 116, 10, 165, 11 128 Bucket: 524, 0, 591, 4, 1316, 11270 [ .. snip .. ] imb@toshi:/home/imb> top -d 1 last pid: 22624; load averages: 0.00, 0.00, 0.00 up 0+03:13:42 14:31:16 49 processes: 1 running, 48 sleeping CPU states: % user, % nice, % system, % interrupt, % idle Mem: 97M Active, 606M Inact, 246M Wired, 844K Cache, 112M Buf, 1044M Free Swap: 1024M Total, 1024M Free Any ideas? Michael From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 18:57:36 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D47B516A41A; Tue, 25 Sep 2007 18:57:36 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.freebsd.org (Postfix) with ESMTP id 55BC913C44B; Tue, 25 Sep 2007 18:57:36 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by koef.zs64.net (8.14.1/8.14.1) with ESMTP id l8PIWmcq038699; Tue, 25 Sep 2007 20:32:48 +0200 (CEST) (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.14.1/8.14.1/Submit) id l8PIWmE9038698; Tue, 25 Sep 2007 14:32:48 -0400 (EDT) (envelope-from cracauer) Date: Tue, 25 Sep 2007 14:32:48 -0400 From: Martin Cracauer To: Daichi GOTO Message-ID: <20070925183248.GA38571@cons.org> References: <46F905FD.9060208@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46F905FD.9060208@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: FreeBSD Current , Masanori OZAWA Subject: Re: The safety expansion for FreeBSD rm(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 18:57:36 -0000 My idea of a safety feature for rm(1): To solve the problem of doing rm foo * instead of rm foo* Look at what the commandline arguments are. If at least - one is appearing twice - or at least one is not appearing at all , then do a "*" expand like from a shell (not perfect of course not easy enough) and see whether all elements of "*" are there *plus* others with no "/". If so, the above situation occured and you only go ahead with a special flag. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 19:38:38 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CAE416A418; Tue, 25 Sep 2007 19:38:38 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.freebsd.org (Postfix) with ESMTP id B3DD413C455; Tue, 25 Sep 2007 19:38:37 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.6/8.13.6) with ESMTP id l8PJcZOr089877; Tue, 25 Sep 2007 15:38:35 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-current@FreeBSD.org Date: Tue, 25 Sep 2007 15:38:31 -0400 User-Agent: KMail/1.6.2 References: <200709181516.11207.jkim@FreeBSD.org> <200709241259.01518.jkim@FreeBSD.org> <46F7EDD6.4010508@root.org> In-Reply-To: <46F7EDD6.4010508@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200709251538.33353.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.90.2/4396/Tue Sep 25 14:48:03 2007 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-acpi@FreeBSD.org, John Baldwin , Nate Lawson Subject: Re: [PATCH] OsdSynch.c modernization X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 19:38:38 -0000 On Monday 24 September 2007 01:03 pm, Nate Lawson wrote: > Jung-uk Kim wrote: > > (At least on my laptop) I found the malloc() was called from our > > code, i.e., AcpiOsExecute() from OsdSched.c. I'll try something > > shortly cause I was going to rewrite the file anyway. > > Yep, that's because we need a task structure that's different for > each call and acpi-ca doesn't like the "pending" argument (see > OsdSchedule.c). One fix for this is to just use a hack and cast > the fn to discard the extra arg. Not sure this would work. I quickly tested it but didn't work. :-( Actually it is not just pending argument but struct task itself has to be allocated. I did crude hack to see if it is possible to have it working with spin mutex gracefully. It can be done if we pre-allocate some space for the tasks and use fast taskqueue. Does it make sense to you? Thanks, Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 19:54:46 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9605316A41B for ; Tue, 25 Sep 2007 19:54:46 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id CD8C213C467; Tue, 25 Sep 2007 19:54:45 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F96787.20406@FreeBSD.org> Date: Tue, 25 Sep 2007 21:54:47 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: "S.N.Grigoriev" References: <1291921190632545@webmail31.yandex.ru> 9070000000021720668 <71531190719695@webmail24.yandex.ru> In-Reply-To: <71531190719695@webmail24.yandex.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 19:54:46 -0000 S.N.Grigoriev wrote: > 25.09.07, 13:07, Kris Kennaway (kris@FreeBSD.org): > >> S.N.Grigoriev wrote: >>> Hi, list, >>> >>> This problem has already been reported this year at least twice. >>> I can confirm it still exists. Probably it has been introduced >>> near the beginning of May because April and earlyer sources >>> handle parallel printing correctly. >> So we can cross-reference, what number is your PR? >> Kris > > Hi, Kris, > > The following messages posted to freebsd-current@ > this year: That's not what I asked. If you discover a bug and it doesn't get solved right away when you send email to a mailing list, your next step is supposed to be filing a bug report so that the issue gets tracked. Better late than never, so can you please do so now? Kris From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 21:37:43 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3AF2816A41A; Tue, 25 Sep 2007 21:37:43 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.freebsd.org (Postfix) with ESMTP id D520013C447; Tue, 25 Sep 2007 21:37:42 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.6/8.13.6) with ESMTP id l8PLbfQk098394; Tue, 25 Sep 2007 17:37:41 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-current@FreeBSD.org Date: Tue, 25 Sep 2007 17:37:34 -0400 User-Agent: KMail/1.6.2 References: <200709181516.11207.jkim@FreeBSD.org> <46F7EDD6.4010508@root.org> <200709251538.33353.jkim@FreeBSD.org> In-Reply-To: <200709251538.33353.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200709251737.38780.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.90.2/4396/Tue Sep 25 14:48:03 2007 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-acpi@FreeBSD.org, John Baldwin , Nate Lawson Subject: Re: [PATCH] OsdSynch.c modernization X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 21:37:43 -0000 On Tuesday 25 September 2007 03:38 pm, Jung-uk Kim wrote: > On Monday 24 September 2007 01:03 pm, Nate Lawson wrote: > > Jung-uk Kim wrote: > > > (At least on my laptop) I found the malloc() was called from > > > our code, i.e., AcpiOsExecute() from OsdSched.c. I'll try > > > something shortly cause I was going to rewrite the file anyway. > > > > Yep, that's because we need a task structure that's different for > > each call and acpi-ca doesn't like the "pending" argument (see > > OsdSchedule.c). One fix for this is to just use a hack and cast > > the fn to discard the extra arg. Not sure this would work. > > I quickly tested it but didn't work. :-( > > Actually it is not just pending argument but struct task itself has > to be allocated. I did crude hack to see if it is possible to have > it working with spin mutex gracefully. It can be done if we > pre-allocate some space for the tasks and use fast taskqueue. Does > it make sense to you? FYI, here is the hack: http://people.freebsd.org/~jkim/acpica/Osd.diff Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 22:43:22 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93D7816A420 for ; Tue, 25 Sep 2007 22:43:22 +0000 (UTC) (envelope-from SRS0=8d06338667b7359965bc8eba8c63f618734e4dfc=469=es.net=oberman@es.net) Received: from postal1.es.net (postal2.es.net [IPv6:2001:400:14:3::7]) by mx1.freebsd.org (Postfix) with ESMTP id 1A61713C447 for ; Tue, 25 Sep 2007 22:43:21 +0000 (UTC) (envelope-from SRS0=8d06338667b7359965bc8eba8c63f618734e4dfc=469=es.net=oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id EFQ83818; Tue, 25 Sep 2007 15:43:18 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 33A6645012; Tue, 25 Sep 2007 15:43:18 -0700 (PDT) To: martinko In-Reply-To: Your message of "Tue, 25 Sep 2007 20:35:44 +0200." Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1190760198_65440P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Tue, 25 Sep 2007 15:43:18 -0700 From: "Kevin Oberman" Message-Id: <20070925224318.33A6645012@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ;; X-Sender: X-To_Name: martinko X-To_Domain: users.sf.net X-To: martinko X-To_Email: gamato@users.sf.net X-To_Alias: gamato Cc: freebsd-current@freebsd.org Subject: Re: GSoC2007: cnst-sensors.2007-09-13.patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 22:43:22 -0000 --==_Exmh_1190760198_65440P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > From: martinko > Date: Tue, 25 Sep 2007 20:35:44 +0200 > Sender: owner-freebsd-current@freebsd.org > > Chuck Swiger wrote: > > > > The threshold temperature varies depending on the exact part, but is > > generally around 65 Celsius-- and is hot enough that you don't really > > want to encounter it in normal operation, as it's a sign that cooling is > > not adequate for the system to continue to operate safely at full > > speed. Most of the Intel CPUs also include a second thermal circuit > > called THERMTRIP which fires around 95 Celsius which will shut the CPU > > down entirely to prevent a catastrophic failure. > > > > > I've got Pentium-M at 2GHz and when fully loaded it heats up to 79 > Celsius. Could it be OK or do I have a faulty laptop ? My Pentium-M 2GHz system will get well above 80C when doing big builds and this is well below the defined PSV (94.5C) and CRT (99C) levels. These things can run very hot and be perfectly happy. OTOH, it might be time to clean the heatsink in the machine. That can hurt heat transfer as a machine gets older. FWIW, the spec on the Pentium-M 2GHZ system is 105C, so CRT at 99 looks right. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1190760198_65440P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFG+Y8Gkn3rs5h7N1ERAq0kAKCVchfPUitsI5iRmMjfJ1lKd1o4mwCgi+y1 n7PvQi9Yi5rmJ8Cjln7jbhw= =AEIr -----END PGP SIGNATURE----- --==_Exmh_1190760198_65440P-- From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 00:48:54 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A394916A41A for ; Wed, 26 Sep 2007 00:48:54 +0000 (UTC) (envelope-from drumslayer2@yahoo.com) Received: from web63413.mail.re1.yahoo.com (web63413.mail.re1.yahoo.com [69.147.97.53]) by mx1.freebsd.org (Postfix) with SMTP id 2AF1713C469 for ; Wed, 26 Sep 2007 00:48:53 +0000 (UTC) (envelope-from drumslayer2@yahoo.com) Received: (qmail 11447 invoked by uid 60001); 26 Sep 2007 00:48:52 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=DNQB4vj1ul5WUbAFfkalpqov2zYSHTBeyrXHq2bByermxw3A2nSu9740cy5IUTKTvR5TyFsZHN1x8viVJr97tSaEsvBZW743oeIakgb4206o/SatWIE7t4wns5Lx0xatDDmWz+wKzSDGe5cu8jZsabam1ktJXJOOaTrWH3mtCek=; X-YMail-OSG: D_cfNhEVM1npMQ6YBxHo_CyyH4hv_mBd5oOIxIIzi3w1FPujpENrcXHY00rjTKryWcozkvA2muz_El9m3rvKB4i2lQ_.JGNs3xzXeW_ecCrI.UjdS5vKnM4mCSNYrQj5MSBiDOprdf92JHg- Received: from [67.112.21.27] by web63413.mail.re1.yahoo.com via HTTP; Tue, 25 Sep 2007 17:48:52 PDT Date: Tue, 25 Sep 2007 17:48:52 -0700 (PDT) From: "N. Harrington" To: FreeBSD Current MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <363087.11106.qm@web63413.mail.re1.yahoo.com> Subject: Unable to install Current Snapshot ISO via USB attached CD drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 00:48:54 -0000 Hello I am using both a Tyan S2881 and S2882 motherboard with Opteron Processor. I have been trying to install the 7.X amd64 snapshot for some time now via A USB attached CD rom, (same as I always have for 4, 5 and 6) But when using a 7 snapshot disk, the install always borks at the same place. I can install the snapshots just fine if I ATA attach to the cd unit, but I cannot if the CD unit is connected via USB. The errors are always: F1 screen Write failure transfer! (wrote -1 bytes of 1425408 bytes) F2 screen .... /stand/gunzip : : too many length or distance symbols /stand/cpio: premature end of file F1 Retry: Write Failure On Transfer Wrote -1 bytes of 1425408 bytes /stand/gunzip : invalid code length set Being able to install via USB is very important to me. It seems a shame 7 would be broken in this way. Might anyone know what could be happening? I can swap the disk with a 6.X disk and it ill install via USB just fine. I also cannot install To a USB attached drive using 7, but I can with 6. I have tried with the last 3 snapshots up to 200709. Thanks! Nicole The Large Print Giveth And The Small Print Taketh Away -- Anon From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 05:06:04 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78E0B16A419 for ; Wed, 26 Sep 2007 05:06:04 +0000 (UTC) (envelope-from nslay@comcast.net) Received: from alnrmhc13.comcast.net (alnrmhc13.comcast.net [206.18.177.53]) by mx1.freebsd.org (Postfix) with ESMTP id 5617513C494 for ; Wed, 26 Sep 2007 05:06:04 +0000 (UTC) (envelope-from nslay@comcast.net) Received: from antenna.local (c-68-35-224-189.hsd1.fl.comcast.net[68.35.224.189]) by comcast.net (alnrmhc13) with ESMTP id <20070926045522b130008snie>; Wed, 26 Sep 2007 04:55:22 +0000 Message-ID: <46F9E62C.1020701@comcast.net> Date: Wed, 26 Sep 2007 00:55:08 -0400 From: Nathan Lay User-Agent: Thunderbird 2.0.0.6 (X11/20070925) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Subject: iwi strange 'list scan' output X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 05:06:04 -0000 Hi list, I am running a CURRENT build as recent as Monday. I used to be really=20 annoyed that ifconfig truncated the longer SSID names until I read=20 somewhere in the man page that the '-v' flag alleviated that problem. =20 Just now I tried 'ifconfig -v iwi0 list scan' and it prints out a lot of = these '+?' for some of the access points. Without the '-v' flag, it=20 behaves normally. I haven't investigated the cause yet. Anybody=20 experience this? Here is the full output: SSID BSSID CHAN RATE S:N = INT CAPS Lamp 00:18:4d:71:5d:36 1 54M 37:0 =20 100 EPS WPA linksys 00:1a:70:59:70:cf 6 54M 31:0 =20 100 E =20 Kleiner Satellit 00:1a:70:4e:4f:32 6 54M 22:0 =20 100 EP RSN WME NLRCJM231 00:1c:10:16:5e:03 6 54M 19:0 =20 100 EP WPA AndrewMCameron 00:18:4d:80:39:a2 11 54M 30:0 =20 100 EPS WPA ATH TalWireless 00:14:6c:02:a4:82 11 54M 21:0 =20 100 EP=20 stephm143 00:0f:b5:5c:03:8c 11 54M 23:0 =20 100 EP=20 Thaleia 00:14:51:77:00:dd 2 54M 33:0 =20 100 EP WPA RSN MITCH 00:1b:11:55:d3:d9 3 54M 23:0 =20 100 EPS WPA RSN WME From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 10:01:44 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C816016A420; Wed, 26 Sep 2007 10:01:44 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 91EF713C457; Wed, 26 Sep 2007 10:01:44 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 82FDE2F4AC; Wed, 26 Sep 2007 06:01:43 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 26 Sep 2007 06:01:43 -0400 X-Sasl-enc: Cc8Gnxu0qAflUfU5vMawqPso89wzlGGq0qeL9DRwBS63 1190800903 Received: from [192.168.1.235] (64-142-85-108.dsl.dynamic.sonic.net [64.142.85.108]) by mail.messagingengine.com (Postfix) with ESMTP id B79CC233A4; Wed, 26 Sep 2007 06:01:42 -0400 (EDT) Message-ID: <46FA2E46.8020303@freebsd.org> Date: Wed, 26 Sep 2007 03:02:46 -0700 From: Darren Reed User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Kris Kennaway References: <20070921102946.T11189@borg> <46F415BF.9010500@FreeBSD.org> <20070921140550.D96923@thebighonker.lerctr.org> <46F41CFF.6080108@FreeBSD.org> <46F58799.1030702@freebsd.org> <46F58B21.8030307@FreeBSD.org> <20070924091558.GB32006@team.vega.ru> <46F78C59.1020801@FreeBSD.org> <20070924080347.O84223@thebighonker.lerctr.org> <20070924144210.GA82735@team.vega.ru> <46F7D7A4.5090007@samsco.org> <46F80A39.3050707@FreeBSD.org> <46F8951C.50904@freebsd.org> <46F8CE67.60206@FreeBSD.org> In-Reply-To: <46F8CE67.60206@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Larry Rosenman Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 10:01:44 -0000 Kris Kennaway wrote: > Darren Reed wrote: >> Kris Kennaway wrote: >>> ... >>> Well yes, that is one hypothesis, but the evidence points elsewhere >>> as well. Prior the change you reference, some of my zfs machines >>> would run for weeks before hitting a load pattern that exhausted >>> their kmem_map and triggered the panic. Also unless I have missed >>> it I am not seeing the sudden flood of panic reports that may >>> indicate sudden breakage. It is quite possible that this particular >>> report has nothing to do with the recent change. >> >> Indeed. >> >> But here's something else to ponder... >> >> I've been using ZFS since it was internal beta at Sun, at first on >> i386 and later on amd64. >> I've never run into this kind of panic on Solaris. System can get >> very slow, yes, with >> ZFS hogging lots of memory, but it never panic'd because of it. >> >> We need to come up with a strategy here to solve this problem, be it >> fixing the kmem >> virtual memory or fixing zfs. > > Yes, Solaris does something architecturally different because it is > apparently acceptable for zfs to use gigabytes of memory by default. Well, if you were designing a file system for servers, is there any reason that you wouldn't try to use all of the RAM available? A similar thought process goes into having a unified buffer cache that uses all the free RAM that it can (on a 1.5GB NetBSD box, 1.4GB is file cache.) Even if I'm running a desktop workstation, if I'm not there, there's no reason that ZFS shouldn't be able to encourage the OS to swap out all of the applications (well as much as can be) if it so desires. The problem comes in deciding how strong ZFS's hold should be and how to apply pressure from other parts of the system that want to use the RAM as well. Now given that we have a ZFS tuning guide, surely the question we need to ask ourselves is why can't we take the recommendations from that and make up some code to implement the trends discussed? And how do we measure how much memory ZFS is using? Darren From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 11:36:46 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F5CE16A41B for ; Wed, 26 Sep 2007 11:36:46 +0000 (UTC) (envelope-from brucec@muon.bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [80.68.94.188]) by mx1.freebsd.org (Postfix) with ESMTP id 060F113C448 for ; Wed, 26 Sep 2007 11:36:45 +0000 (UTC) (envelope-from brucec@muon.bluestop.org) Received: by muon.bluestop.org (Postfix, from userid 1000) id 3F69A301F6; Wed, 26 Sep 2007 12:36:44 +0100 (BST) Date: Wed, 26 Sep 2007 12:36:44 +0100 From: bruce@cran.org.uk To: current@freebsd.org Message-ID: <20070926113643.GA21109@muon.bluestop.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) Cc: Subject: Interrupt storm on ahc0 when drm module is loaded X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 11:36:46 -0000 I've come some sort of conflict between the drm and ahc drivers: whenever drm is loaded I get an interrupt storm on ahc0. My system is: 7.0-CURRENT #0: Tue Sep 25 18:08:50 BST 2007 /usr/obj/usr/src/sys/GENERIC i386 I'm running Xorg 7.3 ahc0: port 0xdc00-0xdcff mem 0xd9200000-0xd9200fff irq 16 at device 9.0 on pci0 ahc0: [ITHREAD] da0 at ahc0 bus 0 target 6 lun 0 drm0: on vgapci0 info: [drm] AGP at 0xd0000000 64MB info: [drm] Initialized mga 3.2.2 20060319 info: [drm] Initialized card for AGP DMA drm0: [ITHREAD] vmstat -i: interrupt total rate irq1: atkbd0 4036 0 irq14: ata0 58 0 irq16: ahc0 15004943 2824 irq19: fxp0 40961 7 cpu0: timer 10624196 1999 cpu1: timer 10606936 1996 Total 36281130 6828 Over time the rate for ahc0 grows until I get the "Interrupt storm detected: throttling irq16" messages. I can trigger the problem by changing the default colour depth to 16 bits in my xorg.conf file: this enables the drm module to load and immediately the interrupt rate starts to climb. -- Bruce From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 11:47:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 947E016A417 for ; Wed, 26 Sep 2007 11:47:18 +0000 (UTC) (envelope-from fergus@cobbled.net) Received: from mail1.slb.deg.dub.stisp.net (mail1.slb.deg.dub.stisp.net [84.203.253.98]) by mx1.freebsd.org (Postfix) with SMTP id 09AAE13C43E for ; Wed, 26 Sep 2007 11:47:17 +0000 (UTC) (envelope-from fergus@cobbled.net) Received: (qmail 20338 invoked from network); 26 Sep 2007 11:47:15 -0000 Received: from unknown (HELO holyman.cobbled.net) (84.203.180.117) by mail1.slb.deg.dub.stisp.net with SMTP; 26 Sep 2007 11:47:15 -0000 Received: by holyman.cobbled.net (Postfix, from userid 16385) id 24C89171B7; Wed, 26 Sep 2007 11:47:06 +0000 (UTC) Date: Wed, 26 Sep 2007 11:47:06 +0000 From: ttw+bsd@cobbled.net To: FreeBSD Current Message-ID: <20070926114705.GA12643@holyman.cobbled.net> Mail-Followup-To: FreeBSD Current References: <46F905FD.9060208@freebsd.org> <20070925194008.3c2d7113@epia-2.farid-hajji.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070925194008.3c2d7113@epia-2.farid-hajji.net> Subject: Re: The safety expansion for FreeBSD rm(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 11:47:18 -0000 Daichi GOTO wrote: [ ... ] > Have you any dreams that rm(1) autonomously judges target should > be remove or not? To complexify system base command is objectionable > behavior but adding some little and simple mechanism to prevent a > issue is acceptable I suppose. this is a nice little feature but from an administrative point of view i don't think it will be used (i'm infallable, as are most admins ... at least within their own heads) and there are other more comprehensive (i.e. not just the rm binary) tools for critical paths (as others have pointed out). from a user perspective it would be nice to have '/etc/rm.conf' or something so the admin can prevent user foot shooting, however, how many user deletes will actually be performed by 'rm'. basically, it's very clever, non-intrusive feature but i just can't see any value from it. perhaps if, instead of overlapping the current flags function, you used this feature to allow the user to be prompted when deleting a 'uunlink' file, or so that a user may set places where 'rm' will effectively ignore the 'uunlink' flag. still not sure how much value but it may encourage the use of 'uunlink' so that more paths are protected (i.e. if more binaries are flags aware we don't need to constantly change flags to perform functions). one obstacle i can think of is that many files may be stored on filesystems incompatible with flags. From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 11:28:23 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C242916A418 for ; Tue, 25 Sep 2007 11:28:23 +0000 (UTC) (envelope-from serguey-grigoriev@yandex.ru) Received: from webmail24.mail.yandex.net (webmail24.mail.yandex.net [213.180.223.151]) by mx1.freebsd.org (Postfix) with ESMTP id ED21713C43E for ; Tue, 25 Sep 2007 11:28:22 +0000 (UTC) (envelope-from serguey-grigoriev@yandex.ru) Received: from YAMAIL (webmail24) by mail.yandex.ru id S491844AbXIYL2P for (+ 1 other); Tue, 25 Sep 2007 15:28:15 +0400 X-Yandex-Spam: 1 Received: from [77.244.18.3] ([77.244.18.3]) by mail.yandex.ru with HTTP; Tue, 25 Sep 2007 15:28:15 +0400 From: "S.N.Grigoriev" To: kris@FreeBSD.org In-Reply-To: 9070000000021720668 References: <1291921190632545@webmail31.yandex.ru> 9070000000021720668 MIME-Version: 1.0 Message-Id: <71531190719695@webmail24.yandex.ru> Date: Tue, 25 Sep 2007 15:28:15 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailman-Approved-At: Wed, 26 Sep 2007 12:34:24 +0000 Cc: freebsd-current@freebsd.org Subject: Re: Parallel port printing crashes 7.0 system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 11:28:23 -0000 25.09.07, 13:07, Kris Kennaway (kris@FreeBSD.org): > S.N.Grigoriev wrote: > > Hi, list, > > > > This problem has already been reported this year at least twice. > > I can confirm it still exists. Probably it has been introduced > > near the beginning of May because April and earlyer sources > > handle parallel printing correctly. > So we can cross-reference, what number is your PR? > Kris Hi, Kris, The following messages posted to freebsd-current@ this year: On Wen May 16 I wrote: > From: S.N.Grigoriev > To: freebsd-current@freebsd.org > Subject: Crash during sending print jobs > > Hi, > > beginning with last week my 7-Current amd64 system panics > during sending print jobs (especially PostScript) to my > LPT connected laser printer. Kernels compiled with April > or March sources still work fine. Does anybody find this > problem? On Mon, Jun 4 I wrote: > The problem persists. GENERIC compiled with today sources > crashes with the following output: > panic: bad stray interrupt > cpuid = 0 > KDB: enter: panic > [thread pid = 11 tid 100002 ] > Stopped at kdb_enter+0x2f: leave > > > The call stack trace is: > > Tracing pid 11 tid 100002 td 0xffffff003db84990 > kdb_enter() at kdb_enter+0x30 > intr_execute_handlers() at intr_execute_handlers+0x183 > Xapic_isr1() at Xapic_isr1()+0x7f > --- interrupt, rip = 0xffffffff8071ec56, rsp = 0xffffffffa075fbd0, rbp > = 0xffffffffa075fbe0 --- > acpi_cpu_c1() at acpi_cpu_c1+0x6 > acpi_cpu_idle() at acpi_cpu_idle+0x27c > sched_idletd() at sched_idletd+0x35 > fork_exit() at fork_exit+0x153 > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffffffa075fd30, rbp = 0 --- On Tue Jul 3 Gary Jennejohn wrote: > Date: Tue, 3 Jul 2007 11:42:48 +0200 > From: Gary Jennejohn > To: freebsd-current@freebsd.org > Subject: panic when printing > Message-ID: <20070703114248.37a2019b.garyj@jennejohn.org> > > I haven't seen this reported before. > > Trying to print to my parallel printer with a -current kernel from July > 2 (amd64) results in a kernel panic. A kernel from June 16 (i386) does > not cause a panic. > > If I boot with the printer turned on then the kernel sees it (PnP) > with no problem. Just printing causes a panic. > > BTW this kernel is using the SMP-scheduler from Jeff Roberson, but > IIRC a different kernel (June 29) w/o that scheduler also panics. > > I can't say whether it's amd64-specific or just due to recent changes to > the sources. I'm rather reluctant to generate a new i386 kernel to check > that, but I could be persuaded to do it. > > Below a typescript of a very limited kgdb session: > > root:peedub:crash:bash:1> gdb /boot/kernel/kernel vmcore.1 > [GDB will not be able to debug user-mode > threads: /usr/lib/libthread_db.so: Undefined symbol > "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free > Software Foundation, Inc. GDB is free software, covered by the GNU > General Public License, and you are welcome to change it and/or > distribute copies of it under certain conditions. Type "show copying" > to see the conditions. There is absolutely no warranty for GDB. Type > "show warranty" for details. This GDB was configured as > "amd64-marcel-freebsd". > > Unread portion of the kernel message buffer: > lpt0: [GIANT-LOCKED] > lpt0: [ITHREAD] > lpt0: [GIANT-LOCKED] > lpt0: [ITHREAD] > lpt0: [GIANT-LOCKED] > lpt0: [ITHREAD] > lpt0: [GIANT-LOCKED] > lpt0: [ITHREAD] > lpt0: [GIANT-LOCKED] > lpt0: [ITHREAD] > lpt0: [GIANT-LOCKED] > lpt0: [ITHREAD] > lpt0: [GIANT-LOCKED] > lpt0: [ITHREAD] > lpt0: [GIANT-LOCKED] > lpt0: [ITHREAD] > lpt0: [GIANT-LOCKED] > lpt0: [ITHREAD] > > > Fatal trap 30: reserved (unknown) fault while in kernel mode > cpuid = 1; apic id = 01 > instruction pointer = 0x8:0xffffffff804ece83 > stack pointer = 0x10:0xffffffffaf97a760 > frame pointer = 0x10:0xffffffffaf97a780 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, IOPL = 0 > current process = 1980 (lpd) > trap number = 30 > panic: reserved (unknown) fault > cpuid = 1 > Uptime: 2h41m43s > Physical memory: 2037 MB > Dumping 977 MB: 961 945 929 913 897 881 865 849 833 817 801 785 769 753 > 737 721 705 689 673 657 641 625 609 593 577 561 545 529 513 497 481 465 > 449 433 417 401 385 369 353 337 321 305 289 273 257 241 225 209 193 177 > 161 145 129 113 97 81 65 49 33 17 1 > > #0 doadump () at pcpu.h:194 > 194 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) bt > #0 doadump () at pcpu.h:194 > #1 0xffffffff802f94db in boot (howto=260) > at /usr/src/sys/kern/kern_shutdown.c:409 > #2 0xffffffff802f97de in panic (fmt=Variable "fmt" is not available. > ) at /usr/src/sys/kern/kern_shutdown.c:563 > #3 0xffffffff804fec9c in trap_fatal (frame=0xffffffffaf97a6b0, eva=0) > at /usr/src/sys/amd64/amd64/trap.c:695 > #4 0xffffffff804ffaa3 in trap (frame=0xffffffffaf97a6b0) > at /usr/src/sys/amd64/amd64/trap.c:498 > #5 0xffffffff804e566e in calltrap () > at /usr/src/sys/amd64/amd64/exception.S:169 > #6 0xffffffff804ece83 in spinlock_exit () at cpufunc.h:391 > #7 0xffffffff804e9291 in ioapic_program_intpin > #(intpin=0xffffff0001043208) > at /usr/src/sys/amd64/amd64/io_apic.c:273 > #8 0xffffffff804e967a in ioapic_disable_intr (isrc=0xffffff0001043208) > at /usr/src/sys/amd64/amd64/io_apic.c:375 > #9 0xffffffff804e843d in intr_remove_handler (cookie=Variable "cookie" > #is not available. > ) > at /usr/src/sys/amd64/amd64/intr_machdep.c:217 > #10 0xffffffff804f23bc in nexus_teardown_intr (dev=Variable "dev" is > #not available. > ) > at /usr/src/sys/amd64/amd64/nexus.c:451 > #11 0xffffffff8031bf8f in bus_generic_teardown_intr > #(dev=0xffffffffabf30000, > child=0xffffff0003285b00, irq=0xffffff0003316480, > cookie=0xffffff001bf44100) at bus_if.h:416 > #12 0xffffffff8022fc9d in ppc_teardown_intr (bus=0xffffff0001216500, > child=0xffffff0003285b00, r=0xffffff0003316480, > ih=0xffffff001bf44100) at bus_if.h:416 > #13 0xffffffff8022e3f4 in ppbus_teardown_intr (bus=0xffffff0003286e00, > child=0xffffff0003285b00, r=Variable "r" is not available. > ) at bus_if.h:416 > #14 0xffffffff8022ef6a in ppb_release_bus (bus=0xffffff0003286e00, > dev=0xffffff0003285b00) at bus_if.h:416 > #15 0xffffffff8022a9a5 in lpt_release_ppbus (dev=0xffffff0003285b00) > at /usr/src/sys/dev/ppbus/lpt.c:227 > #16 0xffffffff8022b796 in lptwrite (dev=Variable "dev" is not available. > ) at /usr/src/sys/dev/ppbus/lpt.c:826 > #17 0xffffffff802c6f61 in giant_write (dev=0xffffff00032fe800, > uio=0xffffffffaf97ab00, ioflag=0) > at /usr/src/sys/kern/kern_conf.c:358 > #18 0xffffffff8028b9f7 in devfs_write_f (fp=0xffffff0003b092d0, > uio=0xffffffffaf97ab00, cred=Variable "cred" is not available. > ) at /usr/src/sys/fs/devfs/devfs_vnops.c:1290 > #19 0xffffffff8033058a in dofilewrite (td=0xffffff00039c5360, fd=6, > fp=0xffffff0003b092d0, auio=0xffffffffaf97ab00, offset=Variable > "offset" is not available. ) at file.h:254 > #20 0xffffffff8033080f in kern_writev (td=0xffffff00039c5360, fd=6, > auio=0xffffffffaf97ab00) at /usr/src/sys/kern/sys_generic.c:373 > #21 0xffffffff8033088b in write (td=0xffffffffabf30000, uap=0x1e) > at /usr/src/sys/kern/sys_generic.c:303 > #22 0xffffffff804ff2d1 in syscall (frame=0xffffffffaf97ac70) > at /usr/src/sys/amd64/amd64/trap.c:820 > #23 0xffffffff804e581b in Xfast_syscall () > at /usr/src/sys/amd64/amd64/exception.S:272 > #24 0x000000080071ccac in ?? () > Previous frame inner to this frame (corrupt stack?) > (kgdb) q > > --- > Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg On Mon, 23 Jul John Baldwin wrote: > On Tuesday 03 July 2007 05:42:48 am Gary Jennejohn wrote: > > I haven't seen this reported before. > > > > Trying to print to my parallel printer with a -current kernel from > > July 2 (amd64) results in a kernel panic. A kernel from June 16 > > (i386) does not cause a panic. > > > > If I boot with the printer turned on then the kernel sees it (PnP) > > with no problem. Just printing causes a panic. > > > > BTW this kernel is using the SMP-scheduler from Jeff Roberson, but > > IIRC a different kernel (June 29) w/o that scheduler also panics. > > > > I can't say whether it's amd64-specific or just due to recent > > changes to the sources. I'm rather reluctant to generate a new i386 > > kernel to check that, but I could be persuaded to do it. > > > > Below a typescript of a very limited kgdb session: > > You got an interrupt after the lpt driver removed its handler. > Really the ppbus device should not be so stupid and should have its > own interrupt handler that routes interrupts to the "active" child. > Regards, Serguey. From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 15:06:04 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14DA716A419 for ; Tue, 25 Sep 2007 15:06:04 +0000 (UTC) (envelope-from hopet@ics.muni.cz) Received: from minas.ics.muni.cz (minas.ics.muni.cz [147.251.4.40]) by mx1.freebsd.org (Postfix) with ESMTP id 82CCE13C45D for ; Tue, 25 Sep 2007 15:06:03 +0000 (UTC) (envelope-from hopet@ics.muni.cz) Received: from KLOBOUCEK (kloboucek.ics.muni.cz [147.251.3.38]) (authenticated user=hopet@ICS.MUNI.CZ bits=0) by minas.ics.muni.cz (8.13.8/8.13.8/SuSE Linux 0.8) with ESMTP id l8PF60Uw002710 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Tue, 25 Sep 2007 17:06:01 +0200 From: "Petr Holub" To: Date: Tue, 25 Sep 2007 17:06:01 +0200 Message-ID: <00ec01c7ff85$9604f8f0$5317fb93@KLOBOUCEK> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 X-Muni-Spam-TestIP: 147.251.3.38 X-Muni-Envelope-From: hopet@ics.muni.cz X-Muni-Envelope-To: current@freebsd.org X-Muni-Virus-Test: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (minas.ics.muni.cz [147.251.4.35]); Tue, 25 Sep 2007 17:06:01 +0200 (CEST) X-Mailman-Approved-At: Wed, 26 Sep 2007 12:34:24 +0000 Cc: Subject: x11/nvidia-driver on Sept07 snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 15:06:04 -0000 Hi, is x11/nvidia-driver supposed to work on September 2007 -CURRENT snapshot? I've given it a shot and it compiles fine, kldloads fine, but doesn't detect graphics card for some reason # sysctl -a | fgrep nvi hw.nvidia.version: NVIDIA UNIX x86 Kernel Module 100.14.11 Wed Jun 13 15:15:08 PDT 2007 hw.nvidia.registry.EnableVia4x: 0 hw.nvidia.registry.EnableALiAGP: 0 hw.nvidia.registry.NvAGP: 1 hw.nvidia.registry.EnableAGPSBA: 0 hw.nvidia.registry.EnableAGPFW: 0 hw.nvidia.registry.SoftEDIDs: 1 hw.nvidia.registry.Mobile: 4294967295 hw.nvidia.registry.ResmanDebugLevel: 4294967295 hw.nvidia.registry.FlatPanelMode: 0 hw.nvidia.registry.DevicesConnected: 0 hw.nvidia.registry.RmLogonRC: 1 hw.nvidia.registry.DetectPrimaryVga: 1 hw.nvidia.registry.dwords: # pciconf -lv |fgrep -i -A2 -B1 nvi vgapci0@pci1:0:0: class=0x030000 card=0x04131462 chip=0x039210de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' device = 'GeForce 7600 GS' class = display # dmesg | fgrep nvid (nothing here) When attempting to run X, I get: (EE) NVIDIA(0): ============= WARNING WARNING WARNING WARNING ============= (EE) NVIDIA(0): This server has a video driver ABI version of 2.0 but this (EE) NVIDIA(0): driver is designed to work with versions before 2.0. (EE) NVIDIA(0): Please check http://www.nvidia.com/ for driver updates or (EE) NVIDIA(0): downgrade to an X server with a supported driver ABI. (EE) NVIDIA(0): =========================================================== (II) Module "ramdac" already built-in NVIDIA: could not open the device file /dev/nvidiactl (No such file or directory ). (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! Please ensure (EE) NVIDIA(0): that there is a supported NVIDIA GPU in this system, and (EE) NVIDIA(0): that the NVIDIA device files have been created properly. (EE) NVIDIA(0): Please consult the NVIDIA README for details. (EE) NVIDIA(0): *** Aborting *** (EE) Screen(s) found, but none have a usable configuration. I can submit more info on request. TIA, Petr From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 09:26:30 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF60916A419 for ; Wed, 26 Sep 2007 09:26:30 +0000 (UTC) (envelope-from ted@omval.tednet.nl) Received: from omval.tednet.nl (omval.tednet.nl [IPv6:2001:7b8:206:1:200:39ff:fe59:b187]) by mx1.freebsd.org (Postfix) with ESMTP id 77A5113C45D for ; Wed, 26 Sep 2007 09:26:30 +0000 (UTC) (envelope-from ted@omval.tednet.nl) Received: from omval.tednet.nl (localhost [127.0.0.1]) by omval.tednet.nl (8.14.1/8.14.1) with ESMTP id l8Q9QPMM063377; Wed, 26 Sep 2007 11:26:25 +0200 (CEST) (envelope-from ted@omval.tednet.nl) Received: (from ted@localhost) by omval.tednet.nl (8.14.1/8.14.1/Submit) id l8Q9QPkG063376; Wed, 26 Sep 2007 11:26:25 +0200 (CEST) (envelope-from ted) Message-Id: <200709260926.l8Q9QPkG063376@omval.tednet.nl> From: ted@tednet.nl (Ted Lindgreen) Date: Wed, 26 Sep 2007 11:26:24 +0200 X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: freebsd-current@freebsd.org X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_40 autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on omval.tednet.nl X-Mailman-Approved-At: Wed, 26 Sep 2007 12:34:24 +0000 Cc: Ted Lindgreen Subject: New acpi_ec.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 09:26:30 -0000 Hi, The file /usr/src/sys/dev/acpica/acpi_ec.c has been updated recently. This broke my patch (about which I have posted earlier this year (around March) to let my Acer 3623 behave properly. I append a new patch, which can be applied to the new acpi_ec.c. To recap the problem and the hack that I found to fix it: - It appears that the EC of my Acer 3623 does not like to be polled for status to soon after writing a command to it. - The error message AE_NO_HARDWARE_RESPONSE is output in enormous amounts, and commands like apm(8) fail. - With a delay of 2500 the amount of AE_NO_HARDWARE_RESPONSE messages drops significantly, and apm(8) works. - With a delay of 3000 no more AE_NO_HARDWARE_RESPONSE messages appear, and everything works flawlessly. regards, -- ted PS. the patch: In /boot/loader.conf I have: debug.acpi.ec.burst="1" debug.acpi.ec.waitbeforepoll="3000" and the change in acpi_ec.c: --- acpi_ec.c 2007-09-26 11:18:27.000000000 +0200 +++ acpi_ec.c.org 2007-09-24 18:59:06.000000000 +0200 @@ -193,10 +193,6 @@ TUNABLE_INT("debug.acpi.ec.timeout", &ec_timeout); SYSCTL_INT(_debug_acpi_ec, OID_AUTO, timeout, CTLFLAG_RW, &ec_timeout, EC_TIMEOUT, "Total time spent waiting for a response (poll+sleep)"); -static int ec_waitbeforepoll = 0; -TUNABLE_INT("debug.acpi.ec.waitbeforepoll", &ec_waitbeforepoll); -SYSCTL_INT(_debug_acpi_ec, OID_AUTO, waitbeforepoll, CTLFLAG_RW, &ec_waitbeforepoll, - 0, "Wait before starting to poll"); static ACPI_STATUS EcLock(struct acpi_ec_softc *sc) @@ -806,10 +802,6 @@ if (cold || rebooting || ec_polled_mode) { static int once; - /* Some EC's just need enough time before they can be polled */ - if (ec_waitbeforepoll > 0) - AcpiOsStall(ec_waitbeforepoll); - else { if (EcCheckStatus(sc, "pre-check", Event) == AE_OK) { if (!once) { device_printf(sc->ec_dev, @@ -818,7 +810,6 @@ } AcpiOsStall(10); } - } } /* Wait for event by polling or GPE (interrupt). */ From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 08:00:20 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F79016A421 for ; Wed, 26 Sep 2007 08:00:20 +0000 (UTC) (envelope-from jpedras@webvolution.net) Received: from mail.portrait.com (mail.portrait.com [64.171.32.41]) by mx1.freebsd.org (Postfix) with ESMTP id 037AF13C4B0 for ; Wed, 26 Sep 2007 08:00:19 +0000 (UTC) (envelope-from jpedras@webvolution.net) Received: from joao-pedras-computer.local (beastie.webvolution.net [64.174.136.225]) (authenticated bits=0) by mail.portrait.com (8.13.1/8.13.1) with ESMTP id l8Q7anur080716 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 26 Sep 2007 00:36:53 -0700 (PDT) (envelope-from jpedras@webvolution.net) Message-ID: <46FA0C14.10201@webvolution.net> Date: Wed, 26 Sep 2007 00:36:52 -0700 From: Joao Pedras User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.3 OpenPGP: id=D7505EC0 Content-Type: multipart/mixed; boundary="------------090507090308000103030805" X-Spam-Status: No, score=0.1 required=3.0 tests=FORGED_RCVD_HELO X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on mail.portrait.com X-Mailman-Approved-At: Wed, 26 Sep 2007 12:34:47 +0000 Subject: lock up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 08:00:20 -0000 This is a multi-part message in MIME format. --------------090507090308000103030805 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Greetings all! A system (Tyan S2932) I am testing CURRENT amd64 with is experiencing a strange lock up. No panic, not much on the console, just a lock up, freeze. I first noticed the issue while tailing a build in a ssh session over a vpn connection. On the local network the issue doesn't seem to occur. I can reproduce the lock up all the time. Last I tried, the system was running CURRENT from a couple hours ago. I have tried: - 4BSD and ULE - switching network cards - taking the IPMI card out (seems to work locally with freeipmi and ipmitoll remotely) - enabled/disabled "redirection after post" (BIOS setting) - without debug - without IPv6 and friends (see rtfree below) dmesg and pciconf attached. The dmesg is after a lock up. rtfree pops a few times before the lock up. I noticed from a recent post some action was taken and the related patch is there (ie. today's CURRENT). The system had a fresh install this past weekend and the LSI MegaRAID array doesn't contain any data, it is just mounted. The system boots off the onboard LSI SAS (couple disks in RAID 1). Thank you for your input. Joao --------------090507090308000103030805 Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0"; name="dmesg.S2932" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.S2932" Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-CURRENT #2: Tue Sep 25 22:52:58 PDT 2007 root@daemons.somedomain.com:/usr/obj/usr/src/sys/GENERIC WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Dual-Core AMD Opteron(tm) Processor 2210 HE (1800.08-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40f12 Stepping = 2 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1f Cores per package: 2 usable memory = 4281667584 (4083 MB) avail memory = 4124246016 (3933 MB) ACPI APIC Table: <082907 APIC1947> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: <082907 XSDT1947> on motherboard acpi0: [ITHREAD] acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 25000000 Hz quality 900 acpi0: Power Button (fixed) acpi0: reservation of fec00000, 1400000 (3) failed acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, d7f00000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x2008-0x200b on acpi0 cpu0: on acpi0 powernow0: on cpu0 cpu1: on acpi0 powernow1: on cpu1 cpu2: on acpi0 powernow2: on cpu2 cpu3: on acpi0 powernow3: on cpu3 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) isab0: port 0x2f00-0x2f7f at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xfdafb000-0xfdafbfff irq 21 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 10 ports with 10 removable, self powered ehci0: mem 0xfdafac00-0xfdafacff irq 22 at device 2.1 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb1: EHCI version 1.0 usb1: companion controller, 10 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: on usb1 uhub1: 10 ports with 10 removable, self powered atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 4.0 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] atapci1: port 0xb480-0xb487,0xb400-0xb403,0xb080-0xb087,0xb000-0xb003,0xac00-0xac0f mem 0xfdaf9000-0xfdaf9fff irq 23 at device 5.0 on pci0 atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] atapci2: port 0xa880-0xa887,0xa800-0xa803,0xa480-0xa487,0xa400-0xa403,0xa080-0xa08f mem 0xfdaf8000-0xfdaf8fff irq 20 at device 5.1 on pci0 atapci2: [ITHREAD] ata4: on atapci2 ata4: [ITHREAD] ata5: on atapci2 ata5: [ITHREAD] atapci3: port 0xa000-0xa007,0x9c00-0x9c03,0x9880-0x9887,0x9800-0x9803,0x9480-0x948f mem 0xfdaf7000-0xfdaf7fff irq 21 at device 5.2 on pci0 atapci3: [ITHREAD] ata6: on atapci3 ata6: [ITHREAD] ata7: on atapci3 ata7: [ITHREAD] pcib1: at device 6.0 on pci0 pci1: on pcib1 ahc0: port 0xc800-0xc8ff mem 0xfdbff000-0xfdbfffff irq 16 at device 6.0 on pci1 ahc0: [ITHREAD] aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs vgapci0: port 0xc000-0xc0ff mem 0xf0000000-0xf7ffffff,0xfdbe0000-0xfdbeffff irq 17 at device 7.0 on pci1 nfe0: port 0x9400-0x9407 mem 0xfdaf6000-0xfdaf6fff,0xfdafa800-0xfdafa8ff,0xfdafa400-0xfdafa40f irq 22 at device 8.0 on pci0 miibus0: on nfe0 e1000phy0: PHY 16 on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto nfe0: Ethernet address: 00:e0:81:48:f8:42 nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe1: port 0x9080-0x9087 mem 0xfdaf5000-0xfdaf5fff,0xfdafa000-0xfdafa0ff,0xfdaf4c00-0xfdaf4c0f irq 23 at device 9.0 on pci0 miibus1: on nfe1 e1000phy1: PHY 17 on miibus1 e1000phy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto nfe1: Ethernet address: 00:e0:81:48:f8:43 nfe1: [FILTER] nfe1: [FILTER] nfe1: [FILTER] nfe1: [FILTER] nfe1: [FILTER] nfe1: [FILTER] nfe1: [FILTER] nfe1: [FILTER] pcib2: at device 10.0 on pci0 pci2: on pcib2 mpt0: port 0xd000-0xd0ff mem 0xfdefc000-0xfdefffff,0xfdee0000-0xfdeeffff irq 18 at device 0.0 on pci2 mpt0: [ITHREAD] mpt0: MPI Version=1.5.13.0 mpt0: mpt_cam_event: 0x16 mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). mpt0: mpt_cam_event: 0x12 mpt0: Unhandled Event Notify Frame. Event 0x12 (ACK not required). mpt0: mpt_cam_event: 0x12 mpt0: Unhandled Event Notify Frame. Event 0x12 (ACK not required). mpt0: mpt_cam_event: 0x16 mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). pcib3: at device 13.0 on pci0 pci3: on pcib3 pcib4: at device 0.0 on pci3 pci4: on pcib4 pcib5: at device 0.0 on pci4 pci5: on pcib5 amr0: mem 0xfcff0000-0xfcffffff,0xfe800000-0xfe8fffff irq 19 at device 14.0 on pci5 amr0: Using 64-bit DMA amr0: [ITHREAD] amr0: delete logical drives supported by controller amr0: Firmware 815C, BIOS H432, 128MB RAM pcib6: at device 0.1 on pci3 pci6: on pcib6 fxp0: port 0xec00-0xec3f mem 0xfebff000-0xfebfffff,0xfea00000-0xfeafffff irq 16 at device 2.0 on pci6 miibus2: on fxp0 inphy0: PHY 1 on miibus2 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:d0:b7:ba:a0:bd fxp0: [ITHREAD] pcib7: at device 14.0 on pci0 pci7: on pcib7 pcib8: at device 15.0 on pci0 pci8: on pcib8 acpi_button0: on acpi0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 drq 0 on acpi0 sio1: type 16550A sio1: [FILTER] fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] orm0: at iomem 0xc0000-0xc8fff,0xc9000-0xca7ff,0xca800-0xcafff,0xd3000-0xd3fff on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: DVDR at ata2-master SATA150 Waiting 5 seconds for SCSI devices to settle amr0: delete logical drives supported by controller amrd0: on amr0 amrd0: 915525MB (1874995200 sectors) RAID 5 (optimal) da0 at mpt0 bus 0 target 11 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 300.000MB/s transfers da0: Command Queueing Enabled da0: 69618MB (142577664 512 byte sectors: 255H 63S/T 8875C) sa0 at ahc0 bus 0 target 2 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 32) SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/da0s1a WARNING: / was not properly dismounted WARNING: /tmp was not properly dismounted /tmp: mount pending error: blocks 52 files 13 WARNING: /usr was not properly dismounted /usr: mount pending error: blocks 37776 files 2374 WARNING: /var was not properly dismounted WARNING: /resource was not properly dismounted --------------090507090308000103030805 Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0"; name="pciconfLV" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="pciconfLV" none0@pci0:0:0: class=0x050000 card=0xcb8410de chip=0x036910de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' device = 'MCP55 Memory Controller' class = memory subclass = RAM isab0@pci0:1:0: class=0x060100 card=0xcb8410de chip=0x036410de rev=0xa3 hdr=0x00 vendor = 'Nvidia Corp' device = 'MCP55 LPC Bridge' class = bridge subclass = PCI-ISA none1@pci0:1:1: class=0x0c0500 card=0xcb8410de chip=0x036810de rev=0xa3 hdr=0x00 vendor = 'Nvidia Corp' device = 'MCP55 SMBus' class = serial bus subclass = SMBus ohci0@pci0:2:0: class=0x0c0310 card=0xcb8410de chip=0x036c10de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' device = 'MCP55 USB Controller' class = serial bus subclass = USB ehci0@pci0:2:1: class=0x0c0320 card=0xcb8410de chip=0x036d10de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' device = 'MCP55 USB Controller' class = serial bus subclass = USB atapci0@pci0:4:0: class=0x01018a card=0xcb8410de chip=0x036e10de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' device = 'MCP55 IDE' class = mass storage subclass = ATA atapci1@pci0:5:0: class=0x010185 card=0xcb8410de chip=0x037f10de rev=0xa3 hdr=0x00 vendor = 'Nvidia Corp' device = 'MCP55 SATA Controller' class = mass storage subclass = ATA atapci2@pci0:5:1: class=0x010185 card=0xcb8410de chip=0x037f10de rev=0xa3 hdr=0x00 vendor = 'Nvidia Corp' device = 'MCP55 SATA Controller' class = mass storage subclass = ATA atapci3@pci0:5:2: class=0x010185 card=0xcb8410de chip=0x037f10de rev=0xa3 hdr=0x00 vendor = 'Nvidia Corp' device = 'MCP55 SATA Controller' class = mass storage subclass = ATA pcib1@pci0:6:0: class=0x060401 card=0xcb8410de chip=0x037010de rev=0xa2 hdr=0x01 vendor = 'Nvidia Corp' device = 'MCP55 PCI bridge' class = bridge subclass = PCI-PCI nfe0@pci0:8:0: class=0x068000 card=0xcb8410de chip=0x037310de rev=0xa3 hdr=0x00 vendor = 'Nvidia Corp' device = 'MCP55 Ethernet' class = bridge nfe1@pci0:9:0: class=0x068000 card=0xcb8410de chip=0x037310de rev=0xa3 hdr=0x00 vendor = 'Nvidia Corp' device = 'MCP55 Ethernet' class = bridge pcib2@pci0:10:0: class=0x060400 card=0x000010de chip=0x037610de rev=0xa3 hdr=0x01 vendor = 'Nvidia Corp' device = 'MCP55 PCI Express bridge' class = bridge subclass = PCI-PCI pcib3@pci0:13:0: class=0x060400 card=0x000010de chip=0x037810de rev=0xa3 hdr=0x01 vendor = 'Nvidia Corp' device = 'MCP55 PCI Express bridge' class = bridge subclass = PCI-PCI pcib7@pci0:14:0: class=0x060400 card=0x000010de chip=0x037510de rev=0xa3 hdr=0x01 vendor = 'Nvidia Corp' device = 'MCP55 PCI Express bridge' class = bridge subclass = PCI-PCI pcib8@pci0:15:0: class=0x060400 card=0x000010de chip=0x037710de rev=0xa3 hdr=0x01 vendor = 'Nvidia Corp' device = 'MCP55 PCI Express bridge' class = bridge subclass = PCI-PCI hostb0@pci0:24:0: class=0x060000 card=0x00000000 chip=0x11001022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron HyperTransport Technology Configuration' class = bridge subclass = HOST-PCI hostb1@pci0:24:1: class=0x060000 card=0x00000000 chip=0x11011022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron Address Map' class = bridge subclass = HOST-PCI hostb2@pci0:24:2: class=0x060000 card=0x00000000 chip=0x11021022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron DRAM Controller' class = bridge subclass = HOST-PCI hostb3@pci0:24:3: class=0x060000 card=0x00000000 chip=0x11031022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron Miscellaneous Control' class = bridge subclass = HOST-PCI hostb4@pci0:25:0: class=0x060000 card=0x00000000 chip=0x11001022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron HyperTransport Technology Configuration' class = bridge subclass = HOST-PCI hostb5@pci0:25:1: class=0x060000 card=0x00000000 chip=0x11011022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron Address Map' class = bridge subclass = HOST-PCI hostb6@pci0:25:2: class=0x060000 card=0x00000000 chip=0x11021022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron DRAM Controller' class = bridge subclass = HOST-PCI hostb7@pci0:25:3: class=0x060000 card=0x00000000 chip=0x11031022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron Miscellaneous Control' class = bridge subclass = HOST-PCI ahc0@pci1:6:0: class=0x010000 card=0xa1809005 chip=0x00109005 rev=0x00 hdr=0x00 vendor = 'Adaptec Inc' device = 'AHA-2940U2W/U2B AHA-2950U2W Ultra2 SCSI Controller' class = mass storage subclass = SCSI vgapci0@pci1:7:0: class=0x030000 card=0x515e1002 chip=0x515e1002 rev=0x02 hdr=0x00 vendor = 'ATI Technologies Inc.' device = 'Radeon ES1000 Radeon ES1000' class = display subclass = VGA mpt0@pci2:0:0: class=0x010000 card=0x10001000 chip=0x00581000 rev=0x04 hdr=0x00 vendor = 'LSI Logic (Was: Symbios Logic, NCR)' device = 'SAS 3000 series, 8-port with 1068E -StorPort' class = mass storage subclass = SCSI pcib4@pci3:0:0: class=0x060400 card=0x00000000 chip=0x01251033 rev=0x07 hdr=0x01 vendor = 'NEC Electronics Hong Kong' class = bridge subclass = PCI-PCI pcib6@pci3:0:1: class=0x060400 card=0x00000000 chip=0x01251033 rev=0x07 hdr=0x01 vendor = 'NEC Electronics Hong Kong' class = bridge subclass = PCI-PCI pcib5@pci4:0:0: class=0x060400 card=0x00000000 chip=0x03358086 rev=0x0a hdr=0x01 vendor = 'Intel Corporation' device = '80331 [Lindsay] I/O processor PCI-X bridge' class = bridge subclass = PCI-PCI amr0@pci5:14:0: class=0x010400 card=0x30081000 chip=0x04091000 rev=0x0a hdr=0x00 vendor = 'LSI Logic (Was: Symbios Logic, NCR)' device = 'MegaRAID' class = mass storage subclass = RAID fxp0@pci6:2:0: class=0x020000 card=0x000c8086 chip=0x12298086 rev=0x08 hdr=0x00 vendor = 'Intel Corporation' device = '82550/1/7/8/9 EtherExpress PRO/100(B) Ethernet Adapter' class = network subclass = ethernet --------------090507090308000103030805-- From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 13:15:47 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FB8716A41B; Wed, 26 Sep 2007 13:15:47 +0000 (UTC) (envelope-from oliver@akephalos.de) Received: from mailout03.sul.t-online.com (mailout03.sul.t-online.de [194.25.134.81]) by mx1.freebsd.org (Postfix) with ESMTP id 5673A13C474; Wed, 26 Sep 2007 13:15:46 +0000 (UTC) (envelope-from oliver@akephalos.de) Received: from fwd32.aul.t-online.de by mailout03.sul.t-online.com with smtp id 1IaWjx-0004Qa-00; Wed, 26 Sep 2007 15:15:45 +0200 Received: from localhost (ZkKZCoZBotvx5Mb3cuyAtjqS8TliA0yM9K1L9r3LCI28z2SrNhI7liGiH2PzmQYewhVpGotEJN@[84.165.113.145]) by fwd32.t-online.de with esmtp id 1IaWjd-0Az88u0; Wed, 26 Sep 2007 15:15:25 +0200 Date: Wed, 26 Sep 2007 15:15:19 +0200 From: Oliver Herold To: freebsd-current@freebsd.org, current@freebsd.org Message-ID: <20070926131518.GA1297@olymp.home> Mail-Followup-To: freebsd-current@freebsd.org, current@freebsd.org References: <00ec01c7ff85$9604f8f0$5317fb93@KLOBOUCEK> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00ec01c7ff85$9604f8f0$5317fb93@KLOBOUCEK> User-Agent: Mutt/1.5.16 (2007-06-09) X-ID: ZkKZCoZBotvx5Mb3cuyAtjqS8TliA0yM9K1L9r3LCI28z2SrNhI7liGiH2PzmQYewhVpGotEJN X-TOI-MSGID: 00e10438-b26d-4d31-b864-a265e0f20d08 Cc: Subject: Re: x11/nvidia-driver on Sept07 snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 13:15:47 -0000 Hi, I'm using a 7300GT and a 6600GT and they work like a charm, apart from the fact of the changed ABI in Xorg 7.3. So I have to start it with startx -- -ignoreABI. I'm using FreeBSD current since some weeks, build from yesterday. Cheers, Oliver On Tue, Sep 25, 2007 at 05:06:01PM +0200, Petr Holub wrote: > Hi, > > is x11/nvidia-driver supposed to work on September 2007 > -CURRENT snapshot? I've given it a shot and it compiles > fine, kldloads fine, but doesn't detect graphics card > for some reason > > # sysctl -a | fgrep nvi > hw.nvidia.version: NVIDIA UNIX x86 Kernel Module 100.14.11 Wed Jun 13 15:15:08 > PDT 2007 > hw.nvidia.registry.EnableVia4x: 0 > hw.nvidia.registry.EnableALiAGP: 0 > hw.nvidia.registry.NvAGP: 1 > hw.nvidia.registry.EnableAGPSBA: 0 > hw.nvidia.registry.EnableAGPFW: 0 > hw.nvidia.registry.SoftEDIDs: 1 > hw.nvidia.registry.Mobile: 4294967295 > hw.nvidia.registry.ResmanDebugLevel: 4294967295 > hw.nvidia.registry.FlatPanelMode: 0 > hw.nvidia.registry.DevicesConnected: 0 > hw.nvidia.registry.RmLogonRC: 1 > hw.nvidia.registry.DetectPrimaryVga: 1 > hw.nvidia.registry.dwords: > > # pciconf -lv |fgrep -i -A2 -B1 nvi > vgapci0@pci1:0:0: class=0x030000 card=0x04131462 chip=0x039210de rev=0xa1 > hdr=0x00 > vendor = 'Nvidia Corp' > device = 'GeForce 7600 GS' > class = display > > # dmesg | fgrep nvid > (nothing here) > > When attempting to run X, I get: > > (EE) NVIDIA(0): ============= WARNING WARNING WARNING WARNING ============= > (EE) NVIDIA(0): This server has a video driver ABI version of 2.0 but this > (EE) NVIDIA(0): driver is designed to work with versions before 2.0. > (EE) NVIDIA(0): Please check http://www.nvidia.com/ for driver updates or > (EE) NVIDIA(0): downgrade to an X server with a supported driver ABI. > (EE) NVIDIA(0): =========================================================== > (II) Module "ramdac" already built-in > NVIDIA: could not open the device file /dev/nvidiactl (No such file or directory > ). > (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! Please ensure > (EE) NVIDIA(0): that there is a supported NVIDIA GPU in this system, and > (EE) NVIDIA(0): that the NVIDIA device files have been created properly. > (EE) NVIDIA(0): Please consult the NVIDIA README for details. > (EE) NVIDIA(0): *** Aborting *** > (EE) Screen(s) found, but none have a usable configuration. > > > I can submit more info on request. > > TIA, > Petr > > _______________________________________________ > 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" -- If it takes a bloodbath, lets get it over with. No more appeasement. -- Ronald Reagan From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 13:15:47 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FB8716A41B; Wed, 26 Sep 2007 13:15:47 +0000 (UTC) (envelope-from oliver@akephalos.de) Received: from mailout03.sul.t-online.com (mailout03.sul.t-online.de [194.25.134.81]) by mx1.freebsd.org (Postfix) with ESMTP id 5673A13C474; Wed, 26 Sep 2007 13:15:46 +0000 (UTC) (envelope-from oliver@akephalos.de) Received: from fwd32.aul.t-online.de by mailout03.sul.t-online.com with smtp id 1IaWjx-0004Qa-00; Wed, 26 Sep 2007 15:15:45 +0200 Received: from localhost (ZkKZCoZBotvx5Mb3cuyAtjqS8TliA0yM9K1L9r3LCI28z2SrNhI7liGiH2PzmQYewhVpGotEJN@[84.165.113.145]) by fwd32.t-online.de with esmtp id 1IaWjd-0Az88u0; Wed, 26 Sep 2007 15:15:25 +0200 Date: Wed, 26 Sep 2007 15:15:19 +0200 From: Oliver Herold To: freebsd-current@freebsd.org, current@freebsd.org Message-ID: <20070926131518.GA1297@olymp.home> Mail-Followup-To: freebsd-current@freebsd.org, current@freebsd.org References: <00ec01c7ff85$9604f8f0$5317fb93@KLOBOUCEK> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00ec01c7ff85$9604f8f0$5317fb93@KLOBOUCEK> User-Agent: Mutt/1.5.16 (2007-06-09) X-ID: ZkKZCoZBotvx5Mb3cuyAtjqS8TliA0yM9K1L9r3LCI28z2SrNhI7liGiH2PzmQYewhVpGotEJN X-TOI-MSGID: 00e10438-b26d-4d31-b864-a265e0f20d08 Cc: Subject: Re: x11/nvidia-driver on Sept07 snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 13:15:47 -0000 Hi, I'm using a 7300GT and a 6600GT and they work like a charm, apart from the fact of the changed ABI in Xorg 7.3. So I have to start it with startx -- -ignoreABI. I'm using FreeBSD current since some weeks, build from yesterday. Cheers, Oliver On Tue, Sep 25, 2007 at 05:06:01PM +0200, Petr Holub wrote: > Hi, > > is x11/nvidia-driver supposed to work on September 2007 > -CURRENT snapshot? I've given it a shot and it compiles > fine, kldloads fine, but doesn't detect graphics card > for some reason > > # sysctl -a | fgrep nvi > hw.nvidia.version: NVIDIA UNIX x86 Kernel Module 100.14.11 Wed Jun 13 15:15:08 > PDT 2007 > hw.nvidia.registry.EnableVia4x: 0 > hw.nvidia.registry.EnableALiAGP: 0 > hw.nvidia.registry.NvAGP: 1 > hw.nvidia.registry.EnableAGPSBA: 0 > hw.nvidia.registry.EnableAGPFW: 0 > hw.nvidia.registry.SoftEDIDs: 1 > hw.nvidia.registry.Mobile: 4294967295 > hw.nvidia.registry.ResmanDebugLevel: 4294967295 > hw.nvidia.registry.FlatPanelMode: 0 > hw.nvidia.registry.DevicesConnected: 0 > hw.nvidia.registry.RmLogonRC: 1 > hw.nvidia.registry.DetectPrimaryVga: 1 > hw.nvidia.registry.dwords: > > # pciconf -lv |fgrep -i -A2 -B1 nvi > vgapci0@pci1:0:0: class=0x030000 card=0x04131462 chip=0x039210de rev=0xa1 > hdr=0x00 > vendor = 'Nvidia Corp' > device = 'GeForce 7600 GS' > class = display > > # dmesg | fgrep nvid > (nothing here) > > When attempting to run X, I get: > > (EE) NVIDIA(0): ============= WARNING WARNING WARNING WARNING ============= > (EE) NVIDIA(0): This server has a video driver ABI version of 2.0 but this > (EE) NVIDIA(0): driver is designed to work with versions before 2.0. > (EE) NVIDIA(0): Please check http://www.nvidia.com/ for driver updates or > (EE) NVIDIA(0): downgrade to an X server with a supported driver ABI. > (EE) NVIDIA(0): =========================================================== > (II) Module "ramdac" already built-in > NVIDIA: could not open the device file /dev/nvidiactl (No such file or directory > ). > (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! Please ensure > (EE) NVIDIA(0): that there is a supported NVIDIA GPU in this system, and > (EE) NVIDIA(0): that the NVIDIA device files have been created properly. > (EE) NVIDIA(0): Please consult the NVIDIA README for details. > (EE) NVIDIA(0): *** Aborting *** > (EE) Screen(s) found, but none have a usable configuration. > > > I can submit more info on request. > > TIA, > Petr > > _______________________________________________ > 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" -- If it takes a bloodbath, lets get it over with. No more appeasement. -- Ronald Reagan From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 13:38:26 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D51C316A41B for ; Wed, 26 Sep 2007 13:38:26 +0000 (UTC) (envelope-from rnsanchez@wait4.org) Received: from sumo.dreamhost.com (sumo.dreamhost.com [66.33.216.29]) by mx1.freebsd.org (Postfix) with ESMTP id DA0C313C481 for ; Wed, 26 Sep 2007 13:38:26 +0000 (UTC) (envelope-from rnsanchez@wait4.org) Received: from spunkymail-a14.g.dreamhost.com (sd-green-bigip-83.dreamhost.com [208.97.132.83]) by sumo.dreamhost.com (Postfix) with ESMTP id 452331B6700 for ; Wed, 26 Sep 2007 06:05:38 -0700 (PDT) Received: from sauron.lan.box (unknown [201.89.136.100]) by spunkymail-a14.g.dreamhost.com (Postfix) with ESMTP id 5BCC9190E2D for ; Wed, 26 Sep 2007 06:05:36 -0700 (PDT) Date: Wed, 26 Sep 2007 10:05:13 -0300 From: Ricardo Nabinger Sanchez To: freebsd-current@freebsd.org Message-Id: <20070926100513.dfbf3bd8.rnsanchez@wait4.org> In-Reply-To: <00ec01c7ff85$9604f8f0$5317fb93@KLOBOUCEK> References: <00ec01c7ff85$9604f8f0$5317fb93@KLOBOUCEK> Organization: SYS_WAIT4 X-Mailer: Sylpheed 2.4.6 (GTK+ 2.10.14; i386-unknown-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: x11/nvidia-driver on Sept07 snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 13:38:26 -0000 On Tue, 25 Sep 2007 17:06:01 +0200 "Petr Holub" wrote: > When attempting to run X, I get: > > (EE) NVIDIA(0): ============= WARNING WARNING WARNING WARNING > ============= (EE) NVIDIA(0): This server has a video driver ABI > version of 2.0 but this (EE) NVIDIA(0): driver is designed to work > with versions before 2.0. (EE) NVIDIA(0): Please check > http://www.nvidia.com/ for driver updates or (EE) NVIDIA(0): > downgrade to an X server with a supported driver ABI. (EE) NVIDIA(0): > =========================================================== (II) > Module "ramdac" already built-in NVIDIA: could not open the device > file /dev/nvidiactl (No such file or directory ). > (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! Please > ensure (EE) NVIDIA(0): that there is a supported NVIDIA GPU in > this system, and (EE) NVIDIA(0): that the NVIDIA device files have > been created properly. (EE) NVIDIA(0): Please consult the NVIDIA > README for details. (EE) NVIDIA(0): *** Aborting *** > (EE) Screen(s) found, but none have a usable configuration. > > > I can submit more info on request. I'm on -stable, but saw that one too. UPDATING tells you to launch X11 as: startx -- -ignoreABI It really works (I'm on X11). -- Ricardo Nabinger Sanchez rnsanchez@wait4.org Powered by FreeBSD "Left to themselves, things tend to go from bad to worse." From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 14:57:28 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CC5D16A41A for ; Wed, 26 Sep 2007 14:57:28 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 0580F13C48E for ; Wed, 26 Sep 2007 14:57:27 +0000 (UTC) (envelope-from sam@errno.com) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l8QEvQfY094121 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Sep 2007 07:57:26 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <46FA7356.1030807@errno.com> Date: Wed, 26 Sep 2007 07:57:26 -0700 From: Sam Leffler User-Agent: Thunderbird 2.0.0.6 (X11/20070814) MIME-Version: 1.0 To: Nathan Lay References: <46F9E62C.1020701@comcast.net> In-Reply-To: <46F9E62C.1020701@comcast.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-current@freebsd.org Subject: Re: iwi strange 'list scan' output X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 14:57:28 -0000 Nathan Lay wrote: > Hi list, > I am running a CURRENT build as recent as Monday. I used to be really = > annoyed that ifconfig truncated the longer SSID names until I read=20 > somewhere in the man page that the '-v' flag alleviated that problem. = > Just now I tried 'ifconfig -v iwi0 list scan' and it prints out a lot=20 > of these '+?' for some of the access points. Without the '-v' flag,=20 > it behaves normally. I haven't investigated the cause yet. Anybody=20 > experience this? > > Here is the full output: > > SSID BSSID CHAN RATE =20 > S:N INT CAPS > Lamp 00:18:4d:71:5d:36 1 54M =20 > 37:0 100 EPS WPA > linksys 00:1a:70:59:70:cf 6 54M =20 > 31:0 100 E Kleiner Satellit 00:1a:70:4e:4f:32 =20 > 6 54M 22:0 100 EP RSN uc:TKIP+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?,=20 > caps 0x0> WME 7 cwmin 4 cwmax 10 txop 0] VO[aifsn 2 cwmin 3 cwmax 4 txop 94]=20 > VI[aifsn 2 cwmin 2 cwmax 3 txop 47]> > NLRCJM231 00:1c:10:16:5e:03 6 54M =20 > 19:0 100 EP WPA > AndrewMCameron 00:18:4d:80:39:a2 11 54M =20 > 30:0 100 EPS WPA=20 > ATH > TalWireless 00:14:6c:02:a4:82 11 54M =20 > 21:0 100 EP stephm143 00:0f:b5:5c:03:8c =20 > 11 54M 23:0 100 EP Thaleia =20 > 00:14:51:77:00:dd 2 54M 33:0 100 EP WPA km:8021X-PSK> RSN uc:TKIP+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+AES-CCMP+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?,=20 > caps 0x0> > MITCH 00:1b:11:55:d3:d9 3 54M =20 > 23:0 100 EPS WPA RSN uc:?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+= ?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?= +?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?+?,=20 > caps 0x0> WME BK[aifsn 7 cwmin 4 cwmax 10 txop 0] VO[aifsn 2 cwmin 3 cwmax 4 txop=20 > 94] VI[aifsn 2 cwmin 2 cwmax 3 txop 47]> -v causes the information elements to be decoded. In some cases the ie=20 decoding is very rudimentary. Not sure if it's worth adding another=20 option to just lift the ssid length restriction. Sam From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 17:13:37 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CEA4516A419 for ; Wed, 26 Sep 2007 17:13:37 +0000 (UTC) (envelope-from ravna@nerdshack.com) Received: from karen.lavabit.com (karen.lavabit.com [72.249.41.33]) by mx1.freebsd.org (Postfix) with ESMTP id CB60013C455 for ; Wed, 26 Sep 2007 17:13:37 +0000 (UTC) (envelope-from ravna@nerdshack.com) Received: from dispatchd.nerdshack.com (jean.lavabit.com [72.249.41.30]) by karen.lavabit.com (Postfix) with SMTP id E000CC842F for ; Wed, 26 Sep 2007 12:13:36 -0500 (CDT) Received: from toy.firlefanz.org (p54ABE7D8.dip.t-dialin.net [84.171.231.216]) by mail.nerdshack.com with ESMTP Wed, 26 Sep 2007 12:13:36 -0500 Message-ID: <46FA92E0.7090602@nerdshack.com> Date: Wed, 26 Sep 2007 19:12:00 +0200 From: Ravna User-Agent: Thunderbird 2.0.0.6 (X11/20070908) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Can't kill KDE procs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 17:13:37 -0000 I'm running a i386 Current of today. Now I have problems with apps that use kdelibs. They freeze after a few clicks and can't be closed. There are no error messages when started from a terminal. They can be terminated, but still remain in memory - along with their kdeinits - both with "madvpo" status. When trying to reboot, the system gets as far as "all buffers synced" and then just sits there. From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 17:24:58 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D38E916A417 for ; Wed, 26 Sep 2007 17:24:58 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (vlk.vlakno.cz [62.168.28.247]) by mx1.freebsd.org (Postfix) with ESMTP id 9810813C458 for ; Wed, 26 Sep 2007 17:24:58 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 984CD667D37; Wed, 26 Sep 2007 19:24:55 +0200 (CEST) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (vlk.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YH2ZniEQSx6U; Wed, 26 Sep 2007 19:24:54 +0200 (CEST) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 8B28B667D34; Wed, 26 Sep 2007 19:24:54 +0200 (CEST) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.13.8/8.13.8/Submit) id l8QHOrFa091196; Wed, 26 Sep 2007 19:24:53 +0200 (CEST) (envelope-from rdivacky) Date: Wed, 26 Sep 2007 19:24:53 +0200 From: Roman Divacky To: Ravna Message-ID: <20070926172453.GA91155@freebsd.org> References: <46FA92E0.7090602@nerdshack.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46FA92E0.7090602@nerdshack.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: Can't kill KDE procs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 17:24:58 -0000 On Wed, Sep 26, 2007 at 07:12:00PM +0200, Ravna wrote: > I'm running a i386 Current of today. > Now I have problems with apps that use kdelibs. > They freeze after a few clicks and can't be closed. > There are no error messages when started from a terminal. > They can be terminated, but still remain in memory - along with their > kdeinits - both with "madvpo" status. > When trying to reboot, the system gets as far as "all buffers synced" > and then just sits there. already fixed, please update your current to a newer date... From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 17:30:26 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD61316A46B for ; Wed, 26 Sep 2007 17:30:26 +0000 (UTC) (envelope-from ravna@nerdshack.com) Received: from karen.lavabit.com (karen.lavabit.com [72.249.41.33]) by mx1.freebsd.org (Postfix) with ESMTP id B6CD113C478 for ; Wed, 26 Sep 2007 17:30:26 +0000 (UTC) (envelope-from ravna@nerdshack.com) Received: from dispatchd.nerdshack.com (jean.lavabit.com [72.249.41.30]) by karen.lavabit.com (Postfix) with SMTP id EEB60C86CA for ; Wed, 26 Sep 2007 12:30:25 -0500 (CDT) Received: from toy.firlefanz.org (p54ABE7D8.dip.t-dialin.net [84.171.231.216]) by mail.nerdshack.com with ESMTP Wed, 26 Sep 2007 12:30:25 -0500 Message-ID: <46FA96D1.3040205@nerdshack.com> Date: Wed, 26 Sep 2007 19:28:49 +0200 From: Ravna User-Agent: Thunderbird 2.0.0.6 (X11/20070908) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Can't kill KDE procs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 17:30:26 -0000 I fear the problem isn't solved. As already said, the build is of today. You don't think I didn't update sources, do you ? My tree is 3h old. From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 17:44:42 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7E9716A418 for ; Wed, 26 Sep 2007 17:44:41 +0000 (UTC) (envelope-from rink@rink.nu) Received: from mx1.rink.nu (thunderstone.rink.nu [80.112.228.34]) by mx1.freebsd.org (Postfix) with ESMTP id 9FF1E13C44B for ; Wed, 26 Sep 2007 17:44:41 +0000 (UTC) (envelope-from rink@rink.nu) Received: from localhost (localhost [127.0.0.1]) by mx1.rink.nu (Postfix) with ESMTP id BDD3E6D433; Wed, 26 Sep 2007 19:24:58 +0200 (CEST) X-Virus-Scanned: amavisd-new at rink.nu Received: from mx1.rink.nu ([127.0.0.1]) by localhost (thunderstone.rink.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oVHsOiA7BUgC; Wed, 26 Sep 2007 19:24:52 +0200 (CEST) Received: by mx1.rink.nu (Postfix, from userid 1000) id 6BC7C6D432; Wed, 26 Sep 2007 19:24:52 +0200 (CEST) Date: Wed, 26 Sep 2007 19:24:52 +0200 From: Rink Springer To: Ravna Message-ID: <20070926172452.GC91097@rink.nu> References: <46FA92E0.7090602@nerdshack.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46FA92E0.7090602@nerdshack.com> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-current@freebsd.org Subject: Re: Can't kill KDE procs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 17:44:42 -0000 Hi Ravna, On Wed, Sep 26, 2007 at 07:12:00PM +0200, Ravna wrote: > They can be terminated, but still remain in memory - along with their > kdeinits - both with "madvpo" status. This is due to a problem in a VM commit introduced two days ago. It has been fixed in revision 1.384 of src/sys/vm/vm_object.c - update your tree and rebuild. Regards, -- Rink P.W. Springer - http://rink.nu "root is always right" -- the kernel From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 18:21:29 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82E3B16A41A for ; Wed, 26 Sep 2007 18:21:29 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by mx1.freebsd.org (Postfix) with ESMTP id 6F54513C4A3 for ; Wed, 26 Sep 2007 18:21:29 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay13.apple.com (relay13.apple.com [17.128.113.29]) by mail-out4.apple.com (Postfix) with ESMTP id 37A911312D36; Wed, 26 Sep 2007 11:21:29 -0700 (PDT) Received: from relay13.apple.com (unknown [127.0.0.1]) by relay13.apple.com (Symantec Mail Security) with ESMTP id 11ABE2802F; Wed, 26 Sep 2007 11:21:29 -0700 (PDT) X-AuditID: 1180711d-a1b5cbb000006cd8-8f-46faa328a6f7 Received: from [17.214.13.96] (cswiger1.apple.com [17.214.13.96]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay13.apple.com (Apple SCV relay) with ESMTP id DBC6128050; Wed, 26 Sep 2007 11:21:28 -0700 (PDT) In-Reply-To: <46FA2E46.8020303@freebsd.org> References: <20070921102946.T11189@borg> <46F415BF.9010500@FreeBSD.org> <20070921140550.D96923@thebighonker.lerctr.org> <46F41CFF.6080108@FreeBSD.org> <46F58799.1030702@freebsd.org> <46F58B21.8030307@FreeBSD.org> <20070924091558.GB32006@team.vega.ru> <46F78C59.1020801@FreeBSD.org> <20070924080347.O84223@thebighonker.lerctr.org> <20070924144210.GA82735@team.vega.ru> <46F7D7A4.5090007@samsco.org> <46F80A39.3050707@FreeBSD.org> <46F8951C.50904@freebsd.org> <46F8CE67.60206@FreeBSD.org> <46FA2E46.8020303@freebsd.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Chuck Swiger Date: Wed, 26 Sep 2007 11:21:27 -0700 To: Darren Reed X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAA== Cc: Kris Kennaway , freebsd-current@freebsd.org, Larry Rosenman Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 18:21:29 -0000 On Sep 26, 2007, at 3:02 AM, Darren Reed wrote: >> Yes, Solaris does something architecturally different because it >> is apparently acceptable for zfs to use gigabytes of memory by >> default. > > Well, if you were designing a file system for servers, is there any > reason that you wouldn't try to use all of the RAM available? > > A similar thought process goes into having a unified buffer cache that > uses all the free RAM that it can (on a 1.5GB NetBSD box, 1.4GB > is file cache.) This is a fine example. One of the nice notions of a "unified buffer cache" is that you should only store data once in physical RAM, and just use VMOs to provide additional references (perhaps mapped copy- on-write) rather than double-buffering stuff between a processes' address space to dedicated kernel disk I/O buffers before they can be read or written out. A key factor to note is that buffer cache can be paged out as needed (by definition, pretty much), but historically, kernel memory was "wired down" to prevent people from paging out critical things like the VM subsystem or disk drivers. Wired down memory is (or perhaps was) a scarce resource, which is why things like the memory disk [md] implementation recommends using swap-based backing rather than kernel malloc(9)-based backing. I'm not certain whether FreeBSD's kernel memory allocator [malloc(9), zone(9)] even supports the notion of allocating pageable memory rather than memory taken from the fixed KVA region. The manpage implies that calling kernel malloc with M_WAITOK will always return a valid pointer and not NULL, but I'm not convinced this is will be true if you try allocating something larger than the size of KVA and/ or the amount of physical RAM available in the system. > Even if I'm running a desktop workstation, if I'm not there, there's > no reason that ZFS shouldn't be able to encourage the OS to swap > out all of the applications (well as much as can be) if it so desires. > > The problem comes in deciding how strong ZFS's hold should be > and how to apply pressure from other parts of the system that > want to use the RAM as well. Obviously, it does no good to page out your buffer cache to swap-- so if the system is under enough memory pressure to want to use that memory for other tasks, then the right thing to do is to shrink the buffer cache somewhat to attempt to minimize the global page-fault frequency rate. > Now given that we have a ZFS tuning guide, surely the question > we need to ask ourselves is why can't we take the recommendations > from that and make up some code to implement the trends discussed? > > And how do we measure how much memory ZFS is using? "vmstat -m", or maybe there are some sysctls being exposed by ZFS with that info? Regards, -- -Chuck From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 22:12:39 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6506816A421; Wed, 26 Sep 2007 22:12:39 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 5AAB713C448; Wed, 26 Sep 2007 22:12:37 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46FAD957.3060208@FreeBSD.org> Date: Thu, 27 Sep 2007 00:12:39 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Darren Reed References: <20070921102946.T11189@borg> <46F415BF.9010500@FreeBSD.org> <20070921140550.D96923@thebighonker.lerctr.org> <46F41CFF.6080108@FreeBSD.org> <46F58799.1030702@freebsd.org> <46F58B21.8030307@FreeBSD.org> <20070924091558.GB32006@team.vega.ru> <46F78C59.1020801@FreeBSD.org> <20070924080347.O84223@thebighonker.lerctr.org> <20070924144210.GA82735@team.vega.ru> <46F7D7A4.5090007@samsco.org> <46F80A39.3050707@FreeBSD.org> <46F8951C.50904@freebsd.org> <46F8CE67.60206@FreeBSD.org> <46FA2E46.8020303@freebsd.org> In-Reply-To: <46FA2E46.8020303@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Larry Rosenman Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 22:12:39 -0000 Darren Reed wrote: > Kris Kennaway wrote: >> Darren Reed wrote: >>> Kris Kennaway wrote: >>>> ... >>>> Well yes, that is one hypothesis, but the evidence points elsewhere >>>> as well. Prior the change you reference, some of my zfs machines >>>> would run for weeks before hitting a load pattern that exhausted >>>> their kmem_map and triggered the panic. Also unless I have missed >>>> it I am not seeing the sudden flood of panic reports that may >>>> indicate sudden breakage. It is quite possible that this particular >>>> report has nothing to do with the recent change. >>> >>> Indeed. >>> >>> But here's something else to ponder... >>> >>> I've been using ZFS since it was internal beta at Sun, at first on >>> i386 and later on amd64. >>> I've never run into this kind of panic on Solaris. System can get >>> very slow, yes, with >>> ZFS hogging lots of memory, but it never panic'd because of it. >>> >>> We need to come up with a strategy here to solve this problem, be it >>> fixing the kmem >>> virtual memory or fixing zfs. >> >> Yes, Solaris does something architecturally different because it is >> apparently acceptable for zfs to use gigabytes of memory by default. > > Well, if you were designing a file system for servers, is there any > reason that you wouldn't try to use all of the RAM available? No, but it's different to what FreeBSD does. Especially on i386. Kris From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 22:20:35 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8D1316A421 for ; Wed, 26 Sep 2007 22:20:35 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id DF8BC13C467; Wed, 26 Sep 2007 22:20:34 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46FADB35.2090708@FreeBSD.org> Date: Thu, 27 Sep 2007 00:20:37 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Joao Pedras References: <46FA0C14.10201@webvolution.net> In-Reply-To: <46FA0C14.10201@webvolution.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: lock up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 22:20:35 -0000 Joao Pedras wrote: > Greetings all! > > A system (Tyan S2932) I am testing CURRENT amd64 with is experiencing a > strange lock up. No panic, not much on the console, just a lock up, freeze. > > I first noticed the issue while tailing a build in a ssh session over a > vpn connection. On the local network the issue doesn't seem to occur. > I can reproduce the lock up all the time. > > Last I tried, the system was running CURRENT from a couple hours ago. > > I have tried: > > - 4BSD and ULE > - switching network cards > - taking the IPMI card out (seems to work locally with freeipmi and > ipmitoll remotely) > - enabled/disabled "redirection after post" (BIOS setting) > - without debug > - without IPv6 and friends (see rtfree below) > > dmesg and pciconf attached. The dmesg is after a lock up. > rtfree pops a few times before the lock up. I noticed from a recent post > some action was taken and the related patch is there (ie. today's CURRENT). > > The system had a fresh install this past weekend and the LSI MegaRAID > array doesn't contain any data, it is just mounted. The system boots off > the onboard LSI SAS (couple disks in RAID 1). > > Thank you for your input. Break to DDB and obtain process traces, etc. See the developers handbook. Kris From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 00:14:08 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56E8716A417 for ; Thu, 27 Sep 2007 00:14:08 +0000 (UTC) (envelope-from nslay@comcast.net) Received: from alnrmhc16.comcast.net (alnrmhc16.comcast.net [206.18.177.56]) by mx1.freebsd.org (Postfix) with ESMTP id 1D68E13C448 for ; Thu, 27 Sep 2007 00:14:08 +0000 (UTC) (envelope-from nslay@comcast.net) Received: from antenna.local (c-68-35-224-189.hsd1.fl.comcast.net[68.35.224.189]) by comcast.net (alnrmhc16) with ESMTP id <20070927001407b1600bqhive>; Thu, 27 Sep 2007 00:14:07 +0000 Message-ID: <46FAF5C1.4070106@comcast.net> Date: Wed, 26 Sep 2007 20:13:53 -0400 From: Nathan Lay User-Agent: Thunderbird 2.0.0.6 (X11/20070925) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: iwi oddities X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 00:14:08 -0000 Hi list, With these rc.conf flags ifconfig_iwi0="powersave wme -bgscan" iwi decides to bring itself up on boot. iwi in 6.2 never brought itself unless 'up' was explicitly specified. Though, my 6.2 rc.conf settings are more along the lines of ifconfig_iwi0="wme bmiss 100" Off topic, why the large bmiss? Well, iwi, in both 6.2 and 7.0 (less so in 7.0) decide to have problems with WPA (i.e. sometimes wpa_supplicant 0.4.8 and 0.5.8, will cycle authentication over and over again in short intervals and I'll have to restart wpa_supplicant or reload if_iwi), or iwi will all the sudden disassociates itself from the AP for no apparent reason. I read somewhere a large beacon miss value helps alleviate these problems with iwi. Sometimes when iwi is reset (i.e. due to firmware errors), I am not able to transmit or recieve anything unless I delete the gateway's arp entry even though I am associated and have an IP. I don't think this problem has to do with iwi, but it is annoying to find that I am no longer able to send or receive data out of the blue. This happens regardless of iwi's configuration or load. Anybody experience these iwi oddities? I am pleased to say that iwi doesn't appear to exhibit that annoying DMA error that was present in 6.2. Is there any useful information I can collect? Best Regards, Nathan Lay From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 01:03:23 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2AA916A419 for ; Thu, 27 Sep 2007 01:03:23 +0000 (UTC) (envelope-from alex.kovalenko@verizon.net) Received: from vms042pub.verizon.net (vms042pub.verizon.net [206.46.252.42]) by mx1.freebsd.org (Postfix) with ESMTP id 7F19613C45D for ; Thu, 27 Sep 2007 01:03:23 +0000 (UTC) (envelope-from alex.kovalenko@verizon.net) Received: from [10.0.3.231] ([141.150.94.61]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JP000EU85LCUQ31@vms042.mailsrvcs.net> for current@freebsd.org; Wed, 26 Sep 2007 20:03:13 -0500 (CDT) Date: Wed, 26 Sep 2007 21:03:02 -0400 From: "Alexandre \"Sunny\" Kovalenko" To: current@freebsd.org Message-id: <1190854982.852.10.camel@RabbitsDen> MIME-version: 1.0 X-Mailer: Evolution 2.10.3 FreeBSD GNOME Team Port Content-type: text/plain Content-transfer-encoding: 7bit Cc: Subject: Panic unloading if_ath X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 01:03:23 -0000 I am seeing this on the relatively regular basis if I am trying to unload if_ath. System is CURRENT as of September 20th and Atheros part is ath0: mem 0xedf00000-0xedf0ffff irq 17 at device 0.0 on pci3 Unfortunately, I do not have 100% reliable way to reproduce it, but approximate scenario is as follows: -- Network becomes unresponsive -- I am setting roaming to DEVICE (I should make it a habit of doing it right after boot, because this setting is not picked up from rc.conf, but occasionally I forget). -- when the step above does not work, I try to kldunload if_ath. Network interface is configured with the static address using wpa_supplicant with two networks with the same priority visible at the same time. If there is any additional information, I can provide, please, let me know. Unread portion of the kernel message buffer: <5>ath0: link state changed to DOWN kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x188 fault code = supervisor read, page not present instruction pointer = 0x20:0xc04ff0a5 stack pointer = 0x28:0xe38859d8 frame pointer = 0x28:0xe38859f0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 908 (wpa_supplicant) trap number = 12 panic: page fault cpuid = 1 Uptime: 22h34m46s Physical memory: 2030 MB Dumping 213 MB: 198 182 166 150 134 118 102 86 70 54 38 22 6 #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc050b1b7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #2 0xc050b4ab in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:563 #3 0xc06c8293 in trap_fatal (frame=0xe3885998, eva=392) at /usr/src/sys/i386/i386/trap.c:872 #4 0xc06c8bd1 in trap (frame=0xe3885998) at /usr/src/sys/i386/i386/trap.c:277 #5 0xc06aee8b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #6 0xc04ff0a5 in _mtx_lock_sleep (m=0xc4e4e10c, tid=3301954624, opts=0, file=0xc5642f2c "/usr/src/sys/modules/ath/../../dev/ath/if_ath.c", line=2215) at /usr/src/sys/kern/kern_mutex.c:360 #7 0xc04ff4d2 in _mtx_lock_flags (m=0xc4e4e10c, opts=0, file=0xc5642f2c "/usr/src/sys/modules/ath/../../dev/ath/if_ath.c", line=2215) at /usr/src/sys/kern/kern_mutex.c:186 #8 0xc56398d1 in ?? () #9 0xc4e4e10c in ?? () #10 0x00000000 in ?? () #11 0xc5642f2c in ?? () #12 0x000008a7 in ?? () #13 0xe3885a38 in ?? () #14 0xc0865408 in ?? () #15 0xc565d22c in ?? () #16 0x00000014 in ?? () #17 0xca5e80e0 in ?? () #18 0xe3885b28 in ?? () #19 0xc086ff4f in ?? () #20 0xc565d22c in ?? () #21 0xc565e4a4 in ?? () #22 0x00000007 in ?? () #23 0xc0513b96 in mi_switch (flags=Variable "flags" is not available. ) at /usr/src/sys/kern/kern_synch.c:442 Previous frame inner to this frame (corrupt stack?) (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc050b1b7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #2 0xc050b4ab in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:563 #3 0xc06c8293 in trap_fatal (frame=0xe3885998, eva=392) at /usr/src/sys/i386/i386/trap.c:872 #4 0xc06c8bd1 in trap (frame=0xe3885998) at /usr/src/sys/i386/i386/trap.c:277 #5 0xc06aee8b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #6 0xc04ff0a5 in _mtx_lock_sleep (m=0xc4e4e10c, tid=3301954624, opts=0, file=0xc5642f2c "/usr/src/sys/modules/ath/../../dev/ath/if_ath.c", line=2215) at /usr/src/sys/kern/kern_mutex.c:360 #7 0xc04ff4d2 in _mtx_lock_flags (m=0xc4e4e10c, opts=0, file=0xc5642f2c "/usr/src/sys/modules/ath/../../dev/ath/if_ath.c", line=2215) at /usr/src/sys/kern/kern_mutex.c:186 #8 0xc56398d1 in ?? () #9 0xc4e4e10c in ?? () #10 0x00000000 in ?? () #11 0xc5642f2c in ?? () #12 0x000008a7 in ?? () #13 0xe3885a38 in ?? () #14 0xc0865408 in ?? () #15 0xc565d22c in ?? () #16 0x00000014 in ?? () #17 0xca5e80e0 in ?? () #18 0xe3885b28 in ?? () #19 0xc086ff4f in ?? () #20 0xc565d22c in ?? () #21 0xc565e4a4 in ?? () #22 0x00000007 in ?? () #23 0xc0513b96 in mi_switch (flags=Variable "flags" is not available. ) at /usr/src/sys/kern/kern_synch.c:442 (kgdb) -- Alexandre "Sunny" Kovalenko From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 01:31:25 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACA6216A417 for ; Thu, 27 Sep 2007 01:31:25 +0000 (UTC) (envelope-from staale@kristoffersen.ws) Received: from smtp.bluecom.no (smtp.bluecom.no [193.75.75.28]) by mx1.freebsd.org (Postfix) with ESMTP id 55F8713C46E for ; Thu, 27 Sep 2007 01:31:25 +0000 (UTC) (envelope-from staale@kristoffersen.ws) Received: from eschew.pusen.org (unknown [193.69.145.10]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.bluecom.no (Postfix) with ESMTP id 292881700E0 for ; Thu, 27 Sep 2007 03:01:45 +0200 (CEST) Received: from chiller by eschew.pusen.org with local (Exim 4.67) (envelope-from ) id 1Iahl5-00033i-VB for freebsd-current@freebsd.org; Thu, 27 Sep 2007 03:01:39 +0200 Date: Thu, 27 Sep 2007 03:01:39 +0200 From: =?iso-8859-1?Q?St=E5le?= Kristoffersen To: freebsd-current@freebsd.org Message-ID: <20070927010139.GC22695@eschew.pusen.org> References: <46A7B47F.3050300@berkeley.edu> <46A7B607.2070207@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <46A7B607.2070207@samsco.org> User-Agent: Mutt/1.5.13 (2006-08-11) Subject: Re: Are SATA port multipliers supported in -CURRENT? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 01:31:25 -0000 On 2007-07-25 at 14:43, Scott Long wrote: > Steven Schlansker wrote: > > Hello everyone, > > I am considering buying a SiI 3132 SATA card along with a 5-1 port > > multiplier. I'm trying to see if FreeBSD supports such a configuration, > > but the only reference found to port multipliers and FreeBSD was some > > poor, lonely man asking about a "porn multiplier" crashing his system on > > startup. :-p > > The thread trailed off quickly, without resolution. > > > > So my question is: Are port multipliers supported in CURRENT? Are > > there any caveats? I don't see anything in UPDATING, the handbook, or > > our friend Google. I want to check that it is supported before I drop > > $80 on it :) Thanks a bunch! > > Steven > > They are only supported at the moment by controllers that are > intelligent enough to hide the details of how they work from the OS. > The SiI family probably doesn't fall into this category. I'm working > on this as part of a larger SATA/SAS/SCSI/FC overhaul, but it'll be > a few months before there are any results. Whats the status of freebsd's port multiplier support? I'm looking into buying a Norco DS-1220, http://www.norcotek.com/item_detail.php?categoryid=12&modelno=ds1220 (but without the controller) Will it work, and if yes what controllers would it work with? -- Ståle Kristoffersen From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 01:39:25 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8B6116A419 for ; Thu, 27 Sep 2007 01:39:25 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 866DA13C459 for ; Thu, 27 Sep 2007 01:39:25 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l8R1dLKS066089; Wed, 26 Sep 2007 19:39:22 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <46FB09C5.9080506@samsco.org> Date: Wed, 26 Sep 2007 19:39:17 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4 MIME-Version: 1.0 To: =?ISO-8859-1?Q?St=E5le_Kristoffersen?= References: <46A7B47F.3050300@berkeley.edu> <46A7B607.2070207@samsco.org> <20070927010139.GC22695@eschew.pusen.org> In-Reply-To: <20070927010139.GC22695@eschew.pusen.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Wed, 26 Sep 2007 19:39:22 -0600 (MDT) X-Spam-Status: No, score=-1.4 required=5.5 tests=ALL_TRUSTED,DRUGS_PAIN autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-current@freebsd.org Subject: Re: Are SATA port multipliers supported in -CURRENT? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 01:39:26 -0000 Ståle Kristoffersen wrote: > On 2007-07-25 at 14:43, Scott Long wrote: >> Steven Schlansker wrote: >>> Hello everyone, >>> I am considering buying a SiI 3132 SATA card along with a 5-1 port >>> multiplier. I'm trying to see if FreeBSD supports such a configuration, >>> but the only reference found to port multipliers and FreeBSD was some >>> poor, lonely man asking about a "porn multiplier" crashing his system on >>> startup. :-p >>> The thread trailed off quickly, without resolution. >>> >>> So my question is: Are port multipliers supported in CURRENT? Are >>> there any caveats? I don't see anything in UPDATING, the handbook, or >>> our friend Google. I want to check that it is supported before I drop >>> $80 on it :) Thanks a bunch! >>> Steven >> They are only supported at the moment by controllers that are >> intelligent enough to hide the details of how they work from the OS. >> The SiI family probably doesn't fall into this category. I'm working >> on this as part of a larger SATA/SAS/SCSI/FC overhaul, but it'll be >> a few months before there are any results. > > Whats the status of freebsd's port multiplier support? > I'm looking into buying a Norco DS-1220, > http://www.norcotek.com/item_detail.php?categoryid=12&modelno=ds1220 > (but without the controller) > Will it work, and if yes what controllers would it work with? > It might work with an LSI SAS controller. I still don't have support written for generic SAS/SATA controllers. Scott From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 01:41:53 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2182516A418; Thu, 27 Sep 2007 01:41:53 +0000 (UTC) (envelope-from beech@FreeBSD.org) Received: from stargate.alaskaparadise.com (137-42-178-69.gci.net [69.178.42.137]) by mx1.freebsd.org (Postfix) with ESMTP id 60E8113C480; Thu, 27 Sep 2007 01:41:51 +0000 (UTC) (envelope-from beech@FreeBSD.org) Received: by stargate.alaskaparadise.com (Postfix, from userid 125) id 3BCA6875B; Wed, 26 Sep 2007 17:33:03 -0800 (AKDT) Received: from [127.0.0.1] (zardoz.alaskaparadise.com [172.16.0.5]) by stargate.alaskaparadise.com (Postfix) with ESMTP id 210DF7EB0; Wed, 26 Sep 2007 17:29:01 -0800 (AKDT) Message-ID: <46FB0752.1040006@FreeBSD.org> Date: Wed, 26 Sep 2007 17:28:50 -0800 From: Beech Rintoul User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: freebsd-current@freebsd.org, flz@freebsd.org Content-Type: multipart/mixed; boundary="------------060201050108000805050608" Cc: Subject: Yesterday's -current breaks xorg X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 01:41:53 -0000 This is a multi-part message in MIME format. --------------060201050108000805050608 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I wasn't sure which list to send this, so I'll start here. -CURRENT from yesterday breaks xorg (just hangs). log attached Beech -- --------------------------------------------------------------------------------------- Beech Rintoul - FreeBSD Developer - beech@FreeBSD.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.FreeBSD.org/releases/6.2R/announce.html --------------------------------------------------------------------------------------- --------------060201050108000805050608 Content-Type: text/plain; name="xorg.log" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="xorg.log" X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.0-CURRENT i386 Current Operating System: FreeBSD stargate.alaskaparadise.com 7.0-CURRENT FreeBSD 7.0-CURRENT #11: Wed Sep 26 15:56:16 AKDT 2007 root@stargate.alaskaparadise.com:/usr/obj/usr/src/sys/STARGATE i386 Build Date: 13 September 2007 11:40:29PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 26 17:04:09 2007 (==) Using config file: "/usr/local/lib/X11/xorg.conf" (==) ServerLayout "X.org Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (==) Automatically adding devices (==) Automatically enabling devices (==) Including the default font path /usr/local/lib/X11/fonts/misc/,/usr/local/lib/X11/fonts/TTF/,/usr/local/lib/X11/fonts/OTF,/usr/local/lib/X11/fonts/Type1/,/usr/local/lib/X11/fonts/100dpi/,/usr/local/lib/X11/fonts/75dpi/. (**) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, /usr/local/share/ghostscript/fonts/, /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/ (**) RgbPath set to "/usr/local/share/X11/rgb" (**) ModulePath set to "/usr/local/lib/xorg/modules" (II) Loader magic: 0x82423e0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on freebsd (II) LoadModule: "pcidata" (II) Loading /usr/local/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x00000000, mode1Res1 = 0x80000000 (WW) OS did not count PCI devices, guessing wildly (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1039,0620 card 0000,0000 rev 02 class 06,00,00 hdr 80 (II) PCI: 00:00:1: chip 1039,5513 card 1039,5513 rev d0 class 01,01,8a hdr 80 (II) PCI: 00:01:0: chip 1039,0008 card 0000,0000 rev b1 class 06,01,00 hdr 80 (II) PCI: 00:01:1: chip 1039,0009 card 0000,0000 rev 00 class ff,00,00 hdr 80 (II) PCI: 00:01:2: chip 1039,7001 card 0000,0000 rev 11 class 0c,03,10 hdr 80 (II) PCI: 00:02:0: chip 1039,0001 card 0000,0000 rev 00 class 06,04,00 hdr 01 (II) PCI: 00:06:0: chip 1013,6003 card 1013,6003 rev 01 class 04,01,00 hdr 00 (II) PCI: 00:0a:0: chip 11ad,c115 card 11ad,c001 rev 25 class 02,00,00 hdr 00 (II) PCI: 00:0b:0: chip 1186,1300 card 1186,1301 rev 10 class 02,00,00 hdr 00 (II) PCI: 00:0c:0: chip 168c,0013 card 1186,3a14 rev 01 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 1039,6306 card 1039,6306 rev 2a class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:1:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:2:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set) (II) Bus 1 I/O range: [0] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[B] [1] -1 0 0x0000c400 - 0x0000c4ff (0x100) IX[B] [2] -1 0 0x0000c800 - 0x0000c8ff (0x100) IX[B] [3] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xf7f00000 - 0xf7ffffff (0x100000) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0xf7000000 - 0xf77fffff (0x800000) MX[B] (--) PCI:*(1:0:0) Silicon Integrated Systems [SiS] 530/620 PCI/AGP VGA Display Adapter rev 42, Mem @ 0xf7000000/23, 0xf7fe0000/16, I/O @ 0xcc00/7 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) PCI Memory resource overlap reduced 0xf8000000 from 0xffffffff to 0xf7ffffff (II) Active PCI resource ranges: [0] -1 0 0xfedf0000 - 0xfedfffff (0x10000) MX[B]E [1] -1 0 0xfeded800 - 0xfededfff (0x800) MX[B]E [2] -1 0 0xfededc00 - 0xfededfff (0x400) MX[B]E [3] -1 0 0xfec00000 - 0xfeffffff (0x400000) MX[B]E [4] -1 0 0xfedee000 - 0xfedeffff (0x2000) MX[B]E [5] -1 0 0xfedef000 - 0xfedeffff (0x1000) MX[B]E [6] -1 0 0xf8000000 - 0xf7ffffff (0x0) MX[B]EO [7] -1 0 0xf7fe0000 - 0xf7feffff (0x10000) MX[B](B) [8] -1 0 0xf7000000 - 0xf77fffff (0x800000) MX[B](B) [9] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [10] -1 0 0x0000d800 - 0x0000d8ff (0x100) IX[B]E [11] -1 0 0x0000dcf0 - 0x0000dcff (0x10) IX[B]E [12] -1 0 0x00000374 - 0x00000377 (0x4) IX[B]E [13] -1 0 0x00000170 - 0x0000017f (0x10) IX[B]E [14] -1 0 0x000003f4 - 0x000003f7 (0x4) IX[B]E [15] -1 0 0x000001f0 - 0x000001ff (0x10) IX[B]E [16] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B](B) (II) PCI Memory resource overlap reduced 0xfeded800 from 0xfededfff to 0xfededbff (II) PCI Memory resource overlap reduced 0xfec00000 from 0xfeffffff to 0xfecfffff (II) PCI Memory resource overlap reduced 0xfedee000 from 0xfedeffff to 0xfedeefff (II) Active PCI resource ranges after removing overlaps: [0] -1 0 0xfedf0000 - 0xfedfffff (0x10000) MX[B]E [1] -1 0 0xfeded800 - 0xfededbff (0x400) MX[B]E [2] -1 0 0xfededc00 - 0xfededfff (0x400) MX[B]E [3] -1 0 0xfec00000 - 0xfecfffff (0x100000) MX[B]E [4] -1 0 0xfedee000 - 0xfedeefff (0x1000) MX[B]E [5] -1 0 0xfedef000 - 0xfedeffff (0x1000) MX[B]E [6] -1 0 0xf8000000 - 0xf7ffffff (0x0) MX[B]EO [7] -1 0 0xf7fe0000 - 0xf7feffff (0x10000) MX[B](B) [8] -1 0 0xf7000000 - 0xf77fffff (0x800000) MX[B](B) [9] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [10] -1 0 0x0000d800 - 0x0000d8ff (0x100) IX[B]E [11] -1 0 0x0000dcf0 - 0x0000dcff (0x10) IX[B]E [12] -1 0 0x00000374 - 0x00000377 (0x4) IX[B]E [13] -1 0 0x00000170 - 0x0000017f (0x10) IX[B]E [14] -1 0 0x000003f4 - 0x000003f7 (0x4) IX[B]E [15] -1 0 0x000001f0 - 0x000001ff (0x10) IX[B]E [16] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B](B) (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) All system resource ranges: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xfedf0000 - 0xfedfffff (0x10000) MX[B]E [5] -1 0 0xfeded800 - 0xfededbff (0x400) MX[B]E [6] -1 0 0xfededc00 - 0xfededfff (0x400) MX[B]E [7] -1 0 0xfec00000 - 0xfecfffff (0x100000) MX[B]E [8] -1 0 0xfedee000 - 0xfedeefff (0x1000) MX[B]E [9] -1 0 0xfedef000 - 0xfedeffff (0x1000) MX[B]E [10] -1 0 0xf8000000 - 0xf7ffffff (0x0) MX[B]EO [11] -1 0 0xf7fe0000 - 0xf7feffff (0x10000) MX[B](B) [12] -1 0 0xf7000000 - 0xf77fffff (0x800000) MX[B](B) [13] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [14] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [15] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [16] -1 0 0x0000d800 - 0x0000d8ff (0x100) IX[B]E [17] -1 0 0x0000dcf0 - 0x0000dcff (0x10) IX[B]E [18] -1 0 0x00000374 - 0x00000377 (0x4) IX[B]E [19] -1 0 0x00000170 - 0x0000017f (0x10) IX[B]E [20] -1 0 0x000003f4 - 0x000003f7 (0x4) IX[B]E [21] -1 0 0x000001f0 - 0x000001ff (0x10) IX[B]E [22] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B](B) (II) "extmod" will be loaded. This was enabled by default and also specified in the config file. (II) "dbe" will be loaded. This was enabled by default and also specified in the config file. (II) "glx" will be loaded. This was enabled by default and also specified in the config file. (II) "freetype" will be loaded. This was enabled by default and also specified in the config file. (II) "type1" will be loaded. This was enabled by default and also specified in the config file. (II) "record" will be loaded. This was enabled by default and also specified in the config file. (II) "dri" will be loaded. This was enabled by default and also specified in the config file. (II) LoadModule: "extmod" (II) Loading /usr/local/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "record" (II) Loading /usr/local/lib/xorg/modules/extensions//librecord.so (II) Module record: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.13.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension RECORD (II) LoadModule: "dbe" (II) Loading /usr/local/lib/xorg/modules/extensions//libdbe.so (II) Module dbe: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "glx" (II) Loading /usr/local/lib/xorg/modules/extensions//libglx.so (II) Module glx: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.3 (==) AIGLX disabled (II) Loading extension GLX (II) LoadModule: "xtrap" (II) Loading /usr/local/lib/xorg/modules/extensions//libxtrap.so (II) Module xtrap: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension DEC-XTRAP (II) LoadModule: "dri" (II) Loading /usr/local/lib/xorg/modules/extensions//libdri.so (II) Module dri: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.3 (II) Loading extension XFree86-DRI (II) LoadModule: "freetype" (II) Loading /usr/local/lib/xorg/modules//fonts/libfreetype.so (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project" compiled for 1.4.0, module version = 2.1.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.5 (II) Loading font FreeType (II) LoadModule: "type1" (II) Loading /usr/local/lib/xorg/modules//fonts/libtype1.so (II) Module type1: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.2 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.5 (II) Loading font Type1 (II) LoadModule: "sis" (II) Loading /usr/local/lib/xorg/modules/drivers//sis_drv.so (II) Module sis: vendor="X.Org Foundation" compiled for 1.4.0, module version = 0.7.1 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 2.0 (II) LoadModule: "mouse" (II) Loading /usr/local/lib/xorg/modules/input//mouse_drv.so (II) Module mouse: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.2.2 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 2.0 (II) LoadModule: "kbd" (II) Loading /usr/local/lib/xorg/modules/input//kbd_drv.so (II) Module kbd: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.2.2 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 2.0 (II) SIS: driver for SiS chipsets: SIS5597/5598, SIS530/620, SIS6326/AGP/DVD, SIS300/305, SIS630/730, SIS540, SIS315, SIS315H, SIS315PRO/E, SIS550, SIS650/M650/651/740, SIS330(Xabre), SIS660/[M]661[F|M]X/[M]670/[M]741[GX]/[M]760[GX]/[M]761[GX]/[M]770[GX], SIS340 (II) SIS: driver for XGI chipsets: Volari Z7 (XG20), Volari V3XT/V5/V8/Duo (XG40) (II) Primary Device is: PCI 01:00:0 (--) Chipset SIS530/620 found (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xfedf0000 - 0xfedfffff (0x10000) MX[B]E [5] -1 0 0xfeded800 - 0xfededbff (0x400) MX[B]E [6] -1 0 0xfededc00 - 0xfededfff (0x400) MX[B]E [7] -1 0 0xfec00000 - 0xfecfffff (0x100000) MX[B]E [8] -1 0 0xfedee000 - 0xfedeefff (0x1000) MX[B]E [9] -1 0 0xfedef000 - 0xfedeffff (0x1000) MX[B]E [10] -1 0 0xf8000000 - 0xf7ffffff (0x0) MX[B]EO [11] -1 0 0xf7fe0000 - 0xf7feffff (0x10000) MX[B](B) [12] -1 0 0xf7000000 - 0xf77fffff (0x800000) MX[B](B) [13] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [14] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [15] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [16] -1 0 0x0000d800 - 0x0000d8ff (0x100) IX[B]E [17] -1 0 0x0000dcf0 - 0x0000dcff (0x10) IX[B]E [18] -1 0 0x00000374 - 0x00000377 (0x4) IX[B]E [19] -1 0 0x00000170 - 0x0000017f (0x10) IX[B]E [20] -1 0 0x000003f4 - 0x000003f7 (0x4) IX[B]E [21] -1 0 0x000001f0 - 0x000001ff (0x10) IX[B]E [22] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B](B) (II) resource ranges after probing: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xfedf0000 - 0xfedfffff (0x10000) MX[B]E [5] -1 0 0xfeded800 - 0xfededbff (0x400) MX[B]E [6] -1 0 0xfededc00 - 0xfededfff (0x400) MX[B]E [7] -1 0 0xfec00000 - 0xfecfffff (0x100000) MX[B]E [8] -1 0 0xfedee000 - 0xfedeefff (0x1000) MX[B]E [9] -1 0 0xfedef000 - 0xfedeffff (0x1000) MX[B]E [10] -1 0 0xf8000000 - 0xf7ffffff (0x0) MX[B]EO [11] -1 0 0xf7fe0000 - 0xf7feffff (0x10000) MX[B](B) [12] -1 0 0xf7000000 - 0xf77fffff (0x800000) MX[B](B) [13] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [14] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [15] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [17] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [18] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [19] -1 0 0x0000d800 - 0x0000d8ff (0x100) IX[B]E [20] -1 0 0x0000dcf0 - 0x0000dcff (0x10) IX[B]E [21] -1 0 0x00000374 - 0x00000377 (0x4) IX[B]E [22] -1 0 0x00000170 - 0x0000017f (0x10) IX[B]E [23] -1 0 0x000003f4 - 0x000003f7 (0x4) IX[B]E [24] -1 0 0x000001f0 - 0x000001ff (0x10) IX[B]E [25] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B](B) [26] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [27] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (II) SIS(0): SiS driver (2005/09/20-1, compiled for X.org 1.4.0.0) (II) SIS(0): Copyright (C) 2001-2005 Thomas Winischhofer and others (II) SIS(0): *** See http://www.winischhofer.at/linuxsisvga.shtml (II) SIS(0): *** for documentation and updates. (--) SIS(0): Relocated I/O registers at 0xCC00 (==) SIS(0): Write-combining range (0xa0000,0x10000) was already clear (II) Loading sub module "ramdac" (II) LoadModule: "ramdac"(II) Module "ramdac" already built-in (**) SIS(0): Depth 24, (--) framebuffer bpp 32 (==) SIS(0): RGB weight 888 (==) SIS(0): Default visual is TrueColor (==) SIS(0): Fast VRAM timing enabled (for read only) (==) SIS(0): Using XAA acceleration architecture (==) SIS(0): Using HW cursor (==) SIS(0): TurboQueue disabled (==) SIS(0): DRI disabled (--) SIS(0): Memory clock: 65.146 MHz (--) SIS(0): DRAM bus width: 64 bit (--) SIS(0): Linear framebuffer at 0xF7000000 (--) SIS(0): MMIO registers at 0xF7FE0000 (size 64K) (--) SIS(0): VideoRAM: 4096 KB (II) SIS(0): Using 4094K of framebuffer memory at offset 0K (--) SIS(0): Hardware supports one video overlay (==) SIS(0): Using gamma correction (1.0, 1.0, 1.0) (II) SIS(0): Gamma correction is enabled (--) SIS(0): Maximum pixel clock at 32 bpp is 91.2044 MHz (II) Loading sub module "ddc" (II) LoadModule: "ddc"(II) Module "ddc" already built-in (II) Loading sub module "vbe" (II) LoadModule: "vbe" (II) Loading /usr/local/lib/xorg/modules//libvbe.so (II) Module vbe: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.1.0 ABI class: X.Org Video Driver, version 2.0 (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/local/lib/xorg/modules//libint10.so (II) Module int10: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (II) SIS(0): initializing int10 (==) SIS(0): Write-combining range (0xa0000,0x20000) was already clear (==) SIS(0): Write-combining range (0xc0000,0x40000) was already clear (II) SIS(0): Primary V_BIOS segment is: 0xc000 (==) SIS(0): Write-combining range (0x0,0x1000) was already clear (==) SIS(0): Write-combining range (0x0,0x1000) was already clear (==) SIS(0): Write-combining range (0x0,0x1000) was already clear (II) SIS(0): VESA BIOS detected (II) SIS(0): VESA VBE Version 2.0 (II) SIS(0): VESA VBE Total Mem: 4096 kB (II) SIS(0): VESA VBE OEM: SiS (II) SIS(0): VESA VBE OEM Software Rev: 1.0 (II) SIS(0): VESA VBE OEM Vendor: Silicon Integrated Systems Corp. (II) SIS(0): VESA VBE OEM Product: 6306 (II) SIS(0): VESA VBE OEM Product Rev: 0A (II) Loading sub module "ddc" (II) LoadModule: "ddc"(II) Module "ddc" already built-in (==) SIS(0): Write-combining range (0x0,0x1000) was already clear (==) SIS(0): Write-combining range (0x0,0x1000) was already clear (II) SIS(0): VESA VBE DDC supported (II) SIS(0): VESA VBE DDC Level 2 (II) SIS(0): VESA VBE DDC transfer in appr. 1 sec. (==) SIS(0): Write-combining range (0x0,0x1000) was already clear (==) SIS(0): Write-combining range (0x0,0x1000) was already clear (II) SIS(0): VESA VBE DDC read successfully (--) SIS(0): VBE CRT1 DDC monitor info: (II) SIS(0): Manufacturer: GWY Model: 7658 Serial#: 294966 (II) SIS(0): Year: 1998 Week: 10 (II) SIS(0): EDID Version: 1.1 (II) SIS(0): Analog Display Input, Input Voltage Level: 0.714/0.286 V (II) SIS(0): Sync: Separate (II) SIS(0): Max H-Image Size [cm]: horiz.: 33 vert.: 24 (II) SIS(0): Gamma: 2.70 (II) SIS(0): DPMS capabilities: Suspend Off; RGB/Color Display (II) SIS(0): redX: 0.612 redY: 0.353 greenX: 0.293 greenY: 0.595 (II) SIS(0): blueX: 0.149 blueY: 0.068 whiteX: 0.281 whiteY: 0.311 (II) SIS(0): Supported VESA Video Modes: (II) SIS(0): 720x400@70Hz (II) SIS(0): 640x480@60Hz (II) SIS(0): 640x480@75Hz (II) SIS(0): 800x600@75Hz (II) SIS(0): 1024x768@75Hz (II) SIS(0): Manufacturer's mask: 0 (II) SIS(0): Supported Future Video Modes: (II) SIS(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897 (II) SIS(0): #1: hsize: 800 vsize 600 refresh: 85 vid: 22853 (II) SIS(0): Supported additional Video Mode: (II) SIS(0): clock: 56.2 MHz Image Size: 310 x 230 mm (II) SIS(0): h_active: 800 h_sync: 832 h_sync_end 896 h_blank_end 1048 h_border: 0 (II) SIS(0): v_active: 600 v_sync: 601 v_sync_end 604 v_blanking: 631 v_border: 0 (II) SIS(0): Supported additional Video Mode: (II) SIS(0): clock: 49.5 MHz Image Size: 310 x 230 mm (II) SIS(0): h_active: 800 h_sync: 816 h_sync_end 896 h_blank_end 1056 h_border: 0 (II) SIS(0): v_active: 856 v_sync: 857 v_sync_end 860 v_blanking: 881 v_border: 0 (II) SIS(0): Monitor name: GATEWAY EV700 (II) SIS(0): Ranges: V min: 50 V max: 120 Hz, H min: 30 H max: 70 kHz, (II) SIS(0): EDID (in hex): (II) SIS(0): 00ffffffffffff001ef9587636800400 (II) SIS(0): 0a080101282118aa68d1629c5a4b9826 (II) SIS(0): 11484fa4420081804559010101010101 (II) SIS(0): 010101010101f91520f830581f202040 (II) SIS(0): 130036e61000001e5613200031581930 (II) SIS(0): 1050130036e61000001e000000fc0047 (II) SIS(0): 415445574159204556373030000000fd (II) SIS(0): 0032781e46ff000a202020202020007f (II) SIS(0): EDID vendor "GWY", prod id 30296 (II) SIS(0): Using hsync ranges from config file (II) SIS(0): Using vrefresh ranges from config file (II) SIS(0): Printing DDC gathered Modelines: (II) SIS(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz) (II) SIS(0): Modeline "800x856"x0.0 49.50 800 816 896 1056 856 857 860 881 +hsync +vsync (46.9 kHz) (II) SIS(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz) (II) SIS(0): Modeline "640x480"x0.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) (II) SIS(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz) (II) SIS(0): Modeline "1024x768"x0.0 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz) (II) SIS(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz) (II) SIS(0): Modeline "1280x1024"x59.9 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync (63.7 kHz) (II) SIS(0): Modeline "800x600"x84.9 56.75 800 848 928 1056 600 603 607 633 -hsync +vsync (53.7 kHz) (--) SIS(0): End of VBE CRT1 DDC monitor info (==) SIS(0): Min pixel clock is 5 MHz (--) SIS(0): Max pixel clock is 91 MHz (II) SIS(0): Monitor0: Using hsync range of 30.00-70.00 kHz (II) SIS(0): Monitor0: Using vrefresh range of 50.00-120.00 Hz (II) SIS(0): Estimated virtual size for aspect ratio 1.3750 is 1024x768 (II) SIS(0): Clock range: 5.00 to 91.20 MHz (II) SIS(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) SIS(0): Not using default mode "1152x864" (width too large for virtual size) (II) SIS(0): Not using default mode "1280x960" (insufficient memory for mode) (II) SIS(0): Not using default mode "1280x960" (insufficient memory for mode) (II) SIS(0): Not using default mode "640x480" (hsync out of range) (II) SIS(0): Not using default mode "1280x1024" (insufficient memory for mode) (II) SIS(0): Not using default mode "1280x1024" (insufficient memory for mode) (II) SIS(0): Not using default mode "640x512" (hsync out of range) (II) SIS(0): Not using default mode "1280x1024" (insufficient memory for mode) (II) SIS(0): Not using default mode "640x512" (hsync out of range) (II) SIS(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) SIS(0): Not using default mode "800x600" (hsync out of range) (II) SIS(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) SIS(0): Not using default mode "800x600" (hsync out of range) (II) SIS(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) SIS(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) SIS(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) SIS(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) SIS(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) SIS(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) SIS(0): Not using default mode "1792x1344" (insufficient memory for mode) (II) SIS(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan) (II) SIS(0): Not using default mode "1792x1344" (insufficient memory for mode) (II) SIS(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan) (II) SIS(0): Not using default mode "1856x1392" (insufficient memory for mode) (II) SIS(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan) (II) SIS(0): Not using default mode "1856x1392" (insufficient memory for mode) (II) SIS(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan) (II) SIS(0): Not using default mode "1920x1440" (insufficient memory for mode) (II) SIS(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) SIS(0): Not using default mode "1920x1440" (insufficient memory for mode) (II) SIS(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) SIS(0): Not using default mode "1152x768" (width too large for virtual size) (II) SIS(0): Not using default mode "1400x1050" (insufficient memory for mode) (II) SIS(0): Not using default mode "1400x1050" (insufficient memory for mode) (II) SIS(0): Not using default mode "700x525" (hsync out of range) (II) SIS(0): Not using default mode "1600x1024" (insufficient memory for mode) (II) SIS(0): Not using default mode "1920x1440" (insufficient memory for mode) (II) SIS(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) SIS(0): Not using default mode "2048x1536" (insufficient memory for mode) (II) SIS(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) SIS(0): Not using default mode "2048x1536" (insufficient memory for mode) (II) SIS(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) SIS(0): Not using default mode "2048x1536" (insufficient memory for mode) (II) SIS(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) SIS(0): Not using driver mode "800x856" (height too large for virtual size) (II) SIS(0): Not using driver mode "1280x1024" (insufficient memory for mode) (--) SIS(0): Virtual size is 1024x768 (pitch 1024) (**) SIS(0): *Driver mode "1024x768": 78.8 MHz, 60.1 kHz, 75.1 Hz (II) SIS(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz) (**) SIS(0): *Default mode "1024x768": 78.8 MHz, 60.0 kHz, 75.0 Hz (II) SIS(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz) (**) SIS(0): *Default mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz (II) SIS(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz) (**) SIS(0): *Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz (II) SIS(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz) (**) SIS(0): *Default mode "1024x768": 44.9 MHz, 35.5 kHz, 86.9 Hz (I) (II) SIS(0): Modeline "1024x768"x86.9 44.90 1024 1032 1208 1264 768 768 776 817 interlace +hsync +vsync (35.5 kHz) (**) SIS(0): *Default mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz (II) SIS(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz) (**) SIS(0): *Driver mode "800x600": 56.2 MHz, 53.7 kHz, 85.1 Hz (II) SIS(0): Modeline "800x600"x85.1 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz) (**) SIS(0): *Driver mode "800x600": 56.8 MHz, 53.7 kHz, 84.9 Hz (II) SIS(0): Modeline "800x600"x84.9 56.75 800 848 928 1056 600 603 607 633 -hsync +vsync (53.7 kHz) (**) SIS(0): *Driver mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz (II) SIS(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz) (**) SIS(0): *Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz (II) SIS(0): Modeline "800x600"x85.1 56.30 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz) (**) SIS(0): *Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz (II) SIS(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz) (**) SIS(0): *Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz (II) SIS(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz) (**) SIS(0): *Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz (II) SIS(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) (**) SIS(0): *Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz (II) SIS(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz) (**) SIS(0): *Default mode "700x525": 61.0 MHz, 64.9 kHz, 60.0 Hz (D) (II) SIS(0): Modeline "700x525"x60.0 61.00 700 744 820 940 525 526 532 541 doublescan +hsync +vsync (64.9 kHz) (**) SIS(0): *Default mode "640x512": 54.0 MHz, 64.0 kHz, 60.0 Hz (D) (II) SIS(0): Modeline "640x512"x60.0 54.00 640 664 720 844 512 512 514 533 doublescan +hsync +vsync (64.0 kHz) (**) SIS(0): *Driver mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz (II) SIS(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz) (**) SIS(0): *Driver mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz (II) SIS(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) (**) SIS(0): *Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz (II) SIS(0): Modeline "640x480"x85.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz) (**) SIS(0): *Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz (II) SIS(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz) (**) SIS(0): *Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz (II) SIS(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz) (**) SIS(0): *Default mode "640x480": 54.0 MHz, 60.0 kHz, 60.0 Hz (D) (II) SIS(0): Modeline "640x480"x60.0 54.00 640 688 744 900 480 480 482 500 doublescan +hsync +vsync (60.0 kHz) (**) SIS(0): *Default mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz (II) SIS(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) (**) SIS(0): *Driver mode "720x400": 28.3 MHz, 31.5 kHz, 70.1 Hz (II) SIS(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz) (**) SIS(0): *Default mode "720x400": 35.5 MHz, 37.9 kHz, 85.0 Hz (II) SIS(0): Modeline "720x400"x85.0 35.50 720 756 828 936 400 401 404 446 -hsync +vsync (37.9 kHz) (**) SIS(0): *Default mode "640x400": 31.5 MHz, 37.9 kHz, 85.1 Hz (II) SIS(0): Modeline "640x400"x85.1 31.50 640 672 736 832 400 401 404 445 -hsync +vsync (37.9 kHz) (**) SIS(0): *Default mode "576x432": 54.0 MHz, 67.5 kHz, 75.0 Hz (D) (II) SIS(0): Modeline "576x432"x75.0 54.00 576 608 672 800 432 432 434 450 doublescan +hsync +vsync (67.5 kHz) (**) SIS(0): *Default mode "640x350": 31.5 MHz, 37.9 kHz, 85.1 Hz (II) SIS(0): Modeline "640x350"x85.1 31.50 640 672 736 832 350 382 385 445 +hsync -vsync (37.9 kHz) (**) SIS(0): *Default mode "576x384": 32.5 MHz, 44.2 kHz, 54.8 Hz (D) (II) SIS(0): Modeline "576x384"x54.8 32.50 576 589 657 736 384 385 388 403 doublescan +hsync +vsync (44.2 kHz) (**) SIS(0): *Default mode "512x384": 47.2 MHz, 68.7 kHz, 85.0 Hz (D) (II) SIS(0): Modeline "512x384"x85.0 47.25 512 536 584 688 384 384 386 404 doublescan +hsync +vsync (68.7 kHz) (**) SIS(0): *Default mode "512x384": 39.4 MHz, 60.0 kHz, 75.0 Hz (D) (II) SIS(0): Modeline "512x384"x75.0 39.38 512 520 568 656 384 384 386 400 doublescan +hsync +vsync (60.0 kHz) (**) SIS(0): *Default mode "512x384": 37.5 MHz, 56.5 kHz, 70.1 Hz (D) (II) SIS(0): Modeline "512x384"x70.1 37.50 512 524 592 664 384 385 388 403 doublescan -hsync -vsync (56.5 kHz) (**) SIS(0): *Default mode "512x384": 32.5 MHz, 48.4 kHz, 60.0 Hz (D) (II) SIS(0): Modeline "512x384"x60.0 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync (48.4 kHz) (**) SIS(0): *Default mode "512x384": 22.4 MHz, 35.5 kHz, 86.6 Hz (D) (II) SIS(0): Modeline "512x384"x86.6 22.45 512 516 604 632 384 384 388 409 interlace doublescan +hsync +vsync (35.5 kHz) (**) SIS(0): *Default mode "416x312": 28.6 MHz, 49.7 kHz, 74.7 Hz (D) (II) SIS(0): Modeline "416x312"x74.7 28.64 416 432 464 576 312 312 314 333 doublescan -hsync -vsync (49.7 kHz) (**) SIS(0): *Default mode "400x300": 28.1 MHz, 53.7 kHz, 85.3 Hz (D) (II) SIS(0): Modeline "400x300"x85.3 28.15 400 416 448 524 300 300 302 315 doublescan +hsync +vsync (53.7 kHz) (**) SIS(0): *Default mode "400x300": 24.8 MHz, 46.9 kHz, 75.1 Hz (D) (II) SIS(0): Modeline "400x300"x75.1 24.75 400 408 448 528 300 300 302 312 doublescan +hsync +vsync (46.9 kHz) (**) SIS(0): *Default mode "400x300": 25.0 MHz, 48.1 kHz, 72.2 Hz (D) (II) SIS(0): Modeline "400x300"x72.2 25.00 400 428 488 520 300 318 321 333 doublescan +hsync +vsync (48.1 kHz) (**) SIS(0): *Default mode "400x300": 20.0 MHz, 37.9 kHz, 60.3 Hz (D) (II) SIS(0): Modeline "400x300"x60.3 20.00 400 420 484 528 300 300 302 314 doublescan +hsync +vsync (37.9 kHz) (**) SIS(0): *Default mode "400x300": 18.0 MHz, 35.2 kHz, 56.3 Hz (D) (II) SIS(0): Modeline "400x300"x56.3 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync (35.2 kHz) (**) SIS(0): *Default mode "320x240": 18.0 MHz, 43.3 kHz, 85.2 Hz (D) (II) SIS(0): Modeline "320x240"x85.2 18.00 320 348 376 416 240 240 242 254 doublescan -hsync -vsync (43.3 kHz) (**) SIS(0): *Default mode "320x240": 15.8 MHz, 37.5 kHz, 75.0 Hz (D) (II) SIS(0): Modeline "320x240"x75.0 15.75 320 328 360 420 240 240 242 250 doublescan -hsync -vsync (37.5 kHz) (**) SIS(0): *Default mode "320x240": 15.8 MHz, 37.9 kHz, 72.8 Hz (D) (II) SIS(0): Modeline "320x240"x72.8 15.75 320 332 352 416 240 244 246 260 doublescan -hsync -vsync (37.9 kHz) (**) SIS(0): *Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D) (II) SIS(0): Modeline "320x240"x60.1 12.59 320 328 376 400 240 245 246 262 doublescan -hsync -vsync (31.5 kHz) (**) SIS(0): *Default mode "360x200": 17.8 MHz, 37.9 kHz, 85.0 Hz (D) (II) SIS(0): Modeline "360x200"x85.0 17.75 360 378 414 468 200 200 202 223 doublescan -hsync +vsync (37.9 kHz) (**) SIS(0): *Default mode "320x200": 15.8 MHz, 37.9 kHz, 85.3 Hz (D) (II) SIS(0): Modeline "320x200"x85.3 15.75 320 336 368 416 200 200 202 222 doublescan -hsync +vsync (37.9 kHz) (**) SIS(0): *Default mode "320x175": 15.8 MHz, 37.9 kHz, 85.3 Hz (D) (II) SIS(0): Modeline "320x175"x85.3 15.75 320 336 368 416 175 191 192 222 doublescan +hsync -vsync (37.9 kHz) (**) SIS(0): Display dimensions: (330, 240) mm (**) SIS(0): DPI set to (78, 81) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/local/lib/xorg/modules//libfb.so (II) Module fb: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.3 (II) Loading sub module "xaa" (II) LoadModule: "xaa" (II) Loading /usr/local/lib/xorg/modules//libxaa.so (II) Module xaa: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.2.0 ABI class: X.Org Video Driver, version 2.0 (II) SIS(0): 2D acceleration enabled (==) SIS(0): Write-combining range (0x0,0x1000) was already clear (--) Depth 24 pixmap format is 32 bpp (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] 0 0 0xf7fe0000 - 0xf7feffff (0x10000) MX[B] [1] 0 0 0xf7000000 - 0xf77fffff (0x800000) MX[B] [2] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [3] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [4] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [5] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [6] -1 0 0xfedf0000 - 0xfedfffff (0x10000) MX[B]E [7] -1 0 0xfeded800 - 0xfededbff (0x400) MX[B]E [8] -1 0 0xfededc00 - 0xfededfff (0x400) MX[B]E [9] -1 0 0xfec00000 - 0xfecfffff (0x100000) MX[B]E [10] -1 0 0xfedee000 - 0xfedeefff (0x1000) MX[B]E [11] -1 0 0xfedef000 - 0xfedeffff (0x1000) MX[B]E [12] -1 0 0xf8000000 - 0xf7ffffff (0x0) MX[B]EO [13] -1 0 0xf7fe0000 - 0xf7feffff (0x10000) MX[B](B) [14] -1 0 0xf7000000 - 0xf77fffff (0x800000) MX[B](B) [15] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprU) [16] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprU) [17] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprU) [18] 0 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B] [19] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [20] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [21] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [22] -1 0 0x0000d800 - 0x0000d8ff (0x100) IX[B]E [23] -1 0 0x0000dcf0 - 0x0000dcff (0x10) IX[B]E [24] -1 0 0x00000374 - 0x00000377 (0x4) IX[B]E [25] -1 0 0x00000170 - 0x0000017f (0x10) IX[B]E [26] -1 0 0x000003f4 - 0x000003f7 (0x4) IX[B]E [27] -1 0 0x000001f0 - 0x000001ff (0x10) IX[B]E [28] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B](B) [29] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) [30] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) (II) Loading sub module "vbe" (II) LoadModule: "vbe" (II) Reloading /usr/local/lib/xorg/modules//libvbe.so (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Reloading /usr/local/lib/xorg/modules//libint10.so (II) SIS(0): initializing int10 (==) SIS(0): Write-combining range (0xa0000,0x20000) was already clear (II) SIS(0): Primary V_BIOS segment is: 0xc000 (==) SIS(0): Write-combining range (0x0,0x1000) was already clear (==) SIS(0): Write-combining range (0x0,0x1000) was already clear (==) SIS(0): Write-combining range (0x0,0x1000) was already clear (II) SIS(0): VESA BIOS detected (II) SIS(0): VESA VBE Version 2.0 (II) SIS(0): VESA VBE Total Mem: 4096 kB (II) SIS(0): VESA VBE OEM: SiS (II) SIS(0): VESA VBE OEM Software Rev: 1.0 (II) SIS(0): VESA VBE OEM Vendor: Silicon Integrated Systems Corp. (II) SIS(0): VESA VBE OEM Product: 6306 (II) SIS(0): VESA VBE OEM Product Rev: 0A (==) SIS(0): Write-combining range (0xf7fe0000,0x10000) was already clear (==) SIS(0): Write-combining range (0xf7000000,0x400000) (II) SIS(0): Framebuffer from (0,0) to (1023,1021) (II) SIS(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles 8x8 mono pattern filled rectangles Indirect CPU to Screen color expansion Solid Lines Dashed Lines Offscreen Pixmaps Setting up tile and stipple cache: 8 128x128 slots (II) SIS(0): Benchmarking system RAM to video RAM memory transfer methods: (--) SIS(0): Checked libc memcpy()... 1883216 (--) SIS(0): Checked built-in-1 memcpy()... 1906124 (--) SIS(0): Checked built-in-2 memcpy()... 6058502 (--) SIS(0): Checked MMX memcpy()... 1895103 (--) SIS(0): Using libc method for aligned data transfers to video RAM (--) SIS(0): Using libc method for unaligned data transfers to video RAM (==) SIS(0): Backing store disabled (==) SIS(0): Silken mouse enabled (**) Option "dpms" (**) SIS(0): DPMS enabled (II) SIS(0): Using SiS5597/5598/6326/530/620 HW Xv (==) RandR enabled (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension XAccessControlExtension (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFIXES (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) Initializing built-in extension XEVIE (II) Loading sub module "GLcore" (II) LoadModule: "GLcore" (II) Loading /usr/local/lib/xorg/modules/extensions//libGLcore.so (II) Module GLcore: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.3 (II) GLX: Initialized MESA-PROXY GL provider for screen 0 (**) Option "Protocol" "auto" (**) Mouse0: Device: "/dev/sysmouse" (**) Mouse0: Protocol: "auto" (**) Option "CorePointer" (**) Mouse0: always reports core events (**) Option "Device" "/dev/sysmouse" (==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50 (**) Option "ZAxisMapping" "4 5 6 7" (**) Mouse0: ZAxisMapping: buttons 4, 5, 6 and 7 (**) Mouse0: Buttons: 11 (**) Mouse0: Sensitivity: 1 (**) Option "CoreKeyboard" (**) Keyboard0: always reports core events (**) Option "Protocol" "standard" (**) Keyboard0: Protocol: standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xorg" (**) Keyboard0: XkbRules: "xorg" (**) Option "XkbModel" "pc105" (**) Keyboard0: XkbModel: "pc105" (**) Option "XkbLayout" "us" (**) Keyboard0: XkbLayout: "us" (**) Option "CustomKeycodes" "off" (**) Keyboard0: CustomKeycodes disabled (II) evaluating device (Keyboard0) (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD) (II) evaluating device (Mouse0) (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) (II) Mouse0: SetupAuto: hw.iftype is 4, hw.model is 0 (II) Mouse0: SetupAuto: protocol is SysMouse [config/hal] couldn't initialise context: (null) ((null)) FreeFontPath: FPE "/usr/local/lib/X11/fonts/misc/" refcount is 2, should be 1; fixing. --------------060201050108000805050608-- From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 02:13:25 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27A5016A41B for ; Thu, 27 Sep 2007 02:13:25 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (cl-162.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:a1::2]) by mx1.freebsd.org (Postfix) with ESMTP id A0FC913C461 for ; Thu, 27 Sep 2007 02:13:24 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.13.8/8.13.8) with ESMTP id l8R2DMjI002638; Wed, 26 Sep 2007 21:13:22 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.13.8/8.13.8/Submit) id l8R2DMmP002636; Wed, 26 Sep 2007 21:13:22 -0500 (CDT) (envelope-from brooks) Date: Wed, 26 Sep 2007 21:13:22 -0500 From: Brooks Davis To: Nathan Lay Message-ID: <20070927021322.GB1216@lor.one-eyed-alien.net> References: <46FAF5C1.4070106@comcast.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3uo+9/B/ebqu+fSQ" Content-Disposition: inline In-Reply-To: <46FAF5C1.4070106@comcast.net> User-Agent: Mutt/1.5.15 (2007-04-06) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Wed, 26 Sep 2007 21:13:23 -0500 (CDT) Cc: freebsd-current@freebsd.org Subject: Re: iwi oddities X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 02:13:25 -0000 --3uo+9/B/ebqu+fSQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 26, 2007 at 08:13:53PM -0400, Nathan Lay wrote: > Hi list, > With these rc.conf flags >=20 > ifconfig_iwi0=3D"powersave wme -bgscan" >=20 > iwi decides to bring itself up on boot. iwi in 6.2 never brought itself= =20 > unless 'up' was explicitly specified. Though, my 6.2 rc.conf settings a= re=20 > more along the lines of >=20 > ifconfig_iwi0=3D"wme bmiss 100" I'm can't speak to why that particular combination causes the interface to be set up, but if you specifically don't want the device to be touched until you manually run /etc/rc.d/netif (or something similar) on it add the NOAUTO keyword to the line and the interface will be ignored on boot. It was specifically intended to allow onboard wireless devices to be configured in /etc/rc.conf, but not start until an external trigger occurs. -- Brooks --3uo+9/B/ebqu+fSQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFG+xHCXY6L6fI4GtQRAv81AKDgEeqjW3LzdXNDhHyqZD/hhb2DKwCdHK7q 0cmj5TFNGbXROAOzfe4gFgk= =VLdb -----END PGP SIGNATURE----- --3uo+9/B/ebqu+fSQ-- From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 02:17:39 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9713B16A49E for ; Thu, 27 Sep 2007 02:17:39 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (cl-162.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:a1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 008C513C455 for ; Thu, 27 Sep 2007 02:17:38 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.13.8/8.13.8) with ESMTP id l8R2Hbxk002929; Wed, 26 Sep 2007 21:17:37 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.13.8/8.13.8/Submit) id l8R2HbJv002928; Wed, 26 Sep 2007 21:17:37 -0500 (CDT) (envelope-from brooks) Date: Wed, 26 Sep 2007 21:17:37 -0500 From: Brooks Davis To: Nathan Lay Message-ID: <20070927021737.GC1216@lor.one-eyed-alien.net> References: <46FAF5C1.4070106@comcast.net> <20070927021322.GB1216@lor.one-eyed-alien.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PuGuTyElPB9bOcsM" Content-Disposition: inline In-Reply-To: <20070927021322.GB1216@lor.one-eyed-alien.net> User-Agent: Mutt/1.5.15 (2007-04-06) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Wed, 26 Sep 2007 21:17:37 -0500 (CDT) Cc: freebsd-current@freebsd.org Subject: Re: iwi oddities X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 02:17:39 -0000 --PuGuTyElPB9bOcsM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 26, 2007 at 09:13:22PM -0500, Brooks Davis wrote: > On Wed, Sep 26, 2007 at 08:13:53PM -0400, Nathan Lay wrote: > > Hi list, > > With these rc.conf flags > >=20 > > ifconfig_iwi0=3D"powersave wme -bgscan" > >=20 > > iwi decides to bring itself up on boot. iwi in 6.2 never brought itse= lf=20 > > unless 'up' was explicitly specified. Though, my 6.2 rc.conf settings= are=20 > > more along the lines of > >=20 > > ifconfig_iwi0=3D"wme bmiss 100" >=20 > I'm can't speak to why that particular combination causes the interface > to be set up, but if you specifically don't want the device to be touched > until you manually run /etc/rc.d/netif (or something similar) on it add > the NOAUTO keyword to the line and the interface will be ignored on > boot. It was specifically intended to allow onboard wireless devices to = be > configured in /etc/rc.conf, but not start until an external trigger occur= s. Actually, I spoke too soon. The interface comes up specificaly because you= set anything in the ifconfig_iwi0 variable. That should be the case in 6.2 as well. The code that executed the "ifconfig iwi0 $ifconfig_iwi0"[0] bit fir= st does "ifconfig iwi0 up". -- Brooks [0] Actually not quite since we have magic keywords like DHCP, WPA, and NOAUTO now and those get removed. --PuGuTyElPB9bOcsM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFG+xLAXY6L6fI4GtQRAgZEAJ9ob+yH7qfD5RX9ym/hfzHAV1X56wCdGily Oi03baAKiaeI2dKa9aKur9o= =reBD -----END PGP SIGNATURE----- --PuGuTyElPB9bOcsM-- From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 02:35:21 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 828B816A419; Thu, 27 Sep 2007 02:35:21 +0000 (UTC) (envelope-from beech@FreeBSD.org) Received: from stargate.alaskaparadise.com (137-42-178-69.gci.net [69.178.42.137]) by mx1.freebsd.org (Postfix) with ESMTP id 4DD1B13C455; Thu, 27 Sep 2007 02:35:21 +0000 (UTC) (envelope-from beech@FreeBSD.org) Received: from [127.0.0.1] (zardoz.alaskaparadise.com [172.16.0.5]) by stargate.alaskaparadise.com (Postfix) with ESMTP id C76A08754; Wed, 26 Sep 2007 18:35:20 -0800 (AKDT) Message-ID: <46FB16E6.1010908@FreeBSD.org> Date: Wed, 26 Sep 2007 18:35:18 -0800 From: Beech Rintoul User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: freebsd-current@freebsd.org, flz@freebsd.org References: <46FB0752.1040006@FreeBSD.org> In-Reply-To: <46FB0752.1040006@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Yesterday's -current breaks xorg (fixed) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 02:35:21 -0000 Beech Rintoul wrote: > I wasn't sure which list to send this, so I'll start here. -CURRENT > from yesterday breaks xorg (just hangs). > > log attached > > Beech Removed .ICE* .X11* from temp, .Xauthority from home dir and restarted. Fixed. -- --------------------------------------------------------------------------------------- Beech Rintoul - FreeBSD Developer - beech@FreeBSD.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.FreeBSD.org/releases/6.2R/announce.html --------------------------------------------------------------------------------------- From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 04:24:25 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D622E16A419 for ; Thu, 27 Sep 2007 04:24:25 +0000 (UTC) (envelope-from crapsh@MonkeyBrains.NET) Received: from ape.monkeybrains.net (ape.monkeybrains.net [208.69.40.11]) by mx1.freebsd.org (Postfix) with ESMTP id 9B29613C4A7 for ; Thu, 27 Sep 2007 04:24:25 +0000 (UTC) (envelope-from crapsh@MonkeyBrains.NET) Received: from [192.168.1.125] (adsl-75-61-235-81.dsl.pltn13.sbcglobal.net [75.61.235.81]) (authenticated bits=0) by ape.monkeybrains.net (8.14.1/8.14.1) with ESMTP id l8R4OLAc001012 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 26 Sep 2007 21:24:24 -0700 (PDT) (envelope-from crapsh@MonkeyBrains.NET) Message-ID: <46FB3067.8040706@MonkeyBrains.NET> Date: Wed, 26 Sep 2007 21:24:07 -0700 From: Rudy User-Agent: Thunderbird 1.5.0.13 (Macintosh/20070809) 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: ClamAV version 0.91.1, clamav-milter version 0.91.1 on pita.monkeybrains.net X-Virus-Status: Clean Subject: Flash plugin status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 04:24:25 -0000 About a month ago, Flash 7 was marked unsafe, and Flash 9 doesn't work on many sites. [1] Anyone have any tricks to get Flash 9 working in 7.x? [2] Any update on getting the freebsd foundation to take on Flash (ala Java)? [3] Anyone work at Adobe (nee Macromedia) that can get a build for FreeBSD published? Stirring up the same old problem, Rudy From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 04:56:58 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04AA516A41B for ; Thu, 27 Sep 2007 04:56:58 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.freebsd.org (Postfix) with ESMTP id 86E8B13C457 for ; Thu, 27 Sep 2007 04:56:57 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: by ug-out-1314.google.com with SMTP id a2so1465227ugf for ; Wed, 26 Sep 2007 21:56:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=fNQe0T9eobFKHOwOJN5bQzErChNZcsAi8OhYz2LttzA=; b=uTlAClLTfz8Qazx8vS8iiQ3Ra5IMZn2hVXbhnAqtuzmcFYk6QGWV65Hfl2Ipa6QLj3hELnpXNBoMT5uz3+Z6Z6InwdXd1EZjLxwTGZrDr+5B1RMDP+zGwsWSrBnE3qVvNYTFnl+gdly2pYHfmZCj6COvXJpf7krpHM8AqPOwScs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Z9Tw2d1GLeOMU+vTVCBbgT+SKhKOgDD/+U8bbRzZDiEiS94cv7cAL1iKZn6Fv1QmIKsuWXuUSCvEFhOu15QSDyjwbWdnu8vAnRLUC8D5Uszj8Kz1AA5IpEZKopngn9kZtc0HE3VP+pX2xmkn3GXb0h/q3EnF1LwUME3bkQZWJDc= Received: by 10.66.249.14 with SMTP id w14mr3137201ugh.1190869016125; Wed, 26 Sep 2007 21:56:56 -0700 (PDT) Received: by 10.86.91.5 with HTTP; Wed, 26 Sep 2007 21:56:56 -0700 (PDT) Message-ID: <11167f520709262156k5aa8d14br9b14ebb85d8adb4b@mail.gmail.com> Date: Wed, 26 Sep 2007 23:56:56 -0500 From: "Sam Fourman Jr." To: Rudy In-Reply-To: <46FB3067.8040706@MonkeyBrains.NET> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46FB3067.8040706@MonkeyBrains.NET> Cc: freebsd-current@freebsd.org Subject: Re: Flash plugin status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 04:56:58 -0000 On 9/26/07, Rudy wrote: > > About a month ago, Flash 7 was marked unsafe, and Flash 9 doesn't work > on many sites. > > [1] Anyone have any tricks to get Flash 9 working in 7.x? > [2] Any update on getting the freebsd foundation to take > on Flash (ala Java)? > [3] Anyone work at Adobe (nee Macromedia) that can get a > build for FreeBSD published? > > > Stirring up the same old problem, > Rudy > _______________________________________________ > 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" > I would Love to have a native build of Flash for FreeBSD, I heard something about the PC-BSD project approaching Adobe, for a native build of flash, I heard this on a BSD talk interview a month or so ago. does anyone know the steps that would need to be taken in order to bring the flash issue to the attention of the FreeBSD foundation. Maybe the FreeBSD foundation does not realize how many sites require flash 9 now. Willing to help in anyway I can Sam Fourman Jr. From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 06:00:48 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 004FC16A418 for ; Thu, 27 Sep 2007 06:00:47 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id A3E8A13C4A6 for ; Thu, 27 Sep 2007 06:00:47 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id D41E320D3; Thu, 27 Sep 2007 08:00:40 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id C023620D2; Thu, 27 Sep 2007 08:00:40 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id A81538444C; Thu, 27 Sep 2007 08:00:40 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Chuck Swiger References: <20070921102946.T11189@borg> <46F415BF.9010500@FreeBSD.org> <20070921140550.D96923@thebighonker.lerctr.org> <46F41CFF.6080108@FreeBSD.org> <46F58799.1030702@freebsd.org> <46F58B21.8030307@FreeBSD.org> <20070924091558.GB32006@team.vega.ru> <46F78C59.1020801@FreeBSD.org> <20070924080347.O84223@thebighonker.lerctr.org> <20070924144210.GA82735@team.vega.ru> <46F7D7A4.5090007@samsco.org> <46F80A39.3050707@FreeBSD.org> <46F8951C.50904@freebsd.org> <46F8CE67.60206@FreeBSD.org> <46FA2E46.8020303@freebsd.org> Date: Thu, 27 Sep 2007 08:00:40 +0200 In-Reply-To: (Chuck Swiger's message of "Wed\, 26 Sep 2007 11\:21\:27 -0700") Message-ID: <86zlz8zlyv.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Darren Reed , Kris Kennaway , freebsd-current@freebsd.org, Larry Rosenman Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 06:00:48 -0000 Chuck Swiger writes: > I'm not certain whether FreeBSD's kernel memory allocator [malloc(9), > zone(9)] even supports the notion of allocating pageable memory > rather than memory taken from the fixed KVA region. The manpage > implies that calling kernel malloc with M_WAITOK will always return a > valid pointer and not NULL, but I'm not convinced this is will be > true if you try allocating something larger than the size of KVA and/ > or the amount of physical RAM available in the system. malloc(M_WAITOK) will panic if the request is not satisfiable. Where do you think "kmem_map too small" comes from? DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 10:48:31 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB71416A468 for ; Thu, 27 Sep 2007 10:48:31 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.freebsd.org (Postfix) with ESMTP id 4043A13C455 for ; Thu, 27 Sep 2007 10:48:30 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A5120.dip.t-dialin.net [84.154.81.32]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id l8RAmR1U061913; Thu, 27 Sep 2007 12:48:28 +0200 (CEST) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.6/8.13.6) with ESMTP id l8RAm9GT022632; Thu, 27 Sep 2007 12:48:21 +0200 (CEST) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.13.8/8.13.8) with ESMTP id l8RAm8l0017908; Thu, 27 Sep 2007 12:48:08 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200709271048.l8RAm8l0017908@fire.js.berklix.net> To: "Sam Fourman Jr." In-reply-to: <11167f520709262156k5aa8d14br9b14ebb85d8adb4b@mail.gmail.com> References: <46FB3067.8040706@MonkeyBrains.NET> <11167f520709262156k5aa8d14br9b14ebb85d8adb4b@mail.gmail.com> Comments: In-reply-to "Sam Fourman Jr." message dated "Wed, 26 Sep 2007 23:56:56 -0500." Date: Thu, 27 Sep 2007 12:48:08 +0200 From: "Julian H. Stacey" Cc: freebsd-current@freebsd.org, Deb Goodkin , Rudy Subject: Re: Flash plugin status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 10:48:31 -0000 Sam F. > does anyone know the steps that would need to be taken in order to > bring the flash issue to the attention of the FreeBSD foundation. ...... > Willing to help in anyway I can To contact, write to Deb Goodkin http://freebsdfoundation.org cc'd (She announces foundation things to announce@freebsd.org) -- Julian Stacey. Munich Computer Consultant, BSD Unix C Linux. http://berklix.com Ihr Rauch=mein allergischer Kopfschmerz. Dump cigs 4 snuff. From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 11:27:58 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B81F116A419 for ; Thu, 27 Sep 2007 11:27:58 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.freebsd.org (Postfix) with ESMTP id 7F84213C46E for ; Thu, 27 Sep 2007 11:27:58 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from parancell.ongs.co.jp (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id 72F35244C3A; Thu, 27 Sep 2007 20:27:56 +0900 (JST) Message-ID: <46FB93BC.2000508@freebsd.org> Date: Thu, 27 Sep 2007 20:27:56 +0900 From: Daichi GOTO User-Agent: Thunderbird 2.0.0.6 (X11/20070803) MIME-Version: 1.0 To: cpghost References: <46F905FD.9060208@freebsd.org> <20070925194008.3c2d7113@epia-2.farid-hajji.net> In-Reply-To: <20070925194008.3c2d7113@epia-2.farid-hajji.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , Masanori OZAWA Subject: Re: The safety expansion for FreeBSD rm(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 11:27:58 -0000 cpghost wrote: > On Tue, 25 Sep 2007 21:58:37 +0900 > Daichi GOTO wrote: > >> Today is not unionfs. Introduction for safety expansion of rm(1). >> I know that some unix folks have a experience that you remove some >> files or directories accidentally. Yes, me too. LoL >> >> Have you any dreams that rm(1) autonomously judges target should >> be remove or not? To complexify system base command is objectionable >> behavior but adding some little and simple mechanism to prevent a >> issue is acceptable I suppose. >> >> We have created safety expansion for rm(1). If you have any interests, >> please try follow patch. >> >> http://people.freebsd.org/~daichi/safety-rm/ >> >> Thanks :) > > Interesting idea, but isn't that a violation of POLA? Imagine an What's POLA?? > unsuspecting sysadmin trying to rm something, and forgetting > or not knowing about ~/.rm? > > Isn't it better to protect important system directories with > something like: > # chflags sunlink /path/to/dir > and unprotect them with > # chflags nosunlink /path/to/dir > to avoid mistakes? Of course that's one of the ways, I suppose :) chflags is useful but root limitation feature is not useful for common users I suppose. With our expansion, common users can check files or directories on self-responsibility. And unusual commands like chflags I just suppose are no much point in this case. What is important is that adding mistake protecting functions into common commands like rm(1) itself. Of course I respect your opinions and all comments are welcome :) I have no intention to add our expansion to src tree. It just is a little patch for folks who have a interest of it. Thanks > Thanks, > -cpghost. -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 11:37:25 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D462316A477 for ; Thu, 27 Sep 2007 11:37:25 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.freebsd.org (Postfix) with ESMTP id 9B47013C48E for ; Thu, 27 Sep 2007 11:37:25 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from parancell.ongs.co.jp (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id 48F9C244C48; Thu, 27 Sep 2007 20:37:24 +0900 (JST) Message-ID: <46FB95F4.2000706@freebsd.org> Date: Thu, 27 Sep 2007 20:37:24 +0900 From: Daichi GOTO User-Agent: Thunderbird 2.0.0.6 (X11/20070803) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG, Masanori OZAWA References: <200709251800.l8PI0lof013108@lurza.secnetix.de> In-Reply-To: <200709251800.l8PI0lof013108@lurza.secnetix.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: The safety expansion for FreeBSD rm(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 11:37:25 -0000 Oliver Fromme wrote: > Daichi GOTO wrote: > > Have you any dreams that rm(1) autonomously judges target should > > be remove or not? To complexify system base command is objectionable > > behavior but adding some little and simple mechanism to prevent a > > issue is acceptable I suppose. > > I think it could cause confusion for some users or admins. > > It could also be dangerous. I remember an emergency case > when /home was an NFS mount that was dead, i.e. every > process that tried to access something in /home just hung > forever in state "D" (disk wait). During the emergency > actions on the serial console I also needed to use the > rm(1) command ... Now if it tried to read ~/.rm, it would > have drawn me mouch deeper into trouble than I already > were. :-) True, the -f option would have prevented it, > _if_ I remembered before to use it. We have realized that issue, but do not understand thats cause still now. Do you know the reason? > A common precaution against accidental rm is to establish > a snapshot rotation system. For example, create hourly > snapshots (with a cron job) and delete them automatically > after a while. So if you accidentally remove something, > you can copy it back from the latest snapshot. NetApp > Filers have such a feature built-in. You can also easily > set it up yourself with ZFS, or even with UFS snapshots, > although the latter are a bit heavyweight, IMHO. Yes. At the moment ZFS looks a best way of snapshot feature. I have heard that snapshot of UFS2 is slow under very mass files and heavy load situation. > And finally, there is chflags(1). If you know in advance > that certain files or directories must not be removed, > then "chflags schg" or "chflags uchg" them. That's the > same effect as creating a ~/.rm file with your patch. Yes. It is one of the ways :) > Another advantage of chflags(1) is that it also protects > against other kinds of damage. For example when using > shell redirection ("echo > some/important/file"), cp, dd > or other commands. In those cases chflags also offers > protection (and a snapshot would offer recovery), while > your patch only protects against rm and nothing else. > > Just my 2 cents. > > Best regards > Oliver -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 11:41:46 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3473F16A41A for ; Thu, 27 Sep 2007 11:41:46 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.freebsd.org (Postfix) with ESMTP id 063F713C44B for ; Thu, 27 Sep 2007 11:41:45 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from parancell.ongs.co.jp (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id B610B244C49; Thu, 27 Sep 2007 20:41:44 +0900 (JST) Message-ID: <46FB96F8.20600@freebsd.org> Date: Thu, 27 Sep 2007 20:41:44 +0900 From: Daichi GOTO User-Agent: Thunderbird 2.0.0.6 (X11/20070803) MIME-Version: 1.0 To: Martin Cracauer References: <46F905FD.9060208@freebsd.org> <20070925183248.GA38571@cons.org> In-Reply-To: <20070925183248.GA38571@cons.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , Masanori OZAWA Subject: Re: The safety expansion for FreeBSD rm(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 11:41:46 -0000 Martin Cracauer wrote: > My idea of a safety feature for rm(1): > > To solve the problem of doing > rm foo * > instead of > rm foo* > > Look at what the commandline arguments are. If at least > - one is appearing twice > - or at least one is not appearing at all > > , then do a "*" expand like from a shell (not perfect of course not > easy enough) and see whether all elements of "*" are there *plus* > others with no "/". If so, the above situation occured and you only > go ahead with a special flag. > > Martin Wow, it's a interest :) -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 11:55:05 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B7E516A46C for ; Thu, 27 Sep 2007 11:55:05 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.freebsd.org (Postfix) with ESMTP id CAD0913C4BE for ; Thu, 27 Sep 2007 11:55:04 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from parancell.ongs.co.jp (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id F08A3244C48; Thu, 27 Sep 2007 20:55:03 +0900 (JST) Message-ID: <46FB9A17.2000201@freebsd.org> Date: Thu, 27 Sep 2007 20:55:03 +0900 From: Daichi GOTO User-Agent: Thunderbird 2.0.0.6 (X11/20070803) MIME-Version: 1.0 To: Brooks Davis References: <46F905FD.9060208@freebsd.org> <20070925184318.GC78038@lor.one-eyed-alien.net> In-Reply-To: <20070925184318.GC78038@lor.one-eyed-alien.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , Masanori OZAWA Subject: Re: The safety expansion for FreeBSD rm(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 11:55:05 -0000 Brooks Davis wrote: > On Tue, Sep 25, 2007 at 09:58:37PM +0900, Daichi GOTO wrote: >> Hi Guys again >> >> Today is not unionfs. Introduction for safety expansion of rm(1). >> I know that some unix folks have a experience that you remove some >> files or directories accidentally. Yes, me too. LoL >> >> Have you any dreams that rm(1) autonomously judges target should >> be remove or not? To complexify system base command is objectionable >> behavior but adding some little and simple mechanism to prevent a >> issue is acceptable I suppose. >> >> We have created safety expansion for rm(1). If you have any interests, >> please try follow patch. >> >> http://people.freebsd.org/~daichi/safety-rm/ >> >> Thanks :) > > This seems like an interesting extension of rm(1) in a fairly harmless manner. Yes, that's what it is :) > It seems like a fairly logical extension of the tcsh rmstar variable. The > one concern I would have with it is that unlike the rmstar variable, it would > always run even if the rm command is run in a script. > > What do you think of adding a flag to enable this behavior so users > could make rm an alias that uses the flag? That would keep it from > effecting scripts. Great! Exactly my point. We have gotten a discussion that to add an option like that or not. Yeah, we'll add an option you pointed. What is a best alphabet as option charactor do you think? -s (means safety remove)?? -e (means rm expansion)?? Is -s better?? > -- Brooks -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 22:25:57 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C8AB16A418 for ; Wed, 26 Sep 2007 22:25:57 +0000 (UTC) (envelope-from jpedras@webvolution.net) Received: from mail.portrait.com (mail.portrait.com [64.171.32.41]) by mx1.freebsd.org (Postfix) with ESMTP id E64CC13C48A for ; Wed, 26 Sep 2007 22:25:56 +0000 (UTC) (envelope-from jpedras@webvolution.net) Received: from teko.portrait.moc (novato.portrait.com [64.171.32.25]) (authenticated bits=0) by mail.portrait.com (8.13.1/8.13.1) with ESMTP id l8QMPhjw094602 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Sep 2007 15:25:44 -0700 (PDT) (envelope-from jpedras@webvolution.net) Message-ID: <46FADC63.50303@webvolution.net> Date: Wed, 26 Sep 2007 15:25:39 -0700 From: Joao Pedras User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Kris Kennaway References: <46FA0C14.10201@webvolution.net> <46FADB35.2090708@FreeBSD.org> In-Reply-To: <46FADB35.2090708@FreeBSD.org> X-Enigmail-Version: 0.95.3 OpenPGP: id=D7505EC0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.0 tests=ALL_TRUSTED X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on mail.portrait.com X-Mailman-Approved-At: Thu, 27 Sep 2007 12:07:43 +0000 Cc: freebsd-current@freebsd.org Subject: Re: lock up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 22:25:57 -0000 I will Kris. That was my next step. Just trying to see if this was obvious to anyone. Kris Kennaway wrote: > Joao Pedras wrote: >> Greetings all! >> >> A system (Tyan S2932) I am testing CURRENT amd64 with is experiencing a >> strange lock up. No panic, not much on the console, just a lock up, >> freeze. >> >> I first noticed the issue while tailing a build in a ssh session over a >> vpn connection. On the local network the issue doesn't seem to occur. >> I can reproduce the lock up all the time. >> >> Last I tried, the system was running CURRENT from a couple hours ago. >> >> I have tried: >> >> - 4BSD and ULE >> - switching network cards >> - taking the IPMI card out (seems to work locally with freeipmi and >> ipmitoll remotely) >> - enabled/disabled "redirection after post" (BIOS setting) >> - without debug >> - without IPv6 and friends (see rtfree below) >> >> dmesg and pciconf attached. The dmesg is after a lock up. >> rtfree pops a few times before the lock up. I noticed from a recent post >> some action was taken and the related patch is there (ie. today's >> CURRENT). >> >> The system had a fresh install this past weekend and the LSI MegaRAID >> array doesn't contain any data, it is just mounted. The system boots off >> the onboard LSI SAS (couple disks in RAID 1). >> >> Thank you for your input. > > Break to DDB and obtain process traces, etc. See the developers handbook. > > Kris > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 11:27:35 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D5A016A417 for ; Thu, 27 Sep 2007 11:27:35 +0000 (UTC) (envelope-from vermaden@interia.pl) Received: from smtp4.poczta.interia.pl (smtp35.poczta.interia.pl [80.48.65.35]) by mx1.freebsd.org (Postfix) with ESMTP id 93CBB13C467 for ; Thu, 27 Sep 2007 11:27:34 +0000 (UTC) (envelope-from vermaden@interia.pl) Received: by smtp4.poczta.interia.pl (INTERIA.PL, from userid 502) id C45A02EA944; Thu, 27 Sep 2007 13:07:39 +0200 (CEST) Received: from f46.poczta.interia.pl (f46.poczta.interia.pl [10.217.2.46]) by smtp4.poczta.interia.pl (INTERIA.PL) with ESMTP id 4F4392EA907 for ; Thu, 27 Sep 2007 13:07:39 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by f46.poczta.interia.pl (Postfix) with ESMTP id 32E8946CCB8 for ; Thu, 27 Sep 2007 13:07:39 +0200 (CEST) Date: 27 Sep 2007 13:07:39 +0200 From: vermaden To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=ISO-8859-2 Content-Transfer-Encoding: QUOTED-PRINTABLE X-ORIGINATE-IP: 217.76.112.72 X-Mailer: PSE Message-Id: <20070927110739.32E8946CCB8@f46.poczta.interia.pl> X-EMID: e540acc X-Mailman-Approved-At: Thu, 27 Sep 2007 12:07:43 +0000 Subject: ASUS P5B-MX [946GZ/GMA 3000] does not work with Intel driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 11:27:35 -0000 I cannot make Intel 3000GMA in ASUS P5B-MX to work with intel driver. I added all info below. How can I help you more to resolve this problem? hardware: ASUS P5B-MX [946GZ chipset + GMA 3000] (82946GZ + ICH7 exacly) kernel config: generic SMP config from /usr/src/sys/i386/conf/SMP ---------------------------------------------------------------------------= ----- % uname -a FreeBSD siewa 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed Sep 26 09:31:01 CEST 20= 07 root at siewa:/usr/obj/usr/src/sys/CUSTOM i386 ---------------------------------------------------------------------------= ----- % kldstat=20 Id Refs Address Size Name 1 12 0xc0400000 7e7820 kernel 2 1 0xc0be8000 633ec acpi.ko 3 1 0xc53bc000 1b000 linux.ko 4 1 0xc5696000 6000 i915.ko 5 1 0xc569c000 f000 drm.ko ---------------------------------------------------------------------------= ----- # kldload agp kldload: can't load agp: File exists ---------------------------------------------------------------------------= ----- % pkg_info xf86-video-intel-2.1.1 Information for xf86-video-intel-2.1.1: Comment: Driver for Intel integrated graphics chipsets Description: Driver for Intel integrated graphics chipsets. It supports the i810, i810-DC100, i810e, i815, i830M, 845G, 852GM, 855GM, 865G, 915G, 915GM, 945G, 945GM, 965G, 965Q, 946GZ and 965GM chipsets. ---------------------------------------------------------------------------= ----- % pciconf -lv hostb0 at pci0:0:0:=09class=3D0x060000 card=3D0x823b1043 chip=3D0x29708086 = rev=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' class =3D bridge subclass =3D HOST-PCI none0 at pci0:2:0:=09class=3D0x030000 card=3D0x823b1043 chip=3D0x29728086 r= ev=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' class =3D display subclass =3D VGA none1 at pci0:27:0:=09class=3D0x040300 card=3D0x82901043 chip=3D0x27d88086 = rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801G (ICH7 Family) High Definition Audio' class =3D multimedia uhci0 at pci0:29:0:=09class=3D0x0c0300 card=3D0x81791043 chip=3D0x27c88086 = rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801G (ICH7 Family) USB Universal Host Controller' class =3D serial bus subclass =3D USB uhci1 at pci0:29:1:=09class=3D0x0c0300 card=3D0x81791043 chip=3D0x27c98086 = rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801G (ICH7 Family) USB Universal Host Controller' class =3D serial bus subclass =3D USB uhci2 at pci0:29:2:=09class=3D0x0c0300 card=3D0x81791043 chip=3D0x27ca8086 = rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801G (ICH7 Family) USB Universal Host Controller' class =3D serial bus subclass =3D USB uhci3 at pci0:29:3:=09class=3D0x0c0300 card=3D0x81791043 chip=3D0x27cb8086 = rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801G (ICH7 Family) USB Universal Host Controller' class =3D serial bus subclass =3D USB ehci0 at pci0:29:7:=09class=3D0x0c0320 card=3D0x81791043 chip=3D0x27cc8086 = rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801G (ICH7 Family) USB 2.0 Enhanced Host Controller' class =3D serial bus subclass =3D USB pcib1 at pci0:30:0:=09class=3D0x060401 card=3D0x81791043 chip=3D0x244e8086 = rev=3D0xe1 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D '82801BA/CA/DB/DBL/EB/ER/FB (ICH2/3/4/4/5/5/6), 6300ESB = Hub Interface to PCI Bridge' class =3D bridge subclass =3D PCI-PCI isab0 at pci0:31:0:=09class=3D0x060100 card=3D0x81791043 chip=3D0x27b88086 = rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801GB/GR (ICH7 Family) LPC Interface Controller' class =3D bridge subclass =3D PCI-ISA atapci0 at pci0:31:1:=09class=3D0x01018f card=3D0x81791043 chip=3D0x27df808= 6 rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801G (ICH7 Family) Ultra ATA Storage Controller' class =3D mass storage subclass =3D ATA atapci1 at pci0:31:2:=09class=3D0x01018f card=3D0x81791043 chip=3D0x27c0808= 6 rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controll= er' class =3D mass storage subclass =3D ATA none2 at pci0:31:3:=09class=3D0x0c0500 card=3D0x81791043 chip=3D0x27da8086 = rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801G (ICH7 Family) SMBus Controller' class =3D serial bus subclass =3D SMBus rl0 at pci1:0:0:=09class=3D0x020000 card=3D0x10015354 chip=3D0x813910ec rev= =3D0x10 hdr=3D0x00 vendor =3D 'Realtek Semiconductor' device =3D 'RT8139 (A/B/C/810x/813x/C+) Fast Ethernet Adapter' class =3D network subclass =3D ethernet ---------------------------------------------------------------------------= ----- % cat /etc/X11/xorg.conf=20 Section "ServerLayout" =09Identifier "X.org Configured" =09Screen 0 "Screen0" 0 0 =09InputDevice "Mouse0" "CorePointer" =09InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" =09RgbPath "/usr/local/share/X11/rgb" =09ModulePath "/usr/local/lib/xorg/modules" EndSection Section "Module" Load "dri" Load "glx" =09 Load "dbe" =09 Load "extmod" EndSection Section "Device" Identifier "Card0" Driver "intel" EndSection Section "InputDevice" =09Identifier "Keyboard0" =09Driver "kbd" EndSection Section "InputDevice" =09Identifier "Mouse0" =09Driver "mouse" =09Option=09 "Protocol" "auto" =09Option=09 "Device" "/dev/sysmouse" EndSection Section "Monitor" =09Identifier "Monitor0" =09HorizSync 30.0 - 83.0 =09VertRefresh 55.0 - 75.0 =09Option=09 "DPMS" EndSection Section "Screen" =09Identifier "Screen0" =09Device "Card0" =09Monitor "Monitor0" DefaultDepth 24 =09SubSection "Display" =09=09Modes "1280x1024" =09EndSubSection EndSection ---------------------------------------------------------------------------= ----- % cat ~/.xinitrc=20 exec twm ---------------------------------------------------------------------------= ----- % startx x3d09e417d83b660d60edaa2f90afe8b4: not found xauth: creating new authority file /home/vermaden/.serverauth.851 X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386=20 Current Operating System: FreeBSD siewa 6.2-STABLE FreeBSD 6.2-STABLE #0: W= ed Sep 26 09:31:01 CEST 2007 root at siewa:/usr/obj/usr/src/sys/CUSTOM = i386 Build Date: 31 July 2007 =09Before reporting problems, check http://wiki.x.org =09to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (=3D=3D) default setting, =09(++) from command line, (!!) notice, (II) informational, =09(WW) warning, (EE) error, (NI) not implemented, (??) unknown. (=3D=3D) Log file: "/var/log/Xorg.0.log", Time: Thu Sep 27 12:21:10 2007 (=3D=3D) Using config file: "/etc/X11/xorg.conf" (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory) (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (EE) intel(0): Couldn't allocate video memory Fatal server error: AddScreen/ScreenInit failed for driver 0 X connection to :0.0 broken (explicit kill or server shutdown). ---------------------------------------------------------------------------= ----- % cat /var/log/Xorg.0.log X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386=20 Current Operating System: FreeBSD siewa 6.2-STABLE FreeBSD 6.2-STABLE #0: W= ed Sep 26 09:31:01 CEST 2007 root at siewa:/usr/obj/usr/src/sys/CUSTOM = i386 Build Date: 31 July 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (=3D=3D) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (=3D=3D) Log file: "/var/log/Xorg.0.log", Time: Thu Sep 27 12:21:10 2007 (=3D=3D) Using config file: "/etc/X11/xorg.conf" (=3D=3D) ServerLayout "X.org Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (=3D=3D) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/ (**) RgbPath set to "/usr/local/share/X11/rgb" (**) ModulePath set to "/usr/local/lib/xorg/modules" (II) Loader magic: 0x819e340 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.1 X.Org XInput driver : 0.7 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on freebsd (II) LoadModule: "pcidata" (II) Loading /usr/local/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.0.0 ABI class: X.Org Video Driver, version 1.1 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages =3D 0x03, oldVal1 =3D 0x00000000, mode1Res1 =3D 0x80000000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2970 card 1043,823b rev 02 class 06,00,00 hdr = 00 (II) PCI: 00:02:0: chip 8086,2972 card 1043,823b rev 02 class 03,00,00 hdr = 00 (II) PCI: 00:1b:0: chip 8086,27d8 card 1043,8290 rev 01 class 04,03,00 hdr = 00 (II) PCI: 00:1d:0: chip 8086,27c8 card 1043,8179 rev 01 class 0c,03,00 hdr = 80 (II) PCI: 00:1d:1: chip 8086,27c9 card 1043,8179 rev 01 class 0c,03,00 hdr = 00 (II) PCI: 00:1d:2: chip 8086,27ca card 1043,8179 rev 01 class 0c,03,00 hdr = 00 (II) PCI: 00:1d:3: chip 8086,27cb card 1043,8179 rev 01 class 0c,03,00 hdr = 00 (II) PCI: 00:1d:7: chip 8086,27cc card 1043,8179 rev 01 class 0c,03,20 hdr = 00 (II) PCI: 00:1e:0: chip 8086,244e card 0000,0000 rev e1 class 06,04,01 hdr = 01 (II) PCI: 00:1f:0: chip 8086,27b8 card 1043,8179 rev 01 class 06,01,00 hdr = 80 (II) PCI: 00:1f:1: chip 8086,27df card 1043,8179 rev 01 class 01,01,8f hdr = 00 (II) PCI: 00:1f:2: chip 8086,27c0 card 1043,8179 rev 01 class 01,01,8f hdr = 00 (II) PCI: 00:1f:3: chip 8086,27da card 1043,8179 rev 01 class 0c,05,00 hdr = 00 (II) PCI: 01:00:0: chip 10ec,8139 card 5354,1001 rev 10 class 02,00,00 hdr = 00 (II) PCI: End of PCI scan (II) Intel Bridge workaround enabled (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Subtractive PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x0002 (VGA_EN is cleare= d) (II) Bus 1 I/O range: [0] -1 0 0x0000e000 - 0x0000efff (0x1000) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xfeb00000 - 0xfebfffff (0x100000) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set= ) (--) PCI:*(0:2:0) Intel Corporation 82946GZ/GL Integrated Graphics Controll= er rev 2, Mem @ 0xfea00000/20, 0xe0000000/28, I/O @ 0xdc00/3 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) Active PCI resource ranges: [0] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]E [1] -1 0 0xfe9f7c00 - 0xfe9f7fff (0x400) MX[B]E [2] -1 0 0xfe9f8000 - 0xfe9fffff (0x8000) MX[B]E [3] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [4] -1 0 0xfea00000 - 0xfeafffff (0x100000) MX[B](B) [5] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B]E [6] -1 0 0x00000400 - 0x000004ff (0x100) IX[B]E [7] -1 0 0x0000c800 - 0x0000c8ff (0x100) IX[B]E [8] -1 0 0x0000c880 - 0x0000c8ff (0x80) IX[B]E [9] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[B]E [10] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[B]E [11] -1 0 0x0000d080 - 0x0000d0ff (0x80) IX[B]E [12] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]E [13] -1 0 0x000008f8 - 0x000008ff (0x8) IX[B]E [14] -1 0 0x000008f0 - 0x000008ff (0x10) IX[B]E [15] -1 0 0x0000c400 - 0x0000c4ff (0x100) IX[B]E [16] -1 0 0x0000c480 - 0x0000c4ff (0x80) IX[B]E [17] -1 0 0x0000d880 - 0x0000d8ff (0x80) IX[B]E [18] -1 0 0x0000d800 - 0x0000d8ff (0x100) IX[B]E [19] -1 0 0x0000d480 - 0x0000d4ff (0x80) IX[B]E [20] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [21] -1 0 0x0000dc00 - 0x0000dc07 (0x8) IX[B](B) (II) PCI I/O resource overlap reduced 0x0000c800 from 0x0000c8ff to 0x0000c= 87f (II) PCI I/O resource overlap reduced 0x0000d000 from 0x0000d0ff to 0x0000d= 07f (II) PCI I/O resource overlap reduced 0x000008f0 from 0x000008ff to 0x00000= 8f7 (II) PCI I/O resource overlap reduced 0x0000c400 from 0x0000c4ff to 0x0000c= 47f (II) PCI I/O resource overlap reduced 0x0000d800 from 0x0000d8ff to 0x0000d= 87f (II) PCI I/O resource overlap reduced 0x0000d400 from 0x0000d4ff to 0x0000d= 47f (II) Active PCI resource ranges after removing overlaps: [0] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]E [1] -1 0 0xfe9f7c00 - 0xfe9f7fff (0x400) MX[B]E [2] -1 0 0xfe9f8000 - 0xfe9fffff (0x8000) MX[B]E [3] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [4] -1 0 0xfea00000 - 0xfeafffff (0x100000) MX[B](B) [5] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B]E [6] -1 0 0x00000400 - 0x000004ff (0x100) IX[B]E [7] -1 0 0x0000c800 - 0x0000c87f (0x80) IX[B]E [8] -1 0 0x0000c880 - 0x0000c8ff (0x80) IX[B]E [9] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[B]E [10] -1 0 0x0000d000 - 0x0000d07f (0x80) IX[B]E [11] -1 0 0x0000d080 - 0x0000d0ff (0x80) IX[B]E [12] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]E [13] -1 0 0x000008f8 - 0x000008ff (0x8) IX[B]E [14] -1 0 0x000008f0 - 0x000008f7 (0x8) IX[B]E [15] -1 0 0x0000c400 - 0x0000c47f (0x80) IX[B]E [16] -1 0 0x0000c480 - 0x0000c4ff (0x80) IX[B]E [17] -1 0 0x0000d880 - 0x0000d8ff (0x80) IX[B]E [18] -1 0 0x0000d800 - 0x0000d87f (0x80) IX[B]E [19] -1 0 0x0000d480 - 0x0000d4ff (0x80) IX[B]E [20] -1 0 0x0000d400 - 0x0000d47f (0x80) IX[B]E [21] -1 0 0x0000dc00 - 0x0000dc07 (0x8) IX[B](B) (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) All system resource ranges: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]E [5] -1 0 0xfe9f7c00 - 0xfe9f7fff (0x400) MX[B]E [6] -1 0 0xfe9f8000 - 0xfe9fffff (0x8000) MX[B]E [7] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [8] -1 0 0xfea00000 - 0xfeafffff (0x100000) MX[B](B) [9] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [10] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [11] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B]E [12] -1 0 0x00000400 - 0x000004ff (0x100) IX[B]E [13] -1 0 0x0000c800 - 0x0000c87f (0x80) IX[B]E [14] -1 0 0x0000c880 - 0x0000c8ff (0x80) IX[B]E [15] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[B]E [16] -1 0 0x0000d000 - 0x0000d07f (0x80) IX[B]E [17] -1 0 0x0000d080 - 0x0000d0ff (0x80) IX[B]E [18] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]E [19] -1 0 0x000008f8 - 0x000008ff (0x8) IX[B]E [20] -1 0 0x000008f0 - 0x000008f7 (0x8) IX[B]E [21] -1 0 0x0000c400 - 0x0000c47f (0x80) IX[B]E [22] -1 0 0x0000c480 - 0x0000c4ff (0x80) IX[B]E [23] -1 0 0x0000d880 - 0x0000d8ff (0x80) IX[B]E [24] -1 0 0x0000d800 - 0x0000d87f (0x80) IX[B]E [25] -1 0 0x0000d480 - 0x0000d4ff (0x80) IX[B]E [26] -1 0 0x0000d400 - 0x0000d47f (0x80) IX[B]E [27] -1 0 0x0000dc00 - 0x0000dc07 (0x8) IX[B](B) (II) LoadModule: "dri" (II) Loading /usr/local/lib/xorg/modules/extensions//libdri.so (II) Module dri: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.0.0 ABI class: X.Org Server Extension, version 0.3 (II) Loading extension XFree86-DRI (II) LoadModule: "glx" (II) Loading /usr/local/lib/xorg/modules/extensions//libglx.so (II) Module glx: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.0.0 ABI class: X.Org Server Extension, version 0.3 (=3D=3D) AIGLX disabled (II) Loading extension GLX (II) LoadModule: "dbe" (II) Loading /usr/local/lib/xorg/modules/extensions//libdbe.so (II) Module dbe: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "extmod" (II) Loading /usr/local/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "intel" (II) Loading /usr/local/lib/xorg/modules/drivers//intel_drv.so (II) Module intel: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 2.1.1 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 1.1 (II) LoadModule: "mouse" (II) Loading /usr/local/lib/xorg/modules/input//mouse_drv.so (II) Module mouse: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.1.1 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.7 (II) LoadModule: "kbd" (II) Loading /usr/local/lib/xorg/modules/input//kbd_drv.so (II) Module kbd: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.1.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.7 (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, 965G, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33 (II) Primary Device is: PCI 00:02:0 (--) Assigning device section with no busID to primary device (--) Chipset 946GZ found (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]E [5] -1 0 0xfe9f7c00 - 0xfe9f7fff (0x400) MX[B]E [6] -1 0 0xfe9f8000 - 0xfe9fffff (0x8000) MX[B]E [7] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [8] -1 0 0xfea00000 - 0xfeafffff (0x100000) MX[B](B) [9] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [10] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [11] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B]E [12] -1 0 0x00000400 - 0x000004ff (0x100) IX[B]E [13] -1 0 0x0000c800 - 0x0000c87f (0x80) IX[B]E [14] -1 0 0x0000c880 - 0x0000c8ff (0x80) IX[B]E [15] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[B]E [16] -1 0 0x0000d000 - 0x0000d07f (0x80) IX[B]E [17] -1 0 0x0000d080 - 0x0000d0ff (0x80) IX[B]E [18] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]E [19] -1 0 0x000008f8 - 0x000008ff (0x8) IX[B]E [20] -1 0 0x000008f0 - 0x000008f7 (0x8) IX[B]E [21] -1 0 0x0000c400 - 0x0000c47f (0x80) IX[B]E [22] -1 0 0x0000c480 - 0x0000c4ff (0x80) IX[B]E [23] -1 0 0x0000d880 - 0x0000d8ff (0x80) IX[B]E [24] -1 0 0x0000d800 - 0x0000d87f (0x80) IX[B]E [25] -1 0 0x0000d480 - 0x0000d4ff (0x80) IX[B]E [26] -1 0 0x0000d400 - 0x0000d47f (0x80) IX[B]E [27] -1 0 0x0000dc00 - 0x0000dc07 (0x8) IX[B](B) (II) resource ranges after probing: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]E [5] -1 0 0xfe9f7c00 - 0xfe9f7fff (0x400) MX[B]E [6] -1 0 0xfe9f8000 - 0xfe9fffff (0x8000) MX[B]E [7] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [8] -1 0 0xfea00000 - 0xfeafffff (0x100000) MX[B](B) [9] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [10] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [11] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [12] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [13] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [14] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B]E [15] -1 0 0x00000400 - 0x000004ff (0x100) IX[B]E [16] -1 0 0x0000c800 - 0x0000c87f (0x80) IX[B]E [17] -1 0 0x0000c880 - 0x0000c8ff (0x80) IX[B]E [18] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[B]E [19] -1 0 0x0000d000 - 0x0000d07f (0x80) IX[B]E [20] -1 0 0x0000d080 - 0x0000d0ff (0x80) IX[B]E [21] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]E [22] -1 0 0x000008f8 - 0x000008ff (0x8) IX[B]E [23] -1 0 0x000008f0 - 0x000008f7 (0x8) IX[B]E [24] -1 0 0x0000c400 - 0x0000c47f (0x80) IX[B]E [25] -1 0 0x0000c480 - 0x0000c4ff (0x80) IX[B]E [26] -1 0 0x0000d880 - 0x0000d8ff (0x80) IX[B]E [27] -1 0 0x0000d800 - 0x0000d87f (0x80) IX[B]E [28] -1 0 0x0000d480 - 0x0000d4ff (0x80) IX[B]E [29] -1 0 0x0000d400 - 0x0000d47f (0x80) IX[B]E [30] -1 0 0x0000dc00 - 0x0000dc07 (0x8) IX[B](B) [31] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [32] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/local/lib/xorg/modules//libint10.so (II) Module int10: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.0.0 ABI class: X.Org Video Driver, version 1.1 (II) Loading sub module "vbe" (II) LoadModule: "vbe" (II) Loading /usr/local/lib/xorg/modules//libvbe.so (II) Module vbe: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.1.0 ABI class: X.Org Video Driver, version 1.1 (II) Loading sub module "vgahw" (II) LoadModule: "vgahw" (II) Loading /usr/local/lib/xorg/modules//libvgahw.so (II) Module vgahw: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 0.1.0 ABI class: X.Org Video Driver, version 1.1 (**) intel(0): Depth 24, (--) framebuffer bpp 32 (=3D=3D) intel(0): RGB weight 888 (=3D=3D) intel(0): Default visual is TrueColor (II) intel(0): Integrated Graphics Chipset: Intel(R) 946GZ (--) intel(0): Chipset: "946GZ" (--) intel(0): Linear framebuffer at 0xE0000000 (--) intel(0): IO registers at addr 0xFEA00000 (=3D=3D) intel(0): Write-combining range (0xfea00000,0x80000) was already c= lear (=3D=3D) intel(0): Write-combining range (0xfea80000,0x80000) was already c= lear (II) intel(0): 2 display pipes available. (=3D=3D) intel(0): Using XAA for acceleration (--) intel(0): Will try to allocate texture pool for old Mesa 3D driver. (II) intel(0): Will try to reserve 32768 kiB of AGP aperture space for the DRM memory manager. (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Loading /usr/local/lib/xorg/modules//libddc.so (II) Module ddc: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.0.0 ABI class: X.Org Video Driver, version 1.1 (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Loading /usr/local/lib/xorg/modules//libi2c.so (II) Module i2c: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.2.0 ABI class: X.Org Video Driver, version 1.1 (II) intel(0): Output VGA using monitor section Monitor0 (II) intel(0): I2C bus "CRTDDC_A" initialized. (II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" initialized. (II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" register= ed at address 0x70. (II) intel(0): No SDVO device found on SDVOB (II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" removed. (II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" removed. (II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" initialized. (II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" register= ed at address 0x72. (II) intel(0): No SDVO device found on SDVOC (II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" removed. (II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" removed. (=3D=3D) intel(0): Write-combining range (0xa0000,0x10000) was already clea= r (II) intel(0): I2C device "CRTDDC_A:ddc2" registered at address 0xA0. (II) intel(0): I2C device "CRTDDC_A:ddc2" removed. (II) intel(0): Using hsync ranges from config file (II) intel(0): Using vrefresh ranges from config file (II) intel(0): Printing DDC gathered Modelines: (II) intel(0): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 62= 8 +hsync +vsync (II) intel(0): Modeline "640x480" 31.50 640 656 720 840 480 481 484 500= -hsync -vsync (II) intel(0): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525= -hsync -vsync (II) intel(0): Modeline "720x400" 28.32 720 738 846 900 400 412 414 449= -hsync +vsync (II) intel(0): Modeline "1280x1024" 135.00 1280 1296 1440 1688 1024 1025= 1028 1066 +hsync +vsync (II) intel(0): Modeline "1024x768" 78.80 1024 1040 1136 1312 768 769 77= 2 800 +hsync +vsync (II) intel(0): Modeline "1024x768" 75.00 1024 1048 1184 1328 768 771 77= 7 806 -hsync -vsync (II) intel(0): Modeline "1024x768" 65.00 1024 1048 1184 1344 768 771 77= 7 806 -hsync -vsync (II) intel(0): Modeline "800x600" 49.50 800 816 896 1056 600 601 604 62= 5 +hsync +vsync (II) intel(0): Modeline "1280x1024" 138.75 1280 1368 1504 1728 1024 1027= 1034 1072 -hsync +vsync (II) intel(0): Modeline "1280x1024" 109.00 1280 1368 1496 1712 1024 1027= 1034 1063 -hsync +vsync (II) intel(0): Modeline "1024x768" 82.00 1024 1088 1192 1360 768 771 77= 5 805 -hsync +vsync (II) intel(0): Modeline "1024x768" 63.50 1024 1072 1176 1328 768 771 77= 5 798 -hsync +vsync (II) intel(0): Modeline "800x600" 49.00 800 840 920 1040 600 603 607 62= 9 -hsync +vsync (II) intel(0): Modeline "800x600" 38.25 800 832 912 1024 600 603 607 62= 4 -hsync +vsync (II) intel(0): Modeline "1280x1024" 108.00 1280 1328 1440 1688 1024 1025= 1028 1066 +hsync +vsync (II) intel(0): EDID vendor "ACR", prod id 44369 (II) intel(0): Output VGA connected (II) intel(0): Output VGA using initial mode 1280x1024 (=3D=3D) intel(0): Write-combining range (0xa0000,0x10000) was already clea= r (II) intel(0): detected 512 kB GTT. (II) intel(0): detected 7676 kB stolen memory. (=3D=3D) intel(0): video overlay key set to 0x101fe (=3D=3D) intel(0): Will not try to enable page flipping (=3D=3D) intel(0): Triple buffering disabled (=3D=3D) intel(0): Using gamma correction (1.0, 1.0, 1.0) (**) intel(0): Display dimensions: (340, 270) mm (**) intel(0): DPI set to (95, 120) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/local/lib/xorg/modules//libfb.so (II) Module fb: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.3 (II) Loading sub module "xaa" (II) LoadModule: "xaa" (II) Loading /usr/local/lib/xorg/modules//libxaa.so (II) Module xaa: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.2.0 ABI class: X.Org Video Driver, version 1.1 (II) Loading sub module "ramdac" (II) LoadModule: "ramdac" (II) Loading /usr/local/lib/xorg/modules//libramdac.so (II) Module ramdac: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 0.1.0 ABI class: X.Org Video Driver, version 1.1 (II) intel(0): Comparing regs from server start up to After PreInit (=3D=3D) Depth 24 pixmap format is 32 bpp (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] 0 0 0xe0000000 - 0xefffffff (0x10000000) MS[B] [1] 0 0 0xfea00000 - 0xfeafffff (0x100000) MS[B] [2] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [3] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [4] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [5] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [6] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]E [7] -1 0 0xfe9f7c00 - 0xfe9f7fff (0x400) MX[B]E [8] -1 0 0xfe9f8000 - 0xfe9fffff (0x8000) MX[B]E [9] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [10] -1 0 0xfea00000 - 0xfeafffff (0x100000) MX[B](B) [11] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD) [12] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD) [13] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD) [14] 0 0 0x0000dc00 - 0x0000dc07 (0x8) IS[B] [15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [16] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [17] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B]E [18] -1 0 0x00000400 - 0x000004ff (0x100) IX[B]E [19] -1 0 0x0000c800 - 0x0000c87f (0x80) IX[B]E [20] -1 0 0x0000c880 - 0x0000c8ff (0x80) IX[B]E [21] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[B]E [22] -1 0 0x0000d000 - 0x0000d07f (0x80) IX[B]E [23] -1 0 0x0000d080 - 0x0000d0ff (0x80) IX[B]E [24] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]E [25] -1 0 0x000008f8 - 0x000008ff (0x8) IX[B]E [26] -1 0 0x000008f0 - 0x000008f7 (0x8) IX[B]E [27] -1 0 0x0000c400 - 0x0000c47f (0x80) IX[B]E [28] -1 0 0x0000c480 - 0x0000c4ff (0x80) IX[B]E [29] -1 0 0x0000d880 - 0x0000d8ff (0x80) IX[B]E [30] -1 0 0x0000d800 - 0x0000d87f (0x80) IX[B]E [31] -1 0 0x0000d480 - 0x0000d4ff (0x80) IX[B]E [32] -1 0 0x0000d400 - 0x0000d47f (0x80) IX[B]E [33] -1 0 0x0000dc00 - 0x0000dc07 (0x8) IX[B](B) [34] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) [35] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory) (WW) intel(0): /dev/agpgart is either not available, or no memory is availa= ble for allocation. Using pre-allocated memory only. (=3D=3D) intel(0): VideoRam: 7676 KB (=3D=3D) intel(0): Write-combining range (0xfea00000,0x80000) was already c= lear (=3D=3D) intel(0): Write-combining range (0xfea80000,0x80000) was already c= lear (II) intel(0): Attempting memory allocation with tiled buffers and=20 large DRI memory manager reservation: (II) intel(0): Allocating 255 scanlines for pixmap cache (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (II) intel(0): Attempting memory allocation with tiled buffers and=20 small DRI memory manager reservation: (II) intel(0): Allocating 255 scanlines for pixmap cache (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (II) intel(0): Attempting memory allocation with untiled buffers and=20 large DRI memory manager reservation: (II) intel(0): Allocating 255 scanlines for pixmap cache (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (II) intel(0): Attempting memory allocation with untiled buffers and=20 small DRI memory manager reservation: (II) intel(0): Allocating 255 scanlines for pixmap cache (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (WW) intel(0): Not enough video memory. Disabling DRI. (II) intel(0): Allocating 255 scanlines for pixmap cache (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (EE) intel(0): Couldn't allocate video memory Fatal server error: AddScreen/ScreenInit failed for driver 0 ---------------------------------------------------------------------- Gra - zostan agentem ABW! Zobacz >>> http://link.interia.pl/f1ba5 From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 12:08:43 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D102D16A468 for ; Thu, 27 Sep 2007 12:08:43 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.191]) by mx1.freebsd.org (Postfix) with ESMTP id 7595F13C474 for ; Thu, 27 Sep 2007 12:08:43 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by fk-out-0910.google.com with SMTP id b27so3032298fka for ; Thu, 27 Sep 2007 05:08:42 -0700 (PDT) Received: by 10.82.152.16 with SMTP id z16mr4427120bud.1190894921219; Thu, 27 Sep 2007 05:08:41 -0700 (PDT) Received: by 10.82.148.14 with HTTP; Thu, 27 Sep 2007 05:08:41 -0700 (PDT) Message-ID: Date: Thu, 27 Sep 2007 15:08:41 +0300 From: "Vlad GALU" To: "Jeff Roberson" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070924161054.T547@10.0.0.1> Cc: FreeBSD Current Subject: Re: Bogus numbers with rev 1.209 of sched_ule.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 12:08:43 -0000 On 9/25/07, Vlad GALU wrote: > On 9/25/07, Jeff Roberson wrote: > > On Mon, 24 Sep 2007, Vlad GALU wrote: > > > > > -- cut here -- > > > > > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > > > 34653 root 1 5 0 3136K 1048K ttyin 0 0:00 nan% getty > > > 37990 root 1 8 0 4328K 2272K wait 1 0:00 nan% bash > > > 37915 dapyx 1 8 0 3564K 1540K wait 0 0:00 nan% su > > > 37711 dapyx 1 20 0 4392K 2432K pause 0 0:00 nan% tcsh > > > -- and here -- > > > > Try rebuilding world? Or at least libkvm/top/ps? I've never seen this > > problem but I upgraded my world at the same time that I made several > > changes that impacted libkvm. > > > > Unfortunately, I've already tried that. I confirmed to myself that this wasn't a PEBKAC by switching back to 4BSD, where the figures are normal. The box where I first saw this is SMP, but I tried it on an UP and the symptom showed there as well. > > > Thanks, > > Jeff > > > > > > > > -- > > > If it's there, and you can see it, it's real. > > > If it's not there, and you can see it, it's virtual. > > > If it's there, and you can't see it, it's transparent. > > > If it's not there, and you can't see it, you erased 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" > > > > > > > > -- > If it's there, and you can see it, it's real. > If it's not there, and you can see it, it's virtual. > If it's there, and you can't see it, it's transparent. > If it's not there, and you can't see it, you erased it. > -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 12:10:19 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3AED16A468 for ; Thu, 27 Sep 2007 12:10:19 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.freebsd.org (Postfix) with ESMTP id 864FB13C4D1 for ; Thu, 27 Sep 2007 12:10:19 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from parancell.ongs.co.jp (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id 71376244C3A for ; Thu, 27 Sep 2007 21:10:18 +0900 (JST) Message-ID: <46FB9DAA.1080104@freebsd.org> Date: Thu, 27 Sep 2007 21:10:18 +0900 From: Daichi GOTO User-Agent: Thunderbird 2.0.0.6 (X11/20070803) MIME-Version: 1.0 To: FreeBSD Current References: <46F905FD.9060208@freebsd.org> <20070925194008.3c2d7113@epia-2.farid-hajji.net> <20070926114705.GA12643@holyman.cobbled.net> In-Reply-To: <20070926114705.GA12643@holyman.cobbled.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: The safety expansion for FreeBSD rm(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 12:10:19 -0000 Oh yeah--it's an interesting point, and we are going to think about it :) ttw+bsd@cobbled.net wrote: > Daichi GOTO wrote: > [ ... ] >> Have you any dreams that rm(1) autonomously judges target should >> be remove or not? To complexify system base command is objectionable >> behavior but adding some little and simple mechanism to prevent a >> issue is acceptable I suppose. > > this is a nice little feature but from an administrative point of view > i don't think it will be used (i'm infallable, as are most admins > ... at least within their own heads) and there are other more > comprehensive (i.e. not just the rm binary) tools for critical paths > (as others have pointed out). from a user perspective it would be > nice to have '/etc/rm.conf' or something so the admin can prevent user > foot shooting, however, how many user deletes will actually be performed > by 'rm'. basically, it's very clever, non-intrusive feature but i > just can't see any value from it. > > perhaps if, instead of overlapping the current flags function, you > used this feature to allow the user to be prompted when deleting a > 'uunlink' file, or so that a user may set places where 'rm' will > effectively ignore the 'uunlink' flag. still not sure how much value > but it may encourage the use of 'uunlink' so that more paths are > protected (i.e. if more binaries are flags aware we don't need to > constantly change flags to perform functions). one obstacle i can > think of is that many files may be stored on filesystems incompatible > with flags. > _______________________________________________ > 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" -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 12:28:06 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A81F16A417 for ; Thu, 27 Sep 2007 12:28:06 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout2.freenet.de (mout2.freenet.de [IPv6:2001:748:100:40::2:4]) by mx1.freebsd.org (Postfix) with ESMTP id 815FA13C478 for ; Thu, 27 Sep 2007 12:28:05 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from [195.4.92.21] (helo=mx11.freenet.de) by mout2.freenet.de with esmtpa (Exim 4.68) (envelope-from ) id 1IasTL-0003Du-44; Thu, 27 Sep 2007 14:28:03 +0200 Received: from x0b81.x.pppool.de ([89.59.11.129]:52547 helo=peedub.jennejohn.org) by mx11.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.68 #6) id 1IasTI-0006ot-Qg; Thu, 27 Sep 2007 14:28:00 +0200 Date: Thu, 27 Sep 2007 14:28:02 +0200 From: Gary Jennejohn To: freebsd-current@freebsd.org Message-ID: <20070927142802.1ae6541d@peedub.jennejohn.org> In-Reply-To: <20070926113643.GA21109@muon.bluestop.org> References: <20070926113643.GA21109@muon.bluestop.org> Organization: DENX Softwre Engineering GmbH X-Mailer: Claws Mail 3.0.0 (GTK+ 2.10.13; amd64-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: bruce@cran.org.uk Subject: Re: Interrupt storm on ahc0 when drm module is loaded X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.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, 27 Sep 2007 12:28:06 -0000 On Wed, 26 Sep 2007 12:36:44 +0100 bruce@cran.org.uk wrote: > I've come some sort of conflict between the drm and ahc drivers: > whenever drm is loaded I get an interrupt storm on ahc0. My system is: > > 7.0-CURRENT #0: Tue Sep 25 18:08:50 BST 2007 > /usr/obj/usr/src/sys/GENERIC i386 > > I'm running Xorg 7.3 > > ahc0: port 0xdc00-0xdcff mem > 0xd9200000-0xd9200fff irq 16 at device 9.0 on pci0 > ahc0: [ITHREAD] > da0 at ahc0 bus 0 target 6 lun 0 > > drm0: on vgapci0 > info: [drm] AGP at 0xd0000000 64MB > info: [drm] Initialized mga 3.2.2 20060319 > info: [drm] Initialized card for AGP DMA > drm0: [ITHREAD] > > vmstat -i: > interrupt total rate > irq1: atkbd0 4036 0 > irq14: ata0 58 0 > irq16: ahc0 15004943 2824 > irq19: fxp0 40961 7 > cpu0: timer 10624196 1999 > cpu1: timer 10606936 1996 > Total 36281130 6828 > > Over time the rate for ahc0 grows until I get the "Interrupt storm > detected: throttling irq16" messages. I can trigger the problem by > changing the default colour depth to 16 bits in my xorg.conf file: this > enables the drm module to load and immediately the interrupt rate starts > to climb. > Have you looked at disabling interrupts for VGA in your BIOS (if possible)? Don't know what effect this would have on X11's performance. You could also try a different PCI slot. An unrelated question. I also have a 19160 but the SCSI BIOS never shows up at boot time so I can't boot from it. Did you ever see anything like that? -- Gary Jennejohn From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 13:51:34 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8023716A419; Thu, 27 Sep 2007 13:51:34 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0134713C465; Thu, 27 Sep 2007 13:51:33 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from epia-2.farid-hajji.net (epia-2 [192.168.254.11]) by fw.farid-hajji.net (Postfix) with ESMTP id 2EB85DF81D; Thu, 27 Sep 2007 15:52:15 +0200 (CEST) Date: Thu, 27 Sep 2007 15:55:19 +0200 From: cpghost To: Daichi GOTO Message-ID: <20070927155519.114cac72@epia-2.farid-hajji.net> In-Reply-To: <46FB93BC.2000508@freebsd.org> References: <46F905FD.9060208@freebsd.org> <20070925194008.3c2d7113@epia-2.farid-hajji.net> <46FB93BC.2000508@freebsd.org> Organization: Cordula's Web X-Mailer: Claws Mail 3.0.0 (GTK+ 2.10.14; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: wrapping dynamic syscalls with wrap(1) (was: safety-rm) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 13:51:34 -0000 On Thu, 27 Sep 2007 20:27:56 +0900 Daichi GOTO wrote: > >> We have created safety expansion for rm(1). If you have any > >> interests, please try follow patch. > >> > >> http://people.freebsd.org/~daichi/safety-rm/ > > And unusual commands like chflags I just suppose are no much > point in this case. What is important is that adding mistake > protecting functions into common commands like rm(1) itself. Perhaps the solution is not general enough: rm(1) is but one program using the unlink(2) syscall. Why not protect unlink(2) itself by wrapping it into a function that does all this checking that you're putting into safety-rm right now? Users who want to protect themselves could then dynamically link this unlink-wrapper into all their applications. When an application calls unlink(2), that call will be diverted to unlink(3), the wrapper. Ideally, users should have a generic way to wrap syscalls (or other dynamic library calls) with a program similar to env(1), let's call it wrap(1). A call to wrap(1): $ wrap lib1 lib2 lib3 ... prog would dynamically relink prog in such a way that it uses objects taken from lib1, lib2, lib3 ... instead of the libraries it is already linked to against. To protect unlink(2) in a shell session, one could then write an unlink(3) wrapper into a library libsafe_unlink.so, and invoke the shell like: $ wrap safe_unlink /bin/sh Now, every call to unlink(2) (be it from /bin/sh - that's easy, or from all their children - that's the hard part), would call the unlink(3) from this library wrapper libsafe_unlink.so That would be really useful, not only in the unlink(2) case. You could do all kinds of stuff with that, like profiling, instrumenting etc... Of course, there's already libmap.conf(5), but it would be nice to have something that's not limited to root, and that could be used more dynamically, as in wrap(1). Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/ From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 14:16:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E76B16A41B for ; Thu, 27 Sep 2007 14:16:18 +0000 (UTC) (envelope-from cb@severious.net) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.freebsd.org (Postfix) with ESMTP id 4641513C4BD for ; Thu, 27 Sep 2007 14:16:17 +0000 (UTC) (envelope-from cb@severious.net) Received: by ion.gank.org (Postfix, from userid 1001) id B2E64111F3; Thu, 27 Sep 2007 09:16:17 -0500 (CDT) Date: Thu, 27 Sep 2007 09:16:16 -0500 From: Craig Boston To: cpghost Message-ID: <20070927141608.GA929@nowhere> Mail-Followup-To: Craig Boston , cpghost , Daichi GOTO , FreeBSD Current References: <46F905FD.9060208@freebsd.org> <20070925194008.3c2d7113@epia-2.farid-hajji.net> <46FB93BC.2000508@freebsd.org> <20070927155519.114cac72@epia-2.farid-hajji.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070927155519.114cac72@epia-2.farid-hajji.net> User-Agent: Mutt/1.4.2.3i Cc: Daichi GOTO , FreeBSD Current Subject: Re: wrapping dynamic syscalls with wrap(1) (was: safety-rm) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 14:16:18 -0000 On Thu, Sep 27, 2007 at 03:55:19PM +0200, cpghost wrote: > Ideally, users should have a generic way to wrap syscalls (or > other dynamic library calls) with a program similar to env(1), > let's call it wrap(1). A call to wrap(1): Anyone who implements this should be aware of the security issues surrounding system-call wrapping: http://www.watson.org/~robert/2007woot/ The short version is that it's extremely difficult to safely wrap system calls, and probably impossible without kernel support. Craig From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 14:32:16 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36B7116A41A for ; Thu, 27 Sep 2007 14:32:16 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id 8DD9913C459 for ; Thu, 27 Sep 2007 14:32:15 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id l8REUlAa017381; Thu, 27 Sep 2007 16:30:55 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id l8REUl1v017380; Thu, 27 Sep 2007 16:30:47 +0200 (CEST) (envelope-from olli) Date: Thu, 27 Sep 2007 16:30:47 +0200 (CEST) Message-Id: <200709271430.l8REUl1v017380@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG, cpghost@cordula.ws, Daichi GOTO In-Reply-To: <20070927155519.114cac72@epia-2.farid-hajji.net> X-Newsgroups: list.freebsd-current User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Thu, 27 Sep 2007 16:30:55 +0200 (CEST) Cc: Subject: Re: wrapping dynamic syscalls with wrap(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@FreeBSD.ORG, cpghost@cordula.ws, Daichi GOTO List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 14:32:16 -0000 cpghost wrote: > Daichi GOTO wrote: > > And unusual commands like chflags I just suppose are no much I think that chflags(1) is not "unusual". A non-standard extension to rm(1) would be unusual. > > point in this case. What is important is that adding mistake > > protecting functions into common commands like rm(1) itself. > > Perhaps the solution is not general enough: rm(1) is but one > program using the unlink(2) syscall. Why not protect unlink(2) > itself by wrapping it into a function that does all this checking > that you're putting into safety-rm right now? > > Users who want to protect themselves could then dynamically > link this unlink-wrapper into all their applications. When an > application calls unlink(2), that call will be diverted to > unlink(3), the wrapper. That's an interesting idea. > Ideally, users should have a generic way to wrap syscalls (or > other dynamic library calls) with a program similar to env(1), > let's call it wrap(1). A call to wrap(1): > > $ wrap lib1 lib2 lib3 ... prog How is that different from this: $ LD_PRELOAD="lib1 lib2 lib3 ..." prog Well, if you want to save a little bit of typing, wrap(1) could be trivially implemented as a shell script: #/bin/sh - if [ $# -lt 1 ]; then echo "Usage: ${0##*/} [ ...] " >&2 exit 1 fi eval PROG=\$$# LIBS=${*%$PROG} LD_PRELOAD="${LIBS% }" exec "$PROG" By the way, I have used the LD_PRELOAD trick in the past; it works fine. I used it to wrap a few functions in libX11 in order to capture video and audio from certain closed- source player applications that didn't allow to save media files to disk. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "FreeBSD is Yoda, Linux is Luke Skywalker" -- Daniel C. Sobral From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 15:06:39 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60A8216A419; Thu, 27 Sep 2007 15:06:39 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 140FB13C459; Thu, 27 Sep 2007 15:06:39 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 5BEF72F578; Thu, 27 Sep 2007 11:06:38 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Thu, 27 Sep 2007 11:06:38 -0400 X-Sasl-enc: IiANS9GHHG49wGcPjnvee/tVGsL1PFixhLJeuwpwHiSH 1190905598 Received: from [192.168.1.235] (64-142-85-108.dsl.dynamic.sonic.net [64.142.85.108]) by mail.messagingengine.com (Postfix) with ESMTP id 40BBB5789; Thu, 27 Sep 2007 11:06:37 -0400 (EDT) Message-ID: <46FBC739.20808@freebsd.org> Date: Thu, 27 Sep 2007 08:07:37 -0700 From: Darren Reed User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Kris Kennaway References: <20070921102946.T11189@borg> <46F415BF.9010500@FreeBSD.org> <20070921140550.D96923@thebighonker.lerctr.org> <46F41CFF.6080108@FreeBSD.org> <46F58799.1030702@freebsd.org> <46F58B21.8030307@FreeBSD.org> <20070924091558.GB32006@team.vega.ru> <46F78C59.1020801@FreeBSD.org> <20070924080347.O84223@thebighonker.lerctr.org> <20070924144210.GA82735@team.vega.ru> <46F7D7A4.5090007@samsco.org> <46F80A39.3050707@FreeBSD.org> <46F8951C.50904@freebsd.org> <46F8CE67.60206@FreeBSD.org> <46FA2E46.8020303@freebsd.org> <46FAD957.3060208@FreeBSD.org> In-Reply-To: <46FAD957.3060208@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Larry Rosenman Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 15:06:39 -0000 Kris Kennaway wrote: > Darren Reed wrote: >> Kris Kennaway wrote: >>> Darren Reed wrote: >>>> Kris Kennaway wrote: >>>>> ... >>>>> Well yes, that is one hypothesis, but the evidence points >>>>> elsewhere as well. Prior the change you reference, some of my zfs >>>>> machines would run for weeks before hitting a load pattern that >>>>> exhausted their kmem_map and triggered the panic. Also unless I >>>>> have missed it I am not seeing the sudden flood of panic reports >>>>> that may indicate sudden breakage. It is quite possible that this >>>>> particular report has nothing to do with the recent change. >>>> >>>> Indeed. >>>> >>>> But here's something else to ponder... >>>> >>>> I've been using ZFS since it was internal beta at Sun, at first on >>>> i386 and later on amd64. >>>> I've never run into this kind of panic on Solaris. System can get >>>> very slow, yes, with >>>> ZFS hogging lots of memory, but it never panic'd because of it. >>>> >>>> We need to come up with a strategy here to solve this problem, be >>>> it fixing the kmem >>>> virtual memory or fixing zfs. >>> >>> Yes, Solaris does something architecturally different because it is >>> apparently acceptable for zfs to use gigabytes of memory by default. >> >> Well, if you were designing a file system for servers, is there any >> reason that you wouldn't try to use all of the RAM available? > > No, but it's different to what FreeBSD does. Especially on i386. In the ZFS tuning guide, it mentions that the ARC should be tuned if memory is tight and that the ARC should be no more than 80% of the kmem vm. Does this advice also correspond to FreeBSD? Or do we ship with a small ARC by default and the only problem is the kmem map? Darren From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 15:29:07 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7744A16A418 for ; Thu, 27 Sep 2007 15:29:07 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 5EA3613C49D for ; Thu, 27 Sep 2007 15:29:07 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id 71E991A4D81; Thu, 27 Sep 2007 08:05:26 -0700 (PDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Thu, 27 Sep 2007 10:53:09 -0400 User-Agent: KMail/1.9.7 References: <46E92139.1030508@adam.com.au> <20070913153342.GJ945@void.codelabs.ru> In-Reply-To: <20070913153342.GJ945@void.codelabs.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709271053.09977.jhb@freebsd.org> Cc: Pete Subject: Re: FreeBSD 6.x and HP? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 15:29:07 -0000 On Thursday 13 September 2007 11:33:43 am Eygene Ryabinkin wrote: > Pete, good day. > > Thu, Sep 13, 2007 at 09:08:33PM +0930, Pete wrote: > > I've been having a rather unusual, but very annoying issue with HP DL140 G3 > > Servers and FreeBSD. I thought I might give the mailing list a try to see what > > I can find and whether anyone else has had similar issues. When trying to > > install FreeBSD 6.x AMD64, as these boxes look to have the Woodcrest core Xeon > > CPUs (5100-series), which support EMT64T, I have encountered the following > > issues. > > I didn't tried FreeBSD on these servers, but for Linux 64-bit systems > demand that "8042 Emulation Support" must be disabled (BIOS, menu > "Advanced"). Try this, may be it will help, especially if you have > no problems with FreeBSD/i386 and 8042 emulation is currently enabled > on your machine. > > Drop me a letter if things will fail for you, I might be able to > check FreeBSD/amd64 on the DL140 G3 I have at hand. FreeBSD 6.x should work fine on a DL 140 G3, and you don't have to fiddle with the 8042 emulation stuff (either setting works). I think it might hang on reboot if 8042 is turned off though (fixed in 6.2-stable). -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 16:44:28 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 964AE16A41A for ; Thu, 27 Sep 2007 16:44:28 +0000 (UTC) (envelope-from SRS0=2ad5e8a3e4056f874a577467dff54e86260b4aa2=471=es.net=oberman@es.net) Received: from postal1.es.net (postal4.es.net [IPv6:2001:400:6000:1::66]) by mx1.freebsd.org (Postfix) with ESMTP id E507713C455 for ; Thu, 27 Sep 2007 16:44:25 +0000 (UTC) (envelope-from SRS0=2ad5e8a3e4056f874a577467dff54e86260b4aa2=471=es.net=oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal4.es.net (Postal Node 4) with ESMTP (SSL) id GZT51823; Thu, 27 Sep 2007 09:44:23 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id A801B45019; Thu, 27 Sep 2007 09:44:21 -0700 (PDT) To: Rudy In-Reply-To: Your message of "Wed, 26 Sep 2007 21:24:07 PDT." <46FB3067.8040706@MonkeyBrains.NET> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1190911461_26412P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 27 Sep 2007 09:44:21 -0700 From: "Kevin Oberman" Message-Id: <20070927164421.A801B45019@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ;; X-Sender: X-To_Name: Rudy X-To_Domain: monkeybrains.net X-To: Rudy X-To_Email: crapsh@MonkeyBrains.NET X-To_Alias: crapsh Cc: freebsd-current@freebsd.org Subject: Re: Flash plugin status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 16:44:28 -0000 --==_Exmh_1190911461_26412P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Wed, 26 Sep 2007 21:24:07 -0700 > From: Rudy > Sender: owner-freebsd-current@freebsd.org > > > About a month ago, Flash 7 was marked unsafe, and Flash 9 doesn't work > on many sites. > > [1] Anyone have any tricks to get Flash 9 working in 7.x? > [2] Any update on getting the freebsd foundation to take > on Flash (ala Java)? > [3] Anyone work at Adobe (nee Macromedia) that can get a > build for FreeBSD published? For the record, after the update to linux-flashplugin7 3 days ago, it is no longer marked unsafe and I have had no problems updating. It now will, by default, build with support for nspluginwrapper. I did the update and ran: nspluginwrapper -i -v /usr/X11R6/lib/linux-mozilla/plugins/nphelix.so \ /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so (I don't like the Acrobat plugin, so I don't install that one.) Note that nspluginwrapper must be run by each user before starting firefox. I have no joy to spread in Flash 9. Happily, most of the sites I use that are Flash-based are still working with Flash 7. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1190911461_26412P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFG+93lkn3rs5h7N1ERAqGRAKCTKVu3zDaK1D0gl17Ow56H2FHGdACeK11T xEoUL0KQLbxZQwRXHop4RhQ= =c1M/ -----END PGP SIGNATURE----- --==_Exmh_1190911461_26412P-- From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 17:08:45 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC6B516A417; Thu, 27 Sep 2007 17:08:45 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by mx1.freebsd.org (Postfix) with ESMTP id 9A20E13C465; Thu, 27 Sep 2007 17:08:45 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay12.apple.com (relay12.apple.com [17.128.113.53]) by mail-out3.apple.com (Postfix) with ESMTP id 9827F12CAF35; Thu, 27 Sep 2007 10:08:45 -0700 (PDT) Received: from relay12.apple.com (unknown [127.0.0.1]) by relay12.apple.com (Symantec Mail Security) with ESMTP id 782132804F; Thu, 27 Sep 2007 10:08:45 -0700 (PDT) X-AuditID: 11807135-a5effbb000006e40-96-46fbe39d7c38 Received: from [17.214.13.96] (cswiger1.apple.com [17.214.13.96]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay12.apple.com (Apple SCV relay) with ESMTP id 59B282804C; Thu, 27 Sep 2007 10:08:45 -0700 (PDT) In-Reply-To: <86zlz8zlyv.fsf@ds4.des.no> References: <20070921102946.T11189@borg> <46F415BF.9010500@FreeBSD.org> <20070921140550.D96923@thebighonker.lerctr.org> <46F41CFF.6080108@FreeBSD.org> <46F58799.1030702@freebsd.org> <46F58B21.8030307@FreeBSD.org> <20070924091558.GB32006@team.vega.ru> <46F78C59.1020801@FreeBSD.org> <20070924080347.O84223@thebighonker.lerctr.org> <20070924144210.GA82735@team.vega.ru> <46F7D7A4.5090007@samsco.org> <46F80A39.3050707@FreeBSD.org> <46F8951C.50904@freebsd.org> <46F8CE67.60206@FreeBSD.org> <46FA2E46.8020303@freebsd.org> <86zlz8zlyv.fsf@ds4.des.no> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <84E9AA30-96B5-4517-B43E-0AC98550639D@mac.com> Content-Transfer-Encoding: quoted-printable From: Chuck Swiger Date: Thu, 27 Sep 2007 10:08:44 -0700 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAA== Cc: Darren Reed , Kris Kennaway , freebsd-current@freebsd.org, Larry Rosenman Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 17:08:45 -0000 On Sep 26, 2007, at 11:00 PM, Dag-Erling Sm=F8rgrav wrote: > Chuck Swiger writes: >> I'm not certain whether FreeBSD's kernel memory allocator [malloc(9), >> zone(9)] even supports the notion of allocating pageable memory >> rather than memory taken from the fixed KVA region. The manpage >> implies that calling kernel malloc with M_WAITOK will always return a >> valid pointer and not NULL, but I'm not convinced this is will be >> true if you try allocating something larger than the size of KVA and/ >> or the amount of physical RAM available in the system. > > malloc(M_WAITOK) will panic if the request is not satisfiable. =20 > Where do > you think "kmem_map too small" comes from? Indeed-- an excellent point that would be nifty to find in the docs: --- src/share/man/man9/malloc.9~ 2005-02-22 12:20:20.000000000 -0500 +++ src/share/man/man9/malloc.9 2007-09-27 13:00:36.000000000 -0400 @@ -289,7 +289,9 @@ .Dv NULL if the request could not be satisfied (implying that .Dv M_NOWAIT -was set). +was set). However, if +.Dv M_WAITOK +is set and the request could not be satisfied, the kernel will panic. .Sh DIAGNOSTICS A kernel compiled with the .Dv INVARIANTS ...? --=20 -Chuck From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 22:15:38 2007 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE27816A41B for ; Thu, 27 Sep 2007 22:15:38 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id 9A68B13C47E for ; Thu, 27 Sep 2007 22:15:38 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 73095 invoked from network); 27 Sep 2007 22:15:39 -0000 Received: from ppp-71-139-1-224.dsl.snfc21.pacbell.net (HELO ?10.0.0.15?) (nate-mail@71.139.1.224) by root.org with ESMTPA; 27 Sep 2007 22:15:39 -0000 Message-ID: <46FC2B86.9000100@root.org> Date: Thu, 27 Sep 2007 15:15:34 -0700 From: Nate Lawson User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: acpi@freebsd.org, current@FreeBSD.org X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: boot hangs with acpi enabled? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 22:15:39 -0000 Could anyone who is experiencing a boot-time hang on 7-current with acpi enabled send some information? First, be sure your system works with acpi disabled (hint.acpi.0.disabled="1"), otherwise it's something else. Then, compile your kernel with: options DDB options KDB Reboot with the new kernel and hit CTRL-ALT-ESC when the boot hangs. Type "trace" to get a stack trace as to what's hung. Copy down those lines or take a small photo and send it back. Thanks, -- Nate From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 22:19:49 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A3D116A418 for ; Thu, 27 Sep 2007 22:19:49 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 9FDF213C469; Thu, 27 Sep 2007 22:19:47 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46FC2C85.4080600@FreeBSD.org> Date: Fri, 28 Sep 2007 00:19:49 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Joao Pedras References: <46FA0C14.10201@webvolution.net> <46FADB35.2090708@FreeBSD.org> <46FC2AA7.2040308@webvolution.net> In-Reply-To: <46FC2AA7.2040308@webvolution.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: lock up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 22:19:49 -0000 Joao Pedras wrote: > Hi again, > > hope this info sheds some light on this. A similar system is getting > setup to reproduce the problem there as well. > > Thanks! > > Joao > > Kris Kennaway wrote: >> Joao Pedras wrote: >>> Greetings all! >>> >>> A system (Tyan S2932) I am testing CURRENT amd64 with is experiencing a >>> strange lock up. No panic, not much on the console, just a lock up, >>> freeze. >>> >>> I first noticed the issue while tailing a build in a ssh session over a >>> vpn connection. On the local network the issue doesn't seem to occur. >>> I can reproduce the lock up all the time. >>> >>> Last I tried, the system was running CURRENT from a couple hours ago. >>> >>> I have tried: >>> >>> - 4BSD and ULE >>> - switching network cards >>> - taking the IPMI card out (seems to work locally with freeipmi and >>> ipmitoll remotely) >>> - enabled/disabled "redirection after post" (BIOS setting) >>> - without debug >>> - without IPv6 and friends (see rtfree below) >>> >>> dmesg and pciconf attached. The dmesg is after a lock up. >>> rtfree pops a few times before the lock up. I noticed from a recent post >>> some action was taken and the related patch is there (ie. today's >>> CURRENT). >>> >>> The system had a fresh install this past weekend and the LSI MegaRAID >>> array doesn't contain any data, it is just mounted. The system boots off >>> the onboard LSI SAS (couple disks in RAID 1). >>> >>> Thank you for your input. >> Break to DDB and obtain process traces, etc. See the developers handbook. >> >> Kris >> Well that's a start, but you need to trace other processes too, e.g. the running ones. Do an 'alltrace' to trace everything. Kris From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 16:26:13 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66DCE16A41B for ; Thu, 27 Sep 2007 16:26:13 +0000 (UTC) (envelope-from jaj@hcl-club.lu) Received: from 0b10111.de (hcl-club.lu [62.75.155.129]) by mx1.freebsd.org (Postfix) with ESMTP id 202FA13C480 for ; Thu, 27 Sep 2007 16:26:13 +0000 (UTC) (envelope-from jaj@hcl-club.lu) Received: from localhost (4be54-4-82-234-154-189.fbx.proxad.net [82.234.154.189]) by 0b10111.de (Postfix) with ESMTP id 23120872C10E; Thu, 27 Sep 2007 18:09:18 +0200 (CEST) Date: Thu, 27 Sep 2007 18:09:14 +0200 From: Jona Joachim To: Rudy Message-ID: <20070927180914.735bd431@hcl-club.lu> In-Reply-To: <46FB3067.8040706@MonkeyBrains.NET> References: <46FB3067.8040706@MonkeyBrains.NET> X-Mailer: Claws Mail 3.0.1 (GTK+ 2.10.14; i386-portbld-freebsd6.2) X-Face: &>dujC`JZV!}?Y^1"%N{x!f+rW}; PX\_Cg[!|MA~tn3ebIKM|~p=,,U~YJt,Exd`Spk.1Ln zg, Q]0=:!/LTs-eg.Fz, @giLyD'D=s, L\-AJyZ8tcV`kPifedMA@rhoEikoo~K%@iDLNq2?aHZjIt) GqBY7o#9+8j/uuXDVG3`XFEH_4$T%._*%;|vIaP Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 28 Sep 2007 02:09:29 +0000 Cc: freebsd-current@freebsd.org Subject: Re: Flash plugin status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 16:26:13 -0000 On Wed, 26 Sep 2007 21:24:07 -0700 Rudy wrote: > > About a month ago, Flash 7 was marked unsafe, and Flash 9 doesn't > work on many sites. > > [1] Anyone have any tricks to get Flash 9 working in 7.x? > [2] Any update on getting the freebsd foundation to take > on Flash (ala Java)? That would be horrible! Do you want the FreeBSD Foundation to work against our freedom and encourage the use of proprietary binary formats on the World Wide Web? Whenever I come to a Flash-only site I just move away thinking that the content is probably not worth wasting my time. You might want to consider gnash. While gnash cannot replace Flash as of today it is evolving quickly. Best regards, Jona -- "I am chaos. I am the substance from which your artists and scientists build rhythms. I am the spirit with which your children and clowns laugh in happy anarchy. I am chaos. I am alive, and tell you that you are free." Eris, Goddess Of Chaos, Discord & Confusion From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 22:12:12 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 21B3116A418; Thu, 27 Sep 2007 22:12:12 +0000 (UTC) (envelope-from jpedras@webvolution.net) Received: from mail.portrait.com (mail.portrait.com [64.171.32.41]) by mx1.freebsd.org (Postfix) with ESMTP id CAC3E13C461; Thu, 27 Sep 2007 22:12:11 +0000 (UTC) (envelope-from jpedras@webvolution.net) Received: from teko.tafkap.priv (beastie.webvolution.net [64.174.136.225]) (authenticated bits=0) by mail.portrait.com (8.13.1/8.13.1) with ESMTP id l8RMBwbX015819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Sep 2007 15:12:02 -0700 (PDT) (envelope-from jpedras@webvolution.net) Message-ID: <46FC2AA7.2040308@webvolution.net> Date: Thu, 27 Sep 2007 15:11:51 -0700 From: Joao Pedras User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Kris Kennaway References: <46FA0C14.10201@webvolution.net> <46FADB35.2090708@FreeBSD.org> In-Reply-To: <46FADB35.2090708@FreeBSD.org> X-Enigmail-Version: 0.95.3 OpenPGP: id=D7505EC0 Content-Type: multipart/mixed; boundary="------------010206050808020904080406" X-Spam-Status: No, score=0.1 required=3.0 tests=FORGED_RCVD_HELO X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on mail.portrait.com X-Mailman-Approved-At: Fri, 28 Sep 2007 02:09:29 +0000 Cc: freebsd-current@freebsd.org Subject: Re: lock up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 22:12:12 -0000 This is a multi-part message in MIME format. --------------010206050808020904080406 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi again, hope this info sheds some light on this. A similar system is getting setup to reproduce the problem there as well. Thanks! Joao Kris Kennaway wrote: > Joao Pedras wrote: >> Greetings all! >> >> A system (Tyan S2932) I am testing CURRENT amd64 with is experiencing a >> strange lock up. No panic, not much on the console, just a lock up, >> freeze. >> >> I first noticed the issue while tailing a build in a ssh session over a >> vpn connection. On the local network the issue doesn't seem to occur. >> I can reproduce the lock up all the time. >> >> Last I tried, the system was running CURRENT from a couple hours ago. >> >> I have tried: >> >> - 4BSD and ULE >> - switching network cards >> - taking the IPMI card out (seems to work locally with freeipmi and >> ipmitoll remotely) >> - enabled/disabled "redirection after post" (BIOS setting) >> - without debug >> - without IPv6 and friends (see rtfree below) >> >> dmesg and pciconf attached. The dmesg is after a lock up. >> rtfree pops a few times before the lock up. I noticed from a recent post >> some action was taken and the related patch is there (ie. today's >> CURRENT). >> >> The system had a fresh install this past weekend and the LSI MegaRAID >> array doesn't contain any data, it is just mounted. The system boots off >> the onboard LSI SAS (couple disks in RAID 1). >> >> Thank you for your input. > > Break to DDB and obtain process traces, etc. See the developers handbook. > > Kris > --------------010206050808020904080406 Content-Type: application/octet-stream; name="s2932-6.out" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="s2932-6.out" W3Jvb3RAZGFlbW9ucyB+XSMgcnRmcmVlOiAweGZmZmZmZjAwMDNiYmQ0YjAgaGFzIDEgcmVm cwpLREI6IGVudGVyOiBtYW51YWwgZXNjYXBlIHRvIGRlYnVnZ2VyClt0aHJlYWQgcGlkIDIw IHRpZCAxMDAwMjEgXQpTdG9wcGVkIGF0ICAgICAga2RiX2VudGVyKzB4MzE6IGxlYXZlCmRi PiBwcwogIHBpZCAgcHBpZCAgcGdycCAgIHVpZCAgIHN0YXRlICAgd21lc2cgICAgICAgICB3 Y2hhbiAgICAgICAgY21kCjI2NTI4IDI2NTI3IDE4NTA3ICAgICAwICBSVisgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICBtYWtlCjI2NTI3IDI2NTEzIDE4NTA3ICAgICAwICBT KyAgICAgIHBwd2FpdCAgIDB4ZmZmZmZmMDAwM2I0NDAwMCBtYWtlCjI2NTEzIDI2NTEyIDE4 NTA3ICAgICAwICBTKyAgICAgIHdhaXQgICAgIDB4ZmZmZmZmMDAwM2I0NDhjMCBzaAoyNjUx MiAyNDAzNyAxODUwNyAgICAgMCAgUisgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgbWFrZQoyNDAzNyAyNDAyOCAxODUwNyAgICAgMCAgUysgICAgICB3YWl0ICAgICAweGZm ZmZmZjAwMDNjNjIwMDAgc2gKMjQwMjggMjI5NTIgMTg1MDcgICAgIDAgIFMrICAgICAgc2Vs ZWN0ICAgMHhmZmZmZmZmZjgwYWE2ZDEwIG1ha2UKMjM3OTMgMjM3ODAgMTg1MDcgICAgIDAg IFIrICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHNoCjIzNzgwIDIzNzc0IDE4 NTA3ICAgICAwICBTKyAgICAgIHNlbGVjdCAgIDB4ZmZmZmZmZmY4MGFhNmQxMCBtYWtlCjIz Nzc0IDIyOTI3IDE4NTA3ICAgICAwICBTKyAgICAgIHdhaXQgICAgIDB4ZmZmZmZmMDAwZTAy NjAwMCBzaAoyMzYwNCAyMzUwNiAxODUwNyAgICAgMCAgUisgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgc2gKMjM1MjggMjM1MDYgMTg1MDcgICAgIDAgIFIrICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgIHNoCjIzNTA2IDIzNDY5IDE4NTA3ICAgICAwICBT KyAgICAgIHNlbGVjdCAgIDB4ZmZmZmZmZmY4MGFhNmQxMCBtYWtlCjIzNDY5IDIzNDU2IDE4 NTA3ICAgICAwICBTKyAgICAgIHdhaXQgICAgIDB4ZmZmZmZmMDAwM2IzMzQ2MCBzaAoyMzQ1 NiAyMzQ0OCAxODUwNyAgICAgMCAgUysgICAgICBzZWxlY3QgICAweGZmZmZmZmZmODBhYTZk MTAgbWFrZQoyMzQ0OCAyMjkyNyAxODUwNyAgICAgMCAgUysgICAgICB3YWl0ICAgICAweGZm ZmZmZjAwMDYyODA4YzAgc2gKMjI5NTIgMjI5NDYgMTg1MDcgICAgIDAgIFMrICAgICAgd2Fp dCAgICAgMHhmZmZmZmYwMDA2NWRjMDAwIHNoCjIyOTUwIDIyOTQxIDE4NTA3ICAgICAwICBS KyAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBzaAoyMjk0NiAyMjk0MiAxODUw NyAgICAgMCAgUysgICAgICBzZWxlY3QgICAweGZmZmZmZmZmODBhYTZkMTAgbWFrZQoyMjk0 MiAyMjkyNyAxODUwNyAgICAgMCAgUysgICAgICB3YWl0ICAgICAweGZmZmZmZjAwMDY1ZGQ4 YzAgc2gKLS1Nb3JlLS0gICAgICAgIDIyOTQxIDIyOTM1IDE4NTA3ICAgICAwICBTKyAgICAg IHNlbGVjdCAgIDB4ZmZmZmZmZmY4MGFhNmQxMCBtYWtlCjIyOTM1IDIyOTI3IDE4NTA3ICAg ICAwICBTKyAgICAgIHdhaXQgICAgIDB4ZmZmZmZmMDAwM2RkYzQ2MCBzaAoyMjkyNyAyMjky NiAxODUwNyAgICAgMCAgUisgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgbWFr ZQoyMjkyNiAyMjQ3NSAxODUwNyAgICAgMCAgUysgICAgICB3YWl0ICAgICAweGZmZmZmZjAw MDY4Nzc4YzAgc2gKMjI0NzUgMjI0NzMgMTg1MDcgICAgIDAgIFMrICAgICAgc2VsZWN0ICAg MHhmZmZmZmZmZjgwYWE2ZDEwIG1ha2UKMjI0NzMgMjIzODggMTg1MDcgICAgIDAgIFMrICAg ICAgd2FpdCAgICAgMHhmZmZmZmYwMDAzYWZjOGMwIHNoCjIyMzg4IDE4NTA3IDE4NTA3ICAg ICAwICBTKyAgICAgIHNlbGVjdCAgIDB4ZmZmZmZmZmY4MGFhNmQxMCBtYWtlCjE4NTA3ICAg OTYyIDE4NTA3ICAgICAwICBTKyAgICAgIHdhaXQgICAgIDB4ZmZmZmZmMDAwM2FiYzAwMCBz aAogIDk2MiAgIDk2MSAgIDk2MiAgICAgMCAgUysgICAgICB3YWl0ICAgICAweGZmZmZmZjAw MDNhZmMwMDAgYmFzaAogIDk2MSAgIDk1OSAgIDk2MSAgMTAwMSAgUysgICAgICB3YWl0ICAg ICAweGZmZmZmZjAwMDNhMWMwMDAgc3UKICA5NTkgICA5NTggICA5NTkgIDEwMDEgIFNzKyAg ICAgd2FpdCAgICAgMHhmZmZmZmYwMDAzYmEyMDAwIGJhc2gKICA5NTggICA5NTUgICA5NTUg IDEwMDEgIFIgICAgICAgQ1BVIDMgICAgICAgICAgICAgICAgICAgICAgIHNzaGQKICA5NTUg ICA3MDkgICA5NTUgICAgIDAgIFNzICAgICAgc2J3YWl0ICAgMHhmZmZmZmYwMDAzZTE1YzNj IHNzaGQKICA5MzAgICAgIDAgICAgIDAgICAgIDAgIFNMICAgICAgaXBtaXJlcSAgMHhmZmZm ZmYwMDAzYTVlMzQ4IFtpcG1pMDoga2NzXQogIDkwNSAgICAgMSAgIDkwNSAgICA2NSAgU3Mg ICAgICBzZWxlY3QgICAweGZmZmZmZmZmODBhYTZkMTAgZGhjbGllbnQKICA4ODUgICAgIDEg ICA4ODQgICAgIDAgIFMrICAgICAgc2VsZWN0ICAgMHhmZmZmZmZmZjgwYWE2ZDEwIGRoY2xp ZW50CiAgNzcxICAgNzY5ICAgNzcxICAgICAwICBTKyAgICAgIHR0eWluICAgIDB4ZmZmZmZm MDAwMzk0NTgxMCBiYXNoCiAgNzcwICAgICAxICAgNzcwICAgICAwICBTcysgICAgIHR0eWlu ICAgIDB4ZmZmZmZmMDAwMzkxMzgxMCBnZXR0eQogIDc2OSAgICAgMSAgIDc2OSAgICAgMCAg U3MrICAgICB3YWl0ICAgICAweGZmZmZmZjAwMDNjZjg0NjAgbG9naW4KICA3NjggICAgIDEg ICA3NjggICAgIDAgIFNzKyAgICAgdHR5aW4gICAgMHhmZmZmZmYwMDAzOTViNDEwIGdldHR5 Ci0tTW9yZS0tICAgICAgICAgIDc2NyAgICAgMSAgIDc2NyAgICAgMCAgU3MrICAgICB0dHlp biAgICAweGZmZmZmZjAwMDM5NTRjMTAgZ2V0dHkKICA3MjUgICAgIDEgICA3MjUgICAgIDAg IFNzICAgICAgbmFuc2xwICAgMHhmZmZmZmZmZjgwYTFlMTI4IGNyb24KICA3MTkgICAgIDEg ICA3MTkgICAgMjUgIFNzICAgICAgcGF1c2UgICAgMHhmZmZmZmYwMDAzYmI0MGMwIHNlbmRt YWlsCiAgNzE1ICAgICAxICAgNzE1ICAgICAwICBTcyAgICAgIHNlbGVjdCAgIDB4ZmZmZmZm ZmY4MGFhNmQxMCBzZW5kbWFpbAogIDcwOSAgICAgMSAgIDcwOSAgICAgMCAgU3MgICAgICBz ZWxlY3QgICAweGZmZmZmZmZmODBhYTZkMTAgc3NoZAogIDU5NCAgICAgMSAgIDU5NCAgICAg MCAgU3MgICAgICBzZWxlY3QgICAweGZmZmZmZmZmODBhYTZkMTAgc3lzbG9nZAogIDU0OCAg ICAgMSAgIDU0OCAgICAgMCAgU3MgICAgICBzZWxlY3QgICAweGZmZmZmZmZmODBhYTZkMTAg ZGV2ZAogIDE2NyAgICAgMSAgIDE2NyAgICAgMCAgU3MgICAgICBwYXVzZSAgICAweGZmZmZm ZjAwMDNiMzU1MjAgYWRqa2VybnR6CiAgIDU0ICAgICAwICAgICAwICAgICAwICBTTCAgICAg IC0gICAgICAgIDB4ZmZmZmZmZmY4MGExZGRhOCBbc2NoZWRjcHVdCiAgIDUzICAgICAwICAg ICAwICAgICAwICBTTCAgICAgIHNkZmx1c2ggIDB4ZmZmZmZmZmY4MGFiNmQyOCBbc29mdGRl cGZsdXNoXQogICA1MiAgICAgMCAgICAgMCAgICAgMCAgU0wgICAgICBzeW5jZXIgICAweGZm ZmZmZmZmODBhMWRkYTAgW3N5bmNlcl0KICAgNTEgICAgIDAgICAgIDAgICAgIDAgIFNMICAg ICAgdmxydXd0ICAgMHhmZmZmZmYwMDAzYTIxNDYwIFt2bmxydV0KICAgNTAgICAgIDAgICAg IDAgICAgIDAgIFNMICAgICAgcHNsZWVwICAgMHhmZmZmZmZmZjgwYWE3NTljIFtidWZkYWVt b25dCiAgIDQ5ICAgICAwICAgICAwICAgICAwICBTTCAgICAgIHBnemVybyAgIDB4ZmZmZmZm ZmY4MGFiODdhNCBbcGFnZXplcm9dCiAgIDQ4ICAgICAwICAgICAwICAgICAwICBTTCAgICAg IHBzbGVlcCAgIDB4ZmZmZmZmZmY4MGFiN2FlOCBbdm1kYWVtb25dCiAgIDQ3ICAgICAwICAg ICAwICAgICAwICBTTCAgICAgIHBzbGVlcCAgIDB4ZmZmZmZmZmY4MGFiN2FhYyBbcGFnZWRh ZW1vbl0KICAgNDYgICAgIDAgICAgIDAgICAgIDAgIFNMICAgICAgd2FpdGluZ18gMHhmZmZm ZmZmZjgwYWFhY2E4IFtzY3RwX2l0ZXJhdG9yXQogICA0NSAgICAgMCAgICAgMCAgICAgMCAg UkwgICAgICBDUFUgMCAgICAgICAgICAgICAgICAgICAgICAgW2lycTE6IGF0a2JkMF0KICAg NDQgICAgIDAgICAgIDAgICAgIDAgIFNMICAgICAgLSAgICAgICAgMHhmZmZmZmYwMDAzOTRm NDQ4IFtmZGMwXQogICA0MyAgICAgMCAgICAgMCAgICAgMCAgV0wgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgW3N3aTA6IHNpb10KLS1Nb3JlLS0gICAgICAgICAgIDQyICAg ICAwICAgICAwICAgICAwICBXTCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBb aXJxMTk6IGFtcjBdCiAgIDQxICAgICAwICAgICAwICAgICAwICBTTCAgICAgIGlkbGUgICAg IDB4ZmZmZmZmZmY4MGU1YTAwMCBbbXB0X3JlY292ZXJ5MF0KICAgNDAgICAgIDAgICAgIDAg ICAgIDAgIFdMICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFtpcnExODogbXB0 MF0KICAgMzkgICAgIDAgICAgIDAgICAgIDAgIFNMICAgICAgLSAgICAgICAgMHhmZmZmZmYw MDAzODgwZTAwIFtuZmUxIHRhc2txXQogICAzOCAgICAgMCAgICAgMCAgICAgMCAgU0wgICAg ICAtICAgICAgICAweGZmZmZmZjAwMDM2OTYwMDAgW25mZTAgdGFza3FdCiAgIDM3ICAgICAw ICAgICAwICAgICAwICBTTCAgICAgIGlkbGUgICAgIDB4ZmZmZmZmMDAwMzQzMGMwMCBbYWlj X3JlY292ZXJ5MF0KICAgMzYgICAgIDAgICAgIDAgICAgIDAgIFdMICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgIFtpcnExNjogYWhjMF0KICAgMzUgICAgIDAgICAgIDAgICAg IDAgIFNMICAgICAgaWRsZSAgICAgMHhmZmZmZmYwMDAzNDMwYzAwIFthaWNfcmVjb3Zlcnkw XQogICAzNCAgICAgMCAgICAgMCAgICAgMCAgV0wgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgW2lycTIwOiBhdGFwY2kyXQogICAzMyAgICAgMCAgICAgMCAgICAgMCAgV0wg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgW2lycTIzOiBhdGFwY2kxXQogICAz MiAgICAgMCAgICAgMCAgICAgMCAgV0wgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgW2lycTE1OiBhdGExXQogICAzMSAgICAgMCAgICAgMCAgICAgMCAgV0wgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgW2lycTE0OiBhdGEwXQogICAzMCAgICAgMCAgICAg MCAgICAgMCAgU0wgICAgICB1c2JldnQgICAweGZmZmZmZjAwMDEyZDg0MjAgW3VzYjFdCiAg IDI5ICAgICAwICAgICAwICAgICAwICBXTCAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICBbaXJxMjI6IGVoY2kwXQogICAyOCAgICAgMCAgICAgMCAgICAgMCAgU0wgICAgICB1 c2J0c2sgICAweGZmZmZmZmZmODBhMTk3NjggW3VzYnRhc2stZHJdCiAgIDI3ICAgICAwICAg ICAwICAgICAwICBTTCAgICAgIHVzYnRzayAgIDB4ZmZmZmZmZmY4MGExOTc0MCBbdXNidGFz ay1oY10KICAgMjYgICAgIDAgICAgIDAgICAgIDAgIFNMICAgICAgdXNiZXZ0ICAgMHhmZmZm ZmZmZjgwZTQyNDIwIFt1c2IwXQogICAyNSAgICAgMCAgICAgMCAgICAgMCAgV0wgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgW2lycTIxOiBvaGNpMCtdCiAgIDI0ICAgICAw ICAgICAwICAgICAwICBXTCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBbaXJx OTogYWNwaTBdCiAgIDIzICAgICAwICAgICAwICAgICAwICBXTCAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICBbc3dpMjogY2FtYmlvXQotLU1vcmUtLSAgICAgICAgICAgMjIg ICAgIDAgICAgIDAgICAgIDAgIFNMICAgICAgY2NiX3NjYW4gMHhmZmZmZmZmZjgwOWU4NGEw IFt4cHRfdGhyZF0KICAgIDkgICAgIDAgICAgIDAgICAgIDAgIFNMICAgICAgLSAgICAgICAg MHhmZmZmZmYwMDAxMjM4MDgwIFthY3BpX3Rhc2tfMl0KICAgIDggICAgIDAgICAgIDAgICAg IDAgIFNMICAgICAgLSAgICAgICAgMHhmZmZmZmYwMDAxMjM4MDgwIFthY3BpX3Rhc2tfMV0K ICAgIDcgICAgIDAgICAgIDAgICAgIDAgIFNMICAgICAgLSAgICAgICAgMHhmZmZmZmYwMDAx MjM4MDgwIFthY3BpX3Rhc2tfMF0KICAgIDYgICAgIDAgICAgIDAgICAgIDAgIFNMICAgICAg LSAgICAgICAgMHhmZmZmZmYwMDAxMjM4MTAwIFtrcXVldWUgdGFza3FdCiAgIDIxICAgICAw ICAgICAwICAgICAwICBXTCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBbc3dp NjogdGFzayBxdWV1ZV0KICAgMjAgICAgIDAgICAgIDAgICAgIDAgIFJMICAgICAgQ1BVIDEg ICAgICAgICAgICAgICAgICAgICAgIFtzd2k2OiBHaWFudCB0YXNrcV0KICAgIDUgICAgIDAg ICAgIDAgICAgIDAgIFNMICAgICAgLSAgICAgICAgMHhmZmZmZmYwMDAxMWYwNDgwIFt0aHJl YWQgdGFza3FdCiAgIDE5ICAgICAwICAgICAwICAgICAwICBSTCAgICAgIENQVSAyICAgICAg ICAgICAgICAgICAgICAgICBbc3dpNTogK10KICAgMTggICAgIDAgICAgIDAgICAgIDAgIFNM ICAgICAgLSAgICAgICAgMHhmZmZmZmZmZjgwYTFkZGE4IFt5YXJyb3ddCiAgICA0ICAgICAw ICAgICAwICAgICAwICBTTCAgICAgIC0gICAgICAgIDB4ZmZmZmZmZmY4MGExYTcxOCBbZ19k b3duXQogICAgMyAgICAgMCAgICAgMCAgICAgMCAgU0wgICAgICAtICAgICAgICAweGZmZmZm ZmZmODBhMWE3MTAgW2dfdXBdCiAgICAyICAgICAwICAgICAwICAgICAwICBTTCAgICAgIC0g ICAgICAgIDB4ZmZmZmZmZmY4MGExYTcwMCBbZ19ldmVudF0KICAgMTcgICAgIDAgICAgIDAg ICAgIDAgIFdMICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFtzd2kxOiBuZXRd CiAgIDE2ICAgICAwICAgICAwICAgICAwICBXTCAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICBbc3dpMzogdm1dCiAgIDE1ICAgICAwICAgICAwICAgICAwICBSTCAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICBbc3dpNDogY2xvY2sgc2lvXQogICAxNCAgICAg MCAgICAgMCAgICAgMCAgUkwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgW2lk bGU6IGNwdTBdCiAgIDEzICAgICAwICAgICAwICAgICAwICBSTCAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICBbaWRsZTogY3B1MV0KICAgMTIgICAgIDAgICAgIDAgICAgIDAg IFJMICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFtpZGxlOiBjcHUyXQogICAx MSAgICAgMCAgICAgMCAgICAgMCAgUkwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgW2lkbGU6IGNwdTNdCi0tTW9yZS0tICAgICAgICAgICAgMSAgICAgMCAgICAgMSAgICAg MCAgU0xzICAgICB3YWl0ICAgICAweGZmZmZmZjAwMDEwZTQ4YzAgW2luaXRdCiAgIDEwICAg ICAwICAgICAwICAgICAwICBTTCAgICAgIGF1ZGl0X3dvIDB4ZmZmZmZmZmY4MGFiNjIwMCBb YXVkaXRdCiAgICAwICAgICAwICAgICAwICAgICAwICBXTHMgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICBbc3dhcHBlcl0KMjQ0NzYgMjI5MjcgMTg1MDcgICAgIDAgIForICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHNoCjI0OTU5IDIyOTI3IDE4NTA3ICAg ICAwICBaKyAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBzaAoyNTEwNCAyMjky NyAxODUwNyAgICAgMCAgWisgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgc2gK ZGI+IHRyYWNlClRyYWNpbmcgcGlkIDIwIHRpZCAxMDAwMjEgdGQgMHhmZmZmZmYwMDAxMjM3 NjgwCmtkYl9lbnRlcigpIGF0IGtkYl9lbnRlcisweDMxCnNjZ2V0YygpIGF0IHNjZ2V0Yysw eDQ2MQpzY2tiZGV2ZW50KCkgYXQgc2NrYmRldmVudCsweGE0CmtiZG11eF9pbnRyKCkgYXQg a2JkbXV4X2ludHIrMHg0MwprYmRtdXhfa2JkX2ludHIoKSBhdCBrYmRtdXhfa2JkX2ludHIr MHgyMAp0YXNrcXVldWVfcnVuKCkgYXQgdGFza3F1ZXVlX3J1bisweDk0Cml0aHJlYWRfbG9v cCgpIGF0IGl0aHJlYWRfbG9vcCsweGUwCmZvcmtfZXhpdCgpIGF0IGZvcmtfZXhpdCsweDEy YQpmb3JrX3RyYW1wb2xpbmUoKSBhdCBmb3JrX3RyYW1wb2xpbmUrMHhlCi0tLSB0cmFwIDAs IHJpcCA9IDAsIHJzcCA9IDB4ZmZmZmZmZmZhYzJiY2QzMCwgcmJwID0gMCAtLS0KZGI+IHBh bmMIIAhpYwpwYW5pYzogZnJvbSBkZWJ1Z2dlcgpjcHVpZCA9IDEKS0RCOiBzdGFjayBiYWNr dHJhY2U6CmRiX3RyYWNlX3NlbGZfd3JhcHBlcigpIGF0IGRiX3RyYWNlX3NlbGZfd3JhcHBl cisweDJhCm1pX3N3aXRjaCgpIGF0IG1pX3N3aXRjaCsweDM5YwpzY2hlZF9iaW5kKCkgYXQg c2NoZWRfYmluZCsweDgzCmJvb3QoKSBhdCBib290KzB4M2YKcGFuaWMoKSBhdCBwYW5pYysw eDE2NwpkYl9wYW5pYygpIGF0IGRiX3BhbmljKzB4MTcKZGJfY29tbWFuZF9sb29wKCkgYXQg ZGJfY29tbWFuZF9sb29wKzB4MWRjCmRiX3RyYXAoKSBhdCBkYl90cmFwKzB4NmYKa2RiX3Ry YXAoKSBhdCBrZGJfdHJhcCsweDk1CnRyYXAoKSBhdCB0cmFwKzB4Mjk1CmNhbGx0cmFwKCkg YXQgY2FsbHRyYXArMHg4Ci0tLSB0cmFwIDB4MywgcmlwID0gMHhmZmZmZmZmZjgwNDlkZmYx LCByc3AgPSAweGZmZmZmZmZmYWMyYmNhOTAsIHJicCA9IDB4ZmZmZmZmZmZhYzJiY2FhMCAt LS0Ka2RiX2VudGVyKCkgYXQga2RiX2VudGVyKzB4MzEKc2NnZXRjKCkgYXQgc2NnZXRjKzB4 NDYxCnNja2JkZXZlbnQoKSBhdCBzY2tiZGV2ZW50KzB4YTQKa2JkbXV4X2ludHIoKSBhdCBr YmRtdXhfaW50cisweDQzCmtiZG11eF9rYmRfaW50cigpIGF0IGtiZG11eF9rYmRfaW50cisw eDIwCnRhc2txdWV1ZV9ydW4oKSBhdCB0YXNrcXVldWVfcnVuKzB4OTQKaXRocmVhZF9sb29w KCkgYXQgaXRocmVhZF9sb29wKzB4ZTAKZm9ya19leGl0KCkgYXQgZm9ya19leGl0KzB4MTJh CmZvcmtfdHJhbXBvbGluZSgpIGF0IGZvcmtfdHJhbXBvbGluZSsweGUKLS0tIHRyYXAgMCwg cmlwID0gMCwgcnNwID0gMHhmZmZmZmZmZmFjMmJjZDMwLCByYnAgPSAwIC0tLQpkYj4gY29u dGludWUKS0RCOiBlbnRlcjogbWFudWFsIGVzY2FwZSB0byBkZWJ1Z2dlcgpbdGhyZWFkIHBp ZCAyMCB0aWQgMTAwMDIxIF0KU3RvcHBlZCBhdCAgICAgIGtkYl9lbnRlcisweDMxOiBsZWF2 ZQo= --------------010206050808020904080406-- From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 04:18:03 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B2C0B16A418 for ; Fri, 28 Sep 2007 04:18:03 +0000 (UTC) (envelope-from e.schuele@computer.org) Received: from smtpout06.prod.mesa1.secureserver.net (smtpout06-04.prod.mesa1.secureserver.net [64.202.165.227]) by mx1.freebsd.org (Postfix) with SMTP id 7B7AE13C459 for ; Fri, 28 Sep 2007 04:18:03 +0000 (UTC) (envelope-from e.schuele@computer.org) Received: (qmail 25575 invoked from network); 28 Sep 2007 04:18:02 -0000 Received: from unknown (96.226.25.79) by smtpout06-04.prod.mesa1.secureserver.net (64.202.165.227) with ESMTP; 28 Sep 2007 04:18:02 -0000 Message-ID: <46FC8079.6030304@computer.org> Date: Thu, 27 Sep 2007 23:18:01 -0500 From: Eric Schuele User-Agent: Thunderbird 2.0.0.6 (X11/20070921) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.2 OpenPGP: url=http://www.ravenlock.us/files/pub_schuele.pgp Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigDF7A1FE691AEED326B6E52B9" Subject: Trouble with GDB and specific app on 7.0-CURRENT.... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 04:18:03 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDF7A1FE691AEED326B6E52B9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello, I have a particular app that I am unable to debug using gdb. When I attach to the app and continue it, gdb begins to take up 100% of my cpu. It will do this forever (well longer than I've ever waited). I am able to debug this particular app on my 6.2-STABLE machine. And I can debug other apps on my 7.0 machine. I've tried both gdb 6.1 and gdb 6.6 on my 7.0 machine with no change in behavior. I first thought maybe I had done something odd when rebuilding my kernel/world? But I've built a second 7.0 machine and stuck with the GENERIC kernel and I have the same results. Most times I can not break into the app once I have continued it. I have attached gdb to gdb to watch what it is doing and it appears to give me a few different backtraces, though it is always one of maybe three traces. [See below for bt of gdb attached to gdb, unfortunately its not the same bt I was seeing... but may offer some insight?] Has anyone seen behavior like this? What else can I provide that might help diagnose this? --=20 Regards, Eric Backtrace of gdb =3D=3D> gdb #0 0x2874cbbb in ptrace () from /lib/libc.so.7 #1 0x08068b42 in i386fbsd_resume (ptid=3D{pid =3D -1, lwp =3D 0, tid =3D= 0}, step=3D0, signal=3DTARGET_SIGNAL_CHLD) at i386fbsd-nat.c:76 #2 0x080ed0de in resume (step=3D0, sig=3DTARGET_SIGNAL_CHLD) at infrun.c= :626 #3 0x080f05ed in keep_going (ecs=3D0xbfbfe544) at infrun.c:2892 #4 0x080ef284 in handle_inferior_event (ecs=3D0xbfbfe544) at infrun.c:20= 21 #5 0x080ed63e in wait_for_inferior () at infrun.c:1009 #6 0x080ed46a in proceed (addr=3D4294967295, siggnal=3DTARGET_SIGNAL_DEF= AULT, step=3D0) at infrun.c:827 #7 0x080ea249 in continue_command (proc_count_exp=3D0x0, from_tty=3D1) at infcmd.c:642 #8 0x0808082b in do_cfunc (c=3D0x28977190, args=3D0x0, from_tty=3D1) at .././gdb/cli/cli-decode.c:62 #9 0x08082e6d in cmd_func (cmd=3D0x28977190, args=3D0x0, from_tty=3D1) at .././gdb/cli/cli-decode.c:1666 #10 0x08054cbd in execute_command (p=3D0x2890c081 "", from_tty=3D1) at to= p.c:455 #11 0x080feadf in command_handler (command=3D0x2890c080 "c") at event-top.c:519 #12 0x080ff307 in command_line_handler (rl=3D0x2895b112 "c") at event-top.c:804 #13 0x28319826 in rl_callback_read_char () from /lib/libreadline.so.7 #14 0x080fe1cf in rl_callback_read_char_wrapper (client_data=3D0x0) at event-top.c:179 --------------enigDF7A1FE691AEED326B6E52B9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFG/IB5ngSDRM3IXUoRAvsSAKDYYe94qXqXGLnpW/+3jY3Ml74h5QCgmJoi vK0+1eE8d9gJKLr5yM1aT2E= =lXiV -----END PGP SIGNATURE----- --------------enigDF7A1FE691AEED326B6E52B9-- From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 04:32:01 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 58B7316A469 for ; Fri, 28 Sep 2007 04:32:01 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 25FA913C4B8 for ; Fri, 28 Sep 2007 04:32:01 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.1/8.14.1) with ESMTP id l8S4TdLU034337; Thu, 27 Sep 2007 21:29:39 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.1/8.14.1/Submit) id l8S4Tdl4034336; Thu, 27 Sep 2007 21:29:39 -0700 (PDT) (envelope-from sgk) Date: Thu, 27 Sep 2007 21:29:39 -0700 From: Steve Kargl To: Eric Schuele Message-ID: <20070928042939.GA34316@troutmask.apl.washington.edu> References: <46FC8079.6030304@computer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46FC8079.6030304@computer.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: Trouble with GDB and specific app on 7.0-CURRENT.... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 04:32:01 -0000 On Thu, Sep 27, 2007 at 11:18:01PM -0500, Eric Schuele wrote: > > Has anyone seen behavior like this? What else can I provide that might > help diagnose this? > Are you by any chance using tcsh as your shell? -- Steve From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 04:58:38 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4648B16A419 for ; Fri, 28 Sep 2007 04:58:38 +0000 (UTC) (envelope-from e.schuele@computer.org) Received: from smtpauth02.prod.mesa1.secureserver.net (smtpauth02.prod.mesa1.secureserver.net [64.202.165.182]) by mx1.freebsd.org (Postfix) with SMTP id E99B113C494 for ; Fri, 28 Sep 2007 04:58:37 +0000 (UTC) (envelope-from e.schuele@computer.org) Received: (qmail 3976 invoked from network); 28 Sep 2007 04:58:36 -0000 Received: from unknown (96.226.25.79) by smtpauth02.prod.mesa1.secureserver.net (64.202.165.182) with ESMTP; 28 Sep 2007 04:58:36 -0000 Message-ID: <46FC89FB.2070506@computer.org> Date: Thu, 27 Sep 2007 23:58:35 -0500 From: Eric Schuele User-Agent: Thunderbird 2.0.0.6 (X11/20070921) MIME-Version: 1.0 To: Steve Kargl , freebsd-current@freebsd.org References: <46FC8079.6030304@computer.org> <20070928042939.GA34316@troutmask.apl.washington.edu> In-Reply-To: <20070928042939.GA34316@troutmask.apl.washington.edu> X-Enigmail-Version: 0.95.2 OpenPGP: url=http://www.ravenlock.us/files/pub_schuele.pgp Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig03A4BA40699D089F31752C2D" Cc: Subject: Re: Trouble with GDB and specific app on 7.0-CURRENT.... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 04:58:38 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig03A4BA40699D089F31752C2D Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 09/27/2007 23:29, Steve Kargl wrote: > On Thu, Sep 27, 2007 at 11:18:01PM -0500, Eric Schuele wrote: >> Has anyone seen behavior like this? What else can I provide that migh= t >> help diagnose this? >> >=20 > Are you by any chance using tcsh as your shell? >=20 heh... Yes, as a matter of fact. How is that affecting me? I've always used tcsh and not had these troubles. --=20 Regards, Eric --------------enig03A4BA40699D089F31752C2D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFG/In8ngSDRM3IXUoRAmC5AJ9xGrBkcHpVSyyLDsHXCtss1kY4yACg1X4h HqPztevhxZqvut5DNLoR1wM= =gZDQ -----END PGP SIGNATURE----- --------------enig03A4BA40699D089F31752C2D-- From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 05:15:11 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84E1216A420 for ; Fri, 28 Sep 2007 05:15:11 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 612CF13C469 for ; Fri, 28 Sep 2007 05:15:11 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.1/8.14.1) with ESMTP id l8S5CqfC034653; Thu, 27 Sep 2007 22:12:52 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.1/8.14.1/Submit) id l8S5Cq0l034652; Thu, 27 Sep 2007 22:12:52 -0700 (PDT) (envelope-from sgk) Date: Thu, 27 Sep 2007 22:12:52 -0700 From: Steve Kargl To: Eric Schuele Message-ID: <20070928051252.GA34607@troutmask.apl.washington.edu> References: <46FC8079.6030304@computer.org> <20070928042939.GA34316@troutmask.apl.washington.edu> <46FC89FB.2070506@computer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46FC89FB.2070506@computer.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: Trouble with GDB and specific app on 7.0-CURRENT.... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 05:15:11 -0000 On Thu, Sep 27, 2007 at 11:58:35PM -0500, Eric Schuele wrote: > On 09/27/2007 23:29, Steve Kargl wrote: > > On Thu, Sep 27, 2007 at 11:18:01PM -0500, Eric Schuele wrote: > >> Has anyone seen behavior like this? What else can I provide that might > >> help diagnose this? > >> > > > > Are you by any chance using tcsh as your shell? > > > > heh... Yes, as a matter of fact. How is that affecting me? I've always > used tcsh and not had these troubles. > Signal handling in tcsh is broken, and one manifestation of the problem is the behavior you're seeing with gdb. I've repeatedly asked to have the 6.15.0 version of tcsh backed out of src/ to the previously working 6.14.0 version, but no one who can affect such a change seems to think a default user shell with broken signal handling is a problem. The only workaround that I've found is "setenv SHELL sh" prior to executing gdb. -- Steve From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 05:28:15 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32A5E16A417 for ; Fri, 28 Sep 2007 05:28:15 +0000 (UTC) (envelope-from e.schuele@computer.org) Received: from smtpout06.prod.mesa1.secureserver.net (smtpout06-04.prod.mesa1.secureserver.net [64.202.165.227]) by mx1.freebsd.org (Postfix) with SMTP id ED31913C45A for ; Fri, 28 Sep 2007 05:28:14 +0000 (UTC) (envelope-from e.schuele@computer.org) Received: (qmail 1381 invoked from network); 28 Sep 2007 05:28:14 -0000 Received: from unknown (96.226.25.79) by smtpout06-04.prod.mesa1.secureserver.net (64.202.165.227) with ESMTP; 28 Sep 2007 05:28:13 -0000 Message-ID: <46FC90EC.4060808@computer.org> Date: Fri, 28 Sep 2007 00:28:12 -0500 From: Eric Schuele User-Agent: Thunderbird 2.0.0.6 (X11/20070921) MIME-Version: 1.0 To: Steve Kargl , freebsd-current@freebsd.org References: <46FC8079.6030304@computer.org> <20070928042939.GA34316@troutmask.apl.washington.edu> <46FC89FB.2070506@computer.org> <20070928051252.GA34607@troutmask.apl.washington.edu> In-Reply-To: <20070928051252.GA34607@troutmask.apl.washington.edu> X-Enigmail-Version: 0.95.2 OpenPGP: url=http://www.ravenlock.us/files/pub_schuele.pgp Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig49ACB790D587ADCB10CD82A3" Cc: Subject: Re: Trouble with GDB and specific app on 7.0-CURRENT.... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 05:28:15 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig49ACB790D587ADCB10CD82A3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 09/28/2007 00:12, Steve Kargl wrote: > On Thu, Sep 27, 2007 at 11:58:35PM -0500, Eric Schuele wrote: >> On 09/27/2007 23:29, Steve Kargl wrote: >>> On Thu, Sep 27, 2007 at 11:18:01PM -0500, Eric Schuele wrote: >>>> Has anyone seen behavior like this? What else can I provide that mi= ght >>>> help diagnose this? >>>> >>> Are you by any chance using tcsh as your shell? >>> >> heh... Yes, as a matter of fact. How is that affecting me? I've alwa= ys >> used tcsh and not had these troubles. >> >=20 > Signal handling in tcsh is broken, and one manifestation of > the problem is the behavior you're seeing with gdb. I've=20 > repeatedly asked to have the 6.15.0 version of tcsh backed > out of src/ to the previously working 6.14.0 version, but no > one who can affect such a change seems to think a default user > shell with broken signal handling is a problem. The only > workaround that I've found is "setenv SHELL sh" prior to > executing gdb. Hmm... yeah.. I found the bug report after you mentioned tcsh. However changing that var has no effect for me. In fact using sh as my shell makes no difference either. Maybe I should rollback my tcsh and see what happens? --=20 Regards, Eric --------------enig49ACB790D587ADCB10CD82A3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFG/JDtngSDRM3IXUoRArxMAJ0S5R4HIY8inIENPAIZNtrg9/nPxACfbdF0 g5+NCIsSJlyoCfGJwhGbQ7M= =lIlB -----END PGP SIGNATURE----- --------------enig49ACB790D587ADCB10CD82A3-- From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 05:34:21 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A075916A418; Fri, 28 Sep 2007 05:34:21 +0000 (UTC) (envelope-from jpedras+freebsd-current@webvolution.net) Received: from mail.portrait.com (mail.portrait.com [64.171.32.41]) by mx1.freebsd.org (Postfix) with ESMTP id 6C76F13C455; Fri, 28 Sep 2007 05:34:21 +0000 (UTC) (envelope-from jpedras+freebsd-current@webvolution.net) Received: from teko.tafkap.priv (beastie.webvolution.net [64.174.136.225]) (authenticated bits=0) by mail.portrait.com (8.13.1/8.13.1) with ESMTP id l8S5JiIx021881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Sep 2007 22:19:48 -0700 (PDT) (envelope-from jpedras+freebsd-current@webvolution.net) Message-ID: <46FC8EEE.5080908@webvolution.net> Date: Thu, 27 Sep 2007 22:19:42 -0700 From: Joao Pedras User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Kris Kennaway References: <46FA0C14.10201@webvolution.net> <46FADB35.2090708@FreeBSD.org> <46FC2AA7.2040308@webvolution.net> <46FC2C85.4080600@FreeBSD.org> In-Reply-To: <46FC2C85.4080600@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.1 required=3.0 tests=FORGED_RCVD_HELO X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on mail.portrait.com Cc: freebsd-current@freebsd.org Subject: Re: lock up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 05:34:21 -0000 Kris Kennaway wrote: > Joao Pedras wrote: >> Hi again, >> >> hope this info sheds some light on this. A similar system is getting >> setup to reproduce the problem there as well. >> >> Thanks! >> >> Joao >> >> Kris Kennaway wrote: >>> Joao Pedras wrote: >>>> Greetings all! >>>> >>>> A system (Tyan S2932) I am testing CURRENT amd64 with is experiencing a >>>> strange lock up. No panic, not much on the console, just a lock up, >>>> freeze. >>>> >>>> I first noticed the issue while tailing a build in a ssh session over a >>>> vpn connection. On the local network the issue doesn't seem to occur. >>>> I can reproduce the lock up all the time. >>>> >>>> Last I tried, the system was running CURRENT from a couple hours ago. >>>> >>>> I have tried: >>>> >>>> - 4BSD and ULE >>>> - switching network cards >>>> - taking the IPMI card out (seems to work locally with freeipmi and >>>> ipmitoll remotely) >>>> - enabled/disabled "redirection after post" (BIOS setting) >>>> - without debug >>>> - without IPv6 and friends (see rtfree below) >>>> >>>> dmesg and pciconf attached. The dmesg is after a lock up. >>>> rtfree pops a few times before the lock up. I noticed from a recent >>>> post >>>> some action was taken and the related patch is there (ie. today's >>>> CURRENT). >>>> >>>> The system had a fresh install this past weekend and the LSI MegaRAID >>>> array doesn't contain any data, it is just mounted. The system boots >>>> off >>>> the onboard LSI SAS (couple disks in RAID 1). >>>> >>>> Thank you for your input. >>> Break to DDB and obtain process traces, etc. See the developers >>> handbook. >>> >>> Kris >>> > > Well that's a start, but you need to trace other processes too, e.g. the > running ones. Do an 'alltrace' to trace everything. > > Kris > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Thank you for your help Kris. I am not very familiar with these tasks. I got the 'alltrace' and I also saved a crash dump. The session output is here http://pedras.webvolution.net/s2932-9.txt. I was able to reproduce the issue on a similar system (a vanilla Tyan S2932, one SATA disc only) and it exhibits the exact same problem. Thanks again. Joao From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 07:21:37 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 33FF516A420 for ; Fri, 28 Sep 2007 07:21:37 +0000 (UTC) (envelope-from h.schmalzbauer@omnisec.de) Received: from host.omnisec.de (host.omnisec.de [62.245.232.135]) by mx1.freebsd.org (Postfix) with ESMTP id A5CBF13C48E for ; Fri, 28 Sep 2007 07:21:36 +0000 (UTC) (envelope-from h.schmalzbauer@omnisec.de) Received: from tek.flintsbach.schmalzbauer.de (tek.flintsbach.schmalzbauer.de [172.21.2.3]) by host.omnisec.de (8.13.8/8.13.8) with ESMTP id l8S7LT7T027522 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 28 Sep 2007 09:21:35 +0200 (CEST) (envelope-from h.schmalzbauer@omnisec.de) Received: from titan.flintsbach.schmalzbauer.de (titan.flintsbach.schmalzbauer.de [IPv6:fec0::1:0:0:1:1]) by tek.flintsbach.schmalzbauer.de (8.13.8/8.13.8) with ESMTP id l8S7LTLa076086 for ; Fri, 28 Sep 2007 09:21:29 +0200 (CEST) (envelope-from h.schmalzbauer@omnisec.de) Received: from localhost (localhost [[UNIX: localhost]]) by titan.flintsbach.schmalzbauer.de (8.14.1/8.14.1/Submit) id l8S7N2nA001373 for freebsd-current@freebsd.org; Fri, 28 Sep 2007 09:23:02 +0200 (CEST) (envelope-from h.schmalzbauer@omnisec.de) X-Authentication-Warning: titan.flintsbach.schmalzbauer.de: harry set sender to h.schmalzbauer@omnisec.de using -f From: Harald Schmalzbauer Organization: OmniSEC To: freebsd-current@freebsd.org Date: Fri, 28 Sep 2007 09:23:01 +0200 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2934628.ZGsl1gBB6N"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200709280923.02006.h.schmalzbauer@omnisec.de> Subject: gjournal blocking hd writes (gpt) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 07:21:37 -0000 --nextPart2934628.ZGsl1gBB6N Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, when I try to alter the GPT on a drive which contains gjournal journal it=20 fails even if kern.geom.debugflags=3D16. I have to stop all journals before I can write to that drive. Afterwards gjournal starts up again automatically in contrast to gmirror fo= r=20 example. I thought gpt uses geom to write to the drive these days in -current, so=20 kern.geom.debugflags shouldn't be needed anymore. Is that correct? Why the problem with gjournal? Thanks =2DHarry --nextPart2934628.ZGsl1gBB6N Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBG/KvVLDqVQ9VXb8gRAoxPAJ9ZU0lUkjREqIrpADMBWZDUdY3UhwCgkNQg Rf1UOTsMDAbFlpH08PO1CXE= =KHZk -----END PGP SIGNATURE----- --nextPart2934628.ZGsl1gBB6N-- From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 08:03:17 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 901C916A420 for ; Fri, 28 Sep 2007 08:03:17 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.freebsd.org (Postfix) with ESMTP id 2B32513C44B for ; Fri, 28 Sep 2007 08:03:16 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so2144990nfb for ; Fri, 28 Sep 2007 01:03:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=0Y9m4WuJessolPPSqWFC93B0SfkLGvN+Ym0+5ttZYNk=; b=s9X9qZgWVDao0vvnqnDT/0ncWGa9MLrY4Ivdy3LhDQ/7TmtfojjMRyziG4pmcyA0mVk1ucdU19lYAHRNuzfvngNDRBhV/eKj0eh0KA/UTVp8u76qa4O2mJkQk/SmKnuDCFiNUagZOSjC3Oz4QtqpIwlHiR6kUHyRrYO/jngvszY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=d1QghoUYpj1bD3NTonPBhIi6LZdG3V4tkGjudrGHRLknZz6tiaWTRtHro0hTgsToag9VrqzfKzXyrXRg7vEhRqI+cQ0YmRhRXbFCkqr0m0V7WH4krGgdxMDX5W4bq9nechvlYLyHGeVhCnqpEdEooTyTMO202/VaiVgEK0ODNGk= Received: by 10.78.176.20 with SMTP id y20mr2736408hue.1190966595479; Fri, 28 Sep 2007 01:03:15 -0700 (PDT) Received: by 10.78.166.18 with HTTP; Fri, 28 Sep 2007 01:03:15 -0700 (PDT) Message-ID: Date: Fri, 28 Sep 2007 10:03:15 +0200 From: "Claus Guttesen" To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: 8-core server X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 08:03:17 -0000 Hi. Upgraded our 4-core to an 8-core. Part of dmesg: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 But then it says: SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #7 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #6 Launched! Are some of the cores disabled or did they just take a walk? :-) This is on current from Mon Sep 24 2007. -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 08:11:49 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7172D16A41A for ; Fri, 28 Sep 2007 08:11:49 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 662D013C447 for ; Fri, 28 Sep 2007 08:11:49 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 412A11CC02B; Fri, 28 Sep 2007 01:11:49 -0700 (PDT) Date: Fri, 28 Sep 2007 01:11:49 -0700 From: Jeremy Chadwick To: Claus Guttesen Message-ID: <20070928081149.GA16874@eos.sc1.parodius.com> Mail-Followup-To: Claus Guttesen , freebsd-current@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org Subject: Re: 8-core server X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 08:11:49 -0000 On Fri, Sep 28, 2007 at 10:03:15AM +0200, Claus Guttesen wrote: > Upgraded our 4-core to an 8-core. > > Part of dmesg: > > FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > cpu4 (AP): APIC ID: 4 > cpu5 (AP): APIC ID: 5 > cpu6 (AP): APIC ID: 6 > cpu7 (AP): APIC ID: 7 > > But then it says: > > SMP: AP CPU #1 Launched! > SMP: AP CPU #2 Launched! > SMP: AP CPU #3 Launched! > SMP: AP CPU #4 Launched! > SMP: AP CPU #7 Launched! > SMP: AP CPU #5 Launched! > SMP: AP CPU #6 Launched! > > Are some of the cores disabled or did they just take a walk? :-) This > is on current from Mon Sep 24 2007. So what's the problem? I see 7 additional processors launched ("SMP: AP CPU #[1-7] Launched!"), while CPU #0 is the base processor, so it never shows that message. That makes 8. Example from my dual-core system at home: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 SMP: AP CPU #1 Launched! -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 08:13:43 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F07C316A46E for ; Fri, 28 Sep 2007 08:13:43 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 9A49F13C49D; Fri, 28 Sep 2007 08:13:42 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46FCB7B7.9010301@FreeBSD.org> Date: Fri, 28 Sep 2007 10:13:43 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Claus Guttesen References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: 8-core server X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 08:13:44 -0000 Claus Guttesen wrote: > Hi. > > Upgraded our 4-core to an 8-core. > > Part of dmesg: > > FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > cpu4 (AP): APIC ID: 4 > cpu5 (AP): APIC ID: 5 > cpu6 (AP): APIC ID: 6 > cpu7 (AP): APIC ID: 7 > > But then it says: > > SMP: AP CPU #1 Launched! > SMP: AP CPU #2 Launched! > SMP: AP CPU #3 Launched! > SMP: AP CPU #4 Launched! > SMP: AP CPU #7 Launched! > SMP: AP CPU #5 Launched! > SMP: AP CPU #6 Launched! > > Are some of the cores disabled or did they just take a walk? :-) This > is on current from Mon Sep 24 2007. > I see the extra 7 cores being launched correctly, what is the problem? Kris From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 08:15:36 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F20916A417 for ; Fri, 28 Sep 2007 08:15:36 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 3002E13C4A7 for ; Fri, 28 Sep 2007 08:15:36 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 528DB20D8; Fri, 28 Sep 2007 10:15:31 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 45C2D20D7; Fri, 28 Sep 2007 10:15:31 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id 2F9D4844A1; Fri, 28 Sep 2007 10:15:31 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Jona Joachim References: <46FB3067.8040706@MonkeyBrains.NET> <20070927180914.735bd431@hcl-club.lu> Date: Fri, 28 Sep 2007 10:15:31 +0200 In-Reply-To: <20070927180914.735bd431@hcl-club.lu> (Jona Joachim's message of "Thu\, 27 Sep 2007 18\:09\:14 +0200") Message-ID: <86ps039pek.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, Rudy Subject: Re: Flash plugin status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 08:15:36 -0000 Jona Joachim writes: > Rudy wrote: > > [2] Any update on getting the freebsd foundation to take > > on Flash (ala Java)? > That would be horrible! > Do you want the FreeBSD Foundation to work against our freedom and > encourage the use of proprietary binary formats on the World Wide Web? I think you're confusing the FreeBSD Foundation with the Free Software Foundation. The FreeBSD Foundation does not have a political agenda. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 08:16:55 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 337DF16A420 for ; Fri, 28 Sep 2007 08:16:55 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id EBD9813C48A for ; Fri, 28 Sep 2007 08:16:54 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 9BABE20A0; Fri, 28 Sep 2007 10:16:51 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 1E0B82099; Fri, 28 Sep 2007 10:16:51 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id 09F59844A1; Fri, 28 Sep 2007 10:16:51 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "Claus Guttesen" References: Date: Fri, 28 Sep 2007 10:16:50 +0200 In-Reply-To: (Claus Guttesen's message of "Fri\, 28 Sep 2007 10\:03\:15 +0200") Message-ID: <86lkar9pcd.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: 8-core server X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 08:16:55 -0000 "Claus Guttesen" writes: > Upgraded our 4-core to an 8-core. > > Part of dmesg: > > FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > cpu4 (AP): APIC ID: 4 > cpu5 (AP): APIC ID: 5 > cpu6 (AP): APIC ID: 6 > cpu7 (AP): APIC ID: 7 > > But then it says: > > SMP: AP CPU #1 Launched! > SMP: AP CPU #2 Launched! > SMP: AP CPU #3 Launched! > SMP: AP CPU #4 Launched! > SMP: AP CPU #7 Launched! > SMP: AP CPU #5 Launched! > SMP: AP CPU #6 Launched! > > Are some of the cores disabled or did they just take a walk? :-) This > is on current from Mon Sep 24 2007. All cores were detected and started. What is the problem? DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 08:21:09 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C191E16A41A for ; Fri, 28 Sep 2007 08:21:09 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185]) by mx1.freebsd.org (Postfix) with ESMTP id 5954F13C46A for ; Fri, 28 Sep 2007 08:21:09 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so2148485nfb for ; Fri, 28 Sep 2007 01:21:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=xoyrstOkSF9+ugYd6rXNZWBOuvnrpwt08taVsxERCUc=; b=SpFGnGAbDBsHbWpHyih1xiyZC8gyhSb140osxHorOZsRrN8mixjuJkK/tgn3ZYX82GTl7CFu+mYi1/gN1u9xMBsobrWTlqYiRkxwZNWcHpGOERlxkimW+pSAph1fUXH+rL4Y44rNT9TDRGpYw2850xfJjltGIjv5c6kriHlvtUo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=s2Ofh7Uz2otxWeZ6nZDAxmYZblVwQx/MF5HbgLDkrrPyxpWnyIUTQGBZKbfd4Bll68jpixIlR5ZKeQE3wtrgIvTJFqwd3G3Ar4QPiYerDzalDPrzcghVRjBqHm8tTjARLzfauP8KVfxxngx+UrzNO5H4yJWeBzpJWydK0j0U7Xg= Received: by 10.78.186.9 with SMTP id j9mr2732063huf.1190967667388; Fri, 28 Sep 2007 01:21:07 -0700 (PDT) Received: by 10.78.166.18 with HTTP; Fri, 28 Sep 2007 01:21:07 -0700 (PDT) Message-ID: Date: Fri, 28 Sep 2007 10:21:07 +0200 From: "Claus Guttesen" To: "Kris Kennaway" In-Reply-To: <46FCB7B7.9010301@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46FCB7B7.9010301@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: 8-core server X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 08:21:09 -0000 > > Part of dmesg: > > > > FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs > > cpu0 (BSP): APIC ID: 0 > > cpu1 (AP): APIC ID: 1 > > cpu2 (AP): APIC ID: 2 > > cpu3 (AP): APIC ID: 3 > > cpu4 (AP): APIC ID: 4 > > cpu5 (AP): APIC ID: 5 > > cpu6 (AP): APIC ID: 6 > > cpu7 (AP): APIC ID: 7 > > > > But then it says: > > > > SMP: AP CPU #1 Launched! > > SMP: AP CPU #2 Launched! > > SMP: AP CPU #3 Launched! > > SMP: AP CPU #4 Launched! > > SMP: AP CPU #7 Launched! > > SMP: AP CPU #5 Launched! > > SMP: AP CPU #6 Launched! Isn't there supposed to be a last line saying 'SMP: AP CPU #7 Launched!'? > > I see the extra 7 cores being launched correctly, what is the problem? > > Kris > > -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 08:23:27 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29B6A16A418 for ; Fri, 28 Sep 2007 08:23:27 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.freebsd.org (Postfix) with ESMTP id B2D8513C467 for ; Fri, 28 Sep 2007 08:23:26 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so2148927nfb for ; Fri, 28 Sep 2007 01:23:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Xk4sncflB0Vs4OUggi5koGXCBU6ZNEqeQDBu3ITYx+I=; b=eTWIhchHIlRwiRA9mTefjhG/AbN7e2V8ryIvzTviSPlzJQqnj/T6lfrWLxnsxn7LgUR//TWfpCIF5xLnV4elPSDU3NYijVEu2UBHEkSZ0pqOufVwSUHwSvNMVhyQmsIVCc4GmwbM+C1FBRWcBY3IrE/VOyUt+F+y4ivJO0fgJD8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pnV2QbCdi9UW7uWPkaoT+9T+pg0eNEqBfU/mcUzFLd/hgSL98axDIVHMVguOH03BNbU7nG/gJg1xdhYU38v5HpaPVDqFsiBvjONynTy3G+HZ/71klljbNf/OI8HAUmLYd9/7ZBStyNWD7YeUJLNG2jWLeDWoQf9sYQtagawEq+4= Received: by 10.78.134.2 with SMTP id h2mr2751464hud.1190967804577; Fri, 28 Sep 2007 01:23:24 -0700 (PDT) Received: by 10.78.166.18 with HTTP; Fri, 28 Sep 2007 01:23:24 -0700 (PDT) Message-ID: Date: Fri, 28 Sep 2007 10:23:24 +0200 From: "Claus Guttesen" To: "Claus Guttesen" , freebsd-current@freebsd.org In-Reply-To: <20070928081149.GA16874@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070928081149.GA16874@eos.sc1.parodius.com> Cc: Subject: Re: 8-core server X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 08:23:27 -0000 > > SMP: AP CPU #1 Launched! > > SMP: AP CPU #2 Launched! > > SMP: AP CPU #3 Launched! > > SMP: AP CPU #4 Launched! > > SMP: AP CPU #7 Launched! > > SMP: AP CPU #5 Launched! > > SMP: AP CPU #6 Launched! > > > > Are some of the cores disabled or did they just take a walk? :-) This > > is on current from Mon Sep 24 2007. > > So what's the problem? I see 7 additional processors launched ("SMP: AP > CPU #[1-7] Launched!"), while CPU #0 is the base processor, so it never > shows that message. That makes 8. Pardon, my bad. Cpu #7 was launched prior to 5 and 6. -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 08:33:22 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F96D16A469; Fri, 28 Sep 2007 08:33:22 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 589DE13C4A8; Fri, 28 Sep 2007 08:33:22 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 3FEB21CC02B; Fri, 28 Sep 2007 01:33:22 -0700 (PDT) Date: Fri, 28 Sep 2007 01:33:22 -0700 From: Jeremy Chadwick To: Claus Guttesen Message-ID: <20070928083322.GA17225@eos.sc1.parodius.com> Mail-Followup-To: Claus Guttesen , Kris Kennaway , freebsd-current@freebsd.org References: <46FCB7B7.9010301@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org Subject: Re: 8-core server X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 08:33:22 -0000 On Fri, Sep 28, 2007 at 10:21:07AM +0200, Claus Guttesen wrote: > > > Part of dmesg: > > > > > > FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs > > > cpu0 (BSP): APIC ID: 0 > > > cpu1 (AP): APIC ID: 1 > > > cpu2 (AP): APIC ID: 2 > > > cpu3 (AP): APIC ID: 3 > > > cpu4 (AP): APIC ID: 4 > > > cpu5 (AP): APIC ID: 5 > > > cpu6 (AP): APIC ID: 6 > > > cpu7 (AP): APIC ID: 7 > > > > > > But then it says: > > > > > > SMP: AP CPU #1 Launched! > > > SMP: AP CPU #2 Launched! > > > SMP: AP CPU #3 Launched! > > > SMP: AP CPU #4 Launched! > > > SMP: AP CPU #7 Launched! > > > SMP: AP CPU #5 Launched! > > > SMP: AP CPU #6 Launched! > > Isn't there supposed to be a last line saying 'SMP: AP CPU #7 Launched!'? It's right here: > > > SMP: AP CPU #7 Launched! I think what you're not noticing is that the cores are being launched in non-sequential order. 1, 2, 3, 4, 7, 5, 6. This isn't a problem. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 10:10:16 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F49116A418 for ; Fri, 28 Sep 2007 10:10:16 +0000 (UTC) (envelope-from jaj@hcl-club.lu) Received: from 0b10111.de (hcl-club.lu [62.75.155.129]) by mx1.freebsd.org (Postfix) with ESMTP id 2744D13C4A7 for ; Fri, 28 Sep 2007 10:10:15 +0000 (UTC) (envelope-from jaj@hcl-club.lu) Received: from localhost (4be54-4-82-234-154-189.fbx.proxad.net [82.234.154.189]) by 0b10111.de (Postfix) with ESMTP id EBD10872C460; Fri, 28 Sep 2007 12:10:14 +0200 (CEST) Date: Fri, 28 Sep 2007 12:10:10 +0200 From: Jona Joachim To: Dag-Erling =?UTF-8?B?U23DuHJncmF2?= Message-ID: <20070928121010.47ec5bcb@hcl-club.lu> In-Reply-To: <86ps039pek.fsf@ds4.des.no> References: <46FB3067.8040706@MonkeyBrains.NET> <20070927180914.735bd431@hcl-club.lu> <86ps039pek.fsf@ds4.des.no> X-Mailer: Claws Mail 3.0.1 (GTK+ 2.10.14; i386-portbld-freebsd6.2) X-Face: &>dujC`JZV!}?Y^1"%N{x!f+rW}; PX\_Cg[!|MA~tn3ebIKM|~p=,,U~YJt,Exd`Spk.1Ln zg, Q]0=:!/LTs-eg.Fz, @giLyD'D=s, L\-AJyZ8tcV`kPifedMA@rhoEikoo~K%@iDLNq2?aHZjIt) GqBY7o#9+8j/uuXDVG3`XFEH_4$T%._*%;|vIaP Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Fri, 28 Sep 2007 11:07:24 +0000 Cc: freebsd-current@freebsd.org, Rudy Subject: Re: Flash plugin status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 10:10:16 -0000 On Fri, 28 Sep 2007 10:15:31 +0200 Dag-Erling Sm=C3=B8rgrav wrote: > Jona Joachim writes: > > Rudy wrote: > > > [2] Any update on getting the freebsd foundation to take > > > on Flash (ala Java)? > > That would be horrible! > > Do you want the FreeBSD Foundation to work against our freedom and > > encourage the use of proprietary binary formats on the World Wide > > Web? >=20 > I think you're confusing the FreeBSD Foundation with the Free Software > Foundation. The FreeBSD Foundation does not have a political agenda. The FreeBSD Foundation supports and represents the FreeBSD Project. Are you saying that the FreeBSD Project, along with the FreeBSD Foundation don't care about free software? Regards, Jona --=20 "I am chaos. I am the substance from which your artists and scientists build rhythms. I am the spirit with which your children and clowns laugh in happy anarchy. I am chaos. I am alive, and tell you that you are free." Eris, Goddess Of Chaos, Discord & Confusion From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 12:22:29 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0EB9516A418 for ; Fri, 28 Sep 2007 12:22:29 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from pd2mo1so.prod.shaw.ca (idcmail-mo1so.shaw.ca [24.71.223.10]) by mx1.freebsd.org (Postfix) with ESMTP id D8B5D13C48A for ; Fri, 28 Sep 2007 12:22:28 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from pd2mr5so.prod.shaw.ca (pd2mr5so-qfe3.prod.shaw.ca [10.0.141.8]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0JP200H3ASRPOM50@l-daemon> for freebsd-current@freebsd.org; Fri, 28 Sep 2007 05:19:01 -0600 (MDT) Received: from pn2ml9so.prod.shaw.ca ([10.0.121.7]) by pd2mr5so.prod.shaw.ca (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0JP2009E4SROKX90@pd2mr5so.prod.shaw.ca> for freebsd-current@freebsd.org; Fri, 28 Sep 2007 05:19:01 -0600 (MDT) Received: from hexahedron.daemonology.net ([24.82.201.197]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with SMTP id <0JP200M1XSROGP03@l-daemon> for freebsd-current@freebsd.org; Fri, 28 Sep 2007 05:19:00 -0600 (MDT) Received: (qmail 4329 invoked from network); Fri, 28 Sep 2007 11:18:59 +0000 Received: from unknown (HELO hexahedron.daemonology.net) (127.0.0.1) by localhost with SMTP; Fri, 28 Sep 2007 11:18:59 +0000 Date: Fri, 28 Sep 2007 04:18:58 -0700 From: Colin Percival In-reply-to: <20070928121010.47ec5bcb@hcl-club.lu> To: Jona Joachim Message-id: <46FCE322.2000900@freebsd.org> MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 8BIT X-Enigmail-Version: 0.95.0 Followup-to: freebsd-crap@freebsd.org References: <46FB3067.8040706@MonkeyBrains.NET> <20070927180914.735bd431@hcl-club.lu> <86ps039pek.fsf@ds4.des.no> <20070928121010.47ec5bcb@hcl-club.lu> User-Agent: Thunderbird 2.0.0.6 (X11/20070812) Cc: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= , freebsd-current@freebsd.org Subject: Re: Flash plugin status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 12:22:29 -0000 Jona Joachim wrote: > On Fri, 28 Sep 2007 10:15:31 +0200 > Dag-Erling Smørgrav wrote: >> Jona Joachim writes: >>> Do you want the FreeBSD Foundation to work against our freedom and >>> encourage the use of proprietary binary formats on the World Wide >>> Web? >> >> I think you're confusing the FreeBSD Foundation with the Free Software >> Foundation. The FreeBSD Foundation does not have a political agenda. > > The FreeBSD Foundation supports and represents the FreeBSD Project. No. The FreeBSD Foundation supports the FreeBSD Project. The FreeBSD Core Team represents the FreeBSD Project. > Are you saying that the FreeBSD Project, along with the FreeBSD > Foundation don't care about free software? I'm sure the FreeBSD Project and the FreeBSD Foundation both care a great deal about free software -- but I don't think either believes in the idea of preserving freedom by placing restrictions on what people are allowed to do, as George W. Bush and Richard Stallman have espoused of late. Colin Percival From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 12:30:52 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA63C16A41A for ; Fri, 28 Sep 2007 12:30:52 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.189]) by mx1.freebsd.org (Postfix) with ESMTP id 381AF13C44B for ; Fri, 28 Sep 2007 12:30:51 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: by fk-out-0910.google.com with SMTP id b27so3408966fka for ; Fri, 28 Sep 2007 05:30:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; bh=+trtyjdQUXm82YtImDTC34Zzx/68DmUbgIpNbwW1NDg=; b=EzelUqpVuzeP3yYcd7yX8fEHcnm1RTy60YStKmvrTCbOiJlRQe7Wt3/sI1fhDX3J4EoXRowWYXmWfwL+nkUFBqRAgmUOXxuZEfAeF3DwVB4bfeNBQ30DaO0US5Ew2XJkSLJRTa7jOzyKnFf71LntCLKAkqFpFy5ybolAoyIJNSI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; b=WRwOD5k8RR7XmVjdJb8MZkBulT1Z0Fg/0aMbFFPkApdmdnbKA2l1Qsno5ejH21DWGYtcww2w0hDz4EroP1wI/qZKFbMXJL6MfPYKmN3RjEYsxaH2yu8kdKl76luHku4qfCIcdxCPLsUzwvMNe/bcSh6JP6eInkQfwXQNFKLEXEg= Received: by 10.82.183.19 with SMTP id g19mr7303645buf.1190982648323; Fri, 28 Sep 2007 05:30:48 -0700 (PDT) Received: from orion ( [89.162.141.1]) by mx.google.com with ESMTPS id 6sm3833716nfv.2007.09.28.05.30.45 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 28 Sep 2007 05:30:46 -0700 (PDT) From: Nikolay Pavlov To: freebsd-current@freebsd.org Date: Fri, 28 Sep 2007 14:52:16 +0300 User-Agent: KMail/1.9.7 References: <46FB3067.8040706@MonkeyBrains.NET> <86ps039pek.fsf@ds4.des.no> <20070928121010.47ec5bcb@hcl-club.lu> In-Reply-To: <20070928121010.47ec5bcb@hcl-club.lu> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1978129.cMMSLi7Xtt"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200709281452.21263.qpadla@gmail.com> Cc: Jona Joachim Subject: Re: Flash plugin status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: qpadla@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 12:30:52 -0000 --nextPart1978129.cMMSLi7Xtt Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 28 September 2007 13:10:10 Jona Joachim wrote: > The FreeBSD Foundation supports and represents the FreeBSD Project. > Are you saying that the FreeBSD Project, along with the FreeBSD > Foundation don't care about free software? With all the respect, but this is technical discussion list, there should=20 be a better place for such questions (maybe freebsd-advocacy or=20 freebsd-chat). =2D-=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 =2D Best regards, Nikolay Pavlov. <<<----------------------------------- = =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 --nextPart1978129.cMMSLi7Xtt Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBG/Or1/2R6KvEYGaIRAqYcAKDHkNqkGtzyqMFnDglVhk8pXbKZ7ACfZiH7 gu/M6jTv3eBEBRhA/7bCAJQ= =pDLl -----END PGP SIGNATURE----- --nextPart1978129.cMMSLi7Xtt-- From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 11:50:59 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 878E716A419 for ; Fri, 28 Sep 2007 11:50:59 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from ns.trinitel.com (186.161.36.72.static.reverse.ltdomains.com [72.36.161.186]) by mx1.freebsd.org (Postfix) with ESMTP id 5EB0213C48E for ; Fri, 28 Sep 2007 11:50:59 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from proton.storspeed.com (209-163-168-124.static.twtelecom.net [209.163.168.124]) (authenticated bits=0) by ns.trinitel.com (8.14.1/8.14.1) with ESMTP id l8SBotdC042497; Fri, 28 Sep 2007 06:50:55 -0500 (CDT) (envelope-from anderson@freebsd.org) Message-ID: <46FCEA99.50209@freebsd.org> Date: Fri, 28 Sep 2007 06:50:49 -0500 From: Eric Anderson User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Jona Joachim References: <46FB3067.8040706@MonkeyBrains.NET> <20070927180914.735bd431@hcl-club.lu> <86ps039pek.fsf@ds4.des.no> <20070928121010.47ec5bcb@hcl-club.lu> In-Reply-To: <20070928121010.47ec5bcb@hcl-club.lu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on ns.trinitel.com X-Mailman-Approved-At: Fri, 28 Sep 2007 12:57:46 +0000 Cc: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= , freebsd-chat@freebsd.org Subject: Re: Flash plugin status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 11:50:59 -0000 Jona Joachim wrote: > On Fri, 28 Sep 2007 10:15:31 +0200 > Dag-Erling Smørgrav wrote: > >> Jona Joachim writes: >>> Rudy wrote: >>>> [2] Any update on getting the freebsd foundation to take >>>> on Flash (ala Java)? >>> That would be horrible! >>> Do you want the FreeBSD Foundation to work against our freedom and >>> encourage the use of proprietary binary formats on the World Wide >>> Web? >> I think you're confusing the FreeBSD Foundation with the Free Software >> Foundation. The FreeBSD Foundation does not have a political agenda. > > The FreeBSD Foundation supports and represents the FreeBSD Project. > Are you saying that the FreeBSD Project, along with the FreeBSD > Foundation don't care about free software? *sigh* Move it to -chat now please... Eric From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 13:34:53 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5AA6316A418 for ; Fri, 28 Sep 2007 13:34:53 +0000 (UTC) (envelope-from cb@severious.net) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.freebsd.org (Postfix) with ESMTP id 38D9413C46A for ; Fri, 28 Sep 2007 13:34:53 +0000 (UTC) (envelope-from cb@severious.net) Received: by ion.gank.org (Postfix, from userid 1001) id 00FAC11100; Fri, 28 Sep 2007 08:34:52 -0500 (CDT) Date: Fri, 28 Sep 2007 08:34:52 -0500 From: Craig Boston To: Scott Long Message-ID: <20070928133452.GA52277@nowhere> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46F7D7A4.5090007@samsco.org> User-Agent: Mutt/1.4.2.2i Cc: Darren Reed , freebsd-current@freebsd.org, Larry Rosenman Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 13:34:53 -0000 On Mon, Sep 24, 2007 at 09:28:36AM -0600, Scott Long wrote: > You're all missing the point, I hate to say. What happened is that a > change was made recently to more accurately account for allocated > memory. Now people are getting kmem_map_too_small panics that weren't > getting them before. So while the accounting is now more accurate, > the outcome is actually harmful. That needs to be fixed before the > release. Agreed. A month ago I had zfs running perfectly on many different i386 machines (albeit with some tweaking to kernel parameters). With a week-old current, it always panics sooner or later now, no matter how low I set the ARC cache size or maxvnodes or how much I pump into kmem_size. Now kmem_map panics are being reported on amd64, which was pretty much unheard of before. If I can track down the exact change I'll just back it out of my local tree. Craig From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 14:24:24 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4E5816A41B; Fri, 28 Sep 2007 14:24:24 +0000 (UTC) (envelope-from fyr@fyrou.net) Received: from noway.fyrou.net (unknown [IPv6:2a01:48:100:1:1::302]) by mx1.freebsd.org (Postfix) with ESMTP id 0994C13C467; Fri, 28 Sep 2007 14:24:23 +0000 (UTC) (envelope-from fyr@fyrou.net) Received: from noway.fyrou.net (localhost [IPv6:::1]) by noway.fyrou.net (8.14.1/8.14.1) with ESMTP id l8SEOKfr060943; Fri, 28 Sep 2007 16:24:20 +0200 (CEST) (envelope-from fyr@noway.fyrou.net) Received: (from fyr@localhost) by noway.fyrou.net (8.14.1/8.14.1/Submit) id l8SEOKN4060942; Fri, 28 Sep 2007 16:24:20 +0200 (CEST) (envelope-from fyr) Date: Fri, 28 Sep 2007 16:24:19 +0200 From: Francois Ranchin To: Craig Boston Message-ID: <20070928142419.GA59916@fyrou.net> Mail-Followup-To: Francois Ranchin , Craig Boston , Scott Long , Darren Reed , freebsd-current@freebsd.org, Larry Rosenman References: <46F7D7A4.5090007@samsco.org> <20070928133452.GA52277@nowhere> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20070928133452.GA52277@nowhere> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.0-CURRENT i386 X-NCC-RegId: fr.witbe X-Virus-Scanned: ClamAV 0.91.2/4419/Fri Sep 28 09:36:28 2007 on noway.fyrou.net X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on noway.fyrou.net Cc: Darren Reed , freebsd-current@freebsd.org, Larry Rosenman Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 14:24:24 -0000 According to Craig Boston : > Agreed. A month ago I had zfs running perfectly on many different i386 > machines (albeit with some tweaking to kernel parameters). With a > week-old current, it always panics sooner or later now, no matter how > low I set the ARC cache size or maxvnodes or how much I pump into > kmem_size. Me too. > Now kmem_map panics are being reported on amd64, which was pretty much > unheard of before. > > If I can track down the exact change I'll just back it out of my local > tree. Perhaps these two (2 weeks old) : arc.c 1.11 and/or zfs_vfsops.c v1.12 Regards, -- François Ranchin -+- fyr@fyrou.net From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 14:37:26 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06B1916A420; Fri, 28 Sep 2007 14:37:26 +0000 (UTC) (envelope-from cb@severious.net) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.freebsd.org (Postfix) with ESMTP id E2C3713C468; Fri, 28 Sep 2007 14:37:25 +0000 (UTC) (envelope-from cb@severious.net) Received: by ion.gank.org (Postfix, from userid 1001) id 70FC810F4E; Fri, 28 Sep 2007 09:37:25 -0500 (CDT) Date: Fri, 28 Sep 2007 09:37:25 -0500 From: Craig Boston To: Francois Ranchin , Scott Long , Darren Reed , freebsd-current@freebsd.org, Larry Rosenman Message-ID: <20070928143725.GB52277@nowhere> References: <46F7D7A4.5090007@samsco.org> <20070928133452.GA52277@nowhere> <20070928142419.GA59916@fyrou.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070928142419.GA59916@fyrou.net> User-Agent: Mutt/1.4.2.2i Cc: Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 14:37:26 -0000 On Fri, Sep 28, 2007 at 04:24:19PM +0200, Francois Ranchin wrote: > Perhaps these two (2 weeks old) : arc.c 1.11 and/or zfs_vfsops.c v1.12 Pretty sure those aren't the root of the problem. I had already tried falling back to a build from before those two changes went in, and while it does take longer to panic it still does eventually. Craig From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 14:41:12 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26BF516A417; Fri, 28 Sep 2007 14:41:12 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) by mx1.freebsd.org (Postfix) with ESMTP id E979513C457; Fri, 28 Sep 2007 14:41:11 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org ([192.147.25.65]:54783) by thebighonker.lerctr.org with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IbH1Y-00007I-6r; Fri, 28 Sep 2007 09:41:04 -0500 Date: Fri, 28 Sep 2007 09:40:57 -0500 (CDT) From: Larry Rosenman To: Craig Boston In-Reply-To: <20070928143725.GB52277@nowhere> Message-ID: <20070928094021.N422@thebighonker.lerctr.org> References: <46F7D7A4.5090007@samsco.org> <20070928133452.GA52277@nowhere> <20070928142419.GA59916@fyrou.net> <20070928143725.GB52277@nowhere> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: -1.5 (-) X-LERCTR-Spam-Score: -1.5 (-) X-Spam-Report: SpamScore (-1.5/5.0) ALL_TRUSTED=-1.8, BAYES_00=-2.599, DNS_FROM_DOB=0.732, RCVD_IN_DOB=1.103, URIBL_RHS_DOB=1.083 X-LERCTR-Spam-Report: SpamScore (-1.5/5.0) ALL_TRUSTED=-1.8, BAYES_00=-2.599, DNS_FROM_DOB=0.732, RCVD_IN_DOB=1.103, URIBL_RHS_DOB=1.083 DomainKey-Status: no signature Cc: Darren Reed , Francois Ranchin , freebsd-current@freebsd.org Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 14:41:12 -0000 On Fri, 28 Sep 2007, Craig Boston wrote: > On Fri, Sep 28, 2007 at 04:24:19PM +0200, Francois Ranchin wrote: >> Perhaps these two (2 weeks old) : arc.c 1.11 and/or zfs_vfsops.c v1.12 > > Pretty sure those aren't the root of the problem. I had already tried > falling back to a build from before those two changes went in, and while > it does take longer to panic it still does eventually. > ScottL@FreeBSD.org mentioned some low-level memory accounting changes that went in, so memory is accounted for more accurately. LER > Craig > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 14:45:05 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97C2416A41A for ; Fri, 28 Sep 2007 14:45:05 +0000 (UTC) (envelope-from thomas@FreeBSD.ORG) Received: from melamine.cuivre.fr.eu.org (melusine.cuivre.fr.eu.org [82.225.155.84]) by mx1.freebsd.org (Postfix) with ESMTP id 59A3513C458 for ; Fri, 28 Sep 2007 14:45:05 +0000 (UTC) (envelope-from thomas@FreeBSD.ORG) Received: by melamine.cuivre.fr.eu.org (Postfix, from userid 1000) id 0C3C85C627; Fri, 28 Sep 2007 16:45:03 +0200 (CEST) Date: Fri, 28 Sep 2007 16:45:03 +0200 From: Thomas Quinot To: Kevin Oberman Message-ID: <20070928144503.GA19788@melamine.cuivre.fr.eu.org> References: <46FB3067.8040706@MonkeyBrains.NET> <20070927164421.A801B45019@ptavv.es.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070927164421.A801B45019@ptavv.es.net> X-message-flag: WARNING! Using Outlook can damage your computer. User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org, Rudy Subject: Re: Flash plugin status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 14:45:05 -0000 * Kevin Oberman, 2007-09-27 : > I did the update and ran: > nspluginwrapper -i -v /usr/X11R6/lib/linux-mozilla/plugins/nphelix.so \ > /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so > > (I don't like the Acrobat plugin, so I don't install that one.) > > Note that nspluginwrapper must be run by each user before starting > firefox. ... unless you run nspluginwrapper as root, in which case it will do what is needed for plugins to be available to all users. > I have no joy to spread in Flash 9. Happily, most of the sites I use Same, unfortunately. But nspluginwrapper was a huge progress for me anyway (compared to linuxpluginwrapper). Thomas. From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 15:22:45 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 106B716A469; Fri, 28 Sep 2007 15:22:45 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id B260A13C480; Fri, 28 Sep 2007 15:22:44 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from [192.168.4.84] (wireless.prattprop.com [209.97.224.24] (may be forged)) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l8SFMaoe078603; Fri, 28 Sep 2007 09:22:41 -0600 (MDT) (envelope-from scottl@samsco.org) References: <46F7D7A4.5090007@samsco.org> <20070928133452.GA52277@nowhere> <20070928142419.GA59916@fyrou.net> <20070928143725.GB52277@nowhere> <20070928094021.N422@thebighonker.lerctr.org> Message-Id: From: Scott Long To: Larry Rosenman In-Reply-To: <20070928094021.N422@thebighonker.lerctr.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes X-Mailer: iPhone Mail (1C28) Mime-Version: 1.0 (iPhone Mail 1C28) Content-Transfer-Encoding: 7bit Date: Fri, 28 Sep 2007 09:22:20 -0600 X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Fri, 28 Sep 2007 09:22:41 -0600 (MDT) X-Spam-Status: No, score=-1.4 required=5.5 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: Darren Reed , Francois Ranchin , "freebsd-current@freebsd.org" , Craig Boston Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 15:22:45 -0000 On Sep 28, 2007, at 8:40 AM, Larry Rosenman wrote: > On Fri, 28 Sep 2007, Craig Boston wrote: > >> On Fri, Sep 28, 2007 at 04:24:19PM +0200, Francois Ranchin wrote: >>> Perhaps these two (2 weeks old) : arc.c 1.11 and/or zfs_vfsops.c >>> v1.12 >> >> Pretty sure those aren't the root of the problem. I had already >> tried >> falling back to a build from before those two changes went in, and >> while >> it does take longer to panic it still does eventually. >> > ScottL@FreeBSD.org mentioned some low-level memory accounting changes > that went in, so memory is accounted for more accurately. > >> Alan Cox pointed out in private that this likely isn't the problem. Scott From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 16:24:49 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED6E016A46B for ; Fri, 28 Sep 2007 16:24:49 +0000 (UTC) (envelope-from jpedras+freebsd-current@webvolution.net) Received: from mail.portrait.com (mail.portrait.com [64.171.32.41]) by mx1.freebsd.org (Postfix) with ESMTP id A4C8113C4C5 for ; Fri, 28 Sep 2007 16:24:49 +0000 (UTC) (envelope-from jpedras+freebsd-current@webvolution.net) Received: from teko.tafkap.priv (beastie.webvolution.net [64.174.136.225]) (authenticated bits=0) by mail.portrait.com (8.13.1/8.13.1) with ESMTP id l8SGOb6u031612 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Sep 2007 09:24:42 -0700 (PDT) (envelope-from jpedras+freebsd-current@webvolution.net) Message-ID: <46FD2ABA.5040307@webvolution.net> Date: Fri, 28 Sep 2007 09:24:26 -0700 From: Joao Pedras User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org, Attilio Rao References: <46FA0C14.10201@webvolution.net> <46FADB35.2090708@FreeBSD.org> <46FC2AA7.2040308@webvolution.net> <46FC2C85.4080600@FreeBSD.org> <46FC8EEE.5080908@webvolution.net> <3bbf2fe10709280337n1be084b3qf1ef7fc94889592b@mail.gmail.com> In-Reply-To: <3bbf2fe10709280337n1be084b3qf1ef7fc94889592b@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.1 required=3.0 tests=FORGED_RCVD_HELO X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on mail.portrait.com Cc: Subject: Re: lock up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 16:24:50 -0000 Attilio Rao wrote: > 2007/9/28, Joao Pedras : >> Thank you for your help Kris. I am not very familiar with these tasks. >> >> I got the 'alltrace' and I also saved a crash dump. >> The session output is here http://pedras.webvolution.net/s2932-9.txt. >> >> I was able to reproduce the issue on a similar system (a vanilla Tyan >> S2932, one SATA disc only) and it exhibits the exact same problem. > > Hello, > when you updated CURRENT last time? > csjp committed a fix which should have resolved the rtfree reference > mismatching problem like a week ago. > > Can you try if a stock, fresh cvsuped current exposes the same problem for you? > > Thanks, > Attilio > > Attilio, I noticed that rtfree fix. This system is running code from 9-25. I will sup it to today's code anyway. Again, it is GENERIC amd64 (SCHED_4BSD). I have another one with ULE and I will give it a try today. Thanks for your help. Joao From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 16:26:14 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29E3D16A469; Fri, 28 Sep 2007 16:26:14 +0000 (UTC) (envelope-from Muhammad.Shafiq@neterion.com) Received: from owa.neterion.com (mx.neterion.com [72.1.205.142]) by mx1.freebsd.org (Postfix) with ESMTP id B5AA713C4BF; Fri, 28 Sep 2007 16:26:13 +0000 (UTC) (envelope-from Muhammad.Shafiq@neterion.com) X-MIMEOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 28 Sep 2007 12:14:07 -0400 Message-ID: <78C9135A3D2ECE4B8162EBDCE82CAD770245002D@nekter> In-Reply-To: <2a41acea0709241028q2503f12fp86eea2d32ac10aa7@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: TX Multiqueue? Thread-Index: Acf+0Hb5oO1MMOqvQp+6JbpC3kH3PQDFbzCA References: <2a41acea0709221656n4aa62776y488c7f2da262c9f6@mail.gmail.com><46F614F2.4050402@freebsd.org> <2a41acea0709241028q2503f12fp86eea2d32ac10aa7@mail.gmail.com> From: "Muhammad Shafiq" To: "Jack Vogel" , "Kip Macy" Cc: Darren Reed , freebsd-net@freebsd.org, FreeBSD Current Subject: RE: TX Multiqueue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 16:26:14 -0000 -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Jack Vogel Sent: Monday, September 24, 2007 10:28 AM To: Kip Macy Cc: Darren Reed; freebsd-net@freebsd.org; FreeBSD Current Subject: Re: TX Multiqueue? On 9/23/07, Kip Macy wrote: > On 9/23/07, Darren Reed wrote: > > Kip Macy wrote: > > > My ethng branch supports multiple rx and tx queues. > > > > > > -Kip > > > > > > > What are your plans for how we use/manage/interact with the mutiple > > rx/tx queues? > > The rx hardware queue is determined by the hardware. Different > hardware allows for different policies. I just use the stock rss_hash > of a crc32 of the 4-tuple in cxgb. I've added a field to the pkthdr > which cxgb uses the least significant bits of to determine which > outbound queue to use. Its up to the upper layers to determine how to > set those bits. One of the changes that is required to take advantaged > of this is moving the queues into the driver. I've added a new > if_start function to ifnet to take advantage of this. I also have a > normal if_start function for backward compatibility. Yes, the queues in Oplin and Zoar are also a hardware feature, not just some software infrastructure. There are a number of different ways that it can be configured. I did not have some settled notion of how things should be managed but I would rather not have it be something done under the covers in the driver, a configurable stack option seems better to me. This needs to be done right or it will just be a hack, I don't know who the right parties are, it should not be just a one-person decision, those with a stake in this sort of thing should all be involved. [Muhammad Shafiq]=20 Based upon our experience, form other OS(s), the HW TX/RX queues are quite helpful in reducing CPU utilization (in MP machines). For example, XFRAME-I/II TX/RX queues, originally intended for "I/O Virtualization", can be affiliated to specific CPU(s); the resulting locality of reference improves cache hits and reduces lock contention, if any. The HW details of this mechanism can be found at the following link:=20 http://www.neterion.com/support/xframe_developer.html We would prefer to have a configurable, generic, mechanism to exploit the multiple TX/RX queues, now supported by NIC vendors. If possible, the mechanism should be extendable to fit into specific capability/requirement of HW vendors.=20 =20 Cheers, Jack _______________________________________________ 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 Sep 28 16:36:23 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B20816A417 for ; Fri, 28 Sep 2007 16:36:23 +0000 (UTC) (envelope-from don@siad.net) Received: from mars.siad.net (mars.siad.net [69.3.214.122]) by mx1.freebsd.org (Postfix) with ESMTP id 0271D13C44B for ; Fri, 28 Sep 2007 16:36:22 +0000 (UTC) (envelope-from don@siad.net) Received: from [69.3.214.123] (rover.siad.net [69.3.214.123]) (authenticated bits=0) by mars.siad.net (8.13.8/8.13.1) with ESMTP id l8SGY2Un049464 for ; Fri, 28 Sep 2007 09:34:03 -0700 (PDT) (envelope-from don@siad.net) Message-ID: <46FD2CFF.4000300@siad.net> Date: Fri, 28 Sep 2007 09:34:07 -0700 From: "Don L. Belcher" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20070522 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <46F5B918.5040804@siad.net> In-Reply-To: <46F5B918.5040804@siad.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-2.0b1 (mars.siad.net [69.3.214.122]); Fri, 28 Sep 2007 09:34:03 -0700 (PDT) Subject: PCI to PCI Bridge initialization fails or is corrupted X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 16:36:23 -0000 If somebody could point out to me where the prefetch decode occurs in the code, this would be a big help. > This worked around about march of this year. It > seems to be failing configuration of prefetch > decode. > > Works with 6.0 > 7.0-CURRENT FreeBSD > > > pcib3@pci2:6:0: class=0x060400 card=0x00000000 chip=0x01001668 > rev=0x11 hdr=0x01 > vendor = 'Actiontec Electronics Inc.' > device = '0304 PCI to PCI Bridge' > class = bridge > subclass = PCI-PCI > > IS: > pcib3: at device 6.0 on pci2 > pcib3: secondary bus 3 > pcib3: subordinate bus 3 > pcib3: I/O decode 0x3000-0x3fff > pcib3: memory decode 0xf0600000-0xf07fffff > pcib3: no prefetched decode > pci3: on pcib3 > pci3: physical bus=3 > > > > SHOULD BE: > pcib3: at device 6.0 on pci2 > pcib3: secondary bus 3 > pcib3: subordinate bus 3 > pcib3: I/O decode 0x3000-0x3fff > pcib3: memory decode 0xf0600000-0xf07fffff > pcib3: prefetched decode 0xfff00000-0xfffff > From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 17:56:20 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3053916A41B for ; Fri, 28 Sep 2007 17:56:20 +0000 (UTC) (envelope-from mgowda82@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.freebsd.org (Postfix) with ESMTP id B21FD13C4B0 for ; Fri, 28 Sep 2007 17:56:18 +0000 (UTC) (envelope-from mgowda82@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so2300019nfb for ; Fri, 28 Sep 2007 10:56:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=A7jBRWdT4B17xvRTA79PKrX36ZnBynBsjnzVZfpOtTM=; b=Onon4Hn3F5VEXBin9oyaJ2OuN0/v2SWiMAOiL4mXcAmQIDxqIeNSTYCHqDi/ZlDw8d2eTaScXy2XuHs/WVpRwEVljRVNw+Tomq8MVprDw9nt1NPB0OzDVpD0sgOYyj6Rh5BytIYmLvqw/HFlx5ECgLFdpcXrHcaf6W6UMasYRN0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Espczm9Wa7N6XO+HZZ5kamh+Z/aSpBVw6DMH2t9QJ2rWTcBDKxgi0xU46xzwhFxT/NNo/N2zXGFvDP4whMwBBn17J3ZWk1DQurW4pSA+akA2QnVnnrdD7dt8jhZli9ti2FT9zdNiWbKa1nCcHPI1+3ahbQK8EIl6vw1u995fN8w= Received: by 10.78.181.13 with SMTP id d13mr88799huf.1191000616134; Fri, 28 Sep 2007 10:30:16 -0700 (PDT) Received: by 10.142.165.5 with HTTP; Fri, 28 Sep 2007 10:30:16 -0700 (PDT) Message-ID: Date: Fri, 28 Sep 2007 10:30:16 -0700 From: "Manjunath R Gowda" To: "Don L. Belcher" In-Reply-To: <46FD2CFF.4000300@siad.net> MIME-Version: 1.0 References: <46F5B918.5040804@siad.net> <46FD2CFF.4000300@siad.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: PCI to PCI Bridge initialization fails or is corrupted X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 17:56:20 -0000 On 9/28/07, Don L. Belcher wrote: > > If somebody could point out to me where the prefetch decode > occurs in the code, this would be a big help. > > > This worked around about march of this year. It > > seems to be failing configuration of prefetch > > decode. > > > > Works with 6.0 > > 7.0-CURRENT FreeBSD > > > > > > pcib3@pci2:6:0: class=0x060400 card=0x00000000 chip=0x01001668 > > rev=0x11 hdr=0x01 > > vendor = 'Actiontec Electronics Inc.' > > device = '0304 PCI to PCI Bridge' > > class = bridge > > subclass = PCI-PCI > > > > IS: > > pcib3: at device 6.0 on pci2 > > pcib3: secondary bus 3 > > pcib3: subordinate bus 3 > > pcib3: I/O decode 0x3000-0x3fff > > pcib3: memory decode 0xf0600000-0xf07fffff > > pcib3: no prefetched decode > > pci3: on pcib3 > > pci3: physical bus=3 > > > > > > > > SHOULD BE: > > pcib3: at device 6.0 on pci2 > > pcib3: secondary bus 3 > > pcib3: subordinate bus 3 > > pcib3: I/O decode 0x3000-0x3fff > > pcib3: memory decode 0xf0600000-0xf07fffff > > pcib3: prefetched decode 0xfff00000-0xfffff > > Do you see the problem with 6.2 as well? Try booting with ACPI disabled. I've seen some issues with PCI intialization code as well. On perticular servers FreeBSD fails to attach pci cards they work fine with Linux. -Manjunath From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 18:13:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CFFF316A419 for ; Fri, 28 Sep 2007 18:13:18 +0000 (UTC) (envelope-from lists@c0mplx.org) Received: from home.c0mplx.org (home.c0mplx.org [IPv6:2001:14b0:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id 7E89D13C4A5 for ; Fri, 28 Sep 2007 18:13:18 +0000 (UTC) (envelope-from lists@c0mplx.org) Received: from pi by home.c0mplx.org with local (Exim 4.66 (FreeBSD)) (envelope-from ) id 1IbKKz-000NQ3-Uk; Fri, 28 Sep 2007 20:13:17 +0200 Date: Fri, 28 Sep 2007 20:13:17 +0200 From: Kurt Jaeger To: "Don L. Belcher" Message-ID: <20070928181317.GA12479@home.c0mplx.org> References: <46F5B918.5040804@siad.net> <46FD2CFF.4000300@siad.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46FD2CFF.4000300@siad.net> Cc: freebsd-current@freebsd.org Subject: Re: PCI to PCI Bridge initialization fails or is corrupted X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 18:13:18 -0000 Hi! > If somebody could point out to me where the prefetch decode > occurs in the code, this would be a big help. I assume you have sys/dev/pci/pci_pci.c, version 1.49 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/pci/pci_pci.c?rev=1.49;content-type=text%2Fplain In line 183f, sc->pmembase is set: sc->pmembase = PCI_PPBMEMBASE(pci_read_config(dev, PCIR_PMBASEH_1, 4), pci_read_config(dev, PCIR_PMBASEL_1, 2)); and if sc->pmembase is set, the function call to pcib_is_prefetch_open() leads to the result you are looking for in line 267: if (pcib_is_prefetch_open(sc)) device_printf(dev, " prefetched decode 0x%jx-0x%jx\n", (uintmax_t)sc->pmembase, (uintmax_t)sc->pmemlimit); But why the pci_read_config() returns something different, I do not know. -- pi@c0mplx.org +49 171 3101372 13 years to go ! From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 18:18:27 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6510616A417 for ; Fri, 28 Sep 2007 18:18:27 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by mx1.freebsd.org (Postfix) with ESMTP id E4D6E13C459 for ; Fri, 28 Sep 2007 18:18:26 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: by ug-out-1314.google.com with SMTP id a2so1789000ugf for ; Fri, 28 Sep 2007 11:18:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=bH5YB1f19FfM881pqvTuJYDZuXAWwd7DoYhuTo8R4tA=; b=AwrTl4NFeWK/EacbMNlKiha0nno69B3pLVsfGTPqhPaJgMOEkq9COuMZrxQ6p68/OrwuMZo4L+NRbv5AL36GrGjBOSV3Y1qsKIdM8cEYQdiVZfiA715PeGTmgW9xS4BCXe+4XDz4t+y4NH1SxE+nEerd7qMihT/9pQl9zGZjrpA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=jHpRPDH6jRezxilxyXkMuC733yMcQL98P3UIiQGZ+UOMfnIUO//0vEhIy15qesUdaFWwVMEs3jqyQrhFaJo7jRbCGw63RFioHiJrEJwolusMCMVIiiRGhy8M0RUHtxQk+ztHxRjxGAJph4XQHY2VTNABoSjazRHcdEMHIZREO5M= Received: by 10.66.240.12 with SMTP id n12mr5392905ugh.1191003505535; Fri, 28 Sep 2007 11:18:25 -0700 (PDT) Received: by 10.67.20.1 with HTTP; Fri, 28 Sep 2007 11:18:25 -0700 (PDT) Message-ID: <3aaaa3a0709281118k7fa35133wdc908a025180e6e0@mail.gmail.com> Date: Fri, 28 Sep 2007 19:18:25 +0100 From: Chris To: "FreeBSD Current" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: problems with 7.0 kernel page faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 18:18:27 -0000 Submitted 2 PRs for 7.0 we only been using it for a few hours and have had repeated kernel page faults crashing the system so was dissapointed considering this is said to be nearly ready for release. PRs are 116719 and 116720 in misc. First one was caused by simply running reboot, I recompiled world with -O which seems to prevent this occuring. Second one is when running 'killall watch' with at least 1 watch process running this causes the kernel to page fault and this happens even when compiled with -O. If anyone is interested can post logs dmesg etc. and have a kernel dump for the 2nd problem. Chris From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 15:20:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D53F16A41A; Fri, 28 Sep 2007 15:20:18 +0000 (UTC) (envelope-from phi@evilphi.com) Received: from mail.twinthornes.com (mail.twinthornes.com [65.75.198.147]) by mx1.freebsd.org (Postfix) with ESMTP id 76D3613C44B; Fri, 28 Sep 2007 15:20:18 +0000 (UTC) (envelope-from phi@evilphi.com) Received: from [10.9.70.100] (pool-71-117-232-141.ptldor.fios.verizon.net [71.117.232.141]) by mail.twinthornes.com (Postfix) with ESMTP id 71C6F4E; Fri, 28 Sep 2007 07:56:46 -0700 (PDT) Message-ID: <46FD1631.9020708@evilphi.com> Date: Fri, 28 Sep 2007 07:56:49 -0700 From: Darren Pilgrim User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Claus Guttesen , Kris Kennaway , freebsd-current@freebsd.org References: <46FCB7B7.9010301@FreeBSD.org> <20070928083322.GA17225@eos.sc1.parodius.com> In-Reply-To: <20070928083322.GA17225@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 28 Sep 2007 18:22:13 +0000 Cc: Subject: Re: 8-core server X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 15:20:18 -0000 Jeremy Chadwick wrote: > I think what you're not noticing is that the cores are being launched in > non-sequential order. 1, 2, 3, 4, 7, 5, 6. This isn't a problem. Why they wouldn't be launched sequentially? -- Darren Pilgrim From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 18:47:16 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFFBC16A417 for ; Fri, 28 Sep 2007 18:47:16 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 66DDC13C48A for ; Fri, 28 Sep 2007 18:47:16 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id l8SIl6Ox056497; Fri, 28 Sep 2007 20:47:06 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id l8SIl1L1059599 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Sep 2007 20:47:02 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id l8SIl1DR057836; Fri, 28 Sep 2007 20:47:01 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id l8SIl09T057835; Fri, 28 Sep 2007 20:47:00 +0200 (CEST) (envelope-from ticso) Date: Fri, 28 Sep 2007 20:47:00 +0200 From: Bernd Walter To: Darren Pilgrim Message-ID: <20070928184659.GB57646@cicely12.cicely.de> References: <46FCB7B7.9010301@FreeBSD.org> <20070928083322.GA17225@eos.sc1.parodius.com> <46FD1631.9020708@evilphi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46FD1631.9020708@evilphi.com> X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=1.018, BAYES_00=-2.599 autolearn=ham version=3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on cicely12.cicely.de Cc: freebsd-current@freebsd.org, Claus Guttesen Subject: Re: 8-core server X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 18:47:17 -0000 On Fri, Sep 28, 2007 at 07:56:49AM -0700, Darren Pilgrim wrote: > Jeremy Chadwick wrote: > >I think what you're not noticing is that the cores are being launched in > >non-sequential order. 1, 2, 3, 4, 7, 5, 6. This isn't a problem. > > Why they wouldn't be launched sequentially? First SMP rule: Don't expect a specific execution order from things running parallel. I don't know the code, but would assume that they are started sequentially and each core prints it's own line, so they get disordered. -- B.Walter http://www.bwct.de http://www.fizon.de bernd@bwct.de info@bwct.de support@fizon.de From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 18:51:43 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 297B316A41A for ; Fri, 28 Sep 2007 18:51:43 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 7197013C44B for ; Fri, 28 Sep 2007 18:51:42 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 28 Sep 2007 18:51:40 -0000 Received: from h081217094222.dyn.cm.kabsi.at (EHLO taxman.pepperland) [81.217.94.222] by mail.gmx.net (mp035) with SMTP; 28 Sep 2007 20:51:40 +0200 X-Authenticated: #16703784 X-Provags-ID: V01U2FsdGVkX18fu6h8S9Mfk+ESyyjJlF32x/SWfK/yFpGL/Njhd1 9s5fsfk/SdFmjU From: Stefan Ehmann To: freebsd-current@freebsd.org Date: Fri, 28 Sep 2007 20:51:40 +0200 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709282051.41459.shoesoft@gmx.net> X-Y-GMX-Trusted: 0 Subject: installworld error: uuencode not found X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 18:51:43 -0000 With fresh sources I get this: ===> share/syscons/scrnmaps (install) ./armscii8-2haik8.mk armscii8-2haik8.tmp uuencode armscii8-2haik8.tmp armscii8-2haik8 > armscii8-2haik8.scm uuencode: not found *** Error code 127 Stop in /usr/src/share/syscons/scrnmaps. Anyone else seeing this or is the error on my end? -- Stefan From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 19:06:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84EC716A418 for ; Fri, 28 Sep 2007 19:06:18 +0000 (UTC) (envelope-from jpedras+freebsd-current@webvolution.net) Received: from mail.portrait.com (mail.portrait.com [64.171.32.41]) by mx1.freebsd.org (Postfix) with ESMTP id 624CB13C46E for ; Fri, 28 Sep 2007 19:06:18 +0000 (UTC) (envelope-from jpedras+freebsd-current@webvolution.net) Received: from teko.tafkap.priv (beastie.webvolution.net [64.174.136.225]) (authenticated bits=0) by mail.portrait.com (8.13.1/8.13.1) with ESMTP id l8SJ65mY034479 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Sep 2007 12:06:09 -0700 (PDT) (envelope-from jpedras+freebsd-current@webvolution.net) Message-ID: <46FD5093.1050606@webvolution.net> Date: Fri, 28 Sep 2007 12:05:55 -0700 From: Joao Pedras User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Stefan Ehmann References: <200709282051.41459.shoesoft@gmx.net> In-Reply-To: <200709282051.41459.shoesoft@gmx.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.1 required=3.0 tests=FORGED_RCVD_HELO X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on mail.portrait.com Cc: freebsd-current@freebsd.org Subject: Re: installworld error: uuencode not found X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 19:06:18 -0000 Stefan, just built sup'ed an hour ago and it finished fine. Thanks. Stefan Ehmann wrote: > With fresh sources I get this: > > ===> share/syscons/scrnmaps (install) > ./armscii8-2haik8.mk armscii8-2haik8.tmp > uuencode armscii8-2haik8.tmp armscii8-2haik8 > armscii8-2haik8.scm > uuencode: not found > *** Error code 127 > > Stop in /usr/src/share/syscons/scrnmaps. > > > Anyone else seeing this or is the error on my end? > From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 19:07:14 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 775BE16A417 for ; Fri, 28 Sep 2007 19:07:14 +0000 (UTC) (envelope-from sa2c@sa2c.net) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.183]) by mx1.freebsd.org (Postfix) with ESMTP id 3504613C481 for ; Fri, 28 Sep 2007 19:07:14 +0000 (UTC) (envelope-from sa2c@sa2c.net) Received: by el-out-1112.google.com with SMTP id r27so698291ele for ; Fri, 28 Sep 2007 12:07:13 -0700 (PDT) Received: by 10.114.154.1 with SMTP id b1mr1197398wae.1191004942378; Fri, 28 Sep 2007 11:42:22 -0700 (PDT) Received: from ?192.168.1.3? ( [220.102.212.119]) by mx.google.com with ESMTPS id j21sm6090260wah.2007.09.28.11.42.20 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 28 Sep 2007 11:42:21 -0700 (PDT) Message-ID: <46FD4B09.20006@sa2c.net> Date: Sat, 29 Sep 2007 03:42:17 +0900 From: NIIMI Satoshi MIME-Version: 1.0 To: freebsd-threads@freebsd.org Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: sched_yield() is very slow when other threads are busy on FreeBSD-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 19:07:14 -0000 Hi, I experienced sched_yield() is very slow when other threads are busy on FreeBSD-current. When I run the program: ------------------------------------------------ #include #include #include #define NUM_THREAD (10) volatile int run = 0; void *start(void *p) { while (!run) ; return p; } int main() { pthread_t th[NUM_THREAD]; int i; for (i = 0; i < NUM_THREAD; i++) { assert(pthread_create(&th[i], NULL, start, NULL) == 0); sched_yield(); } run = 1; for (i = 0; i < NUM_THREAD; i++) assert(pthread_join(th[i], NULL) == 0); return 0; } ------------------------------------------------ The output of /usr/bin/time: FreeBSD 6.2-RELEASE, libthr, HZ=100, GENERIC kernel: 0.55 real 0.55 user 0.00 sys FreeBSD 7-CURRENT, libthr, HZ=100, kernel include GENERIC nooptions INVARIANTS, INVARIANT_SUPPORT, WITNESS, WITNESS_SKIPSPIN: 164.16 real 162.80 user 0.00 sys I tried SCHED_ULE too, but does not help so much. Increasing HZ helps to perform better, but still very slower than FreeBSD-6. Thanks, -- NIIMI Satoshi From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 19:17:14 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AF0D16A417 for ; Fri, 28 Sep 2007 19:17:14 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id DA6FF13C45A for ; Fri, 28 Sep 2007 19:17:13 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 28 Sep 2007 19:17:12 -0000 Received: from h081217094222.dyn.cm.kabsi.at (EHLO taxman.pepperland) [81.217.94.222] by mail.gmx.net (mp057) with SMTP; 28 Sep 2007 21:17:12 +0200 X-Authenticated: #16703784 X-Provags-ID: V01U2FsdGVkX1+VC31odx6VgzD88tCBRQmQfvRYjC5T3OL31Pq5SI uF2gPvKuq7n0Ji From: Stefan Ehmann To: Joao Pedras Date: Fri, 28 Sep 2007 21:17:12 +0200 User-Agent: KMail/1.9.7 References: <200709282051.41459.shoesoft@gmx.net> <46FD5093.1050606@webvolution.net> In-Reply-To: <46FD5093.1050606@webvolution.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709282117.12729.shoesoft@gmx.net> X-Y-GMX-Trusted: 0 Cc: freebsd-current@freebsd.org Subject: Re: installworld error: uuencode not found X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 19:17:14 -0000 On Friday 28 September 2007 21:05:55 Joao Pedras wrote: > Stefan, > > just built sup'ed an hour ago and it finished fine. Thanks for the report. I fixed the "uuencode: not found" by rebuilding/installing it. Now it complains that btxld is not found. Something has probably gone wrong while doing buildworld. I'll try rebuilding and hope everything works fine after that. -- Stefan From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 19:25:10 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BE7716A469 for ; Fri, 28 Sep 2007 19:25:10 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from gnome.kiev.sovam.com (gnome.kiev.sovam.com [212.109.32.24]) by mx1.freebsd.org (Postfix) with ESMTP id C0B2813C4B7 for ; Fri, 28 Sep 2007 19:25:09 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay02.kiev.sovam.com ([62.64.120.197]) by gnome.kiev.sovam.com with esmtp (Exim 4.67 (FreeBSD)) (envelope-from ) id 1IbLSW-0006m9-Bk for freebsd-current@freebsd.org; Fri, 28 Sep 2007 22:25:08 +0300 Received: from [212.82.216.226] (helo=deviant.kiev.zoral.com.ua) by relay02.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1IbLSU-000MV4-0k for freebsd-current@freebsd.org; Fri, 28 Sep 2007 22:25:07 +0300 Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.1/8.14.1) with ESMTP id l8SJP2GZ061301; Fri, 28 Sep 2007 22:25:02 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.1/8.14.1/Submit) id l8SJP2KT061300; Fri, 28 Sep 2007 22:25:02 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 28 Sep 2007 22:25:02 +0300 From: Kostik Belousov To: Chris Message-ID: <20070928192502.GU87366@deviant.kiev.zoral.com.ua> References: <3aaaa3a0709281118k7fa35133wdc908a025180e6e0@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EDT6MSV0B3GxyNyZ" Content-Disposition: inline In-Reply-To: <3aaaa3a0709281118k7fa35133wdc908a025180e6e0@mail.gmail.com> User-Agent: Mutt/1.4.2.3i X-Scanner-Signature: 7155bbd8d023de41950ebecbe4708355 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 1523 [September 28 2007] X-SpamTest-Info: helo_type=3 X-SpamTest-Info: {received from trusted relay: not dialup} X-SpamTest-Method: none X-SpamTest-Method: Local Lists X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release Cc: FreeBSD Current Subject: Re: problems with 7.0 kernel page faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 19:25:10 -0000 --EDT6MSV0B3GxyNyZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 28, 2007 at 07:18:25PM +0100, Chris wrote: > Submitted 2 PRs for 7.0 we only been using it for a few hours and have > had repeated kernel page faults crashing the system so was > dissapointed considering this is said to be nearly ready for release. >=20 > PRs are >=20 > 116719 and 116720 in misc. >=20 > First one was caused by simply running reboot, I recompiled world with > -O which seems to prevent this occuring. >=20 > Second one is when running 'killall watch' with at least 1 watch > process running this causes the kernel to page fault and this happens > even when compiled with -O. >=20 > If anyone is interested can post logs dmesg etc. and have a kernel > dump for the 2nd problem. First one will never be diagnosed since you provided no useful information. I am interested in second one. Please, send the "bt full" backtrace from the coredump. I tried to reproduce it locally with snoopper attached to both ttyv and pseudoterminal, but cannot. When reporting the kernel problems, following guidelines in the developer handbook would facilitate faster responses. --EDT6MSV0B3GxyNyZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFG/VUNC3+MBN1Mb4gRAiebAKDoizJOReWBRu2e/2taAtSiqM4QmACg7S9v kpARo/HbBFw9W0zuxeh+PL8= =OnYt -----END PGP SIGNATURE----- --EDT6MSV0B3GxyNyZ-- From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 19:31:06 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7AD5116A46B for ; Fri, 28 Sep 2007 19:31:06 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id BBFCB13C459 for ; Fri, 28 Sep 2007 19:31:05 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 28 Sep 2007 19:31:04 -0000 Received: from h081217094222.dyn.cm.kabsi.at (EHLO taxman.pepperland) [81.217.94.222] by mail.gmx.net (mp033) with SMTP; 28 Sep 2007 21:31:04 +0200 X-Authenticated: #16703784 X-Provags-ID: V01U2FsdGVkX1864G4wt2o6HCmGlQagtelLQi+t4zqcmIVX3UMEAb DjrICtikwJ5V7c From: Stefan Ehmann To: freebsd-current@freebsd.org Date: Fri, 28 Sep 2007 21:31:06 +0200 User-Agent: KMail/1.9.7 References: <200709282051.41459.shoesoft@gmx.net> In-Reply-To: <200709282051.41459.shoesoft@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709282131.06320.shoesoft@gmx.net> X-Y-GMX-Trusted: 0 Subject: Re: installworld error: uuencode not found X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 19:31:06 -0000 On Friday 28 September 2007 20:51:40 Stefan Ehmann wrote: > With fresh sources I get this: > > ===> share/syscons/scrnmaps (install) > ./armscii8-2haik8.mk armscii8-2haik8.tmp > uuencode armscii8-2haik8.tmp armscii8-2haik8 > armscii8-2haik8.scm > uuencode: not found > *** Error code 127 > > Stop in /usr/src/share/syscons/scrnmaps. > > > Anyone else seeing this or is the error on my end? Now I remembered that the clock was off by two hours for some reason. I adjusted it during buildworld. This must have screwed make and therefor causing these errors. Sorry for the noise. From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 21:20:36 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5071B16A46D; Fri, 28 Sep 2007 21:20:36 +0000 (UTC) (envelope-from jpedras+freebsd-current@webvolution.net) Received: from mail.portrait.com (mail.portrait.com [64.171.32.41]) by mx1.freebsd.org (Postfix) with ESMTP id 2553313C478; Fri, 28 Sep 2007 21:20:35 +0000 (UTC) (envelope-from jpedras+freebsd-current@webvolution.net) Received: from joao-pedras-computer-2.local (beastie.webvolution.net [64.174.136.225]) (authenticated bits=0) by mail.portrait.com (8.13.1/8.13.1) with ESMTP id l8SLKKWA036547 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Sep 2007 14:20:25 -0700 (PDT) (envelope-from jpedras+freebsd-current@webvolution.net) Message-ID: <46FD700C.3080804@webvolution.net> Date: Fri, 28 Sep 2007 14:20:12 -0700 From: Joao Pedras User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org, Attilio Rao References: <46FA0C14.10201@webvolution.net> <46FADB35.2090708@FreeBSD.org> <46FC2AA7.2040308@webvolution.net> <46FC2C85.4080600@FreeBSD.org> <46FC8EEE.5080908@webvolution.net> <3bbf2fe10709280337n1be084b3qf1ef7fc94889592b@mail.gmail.com> <46FD2ABA.5040307@webvolution.net> In-Reply-To: <46FD2ABA.5040307@webvolution.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.1 required=3.0 tests=FORGED_RCVD_HELO X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on mail.portrait.com Cc: Subject: Re: lock up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 21:20:36 -0000 Joao Pedras wrote: > Attilio Rao wrote: >> 2007/9/28, Joao Pedras : >>> Thank you for your help Kris. I am not very familiar with these tasks. >>> >>> I got the 'alltrace' and I also saved a crash dump. >>> The session output is here http://pedras.webvolution.net/s2932-9.txt. >>> >>> I was able to reproduce the issue on a similar system (a vanilla Tyan >>> S2932, one SATA disc only) and it exhibits the exact same problem. >> Hello, >> when you updated CURRENT last time? >> csjp committed a fix which should have resolved the rtfree reference >> mismatching problem like a week ago. >> >> Can you try if a stock, fresh cvsuped current exposes the same problem for you? >> >> Thanks, >> Attilio >> >> > > Attilio, > > I noticed that rtfree fix. This system is running code from 9-25. I will > sup it to today's code anyway. > > Again, it is GENERIC amd64 (SCHED_4BSD). I have another one with ULE and > I will give it a try today. > With today's (this morning's) source the issue occurs and the rtfree warnings are visible. I have condensed the info here http://pedras.webvolution.net/Tyan_S2932/FreeBSD-7/. Thank you for the help. From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 21:44:21 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5FA7E16A469; Fri, 28 Sep 2007 21:44:21 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 1A43E13C45D; Fri, 28 Sep 2007 21:44:19 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46FD75B6.7050709@FreeBSD.org> Date: Fri, 28 Sep 2007 23:44:22 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Craig Boston References: <20070928133452.GA52277@nowhere> In-Reply-To: <20070928133452.GA52277@nowhere> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Darren Reed , freebsd-current@freebsd.org, Larry Rosenman Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 21:44:21 -0000 Craig Boston wrote: > On Mon, Sep 24, 2007 at 09:28:36AM -0600, Scott Long wrote: >> You're all missing the point, I hate to say. What happened is that a >> change was made recently to more accurately account for allocated >> memory. Now people are getting kmem_map_too_small panics that weren't >> getting them before. So while the accounting is now more accurate, >> the outcome is actually harmful. That needs to be fixed before the >> release. > > Agreed. A month ago I had zfs running perfectly on many different i386 > machines (albeit with some tweaking to kernel parameters). With a > week-old current, it always panics sooner or later now, no matter how > low I set the ARC cache size or maxvnodes or how much I pump into > kmem_size. > > Now kmem_map panics are being reported on amd64, which was pretty much > unheard of before. FYI, no :) Kris From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 22:23:10 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6BE8916A41A for ; Fri, 28 Sep 2007 22:23:10 +0000 (UTC) (envelope-from ss.alert@online.no) Received: from mail47.e.nsc.no (mail47.e.nsc.no [193.213.115.47]) by mx1.freebsd.org (Postfix) with ESMTP id EA77013C457 for ; Fri, 28 Sep 2007 22:23:09 +0000 (UTC) (envelope-from ss.alert@online.no) Received: from [192.168.1.222] (ti0034a340-0733.bb.online.no [88.90.2.221]) by mail47.nsc.no (8.13.8/8.13.5) with ESMTP id l8SMN7k0002229 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for ; Sat, 29 Sep 2007 00:23:07 +0200 (MEST) Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: 7bit Message-Id: <92E55685-5D87-48F5-BB93-C9AE66DBA8BF@online.no> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-current@freebsd.org From: Sverre Svenningsen Date: Sat, 29 Sep 2007 00:23:05 +0200 X-Mailer: Apple Mail (2.752.3) Subject: Automatic ZFS snapshots? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 22:23:10 -0000 Sun has created a utility that lets you manage automated snaphots, as detailed here: http://blogs.sun.com/timf/entry/ zfs_automatic_snapshots_now_with Has anyone looked into a method to accomplish something similar on the FreeBSD port? A lot of the value in snaphots lie in the .zfs directories where users can fish out backups of their damaged or deleted files without help from an admin - but for this to work there has to be a system in place that makes new snaphots on a schedule, and also purges the snaphots that have become too old. This is probably going to require some fancy scripting, so i'm curious if anyone has made a set of scripts to do it on freebsd yet? It's probably not possible to port over this thing sun made since it's a plugin for their solaris service control system... -Sverre From owner-freebsd-current@FreeBSD.ORG Sat Sep 29 02:51:00 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0DD1D16A419 for ; Sat, 29 Sep 2007 02:51:00 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.224]) by mx1.freebsd.org (Postfix) with ESMTP id B56CD13C4B0 for ; Sat, 29 Sep 2007 02:50:59 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so1935309nzf for ; Fri, 28 Sep 2007 19:50:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:date:to:subject:message-id:mime-version:content-type:content-disposition:user-agent:organization:x-operation-sytem:from; bh=YlRtpygkwM5kj+y0CJj53ldeZmhCS/V+VrF6Wro+7F8=; b=dToLRCZlT9Q/0/sVZqttfjvsU+6OhdY6V+eX67ufpEL5jjZHs73Aj+3UCmQSsB8Ghccvui5cGSroD+1kK47/MgBbSJzXQ0Iho6qDwC1Nf4MVOKlwJMiffdobgcHRmLvbJrvzGEH2dIER6fG15OBiGmeDH/i9WvVtOIDxjxLBgZ4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:to:subject:message-id:mime-version:content-type:content-disposition:user-agent:organization:x-operation-sytem:from; b=jtB4fpXcySID42XICdQkAhY8XhE7VbiRaAkbIb7yN5jfsmMxALhn0lAAiYpTYXYEE9TX9R7azqnFzhUCbdAToyoXWNPCVmK4gjR3/S2XTX5yf0WwXll9FDSyZ/DCnF+luZhe5Rkys5naRgPglZnpEmZKUXMq8xCaax99+JBJoO4= Received: by 10.115.106.7 with SMTP id i7mr1313132wam.1191034257880; Fri, 28 Sep 2007 19:50:57 -0700 (PDT) Received: from freebsd.weongyo.org ( [211.53.35.67]) by mx.google.com with ESMTPS id n9sm4792486wag.2007.09.28.19.50.55 (version=SSLv3 cipher=OTHER); Fri, 28 Sep 2007 19:50:56 -0700 (PDT) Received: by freebsd.weongyo.org (sSMTP sendmail emulation); Sat, 29 Sep 2007 11:50:31 +0900 Date: Sat, 29 Sep 2007 11:50:30 +0900 To: freebsd-current@freebsd.org Message-ID: <20070929025030.GA66680@freebsd.weongyo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD From: Weongyo Jeong Subject: atheros panic (D-Link DWL-G520) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 02:51:00 -0000 My device is D-Link DWL-G520 and the device encountered a panic when I did `ifconfig ath0 up'. The kernel was cvs-uped yesterday. The following are the panic message: hostap# ifconfig ath0 up ath0: ath_chan_set: unable to reset channel 1 (2412 Mhz, flags 0x480 hal flags 0xc0) hostap# ath0: ath_chan_set: unable to reset channel 11 (2462 Mhz, flags 0x480 hal flags 0xc0) ath0: ath_chan_set: unable to reset channel 13 (2472 Mhz, flags 0x480 hal flags 0xc0) ath0: ath_chan_set: unable to reset channel 3 (2422 Mhz, flags 0x480 hal flags 0xc0) ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz, flags 0x480 hal flags 0xc0) ath0: hardware error; resetting ath0: 0x00080000 0x00000000 0x00000000, 0x00010000 0x00000000 0x00000000 Fatal trap 18: integer divide fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0xc09f0d25 stack pointer = 0x28:0xcbd3acd8 frame pointer = 0x28:0xcbd3acd8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, IOPL = 0 current process = 11 (idle: cpu0) [thread pid 11 tid 100004 ] Stopped at cpu_idle_default+0x5: popl %ebp db> bt Tracing pid 11 tid 100004 td 0xc20f7630 cpu_idle_default(cbd3acf8,c0769e17,c0bad610,2,c0a9a19d,...) at cpu_idle_default+0x5 cpu_idle(c0bad610,2,c0a9a19d,562,cbd3ad24,...) at cpu_idle+0x28 sched_idletd(0,cbd3ad38,c0a9515d,314,c20f6aa0,...) at sched_idletd+0x37 fork_exit(c0769de0,0,cbd3ad38) at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xcbd3ad70, ebp = 0 --- db> And the below informations are device informations: hostap# uname -a FreeBSD hostap 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Thu Sep 27 02:43:04 KST 2007 root@rumhostap:/usr/obj/usr/src/sys/GENERIC i386 hostap# pciconf -lcv ath0@pci2:2:0: class=0x020000 card=0x3a131186 chip=0x0013168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5212, AR5213 802.11a/b/g Wireless Adapter' class = network subclass = ethernet cap 01[44] = powerspec 2 supports D0 D3 current D0 hostap# sysctl -a | grep dev.ath.0 dev.ath.0.%desc: Atheros 5212 dev.ath.0.%driver: ath dev.ath.0.%location: slot=2 function=0 dev.ath.0.%pnpinfo: vendor=0x168c device=0x0013 subvendor=0x1186 subdevice=0x3a13 class=0x020000 dev.ath.0.%parent: pci2 dev.ath.0.smoothing_rate: 95 dev.ath.0.sample_rate: 10 dev.ath.0.countrycode: 0 dev.ath.0.regdomain: 48 dev.ath.0.slottime: 9 dev.ath.0.acktimeout: 96 dev.ath.0.ctstimeout: 96 dev.ath.0.softled: 0 dev.ath.0.ledpin: 0 dev.ath.0.ledon: 0 dev.ath.0.ledidle: 2700 dev.ath.0.txantenna: 0 dev.ath.0.rxantenna: 0 dev.ath.0.diversity: 0 dev.ath.0.txintrperiod: 5 dev.ath.0.diag: 0 dev.ath.0.tpscale: 0 dev.ath.0.tpc: 0 dev.ath.0.tpack: 63 dev.ath.0.tpcts: 63 dev.ath.0.fftxqmin: 2 dev.ath.0.fftxqmax: 50 dev.ath.0.monpass: 24 hostap# ifconfig ath0 list channel Channel 1 : 2412 Mhz 11g Channel 8 : 2447 Mhz 11g Channel 2 : 2417 Mhz 11g Channel 9 : 2452 Mhz 11g Channel 3 : 2422 Mhz 11g Channel 10 : 2457 Mhz 11g Channel 4 : 2427 Mhz 11g Channel 11 : 2462 Mhz 11g Channel 5 : 2432 Mhz 11g Channel 12 : 2467 Mhz 11g Channel 6 : 2437 Mhz 11g Turbo Channel 13 : 2472 Mhz 11g Channel 7 : 2442 Mhz 11g stap# /sbin/ifconfig ath0: flags=8802 metric 0 mtu 1500 ether 00:1b:11:1a:ee:32 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 1 (2412 Mhz 11b) authmode OPEN privacy OFF txpowmax 100 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11b 14 roam:rate11b 1 burst hostap# dmesg | grep -i ath ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: mem 0xe7000000-0xe700ffff irq 11 at device 2.0 on pci2 ath0: [ITHREAD] ath0: using obsoleted if_watchdog interface ath0: Ethernet address: 00:1b:11:1a:ee:32 ath0: mac 7.9 phy 4.5 radio 5.6 From owner-freebsd-current@FreeBSD.ORG Sat Sep 29 03:25:28 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72D4416A417 for ; Sat, 29 Sep 2007 03:25:28 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 2993913C459 for ; Sat, 29 Sep 2007 03:25:27 +0000 (UTC) (envelope-from sam@errno.com) Received: from sam-lefflers-powerbook-g4-15.local ([10.0.0.178]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l8T3PRv5017675 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Sep 2007 20:25:27 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <46FDC5A4.5060403@errno.com> Date: Fri, 28 Sep 2007 20:25:24 -0700 From: Sam Leffler Organization: Errno Consulting User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Weongyo Jeong References: <20070929025030.GA66680@freebsd.weongyo.org> In-Reply-To: <20070929025030.GA66680@freebsd.weongyo.org> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-DCC-Rhyolite-Metrics: o.com; whitelist Cc: freebsd-current@freebsd.org Subject: Re: atheros panic (D-Link DWL-G520) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 03:25:28 -0000 Weongyo Jeong wrote: > My device is D-Link DWL-G520 and the device encountered a panic when I > did `ifconfig ath0 up'. The kernel was cvs-uped yesterday. The following > are the panic message: > > hostap# ifconfig ath0 up > ath0: ath_chan_set: unable to reset channel 1 (2412 Mhz, flags 0x480 hal > flags 0xc0) > hostap# ath0: ath_chan_set: unable to reset channel 11 (2462 Mhz, flags > 0x480 hal flags 0xc0) > ath0: ath_chan_set: unable to reset channel 13 (2472 Mhz, flags 0x480 > hal flags 0xc0) > ath0: ath_chan_set: unable to reset channel 3 (2422 Mhz, flags 0x480 hal > flags 0xc0) > ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz, flags 0x480 hal > flags 0xc0) > ath0: hardware error; resetting > ath0: 0x00080000 0x00000000 0x00000000, 0x00010000 0x00000000 0x00000000 > > > Fatal trap 18: integer divide fault while in kernel mode > cpuid = 0; apic id = 00 > instruction pointer = 0x20:0xc09f0d25 > stack pointer = 0x28:0xcbd3acd8 > frame pointer = 0x28:0xcbd3acd8 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, IOPL = 0 > current process = 11 (idle: cpu0) > [thread pid 11 tid 100004 ] > Stopped at cpu_idle_default+0x5: popl %ebp > db> bt > Tracing pid 11 tid 100004 td 0xc20f7630 > cpu_idle_default(cbd3acf8,c0769e17,c0bad610,2,c0a9a19d,...) at > cpu_idle_default+0x5 > cpu_idle(c0bad610,2,c0a9a19d,562,cbd3ad24,...) at cpu_idle+0x28 > sched_idletd(0,cbd3ad38,c0a9515d,314,c20f6aa0,...) at sched_idletd+0x37 > fork_exit(c0769de0,0,cbd3ad38) at fork_exit+0xb8 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0, eip = 0, esp = 0xcbd3ad70, ebp = 0 --- > db> > > > And the below informations are device informations: > > hostap# uname -a > FreeBSD hostap 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Thu Sep 27 02:43:04 > KST 2007 root@rumhostap:/usr/obj/usr/src/sys/GENERIC i386 > > hostap# pciconf -lcv > ath0@pci2:2:0: class=0x020000 card=0x3a131186 chip=0x0013168c rev=0x01 > hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR5212, AR5213 802.11a/b/g Wireless Adapter' > class = network > subclass = ethernet > cap 01[44] = powerspec 2 supports D0 D3 current D0 > > hostap# sysctl -a | grep dev.ath.0 > dev.ath.0.%desc: Atheros 5212 > dev.ath.0.%driver: ath > dev.ath.0.%location: slot=2 function=0 > dev.ath.0.%pnpinfo: vendor=0x168c device=0x0013 subvendor=0x1186 > subdevice=0x3a13 class=0x020000 > dev.ath.0.%parent: pci2 > dev.ath.0.smoothing_rate: 95 > dev.ath.0.sample_rate: 10 > dev.ath.0.countrycode: 0 > dev.ath.0.regdomain: 48 > dev.ath.0.slottime: 9 > dev.ath.0.acktimeout: 96 > dev.ath.0.ctstimeout: 96 > dev.ath.0.softled: 0 > dev.ath.0.ledpin: 0 > dev.ath.0.ledon: 0 > dev.ath.0.ledidle: 2700 > dev.ath.0.txantenna: 0 > dev.ath.0.rxantenna: 0 > dev.ath.0.diversity: 0 > dev.ath.0.txintrperiod: 5 > dev.ath.0.diag: 0 > dev.ath.0.tpscale: 0 > dev.ath.0.tpc: 0 > dev.ath.0.tpack: 63 > dev.ath.0.tpcts: 63 > dev.ath.0.fftxqmin: 2 > dev.ath.0.fftxqmax: 50 > dev.ath.0.monpass: 24 > > hostap# ifconfig ath0 list channel > Channel 1 : 2412 Mhz 11g Channel 8 : 2447 Mhz 11g > Channel 2 : 2417 Mhz 11g Channel 9 : 2452 Mhz 11g > Channel 3 : 2422 Mhz 11g Channel 10 : 2457 Mhz 11g > Channel 4 : 2427 Mhz 11g Channel 11 : 2462 Mhz 11g > Channel 5 : 2432 Mhz 11g Channel 12 : 2467 Mhz 11g > Channel 6 : 2437 Mhz 11g Turbo Channel 13 : 2472 Mhz 11g > Channel 7 : 2442 Mhz 11g > > stap# /sbin/ifconfig > ath0: flags=8802 metric 0 mtu 1500 > ether 00:1b:11:1a:ee:32 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > ssid "" channel 1 (2412 Mhz 11b) > authmode OPEN privacy OFF txpowmax 100 bmiss 7 scanvalid 60 bgscan > bgscanintvl 300 bgscanidle 250 roam:rssi11b 14 roam:rate11b 1 burst > > hostap# dmesg | grep -i ath > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > ath0: mem 0xe7000000-0xe700ffff irq 11 at device 2.0 on pci2 > ath0: [ITHREAD] > ath0: using obsoleted if_watchdog interface > ath0: Ethernet address: 00:1b:11:1a:ee:32 > ath0: mac 7.9 phy 4.5 radio 5.6 Unfortunately the value of status isn't printed when the ath_hal_reset calls fail. Please add that to the printf in ath_chan_set. Not sure where the divide fault comes from; the stack trace doesn't provide much help. If you don't have INVARIANTS enabled you should do that in case it catches what's going on before the panic happens. Sam From owner-freebsd-current@FreeBSD.ORG Sat Sep 29 04:57:37 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1836516A420 for ; Sat, 29 Sep 2007 04:57:37 +0000 (UTC) (envelope-from freebsd@bitfreak.org) Received: from mail.twinthornes.com (mail.twinthornes.com [65.75.198.147]) by mx1.freebsd.org (Postfix) with ESMTP id E490A13C47E for ; Sat, 29 Sep 2007 04:57:36 +0000 (UTC) (envelope-from freebsd@bitfreak.org) Received: from [10.9.70.100] (pool-71-117-232-141.ptldor.fios.verizon.net [71.117.232.141]) by mail.twinthornes.com (Postfix) with ESMTP id B9B088A for ; Fri, 28 Sep 2007 21:25:11 -0700 (PDT) Message-ID: <46FDD3AB.3050305@bitfreak.org> Date: Fri, 28 Sep 2007 21:25:15 -0700 From: Darren Pilgrim User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <46FCB7B7.9010301@FreeBSD.org> <20070928083322.GA17225@eos.sc1.parodius.com> <46FD1631.9020708@evilphi.com> <20070928184659.GB57646@cicely12.cicely.de> In-Reply-To: <20070928184659.GB57646@cicely12.cicely.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Non-sequential AP starts [Was: Re: 8-core server] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 04:57:37 -0000 Bernd Walter wrote: > On Fri, Sep 28, 2007 at 07:56:49AM -0700, Darren Pilgrim wrote: >> Jeremy Chadwick wrote: >>> I think what you're not noticing is that the cores are being launched in >>> non-sequential order. 1, 2, 3, 4, 7, 5, 6. This isn't a problem. >> Why they wouldn't be launched sequentially? > > First SMP rule: > Don't expect a specific execution order from things running parallel. > > I don't know the code, but would assume that they are started > sequentially and each core prints it's own line, so they get > disordered. This question bugged me long enough for me to go read some source to find the answer, but I ended up with more questions. I guess that's what I get for reading boot code. :) I know it's basically just a race condition, but where does the race actually occur? In each core's execution of startup instructions leading up to the printf() in init_secondary() or in the assignment of the value returned by PCPU_GET(cpudid)? Where is the data behind PCPU_GET() anyway? I couldn't find it. Is AP launch order random or are there CPU characteristics that result in reproducible non-sequential ordering? From owner-freebsd-current@FreeBSD.ORG Sat Sep 29 06:58:01 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A8C5A16A417 for ; Sat, 29 Sep 2007 06:58:01 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.178]) by mx1.freebsd.org (Postfix) with ESMTP id 3818013C44B for ; Sat, 29 Sep 2007 06:58:01 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so3887715waf for ; Fri, 28 Sep 2007 23:58:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:date:to:cc:subject:message-id:references:mime-version:content-type:content-disposition:in-reply-to:user-agent:organization:x-operation-sytem:from; bh=1EXYp4PeLFGVkt0NRyTUr6r4rsHs+JEbwEPFbKnv7hQ=; b=eO03Sbs1OzzgTsxNAtJUf41pkNFGQCw0YKq/vCPiN2Rj/SzlwhPX0e5TUhZdHaWD9vZyVdPYFJ0vR0YOBoMIwi7G0ryqnWusiJ1aeReAgL04IIBvdfYcHhveCAJJZ68YNIk8l53azYFn8iiYHjCGB4q7XrsZevpql39mE6alLT4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:to:cc:subject:message-id:references:mime-version:content-type:content-disposition:in-reply-to:user-agent:organization:x-operation-sytem:from; b=Y4XgkddBx8baYGUI3h6l9kQeMzn8ksnJV4RbFQbLJu8Pa8wyDndAYJV/659XbmHLzHve0z0QFeVkbsQ79vrIXJpy9fKMm0Uj0vk79+LMKOHa+v0bsr0BJgIxof24P9UEKIFxMxuunn0aGWC5NRl8fytvFVz23etVoRveiZM11pk= Received: by 10.114.135.1 with SMTP id i1mr917400wad.1191049080722; Fri, 28 Sep 2007 23:58:00 -0700 (PDT) Received: from freebsd.weongyo.org ( [211.53.35.67]) by mx.google.com with ESMTPS id v35sm7001052wah.2007.09.28.23.57.57 (version=SSLv3 cipher=OTHER); Fri, 28 Sep 2007 23:57:59 -0700 (PDT) Received: by freebsd.weongyo.org (sSMTP sendmail emulation); Sat, 29 Sep 2007 15:57:33 +0900 Date: Sat, 29 Sep 2007 15:57:33 +0900 To: Sam Leffler Message-ID: <20070929065733.GB66680@freebsd.weongyo.org> References: <20070929025030.GA66680@freebsd.weongyo.org> <46FDC5A4.5060403@errno.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46FDC5A4.5060403@errno.com> User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD From: Weongyo Jeong Cc: freebsd-current@freebsd.org Subject: Re: atheros panic (D-Link DWL-G520) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 06:58:01 -0000 On Fri, Sep 28, 2007 at 08:25:24PM -0700, Sam Leffler wrote: > Weongyo Jeong wrote: > > My device is D-Link DWL-G520 and the device encountered a panic when I > > did `ifconfig ath0 up'. The kernel was cvs-uped yesterday. The following > > are the panic message: > > > > hostap# ifconfig ath0 up > > ath0: ath_chan_set: unable to reset channel 1 (2412 Mhz, flags 0x480 hal > > flags 0xc0) > > hostap# ath0: ath_chan_set: unable to reset channel 11 (2462 Mhz, flags > > 0x480 hal flags 0xc0) > > ath0: ath_chan_set: unable to reset channel 13 (2472 Mhz, flags 0x480 > > hal flags 0xc0) > > ath0: ath_chan_set: unable to reset channel 3 (2422 Mhz, flags 0x480 hal > > flags 0xc0) > > ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz, flags 0x480 hal > > flags 0xc0) > > ath0: hardware error; resetting > > ath0: 0x00080000 0x00000000 0x00000000, 0x00010000 0x00000000 0x00000000 > > > > > > Fatal trap 18: integer divide fault while in kernel mode > > cpuid = 0; apic id = 00 > > instruction pointer = 0x20:0xc09f0d25 > > stack pointer = 0x28:0xcbd3acd8 > > frame pointer = 0x28:0xcbd3acd8 > > code segment = base 0x0, limit 0xfffff, type 0x1b > > = DPL 0, pres 1, def32 1, gran 1 > > processor eflags = interrupt enabled, IOPL = 0 > > current process = 11 (idle: cpu0) > > [thread pid 11 tid 100004 ] > > Stopped at cpu_idle_default+0x5: popl %ebp > > db> bt > > Tracing pid 11 tid 100004 td 0xc20f7630 > > cpu_idle_default(cbd3acf8,c0769e17,c0bad610,2,c0a9a19d,...) at > > cpu_idle_default+0x5 > > cpu_idle(c0bad610,2,c0a9a19d,562,cbd3ad24,...) at cpu_idle+0x28 > > sched_idletd(0,cbd3ad38,c0a9515d,314,c20f6aa0,...) at sched_idletd+0x37 > > fork_exit(c0769de0,0,cbd3ad38) at fork_exit+0xb8 > > fork_trampoline() at fork_trampoline+0x8 > > --- trap 0, eip = 0, esp = 0xcbd3ad70, ebp = 0 --- > > db> > > > > > > And the below informations are device informations: > > > > hostap# uname -a > > FreeBSD hostap 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Thu Sep 27 02:43:04 > > KST 2007 root@rumhostap:/usr/obj/usr/src/sys/GENERIC i386 > > > > hostap# pciconf -lcv > > ath0@pci2:2:0: class=0x020000 card=0x3a131186 chip=0x0013168c rev=0x01 > > hdr=0x00 > > vendor = 'Atheros Communications Inc.' > > device = 'AR5212, AR5213 802.11a/b/g Wireless Adapter' > > class = network > > subclass = ethernet > > cap 01[44] = powerspec 2 supports D0 D3 current D0 > > > > hostap# sysctl -a | grep dev.ath.0 > > dev.ath.0.%desc: Atheros 5212 > > dev.ath.0.%driver: ath > > dev.ath.0.%location: slot=2 function=0 > > dev.ath.0.%pnpinfo: vendor=0x168c device=0x0013 subvendor=0x1186 > > subdevice=0x3a13 class=0x020000 > > dev.ath.0.%parent: pci2 > > dev.ath.0.smoothing_rate: 95 > > dev.ath.0.sample_rate: 10 > > dev.ath.0.countrycode: 0 > > dev.ath.0.regdomain: 48 > > dev.ath.0.slottime: 9 > > dev.ath.0.acktimeout: 96 > > dev.ath.0.ctstimeout: 96 > > dev.ath.0.softled: 0 > > dev.ath.0.ledpin: 0 > > dev.ath.0.ledon: 0 > > dev.ath.0.ledidle: 2700 > > dev.ath.0.txantenna: 0 > > dev.ath.0.rxantenna: 0 > > dev.ath.0.diversity: 0 > > dev.ath.0.txintrperiod: 5 > > dev.ath.0.diag: 0 > > dev.ath.0.tpscale: 0 > > dev.ath.0.tpc: 0 > > dev.ath.0.tpack: 63 > > dev.ath.0.tpcts: 63 > > dev.ath.0.fftxqmin: 2 > > dev.ath.0.fftxqmax: 50 > > dev.ath.0.monpass: 24 > > > > hostap# ifconfig ath0 list channel > > Channel 1 : 2412 Mhz 11g Channel 8 : 2447 Mhz 11g > > Channel 2 : 2417 Mhz 11g Channel 9 : 2452 Mhz 11g > > Channel 3 : 2422 Mhz 11g Channel 10 : 2457 Mhz 11g > > Channel 4 : 2427 Mhz 11g Channel 11 : 2462 Mhz 11g > > Channel 5 : 2432 Mhz 11g Channel 12 : 2467 Mhz 11g > > Channel 6 : 2437 Mhz 11g Turbo Channel 13 : 2472 Mhz 11g > > Channel 7 : 2442 Mhz 11g > > > > stap# /sbin/ifconfig > > ath0: flags=8802 metric 0 mtu 1500 > > ether 00:1b:11:1a:ee:32 > > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > > status: no carrier > > ssid "" channel 1 (2412 Mhz 11b) > > authmode OPEN privacy OFF txpowmax 100 bmiss 7 scanvalid 60 bgscan > > bgscanintvl 300 bgscanidle 250 roam:rssi11b 14 roam:rate11b 1 burst > > > > hostap# dmesg | grep -i ath > > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > > ath0: mem 0xe7000000-0xe700ffff irq 11 at device 2.0 on pci2 > > ath0: [ITHREAD] > > ath0: using obsoleted if_watchdog interface > > ath0: Ethernet address: 00:1b:11:1a:ee:32 > > ath0: mac 7.9 phy 4.5 radio 5.6 > > Unfortunately the value of status isn't printed when the ath_hal_reset > calls fail. Please add that to the printf in ath_chan_set. > > Not sure where the divide fault comes from; the stack trace doesn't > provide much help. If you don't have INVARIANTS enabled you should do > that in case it catches what's going on before the panic happens. The status value which is returned by ath_hal_reset() (if_ath.c 5043 line) was 3 (HAL_EIO) and the kernel was compiled with INVARIANTS. Regards, Weongyo Jeong From owner-freebsd-current@FreeBSD.ORG Sat Sep 29 07:41:46 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F08F516A417 for ; Sat, 29 Sep 2007 07:41:46 +0000 (UTC) (envelope-from rmtodd@ichotolot.servalan.com) Received: from mx2.synetsystems.com (mx2.synetsystems.com [76.10.206.15]) by mx1.freebsd.org (Postfix) with ESMTP id C3D8413C461 for ; Sat, 29 Sep 2007 07:41:46 +0000 (UTC) (envelope-from rmtodd@ichotolot.servalan.com) Received: by mx2.synetsystems.com (Postfix, from userid 66) id 1B85C544; Sat, 29 Sep 2007 03:15:18 -0400 (EDT) Received: from rmtodd by servalan.servalan.com with local (Exim 4.66 (FreeBSD)) (envelope-from ) id 1IbVuG-000D9t-23 for freebsd-current@freebsd.org; Sat, 29 Sep 2007 01:34:28 -0500 To: freebsd-current@freebsd.org References: <92E55685-5D87-48F5-BB93-C9AE66DBA8BF@online.no> From: Richard Todd Date: Sat, 29 Sep 2007 01:34:27 -0500 In-Reply-To: (Sverre Svenningsen's message of "Sat, 29 Sep 2007 00:23:05 +0200") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.20 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Automatic ZFS snapshots? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 07:41:47 -0000 Sverre Svenningsen writes: > Sun has created a utility that lets you manage automated snaphots, as > detailed here: http://blogs.sun.com/timf/entry/ > zfs_automatic_snapshots_now_with > > Has anyone looked into a method to accomplish something similar on > the FreeBSD port? > A lot of the value in snaphots lie in the .zfs directories where > users can fish out backups of their damaged or deleted files without > help from an admin - but for this to work there has to be a system in > place that makes new snaphots on a schedule, and also purges the > snaphots that have become too old. Well, if you just want regular creation of snapshots and removal of old snapshots on a specified schedule, /usr/ports/sysutils/freebsd-snapshot might be a good place to start hacking, as it has a set of scripts that do this for UFS snapshots. From owner-freebsd-current@FreeBSD.ORG Sat Sep 29 11:45:05 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1623716A41A for ; Sat, 29 Sep 2007 11:45:05 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72]) by mx1.freebsd.org (Postfix) with ESMTP id E846413C45A for ; Sat, 29 Sep 2007 11:45:04 +0000 (UTC) (envelope-from rrs@cisco.com) X-IronPort-AV: E=Sophos;i="4.21,212,1188802800"; d="scan'208";a="529608884" Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-3.cisco.com with ESMTP; 29 Sep 2007 04:45:04 -0700 Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l8TBj4al028147 for ; Sat, 29 Sep 2007 04:45:04 -0700 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l8TBj41l022803 for ; Sat, 29 Sep 2007 11:45:04 GMT Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 29 Sep 2007 04:45:04 -0700 Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 29 Sep 2007 04:45:04 -0700 Message-ID: <46FE3A98.10003@cisco.com> Date: Sat, 29 Sep 2007 07:44:24 -0400 From: Randall Stewart User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20070601 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 29 Sep 2007 11:45:04.0251 (UTC) FILETIME=[2CEEACB0:01C8028E] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1131; t=1191066304; x=1191930304; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rrs@cisco.com; z=From:=20Randall=20Stewart=20 |Subject:=20strange=20happenings=20in=20current |Sender:=20; bh=taEFSBWWBB8lTeKy+epza9SGoiBEulKA3x42MXWrNbw=; b=NeZCTtOGch/bQvMpgmjGzVmQ6rgYf/bbjOpGvAvCiQoUYsPQQke6ePDzgH1sJ/yhoCP5fP8/ qQWHPdF/NenVWogPYRe50du7AfSzr56AzKy0KOYJM/uGblYHwFQfdjws; Authentication-Results: sj-dkim-4; header.From=rrs@cisco.com; dkim=pass (sig from cisco.com/sjdkim4002 verified; ); Subject: strange happenings in current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 11:45:05 -0000 All: I just observed something strange.... my current was about a couple weeks old.. so I did the usual sup and update. Then I updated (as I usually do) just the kernel.. Rebuilt.. rebooted.. and all of a sudden a) I could not get to the console windows.. only X (ctl-alt-fx did not work. b) I got a very archaic looking welcome to X screen (I have things setup to use gnome-session).. c) When gnome started the clock failed.. and I could not bring up any xterms. Now I quickly rolled back to my kernel.old... but this is strange.. Now I am not sure.. is it because I really need to do a build/install world? (Which I don't do too often... due to the length of time needed on my laptop.. and the possible many 100's of packages to be rebuilt).. or is it something else... Maybe I will get one of my 160 gig drives out.. backup .. and then try the buildworld/install world and put in the new kernel and see if I have any problems... then again.. I leave again for S.J.. so maybe I won't :-0 R -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 803-317-4952 (cell) From owner-freebsd-current@FreeBSD.ORG Sat Sep 29 12:07:57 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1627316A417 for ; Sat, 29 Sep 2007 12:07:57 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.191]) by mx1.freebsd.org (Postfix) with ESMTP id 985CF13C465 for ; Sat, 29 Sep 2007 12:07:56 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: by mu-out-0910.google.com with SMTP id w9so4004966mue for ; Sat, 29 Sep 2007 05:07:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; bh=cSgPx0rBgkWYrdzivL76o3DvbJ1hkHEPJJVzrHAw/J4=; b=T/18+WY1M9R6KwxH8LePVmTF3ARAd/wtCu2iKLlgtoJePMcN6ApN3jJjyT2zTjdxXTh0wOBs++UsGjJHKkWoAUrrQAbFllYYN6w0unNQni4ZXG068BwhORtQKY48PFGktj+7Lsviz85U+y68KkewwOdAP+pQGmxss/PyNgfKJ5I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=V9CMO2RbFZbra9ZbLMeO/kK3h8iAxZ3/952uZnBo6VIvNdAuPC6WeFhG10F5q/DZdQ4EQldeaW51wNtTVDh7TFf1VAxUgmE10rBMkwUZlV4UwI6ohSbUmjkFUb/LbPE/4j+3G6pFmWT62qfdr3qxgTYu/vNYN3bzWtSx8S+zcUc= Received: by 10.78.142.14 with SMTP id p14mr734362hud.1191067674793; Sat, 29 Sep 2007 05:07:54 -0700 (PDT) Received: from ?192.168.0.50? ( [81.26.90.134]) by mx.google.com with ESMTPS id 30sm2864173hue.2007.09.29.05.07.51 (version=SSLv3 cipher=OTHER); Sat, 29 Sep 2007 05:07:53 -0700 (PDT) From: "Alex V. Petrov" To: freebsd-current@freebsd.org Date: Sat, 29 Sep 2007 20:07:46 +0800 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200709292007.46717.alexvpetrov@gmail.com> Subject: x11/nvidia-driver again X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 12:07:57 -0000 Hi All! I read "x11/nvidia-driver on Sept07 snapshot" in this maillist. I have it trouble too. Don't start "startx"/"startx -- -ignoreABI" TROUBLE: NVIDIA: could not open the device file /dev/nvidiactl (No such file or=20 directory). # kldstat Id Refs Address =C2=A0 =C2=A0Size =C2=A0 =C2=A0 Name =C2=A01 =C2=A0 24 0xc0400000 8dec6c =C2=A0 kernel =C2=A02 =C2=A0 =C2=A02 0xc0cdf000 28470 =C2=A0 =C2=A0linux.ko =C2=A03 =C2=A0 =C2=A01 0xc0d08000 6d98 =C2=A0 =C2=A0 snd_ich.ko =C2=A04 =C2=A0 =C2=A02 0xc0d0f000 4a5bc =C2=A0 =C2=A0sound.ko =C2=A05 =C2=A0 =C2=A05 0xc0d5a000 3948 =C2=A0 =C2=A0 libiconv.ko =C2=A06 =C2=A0 =C2=A01 0xc0d5e000 1db4 =C2=A0 =C2=A0 msdosfs_iconv.ko =C2=A07 =C2=A0 =C2=A01 0xc0d60000 1da0 =C2=A0 =C2=A0 cd9660_iconv.ko =C2=A08 =C2=A0 =C2=A01 0xc0d62000 1d74 =C2=A0 =C2=A0 ntfs_iconv.ko =C2=A09 =C2=A0 =C2=A02 0xc0d64000 cb90 =C2=A0 =C2=A0 ntfs.ko 10 =C2=A0 =C2=A01 0xc0d71000 1d5c =C2=A0 =C2=A0 udf_iconv.ko 11 =C2=A0 =C2=A02 0xc0d73000 7e20 =C2=A0 =C2=A0 udf.ko 12 =C2=A0 =C2=A01 0xc0d7b000 4c70 =C2=A0 =C2=A0 atapicam.ko 13 =C2=A0 =C2=A01 0xc0d80000 69154 =C2=A0 =C2=A0acpi.ko 14 =C2=A0 =C2=A01 0xc99da000 73b000 =C2=A0 nvidia.ko Conf my PC: =46reeBSD 7.0-CURRENT #11: Sat Sep 29 04:44:31 KRAST 2007 =C2=A0 =C2=A0 root@alex.:/usr/obj/usr/src/sys/ALEX Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ (2411.12-MHz 686-class= =20 CPU) =C2=A0 Origin =3D "AuthenticAMD" =C2=A0Id =3D 0x20fb1 =C2=A0Stepping =3D 1 =C2=A0 Cores per package: 2 real memory =C2=A0=3D 3221159936 (3071 MB) avail memory =3D 3146612736 (3000 MB) motherboard with Nvidia NForce 4 ultra videocard: vgapci0@pci5:0:0: =C2=A0 =C2=A0 =C2=A0 class=3D0x030000 card=3D0x221b1682 c= hip=3D0x029210de=20 rev=3D0xa1 hdr=3D0x00 =C2=A0 =C2=A0 vendor =C2=A0 =C2=A0 =3D 'Nvidia Corp' =C2=A0 =C2=A0 device =C2=A0 =C2=A0 =3D 'GeForce 7900 GS' =C2=A0 =C2=A0 class =C2=A0 =C2=A0 =C2=A0=3D display I do cvsup src and buil-install world regulary nvidia-driver rebuilded not once In 6.2 nvidia-driver worked fine. P.S. Sorry for bad english Best Regards! Alex V. Petrov From owner-freebsd-current@FreeBSD.ORG Sat Sep 29 12:59:41 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1BC216A419 for ; Sat, 29 Sep 2007 12:59:41 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 441C813C46A for ; Sat, 29 Sep 2007 12:59:40 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp121-45-181-219.lns11.adl2.internode.on.net [121.45.181.219]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id l8TCxXOv091111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 29 Sep 2007 22:29:37 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Sat, 29 Sep 2007 22:29:06 +0930 User-Agent: KMail/1.9.7 References: <200709292007.46717.alexvpetrov@gmail.com> In-Reply-To: <200709292007.46717.alexvpetrov@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1470452.PdvhidURrT"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200709292229.15297.doconnor@gsoft.com.au> X-Spam-Score: -2.312 () BAYES_00 X-Scanned-By: MIMEDefang 2.58 on 203.31.81.10 Cc: "Alex V. Petrov" Subject: Re: x11/nvidia-driver again X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 12:59:41 -0000 --nextPart1470452.PdvhidURrT Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sat, 29 Sep 2007, Alex V. Petrov wrote: > I read "x11/nvidia-driver on Sept07 snapshot" in this maillist. > I have it trouble too. > videocard: > vgapci0@pci5:0:0: =C2=A0 =C2=A0 =C2=A0 class=3D0x030000 card=3D0x221b1682 > chip=3D0x029210de rev=3D0xa1 hdr=3D0x00 > =C2=A0 =C2=A0 vendor =C2=A0 =C2=A0 =3D 'Nvidia Corp' > =C2=A0 =C2=A0 device =C2=A0 =C2=A0 =3D 'GeForce 7900 GS' > =C2=A0 =C2=A0 class =C2=A0 =C2=A0 =C2=A0=3D display This shows the 'vgapci' driver has attached to your card. Is the nvidia.ko loaded before the kernel starts? (ie do you have=20 nvidia_load=3D"YES" in /boot/loader.conf?) It would appear the latest driver should support your card (from the=20 README) and the PCI ID matches what is there. > I do cvsup src and buil-install world regulary > > nvidia-driver rebuilded not once You should rebuild the nvidia port every time you update your kernel,=20 and you should keep your kernel & userland in sync if at all possible. > In 6.2 nvidia-driver worked fine. Was it the same version of the port? =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 --nextPart1470452.PdvhidURrT Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBG/kwj5ZPcIHs/zowRAp7DAJ9xfaYu+tWX5KATVsh4Zdk0bfBWjwCdFBuH 8FoFzSRxgPEeKWwi40xzmvc= =+9TO -----END PGP SIGNATURE----- --nextPart1470452.PdvhidURrT-- From owner-freebsd-current@FreeBSD.ORG Sat Sep 29 13:38:35 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CEAA16A41B for ; Sat, 29 Sep 2007 13:38:35 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.freebsd.org (Postfix) with ESMTP id 0B14613C4BF for ; Sat, 29 Sep 2007 13:38:34 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so2400760nfb for ; Sat, 29 Sep 2007 06:38:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:to:subject:date:user-agent:references:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; bh=YeP3nvhTDFSGKFfmDiT4IpOw5fn75N2S82XWcxW+WX8=; b=FvIoiMmkXQ+ZvBULwhQP8JODeZJ+1X9bt7bPXxlUiiorSQuXoXbpKCE235MTXbphunHfB6eKGMsutVZ1rLBDR488XrnSv9xE+CpXaqT2DKvfAbX1MOiweyf5zSIsB8Zz6ZlA9gaXgjkc4TZwAYP+sMZGGJarDfgp+tHfTPyfDdg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:to:subject:date:user-agent:references:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=lhvr8MupxpnmYfzL68MvvgJIZ2a4AD4463MjAlF7GuhaQUbF/MNPz/swMhQ9N6fiw+UHqEXsI3m1sgcaJMN3uKycNdkxjTPtrnJ8LkQ5JlewLf1la6Fbgugp/VUZ6N3sCZgpBrM50hQeAGpI3Tlm4bP5MP7UQvLcmmmIFSwQJvM= Received: by 10.78.149.13 with SMTP id w13mr810435hud.1191073112954; Sat, 29 Sep 2007 06:38:32 -0700 (PDT) Received: from ?192.168.0.50? ( [81.26.90.134]) by mx.google.com with ESMTPS id o22sm1532344hub.2007.09.29.06.38.28 (version=SSLv3 cipher=OTHER); Sat, 29 Sep 2007 06:38:31 -0700 (PDT) From: "Alex V. Petrov" To: freebsd-current@freebsd.org Date: Sat, 29 Sep 2007 21:38:22 +0800 User-Agent: KMail/1.9.7 References: <200709292007.46717.alexvpetrov@gmail.com> <200709292229.15297.doconnor@gsoft.com.au> In-Reply-To: <200709292229.15297.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200709292138.22953.alexvpetrov@gmail.com> Cc: Subject: Re: x11/nvidia-driver again X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 13:38:35 -0000 > On Sat, 29 Sep 2007, Alex V. Petrov wrote: > > I read "x11/nvidia-driver on Sept07 snapshot" in this maillist. > > I have it trouble too. > > > > videocard: > > vgapci0@pci5:0:0: =9A =9A =9A class=3D0x030000 card=3D0x221b1682 > > chip=3D0x029210de rev=3D0xa1 hdr=3D0x00 > > =9A =9A vendor =9A =9A =3D 'Nvidia Corp' > > =9A =9A device =9A =9A =3D 'GeForce 7900 GS' > > =9A =9A class =9A =9A =9A=3D display > > This shows the 'vgapci' driver has attached to your card. > > Is the nvidia.ko loaded before the kernel starts? (ie do you have > nvidia_load=3D"YES" in /boot/loader.conf?) Thank You very very much. I loaded module nvidia manually :( After adding nvidia_load=3D"YES" in /boot/loader.conf=20 nvidia0 & nvidiactl present in /dev=20 and Xorg starting fine Best Regards! Alex V. Petrov From owner-freebsd-current@FreeBSD.ORG Sat Sep 29 15:19:45 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9232616A41A for ; Sat, 29 Sep 2007 15:19:45 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by mx1.freebsd.org (Postfix) with ESMTP id 21FC713C44B for ; Sat, 29 Sep 2007 15:19:44 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so2408512nfb for ; Sat, 29 Sep 2007 08:19:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; bh=aaCROHDtzTLODVeUpjMr04PnQRXBMFltN9XXpcpkSOY=; b=PWEtt9snE2mYf3STcgb71A+7JoJWlazQSVwTpuzNyZJxfrnmcksu2EMA3e7/oK2Au2rotYOUbbyQ1czibvcIPvmofum6mBX2OwA7NhBZvna5fY6no8FgbeqPACD2YKtAoIVZ5ghcExfo/ClVrf2f2lEuJEEmGp2fjECBFtqw9uM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=cd1QrScxK0TrpHZJUE7eyGcHH9m/Y/FtPvCwSb3TId5mwEIED7YS1Y8qikb+ANFP3Vfg2eoBgOIReTGlqDjt7/WB9BZ3VIhekX0aQwen7bHhRtiQEeJl7ePNsHyT4B4JXq6wYVMA7SVNH8Hu54BMNnfVgcj4dgxKoa/f6XC2FXo= Received: by 10.78.142.14 with SMTP id p14mr4331391hud.1191079183520; Sat, 29 Sep 2007 08:19:43 -0700 (PDT) Received: from ?192.168.0.50? ( [81.26.90.134]) by mx.google.com with ESMTPS id 3sm1557266huc.2007.09.29.08.19.39 (version=SSLv3 cipher=OTHER); Sat, 29 Sep 2007 08:19:42 -0700 (PDT) From: "Alex V. Petrov" To: freebsd-current@freebsd.org Date: Sat, 29 Sep 2007 23:19:34 +0800 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709292319.34214.alexvpetrov@gmail.com> Subject: qemu in current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 15:19:45 -0000 Hi All! When I trying install WinXP in qemu, after string "Setup is starting Windows" in console I see: Bad system call (core dumped) I trying several versions WinXP, W2k, W2k3 - result the same. BUT! Win98 It is installed and works well Versions of ports are actual: kqemu-kmod-1.3.0.p11_2 = up-to-date with port qemu-0.9.0_3 = up-to-date with port Best Regards! Alex V. Petrov From owner-freebsd-current@FreeBSD.ORG Sat Sep 29 15:32:03 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5B8B16A418 for ; Sat, 29 Sep 2007 15:32:03 +0000 (UTC) (envelope-from william88@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.227]) by mx1.freebsd.org (Postfix) with ESMTP id 7D30113C468 for ; Sat, 29 Sep 2007 15:32:02 +0000 (UTC) (envelope-from william88@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so2001132nzf for ; Sat, 29 Sep 2007 08:32:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=UhtWAbOuhz1VJW+eta2Ru0awP0CGNH/kVXPVqsKm+/w=; b=DlrTwYyh0MY8hI3/fBq/k6iZ5JZrL/nmZMa7IWiCEftHqZ97aC7cvia7UY8L0SY8HgP3uqElOPgDL76yKjTdfxfTeeFdEpROkc36YI1hZ0/ZU4ZdVLTDQTnhYNK0FjmWt8JFAm9iXIUc1zBYOTmPGkmgj6E/YXpCSdEUkXwst0Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JHnGVcpK5xKHlOIE84TbaAhe5o1uRkO1mN8CagezKX5GB1jLQHpmwpKMY5Ku+kn/ZeKrlNDpdaZfOyweDQjkSCEzwSCO0/ty5Zv5OJ8GA2ROKK482o7Zj6+BqajyeJwVFmY5USiN/rz8UHkHBTg5L32i/ZDKTrMIuuR3RPWgV8o= Received: by 10.65.107.10 with SMTP id j10mr10398107qbm.1191079921781; Sat, 29 Sep 2007 08:32:01 -0700 (PDT) Received: by 10.141.122.7 with HTTP; Sat, 29 Sep 2007 08:32:01 -0700 (PDT) Message-ID: <632825b40709290832r546057das89daebb00fe43b59@mail.gmail.com> Date: Sat, 29 Sep 2007 12:32:01 -0300 From: William To: "Alex V. Petrov" In-Reply-To: <200709292319.34214.alexvpetrov@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200709292319.34214.alexvpetrov@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: qemu in current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 15:32:03 -0000 On 9/29/07, Alex V. Petrov wrote: > Hi All! > > When I trying install WinXP in qemu, after string "Setup is starting Windows" > in console I see: > Bad system call (core dumped) > > I trying several versions WinXP, W2k, W2k3 - result the same. > > BUT! Win98 It is installed and works well > > Versions of ports are actual: > kqemu-kmod-1.3.0.p11_2 = up-to-date with port > qemu-0.9.0_3 = up-to-date with port Hi, Did you start the aio module or have it built-in on kernel ? kldload aio , Bye > > Best Regards! > Alex V. Petrov > > _______________________________________________ > 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" > -- William Grzybowski ------------------------------------------ Jabber: william88 at gmail dot com Curitiba/PR - Brazil From owner-freebsd-current@FreeBSD.ORG Sat Sep 29 15:47:41 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 108CE16A417 for ; Sat, 29 Sep 2007 15:47:41 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.freebsd.org (Postfix) with ESMTP id 8F61013C43E for ; Sat, 29 Sep 2007 15:47:40 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so2410785nfb for ; Sat, 29 Sep 2007 08:47:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:to:subject:date:user-agent:references:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; bh=PUVi4pqfSd1cua9WNAScDnReR17svdg8oYcNaZCphsg=; b=M2Axvoo6ECr3XZdgH7ArRgSVP6rVDHcFPKbgN7eydBHksCaYI8CkIzodAob+sm2e0pWwc2LWtjbVwF/JOddpjJupzqHYFhs+2BPA4VHS6aCUZ/K2dTlv7d37DLAdK0FdbjcedPVSZHpWiTmhpRe+D8Va3ocupC6/EnENzQW3MEk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:to:subject:date:user-agent:references:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=ZhiM3Hba6YD3+il1tiB6UZlQKP1XdSNrtxIxQGP9YFffWbAvY/Sh6FE6GDXuOeRm8oVWugIA5Nqi2qZu/8Ayl27rq4eNDIO2eJxR27LHAchNMDWjwm17QAQ9DMhPRxsbrrGv8r+sp1D7f8TCJ3fAwicaZwq9NZ7flkVfOxtYC+g= Received: by 10.78.175.14 with SMTP id x14mr955689hue.1191080858421; Sat, 29 Sep 2007 08:47:38 -0700 (PDT) Received: from ?192.168.0.50? ( [81.26.90.134]) by mx.google.com with ESMTPS id v27sm1572736hub.2007.09.29.08.47.33 (version=SSLv3 cipher=OTHER); Sat, 29 Sep 2007 08:47:36 -0700 (PDT) From: "Alex V. Petrov" To: freebsd-current@freebsd.org Date: Sat, 29 Sep 2007 23:47:28 +0800 User-Agent: KMail/1.9.7 References: <200709292319.34214.alexvpetrov@gmail.com> <632825b40709290832r546057das89daebb00fe43b59@mail.gmail.com> In-Reply-To: <632825b40709290832r546057das89daebb00fe43b59@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709292347.28353.alexvpetrov@gmail.com> Cc: William Subject: Re: qemu in current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 15:47:41 -0000 > > When I trying install WinXP in qemu, after string "Setup is starting > > Windows" in console I see: > > Bad system call (core dumped) > > > Hi, > > Did you start the aio module or have it built-in on kernel ? > kldload aio Thanks kldload aio - It has solved a problem. Strange, in 6.2 I do not remember such trouble... Best Regards! Alex V. Petrov From owner-freebsd-current@FreeBSD.ORG Sat Sep 29 16:17:37 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 017CF16A417 for ; Sat, 29 Sep 2007 16:17:37 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id A388D13C448 for ; Sat, 29 Sep 2007 16:17:36 +0000 (UTC) (envelope-from sam@errno.com) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l8TGHYOd022029 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 29 Sep 2007 09:17:36 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <46FE7A9E.8040708@errno.com> Date: Sat, 29 Sep 2007 09:17:34 -0700 From: Sam Leffler User-Agent: Thunderbird 2.0.0.6 (X11/20070814) MIME-Version: 1.0 To: Weongyo Jeong References: <20070929025030.GA66680@freebsd.weongyo.org> <46FDC5A4.5060403@errno.com> <20070929065733.GB66680@freebsd.weongyo.org> In-Reply-To: <20070929065733.GB66680@freebsd.weongyo.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-Rhyolite-Metrics: o.com; whitelist Cc: freebsd-current@freebsd.org Subject: Re: atheros panic (D-Link DWL-G520) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 16:17:37 -0000 Weongyo Jeong wrote: > On Fri, Sep 28, 2007 at 08:25:24PM -0700, Sam Leffler wrote: > >> Weongyo Jeong wrote: >> >>> My device is D-Link DWL-G520 and the device encountered a panic when I >>> did `ifconfig ath0 up'. The kernel was cvs-uped yesterday. The following >>> are the panic message: >>> >>> hostap# ifconfig ath0 up >>> ath0: ath_chan_set: unable to reset channel 1 (2412 Mhz, flags 0x480 hal >>> flags 0xc0) >>> hostap# ath0: ath_chan_set: unable to reset channel 11 (2462 Mhz, flags >>> 0x480 hal flags 0xc0) >>> ath0: ath_chan_set: unable to reset channel 13 (2472 Mhz, flags 0x480 >>> hal flags 0xc0) >>> ath0: ath_chan_set: unable to reset channel 3 (2422 Mhz, flags 0x480 hal >>> flags 0xc0) >>> ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz, flags 0x480 hal >>> flags 0xc0) >>> ath0: hardware error; resetting >>> ath0: 0x00080000 0x00000000 0x00000000, 0x00010000 0x00000000 0x00000000 >>> >>> >>> Fatal trap 18: integer divide fault while in kernel mode >>> cpuid = 0; apic id = 00 >>> instruction pointer = 0x20:0xc09f0d25 >>> stack pointer = 0x28:0xcbd3acd8 >>> frame pointer = 0x28:0xcbd3acd8 >>> code segment = base 0x0, limit 0xfffff, type 0x1b >>> = DPL 0, pres 1, def32 1, gran 1 >>> processor eflags = interrupt enabled, IOPL = 0 >>> current process = 11 (idle: cpu0) >>> [thread pid 11 tid 100004 ] >>> Stopped at cpu_idle_default+0x5: popl %ebp >>> db> bt >>> Tracing pid 11 tid 100004 td 0xc20f7630 >>> cpu_idle_default(cbd3acf8,c0769e17,c0bad610,2,c0a9a19d,...) at >>> cpu_idle_default+0x5 >>> cpu_idle(c0bad610,2,c0a9a19d,562,cbd3ad24,...) at cpu_idle+0x28 >>> sched_idletd(0,cbd3ad38,c0a9515d,314,c20f6aa0,...) at sched_idletd+0x37 >>> fork_exit(c0769de0,0,cbd3ad38) at fork_exit+0xb8 >>> fork_trampoline() at fork_trampoline+0x8 >>> --- trap 0, eip = 0, esp = 0xcbd3ad70, ebp = 0 --- >>> db> >>> >>> >>> And the below informations are device informations: >>> >>> hostap# uname -a >>> FreeBSD hostap 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Thu Sep 27 02:43:04 >>> KST 2007 root@rumhostap:/usr/obj/usr/src/sys/GENERIC i386 >>> >>> hostap# pciconf -lcv >>> ath0@pci2:2:0: class=0x020000 card=0x3a131186 chip=0x0013168c rev=0x01 >>> hdr=0x00 >>> vendor = 'Atheros Communications Inc.' >>> device = 'AR5212, AR5213 802.11a/b/g Wireless Adapter' >>> class = network >>> subclass = ethernet >>> cap 01[44] = powerspec 2 supports D0 D3 current D0 >>> >>> hostap# sysctl -a | grep dev.ath.0 >>> dev.ath.0.%desc: Atheros 5212 >>> dev.ath.0.%driver: ath >>> dev.ath.0.%location: slot=2 function=0 >>> dev.ath.0.%pnpinfo: vendor=0x168c device=0x0013 subvendor=0x1186 >>> subdevice=0x3a13 class=0x020000 >>> dev.ath.0.%parent: pci2 >>> dev.ath.0.smoothing_rate: 95 >>> dev.ath.0.sample_rate: 10 >>> dev.ath.0.countrycode: 0 >>> dev.ath.0.regdomain: 48 >>> dev.ath.0.slottime: 9 >>> dev.ath.0.acktimeout: 96 >>> dev.ath.0.ctstimeout: 96 >>> dev.ath.0.softled: 0 >>> dev.ath.0.ledpin: 0 >>> dev.ath.0.ledon: 0 >>> dev.ath.0.ledidle: 2700 >>> dev.ath.0.txantenna: 0 >>> dev.ath.0.rxantenna: 0 >>> dev.ath.0.diversity: 0 >>> dev.ath.0.txintrperiod: 5 >>> dev.ath.0.diag: 0 >>> dev.ath.0.tpscale: 0 >>> dev.ath.0.tpc: 0 >>> dev.ath.0.tpack: 63 >>> dev.ath.0.tpcts: 63 >>> dev.ath.0.fftxqmin: 2 >>> dev.ath.0.fftxqmax: 50 >>> dev.ath.0.monpass: 24 >>> >>> hostap# ifconfig ath0 list channel >>> Channel 1 : 2412 Mhz 11g Channel 8 : 2447 Mhz 11g >>> Channel 2 : 2417 Mhz 11g Channel 9 : 2452 Mhz 11g >>> Channel 3 : 2422 Mhz 11g Channel 10 : 2457 Mhz 11g >>> Channel 4 : 2427 Mhz 11g Channel 11 : 2462 Mhz 11g >>> Channel 5 : 2432 Mhz 11g Channel 12 : 2467 Mhz 11g >>> Channel 6 : 2437 Mhz 11g Turbo Channel 13 : 2472 Mhz 11g >>> Channel 7 : 2442 Mhz 11g >>> >>> stap# /sbin/ifconfig >>> ath0: flags=8802 metric 0 mtu 1500 >>> ether 00:1b:11:1a:ee:32 >>> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >>> status: no carrier >>> ssid "" channel 1 (2412 Mhz 11b) >>> authmode OPEN privacy OFF txpowmax 100 bmiss 7 scanvalid 60 bgscan >>> bgscanintvl 300 bgscanidle 250 roam:rssi11b 14 roam:rate11b 1 burst >>> >>> hostap# dmesg | grep -i ath >>> ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) >>> ath0: mem 0xe7000000-0xe700ffff irq 11 at device 2.0 on pci2 >>> ath0: [ITHREAD] >>> ath0: using obsoleted if_watchdog interface >>> ath0: Ethernet address: 00:1b:11:1a:ee:32 >>> ath0: mac 7.9 phy 4.5 radio 5.6 >>> >> Unfortunately the value of status isn't printed when the ath_hal_reset >> calls fail. Please add that to the printf in ath_chan_set. >> >> Not sure where the divide fault comes from; the stack trace doesn't >> provide much help. If you don't have INVARIANTS enabled you should do >> that in case it catches what's going on before the panic happens. >> > > The status value which is returned by ath_hal_reset() (if_ath.c 5043 > line) was 3 (HAL_EIO) and the kernel was compiled with INVARIANTS. > The hal couldn't talk to the device as expected. This could be any number of problems but is almost certain to be unrelated to the driver (e.g. cardbus, acpi, memory mapping, bad card). Sam From owner-freebsd-current@FreeBSD.ORG Sat Sep 29 20:14:57 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 329B216A419 for ; Sat, 29 Sep 2007 20:14:57 +0000 (UTC) (envelope-from don@siad.net) Received: from mars.siad.net (mars.siad.net [69.3.214.122]) by mx1.freebsd.org (Postfix) with ESMTP id 08BE013C4BB for ; Sat, 29 Sep 2007 20:14:56 +0000 (UTC) (envelope-from don@siad.net) Received: from [69.3.214.123] (rover.siad.net [69.3.214.123]) (authenticated bits=0) by mars.siad.net (8.13.8/8.13.1) with ESMTP id l8TKBSgt061371; Sat, 29 Sep 2007 13:11:32 -0700 (PDT) (envelope-from don@siad.net) Message-ID: <46FEB17B.6030702@siad.net> Date: Sat, 29 Sep 2007 13:11:39 -0700 From: "Don L. Belcher" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20070522 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kurt Jaeger References: <46F5B918.5040804@siad.net> <46FD2CFF.4000300@siad.net> <20070928181317.GA12479@home.c0mplx.org> In-Reply-To: <20070928181317.GA12479@home.c0mplx.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-2.0b1 (mars.siad.net [69.3.214.122]); Sat, 29 Sep 2007 13:11:33 -0700 (PDT) Cc: freebsd-current@freebsd.org Subject: Re: PCI to PCI Bridge initialization fails or is corrupted X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 20:14:57 -0000 Kurt Jaeger wrote: >Hi! > > > >>If somebody could point out to me where the prefetch decode >>occurs in the code, this would be a big help. >> >> > >I assume you have > >sys/dev/pci/pci_pci.c, version 1.49 > > Yes this is the version I currently have. >http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/pci/pci_pci.c?rev=1.49;content-type=text%2Fplain > >In line 183f, sc->pmembase is set: > > sc->pmembase = PCI_PPBMEMBASE(pci_read_config(dev, PCIR_PMBASEH_1, 4), > pci_read_config(dev, PCIR_PMBASEL_1, 2)); > >and if sc->pmembase is set, the function call to pcib_is_prefetch_open() >leads to the result you are looking for in line 267: > > if (pcib_is_prefetch_open(sc)) > device_printf(dev, " prefetched decode 0x%jx-0x%jx\n", > (uintmax_t)sc->pmembase, (uintmax_t)sc->pmemlimit); > >But why the pci_read_config() returns something different, I do not know. > > > What I meant was where is the hardware initialize at (for the prefetch decode), this code is working as far I could tell. The prefetch decode in the hardware is set to 0. Would any body know if following errors could be causing the failure? acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 7f00000 (3) failed