From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 00:58: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 918D416A419 for ; Sun, 7 Oct 2007 00:58:39 +0000 (UTC) (envelope-from joao.barros@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 28AF213C4A8 for ; Sun, 7 Oct 2007 00:58:38 +0000 (UTC) (envelope-from joao.barros@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so715204nfb for ; Sat, 06 Oct 2007 17:58:38 -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=G93u1MvaprABDg1dpOt5J8qefSUg7HOuYSqPnZ+imGY=; b=uqOJBCD8zY2z/QY06iyIzy3ht6lXfJzgsWnOPaYYyFVqwVwmfIw9EeTx4mMPrJT+NYF3op4eobu/TTCmb6ylzVVxD8wTVwQ1h8by00jRhcg8AGKfhBv3zi/ObGv6RZgcWi62mja/ZookG2N3qJYAhoF7rTjKS9Jv/zqYieSKfA0= 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=Gg0Kby7ONHEKZeI6Cb9O8W1Mc7NwR9oAxl4v62m46MERxpZyVpkrKf/pYIc8SyjTNZLPOg1sHua6MvINpjDv6R691yxfNckSPMNKFaCwJqYmw+shYcAegrIM6SAgLv7+o7OgHZRYF4Xykf1fR0AqHro4x5Q6y+/PBPct2sWaKzc= Received: by 10.78.170.6 with SMTP id s6mr9762333hue.1191717170845; Sat, 06 Oct 2007 17:32:50 -0700 (PDT) Received: by 10.78.163.2 with HTTP; Sat, 6 Oct 2007 17:32:50 -0700 (PDT) Message-ID: <70e8236f0710061732y77486ddfoe521808856325230@mail.gmail.com> Date: Sun, 7 Oct 2007 01:32:50 +0100 From: "Joao Barros" To: "=?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?=" In-Reply-To: <868x6gpk3i.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4707569E.6010400@freebsd.org> <868x6gpk3i.fsf@ds4.des.no> Cc: Darren Reed , FreeBSD Current , pjd@freebsd.org Subject: Re: ZFS & NFS integration... 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, 07 Oct 2007 00:58:39 -0000 On 10/6/07, Dag-Erling Sm=F8rgrav wrote: > Darren Reed writes: > > Whats the planned status for ZFS+NFS with 7.0? > > Don't Do It, basically. I've been using ZFS+NFS on CURRENT since Pawel committed ZFS into the tree using my Mac as the NFS client. Root on ZFS, power failures, constant reads and writes (it's my storage for multimedia and bittorrent downloads). Aside from the need to set max_vnodes on i386: 0 problems :-D --=20 Joao Barros From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 01:04: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 498E916A420 for ; Sun, 7 Oct 2007 01:04:05 +0000 (UTC) (envelope-from joao.barros@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 C6D6013C448 for ; Sun, 7 Oct 2007 01:04:04 +0000 (UTC) (envelope-from joao.barros@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so715457nfb for ; Sat, 06 Oct 2007 18:04:03 -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=GZLnOFG+79X7Ik1yDNaXcL1PDi9YRrslRdcXuAlxR0w=; b=hHglU8fIOlpo6cnvlAvK2CQtgoN5WuvTHx/QzaBBWTnbZMpi9Nbg7aGimgSsXi8OliYeyml9/vP1eNZ/pFN9wccMwnLmTvSj8oGWli+rQ0mjUJ5qskTdKxAP2OUqnyO79cRm15tJysQM1+KxnIKCa3X0fVuLFcP03pPkzgdk4gY= 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=GA4JXBSugEBqvU6nxxKfES7jrVP7Qa63Do3Jfz3EC/+b8KX2hoAlEjmfK+ToOVvl+QI6X5lmXiTxflFg4CMrQuGH46SbhPLvM5dfzIurOZwSrTcmJSY+pRLuITKkSjgssHW054MCLgZ5tLtLpgkzMTzxmTJ0jjbPB7teoDqtYlE= Received: by 10.78.180.18 with SMTP id c18mr9816666huf.1191719043101; Sat, 06 Oct 2007 18:04:03 -0700 (PDT) Received: by 10.78.163.2 with HTTP; Sat, 6 Oct 2007 18:04:03 -0700 (PDT) Message-ID: <70e8236f0710061804o62ea85c6k1d8a5e7d3600ef15@mail.gmail.com> Date: Sun, 7 Oct 2007 02:04:03 +0100 From: "Joao Barros" To: "Pawel Jakub Dawidek" In-Reply-To: <20071005000046.GC92272@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071005000046.GC92272@garage.freebsd.pl> Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS kmem_map too small. 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, 07 Oct 2007 01:04:05 -0000 On 10/5/07, Pawel Jakub Dawidek wrote: > Hi. > > We'are about to branch RELENG_7 and I'd like to start discussion with > folks that experience 'kmem_map too small' panic with the latest HEAD. > > I'm trying hard to reproduce it and I can't, so I need to gather more > info how you are able to provoke this panic. > > What I did was to rsync 200 FreeBSD src trees from one directory to > another on the same ZFS file system. It worked fine. > > The system I'm using is i386 and the only tuning I did is bigger > kmem_map. From my /boot/loader.conf: > > vm.kmem_size=629145600 > vm.kmem_size_max=629145600 > > The machine is dual core Pentium D 3GHz with 1GB of RAM. My pool is: > > lcf:root:/tank/0# zpool status > pool: tank > state: ONLINE > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > tank ONLINE 0 0 0 > ad4 ONLINE 0 0 0 > ad5 ONLINE 0 0 0 > ad6 ONLINE 0 0 0 > ad7 ONLINE 0 0 0 > > errors: No known data errors > > If you can still see those panic, please let me know as soon as possible > and try to describe what your workload looks like, how to reproduce it, > etc. I'd really like ZFS to be rock-stable for 7.0 even on i386. > i386 with 1GB here. I used to get this when chown'ing some thousand files recursively via ssh. Last time I got this was unraring 2GB files from n x 95MB rars via NFS. My system: xeon# zpool status pool: r4x320 state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM r4x320 ONLINE 0 0 0 raidz1 ONLINE 0 0 0 ad0s1d ONLINE 0 0 0 ad1s1d ONLINE 0 0 0 ad4 ONLINE 0 0 0 ad6 ONLINE 0 0 0 errors: No known data errors xeon# cat /boot/loader.conf zfs_load="YES" vfs.root.mountfrom="zfs:r4x320" vfs.zfs.prefetch_disable=1 (I have this to improve video play) xeon# sysctl vm | grep kmem vm.kmem_size_scale: 3 vm.kmem_size_max: 335544320 vm.kmem_size_min: 0 vm.kmem_size: 335544320 xeon# sysctl -a | grep vnodes kern.maxvnodes: 52242 kern.minvnodes: 17414 vfs.freevnodes: 7797 vfs.wantfreevnodes: 17414 vfs.numvnodes: 8230 I usually set kern.maxvnodes to 50000 manually and everything is ok but I see that I forgot to on my last reboot and haven't seen any problems yet: xeon# uptime 1:56AM up 4 days, 15:06 off-topic: it's lovely not having to have your 874GB fs with millions of files checked after a crash or power failure :-D -- Joao Barros From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 01:37: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 3A3BD16A417; Sun, 7 Oct 2007 01:37:36 +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 17F1B13C459; Sun, 7 Oct 2007 01:37:36 +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 839822FC99; Sat, 6 Oct 2007 21:37:35 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Sat, 06 Oct 2007 21:37:35 -0400 X-Sasl-enc: W06mE+jm4t721hdCOxZ9LDIQVTnK6MHndTHnMuvNwZqp 1191721055 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 CEEF0112C; Sat, 6 Oct 2007 21:37:34 -0400 (EDT) Message-ID: <47083883.6000503@freebsd.org> Date: Sat, 06 Oct 2007 18:38:11 -0700 From: Darren Reed User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= References: <4707569E.6010400@freebsd.org> <868x6gpk3i.fsf@ds4.des.no> In-Reply-To: <868x6gpk3i.fsf@ds4.des.no> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: FreeBSD Current , pjd@FreeBSD.org Subject: Re: ZFS & NFS integration... 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, 07 Oct 2007 01:37:36 -0000 Dag-Erling Smørgrav wrote: > Darren Reed writes: > > Whats the planned status for ZFS+NFS with 7.0? > > Don't Do It, basically. > This sounds like a "shoot yourself in the foot" comment. Why? And if it is that bad, shouldn't we disable sharenfs or at least prevent ZFS from recognising it or taking action because of it? Darren From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 02:59: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 E2EF916A418 for ; Sun, 7 Oct 2007 02:59:15 +0000 (UTC) (envelope-from csjp@sub.vaned.net) Received: from sub.vaned.net (sub.vaned.net [205.200.235.40]) by mx1.freebsd.org (Postfix) with ESMTP id B8BE513C45D for ; Sun, 7 Oct 2007 02:59:15 +0000 (UTC) (envelope-from csjp@sub.vaned.net) Received: by sub.vaned.net (Postfix, from userid 1001) id 4E3D217395; Sat, 6 Oct 2007 21:56:37 -0500 (CDT) Date: Sat, 6 Oct 2007 21:56:37 -0500 From: "Christian S.J. Peron" To: Katsuji Ishikawa Message-ID: <20071007025637.GA57492@sub.vaned.net> 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: heavy network load 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, 07 Oct 2007 02:59:16 -0000 I am experiencing this problem too. As a work around, you can remove options SMP from your kernel. The root-cause of this issue is under investigation. On Sat, Oct 06, 2007 at 02:49:01PM +0900, Katsuji Ishikawa wrote: > Hi . > I use -CURRENT on Parallels Desktop(Mac OS X). It works very fine. > But today I csup'ed and installed these. After that, I encountered > network problem.. > > > Details: > > Host: Parallels Desktop (Mac OS X) , 192.168.0.3 > Guest: FreeBSD-CURRENT , 192.168.0.6 > > before (Old current) > katsuji@hexley% ping 192.168.0.6 > PING 192.168.0.6 (192.168.0.6): 56 data bytes > 64 bytes from 192.168.0.6: icmp_seq=0 ttl=64 time=0.462 ms > 64 bytes from 192.168.0.6: icmp_seq=1 ttl=64 time=0.623 ms > 64 bytes from 192.168.0.6: icmp_seq=2 ttl=64 time=0.497 ms > 64 bytes from 192.168.0.6: icmp_seq=3 ttl=64 time=0.571 ms > 64 bytes from 192.168.0.6: icmp_seq=4 ttl=64 time=0.610 ms > 64 bytes from 192.168.0.6: icmp_seq=5 ttl=64 time=0.510 ms > ^C > --- 192.168.0.6 ping statistics --- > 6 packets transmitted, 6 packets received, 0% packet loss > round-trip min/avg/max/stddev = 0.462/0.545/0.623/0.060 ms > > > after (csuped today, occured packet loss...) > katsuji@hexley% ping 192.168.0.6 > PING 192.168.0.6 (192.168.0.6): 56 data bytes > 64 bytes from 192.168.0.6: icmp_seq=0 ttl=64 time=4397.146 ms > 64 bytes from 192.168.0.6: icmp_seq=1 ttl=64 time=3397.082 ms > 64 bytes from 192.168.0.6: icmp_seq=2 ttl=64 time=2397.021 ms > 64 bytes from 192.168.0.6: icmp_seq=3 ttl=64 time=1395.493 ms > 64 bytes from 192.168.0.6: icmp_seq=4 ttl=64 time=393.692 ms > ^C > --- 192.168.0.6 ping statistics --- > 11 packets transmitted, 5 packets received, 54% packet loss > round-trip min/avg/max/stddev = 393.692/2396.087/4397.146/1415.415 ms > > > kernel configuration: > > katsuji@seven% cat ULE3 [/sys/i386/conf] > include GENERIC > ident ULE3 > > nooptions SCHED_4BSD > options SCHED_ULE > > > Have you any good ideas? > > Regards, > > -- > Katsuji ISHIKAWA > _______________________________________________ > 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" -- Christian S.J. Peron csjp@FreeBSD.ORG FreeBSD Committer From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 04:03: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 1B32216A420 for ; Sun, 7 Oct 2007 04:03:42 +0000 (UTC) (envelope-from csjp@sub.vaned.net) Received: from sub.vaned.net (sub.vaned.net [205.200.235.40]) by mx1.freebsd.org (Postfix) with ESMTP id E891F13C458 for ; Sun, 7 Oct 2007 04:03:41 +0000 (UTC) (envelope-from csjp@sub.vaned.net) Received: by sub.vaned.net (Postfix, from userid 1001) id A396F17395; Sat, 6 Oct 2007 23:01:03 -0500 (CDT) Date: Sat, 6 Oct 2007 23:01:03 -0500 From: "Christian S.J. Peron" To: Katsuji Ishikawa Message-ID: <20071007040103.GA58108@sub.vaned.net> References: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org Subject: Re: heavy network load 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, 07 Oct 2007 04:03:42 -0000 --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline The original author of the scheduler has come up with this patch which should fix the issue. Please test the attached patch. On Sat, Oct 06, 2007 at 02:49:01PM +0900, Katsuji Ishikawa wrote: > Hi . > I use -CURRENT on Parallels Desktop(Mac OS X). It works very fine. > But today I csup'ed and installed these. After that, I encountered > network problem.. > > > Details: > > Host: Parallels Desktop (Mac OS X) , 192.168.0.3 > Guest: FreeBSD-CURRENT , 192.168.0.6 > > before (Old current) > katsuji@hexley% ping 192.168.0.6 > PING 192.168.0.6 (192.168.0.6): 56 data bytes > 64 bytes from 192.168.0.6: icmp_seq=0 ttl=64 time=0.462 ms > 64 bytes from 192.168.0.6: icmp_seq=1 ttl=64 time=0.623 ms > 64 bytes from 192.168.0.6: icmp_seq=2 ttl=64 time=0.497 ms > 64 bytes from 192.168.0.6: icmp_seq=3 ttl=64 time=0.571 ms > 64 bytes from 192.168.0.6: icmp_seq=4 ttl=64 time=0.610 ms > 64 bytes from 192.168.0.6: icmp_seq=5 ttl=64 time=0.510 ms > ^C > --- 192.168.0.6 ping statistics --- > 6 packets transmitted, 6 packets received, 0% packet loss > round-trip min/avg/max/stddev = 0.462/0.545/0.623/0.060 ms > > > after (csuped today, occured packet loss...) > katsuji@hexley% ping 192.168.0.6 > PING 192.168.0.6 (192.168.0.6): 56 data bytes > 64 bytes from 192.168.0.6: icmp_seq=0 ttl=64 time=4397.146 ms > 64 bytes from 192.168.0.6: icmp_seq=1 ttl=64 time=3397.082 ms > 64 bytes from 192.168.0.6: icmp_seq=2 ttl=64 time=2397.021 ms > 64 bytes from 192.168.0.6: icmp_seq=3 ttl=64 time=1395.493 ms > 64 bytes from 192.168.0.6: icmp_seq=4 ttl=64 time=393.692 ms > ^C > --- 192.168.0.6 ping statistics --- > 11 packets transmitted, 5 packets received, 54% packet loss > round-trip min/avg/max/stddev = 393.692/2396.087/4397.146/1415.415 ms > > > kernel configuration: > > katsuji@seven% cat ULE3 [/sys/i386/conf] > include GENERIC > ident ULE3 > > nooptions SCHED_4BSD > options SCHED_ULE > > > Have you any good ideas? > > Regards, > > -- > Katsuji ISHIKAWA > _______________________________________________ > 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" -- Christian S.J. Peron csjp@FreeBSD.ORG FreeBSD Committer --T4sUOijqQbZv57TR Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="sched_ule.c.diff" ? change.diff ? d ? kern_lockf.1182548846.diff ? lockf.diff ? lockf_restrict.1183833125.diff ? sched_smp.c ? sched_ule.c.diff Index: sched_ule.c =================================================================== RCS file: /home/ncvs/src/sys/kern/sched_ule.c,v retrieving revision 1.212 diff -u -r1.212 sched_ule.c --- sched_ule.c 2 Oct 2007 01:30:18 -0000 1.212 +++ sched_ule.c 7 Oct 2007 04:01:20 -0000 @@ -743,6 +743,9 @@ int load; int cpu; + if (!smp_started) + return (1); + KASSERT(steal_thresh != 0, ("steal_thresh == 0")); /* We don't want to be preempted while we're iterating over tdqs */ spinlock_enter(); tdg = tdq->tdq_group; --T4sUOijqQbZv57TR-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 05:39: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 2278116A419 for ; Sun, 7 Oct 2007 05:39:29 +0000 (UTC) (envelope-from k.ishish@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.179]) by mx1.freebsd.org (Postfix) with ESMTP id 0209E13C447 for ; Sun, 7 Oct 2007 05:39:28 +0000 (UTC) (envelope-from k.ishish@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so1227558waf for ; Sat, 06 Oct 2007 22:39: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:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=jwYWS/19zFM3vkUlW3/TOLz0JCEPR+tu8A60hXCBp30=; b=FHVPMuxGFB3Nwo5e6HsvHqAdpav15Pu85Hl82zjRl/QQpfBBkC5wHiKcJXa2JKI6VQkZqvGbEufDa2Z/OBKdgJmwoiui1ZpooHXbkFp8n2lJfPZsgkPjHVDW0I42tY0pK9zyXh1q9iYKaI05VbHdhsnYpxGOkCuG44EyF5y9Jgg= 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=aUlK0r7ai4r4/UxKyRVueS+iw/ylP7t4ekonehyRTRMp1JuZVB0KcWsmx7Xxe6d+AZ3IFgowkdQJeDQwnoLE5savusIOl9qdB/yw7ufLe2RmoAFAhcxRc/yJpyUCxqqv45/Z2sjyz7qFa3Nj6h2b8xblQJLt0OFgCdvIaz5D5bU= Received: by 10.142.86.7 with SMTP id j7mr1875280wfb.1191735568488; Sat, 06 Oct 2007 22:39:28 -0700 (PDT) Received: by 10.142.115.1 with HTTP; Sat, 6 Oct 2007 22:39:28 -0700 (PDT) Message-ID: Date: Sun, 7 Oct 2007 14:39:28 +0900 From: "Katsuji Ishikawa" To: "Christian S.J. Peron" In-Reply-To: <20071007040103.GA58108@sub.vaned.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071007040103.GA58108@sub.vaned.net> Cc: freebsd-current@freebsd.org Subject: Re: heavy network load 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, 07 Oct 2007 05:39:29 -0000 I tested your patch (sched_ule.c.diff). Then this network problem was solved! Thank you. patched & make kernel & rebooted & ping test: katsuji@hexley% ping 192.168.0.6 PING 192.168.0.6 (192.168.0.6): 56 data bytes 64 bytes from 192.168.0.6: icmp_seq=0 ttl=64 time=0.457 ms 64 bytes from 192.168.0.6: icmp_seq=1 ttl=64 time=0.508 ms 64 bytes from 192.168.0.6: icmp_seq=2 ttl=64 time=0.700 ms 64 bytes from 192.168.0.6: icmp_seq=3 ttl=64 time=0.505 ms 64 bytes from 192.168.0.6: icmp_seq=4 ttl=64 time=0.616 ms 64 bytes from 192.168.0.6: icmp_seq=5 ttl=64 time=0.535 ms 64 bytes from 192.168.0.6: icmp_seq=6 ttl=64 time=0.630 ms 64 bytes from 192.168.0.6: icmp_seq=7 ttl=64 time=0.557 ms 64 bytes from 192.168.0.6: icmp_seq=8 ttl=64 time=0.549 ms 64 bytes from 192.168.0.6: icmp_seq=9 ttl=64 time=0.431 ms ^C --- 192.168.0.6 ping statistics --- 10 packets transmitted, 10 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.431/0.549/0.700/0.078 ms On 10/7/07, Christian S.J. Peron wrote: > The original author of the scheduler has come up with this patch > which should fix the issue. Please test the attached patch. > > On Sat, Oct 06, 2007 at 02:49:01PM +0900, Katsuji Ishikawa wrote: > > Hi . > > I use -CURRENT on Parallels Desktop(Mac OS X). It works very fine. > > But today I csup'ed and installed these. After that, I encountered > > network problem.. > > > > > > Details: > > > > Host: Parallels Desktop (Mac OS X) , 192.168.0.3 > > Guest: FreeBSD-CURRENT , 192.168.0.6 > > > > before (Old current) > > katsuji@hexley% ping 192.168.0.6 > > PING 192.168.0.6 (192.168.0.6): 56 data bytes > > 64 bytes from 192.168.0.6: icmp_seq=0 ttl=64 time=0.462 ms > > 64 bytes from 192.168.0.6: icmp_seq=1 ttl=64 time=0.623 ms > > 64 bytes from 192.168.0.6: icmp_seq=2 ttl=64 time=0.497 ms > > 64 bytes from 192.168.0.6: icmp_seq=3 ttl=64 time=0.571 ms > > 64 bytes from 192.168.0.6: icmp_seq=4 ttl=64 time=0.610 ms > > 64 bytes from 192.168.0.6: icmp_seq=5 ttl=64 time=0.510 ms > > ^C > > --- 192.168.0.6 ping statistics --- > > 6 packets transmitted, 6 packets received, 0% packet loss > > round-trip min/avg/max/stddev = 0.462/0.545/0.623/0.060 ms > > > > > > after (csuped today, occured packet loss...) > > katsuji@hexley% ping 192.168.0.6 > > PING 192.168.0.6 (192.168.0.6): 56 data bytes > > 64 bytes from 192.168.0.6: icmp_seq=0 ttl=64 time=4397.146 ms > > 64 bytes from 192.168.0.6: icmp_seq=1 ttl=64 time=3397.082 ms > > 64 bytes from 192.168.0.6: icmp_seq=2 ttl=64 time=2397.021 ms > > 64 bytes from 192.168.0.6: icmp_seq=3 ttl=64 time=1395.493 ms > > 64 bytes from 192.168.0.6: icmp_seq=4 ttl=64 time=393.692 ms > > ^C > > --- 192.168.0.6 ping statistics --- > > 11 packets transmitted, 5 packets received, 54% packet loss > > round-trip min/avg/max/stddev = 393.692/2396.087/4397.146/1415.415 ms > > > > > > kernel configuration: > > > > katsuji@seven% cat ULE3 [/sys/i386/conf] > > include GENERIC > > ident ULE3 > > > > nooptions SCHED_4BSD > > options SCHED_ULE > > > > > > Have you any good ideas? > > > > Regards, > > > > -- > > Katsuji ISHIKAWA > > _______________________________________________ > > 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" > > -- > Christian S.J. Peron > csjp@FreeBSD.ORG > FreeBSD Committer > > -- Katsuji ISHIKAWA From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 08:22:12 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 9178216A419; Sun, 7 Oct 2007 08:22: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 5E27513C447; Sun, 7 Oct 2007 08:22:12 +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 l978LrlP027399 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Sun, 7 Oct 2007 04:21:54 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Sun, 7 Oct 2007 01:24:35 -0700 (PDT) From: Jeff Roberson X-X-Sender: jroberson@10.0.0.1 To: Marc Fonvieille In-Reply-To: <20071006191014.GB84780@abigail.blackend.org> Message-ID: <20071007012049.S912@10.0.0.1> References: <20071002165007.D587@10.0.0.1> <20071006074429.GB976@gothic.blackend.org> <20071006102113.GC976@gothic.blackend.org> <47077951.5030906@clearchain.com> <4707866F.7030605@FreeBSD.org> <20071006143141.GD976@gothic.blackend.org> <4707CF8D.3070303@u.washington.edu> <20071006191014.GB84780@abigail.blackend.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Garrett Cooper , Benjamin Close , current@freebsd.org Subject: Re: ULE/yielding patch for testing. 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, 07 Oct 2007 08:22:12 -0000 On Sat, 6 Oct 2007, Marc Fonvieille wrote: > On Sat, Oct 06, 2007 at 11:10:21AM -0700, Garrett Cooper wrote: >> >> Your problem is most likely Flash/Javascript based (I'm basing my >> theory on the fact that there's a lot of Ajax related stuff on the site). >> >> No matter what OS you have, if a website's slow (and it's not >> because you don't have OpenGL support in your X-server), slowness will >> remain constant. It's just the way unfortunately that browsers are designed. >> > [...] > > Not really when the slowness does not exist with 6.X. I have experienced certain websites causing firefox to slow down considerably. When I mouse over firefox the mouse begins to jerk as well but when I move back away from firefox it seems fine again. I suspected it was an x/firefox bug. Although I also sometimes observe mysql hanging for a period of a half second or so while running sysbench. I wonder if we don't have a threading library bug? I know I observed this prior to the thread_lock work so hopefully I didn't break it. Jeff > > -- > Marc > _______________________________________________ > 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 Oct 7 08:33:21 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 826A016A41B; Sun, 7 Oct 2007 08:33:21 +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 D224F13C494; Sun, 7 Oct 2007 08:33:20 +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 l978X8iE028158 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Sun, 7 Oct 2007 04:33:09 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Sun, 7 Oct 2007 01:35:50 -0700 (PDT) From: Jeff Roberson X-X-Sender: jroberson@10.0.0.1 To: Marc Fonvieille In-Reply-To: <20071007012049.S912@10.0.0.1> Message-ID: <20071007013342.D912@10.0.0.1> References: <20071002165007.D587@10.0.0.1> <20071006074429.GB976@gothic.blackend.org> <20071006102113.GC976@gothic.blackend.org> <47077951.5030906@clearchain.com> <4707866F.7030605@FreeBSD.org> <20071006143141.GD976@gothic.blackend.org> <4707CF8D.3070303@u.washington.edu> <20071006191014.GB84780@abigail.blackend.org> <20071007012049.S912@10.0.0.1> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Garrett Cooper , Benjamin Close , current@freebsd.org Subject: Re: ULE/yielding patch for testing. 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, 07 Oct 2007 08:33:21 -0000 On Sun, 7 Oct 2007, Jeff Roberson wrote: > On Sat, 6 Oct 2007, Marc Fonvieille wrote: > >> On Sat, Oct 06, 2007 at 11:10:21AM -0700, Garrett Cooper wrote: >>> >>> Your problem is most likely Flash/Javascript based (I'm basing my >>> theory on the fact that there's a lot of Ajax related stuff on the site). >>> >>> No matter what OS you have, if a website's slow (and it's not >>> because you don't have OpenGL support in your X-server), slowness will >>> remain constant. It's just the way unfortunately that browsers are >>> designed. >>> >> [...] >> >> Not really when the slowness does not exist with 6.X. > > I have experienced certain websites causing firefox to slow down > considerably. When I mouse over firefox the mouse begins to jerk as well but > when I move back away from firefox it seems fine again. I suspected it was > an x/firefox bug. Actually I double-checked this case with dailytech.com. It seems to be spending all of the cpu time in user-space in xwindows. So it seems that it is the new xwindows that has the problem. If you watch the 'TIME' field of top you can see that very little cpu time is attributed to firefox and quite a lot to X windows. So the windowing system is too busy to redraw mouse events even if we are scheduling it well. Jeff > > Although I also sometimes observe mysql hanging for a period of a half second > or so while running sysbench. I wonder if we don't have a threading library > bug? I know I observed this prior to the thread_lock work so hopefully I > didn't break it. > > Jeff > >> >> -- >> Marc >> _______________________________________________ >> 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 Oct 7 08:49: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 7603B16A419; Sun, 7 Oct 2007 08:49:00 +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 394E613C45A; Sun, 7 Oct 2007 08:49:00 +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 DF61420BA; Sun, 7 Oct 2007 10:48:50 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 5B78320AE; Sun, 7 Oct 2007 10:48:50 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id 245FB844A8; Sun, 7 Oct 2007 10:48:50 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Darren Reed References: <4707569E.6010400@freebsd.org> <868x6gpk3i.fsf@ds4.des.no> <47083883.6000503@freebsd.org> Date: Sun, 07 Oct 2007 10:48:49 +0200 In-Reply-To: <47083883.6000503@freebsd.org> (Darren Reed's message of "Sat\, 06 Oct 2007 18\:38\:11 -0700") Message-ID: <863awn9uoe.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 , pjd@FreeBSD.org Subject: Re: ZFS & NFS integration... 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, 07 Oct 2007 08:49:00 -0000 Darren Reed writes: > Dag-Erling Sm=C3=B8rgrav wrote: > > Darren Reed writes: > > > Whats the planned status for ZFS+NFS with 7.0? > > Don't Do It, basically. > This sounds like a "shoot yourself in the foot" comment. > > Why? I haven't figured out the exact details yet, but apparently when the client closes a file that was opened read / write, the server stops responding to that client. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 09:05: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 0058716A419; Sun, 7 Oct 2007 09:05:08 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe08.swip.net [212.247.154.225]) by mx1.freebsd.org (Postfix) with ESMTP id 2032E13C45A; Sun, 7 Oct 2007 09:05:07 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [85.19.218.45] (account mc467741@c2i.net [85.19.218.45] verified) by mailfe08.swip.net (CommuniGate Pro SMTP 5.1.10) with ESMTPA id 638835062; Sun, 07 Oct 2007 11:05:06 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org, Lars Engels Date: Sun, 7 Oct 2007 11:05:30 +0200 User-Agent: KMail/1.9.7 References: <20071006193259.GY30704@e.0x20.net> In-Reply-To: <20071006193259.GY30704@e.0x20.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710071105.31043.hselasky@c2i.net> Cc: current@freebsd.org, freebsd-usb@freebsd.org Subject: Re: usb_insert_transfer panic with if_zyd 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, 07 Oct 2007 09:05:09 -0000 On Saturday 06 October 2007, Lars Engels wrote: > When I use my ZyXEL G-220 Wireless USB Stick with the if_zyd driver, I > get a usb_insert_transfer panic after some traffic went trough. > The mainboard is an Asus P5K with Intel P35 chipset. > FreBSD version: > FreeBSD dhcppc2 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Thu Oct 4 22:15:47 > CEST 2007 root@dhcppc1:/usr/obj/usr/src/sys/GENERIC i386 > > Attached is the backtrace, dmesg and the output of pciconf and usbdevs. > > Lars Hi Lars, What is the panic message ? --HPS From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 09:54:34 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 BE81116A417 for ; Sun, 7 Oct 2007 09:54:34 +0000 (UTC) (envelope-from marc@blackend.org) Received: from abigail.blackend.org (ns0.blackend.org [82.227.222.164]) by mx1.freebsd.org (Postfix) with ESMTP id 22F2713C455 for ; Sun, 7 Oct 2007 09:54:33 +0000 (UTC) (envelope-from marc@blackend.org) Received: from gothic.blackend.org (gothic.blackend.org [192.168.1.203]) by abigail.blackend.org (8.13.4/8.13.3) with ESMTP id l979s90N000228; Sun, 7 Oct 2007 11:54:09 +0200 (CEST) (envelope-from marc@abigail.blackend.org) Received: from gothic.blackend.org (localhost [127.0.0.1]) by gothic.blackend.org (8.14.1/8.14.1) with ESMTP id l979s9im001047; Sun, 7 Oct 2007 11:54:09 +0200 (CEST) (envelope-from marc@gothic.blackend.org) Received: (from marc@localhost) by gothic.blackend.org (8.14.1/8.14.1/Submit) id l979s8xl001046; Sun, 7 Oct 2007 11:54:08 +0200 (CEST) (envelope-from marc) Date: Sun, 7 Oct 2007 11:54:08 +0200 From: Marc Fonvieille To: Jeff Roberson Message-ID: <20071007095408.GA997@gothic.blackend.org> References: <20071002165007.D587@10.0.0.1> <20071006074429.GB976@gothic.blackend.org> <20071006102113.GC976@gothic.blackend.org> <47077951.5030906@clearchain.com> <4707866F.7030605@FreeBSD.org> <20071006143141.GD976@gothic.blackend.org> <4707CF8D.3070303@u.washington.edu> <20071006191014.GB84780@abigail.blackend.org> <20071007012049.S912@10.0.0.1> <20071007013342.D912@10.0.0.1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071007013342.D912@10.0.0.1> X-Useless-Header: blackend.org X-Operating-System: FreeBSD 7.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Garrett Cooper , Benjamin Close , current@freebsd.org Subject: Re: ULE/yielding patch for testing. 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, 07 Oct 2007 09:54:34 -0000 On Sun, Oct 07, 2007 at 01:35:50AM -0700, Jeff Roberson wrote: >>> [...] >>> Not really when the slowness does not exist with 6.X. >> >> I have experienced certain websites causing firefox to slow down >> considerably. When I mouse over firefox the mouse begins to jerk as well >> but when I move back away from firefox it seems fine again. I suspected >> it was an x/firefox bug. > > Actually I double-checked this case with dailytech.com. It seems to be > spending all of the cpu time in user-space in xwindows. So it seems that > it is the new xwindows that has the problem. If you watch the 'TIME' field > of top you can see that very little cpu time is attributed to firefox and > quite a lot to X windows. So the windowing system is too busy to redraw > mouse events even if we are scheduling it well. > You mean Xorg 7.2 or 7.3 with -CURRENT? Currently I observe the problem with Xorg 7.2 or 7.3 under -CURRENT, when Xorg 7.2 with 6.2-STABLE is Ok (I did not try with Xorg 7.3 on -STABLE, but I'm quite sure I'll end to same result). On a completly different machine (a more recent one with a 2.8GHz Celeron), the problem could be less obvious cause of the machine speed but I can notice the difference between 6.2-STABLE and 7-CURRENT with any Xorg version. > Jeff > >> >> Although I also sometimes observe mysql hanging for a period of a half >> second or so while running sysbench. I wonder if we don't have a >> threading library bug? I know I observed this prior to the thread_lock >> work so hopefully I didn't break it. >> I think a lot of people missed that problem cause they run fast machines. For me it's very difficult to track down the issue cause I'm ignorant in these OS areas and the various logs and tools don't give obvious information. -- Marc From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 10:05:09 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 DC56216A418; Sun, 7 Oct 2007 10:05:09 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe08.swip.net [212.247.154.225]) by mx1.freebsd.org (Postfix) with ESMTP id 5BD9413C45D; Sun, 7 Oct 2007 10:05:09 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [85.19.218.45] (account mc467741@c2i.net [85.19.218.45] verified) by mailfe08.swip.net (CommuniGate Pro SMTP 5.1.10) with ESMTPA id 638835062; Sun, 07 Oct 2007 11:05:06 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org, Lars Engels Date: Sun, 7 Oct 2007 11:05:30 +0200 User-Agent: KMail/1.9.7 References: <20071006193259.GY30704@e.0x20.net> In-Reply-To: <20071006193259.GY30704@e.0x20.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710071105.31043.hselasky@c2i.net> Cc: current@freebsd.org, freebsd-usb@freebsd.org Subject: Re: usb_insert_transfer panic with if_zyd 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, 07 Oct 2007 10:05:09 -0000 On Saturday 06 October 2007, Lars Engels wrote: > When I use my ZyXEL G-220 Wireless USB Stick with the if_zyd driver, I > get a usb_insert_transfer panic after some traffic went trough. > The mainboard is an Asus P5K with Intel P35 chipset. > FreBSD version: > FreeBSD dhcppc2 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Thu Oct 4 22:15:47 > CEST 2007 root@dhcppc1:/usr/obj/usr/src/sys/GENERIC i386 > > Attached is the backtrace, dmesg and the output of pciconf and usbdevs. > > Lars Hi Lars, What is the panic message ? --HPS From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 10: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 79DCB16A41A for ; Sun, 7 Oct 2007 10:37:15 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from spacemail1-out.mgmt.space.net (spacemail1-out.mgmt.Space.Net [194.97.149.146]) by mx1.freebsd.org (Postfix) with ESMTP id 11AE413C4A5 for ; Sun, 7 Oct 2007 10:37:14 +0000 (UTC) (envelope-from se@FreeBSD.org) X-SpaceNet-SBRS: None X-IronPort-AV: E=Sophos;i="4.21,240,1188770400"; d="scan'208";a="66379727" Received: from mail.atsec.com ([195.30.252.105]) by spacemail1-out.mgmt.space.net with ESMTP; 07 Oct 2007 12:37:12 +0200 Received: from [192.168.0.12] (p5087739D.dip.t-dialin.net [80.135.115.157]) (Authenticated sender: se@atsec.com) by mail.atsec.com (Postfix) with ESMTP id 2723B720932; Sun, 7 Oct 2007 12:37:10 +0200 (CEST) Message-ID: <4708B6D0.3090009@FreeBSD.org> Date: Sun, 07 Oct 2007 12:37:04 +0200 From: Stefan Esser User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= References: <4707569E.6010400@freebsd.org> <868x6gpk3i.fsf@ds4.des.no> <47083883.6000503@freebsd.org> <863awn9uoe.fsf@ds4.des.no> In-Reply-To: <863awn9uoe.fsf@ds4.des.no> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: Darren Reed , FreeBSD Current , pjd@FreeBSD.org Subject: Re: ZFS & NFS integration... 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, 07 Oct 2007 10:37:15 -0000 Dag-Erling Smørgrav wrote: > Darren Reed writes: >> Dag-Erling Smørgrav wrote: >>> Darren Reed writes: >>>> Whats the planned status for ZFS+NFS with 7.0? >>> Don't Do It, basically. >> This sounds like a "shoot yourself in the foot" comment. >> >> Why? > > I haven't figured out the exact details yet, but apparently when the > client closes a file that was opened read / write, the server stops > responding to that client. I've been operating a file server (P3/733, 512MB) that way for many months. Besides the problems with Samba on ZFS (one of the clients is a DVB-T receiver that reads/writes to SMB shares) there have never been problems. Other clients use NFS (and there exists an unsupported hack that makes the DVB-T receiver use NFS instead of SMB, which I installed to work around the Samba issue, which means that this client now also uses NFS). I use another machine to cut and clean recordings and while the P3 only has an fxp adapter (i.e. 100baseTX), I often max out this link for significant durations (hours at a time). The server seems to run as long as I let it (at least months, since I have upgraded it a few times since ZFS went into the tree). Since my applications/uses include R/W access to files via NFS, I can say that it at least can work reliably. That does not mean, that there can not be problems with NFS to ZFS based files, but there are real world uses that just work. In my case, there is little concurrent access to the NFS server (occasionally I record one or two video streams and watch a third one over the DVB-T box or another client, but there are hardly ever more than two NFS clients at a time). ZFS as a whole has rough edges (especially since the auto-tuning of kernel parameters does not account for it, yet). Regards, STefan From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 10:52: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 6A9CA16A41B for ; Sun, 7 Oct 2007 10:52:38 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from smtp010.mail.ukl.yahoo.com (smtp010.mail.ukl.yahoo.com [217.12.11.79]) by mx1.freebsd.org (Postfix) with SMTP id F341613C461 for ; Sun, 7 Oct 2007 10:52:37 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: (qmail 87042 invoked from network); 7 Oct 2007 10:52:36 -0000 Received: from unknown (HELO Gatekeeper.FreeBSD.org) (st.esser@80.135.115.157 with login) by smtp010.mail.ukl.yahoo.com with SMTP; 7 Oct 2007 10:52:36 -0000 X-YMail-OSG: 6BuI7oIVM1mudajnyKKBu0o6AH5fL_kapT.1z28GqFUpjjO5 Received: from StefanEsser.FreeBSD.org (se [192.168.0.10]) by Gatekeeper.FreeBSD.org (Postfix) with ESMTP id A37F02C06; Sun, 7 Oct 2007 12:52:35 +0200 (CEST) Received: by StefanEsser.FreeBSD.org (Postfix, from userid 200) id 6251F43B5; Sun, 7 Oct 2007 12:52:35 +0200 (CEST) Date: Sun, 7 Oct 2007 12:52:35 +0200 From: Stefan =?iso-8859-1?Q?E=DFer?= To: current@freebsd.org Message-ID: <20071007105235.GA2505@StefanEsser.FreeBSD.org> Mail-Followup-To: Stefan =?iso-8859-1?Q?E=DFer?= , current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Subject: [Patch] man page nsswitch(5) still references cached 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: Sun, 07 Oct 2007 10:52:38 -0000 The renaming of cached to nscd has apparently not been tracked in all man pages. At least in the case of nsswitch(5), there are still references to cached and cached.conf. The attached patch fixes this. I did not search for other occurences of "cached" with much effort, but found at least one other reference in src.con(5). Both are fixed in the attached patch, which I'd like to commit (after re approval) to -CURRENT. BTW: There appear to be broken man page related entries in Obsoletefiles.inc (perhaps because of a line length limit in the case of the latter two files in the following list???): OLD_FILES+=usr/share/man/man5/cached.conf.5 OLD_FILES+=usr/share/man/man8/cached.8 OLD_FILES+=usr/share/man/man3/set_assertion_failure_callback.3. OLD_FILES+=usr/share/man/man3/SSL_COMP_add_compression_method.3 This should probably be fixed at the same time ... (I do not attach a patch, but in case of the obsolete files the fix is obviously to add the missing ".gz" extension to each line ...) Regards, STefan PS: I have decided to CC re@ and to consider this mail as a request for approval, since I do not think that there is much debate and there seems to be only one way to fix this ;-) Index: share/man/man5/nsswitch.conf.5 =================================================================== RCS file: /usr/cvs/src/share/man/man5/nsswitch.conf.5,v retrieving revision 1.17 diff -u -r1.17 nsswitch.conf.5 --- share/man/man5/nsswitch.conf.5 22 Jan 2007 11:45:25 -0000 1.17 +++ share/man/man5/nsswitch.conf.5 7 Oct 2007 10:12:27 -0000 @@ -95,7 +95,7 @@ If this is present, it must be the only source for that entry. .It cache makes use of the -.Xr cached 8 +.Xr nscd 8 daemon. .El .Ss Databases @@ -218,17 +218,17 @@ .Xr nsswitch.conf 5 file. You should also enable caching for this database in -.Xr cached.conf 5 . +.Xr nscd.conf 5 . If for the particular query .Dq cache source returns success, no further sources are queried. -On the other hand, if there are no previously cached data, the +On the other hand, if there are no previously nscd data, the query result will be placed into the cache right after all other sources are processed. Note, that .Dq cache requires -.Xr cached 8 +.Xr nscd 8 daemon to be running. .Ss Compat mode: +/- syntax In historical multi-source implementations, the @@ -353,9 +353,9 @@ databases. .Sh SEE ALSO .Xr nsdispatch 3 , -.Xr cached.conf 5 , +.Xr nscd.conf 5 , .Xr resolv.conf 5 , -.Xr cached 8 , +.Xr nscd 8 , .Xr named 8 , .Xr ypbind 8 .Sh HISTORY Index: share/man/man5/src.conf.5 =================================================================== RCS file: /usr/cvs/src/share/man/man5/src.conf.5,v retrieving revision 1.15 diff -u -r1.15 src.conf.5 --- share/man/man5/src.conf.5 27 Aug 2007 20:22:59 -0000 1.15 +++ share/man/man5/src.conf.5 7 Oct 2007 10:40:23 -0000 @@ -440,7 +440,7 @@ .Pa nsswitch subsystem. The generic caching daemon, -.Xr cached 8 , +.Xr nscd 8 , will not be built either if this option is set. .It Va WITHOUT_OBJC .\" from FreeBSD: src/tools/build/options/WITHOUT_OBJC,v 1.1 2006/03/21 07:50:50 ru Exp From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 11:10: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 C8F8616A421; Sun, 7 Oct 2007 11:10:03 +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 6C4F813C461; Sun, 7 Oct 2007 11:10:03 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 0984A45E93; Sun, 7 Oct 2007 13:10:01 +0200 (CEST) Received: from localhost (cvl74.internetdsl.tpnet.pl [83.19.93.74]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id DD86E45E8F; Sun, 7 Oct 2007 13:09:49 +0200 (CEST) Date: Sun, 7 Oct 2007 13:09:41 +0200 From: Pawel Jakub Dawidek To: Dag-Erling Sm??rgrav Message-ID: <20071007110941.GA4644@garage.freebsd.pl> References: <4707569E.6010400@freebsd.org> <868x6gpk3i.fsf@ds4.des.no> <47083883.6000503@freebsd.org> <863awn9uoe.fsf@ds4.des.no> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="W/nzBZO5zC0uMSeA" Content-Disposition: inline In-Reply-To: <863awn9uoe.fsf@ds4.des.no> 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: Darren Reed , FreeBSD Current Subject: Re: ZFS & NFS integration... 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, 07 Oct 2007 11:10:03 -0000 --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 07, 2007 at 10:48:49AM +0200, Dag-Erling Sm??rgrav wrote: > Darren Reed writes: > > Dag-Erling Sm??rgrav wrote: > > > Darren Reed writes: > > > > Whats the planned status for ZFS+NFS with 7.0? > > > Don't Do It, basically. > > This sounds like a "shoot yourself in the foot" comment. > > > > Why? >=20 > I haven't figured out the exact details yet, but apparently when the > client closes a file that was opened read / write, the server stops > responding to that client. I never saw behaviour like that, and AFAIR noone told about such problems before. Actually I'm using NFS exported ZFS file systems in production at my company: beast:root:~# zfs get -r sharenfs tank | egrep -v 'sharenfs (-|off)' | wc= -l 28 The load is rather light, but I never seen a single problem. So based on other e-mails in this thread as well, it's seems it's not a well known issue. Any chance you could debug it further? My standpoint is that NFS over ZFS is supported by our port, if that's not true, we should work on this. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --W/nzBZO5zC0uMSeA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHCL51ForvXbEpPzQRAhHJAKCoT6fIqe+rkObEURU/d4sqvcmnEgCg+gQE RRfwrFYxOhzF8WvVDDmIHok= =pCEd -----END PGP SIGNATURE----- --W/nzBZO5zC0uMSeA-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 11:18: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 B34EC16A417; Sun, 7 Oct 2007 11:18:00 +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 5C59413C465; Sun, 7 Oct 2007 11:18:00 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 4D4B645EA7; Sun, 7 Oct 2007 13:17:59 +0200 (CEST) Received: from localhost (cvl74.internetdsl.tpnet.pl [83.19.93.74]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id B591945E93; Sun, 7 Oct 2007 13:17:49 +0200 (CEST) Date: Sun, 7 Oct 2007 13:17:41 +0200 From: Pawel Jakub Dawidek To: Darren Reed Message-ID: <20071007111741.GB4644@garage.freebsd.pl> References: <4707569E.6010400@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MfFXiAuoTsnnDAfZ" Content-Disposition: inline In-Reply-To: <4707569E.6010400@freebsd.org> 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: FreeBSD Current Subject: Re: ZFS & NFS integration... 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, 07 Oct 2007 11:18:00 -0000 --MfFXiAuoTsnnDAfZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Oct 06, 2007 at 02:34:22AM -0700, Darren Reed wrote: > Pawel, >=20 > Whats the planned status for ZFS+NFS with 7.0? My opinion is that it should work and people should try it, of course keeping the experimental status of ZFS in 7.0 in mind all the time. > A minor nit that I've just run into is needing to have an > empty /etc/exports file so that mountd starts...any thoughts > on making mountd more intelligent? It's just a matter of improving /etc/rc.d/mountd script, I guess. In my opinion it would be best to start mountd as a dependency if it's not enabled in rc.conf, but there are some ZFS file systems with sharenfs!=3Doff. Then we would start mountd (and other damons needed for NFS export to work) with /etc/zfs/exports file only. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --MfFXiAuoTsnnDAfZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHCMBVForvXbEpPzQRArNOAKCsvapyXCCfsIyp/KvnbEUGo30giACg8g9Q 20il/FETZtKUCpyhqE6ZkTg= =wH/q -----END PGP SIGNATURE----- --MfFXiAuoTsnnDAfZ-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 11:57:42 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 1207216A41A; Sun, 7 Oct 2007 11:57:42 +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 C90B213C448; Sun, 7 Oct 2007 11:57:41 +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 l97BvN6U045575 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Sun, 7 Oct 2007 07:57:24 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Sun, 7 Oct 2007 05:00:05 -0700 (PDT) From: Jeff Roberson X-X-Sender: jroberson@10.0.0.1 To: Marc Fonvieille In-Reply-To: <20071007095408.GA997@gothic.blackend.org> Message-ID: <20071007045911.Y912@10.0.0.1> References: <20071002165007.D587@10.0.0.1> <20071006074429.GB976@gothic.blackend.org> <20071006102113.GC976@gothic.blackend.org> <47077951.5030906@clearchain.com> <4707866F.7030605@FreeBSD.org> <20071006143141.GD976@gothic.blackend.org> <4707CF8D.3070303@u.washington.edu> <20071006191014.GB84780@abigail.blackend.org> <20071007012049.S912@10.0.0.1> <20071007013342.D912@10.0.0.1> <20071007095408.GA997@gothic.blackend.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Garrett Cooper , Benjamin Close , current@freebsd.org Subject: Re: ULE/yielding patch for testing. 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, 07 Oct 2007 11:57:42 -0000 On Sun, 7 Oct 2007, Marc Fonvieille wrote: > On Sun, Oct 07, 2007 at 01:35:50AM -0700, Jeff Roberson wrote: >>>> [...] >>>> Not really when the slowness does not exist with 6.X. >>> >>> I have experienced certain websites causing firefox to slow down >>> considerably. When I mouse over firefox the mouse begins to jerk as well >>> but when I move back away from firefox it seems fine again. I suspected >>> it was an x/firefox bug. >> >> Actually I double-checked this case with dailytech.com. It seems to be >> spending all of the cpu time in user-space in xwindows. So it seems that >> it is the new xwindows that has the problem. If you watch the 'TIME' field >> of top you can see that very little cpu time is attributed to firefox and >> quite a lot to X windows. So the windowing system is too busy to redraw >> mouse events even if we are scheduling it well. >> > > You mean Xorg 7.2 or 7.3 with -CURRENT? > Currently I observe the problem with Xorg 7.2 or 7.3 under -CURRENT, > when Xorg 7.2 with 6.2-STABLE is Ok (I did not try with Xorg 7.3 on > -STABLE, but I'm quite sure I'll end to same result). > On a completly different machine (a more recent one with a 2.8GHz > Celeron), the problem could be less obvious cause of the machine speed > but I can notice the difference between 6.2-STABLE and 7-CURRENT with > any Xorg version. Can you give a dozen lines of 'vmstat 1' output while rendering this page in 7.0 and 6.2? Thanks, Jeff > >> Jeff >> >>> >>> Although I also sometimes observe mysql hanging for a period of a half >>> second or so while running sysbench. I wonder if we don't have a >>> threading library bug? I know I observed this prior to the thread_lock >>> work so hopefully I didn't break it. >>> > > I think a lot of people missed that problem cause they run fast > machines. For me it's very difficult to track down the issue cause I'm > ignorant in these OS areas and the various logs and tools don't give > obvious information. > > -- > Marc > From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 12:05: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 9062216A46B for ; Sun, 7 Oct 2007 12:05:37 +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 271FC13C474 for ; Sun, 7 Oct 2007 12:05:32 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from [195.4.92.10] (helo=mx0.freenet.de) by mout1.freenet.de with esmtpa (Exim 4.68) (envelope-from ) id 1IeUt0-00064J-L8 for freebsd-current@freebsd.org; Sun, 07 Oct 2007 14:05:30 +0200 Received: from x11b5.x.pppool.de ([89.59.17.181]:54572 helo=peedub.jennejohn.org) by mx0.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.68 #6) id 1IeUt0-0006f9-Fi for freebsd-current@freebsd.org; Sun, 07 Oct 2007 14:05:30 +0200 Date: Sun, 7 Oct 2007 14:05:29 +0200 From: Gary Jennejohn To: freebsd-current@freebsd.org Message-ID: <20071007140529.058663cb@peedub.jennejohn.org> In-Reply-To: <1191604530.909.9.camel@workstation.martenvijn.nl> References: <47063652.8070106@unsane.co.uk> <1191604530.909.9.camel@workstation.martenvijn.nl> Organization: DENX Softwre Engineering GmbH X-Mailer: Claws Mail 3.0.2 (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: openoffice 2.3 package 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: Sun, 07 Oct 2007 12:05:37 -0000 On Fri, 05 Oct 2007 19:15:30 +0200 Marten Vijn wrote: > On Fri, 2007-10-05 at 13:08 +0000, Aryeh Friedman wrote: > > On 10/5/07, Vince wrote: > > > For some reason I couldnt run the 6.x versions of open office even with > > > compat6x, (core dumped.) So i have built my own. I couldnt find any > > > 7-CURRENT i386 packages online so I can make mine available to anyone > > > without the time/space to build one if anyone needs/wants it. > > > > For anyone who doesn't read -questions OO completely fails to build on > > 7-current amd64 > > > ftp://ooopackages.good-day.net/pub/OpenOffice.org/FreeBSD/2.2.1/FreeBSD7/amd64 > At least OOo_2.2.1_FreeBSD70X86_64_install_all.tbz has the problem that a) closing the window with ctrl-Q doesn't kill the OOo process b) trying to export to PDF kills OOo without producing any PDF output -- Gary Jennejohn From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 13:09: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 0D39816A468 for ; Sun, 7 Oct 2007 13:09:57 +0000 (UTC) (envelope-from marc@blackend.org) Received: from abigail.blackend.org (ns0.blackend.org [82.227.222.164]) by mx1.freebsd.org (Postfix) with ESMTP id 3213A13C4A5 for ; Sun, 7 Oct 2007 13:09:55 +0000 (UTC) (envelope-from marc@blackend.org) Received: from gothic.blackend.org (gothic.blackend.org [192.168.1.203]) by abigail.blackend.org (8.13.4/8.13.3) with ESMTP id l97D9Vxs005882; Sun, 7 Oct 2007 15:09:31 +0200 (CEST) (envelope-from marc@abigail.blackend.org) Received: from gothic.blackend.org (localhost.blackend.org [127.0.0.1]) by gothic.blackend.org (8.14.1/8.13.8) with ESMTP id l97D9VM5001152; Sun, 7 Oct 2007 15:09:31 +0200 (CEST) (envelope-from marc@gothic.blackend.org) Received: (from marc@localhost) by gothic.blackend.org (8.14.1/8.13.8/Submit) id l97D9T7P001151; Sun, 7 Oct 2007 15:09:29 +0200 (CEST) (envelope-from marc) Date: Sun, 7 Oct 2007 15:09:29 +0200 From: Marc Fonvieille To: Jeff Roberson Message-ID: <20071007130929.GA1132@gothic.blackend.org> References: <20071006102113.GC976@gothic.blackend.org> <47077951.5030906@clearchain.com> <4707866F.7030605@FreeBSD.org> <20071006143141.GD976@gothic.blackend.org> <4707CF8D.3070303@u.washington.edu> <20071006191014.GB84780@abigail.blackend.org> <20071007012049.S912@10.0.0.1> <20071007013342.D912@10.0.0.1> <20071007095408.GA997@gothic.blackend.org> <20071007045911.Y912@10.0.0.1> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: <20071007045911.Y912@10.0.0.1> X-Useless-Header: blackend.org X-Operating-System: FreeBSD 6.2-STABLE User-Agent: Mutt/1.5.15 (2007-04-06) Cc: Garrett Cooper , Benjamin Close , current@freebsd.org Subject: Re: ULE/yielding patch for testing. 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, 07 Oct 2007 13:09:57 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Oct 07, 2007 at 05:00:05AM -0700, Jeff Roberson wrote: > > > > You mean Xorg 7.2 or 7.3 with -CURRENT? > > Currently I observe the problem with Xorg 7.2 or 7.3 under -CURRENT, > > when Xorg 7.2 with 6.2-STABLE is Ok (I did not try with Xorg 7.3 on > > -STABLE, but I'm quite sure I'll end to same result). > > On a completly different machine (a more recent one with a 2.8GHz > > Celeron), the problem could be less obvious cause of the machine speed > > but I can notice the difference between 6.2-STABLE and 7-CURRENT with > > any Xorg version. > > Can you give a dozen lines of 'vmstat 1' output while rendering this page in > 7.0 and 6.2? > I attached the logs while rendering a french newspaper page. -- Marc --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="vmstat62.txt" procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad4 cd0 in sy cs us sy id 0 0 1 128016 864572 2 0 1 0 0 0 1 0 1437 3968 1335 19 3 78 0 0 0 128016 864572 2 0 0 0 0 0 2 0 1362 1495 757 4 2 94 0 0 0 128016 864572 2 0 0 0 0 0 0 0 1360 1284 736 8 2 91 0 0 0 128016 864572 0 0 0 0 0 0 0 0 1358 812 633 1 0 99 0 0 0 129464 863348 554 39 7 0 251 0 8 0 1382 2144 982 30 2 68 2 0 0 129464 863348 197 0 0 0 197 0 0 0 1379 2132 944 23 2 74 0 0 0 129464 863348 83 0 0 0 83 0 0 0 1373 1411 782 7 2 91 0 0 0 129464 863348 45 0 0 0 45 0 0 0 1373 1587 820 8 2 90 0 0 0 129464 863348 0 0 0 0 0 0 0 0 1364 1161 714 5 2 94 1 0 0 129492 862972 233 0 0 0 202 0 15 0 1583 5298 2042 81 8 11 1 0 0 130876 861384 567 0 0 0 223 0 19 0 1369 3867 1167 86 5 9 1 0 0 133124 858768 568 4 7 0 40 0 30 0 1376 2231 852 76 8 16 1 0 0 134416 857328 1252 0 0 0 935 0 10 0 1376 2089 896 91 4 5 1 0 0 135520 855780 815 15 4 0 499 0 13 0 1416 1831 907 91 2 7 1 2 0 137420 853884 661 0 5 0 241 0 6 0 1365 1650 774 94 2 5 2 0 0 137740 853216 229 0 8 0 138 0 16 0 1366 2531 954 95 3 2 0 0 0 137740 853212 135 0 0 0 133 0 0 0 1371 2001 938 28 1 71 0 0 0 137864 853088 31 0 0 0 0 0 0 0 1363 808 652 0 3 97 2 0 1 137844 853004 1182 0 4 0 951 0 9 0 1405 3621 1077 9 7 84 0 0 0 137908 852940 120 0 0 0 104 0 0 0 1453 5358 1553 11 2 88 0 0 0 137908 852940 0 0 0 0 0 0 0 0 1369 812 661 1 0 99 0 0 0 137908 852940 0 0 0 0 0 0 0 0 1367 772 647 0 2 98 0 0 0 137908 852940 0 0 0 0 0 0 0 0 1456 5297 1450 2 3 95 0 0 0 137908 852940 0 0 0 0 0 0 0 0 1398 2011 883 0 1 99 0 0 0 137908 852940 0 0 0 0 0 0 0 0 1366 797 646 1 1 98 0 0 0 137908 852940 2 0 0 0 0 0 0 0 1368 761 646 0 0 100 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="vmstat7.txt" procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad4 cd0 in sy cs us sy id 0 0 0 258476 588312 0 0 0 0 0 0 0 0 1220 1732 1477065 15 3 82 0 0 0 258476 588312 0 0 0 0 0 0 0 0 1218 1859 1712290 8 2 91 0 0 0 258476 588312 0 0 0 0 0 0 0 0 1219 1014 1743108 2 1 97 0 0 0 258476 588328 0 0 0 0 4 0 4 0 1220 1044 1841916 4 4 92 0 0 0 258476 588328 0 0 0 0 0 0 0 0 1221 1915 1692427 10 5 85 1 0 1 258476 588324 1811 0 0 0 1814 0 0 0 1229 7340 1354707 19 10 71 1 0 0 258604 588116 2805 0 0 0 2800 0 0 0 1453 10766 372468 60 21 19 1 0 0 259628 587320 555 0 0 0 376 0 1 0 1372 7203 624241 50 16 33 2 0 1 259048 587128 2999 0 0 0 2957 0 1 0 1384 10622 1725 79 21 0 1 0 0 259172 586920 1061 0 0 0 1011 0 0 0 1482 6675 2116 81 19 0 1 0 0 261312 585016 768 0 0 0 348 0 3 0 1624 5813 11076 77 23 0 2 0 1 265612 581652 2022 0 0 0 1202 0 2 0 1571 6680 2132 84 16 1 1 0 0 266764 579496 1539 0 0 0 1041 0 7 0 1298 5764 39597 87 11 2 0 0 0 266764 579456 371 0 0 0 361 0 0 0 1221 2744 1223736 26 9 66 1 0 0 266764 579456 0 0 0 0 16 0 10 0 1303 4894 1550900 8 9 84 0 0 0 266764 579456 0 0 0 0 0 0 0 0 1228 1420 1778206 3 2 95 0 0 0 266764 579456 0 0 0 0 0 0 1 0 1217 811 1796256 1 1 98 1 0 0 266764 579480 0 0 0 0 6 0 6 0 1239 1439 1832112 2 3 95 0 0 0 266764 579472 696 0 0 0 694 0 0 0 1313 6648 979531 40 8 52 0 0 0 266764 579320 1332 0 0 0 1295 0 0 0 1346 295285 463331 16 61 23 0 0 1 266764 579320 0 0 0 0 0 0 0 0 1239 2218 1835521 2 2 96 2 0 0 266764 579320 0 0 0 0 0 0 0 0 1214 770 1910521 0 2 98 1 0 0 266764 579320 0 0 0 0 0 0 0 0 1213 797 1894476 1 3 96 0 0 1 266764 579316 1 0 0 0 0 0 0 0 1222 792 1833074 1 2 98 --17pEHd4RhPHOinZp-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 14:21: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 8D90E16A49A; Sun, 7 Oct 2007 14:21:45 +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 4D43813C46E; Sun, 7 Oct 2007 14:21:44 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 3DD00668D86; Sun, 7 Oct 2007 16:02:42 +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 nhOotuT6BG59; Sun, 7 Oct 2007 16:02:38 +0200 (CEST) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 575A0668D6F; Sun, 7 Oct 2007 16:02:38 +0200 (CEST) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.13.8/8.13.8/Submit) id l97E2cto044832; Sun, 7 Oct 2007 16:02:38 +0200 (CEST) (envelope-from rdivacky) Date: Sun, 7 Oct 2007 16:02:37 +0200 From: Roman Divacky To: current@freebsd.org Message-ID: <20071007140237.GA44735@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: peter@freebsd.org Subject: pad argument for mmap/lseek/etc. 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, 07 Oct 2007 14:21:45 -0000 hi 3 months ago Peter Wemm removed "pad" argument from mmap/lseek/etc. syscalls arguments. Unfortunately he forgot to update the struct XYZ_args definitions shipped with the actual functions like this: vm/vm_mmap.c: #ifndef _SYS_SYSPROTO_H_ struct mmap_args { void *addr; size_t len; int prot; int flags; int fd; long pad; off_t pos; }; #endif /* * MPSAFE */ int mmap(td, uap) struct thread *td; struct mmap_args *uap; it would be nice to get this removed. I'd submit a patch but I dont know what syscalls this affected. thnx roman From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 15:15: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 4030416A41A; Sun, 7 Oct 2007 15:15:45 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.freebsd.org (Postfix) with ESMTP id EFCC013C455; Sun, 7 Oct 2007 15:15:44 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (p54A5735D.dip.t-dialin.net [84.165.115.93]) by redbull.bpaserver.net (Postfix) with ESMTP id C625B2E2AB; Sun, 7 Oct 2007 17:15:35 +0200 (CEST) Received: from deskjail (deskjail.Leidinger.net [192.168.1.109]) by outgoing.leidinger.net (Postfix) with ESMTP id D687E5B4800; Sun, 7 Oct 2007 17:14:38 +0200 (CEST) Date: Sun, 7 Oct 2007 17:15:41 +0200 From: Alexander Leidinger To: Stefan =?UTF-8?B?RcOfZXI=?= Message-ID: <20071007171541.4bd00627@deskjail> In-Reply-To: <20071007105235.GA2505@StefanEsser.FreeBSD.org> References: <20071007105235.GA2505@StefanEsser.FreeBSD.org> X-Mailer: Claws Mail 3.0.1 (GTK+ 2.10.14; i686-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-14.6, required 8, BAYES_00 -15.00, MIME_8BIT_HEADER 0.30, RDNS_DYNAMIC 0.10) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No Cc: current@freebsd.org Subject: Re: [Patch] man page nsswitch(5) still references cached 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: Sun, 07 Oct 2007 15:15:45 -0000 Quoting Stefan E=C3=9Fer (Sun, 7 Oct 2007 12:52:35 +0200): > The renaming of cached to nscd has apparently not been tracked in all man > pages. At least in the case of nsswitch(5), there are still references to > cached and cached.conf. The attached patch fixes this. I did not search > for other occurences of "cached" with much effort, but found at least one > other reference in src.con(5). Both are fixed in the attached patch, which > I'd like to commit (after re approval) to -CURRENT. >=20 > BTW: There appear to be broken man page related entries in Obsoletefiles.= inc > (perhaps because of a line length limit in the case of the latter two fil= es > in the following list???): Why do you think it is a length limit which is the cause of the problems you see? > OLD_FILES+=3Dusr/share/man/man5/cached.conf.5 > OLD_FILES+=3Dusr/share/man/man8/cached.8 > OLD_FILES+=3Dusr/share/man/man3/set_assertion_failure_callback.3. > OLD_FILES+=3Dusr/share/man/man3/SSL_COMP_add_compression_method.3 >=20 > This should probably be fixed at the same time ... >=20 > (I do not attach a patch, but in case of the obsolete files the fix is > obviously to add the missing ".gz" extension to each line ...) I can confirm that if the files are installed as XXX.gz, they have to be listed as XXX.gz in ObsoleteFiles.inc. Bye, Alexander. --=20 If you'd like to keep track of applications in the FreeBSD ports tree, take= a look at FreshPorts; http://www.freshports.org/ http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 15:27: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 4F83E16A418; Sun, 7 Oct 2007 15:27:09 +0000 (UTC) (envelope-from csjp@sub.vaned.net) Received: from sub.vaned.net (sub.vaned.net [205.200.235.40]) by mx1.freebsd.org (Postfix) with ESMTP id 1F51B13C461; Sun, 7 Oct 2007 15:27:08 +0000 (UTC) (envelope-from csjp@sub.vaned.net) Received: by sub.vaned.net (Postfix, from userid 1001) id 4A4F117391; Sun, 7 Oct 2007 10:24:29 -0500 (CDT) Date: Sun, 7 Oct 2007 10:24:29 -0500 From: "Christian S.J. Peron" To: Katsuji Ishikawa Message-ID: <20071007152429.GA67909@sub.vaned.net> References: <20071007040103.GA58108@sub.vaned.net> 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, "Christian S.J. Peron" Subject: Re: heavy network load 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, 07 Oct 2007 15:27:09 -0000 On Sun, Oct 07, 2007 at 02:39:28PM +0900, Katsuji Ishikawa wrote: > I tested your patch (sched_ule.c.diff). > Then this network problem was solved! > > Thank you. > I suspect this patch will be committed sooner then later. Thanks for the quick turn around on testing. -- Christian S.J. Peron csjp@FreeBSD.ORG FreeBSD Committer From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 17:12: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 219F016A417 for ; Sun, 7 Oct 2007 17:12:04 +0000 (UTC) (envelope-from fbsd-st@donut.de) Received: from smtp.free.de (smtp.free.de [193.28.225.103]) by mx1.freebsd.org (Postfix) with ESMTP id 792A013C45B for ; Sun, 7 Oct 2007 17:12:03 +0000 (UTC) (envelope-from fbsd-st@donut.de) Received: (qmail 28632 invoked by uid 98); 7 Oct 2007 18:45:20 +0200 Received: from 193.28.225.103 by smtp.free.de (envelope-from , uid 82) with qmail-scanner-1.25 (clamdscan: 0.90.1/3618. Clear:RC:1(193.28.225.103):. Processed in 0.044716 secs); 07 Oct 2007 16:45:20 -0000 X-Qmail-Scanner-Mail-From: fbsd-st@donut.de via smtp.free.de X-Qmail-Scanner: 1.25 (Clear:RC:1(193.28.225.103):. Processed in 0.044716 secs) Received: from smtp.free.de (HELO [192.168.40.3]) (peanuts@[193.28.225.103]) (envelope-sender ) by smtp.free.de (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 7 Oct 2007 18:45:20 +0200 Message-ID: <47090D1F.2090502@donut.de> Date: Sun, 07 Oct 2007 18:45:19 +0200 From: Rolf Witt User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.6) Gecko/20070728 Thunderbird/2.0.0.6 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 07 Oct 2007 17:35:11 +0000 Subject: Question about netstat -s output (xx discarded due to memory problems) 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, 07 Oct 2007 17:12:04 -0000 Hi, which is the exact cause of: "46 discarded due to memory problems" (section tcp) in a netstat -s output? Since the Sourcen of in the middle of Septembers see I there values greater than zero. The values increase, if I look from my Windows Firefox Clients via Squid Flash movies (youtube.com or spiegel.de), but not with normal http-traffic. Local nettraffic (samba, netio, etc.) does no effect of this counter. Do I have a problem? rowi From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 18:41:35 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 5699F16A418; Sun, 7 Oct 2007 18:41:35 +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 1397513C467; Sun, 7 Oct 2007 18:41:34 +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 l97IfW39003784 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Sun, 7 Oct 2007 14:41:33 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Sun, 7 Oct 2007 11:44:13 -0700 (PDT) From: Jeff Roberson X-X-Sender: jroberson@10.0.0.1 To: Marc Fonvieille In-Reply-To: <20071007130929.GA1132@gothic.blackend.org> Message-ID: <20071007114345.E912@10.0.0.1> References: <20071006102113.GC976@gothic.blackend.org> <47077951.5030906@clearchain.com> <4707866F.7030605@FreeBSD.org> <20071006143141.GD976@gothic.blackend.org> <4707CF8D.3070303@u.washington.edu> <20071006191014.GB84780@abigail.blackend.org> <20071007012049.S912@10.0.0.1> <20071007013342.D912@10.0.0.1> <20071007095408.GA997@gothic.blackend.org> <20071007045911.Y912@10.0.0.1> <20071007130929.GA1132@gothic.blackend.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@freebsd.org Subject: Re: ULE/yielding patch for testing. 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, 07 Oct 2007 18:41:35 -0000 On Sun, 7 Oct 2007, Marc Fonvieille wrote: > On Sun, Oct 07, 2007 at 05:00:05AM -0700, Jeff Roberson wrote: >>> >>> You mean Xorg 7.2 or 7.3 with -CURRENT? >>> Currently I observe the problem with Xorg 7.2 or 7.3 under -CURRENT, >>> when Xorg 7.2 with 6.2-STABLE is Ok (I did not try with Xorg 7.3 on >>> -STABLE, but I'm quite sure I'll end to same result). >>> On a completly different machine (a more recent one with a 2.8GHz >>> Celeron), the problem could be less obvious cause of the machine speed >>> but I can notice the difference between 6.2-STABLE and 7-CURRENT with >>> any Xorg version. >> >> Can you give a dozen lines of 'vmstat 1' output while rendering this page in >> 7.0 and 6.2? >> > > I attached the logs while rendering a french newspaper page. Is this a SMP kernel on a UP machine? If so can you try without SMP in your config? > > -- > Marc > From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 18:59: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 8CEFE16A418 for ; Sun, 7 Oct 2007 18:59:15 +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 1FF8413C465 for ; Sun, 7 Oct 2007 18:59:14 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 21538 invoked by uid 399); 7 Oct 2007 18:59:14 -0000 Received: from localhost (HELO slave.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 7 Oct 2007 18:59:14 -0000 X-Originating-IP: 127.0.0.1 Date: Sun, 7 Oct 2007 11:59:12 -0700 (PDT) From: Doug Barton To: Aryeh Friedman In-Reply-To: Message-ID: References: <4705CA47.9090101@delphij.net> <20071005080544.GA48744@freebie.xs4all.nl> 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; format=flowed; charset=US-ASCII Cc: Wilko Bulte , freebsd-current@freebsd.org, d@delphij.net Subject: Re: viral license free fork of freebsd 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, 07 Oct 2007 18:59:15 -0000 Guys, License issues are off topic for -current. If you want to talk about actual code for a new project that is very closely related to FreeBSD then -hackers might be the right list. Anything else belongs on -chat. Thanks, Doug -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 19:13: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 2E91F16A41A for ; Sun, 7 Oct 2007 19:13:42 +0000 (UTC) (envelope-from freebsd-questions@stellablue.org) Received: from mail5.neteze.com (mail5.neteze.com [209.160.67.25]) by mx1.freebsd.org (Postfix) with ESMTP id 05EE213C4A6 for ; Sun, 7 Oct 2007 19:13:41 +0000 (UTC) (envelope-from freebsd-questions@stellablue.org) Received: from 66-169-93-064.dhcp.ahvl.nc.charter.com ([66.169.93.64] helo=[127.0.0.1]) by mail5.neteze.com with esmtpa (Exim 4.63) (envelope-from ) id 1IeaVn-0000OL-20 for freebsd-current@freebsd.org; Sun, 07 Oct 2007 18:05:55 +0000 Message-ID: <47091FDE.4060808@stellablue.org> Date: Sun, 07 Oct 2007 14:05:18 -0400 From: Steven Brown 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-Antivirus: avast! (VPS 000778-5, 10/06/2007), Outbound message X-Antivirus-Status: Clean Subject: Panic: mutex Giant not owned cam_xpt.c :4799 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, 07 Oct 2007 19:13:42 -0000 Just decided to try out the 0907 snapshot of -CURRENT (amd64) and it won't boot off the install CD Thought I would post as much info as I could for interested parties. I have to copy by hand, so I will try to include as much as I can. panic: mutex Giant not owned at /usr/src/sys/cam/cam_xpt.c :4799 This error occurs right after "md0: Preloaded image .... The motherboard is an Asus P5M2-R, with dual bge ethernets (on mb), a Adaptec 3405 SATA/SAS RAID PCI-e card (aac driver), and has an Intel Q6600 quad core. 4GB of RAM. You will soon see why I included the information on the Adaptec card. This hardware works fine using 6.2-RELEASE p8 -- well, at least i386 does. This system has a modified src/sys/dev/aac which includes the vendor ID info for the 3405/3805 cards and has no problems booting (and running), detecting Adaptec card, etc. I also have a CD with the same snapshot (CURRENT, 0907) in an i386 version (not AMD64) which appears to produce the same error. Upon the panic, the system entered the debugger and I typed "trace" to get the following from AMD64 snapshot: Tracing pid 26 tid 100026 td 0xffffff0002245680 kdb_enter() at kdb_enter+0x31 panic() at panic+0x173 _mtx_assert() at _mtx_assert+0xd6 xpt_release_simq() at xpt_release_simq()+0x27 aac_alloc_commands() at aac_alloc_commands()+0x156 aac_command_thread() at aac_command_thread()+0xe5 fork_exit() at fork_exit+0x12a fork_trampoline() at fork_trampoline()+0xe --- trap 0, rip = 0, rsp = 0xffffffffac6fdd30, rbp = 0 --- Hope this helps someone, Steve From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 19:55:36 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 AB89716A420 for ; Sun, 7 Oct 2007 19:55:36 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from spacemail2-out.mgmt.space.net (spacemail2-out.mgmt.Space.Net [194.97.149.148]) by mx1.freebsd.org (Postfix) with ESMTP id 340C013C45B for ; Sun, 7 Oct 2007 19:55:35 +0000 (UTC) (envelope-from se@FreeBSD.org) X-SpaceNet-SBRS: None X-IronPort-AV: E=Sophos;i="4.21,240,1188770400"; d="scan'208";a="63447180" Received: from mail.atsec.com ([195.30.252.105]) by spacemail2-out.mgmt.space.net with ESMTP; 07 Oct 2007 21:55:34 +0200 Received: from [192.168.0.12] (p5087739D.dip.t-dialin.net [80.135.115.157]) (Authenticated sender: se@atsec.com) by mail.atsec.com (Postfix) with ESMTP id 4BB2672092F; Sun, 7 Oct 2007 21:55:34 +0200 (CEST) Message-ID: <470939B5.2090309@FreeBSD.org> Date: Sun, 07 Oct 2007 21:55:33 +0200 From: Stefan Esser User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Alexander Leidinger References: <20071007105235.GA2505@StefanEsser.FreeBSD.org> <20071007171541.4bd00627@deskjail> In-Reply-To: <20071007171541.4bd00627@deskjail> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: [Patch] man page nsswitch(5) still references cached 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: Sun, 07 Oct 2007 19:55:36 -0000 Alexander Leidinger schrieb: >> BTW: There appear to be broken man page related entries in Obsoletefiles.inc >> (perhaps because of a line length limit in the case of the latter two files >> in the following list???): > > Why do you think it is a length limit which is the cause of the > problems you see? Well, see the last two lines, 63 chars long, 10 for "OLD_FILES+=" and 53 chars for the file name. It may be that files were added to the list by a cut&paste action and that some characters had wrapped around to the next line and were forgotten. But it is not relevant, just strange. >> OLD_FILES+=usr/share/man/man5/cached.conf.5 >> OLD_FILES+=usr/share/man/man8/cached.8 >> OLD_FILES+=usr/share/man/man3/set_assertion_failure_callback.3. >> OLD_FILES+=usr/share/man/man3/SSL_COMP_add_compression_method.3 [...] > I can confirm that if the files are installed as XXX.gz, they have to > be listed as XXX.gz in ObsoleteFiles.inc. Yes, and the four lines above are the only ones that do not end in ".gz". I forgot to CC my mail to re@, but Michael Bushkov reviewed it, found that I had replaced one instance of cached too many and the corrected patch to re@ for approval ... Regards, STefan From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 21:25: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 18FA716A417 for ; Sun, 7 Oct 2007 21:25:48 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from mail.kuban.ru (mail.kuban.ru [62.183.66.246]) by mx1.freebsd.org (Postfix) with ESMTP id 7A23513C461 for ; Sun, 7 Oct 2007 21:25:47 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from bsam.ru ([85.172.12.42]) by mail.kuban.ru (8.9.1/8.9.1) with ESMTP id l97KkCH8012626 for ; Mon, 8 Oct 2007 00:46:24 +0400 (MSD) Received: (from bsam@localhost) by bsam.ru (8.14.1/8.14.1/Submit) id l97Kmppe002026; Mon, 8 Oct 2007 00:48:51 +0400 (MSD) (envelope-from bsam@ipt.ru) X-Authentication-Warning: bsam.ru: bsam set sender to bsam@ipt.ru using -f To: freebsd-current@freebsd.org References: <47063652.8070106@unsane.co.uk> From: Boris Samorodov Date: Mon, 08 Oct 2007 00:48:51 +0400 Message-ID: <10944700@bsam.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: openoffice 2.3 package 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, 07 Oct 2007 21:25:48 -0000 On Fri, 5 Oct 2007 13:08:31 +0000 Aryeh Friedman wrote: > On 10/5/07, Vince wrote: > > For some reason I couldnt run the 6.x versions of open office even with > > compat6x, (core dumped.) So i have built my own. I couldnt find any > > 7-CURRENT i386 packages online so I can make mine available to anyone > > without the time/space to build one if anyone needs/wants it. > For anyone who doesn't read -questions OO completely fails to build on > 7-current amd64 Build at 05.10.2007: https://and.ipt.ru/tb/logs/7-amd64-FreeBSD/openoffice.org-2.3.0.log https://and.ipt.ru/tb/packages/7-amd64-FreeBSD/All/openoffice.org-2.3.0.tbz WBR -- bsam From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 22:14: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 BBA6B16A418 for ; Sun, 7 Oct 2007 22:14:44 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mx1.freebsd.org (Postfix) with ESMTP id 30A7F13C44B for ; Sun, 7 Oct 2007 22:14:43 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l97MEgkB074061 for ; Mon, 8 Oct 2007 08:14:42 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l97MEgAI074060 for freebsd-current@freebsd.org; Mon, 8 Oct 2007 08:14:42 +1000 (EST) (envelope-from peter) Date: Mon, 8 Oct 2007 08:14:42 +1000 From: Peter Jeremy To: freebsd-current@freebsd.org Message-ID: <20071007221442.GA74030@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PNTmBPCT7hxwcZjr" Content-Disposition: inline X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.16 (2007-06-09) Subject: bgfsck strikes 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: Sun, 07 Oct 2007 22:14:44 -0000 --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable FreeBSD server.vk2pj.dyndns.org 7.0-CURRENT FreeBSD 7.0-CURRENT #9: Wed Oct= 3 12:00:03 EST 2007 root@server.vk2pj.dyndns.org:/var/obj/k7/usr/src/= sys/server i386 A short power glitch last night reset my main server at 1929. It had been reasonably idle and I wanted it back so I let it reboot normally and relied on bgfsck to cleanup. bgfsck cleared 13 unreferenced files in /var and /usr and all seemed OK. At 0247, it panic'd "panic: getblk: bp 0xcceb52cc not locked" with the following backtrace: #8 0xc055c945 in panic (fmt=3D0xc073040f "getblk: bp %p not locked") at /u= sr/src/sys/kern/kern_shutdown.c:547 #9 0xc05c4843 in getblk (vp=3D0xc2c9ccc0, blkno=3D0x18b88dc0, size=3D0x400= 0, slpflag=3DVariable "slpflag" is not available. ) at /usr/src/sys/kern/vfs_bio.c:2666 #10 0xc05c4e24 in breadn (vp=3D0xc2c9ccc0, blkno=3DUnhandled dwarf expressi= on opcode 0x93 ) at /usr/src/sys/kern/vfs_bio.c:786 #11 0xc05c4fac in bread (vp=3D0xc2c9ccc0, blkno=3DUnhandled dwarf expressio= n opcode 0x93 ) at /usr/src/sys/kern/vfs_bio.c:734 #12 0xc0664d7a in ffs_update (vp=3D0xc31f3660, waitfor=3D0x0) at /usr/src/s= ys/ufs/ffs/ffs_inode.c:103 #13 0xc06845ea in ufs_inactive (ap=3D0xd62a9adc) at /usr/src/sys/ufs/ufs/uf= s_inode.c:159 #14 0xc06f4d15 in VOP_INACTIVE_APV (vop=3D0xc07828a0, a=3D0xd62a9adc) at vn= ode_if.c:1513 #15 0xc05d4401 in vinactive (vp=3D0xc31f3660, td=3D0xc2ffd210) at vnode_if.= h:796 #16 0xc05d7d66 in vput (vp=3D0xc31f3660) at /usr/src/sys/kern/vfs_subr.c:21= 97 #17 0xc05e2c1b in vn_close (vp=3D0xc31f3660, flags=3D0xa, file_cred=3D0xc30= 1a400, td=3D0xc2ffd210) at /usr/src/sys/kern/vfs_vnops.c:295 #18 0xc05e2d17 in vn_closefile (fp=3D0xc308e8b8, td=3D0xc2ffd210) at /usr/s= rc/sys/kern/vfs_vnops.c:868 #19 0xc05316d2 in fdrop (fp=3D0xc308e8b8, td=3D0xc2ffd210) at file.h:297 #20 0xc0532c03 in closef (fp=3D0xc308e8b8, td=3D0xc2ffd210) at /usr/src/sys= /kern/kern_descrip.c:1958 #21 0xc0532f91 in kern_close (td=3D0xc2ffd210, fd=3D0x6) at /usr/src/sys/ke= rn/kern_descrip.c:1054 #22 0xc053302a in close (td=3D0xc2ffd210, uap=3D0xd62a9cfc) at /usr/src/sys= /kern/kern_descrip.c:1006 #23 0xc06dfffa in syscall (frame=3D0xd62a9d38) at /usr/src/sys/i386/i386/tr= ap.c:1008 #24 0xc06cdbb0 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s= :196 This time, I manually fsck'd it and was greeted with several thousand errors. Looking through them, it looks very much like UFS had just stopped garbage collecting unreferenced files so deleted files were just left lying around. Is it worth trying to investigate this further or should I just put it down to "don't use bgfsck"? --=20 Peter Jeremy --PNTmBPCT7hxwcZjr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHCVpS/opHv/APuIcRAkneAJ44PfKlJLrTMybyN1kfDMDg9mU22ACeJBI/ xmBIr5U011u2RsWEnhm7XL0= =/26q -----END PGP SIGNATURE----- --PNTmBPCT7hxwcZjr-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 22:44: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 280E116A41A for ; Sun, 7 Oct 2007 22:44:22 +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 E9F7013C45D for ; Sun, 7 Oct 2007 22:44:21 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so1481930waf for ; Sun, 07 Oct 2007 15:44:21 -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=5NL/pfoRck50jly+jCAWYHyNomi3a5WmOVgGLoYTEME=; b=jywGfNpt30mY7tPH9ckOnW7Rz6wwTMl6rr4wlbvO4SR2HDrV1W7zjO2AtVutjx8Plwu48fLicCPDGgjsVCopBCGeMp8TfTi2eXNhO94GRhc08He2l/1VZ5SnXxnoFNbl6MP5lDrlYXieK2qXCd6BLx0wTf/KLe8HZlDjOLBsmmA= 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=iHwl6l5BLcJM7BaIS6rZ/JS1CrRX8P9AK40oKg2IoELqEtpGIcVHv3HS2IzNWiZFI8c5fYsjXwoj2JnzCft4VV/MtmusbiJJ21VbkwCA4xVKJpW0GqLM2bpeQzpi16vL+OO8zooOPtmuEs2jfNHtmjEiB3YJppR/Gilo7ORfA8Q= Received: by 10.114.38.2 with SMTP id l2mr10027964wal.1191797061573; Sun, 07 Oct 2007 15:44:21 -0700 (PDT) Received: by 10.114.13.15 with HTTP; Sun, 7 Oct 2007 15:44:21 -0700 (PDT) Message-ID: Date: Sun, 7 Oct 2007 15:44:21 -0700 From: "Kip Macy" To: "Eric Schuele" In-Reply-To: <46FC90EC.4060808@computer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46FC8079.6030304@computer.org> <20070928042939.GA34316@troutmask.apl.washington.edu> <46FC89FB.2070506@computer.org> <20070928051252.GA34607@troutmask.apl.washington.edu> <46FC90EC.4060808@computer.org> Cc: freebsd-current@freebsd.org, Steve Kargl 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: Sun, 07 Oct 2007 22:44:22 -0000 On 9/27/07, Eric Schuele wrote: > 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 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. > > 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? You need to actually execute a different shell. Changing the variable isn't going to help. -Kip From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 22:47: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 34F6C16A540 for ; Sun, 7 Oct 2007 22:47:02 +0000 (UTC) (envelope-from e.schuele@computer.org) Received: from smtpauth14.prod.mesa1.secureserver.net (smtpauth14.prod.mesa1.secureserver.net [64.202.165.39]) by mx1.freebsd.org (Postfix) with SMTP id E1E1B13C480 for ; Sun, 7 Oct 2007 22:47:01 +0000 (UTC) (envelope-from e.schuele@computer.org) Received: (qmail 21009 invoked from network); 7 Oct 2007 22:47:01 -0000 Received: from unknown (96.226.25.79) by smtpauth14.prod.mesa1.secureserver.net (64.202.165.39) with ESMTP; 07 Oct 2007 22:47:00 -0000 Message-ID: <470961E4.8060700@computer.org> Date: Sun, 07 Oct 2007 17:47:00 -0500 From: Eric Schuele User-Agent: Thunderbird 2.0.0.6 (X11/20070921) MIME-Version: 1.0 To: Kip Macy References: <46FC8079.6030304@computer.org> <20070928042939.GA34316@troutmask.apl.washington.edu> <46FC89FB.2070506@computer.org> <20070928051252.GA34607@troutmask.apl.washington.edu> <46FC90EC.4060808@computer.org> In-Reply-To: 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="------------enigD1AD7D962A238DD3EF8BDAEC" Cc: freebsd-current@freebsd.org, Steve Kargl 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: Sun, 07 Oct 2007 22:47:02 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD1AD7D962A238DD3EF8BDAEC Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 10/07/2007 17:44, Kip Macy wrote: > On 9/27/07, Eric Schuele wrote: >> 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 = 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 al= ways >>>> 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. >> Hmm... yeah.. I found the bug report after you mentioned tcsh. Howeve= r >> 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 > You need to actually execute a different shell. Changing the variable > isn't going to help. I did execute a different shell. Tried several in fact. >=20 > -Kip >=20 >=20 --=20 Regards, Eric --------------enigD1AD7D962A238DD3EF8BDAEC 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) iD8DBQFHCWHkngSDRM3IXUoRAvgGAJ9sVi77PI4bfvPQErxYS//cbFZ+awCfeJW6 0ae2J0ubA2GfNG1XVaC++Cs= =SBZ/ -----END PGP SIGNATURE----- --------------enigD1AD7D962A238DD3EF8BDAEC-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 23:13: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 B833416A421 for ; Sun, 7 Oct 2007 23:13:22 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mx1.freebsd.org (Postfix) with ESMTP id 3FBE913C45B for ; Sun, 7 Oct 2007 23:13:21 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l97NCrO8074361; Mon, 8 Oct 2007 09:12:53 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l97NCqgC074360; Mon, 8 Oct 2007 09:12:52 +1000 (EST) (envelope-from peter) Date: Mon, 8 Oct 2007 09:12:52 +1000 From: Peter Jeremy To: Rolf Witt Message-ID: <20071007231252.GI74080@turion.vk2pj.dyndns.org> References: <47090D1F.2090502@donut.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline In-Reply-To: <47090D1F.2090502@donut.de> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org Subject: Re: Question about netstat -s output (xx discarded due to memory problems) 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, 07 Oct 2007 23:13:22 -0000 --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-Oct-07 18:45:19 +0200, Rolf Witt wrote: >which is the exact cause of: "46 discarded due to memory problems" >(section tcp) in a netstat -s output? Looking at the source, this is tcps_rcvmemdrop - which is incremented in sys/netinet/tcp_reass.c:tcp_reass() when either: - A segment is dropped to prevent the TCP reassembly queue getting too large (this will also increment net.inet.tcp.reass.overflows) - A new queue entry can't be allocated because tcp_reass_zone is full. >Since the Sourcen of in the middle of Septembers see I there values >greater than zero. This implies you are receiving excessive out-of-order packets - which is undesirable but not under your control. --=20 Peter Jeremy --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHCWf0/opHv/APuIcRAuL7AJ4kczSplTxug+e1fdmm2EkWqBL0XwCguGu4 41CJaoYnaMwhhnReveffu10= =+NHp -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 23:19: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 5058A16A419 for ; Sun, 7 Oct 2007 23:19:29 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from aaron.protected-networks.net (aaron.protected-networks.net [202.12.127.66]) by mx1.freebsd.org (Postfix) with ESMTP id 0B15513C46A for ; Sun, 7 Oct 2007 23:19:28 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from localhost (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id E8CECC42D for ; Sun, 7 Oct 2007 19:06:36 -0400 (EDT) Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [202.12.127.84]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Iain Michael Butler", Issuer "Protected Networks Certificate Authority" (verified OK)) (Authenticated sender: imb@protected-networks.net) by aaron.protected-networks.net (Postfix) with ESMTP id 79764C614 for ; Sun, 7 Oct 2007 19:06:22 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=protected-networks.net; s=200705; t=1191798382; bh=hwx3GKKyQlYuIN gnXiyH0bSYMOkblJGfY/Lg4SySzhI=; h=DomainKey-Signature:Message-ID: Date:From:User-Agent:MIME-Version:To:Subject:X-Enigmail-Version: OpenPGP:Content-Type:Content-Transfer-Encoding; b=n6/QwJy2un/K+7Ct qRg2SMbi+Dc9ZwlJCnscrjUih60/4WwZkJWQn8HTmy8Ru7dMCvd0gf0HKKclSESGdyF ZOYNNwo1KKh4dyEioRzNuMJ8ay5cic6CBMvn51zz/47+K DomainKey-Signature: a=rsa-sha1; s=200509; d=protected-networks.net; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:subject: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=PKMAi4Y/Ub9TdRlizkRF3/Rd3ZR8xJcO/V6sjkqG508Chqn+9v6OuZmlERYgCwynK rQC/SVQ25TgJkjrf4cU0QqFHNBFQ5lJazJbSxpC+mXaZGhgOvlfkjNFbEw7FD1i Message-ID: <4709666D.5070504@protected-networks.net> Date: Sun, 07 Oct 2007 19:06:21 -0400 From: Michael Butler User-Agent: Thunderbird 2.0.0.6 (X11/20070903) MIME-Version: 1.0 To: freebsd-current X-Enigmail-Version: 0.95.2 OpenPGP: id=0442D492 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Gkrellmd prompts "sleeping thread" 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, 07 Oct 2007 23:19:29 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 For whatever reason I seem to be able to reliably reproduce a panic on - -current by running gkrellmd on one of my machines yet another (this one) has no problems at all :-( Any thoughts welcome .. mail# more info.0 Dump header from device /dev/ar0s1b Architecture: i386 Architecture Version: 2 Dump Length: 97525760B (93 MB) Blocksize: 512 Dumptime: Sun Oct 7 17:15:51 2007 Hostname: mail.auburn.protected-networks.net Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.0-CURRENT #1: Thu Oct 4 22:33:53 EDT 2007 root@mail.auburn.protected-networks.net:/usr/obj/usr/src/sys/AUBURN Panic String: sleeping thread Dump Parity: 3933400909 Bounds: 0 Dump Status: good mail# kgdb /boot/kernel.old/kernel vmcore.0 kgdb: kvm_nlist(_stopped_cpus): kgdb: kvm_nlist(_stoppcbs): [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 "i386-marcel-freebsd". (no debugging symbols found)...Attempt to extract a component of a value that is not a structure pointer. (kgdb) bt #0 0xc059f32b in doadump () #1 0xc059f7a4 in boot () #2 0xc059fb18 in panic () #3 0xc05cf172 in propagate_priority () #4 0xc05cfa66 in turnstile_wait () #5 0xc0593f11 in _mtx_lock_sleep () #6 0xc0676011 in intsmb_rawintr () #7 0xc0583a4d in ithread_loop () #8 0xc0580774 in fork_exit () #9 0xc07058a0 in fork_trampoline () -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHCWZtQv9rrgRC1JIRAnrDAJ9prbau6NmtT+ZHMI4lDopRLWo/hQCcDICE ibHiIY24lOuvWsbxAPOg5T4= =kcyS -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 00:41: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 37D1516A417 for ; Mon, 8 Oct 2007 00:41:03 +0000 (UTC) (envelope-from tijl@ulyssis.org) Received: from nibbel.kulnet.kuleuven.ac.be (nibbel.kulnet.kuleuven.ac.be [134.58.240.41]) by mx1.freebsd.org (Postfix) with ESMTP id B7DFD13C45A for ; Mon, 8 Oct 2007 00:41:02 +0000 (UTC) (envelope-from tijl@ulyssis.org) Received: from localhost (localhost [127.0.0.1]) by nibbel.kulnet.kuleuven.ac.be (Postfix) with ESMTP id ACAE94D33C; Mon, 8 Oct 2007 02:09:48 +0200 (CEST) Received: from smtps02.kuleuven.be (smtpshost02.kulnet.kuleuven.be [134.58.240.75]) by nibbel.kulnet.kuleuven.ac.be (Postfix) with ESMTP id 8E3FE4DA91; Mon, 8 Oct 2007 02:09:34 +0200 (CEST) Received: from kalimero.kotnet.org (kalimero.kotnet.org [10.4.16.222]) by smtps02.kuleuven.be (Postfix) with ESMTP id 662ABF3863; Mon, 8 Oct 2007 02:09:34 +0200 (CEST) Received: from kalimero.kotnet.org (kalimero.kotnet.org [127.0.0.1]) by kalimero.kotnet.org (8.14.1/8.14.1) with ESMTP id l9809YBV009976; Mon, 8 Oct 2007 02:09:34 +0200 (CEST) (envelope-from tijl@ulyssis.org) X-Kuleuven: This mail passed the K.U.Leuven mailcluster From: Tijl Coosemans To: freebsd-current@freebsd.org Date: Mon, 8 Oct 2007 02:09:32 +0200 User-Agent: KMail/1.9.7 References: <46FC8079.6030304@computer.org> <470961E4.8060700@computer.org> In-Reply-To: <470961E4.8060700@computer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710080209.33529.tijl@ulyssis.org> X-Virus-Scanned: by KULeuven Antivirus Cluster Cc: Kip Macy , Steve Kargl , Eric Schuele 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: Mon, 08 Oct 2007 00:41:03 -0000 On Monday 08 October 2007 00:47:00 Eric Schuele wrote: > On 10/07/2007 17:44, Kip Macy wrote: >> On 9/27/07, Eric Schuele wrote: >>> 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 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. >>> >>> 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? >> >> You need to actually execute a different shell. Changing the >> variable isn't going to help. > > I did execute a different shell. Tried several in fact. I'm not sure it will help, but you might want to give the patch in http://www.freebsd.org/cgi/query-pr.cgi?pr=115469 a try. From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 01:27: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 02EE816A418 for ; Mon, 8 Oct 2007 01:27:15 +0000 (UTC) (envelope-from SRS0=fec1bda5f3f7c3c77be41be13bf3dfb92ce82747=481=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 1E0EE13C457 for ; Mon, 8 Oct 2007 01:27:11 +0000 (UTC) (envelope-from SRS0=fec1bda5f3f7c3c77be41be13bf3dfb92ce82747=481=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 NLH95354; Sun, 07 Oct 2007 18:25:54 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 9615E4500E; Sun, 7 Oct 2007 18:25:53 -0700 (PDT) To: Peter Jeremy In-Reply-To: Your message of "Mon, 08 Oct 2007 08:14:42 +1000." <20071007221442.GA74030@turion.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1191806753_39355P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Sun, 07 Oct 2007 18:25:53 -0700 From: "Kevin Oberman" Message-Id: <20071008012553.9615E4500E@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ;; X-Sender: X-To_Name: Peter Jeremy X-To_Domain: optushome.com.au X-To: Peter Jeremy X-To_Email: peterjeremy@optushome.com.au X-To_Alias: peterjeremy Cc: freebsd-current@freebsd.org Subject: Re: bgfsck strikes 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: Mon, 08 Oct 2007 01:27:15 -0000 --==_Exmh_1191806753_39355P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Mon, 8 Oct 2007 08:14:42 +1000 > From: Peter Jeremy > Sender: owner-freebsd-current@freebsd.org > > FreeBSD server.vk2pj.dyndns.org 7.0-CURRENT FreeBSD 7.0-CURRENT #9: Wed Oct 3 12:00:03 EST 2007 root@server.vk2pj.dyndns.org:/var/obj/k7/usr/src/sys/server i386 > > A short power glitch last night reset my main server at 1929. It had > been reasonably idle and I wanted it back so I let it reboot normally > and relied on bgfsck to cleanup. bgfsck cleared 13 unreferenced files > in /var and /usr and all seemed OK. > > At 0247, it panic'd "panic: getblk: bp 0xcceb52cc not locked" with > the following backtrace: > #8 0xc055c945 in panic (fmt=0xc073040f "getblk: bp %p not locked") at /usr/src/sys/kern/kern_shutdown.c:547 > #9 0xc05c4843 in getblk (vp=0xc2c9ccc0, blkno=0x18b88dc0, size=0x4000, slpflag=Variable "slpflag" is not available.) at /usr/src/sys/kern/vfs_bio.c:2666 > #10 0xc05c4e24 in breadn (vp=0xc2c9ccc0, blkno=Unhandled dwarf expression opcode 0x93 > ) at /usr/src/sys/kern/vfs_bio.c:786 > #11 0xc05c4fac in bread (vp=0xc2c9ccc0, blkno=Unhandled dwarf expression opcode 0x93 > ) at /usr/src/sys/kern/vfs_bio.c:734 > #12 0xc0664d7a in ffs_update (vp=0xc31f3660, waitfor=0x0) at /usr/src/sys/ufs/ffs/ffs_inode.c:103 > #13 0xc06845ea in ufs_inactive (ap=0xd62a9adc) at /usr/src/sys/ufs/ufs/ufs_inode.c:159 > #14 0xc06f4d15 in VOP_INACTIVE_APV (vop=0xc07828a0, a=0xd62a9adc) at vnode_if.c:1513 > #15 0xc05d4401 in vinactive (vp=0xc31f3660, td=0xc2ffd210) at vnode_if.h:796 > #16 0xc05d7d66 in vput (vp=0xc31f3660) at /usr/src/sys/kern/vfs_subr.c:2197 > #17 0xc05e2c1b in vn_close (vp=0xc31f3660, flags=0xa, file_cred=0xc301a400, td=0xc2ffd210) > at /usr/src/sys/kern/vfs_vnops.c:295 > #18 0xc05e2d17 in vn_closefile (fp=0xc308e8b8, td=0xc2ffd210) at /usr/src/sys/kern/vfs_vnops.c:868 > #19 0xc05316d2 in fdrop (fp=0xc308e8b8, td=0xc2ffd210) at file.h:297 > #20 0xc0532c03 in closef (fp=0xc308e8b8, td=0xc2ffd210) at /usr/src/sys/kern/kern_descrip.c:1958 > #21 0xc0532f91 in kern_close (td=0xc2ffd210, fd=0x6) at /usr/src/sys/kern/kern_descrip.c:1054 > #22 0xc053302a in close (td=0xc2ffd210, uap=0xd62a9cfc) at /usr/src/sys/kern/kern_descrip.c:1006 > #23 0xc06dfffa in syscall (frame=0xd62a9d38) at /usr/src/sys/i386/i386/trap.c:1008 > #24 0xc06cdbb0 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:196 > > This time, I manually fsck'd it and was greeted with several thousand > errors. Looking through them, it looks very much like UFS had just > stopped garbage collecting unreferenced files so deleted files were > just left lying around. > > Is it worth trying to investigate this further or should I just put it > down to "don't use bgfsck"? Silly question, but is the disk doing write caching? If so, it is possible that the data in the cache was lost, leaving inconsistency in the metadata. It's not a trivial issue to deal with, especially on disks that lie about whether data has actually been written to disk. -- 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_1191806753_39355P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFHCYchkn3rs5h7N1ERAsNcAKCxG8/MCzg//f8rFoh/4bcMOrOQvQCeLGi/ UuD008VNOLZwS/YOwwKtNhQ= =KBkY -----END PGP SIGNATURE----- --==_Exmh_1191806753_39355P-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 01:48: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 493C416A419 for ; Mon, 8 Oct 2007 01:48:44 +0000 (UTC) (envelope-from e.schuele@computer.org) Received: from smtpout05.prod.mesa1.secureserver.net (smtpout05-04.prod.mesa1.secureserver.net [64.202.165.221]) by mx1.freebsd.org (Postfix) with SMTP id 047F713C447 for ; Mon, 8 Oct 2007 01:48:43 +0000 (UTC) (envelope-from e.schuele@computer.org) Received: (qmail 13158 invoked from network); 8 Oct 2007 01:48:42 -0000 Received: from unknown (96.226.25.79) by smtpout05-04.prod.mesa1.secureserver.net (64.202.165.221) with ESMTP; 08 Oct 2007 01:48:42 -0000 Message-ID: <47098C79.2030700@computer.org> Date: Sun, 07 Oct 2007 20:48:41 -0500 From: Eric Schuele User-Agent: Thunderbird 2.0.0.6 (X11/20070921) MIME-Version: 1.0 To: Tijl Coosemans References: <46FC8079.6030304@computer.org> <470961E4.8060700@computer.org> <200710080209.33529.tijl@ulyssis.org> In-Reply-To: <200710080209.33529.tijl@ulyssis.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="------------enig4FE5809987C3780CC6E183D0" Cc: Kip Macy , freebsd-current@freebsd.org, Steve Kargl 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: Mon, 08 Oct 2007 01:48:44 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig4FE5809987C3780CC6E183D0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable On 10/07/2007 19:09, Tijl Coosemans wrote: > On Monday 08 October 2007 00:47:00 Eric Schuele wrote: >> On 10/07/2007 17:44, Kip Macy wrote: >>> On 9/27/07, Eric Schuele wrote: >>>> 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 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. >>>> 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? >>> You need to actually execute a different shell. Changing the >>> variable isn't going to help. >> I did execute a different shell. Tried several in fact. >=20 > I'm not sure it will help, but you might want to give the patch in > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D115469 a try. >=20 >=20 To read the description, I don't believe I am experiencing this problem. After further investigation, I came to the following conclusion. Imagine one function, main() for example, written to call another function, my_func(), 10 times. However on the 6th call to said function... gdb refuses to step into the function... instead taking 100% of your cpu, seemingly forever. That is what I am seeing. Do you still think the patch is applicable to my situation? If so I will give it a shot. --=20 Regards, Eric --------------enig4FE5809987C3780CC6E183D0 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) iD8DBQFHCYx5ngSDRM3IXUoRAjIiAKDAhfH5IKgujj2fOWwRO+bg+XAoEwCfbgU+ aSS7CORdrJGoBfogoMYtI4w= =ioMa -----END PGP SIGNATURE----- --------------enig4FE5809987C3780CC6E183D0-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 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 6D21B16A417 for ; Mon, 8 Oct 2007 03:25:28 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from aaron.protected-networks.net (aaron.protected-networks.net [202.12.127.66]) by mx1.freebsd.org (Postfix) with ESMTP id 2312913C43E for ; Mon, 8 Oct 2007 03:25:28 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from localhost (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 695A7C668 for ; Sun, 7 Oct 2007 23:25:27 -0400 (EDT) Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [202.12.127.84]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Iain Michael Butler", Issuer "Protected Networks Certificate Authority" (verified OK)) (Authenticated sender: imb@protected-networks.net) by aaron.protected-networks.net (Postfix) with ESMTP id 4CC5CC1E6 for ; Sun, 7 Oct 2007 23:25:15 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=protected-networks.net; s=200705; t=1191813915; bh=HnKPJ4nYa2eUQz DZJ1eBYeQbWLOrUdnToSIQ+i1MDck=; h=DomainKey-Signature:Message-ID: Date:From:User-Agent:MIME-Version:To:Subject:References: In-Reply-To:X-Enigmail-Version:OpenPGP:Content-Type: Content-Transfer-Encoding; b=nJ/bjUKFjdkqaMP3M6Cllb8/4FSCT9Tdv0iPm aAYGKhKXA3dU9rQrAe/q1pTH/R7/AzKB0BSuJ9YylEM2tyvzYx9Fe68iVe72LxKrGEC 4dFlufaLRpwuDv6CL+sRNs1W DomainKey-Signature: a=rsa-sha1; s=200509; d=protected-networks.net; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:subject: references:in-reply-to:x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=JeZsTExBvk1ObwT/y616aAqUsj1qaIprvNcR8+vEDLZnFXFiiafBuWLg/HMax5u/D iyksAHey8B2mSYMySuzvB5OyQFqAoCk8eXAVaHj0iGj1p/XaDxrK5B9UBRkO7Mm Message-ID: <4709A31A.3080201@protected-networks.net> Date: Sun, 07 Oct 2007 23:25:14 -0400 From: Michael Butler User-Agent: Thunderbird 2.0.0.6 (X11/20070903) MIME-Version: 1.0 To: freebsd-current References: <4709666D.5070504@protected-networks.net> In-Reply-To: <4709666D.5070504@protected-networks.net> X-Enigmail-Version: 0.95.2 OpenPGP: id=0442D492 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Gkrellmd prompts "sleeping thread" 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, 08 Oct 2007 03:25:28 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I wrote: > For whatever reason I seem to be able to reliably reproduce a panic on > -current by running gkrellmd on one of my machines yet another (this > one) has no problems at all :-( [ .. snip .. ] > This GDB was configured as "i386-marcel-freebsd". > (no debugging symbols found)...Attempt to extract a component of a value > that is not a structure pointer. > (kgdb) bt > #0 0xc059f32b in doadump () > #1 0xc059f7a4 in boot () > #2 0xc059fb18 in panic () > #3 0xc05cf172 in propagate_priority () > #4 0xc05cfa66 in turnstile_wait () > #5 0xc0593f11 in _mtx_lock_sleep () > #6 0xc0676011 in intsmb_rawintr () .. as a further data point, removing the intpm driver (which also provides intsmb) avoids the panic. Something odd with intsmb? Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHCaMaQv9rrgRC1JIRAmJrAJ9PvRgDYrCswp6K71Z98X8dEsjAfwCgxgj5 mvYHgERL3PWqOyT5gVKcZfE= =dSLr -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 05:41: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 4688016A419 for ; Mon, 8 Oct 2007 05:41:49 +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 F3F9913C4BA for ; Mon, 8 Oct 2007 05:41:48 +0000 (UTC) (envelope-from e.schuele@computer.org) Received: (qmail 962 invoked from network); 8 Oct 2007 05:41:48 -0000 Received: from unknown (96.226.25.79) by smtpauth02.prod.mesa1.secureserver.net (64.202.165.182) with ESMTP; 08 Oct 2007 05:41:47 -0000 Message-ID: <4709C31A.1010900@computer.org> Date: Mon, 08 Oct 2007 00:41:46 -0500 From: Eric Schuele User-Agent: Thunderbird 2.0.0.6 (X11/20070921) MIME-Version: 1.0 To: Tijl Coosemans References: <46FC8079.6030304@computer.org> <470961E4.8060700@computer.org> <200710080209.33529.tijl@ulyssis.org> In-Reply-To: <200710080209.33529.tijl@ulyssis.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="------------enig71B66F0628D242F621BCF46B" Cc: Kip Macy , freebsd-current@freebsd.org, Steve Kargl 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: Mon, 08 Oct 2007 05:41:49 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig71B66F0628D242F621BCF46B Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable On 10/07/2007 19:09, Tijl Coosemans wrote: > On Monday 08 October 2007 00:47:00 Eric Schuele wrote: >> On 10/07/2007 17:44, Kip Macy wrote: >>> On 9/27/07, Eric Schuele wrote: >>>> 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 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. >>>> 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? >>> You need to actually execute a different shell. Changing the >>> variable isn't going to help. >> I did execute a different shell. Tried several in fact. >=20 > I'm not sure it will help, but you might want to give the patch in > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D115469 a try. I have given the patch a try and it appears to be working! Very nice. I take a better look tomorrow... but it certainly looks fixed. Thanks. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >=20 >=20 --=20 Regards, Eric --------------enig71B66F0628D242F621BCF46B 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) iD8DBQFHCcMbngSDRM3IXUoRAs1TAJ9FOJQgINAfMmjPOXbfq8ehk+iPCwCg6xH2 Y0KRi//QVjgOsK1xRqK63tk= =ArWs -----END PGP SIGNATURE----- --------------enig71B66F0628D242F621BCF46B-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 06:21: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 396F316A419 for ; Mon, 8 Oct 2007 06:21:58 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.186]) by mx1.freebsd.org (Postfix) with ESMTP id EFC1C13C45A for ; Mon, 8 Oct 2007 06:21:57 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so589688rvb for ; Sun, 07 Oct 2007 23:21:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:subject:message-id:reply-to:mime-version:content-type:content-disposition:user-agent; bh=YHYewwzEmB4NSpZn3NQdZAwdLMmB0pjYFR6SsVAfBYg=; b=YCcW5ur2Z5MjbqWVeYubfLRO2JpjmcuexdHcgImNRe95mKoLO7kBImJnM8Y67LQY5qU09Nkwkf64OV3P9jMz0hjBcZkrxRT/XXepowvT4MP5SkML6i2Nj5QyFqv8oB3mhPa6swb4Tibc69tdFNbbk6ubc5C8abyQY9cQIyDPev0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:subject:message-id:reply-to:mime-version:content-type:content-disposition:user-agent; b=YqyZD7Jf5yd/mfyiu3kh0DtPLKPWZwUoI+5vIxZeDoE9sZdf1fHmB6ogIK5oVgE20agi23UNyTRMAopVmmAr/tuomYU91iNG8BLDyy9f8y2igUBJ/KjA+j6cB0nJ+SD1Z6M+615/TVU38o7ZrWUnb5K9hdzZksIPzkXz3qBgoA8= Received: by 10.114.183.1 with SMTP id g1mr10403764waf.1191824516885; Sun, 07 Oct 2007 23:21:56 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id j38sm11694854waf.2007.10.07.23.21.52 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 07 Oct 2007 23:21:55 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l986HxBU047981 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 8 Oct 2007 15:17:59 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l986HwCB047980 for freebsd-current@FreeBSD.org; Mon, 8 Oct 2007 15:17:58 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 8 Oct 2007 15:17:58 +0900 From: Pyun YongHyeon To: freebsd-current@FreeBSD.org Message-ID: <20071008061758.GF46694@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: CFT: vr(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@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, 08 Oct 2007 06:21:58 -0000 --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline It seems that there had been several stability issues in vr(4). Here is mimimal patch that make vr(4) work reliably under heavy network loads. The patch does the following: - Always check writability of mbuf before padding and make a writable copy of the mbuf if mbuf is marked as read-only. - Before padding is done check remaining bytes such that it can safely extend buffer size of the mbuf. - Before padding always check the return value of m_defrag(9). - Zero out pad space to avoid leaking data. If you have vr(4) hardware please give it spin and let me know the result. -- Regards, Pyun YongHyeon --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="vr.pad.patch" Index: if_vr.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_vr.c,v retrieving revision 1.126 diff -u -r1.126 if_vr.c --- if_vr.c 23 Apr 2007 12:19:02 -0000 1.126 +++ if_vr.c 8 Oct 2007 06:14:41 -0000 @@ -1217,6 +1217,7 @@ struct vr_desc *cur_tx, *n_tx; struct vr_desc *f = NULL; uint32_t cval; + int padlen; if (ifp->if_drv_flags & IFF_DRV_OACTIVE) return; @@ -1250,11 +1251,33 @@ * ourselves. */ if (m_head->m_pkthdr.len < VR_MIN_FRAMELEN) { - if (m_head->m_next != NULL) - m_head = m_defrag(m_head, M_DONTWAIT); - m_head->m_pkthdr.len += VR_MIN_FRAMELEN - m_head->m_len; + padlen = VR_MIN_FRAMELEN - m_head->m_pkthdr.len; + if (M_WRITABLE(m_head) == 0) { + m = m_dup(m_head, M_DONTWAIT); + if (m == NULL) { + IFQ_DRV_PREPEND(&ifp->if_snd, m_head); + break; + } + m_freem(m_head); + m_head = m; + } + if (m_head->m_next != NULL || + M_TRAILINGSPACE(m_head) < padlen) { + m = m_defrag(m_head, M_DONTWAIT); + if (m == NULL) { + IFQ_DRV_PREPEND(&ifp->if_snd, m_head); + break; + } + m_head = m; + } + /* + * Manually pad short frames, and zero the pad space + * to avoid leaking data. + */ + bzero(mtod(m_head, char *) + m_head->m_pkthdr.len, + padlen); + m_head->m_pkthdr.len += padlen; m_head->m_len = m_head->m_pkthdr.len; - /* XXX: bzero the padding bytes */ } n_tx = cur_tx; --envbJBWh7q8WU6mo-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 07:05: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 85D3916A469 for ; Mon, 8 Oct 2007 07:05:12 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id 324AE13C481 for ; Mon, 8 Oct 2007 07:05:12 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 8D05841C756; Mon, 8 Oct 2007 09:05:10 +0200 (CEST) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id 4VjG0hZoDdX5; Mon, 8 Oct 2007 09:05:05 +0200 (CEST) Received: by mail.cksoft.de (Postfix, from userid 66) id 128CA41C752; Mon, 8 Oct 2007 09:05:05 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id D5053444885; Mon, 8 Oct 2007 07:04:32 +0000 (UTC) Date: Mon, 8 Oct 2007 07:04:32 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Pyun YongHyeon In-Reply-To: <20071008061758.GF46694@cdnetworks.co.kr> Message-ID: <20071008070345.E6043@maildrop.int.zabbadoz.net> References: <20071008061758.GF46694@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@FreeBSD.org Subject: Re: CFT: vr(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, 08 Oct 2007 07:05:12 -0000 On Mon, 8 Oct 2007, Pyun YongHyeon wrote: > It seems that there had been several stability issues in vr(4). > Here is mimimal patch that make vr(4) work reliably under heavy > network loads. The patch does the following: > - Always check writability of mbuf before padding and make a > writable copy of the mbuf if mbuf is marked as read-only. > - Before padding is done check remaining bytes such that it can > safely extend buffer size of the mbuf. > - Before padding always check the return value of m_defrag(9). > - Zero out pad space to avoid leaking data. > > If you have vr(4) hardware please give it spin and let me know > the result. Had you seen wpaul's posting to net@ a few weeks ago. That had a patch attached as well. What about that? -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT Software is harder than hardware so better get it right the first time. From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 07:19:14 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 8FA8E16A421; Mon, 8 Oct 2007 07:19:14 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.freebsd.org (Postfix) with ESMTP id 2FB1713C459; Mon, 8 Oct 2007 07:19:14 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (p54A55168.dip.t-dialin.net [84.165.81.104]) by redbull.bpaserver.net (Postfix) with ESMTP id BE3A92E1DD; Mon, 8 Oct 2007 09:19:03 +0200 (CEST) Received: from webmail.leidinger.net (webmail.Leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id CCEB15B4800; Mon, 8 Oct 2007 09:18:06 +0200 (CEST) Received: (from www@localhost) by webmail.leidinger.net (8.14.1/8.13.8/Submit) id l987I6kT087729; Mon, 8 Oct 2007 09:18:06 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde MIME library) with HTTP; Mon, 08 Oct 2007 09:18:06 +0200 Message-ID: <20071008091806.4gum80p05ckwc480@webmail.leidinger.net> X-Priority: 3 (Normal) Date: Mon, 08 Oct 2007 09:18:06 +0200 From: Alexander Leidinger To: Stefan Esser References: <20071007105235.GA2505@StefanEsser.FreeBSD.org> <20071007171541.4bd00627@deskjail> <470939B5.2090309@FreeBSD.org> In-Reply-To: <470939B5.2090309@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1.4) / FreeBSD-7.0 X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-12.904, required 8, BAYES_00 -15.00, J_CHICKENPOX_35 0.60, MIME_QP_LONG_LINE 1.40, RDNS_DYNAMIC 0.10) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No Cc: current@FreeBSD.org Subject: Re: [Patch] man page nsswitch(5) still references cached 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: Mon, 08 Oct 2007 07:19:14 -0000 Quoting Stefan Esser (from Sun, 07 Oct 2007 21:55:33 +0200)= : > Alexander Leidinger schrieb: >>> BTW: There appear to be broken man page related entries in =20 >>> Obsoletefiles.inc >>> (perhaps because of a line length limit in the case of the latter two fi= les >>> in the following list???): >> >> Why do you think it is a length limit which is the cause of the >> problems you see? > > Well, see the last two lines, 63 chars long, 10 for "OLD_FILES+=3D" and > 53 chars for the file name. It may be that files were added to the list > by a cut&paste action and that some characters had wrapped around to > the next line and were forgotten. But it is not relevant, just strange. So you don't think it is a length limitation in make which causes the =20 problem, but a length limitation somewhere before adding it to =20 ObsoleteFiles.inc? Bye, Alexander. --=20 The world is coming to an end... SAVE YOUR BUFFERS!! http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 07: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 45EF216A417 for ; Mon, 8 Oct 2007 07:32:50 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mx1.freebsd.org (Postfix) with ESMTP id C293F13C4AC for ; Mon, 8 Oct 2007 07:32:49 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l987WdC2075409; Mon, 8 Oct 2007 17:32:39 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l987WdOs075408; Mon, 8 Oct 2007 17:32:39 +1000 (EST) (envelope-from peter) Date: Mon, 8 Oct 2007 17:32:39 +1000 From: Peter Jeremy To: Kevin Oberman Message-ID: <20071008073239.GA75381@turion.vk2pj.dyndns.org> References: <20071007221442.GA74030@turion.vk2pj.dyndns.org> <20071008012553.9615E4500E@ptavv.es.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline In-Reply-To: <20071008012553.9615E4500E@ptavv.es.net> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org Subject: Re: bgfsck strikes 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: Mon, 08 Oct 2007 07:32:50 -0000 --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-Oct-07 18:25:53 -0700, Kevin Oberman wrote: >Silly question, but is the disk doing write caching? I have hw.ata.wc=3D"0" and judging by the disk write performance, caching really is off. --=20 Peter Jeremy --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHCd0X/opHv/APuIcRAvV1AKCedMHOO50P130hwmMl42C4w1joxQCgr6XS EZWaBOqQ6D+TAbNFhZTF1Q4= =rD55 -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 07:33: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 45FD316A417 for ; Mon, 8 Oct 2007 07:33:01 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by mx1.freebsd.org (Postfix) with ESMTP id B3FC513C447 for ; Mon, 8 Oct 2007 07:33:00 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so1609455waf for ; Mon, 08 Oct 2007 00:32:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=6R9e+Ej9lMcRYO96RcL8NNltjQzonAKBtlGrPqGTLrA=; b=EZqAlUwpIrRbdNl6ZKKpzt1HW2+sUg9sgz+ew1UDrjunyydn6cR55ysd4DYXRjV/WxJnyFrJNZgfr7weSjWtk2G5/r/x0MJ3qdlemaq9OB8cznTdo67agUHs9XaxE+FMwhK1LDb1621o0PpbP61wQvCnz0J1xLIybHfTIXwoOxg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=aI5JTN1Qq4hqCWqXmmhOEVAjarJQTTxddlYQeY52wSpwtHhHm+Qm/20I0OvOp868gupDum6Sb+ytOqJ9lOiSkI2IcJljVztgW/4T5KJLlg8F7JE5/V69l+j7o7ACelMchwRggXAEljv7xSqeenJ69DIH1lkzxs1UTwAhW79ehmU= Received: by 10.114.199.1 with SMTP id w1mr429276waf.1191828779419; Mon, 08 Oct 2007 00:32:59 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id k24sm11791357waf.2007.10.08.00.32.54 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 08 Oct 2007 00:32:58 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l987TCPn048191 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Oct 2007 16:29:12 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l987TBBw048190; Mon, 8 Oct 2007 16:29:11 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 8 Oct 2007 16:29:11 +0900 From: Pyun YongHyeon To: "Bjoern A. Zeeb" Message-ID: <20071008072911.GG46694@cdnetworks.co.kr> References: <20071008061758.GF46694@cdnetworks.co.kr> <20071008070345.E6043@maildrop.int.zabbadoz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071008070345.E6043@maildrop.int.zabbadoz.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@FreeBSD.org Subject: Re: CFT: vr(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@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, 08 Oct 2007 07:33:01 -0000 On Mon, Oct 08, 2007 at 07:04:32AM +0000, Bjoern A. Zeeb wrote: > On Mon, 8 Oct 2007, Pyun YongHyeon wrote: > > >It seems that there had been several stability issues in vr(4). > >Here is mimimal patch that make vr(4) work reliably under heavy > >network loads. The patch does the following: > >- Always check writability of mbuf before padding and make a > > writable copy of the mbuf if mbuf is marked as read-only. > >- Before padding is done check remaining bytes such that it can > > safely extend buffer size of the mbuf. > >- Before padding always check the return value of m_defrag(9). > >- Zero out pad space to avoid leaking data. > > > >If you have vr(4) hardware please give it spin and let me know > >the result. > > Had you seen wpaul's posting to net@ a few weeks ago. That had a patch > attached as well. What about that? > Yep, and I also asked for testing a patch for the issue. He said testing the patch would take a while and I'm still waiting for the result. http://lists.freebsd.org/pipermail/freebsd-current/2007-August/076495.html -- Regards, Pyun YongHyeon From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 09:56: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 5D18216A420 for ; Mon, 8 Oct 2007 09:56:05 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from spacemail1-out.mgmt.space.net (spacemail1-out.mgmt.Space.Net [194.97.149.146]) by mx1.freebsd.org (Postfix) with ESMTP id D7F8A13C480 for ; Mon, 8 Oct 2007 09:56:04 +0000 (UTC) (envelope-from se@FreeBSD.org) X-SpaceNet-SBRS: None X-IronPort-AV: E=Sophos;i="4.21,242,1188770400"; d="scan'208";a="66974443" Received: from mail.atsec.com ([195.30.252.105]) by spacemail1-out.mgmt.space.net with ESMTP; 08 Oct 2007 11:56:03 +0200 Received: from [10.2.2.88] (frueh.atsec.com [217.110.13.170]) (Authenticated sender: se@atsec.com) by mail.atsec.com (Postfix) with ESMTP id 1543D7208ED; Mon, 8 Oct 2007 11:56:01 +0200 (CEST) Message-ID: <4709FEB0.80004@FreeBSD.org> Date: Mon, 08 Oct 2007 11:56:00 +0200 From: Stefan Esser User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org, freebsd-current@freebsd.org References: <20071002164246.GA986@hades.panopticon> <20071003003329.GA78359@hades.panopticon> In-Reply-To: <20071003003329.GA78359@hades.panopticon> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: Subject: Re: Need motherboard for home fileserver 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, 08 Oct 2007 09:56:05 -0000 Dmitry Marakasov schrieb: > * Dmitry Marakasov (amdmi3@amdmi3.ru) wrote: > > Thanks for you replies so far. Now after some digging I understand a bit > what I actually need. > > Well, I hoped to get a SocketAM2 board for AthlonX2, as it is 30-40% > cheaper than Core2Duo with similar performance, but most of AM2 > motherboards use nForce chipset, which is unsupported by CURRENT. What made you come to that conclusion??? I use an Abit AN-M2HD (and I know I'm not alone with that main-board) which is based on the nForce 7050/630a and works very well. I had one issue with an LCD connected to the HDMI port (a HDMI-to-DVI cable is bundled) and since it happened outside X11 (i.e., with a text console), it might have been a bogus enabling of HDCP. (Hard to describe, the screen showed a picture like an unsynchronized TV, but steady; only a power cycle allowed recovery ...) > The only solution I've found is M2N32-SLI (thanks Craig), but I'll > need to buy video card and Intel Gbit NIC. The video integrated into the 7050/630a works surprisingly well with the Vesa driver, but is also supported by the current (binary) nvidia driver. (Also, since the upgrade of xorg to 7.3, there is an issue in the port, which reports an API mismatch, but there is a work-around and the port is being fixed to support xorg 7.3, too.) > Though Core 2 Duo CPUs are more expensive, choice of motherboards is > much wider, and they are generally cheaper than M2N32-SLI, so price > of AMD/Intel platforms is nearly equal. I've found some MB's with I prefered the AMD X2 for several reasons, one of the most important ones was idle CPU power consumption. The Core 2 (and typical chip-sets) consume 10W to 15W more idle power, which translates to about $30 a year where I live ... > integrated video and Intel ethernet: ASUS P5B-VM DO, Intel DG33BUC, > Intel DG33FBC. I think I'll buy one of those, but just to be sure, > are those statements right: > - Marvell/NVidia NICs suck, and I am right that I definitely need Intel. > (what about RealTec, btw?) > - ICH8DO should work as well as ICH8 and G33 should work as well as G965 > (didn't find menton of ICH8DO in src/sys/dev/ata/ata-chipset.c) > - ADI*/Realtec(ALC*)/Sigmatel(STAC*) HDA CODECs provide more or less > equal sound quality. And it can be considered `good' to > non-audiophiles. Well, you may want to take a look at the Abit AN-M2 (or -M2HD, if you are interested in firewire support, or possibly in HDMI/HDCP). All functions appear to be well supported (disk, video, sound, integrated PCIe Gigabit Ethernet). Combined with an "Arctic Cooling Freezer 64 Pro PWM" it gives a cheap, compact, and quiet (and power-efficient!) small server with quite good performance (though with only a limited number of PCIe and PCI slots, since it has a uATX form factor). BTW: The AMD/ATI 690G chip set also allows to build a compact home server (and with the recently announced support for an open source graphics driver, the on-chip video may become well supported; but I guess it will work as well with the Vesa driver as the 7050 did when I tried it ...) The 690G should have another 5W less idle power consumption ... (But beware: 690G main-board often have only 100baseTX Ethernet or a Realtek Gigabit Ethernet chip on PCI, which may limit network throughput ...) Regards, STefan So, no reason From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 10:02:36 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 39C8F16A417 for ; Mon, 8 Oct 2007 10:02:36 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from spacemail1-out.mgmt.space.net (spacemail1-out.mgmt.Space.Net [194.97.149.146]) by mx1.freebsd.org (Postfix) with ESMTP id B406913C45A for ; Mon, 8 Oct 2007 10:02:35 +0000 (UTC) (envelope-from se@FreeBSD.org) X-SpaceNet-SBRS: None X-IronPort-AV: E=Sophos;i="4.21,242,1188770400"; d="scan'208";a="66977589" Received: from mail.atsec.com ([195.30.252.105]) by spacemail1-out.mgmt.space.net with ESMTP; 08 Oct 2007 12:02:34 +0200 Received: from [10.2.2.88] (frueh.atsec.com [217.110.13.170]) (Authenticated sender: se@atsec.com) by mail.atsec.com (Postfix) with ESMTP id AF5DE72091C; Mon, 8 Oct 2007 12:02:33 +0200 (CEST) Message-ID: <470A0038.5070802@FreeBSD.org> Date: Mon, 08 Oct 2007 12:02:32 +0200 From: Stefan Esser User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Alexander Leidinger References: <20071007105235.GA2505@StefanEsser.FreeBSD.org> <20071007171541.4bd00627@deskjail> <470939B5.2090309@FreeBSD.org> <20071008091806.4gum80p05ckwc480@webmail.leidinger.net> In-Reply-To: <20071008091806.4gum80p05ckwc480@webmail.leidinger.net> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: current@FreeBSD.org Subject: Re: [Patch] man page nsswitch(5) still references cached 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: Mon, 08 Oct 2007 10:02:36 -0000 Alexander Leidinger wrote: > Quoting Stefan Esser (from Sun, 07 Oct 2007 21:55:33 > +0200): >>> Why do you think it is a length limit which is the cause of the >>> problems you see? >> >> Well, see the last two lines, 63 chars long, 10 for "OLD_FILES+=" and >> 53 chars for the file name. It may be that files were added to the list >> by a cut&paste action and that some characters had wrapped around to >> the next line and were forgotten. But it is not relevant, just strange. > > So you don't think it is a length limitation in make which causes the > problem, but a length limitation somewhere before adding it to > ObsoleteFiles.inc? No, it probably is no limit in any part of the infrastructure. Both these short lines were added with revision 1.7, 2 years ago, but there were longer lines in that commit, which are complete. So, there is no issue that needs fixing, except for the two affected lines ... Regards, STefan From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 10:43: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 AAB3516A418 for ; Mon, 8 Oct 2007 10:43:24 +0000 (UTC) (envelope-from tijl@ulyssis.org) Received: from rusty.kulnet.kuleuven.ac.be (rusty.kulnet.kuleuven.ac.be [134.58.240.42]) by mx1.freebsd.org (Postfix) with ESMTP id 5FECF13C48D for ; Mon, 8 Oct 2007 10:43:24 +0000 (UTC) (envelope-from tijl@ulyssis.org) Received: from localhost (localhost [127.0.0.1]) by rusty.kulnet.kuleuven.ac.be (Postfix) with ESMTP id A4FDA1D9669; Mon, 8 Oct 2007 12:43:22 +0200 (CEST) Received: from smtps01.kuleuven.be (smtpshost01.kulnet.kuleuven.be [134.58.240.74]) by rusty.kulnet.kuleuven.ac.be (Postfix) with ESMTP id 045221D80AE; Mon, 8 Oct 2007 12:35:55 +0200 (CEST) Received: from kalimero.kotnet.org (kalimero.kotnet.org [10.4.16.222]) by smtps01.kuleuven.be (Postfix) with ESMTP id C2CEF31E704; Mon, 8 Oct 2007 12:35:54 +0200 (CEST) Received: from kalimero.kotnet.org (kalimero.kotnet.org [127.0.0.1]) by kalimero.kotnet.org (8.14.1/8.14.1) with ESMTP id l98AZsqv001645; Mon, 8 Oct 2007 12:35:54 +0200 (CEST) (envelope-from tijl@ulyssis.org) X-Kuleuven: This mail passed the K.U.Leuven mailcluster From: Tijl Coosemans To: freebsd-current@freebsd.org Date: Mon, 8 Oct 2007 12:35:52 +0200 User-Agent: KMail/1.9.7 References: <46FC8079.6030304@computer.org> <200710080209.33529.tijl@ulyssis.org> <4709C31A.1010900@computer.org> In-Reply-To: <4709C31A.1010900@computer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710081235.53734.tijl@ulyssis.org> X-Virus-Scanned: by KULeuven Antivirus Cluster Cc: Kip Macy , Steve Kargl , Eric Schuele 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: Mon, 08 Oct 2007 10:43:24 -0000 On Monday 08 October 2007 07:41:46 Eric Schuele wrote: > On 10/07/2007 19:09, Tijl Coosemans wrote: >> I'm not sure it will help, but you might want to give the patch in >> http://www.freebsd.org/cgi/query-pr.cgi?pr=115469 a try. > I have given the patch a try and it appears to be working! Very > nice. I take a better look tomorrow... but it certainly looks fixed. I read your original message in the archives and there you mention it happens after continuing the process. I suspect the continuing doesn't happen properly, because that's exactly what the patch in the PR fixes. I hope a committer can have a look at it now, because a working debugger is quite important. From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 11:28: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 810C116A417 for ; Mon, 8 Oct 2007 11:28:16 +0000 (UTC) (envelope-from toomany@toomany.net) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5A21B13C455 for ; Mon, 8 Oct 2007 11:28:16 +0000 (UTC) (envelope-from toomany@toomany.net) Received: by wa-out-1112.google.com with SMTP id k17so1665326waf for ; Mon, 08 Oct 2007 04:28:15 -0700 (PDT) Received: by 10.114.121.1 with SMTP id t1mr1090193wac.1191842895348; Mon, 08 Oct 2007 04:28:15 -0700 (PDT) Received: by 10.114.36.11 with HTTP; Mon, 8 Oct 2007 04:28:15 -0700 (PDT) Message-ID: Date: Mon, 8 Oct 2007 13:28:15 +0200 From: "TooMany Secrets" To: "Stefan Esser" In-Reply-To: <4709FEB0.80004@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline References: <20071002164246.GA986@hades.panopticon> <20071003003329.GA78359@hades.panopticon> <4709FEB0.80004@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: Need motherboard for home fileserver 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, 08 Oct 2007 11:28:16 -0000 MjAwNy8xMC84LCBTdGVmYW4gRXNzZXIgPHNlQGZyZWVic2Qub3JnPjoKPiBXZWxsLCB5b3UgbWF5 IHdhbnQgdG8gdGFrZSBhIGxvb2sgYXQgdGhlIEFiaXQgQU4tTTIgKG9yIC1NMkhELCBpZiB5b3UK PiBhcmUgaW50ZXJlc3RlZCBpbiBmaXJld2lyZSBzdXBwb3J0LCBvciBwb3NzaWJseSBpbiBIRE1J L0hEQ1ApLiBBbGwKPiBmdW5jdGlvbnMgYXBwZWFyIHRvIGJlIHdlbGwgc3VwcG9ydGVkIChkaXNr LCB2aWRlbywgc291bmQsIGludGVncmF0ZWQKPiBQQ0llIEdpZ2FiaXQgRXRoZXJuZXQpLiBDb21i aW5lZCB3aXRoIGFuICJBcmN0aWMgQ29vbGluZyBGcmVlemVyIDY0IFBybwo+IFBXTSIgaXQgZ2l2 ZXMgYSBjaGVhcCwgY29tcGFjdCwgYW5kIHF1aWV0IChhbmQgcG93ZXItZWZmaWNpZW50ISkgc21h bGwKPiBzZXJ2ZXIgd2l0aCBxdWl0ZSBnb29kIHBlcmZvcm1hbmNlICh0aG91Z2ggd2l0aCBvbmx5 IGEgbGltaXRlZCBudW1iZXIKPiBvZiBQQ0llIGFuZCBQQ0kgc2xvdHMsIHNpbmNlIGl0IGhhcyBh IHVBVFggZm9ybSBmYWN0b3IpLgoKSSdtIHZlcnkgaW50ZXJlc3RlZCBpbiB0aGlzIG1iLCBidXQg aXMgY29ycmVjdGx5IHN1cHBvcnRlZCBpbiA2LjItU1RBQkxFIGFsc28/CgpUaGFuayB5b3UgdmVy eSBtdWNoIGZvciB5b3VyIGdyZWF0IGluZm9ybWF0aW9uLgoKLS0gCkhhdmUgYSBuaWNlIGRheSAg Oy0pClRvb01hbnlTZWNyZXRzCgo9PT09PT09PT09PT09PT09PT09PT09PT09PT09CkRpam8gQ29u ZnVjaW86CiJFeMOtZ2V0ZSBtdWNobyBhIHRpIG1pc21vIHkgZXNwZXJhIHBvY28gZGUgbG9zIGRl bcOhcy4gQXPDrSB0ZSBhaG9ycmFyw6FzCmRpc2d1c3Rvcy4iCj09PT09PT09PT09PT09PT09PT09 PT09PT09PT0K From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 12:07: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 8D81C16A417; Mon, 8 Oct 2007 12:07:06 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp4.yandex.ru (smtp4.yandex.ru [213.180.223.136]) by mx1.freebsd.org (Postfix) with ESMTP id D90A013C459; Mon, 8 Oct 2007 12:07:04 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from ns.kirov.so-cdu.ru ([77.72.136.145]:13521 "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 S741090AbXJHMGp (ORCPT + 1 other); Mon, 8 Oct 2007 16:06:45 +0400 X-Comment: RFC 2476 MSA function at smtp4.yandex.ru logged sender identity as: bu7cher Message-ID: <470A1D53.40209@yandex.ru> Date: Mon, 08 Oct 2007 16:06:43 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: TooMany Secrets References: <20071002164246.GA986@hades.panopticon> <20071003003329.GA78359@hades.panopticon> <4709FEB0.80004@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Need motherboard for home fileserver 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, 08 Oct 2007 12:07:06 -0000 TooMany Secrets wrote: > 2007/10/8, Stefan Esser : >> Well, you may want to take a look at the Abit AN-M2 (or -M2HD, if you >> are interested in firewire support, or possibly in HDMI/HDCP). All >> functions appear to be well supported (disk, video, sound, integrated >> PCIe Gigabit Ethernet). Combined with an "Arctic Cooling Freezer 64 Pro >> PWM" it gives a cheap, compact, and quiet (and power-efficient!) small >> server with quite good performance (though with only a limited number >> of PCIe and PCI slots, since it has a uATX form factor). > > I'm very interested in this mb, but is correctly supported in 6.2-STABLE also? There is one issue. ATI IXP600/IXP700 not yet supported with ata(4) driver. And you will have only UDMA33 is the best case. But you can found a patch in gnats (PR ). http://www.freebsd.org/cgi/query-pr.cgi?pr=116125 -- WBR, Andrey V. Elsukov From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 12:15: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 15ACB16A41B; Mon, 8 Oct 2007 12:15:40 +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 A67C213C448; Mon, 8 Oct 2007 12:15:39 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 42C3C45E90; Mon, 8 Oct 2007 14:15:38 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id CE2BA45684; Mon, 8 Oct 2007 14:15:31 +0200 (CEST) Date: Mon, 8 Oct 2007 14:15:23 +0200 From: Pawel Jakub Dawidek To: freebsd-fs@FreeBSD.org Message-ID: <20071008121523.GM2327@garage.freebsd.pl> References: <20071005000046.GC92272@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Tnj+unmjHTqEM5y0" Content-Disposition: inline In-Reply-To: <20071005000046.GC92272@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=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-current@FreeBSD.org Subject: Re: ZFS kmem_map too small. 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, 08 Oct 2007 12:15:40 -0000 --Tnj+unmjHTqEM5y0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Here are some updates: I was able to reproduce the panic by rsyncing big files and trying bonnie++ test suggested in this thread. Can you guys retry with this patch: http://people.freebsd.org/~pjd/patches/vm_kern.c.2.patch It's a hack, yes, but allows to mitigate the problem quite well. I'm looking for a solution that can be used for 7.0 before we find a better fix. BTW. To use ZFS you _must_ increase vm.kmem_size/vm.kmem_size_max. If you have the problem discussed here and you're using standard values, please retry with vm.kmem_size/vm.kmem_size_max set to at least 600MB in /boot/loader.conf. I'm not sure if it's not too late to ask re@ about increasing the default kmem size at least on amd64. ~300MB we have there is silly small. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --Tnj+unmjHTqEM5y0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHCh9bForvXbEpPzQRAlLFAKD2Xo69Xid2JKshQ3ATi1m6MM/CrgCdFmN8 t4Ayssew0tklY0lh+iOSEFA= =sRS8 -----END PGP SIGNATURE----- --Tnj+unmjHTqEM5y0-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 12:42: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 36ABB16A420; Mon, 8 Oct 2007 12:42:37 +0000 (UTC) (envelope-from master-list@arcor.de) Received: from mail.i88.de (i88.de [88.198.25.141]) by mx1.freebsd.org (Postfix) with ESMTP id DF45F13C494; Mon, 8 Oct 2007 12:42:36 +0000 (UTC) (envelope-from master-list@arcor.de) Received: from localhost (localhost [127.0.0.1]) by mail.i88.de (Postfix) with ESMTP id D5CB48450C; Mon, 8 Oct 2007 14:26:42 +0200 (CEST) Received: from mail.i88.de ([127.0.0.1]) by localhost (serv.i88.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q12ieydvO5fI; Mon, 8 Oct 2007 14:26:34 +0200 (CEST) Received: from [192.168.10.13] (p549D6E58.dip.t-dialin.net [84.157.110.88]) by mail.i88.de (Postfix) with ESMTP id CC0DA84507; Mon, 8 Oct 2007 14:26:33 +0200 (CEST) Message-ID: <470A21F8.8030506@arcor.de> Date: Mon, 08 Oct 2007 14:26:32 +0200 From: Micha Mutschler User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: freebsd-fs@freebsd.org, freebsd-current@freebsd.org References: <20071005000046.GC92272@garage.freebsd.pl> In-Reply-To: <20071005000046.GC92272@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: ZFS kmem_map too small. 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, 08 Oct 2007 12:42:37 -0000 Pawel Jakub Dawidek wrote: > If you can still see those panic, please let me know as soon as possible > and try to describe what your workload looks like, how to reproduce it, > etc. I'd really like ZFS to be rock-stable for 7.0 even on i386. > Hi! I was doing a ports rsync from a zfs to /usr/ports (ufs). That worked fine. The crash happend as I started to copy (parallel to the rsync) a huge file from a nfs server to the zfs. For 512 MB RAM I've set: kern.maxvnodes="25000" vfs.zfs.prefetch_disable="1" vfs.zfs.arc_max="52428800" vm.kmem_size_max="402653184" vfs.zfs.zil_disable="1" [root@filer ~]# zpool status pool: xport state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM xport ONLINE 0 0 0 raidz1 ONLINE 0 0 0 ad8 ONLINE 0 0 0 ad9 ONLINE 0 0 0 ad10 ONLINE 0 0 0 ad11 ONLINE 0 0 0 errors: No known data errors [root@filer ~]# [root@filer ~]# zfs list NAME USED AVAIL REFER MOUNTPOINT xport 33.8G 514G 33.6G /xport xport/ports 212M 514G 212M /xport/ports xport/t 26.9K 514G 26.9K /xport/t [root@filer ~]# (I'm using 200709) regarts, Micha Mutschler From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 12:47: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 26A8316A417 for ; Mon, 8 Oct 2007 12:47:56 +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 CC8F013C455 for ; Mon, 8 Oct 2007 12:47:55 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Ies1A-0006DX-Md for freebsd-current@freebsd.org; Mon, 08 Oct 2007 12:47:28 +0000 Received: from 78-0-80-105.adsl.net.t-com.hr ([78.0.80.105]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 08 Oct 2007 12:47:28 +0000 Received: from ivoras by 78-0-80-105.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 08 Oct 2007 12:47:28 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Mon, 08 Oct 2007 14:47:01 +0200 Lines: 31 Message-ID: References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF8B06EB3D7455C221DFAECA9" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 78-0-80-105.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) In-Reply-To: <20071008121523.GM2327@garage.freebsd.pl> X-Enigmail-Version: 0.95.3 Sender: news Cc: freebsd-fs@freebsd.org Subject: Re: ZFS kmem_map too small. 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, 08 Oct 2007 12:47:56 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF8B06EB3D7455C221DFAECA9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Pawel Jakub Dawidek wrote: > I'm not sure if it's not too late to ask re@ about increasing the > default kmem size at least on amd64. ~300MB we have there is silly > small. Is kmem / arc allocation static or dynamic? I.e. the "regular" file cache can use up all (or at least big chunk of) memory and then return it to applications when they need it. I suppose this is not the case with ZFS? --------------enigF8B06EB3D7455C221DFAECA9 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 iD8DBQFHCibGldnAQVacBcgRAhTfAJ9rRTPSls0H7ccJnEIelEtU0w+HGgCg4xly ODIKTGU9NMrj8CFtkqfQbZs= =oQn1 -----END PGP SIGNATURE----- --------------enigF8B06EB3D7455C221DFAECA9-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 13:05: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 2E19E16A417 for ; Mon, 8 Oct 2007 13:05:21 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from spacemail1-out.mgmt.space.net (spacemail1-out.mgmt.Space.Net [194.97.149.146]) by mx1.freebsd.org (Postfix) with ESMTP id 674ED13C4A5 for ; Mon, 8 Oct 2007 13:05:19 +0000 (UTC) (envelope-from se@FreeBSD.org) X-SpaceNet-SBRS: None X-IronPort-AV: E=Sophos;i="4.21,242,1188770400"; d="scan'208";a="67063342" Received: from mail.atsec.com ([195.30.252.105]) by spacemail1-out.mgmt.space.net with ESMTP; 08 Oct 2007 15:05:11 +0200 Received: from [10.2.2.88] (frueh.atsec.com [217.110.13.170]) (Authenticated sender: se@atsec.com) by mail.atsec.com (Postfix) with ESMTP id 51D0072091C; Mon, 8 Oct 2007 15:05:17 +0200 (CEST) Message-ID: <470A2B0C.2020502@FreeBSD.org> Date: Mon, 08 Oct 2007 15:05:16 +0200 From: Stefan Esser User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: "Andrey V. Elsukov" References: <20071002164246.GA986@hades.panopticon> <20071003003329.GA78359@hades.panopticon> <4709FEB0.80004@FreeBSD.org> <470A1D53.40209@yandex.ru> In-Reply-To: <470A1D53.40209@yandex.ru> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, TooMany Secrets Subject: Re: Need motherboard for home fileserver 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, 08 Oct 2007 13:05:21 -0000 Andrey V. Elsukov schrieb: > TooMany Secrets wrote: >> 2007/10/8, Stefan Esser : >>> Well, you may want to take a look at the Abit AN-M2 (or -M2HD, if you >>> are interested in firewire support, or possibly in HDMI/HDCP). All >>> functions appear to be well supported (disk, video, sound, integrated >>> PCIe Gigabit Ethernet). Combined with an "Arctic Cooling Freezer 64 Pro >>> PWM" it gives a cheap, compact, and quiet (and power-efficient!) small >>> server with quite good performance (though with only a limited number >>> of PCIe and PCI slots, since it has a uATX form factor). >> >> I'm very interested in this mb, but is correctly supported in >> 6.2-STABLE also? > > There is one issue. ATI IXP600/IXP700 not yet supported with ata(4) > driver. And you will have only UDMA33 is the best case. But you can > found a patch in gnats (PR ). > http://www.freebsd.org/cgi/query-pr.cgi?pr=116125 No, the Abit AN-M2(HD) are based on nForce chip-sets (630a with integrated 7025/7050 graphics), no patch is required for ata(4) (since the SATA/IDE parts are mostly identical to the nF6150/430, with the addition of AHCI support, which can be optionally enabled in the BIOS). Regards, STefan From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 13:30: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 D62E416A417; Mon, 8 Oct 2007 13:30:51 +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 8AA6113C45B; Mon, 8 Oct 2007 13:30:51 +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 4A0DB20C9; Mon, 8 Oct 2007 15:30:42 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id B9A0120C8; Mon, 8 Oct 2007 15:30:41 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id 8395284481; Mon, 8 Oct 2007 15:30:41 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Pawel Jakub Dawidek References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> Date: Mon, 08 Oct 2007 15:30:41 +0200 Message-ID: <86bqb97mym.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-fs@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: ZFS kmem_map too small. 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, 08 Oct 2007 13:30:51 -0000 Pawel Jakub Dawidek writes: > I'm not sure if it's not too late to ask re@ about increasing the > default kmem size at least on amd64. ~300MB we have there is silly > small. Speaking of which, I tried setting vm.kmem_size to 2G on a C2D system with 4 GB RAM, but it simply panics: OK set vm.kmem_size=3D2G OK boot -s GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb 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 #8: Tue Sep 25 13:31:41 CEST 2007 des@ds4.des.no:/usr/obj/usr/src/sys/ds4 kmem_suballoc: bad status return of 3. panic: kmem_suballoc cpuid =3D 0 KDB: enter: panic [thread pid 0 tid 0 ] Stopped at kdb_enter+0x31: popq %rbp db> where Tracing pid 0 tid 0 td 0xffffffff805af4a0 kdb_enter() at kdb_enter+0x31 panic() at panic+0x166 kmem_suballoc() at kmem_suballoc+0xc3 kmeminit() at kmeminit+0x16e mi_startup() at mi_startup+0x59 btext() at btext+0x2c db> reset with vm.kmem_size unset and vm.kmem_size_max=3D2G, it boots fine: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz (2400.01-MHz K8-class = CPU) Origin =3D "GenuineIntel" Id =3D 0x6f6 Stepping =3D 6 Features=3D0xbfebfbff Features2=3D0xe3bd AMD Features=3D0x20100800 AMD Features2=3D0x1 Cores per package: 2 usable memory =3D 4286398464 (4087 MB) avail memory =3D 4130979840 (3939 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard [...] DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 13:39: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 1EF9216A417; Mon, 8 Oct 2007 13:39:03 +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 D810B13C47E; Mon, 8 Oct 2007 13:39:01 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 39C0145EA7; Mon, 8 Oct 2007 15:39:00 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id DC6B145683; Mon, 8 Oct 2007 15:38:54 +0200 (CEST) Date: Mon, 8 Oct 2007 15:38:46 +0200 From: Pawel Jakub Dawidek To: Dag-Erling Sm??rgrav Message-ID: <20071008133846.GP2327@garage.freebsd.pl> References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> <86bqb97mym.fsf@ds4.des.no> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yEbVe0JFHWhrOjGA" Content-Disposition: inline In-Reply-To: <86bqb97mym.fsf@ds4.des.no> 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=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: ZFS kmem_map too small. 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, 08 Oct 2007 13:39:03 -0000 --yEbVe0JFHWhrOjGA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 08, 2007 at 03:30:41PM +0200, Dag-Erling Sm??rgrav wrote: > Pawel Jakub Dawidek writes: > > I'm not sure if it's not too late to ask re@ about increasing the > > default kmem size at least on amd64. ~300MB we have there is silly > > small. >=20 > Speaking of which, I tried setting vm.kmem_size to 2G on a C2D system > with 4 GB RAM, but it simply panics: >=20 > OK set vm.kmem_size=3D2G > OK boot -s > GDB: no debug ports present > KDB: debugger backends: ddb > KDB: current backend: ddb > 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 #8: Tue Sep 25 13:31:41 CEST 2007 > des@ds4.des.no:/usr/obj/usr/src/sys/ds4 > kmem_suballoc: bad status return of 3. > panic: kmem_suballoc > cpuid =3D 0 > KDB: enter: panic > [thread pid 0 tid 0 ] > Stopped at kdb_enter+0x31: popq %rbp > db> where > Tracing pid 0 tid 0 td 0xffffffff805af4a0 > kdb_enter() at kdb_enter+0x31 > panic() at panic+0x166 > kmem_suballoc() at kmem_suballoc+0xc3 > kmeminit() at kmeminit+0x16e > mi_startup() at mi_startup+0x59 > btext() at btext+0x2c > db> reset >=20 > with vm.kmem_size unset and vm.kmem_size_max=3D2G, it boots fine: >=20 > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz (2400.01-MHz K8-clas= s CPU) > Origin =3D "GenuineIntel" Id =3D 0x6f6 Stepping =3D 6 > Features=3D0xbfebfbff > Features2=3D0xe3bd > AMD Features=3D0x20100800 > AMD Features2=3D0x1 > Cores per package: 2 > usable memory =3D 4286398464 (4087 MB) > avail memory =3D 4130979840 (3939 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > ioapic0: Changing APIC ID to 2 > ioapic0 irqs 0-23 on motherboard > [...] For i386 one has to set, eg. 'options KVA_PAGES=3D512' to the kernel config to be able to define kmem larger than ~700MB. I guess you're running amd64, maybe there is similar requirement? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --yEbVe0JFHWhrOjGA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHCjLmForvXbEpPzQRAkoHAKDf/geY/dDi93PiMUUQVReTNb+AhwCgonvy erlqcJb/7HloqTc2UVOSnYs= =lU5S -----END PGP SIGNATURE----- --yEbVe0JFHWhrOjGA-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 13:44: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 83D0516A418; Mon, 8 Oct 2007 13:44:18 +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 E7DE213C467; Mon, 8 Oct 2007 13:44:17 +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 l98DiEUh016370; Mon, 8 Oct 2007 15:44:15 +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 l98Di8fZ077782 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Oct 2007 15:44:08 +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 l98Di882006881; Mon, 8 Oct 2007 15:44:08 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id l98Di8rY006880; Mon, 8 Oct 2007 15:44:08 +0200 (CEST) (envelope-from ticso) Date: Mon, 8 Oct 2007 15:44:07 +0200 From: Bernd Walter To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= Message-ID: <20071008134407.GB67153@cicely12.cicely.de> References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> <86bqb97mym.fsf@ds4.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <86bqb97mym.fsf@ds4.des.no> X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1.8, 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-fs@freebsd.org, freebsd-current@freebsd.org, Pawel Jakub Dawidek Subject: Re: ZFS kmem_map too small. 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: Mon, 08 Oct 2007 13:44:18 -0000 On Mon, Oct 08, 2007 at 03:30:41PM +0200, Dag-Erling Smørgrav wrote: > Pawel Jakub Dawidek writes: > > I'm not sure if it's not too late to ask re@ about increasing the > > default kmem size at least on amd64. ~300MB we have there is silly > > small. > > Speaking of which, I tried setting vm.kmem_size to 2G on a C2D system > with 4 GB RAM, but it simply panics: > > OK set vm.kmem_size=2G This sounds like there's a signed 32 bit limit somewhere. Wild guess: Maybe it is a loader parsing limitation and not one of the kernel. > OK boot -s > GDB: no debug ports present > KDB: debugger backends: ddb > KDB: current backend: ddb > 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 #8: Tue Sep 25 13:31:41 CEST 2007 > des@ds4.des.no:/usr/obj/usr/src/sys/ds4 > kmem_suballoc: bad status return of 3. > panic: kmem_suballoc > cpuid = 0 > KDB: enter: panic > [thread pid 0 tid 0 ] > Stopped at kdb_enter+0x31: popq %rbp > db> where > Tracing pid 0 tid 0 td 0xffffffff805af4a0 > kdb_enter() at kdb_enter+0x31 > panic() at panic+0x166 > kmem_suballoc() at kmem_suballoc+0xc3 > kmeminit() at kmeminit+0x16e > mi_startup() at mi_startup+0x59 > btext() at btext+0x2c > db> reset > > with vm.kmem_size unset and vm.kmem_size_max=2G, it boots fine: What is the vakue for vm.kmem_size_max after booting? Maybe a errously parsed value on max isn't that critical. -- 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 Mon Oct 8 14:08: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 6864616A420 for ; Mon, 8 Oct 2007 14:08:52 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id 11D6913C474 for ; Mon, 8 Oct 2007 14:08:51 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1IetHt-0001VN-JR; Mon, 08 Oct 2007 16:08:49 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: =?iso-8859-1?Q?Angel_H=F6ngens?= In-reply-to: <000b01c7fc23$d6ee60f0$84cb22d0$@nl> References: <000b01c7fc23$d6ee60f0$84cb22d0$@nl> Comments: In-reply-to =?iso-8859-1?Q?Angel_H=F6ngens?= message dated "Fri, 21 Sep 2007 09:48:45 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 08 Oct 2007 16:08:49 +0200 From: Danny Braniss Message-ID: Cc: freebsd-current@freebsd.org Subject: Re: iscsi port in /etc/services? 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, 08 Oct 2007 14:08:52 -0000 > Hey guys, my first post here, so don't shoot me. (Don't know if this is= =3Dthe > right place to come with the question) >=20 > I'm running RELENG_6 (built yesterday)m and after installing the > iscsi-target from ports, I found that I could not get it started.. I = =3Dgot > the error =22***ERROR*** getaddrinfo: servname not supported for =3Dai_= socktype=22, > which after googling for half an hour turns out to be a cryptic message= > meaning a service is not found in /etc/services. >=20 > After getting a later version of /etc/services, the iscsi-target would > start, but I was not able to connect using an initiator on another =3Dm= achine. > I then found out these ports in /etc/services: (apparently since rev = =3D1.112) >=20 > iscsi 860/tcp> iscsi 860/udp >=20 > While my initiator expected to see port 3260. After some more googling,= =3DI > found out port 860 is a port to be used ONLY when in need of a system = =3DTCP > port number (?) but by default, port 3260 must be used: >=20 > RFC3720 says: >=20 > The well-known user TCP port number for iSCSI connections assigned b= y > IANA is 3260 and this is the default iSCSI port. Implementations > needing a system TCP port number may use port 860, the port assigned= > by IANA as the iSCSI system port; however in order to use port 860, > it MUST be explicitly specified - implementations MUST NOT default t= o > use of port 860, as 3260 is the only allowed default. >=20 > Is this in error in /etc/services, or an error in my logic? >=20 >=20 > Kind regards, >=20 > Angelo H=F6ngens > The Netherlands. As far as I can tell, iscsi-target does NOT use /etc/services, it specifi= cally requests port 3260, unless it's changed by the the -p flag. So your problem is somewhere in the configuration file. danny PS: the nice thing about FreeBSD is that you have the sources, of course = that needs some basic computer language knowledge :-) From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 14:27:36 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 724C516A418 for ; Mon, 8 Oct 2007 14:27:36 +0000 (UTC) (envelope-from marc@blackend.org) Received: from abigail.blackend.org (ns0.blackend.org [82.227.222.164]) by mx1.freebsd.org (Postfix) with ESMTP id BA5C513C461 for ; Mon, 8 Oct 2007 14:27:34 +0000 (UTC) (envelope-from marc@blackend.org) Received: from gothic.blackend.org (gothic.blackend.org [192.168.1.203]) by abigail.blackend.org (8.13.4/8.13.3) with ESMTP id l98ERM9A032404; Mon, 8 Oct 2007 16:27:22 +0200 (CEST) (envelope-from marc@abigail.blackend.org) Received: from gothic.blackend.org (localhost [127.0.0.1]) by gothic.blackend.org (8.14.1/8.14.1) with ESMTP id l98ERMRU098263; Mon, 8 Oct 2007 16:27:22 +0200 (CEST) (envelope-from marc@gothic.blackend.org) Received: (from marc@localhost) by gothic.blackend.org (8.14.1/8.14.1/Submit) id l98ERLZp098262; Mon, 8 Oct 2007 16:27:21 +0200 (CEST) (envelope-from marc) Date: Mon, 8 Oct 2007 16:27:21 +0200 From: Marc Fonvieille To: Jeff Roberson Message-ID: <20071008142721.GB22255@gothic.blackend.org> References: <4707866F.7030605@FreeBSD.org> <20071006143141.GD976@gothic.blackend.org> <4707CF8D.3070303@u.washington.edu> <20071006191014.GB84780@abigail.blackend.org> <20071007012049.S912@10.0.0.1> <20071007013342.D912@10.0.0.1> <20071007095408.GA997@gothic.blackend.org> <20071007045911.Y912@10.0.0.1> <20071007130929.GA1132@gothic.blackend.org> <20071007114345.E912@10.0.0.1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071007114345.E912@10.0.0.1> X-Useless-Header: blackend.org X-Operating-System: FreeBSD 7.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: current@freebsd.org Subject: Re: ULE/yielding patch for testing. 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, 08 Oct 2007 14:27:36 -0000 On Sun, Oct 07, 2007 at 11:44:13AM -0700, Jeff Roberson wrote: > On Sun, 7 Oct 2007, Marc Fonvieille wrote: > >> On Sun, Oct 07, 2007 at 05:00:05AM -0700, Jeff Roberson wrote: >>>> >>>> You mean Xorg 7.2 or 7.3 with -CURRENT? >>>> Currently I observe the problem with Xorg 7.2 or 7.3 under -CURRENT, >>>> when Xorg 7.2 with 6.2-STABLE is Ok (I did not try with Xorg 7.3 on >>>> -STABLE, but I'm quite sure I'll end to same result). >>>> On a completly different machine (a more recent one with a 2.8GHz >>>> Celeron), the problem could be less obvious cause of the machine speed >>>> but I can notice the difference between 6.2-STABLE and 7-CURRENT with >>>> any Xorg version. >>> >>> Can you give a dozen lines of 'vmstat 1' output while rendering this >>> page in >>> 7.0 and 6.2? >>> >> >> I attached the logs while rendering a french newspaper page. > > Is this a SMP kernel on a UP machine? If so can you try without SMP in > your config? > Without SMP and apic, the number of context switches is lower: procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad4 cd0 in sy cs us sy id 0 0 0 501656 89424 0 0 0 0 0 0 0 0 1266 3532 1511 8 7 86 0 0 0 501656 89424 0 0 0 0 0 0 0 0 1252 8127 964 11 6 83 1 0 0 501656 89424 0 0 0 0 0 0 0 0 1253 1514 973 2 7 92 3 0 0 501656 89424 2647 0 0 0 2662 0 6 0 1397 12460 2663 42 24 34 2 0 0 501656 89424 379 0 0 0 375 0 0 0 1307 16338 2528 81 17 2 4 0 0 501500 89424 5 0 0 0 0 0 0 0 1561 6544 1818 85 15 0 4 0 0 501300 89424 1693 0 0 0 1693 0 1 0 1507 9523 1780 86 14 0 3 0 0 501792 89424 876 0 0 0 873 0 3 0 1321 14872 1693 81 19 0 1 0 0 501580 89424 2674 0 0 0 2574 0 0 0 1305 10642 1690 88 12 0 2 0 0 501580 89424 876 0 0 0 866 0 0 0 1266 12783 2005 58 10 33 2 0 0 501580 89424 0 0 0 0 0 0 3 0 1291 1464 996 2 6 92 but still a slightly higher than on 6.X, but I'm still experiencing slowdown of webpage rendering during compilation. -- Marc From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 14:30: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 EB1C116A41A for ; Mon, 8 Oct 2007 14:30:59 +0000 (UTC) (envelope-from freebsd@hansmi.ch) Received: from hansmi.home.forkbomb.ch (hansmi.home.forkbomb.ch [213.144.146.165]) by mx1.freebsd.org (Postfix) with ESMTP id EF66F13C467 for ; Mon, 8 Oct 2007 14:30:58 +0000 (UTC) (envelope-from freebsd@hansmi.ch) Received: (qmail 21341 invoked by uid 1000); 8 Oct 2007 14:04:16 -0000 Date: Mon, 8 Oct 2007 16:04:16 +0200 From: Michael Hanselmann To: "Timur I. Bakeyev" Message-ID: <20071008140416.GA21134@hansmi.ch> References: <20070716190258.GA25030@hansmi.ch> <20071008140113.GG98428@com.bat.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071008140113.GG98428@com.bat.ru> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: tobias.mueller@hostpoint.ch, m.kooijman@student.utwente.nl, freebsd-current@freebsd.org, bushman@freebsd.org, elias.wittwer@hostpoint.ch Subject: Re: [PATCH] Implement getgroupmembership(3) for massive performance gain when using LDAP or Winbind 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, 08 Oct 2007 14:31:00 -0000 Hi Timur On Mon, Oct 08, 2007 at 04:01:14PM +0200, Timur I. Bakeyev wrote: > On Mon, Jul 16, 2007 at 09:02:58PM +0200, Michael Hanselmann wrote: > > I was working with a company which plans to migrate its FreeBSD servers > > from using /etc/{passwd,group} to LDAP. They will have about 45'000 > > users and as much groups in the directory. > Did you get any reaction on your patch and estimation when it maybe included > into the CURRENT? I'm in contact with Michael Bushkov, who reviewed the patch some time ago. After taking some time to implement them, I sent him the newest version just on Friday night. He told me to review it again this week. I'll bounce you the mail I sent to him. Thanks, Michael -- http://hansmi.ch/ From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 14:31: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 66F0116A41B for ; Mon, 8 Oct 2007 14:31:18 +0000 (UTC) (envelope-from marc@blackend.org) Received: from abigail.blackend.org (ns0.blackend.org [82.227.222.164]) by mx1.freebsd.org (Postfix) with ESMTP id B0FD113C46E for ; Mon, 8 Oct 2007 14:31:17 +0000 (UTC) (envelope-from marc@blackend.org) Received: from gothic.blackend.org (gothic.blackend.org [192.168.1.203]) by abigail.blackend.org (8.13.4/8.13.3) with ESMTP id l98EV7Di032493; Mon, 8 Oct 2007 16:31:07 +0200 (CEST) (envelope-from marc@abigail.blackend.org) Received: from gothic.blackend.org (localhost [127.0.0.1]) by gothic.blackend.org (8.14.1/8.14.1) with ESMTP id l98EV7hn098276; Mon, 8 Oct 2007 16:31:07 +0200 (CEST) (envelope-from marc@gothic.blackend.org) Received: (from marc@localhost) by gothic.blackend.org (8.14.1/8.14.1/Submit) id l98EV7iR098275; Mon, 8 Oct 2007 16:31:07 +0200 (CEST) (envelope-from marc) Date: Mon, 8 Oct 2007 16:31:07 +0200 From: Marc Fonvieille To: Jeff Roberson Message-ID: <20071008143107.GC22255@gothic.blackend.org> References: <20071006143141.GD976@gothic.blackend.org> <4707CF8D.3070303@u.washington.edu> <20071006191014.GB84780@abigail.blackend.org> <20071007012049.S912@10.0.0.1> <20071007013342.D912@10.0.0.1> <20071007095408.GA997@gothic.blackend.org> <20071007045911.Y912@10.0.0.1> <20071007130929.GA1132@gothic.blackend.org> <20071007114345.E912@10.0.0.1> <20071008142721.GB22255@gothic.blackend.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071008142721.GB22255@gothic.blackend.org> X-Useless-Header: blackend.org X-Operating-System: FreeBSD 7.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: current@freebsd.org Subject: Re: ULE/yielding patch for testing. 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, 08 Oct 2007 14:31:18 -0000 On Mon, Oct 08, 2007 at 04:27:21PM +0200, Marc Fonvieille wrote: > > > > Is this a SMP kernel on a UP machine? If so can you try without SMP in > > your config? > > > > Without SMP and apic, the number of context switches is lower: > > procs memory page disks faults cpu > r b w avm fre flt re pi po fr sr ad4 cd0 in sy cs us sy id > 0 0 0 501656 89424 0 0 0 0 0 0 0 0 1266 3532 1511 8 7 86 > 0 0 0 501656 89424 0 0 0 0 0 0 0 0 1252 8127 964 11 6 83 > 1 0 0 501656 89424 0 0 0 0 0 0 0 0 1253 1514 973 2 7 92 > 3 0 0 501656 89424 2647 0 0 0 2662 0 6 0 1397 12460 2663 42 24 34 > 2 0 0 501656 89424 379 0 0 0 375 0 0 0 1307 16338 2528 81 17 2 > 4 0 0 501500 89424 5 0 0 0 0 0 0 0 1561 6544 1818 85 15 0 > 4 0 0 501300 89424 1693 0 0 0 1693 0 1 0 1507 9523 1780 86 14 0 > 3 0 0 501792 89424 876 0 0 0 873 0 3 0 1321 14872 1693 81 19 0 > 1 0 0 501580 89424 2674 0 0 0 2574 0 0 0 1305 10642 1690 88 12 0 > 2 0 0 501580 89424 876 0 0 0 866 0 0 0 1266 12783 2005 58 10 33 > 2 0 0 501580 89424 0 0 0 0 0 0 3 0 1291 1464 996 2 6 92 > > > but still a slightly higher than on 6.X, but I'm still experiencing > slowdown of webpage rendering during compilation. > The "slightly higher" is my fault, I was running an additional application compared to the previous test, without this app the result (the number of cs is identical). -- Marc From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 14:42: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 D9DFF16A468; Mon, 8 Oct 2007 14:42:39 +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 8CCEB13C480; Mon, 8 Oct 2007 14:42:39 +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 4AAFD20BC; Mon, 8 Oct 2007 16:42:30 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 32E6020BB; Mon, 8 Oct 2007 16:42:30 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id 2179684486; Mon, 8 Oct 2007 16:42:30 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: ticso@cicely.de References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> <86bqb97mym.fsf@ds4.des.no> <20071008134407.GB67153@cicely12.cicely.de> Date: Mon, 08 Oct 2007 16:42:30 +0200 In-Reply-To: <20071008134407.GB67153@cicely12.cicely.de> (Bernd Walter's message of "Mon\, 8 Oct 2007 15\:44\:07 +0200") Message-ID: <864ph17jmx.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-fs@freebsd.org, freebsd-current@freebsd.org, Pawel Jakub Dawidek Subject: Re: ZFS kmem_map too small. 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, 08 Oct 2007 14:42:40 -0000 Bernd Walter writes: > On Mon, Oct 08, 2007 at 03:30:41PM +0200, Dag-Erling Sm=C3=B8rgrav wrote: > > Speaking of which, I tried setting vm.kmem_size to 2G on a C2D system > > with 4 GB RAM, but it simply panics: > >=20 > > OK set vm.kmem_size=3D2G > This sounds like there's a signed 32 bit limit somewhere. Yes, this is really stupid - vm.kmem_size is an int. Thanks for setting me on the right track. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 15:01: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 5642116A41B for ; Mon, 8 Oct 2007 15:01:16 +0000 (UTC) (envelope-from timur@com.bat.ru) Received: from mail.bat.ru (dzokonda.xs4all.nl [194.109.164.75]) by mx1.freebsd.org (Postfix) with ESMTP id 77D5D13C468 for ; Mon, 8 Oct 2007 15:01:15 +0000 (UTC) (envelope-from timur@com.bat.ru) Received: from timur.home.bat.ru ([192.168.0.4] verified) by mail.bat.ru (CommuniGate Pro SMTP 4.2.7) with ESMTP-TLS id 653691; Mon, 08 Oct 2007 16:03:55 +0200 Received: (from timur@localhost) by timur.home.bat.ru (8.14.1/8.14.1/Submit) id l98E1EIh022509; Mon, 8 Oct 2007 16:01:14 +0200 (CEST) (envelope-from timur) Date: Mon, 8 Oct 2007 16:01:14 +0200 From: "Timur I. Bakeyev" To: Michael Hanselmann Message-ID: <20071008140113.GG98428@com.bat.ru> References: <20070716190258.GA25030@hansmi.ch> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="a+b56+3nqLzpiR9O" Content-Disposition: inline In-Reply-To: <20070716190258.GA25030@hansmi.ch> User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: tobias.mueller@hostpoint.ch, m.kooijman@student.utwente.nl, freebsd-current@freebsd.org, elias.wittwer@hostpoint.ch Subject: Re: [PATCH] Implement getgroupmembership(3) for massive performance gain when using LDAP or Winbind 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, 08 Oct 2007 15:01:16 -0000 --a+b56+3nqLzpiR9O Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, Michael! On Mon, Jul 16, 2007 at 09:02:58PM +0200, Michael Hanselmann wrote: > Hello >=20 > I was working with a company which plans to migrate its FreeBSD servers > from using /etc/{passwd,group} to LDAP. They will have about 45'000 > users and as much groups in the directory. Did you get any reaction on your patch and estimation when it maybe included into the CURRENT? With best regards, Timur Bakeyev. --a+b56+3nqLzpiR9O Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHCjgpC/BkEmC6H0cRAkryAJ9J56oitwIGTXs3T1mIn5J1fJx3BwCg5kLL TXHNOcw63t2SAyhzM6R2xzY= =Uqsr -----END PGP SIGNATURE----- --a+b56+3nqLzpiR9O-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 15:29: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 6CEFF16A41A; Mon, 8 Oct 2007 15:29:02 +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 22C0713C448; Mon, 8 Oct 2007 15:29:02 +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 857F820BF; Mon, 8 Oct 2007 17:28:52 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 0182420BA; Mon, 8 Oct 2007 17:28:51 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id C181F8442C; Mon, 8 Oct 2007 17:28:51 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: ticso@cicely.de References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> <86bqb97mym.fsf@ds4.des.no> <20071008134407.GB67153@cicely12.cicely.de> <864ph17jmx.fsf@ds4.des.no> Date: Mon, 08 Oct 2007 17:28:51 +0200 In-Reply-To: <864ph17jmx.fsf@ds4.des.no> ("Dag-Erling =?utf-8?Q?Sm=C3=B8rg?= =?utf-8?Q?rav=22's?= message of "Mon\, 08 Oct 2007 16\:42\:30 +0200") Message-ID: <86ve9hr5fw.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-fs@freebsd.org, freebsd-current@freebsd.org, Pawel Jakub Dawidek Subject: Re: ZFS kmem_map too small. 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, 08 Oct 2007 15:29:02 -0000 Dag-Erling Sm=C3=B8rgrav writes: > Bernd Walter writes: > > On Mon, Oct 08, 2007 at 03:30:41PM +0200, Dag-Erling Sm=C3=B8rgrav wrot= e: > > > Speaking of which, I tried setting vm.kmem_size to 2G on a C2D system > > > with 4 GB RAM, but it simply panics: > > >=20 > > > OK set vm.kmem_size=3D2G > > This sounds like there's a signed 32 bit limit somewhere. > Yes, this is really stupid - vm.kmem_size is an int. Thanks for setting > me on the right track. Actually, somebody pointed out to me that due to the memory model used, amd64 can only have 2 GB KVA, and that includes other things besides kmem, so even with the tunable bug fixed, the best I can hope for is probably 1.5 GB. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 15:31:12 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 524E016A468; Mon, 8 Oct 2007 15:31:12 +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 E7DD213C4A5; Mon, 8 Oct 2007 15:31:11 +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 1IeuZb-000EWA-0H; Mon, 08 Oct 2007 18:31:11 +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 1IeuZX-000JkX-Hq; Mon, 08 Oct 2007 18:31:10 +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 l98FV7SV035915; Mon, 8 Oct 2007 18:31:07 +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 l98FV6c4035910; Mon, 8 Oct 2007 18:31:06 +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: Mon, 8 Oct 2007 18:31:06 +0300 From: Kostik Belousov To: Roman Divacky Message-ID: <20071008153106.GN2180@deviant.kiev.zoral.com.ua> References: <20071007140237.GA44735@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Kynn+LdAwU9N+JqL" Content-Disposition: inline In-Reply-To: <20071007140237.GA44735@freebsd.org> User-Agent: Mutt/1.4.2.3i X-Scanner-Signature: fa1e9f04260dd27375e84b1224048298 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 1570 [Oct 08 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: current@freebsd.org, peter@freebsd.org Subject: Re: pad argument for mmap/lseek/etc. 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, 08 Oct 2007 15:31:12 -0000 --Kynn+LdAwU9N+JqL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 07, 2007 at 04:02:37PM +0200, Roman Divacky wrote: > hi >=20 > 3 months ago Peter Wemm removed "pad" argument from mmap/lseek/etc. sysca= lls > arguments. >=20 > Unfortunately he forgot to update the struct XYZ_args definitions shipped > with the actual functions like this: >=20 > vm/vm_mmap.c: >=20 > #ifndef _SYS_SYSPROTO_H_ > struct mmap_args { > void *addr; > size_t len; > int prot; > int flags; > int fd; > long pad; > off_t pos; > }; > #endif >=20 > /* > * MPSAFE > */ > int > mmap(td, uap) > struct thread *td; > struct mmap_args *uap; >=20 > it would be nice to get this removed. I'd submit a patch but I dont > know what syscalls this affected. You should lookup the corresponding commit that obviously touched syscalls.master (seems to be rev. 1.232), and get the syscalls list from there. Then, you should copy the old structure definitions to freebsd6_XXX functions, and delete the paddings inplace. The interesting question is whether the _SYS_SYSPROTO_H and absense of the sys/sysproto.h supported. Or, shall we remove these #ifdef blocks instead of fixing them in whole kernel. --Kynn+LdAwU9N+JqL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHCk06C3+MBN1Mb4gRApzUAKDIZVtxRXcKRMj+TuKihD6Y5PJwzwCdGcKT kwYDwtOw4ECnizLy9/JzIAk= =LwWF -----END PGP SIGNATURE----- --Kynn+LdAwU9N+JqL-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 16:18: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 0FEC916A4C1 for ; Mon, 8 Oct 2007 16:18:13 +0000 (UTC) (envelope-from ups@freebsd.org) Received: from smtpauth11.prod.mesa1.secureserver.net (smtpauth11.prod.mesa1.secureserver.net [64.202.165.33]) by mx1.freebsd.org (Postfix) with SMTP id B7B5513C467 for ; Mon, 8 Oct 2007 16:18:12 +0000 (UTC) (envelope-from ups@freebsd.org) Received: (qmail 4666 invoked from network); 8 Oct 2007 15:51:32 -0000 Received: from unknown (66.23.216.53) by smtpauth11.prod.mesa1.secureserver.net (64.202.165.33) with ESMTP; 08 Oct 2007 15:51:30 -0000 Message-ID: <470A519A.5030708@freebsd.org> Date: Mon, 08 Oct 2007 11:49:46 -0400 From: Stephan Uphoff User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Eric Anderson References: <47041B1D.8060900@delphij.net> <47043B71.1@mawer.org> <470445EB.2040401@freebsd.org> In-Reply-To: <470445EB.2040401@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, d@delphij.net, Philip Murray , Antony Mawer Subject: Re: GJournal 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, 08 Oct 2007 16:18:13 -0000 Eric Anderson wrote: > Antony Mawer wrote: >> On 4/10/2007 8:43 AM, LI Xin wrote: >>> Philip Murray wrote: >>>> Hi, >>>> >>>> I've got a 3TB volume that I really really want to avoid fscks on >>>> (they're taking 4-5hours on an exist 1.5TB volume) so Gjournal is >>>> looking good. >>>> >>>> Is it possible to make it only journal meta-data? Instead of data and >>>> meta-data (ie, like XFS, ext3 by default etc), it seems like you'd >>>> take >>>> less of a performance hit due to not having to write all the data >>>> twice. >>> >>> Not now. gjournal now acts as a block-level journal provider which >>> does >>> not distinguish between meta-data and file data. >> >> Has anyone heard any more information on "BLUFFS" - the "BSD Logging >> Updated Fast File System" that was mentioned at the May 2007 >> Developer Summit? The only information I have been able to find is >> the PDF slides from the presentation, which are here: >> >> http://people.freebsd.org/~ups/pubs/asiabsdcon2007/asiabsdcon_slides_2007.pdf >> >> >> The last slide states the anticipated testing date as Q1, slipped to >> Q2... we are now in Q4 and the only thing I can find on BLUFFS is >> said PDF above. >> >> I do hold out hope for a proper journalled FS for FreeBSD, as while >> ZFS is brilliant in many regards, it is very memory-heavy and as such >> not suitable for all applications... at the same time, UFS is >> reaching the stage where larger filesystems take hours or even days >> to fsck, or sometimes fail altogether from lack of memory. While >> gjournal does provide a partial solution, the penalty from having to >> write the data out to disk twice is a limitation... > > Last I heard from ups@, he was slammed with other things so BLUFFS was > temporarily on hold. > > Eric > > Unfortunately this is still true. While this is my personal priority and I plan to spend substantial time on bluffs the next months I can't promise that this will actually happen. Stephan Stephan From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 16:27: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 994F516A417; Mon, 8 Oct 2007 16:27:43 +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 81EA313C45D; Mon, 8 Oct 2007 16:27:43 +0000 (UTC) (envelope-from cb@severious.net) Received: by ion.gank.org (Postfix, from userid 1001) id 32799115D7; Mon, 8 Oct 2007 11:27:43 -0500 (CDT) Date: Mon, 8 Oct 2007 11:27:42 -0500 From: Craig Boston To: Bakul Shah Message-ID: <20071008162730.GA98555@nowhere> Mail-Followup-To: Craig Boston , Bakul Shah , Pawel Jakub Dawidek , freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org References: <20071005180119.GE98210@garage.freebsd.pl> <20071006174614.E1D575B52@mail.bitblocks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071006174614.E1D575B52@mail.bitblocks.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org, Pawel Jakub Dawidek Subject: Re: ZFS kmem_map too small. 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, 08 Oct 2007 16:27:43 -0000 On Sat, Oct 06, 2007 at 10:46:14AM -0700, Bakul Shah wrote: > There two differences: R1.11 arc_reclaim_needed() returns 1 when 80% > of kmem is used, while R1.10 does so at 50% of kmem. I'll bet it's this change that provokes the problem; as even when manually tuning the ARC size to 1/2 kmem_size or lower I still sometimes get panics. Probably what's happening is kmem usage gets high from other things, and when there's a sudden spike zfs can't react fast enough and shrink the ARC. At 50% it acts more conservatively so there's more memory available for burst usage. I noticed that some of the time, on my mostly-stable system, the panic happens when the nvidia driver is trying to allocate a 128K chunk. vmstat -m only shows nvidia at ~12MB total though, so I think it just gets hit because it malloc/frees large blocks more than most subsystems. The 512MB memory one doesn't run X at all, but it's by far the least stable of the bunch. Unfortunately it doesn't seem to want to create crash dumps for some reason. > Still, fiddling with limits to make the panic go away seems > to somehow miss the point as I always worry it will show up > under other conditions. May be there a way to ensure that > kmem_map is never too small or may be zfs can reserve a few > resources for its own use so that it can get out of a tight > spot? I don't think having ZFS reserve resources would help, as at least for me the kmem_map panic doesn't always happen within ZFS code. It's just that the increased kernel memory demands from ZFS are causing it to run out at times. I still think the best course is to have ZFS's cache use VM objects like the buffer cache does, but I know this is a very nontrivial thing to do. Craig From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 16:33: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 1B1E616A417; Mon, 8 Oct 2007 16:33:51 +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 0597F13C45A; Mon, 8 Oct 2007 16:33:50 +0000 (UTC) (envelope-from cb@severious.net) Received: by ion.gank.org (Postfix, from userid 1001) id AF63611794; Mon, 8 Oct 2007 11:33:50 -0500 (CDT) Date: Mon, 8 Oct 2007 11:33:49 -0500 From: Craig Boston To: Pawel Jakub Dawidek Message-ID: <20071008163349.GB98555@nowhere> Mail-Followup-To: Craig Boston , Pawel Jakub Dawidek , freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071008121523.GM2327@garage.freebsd.pl> User-Agent: Mutt/1.4.2.3i Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: ZFS kmem_map too small. 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, 08 Oct 2007 16:33:51 -0000 On Mon, Oct 08, 2007 at 02:15:23PM +0200, Pawel Jakub Dawidek wrote: > It's a hack, yes, but allows to mitigate the problem quite well. I'm > looking for a solution that can be used for 7.0 before we find a better > fix. Um, tsleep()ing when M_NOWAIT is set? Yes, I'd call that quite a hack :) Sorry to spam the thread again, but one thing I noticed is that zfs does an awful lot of allocations of various sizes: $ uptime 11:30AM up 2 days, 18:06, 11 users, load averages: 0.05, 0.12, 0.15 (was idle most of the weekend) $ vmstat -m | grep solaris solaris 83176 341456K - 53216607 16,32,64,128,256,512,1024,2048,4096 I'm not completely up-to-date on what algorithm the kernel allocator is using these days, but is it possible that kernel memory is getting fragmented by all of those allocations? Craig From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 16:42: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 4A25316A417 for ; Mon, 8 Oct 2007 16:42:52 +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 2C83A13C447 for ; Mon, 8 Oct 2007 16:42:52 +0000 (UTC) (envelope-from cb@severious.net) Received: by ion.gank.org (Postfix, from userid 1001) id E7F0F115D7; Mon, 8 Oct 2007 11:42:51 -0500 (CDT) Date: Mon, 8 Oct 2007 11:42:51 -0500 From: Craig Boston To: "Ralf S. Engelschall" Message-ID: <20071008164250.GC98555@nowhere> Mail-Followup-To: Craig Boston , "Ralf S. Engelschall" , freebsd-current@freebsd.org References: <20071005193825.GA66299@engelschall.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071005193825.GA66299@engelschall.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: cosmetics: bsdlabel fstype for ZFS partitions? 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, 08 Oct 2007 16:42:52 -0000 On Fri, Oct 05, 2007 at 09:38:25PM +0200, Ralf S. Engelschall wrote: > I currently use "unused" here for the partition of the ZFS pool and > everything works just fine, of coure. But it looks a little bit strange > to me and this small cosmetic issue should be fixed IMHO. I tend to abuse 'vinum' for this, and I suspect many use 4.2BSD just out of paranoia of 'unused' being accidentally overwritten. I also have ZFS on a few GPT-labeled disks and had a hard time deciding what GUID to use. I couldn't find a good reference for what Sun uses for ZFS disks, so I ended up making up a bogus one under FreeBSD's range. 516e7cba-6ecf-11d6-8ff8-00022d09712b Craig From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 17:02: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 4DCEF16A476 for ; Mon, 8 Oct 2007 17:02:27 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.68]) by mx1.freebsd.org (Postfix) with ESMTP id 66AD013C481 for ; Mon, 8 Oct 2007 17:02:26 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (smtpin06-en2 [10.13.10.151]) by smtpoutm.mac.com (Xserve/smtpout005/MantshX 4.0) with ESMTP id l98H2QRV004086; Mon, 8 Oct 2007 10:02:26 -0700 (PDT) Received: from [172.24.104.105] (natint3.juniper.net [66.129.224.36]) (authenticated bits=0) by mac.com (Xserve/smtpin06/MantshX 4.0) with ESMTP id l98H2OJT019591 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 8 Oct 2007 10:02:25 -0700 (PDT) In-Reply-To: <20071008164250.GC98555@nowhere> References: <20071005193825.GA66299@engelschall.com> <20071008164250.GC98555@nowhere> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <539A3DC9-59C9-4106-8F35-4D5676707EC0@mac.com> Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Mon, 8 Oct 2007 10:02:03 -0700 To: Craig Boston X-Mailer: Apple Mail (2.752.3) Cc: freebsd-current@freebsd.org, "Ralf S. Engelschall" Subject: Re: cosmetics: bsdlabel fstype for ZFS partitions? 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, 08 Oct 2007 17:02:27 -0000 On Oct 8, 2007, at 9:42 AM, Craig Boston wrote: > On Fri, Oct 05, 2007 at 09:38:25PM +0200, Ralf S. Engelschall wrote: >> I currently use "unused" here for the partition of the ZFS pool and >> everything works just fine, of coure. But it looks a little bit >> strange >> to me and this small cosmetic issue should be fixed IMHO. > > I tend to abuse 'vinum' for this, and I suspect many use 4.2BSD > just out > of paranoia of 'unused' being accidentally overwritten. > > I also have ZFS on a few GPT-labeled disks and had a hard time > deciding > what GUID to use. I couldn't find a good reference for what Sun uses > for ZFS disks, so I ended up making up a bogus one under FreeBSD's > range. > > 516e7cba-6ecf-11d6-8ff8-00022d09712b This is technically speaking not a good idea because the UUID may be in use already. In this case, given that the MAC address is in one of my machines, it can only be a UUID I can possibly generate (legally) and I can tell you that the UUID is not in use :-) If no-one has created their own UUID for ZFS, I'll re-use Craig's one so that he doesn't have to change his GPT. Any objections for using Craig's synthesized UUID for ZFS file systems? -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 17:18: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 9333716A417 for ; Mon, 8 Oct 2007 17:18:13 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.233]) by mx1.freebsd.org (Postfix) with ESMTP id 4FE6213C48D for ; Mon, 8 Oct 2007 17:18:12 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by wr-out-0506.google.com with SMTP id 70so617128wra for ; Mon, 08 Oct 2007 10:18:11 -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=DFqOBvECxVKQzhVij+f+RDRd6rcieximN8lGL0C9N68=; b=bsZUEtcC0S7M8kabIsDAUYNj5imp2zaMa7TaqpxmoT9kuKu2NYd6u5RSIqjOgMACliUJvrhopTJlB+A5b+4CccuDclT4fiIb9JaFXxPI+Vbhr/pfEYnGMMXOZhs3vT7WTV5fD8YoOd01DhYZWHcbJ/eR++OWTiDlvgI7jOeIAEI= 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=lCyhIjEDU0m7klQn/8Ox33YeGONoFXyXgAi+GZWl4brhbHPkm/QFrLzEo9zVd7higDOa4xthhj7HAa77kvm7rmgBstyXvzghbhR0I/220fY0Wt+9D8dcJa0bRzjJTS3oqcYXC/fuiC2raT3x5TyXIt6ZD2UM9khp9A/ixECTM6I= Received: by 10.78.193.5 with SMTP id q5mr10781511huf.1191863890340; Mon, 08 Oct 2007 10:18:10 -0700 (PDT) Received: by 10.78.146.10 with HTTP; Mon, 8 Oct 2007 10:18:10 -0700 (PDT) Message-ID: Date: Mon, 8 Oct 2007 19:18:10 +0200 From: "Claus Guttesen" To: "Pawel Jakub Dawidek" In-Reply-To: <20071008121523.GM2327@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS kmem_map too small. 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, 08 Oct 2007 17:18:13 -0000 > I was able to reproduce the panic by rsyncing big files and trying > bonnie++ test suggested in this thread. > > Can you guys retry with this patch: > > http://people.freebsd.org/~pjd/patches/vm_kern.c.2.patch > > It's a hack, yes, but allows to mitigate the problem quite well. I'm > looking for a solution that can be used for 7.0 before we find a better > fix. Congrats Pawel! You made my server survive my rsync of 90 GB. :-) This is on same src as the one that required a reboot except for your patch. So this fix does 'alleviate kmem_map too small' in my case. -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 17:25:52 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 2DD5816A41A; Mon, 8 Oct 2007 17:25:52 +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 D38FE13C48D; Mon, 8 Oct 2007 17:25:50 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 3A82C668E15; Mon, 8 Oct 2007 19:25:49 +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 uQWlm7W9DHTi; Mon, 8 Oct 2007 19:25:45 +0200 (CEST) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 50ED3668E14; Mon, 8 Oct 2007 19:25:45 +0200 (CEST) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.13.8/8.13.8/Submit) id l98HPjBD091451; Mon, 8 Oct 2007 19:25:45 +0200 (CEST) (envelope-from rdivacky) Date: Mon, 8 Oct 2007 19:25:45 +0200 From: Roman Divacky To: Kostik Belousov Message-ID: <20071008172545.GA91406@freebsd.org> References: <20071007140237.GA44735@freebsd.org> <20071008153106.GN2180@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071008153106.GN2180@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org, peter@freebsd.org Subject: Re: pad argument for mmap/lseek/etc. 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, 08 Oct 2007 17:25:52 -0000 > The interesting question is whether the _SYS_SYSPROTO_H and absense of the > sys/sysproto.h supported. Or, shall we remove these #ifdef blocks instead > of fixing them in whole kernel. I also support this idea... does anyone have an argument against or should I just provide a patch (removing those definitions) roman From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 17:31: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 4985916A418 for ; Mon, 8 Oct 2007 17:31:49 +0000 (UTC) (envelope-from rse@engelschall.com) Received: from visp1.engelschall.com (visp1.engelschall.com [195.30.6.144]) by mx1.freebsd.org (Postfix) with ESMTP id 0FC5B13C457 for ; Mon, 8 Oct 2007 17:31:49 +0000 (UTC) (envelope-from rse@engelschall.com) Received: by visp1.engelschall.com (Postfix, from userid 21100) id CA5C01B44816; Mon, 8 Oct 2007 19:31:48 +0200 (CEST) Received: by en1.engelschall.com (Postfix, from userid 10000) id 12C416D83E; Mon, 8 Oct 2007 19:28:01 +0200 (CEST) Date: Mon, 8 Oct 2007 19:28:01 +0200 From: "Ralf S. Engelschall" To: freebsd-current@freebsd.org Message-ID: <20071008172801.GA82997@engelschall.com> References: <20071005193825.GA66299@engelschall.com> <20071008164250.GC98555@nowhere> <539A3DC9-59C9-4106-8F35-4D5676707EC0@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <539A3DC9-59C9-4106-8F35-4D5676707EC0@mac.com> Organization: FreeBSD User-Agent: Mutt/1.5.16 OpenPKG/CURRENT (2007-06-09) Subject: Re: cosmetics: bsdlabel fstype for ZFS partitions? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Ralf S. Engelschall" List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Oct 2007 17:31:49 -0000 On Mon, Oct 08, 2007, Marcel Moolenaar wrote: > On Oct 8, 2007, at 9:42 AM, Craig Boston wrote: >> On Fri, Oct 05, 2007 at 09:38:25PM +0200, Ralf S. Engelschall wrote: > [...] >> what GUID to use. I couldn't find a good reference for what Sun uses >> for ZFS disks, so I ended up making up a bogus one under FreeBSD's >> range. >> >> 516e7cba-6ecf-11d6-8ff8-00022d09712b Well, this UUID is... $ uuid -d 516e7cba-6ecf-11d6-8ff8-00022d09712b encode: STR: 516e7cba-6ecf-11d6-8ff8-00022d09712b SIV: 108241150102539780167861756444952588587 decode: variant: DCE 1.1, ISO/IEC 11578:1996 version: 1 (time and node based) content: time: 2002-05-24 04:32:55.748933.8 UTC clock: 4088 (usually random) node: 00:02:2d:09:71:2b (global unicast) > This is technically speaking not a good idea because the UUID may > be in use already. In this case, given that the MAC address is in > one of my machines, it can only be a UUID I can possibly generate > (legally) and I can tell you that the UUID is not in use :-) > > If no-one has created their own UUID for ZFS, I'll re-use Craig's > one so that he doesn't have to change his GPT. Any objections for > using Craig's synthesized UUID for ZFS file systems? Well, if a really synthesized UUID for ZFS under FreeBSD is wished, I would propose to generate a UUID v3 for this purpose and add this to the FreeBSD handbook so people can find it. For instance something like: $ uuid -v3 ns:DNS zfs.FreeBSD.org 61d35356-226b-38dd-8346-f97771b80070 $ uuid -d 61d35356-226b-38dd-8346-f97771b80070 encode: STR: 61d35356-226b-38dd-8346-f97771b80070 SIV: 130032380492558881552004941246316937328 decode: variant: DCE 1.1, ISO/IEC 11578:1996 version: 3 (name based, MD5) content: 61:D3:53:56:22:6B:08:DD:03:46:F9:77:71:B8:00:70 (not decipherable: MD5 message digest only) Ralf S. Engelschall rse@engelschall.com www.engelschall.com From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 17: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 85FEB16A421 for ; Mon, 8 Oct 2007 17: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 42AEE13C465 for ; Mon, 8 Oct 2007 17: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 l98Hx4OR094011; Mon, 8 Oct 2007 13:59:04 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-current@FreeBSD.org, "Ralf S. Engelschall" Date: Mon, 8 Oct 2007 13:58:54 -0400 User-Agent: KMail/1.6.2 References: <20071005193825.GA66299@engelschall.com> <539A3DC9-59C9-4106-8F35-4D5676707EC0@mac.com> <20071008172801.GA82997@engelschall.com> In-Reply-To: <20071008172801.GA82997@engelschall.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200710081358.56947.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.90.2/4506/Mon Oct 8 12:43:33 2007 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Subject: Re: cosmetics: bsdlabel fstype for ZFS partitions? 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, 08 Oct 2007 17:59:05 -0000 On Monday 08 October 2007 01:28 pm, Ralf S. Engelschall wrote: > On Mon, Oct 08, 2007, Marcel Moolenaar wrote: > > On Oct 8, 2007, at 9:42 AM, Craig Boston wrote: > >> On Fri, Oct 05, 2007 at 09:38:25PM +0200, Ralf S. Engelschall > >> wrote: > > > > [...] > > > >> what GUID to use. I couldn't find a good reference for what Sun > >> uses for ZFS disks, so I ended up making up a bogus one under > >> FreeBSD's range. > >> > >> 516e7cba-6ecf-11d6-8ff8-00022d09712b > > Well, this UUID is... > > $ uuid -d 516e7cba-6ecf-11d6-8ff8-00022d09712b > encode: STR: 516e7cba-6ecf-11d6-8ff8-00022d09712b > SIV: 108241150102539780167861756444952588587 > decode: variant: DCE 1.1, ISO/IEC 11578:1996 > version: 1 (time and node based) > content: time: 2002-05-24 04:32:55.748933.8 UTC > clock: 4088 (usually random) > node: 00:02:2d:09:71:2b (global unicast) > > > This is technically speaking not a good idea because the UUID may > > be in use already. In this case, given that the MAC address is in > > one of my machines, it can only be a UUID I can possibly generate > > (legally) and I can tell you that the UUID is not in use :-) > > > > If no-one has created their own UUID for ZFS, I'll re-use Craig's > > one so that he doesn't have to change his GPT. Any objections for > > using Craig's synthesized UUID for ZFS file systems? > > Well, if a really synthesized UUID for ZFS under FreeBSD is wished, > I would propose to generate a UUID v3 for this purpose and add this > to the FreeBSD handbook so people can find it. For instance > something like: > > $ uuid -v3 ns:DNS zfs.FreeBSD.org > 61d35356-226b-38dd-8346-f97771b80070 > $ uuid -d 61d35356-226b-38dd-8346-f97771b80070 > encode: STR: 61d35356-226b-38dd-8346-f97771b80070 > SIV: 130032380492558881552004941246316937328 > decode: variant: DCE 1.1, ISO/IEC 11578:1996 > version: 3 (name based, MD5) > content: 61:D3:53:56:22:6B:08:DD:03:46:F9:77:71:B8:00:70 > (not decipherable: MD5 message digest only) FYI, FreeBSD's UUIDs are here: http://fxr.watson.org/fxr/source/sys/gpt.h#L77 We have been using them for years and I don't think it is necessary to switch the encoding from v1 to v3 IMHO. BTW, just out of my curiosity, I grok'd OpenSolaris sources. OpenSolaris seems to use the following UUID for ZFS nowadays: http://fxr.watson.org/fxr/source/common/sys/efi_partition.h?v=OPENSOLARIS#L113 It seems it was reserved for cachefs but never used (according to some comments in the OpenSolaris source tree). So, instead of adding another UUID for ZFS, they just reused it for ZFS, I guess. I wonder what Apple would do for the upcoming ZFS support. ;-) http://arstechnica.com/journals/apple.ars/2007/10/07/apple-delivers-zfs-readwrite-developer-preview-1-1-for-leopard Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 18:14: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 7466B16A41A; Mon, 8 Oct 2007 18:14:49 +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 6307713C457; Mon, 8 Oct 2007 18:14:49 +0000 (UTC) (envelope-from cb@severious.net) Received: by ion.gank.org (Postfix, from userid 1001) id 05316110F2; Mon, 8 Oct 2007 13:14:49 -0500 (CDT) Date: Mon, 8 Oct 2007 13:14:47 -0500 From: Craig Boston To: Pawel Jakub Dawidek , freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org Message-ID: <20071008181447.GD98555@nowhere> Mail-Followup-To: Craig Boston , Pawel Jakub Dawidek , freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> <20071008163349.GB98555@nowhere> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071008163349.GB98555@nowhere> User-Agent: Mutt/1.4.2.3i Cc: Subject: Re: ZFS kmem_map too small. 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, 08 Oct 2007 18:14:49 -0000 On Mon, Oct 08, 2007 at 11:33:49AM -0500, Craig Boston wrote: > Um, tsleep()ing when M_NOWAIT is set? Yes, I'd call that quite a hack > :) Oops, my binary logic is inverted today. Please ignore. Craig From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 18:22: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 5278316A46B for ; Mon, 8 Oct 2007 18:22:57 +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 B723D13C494 for ; Mon, 8 Oct 2007 18:22:55 +0000 (UTC) (envelope-from hopet@ics.muni.cz) Received: from KLOBOUCEK (w54-145.fi.muni.cz [147.251.54.145]) (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 l98IMr9g009023 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Mon, 8 Oct 2007 20:22:54 +0200 From: "Petr Holub" To: Date: Mon, 8 Oct 2007 20:24:07 +0200 Message-ID: <031401c809d8$69c12270$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.54.145 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]); Mon, 08 Oct 2007 20:22:54 +0200 (CEST) X-Mailman-Approved-At: Mon, 08 Oct 2007 19:11:04 +0000 Cc: Subject: panic on boot 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, 08 Oct 2007 18:22:57 -0000 Hi, I was about to install September -CURRENT snapshot on a machine with 10GE card. When attempting to install from USB CDROM (it's a 1U machine without, I get something like a kernel panic with a stacktrace running indefinitely and very fast. I must be in a very early stage as I was unable to break it anyhow. When I tried to break in using serial console (setup using BIOS), the last message I get in the console is CD Loader 1.2 and then nothing, but the screen keeps running with sth like register dump. This behavior also occurs with both i386 and amd64 Sept07 snapshot, i386 March07 snapshot and i386 FreeSBIE 1.1 which I attempted to run as well. However, Feisty Fawn runs and installs just fine. Basically, it's a dual processor dual core (4 cores in total) Intel Xeon 5160 @ 3GHz with 4GB RAM. Is there any way to stop this and debug it? TIA, Petr From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 19:34: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 0BC6616A41A for ; Mon, 8 Oct 2007 19:34:11 +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 B591C13C480 for ; Mon, 8 Oct 2007 19:34:10 +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 1IeyMk-0007go-0p for current@freebsd.org; Mon, 08 Oct 2007 22:34:10 +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 1IeyMh-000JCv-Du for current@freebsd.org; Mon, 08 Oct 2007 22:34:09 +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 l98JY6CK069834; Mon, 8 Oct 2007 22:34:06 +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 l98JY6hu069833; Mon, 8 Oct 2007 22:34:06 +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: Mon, 8 Oct 2007 22:34:06 +0300 From: Kostik Belousov To: Petr Holub Message-ID: <20071008193406.GT2180@deviant.kiev.zoral.com.ua> References: <031401c809d8$69c12270$5317fb93@KLOBOUCEK> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xsILJLaVOAbiPmXa" Content-Disposition: inline In-Reply-To: <031401c809d8$69c12270$5317fb93@KLOBOUCEK> User-Agent: Mutt/1.4.2.3i X-Scanner-Signature: 5e2df25549de819b25d1bfd51e9f52eb X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 1570 [Oct 08 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: current@freebsd.org Subject: Re: panic on boot 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, 08 Oct 2007 19:34:11 -0000 --xsILJLaVOAbiPmXa Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 08, 2007 at 08:24:07PM +0200, Petr Holub wrote: > Hi, >=20 > I was about to install September -CURRENT snapshot on a machine > with 10GE card. When attempting to install from USB CDROM (it's > a 1U machine without, I get something like a kernel panic > with a stacktrace running indefinitely and very fast. I must be > in a very early stage as I was unable to break it anyhow. When > I tried to break in using serial console (setup using BIOS), the > last message I get in the console is > CD Loader 1.2 > and then nothing, but the screen keeps running with sth like register > dump. >=20 > This behavior also occurs with both i386 and amd64 Sept07 snapshot, > i386 March07 snapshot and i386 FreeSBIE 1.1 which I attempted to run > as well. However, Feisty Fawn runs and installs just fine. >=20 > Basically, it's a dual processor dual core (4 cores in total) > Intel Xeon 5160 @ 3GHz with 4GB RAM. >=20 > Is there any way to stop this and debug it? There is a known problem with some BIOSes trying to enter protected mode when serving requests, esp. USB stacks. The usual simptom of the problem is BTX panic on the console. I cannot say for sure whether this is your case. The patch exists that modifies BTX to reflect interrupts and requests into the real mode, see http://people.freebsd.org/~kib/realbtx/ http://people.freebsd.org/~kib/realbtx/realbtx.2.patch You would need to either somehow inplant supplied loader into your CD image, or rebuild the whole installation CD with patch applied. Again, I cannot guarantee that the patch is relevant for your problem. --xsILJLaVOAbiPmXa Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHCoYuC3+MBN1Mb4gRAumSAJkBuky4AT6+gr6eMKEXMLJC8mcERACfeeR6 0a332efIhgJiEyRnJBP/OmM= =w6B+ -----END PGP SIGNATURE----- --xsILJLaVOAbiPmXa-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 19:31:36 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 A00E716A419 for ; Mon, 8 Oct 2007 19:31:36 +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 22BAD13C4BC for ; Mon, 8 Oct 2007 19:31:35 +0000 (UTC) (envelope-from hopet@ics.muni.cz) Received: from KLOBOUCEK (w54-145.fi.muni.cz [147.251.54.145]) (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 l98JVYH7022659 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Mon, 8 Oct 2007 21:31:34 +0200 From: "Petr Holub" To: Date: Mon, 8 Oct 2007 21:32:47 +0200 Message-ID: <031701c809e2$01d82320$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 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 X-Muni-Spam-TestIP: 147.251.54.145 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]); Mon, 08 Oct 2007 21:31:34 +0200 (CEST) X-Mailman-Approved-At: Mon, 08 Oct 2007 19:48:41 +0000 Cc: Subject: RE: panic on boot 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, 08 Oct 2007 19:31:36 -0000 > Is there any way to stop this and debug it? A small update: it seems like a BTX fault described here: http://people.freebsd.org/~jhb/docs/loader.txt but it goes on and on so fast that it's not readable and I haven't figured out any way to stop it or redirect it to console so that I can save it. Any ideas? TIA, Petr From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 20:28: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 90C3F16A417; Mon, 8 Oct 2007 20:28:36 +0000 (UTC) (envelope-from gb@isis.u-strasbg.fr) Received: from mailhost.u-strasbg.fr (mailhost.u-strasbg.fr [IPv6:2001:660:2402::156]) by mx1.freebsd.org (Postfix) with ESMTP id 2CF6913C474; Mon, 8 Oct 2007 20:28:36 +0000 (UTC) (envelope-from gb@isis.u-strasbg.fr) Received: from 6nq.u-strasbg.fr (mojito.u-strasbg.fr [IPv6:2001:660:4701:1002::3]) by mailhost.u-strasbg.fr (8.13.8/jtpda-5.5pre1) with ESMTP id l98KSTS7010471 ; Mon, 8 Oct 2007 22:28:29 +0200 (CEST) Received: by 6nq.u-strasbg.fr (Postfix, from userid 1001) id 1EB8D8184; Mon, 8 Oct 2007 22:27:44 +0200 (CEST) Date: Mon, 8 Oct 2007 22:27:44 +0200 From: Guy Brand To: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Message-ID: <20071008202743.GA1555@isis.u-strasbg.fr> References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20071008121523.GM2327@garage.freebsd.pl> x-gpg-fingerprint: B423 4924 012E 52F3 BA9E 547F CC8C 0BC5 9C0E B1CA x-gpg-key: 9C0EB1CA User-Agent: Mutt/1.5.16 (2007-06-09) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (mailhost.u-strasbg.fr [IPv6:2001:660:2402::156]); Mon, 08 Oct 2007 22:28:29 +0200 (CEST) X-Virus-Scanned: ClamAV 0.88.7/4507/Mon Oct 8 20:42:59 2007 on mr6.u-strasbg.fr X-Virus-Status: Clean X-Spam-Status: No, score=0.1 required=5.0 tests=AWL,NO_RELAYS autolearn=disabled version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on mr6.u-strasbg.fr Cc: Subject: Re: ZFS kmem_map too small. 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, 08 Oct 2007 20:28:36 -0000 Pawel Jakub Dawidek (pjd@freebsd.org) on 08/10/2007 at 14:15 wrote: > Can you guys retry with this patch: > > http://people.freebsd.org/~pjd/patches/vm_kern.c.2.patch > > It's a hack, yes, but allows to mitigate the problem quite well. I'm > looking for a solution that can be used for 7.0 before we find a better > fix. > > BTW. To use ZFS you _must_ increase vm.kmem_size/vm.kmem_size_max. > If you have the problem discussed here and you're using standard values, > please retry with vm.kmem_size/vm.kmem_size_max set to at least 600MB in > /boot/loader.conf. Hi, On a Lenovo X61s from yesterday (FreeBSD 7.0-CURRENT #1: Sun Oct 7 21:55:14 CEST 2007) with hw.model: Intel(R) Core(TM)2 Duo CPU L7500 @ 1.60GHz hw.physmem: 2091008000 hw.machine_arch: i386 hw.realmem: 2104164352 and a single zpool containing ad4s2 slice (all FS except /). I tuned vm.kmem_size and ran ad vitam: - vt0: rsync /usr/src /tmp/. && rm -rf /tmp/src - vt1: dd if=/dev/zero of=/tmp/file bs=1k count=1000000 The kernel panics until vm.kmem_size/vm.kmem_size_max is set to 671088640 where I could have both loops running for 3 hours. But then the system was hanging: rsync and dd seem stopped in their execution. This was confirmed on another term (load of 0). Any attempt to R/W from the poll (touch/ls) hangs the terminal. I could still log in to a term, but reboot/shutdown failed. I applied your patch and re-run the tests. After eight hours, the kernel is still up and usable. Thanks Pawel. > I'm not sure if it's not too late to ask re@ about increasing the > default kmem size at least on amd64. ~300MB we have there is silly > small. Default vm.kmem_size value is 335544320 on my laptop: a portsnap fetch + extract from scratch panics with kmem_map too small. -- bug From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 21:11: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 505B816A417 for ; Mon, 8 Oct 2007 21:11: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 C40A713C481 for ; Mon, 8 Oct 2007 21:11:16 +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 l98LBEmm016611 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 8 Oct 2007 23:11:15 +0200 From: "Petr Holub" To: "Kostik Belousov" Date: Mon, 8 Oct 2007 23:11:23 +0200 Message-ID: <031f01c809ef$c829de80$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 Importance: Normal In-Reply-To: <20071008193406.GT2180@deviant.kiev.zoral.com.ua> 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]); Mon, 08 Oct 2007 23:11:15 +0200 (CEST) X-Mailman-Approved-At: Mon, 08 Oct 2007 21:36:24 +0000 Cc: current@freebsd.org Subject: RE: panic on boot 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, 08 Oct 2007 21:11:17 -0000 > The patch exists that modifies BTX to reflect interrupts and requests into > the real mode, see > http://people.freebsd.org/~kib/realbtx/ > http://people.freebsd.org/~kib/realbtx/realbtx.2.patch > > You would need to either somehow inplant supplied loader into your CD > image, or rebuild the whole installation CD with patch applied. Again, > I cannot guarantee that the patch is relevant for your problem. Despite you couldn't guarantee it, it really helped and it boots now. I've used the binary loader available from ~kib site and just replaced it on the original ISO: mdcondifig -> mount -> tar cf - | (cd elswhere && tar xvpf -) -> replace the loader -> mkisomages.sh Thanks a lot, Petr From owner-freebsd-current@FreeBSD.ORG Mon Oct 8 23:46: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 8C17C16A418 for ; Mon, 8 Oct 2007 23:46:38 +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 08E1713C44B for ; Mon, 8 Oct 2007 23:46:37 +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 l98Nkamv008777 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 9 Oct 2007 01:46:36 +0200 From: "Petr Holub" To: "Kostik Belousov" Date: Tue, 9 Oct 2007 01:47:03 +0200 Message-ID: <032a01c80a05$871b32c0$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 Importance: Normal In-Reply-To: <20071008193406.GT2180@deviant.kiev.zoral.com.ua> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 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]); Tue, 09 Oct 2007 01:46:36 +0200 (CEST) X-Mailman-Approved-At: Mon, 08 Oct 2007 23:58:01 +0000 Cc: current@freebsd.org Subject: RE: panic on boot 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, 08 Oct 2007 23:46:38 -0000 > The patch exists that modifies BTX to reflect interrupts and requests into > the real mode, see > http://people.freebsd.org/~kib/realbtx/ > http://people.freebsd.org/~kib/realbtx/realbtx.2.patch After booting the machine with this patch, it works like a charm, looks fairly stable, Myrinet 10GE card up and running. So I wonder: would it be possible to include this realbtx into 7.0-RELEASE? It seems rather important, as many machines are now being installed off USB CD drives and USB keys... Thanks a lot, Petr From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 02:12: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 B07E816A419 for ; Tue, 9 Oct 2007 02:12:00 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-iport-2.cisco.com (sj-iport-2-in.cisco.com [171.71.176.71]) by mx1.freebsd.org (Postfix) with ESMTP id 935E413C45B for ; Tue, 9 Oct 2007 02:12:00 +0000 (UTC) (envelope-from rrs@cisco.com) X-IronPort-AV: E=Sophos;i="4.21,245,1188802800"; d="scan'208";a="404851480" Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-2.cisco.com with ESMTP; 08 Oct 2007 19:12:00 -0700 Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l992Bx8M007065 for ; Mon, 8 Oct 2007 19:11:59 -0700 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l992BxYt028516 for ; Tue, 9 Oct 2007 02:11:59 GMT Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 8 Oct 2007 19:11:59 -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); Mon, 8 Oct 2007 19:11:58 -0700 Message-ID: <470AE33B.7000806@cisco.com> Date: Mon, 08 Oct 2007 22:11:07 -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: 09 Oct 2007 02:11:58.0962 (UTC) FILETIME=[C5D57520:01C80A19] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=621; t=1191895919; x=1192759919; 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:=20AMD64=20panic=20on=20boot |Sender:=20; bh=xa+nWVyK0svFzr4lWAaGLLdeMjJD1Dk5xZjp0DGfNIs=; b=WOjesNisjLCSeLyHuInzU3ld48oOzHPNg6OS6O3UQyvdXXvrFPCbUsoVfWFUXuL31G8u/Z8S +MhHQ3oqtEf5cOQrL61E6QG3Kr5l6dm4bdcarMY/cENXUi7OZ5eVfjmu; Authentication-Results: sj-dkim-4; header.From=rrs@cisco.com; dkim=pass (sig from cisco.com/sjdkim4002 verified; ); Subject: AMD64 panic on boot 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, 09 Oct 2007 02:12:00 -0000 Hi all: I just updated to the latest.. and I am seeing a crash on boot up of my 8-core Xeon machines (running in AMD mode). its a pagefault UA= 0x2b sysctl_handle_int+0x27 syscall+0x254 Xfast_syscall+0xab IP= 0xffffffff8048e7d7 I can't get a core unfortunately.. I get a core device unavailable.. I have one of the machines sitting in a DDB> prompt and its twin sitting on the old kernel.. Let me know how I can help.. and in the mean time I will poke around in kgdb on the running machine :-) R -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 803-317-4952 (cell) From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 02:15: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 066D116A41A for ; Tue, 9 Oct 2007 02:15:32 +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 DE01D13C4AA for ; Tue, 9 Oct 2007 02:15:31 +0000 (UTC) (envelope-from rrs@cisco.com) X-IronPort-AV: E=Sophos;i="4.21,245,1188802800"; d="scan'208";a="532762274" Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-3.cisco.com with ESMTP; 08 Oct 2007 19:15:27 -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 l992FRms010089; Mon, 8 Oct 2007 19:15:27 -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 l992FR0W016932; Tue, 9 Oct 2007 02:15:27 GMT Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 8 Oct 2007 19:15:27 -0700 Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 8 Oct 2007 19:15:26 -0700 Message-ID: <470AE40D.7090006@cisco.com> Date: Mon, 08 Oct 2007 22:14:37 -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, Michael Tuexen References: <470AE33B.7000806@cisco.com> In-Reply-To: <470AE33B.7000806@cisco.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 09 Oct 2007 02:15:26.0679 (UTC) FILETIME=[41A48E70:01C80A1A] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1249; t=1191896127; x=1192760127; 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:=20Re=3A=20AMD64=20panic=20on=20boot |Sender:=20; bh=vpcyOjcxopa2iCu7aIpfI+qlCcMpMDMqEqMcjTUa900=; b=QXLM4MfYWQgo+YlJcNDpOnfHVqke6ebHDD7aUwjr36kpzV2VD2zcw/um2nIIxU0hD3Xcxtuq 2rX6SRc2jcYb/3hZAEKnqWVH5CsutdMYvvqeG4YtoxaYdy6WB2I5I4gJ; Authentication-Results: sj-dkim-4; header.From=rrs@cisco.com; dkim=pass (sig from cisco.com/sjdkim4002 verified; ); Cc: Subject: Re: AMD64 panic on boot 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, 09 Oct 2007 02:15:32 -0000 Randall Stewart wrote: > Hi all: > > I just updated to the latest.. and I am seeing a crash on > boot up of my 8-core Xeon machines (running in AMD mode). > > its a > > pagefault UA= 0x2b > > sysctl_handle_int+0x27 > syscall+0x254 > Xfast_syscall+0xab > > IP= 0xffffffff8048e7d7 > > > I can't get a core unfortunately.. I get a core device > unavailable.. > > I have one of the machines sitting in a DDB> prompt > and its twin sitting on the old kernel.. > > Let me know how I can help.. and in the mean time I will poke > around in kgdb on the running machine :-) > > R Hmm.. it appears to be in.. 0xffffffff8048e2e7 is in sysctl_handle_int (../../../kern/kern_sysctl.c:816). 811 */ 812 if (arg1) 813 tmpout = *(int *)arg1; 814 else 815 tmpout = arg2; 816 error = SYSCTL_OUT(req, &tmpout, sizeof(int)); 817 818 if (error || !req->newptr) 819 return (error); So its trying to copy out and faulting.. not sure what.. Let me know if there is some info I can poke out of DDB R -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 803-317-4952 (cell) From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 03:21: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 5D56F16A417 for ; Tue, 9 Oct 2007 03:21:02 +0000 (UTC) (envelope-from imperial_courier@yahoo.com) Received: from web53907.mail.re2.yahoo.com (web53907.mail.re2.yahoo.com [206.190.36.217]) by mx1.freebsd.org (Postfix) with SMTP id 18C0713C45A for ; Tue, 9 Oct 2007 03:21:01 +0000 (UTC) (envelope-from imperial_courier@yahoo.com) Received: (qmail 89756 invoked by uid 60001); 9 Oct 2007 03:21:01 -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=dbfphmVsHI5BR9bQ9lwUc29zQf+ETJBRitex6ftGix5SFUEtA/VVlS2/7nvzpAIcFYUVhsKfCmylLh5LJFo1zQOidFikSWSD7vWLoPlkS3lXOHwz0A2O8Ki0xpUnwmpg3t9orpdS7FtZQG8xwabBSx8BMQzinkTkEl5SAjCevSg=; X-YMail-OSG: z2jsQI8VM1mmAFt01icRpBMVUTeVhufx5ogARuqYR1LGIY2aTWQxFnPxW2mbW4gAQaD1BLTBQixY1WUoGsE2GGvjdCSQjPfDDVHIgqiJelDLp7v_4QKC8PSpRzsqTG_GhCfrNizyfg61oonEwl.Ijg-- Received: from [209.166.103.242] by web53907.mail.re2.yahoo.com via HTTP; Mon, 08 Oct 2007 20:21:00 PDT Date: Mon, 8 Oct 2007 20:21:00 -0700 (PDT) From: Dave Frantz To: freebsd-current@freebsd.org, Kip Macy , "Søren" Schmidt MIME-Version: 1.0 Message-ID: <48190.89022.qm@web53907.mail.re2.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: FreeBSD 7.0-current Locks During Device Probe--Solved 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, 09 Oct 2007 03:21:02 -0000 I finally figured out what was causing FreeBSD 7.0-current to crash on my machine during the device probe. It turns out that if options CPUFREQ is compiled in, the system will not boot. However, it can be safely kldloaded in later. I'm not entirely sure why my system dislikes CPUFREQ, but I can live without it. If you guys have any questions or anything, just let me know. -Dave --------------------------------- Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 03:56: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 4431F16A505; Tue, 9 Oct 2007 03:56:07 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp4.yandex.ru (smtp4.yandex.ru [213.180.223.136]) by mx1.freebsd.org (Postfix) with ESMTP id 3AB0313C45A; Tue, 9 Oct 2007 03:56:05 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from ns.kirov.so-cdu.ru ([77.72.136.145]:39411 "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 S737770AbXJIDzx (ORCPT + 1 other); Tue, 9 Oct 2007 07:55:53 +0400 X-Comment: RFC 2476 MSA function at smtp4.yandex.ru logged sender identity as: bu7cher Message-ID: <470AFBC6.5050704@yandex.ru> Date: Tue, 09 Oct 2007 07:55:50 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: Stefan Esser References: <20071002164246.GA986@hades.panopticon> <20071003003329.GA78359@hades.panopticon> <4709FEB0.80004@FreeBSD.org> <470A1D53.40209@yandex.ru> <470A2B0C.2020502@FreeBSD.org> In-Reply-To: <470A2B0C.2020502@FreeBSD.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, TooMany Secrets Subject: Re: Need motherboard for home fileserver 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, 09 Oct 2007 03:56:07 -0000 Stefan Esser wrote: > No, the Abit AN-M2(HD) are based on nForce chip-sets (630a with > integrated 7025/7050 graphics), no patch is required for ata(4) > (since the SATA/IDE parts are mostly identical to the nF6150/430, > with the addition of AHCI support, which can be optionally enabled > in the BIOS). Ah, yes. Sorry, my mistake. http://www.uabit.com/index.php?option=com_content&task=view&id=32&Itemid=48&page=1&model=384 -- WBR, Andrey V. Elsukov From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 04:27: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 3BA9716A41B for ; Tue, 9 Oct 2007 04:27:00 +0000 (UTC) (envelope-from ari@ish.com.au) Received: from fish.ish.com.au (eth5921.nsw.adsl.internode.on.net [59.167.240.32]) by mx1.freebsd.org (Postfix) with ESMTP id 8415413C459 for ; Tue, 9 Oct 2007 04:26:59 +0000 (UTC) (envelope-from ari@ish.com.au) Received: from ip-182.ish.com.au ([203.29.62.182]) by fish.ish.com.au with esmtpa (Exim 4.43) id 1If6fM-0003WL-0A; Tue, 09 Oct 2007 14:25:56 +1000 Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-102-995934820" Message-Id: Content-Transfer-Encoding: 7bit From: Aristedes Maniatis Date: Tue, 9 Oct 2007 14:26:55 +1000 To: freebsd-current@freebsd.org X-Pgp-Agent: GPGMail 1.1.2 (Tiger) X-Mailer: Apple Mail (2.752.2) Subject: buildworld broken in tcsh 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, 09 Oct 2007 04:27:00 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-102-995934820 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Using Current csupped as of yesterday, buildworld fails. FreeBSD splash.ish.com.au 7.0-CURRENT-200708 FreeBSD 7.0- CURRENT-200708 #0: Fri Aug 17 07:47:18 UTC 2007 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 CPU: Dual Core AMD Opteron(tm) Processor 175 (2211.34-MHz 686-class CPU) I tried both i386 and cross-building to amd64 with similar results. I'm guessing this is some sort of GCC change between the last snapshot and today's current. I've looked on the wiki and the lists but can't find a FAQ about this. Thanks Ari Maniatis -------------------------------------------------------------- >>> 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 -j 8 -m /usr/src/share/mk" make -f Makefile.inc1 TARGET=i386 TARGET_ARCH=i386 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 In file included from /usr/src/bin/csh/config.h:235, from /usr/src/bin/csh/../../contrib/tcsh/sh.h:36, from /usr/src/bin/csh/../../contrib/tcsh/tc.const.c: 33: /usr/src/bin/csh/../../contrib/tcsh/config_f.h:63:1: warning: "NLS" redefined In file included from /usr/src/bin/csh/../../contrib/tcsh/sh.h:36, from /usr/src/bin/csh/../../contrib/tcsh/tc.const.c: 33: /usr/src/bin/csh/config.h:180:1: warning: this is the location of the previous definition In file included from /usr/src/bin/csh/../../contrib/tcsh/sh.h:366, from /usr/src/bin/csh/../../contrib/tcsh/tc.const.c: 33: /usr/include/varargs.h:34:2: error: #error " is obsolete with this version of GCC." /usr/include/varargs.h:35:2: error: #error "Change your code to use instead." In file included from /usr/src/bin/csh/config.h:235: /usr/src/bin/csh/../../contrib/tcsh/config_f.h:63:1: warning: "NLS" redefined /usr/src/bin/csh/config.h:180:1: warning: this is the location of the previous definition 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 In file included from /usr/src/bin/csh/config.h:235, from /usr/src/bin/csh/../../contrib/tcsh/sh.h:36, from /usr/src/bin/csh/../../contrib/tcsh/gethost.c:33: /usr/src/bin/csh/../../contrib/tcsh/config_f.h:63:1: warning: "NLS" redefined In file included from /usr/src/bin/csh/../../contrib/tcsh/sh.h:36, from /usr/src/bin/csh/../../contrib/tcsh/gethost.c:33: /usr/src/bin/csh/config.h:180:1: warning: this is the location of the previous definition In file included from /usr/src/bin/csh/../../contrib/tcsh/sh.h:366, from /usr/src/bin/csh/../../contrib/tcsh/gethost.c:33: /usr/include/varargs.h:34:2: error: #error " is obsolete with this version of GCC." /usr/include/varargs.h:35:2: error: #error "Change your code to use instead." In file included from /usr/src/bin/csh/../../contrib/tcsh/gethost.c:33: /usr/src/bin/csh/../../contrib/tcsh/sh.h:484: error: expected declaration specifiers or '...' before '*' token /usr/src/bin/csh/../../contrib/tcsh/sh.h:484: error: 'RETSIGTYPE' declared as function returning a function In file included from /usr/src/bin/csh/../../contrib/tcsh/gethost.c:33: /usr/src/bin/csh/../../contrib/tcsh/sh.h:750: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'parintr' /usr/src/bin/csh/../../contrib/tcsh/sh.h:751: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'parterm' In file included from /usr/src/bin/csh/../../contrib/tcsh/tc.h:42, from /usr/src/bin/csh/../../contrib/tcsh/sh.h:1252, from /usr/src/bin/csh/../../contrib/tcsh/gethost.c:33: /usr/src/bin/csh/../../contrib/tcsh/tc.decls.h:90: error: 'alrmcatch' declared as function returning a function In file included from /usr/src/bin/csh/../../contrib/tcsh/sh.h:1304, from /usr/src/bin/csh/../../contrib/tcsh/gethost.c:33: /usr/src/bin/csh/../../contrib/tcsh/sh.decls.h:45: error: 'pintr' declared as function returning a function /usr/src/bin/csh/../../contrib/tcsh/sh.decls.h:314: error: 'pchild' declared as function returning a function *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error --------------------------> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A --Apple-Mail-102-995934820 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iEYEARECAAYFAkcLAxAACgkQ72p9Lj5JECritgCePiVM4op1OvlmZMhXgYo2K8Rw gx0An0cvTbdh8NbuD+Fisn1YEsMUJnai =80+y -----END PGP SIGNATURE----- --Apple-Mail-102-995934820-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 06: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 61F5516A418 for ; Tue, 9 Oct 2007 06:20:35 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from spider.deepcore.dk (cpe.atm2-0-70484.0x50a6c9a6.abnxx16.customer.tele.dk [80.166.201.166]) by mx1.freebsd.org (Postfix) with ESMTP id 0231B13C459 for ; Tue, 9 Oct 2007 06:20:34 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from ws.deepcore.dk (ws.deepcore.dk [194.192.25.137]) by spider.deepcore.dk (8.13.8/8.13.8) with ESMTP id l996KXjh089976; Tue, 9 Oct 2007 08:20:34 +0200 (CEST) (envelope-from sos@deepcore.dk) Message-ID: <470B1DB1.1030700@deepcore.dk> Date: Tue, 09 Oct 2007 08:20:33 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Dave Frantz References: <48190.89022.qm@web53907.mail.re2.yahoo.com> In-Reply-To: <48190.89022.qm@web53907.mail.re2.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Cc: Kip Macy , freebsd-current@freebsd.org Subject: Re: FreeBSD 7.0-current Locks During Device Probe--Solved 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, 09 Oct 2007 06:20:35 -0000 Dave Frantz wrote: > I finally figured out what was causing FreeBSD 7.0-current to crash on = > my machine during the device probe. It turns out that if options=20 > CPUFREQ is compiled in, the system will not boot. However, it can be=20 > safely kldloaded in later. > > I'm not entirely sure why my system dislikes CPUFREQ, but I can live=20 > without it. If you guys have any questions or anything, just let me kno= w. Thanks for the report! I've had problems with cpufreq before, but that was when running gdm, it = would lock the system solid if loaded before gdm was started but worked=20 fine afterwards. -S=F8ren From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 07:45: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 070B216A538 for ; Tue, 9 Oct 2007 07:45:16 +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 98DB213C4AA for ; Tue, 9 Oct 2007 07:45:15 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 13207 invoked by uid 399); 9 Oct 2007 07:45:15 -0000 Received: from localhost (HELO slave.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 9 Oct 2007 07:45:15 -0000 X-Originating-IP: 127.0.0.1 Date: Tue, 9 Oct 2007 00:45:13 -0700 (PDT) From: Doug Barton To: freebsd-current@freebsd.org Message-ID: 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; format=flowed; charset=US-ASCII Cc: freebsd-rc@freebsd.org Subject: HEADS UP: Compatibility for (really) old rc variables removed 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, 09 Oct 2007 07:45:16 -0000 Please see below. The old variables affected are: portmap_* xntpd_* single_mountd_enable dhcp_program dhcp_flags If you have any of these in your /etc/rc.conf[.local] you should update them to their new equivalents. Doug ---------- Forwarded message ---------- From: Doug Barton To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Date: Tue, 9 Oct 2007 00:20:44 Subject: cvs commit: src/etc rc.subr dougb 2007-10-09 07:20:44 UTC FreeBSD src repository Modified files: etc rc.subr Log: Remove pre-rc.d compatibility shims that were added before the 5.0 branch for pre-5.0 variable names. Remove two dhcp compatibility variables added after the 5.1-RELEASE. Remove the now-unused support for these shims. Approved by: re (kensmith) Revision Changes Path 1.77 +0 -16 src/etc/rc.subr http://www.FreeBSD.org/cgi/cvsweb.cgi/src/etc/rc.subr.diff?&r1=1.76&r2=1.77&f=h From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 07:47: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 B98AB16A41A for ; Tue, 9 Oct 2007 07:47:54 +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 4CE6B13C459 for ; Tue, 9 Oct 2007 07:47:54 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 16002 invoked by uid 399); 9 Oct 2007 07:47:53 -0000 Received: from localhost (HELO slave.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 9 Oct 2007 07:47:53 -0000 X-Originating-IP: 127.0.0.1 Date: Tue, 9 Oct 2007 00:47:51 -0700 (PDT) From: Doug Barton To: freebsd-current@freebsd.org Message-ID: 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; format=flowed; charset=US-ASCII Cc: freebsd-rc@freebsd.org Subject: HEADS UP: Support for /etc/rc.early is now deprecated 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, 09 Oct 2007 07:47:54 -0000 Please see below. If you need help converting an rc.early script that you are currently using to the new rc.d style please see rc(8) first, and if you get stuck the folks on freebsd-rc@ will be glad to help. Regards, Doug ---------- Forwarded message ---------- From: Doug Barton To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Date: Tue, 9 Oct 2007 00:30:14 Subject: cvs commit: src/etc/rc.d early.sh dougb 2007-10-09 07:30:14 UTC FreeBSD src repository Modified files: etc/rc.d early.sh Log: Deprecate use of the early.sh script as advertised when the support for local rc.d scripts in the overall boot order was added. Proper rc.d scripts are run by rc.subr in a subshell, whereas scripts that end in .sh are sourced into rc's shell. The latter has potential to create serious boot problems, and there is no reason that the same functionality cannot be added by the user in the form of a proper rc.d script (as opposed to being added by the user in the form of /etc/rc.early). This script will be removed prior to the 8.0 branch. Approved by: re (kensmith) Revision Changes Path 1.3 +3 -0 src/etc/rc.d/early.sh http://www.FreeBSD.org/cgi/cvsweb.cgi/src/etc/rc.d/early.sh.diff?&r1=1.2&r2=1.3&f=h From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 08:18: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 04FC216A41A for ; Tue, 9 Oct 2007 08:18:52 +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 7448013C43E; Tue, 9 Oct 2007 08:18:50 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <470B396A.5030400@FreeBSD.org> Date: Tue, 09 Oct 2007 10:18:50 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= References: <48190.89022.qm@web53907.mail.re2.yahoo.com> <470B1DB1.1030700@deepcore.dk> In-Reply-To: <470B1DB1.1030700@deepcore.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: Dave Frantz , Kip Macy , freebsd-current@freebsd.org Subject: Re: FreeBSD 7.0-current Locks During Device Probe--Solved 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, 09 Oct 2007 08:18:52 -0000 Søren Schmidt wrote: > Dave Frantz wrote: >> I finally figured out what was causing FreeBSD 7.0-current to crash on >> my machine during the device probe. It turns out that if options >> CPUFREQ is compiled in, the system will not boot. However, it can be >> safely kldloaded in later. >> >> I'm not entirely sure why my system dislikes CPUFREQ, but I can live >> without it. If you guys have any questions or anything, just let me know. > Thanks for the report! > > I've had problems with cpufreq before, but that was when running gdm, it > would lock the system solid if loaded before gdm was started but worked > fine afterwards. The only problems I had were to do with acpi throttling in conjunction with cpufreq, which would hang my dual core opteron. Unfortunately I have forgotten the tunable to disable this but you should be able to google for it. Disabling acpi would also do it with a sledgehammer on i386. Kris From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 08:20: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 344DA16A420 for ; Tue, 9 Oct 2007 08:20:57 +0000 (UTC) (envelope-from ckadi35@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 C2B7313C478 for ; Tue, 9 Oct 2007 08:20:56 +0000 (UTC) (envelope-from ckadi35@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1183304nfb for ; Tue, 09 Oct 2007 01:20:55 -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; bh=fy+71Zgi533iNwdb5XUSeBCTBwLzCVqitYzmWKI4B+0=; b=GfXiKDQsKgcRezXLd5H1vLYyT4ncOyMv596Y+VDGLQMBT80hNb+FCCRC3I/kh8s3yDsEQdSQeSyzhiYwX8KeV4FIrp2Swb5hVz1uUQJrvUpZPlf3MJwByA3AyavCZfi1Yw29+35MlsxmP2piZilIm5+jeLFJmQuV5DvZ8XFdmQ8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=an+5WAFoD7BihHCj9ikTxNFoJfNJr4Gys8lJnXlWNQ663L9CDCGSmD6lE/DxMsPgiO9hJswbk6VfFCPLgdTQ+UkKXEqAgih/A+UCrE5Cgxk6bFRlIfAgw4DGSKpef5OQgXJUJ8qwsm3Gl3x/2Mo8swXwhHHxwWPfC88IrBQRaGk= Received: by 10.78.201.15 with SMTP id y15mr11480859huf.1191916611858; Tue, 09 Oct 2007 00:56:51 -0700 (PDT) Received: by 10.78.206.20 with HTTP; Tue, 9 Oct 2007 00:56:51 -0700 (PDT) Message-ID: Date: Tue, 9 Oct 2007 09:56:51 +0200 From: ck To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ipsec based rfc 4303 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, 09 Oct 2007 08:20:57 -0000 hi, i'm looking if there is an implementation of IPSec based on the rfc 4303. best regards ckd From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 08: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 2E5F816A419 for ; Tue, 9 Oct 2007 08:23:59 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.freebsd.org (Postfix) with ESMTP id DB61213C458 for ; Tue, 9 Oct 2007 08:23:58 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so3038594pyb for ; Tue, 09 Oct 2007 01:23: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:mime-version:content-type:content-transfer-encoding:content-disposition; bh=c/2fsyRSmtliUMCWemhEL+boOZ+k/jvd7Z1I4glxjpo=; b=eCU6pJbwLJAj/6FlVu+IR/HA6nKG0rH2VfsLtaIPhSQpRJuFQOCl1uLGuBIucsJGIALX4F9qLuMPobS3YD4BVjLZbuCOqz5FkNkxyhPdCrl59o3H4EWz8NQmzyx/L7ukSw3MXKKmhnW6oPl9FCTkb2apHty2KEv2I1jNJkm6zSk= 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=OLxB5gVsRtdVzNNzE37UE2M7L+uqkc+nEsnqbo6JWSCxJyPnYPnDWjGyfqiOwuHRxgCG+GPJEm3ILkZYHkMVQimO9wytkcv6FU87kULAb+qQaNxec2wFvn5JGa/Ajoi7CqWeqGED7dwOkHHUllgEyCqyCG+HF2X3OUMSZGU2wRo= Received: by 10.65.244.15 with SMTP id w15mr27206216qbr.1191918237098; Tue, 09 Oct 2007 01:23:57 -0700 (PDT) Received: by 10.65.105.2 with HTTP; Tue, 9 Oct 2007 01:23:57 -0700 (PDT) Message-ID: Date: Tue, 9 Oct 2007 08:23:57 +0000 From: "Aryeh Friedman" 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: latest ule patches 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, 09 Oct 2007 08:23:59 -0000 Are the ule/sched/4bsd patchs posted tonight any major improvement (such as the new min/max slice algorithm?) From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 08:26: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 D54CC16A41B for ; Tue, 9 Oct 2007 08:26:26 +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 04E2A13C45A; Tue, 9 Oct 2007 08:26:25 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <470B3B31.10307@FreeBSD.org> Date: Tue, 09 Oct 2007 10:26:25 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Randall Stewart References: <470AE33B.7000806@cisco.com> <470AE40D.7090006@cisco.com> In-Reply-To: <470AE40D.7090006@cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Michael Tuexen , freebsd-current@freebsd.org Subject: Re: AMD64 panic on boot 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, 09 Oct 2007 08:26:26 -0000 Randall Stewart wrote: > Randall Stewart wrote: >> Hi all: >> >> I just updated to the latest.. and I am seeing a crash on >> boot up of my 8-core Xeon machines (running in AMD mode). >> >> its a >> >> pagefault UA= 0x2b >> >> sysctl_handle_int+0x27 >> syscall+0x254 >> Xfast_syscall+0xab >> >> IP= 0xffffffff8048e7d7 >> >> >> I can't get a core unfortunately.. I get a core device >> unavailable.. >> >> I have one of the machines sitting in a DDB> prompt >> and its twin sitting on the old kernel.. >> >> Let me know how I can help.. and in the mean time I will poke >> around in kgdb on the running machine :-) >> >> R > Hmm.. it appears to be in.. > 0xffffffff8048e2e7 is in sysctl_handle_int > (../../../kern/kern_sysctl.c:816). > 811 */ > 812 if (arg1) > 813 tmpout = *(int *)arg1; > 814 else > 815 tmpout = arg2; > 816 error = SYSCTL_OUT(req, &tmpout, sizeof(int)); > 817 > 818 if (error || !req->newptr) > 819 return (error); > > > So its trying to copy out and faulting.. not sure what.. > > Let me know if there is some info I can poke out of DDB > > R > > I also saw a page fault from sysctl -a the other day...I thought it might be my fault (from my p4 branch, not cvs) but didnt investigate. Maybe it wasn't. Kris From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 08:29: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 5E3D816A41A for ; Tue, 9 Oct 2007 08:29:04 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by mx1.freebsd.org (Postfix) with ESMTP id 1C59D13C469 for ; Tue, 9 Oct 2007 08:29:03 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so3040867pyb for ; Tue, 09 Oct 2007 01:29:03 -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=J1/khZqnR+27PLNhxU6fU5iaBnzFAJrQgbKO3qPFJ4c=; b=GJt+pOetcW8t1e4TImTN2iDFNEwSNIUxg17UA+RHb973PYEP1m1yUR9MWRBku5nEDpbOy96MoMqNugNVLbUP+zyOWpS0jFZuE2wcrF12+eo7AqjEckvcTDbe/j/nxiQaU206MVuHqwsVaqtK1WQ74f5Akkg8R54/r61P5mc8KEg= 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=EPVK9254DCvxkIkuajYv+gnwF5oyg1tsk6Up0foYtbGuZIF4xQcr/akoPGbGMX06pto+cF2OUHEv42VBINO482lM1g2cDfCa2on5rzrwo9eKIJragx2gI2IBlqYgf1umAgEwlOU7HIst/5zf6ui+2ze6ufMMVf0PmqIKuePreoM= Received: by 10.65.240.17 with SMTP id s17mr9055494qbr.1191918543103; Tue, 09 Oct 2007 01:29:03 -0700 (PDT) Received: by 10.65.105.2 with HTTP; Tue, 9 Oct 2007 01:29:03 -0700 (PDT) Message-ID: Date: Tue, 9 Oct 2007 08:29:03 +0000 From: "Aryeh Friedman" To: "Remko Lodder" In-Reply-To: <20071009082707.GH1812@elvandar.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071009082707.GH1812@elvandar.org> Cc: freebsd-current@freebsd.org Subject: Re: latest ule patches 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, 09 Oct 2007 08:29:04 -0000 On 10/9/07, Remko Lodder wrote: > On Tue, Oct 09, 2007 at 08:23:57AM +0000, Aryeh Friedman wrote: > > Are the ule/sched/4bsd patchs posted tonight any major improvement > > (such as the new min/max slice algorithm?) > > test them? Since I currently hand apply the yield patch I don't want to mess anything up... From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 08:33: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 08B0716A417 for ; Tue, 9 Oct 2007 08:33:36 +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 C75CD13C457 for ; Tue, 9 Oct 2007 08:33:35 +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 l998WlFx008789 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Tue, 9 Oct 2007 04:32:48 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Tue, 9 Oct 2007 01:35:24 -0700 (PDT) From: Jeff Roberson X-X-Sender: jroberson@10.0.0.1 To: Aryeh Friedman In-Reply-To: Message-ID: <20071009013446.P912@10.0.0.1> References: <20071009082707.GH1812@elvandar.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Remko Lodder , freebsd-current@freebsd.org Subject: Re: latest ule patches 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, 09 Oct 2007 08:33:36 -0000 On Tue, 9 Oct 2007, Aryeh Friedman wrote: > On 10/9/07, Remko Lodder wrote: >> On Tue, Oct 09, 2007 at 08:23:57AM +0000, Aryeh Friedman wrote: >>> Are the ule/sched/4bsd patchs posted tonight any major improvement >>> (such as the new min/max slice algorithm?) >> >> test them? > > Since I currently hand apply the yield patch I don't want to mess anything up... These are the yield patches that I posted last week along with a couple of other minor fixes. Thanks, Jeff > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 08:40: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 17E2616A41A for ; Tue, 9 Oct 2007 08:40:34 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by mx1.freebsd.org (Postfix) with ESMTP id A340B13C45B for ; Tue, 9 Oct 2007 08:40:33 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so3046058pyb for ; Tue, 09 Oct 2007 01:40:33 -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=NcNma9p2eDzbxTUXF0wUUCIbOfkxPI8+FQGGlbBQBpo=; b=jHna8B5QC/wKKbzLMelvb8aB/dLSeCnOHJbu/V1PsvLsSrzgDUuj0cYuTEZdoMzIRD3xqToTf9uo73K9m18YvbvkWg0fknDtb0YdXRa2kU4cAbwuZu4iU0lLC8fH5FVeo/I26VAu2U13uPWm6lnlSQLBMZpGbIIhaRIxmSTeFl8= 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=tlVoS2EqaqQQh1Y8pkNFTCfnprnIs+KpxiWwKU/Smvwnj6sSoulN09cN2rh012Ye8kidBPsl7umrNk7vMH83cadRp1efnPZg8ZYi73h+VUjFEEMZ+vSHgSr88yXCFDxHZJTn5E876KXzEyEtZY44hOEjsA+4d2WmvXhEtkg18vw= Received: by 10.65.59.11 with SMTP id m11mr25171046qbk.1191919232315; Tue, 09 Oct 2007 01:40:32 -0700 (PDT) Received: by 10.65.105.2 with HTTP; Tue, 9 Oct 2007 01:40:32 -0700 (PDT) Message-ID: Date: Tue, 9 Oct 2007 08:40:32 +0000 From: "Aryeh Friedman" To: "Jeff Roberson" , freebsd-current@freebsd.org In-Reply-To: <20071009013446.P912@10.0.0.1> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071009082707.GH1812@elvandar.org> <20071009013446.P912@10.0.0.1> Cc: Subject: Re: latest ule patches 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, 09 Oct 2007 08:40:34 -0000 On 10/9/07, Jeff Roberson wrote: > On Tue, 9 Oct 2007, Aryeh Friedman wrote: > > > On 10/9/07, Remko Lodder wrote: > >> On Tue, Oct 09, 2007 at 08:23:57AM +0000, Aryeh Friedman wrote: > >>> Are the ule/sched/4bsd patchs posted tonight any major improvement > >>> (such as the new min/max slice algorithm?) > >> > >> test them? > > > > Since I currently hand apply the yield patch I don't want to mess anything up... > > These are the yield patches that I posted last week along with a couple of > other minor fixes. ok so one less patch to handle.... how long to dynamic min/max (thats what I call and from what astrodog told me it is roughly our idea with some bells and whistles) From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 08:57: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 ACF1F16A419 for ; Tue, 9 Oct 2007 08:57:04 +0000 (UTC) (envelope-from astrodog@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.186]) by mx1.freebsd.org (Postfix) with ESMTP id 875E913C468 for ; Tue, 9 Oct 2007 08:57:04 +0000 (UTC) (envelope-from astrodog@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so871201rvb for ; Tue, 09 Oct 2007 01:57:04 -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:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=FUeT+/IzPSAyOXH4svDtjXMTe6yvlh0m7eIE4pAjDG0=; b=g39QAHvhoAiJzC5sj+dM1bmeCDf+ByT4rTQcAumsnmBtsqb4Bhsbcyp5YOv1Kuepf816eeyf/89QkxCx7/XRwV9ZAuGxHjv2jBjAbKjJgrRvNDHLxgp153Of2ROuiWKE7Kx3AyP75FXISoH7bhg04rO3ryKD/Wp3b936C+Xlzkc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=J61YWpFPQ+UoWm1kQMjziI4977A84TWXG8ZjCOE+PWx0aW204oU3irYFZfZSeTET9LsXIqlcjlXVhB1xmOcjHZnXkn2EMPNhgFXys+EeP0FTpfxA3ICcFp5+OHlIHTWTlZZ2JMndPXbi/ygxkEZjZAaLqRK7QlGu7HQIsVFluUM= Received: by 10.141.50.17 with SMTP id c17mr1276702rvk.1191920224039; Tue, 09 Oct 2007 01:57:04 -0700 (PDT) Received: by 10.141.74.5 with HTTP; Tue, 9 Oct 2007 01:57:04 -0700 (PDT) Message-ID: <2fd864e0710090157vda68659y6864d4c824d65354@mail.gmail.com> Date: Tue, 9 Oct 2007 03:57:04 -0500 From: Astrodog In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071009082707.GH1812@elvandar.org> <20071009013446.P912@10.0.0.1> Cc: Jeff Roberson , freebsd-current@freebsd.org Subject: Re: latest ule patches 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, 09 Oct 2007 08:57:04 -0000 On 10/9/07, Aryeh Friedman wrote: > On 10/9/07, Jeff Roberson wrote: > > On Tue, 9 Oct 2007, Aryeh Friedman wrote: > > > > > On 10/9/07, Remko Lodder wrote: > > >> On Tue, Oct 09, 2007 at 08:23:57AM +0000, Aryeh Friedman wrote: > > >>> Are the ule/sched/4bsd patchs posted tonight any major improvement > > >>> (such as the new min/max slice algorithm?) > > >> > > >> test them? > > > > > > Since I currently hand apply the yield patch I don't want to mess anything up... > > > > These are the yield patches that I posted last week along with a couple of > > other minor fixes. > > ok so one less patch to handle.... how long to dynamic min/max (thats > what I call and from what astrodog told me it is roughly our idea with > some bells and whistles) > _______________________________________________ > 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" > Ehm. You must have completely misunderstood what I said off list. I discussed tunable/variable min/max slices with Jeff, based on the conversation we had. He came up with something better, after I explained where the variation is useful. Whatever "product" comes out of this, is the result of Jeff hearing a relatively bad idea, and set of circumstances, and replacing it with something that is appropriate for far more environments. I apologize if I did not make that clear. --- Harrison From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 09:25: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 EC1CF16A417 for ; Tue, 9 Oct 2007 09:25:08 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.freebsd.org (Postfix) with ESMTP id A915C13C43E for ; Tue, 9 Oct 2007 09:25:08 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so3065113pyb for ; Tue, 09 Oct 2007 02:25: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:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=KWTP4zc6sZdp3X1tPS4ndGA80u/1p5JKqfuelANnvsM=; b=LORuYvgoXiZl7QBoptExQih9SsGxkyXzWFWXg+7JWROQLvP9Ov6pIirgY3mwz01659xxWxaxZrPypggDQ5d11AbAX2xH0U30gIU+i7mVGEcs2rLe5CBjTqFBc81QGXwtLoUPXnLktZORateiFgjWFdHBuzdTiOpvGAFWajO/Fow= 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=MvI+wY5hQLKVv+xZ6XduDUb2eDOg6DYgiTYWVTnqbVFyQX9jxoSVbnUQWzwhjfdPJuLgOrBlQk59Yn5sbKuP25PnIyO6StiKPS3NhRJqkE7O3c9zmugaL/9+O/Yx72omcebZmoQmK3ecoZ2BY820iRGSvsKpozGHNCVz1Y3+9bs= Received: by 10.65.133.8 with SMTP id k8mr22765039qbn.1191921907355; Tue, 09 Oct 2007 02:25:07 -0700 (PDT) Received: by 10.65.105.2 with HTTP; Tue, 9 Oct 2007 02:25:07 -0700 (PDT) Message-ID: Date: Tue, 9 Oct 2007 09:25:07 +0000 From: "Aryeh Friedman" To: Astrodog , freebsd-current@freebsd.org In-Reply-To: <2fd864e0710090157vda68659y6864d4c824d65354@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071009082707.GH1812@elvandar.org> <20071009013446.P912@10.0.0.1> <2fd864e0710090157vda68659y6864d4c824d65354@mail.gmail.com> Cc: Subject: Re: latest ule patches 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, 09 Oct 2007 09:25:09 -0000 1. I tend to get a little confused on stuff as you might now from off list 2. I never meant to imply anything that was not publically known and/or orgin of ideas that where not mine as being mine On 10/9/07, Astrodog wrote: > On 10/9/07, Aryeh Friedman wrote: > > On 10/9/07, Jeff Roberson wrote: > > > On Tue, 9 Oct 2007, Aryeh Friedman wrote: > > > > > > > On 10/9/07, Remko Lodder wrote: > > > >> On Tue, Oct 09, 2007 at 08:23:57AM +0000, Aryeh Friedman wrote: > > > >>> Are the ule/sched/4bsd patchs posted tonight any major improvement > > > >>> (such as the new min/max slice algorithm?) > > > >> > > > >> test them? > > > > > > > > Since I currently hand apply the yield patch I don't want to mess anything up... > > > > > > These are the yield patches that I posted last week along with a couple of > > > other minor fixes. > > > > ok so one less patch to handle.... how long to dynamic min/max (thats > > what I call and from what astrodog told me it is roughly our idea with > > some bells and whistles) > > _______________________________________________ > > 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" > > > > Ehm. You must have completely misunderstood what I said off list. > > I discussed tunable/variable min/max slices with Jeff, based on the > conversation we had. He came up with something better, after I > explained where the variation is useful. > > Whatever "product" comes out of this, is the result of Jeff hearing a > relatively bad idea, and set of circumstances, and replacing it with > something that is appropriate for far more environments. > > I apologize if I did not make that clear. > > --- Harrison > _______________________________________________ > 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 Oct 9 09:26: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 88DDF16A417 for ; Tue, 9 Oct 2007 09:26:21 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from av7-2-sn3.vrr.skanova.net (av7-2-sn3.vrr.skanova.net [81.228.9.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1B80513C458 for ; Tue, 9 Oct 2007 09:26:21 +0000 (UTC) (envelope-from johan@stromnet.se) Received: by av7-2-sn3.vrr.skanova.net (Postfix, from userid 502) id EB6C738CDE; Tue, 9 Oct 2007 11:05:43 +0200 (CEST) Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net [81.228.9.102]) by av7-2-sn3.vrr.skanova.net (Postfix) with ESMTP id D0EB538B23 for ; Tue, 9 Oct 2007 11:05:43 +0200 (CEST) Received: from phomca.stromnet.se (90-224-172-102-no129.tbcn.telia.com [90.224.172.102]) by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 1020037E51 for ; Tue, 9 Oct 2007 11:06:49 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by phomca.stromnet.se (Postfix) with ESMTP id B5DA6BB06 for ; Tue, 9 Oct 2007 11:06:49 +0200 (CEST) X-Virus-Scanned: amavisd-new at stromnet.se Received: from phomca.stromnet.se ([127.0.0.1]) by localhost (phomca.stromnet.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w1kbMyWxwlA6 for ; Tue, 9 Oct 2007 11:06:44 +0200 (CEST) Received: from [IPv6:2001:16d8:ff20:1:217:f2ff:fef0:d6b7] (unknown [IPv6:2001:16d8:ff20:1:217:f2ff:fef0:d6b7]) by phomca.stromnet.se (Postfix) with ESMTP id 96BD1BB07 for ; Tue, 9 Oct 2007 11:06:44 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: quoted-printable Message-Id: <3B212846-8428-45A1-8B9E-7DF58423FB8C@stromnet.se> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed To: freebsd-current@freebsd.org From: =?ISO-8859-1?Q?Johan_Str=F6m?= Date: Tue, 9 Oct 2007 11:06:40 +0200 X-Mailer: Apple Mail (2.752.3) Subject: USB crash 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, 09 Oct 2007 09:26:21 -0000 Dunno if this is where it should go but just for the record. Updated my IPMI card firmware, and it have some virtual USB device =20 thingy (for mounting remote images etc). It detached at the beginning =20= of the upgrade procedure, but when the upgrade was done and the =20 device reattached, the box paniced: Fatal trap 12: page fault while in kernel mode cpuid =3D 0; apic id =3D 00 fault virtual address =3D 0x290 fault code =3D supervisod read data, page not present instruction pointer =3D 0x8:0xfffffffffff80401014 stack pointer: 0x10: 0xfffffffffb03e6da0 frame pointer: 0x10: 0xfffffffffb03e6de0 code segment =3D base 0x0, limit 0xffffff, type 0x1b =3D dpl 0, pres 1, long 1, def32 0, gran 1 processor eflgs =3D interrupt enabled, resume, IOPL=3D0 current process =3D 42 (usb4) [thread pid 42 tid 100046] Stopped at usb_transfer_complete+0x1d4: movq 0x290(%r14),%r11 db> where Tracing pid 42 tid 100046 td 0xffffff00058e46a0 usb_transfer_complete() at usb_transfer_complete+0x1d4 bus_dmamap_load() at bus_dmamap_load+0x330 usbd_transfer() at usbd_transfer+0xee usbd_do_request_flags_pipe() at usbd_do_request_flags_pipe+0x8f usbd_do_request_flags() at usbd_do_request_flags+0x25 usbd_get_string_desc() at usbd_get_string_desc+0x9b usbd_get_string() at usbd_get_string+0x83 uhub_child_pnpinfo_str() at uhub_child_pnpinfo_str+0xd9 devaddq() at devaddq+0xd5 device_attach() at device_attach+0x156 usbd_new_device() at usbd_new_device+0x828 uhub_explore() at uhub_explore+0x1bd usb_discover() at usb_discover+0x38 usb_event_thread() at usb_event_thread+0x8a fork_exit() at fork_exit+0x11f fork_trampoline() at fork_trampoline+0xe --- trap 0, rip =3D 0, rsp =3D 0xffffffffb03e7d30, rbp =3D 0 --- db> Dont realy know what might be usefull.. I'll keep the box in the =20 debugger for a few hours now if anyone can answer quick and tell me =20 what to do to help more :) FreeBSD-CURRENT from a few days back, GENERIC minus witness and =20 invariants, but with ULE scheduler. Box is a dual quadcore xeon. -- Johan Str=F6m Stromnet johan@stromnet.se http://www.stromnet.se/ From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 10:06: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 B200716A418 for ; Tue, 9 Oct 2007 10:06:46 +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 61B5B13C46A for ; Tue, 9 Oct 2007 10:06:46 +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 1IfBzB-000382-OU for current@freebsd.org; Tue, 09 Oct 2007 13:06:45 +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 1IfBzA-000Asd-Nm for current@freebsd.org; Tue, 09 Oct 2007 13:06:45 +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 l99A6ZEY069879; Tue, 9 Oct 2007 13:06:35 +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 l99A6ZIs069601; Tue, 9 Oct 2007 13:06:35 +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: Tue, 9 Oct 2007 13:06:35 +0300 From: Kostik Belousov To: Petr Holub Message-ID: <20071009100635.GX2180@deviant.kiev.zoral.com.ua> References: <20071008193406.GT2180@deviant.kiev.zoral.com.ua> <032a01c80a05$871b32c0$5317fb93@KLOBOUCEK> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6TME3aayZmn2Ikqb" Content-Disposition: inline In-Reply-To: <032a01c80a05$871b32c0$5317fb93@KLOBOUCEK> User-Agent: Mutt/1.4.2.3i X-Scanner-Signature: 669e5d776fa0e81a52da9f410dfff76f X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 1576 [Oct 09 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: current@freebsd.org Subject: Re: panic on boot 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, 09 Oct 2007 10:06:46 -0000 --6TME3aayZmn2Ikqb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 09, 2007 at 01:47:03AM +0200, Petr Holub wrote: > > The patch exists that modifies BTX to reflect interrupts and requests i= nto > > the real mode, see > > http://people.freebsd.org/~kib/realbtx/ > > http://people.freebsd.org/~kib/realbtx/realbtx.2.patch >=20 > After booting the machine with this patch, it works like a charm, > looks fairly stable, Myrinet 10GE card up and running. So I > wonder: would it be possible to include this realbtx into 7.0-RELEASE? > It seems rather important, as many machines are now being > installed off USB CD drives and USB keys... No, it is definitely not for 7.0. There were some reports that keyboard works quite jerky under the /boot/loader, and some keystrokes were missing. Another, possible related, report was the need to press some key to actually boot, since loader timer did not work. I had no time to look at these problems. Also, it seems that code shall be conditionalized, and either alternate boot2/loader provided, or compile option present to select between vm86 btx/real btx. This was not thought of too. --6TME3aayZmn2Ikqb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHC1KqC3+MBN1Mb4gRAreMAKDN0iGfjC3oOKaKWRXF0jH6IA4ROwCeLu2Y YcOHMylWereBzmV/iWymt0E= =U3TI -----END PGP SIGNATURE----- --6TME3aayZmn2Ikqb-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 11: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 5EF7216A419 for ; Tue, 9 Oct 2007 11:02:09 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by mx1.freebsd.org (Postfix) with ESMTP id 3E5D013C4AA for ; Tue, 9 Oct 2007 11:02:09 +0000 (UTC) (envelope-from rrs@cisco.com) X-IronPort-AV: E=Sophos;i="4.21,248,1188802800"; d="scan'208";a="233224125" Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 09 Oct 2007 04:02:09 -0700 Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l99B28K2020174; Tue, 9 Oct 2007 04:02:08 -0700 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l99B2B0W001863; Tue, 9 Oct 2007 11:02:11 GMT Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 9 Oct 2007 04:02:08 -0700 Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 9 Oct 2007 04:02:08 -0700 Message-ID: <470B5F7E.9040307@cisco.com> Date: Tue, 09 Oct 2007 07:01:18 -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 References: <470AE33B.7000806@cisco.com> <470AE40D.7090006@cisco.com> In-Reply-To: <470AE40D.7090006@cisco.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 09 Oct 2007 11:02:08.0177 (UTC) FILETIME=[D59A7A10:01C80A63] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1718; t=1191927729; x=1192791729; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rrs@cisco.com; z=From:=20Randall=20Stewart=20 |Subject:=20Re=3A=20AMD64=20panic=20on=20boot |Sender:=20; bh=hiw33sz5uq+qRjZJN3zeW911YeqNk5YEivSwDM4qaAI=; b=R/e2GCJJAXRr3Tqe4Ry8x7IcyYo/qoqX4OE0UN03EV92+8N3KPqjttlsH4Z6zH6o6u2UYHVZ loxEa5I1/yGo8olS96lh387WyVobo3vpoA/U36hc71BaEBevk9+4S9qDeTdoJlzJnvM6qTO9bL tDd/QyTdrVtXxTMovJf5oNKYg=; Authentication-Results: sj-dkim-1; header.From=rrs@cisco.com; dkim=pass (sig from cisco.com/sjdkim1004 verified; ); Cc: Michael Tuexen Subject: Re: AMD64 panic on boot 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, 09 Oct 2007 11:02:09 -0000 Ok... after a bit of poking around and recompiling.. and yet another sync to current.. its a no-op.. Turns out I had some modified files that I did not realize on my machine .. that were actually old .. not new.. So, with the proper update to current.. all is well both my 8 core AMD's are back up again (Michael, you should be able to access these now). R Randall Stewart wrote: > Randall Stewart wrote: > >> Hi all: >> >> I just updated to the latest.. and I am seeing a crash on >> boot up of my 8-core Xeon machines (running in AMD mode). >> >> its a >> >> pagefault UA= 0x2b >> >> sysctl_handle_int+0x27 >> syscall+0x254 >> Xfast_syscall+0xab >> >> IP= 0xffffffff8048e7d7 >> >> >> I can't get a core unfortunately.. I get a core device >> unavailable.. >> >> I have one of the machines sitting in a DDB> prompt >> and its twin sitting on the old kernel.. >> >> Let me know how I can help.. and in the mean time I will poke >> around in kgdb on the running machine :-) >> >> R > > Hmm.. it appears to be in.. > 0xffffffff8048e2e7 is in sysctl_handle_int > (../../../kern/kern_sysctl.c:816). > 811 */ > 812 if (arg1) > 813 tmpout = *(int *)arg1; > 814 else > 815 tmpout = arg2; > 816 error = SYSCTL_OUT(req, &tmpout, sizeof(int)); > 817 > 818 if (error || !req->newptr) > 819 return (error); > > > So its trying to copy out and faulting.. not sure what.. > > Let me know if there is some info I can poke out of DDB > > R > > -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 803-317-4952 (cell) From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 08:27: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 1DC7F16A421 for ; Tue, 9 Oct 2007 08:27: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 DC91213C46E for ; Tue, 9 Oct 2007 08:27:08 +0000 (UTC) (envelope-from remko@elvandar.org) Received: by guardian.elvandar.org (Postfix, from userid 1001) id CA0E17EDFAB; Tue, 9 Oct 2007 10:27:07 +0200 (CEST) Date: Tue, 9 Oct 2007 10:27:07 +0200 From: Remko Lodder To: Aryeh Friedman Message-ID: <20071009082707.GH1812@elvandar.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.15 (2007-04-06) X-Mailman-Approved-At: Tue, 09 Oct 2007 11:40:46 +0000 Cc: freebsd-current@freebsd.org Subject: Re: latest ule patches 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, 09 Oct 2007 08:27:09 -0000 On Tue, Oct 09, 2007 at 08:23:57AM +0000, Aryeh Friedman wrote: > Are the ule/sched/4bsd patchs posted tonight any major improvement > (such as the new min/max slice algorithm?) test them? -- Kind regards, Remko Lodder ** remko@elvandar.org FreeBSD ** remko@FreeBSD.org /* Quis custodiet ipsos custodes */ From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 09:44: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 ED9E316A469 for ; Tue, 9 Oct 2007 09:44:25 +0000 (UTC) (envelope-from remko@elvandar.org) Received: from galain.elvandar.org (redqueen.elvandar.org [217.148.169.55]) by mx1.freebsd.org (Postfix) with ESMTP id 9ABE113C45D for ; Tue, 9 Oct 2007 09:44:25 +0000 (UTC) (envelope-from remko@elvandar.org) Received: from localhost.we-dare.net ([127.0.0.1] helo=galain.elvandar.org) by galain.elvandar.org with esmtpa (Exim 4.67) (envelope-from ) id 1IfAUZ-0001S5-ST; Tue, 09 Oct 2007 10:31:03 +0200 Received: from 194.74.82.3 (SquirrelMail authenticated user remko) by galain.elvandar.org with HTTP; Tue, 9 Oct 2007 10:31:03 +0200 (CEST) Message-ID: <10044.194.74.82.3.1191918663.squirrel@galain.elvandar.org> Date: Tue, 9 Oct 2007 10:31:03 +0200 (CEST) From: "Remko Lodder" To: "Aryeh Friedman" User-Agent: SquirrelMail/1.4.11 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Mailman-Approved-At: Tue, 09 Oct 2007 11:40:46 +0000 Cc: freebsd-current@freebsd.org Subject: Re: latest ule patches X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: remko@elvandar.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2007 09:44:26 -0000 Well, you can always revert the situation ofcourse. IF you dont try, you dont know. On this short notice not a lot of people had tested this. On Tue, October 9, 2007 10:29 am, Aryeh Friedman wrote: > On 10/9/07, Remko Lodder wrote: >> On Tue, Oct 09, 2007 at 08:23:57AM +0000, Aryeh Friedman wrote: >> > Are the ule/sched/4bsd patchs posted tonight any major improvement >> > (such as the new min/max slice algorithm?) >> >> test them? > > Since I currently hand apply the yield patch I don't want to mess anything > up... > -- Kind regards, Remko Lodder ** remko@elvandar.org FreeBSD ** remko@FreeBSD.org /* Quis custodiet ipsos custodes */ From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 10:23: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 E391F16A41A for ; Tue, 9 Oct 2007 10:23:45 +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 5BB5313C469 for ; Tue, 9 Oct 2007 10:23:44 +0000 (UTC) (envelope-from hopet@ics.muni.cz) Received: from KLOBOUCEK (w54-145.fi.muni.cz [147.251.54.145]) (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 l99ANhLP032756 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Tue, 9 Oct 2007 12:23:43 +0200 From: "Petr Holub" To: Date: Tue, 9 Oct 2007 12:23:49 +0200 Message-ID: <034601c80a5e$7b3a6fd0$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.54.145 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, 09 Oct 2007 12:23:43 +0200 (CEST) X-Mailman-Approved-At: Tue, 09 Oct 2007 11:40:46 +0000 Cc: Subject: panic while inserting USB key 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, 09 Oct 2007 10:23:46 -0000 Hi, I'm consistently encountering kernel panic when inserting a USB key (yes, it's the same machine I had to use realbtx for): Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x290 fault code = supervisor read data, page not present instruction pointer = 0x8:0xffffffff804010a4 stack pointer = 0x10:0xffffffffac2dada0 frame pointer = 0x10:0xffffffffac2dade0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 37 (usb4) [thread pid 37 tid 100032 ] Stopped at usb_transfer_complete+0x1d4: movq 0x290(%r14),%r11 db> bt Tracing pid 37 tid 100032 td 0xffffff0001242000 usb_transfer_complete() at usb_transfer_complete+0x1d4 bus_dmamap_load() at bus_dmamap_load+0x330 usbd_transfer() at usbd_transfer+0xee usbd_do_request_flags_pipe() at usbd_do_request_flags_pipe+0x8f usbd_do_request_flags() at usbd_do_request_flags+0x25 usbd_get_string_desc() at usbd_get_string_desc+0x9b usbd_get_string() at usbd_get_string+0x83 usbd_devinfo_vp() at usbd_devinfo_vp+0x6f usbd_devinfo() at usbd_devinfo+0x46 usbd_new_device() at usbd_new_device+0x5b2 uhub_explore() at uhub_explore+0x1bd usb_discover() at usb_discover+0x38 usb_event_thread() at usb_event_thread+0x8a fork_exit() at fork_exit+0x11f fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffac2dbd30, rbp = 0 --- db> sh threads 100071 (0xffffff00037d7350) sched_switch() at sched_switch+0x1fe 100083 (0xffffff00037dd9f0) sched_switch() at sched_switch+0x1fe 100082 (0xffffff0003885000) sched_switch() at sched_switch+0x1fe 100096 (0xffffff0003b53000) sched_switch() at sched_switch+0x1fe 100063 (0xffffff00037dc350) sched_switch() at sched_switch+0x1fe 100065 (0xffffff00037da9f0) sched_switch() at sched_switch+0x1fe 100069 (0xffffff00037d79f0) sched_switch() at sched_switch+0x1fe 100058 (0xffffff00037a3350) sched_switch() at sched_switch+0x1fe 100067 (0xffffff00037da350) sched_switch() at sched_switch+0x1fe 100112 (0xffffff0003be9000) sched_switch() at sched_switch+0x1fe 100113 (0xffffff0003be89f0) sched_switch() at sched_switch+0x1fe 100056 (0xffffff00037a39f0) sched_switch() at sched_switch+0x1fe 100060 (0xffffff00037dd000) sched_switch() at sched_switch+0x1fe 100062 (0xffffff00037dc6a0) sched_switch() at sched_switch+0x1fe 100051 (0xffffff00036cd350) sched_switch() at sched_switch+0x1fe 100050 (0xffffff00036cd6a0) sched_switch() at sched_switch+0x1fe 100053 (0xffffff00036389f0) sched_switch() at sched_switch+0x1fe 100064 (0xffffff00037dc000) sched_switch() at sched_switch+0x1fe 100039 (0xffffff0003637000) sched_switch() at sched_switch+0x1fe 100040 (0xffffff00036359f0) sched_switch() at sched_switch+0x1fe 100041 (0xffffff00036356a0) sched_switch() at sched_switch+0x1fe 100042 (0xffffff0003635350) sched_switch() at sched_switch+0x1fe 100043 (0xffffff0003635000) sched_switch() at sched_switch+0x1fe 100044 (0xffffff00012439f0) sched_switch() at sched_switch+0x1fe 100045 (0xffffff00036d09f0) sched_switch() at sched_switch+0x1fe 100046 (0xffffff00036d06a0) sched_switch() at sched_switch+0x1fe 100047 (0xffffff00036d0350) cpustop_handler() at cpustop_handler+0x40 100048 (0xffffff00036d0000) sched_switch() at sched_switch+0x1fe 100030 (0xffffff00012426a0) fork_trampoline() at fork_trampoline 100031 (0xffffff0001242350) fork_trampoline() at fork_trampoline 100032 (0xffffff0001242000) usb_transfer_complete() at usb_transfer_complete+ 0x1d4 100033 (0xffffff000123b9f0) sched_switch() at sched_switch+0x1fe 100034 (0xffffff000123b6a0) fork_trampoline() at fork_trampoline 100035 (0xffffff0003638000) sched_switch() at sched_switch+0x1fe 100036 (0xffffff00036379f0) fork_trampoline() at fork_trampoline 100037 (0xffffff00036376a0) sched_switch() at sched_switch+0x1fe 100038 (0xffffff0003637350) sched_switch() at sched_switch+0x1fe 100022 (0xffffff0001239350) sched_switch() at sched_switch+0x1fe 100023 (0xffffff0001239000) sched_switch() at sched_switch+0x1fe 100024 (0xffffff00011129f0) sched_switch() at sched_switch+0x1fe 100025 (0xffffff00011126a0) sched_switch() at sched_switch+0x1fe 100026 (0xffffff00012436a0) sched_switch() at sched_switch+0x1fe 100027 (0xffffff0001243350) sched_switch() at sched_switch+0x1fe 100028 (0xffffff0001243000) fork_trampoline() at fork_trampoline 100029 (0xffffff00012429f0) sched_switch() at sched_switch+0x1fe 100015 (0xffffff0001111350) sched_switch() at sched_switch+0x1fe 100016 (0xffffff0001111000) sched_switch() at sched_switch+0x1fe 100017 (0xffffff00010ea9f0) sched_switch() at sched_switch+0x1fe 100018 (0xffffff000123b350) sched_switch() at sched_switch+0x1fe 100019 (0xffffff000123b000) sched_switch() at sched_switch+0x1fe 100020 (0xffffff00012399f0) fork_trampoline() at fork_trampoline 100021 (0xffffff00012396a0) sched_switch() at sched_switch+0x1fe 100009 (0xffffff00010e86a0) sched_switch() at sched_switch+0x1fe 100010 (0xffffff00010e8350) sched_switch() at sched_switch+0x1fe 100011 (0xffffff0001112350) sched_switch() at sched_switch+0x1fe 100012 (0xffffff0001112000) sched_switch() at sched_switch+0x1fe 100013 (0xffffff00011119f0) sched_switch() at sched_switch+0x1fe 100014 (0xffffff00011116a0) sched_switch() at sched_switch+0x1fe 100004 (0xffffff00010e5000) sched_switch() at sched_switch+0x1fe 100005 (0xffffff00010ea6a0) fork_trampoline() at fork_trampoline 100006 (0xffffff00010ea350) sched_switch() at sched_switch+0x1fe 100007 (0xffffff00010ea000) sched_switch() at sched_switch+0x1fe 100008 (0xffffff00010e89f0) cpustop_handler() at cpustop_handler+0x40 100000 (0xffffff00010e8000) sched_switch() at sched_switch+0x1fe 100001 (0xffffff00010e59f0) cpustop_handler() at cpustop_handler+0x40 100002 (0xffffff00010e56a0) sched_switch() at sched_switch+0x1fe 100003 (0xffffff00010e5350) sched_switch() at sched_switch+0x1fe 0 (0xffffffff80a2a1c0) sched_switch() at sched_switch+0x1fe If the post-mortem analysis using kgdb and dump doesn't lie due to some memory corruption or sth like that, it shoudl be: (kgdb) up 11 #11 0xffffffff804010a4 in usb_transfer_complete (xfer=0xffffff00036e4800) at /usr/src/sys/dev/usb/usbdi.c:947 947 STAILQ_REMOVE_HEAD(&pipe->queue, next); (kgdb) up #12 0xffffffff806f05c0 in bus_dmamap_load (dmat=0xffffff00036cad80, map=0xffffff0003f42100, buf=0xffffffffac2defe0, buflen=0, callback=0xffffffff80401180 , callback_arg=0xffffff00036e4800, flags=0) at /usr/src/sys/amd64/amd64/busdma_machdep.c:739 739 (*callback)(callback_arg, dmat->segments, nsegs + 1, 0); (kgdb) up #13 0xffffffff804017ae in usbd_transfer (xfer=0xffffff00036e4800) at /usr/src/sys/dev/usb/usbdi.c:312 312 err = bus_dmamap_load(tag, dmap->map, xfer->buffer, size , (kgdb) up #14 0xffffffff804019ff in usbd_do_request_flags_pipe (dev=0xffffff000389cc00, pipe=0xffffff00c5fe5300, req=0xffffffffac2def80, data=0xffffffffac2defe0, flags=Variable "flags" is not available. ) at /usr/src/sys/dev/usb/usbdi.c:1098 1098 err = usbd_sync_transfer(xfer); (kgdb) up #15 0xffffffff80401b35 in usbd_do_request_flags (dev=Variable "dev" is not avail able. ) at /usr/src/sys/dev/usb/usbdi.c:1068 1068 return (usbd_do_request_flags_pipe(dev, dev->default_pipe, req, Any clues? (Should I reenable INVARIANTS and WITNESS for this? I've disabled them in order to prepare for Myrinet 10GE card benchmarking.) Thanks, Petr PS: when doing background fsck after the crash, the machine becomes severly unresponsive and jerky :(. From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 13:27: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 CC23516A418 for ; Tue, 9 Oct 2007 13:27:20 +0000 (UTC) (envelope-from is@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.freebsd.org (Postfix) with ESMTP id 803B613C459 for ; Tue, 9 Oct 2007 13:27:20 +0000 (UTC) (envelope-from is@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id 41E0019152 for ; Tue, 9 Oct 2007 16:50:05 +0400 (MSD) Received: from localhost (is1.park.rambler.ru [81.19.64.121]) by relay0.rambler.ru (Postfix) with ESMTP id 06660DE31 for ; Tue, 9 Oct 2007 16:50:05 +0400 (MSD) Date: Tue, 9 Oct 2007 16:50:01 +0400 From: Igor Sysoev To: freebsd-current@freebsd.org Message-ID: <20071009125001.GC5758@rambler-co.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Subject: sendfile and page usage statistics 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, 09 Oct 2007 13:27:20 -0000 As I understand if sendfile() with hardware TX chsum or TSO are used, then CPU does not touch file pages at all. So pagedaemon never set PG_REFERENCED to vnode object pages while scanning them. Does VM set PG_REFERENCED by another way ? Otherwise, often used files that accessed by sendfile() only have small chances to be cached by VM. -- Igor Sysoev http://sysoev.ru/en/ From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 14:34: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 613C516A473 for ; Tue, 9 Oct 2007 14:34:36 +0000 (UTC) (envelope-from wvaughan@steelerubber.com) Received: from toaster.steelerubber.com (toaster.steelerubber.com [166.82.96.8]) by mx1.freebsd.org (Postfix) with ESMTP id 118A013C494 for ; Tue, 9 Oct 2007 14:34:35 +0000 (UTC) (envelope-from wvaughan@steelerubber.com) Received: (qmail 6974 invoked by uid 89); 9 Oct 2007 14:34:34 -0000 Received: from unknown (HELO ?166.82.96.28?) (166.82.96.28) by toaster.steelerubber.com with SMTP; 9 Oct 2007 14:34:34 -0000 Message-ID: <470B9114.6050501@steelerubber.com> Date: Tue, 09 Oct 2007 10:32:52 -0400 From: Walter Vaughan User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <031401c809d8$69c12270$5317fb93@KLOBOUCEK> In-Reply-To: <031401c809d8$69c12270$5317fb93@KLOBOUCEK> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: panic on boot 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, 09 Oct 2007 14:34:36 -0000 Petr Holub wrote: > Basically, it's a dual processor dual core (4 cores in total) > Intel Xeon 5160 @ 3GHz with 4GB RAM. I had evil problems with an 8 core system with only 4 Gig. Added 4 more and never a panic again. From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 14:40:56 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 3F25D16A419 for ; Tue, 9 Oct 2007 14:40:56 +0000 (UTC) (envelope-from iwasaki@jp.FreeBSD.org) Received: from locore.org (ns01.locore.org [218.45.21.227]) by mx1.freebsd.org (Postfix) with ESMTP id C7DB913C4A5 for ; Tue, 9 Oct 2007 14:40:55 +0000 (UTC) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (celeron.v4.locore.org [192.168.0.10]) by locore.org (8.13.8/8.13.8/iwasaki) with ESMTP/inet id l99ES1cZ002145; Tue, 9 Oct 2007 23:28:01 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Date: Tue, 09 Oct 2007 23:28:01 +0900 (JST) Message-Id: <20071009.232801.21360508.iwasaki@jp.FreeBSD.org> To: scottl@samsco.org From: Mitsuru IWASAKI X-Mailer: Mew version 3.3 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: current@freebsd.org, yatsu@hi-tech.ac.jp Subject: CFR: ciss(4) patches 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, 09 Oct 2007 14:40:56 -0000 Hi, Scott and current@. # I'm not sure who is the ciss(4) maintainer currently, but # it seems Scott made last few changes. I'm investigating `ciss0: ADAPTER HEARTBEAT FAILED' problem, and suspecting that it is caused by the some sort of power-failure(defect of processor power module, power management related bugs in controller firmware or something). Comparing the source code with Linux cciss driver, I've noticed that ciss(4) doesn't do polling by sending NOP-MESSAGES and handle the requests in completed-queue when HW error is detected. The patches at: http://people.freebsd.org/~iwasaki/ciss/ciss-failover.patch I'm not sure the patches can solve the problem, but the patches doesn't hurt anything. I'd like to try any possible solution one by one anyway. It is testing by Yatsu-san over a week on 6-R w/E200i, so far so good. # Oh yes, I don't have the machine w/ Smart Array around here ;) I'll commit the patches on coming weekend if no objections. My next target would be MPSAFE patches MFC to 6-STABLE. Any suggestions are appreciated. Thanks! From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 14:53: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 E862D16A417 for ; Tue, 9 Oct 2007 14:53:17 +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 8EC8813C448 for ; Tue, 9 Oct 2007 14:53:17 +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 l99ErAlS025943; Tue, 9 Oct 2007 08:53:11 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <470B95C1.9050005@samsco.org> Date: Tue, 09 Oct 2007 08:52:49 -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: Mitsuru IWASAKI References: <20071009.232801.21360508.iwasaki@jp.FreeBSD.org> In-Reply-To: <20071009.232801.21360508.iwasaki@jp.FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Tue, 09 Oct 2007 08:53:11 -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: current@freebsd.org, yatsu@hi-tech.ac.jp Subject: Re: CFR: ciss(4) patches 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, 09 Oct 2007 14:53:18 -0000 Mitsuru IWASAKI wrote: > Hi, Scott and current@. > # I'm not sure who is the ciss(4) maintainer currently, but > # it seems Scott made last few changes. > > I'm investigating `ciss0: ADAPTER HEARTBEAT FAILED' problem, and > suspecting that it is caused by the some sort of power-failure(defect > of processor power module, power management related bugs in controller > firmware or something). > > Comparing the source code with Linux cciss driver, I've noticed that > ciss(4) doesn't do polling by sending NOP-MESSAGES and handle the > requests in completed-queue when HW error is detected. > The patches at: > http://people.freebsd.org/~iwasaki/ciss/ciss-failover.patch > > I'm not sure the patches can solve the problem, but the patches > doesn't hurt anything. I'd like to try any possible solution one by > one anyway. > It is testing by Yatsu-san over a week on 6-R w/E200i, so far so good. > # Oh yes, I don't have the machine w/ Smart Array around here ;) > > I'll commit the patches on coming weekend if no objections. > > My next target would be MPSAFE patches MFC to 6-STABLE. > > Any suggestions are appreciated. > Thanks! Looks worthwhile. You should probably wait until after the code freeze to commit the patch to HEAD. I'll also put the patch into testing at Yahoo. Thanks, Scott From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 16:18: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 8EB5016A417 for ; Tue, 9 Oct 2007 16:18:34 +0000 (UTC) (envelope-from hoschi@etain.frida.mouhaha.de) Received: from etain.frida.mouhaha.de (etain.frida.mouhaha.de [85.236.48.54]) by mx1.freebsd.org (Postfix) with ESMTP id 35CA313C474 for ; Tue, 9 Oct 2007 16:18:34 +0000 (UTC) (envelope-from hoschi@etain.frida.mouhaha.de) Received: from localhost (etain.frida.mouhaha.de [85.236.48.54]) by etain.frida.mouhaha.de (Postfix) with ESMTP id DAAB94B2207 for ; Tue, 9 Oct 2007 17:57:32 +0200 (CEST) X-Virus-Scanned: amavisd-new at mouhaha.de Received: from etain.frida.mouhaha.de ([85.236.48.54]) by localhost (etain.frida.mouhaha.de [85.236.48.54]) (amavisd-new, port 10024) with ESMTP id uEQ6rln4zJgA for ; Tue, 9 Oct 2007 17:57:26 +0200 (CEST) Received: by etain.frida.mouhaha.de (Postfix, from userid 1001) id 78AD24B8CAE; Tue, 9 Oct 2007 17:57:26 +0200 (CEST) Date: Tue, 9 Oct 2007 17:57:26 +0200 From: Oliver Peter To: freebsd-current@freebsd.org Message-ID: <20071009155726.GB26846@nemesis.frida.mouhaha.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qlTNgmc+xy1dBmNv" Content-Disposition: inline X-Operating-System: FreeBSD 6.2-RELEASE-p8 i386 User-Agent: Mutt/1.5.16 (2007-06-09) Subject: em0: watchdog timeout 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, 09 Oct 2007 16:18:34 -0000 --qlTNgmc+xy1dBmNv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, Today I received some em0 watchdog timeouts on my fresh 7.0-CURRENT machine. At first I had only some short ssh hangs but now it seems my server is completely offline. I will not have local access to my computer until this night but I will ask in advance what I can do for you to debug and solve this problem. What information shall I provide? dmesg? Kernel configuration? Humppa Ollie --=20 Oliver PETER, eMail: hoschi@mouhaha.de, ICQ# 113969174 "Worker bees can leave. Even drones can fly away. The Queen is their slave." --qlTNgmc+xy1dBmNv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iEYEARECAAYFAkcLpOYACgkQ6LH/IUVtaI8MPgCeIOTSU0dsqV/YYdLZ7Ls5QXg4 DHAAn0j5clJYJ6TedyM2ubPAFz6Ys420 =7U+r -----END PGP SIGNATURE----- --qlTNgmc+xy1dBmNv-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 16:46: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 417DD16A41B for ; Tue, 9 Oct 2007 16:46:14 +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 D01BB13C457 for ; Tue, 9 Oct 2007 16:46:13 +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 DED2EEB31A3; Wed, 10 Oct 2007 00:46:12 +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 90pskiNDccN6; Wed, 10 Oct 2007 00:46:02 +0800 (CST) Received: from LI-Xins-MacBook.local (71.5.7.139.ptr.us.xo.net [71.5.7.139]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id 7BB62EB0E76; Wed, 10 Oct 2007 00:46:01 +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=A2hAaSwx3BWnDJgEKeZKr+fUjyppcGN6xe4ER3PllQAuB6pyEZFpM4RAmln3fbvV3 Uimi5IKr1hm/f4guVbqPQ== Message-ID: <470BB044.3020308@delphij.net> Date: Tue, 09 Oct 2007 09:45:56 -0700 From: LI Xin Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Oliver Peter References: <20071009155726.GB26846@nemesis.frida.mouhaha.de> In-Reply-To: <20071009155726.GB26846@nemesis.frida.mouhaha.de> 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="------------enigAB62B7F217DB5B82438CA1F9" Cc: freebsd-current@freebsd.org Subject: Re: em0: watchdog timeout 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: Tue, 09 Oct 2007 16:46:14 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigAB62B7F217DB5B82438CA1F9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Oliver Peter wrote: > Hi, >=20 > Today I received some em0 watchdog timeouts on my fresh 7.0-CURRENT > machine. At first I had only some short ssh hangs but now it seems my > server is completely offline. I will not have local access to my > computer until this night but I will ask in advance what I can do for > you to debug and solve this problem. >=20 > What information shall I provide? dmesg? Kernel configuration? I think the following information would be helpful: - pciconf -lv - /var/run/dmesg.boot Perhaps kernel configuration is not quite useful at the moment, though. Thanks for reporting the problem. Cheers, --=20 Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! --------------enigAB62B7F217DB5B82438CA1F9 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 iD8DBQFHC7BEOfuToMruuMARClrWAJwMlmWXTKzz/3FPhsCD4mfRtCAyJQCfRgq6 m5VKW58qZQpo70IyVlJ44cI= =tIPR -----END PGP SIGNATURE----- --------------enigAB62B7F217DB5B82438CA1F9-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 19:04: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 0C87C16A421 for ; Tue, 9 Oct 2007 19:04:57 +0000 (UTC) (envelope-from mv@rulez.sk) Received: from mail.rulez.sk (DaEmoN.RuLeZ.sK [84.16.32.226]) by mx1.freebsd.org (Postfix) with ESMTP id 6CE2D13C45B for ; Tue, 9 Oct 2007 19:04:56 +0000 (UTC) (envelope-from mv@rulez.sk) Received: from localhost (localhost [127.0.0.1]) by mail.rulez.sk (Postfix) with ESMTP id E04665C2D for ; Tue, 9 Oct 2007 20:47:46 +0200 (CEST) X-Virus-Scanned: by amavisd-new at mail.rulez.sk Received: by mail.rulez.sk (Postfix, from userid 1020) id 7ECE65C28; Tue, 9 Oct 2007 20:47:41 +0200 (CEST) Date: Tue, 9 Oct 2007 20:47:41 +0200 From: Milos Vyletel To: freebsd-current@freebsd.org Message-ID: <20071009184741.GA13249@rulez.sk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.2i Subject: panic: mutex sleepq chain not owned 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, 09 Oct 2007 19:04:57 -0000 Hi, after csuping today current (maybe even before, because my system hang with Xorg runnig quite often, but i thought because it was because buggy Xorg), i've seen this panic while working on console. Here are some info. FreeBSD 7.0-CURRENT amd64 CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (2402.42-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6fb Stepping = 11 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 4 usable memory = 4284162048 (4085 MB) avail memory = 4128329728 (3937 MB) panic: mutex sleepq chain not owned at /usr/src/sys/kern/subr_sleepqueue.c:619 cpuid = 2 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a panic() at panic+0x16d unlock_spin() at unlock_spin sleepq_resume_thread() at sleepq_resume_thread+0xa3 sleepq_broadcast() at sleepq_broadcast+0x81 txg_sync_thread() at txg_sync_thread+0x11e fork_exit() at fork_exit+0x128 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xfffffffffbe82d30, rbp = 0 --- KDB: enter: panic Physical memory: 4085 MB Dumping 1320 MB: 1305 1289 1273 1257 1241 1225 1209 1193 1177 1161 1145 1129 1113 1097 1081 1065 1049 1033 1017 1001 985 969 953 937 921 905 889 873 857 841 825 809 793 777 761 745 729 713 697 681 665 649 633 617 601 585 569 553 537 521 505 489 473 457 441 425 409 393 377 361 345 329 313 297 281 265 249 233 217 201 185 169 153 137 121 105 89 73 57 41 25 9 #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 0xffffffff80179afc in db_fncall (dummy1=Variable "dummy1" is not available. ) at /usr/src/sys/ddb/db_command.c:486 #2 0xffffffff80179ff0 in db_command_loop () at /usr/src/sys/ddb/db_command.c:401 #3 0xffffffff8017b90d in db_trap (type=Variable "type" is not available. ) at /usr/src/sys/ddb/db_main.c:222 #4 0xffffffff8024e33a in kdb_trap (type=3, code=0, tf=0xfffffffffbe82930) at /usr/src/sys/kern/subr_kdb.c:502 #5 0xffffffff8035e3d3 in trap (frame=0xfffffffffbe82930) at /usr/src/sys/amd64/amd64/trap.c:472 #6 0xffffffff803451ae in calltrap () at /usr/src/sys/amd64/amd64/exception.S:169 #7 0xffffffff8024e4e3 in kdb_enter (msg=0xffffffff80a20fe0 "") at cpufunc.h:63 #8 0xffffffff8022916a in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:547 #9 0xffffffff8021e91d in _mtx_assert (m=Variable "m" is not available. ) at /usr/src/sys/kern/kern_mutex.c:623 #10 0xffffffff802555a0 in sleepq_resume_thread (sq=0xffffff000364a4b0, td=0xffffff0004b2d9f0, pri=-1) at /usr/src/sys/kern/subr_sleepqueue.c:619 #11 0xffffffff80255c84 in sleepq_broadcast (wchan=0xffffff0006437cd0, flags=Variable "flags" is not available. ) at /usr/src/sys/kern/subr_sleepqueue.c:755 #12 0xffffffff8063f860 in ?? () #13 0xffffff000623cc00 in ?? () #14 0xffffff0006437d70 in ?? () #15 0xffffff0006437cd0 in ?? () #16 0xffffff0006437d60 in ?? () #17 0xffffff0006437d90 in ?? () #18 0xffffff0006437dc8 in ?? () #19 0xffffff0006437cd0 in ?? () #20 0x0000000000000000 in ?? () #21 0xffffff00061ece00 in ?? () #22 0x0000000000000000 in ?? () #23 0x0000000000000000 in ?? () #24 0x0000000000000000 in ?? () #25 0x0000000000000000 in ?? () #26 0x000000001ffa263f in ?? () #27 0x0000000000000000 in ?? () #28 0xffffff0006437c00 in ?? () #29 0xffffff0004b8f9f0 in ?? () #30 0xffffffff8063f742 in ?? () #31 0xffffff0004ba2000 in ?? () #32 0xfffffffffbe82c80 in ?? () #33 0xfffffffffbe82c70 in ?? () #34 0xffffffff8020e12b in fork_exit (callout=0xffffff0006437cc8, arg=0x0, frame=0xffffff0006437d80) at /usr/src/sys/kern/kern_fork.c:796 Previous frame identical to this frame (corrupt stack?) Hope this help to investigate what's wrong. I have kernel.debug and vmcore, so let me know if there is something else what might help. mv From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 19:27: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 62FE516A418; Tue, 9 Oct 2007 19:27:43 +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 1459013C44B; Tue, 9 Oct 2007 19:27:42 +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 9AE0F30E20; Tue, 9 Oct 2007 15:27:42 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 09 Oct 2007 15:27:42 -0400 X-Sasl-enc: zfUDSWbegn5Na/9yFsg6Mj5G7ulbSSGa03FhJ4Wq7PGk 1191958062 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 D5C505637; Tue, 9 Oct 2007 15:27:41 -0400 (EDT) Message-ID: <470BD649.9050505@freebsd.org> Date: Tue, 09 Oct 2007 12:28:09 -0700 From: Darren Reed User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> <86bqb97mym.fsf@ds4.des.no> <20071008133846.GP2327@garage.freebsd.pl> In-Reply-To: <20071008133846.GP2327@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, Dag-Erling Sm??rgrav , freebsd-current@FreeBSD.org Subject: Re: ZFS kmem_map too small. 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, 09 Oct 2007 19:27:43 -0000 Pawel Jakub Dawidek wrote: > ... > > For i386 one has to set, eg. 'options KVA_PAGES=512' to the kernel > config to be able to define kmem larger than ~700MB. I guess you're > running amd64, maybe there is similar requirement? > Given how much RAM PCs have these days, why isn't this a default for GENERIC? Or why isn't it at least a tunable rather than an option? Darren From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 19:31: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 819EB16A469; Tue, 9 Oct 2007 19:31:12 +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 D4EEF13C4B5; Tue, 9 Oct 2007 19:31:11 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id EF4BC45EE5; Tue, 9 Oct 2007 21:31:08 +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 26CB545E93; Tue, 9 Oct 2007 21:31:04 +0200 (CEST) Date: Tue, 9 Oct 2007 21:30:52 +0200 From: Pawel Jakub Dawidek To: Darren Reed Message-ID: <20071009193051.GA13519@garage.freebsd.pl> References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> <86bqb97mym.fsf@ds4.des.no> <20071008133846.GP2327@garage.freebsd.pl> <470BD649.9050505@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Qxx1br4bt0+wmkIi" Content-Disposition: inline In-Reply-To: <470BD649.9050505@freebsd.org> 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: freebsd-fs@FreeBSD.org, Dag-Erling Sm??rgrav , freebsd-current@FreeBSD.org Subject: Re: ZFS kmem_map too small. 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, 09 Oct 2007 19:31:12 -0000 --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 09, 2007 at 12:28:09PM -0700, Darren Reed wrote: > Pawel Jakub Dawidek wrote: > >... > > > >For i386 one has to set, eg. 'options KVA_PAGES=3D512' to the kernel > >config to be able to define kmem larger than ~700MB. I guess you're > >running amd64, maybe there is similar requirement? > > =20 >=20 > Given how much RAM PCs have these days, why isn't this a default for=20 > GENERIC? >=20 > Or why isn't it at least a tunable rather than an option? This may be a good reason - today's PCs have a lot of RAM and KVA_PAGES splits address space between userland and kernel - the more address space for the kernel, the less address space for the userland. KVA_PAGES=3D512 splits 4GB address space in half, so userland processes can address at most 2GB of memory. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHC9brForvXbEpPzQRAq24AKDQ+OUGZ9dwkEXYyuSvKmTG7m31ogCgws3O TnfpmvNtci4dBdOmDiKPbAQ= =xv+V -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 19:40: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 19C9D16A418; Tue, 9 Oct 2007 19:40: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 DF96513C48D; Tue, 9 Oct 2007 19:40:54 +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 80B5B321E4; Tue, 9 Oct 2007 15:40:54 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 09 Oct 2007 15:40:54 -0400 X-Sasl-enc: vkEOe1rImmQifY0I5ICdQWIvM18CYX1cZtL+e23qBSPq 1191958854 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 99A495639; Tue, 9 Oct 2007 15:40:53 -0400 (EDT) Message-ID: <470BD961.4000407@freebsd.org> Date: Tue, 09 Oct 2007 12:41:21 -0700 From: Darren Reed User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> In-Reply-To: <20071008121523.GM2327@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: ZFS kmem_map too small. 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, 09 Oct 2007 19:40:55 -0000 Pawel Jakub Dawidek wrote: > Here are some updates: > > I was able to reproduce the panic by rsyncing big files and trying > bonnie++ test suggested in this thread. > > Can you guys retry with this patch: > > http://people.freebsd.org/~pjd/patches/vm_kern.c.2.patch > So, I have a question... What happens if the "for (i = 0..)" is changed to "while(1)" and the "panic" is subsequently removed? It appears like the code changes the meaning of "WAIT" to "wait for 4 seconds" then panic if it won't work. Previously, "WAIT" was not waiting at all...whch could be described as a bug! If I recall correctly, ZFS caches writes and doe them in spurts and that those spurts are spaced out more than 4 seconds. (For the curious, do "zpool status" and observe the gap in time between write activity.) If you start a large amount of I/O, it is possible that all the KVA will be used up and ZFS will not get a chance to flush its buffers before the 4s timer here expires. Does that sound plausible? Would doubling the 8 to (say) 16 be beneficial here, to at least make the waiting span one ZFS flush out to disk? Darren From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 20:13: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 ED0C316A418 for ; Tue, 9 Oct 2007 20:13:30 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (conducive.net [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id B26FD13C474 for ; Tue, 9 Oct 2007 20:13:30 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:60857 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1IfLSL-0006ty-7J for freebsd-current@freebsd.org; Tue, 09 Oct 2007 20:13:29 +0000 Message-ID: <470BE0E8.5020705@conducive.net> Date: Tue, 09 Oct 2007 16:13:28 -0400 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> <470BD961.4000407@freebsd.org> In-Reply-To: <470BD961.4000407@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ZFS kmem_map too small. 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, 09 Oct 2007 20:13:31 -0000 Darren Reed wrote: > Pawel Jakub Dawidek wrote: >> Here are some updates: >> >> I was able to reproduce the panic by rsyncing big files and trying >> bonnie++ test suggested in this thread. >> >> Can you guys retry with this patch: >> >> http://people.freebsd.org/~pjd/patches/vm_kern.c.2.patch >> > > So, I have a question... > What happens if the "for (i = 0..)" is changed to "while(1)" and > the "panic" is subsequently removed? > > > It appears like the code changes the meaning of "WAIT" to "wait > for 4 seconds" then panic if it won't work. Previously, "WAIT" was > not waiting at all...whch could be described as a bug! > > If I recall correctly, ZFS caches writes and doe them in spurts and > that those spurts are spaced out more than 4 seconds. (For the > curious, do "zpool status" and observe the gap in time between > write activity.) > > If you start a large amount of I/O, it is possible that all the KVA will > be used up and ZFS will not get a chance to flush its buffers before > the 4s timer here expires. Does that sound plausible? > > Would doubling the 8 to (say) 16 be beneficial here, to at least make > the waiting span one ZFS flush out to disk? > > Darren "devil's Advocate" hat on here ... But 4 *seconds* is an entire ice-age in machine cycle terms, so.. A) I hope you are wrong about that part [1]... ;-) B) But if not... Would it not make [ equal | better | optional ] sense to look into shortening that time period? By a factor of ten comes to my mind. At least. Grant - that may mean a performance hit, hence I'd vote for 'optional' - but it should also greatly reduce, not only the likelihood of using up the alloted RAM, but of losing (quite as much of) the contents of those buffers if/as/when disaster strikes. - As it too often does, in one form or another. JM2CW Bill Hacker [1] 4 seconds 'regardless' makes more sense. i.e. flush 'em periodically just in case, even if no *known* alterations have been detected, ELSE more often depending on [ many factors ]. > > _______________________________________________ > 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 Oct 9 20:14: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 6864816A41A for ; Tue, 9 Oct 2007 20:14:44 +0000 (UTC) (envelope-from davidt@yadt.co.uk) Received: from outcold.yadt.co.uk (outcold.yadt.co.uk [81.187.204.178]) by mx1.freebsd.org (Postfix) with SMTP id DA61D13C45D for ; Tue, 9 Oct 2007 20:14:43 +0000 (UTC) (envelope-from davidt@yadt.co.uk) Received: from localhost (localhost [127.0.0.1]) by outcold.yadt.co.uk (Postfix) with ESMTP id 100DC5E7F0 for ; Tue, 9 Oct 2007 20:59:38 +0100 (BST) X-Virus-Scanned: amavisd-new at yadt.co.uk Received: from outcold.yadt.co.uk ([127.0.0.1]) by localhost (outcold.yadt.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oLRK+WyWdbOh for ; Tue, 9 Oct 2007 20:59:34 +0100 (BST) Received: by outcold.yadt.co.uk (Postfix, from userid 1001) id E2F725E7C6; Tue, 9 Oct 2007 20:59:34 +0100 (BST) Date: Tue, 9 Oct 2007 20:59:34 +0100 From: David Taylor To: freebsd-current@freebsd.org Message-ID: <20071009195934.GA13187@outcold.yadt.co.uk> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: Promise SATA controllers & FreeBSD-7 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, 09 Oct 2007 20:14:44 -0000 Well, its been almost 2 months since this was last mentioned (unless I missed something), and nothing appears to have moved since, well, the problem first appeared many months prior to that. So as the branch for -7 is (hopefully) approaching, I thought I'd see if anyone had any news or ideas on this rather irritating problem. Of course the main reason for my post is entirely selfish -- I'd like to experiment with ZFS, but system instability caused by even moderate disk usage is hardly conducive to worthwhile testing... I, too, am seeing the now infamous: adX: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=... messages after simple commands like (cd /usr/ports; make search key=bonnie) In my case, ad4 and ad6, connected to a Promise PDC20579 on-board SATA controller. This system has been essentially entirely stable whilst running 6-STABLE for the past several years. To me, this is a serious problem which will stop me from using FreeBSD-7. If there is any way to help diagnose this problem, I'm willing to give what assistance I can, but I'm not too sure where to begin... Alternatively, if anyone can recommend a cheap PCI SATA card which is known to work well with FreeBSD-7, I might just end up buying that... -- David Taylor From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 20:27: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 8AA5516A419 for ; Tue, 9 Oct 2007 20:27:02 +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 2888F13C44B for ; Tue, 9 Oct 2007 20:27:01 +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 l99KQsXt027883 for ; Tue, 9 Oct 2007 14:26:54 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <470BE3F8.6000807@samsco.org> Date: Tue, 09 Oct 2007 14:26:32 -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: freebsd-current@freebsd.org References: <20071009195934.GA13187@outcold.yadt.co.uk> In-Reply-To: <20071009195934.GA13187@outcold.yadt.co.uk> 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]); Tue, 09 Oct 2007 14:26:54 -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 Subject: Re: Promise SATA controllers & FreeBSD-7 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, 09 Oct 2007 20:27:02 -0000 David Taylor wrote: > Well, its been almost 2 months since this was last mentioned (unless I > missed something), and nothing appears to have moved since, well, the > problem first appeared many months prior to that. > > So as the branch for -7 is (hopefully) approaching, I thought I'd see if > anyone had any news or ideas on this rather irritating problem. Of course > the main reason for my post is entirely selfish -- I'd like to experiment > with ZFS, but system instability caused by even moderate disk usage is > hardly conducive to worthwhile testing... > > I, too, am seeing the now infamous: > > adX: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=... > > messages after simple commands like (cd /usr/ports; make search key=bonnie) > > In my case, ad4 and ad6, connected to a Promise PDC20579 on-board SATA > controller. I'm working on this problem, but on generic ATA controllers, not on Promise in particular. Not sure how different the Promise controllers are and whether what I fix will affect them. I'll let you know when I have something to test, though. > > This system has been essentially entirely stable whilst running 6-STABLE > for the past several years. > > To me, this is a serious problem which will stop me from using FreeBSD-7. > > If there is any way to help diagnose this problem, I'm willing to give > what assistance I can, but I'm not too sure where to begin... > > Alternatively, if anyone can recommend a cheap PCI SATA card which is > known to work well with FreeBSD-7, I might just end up buying that... > 3ware, Areca, Highpoint, Adaptec. All four companies are active in supporting FreeBSD. There are good offerings from LSI as well if you're willing to spend more money. Scott From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 21:01: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 E89EB16A41B; Tue, 9 Oct 2007 21:01:04 +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 379FC13C4DB; Tue, 9 Oct 2007 21:01:03 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 7497C45E90; Tue, 9 Oct 2007 23:01:02 +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 6612A45684; Tue, 9 Oct 2007 23:00:56 +0200 (CEST) Date: Tue, 9 Oct 2007 23:00:43 +0200 From: Pawel Jakub Dawidek To: Darren Reed Message-ID: <20071009210043.GC13519@garage.freebsd.pl> References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> <470BD961.4000407@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="eRtJSFbw+EEWtPj3" Content-Disposition: inline In-Reply-To: <470BD961.4000407@freebsd.org> 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: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: ZFS kmem_map too small. 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, 09 Oct 2007 21:01:05 -0000 --eRtJSFbw+EEWtPj3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 09, 2007 at 12:41:21PM -0700, Darren Reed wrote: > Pawel Jakub Dawidek wrote: > >Here are some updates: > > > >I was able to reproduce the panic by rsyncing big files and trying > >bonnie++ test suggested in this thread. > > > >Can you guys retry with this patch: > > > > http://people.freebsd.org/~pjd/patches/vm_kern.c.2.patch > > =20 >=20 > So, I have a question... > What happens if the "for (i =3D 0..)" is changed to "while(1)" and > the "panic" is subsequently removed? I think it should stay to give the user a hint what's going on instead of hanging there forever. > It appears like the code changes the meaning of "WAIT" to "wait > for 4 seconds" then panic if it won't work. Previously, "WAIT" was > not waiting at all...whch could be described as a bug! It's actually 7 seconds:) > If I recall correctly, ZFS caches writes and doe them in spurts and > that those spurts are spaced out more than 4 seconds. (For the > curious, do "zpool status" and observe the gap in time between > write activity.) >=20 > If you start a large amount of I/O, it is possible that all the KVA will > be used up and ZFS will not get a chance to flush its buffers before > the 4s timer here expires. Does that sound plausible? It depends if the problem we see is because of caching/delaying writes or just caching data for faster reads. If the latter, the cache can be just thrown away, so it's much faster than waiting for buffers to be flushed in former case. ZFS flushes buffers every 5 seconds by default or when there is too much data, so 7 seconds sounds reasonable. > Would doubling the 8 to (say) 16 be beneficial here, to at least make > the waiting span one ZFS flush out to disk? Note that this is visible by the user as almost complete system hang, I think. 16 would make it to wait for 30 seconds. I do agree that waiting even 30 seconds in some extremly rare situations is better than panicing, but I'd first see if 8 fixes the problem. In my testing kernel I added debug printf to see when 'i' is larger than 0 - every value larger than 0 means panic with the old kernel. I never observed 'i' larger than 1. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --eRtJSFbw+EEWtPj3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHC+v7ForvXbEpPzQRAiNlAKCcYhVYuqetJSW65l+JNEnnnVKB7ACdFRx5 xjaHLr4pLF4OEct/3Jzx/Wk= =3bSE -----END PGP SIGNATURE----- --eRtJSFbw+EEWtPj3-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 23:03: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 99C0116A475 for ; Tue, 9 Oct 2007 23:03:19 +0000 (UTC) (envelope-from jfvogel@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 1FAF513C4A3 for ; Tue, 9 Oct 2007 23:03:18 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so16085nfb for ; Tue, 09 Oct 2007 16: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; bh=kS25b+sCGfmYEBBX9u7+1DAM0KJnMz04ZLmcgZ9H2dE=; b=n963B/ILsCtk1/vSbrVC49bVGFuP96DyaksMYAeWrW2v/2Lt+XM3IamKXNmK8pzGTpvqxSqRSkHlPMjzFaGVGjnq4SMG9tKrdGeyGPkHLDwGp6M/0qMoAdgmgE8nJlQHcZwTj1R+bzTww14622qUBm3dQ+rBaPQZXqyVxbYVbeQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=Vz3vTaK/Z7osEmpJzQy9mznguNMg+UmpI2+SQvxUiYfTZ6oM0vg/RbWPoc50g8121q3OfmN1kBDWTsO31kSCTeZhu0fLPONEn35q0OPEk3umoxFOQcOdNRBVCYyXyR1wJKWjvSLA4ZI+/cu9oeXx/AmzTvKFtbYwkCk/T2AR9Kw= Received: by 10.86.89.4 with SMTP id m4mr12153fgb.1191970997660; Tue, 09 Oct 2007 16:03:17 -0700 (PDT) Received: by 10.86.100.19 with HTTP; Tue, 9 Oct 2007 16:03:17 -0700 (PDT) Message-ID: <2a41acea0710091603u7b87d6fdsdaaadf4cafbea2d9@mail.gmail.com> Date: Tue, 9 Oct 2007 16:03:17 -0700 From: "Jack Vogel" To: "Mike Tancsa" , "freebsd-net@freebsd.org" , "FreeBSD Current" MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_3294_26294460.1191970997630" Cc: Subject: Patch to add EEPROM dump 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, 09 Oct 2007 23:03:19 -0000 ------=_Part_3294_26294460.1191970997630 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Mike, This is a patch against my 6.6.6 driver that adds a new value to the debug sysctl, you would give the command 'sysctl dev.em.0.debug=2' and it will dump out the first 32 16-bit words of the prom. Mike, go to e1000.sourceforge.net/wiki and look under issues, you will find one talking about 82573, that will show you the word that gets patched, and you can look at your own with this patch. I was wondering what the general reaction to this is, it may be useful at some points in helping debug things. Comments? Jack ------=_Part_3294_26294460.1191970997630 Content-Type: application/octet-stream; name=eeprom-dump.patch Content-Transfer-Encoding: base64 X-Attachment-Id: f_f7l0m8f3 Content-Disposition: attachment; filename=eeprom-dump.patch LS0tIGlmX2VtLmMJRnJpIE9jdCAgNSAwOToyMzo1MCAyMDA3CisrKyAvdG1wL2lmX2VtLmVlcHJv bS5jCVR1ZSBPY3QgIDkgMTU6NTM6NDAgMjAwNwpAQCAtMjc5LDYgKzI3OSw3IEBACiAJCSAgICBz dHJ1Y3QgZW1fZG1hX2FsbG9jICosIGludCk7CiBzdGF0aWMgdm9pZAllbV9kbWFfZnJlZShzdHJ1 Y3QgYWRhcHRlciAqLCBzdHJ1Y3QgZW1fZG1hX2FsbG9jICopOwogc3RhdGljIHZvaWQJZW1fcHJp bnRfZGVidWdfaW5mbyhzdHJ1Y3QgYWRhcHRlciAqKTsKK3N0YXRpYyB2b2lkCWVtX3ByaW50X252 bV9pbmZvKHN0cnVjdCBhZGFwdGVyICopOwogc3RhdGljIGludCAJZW1faXNfdmFsaWRfZXRoZXJf YWRkcih1aW50OF90ICopOwogc3RhdGljIGludAllbV9zeXNjdGxfc3RhdHMoU1lTQ1RMX0hBTkRM RVJfQVJHUyk7CiBzdGF0aWMgaW50CWVtX3N5c2N0bF9kZWJ1Z19pbmZvKFNZU0NUTF9IQU5ETEVS X0FSR1MpOwpAQCAtNDQ3LDcgKzQ0OCw3IEBACiAJLyogU1lTQ1RMIHN0dWZmICovCiAJU1lTQ1RM X0FERF9QUk9DKGRldmljZV9nZXRfc3lzY3RsX2N0eChkZXYpLAogCSAgICBTWVNDVExfQ0hJTERS RU4oZGV2aWNlX2dldF9zeXNjdGxfdHJlZShkZXYpKSwKLQkgICAgT0lEX0FVVE8sICJkZWJ1Z19p bmZvIiwgQ1RMVFlQRV9JTlR8Q1RMRkxBR19SVywgYWRhcHRlciwgMCwKKwkgICAgT0lEX0FVVE8s ICJkZWJ1ZyIsIENUTFRZUEVfSU5UfENUTEZMQUdfUlcsIGFkYXB0ZXIsIDAsCiAJICAgIGVtX3N5 c2N0bF9kZWJ1Z19pbmZvLCAiSSIsICJEZWJ1ZyBJbmZvcm1hdGlvbiIpOwogCiAJU1lTQ1RMX0FE RF9QUk9DKGRldmljZV9nZXRfc3lzY3RsX2N0eChkZXYpLApAQCAtNTA5OSw2ICs1MTAwLDMzIEBA CiAJICAgIChsb25nIGxvbmcpYWRhcHRlci0+c3RhdHMudHNjdGZjKTsKIH0KIAorLyoqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioKKyAqCisgKiAgVGhpcyByb3V0aW5lIHByb3ZpZGVzIGEgd2F5IHRvIGR1bXAgb3V0IHRo ZSBhZGFwdGVyIGVlcHJvbSwKKyAqICBvZnRlbiBhIHVzZWZ1bCBkZWJ1Zy9zZXJ2aWNlIHRvb2wu IFRoaXMgb25seSBkdW1wcyB0aGUgZmlyc3QKKyAqICAzMiB3b3Jkcywgc3R1ZmYgdGhhdCBtYXR0 ZXJzIGlzIGluIHRoYXQgZXh0ZW50LgorICoKKyAqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqLworc3RhdGljIHZvaWQK K2VtX3ByaW50X252bV9pbmZvKHN0cnVjdCBhZGFwdGVyICphZGFwdGVyKQoreworCXUxNgllZXBy b21fZGF0YTsKKwlpbnQJaSwgaiwgcm93ID0gMDsKKworCS8qIEl0cyBhIGJpdCBjcnVkZSwgYnV0 IGl0IGdldHMgdGhlIGpvYiBkb25lICovCisJcHJpbnRmKCJcbkludGVyZmFjZSBFRVBST00gRHVt cDpcbiIpOworCXByaW50ZigiT2Zmc2V0XG4weDAwMDAgICIpOworCWZvciAoaSA9IDAsIGogPSAw OyBpIDwgMzI7IGkrKywgaisrKSB7CisJCWlmIChqID09IDgpIHsgLyogTWFrZSB0aGUgb2Zmc2V0 IGJsb2NrICovCisJCQlqID0gMDsgKytyb3c7CisJCQlwcmludGYoIlxuMHgwMCV4MCAgIixyb3cp OworCQl9CisJCWUxMDAwX3JlYWRfbnZtKCZhZGFwdGVyLT5odywgaSwgMSwgJmVlcHJvbV9kYXRh KTsKKwkJcHJpbnRmKCIlMDR4ICIsIGVlcHJvbV9kYXRhKTsKKwl9CisJcHJpbnRmKCJcbiIpOwor fQorCiBzdGF0aWMgaW50CiBlbV9zeXNjdGxfZGVidWdfaW5mbyhTWVNDVExfSEFORExFUl9BUkdT KQogewpAQCAtNTExNSw2ICs1MTQzLDE1IEBACiAJaWYgKHJlc3VsdCA9PSAxKSB7CiAJCWFkYXB0 ZXIgPSAoc3RydWN0IGFkYXB0ZXIgKilhcmcxOwogCQllbV9wcmludF9kZWJ1Z19pbmZvKGFkYXB0 ZXIpOworCX0KKwkvKgorCSAqIFRoaXMgdmFsdWUgd2lsbCBjYXVzZSBhIGhleCBkdW1wIG9mIHRo ZQorCSAqIGZpcnN0IDMyIDE2LWJpdCB3b3JkcyBvZiB0aGUgRUVQUk9NIHRvCisJICogdGhlIHNj cmVlbi4KKwkgKi8KKwlpZiAocmVzdWx0ID09IDIpIHsKKwkJYWRhcHRlciA9IChzdHJ1Y3QgYWRh cHRlciAqKWFyZzE7CisJCWVtX3ByaW50X252bV9pbmZvKGFkYXB0ZXIpOwogCX0KIAogCXJldHVy biAoZXJyb3IpOwo= ------=_Part_3294_26294460.1191970997630-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 05: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 A192B16A419 for ; Wed, 10 Oct 2007 05:15:47 +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 778E013C44B for ; Wed, 10 Oct 2007 05:15:47 +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 1IfTv7-0000go-9k for ; Wed, 10 Oct 2007 14:15:45 +0900 Message-ID: <470C6000.60902@fusiongol.com> Date: Wed, 10 Oct 2007 14:15:44 +0900 From: Nathan Butcher User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20071009120010.833FE16A4D2@hub.freebsd.org> In-Reply-To: <20071009120010.833FE16A4D2@hub.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: IDE compact flash reader FAILURE message 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, 10 Oct 2007 05:15:47 -0000 This is not a big issue in CURRENT, or is even much of a priority I feel, but I thought I'd ask about it anyway. I have a compact flash reader inserted into the IDE port on my motherboard. It can host two compact flash cards. Currently I have an 8GB 133x compact flash and an 8GB 266x compact flash (both Transcend) in the slots. What I find interesting is that the 8GB 266x compact flash appears in dmesg as such:- ad5: FAILURE - SET_MULTI status=51 error=4 ad5: 7775MB at ata2-slave UDMA66 It seems like I can write to it anyway, but I haven't tried yet. What's the reason for the FAILURE? I assume it has something to do with the faster write speed on the card. From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 05:57: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 A313F16A419 for ; Wed, 10 Oct 2007 05:57:54 +0000 (UTC) (envelope-from is@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.freebsd.org (Postfix) with ESMTP id 6184813C458 for ; Wed, 10 Oct 2007 05:57:54 +0000 (UTC) (envelope-from is@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id E9F089B5A for ; Wed, 10 Oct 2007 09:57:52 +0400 (MSD) Received: from localhost (is1.park.rambler.ru [81.19.64.121]) by relay0.rambler.ru (Postfix) with ESMTP id B0E3E9A85 for ; Wed, 10 Oct 2007 09:57:52 +0400 (MSD) Date: Wed, 10 Oct 2007 09:57:48 +0400 From: Igor Sysoev To: freebsd-current@freebsd.org Message-ID: <20071010055748.GA18931@rambler-co.ru> References: <20071009125001.GC5758@rambler-co.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20071009125001.GC5758@rambler-co.ru> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Subject: Re: sendfile and page usage statistics 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, 10 Oct 2007 05:57:54 -0000 On Tue, Oct 09, 2007 at 04:50:01PM +0400, Igor Sysoev wrote: > As I understand if sendfile() with hardware TX chsum or TSO are used, > then CPU does not touch file pages at all. So pagedaemon never set > PG_REFERENCED to vnode object pages while scanning them. > Does VM set PG_REFERENCED by another way ? Otherwise, often used files > that accessed by sendfile() only have small chances to be cached by VM. I have looked kern_sendfile() in CURRENT and it seems to me that PG_REFERENCED is never set when sendfile() gets cached vm_page. I have looked the code path: vm_page_grab() vm_page_lookup() vm_page_wire() sf_buf_alloc() on i386 and amd64 and have not seen PG_REFERENCED. -- Igor Sysoev http://sysoev.ru/en/ From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 06:06: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 829A816A41B for ; Wed, 10 Oct 2007 06:06:12 +0000 (UTC) (envelope-from is@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.freebsd.org (Postfix) with ESMTP id 4026913C48A for ; Wed, 10 Oct 2007 06:06:12 +0000 (UTC) (envelope-from is@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id 3FB4C31BA4 for ; Wed, 10 Oct 2007 10:06:10 +0400 (MSD) Received: from localhost (is1.park.rambler.ru [81.19.64.121]) by relay0.rambler.ru (Postfix) with ESMTP id EBA78318B4 for ; Wed, 10 Oct 2007 10:06:09 +0400 (MSD) Date: Wed, 10 Oct 2007 10:06:06 +0400 From: Igor Sysoev To: freebsd-current@freebsd.org Message-ID: <20071010060605.GB18931@rambler-co.ru> References: <20071009125001.GC5758@rambler-co.ru> <20071010055748.GA18931@rambler-co.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20071010055748.GA18931@rambler-co.ru> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Subject: Re: sendfile and page usage statistics 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, 10 Oct 2007 06:06:12 -0000 On Wed, Oct 10, 2007 at 09:57:48AM +0400, Igor Sysoev wrote: > On Tue, Oct 09, 2007 at 04:50:01PM +0400, Igor Sysoev wrote: > > > As I understand if sendfile() with hardware TX chsum or TSO are used, > > then CPU does not touch file pages at all. So pagedaemon never set > > PG_REFERENCED to vnode object pages while scanning them. > > Does VM set PG_REFERENCED by another way ? Otherwise, often used files > > that accessed by sendfile() only have small chances to be cached by VM. > > I have looked kern_sendfile() in CURRENT and it seems to me that > PG_REFERENCED is never set when sendfile() gets cached vm_page. > I have looked the code path: > > vm_page_grab() > vm_page_lookup() > vm_page_wire() > sf_buf_alloc() on i386 and amd64 > > and have not seen PG_REFERENCED. As I understand the following patch against uipc_syscalls.c should fix the bug to some extent: if (pg->valid && vm_page_is_valid(pg, pgoff, xfsize)) + vm_page_flag_set(pg, PG_REFERENCED); VM_OBJECT_UNLOCK(obj); else if (m != NULL) -- Igor Sysoev http://sysoev.ru/en/ From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 06:25: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 4EC3C16A417 for ; Wed, 10 Oct 2007 06:25:49 +0000 (UTC) (envelope-from is@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.freebsd.org (Postfix) with ESMTP id 0DD2113C49D for ; Wed, 10 Oct 2007 06:25:47 +0000 (UTC) (envelope-from is@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id BBEF110D53; Wed, 10 Oct 2007 10:25:45 +0400 (MSD) Received: from localhost (is1.park.rambler.ru [81.19.64.121]) by relay0.rambler.ru (Postfix) with ESMTP id 3D5F4108DF; Wed, 10 Oct 2007 10:25:45 +0400 (MSD) Date: Wed, 10 Oct 2007 10:25:41 +0400 From: Igor Sysoev To: Antony Mawer Message-ID: <20071010062541.GA23840@rambler-co.ru> References: <20071009125001.GC5758@rambler-co.ru> <20071010055748.GA18931@rambler-co.ru> <20071010060605.GB18931@rambler-co.ru> <470C6DD4.1060509@mawer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <470C6DD4.1060509@mawer.org> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: freebsd-current@freebsd.org Subject: Re: sendfile and page usage statistics 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, 10 Oct 2007 06:25:49 -0000 On Wed, Oct 10, 2007 at 04:14:44PM +1000, Antony Mawer wrote: > On 10/10/2007 4:06 PM, Igor Sysoev wrote: > >On Wed, Oct 10, 2007 at 09:57:48AM +0400, Igor Sysoev wrote: > > > >>On Tue, Oct 09, 2007 at 04:50:01PM +0400, Igor Sysoev wrote: > >> > >>>As I understand if sendfile() with hardware TX chsum or TSO are used, > >>>then CPU does not touch file pages at all. So pagedaemon never set > >>>PG_REFERENCED to vnode object pages while scanning them. > >>>Does VM set PG_REFERENCED by another way ? Otherwise, often used files > >>>that accessed by sendfile() only have small chances to be cached by VM. > >>I have looked kern_sendfile() in CURRENT and it seems to me that > >>PG_REFERENCED is never set when sendfile() gets cached vm_page. > >>I have looked the code path: > >> > >>vm_page_grab() > >> vm_page_lookup() > >> vm_page_wire() > >>sf_buf_alloc() on i386 and amd64 > >> > >>and have not seen PG_REFERENCED. > > > >As I understand the following patch against uipc_syscalls.c > >should fix the bug to some extent: > > > > if (pg->valid && vm_page_is_valid(pg, pgoff, > > xfsize)) > >+ vm_page_flag_set(pg, PG_REFERENCED); > > VM_OBJECT_UNLOCK(obj); > > else if (m != NULL) > > You are missing opening/closing braces on your if() statement with this > change... Oh, thank you! You have saved me from coredump. This is why in my coding style I always use braces for single statement inside if(). -- Igor Sysoev http://sysoev.ru/en/ From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 06:45: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 21DA016A419 for ; Wed, 10 Oct 2007 06:45:40 +0000 (UTC) (envelope-from fbsd-current@mawer.org) Received: from outbound.icp-qv1-irony-out1.iinet.net.au (outbound.icp-qv1-irony-out1.iinet.net.au [203.59.1.108]) by mx1.freebsd.org (Postfix) with ESMTP id 9BBBE13C447 for ; Wed, 10 Oct 2007 06:45:39 +0000 (UTC) (envelope-from fbsd-current@mawer.org) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAADoLDEfLzq3r/2dsb2JhbAAM X-IronPort-AV: E=Sophos;i="4.21,252,1188748800"; d="scan'208";a="212953357" Received: from unknown (HELO [10.24.1.1]) ([203.206.173.235]) by outbound.icp-qv1-irony-out1.iinet.net.au with ESMTP; 10 Oct 2007 14:16:04 +0800 Message-ID: <470C6DD4.1060509@mawer.org> Date: Wed, 10 Oct 2007 16:14:44 +1000 From: Antony Mawer User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Igor Sysoev References: <20071009125001.GC5758@rambler-co.ru> <20071010055748.GA18931@rambler-co.ru> <20071010060605.GB18931@rambler-co.ru> In-Reply-To: <20071010060605.GB18931@rambler-co.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: sendfile and page usage statistics 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, 10 Oct 2007 06:45:40 -0000 On 10/10/2007 4:06 PM, Igor Sysoev wrote: > On Wed, Oct 10, 2007 at 09:57:48AM +0400, Igor Sysoev wrote: > >> On Tue, Oct 09, 2007 at 04:50:01PM +0400, Igor Sysoev wrote: >> >>> As I understand if sendfile() with hardware TX chsum or TSO are used, >>> then CPU does not touch file pages at all. So pagedaemon never set >>> PG_REFERENCED to vnode object pages while scanning them. >>> Does VM set PG_REFERENCED by another way ? Otherwise, often used files >>> that accessed by sendfile() only have small chances to be cached by VM. >> I have looked kern_sendfile() in CURRENT and it seems to me that >> PG_REFERENCED is never set when sendfile() gets cached vm_page. >> I have looked the code path: >> >> vm_page_grab() >> vm_page_lookup() >> vm_page_wire() >> sf_buf_alloc() on i386 and amd64 >> >> and have not seen PG_REFERENCED. > > As I understand the following patch against uipc_syscalls.c > should fix the bug to some extent: > > if (pg->valid && vm_page_is_valid(pg, pgoff, xfsize)) > + vm_page_flag_set(pg, PG_REFERENCED); > VM_OBJECT_UNLOCK(obj); > else if (m != NULL) You are missing opening/closing braces on your if() statement with this change... --Antony From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 07:45: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 782E416A421; Wed, 10 Oct 2007 07:45:09 +0000 (UTC) (envelope-from bushman@freebsd.org) Received: from mail.r61.net (mail.r61.net [195.208.245.249]) by mx1.freebsd.org (Postfix) with ESMTP id 6E0D913C457; Wed, 10 Oct 2007 07:45:06 +0000 (UTC) (envelope-from bushman@freebsd.org) Received: from [127.0.0.1] (shogun.cc.rsu.ru [195.208.252.84]) (authenticated bits=0) by mail.r61.net (8.14.1/8.14.1) with ESMTP id l9A76KTa008770; Wed, 10 Oct 2007 11:06:25 +0400 (MSD) (envelope-from bushman@freebsd.org) Message-ID: <470C79C3.4010603@freebsd.org> Date: Wed, 10 Oct 2007 11:05:39 +0400 From: Michael Bushkov User-Agent: Thunderbird 2.0.0.5 (Windows/20070716) MIME-Version: 1.0 To: "Timur I. Bakeyev" References: <20070716190258.GA25030@hansmi.ch> <20071008140113.GG98428@com.bat.ru> In-Reply-To: <20071008140113.GG98428@com.bat.ru> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit Cc: tobias.mueller@hostpoint.ch, Michael Hanselmann , elias.wittwer@hostpoint.ch, freebsd-current@freebsd.org, m.kooijman@student.utwente.nl Subject: Re: [PATCH] Implement getgroupmembership(3) for massive performance gain when using LDAP or Winbind 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, 10 Oct 2007 07:45:09 -0000 Hi Timur, I'm in the process of reviewing this patch. If it's ok I'll commit it after the HEAD is unfrozen. Timur I. Bakeyev wrote: > Hi, Michael! > > On Mon, Jul 16, 2007 at 09:02:58PM +0200, Michael Hanselmann wrote: >> Hello >> >> I was working with a company which plans to migrate its FreeBSD servers >> from using /etc/{passwd,group} to LDAP. They will have about 45'000 >> users and as much groups in the directory. > > Did you get any reaction on your patch and estimation when it maybe included > into the CURRENT? > > With best regards, > Timur Bakeyev. -- With best regards, Michael Bushkov Southern Federal University From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 08:09: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 2613816A417 for ; Wed, 10 Oct 2007 08:09:08 +0000 (UTC) (envelope-from ari@ish.com.au) Received: from fish.ish.com.au (eth5921.nsw.adsl.internode.on.net [59.167.240.32]) by mx1.freebsd.org (Postfix) with ESMTP id 988DD13C469 for ; Wed, 10 Oct 2007 08:09:07 +0000 (UTC) (envelope-from ari@ish.com.au) Received: from ip-182.ish.com.au ([203.29.62.182]) by fish.ish.com.au with esmtpa (Exim 4.43) id 1IfWc3-0001iq-C9 for freebsd-current@freebsd.org; Wed, 10 Oct 2007 18:08:15 +1000 Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: References: Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-125--1051819890" Message-Id: <283BA267-2D4E-4212-BC64-60F06A9F0E29@ish.com.au> Content-Transfer-Encoding: 7bit From: Aristedes Maniatis Date: Wed, 10 Oct 2007 18:09:04 +1000 To: freebsd-current@freebsd.org X-Pgp-Agent: GPGMail 1.1.2 (Tiger) X-Mailer: Apple Mail (2.752.2) Subject: Re: buildworld broken in tcsh [solved] 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, 10 Oct 2007 08:09:08 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-125--1051819890 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On 09/10/2007, at 2:26 PM, Aristedes Maniatis wrote: > Using Current csupped as of yesterday, buildworld fails. Just to follow up on this, I found a very similar problem reported to this list some time ago, but with no responses: http://article.gmane.org/gmane.os.freebsd.current/94159 I've been able to locate the source of the problem. My attempts to csup the source tree have been failing since I used cvsup.au.FreeBSD.org and that is returning some broken code. Changing to cvsup.FreeBSD.org and updating, then building and everything is gorgeous. So cvsup.au.freebsd.org is definitely returning broken results, but there is no indication that it is broken, until I thought it suspicious that nothing had been committed in the last 24 hours according to its output. Obviously maintaining a set of mirrors around the world is a difficult task - is there someone I should alert to this problem? Is there some way for users to check the reliability of these mirrors other than to just always use the master server (which I guess puts too much load on it). Thanks Ari Maniatis --------------------------> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A --Apple-Mail-125--1051819890 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iEYEARECAAYFAkcMiKEACgkQ72p9Lj5JECqIiwCeIhpXB2P87BTz0JS7GzpxwgRs 5IYAn0PAGTZfkNDSOWsB4DsP2fgD5WoU =4DCM -----END PGP SIGNATURE----- --Apple-Mail-125--1051819890-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 09:00: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 13BFA16A420 for ; Wed, 10 Oct 2007 09:00:21 +0000 (UTC) (envelope-from stevenschlansker@berkeley.edu) Received: from smtp-out1.berkeley.edu (smtp-out1.Berkeley.EDU [128.32.61.106]) by mx1.freebsd.org (Postfix) with ESMTP id 0451813C448 for ; Wed, 10 Oct 2007 09:00:20 +0000 (UTC) (envelope-from stevenschlansker@berkeley.edu) Received: from 209-204-139-199.dsl.dynamic.sonic.net ([209.204.139.199] helo=[192.168.42.2]) by fe4.calmail with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (auth plain:stevenschlansker@berkeley.edu) (envelope-from ) id 1IfXQS-0006ZL-F9 for freebsd-current@freebsd.org; Wed, 10 Oct 2007 02:00:20 -0700 Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: 7bit Message-Id: <441699AE-B2BB-4D1A-807E-0F02C998854F@berkeley.edu> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-current@freebsd.org From: Steven Schlansker Date: Wed, 10 Oct 2007 02:00:10 -0700 X-Mailer: Apple Mail (2.752.3) Subject: uma_zalloc_arg with with nonsleepable locks held 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, 10 Oct 2007 09:00:21 -0000 csup as of yesterday, FreeBSD keg.CSUA.Berkeley.EDU 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Tue Oct 9 19:13:43 PDT 2007 root@keg.CSUA.Berkeley.EDU:/usr/obj/usr/ src/sys/GENERIC i386 I get these lovely messages in dmesg: uma_zalloc_arg: zone "mbuf" with the following non-sleepable locks held: exclusive sleep mutex nfsd_mtx r = 0 (0xc0c06f00) locked @ /usr/src/ sys/nfsserver/nfs_srvsock.c:654 KDB: stack backtrace: db_trace_self_wrapper (c0a9c175,e69b2af8,c078428d,c0a9c538,e69b2b0c,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0a9c538,e69b2b0c,4,1,0,...) at kdb_backtrace+0x29 witness_warn(5,0,c0aba40d,c0aa1684,e69b2b1c,...) at witness_warn+0x1cd uma_zalloc_arg(c1466d20,e69b2b70,2,8,c4a32b24,...) at uma_zalloc_arg +0x34 nfs_realign(c0c06f00,0,c0ab4064,28e,0,...) at nfs_realign+0x6f nfsrv_rcv(c4a5adec,c4a32b00,2,161,0,...) at nfsrv_rcv+0x46a nfssvc(c4328210,e69b2cfc,8,e69b2d38,c0b46688,...) at nfssvc+0x6de syscall(e69b2d38) at syscall+0x2b3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280c4f7b, esp = 0xbfbfeb2c, ebp = 0xbfbfeb48 --- uma_zalloc_arg: zone "mbuf_cluster" with the following non-sleepable locks held: exclusive sleep mutex nfsd_mtx r = 0 (0xc0c06f00) locked @ /usr/src/ sys/nfsserver/nfs_srvsock.c:654 KDB: stack backtrace: db_trace_self_wrapper (c0a9c175,e69b2af8,c078428d,c0a9c538,e69b2b0c,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0a9c538,e69b2b0c,4,1,0,...) at kdb_backtrace+0x29 witness_warn(5,0,c0aba40d,c0a9758e,e69b2b1c,...) at witness_warn+0x1cd uma_zalloc_arg(c145e000,c6d17000,2,8,c4a32b24,...) at uma_zalloc_arg +0x34 nfs_realign(c0c06f00,0,c0ab4064,28e,0,...) at nfs_realign+0xba nfsrv_rcv(c4a5adec,c4a32b00,2,161,0,...) at nfsrv_rcv+0x46a nfssvc(c4328210,e69b2cfc,8,e69b2d38,c0b46688,...) at nfssvc+0x6de syscall(e69b2d38) at syscall+0x2b3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280c4f7b, esp = 0xbfbfeb2c, ebp = 0xbfbfeb48 --- uma_zalloc_arg: zone "mbuf" with the following non-sleepable locks held: exclusive sleep mutex nfsd_mtx r = 0 (0xc0c06f00) locked @ /usr/src/ sys/nfsserver/nfs_srvsock.c:654 KDB: stack backtrace: db_trace_self_wrapper (c0a9c175,e69b2af8,c078428d,c0a9c538,e69b2b0c,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0a9c538,e69b2b0c,4,1,0,...) at kdb_backtrace+0x29 witness_warn(5,0,c0aba40d,c0aa1684,e69b2b1c,...) at witness_warn+0x1cd uma_zalloc_arg(c1466d20,e69b2b70,2,8,c4a32b24,...) at uma_zalloc_arg +0x34 nfs_realign(c0c06f00,0,c0ab4064,28e,0,...) at nfs_realign+0x6f nfsrv_rcv(c4a5adec,c4a32b00,2,161,0,...) at nfsrv_rcv+0x46a nfssvc(c4328210,e69b2cfc,8,e69b2d38,c0b46688,...) at nfssvc+0x6de syscall(e69b2d38) at syscall+0x2b3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280c4f7b, esp = 0xbfbfeb2c, ebp = 0xbfbfeb48 --- uma_zalloc_arg: zone "mbuf_cluster" with the following non-sleepable locks held: exclusive sleep mutex nfsd_mtx r = 0 (0xc0c06f00) locked @ /usr/src/ sys/nfsserver/nfs_srvsock.c:654 KDB: stack backtrace: db_trace_self_wrapper (c0a9c175,e69b2af8,c078428d,c0a9c538,e69b2b0c,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0a9c538,e69b2b0c,4,1,0,...) at kdb_backtrace+0x29 witness_warn(5,0,c0aba40d,c0a9758e,e69b2b1c,...) at witness_warn+0x1cd uma_zalloc_arg(c145e000,c5671800,2,8,c4a32b24,...) at uma_zalloc_arg +0x34 nfs_realign(c0c06f00,0,c0ab4064,28e,0,...) at nfs_realign+0xba nfsrv_rcv(c4a5adec,c4a32b00,2,161,0,...) at nfsrv_rcv+0x46a nfssvc(c4328210,e69b2cfc,8,e69b2d38,c0b46688,...) at nfssvc+0x6de syscall(e69b2d38) at syscall+0x2b3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280c4f7b, esp = 0xbfbfeb2c, ebp = 0xbfbfeb48 --- uma_zalloc_arg: zone "mbuf" with the following non-sleepable locks held: exclusive sleep mutex nfsd_mtx r = 0 (0xc0c06f00) locked @ /usr/src/ sys/nfsserver/nfs_srvsock.c:654 KDB: stack backtrace: db_trace_self_wrapper (c0a9c175,e69b2af8,c078428d,c0a9c538,e69b2b0c,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0a9c538,e69b2b0c,4,1,0,...) at kdb_backtrace+0x29 witness_warn(5,0,c0aba40d,c0aa1684,e69b2b1c,...) at witness_warn+0x1cd uma_zalloc_arg(c1466d20,e69b2b70,2,8,c4a32b24,...) at uma_zalloc_arg +0x34 nfs_realign(c0c06f00,0,c0ab4064,28e,0,...) at nfs_realign+0x6f nfsrv_rcv(c4a5adec,c4a32b00,2,161,0,...) at nfsrv_rcv+0x46a nfssvc(c4328210,e69b2cfc,8,e69b2d38,c0b46688,...) at nfssvc+0x6de syscall(e69b2d38) at syscall+0x2b3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280c4f7b, esp = 0xbfbfeb2c, ebp = 0xbfbfeb48 --- uma_zalloc_arg: zone "mbuf" with the following non-sleepable locks held: exclusive sleep mutex nfsd_mtx r = 0 (0xc0c06f00) locked @ /usr/src/ sys/nfsserver/nfs_srvsock.c:654 KDB: stack backtrace: db_trace_self_wrapper (c0a9c175,e69b2af8,c078428d,c0a9c538,e69b2b0c,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0a9c538,e69b2b0c,4,1,0,...) at kdb_backtrace+0x29 witness_warn(5,0,c0aba40d,c0aa1684,e69b2b1c,...) at witness_warn+0x1cd uma_zalloc_arg(c1466d20,e69b2b70,2,8,c4a32b24,...) at uma_zalloc_arg +0x34 nfs_realign(c0c06f00,0,c0ab4064,28e,0,...) at nfs_realign+0x6f nfsrv_rcv(c4a5adec,c4a32b00,2,161,0,...) at nfsrv_rcv+0x46a nfssvc(c4328210,e69b2cfc,8,e69b2d38,c0b46688,...) at nfssvc+0x6de syscall(e69b2d38) at syscall+0x2b3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280c4f7b, esp = 0xbfbfeb2c, ebp = 0xbfbfeb48 --- uma_zalloc_arg: zone "mbuf_cluster" with the following non-sleepable locks held: exclusive sleep mutex nfsd_mtx r = 0 (0xc0c06f00) locked @ /usr/src/ sys/nfsserver/nfs_srvsock.c:654 KDB: stack backtrace: db_trace_self_wrapper (c0a9c175,e69b2af8,c078428d,c0a9c538,e69b2b0c,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0a9c538,e69b2b0c,4,1,0,...) at kdb_backtrace+0x29 witness_warn(5,0,c0aba40d,c0a9758e,e69b2b1c,...) at witness_warn+0x1cd uma_zalloc_arg(c145e000,c4dc7300,2,8,c4a32b24,...) at uma_zalloc_arg +0x34 nfs_realign(c0c06f00,0,c0ab4064,28e,0,...) at nfs_realign+0xba nfsrv_rcv(c4a5adec,c4a32b00,2,161,0,...) at nfsrv_rcv+0x46a nfssvc(c4328210,e69b2cfc,8,e69b2d38,c0b46688,...) at nfssvc+0x6de syscall(e69b2d38) at syscall+0x2b3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280c4f7b, esp = 0xbfbfeb2c, ebp = 0xbfbfeb48 --- uma_zalloc_arg: zone "mbuf" with the following non-sleepable locks held: exclusive sleep mutex nfsd_mtx r = 0 (0xc0c06f00) locked @ /usr/src/ sys/nfsserver/nfs_srvsock.c:654 KDB: stack backtrace: db_trace_self_wrapper (c0a9c175,e69b2af8,c078428d,c0a9c538,e69b2b0c,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0a9c538,e69b2b0c,4,1,0,...) at kdb_backtrace+0x29 witness_warn(5,0,c0aba40d,c0aa1684,e69b2b1c,...) at witness_warn+0x1cd uma_zalloc_arg(c1466d20,e69b2b70,2,8,c4a32b24,...) at uma_zalloc_arg +0x34 nfs_realign(c0c06f00,0,c0ab4064,28e,0,...) at nfs_realign+0x6f nfsrv_rcv(c4a5adec,c4a32b00,2,161,0,...) at nfsrv_rcv+0x46a nfssvc(c4328210,e69b2cfc,8,e69b2d38,c0b46688,...) at nfssvc+0x6de syscall(e69b2d38) at syscall+0x2b3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280c4f7b, esp = 0xbfbfeb2c, ebp = 0xbfbfeb48 --- uma_zalloc_arg: zone "mbuf_cluster" with the following non-sleepable locks held: exclusive sleep mutex nfsd_mtx r = 0 (0xc0c06f00) locked @ /usr/src/ sys/nfsserver/nfs_srvsock.c:654 KDB: stack backtrace: db_trace_self_wrapper (c0a9c175,e69b2af8,c078428d,c0a9c538,e69b2b0c,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0a9c538,e69b2b0c,4,1,0,...) at kdb_backtrace+0x29 witness_warn(5,0,c0aba40d,c0a9758e,e69b2b1c,...) at witness_warn+0x1cd uma_zalloc_arg(c145e000,c4e46b00,2,8,c4a32b24,...) at uma_zalloc_arg +0x34 nfs_realign(c0c06f00,0,c0ab4064,28e,0,...) at nfs_realign+0xba nfsrv_rcv(c4a5adec,c4a32b00,2,161,0,...) at nfsrv_rcv+0x46a nfssvc(c4328210,e69b2cfc,8,e69b2d38,c0b46688,...) at nfssvc+0x6de syscall(e69b2d38) at syscall+0x2b3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280c4f7b, esp = 0xbfbfeb2c, ebp = 0xbfbfeb48 --- uma_zalloc_arg: zone "mbuf" with the following non-sleepable locks held: exclusive sleep mutex nfsd_mtx r = 0 (0xc0c06f00) locked @ /usr/src/ sys/nfsserver/nfs_srvsock.c:654 KDB: stack backtrace: db_trace_self_wrapper (c0a9c175,e69b2af8,c078428d,c0a9c538,e69b2b0c,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0a9c538,e69b2b0c,4,1,0,...) at kdb_backtrace+0x29 witness_warn(5,0,c0aba40d,c0aa1684,e69b2b1c,...) at witness_warn+0x1cd uma_zalloc_arg(c1466d20,e69b2b70,2,8,c4a32b24,...) at uma_zalloc_arg +0x34 nfs_realign(c0c06f00,0,c0ab4064,28e,0,...) at nfs_realign+0x6f nfsrv_rcv(c4a5adec,c4a32b00,2,161,0,...) at nfsrv_rcv+0x46a nfssvc(c4328210,e69b2cfc,8,e69b2d38,c0b46688,...) at nfssvc+0x6de syscall(e69b2d38) at syscall+0x2b3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280c4f7b, esp = 0xbfbfeb2c, ebp = 0xbfbfeb48 --- uma_zalloc_arg: zone "mbuf_cluster" with the following non-sleepable locks held: exclusive sleep mutex nfsd_mtx r = 0 (0xc0c06f00) locked @ /usr/src/ sys/nfsserver/nfs_srvsock.c:654 KDB: stack backtrace: db_trace_self_wrapper (c0a9c175,e69b2af8,c078428d,c0a9c538,e69b2b0c,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0a9c538,e69b2b0c,4,1,0,...) at kdb_backtrace+0x29 witness_warn(5,0,c0aba40d,c0a9758e,e69b2b1c,...) at witness_warn+0x1cd uma_zalloc_arg(c145e000,c546e000,2,8,c4a32b24,...) at uma_zalloc_arg +0x34 nfs_realign(c0c06f00,0,c0ab4064,28e,0,...) at nfs_realign+0xba nfsrv_rcv(c4a5adec,c4a32b00,2,161,0,...) at nfsrv_rcv+0x46a nfssvc(c4328210,e69b2cfc,8,e69b2d38,c0b46688,...) at nfssvc+0x6de syscall(e69b2d38) at syscall+0x2b3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280c4f7b, esp = 0xbfbfeb2c, ebp = 0xbfbfeb48 --- uma_zalloc_arg: zone "mbuf" with the following non-sleepable locks held: exclusive sleep mutex nfsd_mtx r = 0 (0xc0c06f00) locked @ /usr/src/ sys/nfsserver/nfs_srvsock.c:654 KDB: stack backtrace: db_trace_self_wrapper (c0a9c175,e69b2af8,c078428d,c0a9c538,e69b2b0c,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0a9c538,e69b2b0c,4,1,0,...) at kdb_backtrace+0x29 witness_warn(5,0,c0aba40d,c0aa1684,e69b2b1c,...) at witness_warn+0x1cd uma_zalloc_arg(c1466d20,e69b2b70,2,8,c4a32b24,...) at uma_zalloc_arg +0x34 nfs_realign(c0c06f00,0,c0ab4064,28e,0,...) at nfs_realign+0x6f nfsrv_rcv(c4a5adec,c4a32b00,2,161,0,...) at nfsrv_rcv+0x46a nfssvc(c4328210,e69b2cfc,8,e69b2d38,c0b46688,...) at nfssvc+0x6de syscall(e69b2d38) at syscall+0x2b3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280c4f7b, esp = 0xbfbfeb2c, ebp = 0xbfbfeb48 --- uma_zalloc_arg: zone "mbuf" with the following non-sleepable locks held: exclusive sleep mutex nfsd_mtx r = 0 (0xc0c06f00) locked @ /usr/src/ sys/nfsserver/nfs_srvsock.c:654 KDB: stack backtrace: db_trace_self_wrapper (c0a9c175,e69b2af8,c078428d,c0a9c538,e69b2b0c,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0a9c538,e69b2b0c,4,1,0,...) at kdb_backtrace+0x29 witness_warn(5,0,c0aba40d,c0aa1684,e69b2b1c,...) at witness_warn+0x1cd uma_zalloc_arg(c1466d20,e69b2b70,2,8,c4a32b24,...) at uma_zalloc_arg +0x34 nfs_realign(c0c06f00,0,c0ab4064,28e,0,...) at nfs_realign+0x6f nfsrv_rcv(c4a5adec,c4a32b00,2,161,0,...) at nfsrv_rcv+0x46a nfssvc(c4328210,e69b2cfc,8,e69b2d38,c0b46688,...) at nfssvc+0x6de syscall(e69b2d38) at syscall+0x2b3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280c4f7b, esp = 0xbfbfeb2c, ebp = 0xbfbfeb48 --- I hope they are harmless and known about, but I haven't seen anything like this pass over the list for the last few days so I thought I'd put it up in case it was an issue. Steven From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 09:34: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 4FCDF16A421 for ; Wed, 10 Oct 2007 09:34:45 +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 EFE0313C48D for ; Wed, 10 Oct 2007 09:34:44 +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 1IfXxj-00066Y-J5 for freebsd-current@freebsd.org; Wed, 10 Oct 2007 12:34:43 +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 1IfXxh-0008Fe-FH for freebsd-current@freebsd.org; Wed, 10 Oct 2007 12:34:43 +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 l9A9YbFl011830; Wed, 10 Oct 2007 12:34:38 +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 l9A9Yamu011824; Wed, 10 Oct 2007 12:34:36 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 10 Oct 2007 12:34:36 +0300 From: Kostik Belousov To: Igor Sysoev Message-ID: <20071010093436.GB2180@deviant.kiev.zoral.com.ua> References: <20071009125001.GC5758@rambler-co.ru> <20071010055748.GA18931@rambler-co.ru> <20071010060605.GB18931@rambler-co.ru> <470C6DD4.1060509@mawer.org> <20071010062541.GA23840@rambler-co.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Iy2CUD6FdotTkhwY" Content-Disposition: inline In-Reply-To: <20071010062541.GA23840@rambler-co.ru> User-Agent: Mutt/1.4.2.3i X-Scanner-Signature: 847c6fee4a3d87663807aea2254f2919 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 1578 [Oct 09 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@freebsd.org, Antony Mawer Subject: Re: sendfile and page usage statistics 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, 10 Oct 2007 09:34:45 -0000 --Iy2CUD6FdotTkhwY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 10, 2007 at 10:25:41AM +0400, Igor Sysoev wrote: > On Wed, Oct 10, 2007 at 04:14:44PM +1000, Antony Mawer wrote: >=20 > > On 10/10/2007 4:06 PM, Igor Sysoev wrote: > > >On Wed, Oct 10, 2007 at 09:57:48AM +0400, Igor Sysoev wrote: > > > > > >>On Tue, Oct 09, 2007 at 04:50:01PM +0400, Igor Sysoev wrote: > > >> > > >>>As I understand if sendfile() with hardware TX chsum or TSO are used, > > >>>then CPU does not touch file pages at all. So pagedaemon never set > > >>>PG_REFERENCED to vnode object pages while scanning them. > > >>>Does VM set PG_REFERENCED by another way ? Otherwise, often used fil= es > > >>>that accessed by sendfile() only have small chances to be cached by = VM. > > >>I have looked kern_sendfile() in CURRENT and it seems to me that > > >>PG_REFERENCED is never set when sendfile() gets cached vm_page. > > >>I have looked the code path: > > >> > > >>vm_page_grab() > > >> vm_page_lookup() > > >> vm_page_wire() > > >>sf_buf_alloc() on i386 and amd64 > > >> > > >>and have not seen PG_REFERENCED. > > > > > >As I understand the following patch against uipc_syscalls.c > > >should fix the bug to some extent: > > > > > > if (pg->valid && vm_page_is_valid(pg, pgoff,= =20 > > > xfsize)) > > >+ vm_page_flag_set(pg, PG_REFERENCED); > > > VM_OBJECT_UNLOCK(obj); > > > else if (m !=3D NULL) > >=20 > > You are missing opening/closing braces on your if() statement with this= =20 > > change... >=20 > Oh, thank you! You have saved me from coredump. > This is why in my coding style I always use braces for single statement= =20 > inside if(). Also, as a minimum you need to brace the vm_page_flag_set() with vm_page_lock_queues()/vm_page_unlock_queues(). But I think that the actual patch is wrong. The PG_REFERENCED bit shall be set when hardware access bit is set on pte. You patch would set it in advance. --Iy2CUD6FdotTkhwY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHDJysC3+MBN1Mb4gRAj+WAKCQNdZT728t4t7msPeDwic0+0NSaQCeIlGk TfSYvOp0XNmAtrxVuZMgjNM= =yxUs -----END PGP SIGNATURE----- --Iy2CUD6FdotTkhwY-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 09: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 D86DC16A417 for ; Wed, 10 Oct 2007 09:44:21 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id 8848A13C465 for ; Wed, 10 Oct 2007 09:44:21 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost2.sentex.ca (8.14.1/8.13.8) with ESMTP id l9A9QWE9092486; Wed, 10 Oct 2007 05:26:32 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id l9A9QVmo052657 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Oct 2007 05:26:32 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <200710100926.l9A9QVmo052657@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 10 Oct 2007 05:27:06 -0400 To: "Jack Vogel" , "freebsd-net@freebsd.org" , "FreeBSD Current" From: Mike Tancsa In-Reply-To: <2a41acea0710091603u7b87d6fdsdaaadf4cafbea2d9@mail.gmail.co m> References: <2a41acea0710091603u7b87d6fdsdaaadf4cafbea2d9@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: Subject: Re: Patch to add EEPROM dump 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, 10 Oct 2007 09:44:21 -0000 At 07:03 PM 10/9/2007, Jack Vogel wrote: >Mike, > > This is a patch against my 6.6.6 driver that adds a new value to the >debug sysctl, you would give the command 'sysctl dev.em.0.debug=2' >and it will dump out the first 32 16-bit words of the prom. Hi, Yes, I think this would be helpful indeed. I tried it on a few boxes at HQ Interface EEPROM Dump: Offset 0x0000 3000 8f48 8b3e 0d20 f746 0057 ffff ffff 0x0010 ffff ffff 026b 109a 15d9 109a 8086 80df 0x0020 0000 2000 7e54 0000 1000 00da 0004 2700 0x0030 6cc9 3150 0732 040b 2984 0000 c000 0706 Interface EEPROM Dump: Offset 0x0000 3000 8f48 8a3e 0d30 f746 00f4 ffff ffff 0x0010 ffff ffff 026b 108c 15d9 108c 8086 83df 0x0020 0008 2000 7e14 0048 1000 00d8 0000 2700 0x0030 6cc9 3150 0722 040b 0984 0000 c000 0706 em0@pci13:0:0: class=0x020000 card=0x108c15d9 chip=0x108c8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/1000 PM' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[e0] = PCI-Express 1 endpoint em1@pci14:0:0: class=0x020000 card=0x109a15d9 chip=0x109a8086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[e0] = PCI-Express 1 endpoint >I was wondering what the general reaction to this is, it may be useful >at some points in helping debug things. Yes, if anything to better identify a NIC and rev. Thanks for the addition! ---Mike >Comments? > >Jack > >Content-Type: application/octet-stream; name=eeprom-dump.patch >X-Attachment-Id: f_f7l0m8f3 >Content-Disposition: attachment; filename=eeprom-dump.patch > >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 09:50: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 8AE0316A41A for ; Wed, 10 Oct 2007 09:50:24 +0000 (UTC) (envelope-from is@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.freebsd.org (Postfix) with ESMTP id 7E1E513C4B6 for ; Wed, 10 Oct 2007 09:50:23 +0000 (UTC) (envelope-from is@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id 3D3E38DB0; Wed, 10 Oct 2007 13:50:22 +0400 (MSD) Received: from localhost (is1.park.rambler.ru [81.19.64.121]) by relay0.rambler.ru (Postfix) with ESMTP id 199A58882; Wed, 10 Oct 2007 13:50:22 +0400 (MSD) Date: Wed, 10 Oct 2007 13:50:18 +0400 From: Igor Sysoev To: Kostik Belousov Message-ID: <20071010095018.GA28123@rambler-co.ru> References: <20071009125001.GC5758@rambler-co.ru> <20071010055748.GA18931@rambler-co.ru> <20071010060605.GB18931@rambler-co.ru> <470C6DD4.1060509@mawer.org> <20071010062541.GA23840@rambler-co.ru> <20071010093436.GB2180@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20071010093436.GB2180@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: freebsd-current@freebsd.org, Antony Mawer Subject: Re: sendfile and page usage statistics 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, 10 Oct 2007 09:50:24 -0000 On Wed, Oct 10, 2007 at 12:34:36PM +0300, Kostik Belousov wrote: > On Wed, Oct 10, 2007 at 10:25:41AM +0400, Igor Sysoev wrote: > > On Wed, Oct 10, 2007 at 04:14:44PM +1000, Antony Mawer wrote: > > > > > On 10/10/2007 4:06 PM, Igor Sysoev wrote: > > > >On Wed, Oct 10, 2007 at 09:57:48AM +0400, Igor Sysoev wrote: > > > > > > > >>On Tue, Oct 09, 2007 at 04:50:01PM +0400, Igor Sysoev wrote: > > > >> > > > >>>As I understand if sendfile() with hardware TX chsum or TSO are used, > > > >>>then CPU does not touch file pages at all. So pagedaemon never set > > > >>>PG_REFERENCED to vnode object pages while scanning them. > > > >>>Does VM set PG_REFERENCED by another way ? Otherwise, often used files > > > >>>that accessed by sendfile() only have small chances to be cached by VM. > > > >>I have looked kern_sendfile() in CURRENT and it seems to me that > > > >>PG_REFERENCED is never set when sendfile() gets cached vm_page. > > > >>I have looked the code path: > > > >> > > > >>vm_page_grab() > > > >> vm_page_lookup() > > > >> vm_page_wire() > > > >>sf_buf_alloc() on i386 and amd64 > > > >> > > > >>and have not seen PG_REFERENCED. > > > > > > > >As I understand the following patch against uipc_syscalls.c > > > >should fix the bug to some extent: > > > > > > > > if (pg->valid && vm_page_is_valid(pg, pgoff, > > > > xfsize)) > > > >+ vm_page_flag_set(pg, PG_REFERENCED); > > > > VM_OBJECT_UNLOCK(obj); > > > > else if (m != NULL) > > > > > > You are missing opening/closing braces on your if() statement with this > > > change... > > > > Oh, thank you! You have saved me from coredump. > > This is why in my coding style I always use braces for single statement > > inside if(). > > Also, as a minimum you need to brace the vm_page_flag_set() with > vm_page_lock_queues()/vm_page_unlock_queues(). Thank you. > But I think that the actual patch is wrong. The PG_REFERENCED bit shall > be set when hardware access bit is set on pte. You patch would set it in > advance. The problem is that ethernet card that does TX chsum, DMA and TSO never sets PG_A, so sendfile() should set it in advance. I'm going to test the patch on machine where all files takes more memory than physical memory and there are some popular files. I espect to see 1) increased active memory. 2) decreased number i/o. -- Igor Sysoev http://sysoev.ru/en/ From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 09:54: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 9313016A41A; Wed, 10 Oct 2007 09:54:11 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.freebsd.org (Postfix) with ESMTP id 249C213C4A6; Wed, 10 Oct 2007 09:54:11 +0000 (UTC) (envelope-from max@love2party.net) Received: from amd64.laiers.local (dslb-088-066-062-141.pools.arcor-ip.net [88.66.62.141]) by mrelayeu.kundenserver.de (node=mrelayeu0) with ESMTP (Nemesis) id 0MKwh2-1IfYGR3ka2-0000z4; Wed, 10 Oct 2007 11:54:04 +0200 From: Max Laier Organization: FreeBSD To: freebsd-current@freebsd.org Date: Wed, 10 Oct 2007 11:53:43 +0200 User-Agent: KMail/1.9.7 References: <441699AE-B2BB-4D1A-807E-0F02C998854F@berkeley.edu> In-Reply-To: <441699AE-B2BB-4D1A-807E-0F02C998854F@berkeley.edu> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2154658.8nJQbGqejf"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200710101153.58230.max@love2party.net> X-Provags-ID: V01U2FsdGVkX19S+Xu97ctBmUWzPt1BTMXFY4hD0T1PdPOxpwW c5C9ZmkdzL2qC06VRsVqopcW06o0Gjyt7pwQRqbI0pQRiiRdXg 3gQvPFSBZqEpi/n4u4rliJ0FfHTRP6c2xE5MyNmntk= Cc: rick@snowhite.cis.uoguelph.ca, rwatson@FreeBSD.org, Steven Schlansker Subject: Re: uma_zalloc_arg with with nonsleepable locks held 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, 10 Oct 2007 09:54:11 -0000 --nextPart2154658.8nJQbGqejf Content-Type: multipart/mixed; boundary="Boundary-01=_sEKDHePXKAnPfdh" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_sEKDHePXKAnPfdh Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 10 October 2007, Steven Schlansker wrote: > csup as of yesterday, > FreeBSD keg.CSUA.Berkeley.EDU 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Tue > Oct 9 19:13:43 PDT 2007 root@keg.CSUA.Berkeley.EDU:/usr/obj/usr/ > src/sys/GENERIC i386 > > I get these lovely messages in dmesg: The attached should fix that. I'm not 100% certain this doesn't open a=20 race. If that is the case, however, it seems that the race was already=20 there. Thoughts? > uma_zalloc_arg: zone "mbuf" with the following non-sleepable locks > held: exclusive sleep mutex nfsd_mtx r =3D 0 (0xc0c06f00) locked @ > /usr/src/ sys/nfsserver/nfs_srvsock.c:654 > KDB: stack backtrace: > db_trace_self_wrapper > (c0a9c175,e69b2af8,c078428d,c0a9c538,e69b2b0c,...) at > db_trace_self_wrapper+0x26 > kdb_backtrace(c0a9c538,e69b2b0c,4,1,0,...) at kdb_backtrace+0x29 > witness_warn(5,0,c0aba40d,c0aa1684,e69b2b1c,...) at witness_warn+0x1cd > uma_zalloc_arg(c1466d20,e69b2b70,2,8,c4a32b24,...) at uma_zalloc_arg > +0x34 > nfs_realign(c0c06f00,0,c0ab4064,28e,0,...) at nfs_realign+0x6f > nfsrv_rcv(c4a5adec,c4a32b00,2,161,0,...) at nfsrv_rcv+0x46a > nfssvc(c4328210,e69b2cfc,8,e69b2d38,c0b46688,...) at nfssvc+0x6de > syscall(e69b2d38) at syscall+0x2b3 > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (155, FreeBSD ELF32, nfssvc), eip =3D 0x280c4f7b, esp =3D > 0xbfbfeb2c, ebp =3D 0xbfbfeb48 --- =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --Boundary-01=_sEKDHePXKAnPfdh Content-Type: text/x-diff; charset="iso-8859-1"; name="nfs_realign.lock.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="nfs_realign.lock.diff" Index: nfs_srvsock.c =================================================================== RCS file: /usr/store/mlaier/fcvs/src/sys/nfsserver/nfs_srvsock.c,v retrieving revision 1.104 diff -u -r1.104 nfs_srvsock.c --- nfs_srvsock.c 6 Aug 2007 14:26:02 -0000 1.104 +++ nfs_srvsock.c 10 Oct 2007 09:40:52 -0000 @@ -648,19 +648,23 @@ *mpp = recm; if (slp->ns_flag & SLP_LASTFRAG) { struct nfsrv_rec *rec; + struct mbuf *m0; + + m0 = slp->ns_frag; + slp->ns_frag = NULL; NFSD_UNLOCK(); rec = malloc(sizeof(struct nfsrv_rec), M_NFSRVDESC, waitflag == M_DONTWAIT ? M_NOWAIT : M_WAITOK); - NFSD_LOCK(); - if (!rec) { - m_freem(slp->ns_frag); + if (rec == NULL) { + m_freem(m0); + NFSD_LOCK(); } else { - nfs_realign(&slp->ns_frag, 10 * NFSX_UNSIGNED); + nfs_realign(&m0, 10 * NFSX_UNSIGNED); + NFSD_LOCK(); rec->nr_address = NULL; - rec->nr_packet = slp->ns_frag; + rec->nr_packet = m0; STAILQ_INSERT_TAIL(&slp->ns_rec, rec, nr_link); } - slp->ns_frag = NULL; } } } --Boundary-01=_sEKDHePXKAnPfdh-- --nextPart2154658.8nJQbGqejf 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) iD8DBQBHDKE2XyyEoT62BG0RAgrgAJ9PK6j0QqbL9QY346586IGB0ZqBygCeMhE3 bU1dKdt4BGWxIOeiw/Vc2Rw= =Wzej -----END PGP SIGNATURE----- --nextPart2154658.8nJQbGqejf-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 10:13: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 890F916A41B for ; Wed, 10 Oct 2007 10:13:11 +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 1598C13C469 for ; Wed, 10 Oct 2007 10:13:10 +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 1IfYYw-000Ach-1b for freebsd-current@freebsd.org; Wed, 10 Oct 2007 13:13:10 +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 1IfYYu-0009U0-1W for freebsd-current@freebsd.org; Wed, 10 Oct 2007 13:13:09 +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 l9AAD4BJ043678; Wed, 10 Oct 2007 13:13:04 +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 l9AAD4cj043660; Wed, 10 Oct 2007 13:13:04 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 10 Oct 2007 13:13:04 +0300 From: Kostik Belousov To: Cc: Igor Sysoev Message-ID: <20071010101304.GC2180@deviant.kiev.zoral.com.ua> References: <20071009125001.GC5758@rambler-co.ru> <20071010055748.GA18931@rambler-co.ru> <20071010060605.GB18931@rambler-co.ru> <470C6DD4.1060509@mawer.org> <20071010062541.GA23840@rambler-co.ru> <20071010093436.GB2180@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/aHqdxxe3Vo3WJ36" Content-Disposition: inline In-Reply-To: <20071010093436.GB2180@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.4.2.3i X-Scanner-Signature: ca614d1e091d53a46adb2ef7a730c6a6 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 1580 [Oct 10 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@freebsd.org, Antony Mawer Subject: Re: sendfile and page usage statistics 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, 10 Oct 2007 10:13:11 -0000 --/aHqdxxe3Vo3WJ36 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 10, 2007 at 12:34:36PM +0300, Kostik Belousov wrote: > On Wed, Oct 10, 2007 at 10:25:41AM +0400, Igor Sysoev wrote: > > On Wed, Oct 10, 2007 at 04:14:44PM +1000, Antony Mawer wrote: > >=20 > > > On 10/10/2007 4:06 PM, Igor Sysoev wrote: > > > >On Wed, Oct 10, 2007 at 09:57:48AM +0400, Igor Sysoev wrote: > > > > > > > >>On Tue, Oct 09, 2007 at 04:50:01PM +0400, Igor Sysoev wrote: > > > >> > > > >>>As I understand if sendfile() with hardware TX chsum or TSO are us= ed, > > > >>>then CPU does not touch file pages at all. So pagedaemon never set > > > >>>PG_REFERENCED to vnode object pages while scanning them. > > > >>>Does VM set PG_REFERENCED by another way ? Otherwise, often used f= iles > > > >>>that accessed by sendfile() only have small chances to be cached b= y VM. > > > >>I have looked kern_sendfile() in CURRENT and it seems to me that > > > >>PG_REFERENCED is never set when sendfile() gets cached vm_page. > > > >>I have looked the code path: > > > >> > > > >>vm_page_grab() > > > >> vm_page_lookup() > > > >> vm_page_wire() > > > >>sf_buf_alloc() on i386 and amd64 > > > >> > > > >>and have not seen PG_REFERENCED. > > > > > > > >As I understand the following patch against uipc_syscalls.c > > > >should fix the bug to some extent: > > > > > > > > if (pg->valid && vm_page_is_valid(pg, pgoff= ,=20 > > > > xfsize)) > > > >+ vm_page_flag_set(pg, PG_REFERENCED); > > > > VM_OBJECT_UNLOCK(obj); > > > > else if (m !=3D NULL) > > >=20 > > > You are missing opening/closing braces on your if() statement with th= is=20 > > > change... > >=20 > > Oh, thank you! You have saved me from coredump. > > This is why in my coding style I always use braces for single statement= =20 > > inside if(). >=20 > Also, as a minimum you need to brace the vm_page_flag_set() with > vm_page_lock_queues()/vm_page_unlock_queues(). >=20 > But I think that the actual patch is wrong. The PG_REFERENCED bit shall > be set when hardware access bit is set on pte. You patch would set it in > advance. To clarify my point that is badly worded above: PG_REFERENCED shall be translated from PG_A (for i386/amd64) in pte when the sf buffer is dissolved. This way, PG_REFERENCED will be set only when the page was actually used, preventing page cache pollution. The busdma, most likely, shall notify pmap on hw access to the page. --/aHqdxxe3Vo3WJ36 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHDKWvC3+MBN1Mb4gRAvoeAKC8Y1JIVrnE8wxmbyZWQjLPf/nj1wCg4AeK 5R9SJcY79tSSXAgwhoFlCAY= =Xh13 -----END PGP SIGNATURE----- --/aHqdxxe3Vo3WJ36-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 10:21:22 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 D6D6116A41A for ; Wed, 10 Oct 2007 10:21:22 +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 875F613C49D for ; Wed, 10 Oct 2007 10:21:22 +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 1IfYgr-000Blq-LK for current@freebsd.org; Wed, 10 Oct 2007 13:21:21 +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 1IfYgq-000FaI-UJ for current@freebsd.org; Wed, 10 Oct 2007 13:21:21 +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 l9AALKGE074436 for ; Wed, 10 Oct 2007 13:21:20 +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 l9AALKHd074435 for current@freebsd.org; Wed, 10 Oct 2007 13:21:20 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 10 Oct 2007 13:21:20 +0300 From: Kostik Belousov To: current@freebsd.org Message-ID: <20071010102120.GD2180@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7IzduDXdmGAvR4BO" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Scanner-Signature: 5bcd58edb95cdacf596e852bfe0375ec X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 1580 [Oct 10 2007] X-SpamTest-Info: helo_type=3 X-SpamTest-Info: {TO: local part of email appears in body} X-SpamTest-Info: {received from trusted relay: not dialup} X-SpamTest-Method: none X-SpamTest-Method: Local Lists X-SpamTest-Rate: 10 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release Cc: Subject: libkse.so.0 and libkse.so.3 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, 10 Oct 2007 10:21:22 -0000 --7IzduDXdmGAvR4BO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On the current system upgraded today, after recent repocopies of libkse, I get: deviant% ls -l /usr/lib/lib*kse* ~ -r--r--r-- 1 root wheel 272190 Oct 10 13:14 /usr/lib/libkse.a lrwxr-xr-x 1 root wheel 11 Oct 10 13:14 /usr/lib/libkse.so -> libkse.so.0 -r--r--r-- 1 root wheel 144236 Oct 10 13:14 /usr/lib/libkse.so.0 -r--r--r-- 1 root wheel 144284 Oct 3 14:55 /usr/lib/libkse.so.3 Shall the libkse.so.3 be removed ? Or, the version number for actual libkse set to 3 instead of 0 ? --7IzduDXdmGAvR4BO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHDKefC3+MBN1Mb4gRAgbhAJ9BNfyyiOOgT62VpQbFxtjb000GnwCgm5Gu +iG5Mbo36hhAKml3SZjHYv8= =XPCH -----END PGP SIGNATURE----- --7IzduDXdmGAvR4BO-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 11:08: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 BB13416A418 for ; Wed, 10 Oct 2007 11:08:10 +0000 (UTC) (envelope-from dg@dglawrence.com) Received: from dglawrence.com (static-72-90-113-2.ptldor.fios.verizon.net [72.90.113.2]) by mx1.freebsd.org (Postfix) with ESMTP id 9663813C461 for ; Wed, 10 Oct 2007 11:08:09 +0000 (UTC) (envelope-from dg@dglawrence.com) Received: from tnn.dglawrence.com (localhost [127.0.0.1]) by dglawrence.com (8.14.1/8.14.1) with ESMTP id l9AAS0tj041127; Wed, 10 Oct 2007 03:28:00 -0700 (PDT) (envelope-from dg@dglawrence.com) Received: (from dg@localhost) by tnn.dglawrence.com (8.14.1/8.14.1/Submit) id l9AARuvd041126; Wed, 10 Oct 2007 03:27:56 -0700 (PDT) (envelope-from dg@dglawrence.com) X-Authentication-Warning: tnn.dglawrence.com: dg set sender to dg@dglawrence.com using -f Date: Wed, 10 Oct 2007 03:27:56 -0700 From: David G Lawrence To: Igor Sysoev Message-ID: <20071010102756.GE56714@tnn.dglawrence.com> References: <20071009125001.GC5758@rambler-co.ru> <20071010055748.GA18931@rambler-co.ru> <20071010060605.GB18931@rambler-co.ru> <470C6DD4.1060509@mawer.org> <20071010062541.GA23840@rambler-co.ru> <20071010093436.GB2180@deviant.kiev.zoral.com.ua> <20071010095018.GA28123@rambler-co.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071010095018.GA28123@rambler-co.ru> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (dglawrence.com [127.0.0.1]); Wed, 10 Oct 2007 03:28:00 -0700 (PDT) Cc: Kostik Belousov , freebsd-current@freebsd.org, Antony Mawer Subject: Re: sendfile and page usage statistics 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, 10 Oct 2007 11:08:10 -0000 > > But I think that the actual patch is wrong. The PG_REFERENCED bit shall > > be set when hardware access bit is set on pte. You patch would set it in > > advance. > > The problem is that ethernet card that does TX chsum, DMA and TSO never > sets PG_A, so sendfile() should set it in advance. > > I'm going to test the patch on machine where all files takes more memory > than physical memory and there are some popular files. > > I espect to see > 1) increased active memory. > 2) decreased number i/o. I would say that it is far from clear that this change would result in better performance. It is generally the case in FreeBSD that we bias in favor of executable pages (usually the image itself as its pages are executed, but also the image data pages). Pages involved in regular file I/O take a back seat. This is because a regular file is accessed typically in one burst, whereas an executable page is accessed in small chunks over a much larger period of time (and thus is affected more by a cache miss). Thus, PG_REFERENCED gets set for pages that are mmaped, but not for pages involved in read, write, sendfile, etc. Different workloads of course will have different behavior. One side effect of this will likely be much more system paging activity as sendfile causes process pages to be pushed out of memory in favor of cached file data. This is generally a bad thing and would result in reduced interactive performance. -DG David G. Lawrence President Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500 The FreeBSD Project - http://www.freebsd.org Pave the road of life with opportunities. From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 11:16:59 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 7732916A417 for ; Wed, 10 Oct 2007 11:16:59 +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 386AF13C48D for ; Wed, 10 Oct 2007 11:16:59 +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 94D2720BF; Wed, 10 Oct 2007 12:58:34 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 1CF4F20BC; Wed, 10 Oct 2007 12:58:34 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id 0475A84485; Wed, 10 Oct 2007 12:58:33 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "Petr Holub" References: <031f01c809ef$c829de80$5317fb93@KLOBOUCEK> Date: Wed, 10 Oct 2007 12:58:33 +0200 In-Reply-To: <031f01c809ef$c829de80$5317fb93@KLOBOUCEK> (Petr Holub's message of "Mon\, 8 Oct 2007 23\:11\:23 +0200") Message-ID: <86641fgrs6.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: Kostik Belousov , current@freebsd.org Subject: Re: panic on boot 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, 10 Oct 2007 11:16:59 -0000 "Petr Holub" writes: > Despite you couldn't guarantee it, it really helped and it boots now. > I've used the binary loader available from ~kib site and just replaced > it on the original ISO: mdcondifig -> mount -> > tar cf - | (cd elswhere && tar xvpf -) -> replace the loader -> mkisomage= s.sh You realize that you can simply 'tar xf' an ISO image, instead of jumping through hoops with mdconfig? DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 11:25:06 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 2418C16A419 for ; Wed, 10 Oct 2007 11:25:06 +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 134F413C49D for ; Wed, 10 Oct 2007 11:25:06 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 148611CC05C; Wed, 10 Oct 2007 04:25:05 -0700 (PDT) Date: Wed, 10 Oct 2007 04:25:05 -0700 From: Jeremy Chadwick To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= Message-ID: <20071010112505.GA28273@eos.sc1.parodius.com> Mail-Followup-To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= , Petr Holub , Kostik Belousov , current@freebsd.org References: <031f01c809ef$c829de80$5317fb93@KLOBOUCEK> <86641fgrs6.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <86641fgrs6.fsf@ds4.des.no> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Petr Holub , Kostik Belousov , current@freebsd.org Subject: Re: panic on boot 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, 10 Oct 2007 11:25:06 -0000 On Wed, Oct 10, 2007 at 12:58:33PM +0200, Dag-Erling Smørgrav wrote: > "Petr Holub" writes: > > Despite you couldn't guarantee it, it really helped and it boots now. > > I've used the binary loader available from ~kib site and just replaced > > it on the original ISO: mdcondifig -> mount -> > > tar cf - | (cd elswhere && tar xvpf -) -> replace the loader -> mkisomages.sh > > You realize that you can simply 'tar xf' an ISO image, instead of > jumping through hoops with mdconfig? Most FreeBSD users I know of (junior and senior) do not know about libarchive(3), nor what's linked to it (tar). Heck, even *I* didn't know it had ISO9660 and ZIP support until I read the manpage; I thought it was limited to tar, pax, and cpio archives. -- | 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 Wed Oct 10 06: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 1E81216A418 for ; Wed, 10 Oct 2007 06:55:22 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id 4CAA213C44B for ; Wed, 10 Oct 2007 06:55:21 +0000 (UTC) (envelope-from janm@transactionware.com) Received: (qmail 84394 invoked from network); 10 Oct 2007 06:27:31 -0000 Received: from midgard.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 10 Oct 2007 06:27:31 -0000 Received: (qmail 45512 invoked by uid 907); 10 Oct 2007 06:28:37 -0000 Received: from [192.168.1.51] (HELO janmxp) (192.168.1.51) by midgard.transactionware.com (qpsmtpd/0.32) with ESMTP; Wed, 10 Oct 2007 16:28:37 +1000 From: "Jan Mikkelsen" To: "'Igor Sysoev'" , References: <20071009125001.GC5758@rambler-co.ru> <20071010055748.GA18931@rambler-co.ru> <20071010060605.GB18931@rambler-co.ru> In-Reply-To: <20071010060605.GB18931@rambler-co.ru> Date: Wed, 10 Oct 2007 16:28:36 +1000 Organization: Transactionware Message-ID: <001b01c80b06$ca1c9800$5e55c800$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcgLA8p8pAf2uSC0R0S3UW95XAfPowAAqWOA Content-Language: en-au X-Mailman-Approved-At: Wed, 10 Oct 2007 11:25:16 +0000 Cc: Subject: RE: sendfile and page usage statistics 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, 10 Oct 2007 06:55:22 -0000 Hi, Igor Sysoev wrote: > As I understand the following patch against uipc_syscalls.c > should fix the bug to some extent: > > if (pg->valid && vm_page_is_valid(pg, > pgoff, xfsize)) > + vm_page_flag_set(pg, > PG_REFERENCED); > VM_OBJECT_UNLOCK(obj); > else if (m != NULL) > Without knowing anything at all about the surrounding code, I suspect this patch is missing some braces. The change should probably look like this: if (pg->valid && vm_page_is_valid(pg, pgoff, xfsize)) { vm_page_flag_set(pg, PG_REFERENCED); VM_OBJECT_UNLOCK(obj); } else if (m != NULL) I don't think you'll get the behaviour you expect with your change. Regards, Jan Mikkelsen From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 13:28: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 A9DC016A417; Wed, 10 Oct 2007 13:28:09 +0000 (UTC) (envelope-from pvh@sanbi.ac.za) Received: from mail.sanbi.ac.za (polka2.sanbi.ac.za [196.38.142.121]) by mx1.freebsd.org (Postfix) with ESMTP id C4BF213C461; Wed, 10 Oct 2007 13:28:03 +0000 (UTC) (envelope-from pvh@sanbi.ac.za) Received: from speedmetal.sanbi.ac.za (speedmetal.sanbi.ac.za [196.38.142.116]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sanbi.ac.za (Postfix) with ESMTP id 0F7128AC6B8; Wed, 10 Oct 2007 14:55:19 +0200 (SAST) Message-ID: <470CCBB6.3050506@sanbi.ac.za> Date: Wed, 10 Oct 2007 14:55:18 +0200 From: Peter van Heusden User-Agent: Thunderbird 2.0.0.6 (X11/20070926) MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-java@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SANBI-MailScanner-Information: Please contact the ISP for more information X-SANBI-MailScanner: Found to be clean X-SANBI-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (not cached, score=-4.399, required 5, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60) X-SANBI-MailScanner-From: pvh@sanbi.ac.za X-Spam-Status: No Cc: Subject: Which java jdk to use on -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: Wed, 10 Oct 2007 13:28:09 -0000 Hi I am having trouble getting a working jdk on -CURRENT. Thus far, I have diablo-jdk-1.5.0.07.01_7 installed, but it is dumping core in various circumstances - for instance when used as part of OpenOffice, trying to run Sun Download Manager, etc. I have tried installing the java/jdk16 port, but got this: Packing /usr/ports/java/jdk16/work/control/build/bsd-i586/j2re-image/lib/rt.jar 47602320 bytes Exception in thread "main" java.lang.AssertionError at com.sun.java.util.jar.pack.ClassReader.readRef(ClassReader.java:90) at com.sun.java.util.jar.pack.ClassReader.readUtf8Ref(ClassReader.java:102) at com.sun.java.util.jar.pack.ClassReader.readMember(ClassReader.java:306) at com.sun.java.util.jar.pack.ClassReader.readMembers(ClassReader.java:300) at com.sun.java.util.jar.pack.ClassReader.read(ClassReader.java:126) at com.sun.java.util.jar.pack.PackerImpl$DoPack.readClass(PackerImpl.java:490) at com.sun.java.util.jar.pack.PackerImpl$DoPack.run(PackerImpl.java:464) at com.sun.java.util.jar.pack.PackerImpl.pack(PackerImpl.java:73) at com.sun.java.util.jar.pack.Driver.main(Driver.java:261) gmake[3]: *** [pack-jars] Error 1 gmake[3]: Leaving directory `/usr/ports/java/jdk16/work/install/make/pack' gmake[2]: *** [pack-jre] Error 2 gmake[2]: Leaving directory `/usr/ports/java/jdk16/work/install/make/pack' gmake[1]: *** [all] Error 1 gmake[1]: Leaving directory `/usr/ports/java/jdk16/work/install/make' gmake: *** [install-build] Error 2 *** Error code 2 Stop in /usr/ports/java/jdk16. *** Error code 1 Stop in /usr/ports/java/jdk16. and for the java/jdk15 port, I get this: ../../../../../src/share/classes/java/nio/Bits.java:19: duplicate class: Bits class Bits { // package-private ^ ../../../../../src/solaris/classes/sun/net/www/protocol/file/Handler.java:26: duplicate class: Handler public class Handler extends URLStreamHandler { ^ ../../../../../src/share/classes/java/lang/Class.java:10: cannot access java.lang.reflect.Array bad class file: ../../../../../src/share/classes/java/lang/reflect/Array.java file does not contain class java.lang.reflect.Array Please remove or make sure it appears in the correct subdirectory of the classpath. import java.lang.reflect.Array; ^ 3 errors gmake[7]: *** [.compile.classlist] Error 1 gmake[7]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/sun/javac/recompile/library' gmake[6]: *** [optimized] Error 2 gmake[6]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/sun/javac/recompile/library' gmake[5]: *** [all] Error 1 gmake[5]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/sun/javac/recompile' gmake[4]: *** [all] Error 1 gmake[4]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/sun/javac' gmake[3]: *** [all] Error 2 gmake[3]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/java/javac' gmake[2]: *** [all] Error 1 gmake[2]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/java' gmake[1]: *** [all] Error 1 gmake[1]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make' gmake: *** [j2se-build] Error 2 *** Error code 2 Stop in /usr/ports/java/jdk15. *** Error code 1 Stop in /usr/ports/java/jdk15. I'm not sure where to turn at this point - is there a known "good" JDK which works with -CURRENT (on x86)? Thanks, Peter From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 13:34:51 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 B0D7D16A41B for ; Wed, 10 Oct 2007 13:34:51 +0000 (UTC) (envelope-from remy.nonnenmacher@activnetworks.com) Received: from mallaury.nerim.net (mallaury.ipv6.nerim.net [IPv6:2001:7a8:1:5::82]) by mx1.freebsd.org (Postfix) with ESMTP id 73CE613C47E for ; Wed, 10 Oct 2007 13:34:51 +0000 (UTC) (envelope-from remy.nonnenmacher@activnetworks.com) Received: from rn.activnetworks.com (anwadmin.net8.nerim.net [213.41.185.85]) by mallaury.nerim.net (Postfix) with ESMTP id 047664F43E; Wed, 10 Oct 2007 15:34:40 +0200 (CEST) Message-ID: <470CD4F9.1060705@activnetworks.com> Date: Wed, 10 Oct 2007 15:34:49 +0200 From: Remy Nonnenmacher User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.4) Gecko/20070709 SeaMonkey/1.1.2 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= , Petr Holub , Kostik Belousov , current@freebsd.org References: <031f01c809ef$c829de80$5317fb93@KLOBOUCEK> <86641fgrs6.fsf@ds4.des.no> <20071010112505.GA28273@eos.sc1.parodius.com> In-Reply-To: <20071010112505.GA28273@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: Subject: Re: panic on boot 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, 10 Oct 2007 13:34:51 -0000 Jeremy Chadwick wrote: > On Wed, Oct 10, 2007 at 12:58:33PM +0200, Dag-Erling Smørgrav wrote: >> "Petr Holub" writes: >>> Despite you couldn't guarantee it, it really helped and it boots now. >>> I've used the binary loader available from ~kib site and just replaced >>> it on the original ISO: mdcondifig -> mount -> >>> tar cf - | (cd elswhere && tar xvpf -) -> replace the loader -> mkisomages.sh >> You realize that you can simply 'tar xf' an ISO image, instead of >> jumping through hoops with mdconfig? > > Most FreeBSD users I know of (junior and senior) do not know about > libarchive(3), nor what's linked to it (tar). Heck, even *I* didn't > know it had ISO9660 and ZIP support until I read the manpage; I thought > it was limited to tar, pax, and cpio archives. > Holly god (or whatever serves). 25 years in CS, started with punch cards and learning every day. Great day. Thanks DES. RN. IaM From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 13:40: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 EBA0E16A418; Wed, 10 Oct 2007 13:40:08 +0000 (UTC) (envelope-from jhary@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:1f1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 790FE13C45A; Wed, 10 Oct 2007 13:40:08 +0000 (UTC) (envelope-from jhary@unsane.co.uk) Received: from prawn.unsane.co.uk (150.117-84-212.staticip.namesco.net [212.84.117.150]) (authenticated bits=0) by unsane.co.uk (8.14.0/8.14.0) with ESMTP id l9ADeiIk040652 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Oct 2007 14:40:45 +0100 (BST) (envelope-from jhary@unsane.co.uk) Message-ID: <470CD62E.6040101@unsane.co.uk> Date: Wed, 10 Oct 2007 14:39:58 +0100 From: Vince User-Agent: Thunderbird 2.0.0.6 (X11/20070816) MIME-Version: 1.0 To: Peter van Heusden References: <470CCBB6.3050506@sanbi.ac.za> In-Reply-To: <470CCBB6.3050506@sanbi.ac.za> X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-java@freebsd.org Subject: Re: Which java jdk to use on -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: Wed, 10 Oct 2007 13:40:09 -0000 Peter van Heusden wrote: > Hi > > I am having trouble getting a working jdk on -CURRENT. Thus far, I have > diablo-jdk-1.5.0.07.01_7 installed, but it is dumping core in various > circumstances - for instance when used as part of OpenOffice, trying to > run Sun Download Manager, etc. I have tried installing the java/jdk16 > port, but got this: > > > I'm not sure where to turn at this point - is there a known "good" JDK > which works with -CURRENT (on x86)? > I have jdk-1.5.0.12p6,1 built from source using the diablo package as a bootstrap. at the time i needed CFLAGS=-O2 -fno-tree-vrp -pipe in my make.conf, not sure if i still would though. I have the package for it somewhere although I dont think i'm allowed to distribute it ;) Vince > Thanks, > Peter > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 13:42: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 9E1D116A4D6 for ; Wed, 10 Oct 2007 13:42:16 +0000 (UTC) (envelope-from biancalana@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.freebsd.org (Postfix) with ESMTP id 73CBA13C505 for ; Wed, 10 Oct 2007 13:42:08 +0000 (UTC) (envelope-from biancalana@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so393345pyb for ; Wed, 10 Oct 2007 06:42:07 -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=mqz6wXxBblNBCAIlGjf5bwwD0Z+Yi36cy4U8xEEqHrM=; b=c0D8jbSsHPe9yaFGXfXqBK6u3vW0ynEqKOoc6msDESTOdsl0Rf/hgiNRLumV/Tb/X5TLp6+cycJF3G2ElRwwvYMbqq+yLsFIwxM3kBEO+JNPsZIcJqhSpF+qgeP7tWn4m+EKohKkL3xYoddI35TpEMJM63cvbfOsV7aQHeRlpM4= 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=G/ftxjyzYcf5EXBBnmwW//xiNsTfNeYvmGq37CCLJzHELfyvhS7OPjkYd8PtYJ9Mghq3k8XLQAxUIy+icndr1Q0msOnRTFIiNMOFtl7HwgQ7XuH/ui2eILa1h9g6AZgi2iDe3Dtwtf/BtD41KcmOEkSJVK7xlMtyWXhVxp8p224= Received: by 10.65.53.3 with SMTP id f3mr1571119qbk.1192023726904; Wed, 10 Oct 2007 06:42:06 -0700 (PDT) Received: by 10.64.184.9 with HTTP; Wed, 10 Oct 2007 06:42:06 -0700 (PDT) Message-ID: <8e10486b0710100642qe4991a8w4dd1d06dd4bbb45@mail.gmail.com> Date: Wed, 10 Oct 2007 10:42:06 -0300 From: "Alexandre Biancalana" To: "=?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?=" , "Petr Holub" , "Kostik Belousov" , current@freebsd.org In-Reply-To: <20071010112505.GA28273@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <031f01c809ef$c829de80$5317fb93@KLOBOUCEK> <86641fgrs6.fsf@ds4.des.no> <20071010112505.GA28273@eos.sc1.parodius.com> Cc: Subject: Re: panic on boot 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, 10 Oct 2007 13:42:16 -0000 On 10/10/07, Jeremy Chadwick wrote: > On Wed, Oct 10, 2007 at 12:58:33PM +0200, Dag-Erling Sm=F8rgrav wrote: > > "Petr Holub" writes: > > > Despite you couldn't guarantee it, it really helped and it boots now. > > > I've used the binary loader available from ~kib site and just replace= d > > > it on the original ISO: mdcondifig -> mount -> > > > tar cf - | (cd elswhere && tar xvpf -) -> replace the loader -> mkiso= mages.sh > > > > You realize that you can simply 'tar xf' an ISO image, instead of > > jumping through hoops with mdconfig? > > Most FreeBSD users I know of (junior and senior) do not know about > libarchive(3), nor what's linked to it (tar). Heck, even *I* didn't > know it had ISO9660 and ZIP support until I read the manpage; I thought > it was limited to tar, pax, and cpio archives. One more... I doesn't know too !! Question: If "our" tar can handle .zip file why unzip is installed via ports to decompress some .zip files ??? From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 13:45: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 8FCFC16A46D; Wed, 10 Oct 2007 13:45:03 +0000 (UTC) (envelope-from alex.kovalenko@verizon.net) Received: from vms048pub.verizon.net (vms048pub.verizon.net [206.46.252.48]) by mx1.freebsd.org (Postfix) with ESMTP id 734BE13C478; Wed, 10 Oct 2007 13:45:03 +0000 (UTC) (envelope-from alex.kovalenko@verizon.net) Received: from [10.0.3.231] ([70.21.163.71]) by vms048.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JPP003CR7IPHDD8@vms048.mailsrvcs.net>; Wed, 10 Oct 2007 08:44:50 -0500 (CDT) Date: Wed, 10 Oct 2007 09:44:47 -0400 From: "Alexandre \"Sunny\" Kovalenko" In-reply-to: <470CCBB6.3050506@sanbi.ac.za> To: Peter van Heusden Message-id: <1192023887.1022.9.camel@RabbitsDen> MIME-version: 1.0 X-Mailer: Evolution 2.10.3 FreeBSD GNOME Team Port Content-type: text/plain Content-transfer-encoding: 7bit References: <470CCBB6.3050506@sanbi.ac.za> Cc: freebsd-current@freebsd.org, freebsd-java@freebsd.org Subject: Re: Which java jdk to use on -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: Wed, 10 Oct 2007 13:45:03 -0000 On Wed, 2007-10-10 at 14:55 +0200, Peter van Heusden wrote: > Hi > > I am having trouble getting a working jdk on -CURRENT. Thus far, I have > diablo-jdk-1.5.0.07.01_7 installed, but it is dumping core in various > circumstances - for instance when used as part of OpenOffice, trying to > run Sun Download Manager, etc. I have tried installing the java/jdk16 > port, but got this: > > Packing > /usr/ports/java/jdk16/work/control/build/bsd-i586/j2re-image/lib/rt.jar > 47602320 bytes > Exception in thread "main" java.lang.AssertionError > at > com.sun.java.util.jar.pack.ClassReader.readRef(ClassReader.java:90) > at > com.sun.java.util.jar.pack.ClassReader.readUtf8Ref(ClassReader.java:102) > at > com.sun.java.util.jar.pack.ClassReader.readMember(ClassReader.java:306) > at > com.sun.java.util.jar.pack.ClassReader.readMembers(ClassReader.java:300) > at com.sun.java.util.jar.pack.ClassReader.read(ClassReader.java:126) > at > com.sun.java.util.jar.pack.PackerImpl$DoPack.readClass(PackerImpl.java:490) > at > com.sun.java.util.jar.pack.PackerImpl$DoPack.run(PackerImpl.java:464) > at com.sun.java.util.jar.pack.PackerImpl.pack(PackerImpl.java:73) > at com.sun.java.util.jar.pack.Driver.main(Driver.java:261) > gmake[3]: *** [pack-jars] Error 1 > gmake[3]: Leaving directory `/usr/ports/java/jdk16/work/install/make/pack' > gmake[2]: *** [pack-jre] Error 2 > gmake[2]: Leaving directory `/usr/ports/java/jdk16/work/install/make/pack' > gmake[1]: *** [all] Error 1 > gmake[1]: Leaving directory `/usr/ports/java/jdk16/work/install/make' > gmake: *** [install-build] Error 2 > *** Error code 2 > > Stop in /usr/ports/java/jdk16. > *** Error code 1 > > Stop in /usr/ports/java/jdk16. > > and for the java/jdk15 port, I get this: > > ../../../../../src/share/classes/java/nio/Bits.java:19: duplicate class: > Bits > class Bits { // package-private > ^ > ../../../../../src/solaris/classes/sun/net/www/protocol/file/Handler.java:26: > duplicate class: Handler > public class Handler extends URLStreamHandler { > ^ > ../../../../../src/share/classes/java/lang/Class.java:10: cannot access > java.lang.reflect.Array > bad class file: > ../../../../../src/share/classes/java/lang/reflect/Array.java > file does not contain class java.lang.reflect.Array > Please remove or make sure it appears in the correct subdirectory of the > classpath. > import java.lang.reflect.Array; > ^ > 3 errors > gmake[7]: *** [.compile.classlist] Error 1 > gmake[7]: Leaving directory > `/usr/ports/java/jdk15/work/j2se/make/sun/javac/recompile/library' > gmake[6]: *** [optimized] Error 2 > gmake[6]: Leaving directory > `/usr/ports/java/jdk15/work/j2se/make/sun/javac/recompile/library' > gmake[5]: *** [all] Error 1 > gmake[5]: Leaving directory > `/usr/ports/java/jdk15/work/j2se/make/sun/javac/recompile' > gmake[4]: *** [all] Error 1 > gmake[4]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/sun/javac' > gmake[3]: *** [all] Error 2 > gmake[3]: Leaving directory > `/usr/ports/java/jdk15/work/j2se/make/java/javac' > gmake[2]: *** [all] Error 1 > gmake[2]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/java' > gmake[1]: *** [all] Error 1 > gmake[1]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make' > gmake: *** [j2se-build] Error 2 > *** Error code 2 > > Stop in /usr/ports/java/jdk15. > *** Error code 1 > > Stop in /usr/ports/java/jdk15. > > I'm not sure where to turn at this point - is there a known "good" JDK > which works with -CURRENT (on x86)? I think you might want to add CFLAGS+=-fno-tree-vrp to your /etc/make.conf After doing this, I have successfully built and use: jdk-1.3.1p9_8 Java Development Kit 1.3 jdk-1.6.0.1p1_5 Java Development Kit 1.6.0 My system is: sunny:RabbitsDen>uname -a FreeBSD RabbitsDen.RabbitsLawn.verizon.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Sun Sep 30 11:54:51 EDT 2007 root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60 i386 > > Thanks, > Peter > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Alexandre "Sunny" Kovalenko From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 14:05: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 2CA1516A418 for ; Wed, 10 Oct 2007 14:05:48 +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 1D21A13C458 for ; Wed, 10 Oct 2007 14:05: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 D6F6D20C1; Wed, 10 Oct 2007 16:05:37 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id C6CDD20AE; Wed, 10 Oct 2007 16:05:37 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id AF10684485; Wed, 10 Oct 2007 16:05:37 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "Alexandre Biancalana" References: <031f01c809ef$c829de80$5317fb93@KLOBOUCEK> <86641fgrs6.fsf@ds4.des.no> <20071010112505.GA28273@eos.sc1.parodius.com> <8e10486b0710100642qe4991a8w4dd1d06dd4bbb45@mail.gmail.com> Date: Wed, 10 Oct 2007 16:05:37 +0200 In-Reply-To: <8e10486b0710100642qe4991a8w4dd1d06dd4bbb45@mail.gmail.com> (Alexandre Biancalana's message of "Wed\, 10 Oct 2007 10\:42\:06 -0300") Message-ID: <86y7ebdpzi.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: Petr Holub , Kostik Belousov , current@freebsd.org Subject: Re: panic on boot 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, 10 Oct 2007 14:05:48 -0000 "Alexandre Biancalana" writes: > If "our" tar can handle .zip file why unzip is installed via ports to > decompress some .zip files ??? inertia, I guess... send patches! :) DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 14:15:07 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 5924416A419 for ; Wed, 10 Oct 2007 14:15:07 +0000 (UTC) (envelope-from marc@blackend.org) Received: from abigail.blackend.org (ns0.blackend.org [82.227.222.164]) by mx1.freebsd.org (Postfix) with ESMTP id C627813C45B for ; Wed, 10 Oct 2007 14:15:06 +0000 (UTC) (envelope-from marc@blackend.org) Received: from gothic.blackend.org (gothic.blackend.org [192.168.1.203]) by abigail.blackend.org (8.13.4/8.13.3) with ESMTP id l9AEEsJZ071405; Wed, 10 Oct 2007 16:14:54 +0200 (CEST) (envelope-from marc@abigail.blackend.org) Received: from gothic.blackend.org (localhost [127.0.0.1]) by gothic.blackend.org (8.14.1/8.14.1) with ESMTP id l9AEEslK022178; Wed, 10 Oct 2007 16:14:54 +0200 (CEST) (envelope-from marc@gothic.blackend.org) Received: (from marc@localhost) by gothic.blackend.org (8.14.1/8.14.1/Submit) id l9AEEmJG022177; Wed, 10 Oct 2007 16:14:49 +0200 (CEST) (envelope-from marc) Date: Wed, 10 Oct 2007 16:14:48 +0200 From: Marc Fonvieille To: Jeff Roberson Message-ID: <20071010141448.GC1037@gothic.blackend.org> References: <4707CF8D.3070303@u.washington.edu> <20071006191014.GB84780@abigail.blackend.org> <20071007012049.S912@10.0.0.1> <20071007013342.D912@10.0.0.1> <20071007095408.GA997@gothic.blackend.org> <20071007045911.Y912@10.0.0.1> <20071007130929.GA1132@gothic.blackend.org> <20071007114345.E912@10.0.0.1> <20071008142721.GB22255@gothic.blackend.org> <20071008143107.GC22255@gothic.blackend.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071008143107.GC22255@gothic.blackend.org> X-Useless-Header: blackend.org X-Operating-System: FreeBSD 7.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: current@freebsd.org Subject: Re: ULE/yielding patch for testing. 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, 10 Oct 2007 14:15:07 -0000 On Mon, Oct 08, 2007 at 04:31:07PM +0200, Marc Fonvieille wrote: > > > > but still a slightly higher than on 6.X, but I'm still experiencing > > slowdown of webpage rendering during compilation. > > > With -CURRENT from yesterday, the things seem to be really better. Thanks a lot for all your efforts. -- Marc From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 14:17:27 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 B6CF316A419 for ; Wed, 10 Oct 2007 14:17:27 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id 3D6AF13C4B5 for ; Wed, 10 Oct 2007 14:17:27 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from c83-253-31-60.bredband.comhem.se ([83.253.31.60]:58198 helo=falcon.midgard.homeip.net) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1Ifc8l-0001b5-3o for current@freebsd.org; Wed, 10 Oct 2007 16:02:23 +0200 Received: (qmail 40197 invoked from network); 10 Oct 2007 16:02:19 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 10 Oct 2007 16:02:19 +0200 Received: (qmail 81995 invoked by uid 1001); 10 Oct 2007 16:02:19 +0200 Date: Wed, 10 Oct 2007 16:02:19 +0200 From: Erik Trulsson To: Alexandre Biancalana Message-ID: <20071010140219.GA81895@owl.midgard.homeip.net> Mail-Followup-To: Alexandre Biancalana , Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= , Petr Holub , Kostik Belousov , current@freebsd.org References: <031f01c809ef$c829de80$5317fb93@KLOBOUCEK> <86641fgrs6.fsf@ds4.des.no> <20071010112505.GA28273@eos.sc1.parodius.com> <8e10486b0710100642qe4991a8w4dd1d06dd4bbb45@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <8e10486b0710100642qe4991a8w4dd1d06dd4bbb45@mail.gmail.com> User-Agent: Mutt/1.5.16 (2007-06-09) X-Originating-IP: 83.253.31.60 X-Scan-Result: No virus found in message 1Ifc8l-0001b5-3o. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1Ifc8l-0001b5-3o 865c489255ab161eb791bd24ff237653 Cc: Petr Holub , Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= , Kostik Belousov , current@freebsd.org Subject: Re: panic on boot 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, 10 Oct 2007 14:17:27 -0000 On Wed, Oct 10, 2007 at 10:42:06AM -0300, Alexandre Biancalana wrote: > On 10/10/07, Jeremy Chadwick wrote: > > On Wed, Oct 10, 2007 at 12:58:33PM +0200, Dag-Erling Sm=F8rgrav wrote: > > > "Petr Holub" writes: > > > > Despite you couldn't guarantee it, it really helped and it boots no= w. > > > > I've used the binary loader available from ~kib site and just repla= ced > > > > it on the original ISO: mdcondifig -> mount -> > > > > tar cf - | (cd elswhere && tar xvpf -) -> replace the loader -> mki= somages.sh > > > > > > You realize that you can simply 'tar xf' an ISO image, instead of > > > jumping through hoops with mdconfig? > > > > Most FreeBSD users I know of (junior and senior) do not know about > > libarchive(3), nor what's linked to it (tar). Heck, even *I* didn't > > know it had ISO9660 and ZIP support until I read the manpage; I thought > > it was limited to tar, pax, and cpio archives. >=20 > One more... I doesn't know too !! >=20 > Question: >=20 > If "our" tar can handle .zip file why unzip is installed via ports to > decompress some .zip files ??? Keep in mind that "our" tar was only included with FreeBSD from FreeBSD 5.3 and onwards. Support for .zip files was added for FreeBSD 5.4. For older releases of FreeBSD it is necessary to install unzip. It is probably also the case that several of the people working on the ports tree also hadn't noticed that tar had grown support for .zip files. --=20 Erik Trulsson ertr1013@student.uu.se From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 14:18: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 6F78316A46E for ; Wed, 10 Oct 2007 14:18:10 +0000 (UTC) (envelope-from bp@barryp.org) Received: from eden.barryp.org (host-42-60-230-24.midco.net [24.230.60.42]) by mx1.freebsd.org (Postfix) with ESMTP id 4525513C4EB for ; Wed, 10 Oct 2007 14:18:09 +0000 (UTC) (envelope-from bp@barryp.org) Received: from geo.med.und.nodak.edu ([134.129.166.11]) by eden.barryp.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67 (FreeBSD)) (envelope-from ) id 1IfcNz-000A8o-Mn; Wed, 10 Oct 2007 09:18:08 -0500 Message-ID: <470CDF1D.5050707@barryp.org> Date: Wed, 10 Oct 2007 09:18:05 -0500 From: Barry Pederson User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: Martin Nilsson References: <46A7B47F.3050300@berkeley.edu> <46A7B607.2070207@samsco.org> <20070927010139.GC22695@eschew.pusen.org> <46FF4E9B.3080104@gneto.com> In-Reply-To: <46FF4E9B.3080104@gneto.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Wed, 10 Oct 2007 14:18:10 -0000 Martin Nilsson wrote: > Hi, > > Have you looked at the Supermicro CSE-836E1 chassis? > http://www.supermicro.com/products/chassis/3U/836/SC836E1-R800V.cfm > > It is also 3U but have space for 16 drives redundant power and the > computer! The port expander works with the LSI MegaRAID SAS8308ELP board > and SAS/SATA drives in FreeBSD. There is also a cheaper model available > with 16 normal SATA connectors if you prefer that. I've been pondering this chassis too, and have been wondering how the FreeBSD mpt driver would react to the builtin SAS expander. I've been using SAS3041E-R cards (cheaper than the MegaRAIDs) with drives plugged straight into them very happily. Would that same 4-port card plugged into a that chassis' expander simply see 16 sata drives as da0..da15? It looks like these chassis actually have 28-port expanders, with 4 ports going in, 16 ports for drives, and 2 4-port groups for daisy-chaining other chassis. Any idea if another connected chassis full of drives would just show up as da16..da31 and so on? Barry From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 14:20: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 3330216A41B for ; Wed, 10 Oct 2007 14:20:16 +0000 (UTC) (envelope-from news@nermal.rz1.convenimus.net) Received: from mx3.netclusive.de (mx3.netclusive.de [89.110.132.133]) by mx1.freebsd.org (Postfix) with ESMTP id C4AB113C447 for ; Wed, 10 Oct 2007 14:20:15 +0000 (UTC) (envelope-from news@nermal.rz1.convenimus.net) Received: from nermal.rz1.convenimus.net (Fdc93.f.ppp-pool.de [195.4.220.147]) (Authenticated sender: ncf1534p2) by mx3.netclusive.de (Postfix) with ESMTP id D97D8604C1C for ; Wed, 10 Oct 2007 15:59:39 +0200 (CEST) Received: by nermal.rz1.convenimus.net (Postfix, from userid 8) id 98C7F15217; Wed, 10 Oct 2007 15:52:14 +0200 (CEST) To: freebsd-current@freebsd.org Path: not-for-mail From: Christian Baer Newsgroups: gmane.os.freebsd.current Date: Wed, 10 Oct 2007 15:52:14 +0200 (CEST) Organization: Convenimus Projekt Lines: 58 Message-ID: NNTP-Posting-Host: sunny.rz1.convenimus.net X-Trace: nermal.rz1.convenimus.net 1192024334 88189 192.168.100.5 (10 Oct 2007 13:52:14 GMT) X-Complaints-To: abuse@convenimus.net NNTP-Posting-Date: Wed, 10 Oct 2007 13:52:14 +0000 (UTC) User-Agent: slrn/0.9.8.1 (FreeBSD/6.2-RELEASE-p8 (sparc64)) Subject: suggest renaming and extending the -CURRENT and -STABLE lines 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, 10 Oct 2007 14:20:16 -0000 Hello people! Before you all bang around on my head :-) hear me out on this one. It's actually possible that someone has already made this suggestion and I haven't found that thread yet. If so, please point me in the right direction and I'll read up on it, before writing in this thread again. In computer science and mathematics, we sometimes use terms from the "normal" language but use them just a little differently than people outside of our circle would. Sometimes that is unavoidable because our language is just doesn't have enough words to express our thoughts - and to express them exactly. This is usually not much of a problem. However, sometimes we have to communicate with others, who may use our products and ideas but don't embrace our language. As the subject of this thread already suggests, I am referring to the names of the developement branches, which I (even as a computer scientist) consider a little "strange". If someone sees the result of RELENG_6 is called STABLE, he or she will problably think, this is the line where bug fixes are added, security problems fixed and the whole thing is meant for production systems. While the first two things may be true, I would not suggest RELENG_6 for production systems. Normally the -STABLE line works fine. But I *have* times in the past where a driver was changes and suddenly the system *didn't* work after a reboot or showed strange behaviour. What you could (and should?) use for a production system is RELENG_6_2. I am using that, as you can see in the header. :-) Although the handbook titles RELENG_6 as "staying stable...", people are warned not to use it on production systems (which seems strange for something called "stable") while RELENG_6_x isn't even mentioned. What I propose is this: When we have FreeBSD 7.0-RELEASE, we change these things a little. - What is -CURRENT now stays -CURRENT (then probably 8-CURRENT). - RELENG_7 is also called -CURRENT (7.x-CURRENT) - RELENG_7_x could be called 7.x-RELEASE-px (see below) Additionally, I suggest adding a new target. What we numbers we put at the end of the RELENG_ isn't too important at the moment. This would be the new -STABLE brach - and would deserve the name. It would point to the current release and the newest patch. So basicly, if I started at 6.2-RELEASE, it would have brought me through all the patches of that release and will update to 6.2-RELEASE once that is out and so on. I realize that this is somewhat of a change and also that progress is always frowned upon. :-) But IMHO it is a step in the right direction into the right direction because it removes a word that can easily be misunderstood - even by a user who isn't a complete beginner. I'd like your thoughts about this and maybe we can work something out that isn't exactly my idea but will work for the public. Regards Chris From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 14:40: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 7DEC816A421 for ; Wed, 10 Oct 2007 14:40:11 +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 39DF313C4AA for ; Wed, 10 Oct 2007 14:40:11 +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 9402020BF; Wed, 10 Oct 2007 16:39:59 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 8718920BC; Wed, 10 Oct 2007 16:39:59 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id 70C2D84483; Wed, 10 Oct 2007 16:39:59 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Christian Baer References: Date: Wed, 10 Oct 2007 16:39:59 +0200 In-Reply-To: (Christian Baer's message of "Wed\, 10 Oct 2007 15\:52\:14 +0200 \(CEST\)") Message-ID: <86przndoe8.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: suggest renaming and extending the -CURRENT and -STABLE lines 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, 10 Oct 2007 14:40:11 -0000 Christian Baer writes: > If someone sees the result of RELENG_6 is called STABLE, he or she will > problably think, this is the line where bug fixes are added, security > problems fixed and the whole thing is meant for production systems. While > the first two things may be true, I would not suggest RELENG_6 for > production systems. Normally the -STABLE line works fine. But I *have* > times in the past where a driver was changes and suddenly the system > *didn't* work after a reboot or showed strange behaviour. YMMV. I run both CURRENT and STABLE on production systems. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 15:04: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 4496216A418 for ; Wed, 10 Oct 2007 15:04:20 +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 D155013C458 for ; Wed, 10 Oct 2007 15:04:19 +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 l9AF3rLu033925; Wed, 10 Oct 2007 09:03:54 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <470CE9C2.4060300@samsco.org> Date: Wed, 10 Oct 2007 09:03:30 -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: Barry Pederson References: <46A7B47F.3050300@berkeley.edu> <46A7B607.2070207@samsco.org> <20070927010139.GC22695@eschew.pusen.org> <46FF4E9B.3080104@gneto.com> <470CDF1D.5050707@barryp.org> In-Reply-To: <470CDF1D.5050707@barryp.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Wed, 10 Oct 2007 09:03:54 -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: 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: Wed, 10 Oct 2007 15:04:20 -0000 Barry Pederson wrote: > Martin Nilsson wrote: >> Hi, >> >> Have you looked at the Supermicro CSE-836E1 chassis? >> http://www.supermicro.com/products/chassis/3U/836/SC836E1-R800V.cfm >> >> It is also 3U but have space for 16 drives redundant power and the >> computer! The port expander works with the LSI MegaRAID SAS8308ELP >> board and SAS/SATA drives in FreeBSD. There is also a cheaper model >> available with 16 normal SATA connectors if you prefer that. > > I've been pondering this chassis too, and have been wondering how the > FreeBSD mpt driver would react to the builtin SAS expander. I've been > using SAS3041E-R cards (cheaper than the MegaRAIDs) with drives plugged > straight into them very happily. Would that same 4-port card plugged > into a that chassis' expander simply see 16 sata drives as da0..da15? > > It looks like these chassis actually have 28-port expanders, with 4 > ports going in, 16 ports for drives, and 2 4-port groups for > daisy-chaining other chassis. Any idea if another connected chassis > full of drives would just show up as da16..da31 and so on? > There are two possible scenarios here, first is that the controller does a full topology scan and presents the drives to the OS with no OS intervention. Second is that it doesn't do a full scan, and instead presents only the drives that are directly attached. Given that the Linux driver does full discovery itself, I kind of suspect that the latter behavior is what will happen. Full SAS support is on my immediate TODO list, but it's a fairly big project. Scott From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 15:14: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 886B316A417 for ; Wed, 10 Oct 2007 15:14:31 +0000 (UTC) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (gerbercreations.com [71.39.140.16]) by mx1.freebsd.org (Postfix) with ESMTP id 7AEEF13C478 for ; Wed, 10 Oct 2007 15:14:30 +0000 (UTC) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (localhost.eyesbeyond.com [127.0.0.1]) by misty.eyesbeyond.com (8.13.1/8.13.3) with ESMTP id l9AEjV5w003199; Wed, 10 Oct 2007 07:45:31 -0700 (PDT) (envelope-from glewis@eyesbeyond.com) Received: (from glewis@localhost) by misty.eyesbeyond.com (8.13.1/8.13.3/Submit) id l9AEjUxZ003198; Wed, 10 Oct 2007 07:45:30 -0700 (PDT) (envelope-from glewis@eyesbeyond.com) X-Authentication-Warning: misty.eyesbeyond.com: glewis set sender to glewis@eyesbeyond.com using -f Date: Wed, 10 Oct 2007 07:45:29 -0700 From: Greg Lewis To: Peter van Heusden Message-ID: <20071010144529.GA3164@misty.eyesbeyond.com> References: <470CCBB6.3050506@sanbi.ac.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <470CCBB6.3050506@sanbi.ac.za> User-Agent: Mutt/1.4.2.2i Cc: freebsd-current@freebsd.org, freebsd-java@freebsd.org Subject: Re: Which java jdk to use on -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: Wed, 10 Oct 2007 15:14:31 -0000 On Wed, Oct 10, 2007 at 02:55:18PM +0200, Peter van Heusden wrote: > I am having trouble getting a working jdk on -CURRENT. Thus far, I have > diablo-jdk-1.5.0.07.01_7 installed, but it is dumping core in various > circumstances - for instance when used as part of OpenOffice, trying to > run Sun Download Manager, etc. I have tried installing the java/jdk16 > port, but got this: Diablo is just having some problems on -CURRENT. It seems like 6.x applications aren't fully compatible or some of the uses its being put do aren't fully compatible (e.g. you can't use Diablo with another native application that has its own 7.x shared libraries and expect things to work). For jdk16 and jdk15 you either need -fno-tree-vrp as others have mentioned or you should update to a more recent -CURRENT which should have this turned on by default. -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 15:36: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 4D08C16A41B for ; Wed, 10 Oct 2007 15:36:29 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from crivens.terrorteam.de (crivens.terrorteam.de [81.169.171.191]) by mx1.freebsd.org (Postfix) with ESMTP id 09F8413C4B3 for ; Wed, 10 Oct 2007 15:36:28 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from localhost (localhost [127.0.0.1]) by crivens.terrorteam.de (Postfix) with ESMTP id D53C0B023F; Wed, 10 Oct 2007 17:08:47 +0200 (CEST) MIME-Version: 1.0 Date: Wed, 10 Oct 2007 17:08:47 +0200 From: Marian Hettwer To: =?UTF-8?Q?Dag-Erling=20Sm=C3=83=C2=B8rgrav=20 , ?=@terrorteam.de In-Reply-To: <86przndoe8.fsf@ds4.des.no> References: <86przndoe8.fsf@ds4.des.no> Message-ID: <6aefb8ae4a2de897081a2792cdc17ea1@127.0.0.1> X-Sender: mh@kernel32.de User-Agent: RoundCube Webmail/0.1b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org, Christian Baer Subject: Re: suggest renaming and extending the -CURRENT and -STABLE lines 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, 10 Oct 2007 15:36:29 -0000 On Wed, 10 Oct 2007 16:39:59 +0200, Dag-Erling Smørgrav wrote: > Christian Baer writes: >> If someone sees the result of RELENG_6 is called STABLE, he or she will >> problably think, this is the line where bug fixes are added, security >> problems fixed and the whole thing is meant for production systems. > While >> the first two things may be true, I would not suggest RELENG_6 for >> production systems. Normally the -STABLE line works fine. But I *have* >> times in the past where a driver was changes and suddenly the system >> *didn't* work after a reboot or showed strange behaviour. > > YMMV. I run both CURRENT and STABLE on production systems. > Which is higly interesting and important and has basically nothing to do with the original mail / question by the original author ;-) Back to topic? The problem is, that STABLE in FreeBSD-speak is meant as API Stable, not stable in regards to a broken driver or in regards to a branch where the source is frozen. However, I do agree with the original author that it leads to confusion, because API stabilitiy is not the first thing that pops into your mind when you read FreeBSD 6-STABLE ;-) I tend to believe that a renaming won't happen, though. AFAIK the naming convention in FreeBSD haven't changed since... well... forever? ;) It may became something like a holy cow :) My thoughts. Cheers, Marian PS.: I managed to run CURRENT from yesterday on a IBM HS21 Blade with this bloody mpt(4) and bce(4) chipsets. It works! Thumbs Up! The bce(4) was panicing in earlier CURRENTs I tried :) From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 15:57: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 0AC2016A417 for ; Wed, 10 Oct 2007 15:57:56 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id A8A8213C46A for ; Wed, 10 Oct 2007 15:57:55 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: by blah.sun-fish.com (Postfix, from userid 1002) id E077C1B10ED2; Wed, 10 Oct 2007 17:57:53 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on blah.cmotd.com X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.3 Received: from hater.haters.org (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id A172B1B10E0D; Wed, 10 Oct 2007 17:57:51 +0200 (CEST) Message-ID: <470CF67F.2020907@moneybookers.com> Date: Wed, 10 Oct 2007 18:57:51 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.6 (X11/20070918) MIME-Version: 1.0 To: Christian Baer References: In-Reply-To: Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91.2/4521/Wed Oct 10 09:58:01 2007 on blah.cmotd.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: suggest renaming and extending the -CURRENT and -STABLE lines 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, 10 Oct 2007 15:57:56 -0000 Hello, Christian Baer wrote: > Hello people! > > Before you all bang around on my head :-) hear me out on this one. It's > actually possible that someone has already made this suggestion and I > haven't found that thread yet. If so, please point me in the right > direction and I'll read up on it, before writing in this thread again. > This was discussed many times in -stable mail list (and probably on few others?) Anyway STABLE means stable API, so programs compiled on 6.2-RELEASE should work on 6.2-STABLE You can look for "ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!" - very long thread, but normally when something broke in -stable this thread start and start again. P.S. for me STABLE is very stable, and current CURRENT is even more stable (at least on new hardware), and I have both in production. -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 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 E4AB716A418 for ; Wed, 10 Oct 2007 16:36:23 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.188]) by mx1.freebsd.org (Postfix) with ESMTP id 5773C13C46E for ; Wed, 10 Oct 2007 16:36:23 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: by fk-out-0910.google.com with SMTP id b27so267602fka for ; Wed, 10 Oct 2007 09:36:22 -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=ksMi88jhB+Qs29gAzf39ArXmzNlA1wc1Ltg4J40mO4A=; b=BHLCtwo1pC0uUkCL5nZelgUGd2i7nqR0r+EtnEclCfLI4j0SD1Zz1ppRoUVOdDEi2KOKwMelEVYpVAKIu2GOsJELV9fvZLvzCXqSo4Ss0C9he9jUIAWu0vaQE9Ifuv1ftNbbJAtpu21UaIzMd3AlIWw+JsuhwNjQhu3O5YPqyrE= 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=PhA0Bxjl1lq0NDGrDbCzwrCWJYN+WhYiluE3saA1pX6SzQoh4ObnN0GS9froWDUxIvR6tpf9GKuJvbDCAFgbfcR4MbjolBmlTYyoyabb0FjktLxgl/CWI33Nvv6I68t229a7QXqiix4WgAakzh1i3NwQcdED/iXrbeFWaauFvTk= Received: by 10.82.181.10 with SMTP id d10mr1884980buf.1192034181427; Wed, 10 Oct 2007 09:36:21 -0700 (PDT) Received: from orion ( [89.162.141.1]) by mx.google.com with ESMTPS id 7sm5218018nfv.2007.10.10.09.36.18 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 10 Oct 2007 09:36:20 -0700 (PDT) From: Nikolay Pavlov To: freebsd-current@freebsd.org Date: Wed, 10 Oct 2007 19:36:11 +0300 User-Agent: KMail/1.9.7 References: <470CCBB6.3050506@sanbi.ac.za> <20071010144529.GA3164@misty.eyesbeyond.com> In-Reply-To: <20071010144529.GA3164@misty.eyesbeyond.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2785723.PubWroHSby"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200710101936.12827.qpadla@gmail.com> Cc: Greg Lewis , Peter van Heusden , freebsd-java@freebsd.org Subject: Re: Which java jdk to use on -CURRENT? 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: Wed, 10 Oct 2007 16:36:24 -0000 --nextPart2785723.PubWroHSby Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 10 October 2007 17:45:29 Greg Lewis wrote: > On Wed, Oct 10, 2007 at 02:55:18PM +0200, Peter van Heusden wrote: > > I am having trouble getting a working jdk on -CURRENT. Thus far, I > > have diablo-jdk-1.5.0.07.01_7 installed, but it is dumping core in > > various circumstances - for instance when used as part of OpenOffice, > > trying to run Sun Download Manager, etc. I have tried installing the > > java/jdk16 port, but got this: > > Diablo is just having some problems on -CURRENT. It seems like 6.x > applications aren't fully compatible or some of the uses its being put > do aren't fully compatible (e.g. you can't use Diablo with another > native application that has its own 7.x shared libraries and expect > things to work). > > For jdk16 and jdk15 you either need -fno-tree-vrp as others have > mentioned or you should update to a more recent -CURRENT which should > have this turned on by default. gcc-4.2.2 was released recently. Are there any tests results against the=20 ports tree with this bugfix release? There are to many ports marked as=20 broken with gcc-4.2.1.=20 =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 --nextPart2785723.PubWroHSby 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) iD8DBQBHDP98/2R6KvEYGaIRAtSBAJ9aMY+HNq/PJ4zN1XK9hMdmsIxmDACggCuV Mp3vmdao4M8LGw7Dy9HbW0s= =Cvg5 -----END PGP SIGNATURE----- --nextPart2785723.PubWroHSby-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 16:37: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 4289016A417 for ; Wed, 10 Oct 2007 16:37:28 +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 B955913C455 for ; Wed, 10 Oct 2007 16:37:27 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Ife0D-0002zy-JG for freebsd-current@freebsd.org; Wed, 10 Oct 2007 16:01:41 +0000 Received: from 78-1-111-250.adsl.net.t-com.hr ([78.1.111.250]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 10 Oct 2007 16:01:41 +0000 Received: from ivoras by 78-1-111-250.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 10 Oct 2007 16:01:41 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Wed, 10 Oct 2007 17:29:12 +0200 Lines: 44 Message-ID: References: <86przndoe8.fsf@ds4.des.no> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig410617FA8109077B471FD13C" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 78-1-111-250.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) In-Reply-To: <86przndoe8.fsf@ds4.des.no> X-Enigmail-Version: 0.95.3 Sender: news Subject: Re: suggest renaming and extending the -CURRENT and -STABLE lines 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, 10 Oct 2007 16:37:28 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig410617FA8109077B471FD13C Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dag-Erling Sm=C3=B8rgrav wrote: > Christian Baer writes: >> If someone sees the result of RELENG_6 is called STABLE, he or she wil= l >> problably think, this is the line where bug fixes are added, security >> problems fixed and the whole thing is meant for production systems. Wh= ile >> the first two things may be true, I would not suggest RELENG_6 for >> production systems. Normally the -STABLE line works fine. But I *have*= >> times in the past where a driver was changes and suddenly the system >> *didn't* work after a reboot or showed strange behaviour. >=20 > YMMV. I run both CURRENT and STABLE on production systems. And we'll find many other people on this newsgroup who do the same, but not everyone's a kernel hacker, or even a decent programmer, so it's kind of insignificant. This will probably degenerate into a bikeshed so I'll add just one suggestion: rename "-STABLE" to "-ABISTABLE" or "-STABLEABI" and carry on as usual. :) --------------enig410617FA8109077B471FD13C 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 iD8DBQFHDO/IldnAQVacBcgRAmEOAKCAcmPFKHFuGnZWhipasnP6RGrvHACggKCa 9bg8n0oo52+BEqvSt7XJEGQ= =XM2l -----END PGP SIGNATURE----- --------------enig410617FA8109077B471FD13C-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 16:40: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 B57B216A46B for ; Wed, 10 Oct 2007 16:40:49 +0000 (UTC) (envelope-from swhetzel@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 2B92D13C447 for ; Wed, 10 Oct 2007 16:40:48 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so225946nfb for ; Wed, 10 Oct 2007 09:40:47 -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=6HIVj5Sod+B+K5kCoFYCUpDfxBAIlyaH4UX3ACIcZCE=; b=swfZlJo9bNZPqD4XHkcjpC8dTU+EzYrvOxRv4vgCzxTJ10h/8tFSIkUVH6HpR0PKmaaDhZ4CiHoLKdZZbOLkV8u8AsC9puIk6/CzCLEaXEw5DfBUYudokzHFRBmEZkIEla33dxiLB8CS65WKRodE/y5coxgB0jgyK2Nsfu3RuNg= 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=to8rOSfjrItQRZGxjOLB/kvoJ7AfQZBfo7EMlZRctuDMbxqTur4dsMtL8dCD/X/BhKx9xR+C1PNbIPcOpen9SJKwzDNsjWRn4U3TNL62Ps85LEoXUVwaU9NBqe+NqThBHqe1GPzkZtCpRXy5UqLFxP5lr1jOzO82rvQiFBgGBsE= Received: by 10.86.73.17 with SMTP id v17mr705938fga.1192034447361; Wed, 10 Oct 2007 09:40:47 -0700 (PDT) Received: by 10.86.71.6 with HTTP; Wed, 10 Oct 2007 09:40:47 -0700 (PDT) Message-ID: <790a9fff0710100940v12539f86k3961d9009323fa1@mail.gmail.com> Date: Wed, 10 Oct 2007 11:40:47 -0500 From: "Scot Hetzel" To: "Christian Baer" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-current@freebsd.org Subject: Re: suggest renaming and extending the -CURRENT and -STABLE lines 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, 10 Oct 2007 16:40:49 -0000 On 10/10/07, Christian Baer wrote: > Hello people! > > Before you all bang around on my head :-) hear me out on this one. It's > actually possible that someone has already made this suggestion and I > haven't found that thread yet. If so, please point me in the right > direction and I'll read up on it, before writing in this thread again. > There was a thread on this a few years back when we only had the -CURRENT and -STABLE branches. The problem at that time was that when code was being back ported from -CURRENT to -STABLE it would break production machines that had been updated to the latest -STABLE code. The solution was to create the -STABLE security branches where only security and minor fixes were applied. > As the subject of this thread already suggests, I am referring to the > names of the developement branches, which I (even as a computer scientist) > consider a little "strange". > > If someone sees the result of RELENG_6 is called STABLE, he or she will > problably think, this is the line where bug fixes are added, security > problems fixed and the whole thing is meant for production systems. While > the first two things may be true, I would not suggest RELENG_6 for > production systems. Normally the -STABLE line works fine. But I *have* > times in the past where a driver was changes and suddenly the system > *didn't* work after a reboot or showed strange behaviour. > > What you could (and should?) use for a production system is RELENG_6_2. I > am using that, as you can see in the header. :-) Although the handbook > titles RELENG_6 as "staying stable...", people are warned not to use it on > production systems (which seems strange for something called "stable") > while RELENG_6_x isn't even mentioned. > The handbook needs a new section added to: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html which details what the -STABLE security branches (RELENG_x_y) are to be used for. : 23.2.2.2 Who Needs FreeBSD-STABLE? : 23.2.2.3 What are the FreeBSD-STABLE security branches? If you are interested in tracking the security of the current STABLE -RELEASE, then you should consider following the FreeBSD-STABLE security branch. The FreeBSD -STABLE security branches tracks only security and minor fixes relating to the currently supported STABLE -RELEASES. No major changes are made to these branches. Although we endeavor to ensure that the FreeBSD-STABLE security branch compiles and runs at all times, this cannot be guaranteed. We do not recommend that you blindly update any production servers to FreeBSD-STABLE security branch without first thoroughly testing the code in your development environment. To use the -STABLE security branch you need to check out the FreeBSD sources using the RELENG_x_y tag. 23.2.2.5 Using FreeBSD-STABLE : Scot From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 16:46: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 C641B16A419 for ; Wed, 10 Oct 2007 16:46:11 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from galain.elvandar.org (redqueen.elvandar.org [217.148.169.55]) by mx1.freebsd.org (Postfix) with ESMTP id 790F013C4A7 for ; Wed, 10 Oct 2007 16:46:11 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from evilcoder.xs4all.nl ([195.64.94.120] helo=elvandar.local) by galain.elvandar.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1IfehF-000EGw-Sr; Wed, 10 Oct 2007 18:46:09 +0200 Message-ID: <470D0214.9020508@FreeBSD.org> Date: Wed, 10 Oct 2007 18:47:16 +0200 From: Remko Lodder User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Nathan Butcher References: <20071009120010.833FE16A4D2@hub.freebsd.org> <470C6000.60902@fusiongol.com> In-Reply-To: <470C6000.60902@fusiongol.com> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: IDE compact flash reader FAILURE message 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, 10 Oct 2007 16:46:11 -0000 Nathan Butcher wrote: > This is not a big issue in CURRENT, or is even much of a priority I > feel, but I thought I'd ask about it anyway. > > I have a compact flash reader inserted into the IDE port on my > motherboard. It can host two compact flash cards. Currently I have an > 8GB 133x compact flash and an 8GB 266x compact flash (both Transcend) in > the slots. > > What I find interesting is that the 8GB 266x compact flash appears in > dmesg as such:- > > ad5: FAILURE - SET_MULTI status=51 error=4 > ad5: 7775MB at ata2-slave UDMA66 > > It seems like I can write to it anyway, but I haven't tried yet. > What's the reason for the FAILURE? I assume it has something to do with > the faster write speed on the card. > > _______________________________________________ Afair it's a ATA command to set some specific variables, since your flash drives are not ATA drives, they appear to not support it [which sounds correct]. Cheers remko -- Kind regards, Remko Lodder ** remko@elvandar.org FreeBSD ** remko@FreeBSD.org /* Quis custodiet ipsos custodes */ From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 17:36: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 A023B16A418 for ; Wed, 10 Oct 2007 17:36:07 +0000 (UTC) (envelope-from is@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.freebsd.org (Postfix) with ESMTP id 4C3A513C465 for ; Wed, 10 Oct 2007 17:36:07 +0000 (UTC) (envelope-from is@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id 0EF9AE607; Wed, 10 Oct 2007 21:36:06 +0400 (MSD) Received: from localhost (is1.park.rambler.ru [81.19.64.121]) by relay0.rambler.ru (Postfix) with ESMTP id DBF53CCB3; Wed, 10 Oct 2007 21:36:05 +0400 (MSD) Date: Wed, 10 Oct 2007 21:36:01 +0400 From: Igor Sysoev To: David G Lawrence Message-ID: <20071010173601.GB35652@rambler-co.ru> References: <20071009125001.GC5758@rambler-co.ru> <20071010055748.GA18931@rambler-co.ru> <20071010060605.GB18931@rambler-co.ru> <470C6DD4.1060509@mawer.org> <20071010062541.GA23840@rambler-co.ru> <20071010093436.GB2180@deviant.kiev.zoral.com.ua> <20071010095018.GA28123@rambler-co.ru> <20071010102756.GE56714@tnn.dglawrence.com> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20071010102756.GE56714@tnn.dglawrence.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: Kostik Belousov , freebsd-current@freebsd.org, Antony Mawer Subject: Re: sendfile and page usage statistics 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, 10 Oct 2007 17:36:07 -0000 On Wed, Oct 10, 2007 at 03:27:56AM -0700, David G Lawrence wrote: > > > But I think that the actual patch is wrong. The PG_REFERENCED bit shall > > > be set when hardware access bit is set on pte. You patch would set it in > > > advance. > > > > The problem is that ethernet card that does TX chsum, DMA and TSO never > > sets PG_A, so sendfile() should set it in advance. > > > > I'm going to test the patch on machine where all files takes more memory > > than physical memory and there are some popular files. > > > > I espect to see > > 1) increased active memory. > > 2) decreased number i/o. > > I would say that it is far from clear that this change would result in > better performance. It is generally the case in FreeBSD that we bias in > favor of executable pages (usually the image itself as its pages are > executed, but also the image data pages). Pages involved in regular file > I/O take a back seat. This is because a regular file is accessed typically > in one burst, whereas an executable page is accessed in small chunks over > a much larger period of time (and thus is affected more by a cache miss). > Thus, PG_REFERENCED gets set for pages that are mmaped, but not for > pages involved in read, write, sendfile, etc. Different workloads of > course will have different behavior. > One side effect of this will likely be much more system paging activity > as sendfile causes process pages to be pushed out of memory in favor of > cached file data. This is generally a bad thing and would result in reduced > interactive performance. The read() from file certainly updates vnode pages' PG_A/PG_REFERENCED, because coping to userland is made by CPU. I think write() does the same. I consider sendfile() as send() of mmap()ed file with the difference that user process does not see this mmap(). -- Igor Sysoev http://sysoev.ru/en/ From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 18:13: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 38F3F16A421 for ; Wed, 10 Oct 2007 18:13:01 +0000 (UTC) (envelope-from dg@dglawrence.com) Received: from dglawrence.com (static-72-90-113-2.ptldor.fios.verizon.net [72.90.113.2]) by mx1.freebsd.org (Postfix) with ESMTP id 024DE13C4A7 for ; Wed, 10 Oct 2007 18:13:00 +0000 (UTC) (envelope-from dg@dglawrence.com) Received: from tnn.dglawrence.com (localhost [127.0.0.1]) by dglawrence.com (8.14.1/8.14.1) with ESMTP id l9AID0Yv059413; Wed, 10 Oct 2007 11:13:00 -0700 (PDT) (envelope-from dg@dglawrence.com) Received: (from dg@localhost) by tnn.dglawrence.com (8.14.1/8.14.1/Submit) id l9AID0pR059412; Wed, 10 Oct 2007 11:13:00 -0700 (PDT) (envelope-from dg@dglawrence.com) X-Authentication-Warning: tnn.dglawrence.com: dg set sender to dg@dglawrence.com using -f Date: Wed, 10 Oct 2007 11:12:59 -0700 From: David G Lawrence To: Igor Sysoev Message-ID: <20071010181259.GF56714@tnn.dglawrence.com> References: <20071009125001.GC5758@rambler-co.ru> <20071010055748.GA18931@rambler-co.ru> <20071010060605.GB18931@rambler-co.ru> <470C6DD4.1060509@mawer.org> <20071010062541.GA23840@rambler-co.ru> <20071010093436.GB2180@deviant.kiev.zoral.com.ua> <20071010095018.GA28123@rambler-co.ru> <20071010102756.GE56714@tnn.dglawrence.com> <20071010173601.GB35652@rambler-co.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071010173601.GB35652@rambler-co.ru> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (dglawrence.com [127.0.0.1]); Wed, 10 Oct 2007 11:13:00 -0700 (PDT) Cc: Kostik Belousov , freebsd-current@freebsd.org, Antony Mawer Subject: Re: sendfile and page usage statistics 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, 10 Oct 2007 18:13:01 -0000 > The read() from file certainly updates vnode pages' PG_A/PG_REFERENCED, > because coping to userland is made by CPU. I think write() does the same. No, it does not. The kernel virtual mappings involved in that copy are "special"; page bits (PG_A, PG_M, etc) from those mapping are not preserved from the PTEs (at least not on x86). -DG David G. Lawrence President Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500 The FreeBSD Project - http://www.freebsd.org Pave the road of life with opportunities. From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 18:33: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 6F03416A419 for ; Wed, 10 Oct 2007 18:33:05 +0000 (UTC) (envelope-from chris@arnold.se) Received: from mailstore.infotropic.com (mailstore.infotropic.com [213.136.34.3]) by mx1.freebsd.org (Postfix) with ESMTP id A62C613C457 for ; Wed, 10 Oct 2007 18:33:04 +0000 (UTC) (envelope-from chris@arnold.se) Received: (qmail 37187 invoked by uid 89); 10 Oct 2007 18:06:22 -0000 Received: by simscan 1.2.0 ppid: 37182, pid: 37184, t: 0.1721s scanners: attach: 1.2.0 clamav: 0.90/m:42 Received: from unknown (HELO ?192.168.123.123?) (chris@arnold.se@82.182.86.134) by mailstore.infotropic.com with ESMTPA; 10 Oct 2007 18:06:22 -0000 Date: Wed, 10 Oct 2007 20:06:21 +0200 (CEST) From: Christopher Arnold X-X-Sender: chris@chrishome.localnet To: freebsd-current@freebsd.org Message-ID: <20071010195157.O24133@chrishome.localnet> X-message-flag: =?ISO-8859-1?Q?Outlook_isn=B4t_compliant_with_current_standards?= =?ISO-8859-1?Q?_please_install_another_mail_client!?= MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Compaq Smart Array 5300 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, 10 Oct 2007 18:33:05 -0000 Hi all! anyone aware of issues with Compaq Smart Array 5300 on a current only a day old? This is what i get in the boot message: ciss0: port 0xe800-0xe8ff mem 0xfebc0000-0xfebfffff,0xfea00000-0xfeafffff irq 22 at device 1.0 on pci2 ciss0: can't allocate config window device_attach: ciss0 attach returned 6 The full output can be found at: http://www.arnold.se/boot.txt http://www.arnold.se/pciconf.txt Im trying to run it in a Supermicro 6010 with 370DER+ motherboard. Anyone who has any input on what this could be? /Chris -- http://www.arnolse.se/ http://www.infotropic.com/ From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 18:34: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 D146E16A46B for ; Wed, 10 Oct 2007 18:34:15 +0000 (UTC) (envelope-from so14k@valentine.liquidneon.com) Received: from valentine.liquidneon.com (valentine.liquidneon.com [216.87.78.132]) by mx1.freebsd.org (Postfix) with ESMTP id 8102513C447 for ; Wed, 10 Oct 2007 18:34:15 +0000 (UTC) (envelope-from so14k@valentine.liquidneon.com) Received: by valentine.liquidneon.com (Postfix, from userid 1018) id 8A4808FD39; Wed, 10 Oct 2007 12:34:14 -0600 (MDT) Date: Wed, 10 Oct 2007 12:34:14 -0600 From: Brad Davis To: hackers@FreeBSD.org Message-ID: <20071010183414.GO26700@valentine.liquidneon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: FreeBSD Status Reports for the Third Quarter of 2007 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, 10 Oct 2007 18:34:16 -0000 FreeBSD Quarterly Status Report Introduction This report covers FreeBSD related projects between July and October 2007. The sixth EuroBSDCon was held in Denmark in September. The Google Summer of Code project came to a close and lots of participants are working getting their code merged back into FreeBSD. The bugs in the FreeBSD HEAD branch are being shaked out and it is being prepared for the FreeBSD 7 branching. If your are curious about what's new in FreeBSD 7.0 we suggest reading Ivan Voras' excellent summary here . Thanks to all the reporters for the excellent work! We hope you enjoy reading. __________________________________________________________________ Google Summer of Code * Summer of Code * finstall * FreeBSD-update Front End * gvirstor * MTund - Magic Tunnel Daemon * Porting OpenBSD's sysctl Hardware Sensors Framework to FreeBSD * Ports Collection infrastructure improvements Projects * Apple's MacBook on FreeBSD * Multi-link PPP daemon (MPD) 5.x * Multicast DNS * Porting Linux KVM to FreeBSD * USB FreeBSD Team Reports * FreeBSD.org Admins Report * Ports Collection Network Infrastructure * Network Stack Virtualization Documentation * PC-BSD Handbook * The Hungarian Documentation Project * The Spanish Documentation Project Miscellaneous * EuroBSDcon 2007 * GNATS graphs __________________________________________________________________ Apple's MacBook on FreeBSD URL: http://wiki.freebsd.org/AppleMacbook Contact: Rui Paulo The Summer of Code project went well and we reached interesting results. At least the Mac Mini should be fully supported by now. Regarding the other Apple systems, we still need to polish some edges. Open tasks: 1. Integrate rpaulo-macbook p4 branch into CVS. 2. Continue the work on the remaining issues. __________________________________________________________________ EuroBSDcon 2007 URL: http://2007.EuroBSDCon.org/ Contact: EuroBSDCon 2007 Organizing Committee The sixth EuroBSDCon went well. 215 people attended the conference. Feedback has been very positive. At the conference we had a Best Talk contest. Steven Murdoch, Isaac Levy and Pawel Jakub "zfs-man" Dawidek each received a prize for their fantastic talks. Also over 300 pictures from the conference has been uploaded to Flickr with the tag EuroBSDCon2007 Videos and slides from the talks are now online at the conference website. We thank our speakers for graciously having permitted recording and publication of their talks EuroBSDCon 2008 will take place in Strassbourg. __________________________________________________________________ finstall URL: http://wiki.freebsd.org/finstall Contact: Ivan Voras The "finstall" project is about the new graphical installer for FreeBSD. The basic frameworks (both client-side and server-side) are done during the SoC 2007 and it's ready for major new features to be implemented. This project should yield an usable installer for 7.0-RELEASE. Open tasks: 1. - There are several patches needed for finstall's operation that are still waiting on re@'s approval (unionfs, pwd, kbdmap). Finstall will be late or unusuable until these patches are committed. 2. - After the patches are committed, there are several exciting features to be implemented, among others ZFS and GEOM RAID support. __________________________________________________________________ FreeBSD-update Front End URL: http://developer.berlios.de/projects/facund/ Contact: Andrew Turner The freebsd-update front end is able to wait for freebsd-update to download a new set of patches to apply. It can then install and rollback the patches on either the local computer or over a SSH tunnel. Since the end of the Summer of Code work has moved to BerliOS. The focus has been on writing tests for the front end, back end and communication library. The library has had tests written for most of it while the front and back ends have none. Open tasks: 1. Write more tests. __________________________________________________________________ FreeBSD.org Admins Report Contact: FreeBSD.org Admins Team admins@FreeBSD.org <> Over the last couple of months several FreeBSD.org systems have been experiencing hardware issues. This included the main web-server www.FreeBSD.org which had a bad fan. The bad fan has been replaced so it should hopefully be stable again. In general we are working on replacing older hardware with newer systems and consolidating machine functions in the process. Since August most FreeBSD.org services have been available via IPv6 with connectivity provided from ISC using a tunnel. To honor the "Eat your own dog-food" principle the first two FreeBSD.org infrastructure systems have been upgraded to FreeBSD 7 and more are being upgraded as time permit. Due to heavy load on the project's Perforce and CVS server the two services are being moved to seperate systems to improve performance of both CVS and Perforce. __________________________________________________________________ GNATS graphs URL: http://people.freebsd.org/~edwin/gnats/ Contact: Edwin Groothuis With the leaving of bsd@, we lost the GNATS statistics webpages. On this URL I generate a new set of graphs, right now a subset of what bsd@ had, hopefully a superset of that in the future. __________________________________________________________________ gvirstor URL: http://wiki.freebsd.org/gvirstor Contact: Ivan Voras GEOM_VIRSTOR (virtual disk space / over-commit GEOM class) has been committed to 7-CURRENT and will ship in 7.0-RELEASE. Thanks to Pawel Jakub Dawidek and others who have made this possible. Open tasks: 1. It needs wider exposure and testing. __________________________________________________________________ MTund - Magic Tunnel Daemon URL: http://wiki.freebsd.org/MTund URL: http://www.inf.ethz.ch/personal/mharvan/docs/eurobsdcon.pdf Contact: Matus Harvan IP can easily be tunneled over a plethora of network protocols at various layers, such as IP, ICMP, UDP, TCP, DNS, HTTP, SSH. While a direct connection may not always be possible due to a firewall, the IP packets could be encapsulated as payload in other protocols, which would get through. However, each such encapsulation requires the setup of a different program and the user has to manually probe different encapsulations to find out which of them works in a given environment. MTund is a tunneling daemon using run-time loadable plugins for the different encapsulations. It automagically selects the best encapsulation in each environment and can fail over to another encapsulation. Several plugins have been implemented and the daemon supports multiple concurrent clients. Note that the project originally started under the name of Super Tunnel Daemon, but was later renamed to Magic Tunnel Daemon (MTund). Open tasks: 1. Config file format and parser. 2. More plugins (http, ssh, ...). __________________________________________________________________ Multi-link PPP daemon (MPD) 5.x URL: http://sourceforge.net/projects/mpd/ URL: http://mpd.sourceforge.net/doc5/mpd5.html Contact: Alexander Motin New mpd-5.x branch has been started and first public release is planned soon. The main goal of the new branch is to implement new operation principles based on dynamic on-demand links/bundles creation. There are several benefits received from new design: * Significantly simplified server configuration - no more tons of predefined links/bundles, * New multilink implementation - no more predefined link-bundle relations, * Call forwarding (LAC, PAC, TSA) like in Cisco VPDN setups can now be enabled/configured depending on peer auth name/domain. Open tasks: 1. L2TP auth proxying support. __________________________________________________________________ Multicast DNS URL: http://wiki.freebsd.org/MulticastDNS Contact: Fredrik Lindberg The project (started out as a GSoC 2007 project) aims to provide a complete Multicast DNS and Service Discovery suite. Much progress have been made since the last status report and the project is slowly reaching a usable state. Most features are complete and the current focus is on fixing outstanding bugs, fine tuning and testing. However, there are still a few open tasks (see below). More information and snapshots can be found at the wiki page. Open tasks: 1. Avahi library wrapper. 2. dns_sd (Apple) library wrapper. 3. Testing (always welcome). __________________________________________________________________ Network Stack Virtualization URL: http://imunes.tel.fer.hr/virtnet/ Contact: Marko Zec The network stack virtualization project aims at extending the FreeBSD kernel to maintain multiple independent instances of networking state. This allows for networking independence between jail-like environmens, each maintaining its private network interface set, IPv4 and IPv6 network and port address space, routing tables, IPSec configuration, firewalls, and more. The prototype, which is kept in sync with FreeBSD -CURRENT, should be sufficiently stable for testing and experimental use. The project's web page includes weekly code snapshots, as well as a virtualized FreeBSD system installed on a VMWare disk image available for download. The short-term goal is to deliver production-grade kernel support for virtualized networking for FreeBSD 7.0-RELEASE (as a snap-in kernel replacement), while continuing to keep the code in sync with -CURRENT for possible merging at a later date. __________________________________________________________________ PC-BSD Handbook URL: http://www.pcbsd.org URL: http://www.FreeBSD.org/handbook Contact: Murray Stokely Contact: Matt Olander Contact: Fukang Chen The PC-BSD derivative of FreeBSD is becoming increasingly popular for new users of BSD. Much of the content in the existing FreeBSD Handbook is directly applicable to PC-BSD. We are writing PC-BSD specific installation and port/packages chapters (PBI). These chapters will be checked into docs/en_US.ISO8859-1/books/pcbsd-handbook and will include some of the same chapters as the Handbook does, but with a different &os entity and possibly with some conditional changes in those chapter files. Open tasks: 1. More work is needed on a PC-BSD ports/packages chapter. Fukang may already have some work in this area so coordinate with him first. 2. More text is needed for the PC-BSD installation chapter to augment the screenshots that Fukang has collected. Contact him to coordinate. __________________________________________________________________ Porting Linux KVM to FreeBSD URL: http://feanor.sssup.it/~fabio/freebsd/lkvm/ Contact: Fabio Checconi Contact: Luigi Rizzo Linux KVM (Kernel-based Virtual Machine) is a software package that can be used to create virtual machines fully emulating x86 hardware on top of machines supporting Intel VT-x or AMD-V virtualization extensions, available on newer AMD and Intel processors, e.g., recent Athlon64, Core 2 Duo, Xeon and so on. Linux KVM has been ported to FreeBSD as a loadable kernel module, using the linux-kmod-compat port (in /usr/ports/devel/) to reuse as much as possible of the original source code, plus an userspace client consisting in a modified version of qemu, that uses KVM for the execution of its guests. The porting has been completed, many of the limitations present at the end of the Summer of Code have been removed and the known bugs have been fixed. Some configurations have been tested, FreeBSD-CURRENT i386 guests have been booted on Intel and AMD processors, both in i386 and amd64 (host) installations. Only one client at a time is supported by now and performance is not that exciting, but the project seems to be ready to receive wider testing. __________________________________________________________________ Porting OpenBSD's sysctl Hardware Sensors Framework to FreeBSD URL: http://wiki.freebsd.org/GSoC2007/cnst-sensors URL: http://cnst.livejournal.com/tag/GSoC2007 URL: http://cnst.livejournal.com/data/atom?tag=GSoC2007 URL: http://lists.freebsd.org/pipermail/freebsd-hackers/2007-September/02172 2.html URL: http://p4web.freebsd.org//depot/projects/soc2007/cnst-sensors/?ac=83 Contact: Constantine A. Murenin Contact: Shteryana Shopova The GSoC2007/cnst-sensors project was about porting the sysctl hw.sensors framework from OpenBSD to FreeBSD. The project was successfully completed , committed into DragonFly BSD , and is now pending final review and integration into the FreeBSD's CVS tree (subject to the tree being unfrozen). The sensors framework provides a unified interface for storing, registering and accessing information about hardware monitoring sensors. Sensor types include, but are not limited to, temperature, voltage, fan RPM, time offset and logical drive status. In the OpenBSD base system, the framework spans sensor_attach(9) , sysctl(3) , sysctl(8) , systat(1) , sensorsd(8) , ntpd(8) and more than 50 drivers, ranging from I2C temperature sensors and Super I/O hardware monitors to IPMI and RAID controllers. Several third-party tools are also available, for example, a plug-in for Nagios and ports/sysutils/symon. As a part of this Google Summer of Code project, all core components of the framework were ported, including sysctl, systat and sensorsd. Some drivers for the most popular Super I/O Hardware Monitors were ported, too: it(4) , supporting most contemporary ITE Tech Super I/O, and lm(4) , supporting most contemporary Winbond Super I/O. Moreover, some existing FreeBSD drivers were converted to utilise the framework, for example, coretemp(4) . Open tasks: 1. Final Review and Commit __________________________________________________________________ Ports Collection URL: http://www.freebsd.org/ports/ URL: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/ URL: http://people.freebsd.org/~fenner/portsurvey/ URL: http://portsmon.FreeBSD.org/index.html URL: http://www.freebsd.org/portmgr/index.html URL: http://tinderbox.marcuscom.com URL: http://wiki.freebsd.org/gcc4 Contact: Mark Linimon The ports count is over 17,700. The PR count has decreased a bit to just over 700. There have been 6 experimental runs on the build cluster. The resulting commits include the fixup of last year's DESTDIR changes, the refactoring of perl bits into bsd.perl.mk, the update of xorg from 7.2 to 7.3, the upgrade of all of the autoconf dependencies to the latest version (wherever possible), and the upgrade of Python to 2.5. This effort has resulted in the fewest number of 'open' portmgr PRs in quite some time. portmgr appreciates all the people who worked with us on these patches, and people's patience as we catch up. As well, lofi@ committed the upgrade of QT to 4.3.1. We have added 3 new committers since the last report. Open tasks: 1. GCC4.2 has been imported to the base for 7.0. Unfortunately, this broke a large number of ports. The ones that have not yet been fixed have now been flagged as 'broken' for both i386 and amd64, as appropriate. Please see the GCC4 status page (above) if you are able to help. 2. Most of the remaining ports PRs are "existing port/PR assigned to committer". Although the maintainer-timeout policy is helping to keep the backlog down, we are going to need to do more to get the ports in the shape they really need to be in. 3. Although we have added many maintainers, we still have many unmaintained ports. The packages on amd64 are lagging behind a bit; those on sparc64 require even more work. __________________________________________________________________ Ports Collection infrastructure improvements URL: http://wiki.freebsd.org/G%C3%A1borSoC2007 Contact: Gábor Kövesdán The two most important parts of this Summer of Code projects have been accomplished. The DESTDIR support for the Ports Collection has been rewritten to use a chrooted install. Now it is much more lightweight and easier to understand, but it works well for the most common cases, where it is supposed to be useful. The Perl parts of the Ports Collection infrastructure have been extracted into an own module. At the same time, a new version handling has been invented. You can find more info on the Wiki. __________________________________________________________________ Summer of Code URL: http://www.FreeBSD.org/projects/summerofcode-2007.html URL: http://googlesummerofcode.blogspot.com/2007/09/updates-from-freebsd.htm l URL: http://wiki.freebsd.org/SummerOfCode2007 Contact: Murray Stokely Contact: Robert Watson We're happy to report the successful conclusion of our third consecutive Google Summer of Code. By all accounts, the FreeBSD participation in this program was an unqualified success. We narrowed down the many impressive applications to 25 that were selected for funding and 92% of these completed successfully and were awarded the full $4,500 stipend. The FreeBSD Foundation was also granted $500 per student from Google for a total of $12,500. These student projects included security research, improved installation tools, new utilities, and more. Many of the students have continued working on their FreeBSD projects even after the official close of the program. Three students have already been granted full src/ commit access to CVS and more are expected. At least 2 of our FreeBSD mentors will be meeting with Google organizers in Mountain View this month to discuss the program at the Mentor Summit. Open tasks: 1. Integration of student projects into FreeBSD -CURRENT. Several are currently blocked on the FreeBSD 7.0 code freeze, but we hope to see these contributions included in a future release. 2. Updating the ideas list. Many of the items listed there have been completed and we could always use new projects for next year's students and for others to work on throughout the year. http://www.FreeBSD.org/projects/ideas __________________________________________________________________ The Hungarian Documentation Project URL: http://www.freebsd.org/hu/docproj/hungarian.html URL: http://www.freebsd.org/hu/ URL: http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/ docproj%5fhu&HIDEDEL=NO Contact: Gabor Kovesdan Contact: Gabor Pali We have a new volunteer, Gabor Pali, who provided us some high-quality contributions. As a result, we have been able to add 5 new articles since the last status report. There is also an ongoing effort in the Perforce repository to translate the FreeBSD Handbook to Hungarian. Any kind of support is highly welcome. Open tasks: 1. Translate the Handbook. __________________________________________________________________ The Spanish Documentation Project URL: http://www.freebsd.org/doc/es_ES.ISO8859-1/articles/fdp-es/ Contact: J. Vicente Carrasco Vayá Contact: Gabor Kovesdan After a long break in this project, we started reviewing and refreshing our translations. We have to update the content to reflect the current state of the English version. There are a few parts written in a poor style, another task is to improve these a bit. Any kind of help is highly welcome. Open tasks: 1. Sync the website with the English version. 2. Sync the documentation with the English version. 3. Review the quality of poorly translated parts. 4. Add more translations. __________________________________________________________________ USB URL: http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/ usb/src/sys/dev/usb&HIDEDEL=NO URL: http://perforce.freebsd.org/fileLogView.cgi?FSPC=//depot/projects/usb/s rc/sys/dev/usb/README Contact: Hans Petter Sirevaag Selasky During the last three months there has been a flush of changes going into the FreeBSD USB P4 project. The changes mainly consern the ability to support the USB device side and multi frame USB transfers. Up to date the FreeBSD USB stack has only supported the USB Host Side. Before Christmas 2007 the P4 USB project will offer USB device support and some simple USB device side implementations. Technically an USB device side driver will look very similar to an USB host side driver. Infact there will be very few differences. Support for multi frame USB transfers opens up the possibility to transfer multiple short-packet terminated USB frames to/from different memory locations resulting in only one interrupt on the USB Host Controller. More specific: I have implemented support for the "alt_next" pointer in the EHCI Transfer Descriptor. This should give a noticable increase in the maximum number of short-packet terminated BULK frames that can be transferred per second. I regularly get questions from people asking about when the USB P4 project will be merged into FreeBSD-current. The answer is not simple, but probably something like another year. The reason is not that the current code in the USB P4 project is not usable, but rather that the quality needs to be raised in means of making already good solutions more technically excellent, writing more documentation and styling the code. Ideas and comments with regard to the new USB API are welcome at freebsd-usb@freebsd.org. __________________________________________________________________ From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 18:54: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 580AF16A420 for ; Wed, 10 Oct 2007 18:54:17 +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 39A0313C4C3 for ; Wed, 10 Oct 2007 18:54:16 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 9D90C1CC05F; Wed, 10 Oct 2007 11:54:16 -0700 (PDT) Date: Wed, 10 Oct 2007 11:54:16 -0700 From: Jeremy Chadwick To: Christopher Arnold Message-ID: <20071010185416.GA38522@eos.sc1.parodius.com> Mail-Followup-To: Christopher Arnold , freebsd-current@freebsd.org References: <20071010195157.O24133@chrishome.localnet> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071010195157.O24133@chrishome.localnet> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org Subject: Re: Compaq Smart Array 5300 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, 10 Oct 2007 18:54:17 -0000 On Wed, Oct 10, 2007 at 08:06:21PM +0200, Christopher Arnold wrote: > > Hi all! > > anyone aware of issues with Compaq Smart Array 5300 on a current only a day > old? > > This is what i get in the boot message: > ciss0: port 0xe800-0xe8ff mem > 0xfebc0000-0xfebfffff,0xfea00000-0xfeafffff irq 22 at device 1.0 on pci2 > ciss0: can't allocate config window > device_attach: ciss0 attach returned 6 > > The full output can be found at: > http://www.arnold.se/boot.txt > http://www.arnold.se/pciconf.txt > > Im trying to run it in a Supermicro 6010 with 370DER+ motherboard. > > Anyone who has any input on what this could be? It's one of those bloody QLogic GEM chips; on this motherboard, it's probably the QLogic GEM 354. The motherboard manual does indicate this, although only in the Windows driver section (this does not surprise me, as some other vendors use GEM chips and don't tell you until you actually have to deal with them...) I've dealt with GEMs at work (not Supermicro products), and they do nothing but piss you off in the case there is any sort of SCSI failure. For example, a drive going bad and falling off the bus would normally result in the SCSI subsystem reporting some errors and the OS (hopefully) continuing to work w/out issue (barring if the main OS disk failed, of course :-) ). SCSI's pretty resilient about this sort of thing. The GEM is supposed to handle all of this "for" you in some bizarre manner, but I've never seen it work reliably -- ever. The GEM also can, somehow, manage SCSI IDs for you and do some sort of transparent SCSI ID remapping. This is all what I've seen first-hand. The GEM does have some sort of BIOS (on some mainboards you can hit a control character sequence prior to POST completion and go in and adjust GEM settings), but I don't know how it works. There's comments in the FreeBSD driver code about the GEM chips violating SCSI specification, by the way. If you want me to dig up the cvsweb URL for it, I can. Based on that, and my experiences at work, I'm not left feeling very good about those chips. In general: I wouldn't worry about the lack of ciss0 device. In fact, I'd go so far to recommend you remove ses and ciss from the kernel on that box, and hope for the best. Scott (Long) may have some better (and more accurate) advice on the matter; my experiences are my own. -- | 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 Wed Oct 10 20:21: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 2455A16A420 for ; Wed, 10 Oct 2007 20:21:21 +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 B580A13C4B8 for ; Wed, 10 Oct 2007 20:21:20 +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 213848283-1834499 for multiple; Wed, 10 Oct 2007 16:19:24 -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 l9AKL3aW017064; Wed, 10 Oct 2007 16:21:17 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 10 Oct 2007 15:46:03 -0400 User-Agent: KMail/1.9.6 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710101546.03648.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]); Wed, 10 Oct 2007 16:21:18 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/4523/Wed Oct 10 14:30:26 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: Michiel Boland Subject: Re: confusing kdump 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, 10 Oct 2007 20:21:21 -0000 On Sunday 08 July 2007 11:21:16 am Michiel Boland wrote: > Hi. If a program does something like > > setsockopt(sock, IPPROTO_TCP, TCP_NOPUSH, &onoff, sizeof onoff) > > this is reported by kdump as > > setsockopt(0x2a,0x6,SO_REUSEADDR,0x7fffffffe32c,0x4) > > Note that it reports SO_REUSEADDR rather than TCP_NOPUSH. This is > confusing. > > It's probably a bit useless to compile all possible printable socket > options into kdump, but at least it could be made to not print a symbolic > name if the level is, say, not SOL_SOCKET. Try this: Index: kdump.c =================================================================== RCS file: /usr/cvs/src/usr.bin/kdump/kdump.c,v retrieving revision 1.37 diff -u -r1.37 kdump.c --- kdump.c 10 Jul 2007 00:01:30 -0000 1.37 +++ kdump.c 10 Oct 2007 19:43:48 -0000 @@ -532,10 +532,12 @@ print_number(ip,narg,c); (void)putchar(','); sockoptlevelname((int)*ip, decimal); - ip++; - narg--; - (void)putchar(','); - sockoptname((int)*ip); + if ((int)*ip == SOL_SOCKET) { + ip++; + narg--; + (void)putchar(','); + sockoptname((int)*ip); + } ip++; narg--; #ifdef SYS_freebsd6_lseek -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 20:21: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 7E5E816A419 for ; Wed, 10 Oct 2007 20:21:23 +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 0604E13C43E for ; Wed, 10 Oct 2007 20:21:22 +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 213848287-1834499 for multiple; Wed, 10 Oct 2007 16:19:26 -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 l9AKL3aX017064; Wed, 10 Oct 2007 16:21:20 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org, pyunyh@gmail.com Date: Wed, 10 Oct 2007 15:51:25 -0400 User-Agent: KMail/1.9.6 References: <20070827201809.0367616A418@hub.freebsd.org> <20070828010310.GA85263@cdnetworks.co.kr> In-Reply-To: <20070828010310.GA85263@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710101551.26081.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]); Wed, 10 Oct 2007 16:21:20 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/4523/Wed Oct 10 14:30:26 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: Bill Paul , freebsd-net@freebsd.org Subject: Re: Bug in vr(4) 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: Wed, 10 Oct 2007 20:21:23 -0000 On Monday 27 August 2007 09:03:10 pm Pyun YongHyeon wrote: > On Mon, Aug 27, 2007 at 08:18:08PM +0000, Bill Paul wrote: > > > > I recently started writing a driver for the Via Rhine family of chips > > for VxWorks (they turn up on various x86-based single board systems, > > and I figured it'd be nice to actually support them out of the box), > > and along the way, I noticed a subtle bug in the FreeBSD vr(4) driver. > > > > The vr_attach() routine unconditionally does this for all supported > > chips: > > > > /* > > * Windows may put the chip in suspend mode when it > > * shuts down. Be sure to kick it in the head to wake it > > * up again. > > */ > > VR_CLRBIT(sc, VR_STICKHW, (VR_STICKHW_DS0|VR_STICKHW_DS1)); > > > > The problem is, the VR_STICKHW register is not valid on all Rhine > > devices. The VT86C100A chip, which is present on the D-Link DFE-530TX > > boards, doesn't support power management, and its register space is > > only 128 bytes wide. The VR_STICKHW register offset falls outside this > > range. This may go unnoticed in most scenarios, but if you happen to have > > another PCI device in your system which is assigned the register > > space immediately after that of the Rhine, the vr(4) driver will > > incorrectly stomp it. In my case, the BIOS on my test board decided > > to put the register space for my PRO/100 ethernet board right next > > to the Rhine, and the Rhine driver ended up clobbering the IMR register > > of the PRO/100 device. (Long story short: the board kept locking up on > > boot. Took me the better part of the morning suss out why.) > > > > The strictly correct thing to do would be to check the PCI config space > > to make sure the device supports the power management capability and only > > write to the VR_STICKHW register if it does. A less strictly correct > > but equally effective thing to do would be: > > > > /* > > * Windows may put the chips that support power management into > > * suspend mode when it shuts down. Be sure to kick it in the > > * head to wake it up again. > > */ > > if (pci_get_device(dev) != VIA_DEVICEID_RHINE) > > VR_CLRBIT(sc, VR_STICKHW, (VR_STICKHW_DS0|VR_STICKHW_DS1)); > > > > This is basically the fix I put into my VxWorks driver. I suggest someone > > update the FreeBSD driver as well. > > > > Hi, > > I don't have vr(4) hardwares(if I had I would have converted vr(4) > to use bus_dma(9)). Would you review/test the attached patch? Pyun, I'd say to go ahead and commit the patch. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 20:21: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 BEA0F16A421 for ; Wed, 10 Oct 2007 20:21:27 +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 22F8D13C467 for ; Wed, 10 Oct 2007 20:21:26 +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 213848293-1834499 for multiple; Wed, 10 Oct 2007 16:19:30 -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 l9AKL3aZ017064; Wed, 10 Oct 2007 16:21:24 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 10 Oct 2007 16:15:48 -0400 User-Agent: KMail/1.9.6 References: <20070912172752.GA13960@dan.emsphone.com> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200710101615.48760.jhb@freebsd.org> Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Wed, 10 Oct 2007 16:21:24 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/4523/Wed Oct 10 14:30:26 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: Ivan Voras Subject: Re: Panic in arpresolve->rt_check? 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, 10 Oct 2007 20:21:27 -0000 On Wednesday 12 September 2007 02:50:37 pm Ivan Voras wrote: > Dan Nelson wrote: > > > The same panic was also reported for 6.2 via PR 107865 and PR 112490. > > 112490 included a workaround patch (I haven't tried it; just found it). > > The proposed patch in kern/112490 looks trivial but someone who knows > more about net locking should check it out. Unfortunately it lacks > context and I don't know the code in question to apply it safely on a > production machine :( I also get panics with what appears to be a double free of rt_gwroute in rtexpunge(), so I think while this PR may help some with figuring out the problem, I'm not sure it solves the root bug. Hmm, possibly try this patch: Index: route.c =================================================================== RCS file: /usr/cvs/src/sys/net/route.c,v retrieving revision 1.120 diff -c -r1.120 route.c *** route.c 11 Jun 2007 12:19:34 -0000 1.120 --- route.c 10 Oct 2007 20:12:54 -0000 *************** *** 1314,1319 **** --- 1314,1321 ---- return (ENETUNREACH); } RT_LOCK(rt0); + if (rt0->rt_gwroute != NULL) + RTFREE(rt0->rt_gwroute); rt0->rt_gwroute = rt; if (rt == NULL) { RT_UNLOCK(rt0); -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 20:58: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 C47D316A41A for ; Wed, 10 Oct 2007 20:58:49 +0000 (UTC) (envelope-from maksim.yevmenkin@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 3CA9D13C45D for ; Wed, 10 Oct 2007 20:58:49 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so287783nfb for ; Wed, 10 Oct 2007 13:58:48 -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=9oXtwNOucL57ujmjSX7d5vCy9RhpvMT04Oyn5885TXs=; b=FdM1uuhMvuog5lCNJn3bwzssg+vnTjFijdoG2IYO+8twfQ7YWfK0KkLd9YF6Eni39iTWAlBcDiKeezOqE1ADwBssMaWyKBSVo8POdE8z7TS5j+TrE46QeOuyKYjXH7lvegmwOAfgGP2Et4L9pQ/jfea7/WWWg2moTHn7pOrV2P0= 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=iwYLIoSm3ItOuz2VgquMAxDC9zz4NNaQZmETPnj6LvOVWxlvlzFK0YItnVZN1roQkwY+nlOIkcmqNXR3W3MQXErW/6FSubJZQRs8q5e0y66Q/ltFV4W+vnRUfreWlpSAcvMAMhAfi+Qw2RcQ5kSDK6G5ebjIoZs9fxEKvSbaA8Y= Received: by 10.86.51.2 with SMTP id y2mr842036fgy.1192048338876; Wed, 10 Oct 2007 13:32:18 -0700 (PDT) Received: by 10.86.25.9 with HTTP; Wed, 10 Oct 2007 13:32:18 -0700 (PDT) Message-ID: Date: Wed, 10 Oct 2007 13:32:18 -0700 From: "Maksim Yevmenkin" 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: panic on sparc64 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, 10 Oct 2007 20:58:49 -0000 hello, recent -current often panics with the following stack trace on sparc64. is this something new? or has it been fixed already? thanks, max panic: mutex vm page queue mutex not owned at /usr/src/sys/sparc64/sparc64/pmap.c:1768 cpuid = 0 KDB: enter: panic panic: from debugger cpuid = 0 Uptime: 9h36m23s Dumping 256 MB (2 chunks) chunk at 0: 134217728 bytes | #0 0x00000000c0280318 in doadump () at /usr/src/sys/kern/kern_shutdown.c:240 240 savectx(&dumppcb); (kgdb) where #0 0x00000000c0280318 in doadump () at /usr/src/sys/kern/kern_shutdown.c:240 #1 0x00000000c0280d40 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #2 0x00000000c0281124 in panic (fmt=0xc06454f0 "from debugger") at /usr/src/sys/kern/kern_shutdown.c:563 #3 0x00000000c009ed28 in db_panic (addr=3224044552, have_addr=0, count=-1, modif=0xceff6868 "") at /usr/src/sys/ddb/db_command.c:433 #4 0x00000000c009fc74 in db_command_loop () at /usr/src/sys/ddb/db_command.c:401 #5 0x00000000c00a2d34 in db_trap (type=Variable "type" is not available. ) at /usr/src/sys/ddb/db_main.c:222 #6 0x00000000c02b00d4 in kdb_trap (type=107, code=0, tf=0xceff6cd0) at /usr/src/sys/kern/subr_kdb.c:502 #7 0x00000000c0559990 in trap (tf=0xceff6cd0) at /usr/src/sys/sparc64/sparc64/trap.c:318 #8 0x00000000c0071000 in tl1_trap () #9 0x00000000c02b0408 in kdb_enter (msg=0x12
) at /usr/src/sys/kern/subr_kdb.c:307 #10 0x00000000c02b0408 in kdb_enter (msg=0xc066c008 "panic") at /usr/src/sys/kern/subr_kdb.c:307 #11 0x00000000c02810ec in panic (fmt=0xc066a978 "mutex %s not owned at %s:%d") at /usr/src/sys/kern/kern_shutdown.c:547 #12 0x00000000c0272894 in _mtx_assert (m=0xc07e1598, what=1, file=0xc069aaf0 "/usr/src/sys/sparc64/sparc64/pmap.c", line=1768) at /usr/src/sys/kern/kern_mutex.c:623 #13 0x00000000c0551660 in pmap_page_is_mapped (m=0xfffff80007be2768) at /usr/src/sys/sparc64/sparc64/pmap.c:1768 #14 0x00000000c04e6f14 in vm_page_free_toq (m=0xfffff80007be2768) at /usr/src/sys/vm/vm_page.c:1258 #15 0x00000000c04e72d8 in vm_page_free (m=0xfffff80007be2768) at /usr/src/sys/vm/vm_page.c:498 #16 0x00000000c055bb84 in uma_small_free (mem=0xfffff80001252000, size=8192, flags=8 '\b') at /usr/src/sys/sparc64/sparc64/vm_machdep.c:505 #17 0x00000000c04d3d78 in zone_drain (zone=0xfffff80007fec900) at /usr/src/sys/vm/uma_core.c:767 #18 0x00000000c04cf194 in zone_foreach (zfunc=0xc04d3aa0 ) at /usr/src/sys/vm/uma_core.c:1495 #19 0x00000000c04d41c8 in uma_reclaim () at /usr/src/sys/vm/uma_core.c:2670 #20 0x00000000c04eaf20 in vm_pageout () at /usr/src/sys/vm/vm_pageout.c:696 #21 0x00000000c025bf24 in fork_exit (callout=0xc04ea560 , arg=0x0, frame=0xceff7880) at /usr/src/sys/kern/kern_fork.c:796 #22 0x00000000c00711f0 in fork_trampoline () #23 0x00000000c00711f0 in fork_trampoline () Previous frame identical to this frame (corrupt stack?) From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 21:31: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 4229616A417; Wed, 10 Oct 2007 21:31:28 +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 A073113C469; Wed, 10 Oct 2007 21:31:27 +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 213856265-1834499 for multiple; Wed, 10 Oct 2007 17:29:28 -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 l9ALVLAe017700; Wed, 10 Oct 2007 17:31:22 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 10 Oct 2007 16:46:49 -0400 User-Agent: KMail/1.9.6 References: <20070921202523.GB4044@nowhere> <20071002204850.GA33227@nowhere> In-Reply-To: <20071002204850.GA33227@nowhere> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710101646.50012.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]); Wed, 10 Oct 2007 17:31:22 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/4523/Wed Oct 10 14:30:26 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: danfe@freebsd.org, current@freebsd.org, Craig Boston Subject: Re: Patch for nvidia-driver on current (panic: spin locks can only use msleep_spin) 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, 10 Oct 2007 21:31:28 -0000 On Tuesday 02 October 2007 04:48:57 pm Craig Boston wrote: > Hi all, I did some more investigating and found what was causing the > nvidia driver to occasionally panic on my machine. It calls cv_wait(9) > using a spin mutex, which according to the man page is a no-no. > > I simply changed the os_*_sema interfaces to use a standard mutex > instead. Tried running a bunch of glxgears and xscreensaver GL demos in > parallel and haven't been able to reproduce a panic since. As a bonus, > the 5 second pause I would sometimes get when a GL-based xscreensaver > process terminates seems to be gone as well. > > There doesn't appear to be any documentation that I could find as to > what contexts those functions may be called from. I'm not a locking > guru, so I can't say for certain why a spin mutex was being used. Wild > guess: an artifact from the 4.x or 5.x code that may be obsoleted by > adaptive mutexes. > > Patch is attached; cc danfe@ in case others report this problem to him. Your patch is good, and I think nvidia is going to fix their driver to use a regular mutex as well. It probably uses a spin mutex because on other OS's you have to use a spin mutex to protect data shared with an interrupt handler. However, in the case of FreeBSD, you only use a spin mutex if you use an INTR_FAST/filter handler, and can use a regular mutex otherwise. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 21:31: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 4229616A417; Wed, 10 Oct 2007 21:31:28 +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 A073113C469; Wed, 10 Oct 2007 21:31:27 +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 213856265-1834499 for multiple; Wed, 10 Oct 2007 17:29:28 -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 l9ALVLAe017700; Wed, 10 Oct 2007 17:31:22 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 10 Oct 2007 16:46:49 -0400 User-Agent: KMail/1.9.6 References: <20070921202523.GB4044@nowhere> <20071002204850.GA33227@nowhere> In-Reply-To: <20071002204850.GA33227@nowhere> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710101646.50012.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]); Wed, 10 Oct 2007 17:31:22 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/4523/Wed Oct 10 14:30:26 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: danfe@freebsd.org, current@freebsd.org, Craig Boston Subject: Re: Patch for nvidia-driver on current (panic: spin locks can only use msleep_spin) 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, 10 Oct 2007 21:31:28 -0000 On Tuesday 02 October 2007 04:48:57 pm Craig Boston wrote: > Hi all, I did some more investigating and found what was causing the > nvidia driver to occasionally panic on my machine. It calls cv_wait(9) > using a spin mutex, which according to the man page is a no-no. > > I simply changed the os_*_sema interfaces to use a standard mutex > instead. Tried running a bunch of glxgears and xscreensaver GL demos in > parallel and haven't been able to reproduce a panic since. As a bonus, > the 5 second pause I would sometimes get when a GL-based xscreensaver > process terminates seems to be gone as well. > > There doesn't appear to be any documentation that I could find as to > what contexts those functions may be called from. I'm not a locking > guru, so I can't say for certain why a spin mutex was being used. Wild > guess: an artifact from the 4.x or 5.x code that may be obsoleted by > adaptive mutexes. > > Patch is attached; cc danfe@ in case others report this problem to him. Your patch is good, and I think nvidia is going to fix their driver to use a regular mutex as well. It probably uses a spin mutex because on other OS's you have to use a spin mutex to protect data shared with an interrupt handler. However, in the case of FreeBSD, you only use a spin mutex if you use an INTR_FAST/filter handler, and can use a regular mutex otherwise. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 21:31: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 E26E116A418 for ; Wed, 10 Oct 2007 21:31:31 +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 78A5513C48D for ; Wed, 10 Oct 2007 21:31:31 +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 213856274-1834499 for multiple; Wed, 10 Oct 2007 17:29:30 -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 l9ALVLAf017700; Wed, 10 Oct 2007 17:31:24 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 10 Oct 2007 16:53:53 -0400 User-Agent: KMail/1.9.6 References: <20070928184659.GB57646@cicely12.cicely.de> <46FDD3AB.3050305@bitfreak.org> In-Reply-To: <46FDD3AB.3050305@bitfreak.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710101653.54019.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]); Wed, 10 Oct 2007 17:31:25 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/4523/Wed Oct 10 14:30:26 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: Darren Pilgrim Subject: Re: 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: Wed, 10 Oct 2007 21:31:32 -0000 On Saturday 29 September 2007 12:25:15 am Darren Pilgrim wrote: > 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? The lauch is random. The boot processor sets a flag to tell the APs (which are already running, but spinnin in a loop) "ok, go run". The APs then compete on a spin lock to serialize their final initialization, and they "launch" in the order they acquire the spin lock, which is quite indeterminate. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 21:31: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 C455316A419 for ; Wed, 10 Oct 2007 21:31:32 +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 672DF13C447 for ; Wed, 10 Oct 2007 21:31:32 +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 213856277-1834499 for multiple; Wed, 10 Oct 2007 17:29:33 -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 l9ALVLAg017700; Wed, 10 Oct 2007 17:31:27 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org, w0lfie@clear.net.nz Date: Wed, 10 Oct 2007 16:56:23 -0400 User-Agent: KMail/1.9.6 References: <46feeec8.106.9f9.24060@clear.net.nz> In-Reply-To: <46feeec8.106.9f9.24060@clear.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710101656.23528.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]); Wed, 10 Oct 2007 17:31:27 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/4523/Wed Oct 10 14:30:26 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: Subject: Re: uipc_sockbuf sysctl 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, 10 Oct 2007 21:31:32 -0000 On Saturday 29 September 2007 08:33:12 pm Sam Banks wrote: > Hey all, > > I have started looking into cleaning up sysctl's with empty > descriptions and have come across kern.dummy. > > Looking into sys/kern/uipc_sockbuf.c, kern.dummy does > absolutely nothing other than offer the ability to change > it. The variable that the sysctl call populates (dummy) is > not used directly in sys/kern/uipc_sockbuf.c or, as far as I > can see, anywhere in the sys/ code. > > Is there a reason I'm missing why this seemingly uneeded > sysctl call is in the code or can it be removed with the > attached patch? > > Cheers, It reserves a specific OID value since the old kern.maxsockbuf wasn't OID_AUTO. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 21:31:33 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 A047C16A41B; Wed, 10 Oct 2007 21:31:33 +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 00F6513C455; Wed, 10 Oct 2007 21:31:32 +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 213856282-1834499 for multiple; Wed, 10 Oct 2007 17:29: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 l9ALVLAh017700; Wed, 10 Oct 2007 17:31:29 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 10 Oct 2007 17:14:22 -0400 User-Agent: KMail/1.9.6 References: <20071007140237.GA44735@freebsd.org> <20071008153106.GN2180@deviant.kiev.zoral.com.ua> <20071008172545.GA91406@freebsd.org> In-Reply-To: <20071008172545.GA91406@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710101714.23286.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]); Wed, 10 Oct 2007 17:31:29 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/4523/Wed Oct 10 14:30:26 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: Kostik Belousov , Roman Divacky , current@freebsd.org, peter@freebsd.org Subject: Re: pad argument for mmap/lseek/etc. 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, 10 Oct 2007 21:31:33 -0000 On Monday 08 October 2007 01:25:45 pm Roman Divacky wrote: > > The interesting question is whether the _SYS_SYSPROTO_H and absense of the > > sys/sysproto.h supported. Or, shall we remove these #ifdef blocks instead > > of fixing them in whole kernel. > > I also support this idea... does anyone have an argument against or should I > just provide a patch (removing those definitions) Many people (myself included) find it handy to have the uap structure definition with the function. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 21:31: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 A047C16A41B; Wed, 10 Oct 2007 21:31:33 +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 00F6513C455; Wed, 10 Oct 2007 21:31:32 +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 213856282-1834499 for multiple; Wed, 10 Oct 2007 17:29: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 l9ALVLAh017700; Wed, 10 Oct 2007 17:31:29 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 10 Oct 2007 17:14:22 -0400 User-Agent: KMail/1.9.6 References: <20071007140237.GA44735@freebsd.org> <20071008153106.GN2180@deviant.kiev.zoral.com.ua> <20071008172545.GA91406@freebsd.org> In-Reply-To: <20071008172545.GA91406@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710101714.23286.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]); Wed, 10 Oct 2007 17:31:29 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/4523/Wed Oct 10 14:30:26 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: Kostik Belousov , Roman Divacky , current@freebsd.org, peter@freebsd.org Subject: Re: pad argument for mmap/lseek/etc. 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, 10 Oct 2007 21:31:33 -0000 On Monday 08 October 2007 01:25:45 pm Roman Divacky wrote: > > The interesting question is whether the _SYS_SYSPROTO_H and absense of the > > sys/sysproto.h supported. Or, shall we remove these #ifdef blocks instead > > of fixing them in whole kernel. > > I also support this idea... does anyone have an argument against or should I > just provide a patch (removing those definitions) Many people (myself included) find it handy to have the uap structure definition with the function. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 22:20:55 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 C2ABC16A417 for ; Wed, 10 Oct 2007 22:20:55 +0000 (UTC) (envelope-from alc@cs.rice.edu) Received: from mail.cs.rice.edu (mail.cs.rice.edu [128.42.1.31]) by mx1.freebsd.org (Postfix) with ESMTP id 81E9013C4B2 for ; Wed, 10 Oct 2007 22:20:53 +0000 (UTC) (envelope-from alc@cs.rice.edu) Received: from mail.cs.rice.edu (localhost.localdomain [127.0.0.1]) by mail.cs.rice.edu (Postfix) with ESMTP id 72EA82C2B85; Wed, 10 Oct 2007 16:50:55 -0500 (CDT) X-Virus-Scanned: by amavis-2.4.0 at mail.cs.rice.edu Received: from mail.cs.rice.edu ([127.0.0.1]) by mail.cs.rice.edu (mail.cs.rice.edu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id dWhwCnlMkZcB; Wed, 10 Oct 2007 16:50:47 -0500 (CDT) Received: from [10.194.94.67] (nat-168-7-248-116.rice.edu [168.7.248.116]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.cs.rice.edu (Postfix) with ESMTP id B15902C2B5A; Wed, 10 Oct 2007 16:50:47 -0500 (CDT) Message-ID: <470D492C.6080409@cs.rice.edu> Date: Wed, 10 Oct 2007 16:50:36 -0500 From: Alan Cox User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: maksim.yevmenkin@gmail.com Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: panic on sparc64 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, 10 Oct 2007 22:20:55 -0000 This lock assertion failure in sparc64's pmap.c was fixed by this commit: alc 2007-10-07 18:03:04 UTC FreeBSD src repository Modified files: sys/sparc64/sparc64 pmap.c sys/vm vm_page.c Log: Correct a lock assertion failure in sparc64's pmap_page_is_mapped() that is a consequence of sparc64/sparc64/vm_machdep.c revision 1.76. It occurs when uma_small_free() frees a page. The solution has two parts: (1) Mark pages allocated with VM_ALLOC_NOOBJ as PG_UNMANAGED. (2) Defer the lock assertion in pmap_page_is_mapped() until after PG_UNMANAGED is tested. This is safe because both PG_UNMANAGED and PG_FICTITIOUS are immutable flags, i.e., they do not change state between the time that a page is allocated and freed. Approved by: re (kensmith) PR: 116794 Revision Changes Path 1.166 +1 -1 src/sys/sparc64/sparc64/pmap.c 1.356 +1 -1 src/sys/vm/vm_page.c From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 23:16: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 AB8E116A421; Wed, 10 Oct 2007 23:16:38 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.freebsd.org (Postfix) with ESMTP id 6239C13C468; Wed, 10 Oct 2007 23:16:38 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.14.1/8.13.7) with ESMTP id l9AN5lEm084255; Wed, 10 Oct 2007 16:05:47 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.14.1/8.13.4/Submit) id l9AN5lHn084254; Wed, 10 Oct 2007 16:05:47 -0700 (PDT) Date: Wed, 10 Oct 2007 16:05:47 -0700 (PDT) From: Matthew Dillon Message-Id: <200710102305.l9AN5lHn084254@apollo.backplane.com> To: John Baldwin References: <20071007140237.GA44735@freebsd.org> <20071008153106.GN2180@deviant.kiev.zoral.com.ua> <20071008172545.GA91406@freebsd.org> <200710101714.23286.jhb@freebsd.org> Cc: Kostik Belousov , Roman Divacky , freebsd-current@freebsd.org, current@freebsd.org, peter@freebsd.org Subject: Re: pad argument for mmap/lseek/etc. 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, 10 Oct 2007 23:16:38 -0000 :> > of fixing them in whole kernel. :> :> I also support this idea... does anyone have an argument against or should I :> just provide a patch (removing those definitions) : :Many people (myself included) find it handy to have the uap structure :definition with the function. : :-- :John Baldwin What I did in DragonFly a long time ago was remove the #ifdef and struct defintion entirely and simply put the UAP arguments in comments. i.e.: /* * umount_args(char *path, int flags) */ /* ARGSUSED */ int sys_unmount(struct unmount_args *uap) ... /* * mmap_args(void *addr, size_t len, int prot, int flags, int fd, * long pad, off_t pos) */ ... int sys_mmap(struct mmap_args *uap) ... I had found that not only were the structure definitions out of date, there were many system calls that didn't have them at all as well as other inconsistencies. I also prefixed all system call procedure definitions in the kernel with 'sys_' which got rid of most of the conflicts between kernel function names and standard library headers. That was so the virtual kernel could link against libc but even without a vkernel build I think it's a good idea to get rid of the conflicts. -Matt From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 23:16: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 AB8E116A421; Wed, 10 Oct 2007 23:16:38 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.freebsd.org (Postfix) with ESMTP id 6239C13C468; Wed, 10 Oct 2007 23:16:38 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.14.1/8.13.7) with ESMTP id l9AN5lEm084255; Wed, 10 Oct 2007 16:05:47 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.14.1/8.13.4/Submit) id l9AN5lHn084254; Wed, 10 Oct 2007 16:05:47 -0700 (PDT) Date: Wed, 10 Oct 2007 16:05:47 -0700 (PDT) From: Matthew Dillon Message-Id: <200710102305.l9AN5lHn084254@apollo.backplane.com> To: John Baldwin References: <20071007140237.GA44735@freebsd.org> <20071008153106.GN2180@deviant.kiev.zoral.com.ua> <20071008172545.GA91406@freebsd.org> <200710101714.23286.jhb@freebsd.org> Cc: Kostik Belousov , Roman Divacky , freebsd-current@freebsd.org, current@freebsd.org, peter@freebsd.org Subject: Re: pad argument for mmap/lseek/etc. 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, 10 Oct 2007 23:16:38 -0000 :> > of fixing them in whole kernel. :> :> I also support this idea... does anyone have an argument against or should I :> just provide a patch (removing those definitions) : :Many people (myself included) find it handy to have the uap structure :definition with the function. : :-- :John Baldwin What I did in DragonFly a long time ago was remove the #ifdef and struct defintion entirely and simply put the UAP arguments in comments. i.e.: /* * umount_args(char *path, int flags) */ /* ARGSUSED */ int sys_unmount(struct unmount_args *uap) ... /* * mmap_args(void *addr, size_t len, int prot, int flags, int fd, * long pad, off_t pos) */ ... int sys_mmap(struct mmap_args *uap) ... I had found that not only were the structure definitions out of date, there were many system calls that didn't have them at all as well as other inconsistencies. I also prefixed all system call procedure definitions in the kernel with 'sys_' which got rid of most of the conflicts between kernel function names and standard library headers. That was so the virtual kernel could link against libc but even without a vkernel build I think it's a good idea to get rid of the conflicts. -Matt From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 23:38: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 9438816A418; Wed, 10 Oct 2007 23:38:55 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from optimus.centralmiss.com (ns.centralmiss.com [206.156.254.79]) by mx1.freebsd.org (Postfix) with ESMTP id 5F1C113C458; Wed, 10 Oct 2007 23:38:55 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by optimus.centralmiss.com (Postfix) with ESMTP id E160728454; Wed, 10 Oct 2007 18:16:43 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 64BF161C43; Wed, 10 Oct 2007 18:16:43 -0500 (CDT) Date: Wed, 10 Oct 2007 18:16:43 -0500 From: "Matthew D. Fuller" To: Ivan Voras Message-ID: <20071010231643.GF58929@over-yonder.net> References: <86przndoe8.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.16-fullermd.4 (2007-06-09) Cc: freebsd-current@freebsd.org Subject: Re: suggest renaming and extending the -CURRENT and -STABLE lines 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, 10 Oct 2007 23:38:55 -0000 On Wed, Oct 10, 2007 at 05:29:12PM +0200 I heard the voice of Ivan Voras, and lo! it spake thus: > > And we'll find many other people on this newsgroup who do the same, > but not everyone's a kernel hacker, or even a decent programmer, so > it's kind of insignificant. I'm not a kernel hacker, and I don't remember the last time I ran a production system on a release longer than it took to do a buildworld, going back to 2.1.x. My workstation runs -CURRENT, though I rarely run -CURRENT on other production systems (rarely != never, but it is rare). -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-current@FreeBSD.ORG Wed Oct 10 23:59: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 74B3416A419 for ; Wed, 10 Oct 2007 23:59:10 +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 EA8FB13C478 for ; Wed, 10 Oct 2007 23:59:09 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IflSA-0004Kt-WB for freebsd-current@freebsd.org; Wed, 10 Oct 2007 23:59:03 +0000 Received: from 78-1-108-15.adsl.net.t-com.hr ([78.1.108.15]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 10 Oct 2007 23:59:02 +0000 Received: from ivoras by 78-1-108-15.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 10 Oct 2007 23:59:02 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Thu, 11 Oct 2007 01:58:51 +0200 Lines: 48 Message-ID: References: <86przndoe8.fsf@ds4.des.no> <20071010231643.GF58929@over-yonder.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig0CF52214415F0637A3158BF8" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 78-1-108-15.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) In-Reply-To: <20071010231643.GF58929@over-yonder.net> X-Enigmail-Version: 0.95.3 Sender: news Subject: Re: suggest renaming and extending the -CURRENT and -STABLE lines 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, 10 Oct 2007 23:59:10 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0CF52214415F0637A3158BF8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Matthew D. Fuller wrote: > On Wed, Oct 10, 2007 at 05:29:12PM +0200 I heard the voice of > Ivan Voras, and lo! it spake thus: >> And we'll find many other people on this newsgroup who do the same, >> but not everyone's a kernel hacker, or even a decent programmer, so >> it's kind of insignificant. >=20 > I'm not a kernel hacker, and I don't remember the last time I ran a > production system on a release longer than it took to do a buildworld, > going back to 2.1.x. My workstation runs -CURRENT, though I rarely > run -CURRENT on other production systems (rarely !=3D never, but it is > rare). Unfortunately (for this developer-centric practice), the trend in large and/or important production environments is - as seen in Linux (and Solaris) - to severely limit major OS upgrades. Of course the existing possibility to do is excellent, but more and more end-users, especially big ones, are going with big Linux distributions that basically stay frozen (except for security upgrades) for years. And this idea gets a +1 from me - productions releases that are expected to run for years should be able to "just work" without upgrading to the "kernel of the week". To do this, a stable anchor-point is required and that's what -RELEASEes should be for. I think the fact that not all our -RELEASES are created equal (some are "extended support" releases) should be more advertised and explained. --------------enig0CF52214415F0637A3158BF8 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 iD8DBQFHDWc7ldnAQVacBcgRAq0hAJ0d2UnljgQzZGFFgI2yEAgtMOeEhgCgiUdI acnTUxwg/Hfk5CSBz7Uu14s= =ruxS -----END PGP SIGNATURE----- --------------enig0CF52214415F0637A3158BF8-- From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 00:36: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 07CF516A417 for ; Thu, 11 Oct 2007 00:36:29 +0000 (UTC) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.freebsd.org (Postfix) with ESMTP id 2AC8813C47E for ; Thu, 11 Oct 2007 00:36:28 +0000 (UTC) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: from ednmsw510.dsto.defence.gov.au (ednmsw510.dsto.defence.gov.au [131.185.68.11]) by digger1.defence.gov.au (8.13.8/8.13.8) with ESMTP id l9B0OdRI017161 for ; Thu, 11 Oct 2007 09:54:39 +0930 (CST) Received: from fmbex510.dsto.defence.gov.au (fmbex510.dsto.defence.gov.au) by ednmsw510.dsto.defence.gov.au (Clearswift SMTPRS 5.2.9) with ESMTP id ; Thu, 11 Oct 2007 10:06:21 +0930 Received: from stlex510.dsto.defence.gov.au ([203.6.60.184]) by fmbex510.dsto.defence.gov.au with Microsoft SMTPSVC(6.0.3790.1830); Thu, 11 Oct 2007 10:36:21 +1000 Received: from obelix.dsto.defence.gov.au ([203.6.60.208]) by stlex510.dsto.defence.gov.au with Microsoft SMTPSVC(6.0.3790.1830); Thu, 11 Oct 2007 08:36:20 +0800 Received: from obelix.dsto.defence.gov.au (localhost [127.0.0.1]) by obelix.dsto.defence.gov.au (8.14.1/8.14.1) with ESMTP id l9B0aKqQ084622; Thu, 11 Oct 2007 08:36:20 +0800 (WST) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by obelix.dsto.defence.gov.au (8.14.1/8.14.1/Submit) id l9B0aJqI084621; Thu, 11 Oct 2007 08:36:19 +0800 (WST) (envelope-from wilkinsa) Date: Thu, 11 Oct 2007 08:36:19 +0800 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20071011003619.GA84433@obelix.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org, pyunyh@gmail.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline Organisation: Defence Science Technology Organisation User-Agent: Mutt/1.5.16 (2007-06-09) X-OriginalArrivalTime: 11 Oct 2007 00:36:20.0470 (UTC) FILETIME=[BE409160:01C80B9E] X-TM-AS-Product-Ver: SMEX-7.0.0.1526-5.0.1023-15476.000 X-TM-AS-Result: No--2.348300-0.000000-31 Content-Transfer-Encoding: 7bit Cc: pyunyh@gmail.com Subject: em0: watchdog timeout ... 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, 11 Oct 2007 00:36:30 -0000 Hi all, I have the following NIC: em0@pci5:4:0: class=0x020000 card=0x10018086 chip=0x10268086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '82545GM Gigabit Ethernet Controller' class = network subclass = ethernet And am consistently experiencing: em0: watchdog timeout -- resetting em0: link state changed to DOWN em0: link state changed to UP em0: watchdog timeout -- resetting em0: link state changed to DOWN em0: link state changed to UP em0: watchdog timeout -- resetting em0: link state changed to DOWN em0: link state changed to UP Anything I can do to help debug this ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 01:03: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 ACA5A16A419; Thu, 11 Oct 2007 01:03:23 +0000 (UTC) (envelope-from avatar@mmlab.cse.yzu.edu.tw) Received: from www.mmlab.cse.yzu.edu.tw (www.mmlab.cse.yzu.edu.tw [140.138.150.166]) by mx1.freebsd.org (Postfix) with ESMTP id 6FFBC13C43E; Thu, 11 Oct 2007 01:03:23 +0000 (UTC) (envelope-from avatar@mmlab.cse.yzu.edu.tw) Received: by www.mmlab.cse.yzu.edu.tw (qmail, from userid 1000) id 313078C9B01; Thu, 11 Oct 2007 08:43:42 +0800 (CST) Received: from localhost (localhost [127.0.0.1]) by www.mmlab.cse.yzu.edu.tw (qmail) with ESMTP id D811B8C9B00; Thu, 11 Oct 2007 08:43:42 +0800 (CST) Date: Thu, 11 Oct 2007 08:43:42 +0800 (CST) From: Tai-hwa Liang To: Pawel Jakub Dawidek In-Reply-To: <20071008121523.GM2327@garage.freebsd.pl> Message-ID: <0710110840301.59863@www.mmlab.cse.yzu.edu.tw> References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: ZFS kmem_map too small. 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, 11 Oct 2007 01:03:23 -0000 On Mon, 8 Oct 2007, Pawel Jakub Dawidek wrote: > Here are some updates: > > I was able to reproduce the panic by rsyncing big files and trying > bonnie++ test suggested in this thread. > > Can you guys retry with this patch: > > http://people.freebsd.org/~pjd/patches/vm_kern.c.2.patch > > It's a hack, yes, but allows to mitigate the problem quite well. I'm > looking for a solution that can be used for 7.0 before we find a better > fix. > > BTW. To use ZFS you _must_ increase vm.kmem_size/vm.kmem_size_max. > If you have the problem discussed here and you're using standard values, > please retry with vm.kmem_size/vm.kmem_size_max set to at least 600MB in > /boot/loader.conf. > > I'm not sure if it's not too late to ask re@ about increasing the > default kmem size at least on amd64. ~300MB we have there is silly > small. The latest patch does keep the system surviving longer than before; however, it eventually panicked with different message. - Testing case: while true; do bonnie++ -s 2048 -c 50 -x 20 done - ZFS related settings: vfs.root.mountfrom="zfs:universe" vm.kmem_size_max="629145600" vm.kmem_size="629145600" - zpool status: pool: universe state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM universe ONLINE 0 0 0 ad0s3d ONLINE 0 0 0 errors: No known data errors - panic messages: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x3916545d fault code = supervisor write, page not present instruction pointer = 0x20:0xc04d33c0 stack pointer = 0x28:0xf7b0e930 frame pointer = 0x28:0xf7b0e944 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 3477 (bonnie++) [thread pid 3477 tid 100159 ] Stopped at malloc_type_zone_allocated+0x70: addb %cl,0x758bf45d(%ebx) db> wh Tracing pid 3477 tid 100159 td 0xc4258a50 malloc_type_zone_allocated(c1076d20,0,2,1,0,...) at malloc_type_zone_allocated+0x70 malloc(40,c0824060,2,f7b0e9fc,c080df70,...) at malloc+0x69 zfs_kmem_alloc(40,2,c0607d3e,c3d66228,f7b0e998,...) at zfs_kmem_alloc+0x20 zfs_range_lock(c90da0ec,22f2da,0,1,0,...) at zfs_range_lock+0x20 zfs_freebsd_write(f7b0ebc4,0,0,0,c06be120,...) at zfs_freebsd_write+0x24b VOP_WRITE_APV(c08257c0,f7b0ebc4,c4258a50,c068d7f8,242,...) at VOP_WRITE_APV+0xb6 vn_write(c53bd0d8,f7b0ec60,c7835e00,0,c4258a50,...) at vn_write+0x247 dofilewrite(f7b0ec60,ffffffff,ffffffff,0,c53bd0d8,...) at dofilewrite+0x97 kern_writev(c4258a50,3,f7b0ec60,bfbfdf8b,1,...) at kern_writev+0x58 write(c4258a50,f7b0ecfc,c,f7b0eca4,c065d061,...) at write+0x4f syscall(f7b0ed38) at syscall+0x319 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (4, FreeBSD ELF32, write), eip = 0x282779a3, esp = 0xbfbfdf3c, ebp = 0xbfbfdf58 --- db> -- Cheers, Tai-hwa Liang From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 03:02: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 5A6BD16A41B for ; Thu, 11 Oct 2007 03:02:12 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.187]) by mx1.freebsd.org (Postfix) with ESMTP id CF3A313C4A5 for ; Thu, 11 Oct 2007 03:02:11 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by mu-out-0910.google.com with SMTP id w9so462263mue for ; Wed, 10 Oct 2007 20:02: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:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Y0qQkuysendxfBMRTTaf2qJJm8Yej7JfD5s0U0bBcg8=; b=QgzHDMtCE0VLXX+IkZgTYCwE1aIbHz2NVkOT2WdMUIzSEy+QshsBMRSZvivCa9p53mQB6V9laPYAz8vndz2PqNEHeT2f4xdoh/j2eeF2lHfNqJmkC6fvtFXANXQnEepe+KuWDIozABENvIy51It63w+V7JsmtEi7WJMxCi6ejcU= 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=cmodE60YtbD38B8iYkNPkvl6LLNn0K4HitykIgROpy2Wdd59Z9ZuUBcpiLcVzzOY7go+N33wvSVGakc4tbQnaEVeyW/vxr/v0ej9bzPjPj9pVK7NA6U3Ztj8jaX/4PNFvh3EX/jKN3U1wacsfVFw1ECoM+Ub3iIbEtnubZY9Fbk= Received: by 10.86.51.2 with SMTP id y2mr1082565fgy.1192071730179; Wed, 10 Oct 2007 20:02:10 -0700 (PDT) Received: by 10.86.100.19 with HTTP; Wed, 10 Oct 2007 20:02:10 -0700 (PDT) Message-ID: <2a41acea0710102002j5c09d285kac076ce2b5e4af41@mail.gmail.com> Date: Wed, 10 Oct 2007 20:02:10 -0700 From: "Jack Vogel" To: freebsd-current@freebsd.org, pyunyh@gmail.com In-Reply-To: <20071011003619.GA84433@obelix.dsto.defence.gov.au> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071011003619.GA84433@obelix.dsto.defence.gov.au> Cc: Subject: Re: em0: watchdog timeout ... 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, 11 Oct 2007 03:02:12 -0000 On 10/10/07, Wilkinson, Alex wrote: > Hi all, > > I have the following NIC: > > em0@pci5:4:0: class=0x020000 card=0x10018086 chip=0x10268086 rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = '82545GM Gigabit Ethernet Controller' > class = network > subclass = ethernet > > And am consistently experiencing: > > em0: watchdog timeout -- resetting > em0: link state changed to DOWN > em0: link state changed to UP > em0: watchdog timeout -- resetting > em0: link state changed to DOWN > em0: link state changed to UP > em0: watchdog timeout -- resetting > em0: link state changed to DOWN > em0: link state changed to UP > > Anything I can do to help debug this ? Well, add more detail for one, like timestamps on these events, do they happen once a minute, hour, day? You posted to current so I assume thats what you are running, is it the latest? What is your network like, for instance what is the link partner to this NIC, what kind of traffic, etc, etc.. Jack From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 06:33: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 ECABB16A419 for ; Thu, 11 Oct 2007 06:33:49 +0000 (UTC) (envelope-from ken@tydfam.jp) Received: from ns.tydfam.jp (ns.tydfam.jp [61.197.228.42]) by mx1.freebsd.org (Postfix) with ESMTP id 23BA413C447 for ; Thu, 11 Oct 2007 06:33:48 +0000 (UTC) (envelope-from ken@tydfam.jp) Received: from localhost (tyd3.sub.tydfam.jp [192.168.1.3]) by ns.tydfam.jp (8.14.1/8.14.1) with ESMTP id l9B5nIDp095113; Thu, 11 Oct 2007 14:49:18 +0900 (JST) (envelope-from ken@tydfam.jp) Date: Thu, 11 Oct 2007 14:50:38 +0900 (JST) Message-Id: <20071011.145038.85413808.ken@tydfam.jp> To: alex.kovalenko@verizon.net From: Ken Yamada In-Reply-To: <1192023887.1022.9.camel@RabbitsDen> References: <470CCBB6.3050506@sanbi.ac.za> <1192023887.1022.9.camel@RabbitsDen> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91/4527/Thu Oct 11 11:58:52 2007 on ns.tydfam.jp X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.1 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on ns.tydfam.jp Cc: freebsd-java@freebsd.org, pvh@sanbi.ac.za, freebsd-current@freebsd.org Subject: Re: Which java jdk to use on -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, 11 Oct 2007 06:33:50 -0000 Do you still need "-fno-tree-vrp"? I think that it is fixed sometime in the middle of Sept., and I do not need to add it at least to compile jdk15/16 with -current. I have a different problem with JVM, though. From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 07:27: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 C3AD216A417 for ; Thu, 11 Oct 2007 07:27:17 +0000 (UTC) (envelope-from ckadi35@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 6B37013C467 for ; Thu, 11 Oct 2007 07:27:17 +0000 (UTC) (envelope-from ckadi35@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so386930nfb for ; Thu, 11 Oct 2007 00:27: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; bh=4S1gaW8o1DmlgCVP5Rd3//XlWWDYrG8fjTVfaxvZpE0=; b=Ue4TH3LzuGfZrccc5oKyJ28h2FlfacINoPwsUKUiFY8ejhrid9xYAF/Nu/VuyEiRLlTXM10B8fzCsTmysG482Nyev7hnwDdFEWgVph/ZAyAIZK8ewPiAoBqHHb2wmXiYKMv/4j+N8AEgrVh41Inb6gLt5bcknlAEo4B6o/1S2qY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=fUGZS31aOX7SpKKa7HXxtMbs2gTo45qOXLkTmTA4l2bgyB+0pQKnCsp1BJ5guzroQKBZsVetqFP62TVXJdu4i92oGJGE/ZMpFwOJXubTMZjdm5zj7z+E8CWZ8RcEv8ZYnSHir5vWpsrVvShhc/Kn6fqRHn9UaU1WynztHOPdKj0= Received: by 10.78.200.20 with SMTP id x20mr1136148huf.1192087635690; Thu, 11 Oct 2007 00:27:15 -0700 (PDT) Received: by 10.78.206.20 with HTTP; Thu, 11 Oct 2007 00:27:15 -0700 (PDT) Message-ID: Date: Thu, 11 Oct 2007 09:27:15 +0200 From: ck To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: make error 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, 11 Oct 2007 07:27:17 -0000 Hi, I tryed to make the freeBSD snapshot 200709 and i get this error =3D=3D=3D> cddl/lib/libumem (de=FEend) make: d=F8n=B4t kn=F8w h=F8w t=F8 make umem.c. Sto=FE *** Err=F8r code 2 Stop in /usr/src/cddl/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --=20 Ch=E9rif From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 07:35: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 E0BB316A417 for ; Thu, 11 Oct 2007 07:35:02 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183]) by mx1.freebsd.org (Postfix) with ESMTP id A468313C461 for ; Thu, 11 Oct 2007 07:35:02 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so906813pyb for ; Thu, 11 Oct 2007 00:35: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=DcCL0APVXYRV3ypyd9TakVYGCCkSEDDy7bHEccHHmnU=; b=syavykbq7SroomPXS4wVnMl4gTXFmcQEFzzjP97lZctNTZFbcWUOAlSX27EFpjvV862NQnj8lKkzDh1688DRap0a9G/6laj+sIszM9bYAkePhpqVdGHbjpZw3bA2JzfIG1YLlEVfzbOCctrCmEQYeoGF3waVAQqMMKj38/nlQMs= 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=TLmJYQ+rhKvxwuLHNPPUIGpEhxvOTZAdn+CF1pYAxaQr62ySGUdHRGvRjQmEADgSbyvb4lbH1Kk5ue0MszDcL3g5NRnOCTlPh4FfuwfJ0jw5iVKIJ3kB5+0/0/2hf3Lc3ZF9JaCPThCGgfbS/VYLT9TebYKxEwT09MOdKCQQj/E= Received: by 10.65.155.19 with SMTP id h19mr3432274qbo.1192088101508; Thu, 11 Oct 2007 00:35:01 -0700 (PDT) Received: by 10.65.105.2 with HTTP; Thu, 11 Oct 2007 00:35:01 -0700 (PDT) Message-ID: Date: Thu, 11 Oct 2007 07:35:01 +0000 From: "Aryeh Friedman" To: ck In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-current@freebsd.org Subject: Re: make error 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, 11 Oct 2007 07:35:03 -0000 On 10/11/07, ck wrote: > Hi, > > I tryed to make the freeBSD snapshot 200709 and i get this error Install cvsup and update your sources then try again From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 08:09: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 0F92016A418; Thu, 11 Oct 2007 08:09:09 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from smtp.utwente.nl (unknown [IPv6:2001:610:1908:1000:204:23ff:feb5:7e66]) by mx1.freebsd.org (Postfix) with ESMTP id 9955613C44B; Thu, 11 Oct 2007 08:09:08 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from lux.student.utwente.nl (lux.student.utwente.nl [130.89.170.81]) by smtp.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id l9B0FOHh014795; Thu, 11 Oct 2007 02:15:25 +0200 From: Pieter de Goeje To: freebsd-current@freebsd.org Date: Thu, 11 Oct 2007 02:15:24 +0200 User-Agent: KMail/1.9.7 References: <1191175387.92510.6.camel@shumai.marcuscom.com> <470597DD.6080909@freebsd.org> In-Reply-To: <470597DD.6080909@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710110215.24824.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No Cc: Subject: Re: panic: ffs_blkfree: freeing free block 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, 11 Oct 2007 08:09:09 -0000 On Friday 05 October 2007, Eric Anderson wrote: > Arjan van Leeuwen wrote: > > 2007/10/3, Peter Jeremy : > >> On 2007-Oct-03 15:21:15 +0200, Arjan van Leeuwen > >> > >> wrote: > >>> Also, I note that everytime I panic, my currently opened files are > >> > >> reduced > >> > >>> to 0 bytes. Is that expected? > >> > >> It depends, are you talking about files being read or only files being > >> written? If this is just affecting writes, then this is a side-effect > >> of the stdio buffering, together with the write-back nature of the UFS > >> buffer cache in conjunction with soft-updates: Data on disk is > >> typically about 30 seconds behind reality and the file contents will > >> always be behind the file itself. It is quite normal for recently > >> written files (or files currently being written) to be truncated on > >> disk following a crash. > > > > Yep, these are recently written files indeed. Usually the files I had > > open in my editor while it paniced, files that I save often. > > Oh well... I'm setting my hopes on this panic being resolved soon then > > :). Thanks for the explanation. > > Can anyone provide access to the core dumps? Hi Eric, I've put a coredump and kernel.debug at http://lux.student.utwente.nl/~pyotr/panic/ along with the dmesg and kernel configuration file. uname -a: FreeBSD unforgiven.student.utwente.nl 7.0-CURRENT FreeBSD 7.0-CURRENT #8: Mon Oct 8 01:48:17 CEST 2007 pyotr@unforgiven.student.utwente.nl:/usr/obj/usr/src/sys/UNFORGIVEN amd64 I am not sure about the security impact of putting a coredump in a public place, so I didn't cc current. ("Somewhat" less public this way...) The panic often occurs while doing # portsnap fetch update # portversion -vl \< If you need anything else please let me know. With kind regards, Pieter de Goeje From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 08:31: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 163B916A41A for ; Thu, 11 Oct 2007 08:31:43 +0000 (UTC) (envelope-from cristiano.deana@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 B1E9613C4B6 for ; Thu, 11 Oct 2007 08:31:42 +0000 (UTC) (envelope-from cristiano.deana@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so399512nfb for ; Thu, 11 Oct 2007 01:31:41 -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=bYIgWlbprkgrBao3omHEKy6wO+Tc8bT+vl/0vK0ItWo=; b=LHcf7n3pIyODCpbpfav49hCXKfwwhUSRSfG//8B0exs+XTzteczUN5Z4rigE0egJDHkZ9ttSrp5hGlUEpIlTHyof7j+79T9zyY17bAbjqh52nYIpJAL6oxSm52i0NkmJ03Fj68tgz2+PQTjEm0+rEck3geXhkJAha50y0yOjQMk= 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=ewimVu33H0AlrYmJfYXGEea17V1Y8imXUGUvEBQMaHAnS6NEBNwNy6vubBBxVLwEQ4u3CrYsJnhMUWX+Bg+Mp8ShhlEyoA+nz8oa3iRmFH51QXobHCVGuTHs4lSdPqI0K5rThjIOvcmhTqgSYUijjCmnywhZCKA6YkpSq2BzJv0= Received: by 10.78.200.3 with SMTP id x3mr1162135huf.1192089780534; Thu, 11 Oct 2007 01:03:00 -0700 (PDT) Received: by 10.78.176.3 with HTTP; Thu, 11 Oct 2007 01:03:00 -0700 (PDT) Message-ID: Date: Thu, 11 Oct 2007 10:03:00 +0200 From: "Cristiano Deana" To: freebsd-current@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Subject: Re: make error 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, 11 Oct 2007 08:31:43 -0000 2007/10/11, Aryeh Friedman : > > I tryed to make the freeBSD snapshot 200709 and i get this error > > Install cvsup and update your sources then try again cvsup? why not using /usr/bin/csup ? -- Cris, member of G.U.F.I Italian FreeBSD User Group http://www.gufi.org/ From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 09:20: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 C930116A420 for ; Thu, 11 Oct 2007 09:20:58 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id 9260113C4A6 for ; Thu, 11 Oct 2007 09:20:58 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: by blah.sun-fish.com (Postfix, from userid 1002) id 6FF941B10EA4; Thu, 11 Oct 2007 11:20:56 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on blah.cmotd.com X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.3 Received: from hater.haters.org (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id C29F91B10C26; Thu, 11 Oct 2007 11:20:53 +0200 (CEST) Message-ID: <470DEAF5.2090404@moneybookers.com> Date: Thu, 11 Oct 2007 12:20:53 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.6 (X11/20070918) MIME-Version: 1.0 To: Ken Yamada References: <470CCBB6.3050506@sanbi.ac.za> <1192023887.1022.9.camel@RabbitsDen> <20071011.145038.85413808.ken@tydfam.jp> In-Reply-To: <20071011.145038.85413808.ken@tydfam.jp> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91.2/4529/Thu Oct 11 08:54:06 2007 on blah.cmotd.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org, pvh@sanbi.ac.za, alex.kovalenko@verizon.net, freebsd-java@freebsd.org Subject: Re: Which java jdk to use on -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, 11 Oct 2007 09:20:58 -0000 Hi Ken, Ken Yamada wrote: > Do you still need "-fno-tree-vrp"? > > I think that it is fixed sometime in the middle of Sept., and I do not need to add it at least to compile jdk15/16 with -current. > > I have a different problem with JVM, though. > I read somewhere that in latest -current "-fno-tree-vrp" is set by default, and that's the reason to be able to compile jdk without manually setting it. Although I'm not 100% sure :) > > _______________________________________________ > 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" > -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 11:30: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 B9C8E16A418 for ; Thu, 11 Oct 2007 11:30:25 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from crivens.terrorteam.de (crivens.terrorteam.de [81.169.171.191]) by mx1.freebsd.org (Postfix) with ESMTP id A5C4A13C461 for ; Thu, 11 Oct 2007 11:30:25 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from localhost (localhost [127.0.0.1]) by crivens.terrorteam.de (Postfix) with ESMTP id CFA0FB023F for ; Thu, 11 Oct 2007 13:30:23 +0200 (CEST) MIME-Version: 1.0 Date: Thu, 11 Oct 2007 13:30:23 +0200 From: Marian Hettwer To: freebsd-current@freebsd.org Message-ID: X-Sender: mh@kernel32.de User-Agent: RoundCube Webmail/0.1b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Subject: mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 129 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, 11 Oct 2007 11:30:25 -0000 Hi All, I'm trying out -CURRENT on an IBM HS21 blade. So far the machine looks stable. Only thing that bothers me is the message as stated above. db46-23-freebsd# uptime 11:25AM up 55 mins, 5 users, load averages: 0.01, 0.90, 1.21 db46-23-freebsd# dmesg | grep -c "QUEUE FULL EVENT" 111 db46-23-freebsd# uname -a FreeBSD db46-23-freebsd 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Thu Oct 11 11:09:46 CEST 2007 root@blowfish:/usr/obj/amd64/usr/src/sys/GENERIC amd64 db46-23-freebsd# Is this something to worry about? The LSI Logic controller in question is configured as a hardware RAID-0 Informations about the controller: at boot time from dmesg: mpt0: port 0x4000-0x40ff mem 0xdeffc000-0xdeffffff,0xdefe0000-0xdefeffff irq 16 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). mpt0: mpt_cam_event: 0x21 mpt0: Unhandled Event Notify Frame. Event 0x21 (ACK not required). mpt0: mpt_cam_event: 0x21 mpt0: Unhandled Event Notify Frame. Event 0x21 (ACK not required). da0 at mpt0 bus 0 target 0 lun 0 and from pciconf -lv mpt0@pci0:2:0:0: class=0x010000 card=0x03061014 chip=0x00561000 rev=0x02 hdr=0x00 vendor = 'LSI Logic (Was: Symbios Logic, NCR)' device = 'SAS 3000 series, 4-port with 1064E -StorPort' class = mass storage subclass = SCSI regards, Marian PS.: FWIW, Linux 2.6.20 had severe problems with this specific mpt controller - patches came with Linux 2.6.21 Looks like the LSI Logic stuff isn't very well supported. On the other hand, there's now way around them when using IBM blades :( Same counts for the bce(4) NIC. From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 11:42: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 EF49516A419 for ; Thu, 11 Oct 2007 11:42:11 +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 B3B7913C4BE for ; Thu, 11 Oct 2007 11:42:11 +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 l9BBg4AJ040609; Thu, 11 Oct 2007 05:42:04 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <470E0BF3.6010605@samsco.org> Date: Thu, 11 Oct 2007 05:41:39 -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: Marian Hettwer References: In-Reply-To: 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]); Thu, 11 Oct 2007 05:42:04 -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: freebsd-current@freebsd.org Subject: Re: mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 129 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, 11 Oct 2007 11:42:12 -0000 Marian Hettwer wrote: > Hi All, > > I'm trying out -CURRENT on an IBM HS21 blade. So far the machine looks stable. > Only thing that bothers me is the message as stated above. > > db46-23-freebsd# uptime > 11:25AM up 55 mins, 5 users, load averages: 0.01, 0.90, 1.21 > db46-23-freebsd# dmesg | grep -c "QUEUE FULL EVENT" > 111 > db46-23-freebsd# uname -a > FreeBSD db46-23-freebsd 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Thu Oct 11 11:09:46 CEST 2007 root@blowfish:/usr/obj/amd64/usr/src/sys/GENERIC amd64 > db46-23-freebsd# > > Is this something to worry about? > No, it's nothing to worry about. The message can probably be put under bootverbose. > The LSI Logic controller in question is configured as a hardware RAID-0 > Informations about the controller: > at boot time from dmesg: > > mpt0: port 0x4000-0x40ff mem 0xdeffc000-0xdeffffff,0xdefe0000-0xdefeffff irq 16 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). > mpt0: mpt_cam_event: 0x21 > mpt0: Unhandled Event Notify Frame. Event 0x21 (ACK not required). > mpt0: mpt_cam_event: 0x21 > mpt0: Unhandled Event Notify Frame. Event 0x21 (ACK not required). > da0 at mpt0 bus 0 target 0 lun 0 > > and from pciconf -lv > > mpt0@pci0:2:0:0: class=0x010000 card=0x03061014 chip=0x00561000 rev=0x02 hdr=0x00 > vendor = 'LSI Logic (Was: Symbios Logic, NCR)' > device = 'SAS 3000 series, 4-port with 1064E -StorPort' > class = mass storage > subclass = SCSI > > regards, > Marian > PS.: FWIW, Linux 2.6.20 had severe problems with this specific mpt controller - patches came with Linux 2.6.21 > Looks like the LSI Logic stuff isn't very well supported. On the other hand, there's now way around them when using IBM blades :( > Same counts for the bce(4) NIC. Are you saying that the LSI Logic stuff is not well supported in FreeBSD or in Linux? Neither statement would be at all true. Same with BCE, it's quite well supported. Scott From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 12:00: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 1F1D616A49A for ; Thu, 11 Oct 2007 12:00:10 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from crivens.terrorteam.de (crivens.terrorteam.de [81.169.171.191]) by mx1.freebsd.org (Postfix) with ESMTP id E0A0513C43E for ; Thu, 11 Oct 2007 12:00:09 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from localhost (localhost [127.0.0.1]) by crivens.terrorteam.de (Postfix) with ESMTP id 9447AB023F; Thu, 11 Oct 2007 14:00:08 +0200 (CEST) MIME-Version: 1.0 Date: Thu, 11 Oct 2007 14:00:08 +0200 From: Marian Hettwer To: Scott Long In-Reply-To: <470E0BF3.6010605@samsco.org> References: <470E0BF3.6010605@samsco.org> Message-ID: X-Sender: mh@kernel32.de User-Agent: RoundCube Webmail/0.1b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org Subject: Re: mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 129 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, 11 Oct 2007 12:00:10 -0000 Hi Scott, On Thu, 11 Oct 2007 05:41:39 -0600, Scott Long wrote: > Marian Hettwer wrote: >> Hi All, >> >> I'm trying out -CURRENT on an IBM HS21 blade. So far the machine looks > stable. >> Only thing that bothers me is the message as stated above. >> >> >> Is this something to worry about? >> > > No, it's nothing to worry about. The message can probably be put under > bootverbose. > Oh. glad to hear :) >> PS.: FWIW, Linux 2.6.20 had severe problems with this specific mpt > controller - patches came with Linux 2.6.21 >> Looks like the LSI Logic stuff isn't very well supported. On the other > hand, there's now way around them when using IBM blades :( >> Same counts for the bce(4) NIC. > > Are you saying that the LSI Logic stuff is not well supported in FreeBSD > or in Linux? Neither statement would be at all true. Same with BCE, > it's quite well supported. > Well, both the SAS part of mpt(4) and the functionality for BCM5708S weren't available in FreeBSD 6. Of course, this doesn't obviously mean that they're not well supported. In regards to the specific mpt(4). It got patches in Linux 2.6.21 to get it working. Since I can't provide details, let's stick with: Great to see that both, the mpt(4) and the bce(4) (the specific ones used in HS21 blades) are supported. I already did some stress testing with MySQL in a production replication setup and everything looks stable. So far, so good. If I encounter any problems (panics, whatever) I'd be glad to help out with testing and testing and testing :) ./Marian From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 12:05: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 489F716A419 for ; Thu, 11 Oct 2007 12:05:59 +0000 (UTC) (envelope-from news@nermal.rz1.convenimus.net) Received: from mx4.netclusive.de (mx4.netclusive.de [89.110.132.136]) by mx1.freebsd.org (Postfix) with ESMTP id 154A813C448 for ; Thu, 11 Oct 2007 12:05:58 +0000 (UTC) (envelope-from news@nermal.rz1.convenimus.net) Received: from nermal.rz1.convenimus.net (Fdd69.f.ppp-pool.de [195.4.221.105]) (Authenticated sender: ncf1534p2) by mx4.netclusive.de (Postfix) with ESMTP id 853535E0167 for ; Thu, 11 Oct 2007 14:05:56 +0200 (CEST) Received: by nermal.rz1.convenimus.net (Postfix, from userid 8) id D980215217; Thu, 11 Oct 2007 13:58:10 +0200 (CEST) To: freebsd-current@freebsd.org Path: not-for-mail From: Christian Baer Newsgroups: gmane.os.freebsd.current Date: Thu, 11 Oct 2007 13:58:10 +0200 (CEST) Organization: Convenimus Projekt Lines: 10 Message-ID: References: <86przndoe8.fsf@ds4.des.no> NNTP-Posting-Host: sunny.rz1.convenimus.net Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: nermal.rz1.convenimus.net 1192103890 93945 192.168.100.5 (11 Oct 2007 11:58:10 GMT) X-Complaints-To: abuse@convenimus.net NNTP-Posting-Date: Thu, 11 Oct 2007 11:58:10 +0000 (UTC) User-Agent: slrn/0.9.8.1 (FreeBSD/6.2-RELEASE-p8 (sparc64)) Subject: Re: suggest renaming and extending the -CURRENT and -STABLE lines 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, 11 Oct 2007 12:05:59 -0000 On Wed, 10 Oct 2007 16:39:59 +0200 Dag-Erling Smørgrav wrote: > YMMV. I run both CURRENT and STABLE on production systems. That is your call to make and allways will be, even if the names are changed. The point just is, that both are not recommended in the documentation. And the -STABLE just doesn't reflekt that. Regards Chris From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 12:11: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 42FA616A473 for ; Thu, 11 Oct 2007 12:11:30 +0000 (UTC) (envelope-from news@nermal.rz1.convenimus.net) Received: from mx2.netclusive.de (mx2.netclusive.de [89.110.132.132]) by mx1.freebsd.org (Postfix) with ESMTP id 05F7213C4C3 for ; Thu, 11 Oct 2007 12:11:29 +0000 (UTC) (envelope-from news@nermal.rz1.convenimus.net) Received: from nermal.rz1.convenimus.net (Fdd69.f.ppp-pool.de [195.4.221.105]) (Authenticated sender: ncf1534p2) by mx2.netclusive.de (Postfix) with ESMTP id A64A52602EA for ; Thu, 11 Oct 2007 14:11:26 +0200 (CEST) Received: by nermal.rz1.convenimus.net (Postfix, from userid 8) id A827E15217; Thu, 11 Oct 2007 14:03:42 +0200 (CEST) To: freebsd-current@freebsd.org Path: not-for-mail From: Christian Baer Newsgroups: gmane.os.freebsd.current Date: Thu, 11 Oct 2007 14:03:42 +0200 (CEST) Organization: Convenimus Projekt Lines: 19 Message-ID: References: <86przndoe8.fsf@ds4.des.no> NNTP-Posting-Host: sunny.rz1.convenimus.net X-Trace: nermal.rz1.convenimus.net 1192104222 93945 192.168.100.5 (11 Oct 2007 12:03:42 GMT) X-Complaints-To: abuse@convenimus.net NNTP-Posting-Date: Thu, 11 Oct 2007 12:03:42 +0000 (UTC) User-Agent: slrn/0.9.8.1 (FreeBSD/6.2-RELEASE-p8 (sparc64)) Subject: Re: suggest renaming and extending the -CURRENT and -STABLE lines 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, 11 Oct 2007 12:11:30 -0000 On Wed, 10 Oct 2007 17:29:12 +0200 Ivan Voras wrote: > This will probably degenerate into a bikeshed so I'll add just one > suggestion: rename "-STABLE" to "-ABISTABLE" or "-STABLEABI" and carry > on as usual. :) That however is a little hard for an inexperienced user to read or understand. It may be the technically correct term but we all know that there are lots of those around - not only in CS - that can't possibly mean anything useful to an outsider. Either we give all the branches names that are technically correct but at the same time let the user grasp what he is doing, or we give completely meaningless names (in a technical sense) like "Peter", "Paul" and "Mary" and write characterizations for each of these. Using names like this will force the user to read the documentation before choosing a branch. Regards Chris From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 12:19: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 A84B816A417 for ; Thu, 11 Oct 2007 12:19:09 +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 61D7313C4A3 for ; Thu, 11 Oct 2007 12:19:09 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender:X-Spam-Status:Subject; b=J2rNu2BvTN3MBR2xqywsAgH122Ng3eqvWMkcTCfbpqNHRpGTeT5d0cXUX9dmLU6TlmMcY5cTbRSpefAKMJLov8S/vrG+DdbmWBDVa1zMJMzJzS9Cylkm3A4Hl+9ELCR5GzCSZgI8in2NkoLiAmKDNZQw9UXFbyE7GmOXtFsFyew=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by pobox.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1Ifx0O-000OfZ-Ae; Thu, 11 Oct 2007 16:19:08 +0400 Date: Thu, 11 Oct 2007 16:19:03 +0400 From: Eygene Ryabinkin To: Christian Baer Message-ID: <20071011121903.GE3943@void.codelabs.ru> References: MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-1.9 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_40 Cc: freebsd-current@freebsd.org Subject: Re: suggest renaming and extending the -CURRENT and -STABLE lines 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, 11 Oct 2007 12:19:09 -0000 Christian, good day. Wed, Oct 10, 2007 at 03:52:14PM +0200, Christian Baer wrote: > If someone sees the result of RELENG_6 is called STABLE, he or she will > problably think, this is the line where bug fixes are added, security > problems fixed and the whole thing is meant for production systems. While > the first two things may be true, I would not suggest RELENG_6 for > production systems. Normally the -STABLE line works fine. But I *have* > times in the past where a driver was changes and suddenly the system > *didn't* work after a reboot or showed strange behaviour. But let us look at the issue from the user's side: where can he get RELENG_6? Only cvsup, CTM and monthly snapshots come into my mind. Regular CDs/ISOs will deliver RELENG_6_x. Users that are trying to use snapshots should realize that they're doing it at their own risk, but maybe documentation and FTP directory messages should tell them that shapshots can broke their installations. Seems like CTM users are the educated persons, so they won't need any clarifications. Examples of the CVSup supfiles are the good candidates for the short messages clarifying the nature of the -STABLE and referring to the relevant Handbook sections for more explanations. -- Eygene From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 12:32: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 707FD16A419 for ; Thu, 11 Oct 2007 12:32:21 +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 3871E13C448 for ; Thu, 11 Oct 2007 12:32:20 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Ifx9u-0004Ap-4G for freebsd-current@freebsd.org; Thu, 11 Oct 2007 12:28:58 +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 ; Thu, 11 Oct 2007 12:28:58 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 11 Oct 2007 12:28:58 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Thu, 11 Oct 2007 14:27:41 +0200 Lines: 6 Message-ID: References: <470E0BF3.6010605@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.6 (X11/20070801) In-Reply-To: Sender: news Subject: Re: mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 129 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, 11 Oct 2007 12:32:21 -0000 Marian Hettwer wrote: > Well, both the SAS part of mpt(4) and the functionality for BCM5708S weren't available in FreeBSD 6. I think I've run LSI SAS under 6.2 just fine. The newer "serdes" BCMs are supported on 6-STABLE (i.e. added after 6.2 was released). From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 12: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 BE78B16A41B for ; Thu, 11 Oct 2007 12:34:53 +0000 (UTC) (envelope-from news@nermal.rz1.convenimus.net) Received: from mx1.netclusive.de (mx1.netclusive.de [89.110.132.131]) by mx1.freebsd.org (Postfix) with ESMTP id 60B0113C4BA for ; Thu, 11 Oct 2007 12:34:52 +0000 (UTC) (envelope-from news@nermal.rz1.convenimus.net) Received: from nermal.rz1.convenimus.net (Fdd69.f.ppp-pool.de [195.4.221.105]) (Authenticated sender: ncf1534p2) by mx1.netclusive.de (Postfix) with ESMTP id 5D222DE80B2 for ; Thu, 11 Oct 2007 14:34:49 +0200 (CEST) Received: by nermal.rz1.convenimus.net (Postfix, from userid 8) id AF0BB15217; Thu, 11 Oct 2007 14:27:04 +0200 (CEST) To: freebsd-current@freebsd.org Path: not-for-mail From: Christian Baer Newsgroups: gmane.os.freebsd.current Date: Thu, 11 Oct 2007 14:27:04 +0200 (CEST) Organization: Convenimus Projekt Lines: 42 Message-ID: References: <86przndoe8.fsf@ds4.des.no> <20071010231643.GF58929@over-yonder.net> NNTP-Posting-Host: sunny.rz1.convenimus.net X-Trace: nermal.rz1.convenimus.net 1192105624 93945 192.168.100.5 (11 Oct 2007 12:27:04 GMT) X-Complaints-To: abuse@convenimus.net NNTP-Posting-Date: Thu, 11 Oct 2007 12:27:04 +0000 (UTC) User-Agent: slrn/0.9.8.1 (FreeBSD/6.2-RELEASE-p8 (sparc64)) Subject: Re: suggest renaming and extending the -CURRENT and -STABLE lines 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, 11 Oct 2007 12:34:53 -0000 On Thu, 11 Oct 2007 01:58:51 +0200 Ivan Voras wrote: > Unfortunately (for this developer-centric practice), the trend in large > and/or important production environments is - as seen in Linux (and > Solaris) - to severely limit major OS upgrades. I don't really see what's so unfortunate about that. Most admins (including myself) go by the rule "If it ain't broken, don't fix it!" Production systems, especially in companies are there to do something, and that is not trying out the latest new gadgets out there. In my company, out database server is *very* important and although downtime would not cost us any money off hand, we wouldn't be able to serve our customers anymore, since the information stored in there actually is the service we provide. I am very careful about trying out everything new out there, because every update bears the risk of downtime. And both -STABLE, but especially -CURRENT have risks of that sort. > Of course the existing possibility to do is excellent, but more and more > end-users, especially big ones, are going with big Linux distributions > that basically stay frozen (except for security upgrades) for years. And > this idea gets a +1 from me - productions releases that are expected to > run for years should be able to "just work" without upgrading to the > "kernel of the week". To do this, a stable anchor-point is required and > that's what -RELEASEes should be for. I think the fact that not all our > -RELEASES are created equal (some are "extended support" releases) > should be more advertised and explained. I'm not even sure we should board that train completely. Basicly, RELENG_x_y is just that, but is could also be a good idea to have and alternative. Something that is stable but can still be updated. Usually, an update from one release to the next is relatively painless (major releases excluded). I kept a machine running on RELENG_4 from 4.0-RELEASE until now without ever having to change or reinstall the packages on it. So it is possible. The next step would be to have something that updates like RELENG_x but only uses tested and stable code like RELENG_x_y without confining the user to a single release. Regards Chris From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 12:42: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 4BC1216A418 for ; Thu, 11 Oct 2007 12:42:03 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.226]) by mx1.freebsd.org (Postfix) with ESMTP id F212213C491 for ; Thu, 11 Oct 2007 12:42:02 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: by wr-out-0506.google.com with SMTP id 70so292080wra for ; Thu, 11 Oct 2007 05:42:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=beta; h=domainkey-signature:received:received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; bh=aLS0Yptkxg4zmElqiH/WSWBXM78ihs+aWSAoQP+X328=; b=TC8JZ4zoEJeLbpNQ1HmipIE+9k6QrC9ee1AXYjX14rMo9qCXw3aeAmcfbIkC/u+JPIjnw2iDRPJ2J0AulD5+eCKH2KOsrT99xw3fAsqUxZsp3gJDR7RAEvm9sOA21RB3hzrjLs7BvcBnPuejttoBx04XBagm1bGzp/EolND1Ef4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; b=THFDb2FR6ERceaZiwh0GTJHASHSCeyisdvnvD/An/G12P9LCuOKtnS/wlaFvp7ZtL8tlVmnc6+HHUimnta7WPOdFvUrxSzp3wvf1At84VGPKZ1LZlzfuQeEc0okWKijOTqGSLX+IgeRHMAt8t7Uw6jdk4ngdUShBwc1YVhlbY+E= Received: by 10.90.115.9 with SMTP id n9mr2856504agc.1192106124635; Thu, 11 Oct 2007 05:35:24 -0700 (PDT) Received: from ?127.0.0.1? ( [217.206.187.79]) by mx.google.com with ESMTPS id f7sm10140143nfh.2007.10.11.05.35.23 (version=SSLv3 cipher=RC4-MD5); Thu, 11 Oct 2007 05:35:23 -0700 (PDT) From: Tom Evans To: Marian Hettwer In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-IglZq98aRZqdY1K2rMBe" Date: Thu, 11 Oct 2007 13:35:22 +0100 Message-Id: <1192106122.1677.28.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.10.2 FreeBSD GNOME Team Port Cc: freebsd-current@freebsd.org Subject: Re: mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 129 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, 11 Oct 2007 12:42:03 -0000 --=-IglZq98aRZqdY1K2rMBe Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2007-10-11 at 13:30 +0200, Marian Hettwer wrote: > Hi All, >=20 > I'm trying out -CURRENT on an IBM HS21 blade. So far the machine looks st= able. > Only thing that bothers me is the message as stated above. >=20 > db46-23-freebsd# uptime > 11:25AM up 55 mins, 5 users, load averages: 0.01, 0.90, 1.21 > db46-23-freebsd# dmesg | grep -c "QUEUE FULL EVENT" > 111 > db46-23-freebsd# uname -a > FreeBSD db46-23-freebsd 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Thu Oct 11 11= :09:46 CEST 2007 root@blowfish:/usr/obj/amd64/usr/src/sys/GENERIC amd6= 4 > db46-23-freebsd# >=20 > Is this something to worry about? >=20 > The LSI Logic controller in question is configured as a hardware RAID-0 > Informations about the controller: > at boot time from dmesg: >=20 > mpt0: port 0x4000-0x40ff mem 0xdeffc000-0xdef= fffff,0xdefe0000-0xdefeffff irq 16 at device 0.0 on pci2 > mpt0: [ITHREAD] > mpt0: MPI Version=3D1.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). > mpt0: mpt_cam_event: 0x21 > mpt0: Unhandled Event Notify Frame. Event 0x21 (ACK not required). > mpt0: mpt_cam_event: 0x21 > mpt0: Unhandled Event Notify Frame. Event 0x21 (ACK not required). > da0 at mpt0 bus 0 target 0 lun 0 >=20 > and from pciconf -lv >=20 > mpt0@pci0:2:0:0: class=3D0x010000 card=3D0x03061014 chip=3D0x00561= 000 rev=3D0x02 hdr=3D0x00 > vendor =3D 'LSI Logic (Was: Symbios Logic, NCR)' > device =3D 'SAS 3000 series, 4-port with 1064E -StorPort' > class =3D mass storage > subclass =3D SCSI >=20 > regards, > Marian > PS.: FWIW, Linux 2.6.20 had severe problems with this specific mpt contro= ller - patches came with Linux 2.6.21 > Looks like the LSI Logic stuff isn't very well supported. On the other ha= nd, there's now way around them when using IBM blades :( > Same counts for the bce(4) NIC. >=20 IIRC both mpt(4) and bce(4) have vendor supported drivers, so I'd be surprised if they didn't work well. Here at work, we had some issues with a bce(4) device in about 20 of our Dell boxes running RELENG_6_2 and David Christensen (Broadcom employee) helped fix them and make them work lovely (allowing us to cancel an order of ~20 PCIE em cards :) Tom --=-IglZq98aRZqdY1K2rMBe Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBHDhiKlcRvFfyds/cRAsUVAJ9UemLr3Y96VVi3qnLVUyZJ5/IK9wCffyZO Lhvc7j4ThvjykrSaf2GXrIs= =a5lD -----END PGP SIGNATURE----- --=-IglZq98aRZqdY1K2rMBe-- From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 12:42: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 3186816A41A for ; Thu, 11 Oct 2007 12:42:35 +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 E6A7F13C45A for ; Thu, 11 Oct 2007 12:42:34 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IfxMg-0006Un-BJ for freebsd-current@freebsd.org; Thu, 11 Oct 2007 12:42:10 +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 ; Thu, 11 Oct 2007 12:42:10 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 11 Oct 2007 12:42:10 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Thu, 11 Oct 2007 14:41:43 +0200 Lines: 13 Message-ID: References: <86przndoe8.fsf@ds4.des.no> <20071010231643.GF58929@over-yonder.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.6 (X11/20070801) In-Reply-To: Sender: news Subject: Re: suggest renaming and extending the -CURRENT and -STABLE lines 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, 11 Oct 2007 12:42:35 -0000 Christian Baer wrote: > On Thu, 11 Oct 2007 01:58:51 +0200 Ivan Voras wrote: > >> Unfortunately (for this developer-centric practice), the trend in large >> and/or important production environments is - as seen in Linux (and >> Solaris) - to severely limit major OS upgrades. > > I don't really see what's so unfortunate about that. Most admins > (including myself) go by the rule "If it ain't broken, don't fix it!" You misunderstood, I agree with the practice :) It's "unfortunate" for developers :) From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 12:45: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 B374516A417 for ; Thu, 11 Oct 2007 12:45: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 7CACC13C468 for ; Thu, 11 Oct 2007 12:45:24 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1IfxPS-0006pW-TH for freebsd-current@freebsd.org; Thu, 11 Oct 2007 12:45:02 +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 ; Thu, 11 Oct 2007 12:45:02 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 11 Oct 2007 12:45:02 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Thu, 11 Oct 2007 14:42:54 +0200 Lines: 10 Message-ID: References: <470E0BF3.6010605@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.6 (X11/20070801) In-Reply-To: Sender: news Subject: Re: mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 129 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, 11 Oct 2007 12:45:24 -0000 Ivan Voras wrote: > Marian Hettwer wrote: > >> Well, both the SAS part of mpt(4) and the functionality for BCM5708S weren't available in FreeBSD 6. > > I think I've run LSI SAS under 6.2 just fine. The newer "serdes" BCMs > are supported on 6-STABLE (i.e. added after 6.2 was released). On the other hand, 7-STABLE was branched today (unfortunately without my favorite patches) so most new users will want to go with it... From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 12:47: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 65C3516A41A for ; Thu, 11 Oct 2007 12:47:51 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from smtp.utwente.nl (unknown [IPv6:2001:610:1908:1000:204:23ff:feb5:7e66]) by mx1.freebsd.org (Postfix) with ESMTP id E242D13C442 for ; Thu, 11 Oct 2007 12:47:50 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from lux.student.utwente.nl (lux.student.utwente.nl [130.89.170.81]) by smtp.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id l9BAPtHh001913 for ; Thu, 11 Oct 2007 12:25:56 +0200 From: Pieter de Goeje To: freebsd-current@freebsd.org Date: Thu, 11 Oct 2007 12:25:55 +0200 User-Agent: KMail/1.9.7 References: <1191175387.92510.6.camel@shumai.marcuscom.com> <470597DD.6080909@freebsd.org> <200710110215.24824.pieter@degoeje.nl> In-Reply-To: <200710110215.24824.pieter@degoeje.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710111225.55719.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No Subject: Re: panic: ffs_blkfree: freeing free block 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, 11 Oct 2007 12:47:51 -0000 On Thursday 11 October 2007, Pieter de Goeje wrote: > On Friday 05 October 2007, Eric Anderson wrote: > > Arjan van Leeuwen wrote: > > > 2007/10/3, Peter Jeremy : > > >> On 2007-Oct-03 15:21:15 +0200, Arjan van Leeuwen > > >> > > >> wrote: > > >>> Also, I note that everytime I panic, my currently opened files are > > >> > > >> reduced > > >> > > >>> to 0 bytes. Is that expected? > > >> > > >> It depends, are you talking about files being read or only files being > > >> written? If this is just affecting writes, then this is a side-effect > > >> of the stdio buffering, together with the write-back nature of the UFS > > >> buffer cache in conjunction with soft-updates: Data on disk is > > >> typically about 30 seconds behind reality and the file contents will > > >> always be behind the file itself. It is quite normal for recently > > >> written files (or files currently being written) to be truncated on > > >> disk following a crash. > > > > > > Yep, these are recently written files indeed. Usually the files I had > > > open in my editor while it paniced, files that I save often. > > > Oh well... I'm setting my hopes on this panic being resolved soon then > > > > > > :). Thanks for the explanation. > > > > Can anyone provide access to the core dumps? > > Hi Eric, > > I've put a coredump and kernel.debug at > http://lux.student.utwente.nl/~pyotr/panic/ along with the dmesg and kernel > configuration file. This address is no longer valid. Eric, if you are reading this, I've sent you mail with the correct address :D. > > uname -a: > FreeBSD unforgiven.student.utwente.nl 7.0-CURRENT FreeBSD 7.0-CURRENT #8: > Mon Oct 8 01:48:17 CEST 2007 > pyotr@unforgiven.student.utwente.nl:/usr/obj/usr/src/sys/UNFORGIVEN amd64 > > I am not sure about the security impact of putting a coredump in a public > place, so I didn't cc current. ("Somewhat" less public this way...) > > The panic often occurs while doing > # portsnap fetch update > # portversion -vl \< > > If you need anything else please let me know. > > With kind regards, > Pieter de Goeje From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 12:57: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 5245016A417 for ; Thu, 11 Oct 2007 12:57:40 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from bsd.ultra-secure.de (bsd.ultra-secure.de [62.146.20.26]) by mx1.freebsd.org (Postfix) with ESMTP id A5CD613C48E for ; Thu, 11 Oct 2007 12:57:39 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (qmail 55051 invoked by uid 89); 11 Oct 2007 12:40:08 -0000 Received: by simscan 1.1.0 ppid: 55024, pid: 55036, t: 2.7766s scanners: attach: 1.1.0 clamav: 0.88.7/m:43/d:3620 spam: 3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on bsd.ultra-secure.de X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.7 Received: from unknown (HELO ?212.71.117.70?) (rainer@ultra-secure.de@212.71.117.70) by bsd.ultra-secure.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 11 Oct 2007 12:40:05 -0000 Message-ID: <470E177B.7080007@ultra-secure.de> Date: Thu, 11 Oct 2007 14:30:51 +0200 From: Rainer Duffner User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.12) Gecko/20060911 SUSE/1.5.0.12-3.4 Thunderbird/1.5.0.12 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: Marian Hettwer References: <470E0BF3.6010605@samsco.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 129 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, 11 Oct 2007 12:57:40 -0000 Marian Hettwer wrote: > > Well, both the SAS part of mpt(4) and the functionality for BCM5708S weren't available in FreeBSD 6. But they work in STABLE. All I had to do was to download a STABLE-snapshot. (CURRENT is a no-go in production here) It's also a problem for older HS20 blades. > If I encounter any problems (panics, whatever) I'd be glad to help out with testing and testing and testing :) > Until now, no problems have occured. But we don't do a lot of local disk I/O on them, IIRC. cheers, Rainer From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 12:58: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 71B2D16A421 for ; Thu, 11 Oct 2007 12:58:31 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from crivens.terrorteam.de (crivens.terrorteam.de [81.169.171.191]) by mx1.freebsd.org (Postfix) with ESMTP id 3BF5013C4A6 for ; Thu, 11 Oct 2007 12:58:31 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from localhost (localhost [127.0.0.1]) by crivens.terrorteam.de (Postfix) with ESMTP id D9F13B023F; Thu, 11 Oct 2007 14:58:29 +0200 (CEST) MIME-Version: 1.0 Date: Thu, 11 Oct 2007 14:58:29 +0200 From: Marian Hettwer To: Ivan Voras In-Reply-To: References: Message-ID: <5ae61a82c2d6331a3400fbead53d216c@127.0.0.1> X-Sender: mh@kernel32.de User-Agent: RoundCube Webmail/0.1b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org Subject: Re: mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 129 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, 11 Oct 2007 12:58:31 -0000 On Thu, 11 Oct 2007 14:27:41 +0200, Ivan Voras wrote: > Marian Hettwer wrote: > >> Well, both the SAS part of mpt(4) and the functionality for BCM5708S > weren't available in FreeBSD 6. > > I think I've run LSI SAS under 6.2 just fine. The newer "serdes" BCMs > are supported on 6-STABLE (i.e. added after 6.2 was released). > Good to know! thanks, I'll give it a try later :) ./Marian From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 12:59: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 236F516A469 for ; Thu, 11 Oct 2007 12:59:25 +0000 (UTC) (envelope-from news@nermal.rz1.convenimus.net) Received: from mx4.netclusive.de (mx4.netclusive.de [89.110.132.136]) by mx1.freebsd.org (Postfix) with ESMTP id BDB7013C4A8 for ; Thu, 11 Oct 2007 12:59:24 +0000 (UTC) (envelope-from news@nermal.rz1.convenimus.net) Received: from nermal.rz1.convenimus.net (Fdd69.f.ppp-pool.de [195.4.221.105]) (Authenticated sender: ncf1534p2) by mx4.netclusive.de (Postfix) with ESMTP id D0B4A5E0189 for ; Thu, 11 Oct 2007 14:59:21 +0200 (CEST) Received: by nermal.rz1.convenimus.net (Postfix, from userid 8) id DF52A1521D; Thu, 11 Oct 2007 14:51:37 +0200 (CEST) To: freebsd-current@freebsd.org Path: not-for-mail From: Christian Baer Newsgroups: gmane.os.freebsd.current Date: Thu, 11 Oct 2007 14:51:37 +0200 (CEST) Organization: Convenimus Projekt Lines: 63 Message-ID: References: <86przndoe8.fsf@ds4.des.no> <6aefb8ae4a2de897081a2792cdc17ea1@127.0.0.1> NNTP-Posting-Host: sunny.rz1.convenimus.net X-Trace: nermal.rz1.convenimus.net 1192107097 93945 192.168.100.5 (11 Oct 2007 12:51:37 GMT) X-Complaints-To: abuse@convenimus.net NNTP-Posting-Date: Thu, 11 Oct 2007 12:51:37 +0000 (UTC) User-Agent: slrn/0.9.8.1 (FreeBSD/6.2-RELEASE-p8 (sparc64)) Subject: Re: suggest renaming and extending the -CURRENT and -STABLE lines 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, 11 Oct 2007 12:59:25 -0000 On Wed, 10 Oct 2007 17:08:47 +0200 Marian Hettwer wrote: Would you please take a look at you line break? These long lines are quite hard to read on some readers mutt and slrn (which I use) are among them. >> YMMV. I run both CURRENT and STABLE on production systems. > Which is higly interesting and important and has basically nothing to do > with the original mail / question by the original author ;-) I think that was meant to say that there is nothing that has to be done. I guess everybody has to make his or her own experiences. After something bad happens on a production system, thoughts about bleeding edge do tend to change a little... :-) > Back to topic? The problem is, that STABLE in FreeBSD-speak is meant as > API Stable, not stable in regards to a broken driver or in regards to a > branch where the source is frozen. That part I know. :-) > However, I do agree with the original author that it leads to confusion, > because API stabilitiy is not the first thing that pops into your mind > when you read FreeBSD 6-STABLE ;-) Actually, it's not even the second or third - aspecially since many of the people using FreeBSD don't even know (yet) what that is or it even exists. The terms we use should be understanable to the people who have to work with them. And even to an expert, the fact that -STABLE actually means -ABISTABLE isn't all that clear off hand either. I had discussions with people at university about this subject: "If it's a car, then for God's sake, call it a car and not 'a powered vehical utilizing rubber wheels for optimized traction' which could mean anything from a car, a motorbike, a truck right up to a plane." > I tend to believe that a renaming won't happen, though. AFAIK the naming > convention in FreeBSD haven't changed since... well... forever? ;) Well, since FreeBSD has a finite history, we can be sure that it's not been like this forever. :-) > It may became something like a holy cow :) Yeah - and that may be a problem. I've noticed that there is a certain problem in many people in and about open source projects to be critical about what happened in the past. In fact, I think that many improvements to Linux got in far too late because it was considered an insult to critisize *the* kernel. I know I was beaten up several times (figuratively) after pointing out that the documentation for many OS-projects simply sucks - and I gave reasons and arguments for that at the time, including suggestions for changes. BTW. FreeBSD wasn't among these projects. But noone wanted my input so I just shut up. I hope FreeBSD can live without a holy cow because a holy cow sure as hell will not speed up progress. > PS.: I managed to run CURRENT from yesterday on a IBM HS21 Blade with > this bloody mpt(4) and bce(4) chipsets. It works! Thumbs Up! The bce(4) > was panicing in earlier CURRENTs I tried :) Isn't that more like something you'd discuss on a sado/maso list? :-) Regards Chris From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 13:00: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 7693216A419 for ; Thu, 11 Oct 2007 13:00:51 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from crivens.terrorteam.de (crivens.terrorteam.de [81.169.171.191]) by mx1.freebsd.org (Postfix) with ESMTP id 4684713C45B for ; Thu, 11 Oct 2007 13:00:51 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from localhost (localhost [127.0.0.1]) by crivens.terrorteam.de (Postfix) with ESMTP id 73487B0276; Thu, 11 Oct 2007 15:00:50 +0200 (CEST) MIME-Version: 1.0 Date: Thu, 11 Oct 2007 15:00:50 +0200 From: Marian Hettwer To: Rainer Duffner In-Reply-To: <470E177B.7080007@ultra-secure.de> References: <470E177B.7080007@ultra-secure.de> Message-ID: X-Sender: mh@kernel32.de User-Agent: RoundCube Webmail/0.1b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org Subject: Re: mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 129 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, 11 Oct 2007 13:00:51 -0000 On Thu, 11 Oct 2007 14:30:51 +0200, Rainer Duffner wrote: > Marian Hettwer wrote: >> >> Well, both the SAS part of mpt(4) and the functionality for BCM5708S > weren't available in FreeBSD 6. > > But they work in STABLE. > All I had to do was to download a STABLE-snapshot. > (CURRENT is a no-go in production here) same here... > It's also a problem for older HS20 blades. > jep. >> If I encounter any problems (panics, whatever) I'd be glad to help out > with testing and testing and testing :) >> > > Until now, no problems have occured. But we don't do a lot of local disk > I/O on them, IIRC. > No problems here either. Lot's of disk I/O due to heavy mysql replication setup with InnoDB and MyISAM mixed. At a first glance, everything was stable and as fast as the very same MySQL + my.cnf + Linux 2.6.21 on the same hardware. Good News that :) Cheers, Marian From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 13:01: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 6439216A41A for ; Thu, 11 Oct 2007 13:01:51 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from crivens.terrorteam.de (crivens.terrorteam.de [81.169.171.191]) by mx1.freebsd.org (Postfix) with ESMTP id 34F1B13C448 for ; Thu, 11 Oct 2007 13:01:51 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from localhost (localhost [127.0.0.1]) by crivens.terrorteam.de (Postfix) with ESMTP id 73C34B0276; Thu, 11 Oct 2007 15:01:50 +0200 (CEST) MIME-Version: 1.0 Date: Thu, 11 Oct 2007 15:01:50 +0200 From: Marian Hettwer To: Tom Evans In-Reply-To: <1192106122.1677.28.camel@localhost> References: <1192106122.1677.28.camel@localhost> Message-ID: <247149a0f82a69480b7dfb442fc8e178@127.0.0.1> X-Sender: mh@kernel32.de User-Agent: RoundCube Webmail/0.1b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org Subject: Re: mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 129 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, 11 Oct 2007 13:01:51 -0000 On Thu, 11 Oct 2007 13:35:22 +0100, Tom Evans wrote: > On Thu, 2007-10-11 at 13:30 +0200, Marian Hettwer wrote: >> > > IIRC both mpt(4) and bce(4) have vendor supported drivers, so I'd be > surprised if they didn't work well. Here at work, we had some issues > with a bce(4) device in about 20 of our Dell boxes running RELENG_6_2 > and David Christensen (Broadcom employee) helped fix them and make them > work lovely (allowing us to cancel an order of ~20 PCIE em cards :) > I didn't know that. Thanks for the Heads Up :-) ./Marian From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 13: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 2873116A41B for ; Thu, 11 Oct 2007 13:04:23 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from crivens.terrorteam.de (crivens.terrorteam.de [81.169.171.191]) by mx1.freebsd.org (Postfix) with ESMTP id E565613C4A6 for ; Thu, 11 Oct 2007 13:04:22 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from localhost (localhost [127.0.0.1]) by crivens.terrorteam.de (Postfix) with ESMTP id 1E3D3B0276; Thu, 11 Oct 2007 15:04:22 +0200 (CEST) MIME-Version: 1.0 Date: Thu, 11 Oct 2007 15:04:22 +0200 From: Marian Hettwer To: Ivan Voras In-Reply-To: References: Message-ID: <8a8b9fd8306fafe5e8d8d92179f8cbf2@127.0.0.1> X-Sender: mh@kernel32.de User-Agent: RoundCube Webmail/0.1b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org Subject: Re: mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 129 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, 11 Oct 2007 13:04:23 -0000 On Thu, 11 Oct 2007 14:42:54 +0200, Ivan Voras wrote: > Ivan Voras wrote: >> Marian Hettwer wrote: >> >>> Well, both the SAS part of mpt(4) and the functionality for BCM5708S > weren't available in FreeBSD 6. >> >> I think I've run LSI SAS under 6.2 just fine. The newer "serdes" BCMs >> are supported on 6-STABLE (i.e. added after 6.2 was released). > > On the other hand, 7-STABLE was branched today (unfortunately without my > favorite patches) so most new users will want to go with it... > So RELENG_7 exists as of today? Then it really makes sense for me to do my testing without FreeBSD 6 :) Well, on for some stress testing on this box :-) Cheers, Marian From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 13:10: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 0C16216A420 for ; Thu, 11 Oct 2007 13:10:23 +0000 (UTC) (envelope-from news@nermal.rz1.convenimus.net) Received: from mx2.netclusive.de (mx2.netclusive.de [89.110.132.132]) by mx1.freebsd.org (Postfix) with ESMTP id CED1513C481 for ; Thu, 11 Oct 2007 13:10:22 +0000 (UTC) (envelope-from news@nermal.rz1.convenimus.net) Received: from nermal.rz1.convenimus.net (Fdd69.f.ppp-pool.de [195.4.221.105]) (Authenticated sender: ncf1534p2) by mx2.netclusive.de (Postfix) with ESMTP id 584028983F4 for ; Thu, 11 Oct 2007 15:10:19 +0200 (CEST) Received: by nermal.rz1.convenimus.net (Postfix, from userid 8) id 309061521D; Thu, 11 Oct 2007 15:02:35 +0200 (CEST) To: freebsd-current@freebsd.org Path: not-for-mail From: Christian Baer Newsgroups: gmane.os.freebsd.current Date: Thu, 11 Oct 2007 15:02:35 +0200 (CEST) Organization: Convenimus Projekt Lines: 41 Message-ID: References: <470CF67F.2020907@moneybookers.com> NNTP-Posting-Host: sunny.rz1.convenimus.net X-Trace: nermal.rz1.convenimus.net 1192107755 93945 192.168.100.5 (11 Oct 2007 13:02:35 GMT) X-Complaints-To: abuse@convenimus.net NNTP-Posting-Date: Thu, 11 Oct 2007 13:02:35 +0000 (UTC) User-Agent: slrn/0.9.8.1 (FreeBSD/6.2-RELEASE-p8 (sparc64)) Subject: Re: suggest renaming and extending the -CURRENT and -STABLE lines 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, 11 Oct 2007 13:10:23 -0000 On Wed, 10 Oct 2007 18:57:51 +0300 Stefan Lambrev wrote: > Anyway STABLE means stable API, so programs compiled on 6.2-RELEASE > should work on 6.2-STABLE Sometimes I wish people would actually read a post before answering it. I thought that was more of a German fault than an international one. :-) I didn't need explaining what the -STABLE branch is or what it stands for. But it doesn't make any difference anyway because I still believe the name STABLE is picked badly. I novice user cannot possibly know what to expect or what's behind that. The word "stable" implies that the system is actually kept stable as a goal, not that a new driver or kernel mod could actually break the system or prevent it from booting. > You can look for "ARRRRGH! Guys, who's breaking -STABLE's GMIRROR > code?!" - very long thread, but normally when something broke in -stable > this thread start and start again. Your point? No insult intended, I just haven't got a clue what you are trying to tell me (us). > P.S. for me STABLE is very stable, and current CURRENT is even more > stable (at least on new hardware), > and I have both in production. The important words being "for me". For one, if -CURRENT is as stable as you say, why bother with releases anyway? For seconds... :-) I have had more than one day, where an update from one -STABLE to another (both within one release) broke the system. I can distinctly remember an ata(4) driving causing very interesting - but incorrect - data being written to discs. It was bleeding-edge at the time. Ok, it was fixed pretty quickly but that's not the issue. If that happens on a database server in some firm, the boss will be slightly - ahem - "mad"... Regards Chris From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 17:15: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 64C1816A419 for ; Thu, 11 Oct 2007 17:15:29 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay10.ispgateway.de (smtprelay10.ispgateway.de [80.67.29.24]) by mx1.freebsd.org (Postfix) with ESMTP id B6F2513C455 for ; Thu, 11 Oct 2007 17:15:28 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 28821 invoked from network); 11 Oct 2007 17:15:26 -0000 Received: from unknown (HELO localhost) (775067@[217.50.160.145]) (envelope-sender ) by smtprelay10.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 11 Oct 2007 17:15:26 -0000 Date: Thu, 11 Oct 2007 19:05:17 +0200 From: Fabian Keil To: freebsd-current@FreeBSD.org Message-ID: <20071011190517.770fd3ab@fabiankeil.de> X-Mailer: Claws Mail 3.0.2 (GTK+ 2.10.14; i386-portbld-freebsd7.0) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2008-08-18.asc Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/l/ufglwFTOgljKhyw6jZlD9"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: Subject: zpool scrub causes geli vdev to detach 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, 11 Oct 2007 17:15:29 -0000 --Sig_/l/ufglwFTOgljKhyw6jZlD9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On: FreeBSD TP51.local 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Thu Oct 11 09:21:19 CEST 2007 fk@TP51.local:/usr/obj/usr/src/sys/THINKPAD i386 this zpool: fk@TP51 ~ $sudo zpool status pool: tank state: ONLINE scrub: scrub completed with 0 errors on Thu Oct 11 13:56:28 2007 config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 ad0s3f.eli ONLINE 0 0 0 ad0s2.eli ONLINE 0 0 0 errors: No known data errors worked without issues when it only consisted of ad0s3f.eli, but then I added ad0s2.eli and now scrubbing the pool leads to: Unread portion of the kernel message buffer: GEOM_ELI: Detached ad0s2.eli on last close. GEOM_LABEL: Label for provider ad0s2 is msdosfs/=D2A.=DB,{(#0. panic: Function g_eli_orphan_spoil_assert() called for ad0s3f.eli. KDB: enter: panic panic: from debugger Uptime: 5m27s Physical memory: 1014 MB Dumping 120 MB: 105 89 73 57 41 25 9 #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt =20 #0 doadump () at pcpu.h:195 #1 0xc05db8f3 in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:4= 09 #2 0xc05dbb1c in panic (fmt=3DVariable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:563 #3 0xc04a40c7 in db_panic (addr=3DCould not find the frame base for "db_pa= nic". ) at /usr/src/sys/ddb/db_command.c:433 #4 0xc04a4825 in db_command_loop () at /usr/src/sys/ddb/db_command.c:401 #5 0xc04a6255 in db_trap (type=3D3, code=3D0) at /usr/src/sys/ddb/db_main.= c:222 #6 0xc06014a4 in kdb_trap (type=3D3, code=3D0, tf=3D0xf4bcac1c) at /usr/sr= c/sys/kern/subr_kdb.c:502 #7 0xc0838d2b in trap (frame=3D0xf4bcac1c) at /usr/src/sys/i386/i386/trap.= c:621 #8 0xc082120b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #9 0xc0601602 in kdb_enter (msg=3D0xc0889693 "panic") at cpufunc.h:60 #10 0xc05dbb05 in panic (fmt=3D0xc3e9a0e8 "Function %s() called for %s.") a= t /usr/src/sys/kern/kern_shutdown.c:547 #11 0xc3e92d65 in ?? () #12 0xc3e9a0e8 in ?? () #13 0xc3e99d84 in ?? () #14 0xc3e0d890 in ?? () #15 0xf4bcacac in ?? () #16 0xc058eff5 in g_spoil_event (arg=3D0xc3c92940, flag=3D-945983104) at /u= sr/src/sys/geom/geom_subr.c:903 (kgdb) f 16 #16 0xc058eff5 in g_spoil_event (arg=3D0xc3c92940, flag=3D-945983104) at /u= sr/src/sys/geom/geom_subr.c:903 903 cp->geom->spoiled(cp); (kgdb) l 898 if (!cp->spoiled) 899 continue; 900 cp->spoiled =3D 0; 901 if (cp->geom->spoiled =3D=3D NULL) 902 continue; 903 cp->geom->spoiled(cp); 904 g_topology_assert(); 905 } 906 } 907 =20 As a workaround I'm currently using: --- sys/geom/eli/g_eli.c.orig 2007-10-11 13:35:53.744592827 +0200 +++ sys/geom/eli/g_eli.c 2007-10-11 13:38:41.687509241 +0200 @@ -451,10 +451,14 @@ gp =3D sc->sc_geom; pp =3D LIST_FIRST(&gp->provider); strlcpy(ppname, pp->name, sizeof(ppname)); + + G_ELI_DEBUG(0, "Ignored request to detach %s on last close.", ppnam= e); + /* error =3D g_eli_destroy(sc, 1); KASSERT(error =3D=3D 0, ("Cannot detach %s on last close (error=3D%= d).", ppname, error)); G_ELI_DEBUG(0, "Detached %s on last close.", ppname); + */ } =20 int and with that scrubbing finishes without errors (see status above), but triggers the G_ELI_DEBUG message once or twice: Oct 11 13:46:30 TP51 sudo: fk : TTY=3Dttyv0 ; PWD=3D/home/fk ; USER= =3Droot ; COMMAND=3D/etc/rc.d/zfs start Oct 11 13:46:31 TP51 kernel: WARNING: ZFS is considered to be an experiment= al feature in FreeBSD. Oct 11 13:46:31 TP51 kernel: ZFS filesystem version 6 Oct 11 13:46:31 TP51 kernel: ZFS storage pool version 6 Oct 11 13:46:32 TP51 kernel: GEOM_ELI: Ignored request to detach ad0s3f.eli= on last close. Oct 11 13:46:32 TP51 last message repeated 3 times Oct 11 13:46:32 TP51 kernel: GEOM_ELI: Ignored request to detach ad0s2.eli = on last close. Oct 11 13:46:44 TP51 sudo: fk : TTY=3Dttyv0 ; PWD=3D/home/fk ; USER= =3Droot ; COMMAND=3D/sbin/zpool status Oct 11 13:47:12 TP51 sudo: fk : TTY=3Dttyv0 ; PWD=3D/home/fk ; USER= =3Droot ; COMMAND=3D/sbin/zpool scrub tank Oct 11 13:47:13 TP51 kernel: GEOM_ELI: Ignored request to detach ad0s3f.eli= on last close. Oct 11 13:47:13 TP51 kernel: GEOM_ELI: Ignored request to detach ad0s3f.eli= on last close. Not sure if it helps, but the zdevs are: Geom name: ad0s3f.eli EncryptionAlgorithm: AES-CBC KeyLength: 128 Crypto: software UsedKey: 0 Flags: RW-DETACH, W-OPEN Providers: 1. Name: ad0s3f.eli Mediasize: 8881561600 (8.3G) Sectorsize: 4096 Mode: r1w1e1 Consumers: 1. Name: ad0s3f Mediasize: 8881565184 (8.3G) Sectorsize: 512 Mode: r1w1e1 Geom name: ad0s2.eli EncryptionAlgorithm: AES-CBC KeyLength: 128 Crypto: software UsedKey: 0 Flags: RW-DETACH, W-OPEN Providers: 1. Name: ad0s2.eli Mediasize: 9932263424 (9.3G) Sectorsize: 4096 Mode: r1w1e1 Consumers: 1. Name: ad0s2 Mediasize: 9932267520 (9.3G) Sectorsize: 512 Mode: r1w1e1 Is there an obvious solution, or should I file a PR about this? Fabian --Sig_/l/ufglwFTOgljKhyw6jZlD9 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHDlfNBYqIVf93VJ0RAqiaAJ4mp6QpbH7zzdr0poVjdM+Xa5Ja5wCeIKqE HtXpvymdbzaSpb73VnkgCxk= =Vjkd -----END PGP SIGNATURE----- --Sig_/l/ufglwFTOgljKhyw6jZlD9-- From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 17:32: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 447A816A41A for ; Thu, 11 Oct 2007 17:32:38 +0000 (UTC) (envelope-from chris@arnold.se) Received: from mailstore.infotropic.com (mailstore.infotropic.com [213.136.34.3]) by mx1.freebsd.org (Postfix) with ESMTP id A3E3F13C474 for ; Thu, 11 Oct 2007 17:32:37 +0000 (UTC) (envelope-from chris@arnold.se) Received: (qmail 14600 invoked by uid 89); 11 Oct 2007 17:32:35 -0000 Received: by simscan 1.2.0 ppid: 14595, pid: 14597, t: 0.1335s scanners: attach: 1.2.0 clamav: 0.90/m:42 Received: from unknown (HELO ?192.168.123.123?) (chris@arnold.se@82.182.86.134) by mailstore.infotropic.com with ESMTPA; 11 Oct 2007 17:32:35 -0000 Date: Thu, 11 Oct 2007 19:32:34 +0200 (CEST) From: Christopher Arnold X-X-Sender: chris@chrishome.localnet To: Jeremy Chadwick In-Reply-To: <20071010185416.GA38522@eos.sc1.parodius.com> Message-ID: <20071011192303.P30804@chrishome.localnet> References: <20071010195157.O24133@chrishome.localnet> <20071010185416.GA38522@eos.sc1.parodius.com> X-message-flag: =?ISO-8859-1?Q?Outlook_isn=B4t_compliant_with_current_standards?= =?ISO-8859-1?Q?_please_install_another_mail_client!?= MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: Compaq Smart Array 5300 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, 11 Oct 2007 17:32:38 -0000 On Wed, 10 Oct 2007, Jeremy Chadwick wrote: > On Wed, Oct 10, 2007 at 08:06:21PM +0200, Christopher Arnold wrote: >> >> anyone aware of issues with Compaq Smart Array 5300 on a current only a day >> old? >> >> This is what i get in the boot message: >> ciss0: port 0xe800-0xe8ff mem >> 0xfebc0000-0xfebfffff,0xfea00000-0xfeafffff irq 22 at device 1.0 on pci2 >> ciss0: can't allocate config window >> device_attach: ciss0 attach returned 6 >> >> The full output can be found at: >> http://www.arnold.se/boot.txt >> http://www.arnold.se/pciconf.txt >> >> Im trying to run it in a Supermicro 6010 with 370DER+ motherboard. >> >> Anyone who has any input on what this could be? > > It's one of those bloody QLogic GEM chips; on this motherboard, it's > probably the QLogic GEM 354. The motherboard manual does indicate this, > although only in the Windows driver section (this does not surprise me, > as some other vendors use GEM chips and don't tell you until you > actually have to deal with them...) > I havn't actually verified this, but it may be true. > In general: I wouldn't worry about the lack of ciss0 device. In fact, > I'd go so far to recommend you remove ses and ciss from the kernel on > that box, and hope for the best. Scott (Long) may have some better > (and more accurate) advice on the matter; my experiences are my own. > Removing ciss from the kernel dosn't help. Now i get: kernel: pcib2: on acpi0 kernel: pci2: on pcib2 kernel: pci2: at device 1.0 (no driver attached) Which seems reasonable... Does anyone have an idea what "ciss0 attach returned 6" could stand for? /Chris From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 17:39: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 401B016A417 for ; Thu, 11 Oct 2007 17:39:12 +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 6E1AB13C4A7 for ; Thu, 11 Oct 2007 17:39:11 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 4C9D245EE5; Thu, 11 Oct 2007 19:39:09 +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 B7CCD45CD9; Thu, 11 Oct 2007 19:39:02 +0200 (CEST) Date: Thu, 11 Oct 2007 19:38:46 +0200 From: Pawel Jakub Dawidek To: Fabian Keil Message-ID: <20071011173846.GB52831@garage.freebsd.pl> References: <20071011190517.770fd3ab@fabiankeil.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1LKvkjL3sHcu1TtY" Content-Disposition: inline In-Reply-To: <20071011190517.770fd3ab@fabiankeil.de> 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: freebsd-current@FreeBSD.org Subject: Re: zpool scrub causes geli vdev to detach 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, 11 Oct 2007 17:39:12 -0000 --1LKvkjL3sHcu1TtY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 11, 2007 at 07:05:17PM +0200, Fabian Keil wrote: > On: >=20 > FreeBSD TP51.local 7.0-CURRENT FreeBSD 7.0-CURRENT > #0: Thu Oct 11 09:21:19 CEST 2007 > fk@TP51.local:/usr/obj/usr/src/sys/THINKPAD i386 >=20 > this zpool: >=20 > fk@TP51 ~ $sudo zpool status > pool: tank > state: ONLINE > scrub: scrub completed with 0 errors on Thu Oct 11 13:56:28 2007 > config: >=20 > NAME STATE READ WRITE CKSUM > tank ONLINE 0 0 0 > ad0s3f.eli ONLINE 0 0 0 > ad0s2.eli ONLINE 0 0 0 >=20 > errors: No known data errors >=20 > worked without issues when it only consisted of ad0s3f.eli, > but then I added ad0s2.eli and now scrubbing the pool leads to: >=20 > Unread portion of the kernel message buffer: > GEOM_ELI: Detached ad0s2.eli on last close. > GEOM_LABEL: Label for provider ad0s2 is msdosfs/?A.?,{(#0. > panic: Function g_eli_orphan_spoil_assert() called for ad0s3f.eli. > KDB: enter: panic > panic: from debugger > Uptime: 5m27s > Physical memory: 1014 MB > Dumping 120 MB: 105 89 73 57 41 25 9 >=20 > #0 doadump () at pcpu.h:195 > 195 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) bt =20 > #0 doadump () at pcpu.h:195 > #1 0xc05db8f3 in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c= :409 > #2 0xc05dbb1c in panic (fmt=3DVariable "fmt" is not available. > ) at /usr/src/sys/kern/kern_shutdown.c:563 > #3 0xc04a40c7 in db_panic (addr=3DCould not find the frame base for "db_= panic". > ) at /usr/src/sys/ddb/db_command.c:433 > #4 0xc04a4825 in db_command_loop () at /usr/src/sys/ddb/db_command.c:401 > #5 0xc04a6255 in db_trap (type=3D3, code=3D0) at /usr/src/sys/ddb/db_mai= n.c:222 > #6 0xc06014a4 in kdb_trap (type=3D3, code=3D0, tf=3D0xf4bcac1c) at /usr/= src/sys/kern/subr_kdb.c:502 > #7 0xc0838d2b in trap (frame=3D0xf4bcac1c) at /usr/src/sys/i386/i386/tra= p.c:621 > #8 0xc082120b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 > #9 0xc0601602 in kdb_enter (msg=3D0xc0889693 "panic") at cpufunc.h:60 > #10 0xc05dbb05 in panic (fmt=3D0xc3e9a0e8 "Function %s() called for %s.")= at /usr/src/sys/kern/kern_shutdown.c:547 > #11 0xc3e92d65 in ?? () > #12 0xc3e9a0e8 in ?? () > #13 0xc3e99d84 in ?? () > #14 0xc3e0d890 in ?? () > #15 0xf4bcacac in ?? () > #16 0xc058eff5 in g_spoil_event (arg=3D0xc3c92940, flag=3D-945983104) at = /usr/src/sys/geom/geom_subr.c:903 > (kgdb) f 16 > #16 0xc058eff5 in g_spoil_event (arg=3D0xc3c92940, flag=3D-945983104) at = /usr/src/sys/geom/geom_subr.c:903 > 903 cp->geom->spoiled(cp); > (kgdb) l > 898 if (!cp->spoiled) > 899 continue; > 900 cp->spoiled =3D 0; > 901 if (cp->geom->spoiled =3D=3D NULL) > 902 continue; > 903 cp->geom->spoiled(cp); > 904 g_topology_assert(); > 905 } > 906 } > 907 =20 >=20 > As a workaround I'm currently using: >=20 > --- sys/geom/eli/g_eli.c.orig 2007-10-11 13:35:53.744592827 +0200 > +++ sys/geom/eli/g_eli.c 2007-10-11 13:38:41.687509241 +0200 > @@ -451,10 +451,14 @@ > gp =3D sc->sc_geom; > pp =3D LIST_FIRST(&gp->provider); > strlcpy(ppname, pp->name, sizeof(ppname)); > + > + G_ELI_DEBUG(0, "Ignored request to detach %s on last close.", ppn= ame); > + /* > error =3D g_eli_destroy(sc, 1); > KASSERT(error =3D=3D 0, ("Cannot detach %s on last close (error= =3D%d).", > ppname, error)); > G_ELI_DEBUG(0, "Detached %s on last close.", ppname); > + */ > } > =20 > int >=20 > and with that scrubbing finishes without errors (see status above), > but triggers the G_ELI_DEBUG message once or twice: >=20 > Oct 11 13:46:30 TP51 sudo: fk : TTY=3Dttyv0 ; PWD=3D/home/fk ; USER= =3Droot ; COMMAND=3D/etc/rc.d/zfs start > Oct 11 13:46:31 TP51 kernel: WARNING: ZFS is considered to be an experime= ntal feature in FreeBSD. > Oct 11 13:46:31 TP51 kernel: ZFS filesystem version 6 > Oct 11 13:46:31 TP51 kernel: ZFS storage pool version 6 > Oct 11 13:46:32 TP51 kernel: GEOM_ELI: Ignored request to detach ad0s3f.e= li on last close. > Oct 11 13:46:32 TP51 last message repeated 3 times > Oct 11 13:46:32 TP51 kernel: GEOM_ELI: Ignored request to detach ad0s2.el= i on last close. > Oct 11 13:46:44 TP51 sudo: fk : TTY=3Dttyv0 ; PWD=3D/home/fk ; USER= =3Droot ; COMMAND=3D/sbin/zpool status > Oct 11 13:47:12 TP51 sudo: fk : TTY=3Dttyv0 ; PWD=3D/home/fk ; USER= =3Droot ; COMMAND=3D/sbin/zpool scrub tank > Oct 11 13:47:13 TP51 kernel: GEOM_ELI: Ignored request to detach ad0s3f.e= li on last close. > Oct 11 13:47:13 TP51 kernel: GEOM_ELI: Ignored request to detach ad0s3f.e= li on last close. >=20 > Not sure if it helps, but the zdevs are: >=20 > Geom name: ad0s3f.eli > EncryptionAlgorithm: AES-CBC > KeyLength: 128 > Crypto: software > UsedKey: 0 > Flags: RW-DETACH, W-OPEN > Providers: > 1. Name: ad0s3f.eli > Mediasize: 8881561600 (8.3G) > Sectorsize: 4096 > Mode: r1w1e1 > Consumers: > 1. Name: ad0s3f > Mediasize: 8881565184 (8.3G) > Sectorsize: 512 > Mode: r1w1e1 >=20 > Geom name: ad0s2.eli > EncryptionAlgorithm: AES-CBC > KeyLength: 128 > Crypto: software > UsedKey: 0 > Flags: RW-DETACH, W-OPEN > Providers: > 1. Name: ad0s2.eli > Mediasize: 9932263424 (9.3G) > Sectorsize: 4096 > Mode: r1w1e1 > Consumers: > 1. Name: ad0s2 > Mediasize: 9932267520 (9.3G) > Sectorsize: 512 > Mode: r1w1e1 >=20 >=20 > Is there an obvious solution, or should I file a PR about this? Please file PR, but let me explain. GELI's detach-on-last-close mechanism is a general purpose mechanism, it may not work correctly with ZFS, because ZFS sometimes closes and reopen providers, which will make GELI to detach. In other words you shouldn't configure detach-on-last-close for ZFS components. It shouldn't panic still. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --1LKvkjL3sHcu1TtY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHDl+lForvXbEpPzQRAshYAJ9pD710CNquZxAXbJat2euiJ9a3vwCgtHSi 6BzACCky85JWyCU9EgmpPzE= =/NZ4 -----END PGP SIGNATURE----- --1LKvkjL3sHcu1TtY-- From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 17:56: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 E8A3A16A41B for ; Thu, 11 Oct 2007 17:56:03 +0000 (UTC) (envelope-from Peter.Ross@alumni.tu-berlin.de) Received: from qsrv01ps.mx.bigpond.com (qsrv01ps.mx.bigpond.com [144.140.82.181]) by mx1.freebsd.org (Postfix) with ESMTP id 8E04013C465 for ; Thu, 11 Oct 2007 17:56:03 +0000 (UTC) (envelope-from Peter.Ross@alumni.tu-berlin.de) Received: from oaamta03ps.mx.bigpond.com ([121.220.58.72]) by omta03ps.mx.bigpond.com with ESMTP id <20071011141947.TPQM13511.omta03ps.mx.bigpond.com@oaamta03ps.mx.bigpond.com> for ; Thu, 11 Oct 2007 14:19:47 +0000 Received: from klein.bigpond.com ([121.220.58.72]) by oaamta03ps.mx.bigpond.com with ESMTP id <20071011141945.XQBL8337.oaamta03ps.mx.bigpond.com@klein.bigpond.com>; Thu, 11 Oct 2007 14:19:45 +0000 Received: from klein.bigpond.com (localhost [127.0.0.1]) by klein.bigpond.com (8.14.1/8.14.1) with ESMTP id l9C0NYAC001621; Fri, 12 Oct 2007 00:23:34 GMT (envelope-from Peter.Ross@alumni.tu-berlin.de) Received: from localhost (petros@localhost) by klein.bigpond.com (8.14.1/8.14.1/Submit) with ESMTP id l9C0NU8x001618; Fri, 12 Oct 2007 00:23:32 GMT (envelope-from Peter.Ross@alumni.tu-berlin.de) X-Authentication-Warning: klein.bigpond.com: petros owned process doing -bs Date: Fri, 12 Oct 2007 00:23:29 +0000 (UTC) From: Peter Ross X-X-Sender: petros@klein.bigpond.com To: Eygene Ryabinkin In-Reply-To: <20071011121903.GE3943@void.codelabs.ru> Message-ID: <20071011231222.Y1440@klein.bigpond.com> References: <20071011121903.GE3943@void.codelabs.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-current@freebsd.org, Christian Baer Subject: Re: suggest renaming and extending the -CURRENT and -STABLE lines 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, 11 Oct 2007 17:56:04 -0000 Hi, On Thu, 11 Oct 2007, Eygene Ryabinkin wrote: > Christian, good day. > > Wed, Oct 10, 2007 at 03:52:14PM +0200, Christian Baer wrote: > > If someone sees the result of RELENG_6 is called STABLE, he or she will > > problably think, this is the line where bug fixes are added, security > > problems fixed and the whole thing is meant for production systems. While > > the first two things may be true, I would not suggest RELENG_6 for > > production systems. The handbook explicitly explains it: --------------------------------------------------------------------------- 23.2.2.1 What Is FreeBSD-STABLE? FreeBSD-STABLE is our development branch from which major releases are made. Changes go into this branch at a different pace, and with the general assumption that they have first gone into FreeBSD-CURRENT for testing. This is still a development branch, however, and this means that at any given time, the sources for FreeBSD-STABLE may or may not be suitable for any particular purpose. It is simply another engineering development track, not a resource for end-users. --------------------------------------------------------------------------- > > Normally the -STABLE line works fine. But I *have* > > times in the past where a driver was changes and suddenly the system > > *didn't* work after a reboot or showed strange behaviour. > > But let us look at the issue from the user's side: where can he get > RELENG_6? Only cvsup, CTM and monthly snapshots come into my mind. I would think that someone who uses these tools may look into the handbook. I would guess that most people get the idea of updating via sources from the handbook so this part is hard to miss. And it is headlined "Chapter 23 The Cutting Edge", btw. However, I tried to find information about the RELENG tags useful for production systems in the handbook. The only place I find them mentioned is in the appendix: "A.7.1 Branch Tags". "14.14 FreeBSD Security Advisories" don't mention RELENG tags. So the use of RELENG tags is not that obvious for a newcomer I think. Maybe we should add a comment in the Chapters 23 (Cutting Edge) and 14.14 (Security advisories). To come up with good names isn't that easy. Look at Debian: stable, unstable, testing. It's different but not better I think. Fortunatelly the most FreeBSD releases deserve the attribute stable:-) So when I maintained FreeBSD servers I rarely saw a reason to update to "the kernel of the week". Besides of some security patches I just did it once in a while to a new release, just to keep servers in sync. Of course carefully. Every change of a running system (not only if it's FreeBSD;-) is a risk. BTW: Even my -CURRENT desktop is more stable than a Fedora release I had to endure at work for a while:-) Regards Peter From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 18:12: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 3B49A16A417 for ; Thu, 11 Oct 2007 18:12:36 +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 1480F13C45B for ; Thu, 11 Oct 2007 18:12:36 +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 l9BI8Ff9024405 for ; Thu, 11 Oct 2007 11:08:15 -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 l9BI8Fpv024404 for freebsd-current@freebsd.org; Thu, 11 Oct 2007 11:08:15 -0700 (PDT) (envelope-from sgk) Date: Thu, 11 Oct 2007 11:08:15 -0700 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20071011180815.GA23643@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: Removing a symbol from Symbol.map? 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, 11 Oct 2007 18:12:36 -0000 In my journey through the libm source code, I've discovered that msun/src/w_cabs.c contains a function named z_abs. This symbol appears in libm's Symbol.map, but z_abs has not prototype in any header file under /usr/include. Thus, it is namespace pollution that I'd like to remove. Do I simply remove z_abs from Symbol.map or is there more to it then this? PS: Yes, I know bde will probably object to removal of z_abs because of compatibility issues with fdlibm and the other *BSD. -- Steve From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 18:34: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 0D96316A41A for ; Thu, 11 Oct 2007 18:34:38 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id BD88613C44B for ; Thu, 11 Oct 2007 18:34:37 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.1/8.14.1/NETPLEX) with ESMTP id l9BIYZSj006190; Thu, 11 Oct 2007 14:34:35 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (mail.netplex.net [204.213.176.10]); Thu, 11 Oct 2007 14:34:35 -0400 (EDT) Date: Thu, 11 Oct 2007 14:34:35 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Steve Kargl In-Reply-To: <20071011180815.GA23643@troutmask.apl.washington.edu> Message-ID: References: <20071011180815.GA23643@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: Removing a symbol from Symbol.map? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2007 18:34:38 -0000 On Thu, 11 Oct 2007, Steve Kargl wrote: > In my journey through the libm source code, I've discovered > that msun/src/w_cabs.c contains a function named z_abs. This > symbol appears in libm's Symbol.map, but z_abs has not prototype > in any header file under /usr/include. Thus, it is namespace > pollution that I'd like to remove. Do I simply remove z_abs from > Symbol.map or is there more to it then this? Nope, no more to it than just removing it from the symbol map. I certainly don't have any object to removing symbols that don't belong there. It should be MFC'd to -7 before release if it really shouldn't be there. If it doesn't make it to -7, then we'll need to keep it as a compatibility function forever. > PS: Yes, I know bde will probably object to removal of z_abs > because of compatibility issues with fdlibm and the other *BSD. -- DE From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 18:27: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 5FD3216A421 for ; Thu, 11 Oct 2007 18:27:09 +0000 (UTC) (envelope-from eimar.koort@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by mx1.freebsd.org (Postfix) with ESMTP id 418F613C469 for ; Thu, 11 Oct 2007 18:27:09 +0000 (UTC) (envelope-from eimar.koort@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so733526waf for ; Thu, 11 Oct 2007 11:27: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:mime-version:content-type; bh=w2l7GzXn7WQ6Zqm5eHS2GxKbtKpwWIE+RSKsSQFQ1Gw=; b=fWGS7nvtbv+dCHDyDgMPyRvYkIrMScQ0fbDddNcNMNlDGeX1mN8RAXobvxuPxejZB2yIYLnDijTHsA0tV1LPTBz27/vWGvVcIusN4uARVQQgKouEDJSrwrxbVESu1xouqhVPK7TcTLs3xbcbGipzDYaYJXlPkR26EscCziMmPlk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=MTynQ4PwpcLZAihP3HU3JXqXvxlF3IFd1G7tHe8XNOy4Kih2b/+amWw5Pi6NEu/sMspBapxQrwfMQWxHOP6bFMkmWwW+7vgTD/Kzll7uHx9WvA/ttlxZR8ZPBn2mBunBcl/L+pOjxXTAoXOYt/pE4g1v4kWKOBaoVBVVc9QIR6k= Received: by 10.115.75.1 with SMTP id c1mr2454253wal.1192125546748; Thu, 11 Oct 2007 10:59:06 -0700 (PDT) Received: by 10.114.109.17 with HTTP; Thu, 11 Oct 2007 10:59:06 -0700 (PDT) Message-ID: <109c90a0710111059qf50158bn95574464bcd0a9df@mail.gmail.com> Date: Thu, 11 Oct 2007 20:59:06 +0300 From: "Eimar Koort" To: freebsd-current@freebsd.org MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 11 Oct 2007 18:37:22 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Asus M2N with two sata disks. 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, 11 Oct 2007 18:27:09 -0000 Hi all, Motherboard: Asus M2N [1] Bios version: v02.58 When two SATA disks are added to machine, then it does'nt boot up or sometimes it can boot up but detaching second disk "like mad". Several months ago it was so 'stable', that i could boot up and create geom mirror (Jul 3). After updating several times things went update by update more unstable. At the moment machine is usable only with one disk. Second disk is tested with other operating systems and it works. Also changing sata channels doesn't make it better. And question: has anyone same or similar problem or has found a cure for this problem? Generic kernel (11. Oct 2007 (cvs tag=.) It apperas, that right after 'releng_7' branced). With BIOS default settings: ### /*snip*/ ad4: 305245MB at ata2-master SATA150 ad6: 305245MB at ata2-master SATA150 GEOM_MIRROR: Device mirror/gm0 launced (1/1) Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x8:0xffffffff80492be4 stack pointer = 0x10:0xffffffffa0664a40 frame pointer = 0x10:0xffffffffa0664a50 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 23 (irq21: ohci0+) [thread pid 23 tid 100029 ] Stopped at device_get_softc+0x4: movq 0x80(%rdi),%rax db> ### After disabling floppy disk, USB, Serial and Parallel port: ### /*snip*/ GEOM_MIRROR: Device mirror/gm0 launced (1/1) Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x8:0xffffffff80492be4 stack pointer = 0x10:0xffffffffa0630a40 frame pointer = 0x10:0xffffffffa0630a50 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 23 (irq20: atapci1) [thread pid 30 tid 100022 ] Stopped at device_get_softc+0x4: movq 0x80(%rdi),%rax db> ### One example, when machine is able to boot up with both disk. At the same time all things are slow - login takes about minute or two. ### Oct 11 18:57:20 tusklik kernel: ad6: FAILURE - READ_DMA48 timed out LBA=625142444 Oct 11 18:57:20 tusklik kernel: subdisk6: detached Oct 11 18:57:20 tusklik kernel: ad6: detached Oct 11 18:57:20 tusklik kernel: ad6: 305245MB at ata3-master SATA150 Oct 11 18:57:22 tusklik kernel: subdisk6: detached Oct 11 18:57:22 tusklik kernel: ad6: detached Oct 11 18:57:22 tusklik kernel: ad6: 305245MB at ata3-master SATA150 Oct 11 18:58:25 tusklik kernel: subdisk6: detached Oct 11 18:58:25 tusklik kernel: ad6: detached Oct 11 18:58:25 tusklik kernel: ad6: 305245MB at ata3-master SATA150 Oct 11 18:58:33 tusklik kernel: ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=128 Oct 11 18:58:33 tusklik kernel: subdisk6: detached ### After removing second disk and boot-up 'dmesg' output: ### 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 8.0-CURRENT #0: Thu Oct 11 18:20:14 EEST 2007 root@tusklik.example.ee:/usr/obj/usr/src/sys/GENERIC WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ (2009.13-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40fb2 Stepping = 2 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1f Cores per package: 2 usable memory = 1060196352 (1011 MB) avail memory = 1021550592 (974 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 3ff00000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0 cpu0: on acpi0 powernow0: on cpu0 cpu1: on acpi0 powernow1: on cpu1 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) isab0: port 0x900-0x9ff at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) pci0: at device 1.2 (no driver attached) ehci0: mem 0xdfeffc00-0xdfeffcff irq 21 at device 2.0 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb0: waiting for BIOS to give up control usb0: EHCI version 1.0 usb0: wrong number of companions (1 != 0) usb0: stop timeout usb0: on ehci0 usb0: USB revision 2.0 uhub0: on usb0 uhub0: 10 ports with 10 removable, self powered pcib1: at device 4.0 on pci0 pci1: on pcib1 pci0: at device 5.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 6.0 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] nfe0: port 0xd480-0xd487 mem 0xdfefe000-0xdfefefff irq 23 at device 7.0 on pci0 miibus0: on nfe0 ukphy0: PHY 1 on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto nfe0: Ethernet address: 00:18:f3:49:4b:b7 nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] atapci1: port 0xd400-0xd407,0xd080-0xd083,0xd000-0xd007,0xcc00-0xcc03,0xc880-0xc88f mem 0xdfefd000-0xdfefdfff irq 20 at device 8.0 on pci0 atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] atapci2: port 0xc800-0xc807,0xc480-0xc483,0xc400-0xc407,0xc080-0xc083,0xc000-0xc00f mem 0xdfefc000-0xdfefcfff irq 21 at device 8.1 on pci0 atapci2: [ITHREAD] ata4: on atapci2 ata4: [ITHREAD] ata5: on atapci2 ata5: [ITHREAD] pcib2: at device 9.0 on pci0 pci2: on pcib2 vgapci0: port 0xe800-0xe8ff mem 0xc0000000-0xcfffffff,0xdfff0000-0xdfffffff irq 16 at device 0.0 on pci2 vgapci1: mem 0xdffe0000-0xdffeffff at device 0.1 on pci2 pcib3: at device 11.0 on pci0 pci3: on pcib3 pcib4: at device 12.0 on pci0 pci4: on pcib4 acpi_button0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] acpi_hpet0: iomem 0xfed00000-0xfed00fff on acpi0 Timecounter "HPET" frequency 25000000 Hz quality 900 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse Explorer, device ID 4 orm0: at iomem 0xc0000-0xcdfff on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> 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 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: DVDR at ata0-slave UDMA33 ad4: 305245MB at ata2-master SATA150 ar0: WARNING - mirror protection lost. RAID1 array in DEGRADED mode ar0: 305245MB status: DEGRADED ar0: disk0 DOWN no device found for this subdisk ar0: disk1 READY (mirror) using ad4 at ata2-master SMP: AP CPU #1 Launched! WARNING: WITNESS option enabled, expect reduced performance. GEOM_MIRROR: Device mirror/gm0 launched (1/1). Trying to mount root from ufs:/dev/mirror/gm0s1a ----- [1] http://www.asus.com/products.aspx?l1=3&l2=101&l3=340&l4=0&model=1340&modelmenu=1 -- Eimar Koort ( eimar.koort AT gmail.com ) From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 18:42: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 BEA0B16A420; Thu, 11 Oct 2007 18:42:31 +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 92CAB13C469; Thu, 11 Oct 2007 18:42:31 +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 l9BIcCuV024963; Thu, 11 Oct 2007 11:38:12 -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 l9BIcCET024962; Thu, 11 Oct 2007 11:38:12 -0700 (PDT) (envelope-from sgk) Date: Thu, 11 Oct 2007 11:38:12 -0700 From: Steve Kargl To: Daniel Eischen Message-ID: <20071011183812.GA24863@troutmask.apl.washington.edu> References: <20071011180815.GA23643@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org, bde@freebsd.org Subject: Re: Removing a symbol from Symbol.map? 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, 11 Oct 2007 18:42:31 -0000 On Thu, Oct 11, 2007 at 02:34:35PM -0400, Daniel Eischen wrote: > On Thu, 11 Oct 2007, Steve Kargl wrote: > > >In my journey through the libm source code, I've discovered > >that msun/src/w_cabs.c contains a function named z_abs. This > >symbol appears in libm's Symbol.map, but z_abs has not prototype > >in any header file under /usr/include. Thus, it is namespace > >pollution that I'd like to remove. Do I simply remove z_abs from > >Symbol.map or is there more to it then this? > > Nope, no more to it than just removing it from the symbol > map. I certainly don't have any object to removing symbols > that don't belong there. It should be MFC'd to -7 before > release if it really shouldn't be there. If it doesn't > make it to -7, then we'll need to keep it as a compatibility > function forever. > > >PS: Yes, I know bde will probably object to removal of z_abs > >because of compatibility issues with fdlibm and the other *BSD. > I certainly believe that z_abs should be removed. I've cc'd bde to see if he has an objection. -- Steve From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 18:45: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 5EFC116A418 for ; Thu, 11 Oct 2007 18:45:29 +0000 (UTC) (envelope-from rse@engelschall.com) Received: from visp1.engelschall.com (visp1.engelschall.com [195.30.6.144]) by mx1.freebsd.org (Postfix) with ESMTP id 2B5A713C45A for ; Thu, 11 Oct 2007 18:45:28 +0000 (UTC) (envelope-from rse@engelschall.com) Received: by visp1.engelschall.com (Postfix, from userid 21100) id E929B1B44869; Thu, 11 Oct 2007 20:45:28 +0200 (CEST) Received: by en1.engelschall.com (Postfix, from userid 10000) id 598E76DA6A; Thu, 11 Oct 2007 20:43:40 +0200 (CEST) Date: Thu, 11 Oct 2007 20:43:40 +0200 From: "Ralf S. Engelschall" To: freebsd-current@freebsd.org Message-ID: <20071011184340.GA13972@engelschall.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: FreeBSD User-Agent: Mutt/1.5.16 OpenPKG/CURRENT (2007-06-09) Subject: reanimate ZFS pool after disk cloning and host changing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Ralf S. Engelschall" List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2007 18:45:29 -0000 I've a FreeBSD 7-CURRENT (as of 2007-10-09) running in a VirtualBox virtual machine and with all filesystems except /boot on ZFS. Now that we switched to 7.0-PRERELEASE and 8-CURRENT I today created another virtual machine and just cloned the disks (with "vboxmanage clonevdi", but it doesn't matter here). When I then booted the new virtual machine with the cloned disks, the root filesystem couldn't be mounted during boot via "zfs:zp1/root" as the ZFS pool "zp1" is no longer available. So I booted into the Fixit environment from "7.0-CURRENT-200709-i386-disc1.iso" and tried "zpool import". It was able to detect the pool on device ad0s1f. The problem just is that the hostid has changed (which is correct), so I thought I just have to re-import the ZFS pool with "zfs import -R /zp1 -f zp1". This still worked just fine: all filesystem were available under temporary /zp1 now (I had to use this alternative root or the Fixit environment is immediately dead). But once I then reboot into the system, the ZFS pool is again not found via "zfs:zp1/root"! In tried multiple times with various ways in the Fixit environment: "zfs import zp1" is denied because the hostid is different, "zfs import -f zp1" does the trick (although breaks the Fixit environent) but after reboot the ZFS pool again gone, "zfs import -R /zp1 -f zp1" does also the trick but here again the ZFS pool is gone after reboot. So, the silly question is: what is the correct way to reanimate a ZFS pool after the host has changed, so that one can again directly boot from from one of its filesystems (here "zp1/root")? -- rse@FreeBSD.org Ralf S. Engelschall FreeBSD.org/~rse rse@engelschall.com FreeBSD committer www.engelschall.com From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 18:49: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 28D3716A418 for ; Thu, 11 Oct 2007 18:49:51 +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 DC45013C467 for ; Thu, 11 Oct 2007 18:49:50 +0000 (UTC) (envelope-from jpedras+freebsd-current@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 l9BInck7096421 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 11 Oct 2007 11:49:39 -0700 (PDT) (envelope-from jpedras+freebsd-current@webvolution.net) Message-ID: <470E7045.1040308@webvolution.net> Date: Thu, 11 Oct 2007 11:49:41 -0700 From: Joao Pedras User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org 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 Subject: lock up: swi Giant taskq X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jpedras@webvolution.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2007 18:49:51 -0000 Folks, about a couple weeks ago I sent out some info to this list about a lock up which happens on a couple of similar systems. A PR (http://www.freebsd.org/cgi/query-pr.cgi?pr=116932) has also been submitted. I am wondering if this issue has been noticed by somebody else and what more information could I provide to resolve the issue. Aside form this annoying problem the systems run great and are extremely fast. Appreciate your help. Joao From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 18:53:14 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 4C23E16A41B for ; Thu, 11 Oct 2007 18:53:14 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id D02E113C478 for ; Thu, 11 Oct 2007 18:53:13 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.1/8.14.1) with ESMTP id l9BIrC14003481 for ; Thu, 11 Oct 2007 22:53:12 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Thu, 11 Oct 2007 22:53:12 +0400 (MSD) From: Dmitry Morozovsky To: current@FreeBSD.org Message-ID: <20071011224937.D97516@woozle.rinet.ru> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (woozle.rinet.ru [0.0.0.0]); Thu, 11 Oct 2007 22:53:12 +0400 (MSD) Cc: Subject: INSTKERNNAME= foolproof check 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, 11 Oct 2007 18:53:14 -0000 Colleagues, Today I successfully shoot myself in the foot by typing make installkernel KERNCONF=GENERIC INSTKERNNAME= instead of usual make installkernel KERNCONF=GENERIC INSTKERNNAME=GENERIC Empty INSTKERNNAME leads to wiping /boot completely - rather annoying, especially in my case, where I had some non-trivial (and, of course, no backups ;-) loader.conf What do you think about the following patch? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ Index: Makefile.inc1 =================================================================== RCS file: /home/ncvs/src/Makefile.inc1,v retrieving revision 1.588.2.1 diff -u -r1.588.2.1 Makefile.inc1 --- Makefile.inc1 11 Oct 2007 06:08:51 -0000 1.588.2.1 +++ Makefile.inc1 11 Oct 2007 18:49:19 -0000 @@ -742,6 +742,10 @@ @echo "ERROR: No kernel \"${KERNCONF}\" to install."; \ false .endif +.if empty(INSTKERNNAME) + @echo "ERROR: Kernel install directory is empty."; \ + false +.endif @echo "--------------------------------------------------------------" @echo ">>> Installing kernel" @echo "--------------------------------------------------------------" From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 19:04: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 2164716A41A for ; Thu, 11 Oct 2007 19:04:45 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from heff.fud.org.nz (203-109-251-39.static.bliink.ihug.co.nz [203.109.251.39]) by mx1.freebsd.org (Postfix) with ESMTP id 6ABC513C467 for ; Thu, 11 Oct 2007 19:04:44 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: by heff.fud.org.nz (Postfix, from userid 1001) id 12B471CC5E; Fri, 12 Oct 2007 08:04:42 +1300 (NZDT) Date: Fri, 12 Oct 2007 08:04:41 +1300 From: Andrew Thompson To: "Ralf S. Engelschall" Message-ID: <20071011190441.GA40950@heff.fud.org.nz> References: <20071011184340.GA13972@engelschall.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071011184340.GA13972@engelschall.com> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-current@freebsd.org Subject: Re: reanimate ZFS pool after disk cloning and host changing 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, 11 Oct 2007 19:04:45 -0000 On Thu, Oct 11, 2007 at 08:43:40PM +0200, Ralf S. Engelschall wrote: > I've a FreeBSD 7-CURRENT (as of 2007-10-09) running in a VirtualBox > virtual machine and with all filesystems except /boot on ZFS. Now that > we switched to 7.0-PRERELEASE and 8-CURRENT I today created another > virtual machine and just cloned the disks (with "vboxmanage clonevdi", > but it doesn't matter here). > > When I then booted the new virtual machine with the cloned disks, the > root filesystem couldn't be mounted during boot via "zfs:zp1/root" as > the ZFS pool "zp1" is no longer available. > > So I booted into the Fixit environment from > "7.0-CURRENT-200709-i386-disc1.iso" and tried "zpool import". It was > able to detect the pool on device ad0s1f. The problem just is that the > hostid has changed (which is correct), so I thought I just have to > re-import the ZFS pool with "zfs import -R /zp1 -f zp1". This still > worked just fine: all filesystem were available under temporary /zp1 > now (I had to use this alternative root or the Fixit environment is > immediately dead). But once I then reboot into the system, the ZFS pool > is again not found via "zfs:zp1/root"! > > In tried multiple times with various ways in the Fixit environment: > "zfs import zp1" is denied because the hostid is different, "zfs import > -f zp1" does the trick (although breaks the Fixit environent) but > after reboot the ZFS pool again gone, "zfs import -R /zp1 -f zp1" does > also the trick but here again the ZFS pool is gone after reboot. > > So, the silly question is: what is the correct way to reanimate a ZFS > pool after the host has changed, so that one can again directly boot > from from one of its filesystems (here "zp1/root")? Is /boot/zfs/zpool.cache up to date after importing the pool? If your seperate /boot filesystem isnt mounted when you import then you will need to overwrite it manually. Andrew From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 19:19: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 C115816A41B for ; Thu, 11 Oct 2007 19:19:35 +0000 (UTC) (envelope-from SRS0=aa74f55947507b98d080042648019bab4b184b21=485=es.net=oberman@es.net) Received: from postal1.es.net (postal3.es.net [IPv6:2001:400:14:3::8]) by mx1.freebsd.org (Postfix) with ESMTP id 5F51213C46B for ; Thu, 11 Oct 2007 19:19:35 +0000 (UTC) (envelope-from SRS0=aa74f55947507b98d080042648019bab4b184b21=485=es.net=oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id QCN78958; Thu, 11 Oct 2007 11:28:58 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 869F54500E; Thu, 11 Oct 2007 11:28:58 -0700 (PDT) To: "Aryeh Friedman" In-Reply-To: Your message of "Thu, 11 Oct 2007 07:35:01 -0000." Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1192127338_72177P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 11 Oct 2007 11:28:58 -0700 From: "Kevin Oberman" Message-Id: <20071011182858.869F54500E@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ; ; ; X-Sender: X-To_Name: Aryeh Friedman X-To_Domain: gmail.com X-To: "Aryeh Friedman" X-To_Email: aryeh.friedman@gmail.com X-To_Alias: aryeh.friedman Cc: ck , freebsd-current@freebsd.org Subject: Re: make error 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, 11 Oct 2007 19:19:35 -0000 --==_Exmh_1192127338_72177P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Thu, 11 Oct 2007 07:35:01 +0000 > From: "Aryeh Friedman" > Sender: owner-freebsd-current@freebsd.org > > On 10/11/07, ck wrote: > > Hi, > > > > I tryed to make the freeBSD snapshot 200709 and i get this error > > Install cvsup and update your sources then try again For a snapshot of Sept 2007 you should have csup. No need to install cvsup. -- 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_1192127338_72177P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFHDmtqkn3rs5h7N1ERAujpAKC5lDtnx+tcDPiQDYuERVp/aYJ+/QCgjJu0 Z84DMnnAT8YLMUx5p8m6lMY= =lK4X -----END PGP SIGNATURE----- --==_Exmh_1192127338_72177P-- From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 20: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 0B16C16A468 for ; Thu, 11 Oct 2007 20:34:21 +0000 (UTC) (envelope-from rse@engelschall.com) Received: from visp1.engelschall.com (visp1.engelschall.com [195.30.6.144]) by mx1.freebsd.org (Postfix) with ESMTP id B195B13C494 for ; Thu, 11 Oct 2007 20:34:20 +0000 (UTC) (envelope-from rse@engelschall.com) Received: by visp1.engelschall.com (Postfix, from userid 21100) id 343901B4482D; Thu, 11 Oct 2007 22:34:17 +0200 (CEST) Received: by en1.engelschall.com (Postfix, from userid 10000) id C4B006DC8B; Thu, 11 Oct 2007 22:32:29 +0200 (CEST) Date: Thu, 11 Oct 2007 22:32:29 +0200 From: "Ralf S. Engelschall" To: freebsd-current@freebsd.org Message-ID: <20071011203229.GA39924@engelschall.com> References: <20071011184340.GA13972@engelschall.com> <20071011190441.GA40950@heff.fud.org.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071011190441.GA40950@heff.fud.org.nz> Organization: FreeBSD User-Agent: Mutt/1.5.16 OpenPKG/CURRENT (2007-06-09) Subject: Re: reanimate ZFS pool after disk cloning and host changing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Ralf S. Engelschall" List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2007 20:34:21 -0000 On Fri, Oct 12, 2007, Andrew Thompson wrote: > On Thu, Oct 11, 2007 at 08:43:40PM +0200, Ralf S. Engelschall wrote: > > I've a FreeBSD 7-CURRENT (as of 2007-10-09) running in a VirtualBox > > virtual machine and with all filesystems except /boot on ZFS. Now that > > we switched to 7.0-PRERELEASE and 8-CURRENT I today created another > > virtual machine and just cloned the disks (with "vboxmanage clonevdi", > > but it doesn't matter here). > > > > When I then booted the new virtual machine with the cloned disks, the > > root filesystem couldn't be mounted during boot via "zfs:zp1/root" as > > the ZFS pool "zp1" is no longer available. > > > > So I booted into the Fixit environment from > > "7.0-CURRENT-200709-i386-disc1.iso" and tried "zpool import". It was > > able to detect the pool on device ad0s1f. The problem just is that the > > hostid has changed (which is correct), so I thought I just have to > > re-import the ZFS pool with "zfs import -R /zp1 -f zp1". This still > > worked just fine: all filesystem were available under temporary /zp1 > > now (I had to use this alternative root or the Fixit environment is > > immediately dead). But once I then reboot into the system, the ZFS pool > > is again not found via "zfs:zp1/root"! > > > > In tried multiple times with various ways in the Fixit environment: > > "zfs import zp1" is denied because the hostid is different, "zfs import > > -f zp1" does the trick (although breaks the Fixit environent) but > > after reboot the ZFS pool again gone, "zfs import -R /zp1 -f zp1" does > > also the trick but here again the ZFS pool is gone after reboot. > > > > So, the silly question is: what is the correct way to reanimate a ZFS > > pool after the host has changed, so that one can again directly boot > > from from one of its filesystems (here "zp1/root")? > > Is /boot/zfs/zpool.cache up to date after importing the pool? If your > seperate /boot filesystem isnt mounted when you import then you will > need to overwrite it manually. Ah, an important point which I totally overlooked. In the Fixit environment /boot is not writable, of course. I retried by mounting the UFS /boot manually inside the Fixit environment before doing the "zfs import". This finally did the trick! Thanks for your quick reply and the essential hint. -- rse@FreeBSD.org Ralf S. Engelschall FreeBSD.org/~rse rse@engelschall.com FreeBSD committer www.engelschall.com From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 20:37: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 998B816A419 for ; Thu, 11 Oct 2007 20:37:35 +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 4BDDD13C469 for ; Thu, 11 Oct 2007 20:37:35 +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 214025378-1834499 for multiple; Thu, 11 Oct 2007 16:35:30 -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 l9BKbDaX029273; Thu, 11 Oct 2007 16:37:18 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Thu, 11 Oct 2007 16:26:34 -0400 User-Agent: KMail/1.9.6 References: <4709666D.5070504@protected-networks.net> In-Reply-To: <4709666D.5070504@protected-networks.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710111626.35144.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]); Thu, 11 Oct 2007 16:37:18 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/4529/Thu Oct 11 02:54:06 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: Michael Butler Subject: Re: Gkrellmd prompts "sleeping thread" 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, 11 Oct 2007 20:37:35 -0000 On Sunday 07 October 2007 07:06:21 pm Michael Butler wrote: > For whatever reason I seem to be able to reliably reproduce a panic on > -current by running gkrellmd on one of my machines yet another (this > one) has no problems at all :-( > > Any thoughts welcome .. > > mail# more info.0 > Dump header from device /dev/ar0s1b > Architecture: i386 > Architecture Version: 2 > Dump Length: 97525760B (93 MB) > Blocksize: 512 > Dumptime: Sun Oct 7 17:15:51 2007 > Hostname: mail.auburn.protected-networks.net > Magic: FreeBSD Kernel Dump > Version String: FreeBSD 7.0-CURRENT #1: Thu Oct 4 22:33:53 EDT 2007 > root@mail.auburn.protected-networks.net:/usr/obj/usr/src/sys/AUBURN > Panic String: sleeping thread > Dump Parity: 3933400909 > Bounds: 0 > Dump Status: good > > mail# kgdb /boot/kernel.old/kernel vmcore.0 > kgdb: kvm_nlist(_stopped_cpus): > kgdb: kvm_nlist(_stoppcbs): > [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 "i386-marcel-freebsd". > (no debugging symbols found)...Attempt to extract a component of a value > that is not a structure pointer. > (kgdb) bt > #0 0xc059f32b in doadump () > #1 0xc059f7a4 in boot () > #2 0xc059fb18 in panic () > #3 0xc05cf172 in propagate_priority () > #4 0xc05cfa66 in turnstile_wait () > #5 0xc0593f11 in _mtx_lock_sleep () > #6 0xc0676011 in intsmb_rawintr () > #7 0xc0583a4d in ithread_loop () > #8 0xc0580774 in fork_exit () > #9 0xc07058a0 in fork_trampoline () Can you make sure you have DDB in your kernel and get the full console messages when it panics? It will include the stack trace for the offending thread. But actually, try this patch: Index: intpm.c =================================================================== RCS file: /usr/cvs/src/sys/pci/intpm.c,v retrieving revision 1.39 diff -u -r1.39 intpm.c --- intpm.c 19 Apr 2007 17:14:06 -0000 1.39 +++ intpm.c 11 Oct 2007 20:25:52 -0000 @@ -436,7 +436,7 @@ /* So that it can use device during device probe on SMBus. */ return (intsmb_stop_poll(sc)); - error = tsleep(sc, PWAIT | PCATCH, "SMBWAI", hz / 8); + error = msleep(sc, &sc->lock, PWAIT | PCATCH, "SMBWAI", hz / 8); if (error == 0) { status = bus_read_1(sc->io_res, PIIX4_SMBHSTSTS); if (!(status & PIIX4_SMBHSTSTAT_BUSY)) { -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 21:42:55 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 2DD2E16A419 for ; Thu, 11 Oct 2007 21:42:55 +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 D019A13C461 for ; Thu, 11 Oct 2007 21:42:54 +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 214034623-1834499 for ; Thu, 11 Oct 2007 17:40:54 -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 l9BLgd4D029723 for ; Thu, 11 Oct 2007 17:42:39 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: current@FreeBSD.org User-Agent: KMail/1.9.6 MIME-Version: 1.0 Content-Disposition: inline X-Length: 6410 X-UID: 1788 Date: Thu, 11 Oct 2007 17:41:34 -0400 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200710111741.34992.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]); Thu, 11 Oct 2007 17:42:39 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/4530/Thu Oct 11 16:02:20 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: Subject: New-bus unit wiring via hints.. 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, 11 Oct 2007 21:42:55 -0000 So one of the things I've wanted to get working for a while is to make ACPI or PNP BIOS devices that are also enumerated by hints "claim" the hints device (assuming that ACPI/PNP BIOS has a more accurate resource list) and use the unit number of the hint it claims. For the non-ACPI case this would get rid of many of the boot messages about PNP devices not probing b/c they couldn't get resources. For the ACPI case allowing devices to be wired to units based on hints will fix the COM port switching problem where a BIOS lists COM2 before COM1 in the ACPI namespace and so the FreeBSD kernel ends up calling COM1 sio1 and COM2 sio0. The idea then, is that ideally a bus driver (like acpi0 for ACPI, or isa0 for PNP BIOS) would be able to hint to new-bus what a potential device's unit number should be by comparing properties of the device about to be probed with the list of hints. It should also not trample on the existing method of enumerating devices from hints using bus_enumerate_hinted_children() / BUS_HINTED_CHILD(). There are some assumptions about hints that do have to change slightly: 1) For a device to count as a "hint" it has to have an "at" hint. (hint.foo.0.at="blah"). 2) An "at" hint for a given (name, unit) _reserves_ that unit number. New-bus will no longer use that unit for a device with a wildcard unit unless the bus specifies that it should use this unit. Note that if you add a device with a specific unit it will still use that unit regardless of any hints that may exist. The way I've done this is to add a new bus callout that is invoked by new-bus when it is going to assign a unit number to a device prior to probing the device. New-bus will now invoke a BUS_HINT_DEVICE_UNIT() method for any devices with a wildcard unit to ask the parent bus driver if it wants to specify a unit for this device. BUS_HINT_DEVICE_UNIT() gets a reference to the new device and the name of the devclass it is being added to. The bus driver can then employ whatever matching scheme it wants. So one simple example I have is that this can be used to wire PCI devices. For example, one impl I have of PCI unit wiring is to make the "at" hint be a selector similar to the argument you give to pciconf(8). Thus, you could do: hint.em.0.at="pci4:3:0" and this will bind em0 to the PCI device at bus 4, slot 3, function 0. (And yes, it is domain aware, but supports the same "shortcut" notations for domain 0 that pciconf(8) does.) Note that if there isn't an em(4) device at pci4:3:0, then em0 is simply reserved, and any other em(4) devices in the system will use em1, em2, etc. The code for the PCI routine to handle this wiring looks something like this: void pci_hint_device_unit(device_t bus, device_t child, const char *name, int *unitp) { struct pci_devinfo *dinfo = device_get_ivars(child); char buf[32]; int line, unit; line = 0; snprintf(buf, sizeof(buf), "pci%d:%d:%d:%d", dinfo->cfg.domain, dinfo->cfg.bus, dinfo->cfg.slot, dinfo->cfg.func); line = 0; if (resource_find_dev(&line, name, &unit, "at", buf) == 0) *unitp = unit; else if (dinfo->cfg.domain == 0) { snprintf(buf, sizeof(buf), "pci%d:%d:%d", dinfo->cfg.bus, dinfo->cfg.slot, dinfo->cfg.func); line = 0; if (resource_find_dev(&line, name, &unit, "at", buf) == 0) *unitp = unit; ... } } Alternatively, if a bus wants to do matching based on resources specified in the hints (like acpi(4) or isa(4)) the BUS_HINT_DEVICE_UNIT() method can use a loop to iterate over all the "foo" devices and perform more detailed checks on each unit: static void acpi_hint_device_unit(device_t acdev, device_t child, const char *name, int *unitp) { ... /* * Iterate over all the hints for the devices with the specified * name to see if one's resources are a subset of this device. */ line = 0; for (;;) { if (resource_find_dev(&line, name, &unit, "at", NULL) != 0) break; /* Must have an "at" for acpi or isa. */ resource_string_value(name, unit, "at", &s); if (!(strcmp(s, "acpi0") == 0 || strcmp(s, "acpi") == 0 || strcmp(s, "isa0") == 0 || strcmp(s, "isa") == 0)) continue; /* * Check for matching resources. We must have at least one, * and all resources specified have to match. * */ matches = 0; /* ... here it compares "port", "mem", "irq", etc. resources with the resources ACPI specified for this device via _CRS */ if (matches > 0) { /* We have a winner! */ *unitp = unit; break; } } } The full patch of what I have so far is at http://www.FreeBSD.org/~jhb/patches/hint_wire.patch and it includes the new-bus changes as well as adding unit-wiring to ACPI, ISA, and PCI. However, what I would like to commit first is a simpler version that just includes the new-bus changes and the ACPI unit-wiring. The ACPI changes have to be included because: 1) ACPI doesn't currently respect hints, so it uses sio0 for the first serial port it encounters. Without a BUS_HINT_DEVICE_UNIT() method, new-bus would reserve sio0 and sio1 via the default hints and would assign the first serial port in ACPI to sio2. The current ISA bus doesn't suffer from this as it statically adds devices based on hints before probing any children devices. 2) One of the things this fixes that is visible to users is that if your machine gets the COM ports backwards when using ACPI it should now get them correct (COM1 as sio0) assuming your COM ports use the default hints and you have the default sio hints in your /boot/device.hints file. The simple patch is at http://www.FreeBSD.org/~jhb/patches/hint_wire_acpi.patch Testing and feedback welcome. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 21:58: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 5C90D16A417 for ; Thu, 11 Oct 2007 21:58:29 +0000 (UTC) (envelope-from scode@hyperion.scode.org) Received: from hyperion.scode.org (cl-1361.ams-04.nl.sixxs.net [IPv6:2001:960:2:550::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0E77A13C465 for ; Thu, 11 Oct 2007 21:58:28 +0000 (UTC) (envelope-from scode@hyperion.scode.org) Received: by hyperion.scode.org (Postfix, from userid 1001) id F416A2394AD; Thu, 11 Oct 2007 23:58:26 +0200 (CEST) Date: Thu, 11 Oct 2007 23:58:26 +0200 From: Peter Schuller To: freebsd-current@freebsd.org Message-ID: <20071011215825.GA84601@hyperion.scode.org> References: <20071009195934.GA13187@outcold.yadt.co.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: <20071009195934.GA13187@outcold.yadt.co.uk> User-Agent: Mutt/1.5.16 (2007-06-09) Subject: Re: Promise SATA controllers & FreeBSD-7 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, 11 Oct 2007 21:58:29 -0000 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > Alternatively, if anyone can recommend a cheap PCI SATA card which is > known to work well with FreeBSD-7, I might just end up buying that... There is the supermicro card based on Marvell 88SX6081. I'm using it on 7 so far with good results (in terms of stability anyway; performance is not that great but that could be due to other reasons; the hardware is not exactly high end otherwise). Someone recently mentioned something about the marvell chipset support being broken by recent changes, but I have yet to hear back what it would be. I haven't had issues so far, with 7 drives, out of which 6 are in a ZFS raidz2 and thus often accesses concurrently. The good part about the card is that you can get it for ~ 100 EUR and it has 8 SATA ports. I'll dig up the card model number if you wish, but it's in the archives, and google("supermicro marvell") should do the trick. --=20 / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHDpyBDNor2+l1i30RAp8qAJ4p/JwR553lbjhomshm49htBXLE4wCeM/35 H3uV1VmU4QmH2oAw/ghd+no= =xa1k -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o-- From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 21:59:52 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 B828016A584; Thu, 11 Oct 2007 21:59:52 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.76]) by mx1.freebsd.org (Postfix) with ESMTP id 904C113C467; Thu, 11 Oct 2007 21:59:52 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (asmtp006-s [10.150.69.69]) by smtpoutm.mac.com (Xserve/smtpout013/MantshX 4.0) with ESMTP id l9BLxq5X008985; Thu, 11 Oct 2007 14:59:52 -0700 (PDT) Received: from [172.24.104.105] (natint3.juniper.net [66.129.224.36]) (authenticated bits=0) by mac.com (Xserve/asmtp006/MantshX 4.0) with ESMTP id l9BLxpd3012828 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 11 Oct 2007 14:59:51 -0700 (PDT) In-Reply-To: <200710111741.34992.jhb@FreeBSD.org> References: <200710111741.34992.jhb@FreeBSD.org> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <622950DD-BFEF-450C-8B80-BAB55C7B58CB@mac.com> Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Thu, 11 Oct 2007 14:59:23 -0700 To: John Baldwin X-Mailer: Apple Mail (2.752.3) Cc: current@FreeBSD.org Subject: Re: New-bus unit wiring via hints.. 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, 11 Oct 2007 21:59:52 -0000 On Oct 11, 2007, at 2:41 PM, John Baldwin wrote: > 2) One of the things this fixes that is visible to users is that if > your > machine gets the COM ports backwards when using ACPI it should > now get > them correct (COM1 as sio0) assuming your COM ports use the > default hints > and you have the default sio hints in your /boot/device.hints file. I think you just pointed out the problem of using hints to wire down unit numbers, because hints will stop hinting and will start dictating. If I swap the serial ports in the BIOS then surely my hints will be wrong and ACPI will be right. A default hints file will be even more disastrous than before. -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 23:00: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 9398816A421 for ; Thu, 11 Oct 2007 23:00:38 +0000 (UTC) (envelope-from erik@cederstrand.dk) Received: from mail.itu.dk (pluto.itu.dk [130.226.142.18]) by mx1.freebsd.org (Postfix) with ESMTP id 3B97F13C491 for ; Thu, 11 Oct 2007 23:00:38 +0000 (UTC) (envelope-from erik@cederstrand.dk) Received: from localhost (unknown [10.0.0.3]) by mail.itu.dk (Postfix) with ESMTP id AE22F41C419 for ; Thu, 11 Oct 2007 22:21:25 +0200 (CEST) X-Virus-Scanned: amavisd-new at itu.dk Received: from superman.itu.dk ([130.226.142.5]) by localhost (daredevil.itu.dk [130.226.142.26]) (amavisd-new, port 10024) with ESMTP id I4qjCrj0ciql for ; Thu, 11 Oct 2007 22:20:56 +0200 (CEST) Received: from wimac.littlebit.dk (unknown [85.233.238.191]) by superman.itu.dk (Postfix) with ESMTP id 024B29E6EC for ; Thu, 11 Oct 2007 22:20:41 +0200 (CEST) Message-ID: <470E8583.5060209@cederstrand.dk> Date: Thu, 11 Oct 2007 22:20:19 +0200 From: Erik Cederstrand User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: acpi.ko not being built? 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, 11 Oct 2007 23:00:38 -0000 Hi! I'm attempting to upgrade a server to amd64 CURRENT from an older snapshot. I have "MODULES_OVERRIDE= acpi" in make.conf but apparently only the acpi_*.ko files are being built, not acpi.ko itself. As a result, acpi.ko is not being loaded on boot. This used to work on 6.2, so I'm not sure where to look. This happens on a GENERIC kernel config. My src.conf has the following: WITHOUT_ATM=yes WITHOUT_AUDIT=yes WITHOUT_BLUETOOTH=yes WITHOUT_CVS=yes WITHOUT_DICT=yes WITHOUT_FORTRAN=yes WITHOUT_GAMES=yes WITHOUT_GPIB=yes WITHOUT_HTML=yes WITHOUT_I4B=yes WITHOUT_INFO=yes WITHOUT_IPX=yes WITHOUT_LPR=yes WITHOUT_SENDMAIL=yes WITHOUT_SHAREDOCS=yes WITHOUT_USB=yes but I don't see anything suspicious there. Thanks, Erik From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 23:20: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 92D8716A41A for ; Thu, 11 Oct 2007 23:20:24 +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 3157D13C46A for ; Thu, 11 Oct 2007 23:20:24 +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 l9BNKGrW043954; Thu, 11 Oct 2007 17:20:17 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <470EAF96.5050106@samsco.org> Date: Thu, 11 Oct 2007 17:19:50 -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: Erik Cederstrand References: <470E8583.5060209@cederstrand.dk> In-Reply-To: <470E8583.5060209@cederstrand.dk> 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]); Thu, 11 Oct 2007 17:20:17 -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: freebsd-current@freebsd.org Subject: Re: acpi.ko not being built? 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, 11 Oct 2007 23:20:24 -0000 Erik Cederstrand wrote: > Hi! > > I'm attempting to upgrade a server to amd64 CURRENT from an older > snapshot. I have "MODULES_OVERRIDE= acpi" in make.conf but apparently > only the acpi_*.ko files are being built, not acpi.ko itself. As a > result, acpi.ko is not being loaded on boot. > > This used to work on 6.2, so I'm not sure where to look. This happens on > a GENERIC kernel config. My src.conf has the following: > Since ACPI is mandatory on amd64, it's included in GENERIC. Not sure why it wouldn't be building as a module for you, but if you're using an unmodified GENERIC then you're already getting it included. Scott From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 23:42: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 B4CAE16A41A for ; Thu, 11 Oct 2007 23:42:43 +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 1019F13C481 for ; Thu, 11 Oct 2007 23:42:42 +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 l9BN4kBR009415; Thu, 11 Oct 2007 18:04:46 -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 l9BN4jFE009414; Thu, 11 Oct 2007 18:04:45 -0500 (CDT) (envelope-from brooks) Date: Thu, 11 Oct 2007 18:04:45 -0500 From: Brooks Davis To: Erik Cederstrand Message-ID: <20071011230445.GA9272@lor.one-eyed-alien.net> References: <470E8583.5060209@cederstrand.dk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bp/iNruPH9dso1Pn" Content-Disposition: inline In-Reply-To: <470E8583.5060209@cederstrand.dk> 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]); Thu, 11 Oct 2007 18:04:46 -0500 (CDT) Cc: freebsd-current@freebsd.org Subject: Re: acpi.ko not being built? 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, 11 Oct 2007 23:42:43 -0000 --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 11, 2007 at 10:20:19PM +0200, Erik Cederstrand wrote: > Hi! >=20 > I'm attempting to upgrade a server to amd64 CURRENT from an older snapsh= ot.=20 > I have "MODULES_OVERRIDE=3D acpi" in make.conf but apparently only the= =20 > acpi_*.ko files are being built, not acpi.ko itself. As a result, acpi.k= o is=20 > not being loaded on boot. On amd64 (and ia64) acpi is compiled in the the kernel rather than built as a module. -- Brooks --bp/iNruPH9dso1Pn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFHDqwNXY6L6fI4GtQRAt86AJ9On4g//nI4uUSF/jarg2a4FX9A2QCeNQyh d3BCNUaZ2coBne/7Pxfq4/I= =NtQv -----END PGP SIGNATURE----- --bp/iNruPH9dso1Pn-- From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 01:02: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 4432116A419 for ; Fri, 12 Oct 2007 01:02:12 +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 A56B413C467 for ; Fri, 12 Oct 2007 01:02:11 +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 l9C12884010180; Thu, 11 Oct 2007 20:02:08 -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 l9C1284L010179; Thu, 11 Oct 2007 20:02:08 -0500 (CDT) (envelope-from brooks) Date: Thu, 11 Oct 2007 20:02:08 -0500 From: Brooks Davis To: Scott Long Message-ID: <20071012010208.GB9272@lor.one-eyed-alien.net> References: <470E8583.5060209@cederstrand.dk> <470EAF96.5050106@samsco.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wq9mPyueHGvFACwf" Content-Disposition: inline In-Reply-To: <470EAF96.5050106@samsco.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]); Thu, 11 Oct 2007 20:02:09 -0500 (CDT) Cc: freebsd-current@freebsd.org, Erik Cederstrand Subject: Re: acpi.ko not being built? 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, 12 Oct 2007 01:02:12 -0000 --wq9mPyueHGvFACwf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 11, 2007 at 05:19:50PM -0600, Scott Long wrote: > Erik Cederstrand wrote: > > Hi! > > I'm attempting to upgrade a server to amd64 CURRENT from an older snaps= hot.=20 > > I have "MODULES_OVERRIDE=3D acpi" in make.conf but apparently only the= =20 > > acpi_*.ko files are being built, not acpi.ko itself. As a result, acpi.= ko=20 > > is not being loaded on boot. > > This used to work on 6.2, so I'm not sure where to look. This happens o= n a=20 > > GENERIC kernel config. My src.conf has the following: >=20 > Since ACPI is mandatory on amd64, it's included in GENERIC. Not sure wh= y it=20 > wouldn't be building as a module for you, but if you're using an > unmodified GENERIC then you're already getting it included. When I looked earlier today it looks like the sys/modules/acpi Makefiles would just refuse if you tried. -- Brooks --wq9mPyueHGvFACwf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFHDsePXY6L6fI4GtQRAuczAJ9/yXPiElT2XhA2Z0grGyFVT7OrxgCdFwvE RdskyvigZI5Bj/EwchN1rps= =3GqO -----END PGP SIGNATURE----- --wq9mPyueHGvFACwf-- From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 02:38: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 C19C216A469 for ; Fri, 12 Oct 2007 02:38:18 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: from acm.poly.edu (acm.poly.edu [128.238.9.200]) by mx1.freebsd.org (Postfix) with ESMTP id 5DA2B13C457 for ; Fri, 12 Oct 2007 02:38:18 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: (qmail 33002 invoked from network); 12 Oct 2007 02:33:13 -0000 Received: from unknown (HELO ?192.168.0.2?) (spawk@69.123.41.145) by acm.poly.edu with AES256-SHA encrypted SMTP; 12 Oct 2007 02:33:13 -0000 Message-ID: <470EDE0E.8070800@acm.poly.edu> Date: Thu, 11 Oct 2007 22:38:06 -0400 From: Boris Kochergin User-Agent: Thunderbird 2.0.0.0 (X11/20070609) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: ZFS raidz1 redundancy 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, 12 Oct 2007 02:38:18 -0000 Hi. I'm running running an i386 -CURRENT built on October 2nd. I have a raidz1 pool consisting of seven 400-GiB PATA disks. ad4 and ad5 are part of the pool. This afternoon, the following happened: Oct 11 19:05:27 exodus kernel: ad4: timeout waiting to issue command Oct 11 19:05:27 exodus kernel: ad4: error issuing READ_DMA command Oct 11 19:05:27 exodus root: ZFS: vdev I/O failure, zpool=home path=/dev/ad4 offset=70362711040 size=21504 error=5 The machine proceeded to panic after that, and when it rebooted, the following happened after a while: Oct 11 19:11:40 exodus kernel: ad5: detached Oct 11 19:11:40 exodus kernel: ad4: TIMEOUT - READ_DMA retrying (1 retry left) LBA=32 It crashed again half an hour after that, and when it came back up, ad4 was no longer detected by the ATA controller. The output of "zpool status" is as follows: pool: home state: FAULTED status: One or more devices could not be opened. There are insufficient replicas for the pool to continue functioning. action: Attach the missing device and online it using 'zpool online'. see: http://www.sun.com/msg/ZFS-8000-D3 scrub: none requested config: NAME STATE READ WRITE CKSUM home FAULTED 6 0 0 corrupted data raidz1 DEGRADED 6 0 0 ad4 UNAVAIL 0 0 0 cannot open ad5 ONLINE 0 0 0 ad10 ONLINE 0 0 0 ad11 ONLINE 0 0 0 ad8 ONLINE 0 0 0 ad9 ONLINE 0 0 0 ad6 ONLINE 0 0 0 Is it possible that the data on ad5, in the midst of the failured of ad4, has become inconsistent with the other members of the pool, and that I need to bring ad4 online (I'm fairly sure that it's a motherboard- or power-related issue and that the drive is OK) to be able to access the data on the pool? -Boris From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 03:44: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 968A916A41A; Fri, 12 Oct 2007 03:44:08 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.freebsd.org (Postfix) with ESMTP id 082BD13C467; Fri, 12 Oct 2007 03:44:07 +0000 (UTC) (envelope-from max@love2party.net) Received: from amd64.laiers.local (dslb-088-066-018-083.pools.arcor-ip.net [88.66.18.83]) by mrelayeu.kundenserver.de (node=mrelayeu7) with ESMTP (Nemesis) id 0ML2xA-1IgBRW1kNB-0001gs; Fri, 12 Oct 2007 05:44:06 +0200 From: Max Laier Organization: FreeBSD To: freebsd-net@freebsd.org Date: Fri, 12 Oct 2007 05:43:54 +0200 User-Agent: KMail/1.9.7 References: <200709302232.34505.max@love2party.net> <200710020356.10429.max@love2party.net> In-Reply-To: <200710020356.10429.max@love2party.net> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart8339406.YbBDa69ZZZ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200710120544.04157.max@love2party.net> X-Provags-ID: V01U2FsdGVkX1/3Gu/jctK19UjdVqPFoe84OkjLQ1O/kHPAyUb kBMNESmA/+DJFC59V1nq4CGp1V6yddAHdux6Smkubgimq+I6Sg qJEtUQwQ23q8IFPxTHkK6jJQU5iOHE8sE3IPxTfwEA= Cc: freebsd-current@freebsd.org Subject: Re: libpcap/tcpdump update 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, 12 Oct 2007 03:44:08 -0000 --nextPart8339406.YbBDa69ZZZ Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 02 October 2007, Max Laier wrote: > On Sunday 30 September 2007, Max Laier wrote: > > Hi, > > > > I'd like to get some eyes on > > http://people.freebsd.org/~mlaier/tcpdump/ in order to get $subj into > > the tree. Let me know if you find any problems. Thanks. > > > > This should also take care of bin/116610, by the way. > > Please refresh - the first version didn't get through buildworld - > sorry! I plan to do this really soon now with the HEAD freeze lifted. Did anyone= =20 get to test it? Any objections? =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart8339406.YbBDa69ZZZ 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) iD8DBQBHDu2EXyyEoT62BG0RAo2yAJ9lN//JsU+CMJrNFsxemBXlWU+vkgCffn2u NmerHcJ6Q7ftCygrBwKOmII= =qMU4 -----END PGP SIGNATURE----- --nextPart8339406.YbBDa69ZZZ-- From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 03:44: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 9E02216A41A for ; Fri, 12 Oct 2007 03:44:39 +0000 (UTC) (envelope-from pyunyh@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 50F5313C46B for ; Fri, 12 Oct 2007 03:44:39 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so884160waf for ; Thu, 11 Oct 2007 20:44:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=/EeDRBjxb5OtF1nTfctrNQyt9w8Go+tHjXnhPAqnV1E=; b=aFg6s6qvvjhKpTHd73+5HwEUndOrujDkL0hNTgw7eh+6nujsUmKuJUtvgPxH/GAiIPYTd7xXMa1hTaAcfvCxaaouDZ8/g6ll6140Bkpw7HqHPfQDNAmcJ5ImkaKBaUKze/rgQu49YGZ5luVfuRevnWqyquAlpaxDlnpgKEutChM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=l1NQ9CtBtdjlktAYIDnJQ4XGm3ZrBiFXcHeOP7bh9uOv5Xfj05M8ab27e7FsqJzTc6ciz9HJJgF/ImTBDjRja33iWLZY7BusyCxV71wZFcRgpbzN0hh2IlV6cBCOLhp4pTwTdvJIKTJoPynHSJ1IvZGaplOe4BqjgyMl+VAcy0k= Received: by 10.114.103.1 with SMTP id a1mr3010699wac.1192160678907; Thu, 11 Oct 2007 20:44:38 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id n37sm302305wag.2007.10.11.20.44.35 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 11 Oct 2007 20:44:37 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l9C3evRG064211 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Oct 2007 12:40:57 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l9C3evVc064210; Fri, 12 Oct 2007 12:40:57 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 12 Oct 2007 12:40:57 +0900 From: Pyun YongHyeon To: John Baldwin Message-ID: <20071012034057.GA63854@cdnetworks.co.kr> References: <20070827201809.0367616A418@hub.freebsd.org> <20070828010310.GA85263@cdnetworks.co.kr> <200710101551.26081.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200710101551.26081.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: Bill Paul , freebsd-current@freebsd.org, freebsd-net@freebsd.org Subject: Re: Bug in vr(4) driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@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, 12 Oct 2007 03:44:39 -0000 On Wed, Oct 10, 2007 at 03:51:25PM -0400, John Baldwin wrote: > On Monday 27 August 2007 09:03:10 pm Pyun YongHyeon wrote: > > On Mon, Aug 27, 2007 at 08:18:08PM +0000, Bill Paul wrote: > > > > > > I recently started writing a driver for the Via Rhine family of chips > > > for VxWorks (they turn up on various x86-based single board systems, > > > and I figured it'd be nice to actually support them out of the box), > > > and along the way, I noticed a subtle bug in the FreeBSD vr(4) driver. > > > > > > The vr_attach() routine unconditionally does this for all supported > > > chips: > > > > > > /* > > > * Windows may put the chip in suspend mode when it > > > * shuts down. Be sure to kick it in the head to wake it > > > * up again. > > > */ > > > VR_CLRBIT(sc, VR_STICKHW, (VR_STICKHW_DS0|VR_STICKHW_DS1)); > > > > > > The problem is, the VR_STICKHW register is not valid on all Rhine > > > devices. The VT86C100A chip, which is present on the D-Link DFE-530TX > > > boards, doesn't support power management, and its register space is > > > only 128 bytes wide. The VR_STICKHW register offset falls outside this > > > range. This may go unnoticed in most scenarios, but if you happen to have > > > another PCI device in your system which is assigned the register > > > space immediately after that of the Rhine, the vr(4) driver will > > > incorrectly stomp it. In my case, the BIOS on my test board decided > > > to put the register space for my PRO/100 ethernet board right next > > > to the Rhine, and the Rhine driver ended up clobbering the IMR register > > > of the PRO/100 device. (Long story short: the board kept locking up on > > > boot. Took me the better part of the morning suss out why.) > > > > > > The strictly correct thing to do would be to check the PCI config space > > > to make sure the device supports the power management capability and only > > > write to the VR_STICKHW register if it does. A less strictly correct > > > but equally effective thing to do would be: > > > > > > /* > > > * Windows may put the chips that support power management into > > > * suspend mode when it shuts down. Be sure to kick it in the > > > * head to wake it up again. > > > */ > > > if (pci_get_device(dev) != VIA_DEVICEID_RHINE) > > > VR_CLRBIT(sc, VR_STICKHW, (VR_STICKHW_DS0|VR_STICKHW_DS1)); > > > > > > This is basically the fix I put into my VxWorks driver. I suggest someone > > > update the FreeBSD driver as well. > > > > > > > Hi, > > > > I don't have vr(4) hardwares(if I had I would have converted vr(4) > > to use bus_dma(9)). Would you review/test the attached patch? > > Pyun, > > I'd say to go ahead and commit the patch. > For a record, I've commited the patch to CURRENT/RELENG_7. -- Regards, Pyun YongHyeon From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 03:52: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 E32EB16A468 for ; Fri, 12 Oct 2007 03:52:54 +0000 (UTC) (envelope-from benfell@earth.parts-unknown.org) Received: from earth.parts-unknown.org (earth.parts-unknown.org [66.93.170.243]) by mx1.freebsd.org (Postfix) with SMTP id 8D24613C459 for ; Fri, 12 Oct 2007 03:52:54 +0000 (UTC) (envelope-from benfell@earth.parts-unknown.org) Received: (qmail 3869 invoked by uid 501); 12 Oct 2007 03:25:16 -0000 Date: Thu, 11 Oct 2007 20:25:16 -0700 From: David Benfell To: FreeBSD Current Message-ID: <20071012032516.GA2964@parts-unknown.org> Mail-Followup-To: FreeBSD Current MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3V7upXqbjpZ4EhLz" Content-Disposition: inline X-gnupg-public-key: http://www.parts-unknown.org/gnupg/export-0DD1D1E3 X-stardate: [-29]8340.70 X-moon: The Moon is Waxing Crescent (1% of Full) User-Agent: Mutt/1.5.16 (2007-06-09) Subject: Version 8.0?!!??? 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, 12 Oct 2007 03:52:55 -0000 --3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all, So I was in for a bit of a surprise when I just booted up the a version of CURRENT built today: FreeBSD earth.cybernude.org 8.0-CURRENT FreeBSD 8.0-CURRENT #56: Thu Oct 11= 10:27:17 PDT 2007 root@earth.cybernude.org:/usr/obj/usr/src/sys/EARTH = i386 [snicker] No real harm, right? --=20 David Benfell, LCP benfell@parts-unknown.org --- Resume available at http://www.parts-unknown.org/ NOTE: I sign all messages with GnuPG (0DD1D1E3). --3V7upXqbjpZ4EhLz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHDukcUd+dMw3R0eMRAsjdAJ0WYA0kf/ol8avMqfVDT2r/Y0tbKQCeIqtF GduXMEKtUWN/WQu3KPaEriY= =pGDJ -----END PGP SIGNATURE----- --3V7upXqbjpZ4EhLz-- From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 04:00: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 6E14416A41A for ; Fri, 12 Oct 2007 04:00:13 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (lindfield.ch [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id 1A35913C480 for ; Fri, 12 Oct 2007 04:00:12 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:62161 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1IgBh5-0000Vb-Qi for freebsd-current@freebsd.org; Fri, 12 Oct 2007 04:00:11 +0000 Message-ID: <470EF14B.5080009@conducive.net> Date: Fri, 12 Oct 2007 00:00:11 -0400 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <109c90a0710111059qf50158bn95574464bcd0a9df@mail.gmail.com> In-Reply-To: <109c90a0710111059qf50158bn95574464bcd0a9df@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Asus M2N with two sata disks. 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, 12 Oct 2007 04:00:13 -0000 Eimar Koort wrote: > Hi all, > > Motherboard: Asus M2N [1] > Bios version: v02.58 > > When two SATA disks are added to machine, then it does'nt boot up or > sometimes it can boot up but detaching second disk "like mad". Several > months ago it was so 'stable', that i could boot up and create geom mirror > (Jul 3). After updating several times things went update by update more > unstable. At the moment machine is usable only with one disk. > Second disk is tested with other operating systems and it works. Also > changing sata channels doesn't make it better. > > And question: has anyone same or similar problem or has found a cure for > this problem? > Yes. Adding HDD (PATA or SATA) or even a second NIC on an ASUS P5K. A new Power supply fixed those and other similar problems, but not before I had bought a GigaByte G33-DS3R replacement MB - and hit the same wall. Though I have a dual-trace Fluke 'Scopemeter', the PSU was so cheap I never did check to see if it was voltage drop or just noise spiking. Not to say this applies in your case, just that it is reasonably easy to check. Bill From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 04:01: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 C986116A419; Fri, 12 Oct 2007 04:01:48 +0000 (UTC) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [IPv6:2001:5a8:4:2140::3]) by mx1.freebsd.org (Postfix) with ESMTP id 78BDA13C455; Fri, 12 Oct 2007 04:01:48 +0000 (UTC) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.14.1/8.14.1) with ESMTP id l9C41mq9056906; Thu, 11 Oct 2007 21:01:48 -0700 (PDT) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.14.1/8.14.1/Submit) id l9C41mSg056905; Thu, 11 Oct 2007 21:01:48 -0700 (PDT) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-current@freebsd.org Date: Thu, 11 Oct 2007 21:01:47 -0700 User-Agent: KMail/1.9.6 References: <200710111741.34992.jhb@FreeBSD.org> <622950DD-BFEF-450C-8B80-BAB55C7B58CB@mac.com> In-Reply-To: <622950DD-BFEF-450C-8B80-BAB55C7B58CB@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710112101.48119.peter@wemm.org> Cc: Marcel Moolenaar , current@freebsd.org Subject: Re: New-bus unit wiring via hints.. 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, 12 Oct 2007 04:01:48 -0000 On Thursday 11 October 2007, Marcel Moolenaar wrote: > On Oct 11, 2007, at 2:41 PM, John Baldwin wrote: > > 2) One of the things this fixes that is visible to users is that if > > your > > machine gets the COM ports backwards when using ACPI it should > > now get > > them correct (COM1 as sio0) assuming your COM ports use the > > default hints > > and you have the default sio hints in your /boot/device.hints > > file. > > I think you just pointed out the problem of using hints to wire > down unit numbers, because hints will stop hinting and will start > dictating. If I swap the serial ports in the BIOS then surely > my hints will be wrong and ACPI will be right. Not necessarily. It has been a long standing problem that ACPI is wrong (or sub-optimal) about serial ports. There are many machines that list 0x2f8 first, and 0x3f8 second. As a result, we bind sio0 to com2, and sio1 to com1. I like the way John did it. It reserves the unit numbers for hardware that matches the hints. For example, sio0 may be reserved for a com port that is found that had 0x3f8. If nothing has 0x3f8, then sio0 won't be created. > A default hints > file will be even more disastrous than before. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 04:01: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 C986116A419; Fri, 12 Oct 2007 04:01:48 +0000 (UTC) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [IPv6:2001:5a8:4:2140::3]) by mx1.freebsd.org (Postfix) with ESMTP id 78BDA13C455; Fri, 12 Oct 2007 04:01:48 +0000 (UTC) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.14.1/8.14.1) with ESMTP id l9C41mq9056906; Thu, 11 Oct 2007 21:01:48 -0700 (PDT) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.14.1/8.14.1/Submit) id l9C41mSg056905; Thu, 11 Oct 2007 21:01:48 -0700 (PDT) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-current@freebsd.org Date: Thu, 11 Oct 2007 21:01:47 -0700 User-Agent: KMail/1.9.6 References: <200710111741.34992.jhb@FreeBSD.org> <622950DD-BFEF-450C-8B80-BAB55C7B58CB@mac.com> In-Reply-To: <622950DD-BFEF-450C-8B80-BAB55C7B58CB@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710112101.48119.peter@wemm.org> Cc: Marcel Moolenaar , current@freebsd.org Subject: Re: New-bus unit wiring via hints.. 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, 12 Oct 2007 04:01:48 -0000 On Thursday 11 October 2007, Marcel Moolenaar wrote: > On Oct 11, 2007, at 2:41 PM, John Baldwin wrote: > > 2) One of the things this fixes that is visible to users is that if > > your > > machine gets the COM ports backwards when using ACPI it should > > now get > > them correct (COM1 as sio0) assuming your COM ports use the > > default hints > > and you have the default sio hints in your /boot/device.hints > > file. > > I think you just pointed out the problem of using hints to wire > down unit numbers, because hints will stop hinting and will start > dictating. If I swap the serial ports in the BIOS then surely > my hints will be wrong and ACPI will be right. Not necessarily. It has been a long standing problem that ACPI is wrong (or sub-optimal) about serial ports. There are many machines that list 0x2f8 first, and 0x3f8 second. As a result, we bind sio0 to com2, and sio1 to com1. I like the way John did it. It reserves the unit numbers for hardware that matches the hints. For example, sio0 may be reserved for a com port that is found that had 0x3f8. If nothing has 0x3f8, then sio0 won't be created. > A default hints > file will be even more disastrous than before. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 04:09: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 15CEA16A417 for ; Fri, 12 Oct 2007 04:09:57 +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 B995213C447 for ; Fri, 12 Oct 2007 04:09:56 +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 l9C45YcL029091 for ; Thu, 11 Oct 2007 21:05:34 -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 l9C45Yxf029090 for freebsd-current@freebsd.org; Thu, 11 Oct 2007 21:05:34 -0700 (PDT) (envelope-from sgk) Date: Thu, 11 Oct 2007 21:05:34 -0700 From: Steve Kargl To: FreeBSD Current Message-ID: <20071012040534.GA29064@troutmask.apl.washington.edu> References: <20071012032516.GA2964@parts-unknown.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071012032516.GA2964@parts-unknown.org> User-Agent: Mutt/1.4.2.3i Subject: Re: Version 8.0?!!??? 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, 12 Oct 2007 04:09:57 -0000 On Thu, Oct 11, 2007 at 08:25:16PM -0700, David Benfell wrote: > > So I was in for a bit of a surprise when I just booted up the > a version of CURRENT built today: > > FreeBSD earth.cybernude.org 8.0-CURRENT FreeBSD 8.0-CURRENT #56: Thu Oct 11 10:27:17 PDT 2007 root@earth.cybernude.org:/usr/obj/usr/src/sys/EARTH i386 > > [snicker] > > No real harm, right? > Apparently, you don't read the freebsd-current and cvs-src mailing list. See the archives from today. -- Steve From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 04:30: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 DBBF016A417 for ; Fri, 12 Oct 2007 04:30:48 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mx1.freebsd.org (Postfix) with ESMTP id 4CEBF13C44B for ; Fri, 12 Oct 2007 04:30:47 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l9C4Uh0d093081; Fri, 12 Oct 2007 14:30:43 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l9C4UhFV093080; Fri, 12 Oct 2007 14:30:43 +1000 (EST) (envelope-from peter) Date: Fri, 12 Oct 2007 14:30:43 +1000 From: Peter Jeremy To: Steve Kargl Message-ID: <20071012043043.GF92987@turion.vk2pj.dyndns.org> References: <20071012032516.GA2964@parts-unknown.org> <20071012040534.GA29064@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oyUTqETQ0mS9luUI" Content-Disposition: inline In-Reply-To: <20071012040534.GA29064@troutmask.apl.washington.edu> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.16 (2007-06-09) Cc: FreeBSD Current Subject: Re: Version 8.0?!!??? 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, 12 Oct 2007 04:30:48 -0000 --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-Oct-11 21:05:34 -0700, Steve Kargl wrote: >On Thu, Oct 11, 2007 at 08:25:16PM -0700, David Benfell wrote: >>=20 >> So I was in for a bit of a surprise when I just booted up the >> a version of CURRENT built today: >>=20 >> FreeBSD earth.cybernude.org 8.0-CURRENT FreeBSD 8.0-CURRENT #56: Thu Oct= 11 10:27:17 PDT 2007 root@earth.cybernude.org:/usr/obj/usr/src/sys/EAR= TH i386 >>=20 >> [snicker] >>=20 >> No real harm, right? RELENG_7 was branched yesterday so HEAD is now 8.0-CURRENT. >Apparently, you don't read the freebsd-current and cvs-src >mailing list. See the archives from today.=20 Actually, David's mail is the first freebsd-current mail I can find that mentions 8-current. All the other references I recall seeing have been in cvs-src. I _was_ expecting a heads-up here. FWIW, HEAD is also now unfrozen. --=20 Peter Jeremy --oyUTqETQ0mS9luUI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHDvhz/opHv/APuIcRAkeKAJ4hCozDeVkH2QNeogOjpmNC84XIogCdGTcy O2O9CEcdrAl5B4r4j5SFnEE= =VNAn -----END PGP SIGNATURE----- --oyUTqETQ0mS9luUI-- From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 05:19:03 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 2A68116A51A for ; Fri, 12 Oct 2007 05:19:03 +0000 (UTC) (envelope-from barnaclewes@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 7EE2F13C459 for ; Fri, 12 Oct 2007 05:19:02 +0000 (UTC) (envelope-from barnaclewes@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so668112nfb for ; Thu, 11 Oct 2007 22:19: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=EoGY2jd2vKthp4bkpRe5aawZSuGkJDPdJzWNKBBPuos=; b=dChEkI5IXu/aFV2KLv8nPSHMu3D+1Yk7tvoiXoQH222DmO7q+zRqNJOG2OffdYinGyckDsqiY9wLec2txjUE9dvB8OEUDa0Vhy6hGTCsJLDfQA1K/GYASgPllCdes+jpGlc3WvigpUJ98+pvK3CHxxJemKo3400GOhi82WcXYI8= 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=nHFUMlRPuybOjL6GjGJZZfrqRHTS/wedP8P74NYSXlkEA3jBYKkWP++5Nz6Etpl1/HWSdCmPDe7AdqaTS1IjynuuFM/zncobxKkiz02h30WrJ9TPS2YPxziYeXmaZi0XKbjStskqd5Hj76xIriaAypt9FyQVjzfpF78iOOZquP4= Received: by 10.78.142.14 with SMTP id p14mr1978778hud.1192164809570; Thu, 11 Oct 2007 21:53:29 -0700 (PDT) Received: by 10.78.198.4 with HTTP; Thu, 11 Oct 2007 21:53:29 -0700 (PDT) Message-ID: Date: Thu, 11 Oct 2007 21:53:29 -0700 From: "Wes Peters" To: "Dmitry Morozovsky" In-Reply-To: <20071011224937.D97516@woozle.rinet.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071011224937.D97516@woozle.rinet.ru> Cc: current@freebsd.org Subject: Re: INSTKERNNAME= foolproof check 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, 12 Oct 2007 05:19:03 -0000 On 10/11/07, Dmitry Morozovsky wrote: > Colleagues, > > Today I successfully shoot myself in the foot by typing > > make installkernel KERNCONF=GENERIC INSTKERNNAME= > > instead of usual > > make installkernel KERNCONF=GENERIC INSTKERNNAME=GENERIC > > Empty INSTKERNNAME leads to wiping /boot completely - rather annoying, > especially in my case, where I had some non-trivial (and, of course, no backups > ;-) loader.conf > > What do you think about the following patch? > > Sincerely, > D.Marck [DM5020, MCK-RIPE, DM3-RIPN] > [ FreeBSD committer: marck@FreeBSD.org ] > ------------------------------------------------------------------------ > *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** > ------------------------------------------------------------------------ > > > Index: Makefile.inc1 > =================================================================== > RCS file: /home/ncvs/src/Makefile.inc1,v > retrieving revision 1.588.2.1 > diff -u -r1.588.2.1 Makefile.inc1 > --- Makefile.inc1 11 Oct 2007 06:08:51 -0000 1.588.2.1 > +++ Makefile.inc1 11 Oct 2007 18:49:19 -0000 > @@ -742,6 +742,10 @@ > @echo "ERROR: No kernel \"${KERNCONF}\" to install."; \ > false > .endif > +.if empty(INSTKERNNAME) > + @echo "ERROR: Kernel install directory is empty."; \ > + false > +.endif > @echo "--------------------------------------------------------------" > @echo ">>> Installing kernel" > @echo "--------------------------------------------------------------" > Seems like a very good idea to me. -- Against stupidity the very gods Themselves contend in vain. Friedrich Schiller Wes Peters barnaclewes@gmail.com From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 05:34: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 BEB0E16A41B for ; Fri, 12 Oct 2007 05:34:03 +0000 (UTC) (envelope-from benfell@earth.parts-unknown.org) Received: from earth.parts-unknown.org (earth.parts-unknown.org [66.93.170.243]) by mx1.freebsd.org (Postfix) with SMTP id 9502C13C481 for ; Fri, 12 Oct 2007 05:34:03 +0000 (UTC) (envelope-from benfell@earth.parts-unknown.org) Received: (qmail 52104 invoked by uid 501); 12 Oct 2007 05:33:36 -0000 Date: Thu, 11 Oct 2007 22:33:36 -0700 From: David Benfell To: Peter Jeremy Message-ID: <20071012053336.GA49367@parts-unknown.org> Mail-Followup-To: Peter Jeremy , Steve Kargl , FreeBSD Current References: <20071012032516.GA2964@parts-unknown.org> <20071012040534.GA29064@troutmask.apl.washington.edu> <20071012043043.GF92987@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/" Content-Disposition: inline In-Reply-To: <20071012043043.GF92987@turion.vk2pj.dyndns.org> X-gnupg-public-key: http://www.parts-unknown.org/gnupg/export-0DD1D1E3 X-stardate: [-29]8341.13 X-moon: The Moon is Waxing Crescent (1% of Full) User-Agent: Mutt/1.5.16 (2007-06-09) Cc: FreeBSD Current , Steve Kargl Subject: Re: Version 8.0?!!??? 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, 12 Oct 2007 05:34:03 -0000 --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, 12 Oct 2007 14:30:43 +1000, Peter Jeremy wrote: > On 2007-Oct-11 21:05:34 -0700, Steve Kargl wrote: > >On Thu, Oct 11, 2007 at 08:25:16PM -0700, David Benfell wrote: > >>=20 > >> So I was in for a bit of a surprise when I just booted up the > >> a version of CURRENT built today: > >>=20 > >> FreeBSD earth.cybernude.org 8.0-CURRENT FreeBSD 8.0-CURRENT #56: Thu O= ct 11 10:27:17 PDT 2007 root@earth.cybernude.org:/usr/obj/usr/src/sys/E= ARTH i386 > >>=20 > >> [snicker] > >>=20 > >> No real harm, right? >=20 > RELENG_7 was branched yesterday so HEAD is now 8.0-CURRENT. >=20 > >Apparently, you don't read the freebsd-current and cvs-src > >mailing list. See the archives from today.=20 >=20 > Actually, David's mail is the first freebsd-current mail I can find > that mentions 8-current. All the other references I recall seeing > have been in cvs-src. I _was_ expecting a heads-up here. >=20 > FWIW, HEAD is also now unfrozen. >=20 I am not subscribed to cvs-src. I have had a subscription to freebsd-current for a while, but only actually started building -CURRENT in response to some USB issues (which are only partially resolved) with my Treo 700p. As my systems are production systems, I shall now retreat to RELENG_7. Thanks! --=20 David Benfell, LCP benfell@parts-unknown.org --- Resume available at http://www.parts-unknown.org/ NOTE: I sign all messages with GnuPG (0DD1D1E3). --TB36FDmn/VVEgNH/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHDwcwUd+dMw3R0eMRAmI7AJ421Re9JnhWo+YuEtEzjlBtZcsrHACeOvHB 3ix5Pukle+67Vvo3UeyG+2k= =5fOr -----END PGP SIGNATURE----- --TB36FDmn/VVEgNH/-- From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 06:24:05 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 7FA3216A41B; Fri, 12 Oct 2007 06:24:05 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.70]) by mx1.freebsd.org (Postfix) with ESMTP id 63A8213C459; Fri, 12 Oct 2007 06:24:05 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpoutm.mac.com (Xserve/smtpout007/MantshX 4.0) with ESMTP id l9C6O5v7028774; Thu, 11 Oct 2007 23:24:05 -0700 (PDT) Received: from [172.23.8.50] (nat-service4.juniper.net [66.129.225.151]) (authenticated bits=0) by mac.com (Xserve/smtpin08/MantshX 4.0) with ESMTP id l9C6O0L9016177 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 11 Oct 2007 23:24:01 -0700 (PDT) In-Reply-To: <200710112101.48119.peter@wemm.org> References: <200710111741.34992.jhb@FreeBSD.org> <622950DD-BFEF-450C-8B80-BAB55C7B58CB@mac.com> <200710112101.48119.peter@wemm.org> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <4FF02B0F-1663-4100-9A8F-EAA9CF833DDF@mac.com> Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Thu, 11 Oct 2007 23:23:30 -0700 To: Peter Wemm X-Mailer: Apple Mail (2.752.3) Cc: freebsd-current@freebsd.org, current@freebsd.org Subject: Re: New-bus unit wiring via hints.. 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, 12 Oct 2007 06:24:05 -0000 On Oct 11, 2007, at 9:01 PM, Peter Wemm wrote: > On Thursday 11 October 2007, Marcel Moolenaar wrote: >> On Oct 11, 2007, at 2:41 PM, John Baldwin wrote: >>> 2) One of the things this fixes that is visible to users is that if >>> your >>> machine gets the COM ports backwards when using ACPI it should >>> now get >>> them correct (COM1 as sio0) assuming your COM ports use the >>> default hints >>> and you have the default sio hints in your /boot/device.hints >>> file. >> >> I think you just pointed out the problem of using hints to wire >> down unit numbers, because hints will stop hinting and will start >> dictating. If I swap the serial ports in the BIOS then surely >> my hints will be wrong and ACPI will be right. > > Not necessarily. It has been a long standing problem that ACPI is > wrong > (or sub-optimal) about serial ports. There are many machines that > list > 0x2f8 first, and 0x3f8 second. As a result, we bind sio0 to com2, and > sio1 to com1. I don't think it's wrong. It's just non-legacy. The whiole purpose of ACPI is to migrate away from those legacy resource allocations and allow for greater flexibility. It seems to me that instead of embracing the freedom for BIOS/firmware writers, we hold on to those old and obsolete notions. As such, it's not a step forwards, it's a step back. > I like the way John did it. It reserves the unit numbers for hardware > that matches the hints. This is not a bad thing, but the ambiguity introduced by re-using hints for that is bad and a recipe for problems. -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 06:24: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 7FA3216A41B; Fri, 12 Oct 2007 06:24:05 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.70]) by mx1.freebsd.org (Postfix) with ESMTP id 63A8213C459; Fri, 12 Oct 2007 06:24:05 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpoutm.mac.com (Xserve/smtpout007/MantshX 4.0) with ESMTP id l9C6O5v7028774; Thu, 11 Oct 2007 23:24:05 -0700 (PDT) Received: from [172.23.8.50] (nat-service4.juniper.net [66.129.225.151]) (authenticated bits=0) by mac.com (Xserve/smtpin08/MantshX 4.0) with ESMTP id l9C6O0L9016177 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 11 Oct 2007 23:24:01 -0700 (PDT) In-Reply-To: <200710112101.48119.peter@wemm.org> References: <200710111741.34992.jhb@FreeBSD.org> <622950DD-BFEF-450C-8B80-BAB55C7B58CB@mac.com> <200710112101.48119.peter@wemm.org> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <4FF02B0F-1663-4100-9A8F-EAA9CF833DDF@mac.com> Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Thu, 11 Oct 2007 23:23:30 -0700 To: Peter Wemm X-Mailer: Apple Mail (2.752.3) Cc: freebsd-current@freebsd.org, current@freebsd.org Subject: Re: New-bus unit wiring via hints.. 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, 12 Oct 2007 06:24:05 -0000 On Oct 11, 2007, at 9:01 PM, Peter Wemm wrote: > On Thursday 11 October 2007, Marcel Moolenaar wrote: >> On Oct 11, 2007, at 2:41 PM, John Baldwin wrote: >>> 2) One of the things this fixes that is visible to users is that if >>> your >>> machine gets the COM ports backwards when using ACPI it should >>> now get >>> them correct (COM1 as sio0) assuming your COM ports use the >>> default hints >>> and you have the default sio hints in your /boot/device.hints >>> file. >> >> I think you just pointed out the problem of using hints to wire >> down unit numbers, because hints will stop hinting and will start >> dictating. If I swap the serial ports in the BIOS then surely >> my hints will be wrong and ACPI will be right. > > Not necessarily. It has been a long standing problem that ACPI is > wrong > (or sub-optimal) about serial ports. There are many machines that > list > 0x2f8 first, and 0x3f8 second. As a result, we bind sio0 to com2, and > sio1 to com1. I don't think it's wrong. It's just non-legacy. The whiole purpose of ACPI is to migrate away from those legacy resource allocations and allow for greater flexibility. It seems to me that instead of embracing the freedom for BIOS/firmware writers, we hold on to those old and obsolete notions. As such, it's not a step forwards, it's a step back. > I like the way John did it. It reserves the unit numbers for hardware > that matches the hints. This is not a bad thing, but the ambiguity introduced by re-using hints for that is bad and a recipe for problems. -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 07:57: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 1F6A716A418; Fri, 12 Oct 2007 07:57:45 +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 BE51B13C447; Fri, 12 Oct 2007 07:57:44 +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 l9C7vidH008137; Fri, 12 Oct 2007 03:57:44 -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 l9C7vhRw047486; Fri, 12 Oct 2007 03:57:43 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 0D52073039; Fri, 12 Oct 2007 03:55:58 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20071012075559.0D52073039@freebsd-current.sentex.ca> Date: Fri, 12 Oct 2007 03:55:58 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 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: Fri, 12 Oct 2007 07:57:45 -0000 TB --- 2007-10-12 05:50:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-10-12 05:50:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2007-10-12 05:50:00 - cleaning the object tree TB --- 2007-10-12 05:50:40 - checking out the source tree TB --- 2007-10-12 05:50:40 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2007-10-12 05:50:40 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-10-12 06:01:57 - building world (CFLAGS=-O2 -pipe) TB --- 2007-10-12 06:01:57 - cd /src TB --- 2007-10-12 06:01:57 - /usr/bin/make -B buildworld >>> World build started on Fri Oct 12 06:01:59 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 Fri Oct 12 07:49:10 UTC 2007 TB --- 2007-10-12 07:49:10 - generating LINT kernel config TB --- 2007-10-12 07:49:10 - cd /src/sys/amd64/conf TB --- 2007-10-12 07:49:10 - /usr/bin/make -B LINT TB --- 2007-10-12 07:49:11 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-10-12 07:49:11 - cd /src TB --- 2007-10-12 07:49:11 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Oct 12 07:49:11 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/dev/ips/ips_commands.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/dev/ips/ips_disk.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/dev/ips/ips_ioctl.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/dev/ips/ips_pci.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/dev/ipw/if_ipw.c cc1: warnings being treated as errors /src/sys/dev/ipw/if_ipw.c: In function 'ipw_tx_start': /src/sys/dev/ipw/if_ipw.c:1647: warning: format '%d' expects type 'int', but argument 3 has type 'bus_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-10-12 07:55:58 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-10-12 07:55:58 - ERROR: failed to build lint kernel TB --- 2007-10-12 07:55:58 - tinderbox aborted TB --- 0.91 user 3.72 system 7558.33 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 09:44: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 22C3416A418 for ; Fri, 12 Oct 2007 09:44:35 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (conducive.org [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id D190113C442 for ; Fri, 12 Oct 2007 09:44:34 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:64089 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1IgH4L-0002Uz-1V for freebsd-current@freebsd.org; Fri, 12 Oct 2007 09:44:33 +0000 Message-ID: <470F4200.1080603@conducive.net> Date: Fri, 12 Oct 2007 05:44:32 -0400 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: RELENG-7 i386 Kernel Build Failure? 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, 12 Oct 2007 09:44:35 -0000 I may simply need to do a housecleaning and start fresh, but: i386 After csup to RELENG-7 from 7-CURRENT, using: host=cvsup.dk.freebsd.org make buildworld ran with nary a hitch. Optioned a copy of GENERIC for no 486, SCHED-ULE, saved as WBH make buildkernel barfed on /usr/src/modules/zlib Emptied ~/zfs *and* ~/zlib Next try: barfed on /usr/src/sys/modules/xl no 'README to 'make' Emptied that. Knee-jerk reaction, as there IS a KERNCONF option for xl. See below... Next try: ============= BSD/support -I/usr/src/sys/modules/xfs/../../gnu/fs/xfs -c /usr/src/sys/modules/xfs/../../gnu/fs/xfs/FreeBSD/xfs_fs_subr.c ld -d -warn-common -r -d -o xfs.kld xfs_alloc.o xfs_alloc_btree.o xfs_bit.o xfs_bmap.o xfs_bmap_btree.o xfs_btree.o xfs_buf_item.o xfs_da_btree.o xfs_dir.o xfs_dir2.o xfs_dir2_block.o xfs_dir2_data.o xfs_dir2_leaf.o xfs_dir2_node.o xfs_dir2_sf.o xfs_dir2_trace.o xfs_dir_leaf.o xfs_error.o xfs_extfree_item.o xfs_freebsd_iget.o xfs_fsops.o xfs_ialloc.o xfs_ialloc_btree.o xfs_inode.o xfs_inode_item.o xfs_iocore.o xfs_itable.o xfs_dfrag.o xfs_log.o xfs_log_recover.o xfs_mount.o xfs_rename.o xfs_trans.o xfs_trans_ail.o xfs_trans_buf.o xfs_trans_extfree.o xfs_trans_inode.o xfs_trans_item.o xfs_utils.o xfs_vfsops.o xfs_vnodeops.o xfs_rw.o xfs_iget.o xfs_attr_leaf.o xfs_attr.o xfsrtstubs.o xfsquotasstubs.o xfsdmapistubs.o xfs_dmops.o xfs_qmops.o xfs_mountops.o xfs_vnops.o xfs_frw.o xfs_iomap.o xfs_buf.o xfs_globals.o xfs_dmistubs.o xfs_behavior.o xfs_super.o xfs_stats.o xfs_sysctl.o xfs_vfs.o xfs_vnode.o xfs_fs_subr.o xfs_ioctl.o debug.o ktrace.o mrlock.o uuid.o kmem.o kdb.o :> export_syms awk -f /usr/src/sys/modules/xfs/../../conf/kmod_syms.awk xfs.kld export_syms | xargs -J% objcopy % xfs.kld ld -Bshareable -d -warn-common -o xfs.ko xfs.kld objcopy --strip-debug xfs.ko ===> xl (all) make: don't know how to make bsd.README. Stop *** Error code 2 1 error *** Error code 2 2 errors *** Error code 2 1 error *** Error code 2 1 error 746.318u 74.049s 6:57.90 196.3% 6040+1047k 563+1400io 3pf+0w ============== commented-out 'option xl' (no 3Com NIC's here anyway) Next run: Still barfed in /usr/src/sys/modules/xfs .. trying to speak to 'xl' Emptied that ~/xfs Next Run: barfed in /usr/src/sys/modules/xe '...don't know how to make bsd.README. stop' We've seen that one before.. Despite my crude BFBI approach, something is just not right. Building on a running 7-CURRENT from October iso snapshot. Will wipe the dirtree and pull fresh sources from a different mirror. Bill Hacker From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 10:03: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 3ADA316A4B3 for ; Fri, 12 Oct 2007 10:03:46 +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 2AC3413C4B5 for ; Fri, 12 Oct 2007 10:03:43 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 72471 invoked from network); 12 Oct 2007 14:03:41 +0400 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 12 Oct 2007 14:03:41 +0400 X-AntiVirus: Checked by Dr.Web [version: 4.44, engine: 4.44.0.09170, virus records: 248520, updated: 12.10.2007] Message-ID: <025701c80cb7$2aa209b0$0c00a8c0@Artem> From: "Artem Kuchin" To: "Steve Kargl" , "FreeBSD Current" References: <20071012032516.GA2964@parts-unknown.org> <20071012040534.GA29064@troutmask.apl.washington.edu> Date: Fri, 12 Oct 2007 14:03:35 +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.3198 Cc: Subject: Re: Version 8.0?!!??? 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, 12 Oct 2007 10:03:46 -0000 Steve Kargl wrote: > On Thu, Oct 11, 2007 at 08:25:16PM -0700, David Benfell wrote: >> >> So I was in for a bit of a surprise when I just booted up the >> a version of CURRENT built today: >> >> FreeBSD earth.cybernude.org 8.0-CURRENT FreeBSD 8.0-CURRENT #56: Thu >> Oct 11 10:27:17 PDT 2007 >> root@earth.cybernude.org:/usr/obj/usr/src/sys/EARTH i386 >> >> [snicker] >> >> No real harm, right? >> > > Apparently, you don't read the freebsd-current and cvs-src > mailing list. See the archives from today. Weird! I read current every 4 hours (except night) and did not see anything about this. Only head up for em driver. I do not read cvs-src though. -- Regards, Artem Kuchin From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 10:31: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 569D816A46D; Fri, 12 Oct 2007 10:31:39 +0000 (UTC) (envelope-from erik@cederstrand.dk) Received: from mail.itu.dk (pluto.itu.dk [130.226.142.18]) by mx1.freebsd.org (Postfix) with ESMTP id 021EB13C4A3; Fri, 12 Oct 2007 10:31:38 +0000 (UTC) (envelope-from erik@cederstrand.dk) Received: from localhost (unknown [10.0.0.3]) by mail.itu.dk (Postfix) with ESMTP id E5C0F36F285; Fri, 12 Oct 2007 12:17:02 +0200 (CEST) X-Virus-Scanned: amavisd-new at itu.dk Received: from superman.itu.dk ([130.226.142.5]) by localhost (daredevil.itu.dk [130.226.142.26]) (amavisd-new, port 10024) with ESMTP id WZz+rAegE0ze; Fri, 12 Oct 2007 12:16:46 +0200 (CEST) Received: from [192.168.1.149] (stud1-15.itu.dk [130.226.140.15]) by superman.itu.dk (Postfix) with ESMTP id 6BE869E67F; Fri, 12 Oct 2007 12:16:41 +0200 (CEST) Message-ID: <470F4989.50301@cederstrand.dk> Date: Fri, 12 Oct 2007 12:16:41 +0200 From: Erik Cederstrand User-Agent: Thunderbird 2.0.0.6 (X11/20071008) MIME-Version: 1.0 To: Brooks Davis References: <470E8583.5060209@cederstrand.dk> <20071011230445.GA9272@lor.one-eyed-alien.net> In-Reply-To: <20071011230445.GA9272@lor.one-eyed-alien.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: acpi.ko not being built? 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, 12 Oct 2007 10:31:39 -0000 Brooks Davis wrote: > On Thu, Oct 11, 2007 at 10:20:19PM +0200, Erik Cederstrand wrote: >> Hi! >> >> I'm attempting to upgrade a server to amd64 CURRENT from an older >> snapshot. I have "MODULES_OVERRIDE= acpi" in make.conf but >> apparently only the acpi_*.ko files are being built, not acpi.ko >> itself. As a result, acpi.ko is not being loaded on boot. > > On amd64 (and ia64) acpi is compiled in the the kernel rather than > built as a module. I see, thanks. I was actually trying to get powerd running, but it was complaining about missing "freq". It turns out freq is a sysctl provided by cpufreq and has nothing to do with acpi. So I guess I was asking the wrong question. Anyway, the answers here got me further, but after playing around I now have "powernow0 attach returned 6" in my dmesg, and no dev.cpu.*.freq sysctl's. This looks a lot like PR i386/106850. I can provide any info necessary if anyone wants to look into this. Erik From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 11:55:37 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 4D03516A473 for ; Fri, 12 Oct 2007 11:55:37 +0000 (UTC) (envelope-from prvs=0805a381f1=rermilov@team.vega.ru) Received: from mail.vega.ru (mx1.vega.ru [87.242.77.163]) by mx1.freebsd.org (Postfix) with ESMTP id D645113C45D for ; Fri, 12 Oct 2007 11:55:36 +0000 (UTC) (envelope-from prvs=0805a381f1=rermilov@team.vega.ru) Received: from [87.242.97.68] (port=50771 helo=edoofus.dev.vega.ru) by mail.vega.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IgG8I-000M6X-SL; Fri, 12 Oct 2007 08:44:34 +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 l9C8hnQr059059; Fri, 12 Oct 2007 12:43:49 +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 l9C8hm0T059058; Fri, 12 Oct 2007 12:43:48 +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: Fri, 12 Oct 2007 12:43:48 +0400 From: Ruslan Ermilov To: Dmitry Morozovsky Message-ID: <20071012084347.GA58315@team.vega.ru> References: <20071011224937.D97516@woozle.rinet.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071011224937.D97516@woozle.rinet.ru> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: current@freebsd.org Subject: Re: INSTKERNNAME= foolproof check 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, 12 Oct 2007 11:55:37 -0000 On Thu, Oct 11, 2007 at 10:53:12PM +0400, Dmitry Morozovsky wrote: > Colleagues, > > Today I successfully shoot myself in the foot by typing > > make installkernel KERNCONF=GENERIC INSTKERNNAME= > > instead of usual > > make installkernel KERNCONF=GENERIC INSTKERNNAME=GENERIC > > Empty INSTKERNNAME leads to wiping /boot completely - rather annoying, > especially in my case, where I had some non-trivial (and, of course, no backups > ;-) loader.conf > > What do you think about the following patch? > > Index: Makefile.inc1 > =================================================================== > RCS file: /home/ncvs/src/Makefile.inc1,v > retrieving revision 1.588.2.1 > diff -u -r1.588.2.1 Makefile.inc1 > --- Makefile.inc1 11 Oct 2007 06:08:51 -0000 1.588.2.1 > +++ Makefile.inc1 11 Oct 2007 18:49:19 -0000 > @@ -742,6 +742,10 @@ > @echo "ERROR: No kernel \"${KERNCONF}\" to install."; \ > false > .endif > +.if empty(INSTKERNNAME) > + @echo "ERROR: Kernel install directory is empty."; \ > + false > +.endif > @echo "--------------------------------------------------------------" > @echo ">>> Installing kernel" > @echo "--------------------------------------------------------------" > There's a better place to fix this, so a classical config/make method is fixed as well. Though, this is only one of the many possibilities to shoot yourself in the foot. %%% Index: kern.pre.mk =================================================================== RCS file: /home/ncvs/src/sys/conf/kern.pre.mk,v retrieving revision 1.92 diff -u -p -r1.92 kern.pre.mk --- kern.pre.mk 8 Aug 2007 19:12:06 -0000 1.92 +++ kern.pre.mk 12 Oct 2007 08:41:23 -0000 @@ -10,7 +10,9 @@ SRCCONF?= /etc/src.conf # Can be overridden by makeoptions or /etc/make.conf KERNEL_KO?= kernel -KERNEL?= kernel +.if !defined(KERNEL) || empty(KERNEL) +KERNEL= kernel +.endif KODIR?= /boot/${KERNEL} M= ${MACHINE_ARCH} %%% Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 12:15: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 27AA416A417 for ; Fri, 12 Oct 2007 12:15:46 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id 82A3913C458 for ; Fri, 12 Oct 2007 12:15:45 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from ap-h.matik.com.br (ap-h.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id l9CCFi8x095250 for ; Fri, 12 Oct 2007 09:15:44 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: FreeBSD Current Date: Fri, 12 Oct 2007 09:13:47 -0300 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200710120913.47380.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on msrv.matik.com.br X-Virus-Status: Clean Subject: what is this: SdMaP0? 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, 12 Oct 2007 12:15:46 -0000 somebody has a translation for this in my dmesg of amd64? SdMaP0:: AP1 6C0P.U0 0#0M1B /Lsa utnrcahnesdf!e thank's =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 12:20: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 7659816A41A for ; Fri, 12 Oct 2007 12:20: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 58B2D13C47E for ; Fri, 12 Oct 2007 12:20:49 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 4D0661CC037; Fri, 12 Oct 2007 05:20:49 -0700 (PDT) Date: Fri, 12 Oct 2007 05:20:49 -0700 From: Jeremy Chadwick To: JoaoBR Message-ID: <20071012122049.GA96557@eos.sc1.parodius.com> Mail-Followup-To: JoaoBR , FreeBSD Current References: <200710120913.47380.joao@matik.com.br> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200710120913.47380.joao@matik.com.br> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: FreeBSD Current Subject: Re: what is this: SdMaP0? 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, 12 Oct 2007 12:20:49 -0000 On Fri, Oct 12, 2007 at 09:13:47AM -0300, JoaoBR wrote: > somebody has a translation for this in my dmesg of amd64? > SdMaP0:: AP1 6C0P.U0 0#0M1B /Lsa utnrcahnesdf!e Here's the translation, and look closely: SMP: AP CPU #1 Launched! da0: 160.000MB/s transfe And yes, I have seen this before on amd64. My guess is that it's two things in the kernel trying to output to the console buffer at the exact same time, and there's no mutex lock being done. -- | 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 Oct 12 12:25: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 8978F16A41A for ; Fri, 12 Oct 2007 12:25:31 +0000 (UTC) (envelope-from prvs=0805a381f1=rermilov@team.vega.ru) Received: from mail.vega.ru (mx1.vega.ru [87.242.77.163]) by mx1.freebsd.org (Postfix) with ESMTP id 2550913C461 for ; Fri, 12 Oct 2007 12:25:30 +0000 (UTC) (envelope-from prvs=0805a381f1=rermilov@team.vega.ru) Received: from [87.242.97.68] (port=50732 helo=edoofus.dev.vega.ru) by mail.vega.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IgJ6Z-0002BI-Jr; Fri, 12 Oct 2007 11:54:59 +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 l9CBsOo2095468; Fri, 12 Oct 2007 15:54:24 +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 l9CBsOS1095467; Fri, 12 Oct 2007 15:54:24 +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: Fri, 12 Oct 2007 15:54:24 +0400 From: Ruslan Ermilov To: freebsd-current@freebsd.org, Erik Cederstrand Message-ID: <20071012115424.GB95338@team.vega.ru> References: <470E8583.5060209@cederstrand.dk> <470EAF96.5050106@samsco.org> <20071012010208.GB9272@lor.one-eyed-alien.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071012010208.GB9272@lor.one-eyed-alien.net> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Subject: Re: acpi.ko not being built? 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, 12 Oct 2007 12:25:31 -0000 On Thu, Oct 11, 2007 at 08:02:08PM -0500, Brooks Davis wrote: > On Thu, Oct 11, 2007 at 05:19:50PM -0600, Scott Long wrote: > > Erik Cederstrand wrote: > > > Hi! > > > I'm attempting to upgrade a server to amd64 CURRENT from an older snapshot. > > > I have "MODULES_OVERRIDE= acpi" in make.conf but apparently only the > > > acpi_*.ko files are being built, not acpi.ko itself. As a result, acpi.ko > > > is not being loaded on boot. > > > This used to work on 6.2, so I'm not sure where to look. This happens on a > > > GENERIC kernel config. My src.conf has the following: > > > > Since ACPI is mandatory on amd64, it's included in GENERIC. Not sure why it > > wouldn't be building as a module for you, but if you're using an > > unmodified GENERIC then you're already getting it included. > > When I looked earlier today it looks like the sys/modules/acpi Makefiles > would just refuse if you tried. > This is a (makefile-)documented bug: .if ${MACHINE_ARCH} == "amd64" _aac= aac #_acpi= acpi # doesn't work on amd64 yet # acpi is not enabled because it is broken as a module on ia64 Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 12:29: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 E9E6D16A418 for ; Fri, 12 Oct 2007 12:29:55 +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 868E313C447 for ; Fri, 12 Oct 2007 12:29:55 +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 1IgJeM-00078r-9h for freebsd-current@freebsd.org; Fri, 12 Oct 2007 15:29:54 +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 1IgJeK-000OWZ-CB for freebsd-current@freebsd.org; Fri, 12 Oct 2007 15:29:53 +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 l9CCTntx079326; Fri, 12 Oct 2007 15:29:49 +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 l9CCTmgs079283; Fri, 12 Oct 2007 15:29:48 +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, 12 Oct 2007 15:29:48 +0300 From: Kostik Belousov To: JoaoBR , FreeBSD Current Message-ID: <20071012122948.GM2180@deviant.kiev.zoral.com.ua> References: <200710120913.47380.joao@matik.com.br> <20071012122049.GA96557@eos.sc1.parodius.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bO/C3H35Ok2OdENj" Content-Disposition: inline In-Reply-To: <20071012122049.GA96557@eos.sc1.parodius.com> User-Agent: Mutt/1.4.2.3i X-Scanner-Signature: 7b1a4900bea4ee3727a65c989d5962bc X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 1588 [Oct 12 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: Subject: Re: what is this: SdMaP0? 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, 12 Oct 2007 12:29:56 -0000 --bO/C3H35Ok2OdENj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 12, 2007 at 05:20:49AM -0700, Jeremy Chadwick wrote: > On Fri, Oct 12, 2007 at 09:13:47AM -0300, JoaoBR wrote: > > somebody has a translation for this in my dmesg of amd64? > > SdMaP0:: AP1 6C0P.U0 0#0M1B /Lsa utnrcahnesdf!e >=20 > Here's the translation, and look closely: >=20 > SMP: AP CPU #1 Launched! > da0: 160.000MB/s transfe >=20 > And yes, I have seen this before on amd64. My guess is that it's two > things in the kernel trying to output to the console buffer at the exact > same time, and there's no mutex lock being done. I think that setting the option PRINTF_BUFR_SIZE 128 could help in this situation. --bO/C3H35Ok2OdENj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHD2i8C3+MBN1Mb4gRAsKVAJ9oKbWzEdnsnkEA47hrat6OSuOHTwCeKtRX L/BWj81cBlC4KXoOuhbkx1E= =KtLJ -----END PGP SIGNATURE----- --bO/C3H35Ok2OdENj-- From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 12:41: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 5BC6D16A419 for ; Fri, 12 Oct 2007 12:41:39 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id 07B8B13C468 for ; Fri, 12 Oct 2007 12:41:36 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from c83-253-31-60.bredband.comhem.se ([83.253.31.60]:52890 helo=falcon.midgard.homeip.net) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1IgJay-00046p-64 for freebsd-current@freebsd.org; Fri, 12 Oct 2007 14:26:25 +0200 Received: (qmail 71345 invoked from network); 12 Oct 2007 14:26:21 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 12 Oct 2007 14:26:21 +0200 Received: (qmail 30630 invoked by uid 1001); 12 Oct 2007 14:26:21 +0200 Date: Fri, 12 Oct 2007 14:26:21 +0200 From: Erik Trulsson To: JoaoBR Message-ID: <20071012122621.GA30592@owl.midgard.homeip.net> Mail-Followup-To: JoaoBR , FreeBSD Current References: <200710120913.47380.joao@matik.com.br> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200710120913.47380.joao@matik.com.br> User-Agent: Mutt/1.5.16 (2007-06-09) X-Originating-IP: 83.253.31.60 X-Scan-Result: No virus found in message 1IgJay-00046p-64. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1IgJay-00046p-64 143dcdf0e89b1fd62ffc54a65bf1d451 Cc: FreeBSD Current Subject: Re: what is this: SdMaP0? 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, 12 Oct 2007 12:41:39 -0000 On Fri, Oct 12, 2007 at 09:13:47AM -0300, JoaoBR wrote: > > > somebody has a translation for this in my dmesg of amd64? > > > SdMaP0:: AP1 6C0P.U0 0#0M1B /Lsa utnrcahnesdf!e It is two different outputs that have become mixed together. One saying SMP: AP CPU #1 Launched! and another saying da0: 160.000MB/s transfe (That last word should actually be 'transfers'. I don't know what happened to the final 'rs') -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 12:44: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 7DE1916A683 for ; Fri, 12 Oct 2007 12:44:33 +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 5F33113C491 for ; Fri, 12 Oct 2007 12:44:33 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 40B5B1CC037; Fri, 12 Oct 2007 05:44:33 -0700 (PDT) Date: Fri, 12 Oct 2007 05:44:33 -0700 From: Jeremy Chadwick To: JoaoBR , FreeBSD Current Message-ID: <20071012124433.GA97012@eos.sc1.parodius.com> Mail-Followup-To: JoaoBR , FreeBSD Current References: <200710120913.47380.joao@matik.com.br> <20071012122621.GA30592@owl.midgard.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071012122621.GA30592@owl.midgard.homeip.net> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Subject: Re: what is this: SdMaP0? 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, 12 Oct 2007 12:44:33 -0000 On Fri, Oct 12, 2007 at 02:26:21PM +0200, Erik Trulsson wrote: > It is two different outputs that have become mixed together. > > One saying > > SMP: AP CPU #1 Launched! > > and another saying > > da0: 160.000MB/s transfe > > (That last word should actually be 'transfers'. I don't know what happened > to the final 'rs') They very likely got put on the next line of the dmesg output, since one string would contain a newline. So the line after that would probably be something like "rs". -- | 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 Oct 12 13:10: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 C204B16A419 for ; Fri, 12 Oct 2007 13:10:20 +0000 (UTC) (envelope-from timur@com.bat.ru) Received: from mail.bat.ru (dzokonda.xs4all.nl [194.109.164.75]) by mx1.freebsd.org (Postfix) with ESMTP id 19A0913C49D for ; Fri, 12 Oct 2007 13:10:19 +0000 (UTC) (envelope-from timur@com.bat.ru) Received: from timur.home.bat.ru ([192.168.0.4] verified) by mail.bat.ru (CommuniGate Pro SMTP 4.2.7) with ESMTP-TLS id 661966; Fri, 12 Oct 2007 15:13:00 +0200 Received: (from timur@localhost) by timur.home.bat.ru (8.14.1/8.14.1/Submit) id l9CDAFZg062750; Fri, 12 Oct 2007 15:10:15 +0200 (CEST) (envelope-from timur) Date: Fri, 12 Oct 2007 15:10:15 +0200 From: "Timur I. Bakeyev" To: Michael Bushkov Message-ID: <20071012131015.GB62649@com.bat.ru> References: <20070716190258.GA25030@hansmi.ch> <20071008140113.GG98428@com.bat.ru> <470C79C3.4010603@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <470C79C3.4010603@freebsd.org> User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: tobias.mueller@hostpoint.ch, Michael Hanselmann , elias.wittwer@hostpoint.ch, freebsd-current@freebsd.org, m.kooijman@student.utwente.nl Subject: Re: [PATCH] Implement getgroupmembership(3) for massive performance gain when using LDAP or Winbind 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, 12 Oct 2007 13:10:20 -0000 Hi, Michael and Michael! On Wed, Oct 10, 2007 at 11:05:39AM +0400, Michael Bushkov wrote: > Hi Timur, > I'm in the process of reviewing this patch. If it's ok I'll commit it after the > HEAD is unfrozen. Thank you both for your work on this subject and for pushing it forward into the main repository tree. Matthijs - as soon as it'll be clear that this API will present in FreeBSD at some point I try push getgroupmembership patches for the Samba's winbind module. With best regards, Timur Bakeyev. From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 13:23: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 DE1E316A41A for ; Fri, 12 Oct 2007 13:23:05 +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 7A3F813C4A3 for ; Fri, 12 Oct 2007 13:23:05 +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 1IgKTo-000FGs-O4; Fri, 12 Oct 2007 16:23:04 +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 1IgKTn-0003j1-3N; Fri, 12 Oct 2007 16:23:04 +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 l9CDN0pW006969; Fri, 12 Oct 2007 16:23:00 +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 l9CDMxOe006965; Fri, 12 Oct 2007 16:22:59 +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, 12 Oct 2007 16:22:59 +0300 From: Kostik Belousov To: Sergey Matveychuk Message-ID: <20071012132259.GN2180@deviant.kiev.zoral.com.ua> References: <200710120913.47380.joao@matik.com.br> <20071012122049.GA96557@eos.sc1.parodius.com> <20071012122948.GM2180@deviant.kiev.zoral.com.ua> <470F7082.3050200@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kkj3vgNzAWGjboLC" Content-Disposition: inline In-Reply-To: <470F7082.3050200@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-Scanner-Signature: 4fe2b897d4d72954524b6b73d18f8617 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 1588 [Oct 12 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 , JoaoBR Subject: Re: what is this: SdMaP0? 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, 12 Oct 2007 13:23:06 -0000 --kkj3vgNzAWGjboLC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 12, 2007 at 05:02:58PM +0400, Sergey Matveychuk wrote: > Kostik Belousov wrote: > >On Fri, Oct 12, 2007 at 05:20:49AM -0700, Jeremy Chadwick wrote: > >>On Fri, Oct 12, 2007 at 09:13:47AM -0300, JoaoBR wrote: > >>>somebody has a translation for this in my dmesg of amd64? > >>>SdMaP0:: AP1 6C0P.U0 0#0M1B /Lsa utnrcahnesdf!e > >>Here's the translation, and look closely: > >> > >>SMP: AP CPU #1 Launched! > >>da0: 160.000MB/s transfe > >> > >>And yes, I have seen this before on amd64. My guess is that it's two > >>things in the kernel trying to output to the console buffer at the exact > >>same time, and there's no mutex lock being done. > > > >I think that setting the option PRINTF_BUFR_SIZE 128 could help in this > >situation. >=20 > BTW, note my kern/116310. It fixes relate issue for log() function. But= =20 > I did not touch kernel's printf(). Our logs have no junk now. I answered you somewhere already, AFAIR. I think that the patch is wrong. You cannot use the default mutex in printf(), since it is called from the arbitrary thread contexts. Also, you could get the loss of the information on the panic. PRINTF_BUFR_SIZE seems to be better solution. --kkj3vgNzAWGjboLC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHD3UzC3+MBN1Mb4gRAk/IAKDKKJdSNSVWrerGmUT806zeOpFQ0ACgnlt9 cNm9/pFHFGkQ3aIzaQa/gDg= =xWyM -----END PGP SIGNATURE----- --kkj3vgNzAWGjboLC-- From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 13:39: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 E660A16A420 for ; Fri, 12 Oct 2007 13:39:41 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from mail.ciam.ru (ns.ciam.ru [213.247.195.75]) by mx1.freebsd.org (Postfix) with ESMTP id 9487B13C46A for ; Fri, 12 Oct 2007 13:39:41 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from dhcp250-210.yandex.ru ([87.250.250.210]) by mail.ciam.ru with esmtpa (Exim 4.x) id 1IgKBv-000Avl-5W; Fri, 12 Oct 2007 17:04:35 +0400 Message-ID: <470F7082.3050200@FreeBSD.org> Date: Fri, 12 Oct 2007 17:02:58 +0400 From: Sergey Matveychuk User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Kostik Belousov References: <200710120913.47380.joao@matik.com.br> <20071012122049.GA96557@eos.sc1.parodius.com> <20071012122948.GM2180@deviant.kiev.zoral.com.ua> In-Reply-To: <20071012122948.GM2180@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , JoaoBR Subject: Re: what is this: SdMaP0? 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, 12 Oct 2007 13:39:42 -0000 Kostik Belousov wrote: > On Fri, Oct 12, 2007 at 05:20:49AM -0700, Jeremy Chadwick wrote: >> On Fri, Oct 12, 2007 at 09:13:47AM -0300, JoaoBR wrote: >>> somebody has a translation for this in my dmesg of amd64? >>> SdMaP0:: AP1 6C0P.U0 0#0M1B /Lsa utnrcahnesdf!e >> Here's the translation, and look closely: >> >> SMP: AP CPU #1 Launched! >> da0: 160.000MB/s transfe >> >> And yes, I have seen this before on amd64. My guess is that it's two >> things in the kernel trying to output to the console buffer at the exact >> same time, and there's no mutex lock being done. > > I think that setting the option PRINTF_BUFR_SIZE 128 could help in this > situation. BTW, note my kern/116310. It fixes relate issue for log() function. But I did not touch kernel's printf(). Our logs have no junk now. -- Dixi. Sem. From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 14:38: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 093C516A418; Fri, 12 Oct 2007 14:38:04 +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 BC11113C45B; Fri, 12 Oct 2007 14:38:03 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.1/8.14.1) id l9CEc1Xb008572; Fri, 12 Oct 2007 09:38:01 -0500 (CDT) (envelope-from dan) Date: Fri, 12 Oct 2007 09:38:00 -0500 From: Dan Nelson To: John Baldwin Message-ID: <20071012143800.GA76105@dan.emsphone.com> References: <20070912172752.GA13960@dan.emsphone.com> <200710101615.48760.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200710101615.48760.jhb@freebsd.org> X-OS: FreeBSD 7.0-PRERELEASE User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org, Ivan Voras Subject: Re: Panic in arpresolve->rt_check? 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, 12 Oct 2007 14:38:04 -0000 In the last episode (Oct 10), John Baldwin said: > On Wednesday 12 September 2007 02:50:37 pm Ivan Voras wrote: > > Dan Nelson wrote: > > > The same panic was also reported for 6.2 via PR 107865 and PR > > > 112490. 112490 included a workaround patch (I haven't tried it; > > > just found it). > > > > The proposed patch in kern/112490 looks trivial but someone who > > knows more about net locking should check it out. Unfortunately it > > lacks context and I don't know the code in question to apply it > > safely on a production machine :( > > I also get panics with what appears to be a double free of rt_gwroute > in rtexpunge(), so I think while this PR may help some with figuring > out the problem, I'm not sure it solves the root bug. > > Hmm, possibly try this patch: This makes the panics more frequent on my machine, actually :) > Index: route.c > =================================================================== > RCS file: /usr/cvs/src/sys/net/route.c,v > retrieving revision 1.120 > diff -c -r1.120 route.c > *** route.c 11 Jun 2007 12:19:34 -0000 1.120 > --- route.c 10 Oct 2007 20:12:54 -0000 > *************** > *** 1314,1319 **** > --- 1314,1321 ---- > return (ENETUNREACH); > } > RT_LOCK(rt0); > + if (rt0->rt_gwroute != NULL) > + RTFREE(rt0->rt_gwroute); > rt0->rt_gwroute = rt; > if (rt == NULL) { > RT_UNLOCK(rt0); -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 15: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 746B116A46E; Fri, 12 Oct 2007 15:26:14 +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 A9F9213C47E; Fri, 12 Oct 2007 15:26:10 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <470F9211.8010604@FreeBSD.org> Date: Fri, 12 Oct 2007 17:26:09 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Dan Nelson References: <20070912172752.GA13960@dan.emsphone.com> <200710101615.48760.jhb@freebsd.org> <20071012143800.GA76105@dan.emsphone.com> In-Reply-To: <20071012143800.GA76105@dan.emsphone.com> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Ivan Voras Subject: Re: Panic in arpresolve->rt_check? 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, 12 Oct 2007 15:26:14 -0000 Dan Nelson wrote: > In the last episode (Oct 10), John Baldwin said: >> On Wednesday 12 September 2007 02:50:37 pm Ivan Voras wrote: >>> Dan Nelson wrote: >>>> The same panic was also reported for 6.2 via PR 107865 and PR >>>> 112490. 112490 included a workaround patch (I haven't tried it; >>>> just found it). >>> The proposed patch in kern/112490 looks trivial but someone who >>> knows more about net locking should check it out. Unfortunately it >>> lacks context and I don't know the code in question to apply it >>> safely on a production machine :( >> I also get panics with what appears to be a double free of rt_gwroute >> in rtexpunge(), so I think while this PR may help some with figuring >> out the problem, I'm not sure it solves the root bug. >> >> Hmm, possibly try this patch: > > This makes the panics more frequent on my machine, actually :) > >> Index: route.c >> =================================================================== >> RCS file: /usr/cvs/src/sys/net/route.c,v >> retrieving revision 1.120 >> diff -c -r1.120 route.c >> *** route.c 11 Jun 2007 12:19:34 -0000 1.120 >> --- route.c 10 Oct 2007 20:12:54 -0000 >> *************** >> *** 1314,1319 **** >> --- 1314,1321 ---- >> return (ENETUNREACH); >> } >> RT_LOCK(rt0); >> + if (rt0->rt_gwroute != NULL) >> + RTFREE(rt0->rt_gwroute); >> rt0->rt_gwroute = rt; >> if (rt == NULL) { >> RT_UNLOCK(rt0); > Since you can reproduce this frequently the best thing might be to instrument all the route handling with KTR so that you can do post-mortem and try to figure out where the double-free or missing reference happened. Kris From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 16:53: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 3DE9116A41A for ; Fri, 12 Oct 2007 16:53:34 +0000 (UTC) (envelope-from freebsd-questions@stellablue.org) Received: from mail5.neteze.com (mail5.neteze.com [209.160.67.25]) by mx1.freebsd.org (Postfix) with ESMTP id 1DAC113C468 for ; Fri, 12 Oct 2007 16:53:33 +0000 (UTC) (envelope-from freebsd-questions@stellablue.org) Received: from 66-169-93-064.dhcp.ahvl.nc.charter.com ([66.169.93.64] helo=[127.0.0.1]) by mail5.neteze.com with esmtpa (Exim 4.63) (envelope-from ) id 1IgNlU-00040l-Nr for freebsd-current@freebsd.org; Fri, 12 Oct 2007 16:53:32 +0000 Message-ID: <470FA675.1010409@stellablue.org> Date: Fri, 12 Oct 2007 12:53:09 -0400 From: Steve Brown User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: FreeBSD Current References: <200710120913.47380.joao@matik.com.br> In-Reply-To: <200710120913.47380.joao@matik.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 000780-2, 10/11/2007), Outbound message X-Antivirus-Status: Clean Subject: Re: what is this: SdMaP0? 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, 12 Oct 2007 16:53:34 -0000 JoaoBR wrote: > somebody has a translation for this in my dmesg of amd64? > > > SdMaP0:: AP1 6C0P.U0 0#0M1B /Lsa utnrcahnesdf!e > > thank's > Probably the same thing I see in my firewall logs all the time - slightly obfuscated: Oct 12 00:00:03 x-xxx-x kernel: ipfw: 65i0p0f0w: Deny UD6P5 010608 .D9e5n.y1 92U.D9P4 :156089.9935 .7129.22.5904.:254019.9537 : 7523. 2i5n0 .v2i4a1 .b5g7e:05 Oct 12 00:00:24 xx-xx-x kernel: ipfw: 65000 Deny UDP 217.212.224.159:32768 7i8.pf2w5:0 .24.57:5635 0i0n0 vDiean yb geU1D Oct 11 23:46:48 x-xx-x kernel: ipfw: 505 Deny TCP 65.55.235.159:6704i p7fw: .2550.52 4D1e.n5y9 :8T0C Pi n6 5v.i5a5 .2b3g5e.01 Looks like two different logs combining into one. 6.2-RELEASE, SMP kernel, quad core Steve From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 16: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 306C716A417 for ; Fri, 12 Oct 2007 16:56:58 +0000 (UTC) (envelope-from freebsd-questions@stellablue.org) Received: from mail5.neteze.com (mail5.neteze.com [209.160.67.25]) by mx1.freebsd.org (Postfix) with ESMTP id 115EE13C481 for ; Fri, 12 Oct 2007 16:56:58 +0000 (UTC) (envelope-from freebsd-questions@stellablue.org) Received: from 66-169-93-064.dhcp.ahvl.nc.charter.com ([66.169.93.64] helo=[127.0.0.1]) by mail5.neteze.com with esmtpa (Exim 4.63) (envelope-from ) id 1IgNon-0004PC-34; Fri, 12 Oct 2007 16:56:57 +0000 Message-ID: <470FA741.2090906@stellablue.org> Date: Fri, 12 Oct 2007 12:56:33 -0400 From: Steve Brown User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Steve Brown References: <200710120913.47380.joao@matik.com.br> <470FA675.1010409@stellablue.org> In-Reply-To: <470FA675.1010409@stellablue.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 000780-2, 10/11/2007), Outbound message X-Antivirus-Status: Clean Cc: FreeBSD Current Subject: Re: what is this: SdMaP0? 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, 12 Oct 2007 16:56:58 -0000 Steve Brown wrote: > Probably the same thing I see in my firewall logs all the time - > slightly obfuscated: > > Oct 12 00:00:03 x-xxx-x kernel: ipfw: 65i0p0f0w: Deny UD6P5 010608 > .D9e5n.y1 92U.D9P4 :156089.9935 .7129.22.5904.:254019.9537 : > 7523. 2i5n0 .v2i4a1 .b5g7e:05 > Oct 12 00:00:24 xx-xx-x kernel: ipfw: 65000 Deny UDP > 217.212.224.159:32768 7i8.pf2w5:0 .24.57:5635 0i0n0 vDiean yb geU1D > Oct 11 23:46:48 x-xx-x kernel: ipfw: 505 Deny TCP 65.55.235.159:6704i > p7fw: .2550.52 4D1e.n5y9 :8T0C Pi n6 5v.i5a5 .2b3g5e.01 > > Looks like two different logs combining into one. > > 6.2-RELEASE, SMP kernel, quad core > > Steve Note, this is i386 build, not amd64 ... so it seems to apply across architectures. Steve From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 18:14: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 2C9F416A421 for ; Fri, 12 Oct 2007 18:14:01 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay04.ispgateway.de (smtprelay04.ispgateway.de [80.67.18.16]) by mx1.freebsd.org (Postfix) with ESMTP id 91A9513C465 for ; Fri, 12 Oct 2007 18:14:00 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 17482 invoked from network); 12 Oct 2007 18:13:58 -0000 Received: from unknown (HELO localhost) (775067@[217.50.167.37]) (envelope-sender ) by smtprelay04.ispgateway.de (qmail-ldap-1.03) with SMTP; 12 Oct 2007 18:13:58 -0000 Date: Fri, 12 Oct 2007 20:13:52 +0200 From: Fabian Keil To: Pawel Jakub Dawidek Message-ID: <20071012201352.71f79aca@fabiankeil.de> In-Reply-To: <20071011173846.GB52831@garage.freebsd.pl> References: <20071011190517.770fd3ab@fabiankeil.de> <20071011173846.GB52831@garage.freebsd.pl> X-Mailer: Claws Mail 3.0.2 (GTK+ 2.10.14; i386-portbld-freebsd7.0) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2008-08-18.asc Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/R9BWCdB5WUJzppsVLyvFL13"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-current@FreeBSD.org Subject: Re: zpool scrub causes geli vdev to detach 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, 12 Oct 2007 18:14:01 -0000 --Sig_/R9BWCdB5WUJzppsVLyvFL13 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Pawel Jakub Dawidek wrote: > On Thu, Oct 11, 2007 at 07:05:17PM +0200, Fabian Keil wrote: > > this zpool: > >=20 > > fk@TP51 ~ $sudo zpool status > > pool: tank > > state: ONLINE > > scrub: scrub completed with 0 errors on Thu Oct 11 13:56:28 2007 > > config: > >=20 > > NAME STATE READ WRITE CKSUM > > tank ONLINE 0 0 0 > > ad0s3f.eli ONLINE 0 0 0 > > ad0s2.eli ONLINE 0 0 0 > >=20 > > errors: No known data errors > >=20 > > worked without issues when it only consisted of ad0s3f.eli, > > but then I added ad0s2.eli and now scrubbing the pool leads to: > >=20 > > Unread portion of the kernel message buffer: > > GEOM_ELI: Detached ad0s2.eli on last close. > > GEOM_LABEL: Label for provider ad0s2 is msdosfs/?A.?,{(#0. > > panic: Function g_eli_orphan_spoil_assert() called for ad0s3f.eli. > > KDB: enter: panic > > panic: from debugger > > Uptime: 5m27s > > Physical memory: 1014 MB > > Dumping 120 MB: 105 89 73 57 41 25 9 > > Is there an obvious solution, or should I file a PR about this? >=20 > Please file PR, but let me explain. >=20 > GELI's detach-on-last-close mechanism is a general purpose mechanism, it > may not work correctly with ZFS, because ZFS sometimes closes and reopen > providers, which will make GELI to detach. In other words you shouldn't > configure detach-on-last-close for ZFS components. It shouldn't panic > still. Thanks for the quick response, Pawel. I'll file the PR tomorrow. Before coming up with the "workaround" I already spend some time reading geli(8) looking for a disable-detach-on-last-close option, but obviously didn't find it. Turns out I unintentionally configured detach-on-last-close through /etc/defaults/rc.conf. I just added geli_autodetach=3D"NO" to /etc/rc.conf and the problem is indeed gone. Fabian --Sig_/R9BWCdB5WUJzppsVLyvFL13 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHD7lgBYqIVf93VJ0RAhiVAKDHTig0o8qkYqisYA9srxnYedjT0wCdGcWU +llzRgUVSAkPOT+zmf0CXis= =he9o -----END PGP SIGNATURE----- --Sig_/R9BWCdB5WUJzppsVLyvFL13-- From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 19:21:35 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 CD8AA16A418 for ; Fri, 12 Oct 2007 19:21:35 +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 7CF5213C45D for ; Fri, 12 Oct 2007 19:21:34 +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 214169643-1834499 for multiple; Fri, 12 Oct 2007 15:19:36 -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 l9CJLIM6041669; Fri, 12 Oct 2007 15:21:20 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Marcel Moolenaar Date: Fri, 12 Oct 2007 14:09:31 -0400 User-Agent: KMail/1.9.6 References: <200710111741.34992.jhb@FreeBSD.org> <622950DD-BFEF-450C-8B80-BAB55C7B58CB@mac.com> In-Reply-To: <622950DD-BFEF-450C-8B80-BAB55C7B58CB@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710121409.31407.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]); Fri, 12 Oct 2007 15:21:20 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/4533/Fri Oct 12 06:59:29 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: current@freebsd.org Subject: Re: New-bus unit wiring via hints.. 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, 12 Oct 2007 19:21:35 -0000 On Thursday 11 October 2007 05:59:23 pm Marcel Moolenaar wrote: > > On Oct 11, 2007, at 2:41 PM, John Baldwin wrote: > > > 2) One of the things this fixes that is visible to users is that if > > your > > machine gets the COM ports backwards when using ACPI it should > > now get > > them correct (COM1 as sio0) assuming your COM ports use the > > default hints > > and you have the default sio hints in your /boot/device.hints file. > > I think you just pointed out the problem of using hints to wire > down unit numbers, because hints will stop hinting and will start > dictating. If I swap the serial ports in the BIOS then surely > my hints will be wrong and ACPI will be right. A default hints > file will be even more disastrous than before. hints have always dictated. The issue is that hints are enumerating devices that ACPI/PNPBIOS also dictate, so how does one resolve the differences (do you ignore one or the other, or attempt to merge them, etc.). Note that hints can always be removed. FWIW, the resources for COM1 and COM2 are largely fixed in practice on existing x86 hardware which is what this would affect, and hints can always be removed. Given the number of complaints from people where ACPI enumerates COM2 before COM1 (and the fact that ACPI made _UID useless by not giving it a more strict format.. it's optional and on some systems it is 0-based while on others it is 1-based. I've also seen pci link devices where the _UID is the link index from the $PIR table which == the register offset in config space on the PCI-ISA bridge of the controlling register) and the fact that COM1 and COM2 have de-facto fixed resources on x86, I think it's ok for x86 to include default hints for sio0 and sio1. Do you have any comments on the idea in general of allowing busses to use hints (or some other method) to wire devices to unit numbers? Note that some other examples you could do would be to expand ACPI hinting to allow for things like: hint.foo.0.uid="1" (bind to _UID=1) hint.foo.0.name="COMA" (short name) hint.foo.0.name="\_SB_.PCI0.LPC0.COMA" (long name) In fact, I have uid done as a prototype currently and the way I did it was that the _UID matching took precedence over resource matching, but that policy is up to the bus driver. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 19:50: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 1DD0A16A41A; Fri, 12 Oct 2007 19:50:04 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.70]) by mx1.freebsd.org (Postfix) with ESMTP id B2F2313C458; Fri, 12 Oct 2007 19:50:03 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (smtpin05-en2 [10.13.10.150]) by smtpoutm.mac.com (Xserve/smtpout007/MantshX 4.0) with ESMTP id l9CJo31E018087; Fri, 12 Oct 2007 12:50:03 -0700 (PDT) Received: from [172.24.104.105] (natint3.juniper.net [66.129.224.36]) (authenticated bits=0) by mac.com (Xserve/smtpin05/MantshX 4.0) with ESMTP id l9CJnw7s005580 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 12 Oct 2007 12:50:00 -0700 (PDT) In-Reply-To: <200710121409.31407.jhb@freebsd.org> References: <200710111741.34992.jhb@FreeBSD.org> <622950DD-BFEF-450C-8B80-BAB55C7B58CB@mac.com> <200710121409.31407.jhb@freebsd.org> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <7C92FD4D-39DA-4AAE-A0F6-4D856AAD46EE@mac.com> Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Fri, 12 Oct 2007 12:49:28 -0700 To: John Baldwin X-Mailer: Apple Mail (2.752.3) Cc: current@freebsd.org Subject: Re: New-bus unit wiring via hints.. 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, 12 Oct 2007 19:50:04 -0000 On Oct 12, 2007, at 11:09 AM, John Baldwin wrote: > On Thursday 11 October 2007 05:59:23 pm Marcel Moolenaar wrote: >> >> On Oct 11, 2007, at 2:41 PM, John Baldwin wrote: >> >>> 2) One of the things this fixes that is visible to users is that if >>> your >>> machine gets the COM ports backwards when using ACPI it should >>> now get >>> them correct (COM1 as sio0) assuming your COM ports use the >>> default hints >>> and you have the default sio hints in your /boot/device.hints >>> file. >> >> I think you just pointed out the problem of using hints to wire >> down unit numbers, because hints will stop hinting and will start >> dictating. If I swap the serial ports in the BIOS then surely >> my hints will be wrong and ACPI will be right. A default hints >> file will be even more disastrous than before. > > hints have always dictated. The issue is that hints are > enumerating devices > that ACPI/PNPBIOS also dictate, so how does one resolve the > differences (do > you ignore one or the other, or attempt to merge them, etc.). Note > that > hints can always be removed. I think the conflict is resolved by having hints only apply to the isa bus proper and stop tying apci to the isa bus. This also exposes other flaws with hints, such as using flags to mark a device as (potential) console. > FWIW, the resources for COM1 and COM2 are largely fixed in practice on > existing x86 hardware which is what this would affect, and hints > can always > be removed. Given the number of complaints from people where ACPI > enumerates > COM2 before COM1 (and the fact that ACPI made _UID useless by not > giving it a > more strict format.. it's optional and on some systems it is 0- > based while on > others it is 1-based. But aren't the complaints the immediate result of having hints in the first place. Remove the hints and the complaints go away, right? > I've also seen pci link devices where the _UID is the > link index from the $PIR table which == the register offset in > config space > on the PCI-ISA bridge of the controlling register) and the fact > that COM1 and > COM2 have de-facto fixed resources on x86, I think it's ok for x86 > to include > default hints for sio0 and sio1. If the hints would be specific to the ISA bus, then it would definitely be ok to have them. Even though we don't support i386 hardware, it should not be a big deal to keep the support for the ISA bus. We should really stop using acpi as an alias for isa and start treating it as a separate "bus". > Do you have any comments on the idea in general of allowing busses > to use > hints (or some other method) to wire devices to unit numbers? Wiring unit numbers to particular devices is good. Tying them to hints isn't. I would rather see us go in the direction of having the kernel maintain a configuration file. This would allow us to extend the notion wiring down unit numbers to keeping state across reboots. This could be used in the future for various cases, such as: o video/graphics settings o console settings o fast boot or suspend from disk information o user specified labels or aliases for devices/disks o interrupt routing overrides o quirks o etc No matter how we implement the wiring, one major issue is that the information can be out of sync if the hardware configuration is changed. It would be nice to have at least a boot option that tells the kernel to ignore all the wiring information. It would allow one to boot the kernel, correct any conflicts that would otherwise prohibit the kernel from booting normally and restart. Of course, if the wiring is done with hints, that would then also mean that all the hints are ignored, which currently means that drivers that abuse hints won't get started (i.e. syscons). That's another reason to uncouple hints from wiring. We currently can't boot without hints even though all hardware is found without hints -- we misuse hints as it is. Just my $0.02, -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 20:38:20 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 5548316A418 for ; Fri, 12 Oct 2007 20:38:20 +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 1615513C46B for ; Fri, 12 Oct 2007 20:38:19 +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 214179132-1834499 for multiple; Fri, 12 Oct 2007 16:36:22 -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 l9CKc8Ke042183; Fri, 12 Oct 2007 16:38:09 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Marcel Moolenaar Date: Fri, 12 Oct 2007 16:20:59 -0400 User-Agent: KMail/1.9.6 References: <200710111741.34992.jhb@FreeBSD.org> <200710121409.31407.jhb@freebsd.org> <7C92FD4D-39DA-4AAE-A0F6-4D856AAD46EE@mac.com> In-Reply-To: <7C92FD4D-39DA-4AAE-A0F6-4D856AAD46EE@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710121620.59787.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]); Fri, 12 Oct 2007 16:38:09 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/4533/Fri Oct 12 06:59:29 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: current@freebsd.org Subject: Re: New-bus unit wiring via hints.. 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, 12 Oct 2007 20:38:20 -0000 On Friday 12 October 2007 03:49:28 pm Marcel Moolenaar wrote: > > On Oct 12, 2007, at 11:09 AM, John Baldwin wrote: > > > On Thursday 11 October 2007 05:59:23 pm Marcel Moolenaar wrote: > >> > >> On Oct 11, 2007, at 2:41 PM, John Baldwin wrote: > >> > >>> 2) One of the things this fixes that is visible to users is that if > >>> your > >>> machine gets the COM ports backwards when using ACPI it should > >>> now get > >>> them correct (COM1 as sio0) assuming your COM ports use the > >>> default hints > >>> and you have the default sio hints in your /boot/device.hints > >>> file. > >> > >> I think you just pointed out the problem of using hints to wire > >> down unit numbers, because hints will stop hinting and will start > >> dictating. If I swap the serial ports in the BIOS then surely > >> my hints will be wrong and ACPI will be right. A default hints > >> file will be even more disastrous than before. > > > > hints have always dictated. The issue is that hints are > > enumerating devices > > that ACPI/PNPBIOS also dictate, so how does one resolve the > > differences (do > > you ignore one or the other, or attempt to merge them, etc.). Note > > that > > hints can always be removed. > > I think the conflict is resolved by having hints only apply to the isa > bus proper and stop tying apci to the isa bus. This also exposes other > flaws with hints, such as using flags to mark a device as (potential) > console. The issue here is that the 16550 UART that ACPI enumerates is on the LPC bus, that is, it's an ISA device. In this case, ACPI is subsuming the role of the PNPBIOS to enumerate ISA devices. If you want to move all the ACPI-enumerated ISA devices under isa0 (which we can do, similar to how the ACPI pci(4) driver "claims" the ACPI handles for PCI devices in the ACPI namespace) we can do that, but that doesn't solve the problem at all. The problem is, ACPI is not a "bus". It's a hierarchical namespace that spans multiple busses, including PCI, ISA/LPC, etc. We don't probe PCI devices based on them showing up in ACPI's namespace, we probe them based on PCI's normal enumeration process. One of purposes of ACPI is to enumerate devices on busses that are too dumb to provide their own enumeration (e.g. non-PnP devices on ISA). > > FWIW, the resources for COM1 and COM2 are largely fixed in practice on > > existing x86 hardware which is what this would affect, and hints > > can always > > be removed. Given the number of complaints from people where ACPI > > enumerates > > COM2 before COM1 (and the fact that ACPI made _UID useless by not > > giving it a > > more strict format.. it's optional and on some systems it is 0- > > based while on > > others it is 1-based. > > But aren't the complaints the immediate result of having hints in the > first > place. Remove the hints and the complaints go away, right? No. The kernel console switches because it is bound via hints. Besides, people also don't like the cosmetics of having ttyd0 being COM2 and ttyd1 being COM1, etc. > > I've also seen pci link devices where the _UID is the > > link index from the $PIR table which == the register offset in > > config space > > on the PCI-ISA bridge of the controlling register) and the fact > > that COM1 and > > COM2 have de-facto fixed resources on x86, I think it's ok for x86 > > to include > > default hints for sio0 and sio1. > > If the hints would be specific to the ISA bus, then it would > definitely be > ok to have them. Even though we don't support i386 hardware, it > should not > be a big deal to keep the support for the ISA bus. We should really stop > using acpi as an alias for isa and start treating it as a separate > "bus". See above. ACPI != bus. ACPI == namespace that spans multiple busses. This is an important distinction. > > Do you have any comments on the idea in general of allowing busses > > to use > > hints (or some other method) to wire devices to unit numbers? > > Wiring unit numbers to particular devices is good. Tying them to hints > isn't. I would rather see us go in the direction of having the kernel > maintain a configuration file. This would allow us to extend the notion > wiring down unit numbers to keeping state across reboots. This could > be used in the future for various cases, such as: > o video/graphics settings > o console settings > o fast boot or suspend from disk information > o user specified labels or aliases for devices/disks > o interrupt routing overrides > o quirks > o etc > > No matter how we implement the wiring, one major issue is that the > information can be out of sync if the hardware configuration is changed. > It would be nice to have at least a boot option that tells the kernel > to ignore all the wiring information. It would allow one to boot the > kernel, correct any conflicts that would otherwise prohibit the kernel > from booting normally and restart. > Of course, if the wiring is done with hints, that would then also mean > that all the hints are ignored, which currently means that drivers that > abuse hints won't get started (i.e. syscons). That's another reason to > uncouple hints from wiring. We currently can't boot without hints even > though all hardware is found without hints -- we misuse hints as it is. > > Just my $0.02, This would be to go backwards to 4.x which put the "hints" data into the kernel config file meaning you can't change it at boot-time in the loader. If you want the configuration file separate from the kernel, then what do you consider /boot/device.hints to be? -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 21:10:01 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 51D5E16A41A; Fri, 12 Oct 2007 21:10:01 +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 20DA413C44B; Fri, 12 Oct 2007 21:10:00 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.14.1/8.13.8) with ESMTP id l9CL9xcO059989; Fri, 12 Oct 2007 17:09:59 -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 l9CL9xY1063059; Fri, 12 Oct 2007 17:09:59 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id D470073039; Fri, 12 Oct 2007 17:08:13 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20071012210813.D470073039@freebsd-current.sentex.ca> Date: Fri, 12 Oct 2007 17:08:13 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on clamscanner3 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: Fri, 12 Oct 2007 21:10:01 -0000 TB --- 2007-10-12 20:49:37 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-10-12 20:49:37 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2007-10-12 20:49:37 - cleaning the object tree TB --- 2007-10-12 20:49:58 - checking out the source tree TB --- 2007-10-12 20:49:58 - cd /tinderbox/HEAD/sparc64/sparc64 TB --- 2007-10-12 20:49:58 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-10-12 20:58:43 - building world (CFLAGS=-O2 -pipe) TB --- 2007-10-12 20:58:43 - cd /src TB --- 2007-10-12 20:58:43 - /usr/bin/make -B buildworld >>> World build started on Fri Oct 12 20:58:44 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 [...] echo '#define EXTRA_MODES_FILE "sparc/sparc-modes.def"' >> tm.h /usr/bin/make -f /src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile MFILE=/src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile GCCDIR=/src/gnu/lib/csu/../../../contrib/gcc options.h awk -f /src/gnu/lib/csu/../../../contrib/gcc/opt-gather.awk /src/gnu/lib/csu/../../../contrib/gcc/c.opt /src/gnu/lib/csu/../../../contrib/gcc/common.opt /src/gnu/lib/csu/../../../contrib/gcc/config/sparc/sparc.opt /src/gnu/lib/csu/../../../contrib/gcc/config/sparc/long-double-switch.opt > optionlist awk -f /src/gnu/lib/csu/../../../contrib/gcc/opt-functions.awk -f /src/gnu/lib/csu/../../../contrib/gcc/opth-gen.awk < optionlist > options.h rm -f .depend mkdep -f .depend -a -DCRT_BEGIN -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -DDT_CONFIG -D__GLIBC__=3 -I/src/gnu/lib/csu/../../../contrib/gcclibs/include -I/src/gnu/lib/csu/../../../contrib/gcc/config -I/src/gnu/lib/csu/../../../contrib/gcc -I. -I/src/gnu/lib/csu/../../usr.bin/cc/cc_tools /src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c /src/gnu/lib/csu/../../../contrib/gcc/config/sparc/crtfastmath.c cc -O2 -pipe -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -DDT_CONFIG -D__GLIBC__=3 -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-zero-initialized-in-bss -fno-toplevel-reorder -I/src/gnu/lib/csu/../../../contrib/gcclibs/include -I/src/gnu/lib/csu/../../../contrib/gcc/config -I/src/gnu/lib/csu/../../../contrib/gcc -I. -I/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -std=gnu89 -g0 -DCRT_BEGIN -c -o crtbegin.o /src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c /src/gnu/lib/csu/../../../contrib/gcc/config/sparc/crtfastmath.c cc: cannot specify -o with -c or -S with multiple files *** Error code 1 Stop in /src/gnu/lib/csu. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-10-12 21:08:13 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-10-12 21:08:13 - ERROR: failed to build world TB --- 2007-10-12 21:08:13 - tinderbox aborted TB --- 0.66 user 2.55 system 1115.77 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 21:18:25 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 D534616A41B; Fri, 12 Oct 2007 21:18:25 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.82]) by mx1.freebsd.org (Postfix) with ESMTP id C313A13C45A; Fri, 12 Oct 2007 21:18:25 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (asmtp006-s [10.150.69.69]) by smtpoutm.mac.com (Xserve/smtpout019/MantshX 4.0) with ESMTP id l9CLIPAJ001515; Fri, 12 Oct 2007 14:18:25 -0700 (PDT) Received: from [172.24.104.105] (natint3.juniper.net [66.129.224.36]) (authenticated bits=0) by mac.com (Xserve/asmtp006/MantshX 4.0) with ESMTP id l9CLINYH014125 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 12 Oct 2007 14:18:23 -0700 (PDT) In-Reply-To: <200710121620.59787.jhb@freebsd.org> References: <200710111741.34992.jhb@FreeBSD.org> <200710121409.31407.jhb@freebsd.org> <7C92FD4D-39DA-4AAE-A0F6-4D856AAD46EE@mac.com> <200710121620.59787.jhb@freebsd.org> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Fri, 12 Oct 2007 14:17:51 -0700 To: John Baldwin X-Mailer: Apple Mail (2.752.3) Cc: current@freebsd.org Subject: Re: New-bus unit wiring via hints.. 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, 12 Oct 2007 21:18:26 -0000 On Oct 12, 2007, at 1:20 PM, John Baldwin wrote: > On Friday 12 October 2007 03:49:28 pm Marcel Moolenaar wrote: >> >> On Oct 12, 2007, at 11:09 AM, John Baldwin wrote: >> >>> On Thursday 11 October 2007 05:59:23 pm Marcel Moolenaar wrote: >>>> >>>> On Oct 11, 2007, at 2:41 PM, John Baldwin wrote: >>>> >>>>> 2) One of the things this fixes that is visible to users is >>>>> that if >>>>> your >>>>> machine gets the COM ports backwards when using ACPI it should >>>>> now get >>>>> them correct (COM1 as sio0) assuming your COM ports use the >>>>> default hints >>>>> and you have the default sio hints in your /boot/device.hints >>>>> file. >>>> >>>> I think you just pointed out the problem of using hints to wire >>>> down unit numbers, because hints will stop hinting and will start >>>> dictating. If I swap the serial ports in the BIOS then surely >>>> my hints will be wrong and ACPI will be right. A default hints >>>> file will be even more disastrous than before. >>> >>> hints have always dictated. The issue is that hints are >>> enumerating devices >>> that ACPI/PNPBIOS also dictate, so how does one resolve the >>> differences (do >>> you ignore one or the other, or attempt to merge them, etc.). Note >>> that >>> hints can always be removed. >> >> I think the conflict is resolved by having hints only apply to the >> isa >> bus proper and stop tying apci to the isa bus. This also exposes >> other >> flaws with hints, such as using flags to mark a device as (potential) >> console. > > The issue here is that the 16550 UART that ACPI enumerates is on > the LPC bus, > that is, it's an ISA device. LPC mimics or replaces ISA. I don't treat them the same. For one, ISA has actual slots to plug in extension cards. LPC is enumerated. ISA isn't. > In this case, ACPI is subsuming the role of the > PNPBIOS to enumerate ISA devices. This is a PC notion. There's no PNPBIOS on ia64 for example. There is ACPI that enumerates devices on the LPC bus though. > If you want to move all the > ACPI-enumerated ISA devices under isa0 (which we can do, similar to > how the > ACPI pci(4) driver "claims" the ACPI handles for PCI devices in the > ACPI > namespace) we can do that, but that doesn't solve the problem at all. Hell no. That's exactly what I don't want. The isa(4) bus with its devices should be obsoleted entirely. >>> FWIW, the resources for COM1 and COM2 are largely fixed in >>> practice on >>> existing x86 hardware which is what this would affect, and hints >>> can always >>> be removed. Given the number of complaints from people where ACPI >>> enumerates >>> COM2 before COM1 (and the fact that ACPI made _UID useless by not >>> giving it a >>> more strict format.. it's optional and on some systems it is 0- >>> based while on >>> others it is 1-based. >> >> But aren't the complaints the immediate result of having hints in the >> first >> place. Remove the hints and the complaints go away, right? > > No. The kernel console switches because it is bound via hints. More hints, more problems. As I said before: it's a mistake to use hints for that because it makes hints ambiguous. > Besides, > people also don't like the cosmetics of having ttyd0 being COM2 and > ttyd1 > being COM1, etc. More legacy PC fixation. If the BIOS claims that COM1 is at 0x2f8 then so be it. If COM2 is enumerated first and it ends up as uart0 then so be it. There's no bug. It's all in a name. Device wiring would allow people to tie COM2 to uart1 if they want to, but all this COM-stuff is really nothing more than a fixation on 20-year old conventions that the rest of the world abandoned many years ago. It's turned into a bigger problem than it really is, mostly because we still have those stupid hints that are based on 20-year old conventions. ACPI describes the hardware and FreeBSD should respect that. I consider it mere coincidence that there's a serial port at I/O port 0x3f8 that ends up as sio0 on most current PCs. If ACPI describes a different hardware configuration then I don't think that we're in any position to claim that ACPI is wrong or the hardware broken. We can only claim that IFF there's no hardware at those resources or the hardware is in fact non-functioning. >>> I've also seen pci link devices where the _UID is the >>> link index from the $PIR table which == the register offset in >>> config space >>> on the PCI-ISA bridge of the controlling register) and the fact >>> that COM1 and >>> COM2 have de-facto fixed resources on x86, I think it's ok for x86 >>> to include >>> default hints for sio0 and sio1. >> >> If the hints would be specific to the ISA bus, then it would >> definitely be >> ok to have them. Even though we don't support i386 hardware, it >> should not >> be a big deal to keep the support for the ISA bus. We should >> really stop >> using acpi as an alias for isa and start treating it as a separate >> "bus". > > See above. ACPI != bus. ACPI == namespace that spans multiple > busses. This > is an important distinction. Drivers need a bus attachment to work with ACPI, so we have abstracted it as a bus. Therefore, it's a bus in FreeBSD. The abstraction is good. I don't see a problem with it... > If you want the configuration file separate from the kernel, then > what do you > consider /boot/device.hints to be? Non-existent. -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 21:26:13 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 6A72116A419; Fri, 12 Oct 2007 21:26:13 +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 281CD13C4BD; Fri, 12 Oct 2007 21:26:13 +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 l9CLQC8J061439; Fri, 12 Oct 2007 17:26:12 -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 l9CLQCTl089957; Fri, 12 Oct 2007 17:26:12 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 319FD73039; Fri, 12 Oct 2007 17:24:27 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20071012212427.319FD73039@freebsd-current.sentex.ca> Date: Fri, 12 Oct 2007 17:24:27 -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/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: Fri, 12 Oct 2007 21:26:13 -0000 TB --- 2007-10-12 21:08:04 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-10-12 21:08:04 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2007-10-12 21:08:04 - cleaning the object tree TB --- 2007-10-12 21:08:23 - checking out the source tree TB --- 2007-10-12 21:08:23 - cd /tinderbox/HEAD/sparc64/sun4v TB --- 2007-10-12 21:08:23 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-10-12 21:15:31 - building world (CFLAGS=-O2 -pipe) TB --- 2007-10-12 21:15:31 - cd /src TB --- 2007-10-12 21:15:31 - /usr/bin/make -B buildworld >>> World build started on Fri Oct 12 21:15:32 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 [...] echo '#define EXTRA_MODES_FILE "sparc/sparc-modes.def"' >> tm.h /usr/bin/make -f /src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile MFILE=/src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile GCCDIR=/src/gnu/lib/csu/../../../contrib/gcc options.h awk -f /src/gnu/lib/csu/../../../contrib/gcc/opt-gather.awk /src/gnu/lib/csu/../../../contrib/gcc/c.opt /src/gnu/lib/csu/../../../contrib/gcc/common.opt /src/gnu/lib/csu/../../../contrib/gcc/config/sparc/sparc.opt /src/gnu/lib/csu/../../../contrib/gcc/config/sparc/long-double-switch.opt > optionlist awk -f /src/gnu/lib/csu/../../../contrib/gcc/opt-functions.awk -f /src/gnu/lib/csu/../../../contrib/gcc/opth-gen.awk < optionlist > options.h rm -f .depend mkdep -f .depend -a -DCRT_BEGIN -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -DDT_CONFIG -D__GLIBC__=3 -I/src/gnu/lib/csu/../../../contrib/gcclibs/include -I/src/gnu/lib/csu/../../../contrib/gcc/config -I/src/gnu/lib/csu/../../../contrib/gcc -I. -I/src/gnu/lib/csu/../../usr.bin/cc/cc_tools /src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c /src/gnu/lib/csu/../../../contrib/gcc/config/sparc/crtfastmath.c cc -O2 -pipe -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -DDT_CONFIG -D__GLIBC__=3 -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-zero-initialized-in-bss -fno-toplevel-reorder -I/src/gnu/lib/csu/../../../contrib/gcclibs/include -I/src/gnu/lib/csu/../../../contrib/gcc/config -I/src/gnu/lib/csu/../../../contrib/gcc -I. -I/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -std=gnu89 -g0 -DCRT_BEGIN -c -o crtbegin.o /src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c /src/gnu/lib/csu/../../../contrib/gcc/config/sparc/crtfastmath.c cc: cannot specify -o with -c or -S with multiple files *** Error code 1 Stop in /src/gnu/lib/csu. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-10-12 21:24:27 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-10-12 21:24:27 - ERROR: failed to build world TB --- 2007-10-12 21:24:27 - tinderbox aborted TB --- 0.69 user 2.13 system 982.66 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sun4v.full From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 23:11: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 21F7316A417 for ; Fri, 12 Oct 2007 23:11:14 +0000 (UTC) (envelope-from jfvogel@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 BBB0913C465 for ; Fri, 12 Oct 2007 23:11:13 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so873955nfb for ; Fri, 12 Oct 2007 16:11: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:mime-version:content-type:content-transfer-encoding:content-disposition; bh=zlJdPC5uK0vxl0oAHUr0ypsXaqRm+aiggx4aYFIbxlA=; b=Lm0vN7Q2zwM+78vuk5eMqir3hatHy181ZnBOHsY2Q6508cSpnOgffrxKpXnrk7zDIW4lRB/w3Wdbryjdswh161pql8cFXUZ1g4VS00C/CS7O0B4DdLTrcTaYjD9GFBkAMiGw9RMIJ98sqpTwqjBfigvhh2TjBH9IMqu7qg6/h78= 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=Xvuz1XHE9m16Y7i38Gtu+5+oAg6hFlei6n+kyYKv2azwD1W3CfnJj5fUXjIP4Sm+lO35pQ6Wf0KJHhDrRvSoh2fi+xwMbtKt1/qX/XGBTsObXekpab224SCts8F0HE7Chx/roPjBJbhseREB13tvO6PbDmvGloJdWECadcEF2Xo= Received: by 10.86.76.16 with SMTP id y16mr2731529fga.1192230672190; Fri, 12 Oct 2007 16:11:12 -0700 (PDT) Received: by 10.86.100.19 with HTTP; Fri, 12 Oct 2007 16:11:12 -0700 (PDT) Message-ID: <2a41acea0710121611n4bb8d00egc104118cf7711537@mail.gmail.com> Date: Fri, 12 Oct 2007 16:11:12 -0700 From: "Jack Vogel" To: "FreeBSD Current" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: examples of programmatic use of sysctl 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, 12 Oct 2007 23:11:14 -0000 In my PTP/IEEE 1588 implementation I was considering using sysctl to pass data in and out of the driver and it needs to be from some app program not interactive. I was just wondering if anyone can point me at anything besides the sysctl command that is doing this? Jack From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 18:49: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 883B816A41B for ; Fri, 12 Oct 2007 18:49:30 +0000 (UTC) (envelope-from sbrown@stellablue.org) Received: from mail5.neteze.com (mail5.neteze.com [209.160.67.25]) by mx1.freebsd.org (Postfix) with ESMTP id 69DB713C48E for ; Fri, 12 Oct 2007 18:49:30 +0000 (UTC) (envelope-from sbrown@stellablue.org) Received: from 66-169-93-064.dhcp.ahvl.nc.charter.com ([66.169.93.64] helo=[127.0.0.1]) by mail5.neteze.com with esmtpa (Exim 4.63) (envelope-from ) id 1IgNnm-0004Hn-Fi; Fri, 12 Oct 2007 16:55:54 +0000 Message-ID: <470FA703.4030003@stellablue.org> Date: Fri, 12 Oct 2007 12:55:31 -0400 From: Steven Brown User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Steve Brown References: <200710120913.47380.joao@matik.com.br> <470FA675.1010409@stellablue.org> In-Reply-To: <470FA675.1010409@stellablue.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 000780-2, 10/11/2007), Outbound message X-Antivirus-Status: Clean X-Mailman-Approved-At: Fri, 12 Oct 2007 23:18:52 +0000 Cc: FreeBSD Current Subject: Re: what is this: SdMaP0? 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, 12 Oct 2007 18:49:30 -0000 Steve Brown wrote: > Probably the same thing I see in my firewall logs all the time - > slightly obfuscated: > > Oct 12 00:00:03 x-xxx-x kernel: ipfw: 65i0p0f0w: Deny UD6P5 010608 > .D9e5n.y1 92U.D9P4 :156089.9935 .7129.22.5904.:254019.9537 : > 7523. 2i5n0 .v2i4a1 .b5g7e:05 > Oct 12 00:00:24 xx-xx-x kernel: ipfw: 65000 Deny UDP > 217.212.224.159:32768 7i8.pf2w5:0 .24.57:5635 0i0n0 vDiean yb geU1D > Oct 11 23:46:48 x-xx-x kernel: ipfw: 505 Deny TCP 65.55.235.159:6704i > p7fw: .2550.52 4D1e.n5y9 :8T0C Pi n6 5v.i5a5 .2b3g5e.01 > > Looks like two different logs combining into one. > > 6.2-RELEASE, SMP kernel, quad core > > Steve Note, this is i386 build, not amd64 ... so it seems to apply across architectures. Steve From owner-freebsd-current@FreeBSD.ORG Fri Oct 12 20:30: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 9AF3D16A419 for ; Fri, 12 Oct 2007 20:30:09 +0000 (UTC) (envelope-from varga.michal@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 0BD6413C461 for ; Fri, 12 Oct 2007 20:30:08 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so845672nfb for ; Fri, 12 Oct 2007 13:30:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:subject:from:to:content-type:organization:date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=H09u3WrHY46aGuohEoQvpQp3QyCUQ5c+ZnoOASYbZkU=; b=ZvCKEAJ/J/uSJTkY9Rrs980gx6i+XWv44eURvlSfAYaykkl6dhksyKunqeQyQiVOUuNrSrT1haTMZ90z7+hxzSp4h3rCjF7JXzn1RyJHA7rXgm2yfyJTnqDYF0nuKzDF1iUaJRTz5w0Qi0PQj/cO8qs7zSGKZs3xy9D7tWX0qgg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:subject:from:to:content-type:organization:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=FQEzWm9Mdkgs+J0agGMEONG4B9pDS4dsS+3xeL5/O4tOsj5512wr8haqLiwfLZuAWohApIRCPquI1GOqwlUs5x/bD86FhVNoS5bIrSuSHQ279e0Kx0PB+OUDihUzZuR64LBNuSpe+lXbb420NHHcn/l0WHs5qeultHSTwVl7dd4= Received: by 10.86.99.9 with SMTP id w9mr2629876fgb.1192219514907; Fri, 12 Oct 2007 13:05:14 -0700 (PDT) Received: from ?10.0.100.2? ( [89.176.79.57]) by mx.google.com with ESMTPS id 31sm2135121fkt.2007.10.12.13.05.12 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 12 Oct 2007 13:05:13 -0700 (PDT) From: Michal Varga To: freebsd-current@freebsd.org Content-Type: text/plain Organization: Stonehenge Date: Fri, 12 Oct 2007 22:05:11 +0200 Message-Id: <1192219511.13906.56.camel@xenon.stonehenge.sk> Mime-Version: 1.0 X-Mailer: Evolution 2.10.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 12 Oct 2007 23:19:02 +0000 Subject: AMD690G/V issues with 7-current (sata, usb) 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, 12 Oct 2007 20:30:09 -0000 Yesterday I bought an AMD690-based motherboard for a 7-current desktop - http://www.gigabyte.us/Products/Motherboard/Products_Spec.aspx?ClassValue=Motherboard&ProductID=2437&ProductName=GA-MA69VM-S2 - after previous nightmarish experiences with Asus M2N32-SLI (currently on its way to service center, again, and I just hope they wont even bother to send it back) and generally everything utilizing nForce chipsets, I didn't dare to expect much from anything AM2 related, but this board runs amazingly well and stable.. Well, except for two issuese someone might be willing to look into and make this board perfect for a FreeBSD desktop: SATA: IXP600 SATA AHCI controller isn't currently recognized by FreeBSD. There is an open PR with a patch that works for me - http://www.freebsd.org/cgi/query-pr.cgi?pr=113195 - but quite old and google doesn't show any other activity.. So, is there any reason why this patch wasn't commited? As far as I can tell, there is nothing wrong with it and everything seems to work as it should. For me, at least. USB: Second issue is with USB, the initialization fails every time when there is mouse plugged in prior to FreeBSD boot (but not if the mouse is plugged later). Some snippets from dmesg (sorry, no debug/verbose, as I currently cannot reboot for at least next 12 hours): FreeBSD 7.0-PRERELEASE #0: Fri Oct 12 04:30:49 CEST 2007 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 3600+ (2004.55-MHz 686-class CPU) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 smbios0: at iomem 0xf0ce0-0xf0cfe on motherboard smbios0: Version: 2.3, BCD Revision: 2.3 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of f0000, 8000 (3) failed acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 7fde0000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 ohci0: mem 0xfe02e000-0xfe02efff irq 16 at device 19.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: 2 ports with 2 removable, self powered ohci1: mem 0xfe02d000-0xfe02dfff irq 17 at device 19.1 on pci0 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered ohci2: mem 0xfe02c000-0xfe02cfff irq 18 at device 19.2 on pci0 ohci2: [GIANT-LOCKED] ohci2: [ITHREAD] usb2: OHCI version 1.0, legacy support usb2: SMM does not respond, resetting usb2: on ohci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ohci3: mem 0xfe02b000-0xfe02bfff irq 17 at device 19.3 on pci0 ohci3: [GIANT-LOCKED] ohci3: [ITHREAD] usb3: OHCI version 1.0, legacy support usb3: SMM does not respond, resetting usb3: on ohci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ohci4: mem 0xfe02a000-0xfe02afff irq 18 at device 19.4 on pci0 ohci4: [GIANT-LOCKED] ohci4: [ITHREAD] usb4: OHCI version 1.0, legacy support usb4: SMM does not respond, resetting usb4: on ohci4 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered ehci0: mem 0xfe029000-0xfe0290ff irq 19 at device 19.5 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb5: EHCI version 1.0 usb5: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4 usb5: on ehci0 usb5: USB revision 2.0 uhub5: on usb5 uhub5: 10 ports with 10 removable, self powered When there is mouse attached during boot in any of the USB ports, initialization for that port will fail: lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] uhub0: device problem (TIMEOUT), disabling port 2 but any time after that, I can plug in that mouse (a cheap generic one I've been using for years without problems on other boards with FreeBSD) into any USB port (except that disabled one, of course) and it will work perfectly. Plug, here we go: ums0: on uhub1 ums0: 7 buttons and Z dir. pciconf: ohci0@pci0:0:19:0: class=0x0c0310 card=0x50041458 chip=0x43871002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc.' device = 'IXP SB600 USB Controller (OHCI0)' class = serial bus subclass = USB ohci1@pci0:0:19:1: class=0x0c0310 card=0x50041458 chip=0x43881002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc.' device = 'IXP SB600 USB Controller (OHCI1)' class = serial bus subclass = USB ohci2@pci0:0:19:2: class=0x0c0310 card=0x50041458 chip=0x43891002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc.' device = 'IXP SB600 USB Controller (OHCI2)' class = serial bus subclass = USB ohci3@pci0:0:19:3: class=0x0c0310 card=0x50041458 chip=0x438a1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc.' device = 'IXP SB600 USB Controller (OHCI3)' class = serial bus subclass = USB ohci4@pci0:0:19:4: class=0x0c0310 card=0x50041458 chip=0x438b1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc.' device = 'IXP SB600 USB Controller (OHCI4)' class = serial bus subclass = USB ehci0@pci0:0:19:5: class=0x0c0320 card=0x50041458 chip=0x43861002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc.' device = 'IXP SB600 USB Controller (EHCI)' class = serial bus subclass = USB Anyone interested in debugging this? (please CC: me for reply, I'm subscribed with a different email that is down for maintenance for a few days and didn't want to subscribe again) Regards, m. From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 00:28: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 0487716A419 for ; Sat, 13 Oct 2007 00:28:58 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mx1.freebsd.org (Postfix) with ESMTP id 9CB3A13C459 for ; Sat, 13 Oct 2007 00:28:56 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l9D0StRh009051; Sat, 13 Oct 2007 10:28:55 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l9D0St4N009050; Sat, 13 Oct 2007 10:28:55 +1000 (EST) (envelope-from peter) Date: Sat, 13 Oct 2007 10:28:55 +1000 From: Peter Jeremy To: Jack Vogel Message-ID: <20071013002855.GD93545@turion.vk2pj.dyndns.org> References: <2a41acea0710121611n4bb8d00egc104118cf7711537@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gatW/ieO32f1wygP" Content-Disposition: inline In-Reply-To: <2a41acea0710121611n4bb8d00egc104118cf7711537@mail.gmail.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.16 (2007-06-09) Cc: FreeBSD Current Subject: Re: examples of programmatic use of sysctl 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, 13 Oct 2007 00:28:58 -0000 --gatW/ieO32f1wygP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-Oct-12 16:11:12 -0700, Jack Vogel wrote: >In my PTP/IEEE 1588 implementation I was considering using sysctl >to pass data in and out of the driver and it needs to be from some app >program not interactive. > >I was just wondering if anyone can point me at anything besides the >sysctl command that is doing this? If you mean exchanging data in general between userland and kernel then rummaging though the source looking for sysctlbyname() (or sysctl() or sysctlnametomib()) will turn up lots of hits. Without knowing exactly what you are trying to achieve, I can't be absolutely certain but potentially interesting places to look would be conscontrol(8), dumpon(8), ipcs(1) etc. Note that most of the *stat commands, as well as ps, use sysctl rather than grovelling around in /dev/kmem. --=20 Peter Jeremy --gatW/ieO32f1wygP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHEBFH/opHv/APuIcRAq0EAJ411gISBnPttpkvbx+Uca3fMgLf+wCeNUS/ ggCc8GZGBfdTV1nfUnPMn4k= =BJfC -----END PGP SIGNATURE----- --gatW/ieO32f1wygP-- From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 00:34: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 9FB1316A419; Sat, 13 Oct 2007 00:34:23 +0000 (UTC) (envelope-from peo@intersonic.se) Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com [212.247.8.98]) by mx1.freebsd.org (Postfix) with ESMTP id 7D04113C459; Sat, 13 Oct 2007 00:34:23 +0000 (UTC) (envelope-from peo@intersonic.se) X-Virus-Scanned: amavisd-new at inter-sonic.com Message-ID: <47101288.5080102@intersonic.se> Date: Sat, 13 Oct 2007 02:34:16 +0200 From: Per olof Ljungmark Organization: Intersonic AB User-Agent: Thunderbird 2.0.0.6 (X11/20071009) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.ORG Subject: portupgrade confusion 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, 13 Oct 2007 00:34:23 -0000 Hi, Running portupgrade on RELENG_7, got this whlie updating net-snmp and I have no idea what what this means. System ran -CURRENT from Jan 16 before upgrade to todays sources (RELENG_7): pkgdb -F Fatal error F'aThread is not system scope. t'a la etr rloirn e' Thread is not system scope. 3'1 6a ti nl ifniel e3 1/usr/src/lib/libpthread/thread/thr_sig.c6 (ienr rfniol e= /usr/src/lib/libpthread/thread/thr_sig.c2 )( errno = 2) Abort (core dumped) Thanks, Per olof From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 00:51: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 7497A16A418; Sat, 13 Oct 2007 00:51:17 +0000 (UTC) (envelope-from peo@intersonic.se) Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com [212.247.8.98]) by mx1.freebsd.org (Postfix) with ESMTP id 5253613C46A; Sat, 13 Oct 2007 00:51:17 +0000 (UTC) (envelope-from peo@intersonic.se) X-Virus-Scanned: amavisd-new at inter-sonic.com Message-ID: <47101679.80505@intersonic.se> Date: Sat, 13 Oct 2007 02:51:05 +0200 From: Per olof Ljungmark Organization: Intersonic AB User-Agent: Thunderbird 2.0.0.6 (X11/20071009) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <47101288.5080102@intersonic.se> In-Reply-To: <47101288.5080102@intersonic.se> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.ORG Subject: Re: portupgrade confusion 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, 13 Oct 2007 00:51:17 -0000 Per olof Ljungmark wrote: > Hi, > Running portupgrade on RELENG_7, got this whlie updating net-snmp and I > have no idea what what this means. System ran -CURRENT from Jan 16 > before upgrade to todays sources (RELENG_7): > > pkgdb -F > Fatal error F'aThread is not system scope. > t'a la etr rloirn e' Thread is not system scope. > 3'1 6a ti nl ifniel e3 1/usr/src/lib/libpthread/thread/thr_sig.c6 (ienr > rfniol e= /usr/src/lib/libpthread/thread/thr_sig.c2 )( > errno = 2) > Abort (core dumped) Rebuilding ruby and ruby-bdb fixed it. But the error was quite funny no? From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 01:16: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 B8C1716A417 for ; Sat, 13 Oct 2007 01:16:30 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 771B613C448 for ; Sat, 13 Oct 2007 01:16:30 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.1/8.13.4) with ESMTP id l9D1E6fs009447; Fri, 12 Oct 2007 19:14:06 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 12 Oct 2007 19:14:17 -0600 (MDT) Message-Id: <20071012.191417.-1622602540.imp@bsdimp.com> To: jfvogel@gmail.com From: "M. Warner Losh" In-Reply-To: <2a41acea0710121611n4bb8d00egc104118cf7711537@mail.gmail.com> References: <2a41acea0710121611n4bb8d00egc104118cf7711537@mail.gmail.com> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Fri, 12 Oct 2007 19:14:06 -0600 (MDT) Cc: freebsd-current@FreeBSD.ORG Subject: Re: examples of programmatic use of sysctl 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, 13 Oct 2007 01:16:30 -0000 In message: <2a41acea0710121611n4bb8d00egc104118cf7711537@mail.gmail.com> "Jack Vogel" writes: : In my PTP/IEEE 1588 implementation I was considering using sysctl : to pass data in and out of the driver and it needs to be from some app : program not interactive. Didn't want to pass it back via a socket/ioctl eh? : I was just wondering if anyone can point me at anything besides the : sysctl command that is doing this? man sysctlbyname. Warner From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 01:25: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 9AB8316A420 for ; Sat, 13 Oct 2007 01:25:16 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from phoebe.cse.buffalo.edu (phoebe.cse.buffalo.edu [128.205.32.89]) by mx1.freebsd.org (Postfix) with ESMTP id 651DC13C46E for ; Sat, 13 Oct 2007 01:25:16 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from [192.168.1.101] (cpe-74-77-179-53.buffalo.res.rr.com [74.77.179.53]) (authenticated bits=0) by phoebe.cse.buffalo.edu (8.14.1/8.13.7) with ESMTP id l9D0tt54097466 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 12 Oct 2007 20:55:57 -0400 (EDT) (envelope-from kensmith@cse.buffalo.edu) From: Ken Smith To: David Benfell In-Reply-To: <20071012032516.GA2964@parts-unknown.org> References: <20071012032516.GA2964@parts-unknown.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-HczLbwOICQcTVC/JPUFj" Date: Fri, 12 Oct 2007 20:51:39 -0400 Message-Id: <1192236699.39553.26.camel@neo.cse.buffalo.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2.1 FreeBSD GNOME Team Port X-DCC-Buffalo.EDU-Metrics: phoebe.cse.buffalo.edu 1336; Body=0 Fuz1=0 Fuz2=0 X-Spam-Status: No, score=1.4 required=5.0 tests=PLING_QUERY,RDNS_DYNAMIC autolearn=no version=3.2.3 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on phoebe.cse.buffalo.edu Cc: FreeBSD Current Subject: Re: Version 8.0?!!??? 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, 13 Oct 2007 01:25:16 -0000 --=-HczLbwOICQcTVC/JPUFj Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2007-10-11 at 20:25 -0700, David Benfell wrote: > Hi all, >=20 > So I was in for a bit of a surprise when I just booted up the > a version of CURRENT built today: >=20 > FreeBSD earth.cybernude.org 8.0-CURRENT FreeBSD 8.0-CURRENT #56: Thu Oct = 11 10:27:17 PDT 2007 root@earth.cybernude.org:/usr/obj/usr/src/sys/EART= H i386 >=20 > [snicker] >=20 > No real harm, right? >=20 Oops. Sorry for not giving some sort of a heads-up here. :-( As others have pointed out HEAD becoming 8.0-CURRENT was a side-effect of branching RELENG_7 which signals we're ready to "go public" with the 7.0 release cycle. Sorry for the delay with getting that rolling. We decided to shift to time-based release cycles instead of feature-based release cycles. One side-effect of that is new features already present in the tree may in the end turn out to be not quite ready for prime-time at the point we want to start preparing the release (despite peoples' best intentions this *is* a volunteer project so ...). The bottom line is we had one of those situations arise and we (mostly I) didn't deal with it very well so things dragged on longer than expected. With the branching done we've started to discuss a schedule, that should appear some time in the next day or two. Current plan is for BETA1 builds to begin next Wednesday. As someone else pointed out the HEAD code freeze is over. We'll be trying to keep HEAD in stable shape through to the end of the release because things headed for RELENG_7 first need a bit of testing in HEAD. But in general developers start working on new projects and whatnot in HEAD fairly shortly after a new major branch (e.g. RELENG_7) appears. Unless you're a fairly hardcore developer type if you've been using HEAD because it seemed fairly stable lately now would probably be a good time for you to shift over to RELENG_7. :-) --=20 Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | --=-HczLbwOICQcTVC/JPUFj 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 (FreeBSD) iD8DBQBHEBab/G14VSmup/YRAuMBAJ9rbhmc51s6BD8vZzIbBy/wVTYZdgCeNE/r 8BxKUA7aePzQRg9INRZtkmk= =Y2VT -----END PGP SIGNATURE----- --=-HczLbwOICQcTVC/JPUFj-- From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 04:13:15 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 978E416A418; Sat, 13 Oct 2007 04:13:15 +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 67D5E13C47E; Sat, 13 Oct 2007 04:13:15 +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 l9D4DEbq094394; Sat, 13 Oct 2007 00:13:14 -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 l9D4DElJ089244; Sat, 13 Oct 2007 00:13:14 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id D3D5973039; Sat, 13 Oct 2007 00:11:28 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20071013041128.D3D5973039@freebsd-current.sentex.ca> Date: Sat, 13 Oct 2007 00:11:28 -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: Sat, 13 Oct 2007 04:13:15 -0000 TB --- 2007-10-13 03:53:23 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-10-13 03:53:23 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2007-10-13 03:53:23 - cleaning the object tree TB --- 2007-10-13 03:53:31 - checking out the source tree TB --- 2007-10-13 03:53:31 - cd /tinderbox/HEAD/sparc64/sparc64 TB --- 2007-10-13 03:53:31 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-10-13 04:02:03 - building world (CFLAGS=-O2 -pipe) TB --- 2007-10-13 04:02:03 - cd /src TB --- 2007-10-13 04:02:03 - /usr/bin/make -B buildworld >>> World build started on Sat Oct 13 04:02:04 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 [...] echo '#define EXTRA_MODES_FILE "sparc/sparc-modes.def"' >> tm.h /usr/bin/make -f /src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile MFILE=/src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile GCCDIR=/src/gnu/lib/csu/../../../contrib/gcc options.h awk -f /src/gnu/lib/csu/../../../contrib/gcc/opt-gather.awk /src/gnu/lib/csu/../../../contrib/gcc/c.opt /src/gnu/lib/csu/../../../contrib/gcc/common.opt /src/gnu/lib/csu/../../../contrib/gcc/config/sparc/sparc.opt /src/gnu/lib/csu/../../../contrib/gcc/config/sparc/long-double-switch.opt > optionlist awk -f /src/gnu/lib/csu/../../../contrib/gcc/opt-functions.awk -f /src/gnu/lib/csu/../../../contrib/gcc/opth-gen.awk < optionlist > options.h rm -f .depend mkdep -f .depend -a -DCRT_BEGIN -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -DDT_CONFIG -D__GLIBC__=3 -I/src/gnu/lib/csu/../../../contrib/gcclibs/include -I/src/gnu/lib/csu/../../../contrib/gcc/config -I/src/gnu/lib/csu/../../../contrib/gcc -I. -I/src/gnu/lib/csu/../../usr.bin/cc/cc_tools /src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c /src/gnu/lib/csu/../../../contrib/gcc/config/sparc/crtfastmath.c cc -O2 -pipe -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -DDT_CONFIG -D__GLIBC__=3 -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-zero-initialized-in-bss -fno-toplevel-reorder -I/src/gnu/lib/csu/../../../contrib/gcclibs/include -I/src/gnu/lib/csu/../../../contrib/gcc/config -I/src/gnu/lib/csu/../../../contrib/gcc -I. -I/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -std=gnu89 -g0 -DCRT_BEGIN -c -o crtbegin.o /src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c /src/gnu/lib/csu/../../../contrib/gcc/config/sparc/crtfastmath.c cc: cannot specify -o with -c or -S with multiple files *** Error code 1 Stop in /src/gnu/lib/csu. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-10-13 04:11:28 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-10-13 04:11:28 - ERROR: failed to build world TB --- 2007-10-13 04:11:28 - tinderbox aborted TB --- 0.17 user 0.39 system 1084.49 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 04:29:10 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 017A416A41A; Sat, 13 Oct 2007 04:29:10 +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 C7C1813C46E; Sat, 13 Oct 2007 04:29:09 +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 l9D4T8Da099371; Sat, 13 Oct 2007 00:29:09 -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 l9D4T8x6019734; Sat, 13 Oct 2007 00:29:08 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 8843873039; Sat, 13 Oct 2007 00:27:23 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20071013042723.8843873039@freebsd-current.sentex.ca> Date: Sat, 13 Oct 2007 00:27:23 -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/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: Sat, 13 Oct 2007 04:29:10 -0000 TB --- 2007-10-13 04:11:01 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-10-13 04:11:01 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2007-10-13 04:11:01 - cleaning the object tree TB --- 2007-10-13 04:11:08 - checking out the source tree TB --- 2007-10-13 04:11:08 - cd /tinderbox/HEAD/sparc64/sun4v TB --- 2007-10-13 04:11:08 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-10-13 04:18:30 - building world (CFLAGS=-O2 -pipe) TB --- 2007-10-13 04:18:30 - cd /src TB --- 2007-10-13 04:18:30 - /usr/bin/make -B buildworld >>> World build started on Sat Oct 13 04:18:31 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 [...] echo '#define EXTRA_MODES_FILE "sparc/sparc-modes.def"' >> tm.h /usr/bin/make -f /src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile MFILE=/src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile GCCDIR=/src/gnu/lib/csu/../../../contrib/gcc options.h awk -f /src/gnu/lib/csu/../../../contrib/gcc/opt-gather.awk /src/gnu/lib/csu/../../../contrib/gcc/c.opt /src/gnu/lib/csu/../../../contrib/gcc/common.opt /src/gnu/lib/csu/../../../contrib/gcc/config/sparc/sparc.opt /src/gnu/lib/csu/../../../contrib/gcc/config/sparc/long-double-switch.opt > optionlist awk -f /src/gnu/lib/csu/../../../contrib/gcc/opt-functions.awk -f /src/gnu/lib/csu/../../../contrib/gcc/opth-gen.awk < optionlist > options.h rm -f .depend mkdep -f .depend -a -DCRT_BEGIN -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -DDT_CONFIG -D__GLIBC__=3 -I/src/gnu/lib/csu/../../../contrib/gcclibs/include -I/src/gnu/lib/csu/../../../contrib/gcc/config -I/src/gnu/lib/csu/../../../contrib/gcc -I. -I/src/gnu/lib/csu/../../usr.bin/cc/cc_tools /src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c /src/gnu/lib/csu/../../../contrib/gcc/config/sparc/crtfastmath.c cc -O2 -pipe -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -DDT_CONFIG -D__GLIBC__=3 -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-zero-initialized-in-bss -fno-toplevel-reorder -I/src/gnu/lib/csu/../../../contrib/gcclibs/include -I/src/gnu/lib/csu/../../../contrib/gcc/config -I/src/gnu/lib/csu/../../../contrib/gcc -I. -I/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -std=gnu89 -g0 -DCRT_BEGIN -c -o crtbegin.o /src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c /src/gnu/lib/csu/../../../contrib/gcc/config/sparc/crtfastmath.c cc: cannot specify -o with -c or -S with multiple files *** Error code 1 Stop in /src/gnu/lib/csu. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-10-13 04:27:23 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-10-13 04:27:23 - ERROR: failed to build world TB --- 2007-10-13 04:27:23 - tinderbox aborted TB --- 0.19 user 0.38 system 981.80 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sun4v.full From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 06:01: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 A0C5316A41A for ; Sat, 13 Oct 2007 06:01:58 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (lindfield.ch [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id 79B2513C44B for ; Sat, 13 Oct 2007 06:01:57 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:60063 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1Iga4R-000718-UQ for freebsd-current@freebsd.org; Sat, 13 Oct 2007 06:01:55 +0000 Message-ID: <47105F53.7060701@conducive.net> Date: Sat, 13 Oct 2007 02:01:55 -0400 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <200710111741.34992.jhb@FreeBSD.org> <622950DD-BFEF-450C-8B80-BAB55C7B58CB@mac.com> <200710121409.31407.jhb@freebsd.org> In-Reply-To: <200710121409.31407.jhb@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: New-bus unit wiring via hints.. 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, 13 Oct 2007 06:01:58 -0000 John Baldwin wrote: > On Thursday 11 October 2007 05:59:23 pm Marcel Moolenaar wrote: >> On Oct 11, 2007, at 2:41 PM, John Baldwin wrote: >> *snip* > on the PCI-ISA bridge of the controlling register) and the fact that COM1 and > COM2 have de-facto fixed resources on x86, I think it's ok for x86 to include > default hints for sio0 and sio1. > Historically, COM1: - COM(n): assignments were not that hard-and-fast *anyway* - ergo a once-common BIOS option to reverse them or move 1 or 2 ports within 4 address blocks. To an extent, the 'complaint' is only that modern BIOS and OS haven't undone that long legacy of ambiguity, and 'auto' is a 'don't really care' option. And why try? The physical serial ports are being phased out on many newer MB. Lucky to get a header block. Server grade system boards might be expected to keep 'a' serial port for a while yet, but most laptops have long-since shed them. Scare resources are perhaps better applied to sorting other 'challenging' bus device issues. Such as the vexation that the current rate of progress/economic necessity is causing I/O devices in general to appear, live a *very* short economic life, and be replaced by yet-another newer one at a rate that doesn't allow thorough testing even IF there has been time to code a driver. That's not limited to F/OSS, either... :-( Bill From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 06:25: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 E56D116A419 for ; Sat, 13 Oct 2007 06:25:46 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (lindfield.ch [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id BE46213C469 for ; Sat, 13 Oct 2007 06:25:46 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:61163 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1IgaRV-00073S-Kx for freebsd-current@freebsd.org; Sat, 13 Oct 2007 06:25:45 +0000 Message-ID: <471064E9.3050704@conducive.net> Date: Sat, 13 Oct 2007 02:25:45 -0400 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <1192219511.13906.56.camel@xenon.stonehenge.sk> In-Reply-To: <1192219511.13906.56.camel@xenon.stonehenge.sk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: AMD690G/V issues with 7-current (sata, usb) 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, 13 Oct 2007 06:25:47 -0000 Michal Varga wrote: > Yesterday I bought an AMD690-based motherboard for a 7-current desktop - > > http://www.gigabyte.us/Products/Motherboard/Products_Spec.aspx?ClassValue=Motherboard&ProductID=2437&ProductName=GA-MA69VM-S2 *Snip* > > USB: > Second issue is with USB, the initialization fails every time when there > is mouse plugged in prior to FreeBSD boot (but not if the mouse is > plugged later). Similar. ASUS P5K, GigaByte G33-DS3R. Option the USB mouse support OFF in the BIOS. Otherwise, though detected, it is *ALSO* presumed to be 'in use', since the BIOS deosn't just 'enable' it - it actually starts it, and before the OS boots. If NOT claimed by the BIOS, FreeBSD will find and use it from the defaults in /etc/rc. No need to even bother with an /etc/rc.conf entry. Xorg (if you use it) will generally be au fait with that, even with the mouse active in a CLI session before you startx or a wm. The OS it doing as it should do here - honoring the pre-existing resource claim. Bill From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 07:45: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 B482116A473 for ; Sat, 13 Oct 2007 07:45:01 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id 353BA13C46E for ; Sat, 13 Oct 2007 07:45:00 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from ap-h.matik.com.br (ap-h.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id l9D7ixu5083039 for ; Sat, 13 Oct 2007 04:44:59 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: FreeBSD Current Date: Sat, 13 Oct 2007 04:43:03 -0300 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200710130443.03551.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on msrv.matik.com.br X-Virus-Status: Clean Subject: bge and kern/116328 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, 13 Oct 2007 07:45:01 -0000 about the bge problem related in kern/116328 somebody knows a workaround or if there is some change underway? thank's =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 07:48: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 80C3116A417 for ; Sat, 13 Oct 2007 07:48:52 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id 13D8013C46A for ; Sat, 13 Oct 2007 07:48:51 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from ap-h.matik.com.br (ap-h.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id l9D7mpQS083346; Sat, 13 Oct 2007 04:48:51 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: Jeremy Chadwick Date: Sat, 13 Oct 2007 04:46:55 -0300 User-Agent: KMail/1.9.7 References: <200710120913.47380.joao@matik.com.br> <20071012122621.GA30592@owl.midgard.homeip.net> <20071012124433.GA97012@eos.sc1.parodius.com> In-Reply-To: <20071012124433.GA97012@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200710130446.56137.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on msrv.matik.com.br X-Virus-Status: Clean Cc: FreeBSD Current Subject: Re: what is this: SdMaP0? 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, 13 Oct 2007 07:48:52 -0000 On Friday 12 October 2007 09:44:33 Jeremy Chadwick wrote: > On Fri, Oct 12, 2007 at 02:26:21PM +0200, Erik Trulsson wrote: > > It is two different outputs that have become mixed together. > > > > One saying > > > > SMP: AP CPU #1 Launched! > > > > and another saying > > > > da0: 160.000MB/s transfe > > > > (That last word should actually be 'transfers'. I don't know what > > happened to the final 'rs') > > They very likely got put on the next line of the dmesg output, since > one string would contain a newline. So the line after that would > probably be something like "rs". so dmesg gets encrypted now ;) and yes right, the next line says rs (80.000MHz DT, offset 63, 16bit) thanks =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 09:23: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 C2BF316A418 for ; Sat, 13 Oct 2007 09:23:36 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (lindfield.ch [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id 902BA13C458 for ; Sat, 13 Oct 2007 09:23:36 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:59369 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1IgdDa-0007Nk-QV for freebsd-current@freebsd.org; Sat, 13 Oct 2007 09:23:34 +0000 Message-ID: <47108E96.2090402@conducive.net> Date: Sat, 13 Oct 2007 05:23:34 -0400 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <200710120913.47380.joao@matik.com.br> <20071012122621.GA30592@owl.midgard.homeip.net> <20071012124433.GA97012@eos.sc1.parodius.com> <200710130446.56137.joao@matik.com.br> In-Reply-To: <200710130446.56137.joao@matik.com.br> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: what is this: SdMaP0? 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, 13 Oct 2007 09:23:36 -0000 JoaoBR wrote: > On Friday 12 October 2007 09:44:33 Jeremy Chadwick wrote: >> On Fri, Oct 12, 2007 at 02:26:21PM +0200, Erik Trulsson wrote: >>> It is two different outputs that have become mixed together. >>> >>> One saying >>> >>> SMP: AP CPU #1 Launched! >>> >>> and another saying >>> >>> da0: 160.000MB/s transfe >>> >>> (That last word should actually be 'transfers'. I don't know what >>> happened to the final 'rs') >> They very likely got put on the next line of the dmesg output, since >> one string would contain a newline. So the line after that would >> probably be something like "rs". > > so dmesg gets encrypted now ;) > > and yes right, the next line says > > rs (80.000MHz DT, offset 63, 16bit) > > thanks WT hey - it was good enough for DOS and even CP/M, so if Acacia come with a patent lawsit, we can claim 'prior art'.. Which - BTW - fits their current 'multi display' claim as well. See AN/GSA-51 Bill From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 06:22: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 4BCF316A41A for ; Sat, 13 Oct 2007 06:22:44 +0000 (UTC) (envelope-from wbh@conducive.org) Received: from conducive.org (lindfield.ch [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id 2544A13C468 for ; Sat, 13 Oct 2007 06:22:43 +0000 (UTC) (envelope-from wbh@conducive.org) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:60987 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1IgaE2-00072F-LT for freebsd-current@freebsd.org; Sat, 13 Oct 2007 06:11:50 +0000 Message-ID: <471061A6.9070909@conducive.org> Date: Sat, 13 Oct 2007 02:11:50 -0400 From: W B Hacker User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <1192219511.13906.56.camel@xenon.stonehenge.sk> In-Reply-To: <1192219511.13906.56.camel@xenon.stonehenge.sk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 13 Oct 2007 11:26:50 +0000 Subject: Re: AMD690G/V issues with 7-current (sata, usb) 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, 13 Oct 2007 06:22:44 -0000 Michal Varga wrote: > Yesterday I bought an AMD690-based motherboard for a 7-current desktop - > > http://www.gigabyte.us/Products/Motherboard/Products_Spec.aspx?ClassValue=Motherboard&ProductID=2437&ProductName=GA-MA69VM-S2 *Snip* > > USB: > Second issue is with USB, the initialization fails every time when there > is mouse plugged in prior to FreeBSD boot (but not if the mouse is > plugged later). Similar. ASUS P5K, GigaByte G33-DS3R. Option the USB mouse support OFF in the BIOS. Otherwise, though detected, it is *ALSO* presumed to be 'in use', since the BIOS deosn't just 'enable' it - it actually starts it, and before the OS boots. If NOT claimed by the BIOS, FreeBSD will find and use it from the defaults in /etc/rc. No need to even bother with an /etc/rc.conf entry. Xorg (if you use it) will generally be au fait with that, even with the mouse active in a CLI session before you startx or a wm. The OS it doing as it should do here - honoring the pre-existing resource claim. Bill From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 11:31: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 0C38416A419 for ; Sat, 13 Oct 2007 11:31:30 +0000 (UTC) (envelope-from hoschi@etain.frida.mouhaha.de) Received: from etain.frida.mouhaha.de (etain.frida.mouhaha.de [85.236.48.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8B97B13C455 for ; Sat, 13 Oct 2007 11:31:29 +0000 (UTC) (envelope-from hoschi@etain.frida.mouhaha.de) Received: from localhost (etain.frida.mouhaha.de [85.236.48.54]) by etain.frida.mouhaha.de (Postfix) with ESMTP id 1B0C94B8D30; Sat, 13 Oct 2007 13:31:28 +0200 (CEST) X-Virus-Scanned: amavisd-new at mouhaha.de Received: from etain.frida.mouhaha.de ([85.236.48.54]) by localhost (etain.frida.mouhaha.de [85.236.48.54]) (amavisd-new, port 10024) with ESMTP id tu9NTRPlOJrF; Sat, 13 Oct 2007 13:31:25 +0200 (CEST) Received: by etain.frida.mouhaha.de (Postfix, from userid 1001) id 950684B8D2F; Sat, 13 Oct 2007 13:31:25 +0200 (CEST) Date: Sat, 13 Oct 2007 13:31:25 +0200 From: Oliver Peter To: d@delphij.net Message-ID: <20071013113125.GD26846@nemesis.frida.mouhaha.de> References: <20071009155726.GB26846@nemesis.frida.mouhaha.de> <470BB044.3020308@delphij.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BI5RvnYi6R4T2M87" Content-Disposition: inline In-Reply-To: <470BB044.3020308@delphij.net> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org Subject: Re: em0: watchdog timeout 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, 13 Oct 2007 11:31:30 -0000 --BI5RvnYi6R4T2M87 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Tue, Oct 09, 2007 at 09:45:56AM -0700, LI Xin wrote: > > ... > > Today I received some em0 watchdog timeouts on my fresh 7.0-CURRENT > > machine. At first I had only some short ssh hangs but now it seems my > > server is completely offline. I will not have local access to my > > computer until this night but I will ask in advance what I can do for > > you to debug and solve this problem. Thanks a lot for your reply. I have to correct my report. The machine had these em0 watchdog timeouts, but the 'offline problem' was caused by a craftsman, a drill machine and my cable to the internet... no comment, please :-) Nevertheless, I still have these timeouts and resets on em0. > > What information shall I provide? dmesg? Kernel configuration? > I think the following information would be helpful: >=20 > - pciconf -lv > - /var/run/dmesg.boot Here you go: --- dmesg.boot ----- 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 #0: Mon Oct 8 23:25:08 CEST 2007 hoschi@marathon.geonosis.homeunix.org:/usr/obj/usr/src/sys/MARATHON Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2391.15-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0xf27 Stepping =3D 7 Features=3D0xbfebfbff real memory =3D 1064767488 (1015 MB) avail memory =3D 1032761344 (984 MB) kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, f00000 (3) failed acpi0: reservation of 1000000, 3e771000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 p4tcc0: on cpu0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: mem 0xf0000000-0xf7ffffff,0xff680000-0xff= 6fffff irq 9 at device 2.0 on pci0 uhci0: port 0xff80-0xff9f irq 9= at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xff60-0xff7f irq 1= 1 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xff40-0xff5f irq 1= 0 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xffa00800-0xffa00= bff irq 3 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 6 ports with 6 removable, self powered umass0: on uhub3 umass1: on uhub3 pcib1: at device 30.0 on pci0 pci1: on pcib1 em0: port 0xecc0-0xe= cff mem 0xff8e0000-0xff8fffff irq 10 at device 12.0 on pci1 em0: Ethernet address: 00:0b:db:3d:85:d3 em0: [FILTER] isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177= ,0x376,0xffa0-0xffaf at device 31.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pci0: at device 31.3 (no driver attached) pci0: at device 31.5 (no driver attached) sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acp= i0 sio0: type 16550A sio0: [FILTER] pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcb7ff,0xcb800-0xcbfff,0xe0000-0x= e17ff pnpid ORM0000 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled Timecounter "TSC" frequency 2391146728 Hz quality 800 Timecounters tick every 1.000 msec ad0: 76351MB at ata0-master UDMA100 acd0: CDRW at ata1-master UDMA33 --- pciconf -lv ------- hostb0@pci0:0:0:0: class=3D0x060000 card=3D0x01261028 chip=3D0x2560808= 6 rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82845G/GL/GV/GE/PE DRAM Controller / Host-Hub I/F Bridg= e' class =3D bridge subclass =3D HOST-PCI vgapci0@pci0:0:2:0: class=3D0x030000 card=3D0x01261028 chip=3D0x2562808= 6 rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82845G/GL/GV/GE/PE Integrated Graphics Device' class =3D display subclass =3D VGA uhci0@pci0:0:29:0: class=3D0x0c0300 card=3D0x01261028 chip=3D0x24c2808= 6 rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controlle= r' class =3D serial bus subclass =3D USB uhci1@pci0:0:29:1: class=3D0x0c0300 card=3D0x01261028 chip=3D0x24c4808= 6 rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controlle= r' class =3D serial bus subclass =3D USB uhci2@pci0:0:29:2: class=3D0x0c0300 card=3D0x01261028 chip=3D0x24c7808= 6 rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controlle= r' class =3D serial bus subclass =3D USB ehci0@pci0:0:29:7: class=3D0x0c0320 card=3D0x01261028 chip=3D0x24cd808= 6 rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB 2.0 EHCI Contr= oller' class =3D serial bus subclass =3D USB pcib1@pci0:0:30:0: class=3D0x060400 card=3D0x00000000 chip=3D0x244e808= 6 rev=3D0x81 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D '82801BA/CA/DB/DBL/EB/ER/FB/GB/HB (ICH2/3/4/4/5/5/6/7/8)= , 63xxESB Hub Interface to PCI Bridge' class =3D bridge subclass =3D PCI-PCI isab0@pci0:0:31:0: class=3D0x060100 card=3D0x00000000 chip=3D0x24c0808= 6 rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge' class =3D bridge subclass =3D PCI-ISA atapci0@pci0:0:31:1: class=3D0x01018a card=3D0x01261028 chip=3D0x24cb808= 6 rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801DB/DBL (ICH4/ICH4-L) UltraATA/100 EIDE Controller' class =3D mass storage subclass =3D ATA none0@pci0:0:31:3: class=3D0x0c0500 card=3D0x01261028 chip=3D0x24c3808= 6 rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller' class =3D serial bus subclass =3D SMBus none1@pci0:0:31:5: class=3D0x040100 card=3D0x01261028 chip=3D0x24c5808= 6 rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'intel 82801DB(-M) - AC'97 Audio Controller [B-0] SoundM= AX Integrated Digital Controller' class =3D multimedia subclass =3D audio em0@pci0:1:12:0: class=3D0x020000 card=3D0x002e1028 chip=3D0x100e808= 6 rev=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82540EM Gigabit Ethernet Controller' class =3D network subclass =3D ethernet =20 > Perhaps kernel configuration is not quite useful at the moment, though. > Thanks for reporting the problem. Thanks a lot for your help. Bye Ollie --=20 Oliver PETER, email: hoschi@mouhaha.de, ICQ# 113969174 "Worker bees can leave. Even drones can fly away. The Queen is their slave." --BI5RvnYi6R4T2M87 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iEYEARECAAYFAkcQrI0ACgkQ6LH/IUVtaI+OWwCgiSm7T/LI4eEtuEZ97QRjY7dF Z9sAnRP5DbE0ebqe+X6sodayyOcyWQgF =+Jbk -----END PGP SIGNATURE----- --BI5RvnYi6R4T2M87-- From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 12:36: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 12FBE16A418 for ; Sat, 13 Oct 2007 12:36:45 +0000 (UTC) (envelope-from odnomzagi@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.235]) by mx1.freebsd.org (Postfix) with ESMTP id C577613C43E for ; Sat, 13 Oct 2007 12:36:44 +0000 (UTC) (envelope-from odnomzagi@gmail.com) Received: by wx-out-0506.google.com with SMTP id i29so972215wxd for ; Sat, 13 Oct 2007 05:36:44 -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:mime-version:content-type:content-transfer-encoding:content-disposition; bh=57ZWyTHLNwWhb0uAUi16CPaOl4rH/cGKJZEp1jMLX1E=; b=Gpj0iK+q8FXsQSRdwZE4dYzfvt168Q+EJ19iDPL43/veIGDj06qosRqKNGqyIot04JzVzqCrJQ0OtTPsuEgl35r4bWrs1ki8XLt0+TgURQRoHokjN0pJKUrCEH6fkm3xgNH0AoU1DkSDBThuI/z4A5JoCR85rN6Gk7FG3RW1dx4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=i1ylGkJlIiGdnFHa+MLZjcaA/0SfJ4heldsmSMGjIAfUo4dWlq1a8po14m7nVGnTKYtMinoIKtjNwjfvV+SyPtEKavSLpr4XG4JGmKyg6+Hqd6yYfrG5FaYQ0zLZXt4qu96B8AXYAMK4lvcLvsqUzR8JGVTEjFFOh0PqmJxYIZE= Received: by 10.90.31.2 with SMTP id e2mr6206680age.1192277266363; Sat, 13 Oct 2007 05:07:46 -0700 (PDT) Received: by 10.90.35.20 with HTTP; Sat, 13 Oct 2007 05:07:46 -0700 (PDT) Message-ID: <965aa1910710130507t6b8335edj2afe41b40bca81ff@mail.gmail.com> Date: Sat, 13 Oct 2007 14:07:46 +0200 From: "Justin Smith" To: kensmith@cse.Buffalo.EDU MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mailman-Approved-At: Sat, 13 Oct 2007 12:58:24 +0000 Cc: freebsd-current@freebsd.org Subject: Re: Version 8.0?!!??? 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, 13 Oct 2007 12:36:45 -0000 On Fri, 2007-10-12 at 20:51 -0400, Ken Smith wrote: > Sorry for the delay with getting that rolling. We > decided to shift to time-based release cycles instead of feature-based > release cycles. Hi Ken! Perhaps i've missed something. Can you provide more information about this topic, please? Thank you! -- JS From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 14:27:05 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 7E1D316A473 for ; Sat, 13 Oct 2007 14:27:05 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from aaron.protected-networks.net (aaron.protected-networks.net [202.12.127.66]) by mx1.freebsd.org (Postfix) with ESMTP id 9025713C43E for ; Sat, 13 Oct 2007 14:27:04 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from localhost (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id ED546C5F8; Sat, 13 Oct 2007 10:27:02 -0400 (EDT) Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [202.12.127.84]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Iain Michael Butler", Issuer "Protected Networks Certificate Authority" (verified OK)) (Authenticated sender: imb@protected-networks.net) by aaron.protected-networks.net (Postfix) with ESMTP id 6E96CC507; Sat, 13 Oct 2007 10:26:55 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=protected-networks.net; s=200705; t=1192285615; bh=4izFy4gLu9Y3mn oopG5rmQgVsqtCrznq+1Q/XTNYldo=; h=DomainKey-Signature:Message-ID: Date:From:User-Agent:MIME-Version:To:CC:Subject:References: In-Reply-To:X-Enigmail-Version:OpenPGP:Content-Type: Content-Transfer-Encoding; b=H840oKHHLgd634WO9W79tPsajv8J+zepw5jm3 1L1P4UH0753gzlhHkmn0RRrBwHUNY2zTz+zk+vnOFxCbHDs8OQDdyEq/DFq6QIgHyum KeT268i70hrNfieOIIBoqu2W DomainKey-Signature: a=rsa-sha1; s=200509; d=protected-networks.net; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:cc:subject: references:in-reply-to:x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=SLugQbIIxZOdw70118RxMZN3MZjWzjwKv84clpFxQD0p6g2/4l4cXnd6Z0wxfd3hJ aOOILYHvOYaEP+f+f13aW6HEAYa/XUNzIe1qhZsc/DvP6yjgLk9/godf9WL5wIU Message-ID: <4710D5AE.9080107@protected-networks.net> Date: Sat, 13 Oct 2007 10:26:54 -0400 From: Michael Butler User-Agent: Thunderbird 2.0.0.6 (X11/20070903) MIME-Version: 1.0 To: John Baldwin References: <4709666D.5070504@protected-networks.net> <200710111626.35144.jhb@freebsd.org> In-Reply-To: <200710111626.35144.jhb@freebsd.org> X-Enigmail-Version: 0.95.2 OpenPGP: id=0442D492 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: Gkrellmd prompts "sleeping thread" 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, 13 Oct 2007 14:27:05 -0000 John Baldwin wrote: > On Sunday 07 October 2007 07:06:21 pm Michael Butler wrote: >> For whatever reason I seem to be able to reliably reproduce a panic on >> -current by running gkrellmd on one of my machines yet another (this >> one) has no problems at all :-( [ .. snip .. ] Sorry - have been traveling this week. The patch you offered solves the problem. Thanks! Michael > Can you make sure you have DDB in your kernel and get the full console > messages when it panics? It will include the stack trace for the offending > thread. But actually, try this patch: > > Index: intpm.c > =================================================================== > RCS file: /usr/cvs/src/sys/pci/intpm.c,v > retrieving revision 1.39 > diff -u -r1.39 intpm.c > --- intpm.c 19 Apr 2007 17:14:06 -0000 1.39 > +++ intpm.c 11 Oct 2007 20:25:52 -0000 > @@ -436,7 +436,7 @@ > /* So that it can use device during device probe on SMBus. */ > return (intsmb_stop_poll(sc)); > > - error = tsleep(sc, PWAIT | PCATCH, "SMBWAI", hz / 8); > + error = msleep(sc, &sc->lock, PWAIT | PCATCH, "SMBWAI", hz / 8); > if (error == 0) { > status = bus_read_1(sc->io_res, PIIX4_SMBHSTSTS); > if (!(status & PIIX4_SMBHSTSTAT_BUSY)) { > > From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 15:17: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 B37F116A417 for ; Sat, 13 Oct 2007 15:17:47 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from phoebe.cse.buffalo.edu (phoebe.cse.buffalo.edu [128.205.32.89]) by mx1.freebsd.org (Postfix) with ESMTP id 667D913C43E for ; Sat, 13 Oct 2007 15:17:47 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from [192.168.1.101] (cpe-74-77-179-53.buffalo.res.rr.com [74.77.179.53]) (authenticated bits=0) by phoebe.cse.buffalo.edu (8.14.1/8.13.7) with ESMTP id l9DFHcjJ099990 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sat, 13 Oct 2007 11:17:39 -0400 (EDT) (envelope-from kensmith@cse.buffalo.edu) From: Ken Smith To: Justin Smith In-Reply-To: <965aa1910710130507t6b8335edj2afe41b40bca81ff@mail.gmail.com> References: <965aa1910710130507t6b8335edj2afe41b40bca81ff@mail.gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-9VYnhzCxAutOoi6fzIzY" Date: Sat, 13 Oct 2007 11:13:23 -0400 Message-Id: <1192288404.39553.53.camel@neo.cse.buffalo.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2.1 FreeBSD GNOME Team Port X-DCC-Buffalo.EDU-Metrics: phoebe.cse.buffalo.edu 1336; Body=0 Fuz1=0 Fuz2=0 X-Spam-Status: No, score=1.4 required=5.0 tests=PLING_QUERY,RDNS_DYNAMIC autolearn=no version=3.2.3 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on phoebe.cse.buffalo.edu Cc: freebsd-current@freebsd.org Subject: Re: Version 8.0?!!??? 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, 13 Oct 2007 15:17:47 -0000 --=-9VYnhzCxAutOoi6fzIzY Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2007-10-13 at 14:07 +0200, Justin Smith wrote: > On Fri, 2007-10-12 at 20:51 -0400, Ken Smith wrote: >=20 > > Sorry for the delay with getting that rolling. We > > decided to shift to time-based release cycles instead of feature-based > > release cycles. >=20 > Hi Ken! >=20 > Perhaps i've missed something. Can you provide more information about > this topic, please? >=20 > Thank you! >=20 Releases of new major branches (e.g. the branching of RELENG_7 and the progress towards releasing FreeBSD-7.0) used to be focused on a specific set of features. For example having fine-grained SMP completed. The result of taking that approach (particularly if you include too many features) was clear with what happened to RELENG_5 (FreeBSD-5.X). Most people feel that branch did not go well. As we approached FreeBSD-6.0 my predecessor Scott Long started to advocate us focusing on having specific time based targets for beginning the branching process instead of us focusing on specific feature(s) needing to be completed. For the majority of even large changes like SMP this is feasible in theory (and with a bit more work practice) because most often it can be broken up in steps which is exactly what in the end happend with SMP - we're still reliant on the Giant lock in a few places but it's almost completely gone now. And during that development time the system is still perfectly usable, it's just not fully taking advantage of the improvements (yet). As long as all the developers know (and keep in mind while they're working) the time targets they can make sure any subsystems they're rototilling are stable as we near the branch date. Shifting gears like that takes time. I have a long list of things I need to do better as we approach the time we want the release process for 8.0 to start. And we can wind up with nits like one of the things that slowed down the progress on getting RELENG_7 ready - in the end it was decided one of the subsystems is definitely something we want to implement but it was a little bit too unstable right now to be included in the release so it needed to be backed out and hooks needed to be put in place so it could be added back in when it's ready. The current proposal is that we shoot for doing major branches every 18 months. It remains to be seen if that's reasonable. In general we feel the time based release cycle is the right thing to do but there is a lot of stuff that needs to be adapted to that mode of operation. --=20 Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | --=-9VYnhzCxAutOoi6fzIzY 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 (FreeBSD) iD8DBQBHEOCT/G14VSmup/YRAv1iAJ469soHxhzwE5lOODrhnrZZbuuwbwCfQTzw 9quUmtSBcmX8OBEMi3jB7ps= =6o4w -----END PGP SIGNATURE----- --=-9VYnhzCxAutOoi6fzIzY-- From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 14:57:32 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 D27B716A4DA for ; Sat, 13 Oct 2007 14:57:32 +0000 (UTC) (envelope-from fbsd-st@donut.de) Received: from smtp.free.de (smtp.free.de [193.28.225.103]) by mx1.freebsd.org (Postfix) with ESMTP id 01CAA13C461 for ; Sat, 13 Oct 2007 14:57:31 +0000 (UTC) (envelope-from fbsd-st@donut.de) Received: (qmail 9452 invoked by uid 98); 13 Oct 2007 16:57:30 +0200 Received: from 193.28.225.103 by smtp.free.de (envelope-from , uid 82) with qmail-scanner-1.25 (clamdscan: 0.90.1/3618. Clear:RC:1(193.28.225.103):. Processed in 0.051519 secs); 13 Oct 2007 14:57:30 -0000 X-Qmail-Scanner-Mail-From: fbsd-st@donut.de via smtp.free.de X-Qmail-Scanner: 1.25 (Clear:RC:1(193.28.225.103):. Processed in 0.051519 secs) Received: from smtp.free.de (HELO [192.168.40.3]) (peanuts@[193.28.225.103]) (envelope-sender ) by smtp.free.de (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 13 Oct 2007 16:57:30 +0200 Message-ID: <4710DCDA.1050708@donut.de> Date: Sat, 13 Oct 2007 16:57:30 +0200 From: Rolf Witt User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.6) Gecko/20070728 Thunderbird/2.0.0.6 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: Current@freebsd.org, stable@freebsd.org References: <1191175387.92510.6.camel@shumai.marcuscom.com> <46FFF615.5090108@donut.de> <470447FF.5070409@free.de> In-Reply-To: <470447FF.5070409@free.de> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 13 Oct 2007 15:21:25 +0000 Cc: Subject: Re: panic: ffs_blkfree: freeing free block 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, 13 Oct 2007 14:57:32 -0000 Backtrace from crash tonight (after portsnap cron): # kgdb kernel.debug /var/crash/vmcore.1 kgdb: kvm_nlist(_stopped_cpus): kgdb: kvm_nlist(_stoppcbs): [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Unde fined 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 "i386-marcel-freebsd". Unread portion of the kernel message buffer: dev = ad4s1f, block = 26098960, fs = /usr panic: ffs_blkfree: freeing free block Uptime: 1d10h32m17s Physical memory: 631 MB Dumping 150 MB: 135 119 103 87 71 55 39 23 7 #0 doadump () at pcpu.h:195 195 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) backtrace #0 doadump () at pcpu.h:195 #1 0xc06328a3 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #2 0xc0632aa4 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:563 #3 0xc07d4d10 in ffs_blkfree (ump=0xc323ab00, fs=0xc321c800, devvp=0xc328add0, bno=26098960, size=16384, inum=6500370) at /usr/src/sys/ufs/ffs/ffs_alloc.c:1893 #4 0xc07e8588 in indir_trunc (freeblks=0xc3e12500, dbn=103954304, level=0, lbn=12, countp=0xd9177c4c) at /usr/src/sys/ufs/ffs/ffs_softdep.c:2896 #5 0xc07e8850 in handle_workitem_freeblocks (freeblks=0xc3e12500, flags=0) at /usr/src/sys/ufs/ffs/ffs_softdep.c:2746 #6 0xc07ea0d8 in process_worklist_item (mp=0xc324b7d4, flags=Variable "flags" is not available. ) at /usr/src/sys/ufs/ffs/ffs_softdep.c:963 #7 0xc07eb191 in softdep_process_worklist (mp=0xc324b7d4, full=0) at /usr/src/sys/ufs/ffs/ffs_softdep.c:847 #8 0xc07ed70a in softdep_flush () at /usr/src/sys/ufs/ffs/ffs_softdep.c:758 #9 0xc06121d1 in fork_exit (callout=0xc07ed290 , arg=0x0, frame=0xd9177d38) at /usr/src/sys/kern/kern_fork.c:796 #10 0xc0850170 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:205 (kgdb) # uname -a FreeBSD peanuts.homenet.local 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #121: Thu Oct 11 16:29:05 CEST 2007 rowi@peanuts.homenet.local:/usr/obj/usr/src/sys/PEANUTS i386 Sources from Builddate. Rowi From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 16:12: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 D209B16A418 for ; Sat, 13 Oct 2007 16:12:24 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe13.tele2.se [212.247.155.129]) by mx1.freebsd.org (Postfix) with ESMTP id 7273413C45D for ; Sat, 13 Oct 2007 16:12:24 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [85.19.218.45] (account mc467741@c2i.net [85.19.218.45] verified) by mailfe13.swip.net (CommuniGate Pro SMTP 5.1.10) with ESMTPA id 256868785; Sat, 13 Oct 2007 17:12:22 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Sat, 13 Oct 2007 17:12:42 +0200 User-Agent: KMail/1.9.7 References: <1192219511.13906.56.camel@xenon.stonehenge.sk> <471061A6.9070909@conducive.org> In-Reply-To: <471061A6.9070909@conducive.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710131712.43265.hselasky@c2i.net> Cc: W B Hacker Subject: Re: AMD690G/V issues with 7-current (sata, usb) 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, 13 Oct 2007 16:12:24 -0000 On Saturday 13 October 2007, W B Hacker wrote: > Michal Varga wrote: > > Yesterday I bought an AMD690-based motherboard for a 7-current desktop - > > > > http://www.gigabyte.us/Products/Motherboard/Products_Spec.aspx?ClassValue > >=Motherboard&ProductID=2437&ProductName=GA-MA69VM-S2 > > *Snip* > > > USB: > > Second issue is with USB, the initialization fails every time when there > > is mouse plugged in prior to FreeBSD boot (but not if the mouse is > > plugged later). > > Similar. ASUS P5K, GigaByte G33-DS3R. > > Option the USB mouse support OFF in the BIOS. > > Otherwise, though detected, it is *ALSO* presumed to be 'in use', since the > BIOS deosn't just 'enable' it - it actually starts it, and before the OS > boots. > > If NOT claimed by the BIOS, FreeBSD will find and use it from the defaults > in /etc/rc. No need to even bother with an /etc/rc.conf entry. > > Xorg (if you use it) will generally be au fait with that, even with the > mouse active in a CLI session before you startx or a wm. > > The OS it doing as it should do here - honoring the pre-existing resource > claim. Are you sure about that? I thought that the FreeBSD USB HC drivers always took away control from the BIOS when the USB drivers where loaded. Michal Varga: Do you have USB in the kernel or are you loading the USB modules ? --HPS From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 16:58: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 1162216A46C; Sat, 13 Oct 2007 16:58:18 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from smtp.utwente.nl (unknown [IPv6:2001:610:1908:1000:204:23ff:feb7:ef56]) by mx1.freebsd.org (Postfix) with ESMTP id 8562B13C43E; Sat, 13 Oct 2007 16:58:17 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from lux.student.utwente.nl (lux.student.utwente.nl [130.89.170.81]) by smtp.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id l9DGvl98028916; Sat, 13 Oct 2007 18:57:47 +0200 From: Pieter de Goeje To: freebsd-current@freebsd.org Date: Sat, 13 Oct 2007 18:57:46 +0200 User-Agent: KMail/1.9.7 References: <1191175387.92510.6.camel@shumai.marcuscom.com> <470447FF.5070409@free.de> <4710DCDA.1050708@donut.de> In-Reply-To: <4710DCDA.1050708@donut.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710131857.46963.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No Cc: Rolf Witt Subject: Re: panic: ffs_blkfree: freeing free block 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, 13 Oct 2007 16:58:18 -0000 On Saturday 13 October 2007, Rolf Witt wrote: > Backtrace from crash tonight (after portsnap cron): > > > # uname -a > FreeBSD peanuts.homenet.local 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE > #121: Thu Oct 11 16:29:05 CEST 2007 > rowi@peanuts.homenet.local:/usr/obj/usr/src/sys/PEANUTS i386 > > Sources from Builddate. > > Rowi Eric sent me this patch: http://www.googlebit.com/freebsd/patches/ffs_softdep.c-patch which seems to be working great so far. I am still testing it, but I think it fixed the problem. To apply, cd /usr/src; patch < /path/to/patch and then rebuild the kernel. Cheers, Pieter de Goeje From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 17:11: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 9FA8B16A41B for ; Sat, 13 Oct 2007 17:11:34 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (conducive.net [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id 5F63613C46E for ; Sat, 13 Oct 2007 17:11:33 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:64641 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1IgkWS-0008uE-GF for freebsd-current@freebsd.org; Sat, 13 Oct 2007 17:11:32 +0000 Message-ID: <4710FC44.60103@conducive.net> Date: Sat, 13 Oct 2007 13:11:32 -0400 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <1192219511.13906.56.camel@xenon.stonehenge.sk> <471061A6.9070909@conducive.org> <200710131712.43265.hselasky@c2i.net> In-Reply-To: <200710131712.43265.hselasky@c2i.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: AMD690G/V issues with 7-current (sata, usb) 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, 13 Oct 2007 17:11:34 -0000 Hans Petter Selasky wrote: > On Saturday 13 October 2007, W B Hacker wrote: >> Michal Varga wrote: >>> Yesterday I bought an AMD690-based motherboard for a 7-current desktop - >>> >>> http://www.gigabyte.us/Products/Motherboard/Products_Spec.aspx?ClassValue >>> =Motherboard&ProductID=2437&ProductName=GA-MA69VM-S2 >> *Snip* >> >>> USB: >>> Second issue is with USB, the initialization fails every time when there >>> is mouse plugged in prior to FreeBSD boot (but not if the mouse is >>> plugged later). >> Similar. ASUS P5K, GigaByte G33-DS3R. >> >> Option the USB mouse support OFF in the BIOS. >> >> Otherwise, though detected, it is *ALSO* presumed to be 'in use', since the >> BIOS deosn't just 'enable' it - it actually starts it, and before the OS >> boots. >> >> If NOT claimed by the BIOS, FreeBSD will find and use it from the defaults >> in /etc/rc. No need to even bother with an /etc/rc.conf entry. >> >> Xorg (if you use it) will generally be au fait with that, even with the >> mouse active in a CLI session before you startx or a wm. >> >> The OS it doing as it should do here - honoring the pre-existing resource >> claim. > > Are you sure about that? Certainly sounds 'contrarian' ...but that's what worked. Spent a day or two tracking it, watching /dev/ums0 & the usb devs get loaded, then unloaded, forcing it back in with various /boot/loader.conf and/or manual steps, having the mouse ignored OR go mad.. Commenting in/out default mouse in /etc/rc and trying various manual flags in /etc/rc.conf was no help. Not invoking/not invoking ums in /boot/loader.conf Yet autoload just fine IF unplugged and re-plugged. Tailed /var/log/messages and saw just the right stuff go by. > > I thought that the FreeBSD USB HC drivers always took away control from the > BIOS when the USB drivers where loaded. > It appears to try to do that. 'Always' is subject to a factory recall. dmesg.boot is exactly what one would expect, even to the make & model of each of USB meese tried (Logitech, Kensington, Atech). System would load ums, then unload it. ums0 would appear in /dev, then *disappear*. > Michal Varga: Do you have USB in the kernel or are you loading the USB > modules ? > > --HPS > See above. The BIOS issue has bitten both ways - and more. Lie to it and see if that fixes the problem. HTH, Bill _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 17:20: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 2121416A419 for ; Sat, 13 Oct 2007 17:20:14 +0000 (UTC) (envelope-from oliver@akephalos.de) Received: from mailout11.sul.t-online.com (mailout11.sul.t-online.de [194.25.134.85]) by mx1.freebsd.org (Postfix) with ESMTP id DC13213C447 for ; Sat, 13 Oct 2007 17:20:13 +0000 (UTC) (envelope-from oliver@akephalos.de) Received: from fwd31.aul.t-online.de by mailout11.aul.t-online.de with smtp id 1Igkeq-0001x5-02; Sat, 13 Oct 2007 19:20:12 +0200 Received: from localhost (r914RkZc8t07c5SHFvB2fCVbeusMPz4hYeTy6G6vAKdqVwA0KVt5ZSIEZPKEGd1wdOnPMzXq47@[84.165.124.176]) by fwd31.t-online.de with esmtp id 1Igkel-0LUZ0K0; Sat, 13 Oct 2007 19:20:07 +0200 Date: Sat, 13 Oct 2007 19:20:06 +0200 From: Oliver Herold To: freebsd-current@freebsd.org Message-ID: <20071013172006.GA16773@olymp.home> Mail-Followup-To: freebsd-current@freebsd.org References: <1191175387.92510.6.camel@shumai.marcuscom.com> <470447FF.5070409@free.de> <4710DCDA.1050708@donut.de> <200710131857.46963.pieter@degoeje.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200710131857.46963.pieter@degoeje.nl> User-Agent: Mutt/1.5.16 (2007-06-09) X-ID: r914RkZc8t07c5SHFvB2fCVbeusMPz4hYeTy6G6vAKdqVwA0KVt5ZSIEZPKEGd1wdOnPMzXq47 X-TOI-MSGID: 48a91a96-3f85-4ee0-b43c-840f1c4cfae0 Subject: Re: panic: ffs_blkfree: freeing free block 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, 13 Oct 2007 17:20:14 -0000 Thanks for the patch, I'll try it. Cheers, Oliver On Sat, Oct 13, 2007 at 06:57:46PM +0200, Pieter de Goeje wrote: > On Saturday 13 October 2007, Rolf Witt wrote: > > Backtrace from crash tonight (after portsnap cron): > > > > > > > # uname -a > > FreeBSD peanuts.homenet.local 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE > > #121: Thu Oct 11 16:29:05 CEST 2007 > > rowi@peanuts.homenet.local:/usr/obj/usr/src/sys/PEANUTS i386 > > > > Sources from Builddate. > > > > Rowi > Eric sent me this patch: > http://www.googlebit.com/freebsd/patches/ffs_softdep.c-patch > which seems to be working great so far. I am still testing it, but I think it > fixed the problem. > To apply, cd /usr/src; patch < /path/to/patch and then rebuild the kernel. > > Cheers, > Pieter de Goeje > _______________________________________________ > 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 was in accord with the system so long as it permitted me to function effectively. -- Albert Speer From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 18:36:06 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 4808316A417 for ; Sat, 13 Oct 2007 18:36:06 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.230]) by mx1.freebsd.org (Postfix) with ESMTP id F3EDB13C461 for ; Sat, 13 Oct 2007 18:36:05 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: by wx-out-0506.google.com with SMTP id i29so1028859wxd for ; Sat, 13 Oct 2007 11:36:05 -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:reply-to:organization:user-agent:mime-version:to:cc:subject:x-enigmail-version:openpgp:content-type:from; bh=S+p0ZABTqlFxdw0eYTyuyS+jrRkhNetJLE6YDn02JX4=; b=a1W/HELrCUBQIs/uClZfklWpYlaCcgVubhQkJ6SC7y30m/qZGgd1PVFnX9qdQU5zuaWTC/4fdBN72JZzqW6/CwV2lcofofbD25QdDlGw25KIvhY+0N9tEMC+fmTuNXOsOlC+nh4V6ucWpTuahohE90njD8qWkhnRQ544Y2WOnew= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:reply-to:organization:user-agent:mime-version:to:cc:subject:x-enigmail-version:openpgp:content-type:from; b=W8MScR/De5cR8pZl1Gpgi2tb0LY80FfWWpXPW07y9EZmb2PwaQW1xHCwsHAcxM0MBOlqz2+OoDidoMPOBurJWfBO8CAp/0UI6CWDBgURnsrR1+KANLRy8trOaoananHbrZrGwUgngDFqvCPgNtbnlQf8mtsOfvZUBNCMtphPeS4= Received: by 10.70.115.17 with SMTP id n17mr7537690wxc.1192298904922; Sat, 13 Oct 2007 11:08:24 -0700 (PDT) Received: from island.freebsd.org ( [201.3.196.82]) by mx.google.com with ESMTPS id i17sm2368468wxd.2007.10.13.11.08.22 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 13 Oct 2007 11:08:23 -0700 (PDT) Message-ID: <4711098D.7070001@FreeBSD.org> Date: Sat, 13 Oct 2007 15:08:13 -0300 Organization: FreeBSD User-Agent: Thunderbird 2.0.0.0 (X11/20070521) MIME-Version: 1.0 To: current@freebsd.org X-Enigmail-Version: 0.95.0 OpenPGP: id=53E4CFA8 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig3B72255C210BC3B361CE6D54" From: Marcelo Araujo X-Mailman-Approved-At: Sat, 13 Oct 2007 18:38:28 +0000 Cc: mux@FreeBSD.org, stas@mbsd.msk.ru Subject: ACPI Problem! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: araujo@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Oct 2007 18:36:06 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig3B72255C210BC3B361CE6D54 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi folks! I did update to 7.0-PRERELEASE, but I had many problems with ACPI, after of boot on few minutes my machine freezes per complete! I did test with i8254 timecounter but, I had the same problem, only difference is the machine work more time with i8254! I investigated with another guys and I just changed kern.timecounter.hardware to ACPI-fast. But, On 6.2 I used TSC because is default! I've a laptop HP nx6110, after I changed the timecounter, my machine run fine! NOTE: I can help in any debug or I can do more testing? Best Regards. --=20 Marcelo Araujo (__) araujo@FreeBSD.org \\\'',) http://www.FreeBSD.org \/ \ ^ Power To Server. .\. /_) --------------enig3B72255C210BC3B361CE6D54 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 (FreeBSD) iD8DBQFHEQmSovxJd1Pkz6gRApkqAJ9odhLUx8sIZH4Hq+0f9WepI6hYawCeMu88 mZ/dJcCCDEEcF2LMwpbS2dI= =PyZI -----END PGP SIGNATURE----- --------------enig3B72255C210BC3B361CE6D54-- From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 19: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 684DA16A41A for ; Sat, 13 Oct 2007 19:15:11 +0000 (UTC) (envelope-from varga.michal@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 EB34913C459 for ; Sat, 13 Oct 2007 19:15:10 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so993595nfb for ; Sat, 13 Oct 2007 12:15:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:subject:from:to:cc:content-type:organization:date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=TNbZadgMLBHdWc0CX5uUa1OZ8IDWynyRSogYf6lsZ8U=; b=rWjauThpk1Pl81K7rVgThBr3nBcPJ4wYdiOE/aKXMbwQHgm0A34rZobwzcWzrFvFS/U3WX45Iuj79T7Jv+bNKWznhAZcJ4ynS9WefWWthEQtHeEI08JkXXcFQQqgfHgj6Ef3keiAc7a3YzrgCSDEhXpbGiIEuXafLIwl+b8zZZA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:subject:from:to:cc:content-type:organization:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=uREQCNcTM4YkNivqTi0QLutV/44uZ5nkhmLo4eixMzhlCPML3ZMgNRJzClgbR21mLLvoE3TOfIA4c4JrAOxWd2/OVlyxA8eHox9nqhb9FMkBCDld2TuABhpLrwb/EMMKY+j7rZFdc65P5NqeUZAW17tj/n3RerCby7+lawX6y5Y= Received: by 10.86.81.8 with SMTP id e8mr3481179fgb.1192302909375; Sat, 13 Oct 2007 12:15:09 -0700 (PDT) Received: from ?10.0.100.2? ( [89.176.79.57]) by mx.google.com with ESMTPS id f31sm4472935fkf.2007.10.13.12.15.07 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 13 Oct 2007 12:15:07 -0700 (PDT) From: Michal Varga To: freebsd-current@freebsd.org Content-Type: text/plain Organization: Stonehenge Date: Sat, 13 Oct 2007 21:15:06 +0200 Message-Id: <1192302906.1028.31.camel@xenon.stonehenge.sk> Mime-Version: 1.0 X-Mailer: Evolution 2.10.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: hselasky@c2i.net Subject: GigaByte GA-MA69VM USB+mouse problem [WAS: AMD690G/V issues with 7-current (sata, usb)] 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, 13 Oct 2007 19:15:11 -0000 Sorry to start with a new thread, but nobody CC:ed me as I said before, so I didn't have anything to reply to - >(please CC: me for reply, I'm subscribed with a different email that is >down for maintenance for a few days and didn't want to subscribe again) Fixed now, I resubscribed with this email address. So to the point: > Option the USB mouse support OFF in the BIOS. > Otherwise, though detected, it is *ALSO* presumed to be 'in use', since the > BIOS deosn't just 'enable' it - it actually starts it, and before the OS > boots. Bill, this doesn't change anything, it was one of the first things I tried to do, along with disabling USB2.0 support in bios, etc. But you are right, this option is there, except that I can see no difference with either enabled or disabled. > Michal Varga: Do you have USB in the kernel or are you loading the USB > modules ? I start USB from /boot/loader.conf usb_load="YES" ugen_load="YES" uhid_load="YES" umass_load="YES" ukbd_load="YES" ums_load="YES" ucom_load="YES" uftdi_load="YES" And usbd_enable="YES" in rc.conf. Verbose boot doesn't show anything interesting: [...] ioapic0: routing intpin 7 (ISA IRQ 7) to vector 59 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] sio0 failed to probe at port 0x3f8 irq 4 on isa0 sio1 failed to probe at port 0x2f8 irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) sn0: not probed (disabled) vt0: not probed (disabled) isa_probe_children: probing PnP devices uhub0: device problem (TIMEOUT), disabling port 2 Device configuration finished. Then, after replugging the mouse, everything works fine: ums0: on uhub1 ums0: 7 buttons and Z dir. Is there any other, e.g. some loader.conf tunable, that can show me why usb decided to fail? I've had a Windows drive connected for a while and it doesn't show these symptoms, even better - after I rebooted from Windows 2000 to FreeBSD, the mouse was detected correctly right during the boot, no replug needed (though I did this only once so it may or may not be replicable). Any ideas, what I should try next to possibly resolve this? m. From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 19:56: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 9465516A419 for ; Sat, 13 Oct 2007 19:56:29 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (conducive.net [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id 5781F13C465 for ; Sat, 13 Oct 2007 19:56:29 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:59937 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1Ign63-0009Oi-AV; Sat, 13 Oct 2007 19:56:27 +0000 Message-ID: <471122EB.8090906@conducive.net> Date: Sat, 13 Oct 2007 15:56:27 -0400 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <1192302906.1028.31.camel@xenon.stonehenge.sk> In-Reply-To: <1192302906.1028.31.camel@xenon.stonehenge.sk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Michal Varga Subject: Re: GigaByte GA-MA69VM USB+mouse problem [WAS: AMD690G/V issues with 7-current (sata, usb)] 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, 13 Oct 2007 19:56:29 -0000 Michal Varga wrote: > Sorry to start with a new thread, but nobody CC:ed me as I said before, > so I didn't have anything to reply to - > >> (please CC: me for reply, I'm subscribed with a different email that is >> down for maintenance for a few days and didn't want to subscribe again) > > Fixed now, I resubscribed with this email address. > > > So to the point: > >> Option the USB mouse support OFF in the BIOS. >> Otherwise, though detected, it is *ALSO* presumed to be 'in use', since the >> BIOS deosn't just 'enable' it - it actually starts it, and before the OS >> boots. > > Bill, this doesn't change anything, it was one of the first things I > tried to do, along with disabling USB2.0 support in bios, etc. But you > are right, this option is there, except that I can see no difference > with either enabled or disabled. > Try these in separate login shells: tail -f /var/log/messages - you will be looking for the message announceing ums & usb load ls /dev/u* before unplugging, Again after re-plugging - you are looking for /dev/um0 and at least one /dev/usb(n) changing. > >> Michal Varga: Do you have USB in the kernel or are you loading the USB >> modules ? > > I start USB from /boot/loader.conf > usb_load="YES" > ugen_load="YES" > uhid_load="YES" > umass_load="YES" > ukbd_load="YES" > ums_load="YES" > ucom_load="YES" > uftdi_load="YES" > > And usbd_enable="YES" in rc.conf. Verbose boot doesn't show anything > interesting: > AFAIK, um0 and usb(n) will load by default. IMBW, but an entry in /etc/rc.conf or /boot/loader.conf would only be needed to force them to NOT load. ..which you might just try, as that 'mad mouse' I experienced was a possiblw indication of two drivers competing. > [...] > ioapic0: routing intpin 7 (ISA IRQ 7) to vector 59 > ppc0: [GIANT-LOCKED] > ppc0: [ITHREAD] > sio0 failed to probe at port 0x3f8 irq 4 on isa0 > sio1 failed to probe at port 0x2f8 irq 3 on isa0 > sio2: not probed (disabled) > sio3: not probed (disabled) > sn0: not probed (disabled) > vt0: not probed (disabled) > isa_probe_children: probing PnP devices > uhub0: device problem (TIMEOUT), disabling port 2 > Device configuration finished. > > Then, after replugging the mouse, everything works fine: > ums0: on > uhub1 > ums0: 7 buttons and Z dir. > > Is there any other, e.g. some loader.conf tunable, that can show me why > usb decided to fail? I've had a Windows drive connected for Only diff here was a whole slew of USB stuff was ID'ed w/o error - including the mouse. Yours show only the one uhub0, and that one disabling port 2. Unless you trimmed the output for htis message, that's odd. FWIW - I had left BIOS USB ON, but USB mouse (only) OFF. a while and > it doesn't show these symptoms, even better - after I rebooted from > Windows 2000 to FreeBSD, the mouse was detected correctly right during > the boot, no replug needed (though I did this only once so it may or may > not be replicable). Any ideas, what I should try next to possibly > resolve this? > Try a hard-wired, (i.e. not wireless), and mechanical, not optical mouse. Some optical meese shut themselves OFF part of the time - even if not battery-powered. Laser life issue? Dunno.. Bill From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 20:14: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 B084116A418 for ; Sat, 13 Oct 2007 20:14:39 +0000 (UTC) (envelope-from fbsd-st@donut.de) Received: from smtp.free.de (smtp.free.de [193.28.225.103]) by mx1.freebsd.org (Postfix) with ESMTP id 1033913C469 for ; Sat, 13 Oct 2007 20:14:38 +0000 (UTC) (envelope-from fbsd-st@donut.de) Received: (qmail 44299 invoked by uid 98); 13 Oct 2007 22:14:37 +0200 Received: from 193.28.225.103 by smtp.free.de (envelope-from , uid 82) with qmail-scanner-1.25 (clamdscan: 0.90.1/3618. Clear:RC:1(193.28.225.103):. Processed in 0.045334 secs); 13 Oct 2007 20:14:37 -0000 X-Qmail-Scanner-Mail-From: fbsd-st@donut.de via smtp.free.de X-Qmail-Scanner: 1.25 (Clear:RC:1(193.28.225.103):. Processed in 0.045334 secs) Received: from smtp.free.de (HELO [192.168.40.3]) (peanuts@[193.28.225.103]) (envelope-sender ) by smtp.free.de (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 13 Oct 2007 22:14:37 +0200 Message-ID: <4711272C.4000804@donut.de> Date: Sat, 13 Oct 2007 22:14:36 +0200 From: Rolf Witt User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.6) Gecko/20070728 Thunderbird/2.0.0.6 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: Pieter de Goeje References: <1191175387.92510.6.camel@shumai.marcuscom.com> <470447FF.5070409@free.de> <4710DCDA.1050708@donut.de> <200710131857.46963.pieter@degoeje.nl> In-Reply-To: <200710131857.46963.pieter@degoeje.nl> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 13 Oct 2007 21:40:42 +0000 Cc: freebsd-current@freebsd.org Subject: Re: panic: ffs_blkfree: freeing free block 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, 13 Oct 2007 20:14:39 -0000 Pieter de Goeje wrote: > Eric sent me this patch: > http://www.googlebit.com/freebsd/patches/ffs_softdep.c-patch > which seems to be working great so far. I am still testing it, but I think it > fixed the problem. > To apply, cd /usr/src; patch < /path/to/patch and then rebuild the kernel. Thank you. I will try this patch. cu Rowi