From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 00:30:10 2009 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 A64901065675; Sun, 25 Jan 2009 00:30:10 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 907318FC23; Sun, 25 Jan 2009 00:30:10 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 55D371A3C39; Sat, 24 Jan 2009 16:30:10 -0800 (PST) Date: Sat, 24 Jan 2009 16:30:10 -0800 From: Alfred Perlstein To: Maksim Yevmenkin Message-ID: <20090125003010.GY87077@elvis.mu.org> References: <20090123154336.GJ60948@e.0x20.net> <200901232337.05627.hselasky@c2i.net> <200901240952.21670.hselasky@c2i.net> 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, current@freebsd.org, Hans Petter Selasky Subject: Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 00:30:11 -0000 * Maksim Yevmenkin [090124 01:38] wrote: > > from what i can see you are _NOT_ using _SPIN_ mutexes (aka spin > locks). you are using regular mutexes. let me quote locking(9) man > page > > " > Mutexes > Basically (regular) mutexes will deschedule the thread if the mutex can > not be acquired. A non-spin mutex can be considered to be equivalent to > getting a write lock on an rw_lock (see below), > " > > so, if thread can not get mutex it will be descheduled. this > absolutely can not happen in netgraph! >From a purely academic standpoint... why can't netgraph use standard mutexes? Is there a pointer you can give me? -Alfred From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 00:30:10 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A64901065675; Sun, 25 Jan 2009 00:30:10 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 907318FC23; Sun, 25 Jan 2009 00:30:10 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 55D371A3C39; Sat, 24 Jan 2009 16:30:10 -0800 (PST) Date: Sat, 24 Jan 2009 16:30:10 -0800 From: Alfred Perlstein To: Maksim Yevmenkin Message-ID: <20090125003010.GY87077@elvis.mu.org> References: <20090123154336.GJ60948@e.0x20.net> <200901232337.05627.hselasky@c2i.net> <200901240952.21670.hselasky@c2i.net> 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, current@freebsd.org, Hans Petter Selasky Subject: Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 00:30:11 -0000 * Maksim Yevmenkin [090124 01:38] wrote: > > from what i can see you are _NOT_ using _SPIN_ mutexes (aka spin > locks). you are using regular mutexes. let me quote locking(9) man > page > > " > Mutexes > Basically (regular) mutexes will deschedule the thread if the mutex can > not be acquired. A non-spin mutex can be considered to be equivalent to > getting a write lock on an rw_lock (see below), > " > > so, if thread can not get mutex it will be descheduled. this > absolutely can not happen in netgraph! >From a purely academic standpoint... why can't netgraph use standard mutexes? Is there a pointer you can give me? -Alfred From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 01:33:25 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 335E610656CD; Sun, 25 Jan 2009 01:33:25 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.228]) by mx1.freebsd.org (Postfix) with ESMTP id E9FC18FC0A; Sun, 25 Jan 2009 01:33:24 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so5444307rvf.43 for ; Sat, 24 Jan 2009 17:33:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=nPVaSDwQEDHT9W7x4AZtuQwUvyEStfBPgrrEBE2M+JY=; b=R12KdgDffjoOSlbpRPHPX/zCyVHD6qidnKVvwxVCiyIZHXosJ4ACLrv9Niq7V0UHG2 0UOXas7497QiwZrDYMHnTMh42koVYxBPgdjlW+xXSSpf8D42/jPCtKy+I+ZehrOlpNFZ t8GRuSda8cJbLt9WDbjjFQP+A0Hymp4c1eO8s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=VzTFJwTgPTa1OHSi4kTO8+e6jMUyOo1xhnpA0/CjZ62nWE8vtQ6xixK5G3auzQQRmM STj5l49zduXHD0qd/ZRilZgwpOvrWvrkctOgYu82VFoKh/yBPo7Az0QfPv6wrLWZymby 2C4fvMMhsc2EV3/pcDgeKTapQjyLmzZBpezig= MIME-Version: 1.0 Received: by 10.141.52.3 with SMTP id e3mr588911rvk.262.1232847204711; Sat, 24 Jan 2009 17:33:24 -0800 (PST) In-Reply-To: <20090125003010.GY87077@elvis.mu.org> References: <20090123154336.GJ60948@e.0x20.net> <200901232337.05627.hselasky@c2i.net> <200901240952.21670.hselasky@c2i.net> <20090125003010.GY87077@elvis.mu.org> Date: Sat, 24 Jan 2009 17:33:24 -0800 Message-ID: From: Maksim Yevmenkin To: Alfred Perlstein Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, current@freebsd.org, Hans Petter Selasky Subject: Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 01:33:26 -0000 On Sat, Jan 24, 2009 at 4:30 PM, Alfred Perlstein wrote: > * Maksim Yevmenkin [090124 01:38] wrote: >> >> from what i can see you are _NOT_ using _SPIN_ mutexes (aka spin >> locks). you are using regular mutexes. let me quote locking(9) man >> page >> >> " >> Mutexes >> Basically (regular) mutexes will deschedule the thread if the mutex can >> not be acquired. A non-spin mutex can be considered to be equivalent to >> getting a write lock on an rw_lock (see below), >> " >> >> so, if thread can not get mutex it will be descheduled. this >> absolutely can not happen in netgraph! > > From a purely academic standpoint... why can't netgraph use > standard mutexes? > > Is there a pointer you can give me? well, its not that netgraph can not use mutexes at all. its just that there has to be an understanding between all subsystems that interact with netgraph. its just like Julian said, everybody has to play nice and ensure that control is given back to netgraph as soon as possible. netgraph thread can not be de-scheduled for too long because the same thread services other nodes. in fact, there are other netgraph nodes that use mutexes, there is no way around it. the only rule is that mutexes have to be used prudently. if there is a guarantee that every single code path that is called from netgraph context is "safe" (i.e. any mutexes that are touched in the code path are guaranteed to not cause de-scheduling of netgraph thread for any significant amount of time) then everything is fine. in any case, i really do hope that the patch that i send to Hans Petter today (you were cc'd) is something that we all can agree on. thanks, max From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 01:33:25 2009 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 335E610656CD; Sun, 25 Jan 2009 01:33:25 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.228]) by mx1.freebsd.org (Postfix) with ESMTP id E9FC18FC0A; Sun, 25 Jan 2009 01:33:24 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so5444307rvf.43 for ; Sat, 24 Jan 2009 17:33:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=nPVaSDwQEDHT9W7x4AZtuQwUvyEStfBPgrrEBE2M+JY=; b=R12KdgDffjoOSlbpRPHPX/zCyVHD6qidnKVvwxVCiyIZHXosJ4ACLrv9Niq7V0UHG2 0UOXas7497QiwZrDYMHnTMh42koVYxBPgdjlW+xXSSpf8D42/jPCtKy+I+ZehrOlpNFZ t8GRuSda8cJbLt9WDbjjFQP+A0Hymp4c1eO8s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=VzTFJwTgPTa1OHSi4kTO8+e6jMUyOo1xhnpA0/CjZ62nWE8vtQ6xixK5G3auzQQRmM STj5l49zduXHD0qd/ZRilZgwpOvrWvrkctOgYu82VFoKh/yBPo7Az0QfPv6wrLWZymby 2C4fvMMhsc2EV3/pcDgeKTapQjyLmzZBpezig= MIME-Version: 1.0 Received: by 10.141.52.3 with SMTP id e3mr588911rvk.262.1232847204711; Sat, 24 Jan 2009 17:33:24 -0800 (PST) In-Reply-To: <20090125003010.GY87077@elvis.mu.org> References: <20090123154336.GJ60948@e.0x20.net> <200901232337.05627.hselasky@c2i.net> <200901240952.21670.hselasky@c2i.net> <20090125003010.GY87077@elvis.mu.org> Date: Sat, 24 Jan 2009 17:33:24 -0800 Message-ID: From: Maksim Yevmenkin To: Alfred Perlstein Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, current@freebsd.org, Hans Petter Selasky Subject: Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 01:33:26 -0000 On Sat, Jan 24, 2009 at 4:30 PM, Alfred Perlstein wrote: > * Maksim Yevmenkin [090124 01:38] wrote: >> >> from what i can see you are _NOT_ using _SPIN_ mutexes (aka spin >> locks). you are using regular mutexes. let me quote locking(9) man >> page >> >> " >> Mutexes >> Basically (regular) mutexes will deschedule the thread if the mutex can >> not be acquired. A non-spin mutex can be considered to be equivalent to >> getting a write lock on an rw_lock (see below), >> " >> >> so, if thread can not get mutex it will be descheduled. this >> absolutely can not happen in netgraph! > > From a purely academic standpoint... why can't netgraph use > standard mutexes? > > Is there a pointer you can give me? well, its not that netgraph can not use mutexes at all. its just that there has to be an understanding between all subsystems that interact with netgraph. its just like Julian said, everybody has to play nice and ensure that control is given back to netgraph as soon as possible. netgraph thread can not be de-scheduled for too long because the same thread services other nodes. in fact, there are other netgraph nodes that use mutexes, there is no way around it. the only rule is that mutexes have to be used prudently. if there is a guarantee that every single code path that is called from netgraph context is "safe" (i.e. any mutexes that are touched in the code path are guaranteed to not cause de-scheduling of netgraph thread for any significant amount of time) then everything is fine. in any case, i really do hope that the patch that i send to Hans Petter today (you were cc'd) is something that we all can agree on. thanks, max From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 02:38:17 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96037106566B for ; Sun, 25 Jan 2009 02:38:17 +0000 (UTC) (envelope-from terry@tmk.com) Received: from server.tmk.com (server.tmk.com [204.141.35.63]) by mx1.freebsd.org (Postfix) with ESMTP id 6D7F78FC0A for ; Sun, 25 Jan 2009 02:38:17 +0000 (UTC) (envelope-from terry@tmk.com) Received: from tmk.com by tmk.com (PMDF V6.3-x13 #37010) id <01N4OSG12R2O002BF9@tmk.com> for freebsd-current@freebsd.org; Sat, 24 Jan 2009 21:38:15 -0500 (EST) Date: Sat, 24 Jan 2009 21:21:41 -0500 (EST) From: Terry Kennedy In-reply-to: "Your message dated Sat, 24 Jan 2009 08:17:50 -0800" Sender: Terry Kennedy To: Freddie Cash Message-id: <01N4OT471TUS002BF9@tmk.com> MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=UTF-8 References: <01N4NEOEB7LY00EQWX@tmk.com> Cc: freebsd-current@freebsd.org Subject: Re: Help me select hardware and software options for very large 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: Sun, 25 Jan 2009 02:38:17 -0000 > We did something similar for our off-site, automated backups box. > > One box has 2x 2 GB CompactFlash in IDE adapters, the other has 2x 2 > GB USB flash drives. I assume this was for FreeBSD itself? I was concerned about write cycles (and, to a lesser extent, storage capacity) on CF or USB media. I haven't seen much degradation due to seeks when the FreeBSD space is a separate logical drive on the AMCC controller. That also gets me inherent RAID 6 protection (assuming I carve it from the main batch of drives). > - 64-bit FreeBSD 7.1-RELEASE (started with 7.1-STABLE from August 08) > - UFS for / partition, using gmirror across the two CF/USB drives > - ZFS for everything else This seems to mirror what I'll be doing. It is good to hear that this has been working well for you. > - uses rsync and ssh to backup 83 remote servers everynight, > creating ZFS snapshots every night > - uses rsync to transfer "snapshots" between the two servers In my case, the data will originate on one of the servers (instead of being backups of other servers) and will be synchronized with an off- site server (same hardware) via either 1Gbit or 10Gbit Ethernet (right now I have regular Gigabit hardware), but all I'd need is new add-in cards and an upgrade to the switches at each end of the fiber. The synchonization is currently dones nightly via rdiff-backup. But that package can occasionally loose its marbles, even with < 2TB of data, so I may have to consider alternatives. > The drives on each of the RAID controllers are configured as "Single > Disk Array", so they appear as 24 separate drives to the OS, but still > benefit from the controller's disk cache, management interface, and so > on (as compared to JBOD where it acts like nothing more than a SATA > controller). Hmmm. I was planning to use the hardware RAID 6 on the AMCC, for a number of reasons: 1) that gives me front-panel indications of broken RAID sets, controller-hosted rebuild, and so forth. 2) I'd be using fewer ZFS features (basically, just large partitions and snapshots) so if anything went wrong, I'd have a larger pool of expertise to draw on to fix things (all AMCC users, rather than all FreeBSD ZFS users). Did you consider this option and reject it? If so, can you tell me why? > The drives on one box are configured as 1 large 24-drive raidz2 in ZFS > (this box also has 12x 400 GB drives). > The drives on the other box are configured as 2 separate 11-drive > raidz2 arrays, with 2 hot spares. > The usable space on box boxes is 9 TB. So a single ZFS partition of 8TB would be manageable without long delays for backup snapshots? > Other than a bit of kernel tuning back in August/September, these > boxes have been running nice and smooth. Just waiting for either the > release of FreeBSD 8.0 or an MFC of ZFS v13 to 7-STABLE to get support > for auto-rebuild using hot spares. That's good to hear. What sort of tuning was involved (if it is still needed)? Thanks, Terry Kennedy http://www.tmk.com terry@tmk.com New York, NY USA From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 02:44:07 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B4FB10656D0 for ; Sun, 25 Jan 2009 02:44:07 +0000 (UTC) (envelope-from terry@tmk.com) Received: from server.tmk.com (server.tmk.com [204.141.35.63]) by mx1.freebsd.org (Postfix) with ESMTP id 7394F8FC08 for ; Sun, 25 Jan 2009 02:44:07 +0000 (UTC) (envelope-from terry@tmk.com) Received: from tmk.com by tmk.com (PMDF V6.3-x13 #37010) id <01N4OSG12R2O002BF9@tmk.com> for freebsd-current@freebsd.org; Sat, 24 Jan 2009 21:44:05 -0500 (EST) Date: Sat, 24 Jan 2009 21:38:28 -0500 (EST) From: Terry Kennedy In-reply-to: "Your message dated Sat, 24 Jan 2009 17:18:35 +0000" <74082E20-648A-4B60-AB09-E89CAF0BBB2E@gid.co.uk> Sender: Terry Kennedy To: freebsd-current@freebsd.org Message-id: <01N4OTBFT4YA002BF9@tmk.com> MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=us-ascii; format=flowed; delsp=yes References: <01N4NEOEB7LY00EQWX@tmk.com> Cc: Subject: Re: Help me select hardware and software options for very large 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: Sun, 25 Jan 2009 02:44:08 -0000 > We're using plenty of the closely related S5000PAL m/b with various > Xeons and we're very happy with them. That's good to know. > > p Remote management - Intel Remote Management Module 2 - AXXRM2 > > We tried this and decided it's not worth having (vs the piggybacked > IPMI on that m/b). We found that RMM's power control sometimes doesn't > work (usually when you need it!). Also it's very tricky indeed to use > down an ssh tunnel. OTOH if you need the remote device functionality > there's not really any alternative. I also have out-of-band power control, so that shouldn't be a problem. I assume that anything that borked the system so badly the AXXRMM2 couldn't power it off isn't going to be made worse by pulling the plug. I'll be building one of these systems as a test box before I go and order the parts for the other 2 (primary, backup, hot spare) so if the management card is a wast of money, I'll omit it from the other two builds. At under $170 it's a very small part of the cost of the first build. [I have 4 Tyan M8239's which were completely non-functional on the Tyan S2721-533 motherboards in the current systems, so I definite- ly learned my lesson there.] Terry Kennedy http://www.tmk.com terry@tmk.com New York, NY USA From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 04:08:36 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBFF21065670 for ; Sun, 25 Jan 2009 04:08:36 +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 568698FC12 for ; Sun, 25 Jan 2009 04:08:36 +0000 (UTC) (envelope-from ari@ish.com.au) Received: from [10.29.62.12] (port=51254) by fish.ish.com.au with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1LQwlC-0006tM-2p; Sun, 25 Jan 2009 15:38:15 +1100 Message-Id: <6FE15EE8-19C2-4AEE-8F3D-D7A453A5D201@ish.com.au> From: Aristedes Maniatis To: Terry Kennedy In-Reply-To: <01N4NEOEB7LY00EQWX@tmk.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Sun, 25 Jan 2009 14:57:49 +1100 References: <01N4NEOEB7LY00EQWX@tmk.com> X-Mailer: Apple Mail (2.930.3) Cc: freebsd-current@freebsd.org Subject: Re: Help me select hardware and software options for very large 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: Sun, 25 Jan 2009 04:08:37 -0000 On 24/01/2009, at 1:30 PM, Terry Kennedy wrote: > I'm pretty sure I need ZFS, since even with the 2TB partitions I > have now, > taking snapshots for dump or doing a fsck take approximately forever > 8-) > I'll be using the harware RAID 6 on the 3Ware controller, so I'd > only be > using ZFS to get filesystems larger than 2TB. If you do RAID on the hardware card you get a few downsides: * if your 3ware card dies you'll need a spare of the same model and same BIOS to replace it with. Otherwise you risk your disks not being properly detected. * you don't get the advantage of ZFS check-summing and auto-repairing the data. There are some very nice features in ZFS for doing this on the fly and periodically. You'll want to compare that against what the hardware card gives you. * personally I've found the 3ware utilities much more cumbersome to use than ZFS tools * you can't use RAIDz which has some nice features You'll want to do some tests and see how it performs in different configurations using the type of data and access you plan on implementing. Another person's benchmarks may not necessarily apply to your specific setup, so try it and see. The 3ware cards are still very good to use even if you don't use them in RAID mode. > I've been following the ZFS discussions on -current and -stable, and I > think that while it isn't quite ready yet, it probably will be ready > in > a few months, being available around the same time I get this hardware > asssembled. I recall reading that there will be an import of newer ZFS > code in the near future. That new code is already in Current. Whether it will be ported to 7 is not yet known. On the other hand a great many people are running 7.0/7.1 ZFS in production very successfully with properly tuning. > I think this system may have the most storage ever configured on a > FreeBSD system, and it is probably up near the top in terms of CPU and > memory. I doubt it. 8 core systems are very common these days. I've seen benchmarking with anything up to 64 cores (which I believe is the current FreeBSD limit). As for memory, there was a recent thread with someone installing 64Gb also claiming theirs was the biggest, but others insisting that it certainly wasn't. As for storage, I know Sun sell systems into the petabyte range which I assume these days are powered by ZFS. The above is not to belittle your project; more to reassure you that you aren't anywhere near the limits and you should have no troubles if you tune things properly. Ari Maniatis --------------------------> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 04:16:13 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35B101065673 for ; Sun, 25 Jan 2009 04:16:13 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.176]) by mx1.freebsd.org (Postfix) with ESMTP id 07FFF8FC1E for ; Sun, 25 Jan 2009 04:16:12 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by wa-out-1112.google.com with SMTP id k34so280514wah.27 for ; Sat, 24 Jan 2009 20:16:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=slJo8NUEiH/Ad3EVhtGb2Y0UzM9H3MEBWQMEKYrzF8E=; b=SJ6SP60F++OWxpf/r3VZ0nNIvSAagqvc5SPXB1+492dJIZZGaHQqqSWI8ZIPDweSTB Yjn7Z63zw5ukXGZ0n0OE3Vtwc7hBiA+Rqg35s7IwU9ISNFagSj1huN95ptrznfenCKQO 0P4STF7P9X7u0lMDon1VnqJChekP+WQDBnE3A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=IYJHlJxrO9LWT1Au9vcGoZ5kwOKb6EC5v+qWJXXD4PS2ANXNXrj43UDxIan4JKzyoU D5HP3foOs5qDHopIArYggMEPQGccP3K+XqNR3CRGVAzDSgPwnsL9YyIqI88sP3bzWQYd /878KHg8LjA0APZvqVxftrt4yT+q9Ls50VaR4= MIME-Version: 1.0 Received: by 10.115.106.18 with SMTP id i18mr8534072wam.213.1232856972598; Sat, 24 Jan 2009 20:16:12 -0800 (PST) In-Reply-To: <01N4OT471TUS002BF9@tmk.com> References: <01N4NEOEB7LY00EQWX@tmk.com> <01N4OT471TUS002BF9@tmk.com> Date: Sat, 24 Jan 2009 20:16:12 -0800 Message-ID: From: Freddie Cash To: Terry Kennedy Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Help me select hardware and software options for very large 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: Sun, 25 Jan 2009 04:16:13 -0000 On Sat, Jan 24, 2009 at 6:21 PM, Terry Kennedy wrote: >> We did something similar for our off-site, automated backups box. >> >> One box has 2x 2 GB CompactFlash in IDE adapters, the other has 2x 2 >> GB USB flash drives. > > I assume this was for FreeBSD itself? I was concerned about write > cycles (and, to a lesser extent, storage capacity) on CF or USB > media. I haven't seen much degradation due to seeks when the FreeBSD > space is a separate logical drive on the AMCC controller. That also > gets me inherent RAID 6 protection (assuming I carve it from the main > batch of drives). Correct. On the original box, just / is on the CF. /usr, /var, /tmp, /home, and a bunch of sub-directories of /usr are ZFS filesystems. We also have a /storage directory that we put all the backups in. One the second box (the offsite replica), / and /usr are on the USB, with /home, /var, /tmp, /usr/src, /usr/obj, /usr/ports, /usr/local are all ZFS filesystems. I put /usr onto the USB as well, as I ran into an issue with zpool corruption that couldn't be fixed as not enough apps were available between / and /rescue. 2 GB is still plenty of space for the OS, and it's not like it will be changing all that much. >> The drives on each of the RAID controllers are configured as "Single >> Disk Array", so they appear as 24 separate drives to the OS, but still >> benefit from the controller's disk cache, management interface, and so >> on (as compared to JBOD where it acts like nothing more than a SATA >> controller). > > Hmmm. I was planning to use the hardware RAID 6 on the AMCC, for a > number of reasons: 1) that gives me front-panel indications of broken > RAID sets, controller-hosted rebuild, and so forth. 2) I'd be using > fewer ZFS features (basically, just large partitions and snapshots) > so if anything went wrong, I'd have a larger pool of expertise to draw > on to fix things (all AMCC users, rather than all FreeBSD ZFS users). > > Did you consider this option and reject it? If so, can you tell me > why? Originally, I was going to use hardware RAID6 as well, creating two arrays, and just joing them together with ZFS. But then I figured, if we're going to use ZFS, we may as well use it to the fullest, and use the built-in raidz features. In theory, the performance should be equal or better, due to the CoW feature that eliminates the "write-hole" that plagues RAID5 and RAID6. However, we haven't done any formal benchmarking to see which is actually better: multiple hardware RAID arrays added to the pool, or multiple raidz datasets added to the pool. >> The drives on one box are configured as 1 large 24-drive raidz2 in ZFS >> (this box also has 12x 400 GB drives). > >> The drives on the other box are configured as 2 separate 11-drive >> raidz2 arrays, with 2 hot spares. > >> The usable space on box boxes is 9 TB. > > So a single ZFS partition of 8TB would be manageable without long > delays for backup snapshots? Creating ZFS snapshots is virtually instantaneous. Destroying ZFS snapshots takes a long time, depending on the age and size of the snapshot. But creating and accessing snapshots is nice and quick. The really nice thing about ZFS snapshots is that if you set the ZFS property snapdir to "visible", then you can navigate to //.zfs/snapshot/ and have access to all the snapshots. They'll be listed here, by snapshot name. Just navigate into them as any other directory, and you have full read-only access to the snapshot. >> Other than a bit of kernel tuning back in August/September, these >> boxes have been running nice and smooth. Just waiting for either the >> release of FreeBSD 8.0 or an MFC of ZFS v13 to 7-STABLE to get support >> for auto-rebuild using hot spares. > > That's good to hear. What sort of tuning was involved (if it is still > needed)? Here are the loader.conf settings that we are currently using: # Kernel tunables to set at boot (mostly for ZFS tuning) # Disable DMA for the CF disks # Set kmem to 1.5 GB (the current max on amd64) # Set ZFS Adaptive Read Cache (arc) to about half of kmem (leaving half for the OS) hw.ata.ata_dma=0 kern.hz="100" vfs.zfs.arc_min="512M" vfs.zfs.arc_max="512M" vfs.zfs.prefetch_disable="1" vfs.zfs.zil_disable="0" vm.kmem_size="1596M" vm.kmem_size_max="1596M" Finding the correct arc_min/arc_max and kmem_size_max settings is a bit of a black art, and will depend on the workload for the server. There's a max of 2 GB for kmem_size on FreeBSD 7.x, but the usable max appears to be around 1596 MB, and will change depending on the server. The second box has a max of 1500 MB, for example (won't boot with anything higher). Some people run with an arc_max of 64 MB, we ran with it set to 2 GB for a bit (8 GB of RAM in the box). Basically, we just tune it down a little bit everytime we hit a "kmem_map too small" kernel panic. FreeBSD 8.0 won't have these limitations (kmem_max is 512 GB), and ZFS v13 will auto-tune itself as much as possible. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 06:34:45 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 101341065672 for ; Sun, 25 Jan 2009 06:34:45 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail13.syd.optusnet.com.au (mail13.syd.optusnet.com.au [211.29.132.194]) by mx1.freebsd.org (Postfix) with ESMTP id 96F598FC18 for ; Sun, 25 Jan 2009 06:34:44 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-216-167.belrs3.nsw.optusnet.com.au [122.106.216.167]) by mail13.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n0P6YgQj005484 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 25 Jan 2009 17:34:42 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id n0P6YfOg024480; Sun, 25 Jan 2009 17:34:41 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id n0P6YfE5024479; Sun, 25 Jan 2009 17:34:41 +1100 (EST) (envelope-from peter) Date: Sun, 25 Jan 2009 17:34:41 +1100 From: Peter Jeremy To: Maxim Sobolev Message-ID: <20090125063441.GC1755@server.vk2pj.dyndns.org> References: <200901241638.18591.hselasky@c2i.net> <497B7A80.4060002@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sHrvAb52M6C8blB9" Content-Disposition: inline In-Reply-To: <497B7A80.4060002@FreeBSD.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-current@freebsd.org Subject: Re: Prblem whit USB in FreeBSD 8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 06:34:45 -0000 --sHrvAb52M6C8blB9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2009-Jan-24 12:30:56 -0800, Maxim Sobolev wrote: >I wonder if this situation can be handled automatically. To my ignorant=20 >view, our USB mass storage driver can try sending "synchronize cache"=20 >command and if that fails then failback to the NO_SYNCHRONIZE_CACHE=20 >behavior. This has been discussed in the past. The problem is that some drives lock up when you send a "synchronize cache" command so this isn't a general solution. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --sHrvAb52M6C8blB9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkl8CAEACgkQ/opHv/APuIdhhgCeM1uQYIeBp9Ky29CdSFN3NoOl JwwAmwbFF49NWvJy2a6OUzGtQ2fUuite =23pu -----END PGP SIGNATURE----- --sHrvAb52M6C8blB9-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 07:18:15 2009 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 8AC2A106564A for ; Sun, 25 Jan 2009 07:18:15 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id 4FFEC8FC24 for ; Sun, 25 Jan 2009 07:18:15 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id F19F773098; Sun, 25 Jan 2009 08:23:41 +0100 (CET) Date: Sun, 25 Jan 2009 08:23:41 +0100 From: Luigi Rizzo To: Giorgos Keramidas Message-ID: <20090125072341.GA22319@onelab2.iet.unipi.it> References: <20090123233611.GA58363@onelab2.iet.unipi.it> <877i4lo046.fsf@kobe.laptop> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <877i4lo046.fsf@kobe.laptop> User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org Subject: Re: quickly build a single program ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 07:18:15 -0000 On Sat, Jan 24, 2009 at 05:26:33AM +0200, Giorgos Keramidas wrote: > On Sat, 24 Jan 2009 00:36:11 +0100, Luigi Rizzo wrote: > > how hard would it be to modify the build scripts so that they only try > > to rebuild a single program from a tree where you already made a buildworld ? > > > > i usually do modifications to a single program at a time and it is > > slightly annoying to wait for the build process to scan through all > > the already-built programs to find there is nothing to do for them. > > Most of the time, when there are small changes I just change into the > program's directory and `make'. But this doesn't work when there are > dependencies with other parts of buildworld. ... or when you work on a different tree than the one installed, unless there is an easy way to set the environment variables to point to the correct toolchain and headers/libraries ? Maybe that's all i need in the end. cheers luigi From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 07:41:38 2009 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 7219A106566B for ; Sun, 25 Jan 2009 07:41:38 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id D5F368FC0A for ; Sun, 25 Jan 2009 07:41:37 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (adsl205-109.kln.forthnet.gr [79.103.18.109]) (authenticated bits=128) by igloo.linux.gr (8.14.3/8.14.3/Debian-5) with ESMTP id n0P7fObn013529 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 25 Jan 2009 09:41:30 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.3/8.14.3) with ESMTP id n0P7fO9S025429; Sun, 25 Jan 2009 09:41:24 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.14.3/8.14.3/Submit) id n0P7fMbR025428; Sun, 25 Jan 2009 09:41:22 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) From: Giorgos Keramidas To: Luigi Rizzo References: <20090123233611.GA58363@onelab2.iet.unipi.it> <877i4lo046.fsf@kobe.laptop> <20090125072341.GA22319@onelab2.iet.unipi.it> Date: Sun, 25 Jan 2009 09:41:22 +0200 In-Reply-To: <20090125072341.GA22319@onelab2.iet.unipi.it> (Luigi Rizzo's message of "Sun, 25 Jan 2009 08:23:41 +0100") Message-ID: <877i4j7rz1.fsf@kobe.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-MailScanner-ID: n0P7fObn013529 X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.991, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.41, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: current@freebsd.org Subject: Re: quickly build a single program ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 07:41:38 -0000 On Sun, 25 Jan 2009 08:23:41 +0100, Luigi Rizzo wrote: >On Sat, Jan 24, 2009 at 05:26:33AM +0200, Giorgos Keramidas wrote: >>On Sat, 24 Jan 2009 00:36:11 +0100, Luigi Rizzo wrote: >>> how hard would it be to modify the build scripts so that they only try >>> to rebuild a single program from a tree where you already made a buildworld ? >>> >>> i usually do modifications to a single program at a time and it is >>> slightly annoying to wait for the build process to scan through all >>> the already-built programs to find there is nothing to do for them. >> >> Most of the time, when there are small changes I just change into the >> program's directory and `make'. But this doesn't work when there are >> dependencies with other parts of buildworld. > > ... or when you work on a different tree than the one installed, > unless there is an easy way to set the environment variables > to point to the correct toolchain and headers/libraries ? > > Maybe that's all i need in the end. Yes, that would probably be nice. We have `make buildenv' now, but IIRC it does not actually *build* anything. It only set up environment vars to point to the correct places in /usr/obj and spawns sh. I think it may be useful to add a few bits in `Makefile.inc1' to actually *build* the stages up to _depend with -DNO_CLEAN and then spawn a shell. That would be cool :-) From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 08:30:13 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 941B61065674 for ; Sun, 25 Jan 2009 08:30:13 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outB.internet-mail-service.net (outb.internet-mail-service.net [216.240.47.225]) by mx1.freebsd.org (Postfix) with ESMTP id 739EC8FC14 for ; Sun, 25 Jan 2009 08:30:13 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 1CB1A24E1; Sun, 25 Jan 2009 00:30:13 -0800 (PST) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id 824FA2D600D; Sun, 25 Jan 2009 00:30:12 -0800 (PST) Message-ID: <497C2318.3030108@elischer.org> Date: Sun, 25 Jan 2009 00:30:16 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Alfred Perlstein References: <20090123154336.GJ60948@e.0x20.net> <200901232337.05627.hselasky@c2i.net> <200901240952.21670.hselasky@c2i.net> <20090125003010.GY87077@elvis.mu.org> In-Reply-To: <20090125003010.GY87077@elvis.mu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Hans Petter Selasky , current@freebsd.org, Maksim Yevmenkin Subject: Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 08:30:13 -0000 Alfred Perlstein wrote: > * Maksim Yevmenkin [090124 01:38] wrote: >> from what i can see you are _NOT_ using _SPIN_ mutexes (aka spin >> locks). you are using regular mutexes. let me quote locking(9) man >> page >> >> " >> Mutexes >> Basically (regular) mutexes will deschedule the thread if the mutex can >> not be acquired. A non-spin mutex can be considered to be equivalent to >> getting a write lock on an rw_lock (see below), >> " >> >> so, if thread can not get mutex it will be descheduled. this >> absolutely can not happen in netgraph! > >>From a purely academic standpoint... why can't netgraph use > standard mutexes? > > Is there a pointer you can give me? see my later post.. it can, but you really want to be sure that you know who you are contending with.. > > -Alfred > _______________________________________________ > 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 Jan 25 08:40:31 2009 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 BD3F6106566B for ; Sun, 25 Jan 2009 08:40:31 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outU.internet-mail-service.net (outu.internet-mail-service.net [216.240.47.244]) by mx1.freebsd.org (Postfix) with ESMTP id 9E9F58FC1B for ; Sun, 25 Jan 2009 08:40:31 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 1CB1A24E1; Sun, 25 Jan 2009 00:30:13 -0800 (PST) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id 824FA2D600D; Sun, 25 Jan 2009 00:30:12 -0800 (PST) Message-ID: <497C2318.3030108@elischer.org> Date: Sun, 25 Jan 2009 00:30:16 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Alfred Perlstein References: <20090123154336.GJ60948@e.0x20.net> <200901232337.05627.hselasky@c2i.net> <200901240952.21670.hselasky@c2i.net> <20090125003010.GY87077@elvis.mu.org> In-Reply-To: <20090125003010.GY87077@elvis.mu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Hans Petter Selasky , current@freebsd.org, Maksim Yevmenkin Subject: Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 08:40:32 -0000 Alfred Perlstein wrote: > * Maksim Yevmenkin [090124 01:38] wrote: >> from what i can see you are _NOT_ using _SPIN_ mutexes (aka spin >> locks). you are using regular mutexes. let me quote locking(9) man >> page >> >> " >> Mutexes >> Basically (regular) mutexes will deschedule the thread if the mutex can >> not be acquired. A non-spin mutex can be considered to be equivalent to >> getting a write lock on an rw_lock (see below), >> " >> >> so, if thread can not get mutex it will be descheduled. this >> absolutely can not happen in netgraph! > >>From a purely academic standpoint... why can't netgraph use > standard mutexes? > > Is there a pointer you can give me? see my later post.. it can, but you really want to be sure that you know who you are contending with.. > > -Alfred > _______________________________________________ > 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 Jan 25 08:54:05 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CAEF61065670; Sun, 25 Jan 2009 08:54:05 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id B468B8FC0A; Sun, 25 Jan 2009 08:54:05 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 5AC911A3C39; Sun, 25 Jan 2009 00:54:05 -0800 (PST) Date: Sun, 25 Jan 2009 00:54:05 -0800 From: Alfred Perlstein To: Maksim Yevmenkin Message-ID: <20090125085405.GA87077@elvis.mu.org> References: <20090123154336.GJ60948@e.0x20.net> <200901232337.05627.hselasky@c2i.net> <200901240952.21670.hselasky@c2i.net> <20090125003010.GY87077@elvis.mu.org> 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, current@freebsd.org, Hans Petter Selasky Subject: Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 08:54:06 -0000 * Maksim Yevmenkin [090124 17:33] wrote: > On Sat, Jan 24, 2009 at 4:30 PM, Alfred Perlstein wrote: > > > > From a purely academic standpoint... why can't netgraph use > > standard mutexes? > > > > Is there a pointer you can give me? > > well, its not that netgraph can not use mutexes at all. its just that > there has to be an understanding between all subsystems that interact > with netgraph. its just like Julian said, everybody has to play nice > and ensure that control is given back to netgraph as soon as possible. > netgraph thread can not be de-scheduled for too long because the same > thread services other nodes. in fact, there are other netgraph nodes > that use mutexes, there is no way around it. the only rule is that > mutexes have to be used prudently. if there is a guarantee that every > single code path that is called from netgraph context is "safe" (i.e. > any mutexes that are touched in the code path are guaranteed to not > cause de-scheduling of netgraph thread for any significant amount of > time) then everything is fine. > > in any case, i really do hope that the patch that i send to Hans > Petter today (you were cc'd) is something that we all can agree on. FWIW, with the exception of Giant, all normal mutexes have this guarantee. Giant actually sort of has this guarantee, however it may be held for long periods of _activity_. You can't "block" with a mutex, hence you'll never be behind a sleeping process, only a running process or tandem of running processes. -- - Alfred Perlstein From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 08:54:05 2009 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 CAEF61065670; Sun, 25 Jan 2009 08:54:05 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id B468B8FC0A; Sun, 25 Jan 2009 08:54:05 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 5AC911A3C39; Sun, 25 Jan 2009 00:54:05 -0800 (PST) Date: Sun, 25 Jan 2009 00:54:05 -0800 From: Alfred Perlstein To: Maksim Yevmenkin Message-ID: <20090125085405.GA87077@elvis.mu.org> References: <20090123154336.GJ60948@e.0x20.net> <200901232337.05627.hselasky@c2i.net> <200901240952.21670.hselasky@c2i.net> <20090125003010.GY87077@elvis.mu.org> 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, current@freebsd.org, Hans Petter Selasky Subject: Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 08:54:06 -0000 * Maksim Yevmenkin [090124 17:33] wrote: > On Sat, Jan 24, 2009 at 4:30 PM, Alfred Perlstein wrote: > > > > From a purely academic standpoint... why can't netgraph use > > standard mutexes? > > > > Is there a pointer you can give me? > > well, its not that netgraph can not use mutexes at all. its just that > there has to be an understanding between all subsystems that interact > with netgraph. its just like Julian said, everybody has to play nice > and ensure that control is given back to netgraph as soon as possible. > netgraph thread can not be de-scheduled for too long because the same > thread services other nodes. in fact, there are other netgraph nodes > that use mutexes, there is no way around it. the only rule is that > mutexes have to be used prudently. if there is a guarantee that every > single code path that is called from netgraph context is "safe" (i.e. > any mutexes that are touched in the code path are guaranteed to not > cause de-scheduling of netgraph thread for any significant amount of > time) then everything is fine. > > in any case, i really do hope that the patch that i send to Hans > Petter today (you were cc'd) is something that we all can agree on. FWIW, with the exception of Giant, all normal mutexes have this guarantee. Giant actually sort of has this guarantee, however it may be held for long periods of _activity_. You can't "block" with a mutex, hence you'll never be behind a sleeping process, only a running process or tandem of running processes. -- - Alfred Perlstein From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 09:19:29 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 387C9106564A; Sun, 25 Jan 2009 09:19:29 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by mx1.freebsd.org (Postfix) with ESMTP id 4B4FC8FC1A; Sun, 25 Jan 2009 09:19:08 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so3806519fgb.35 for ; Sun, 25 Jan 2009 01:18:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=3TZPKZmSaYW+lJfox5xMd6lbQUoVtT6Ts8WrlGAZazE=; b=OPmExmhNs1i0J0Fjam3xDjBtLf6TKYAhh869AuVQbnjIBKDUgNFKmF6NiC+JdYxRD7 2P0bmm61GFEoUpM/o0ndkXyYm7KP9ONBnTAUx4I7Wucul6AJjoraLtYBkw+txYBa0lhm YvFdafVTBfGiMmeyCtVF08tqoIEMNkNybgRfE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=aDOH+Pq3DNZcTGnjV2cx83r6/9qeCEm5GlvLhSHhDBybSBbpbP88PssdufChyctSSm hJXXduwe24YwMkRhEPiMtKavPDruvRf7LVV1m1R8VdOn1Vatm1aTFocPArvT3CYxRFkM mrKvOTGsxpsNcWXP3cLbmFiOuHYNyPz7tpErs= MIME-Version: 1.0 Received: by 10.181.28.15 with SMTP id f15mr656223bkj.75.1232875128884; Sun, 25 Jan 2009 01:18:48 -0800 (PST) In-Reply-To: <200901141804.31326.shoesoft@gmx.net> References: <7d6fde3d0901091705v6eb4c7bfxe23708f8651e2125@mail.gmail.com> <496C8A59.6090301@gmx.de> <496CA9E3.90700@mail.zedat.fu-berlin.de> <200901141804.31326.shoesoft@gmx.net> Date: Sun, 25 Jan 2009 01:18:48 -0800 Message-ID: <7d6fde3d0901250118v153b8442v97be05f4fd897928@mail.gmail.com> From: Garrett Cooper To: Stefan Ehmann Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Christoph Mallon , "O. Hartmann" , freebsd-current@freebsd.org, freebsd-x11 Subject: Re: X becomes unresponsive with nvidia and hardlocks with gdb (was Re: X becomes unresponsive with nvidia / xscreensaver and desktop panics) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 09:19:29 -0000 On Wed, Jan 14, 2009 at 9:04 AM, Stefan Ehmann wrote: > On Tuesday 13 January 2009 15:49:07 O. Hartmann wrote: >> Christoph Mallon wrote: >> > O. Hartmann schrieb: >> >> Garrett Cooper wrote: >> >>> - I've rebuilt my xorg-server a few times and it's still claiming that >> >>> it was built with 7.1-RC2 -_-... >> >>> - I can get the Xorg server to go full tilt by just compiling >> >>> something, like buildworld, via an xterm. >> >> >> >> I also experienced this, but not only with the mentioned 'nv' driver, >> >> also with 'vesa'. Compiling a kernel or making buildworld, even with no >> >> -jX option, turns the box sometimes in a state of unresponseness. Mouse >> >> jumping, no keyboard response, sometimes for more than a minute. This >> >> happens on a FBSD 8.0-CUR/AMD64 UP box and it also happens on a FreeBSD >> >> 7.1-STABLE box (also amd64, 4 cores). But on SMP boxes I reralized that >> >> the problem does not impact that harsh as seen on UP boxes. >> >> We also had several P4 32bit machines with HTT enabled around, one of >> >> them was built with FreeBSD 7.1-STABLE AND Xorg and I never realized the >> >> bumpy X11, even when disabling HTT and running UP and Xorgs vesa driver. >> >> >> >> Well, it also seems to make no difference whether I use USB2 stack (in >> >> FreeBSD 8) or the old one. >> > >> > I regularly can observe that batch jobs like large compile jobs get a >> > lower priority number (i.e. they get preferred by the scheduler) than >> > X on my UP machine with SCHED_ULE (7.0-STABLE from early July). Just a >> > bit X activity (switching desktops, scrolling in a browser etc.) is >> > enough to make its priority number higher than that of make+gcc. >> > This also causes interesting cascades like stuttering music: >> > - gcc preferred over X >> > - X cannot redraw xterm fast enough >> > - buffer of xterm fills >> > - mplayer cannot write its status line to xterm and blocks >> > - because mplayer blocks it cannot feed more data to the sound device >> > - music stutters >> >> ... try moving/draging a xterm rapidly over your screen while playing >> music, copying a file or encoding, decoding or even compiling something. >> In my case, suddenly those activities stop running. It is sometimes only >> noticable when listening to music. >> I realised those ghost-stops also without X11 - when high disk I/O >> and/or network I/O happens. This is even harsh on a NFS-server. As I >> mentioned, this is significantly on UP boxes, but can also be watched on >> some slower/older SMP hardware (both with FreeBSD 7.1-STABLE AND FreeBSD >> 8.0-CURRENT). > > I've been observing this since 7.0 IIRC. With 6.x I never noticed this. > > When performing a portupgrade or running mencoder everything becomes very > sluggish sometimes. E.g. Redrawing windows takes several second, even > moderately sized videos can't be played back smoothly anymore. 4BSD seems to > be better than ULE but still not perfect. > > As a workaround I run load intensive tasks with idprio(1), nice(1) doesn't > really help that much. > > Unfortunately I've never been able to reduce this to a simple reproducible > test case. E.g. if Xorg has to be involved and what kind of load causes the > problems. > > But my conclusions were similar to your findings. Simply using lots of CPU > doesn't affect the responsiveness of the system. But when high disk or network > I/O is involved the problem occurs. > > Also, I figured this would not happen on every system. Otherwise there would > have been more complaints on the lists. This also seems to correlate with your > statement that the problem is significant on UP hardware, I run a 4+ years old > Athlon XP CPU. I just upgraded Xorg and manually patched the nvidia-driver Makefile to pick up the latest version from nvidia's site and I'm no longer seeing the high CPU issues with compiling like I used to, so this very problem may have gone away... The release notes for the newest driver hint at a performance regression which was caught after the fact, as well as the fact that they enabled more card features and fixed a few bugs. I submitted a ports PR for this, so hopefully it'll hit the tree in a few days. The other nvidia-driver sets should probably be updated as well. Cheers :), -Garrett From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 09:24:48 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AAEE41065676 for ; Sun, 25 Jan 2009 09:24:48 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outG.internet-mail-service.net (outg.internet-mail-service.net [216.240.47.230]) by mx1.freebsd.org (Postfix) with ESMTP id 874AD8FC22 for ; Sun, 25 Jan 2009 09:24:48 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 1E4B124D0; Sun, 25 Jan 2009 01:24:48 -0800 (PST) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id BB4002D6004; Sun, 25 Jan 2009 01:24:47 -0800 (PST) Message-ID: <497C2FE3.6050304@elischer.org> Date: Sun, 25 Jan 2009 01:24:51 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Alfred Perlstein References: <20090123154336.GJ60948@e.0x20.net> <200901232337.05627.hselasky@c2i.net> <200901240952.21670.hselasky@c2i.net> <20090125003010.GY87077@elvis.mu.org> <20090125085405.GA87077@elvis.mu.org> In-Reply-To: <20090125085405.GA87077@elvis.mu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Hans Petter Selasky , current@freebsd.org, Maksim Yevmenkin Subject: Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 09:24:49 -0000 Alfred Perlstein wrote: > * Maksim Yevmenkin [090124 17:33] wrote: >> On Sat, Jan 24, 2009 at 4:30 PM, Alfred Perlstein wrote: >>> From a purely academic standpoint... why can't netgraph use >>> standard mutexes? >>> >>> Is there a pointer you can give me? >> well, its not that netgraph can not use mutexes at all. its just that >> there has to be an understanding between all subsystems that interact >> with netgraph. its just like Julian said, everybody has to play nice >> and ensure that control is given back to netgraph as soon as possible. >> netgraph thread can not be de-scheduled for too long because the same >> thread services other nodes. in fact, there are other netgraph nodes >> that use mutexes, there is no way around it. the only rule is that >> mutexes have to be used prudently. if there is a guarantee that every >> single code path that is called from netgraph context is "safe" (i.e. >> any mutexes that are touched in the code path are guaranteed to not >> cause de-scheduling of netgraph thread for any significant amount of >> time) then everything is fine. >> >> in any case, i really do hope that the patch that i send to Hans >> Petter today (you were cc'd) is something that we all can agree on. > > FWIW, with the exception of Giant, all normal mutexes have this > guarantee. Giant actually sort of has this guarantee, however it > may be held for long periods of _activity_. > > You can't "block" with a mutex, hence you'll never be behind > a sleeping process, only a running process or tandem of running > processes. > well there is blocking and there is blocking.. if you block on a thread that is going to switch two pointers atomically then that is ok as this si not going to harm throughput of netgraph as a whole. If you block for a thread that is allocating memory, and re-arange the routing table or something large like that, you can really screw up netgraph's thoughput as yo are blocking a thread that ahs to do work in other places too and because your node has blocked it, other nodes are getting starved. See my mail to arch on this topic.. I'm suggesting that there be a flag for mutexes that label them as a 'leaf' mutex. By which I mean the mutex 'call graph' will never see thes as anything as a terminal node. Netgraph has no problems with using mutexes in this way, but getting on a chain of mutexes some of which may take a while to clear ca totally screw it's usefulness. From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 09:24:48 2009 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 AEEA91065677 for ; Sun, 25 Jan 2009 09:24:48 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outF.internet-mail-service.net (outf.internet-mail-service.net [216.240.47.229]) by mx1.freebsd.org (Postfix) with ESMTP id 8B9F38FC23 for ; Sun, 25 Jan 2009 09:24:48 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 1E4B124D0; Sun, 25 Jan 2009 01:24:48 -0800 (PST) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id BB4002D6004; Sun, 25 Jan 2009 01:24:47 -0800 (PST) Message-ID: <497C2FE3.6050304@elischer.org> Date: Sun, 25 Jan 2009 01:24:51 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Alfred Perlstein References: <20090123154336.GJ60948@e.0x20.net> <200901232337.05627.hselasky@c2i.net> <200901240952.21670.hselasky@c2i.net> <20090125003010.GY87077@elvis.mu.org> <20090125085405.GA87077@elvis.mu.org> In-Reply-To: <20090125085405.GA87077@elvis.mu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Hans Petter Selasky , current@freebsd.org, Maksim Yevmenkin Subject: Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 09:24:49 -0000 Alfred Perlstein wrote: > * Maksim Yevmenkin [090124 17:33] wrote: >> On Sat, Jan 24, 2009 at 4:30 PM, Alfred Perlstein wrote: >>> From a purely academic standpoint... why can't netgraph use >>> standard mutexes? >>> >>> Is there a pointer you can give me? >> well, its not that netgraph can not use mutexes at all. its just that >> there has to be an understanding between all subsystems that interact >> with netgraph. its just like Julian said, everybody has to play nice >> and ensure that control is given back to netgraph as soon as possible. >> netgraph thread can not be de-scheduled for too long because the same >> thread services other nodes. in fact, there are other netgraph nodes >> that use mutexes, there is no way around it. the only rule is that >> mutexes have to be used prudently. if there is a guarantee that every >> single code path that is called from netgraph context is "safe" (i.e. >> any mutexes that are touched in the code path are guaranteed to not >> cause de-scheduling of netgraph thread for any significant amount of >> time) then everything is fine. >> >> in any case, i really do hope that the patch that i send to Hans >> Petter today (you were cc'd) is something that we all can agree on. > > FWIW, with the exception of Giant, all normal mutexes have this > guarantee. Giant actually sort of has this guarantee, however it > may be held for long periods of _activity_. > > You can't "block" with a mutex, hence you'll never be behind > a sleeping process, only a running process or tandem of running > processes. > well there is blocking and there is blocking.. if you block on a thread that is going to switch two pointers atomically then that is ok as this si not going to harm throughput of netgraph as a whole. If you block for a thread that is allocating memory, and re-arange the routing table or something large like that, you can really screw up netgraph's thoughput as yo are blocking a thread that ahs to do work in other places too and because your node has blocked it, other nodes are getting starved. See my mail to arch on this topic.. I'm suggesting that there be a flag for mutexes that label them as a 'leaf' mutex. By which I mean the mutex 'call graph' will never see thes as anything as a terminal node. Netgraph has no problems with using mutexes in this way, but getting on a chain of mutexes some of which may take a while to clear ca totally screw it's usefulness. From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 10:39:05 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 378CA106570E; Sun, 25 Jan 2009 10:39:05 +0000 (UTC) To: freebsd-current@freebsd.org Date: Sun, 25 Jan 2009 10:39:05 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20090125103905.378CA106570E@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Subject: net80211 hostap vs powersave X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 10:39:06 -0000 So. Recently, I decided to trade in my Hiptop for a Blackberry Curve 8320. It does many spiffy things. I even got it to do tethering with FreeBSD via USB. (See here for more details: http://www.freebsd.org/~wpaul/bb/ ) There was just thing I had trouble with. The 8320 is a wifi-enabled phone, and I thought it would be nice to use it with my wifi setup at home. My "access point" is actually a soekris board running FreeBSD 7.0 with a Linksys cardbus adapter that uses an Atheros 5212 chipset. Normally, I run it in adhoc mode. Unfortunately, for whatever the reason, the Blackberry doesn't support adhoc networks: you can only connect to BSS networks. "Well, ok," says I, "I guess I'll set ath0 to hostap mode instead." But that didn't work quite right either. The Blackberry could detect the AP now, and it could associate and acquire a DHCP lease, but after that, it seemed that it would only send frames, not receive them. Actually, it seemed that it was the ath0 interface that wasn't sending the frames: using tcpdump I could see traffic coming in, but nothing going out. A bit of investigation showed that the problem had to do with the fact that the Blackberry operates in powersave mode. This is sensible enough since it's a portable device with limited battery power. However it doesn't offer the option to turn it off. It looked like either the ath(4) driver or net80211 had a problem supporting power save in hostap mode. I dug around a bit, and there was one thing that looked a little strange to me. In FreeBSD 7.0, the ieee80211_power.c module has the following two functions: void ieee80211_power_attach(struct ieee80211com *ic) { if (ic->ic_opmode == IEEE80211_M_HOSTAP || ic->ic_opmode == IEEE80211_M_IBSS) { /* NB: driver should override */ ic->ic_set_tim = ieee80211_set_tim; } } void ieee80211_power_lateattach(struct ieee80211com *ic) { /* * Allocate these only if needed. Beware that we * know adhoc mode doesn't support ATIM yet... */ if (ic->ic_opmode == IEEE80211_M_HOSTAP) { ic->ic_tim_len = howmany(ic->ic_max_aid,8) * sizeof(uint8_t); MALLOC(ic->ic_tim_bitmap, uint8_t *, ic->ic_tim_len, M_DEVBUF, M_NOWAIT | M_ZERO); if (ic->ic_tim_bitmap == NULL) { printf("%s: no memory for TIM bitmap!\n", __func__); /* XXX good enough to keep from crashing? */ ic->ic_tim_len = 0; } } } Both of these are effectivelly called from the driver's attach routine, which is run early on when an interface is initialized. Here's what's strange. Both functions hook up some of the plumbing that powersave requires, but only if ic_opmode == IEEE80211_M_HOSTAP (or in the case of ieee80211_power_attach, if ic_opmode is either IEEE80211_M_HOSTAP or IEEE80211_M_IBSS). But none of the wireless drivers set ic_opmode to IEEE80211_M_HOSTAP or IEEE80211_M_IBSS by default: it's up to the user or a startup script to change the operating mode to one of these after the interfaces are attached. This means that at the time these routines are run, ic_opmode can _never_ be IEEE80211_M_HOSTAP or IEEE80211_M_IBSS, so the required setup never happens. I changed these functions to look like this: void ieee80211_power_attach(struct ieee80211com *ic) { if (ic->ic_caps & IEEE80211_C_HOSTAP || ic->ic_caps & IEEE80211_C_IBSS) { /* NB: driver should override */ ic->ic_set_tim = ieee80211_set_tim; } } void ieee80211_power_lateattach(struct ieee80211com *ic) { /* * Allocate these only if needed. Beware that we * know adhoc mode doesn't support ATIM yet... */ if (ic->ic_caps & IEEE80211_C_HOSTAP) { ic->ic_tim_len = howmany(ic->ic_max_aid,8) * sizeof(uint8_t); MALLOC(ic->ic_tim_bitmap, uint8_t *, ic->ic_tim_len, M_DEVBUF, M_NOWAIT | M_ZERO); if (ic->ic_tim_bitmap == NULL) { printf("%s: no memory for TIM bitmap!\n", __func__); /* XXX good enough to keep from crashing? */ ic->ic_tim_len = 0; } } } Note that now they test the interface capabilities (ic_caps) rather than the current operating mode (ic_opmode). With this change, the powersave support now seems to work well enough that the Blackberry can associate and exchange traffic with the ath0 interface as expected. Looking at the code in -current, there have been some changes, but I think the same bug is still there: void ieee80211_power_vattach(struct ieee80211vap *vap) { if (vap->iv_opmode == IEEE80211_M_HOSTAP || vap->iv_opmode == IEEE80211_M_IBSS) { /* NB: driver should override */ vap->iv_update_ps = ieee80211_update_ps; vap->iv_set_tim = ieee80211_set_tim; } } void ieee80211_power_latevattach(struct ieee80211vap *vap) { /* * Allocate these only if needed. Beware that we * know adhoc mode doesn't support ATIM yet... */ if (vap->iv_opmode == IEEE80211_M_HOSTAP) { vap->iv_tim_len = howmany(vap->iv_max_aid,8) * sizeof(uint8_t); vap->iv_tim_bitmap = (uint8_t *) malloc(vap->iv_tim_len, M_80211_POWER, M_NOWAIT | M_ZERO); if (vap->iv_tim_bitmap == NULL) { printf("%s: no memory for TIM bitmap!\n", __func__); /* XXX good enough to keep from crashing? */ vap->iv_tim_len = 0; } } } Unfortunately, I don't have the ability to test the same fix against -current, but it seems to me that it still applies. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= "I put a dollar in a change machine. Nothing changed." - George Carlin ============================================================================= From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 10:55:50 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 475CB1065672 for ; Sun, 25 Jan 2009 10:55:50 +0000 (UTC) (envelope-from sziszi@bsd.hu) Received: from mail.rubicom.hu (mail.rubicom.hu [89.147.80.28]) by mx1.freebsd.org (Postfix) with ESMTP id BF9118FC12 for ; Sun, 25 Jan 2009 10:55:49 +0000 (UTC) (envelope-from sziszi@bsd.hu) Received: from localhost ([127.0.0.1] helo=mail.rubicom.hu) by mail.rubicom.hu with smtp (Exim 4.63) (envelope-from ) id 1LR2eZ-0001nG-Gj for freebsd-current@freebsd.org; Sun, 25 Jan 2009 11:55:47 +0100 Received: from ip5993549e.rubicom.hu ([89.147.84.158] helo=baranyfelhocske.buza.adamsfamily.xx) by mail.rubicom.hu with esmtp (Exim 4.63) (envelope-from ) id 1LR2eZ-0001n8-9c for freebsd-current@freebsd.org; Sun, 25 Jan 2009 11:55:47 +0100 Received: from baranyfelhocske.buza.adamsfamily.xx (localhost [127.0.0.1]) by baranyfelhocske.buza.adamsfamily.xx (8.14.3/8.14.3) with ESMTP id n0PAtlql002620 for ; Sun, 25 Jan 2009 11:55:47 +0100 (CET) (envelope-from sziszi@bsd.hu) Received: (from sziszi@localhost) by baranyfelhocske.buza.adamsfamily.xx (8.14.3/8.14.3/Submit) id n0PAtlcV002619 for freebsd-current@freebsd.org; Sun, 25 Jan 2009 11:55:47 +0100 (CET) (envelope-from sziszi@bsd.hu) X-Authentication-Warning: baranyfelhocske.buza.adamsfamily.xx: sziszi set sender to sziszi@bsd.hu using -f Date: Sun, 25 Jan 2009 11:55:47 +0100 From: Szilveszter Adam To: freebsd-current@freebsd.org Message-ID: <20090125105547.GA1697@baranyfelhocske.buza.adamsfamily.xx> References: <200901241638.18591.hselasky@c2i.net> <497B7A80.4060002@FreeBSD.org> <20090125063441.GC1755@server.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090125063441.GC1755@server.vk2pj.dyndns.org> User-Agent: Mutt/1.5.18 (2008-05-17) Subject: Re: Prblem whit USB in FreeBSD 8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 10:55:50 -0000 On Sun, Jan 25, 2009 at 05:34:41PM +1100, Peter Jeremy wrote: > On 2009-Jan-24 12:30:56 -0800, Maxim Sobolev wrote: > >I wonder if this situation can be handled automatically. To my ignorant > >view, our USB mass storage driver can try sending "synchronize cache" > >command and if that fails then failback to the NO_SYNCHRONIZE_CACHE > >behavior. > > This has been discussed in the past. The problem is that some drives > lock up when you send a "synchronize cache" command so this isn't a > general solution. Exactly. The device in the previous mail (Meizu M6, but the same is true for the M3 MusicCard from the same manufacturer btw which is what I have) was a prime example of this behaviour: with the old usb stack, it often locked up soon after it was connected without the quirk. (At other times, it was "just" not possible to mount it) With the new stack and without the quirk, the effects were even more spectacular when I tried it once: the machine panicked soon after insertion. With the quirk, it behaves well (and looks like a superfloppy) with both stacks. It is a pity btw that the chip/firmware they use is so crappy, because otherwise this device is really open-source friendly, afaik even the firmware can be upgraded on it without any windows-based flashing utility whatsoever. -- Regards: Szilveszter ADAM Budapest Hungary From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 13:38:33 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA5CA106568E; Sun, 25 Jan 2009 13:38:33 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from dhcp-172-28-77-38.eur.corp.google.com (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CCD408FC19; Sun, 25 Jan 2009 13:38:32 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <497C6B57.7000900@FreeBSD.org> Date: Sun, 25 Jan 2009 13:38:31 +0000 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Pawel Jakub Dawidek , FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: panic: existing znode 0xffffff012629a178 for dbuf 0xffffff003bf99540 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 13:38:34 -0000 I got this from stress2 on a zfs pool from an up-to-date 8.0 system: buf.15140: existing znode 0xffffff012629a178 for dbuf 0xffffff003bf99540 panic() at panic+0x17b zfs_znode_dmu_init() at zfs_znode_dmu_init+0xb5 zfs_znode_alloc() at zfs_znode_alloc+0xa0 zfs_mknode() at zfs_mknode+0x205 zfs_freebsd_create() at zfs_freebsd_create+0x617 VOP_CREATE_APV() at VOP_CREATE_APV+0xb3 [...] Unfortunately the console is broken so I can't get more of the backtrace. Any ideas? Kris From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 13:44:24 2009 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 4B5EA1065809 for ; Sun, 25 Jan 2009 13:44:24 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: from web63902.mail.re1.yahoo.com (web63902.mail.re1.yahoo.com [69.147.97.117]) by mx1.freebsd.org (Postfix) with SMTP id D9A498FC21 for ; Sun, 25 Jan 2009 13:44:23 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: (qmail 46400 invoked by uid 60001); 25 Jan 2009 13:44:23 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=R77ut16LYjRPhHgHTa5CsPBrGOL8CO1sapszUMK0AUp2OBAkFa/5RaFzUJ9ph1s15EM3tqmoXQUuE/Cle4Y/wgFxAOpkajlS6qDQ62NChUvxj5FyxoVVg/n25EkS5jsUnutVMT//K7pGbUj5UpJek9RaT74rdwEcGXIhPAvFnNI=; X-YMail-OSG: 2W.aTZgVM1mO7QyF4l7hni1bwt_bF_xXxfCxwMNgsjOuy.ON.9y6_JQu28GqnUPD5Wb9.JaFi2O2q6AZHXdJHw..A3qEMjzhthgIB5BA4Y.QpfrQeRrg9SIp3tRbm9rMy.oaqzTGih9mLnEfKns43sfCb.o- Received: from [98.242.222.229] by web63902.mail.re1.yahoo.com via HTTP; Sun, 25 Jan 2009 05:44:23 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Sun, 25 Jan 2009 05:44:23 -0800 (PST) From: Barney Cordoba To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <471411.45398.qm@web63902.mail.re1.yahoo.com> Cc: jfvogel@gmail.com Subject: Problems with ixgbe X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: barney_cordoba@yahoo.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2009 13:44:24 -0000 I'm trying to fire up a couple of 10g cards (2 different cards with 82598 NICs) hooked up back to back, and I'm having nothing but problems. I haven't gotten the latest version 1.5.6 driver to work under any circumstances. I've gotten the 1.2.16 driver that came in 7.0-RELEASE to work once on fresh boots on each machine, but then when rebooting one of the machines nothing could be done to get them to talk again. I did do quite a bit of testing so it doesn't seem that the cards are faulty. Its just wholly unreliable. It seems that they just don't transmit the frames properly. netstat -i shows outgoing packets but internal hw.ix.0.stats show none transmitted when enabled. I've tried disabling MSI-X, using just 1 queue, all with the same result. I don't have a 7.1 or 8 machine to test with at this location, so I don't know if there is something in 7.0-RELEASE that just won't work with these cards. I don't want to beat my head too badly, or spend time debugging if its just not going to work. First, should 1.5.6 work in 7.0? The README indicates it should. It makes little sense debugging an old driver. Barney From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 19:50:03 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 523661065670 for ; Sun, 25 Jan 2009 19:50:03 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from aeryn.cs.uoguelph.ca (aeryn.cs.uoguelph.ca [131.104.20.160]) by mx1.freebsd.org (Postfix) with ESMTP id 87A878FC12 for ; Sun, 25 Jan 2009 19:50:02 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by aeryn.cs.uoguelph.ca (8.13.1/8.13.1) with ESMTP id n0Q0MqDQ001244; Sun, 25 Jan 2009 19:22:52 -0500 Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id n0PJQAi17277; Sun, 25 Jan 2009 14:26:11 -0500 (EST) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Sun, 25 Jan 2009 14:26:10 -0500 (EST) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Dmitry Marakasov In-Reply-To: <20090123221826.GB30982@deprived.panopticon> Message-ID: References: <20090123221826.GB30982@deprived.panopticon> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.63 on 131.104.20.161 Cc: freebsd-current@freebsd.org Subject: Re: NFS data corruption X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 19:50:03 -0000 On Sat, 24 Jan 2009, Dmitry Marakasov wrote: [stuff about data corruption snipped] > > Is there any way I can help to diagnose and fix the problem? > > Here's amd.map file which is used to mount this filesystem: > > --- > /defaults type:=nfs;rhost:=hive;opts:=rw,nosuid,noexec,-3,-i,-s,-T > * rfs:=/pool/${key} > --- > A couple of simple things you could try: 1 - rebuild your kernel with "option NFS_LEGACYRPC" and try that. 2 - try it without the "-s" option (since nothing reports a failure, is seems unlikely that an RPC would have timed out, but maybe the app. doesn't check for error returns on write. In general, I consider "soft" mounts to be a bad idea, but that's just imho.) Good luck with it, rick From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 19:55:56 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83670106564A for ; Sun, 25 Jan 2009 19:55:56 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk1.360sip.com [72.236.70.240]) by mx1.freebsd.org (Postfix) with ESMTP id 4C25A8FC0A for ; Sun, 25 Jan 2009 19:55:55 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from [192.168.1.38] (S0106001372fd1e07.vs.shawcable.net [70.71.171.106]) (authenticated bits=0) by sippysoft.com (8.13.8/8.13.8) with ESMTP id n0PJtriO071231 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 25 Jan 2009 11:55:54 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Message-ID: <497CC3C4.1070708@FreeBSD.org> Date: Sun, 25 Jan 2009 11:55:48 -0800 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Peter Jeremy References: <200901241638.18591.hselasky@c2i.net> <497B7A80.4060002@FreeBSD.org> <20090125063441.GC1755@server.vk2pj.dyndns.org> In-Reply-To: <20090125063441.GC1755@server.vk2pj.dyndns.org> Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: Re: Prblem whit USB in FreeBSD 8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 19:55:56 -0000 Peter Jeremy wrote: > On 2009-Jan-24 12:30:56 -0800, Maxim Sobolev wrote: >> I wonder if this situation can be handled automatically. To my ignorant >> view, our USB mass storage driver can try sending "synchronize cache" >> command and if that fails then failback to the NO_SYNCHRONIZE_CACHE >> behavior. > > This has been discussed in the past. The problem is that some drives > lock up when you send a "synchronize cache" command so this isn't a > general solution. So what? The drive that is not in the quirks won't work anyway, so that if by auto-detection you can make at least fraction of those drivers working out of the box it would be an improvement. I wonder how other operating systems (Windows, Linux) cope with this issue. Not sure about a Linux, but I really doubt Windows has anything like our quirks, yet all drives work with it. -Maxim From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 20:04:32 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EACB6106564A for ; Sun, 25 Jan 2009 20:04:32 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id AD0488FC08 for ; Sun, 25 Jan 2009 20:04:32 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n0PK4W2X006521 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 25 Jan 2009 12:04:32 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <497CC5D0.3030103@freebsd.org> Date: Sun, 25 Jan 2009 12:04:32 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: Bill Paul References: <20090125103905.378CA106570E@hub.freebsd.org> In-Reply-To: <20090125103905.378CA106570E@hub.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-sonic.net-Metrics: ebb.errno.com; whitelist Cc: freebsd-current@freebsd.org Subject: Re: net80211 hostap vs powersave X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 20:04:33 -0000 Doug White noticed the same issue a few weeks ago and we fixed it but the change was never committed. Hopefully that'll happen soon. power save definitely works in HEAD. Sam From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 20:21:53 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9DEDE106564A for ; Sun, 25 Jan 2009 20:21:53 +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 087AB8FC17 for ; Sun, 25 Jan 2009 20:21:52 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=neEVqQTEdNsA:10 a=wYO06tke1OGfzKJGpPEA:9 a=34Ai5ik5vuyHX7skhdoA:7 a=bdXs_iuYIHYAG01iRxmEoudO-KMA:4 a=SV7veod9ZcQA:10 a=LY0hPdMaydYA:10 Received: from [85.19.218.115] (account mc467741@c2i.net HELO [10.37.1.92]) by mailfe08.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 1184158238; Sun, 25 Jan 2009 21:21:51 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Sun, 25 Jan 2009 21:24:06 +0100 User-Agent: KMail/1.9.7 References: <20090125063441.GC1755@server.vk2pj.dyndns.org> <497CC3C4.1070708@FreeBSD.org> In-Reply-To: <497CC3C4.1070708@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901252124.10886.hselasky@c2i.net> Cc: Peter Jeremy Subject: Re: Prblem whit USB in FreeBSD 8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 20:21:53 -0000 On Sunday 25 January 2009, Maxim Sobolev wrote: > Peter Jeremy wrote: > > On 2009-Jan-24 12:30:56 -0800, Maxim Sobolev wrote: > >> I wonder if this situation can be handled automatically. To my ignorant > >> view, our USB mass storage driver can try sending "synchronize cache" > >> command and if that fails then failback to the NO_SYNCHRONIZE_CACHE > >> behavior. > > > > This has been discussed in the past. The problem is that some drives > > lock up when you send a "synchronize cache" command so this isn't a > > general solution. > > So what? The drive that is not in the quirks won't work anyway, so that > if by auto-detection you can make at least fraction of those drivers > working out of the box it would be an improvement. I wonder how other > operating systems (Windows, Linux) cope with this issue. Not sure about > a Linux, but I really doubt Windows has anything like our quirks, yet > all drives work with it. > Hi, I was thinking about moving the mass storage quirks into the usb2_quirk module so that they can be set by "usbconfig". To some extent I agree that we should try to make things work out of the box. What I could easily do is to add a sysctl which you can set that automatically turns on the most common Mass Storage quirks for all USB Mass Storage Devices plugged. What do you think? --HPS From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 20:37:52 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FA64106566C; Sun, 25 Jan 2009 20:37:52 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id 32A568FC17; Sun, 25 Jan 2009 20:37:52 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.2/8.14.2) with ESMTP id n0PKbpea089719; Sun, 25 Jan 2009 12:37:51 -0800 (PST) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.2/8.14.2/Submit) id n0PKbpDG089718; Sun, 25 Jan 2009 12:37:51 -0800 (PST) (envelope-from obrien) Date: Sun, 25 Jan 2009 12:37:51 -0800 From: "David O'Brien" To: Kris Kennaway Message-ID: <20090125203751.GA89522@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, Kris Kennaway , FreeBSD Current References: <497B3B40.3040306@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <497B3B40.3040306@FreeBSD.org> X-Operating-System: FreeBSD 8.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: FreeBSD Current Subject: Re: Noisy make -j output X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2009 20:37:52 -0000 On Sat, Jan 24, 2009 at 04:01:04PM +0000, Kris Kennaway wrote: > After a fresh buildworld on a system last built in November: > hydra2# make buildworld -j8 -s > --- upgrade_checks --- > --- make --- > [...] > > Why the extra-spammy output now? It's the intended operation of pmake/bmake from 4.4BSD. One reason I believe we haven't trusted 'make -j' in the past is it can be very hard to unwind the output when there is a build error. It turns out this is because dg in the past neutered them (presumably he didn't understand their value). After having used a bmake with the stock behavior I've seen how valuable the markers are. -- -- David (obrien@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 21:03:27 2009 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 AF82A1065758 for ; Sun, 25 Jan 2009 21:03:27 +0000 (UTC) (envelope-from jfvogel@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 7B72B8FC63 for ; Sun, 25 Jan 2009 21:03:27 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wa-out-1112.google.com with SMTP id k34so378787wah.27 for ; Sun, 25 Jan 2009 13:03:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=96ubDXR6ft6kHYHPIB2JaenkHnR0Adr2i0c4gV67uHE=; b=MVYI7yk/o1vehR1dkpHkkHe5H0NQJbd6fKhSNR9ajiGUELlicQt8nBMbIYN1gr+i9D bppEGdJaHGm0SgUyZw06JWxya+ghdWMFjidGx+vSNRRKvbX71TD25Btul4Vi4tvFnhN1 mEGxmlL/JY8OR91ldKhBsLtmjFudpprjcEyM8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=iC1Malbcv1Bv6nS74tvUFt4udVmhNakH8WkHlZabu2JHT/rGgO+1U9y68gRm+7LgNj ACYE7ZcF9kUF9ebXhEjiRkQ/PcF4b5+diCb5vk9wS+/TJYkmkm/UyNr/GpAUipnkYqw4 9YJXjG9F8rGeQ0D1QfBTAn86/tssg3J9Fxp98= MIME-Version: 1.0 Received: by 10.114.144.1 with SMTP id r1mr3872991wad.2.1232915477187; Sun, 25 Jan 2009 12:31:17 -0800 (PST) In-Reply-To: <471411.45398.qm@web63902.mail.re1.yahoo.com> References: <471411.45398.qm@web63902.mail.re1.yahoo.com> Date: Sun, 25 Jan 2009 12:31:17 -0800 Message-ID: <2a41acea0901251231w5dc6b739k420d41e8d4b7f3d7@mail.gmail.com> From: Jack Vogel To: barney_cordoba@yahoo.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: current@freebsd.org Subject: Re: Problems with ixgbe X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 21:03:31 -0000 On Sun, Jan 25, 2009 at 5:44 AM, Barney Cordoba wrote: > I'm trying to fire up a couple of 10g cards (2 different cards with 82598 > NICs) hooked up back to back, and I'm having nothing but problems. I haven't > gotten the latest version 1.5.6 driver to work under any circumstances. I've > gotten the 1.2.16 driver that came in 7.0-RELEASE to work once on fresh > boots on each machine, but then when rebooting one of the machines nothing > could be done to get them to talk again. I did do quite a bit of testing so > it doesn't seem that the cards are faulty. Its just wholly unreliable. It > seems that they just don't transmit the frames properly. netstat -i shows > outgoing packets but internal hw.ix.0.stats show none transmitted when > enabled. I've tried disabling MSI-X, using just 1 queue, all with the same > result. > > I don't have a 7.1 or 8 machine to test with at this location, so I don't > know if there is something in 7.0-RELEASE that just won't work with these > cards. I don't want to beat my head too badly, or spend time debugging if > its just not going to work. > > First, should 1.5.6 work in 7.0? The README indicates it should. It makes > little sense debugging an old driver. > > > Barney > > > > Barney, You never give specifics on your failures. The 1.5.6 driver should work, however there is newer code, I just have been too busy internally to get it checked in yet. Give me more exact details, what hardware, how is it hooked up, etc etc... Jack From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 22:20:41 2009 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 1BF85106564A for ; Sun, 25 Jan 2009 22:20:41 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: from web63904.mail.re1.yahoo.com (web63904.mail.re1.yahoo.com [69.147.97.119]) by mx1.freebsd.org (Postfix) with SMTP id B51528FC13 for ; Sun, 25 Jan 2009 22:20:40 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: (qmail 81717 invoked by uid 60001); 25 Jan 2009 22:20:39 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Message-ID; b=Q3MsWrjhTnnp4kmbNcyDh9oa6kYw+YZuJ1Nrj2zeWI6/hj8xYksfFVibhvcktRCME8S7OQs6/cyDmqF/0ng1QYAyieykWdzsnwdHg5tsPhivGUiWFEUQ0lHRn8scKKd1s9vGdcnhzPFFzTC5/9cLsHPyiVO3/QU0kuDBwUrwHlc=; X-YMail-OSG: rcZz.yQVM1nB5jEp55dd73oMsdmni4m1yRCgA2GVYvCMuC9ekDMdeFDv1bD1pAmVmrwBWKgjeD.tLhuWVQZE1bDCyrsSTR6UgD310lcmyVGoa8RLeFGGdQiWB4lbTni2.wxe5a4bRMSaEx8eNWfnfaFlxLYKt2Gj7s_OAfZcNosgFhGoo1n2buabmU7T198- Received: from [98.242.222.229] by web63904.mail.re1.yahoo.com via HTTP; Sun, 25 Jan 2009 14:20:39 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Sun, 25 Jan 2009 14:20:39 -0800 (PST) From: Barney Cordoba To: Jack Vogel In-Reply-To: <2a41acea0901251231w5dc6b739k420d41e8d4b7f3d7@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <936475.81653.qm@web63904.mail.re1.yahoo.com> Cc: current@freebsd.org Subject: Re: Problems with ixgbe X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: barney_cordoba@yahoo.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2009 22:20:41 -0000 --- On Sun, 1/25/09, Jack Vogel wrote: > From: Jack Vogel > Subject: Re: Problems with ixgbe > To: barney_cordoba@yahoo.com > Cc: current@freebsd.org > Date: Sunday, January 25, 2009, 3:31 PM > On Sun, Jan 25, 2009 at 5:44 AM, Barney Cordoba > wrote: > > > I'm trying to fire up a couple of 10g cards (2 > different cards with 82598 > > NICs) hooked up back to back, and I'm having > nothing but problems. I haven't > > gotten the latest version 1.5.6 driver to work under > any circumstances. I've > > gotten the 1.2.16 driver that came in 7.0-RELEASE to > work once on fresh > > boots on each machine, but then when rebooting one of > the machines nothing > > could be done to get them to talk again. I did do > quite a bit of testing so > > it doesn't seem that the cards are faulty. Its > just wholly unreliable. It > > seems that they just don't transmit the frames > properly. netstat -i shows > > outgoing packets but internal hw.ix.0.stats show none > transmitted when > > enabled. I've tried disabling MSI-X, using just 1 > queue, all with the same > > result. > > > > I don't have a 7.1 or 8 machine to test with at > this location, so I don't > > know if there is something in 7.0-RELEASE that just > won't work with these > > cards. I don't want to beat my head too badly, or > spend time debugging if > > its just not going to work. > > > > First, should 1.5.6 work in 7.0? The README indicates > it should. It makes > > little sense debugging an old driver. > > > > > > Barney > > > > > > > > > Barney, > > You never give specifics on your failures. The 1.5.6 driver > should work, > however > there is newer code, I just have been too busy internally > to get it checked > in yet. > > Give me more exact details, what hardware, how is it hooked > up, etc etc... > > Jack Ok. It doesn't transmit anything. I've tracked it down to bus_dmamap_load_mbuf_sg() failing, which is caused when reserve_bounce_pages() fails. It seems there are no bounce pages available. Barney From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 22:27:53 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D797A106564A; Sun, 25 Jan 2009 22:27:53 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from dhcp-172-28-76-91.eur.corp.google.com (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 750218FC24; Sun, 25 Jan 2009 22:27:52 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <497CE767.3080109@FreeBSD.org> Date: Sun, 25 Jan 2009 22:27:51 +0000 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: obrien@freebsd.org, Kris Kennaway , FreeBSD Current References: <497B3B40.3040306@FreeBSD.org> <20090125203751.GA89522@dragon.NUXI.org> In-Reply-To: <20090125203751.GA89522@dragon.NUXI.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Noisy make -j 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: Sun, 25 Jan 2009 22:27:54 -0000 David O'Brien wrote: > On Sat, Jan 24, 2009 at 04:01:04PM +0000, Kris Kennaway wrote: >> After a fresh buildworld on a system last built in November: >> hydra2# make buildworld -j8 -s >> --- upgrade_checks --- >> --- make --- >> [...] >> >> Why the extra-spammy output now? > > It's the intended operation of pmake/bmake from 4.4BSD. One reason I > believe we haven't trusted 'make -j' in the past is it can be very hard > to unwind the output when there is a build error. It turns out this is > because dg in the past neutered them (presumably he didn't understand > their value). After having used a bmake with the stock behavior I've > seen how valuable the markers are. I consider the change to be exposing debug-level information that is too noisy to be on by default. Also I'm concerned that you've broken things that expect 'make -s' to actually be silent. Kris From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 23:08:14 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CAF651065674; Sun, 25 Jan 2009 23:08:14 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id A4DDE8FC1C; Sun, 25 Jan 2009 23:08:14 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.2/8.14.2) with ESMTP id n0PN8EXr092252; Sun, 25 Jan 2009 15:08:14 -0800 (PST) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.2/8.14.2/Submit) id n0PN8EGD092251; Sun, 25 Jan 2009 15:08:14 -0800 (PST) (envelope-from obrien) Date: Sun, 25 Jan 2009 15:08:14 -0800 From: "David O'Brien" To: Kris Kennaway Message-ID: <20090125230814.GF89522@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, Kris Kennaway , FreeBSD Current References: <497B3B40.3040306@FreeBSD.org> <20090125203751.GA89522@dragon.NUXI.org> <497CE767.3080109@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <497CE767.3080109@FreeBSD.org> X-Operating-System: FreeBSD 8.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: FreeBSD Current Subject: Re: Noisy make -j output X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2009 23:08:15 -0000 On Sun, Jan 25, 2009 at 10:27:51PM +0000, Kris Kennaway wrote: > David O'Brien wrote: >> On Sat, Jan 24, 2009 at 04:01:04PM +0000, Kris Kennaway wrote: >>> After a fresh buildworld on a system last built in November: >>> hydra2# make buildworld -j8 -s >>> --- upgrade_checks --- >>> --- make --- >>> [...] >>> >>> Why the extra-spammy output now? >> It's the intended operation of pmake/bmake from 4.4BSD. One reason I >> believe we haven't trusted 'make -j' in the past is it can be very hard >> to unwind the output when there is a build error. It turns out this is >> because dg in the past neutered them (presumably he didn't understand >> their value). After having used a bmake with the stock behavior I've >> seen how valuable the markers are. > > I consider the change to be exposing debug-level information that is too > noisy to be on by default. What is "debug-level" information? I really don't consider this to be "debug information" any more than the invocation of the compiler. Nor the output from things like 'make obj': ===> share/info (obj) ===> lib (obj) ===> lib/csu/amd64 (obj) ===> lib/libc (obj) ..snip.. With the markers it is easy to write scripts that de-multiplex a build log, giving output roughly what a non-// run would be. This makes it easy to extract errors from build logs. > Also I'm concerned that you've broken things > that expect 'make -s' to actually be silent. 'make -s' : relates to commands executed, not making the output "quiet". >From the man page: Do not echo any commands as they are executed. Equivalent to specifying `@' before each command line in the makefile. If something expects 'make -s' to be minimal output it is broken and non-portable as its assuming '-s' does more than SUSv3 requires of it. -s Do not write makefile command lines or touch messages (see -t) to standard output before executing. This mode shall be the same as if the special target .SILENT were specified without prerequisites. .SILENT Prerequisites of this special target are targets themselves; this shall cause commands associated with them not to be written to the standard output before they are executed. Subsequent occurrences of .SILENT shall add to the list of targets with silent commands. If no prerequisites are specified, make shall behave as if the -s option had been specified and no commands or touch messages associated with any target shall be written to standard output. 'make -Q' (or the special target .POSIX:) can be used to quiet the output from 'make -j'. To see just how silent things in our world are I tried '(cd /usr/src ; make -Q -s -j8 world)', which gives output such as: ===> lib/libdwarf (obj,depend,all,install) ===> cddl/usr.bin/ctfconvert (obj,depend,all,install) ===> cddl/usr.bin/ctfmerge (obj,depend,all,install) ===> games/fortune/strfile (obj,depend,all,install) ===> gnu/usr.bin/gperf (obj,depend,all,install) ===> gnu/usr.bin/gperf/doc (obj) ===> gnu/usr.bin/gperf/doc (depend) ===> gnu/usr.bin/gperf/doc (all) ===> gnu/usr.bin/gperf/doc (install) ===> gnu/usr.bin/groff/tmac (obj,depend,all,install) I then configured a GENERIC and ran '(cd ../../GENERIC ; make -j8 -s -Q)', which gives output such as: ===> aic7xxx (obj) ===> aic7xxx/aicasm (obj) ===> aic7xxx/ahc (obj) ===> aic7xxx/ahc/ahc_eisa (obj) ./aicasm: 880 instructions used ./aicasm: 880 instructions used ./aicasm: 880 instructions used ./aicasm: 826 instructions used ./aicasm: 826 instructions used ./aicasm: 826 instructions used ===> aic7xxx/ahc/ahc_isa (obj) ===> aic7xxx/ahc/ahc_pci (obj) ===> aic7xxx/ahd (obj) which also isn't very silent. Wouldn't this behavior of our mk files also break things that expect 'make -s' to be silent? Do you have a test case I could ponder? Maybe -s should imply -Q? But it looks like there is really more work to be done for -s to really be silent. -- -- David (obrien@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 23:29:45 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 185FC106566B; Sun, 25 Jan 2009 23:29:45 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from dhcp-172-28-76-91.eur.corp.google.com (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 690F78FC0A; Sun, 25 Jan 2009 23:29:43 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <497CF5E6.4040007@FreeBSD.org> Date: Sun, 25 Jan 2009 23:29:42 +0000 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: obrien@freebsd.org, Kris Kennaway , FreeBSD Current References: <497B3B40.3040306@FreeBSD.org> <20090125203751.GA89522@dragon.NUXI.org> <497CE767.3080109@FreeBSD.org> <20090125230814.GF89522@dragon.NUXI.org> In-Reply-To: <20090125230814.GF89522@dragon.NUXI.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Noisy make -j 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: Sun, 25 Jan 2009 23:29:45 -0000 David O'Brien wrote: > On Sun, Jan 25, 2009 at 10:27:51PM +0000, Kris Kennaway wrote: >> David O'Brien wrote: >>> On Sat, Jan 24, 2009 at 04:01:04PM +0000, Kris Kennaway wrote: >>>> After a fresh buildworld on a system last built in November: >>>> hydra2# make buildworld -j8 -s >>>> --- upgrade_checks --- >>>> --- make --- >>>> [...] >>>> >>>> Why the extra-spammy output now? >>> It's the intended operation of pmake/bmake from 4.4BSD. One reason I >>> believe we haven't trusted 'make -j' in the past is it can be very hard >>> to unwind the output when there is a build error. It turns out this is >>> because dg in the past neutered them (presumably he didn't understand >>> their value). After having used a bmake with the stock behavior I've >>> seen how valuable the markers are. >> I consider the change to be exposing debug-level information that is too >> noisy to be on by default. > > What is "debug-level" information? As in the snippet I posted, all of the internal make targets that are executed are now being exposed to the user. make buildworld -j -s is especially unclean. > I really don't consider this to be "debug information" any more than the > invocation of the compiler. Nor the output from things like 'make obj': > ===> share/info (obj) > ===> lib (obj) > ===> lib/csu/amd64 (obj) > ===> lib/libc (obj) > ..snip.. > > > With the markers it is easy to write scripts that de-multiplex a build > log, giving output roughly what a non-// run would be. This makes it > easy to extract errors from build logs. > > >> Also I'm concerned that you've broken things >> that expect 'make -s' to actually be silent. > > 'make -s' : relates to commands executed, not making the output "quiet". >>From the man page: > Do not echo any commands as they are executed. Equivalent to > specifying `@' before each command line in the makefile. > > If something expects 'make -s' to be minimal output it is broken and > non-portable as its assuming '-s' does more than SUSv3 requires of it. > > -s > Do not write makefile command lines or touch messages (see -t) to > standard output before executing. This mode shall be the same as if > the special target .SILENT were specified without prerequisites. > > .SILENT > Prerequisites of this special target are targets themselves; this > shall cause commands associated with them not to be written to the > standard output before they are executed. Subsequent occurrences of > .SILENT shall add to the list of targets with silent commands. If no > prerequisites are specified, make shall behave as if the -s option > had been specified and no commands or touch messages associated with > any target shall be written to standard output. > > > 'make -Q' (or the special target .POSIX:) can be used to quiet the > output from 'make -j'. > > To see just how silent things in our world are I tried > '(cd /usr/src ; make -Q -s -j8 world)', which gives output such as: > ===> lib/libdwarf (obj,depend,all,install) > ===> cddl/usr.bin/ctfconvert (obj,depend,all,install) > ===> cddl/usr.bin/ctfmerge (obj,depend,all,install) > ===> games/fortune/strfile (obj,depend,all,install) > ===> gnu/usr.bin/gperf (obj,depend,all,install) > ===> gnu/usr.bin/gperf/doc (obj) > ===> gnu/usr.bin/gperf/doc (depend) > ===> gnu/usr.bin/gperf/doc (all) > ===> gnu/usr.bin/gperf/doc (install) > ===> gnu/usr.bin/groff/tmac (obj,depend,all,install) > > I then configured a GENERIC and ran > '(cd ../../GENERIC ; make -j8 -s -Q)', which gives output such as: > ===> aic7xxx (obj) > ===> aic7xxx/aicasm (obj) > ===> aic7xxx/ahc (obj) > ===> aic7xxx/ahc/ahc_eisa (obj) > ./aicasm: 880 instructions used > ./aicasm: 880 instructions used > ./aicasm: 880 instructions used > ./aicasm: 826 instructions used > ./aicasm: 826 instructions used > ./aicasm: 826 instructions used > ===> aic7xxx/ahc/ahc_isa (obj) > ===> aic7xxx/ahc/ahc_pci (obj) > ===> aic7xxx/ahd (obj) > > which also isn't very silent. > > Wouldn't this behavior of our mk files also break things that expect > 'make -s' to be silent? I'm thinking of custom makefiles that capture the output and post-process it, which will now have extra text inserted into the output along with the output that is expected to be there. > Do you have a test case I could ponder? Maybe -s should imply -Q? But > it looks like there is really more work to be done for -s to really be > silent. I think -s should either imply -Q or -Q should just go away. Kris From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 23:45:05 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8FA21065673; Sun, 25 Jan 2009 23:45:05 +0000 (UTC) (envelope-from andy@siliconlandmark.com) Received: from lexi.siliconlandmark.com (lexi.siliconlandmark.com [66.184.117.4]) by mx1.freebsd.org (Postfix) with ESMTP id 831A28FC0A; Sun, 25 Jan 2009 23:45:05 +0000 (UTC) (envelope-from andy@siliconlandmark.com) Received: from [10.0.1.102] (c-76-112-231-135.hsd1.mi.comcast.net [76.112.231.135]) (authenticated bits=0) by lexi.siliconlandmark.com (8.14.2/8.14.2) with ESMTP id n0PN8xiV009761 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 25 Jan 2009 23:09:00 GMT (envelope-from andy@siliconlandmark.com) Message-Id: From: Andre Guibert de Bruet To: Maxim Sobolev In-Reply-To: <497CC3C4.1070708@FreeBSD.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Sun, 25 Jan 2009 18:08:54 -0500 References: <200901241638.18591.hselasky@c2i.net> <497B7A80.4060002@FreeBSD.org> <20090125063441.GC1755@server.vk2pj.dyndns.org> <497CC3C4.1070708@FreeBSD.org> X-Mailer: Apple Mail (2.930.3) X-Virus-Scanned: ClamAV 0.94.1/8901/Sun Jan 25 10:10:36 2009 on lexi.siliconlandmark.com X-Virus-Status: Clean Cc: Peter Jeremy , freebsd-current@freebsd.org Subject: Re: Prblem whit USB in FreeBSD 8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jan 2009 23:45:06 -0000 On Jan 25, 2009, at 2:55 PM, Maxim Sobolev wrote: > Peter Jeremy wrote: >> On 2009-Jan-24 12:30:56 -0800, Maxim Sobolev >> wrote: >>> I wonder if this situation can be handled automatically. To my >>> ignorant view, our USB mass storage driver can try sending >>> "synchronize cache" command and if that fails then failback to the >>> NO_SYNCHRONIZE_CACHE behavior. >> This has been discussed in the past. The problem is that some drives >> lock up when you send a "synchronize cache" command so this isn't a >> general solution. > > So what? The drive that is not in the quirks won't work anyway, so > that if by auto-detection you can make at least fraction of those > drivers working out of the box it would be an improvement. I wonder > how other operating systems (Windows, Linux) cope with this issue. > Not sure about a Linux, but I really doubt Windows has anything like > our quirks, yet all drives work with it. Windows has write caching disabled by default. You need to turn it on per-device from the Device Manager by right-clicking on the device, selecting properties, going to the "Policies" tab and selecting "Optimize for performance" (The default is set to "Optimize for quick removal"). Cheers, Andy /* Andre Guibert de Bruet * 436f 6465 2070 6f65 742e 2042 6974 206a */ /* Managing Partner * 6f63 6b65 792e 2053 7973 4164 6d69 6e2e */ /* GSM: +1 734 846 8758 * 2055 4e49 5820 736c 6575 7468 2e00 0000 */ /* WWW: siliconlandmark.com * C/C++, Java, Perl, PHP, SQL, XHTML, XML */ From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 00:23:56 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4ECDE1065673 for ; Mon, 26 Jan 2009 00:23:56 +0000 (UTC) (envelope-from freebsd@chrisbuechler.com) Received: from mail.livebsd.com (mail.livebsd.com [69.64.6.14]) by mx1.freebsd.org (Postfix) with SMTP id E7EB08FC13 for ; Mon, 26 Jan 2009 00:23:55 +0000 (UTC) (envelope-from freebsd@chrisbuechler.com) Received: (qmail 48919 invoked by uid 89); 25 Jan 2009 23:35:02 -0000 Received: from unknown (HELO ?10.0.64.15?) (96.28.38.25) by 172.29.29.14 with SMTP; 25 Jan 2009 23:35:02 -0000 Message-ID: <497CF726.4030206@chrisbuechler.com> Date: Sun, 25 Jan 2009 18:35:02 -0500 From: Chris Buechler User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20090125103905.378CA106570E@hub.freebsd.org> <497CC5D0.3030103@freebsd.org> In-Reply-To: <497CC5D0.3030103@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: net80211 hostap vs powersave X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jan 2009 00:23:56 -0000 Sam Leffler wrote: > > I can confirm that the fix posted by Bill works on 7.1. A pfSense user was having the same trouble with a Blackberry Bold, and this fixed it. We're now including the diff from Bill on our pfSense 1.2.3 images based on FreeBSD 7.1. The Google G1 phone previously didn't work and I suspect this will fix it as well, but have not gotten confirmation from anyone on that yet. Thanks to Bill for posting and Bjoern Zeeb for pointing us to his post! Chris From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 00:34:22 2009 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 6CE90106566C; Mon, 26 Jan 2009 00:34:22 +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 170028FC18; Mon, 26 Jan 2009 00:34:21 +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.3/8.14.3) with ESMTP id n0Q0YJmn099877; Sun, 25 Jan 2009 19:34:19 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0Q0YJmP014044; Sun, 25 Jan 2009 19:34:19 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 5656C7302F; Sun, 25 Jan 2009 19:34:19 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090126003419.5656C7302F@freebsd-current.sentex.ca> Date: Sun, 25 Jan 2009 19:34:19 -0500 (EST) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on clamscanner1 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on powerpc/powerpc 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: Mon, 26 Jan 2009 00:34:23 -0000 TB --- 2009-01-25 23:20:33 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-01-25 23:20:33 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2009-01-25 23:20:33 - cleaning the object tree TB --- 2009-01-25 23:21:04 - cvsupping the source tree TB --- 2009-01-25 23:21:04 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2009-01-25 23:21:12 - building world TB --- 2009-01-25 23:21:12 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-25 23:21:12 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-25 23:21:12 - TARGET=powerpc TB --- 2009-01-25 23:21:12 - TARGET_ARCH=powerpc TB --- 2009-01-25 23:21:12 - TZ=UTC TB --- 2009-01-25 23:21:12 - __MAKE_CONF=/dev/null TB --- 2009-01-25 23:21:12 - cd /src TB --- 2009-01-25 23:21:12 - /usr/bin/make -B buildworld >>> World build started on Sun Jan 25 23:21:13 UTC 2009 >>> 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 [...] gzip -cn /src/share/man/man4/zero.4 > zero.4.gz gzip -cn /src/share/man/man4/zyd.4 > zyd.4.gz ===> share/man/man4/man4.powerpc (all) gzip -cn /src/share/man/man4/man4.powerpc/bm.4 > bm.4.gz gzip -cn /src/share/man/man4/man4.powerpc/pmu.4 > pmu.4.gz gzip -cn /src/share/man/man4/man4.powerpc/powermac_nvram.4 > powermac_nvram.4.gz gzip -cn /src/share/man/man4/man4.powerpc/snd_ai2s.4 > snd_ai2s.4.gz make: don't know how to make snd_davbus. Stop *** Error code 2 Stop in /src/share/man/man4. *** Error code 1 Stop in /src/share/man. *** Error code 1 Stop in /src/share. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-26 00:34:19 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-26 00:34:19 - ERROR: failed to build world TB --- 2009-01-26 00:34:19 - 3573.24 user 328.17 system 4425.48 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 02:00:23 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B61F106566C for ; Mon, 26 Jan 2009 02:00:23 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.29]) by mx1.freebsd.org (Postfix) with ESMTP id D1EB08FC17 for ; Mon, 26 Jan 2009 02:00:22 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so2275695yxb.13 for ; Sun, 25 Jan 2009 18:00:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=c8kEkbe/NcCoZTsQkhO/iTFaxQ5PUnMhcDdfPvpQzPM=; b=I4vVlkKuGxXOC1R5Vfow/fLST7wfyW3BuYCA36MbzlHe7rK3WEFFe2Tni39ufPgNkO 5RNFciIyoNxXvkUnKQIwYVAYLn+WjGSkE8IId9ZGsSN8ALX3jrTOiXyDvKHwIpY7i7wp gp3ciAkUNzCQsRrlhdygJdDe24sVfxBXCzgw8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=P2yjvJGUWaBw8SE2myBWcFfS9EQzzDd2mLrrP24OTF4x4mKqIFjwbkIHZfK3OSl5QC y1Utd4bfcwaeeGjKz84jKOHcFtSKs2Jv1PqZT0EP9hacomvbDiZveDUrllVwTAI06Wsu MFe2DSElvU0I97z8OMr8vRgZtIJ3NvBj9cspc= MIME-Version: 1.0 Received: by 10.90.33.15 with SMTP id g15mr3755189agg.90.1232933740671; Sun, 25 Jan 2009 17:35:40 -0800 (PST) Date: Sun, 25 Jan 2009 20:35:40 -0500 Message-ID: <3c0b01820901251735m4c6a1abfu37a1634818e1724a@mail.gmail.com> From: Alexander Sack To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Reset register flag versus the actual register X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jan 2009 02:00:23 -0000 Hi Everybody: I've ran into the quintessential "it works on Linux but does not work on FreeBSD" vendor comment regarding the boxes ability to reboot successfully. I'm running FreeBSD-6.1 but this also applies the FreeBSD-CURRENT as well. The problem boils down to the fact that the BIOS does set the ResetRegister bit in the FADT feature flags. However, I've noticed that latest stable Linux kernel has the following logic with respect to the reset register: acpi_reboot(): 18 /* Is the reset register supported? */ 19 if (!(acpi_gbl_FADT.flags & ACPI_FADT_RESET_REGISTER) || 20 rr->bit_width != 8 || rr->bit_offset != 0) 21 return; http://lxr.linux.no/linux+v2.6.28/drivers/acpi/reboot.c CURRENT looks like this via the shutdown_final EVENTHANDLE: acpi_shutdown_final(): 1821 } else if ((howto & RB_HALT) == 0 && 1822 (AcpiGbl_FADT.Flags & ACPI_FADT_RESET_REGISTER) && 1823 sc->acpi_handle_reboot) { 1824 /* Reboot using the reset register. */ http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/acpica/acpi.c?rev=1.254 Two questions: 1) Why is the sysctl acpi_handle_reboot zero by default? Shouldn't it be more prudent to rely on the ACPI reboot hook than the legacy keyboard controller methods? I realize there is some history here but it would seem to me that the "&&" should be an "||" which would allow me to override the ACPI_FADT_RESET_REGISTER flag and force an ACPI reset? 2) Is there something to be said for a patch like this: -- acpi.c.0 2009-01-25 19:56:48.000000000 -0500 +++ acpi.c 2009-01-25 20:10:34.000000000 -0500 @@ -1818,18 +1818,20 @@ DELAY(1000000); printf("ACPI power-off failed - timeout\n"); } - } else if ((howto & RB_HALT) == 0 && - (AcpiGbl_FADT.Flags & ACPI_FADT_RESET_REGISTER) && - sc->acpi_handle_reboot) { - /* Reboot using the reset register. */ - status = AcpiHwLowLevelWrite( - AcpiGbl_FADT.ResetRegister.BitWidth, - AcpiGbl_FADT.ResetValue, &AcpiGbl_FADT.ResetRegister); - if (ACPI_FAILURE(status)) { - printf("ACPI reset failed - %s\n", AcpiFormatException(status)); - } else { - DELAY(1000000); - printf("ACPI reset failed - timeout\n"); + } else if ((howto & RB_HALT) == 0 && sc->acpi_handle_reboot) { + if ((AcpiGbl_FADT.Flags & ACPI_FADT_RESET_REGISTER) || + (AcpiGbl_FADT.ResetRegister.BitWidth != 8) || + (AcpiGbl_FADT.ResetRegister.BitOffset != 0)) { + /* Reboot using the reset register. */ + status = AcpiHwLowLevelWrite( + AcpiGbl_FADT.ResetRegister.BitWidth, + AcpiGbl_FADT.ResetValue, &AcpiGbl_FADT.ResetRegister); + if (ACPI_FAILURE(status)) { + printf("ACPI reset failed - %s\n", AcpiFormatException(status)); + } else { + DELAY(1000000); + printf("ACPI reset failed - timeout\n"); + } } } else if (sc->acpi_do_disable && panicstr == NULL) { /* Basically, if the ResetRegister is filled in despite the FADT feature flags bit, trust it and move forward (Linux logic). That's the reason why my box reboots correctly on Linux and utterly hangs miserably on FreeBSD. I understand this is a BIOS/ACPI bug, I understand the keyboard controller reboot method should probably be emulated in the BIOS (though the vendor could argue they no longer support legacy methods which is to me not necessarily a bad thing), and I understand that FreeBSD is not Linux. With that all said, I don't see the downside here with respect to reboot with respect to either points (allow the user to force the issue or believe the ResetRegister values themselves as a test for validity). Feedback most appreciated! Thanks! -aps From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 02:23:44 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FA3C106566C; Mon, 26 Jan 2009 02:23:44 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by mx1.freebsd.org (Postfix) with ESMTP id 185B68FC1F; Mon, 26 Jan 2009 02:23:43 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so2277813yxb.13 for ; Sun, 25 Jan 2009 18:23:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ZfB7sxoiifnC8AtNK80vgBC8D0XbI5a+K2OFnAwg3NE=; b=NAu65q+lNqDwRCcSN9JKOF2HqE1EVNM82O1dFsm7d+2MBtj6sqDLiXLDiEqhpfPElF VGAWPeF+Fyh5gcVoaLdy2wb3casB4cfl2ySi0gsmozitc0OMDbwNA/gzMyOaqkfNpo5l DCgwVWZxuk7iRrJ4L9Cy3LbIPfKLIrBWNJh3M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=YYjPslbZ407fGZeGwRaZ7p3vvEnsY0vkF5ptJ5QQ2a2/ajCvnJ0mAQrVCJEepOsGgO tvGUyRFWckkzJwtZwLZmUbxoqjdZL7pZFA+jtKyCoDY236jmbiG4+9o5ht1WVTQyUr3d FU3R+ZZ/zOvFgUxL4mjAzASyiBuKh4NSU7ZpM= MIME-Version: 1.0 Received: by 10.90.56.17 with SMTP id e17mr334139aga.46.1232936623416; Sun, 25 Jan 2009 18:23:43 -0800 (PST) In-Reply-To: <3c0b01820901251735m4c6a1abfu37a1634818e1724a@mail.gmail.com> References: <3c0b01820901251735m4c6a1abfu37a1634818e1724a@mail.gmail.com> Date: Sun, 25 Jan 2009 21:23:43 -0500 Message-ID: <3c0b01820901251823p5c4536fcy3924d7a1209bfe71@mail.gmail.com> From: Alexander Sack To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Reset register flag versus the actual register X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jan 2009 02:23:45 -0000 Whoops!!! I had a brain fart... On Sun, Jan 25, 2009 at 8:35 PM, Alexander Sack wrote: > Hi Everybody: > > I've ran into the quintessential "it works on Linux but does not work > on FreeBSD" vendor comment regarding the boxes ability to reboot > successfully. I'm running FreeBSD-6.1 but this also applies the > FreeBSD-CURRENT as well. The problem boils down to the fact that the > BIOS does set the ResetRegister bit in the FADT feature flags. > However, I've noticed that latest stable Linux kernel has the > following logic with respect to the reset register: > > acpi_reboot(): > > 18 /* Is the reset register supported? */ > 19 if (!(acpi_gbl_FADT.flags & ACPI_FADT_RESET_REGISTER) || > 20 rr->bit_width != 8 || rr->bit_offset != 0) > 21 return; This checks the flag. I didn't see the NOT for some odd reason. Uggh, weird, I got to go back and now find out why on Linux uses the hook and FreeBSD does not. -aps From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 05:50:41 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63957106566B for ; Mon, 26 Jan 2009 05:50:41 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id E52D88FC0A for ; Mon, 26 Jan 2009 05:50:40 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.123.2.23] (h-66-166-149-52.snvacaid.covad.net [66.166.149.52]) by kientzle.com (8.12.9/8.12.9) with ESMTP id n0Q5obC1009402; Sun, 25 Jan 2009 21:50:39 -0800 (PST) (envelope-from kientzle@freebsd.org) Message-ID: <497D4F2B.2080506@freebsd.org> Date: Sun, 25 Jan 2009 21:50:35 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daichi GOTO References: <49796E09.7000805@ongs.co.jp> In-Reply-To: <49796E09.7000805@ongs.co.jp> Content-Type: multipart/mixed; boundary="------------020505070000060009050406" Cc: FreeBSD Current Subject: Re: sparse file issue?, dd(1) works well but tar(1) not on different partition X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jan 2009 05:50:41 -0000 This is a multi-part message in MIME format. --------------020505070000060009050406 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Daichi GOTO wrote: > > # cd /localapps/qemu/ > # tar cpf - disk0image | tar xpf - -S -C /nfshome/user/ > > gets follow error message. > > # tar cpf - disk0image | tar xpf - -S -C /nfshome/user/ > disk0image: Write request too large > tar: Error exit delayed from previous errors. Please try the attached patch to lib/libarchive/archive_write_disk.c, which should fix this. Cheers, Tim --------------020505070000060009050406 Content-Type: text/plain; name="archive_write_disk-fix-sparse.diff" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="archive_write_disk-fix-sparse.diff" SW5kZXg6IGFyY2hpdmVfd3JpdGVfZGlzay5jCj09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KLS0tIGFyY2hpdmVf d3JpdGVfZGlzay5jCShyZXZpc2lvbiAxODc3MDMpCisrKyBhcmNoaXZlX3dyaXRlX2Rpc2su YwkocmV2aXNpb24gMTg3NzA0KQpAQCAtMTc4LDYgKzE3OCw4IEBACiAJaW50CQkJIGZkOwog CS8qIEN1cnJlbnQgb2Zmc2V0IGZvciB3cml0aW5nIGRhdGEgdG8gdGhlIGZpbGUuICovCiAJ b2ZmX3QJCQkgb2Zmc2V0OworCS8qIExhc3Qgb2Zmc2V0IGFjdHVhbGx5IHdyaXR0ZW4gdG8g ZGlzay4gKi8KKwlvZmZfdAkJCSBmZF9vZmZzZXQ7CiAJLyogTWF4aW11bSBzaXplIG9mIGZp bGUsIC0xIGlmIHVua25vd24uICovCiAJb2ZmX3QJCQkgZmlsZXNpemU7CiAJLyogRGlyIHdl IHdlcmUgaW4gYmVmb3JlIHRoaXMgcmVzdG9yZTsgb25seSBmb3IgZGVlcCBwYXRocy4gKi8K QEAgLTE4Nyw4ICsxODksNiBAQAogCS8qIFVJRC9HSUQgdG8gdXNlIGluIHJlc3RvcmluZyB0 aGlzIGVudHJ5LiAqLwogCXVpZF90CQkJIHVpZDsKIAlnaWRfdAkJCSBnaWQ7Ci0JLyogTGFz dCBvZmZzZXQgd3JpdHRlbiB0byBkaXNrLiAqLwotCW9mZl90CQkJIGxhc3Rfb2Zmc2V0Owog fTsKIAogLyoKQEAgLTIzNSw3ICsyMzUsNyBAQAogc3RhdGljIGdpZF90CXRyaXZpYWxfbG9v a3VwX2dpZCh2b2lkICosIGNvbnN0IGNoYXIgKiwgZ2lkX3QpOwogc3RhdGljIHVpZF90CXRy aXZpYWxfbG9va3VwX3VpZCh2b2lkICosIGNvbnN0IGNoYXIgKiwgdWlkX3QpOwogc3RhdGlj IHNzaXplX3QJd3JpdGVfZGF0YV9ibG9jayhzdHJ1Y3QgYXJjaGl2ZV93cml0ZV9kaXNrICos Ci0JCSAgICBjb25zdCBjaGFyICosIHNpemVfdCwgb2ZmX3QpOworCQkgICAgY29uc3QgY2hh ciAqLCBzaXplX3QpOwogCiBzdGF0aWMgc3RydWN0IGFyY2hpdmVfdnRhYmxlICphcmNoaXZl X3dyaXRlX2Rpc2tfdnRhYmxlKHZvaWQpOwogCkBAIC0zMzcsNyArMzM3LDcgQEAKIAl9CiAJ YS0+ZW50cnkgPSBhcmNoaXZlX2VudHJ5X2Nsb25lKGVudHJ5KTsKIAlhLT5mZCA9IC0xOwot CWEtPmxhc3Rfb2Zmc2V0ID0gMDsKKwlhLT5mZF9vZmZzZXQgPSAwOwogCWEtPm9mZnNldCA9 IDA7CiAJYS0+dWlkID0gYS0+dXNlcl91aWQ7CiAJYS0+bW9kZSA9IGFyY2hpdmVfZW50cnlf bW9kZShhLT5lbnRyeSk7CkBAIC01MTMsOSArNTEzLDkgQEAKIH0KIAogc3RhdGljIHNzaXpl X3QKLXdyaXRlX2RhdGFfYmxvY2soc3RydWN0IGFyY2hpdmVfd3JpdGVfZGlzayAqYSwKLSAg ICBjb25zdCBjaGFyICpidWZmLCBzaXplX3Qgc2l6ZSwgb2ZmX3Qgb2Zmc2V0KQord3JpdGVf ZGF0YV9ibG9jayhzdHJ1Y3QgYXJjaGl2ZV93cml0ZV9kaXNrICphLCBjb25zdCBjaGFyICpi dWZmLCBzaXplX3Qgc2l6ZSkKIHsKKwl1aW50NjRfdCBzdGFydF9zaXplID0gc2l6ZTsKIAlz c2l6ZV90IGJ5dGVzX3dyaXR0ZW4gPSAwOwogCXNzaXplX3QgYmxvY2tfc2l6ZSA9IDAsIGJ5 dGVzX3RvX3dyaXRlOwogCkBAIC01MzgsOCArNTM4LDkgQEAKICNlbmRpZgogCX0KIAotCWlm IChhLT5maWxlc2l6ZSA+PSAwICYmIChvZmZfdCkob2Zmc2V0ICsgc2l6ZSkgPiBhLT5maWxl c2l6ZSkKLQkJc2l6ZSA9IChzaXplX3QpKGEtPmZpbGVzaXplIC0gb2Zmc2V0KTsKKwkvKiBJ ZiB0aGlzIHdyaXRlIHdvdWxkIHJ1biBiZXlvbmQgdGhlIGZpbGUgc2l6ZSwgdHJ1bmNhdGUg aXQuICovCisJaWYgKGEtPmZpbGVzaXplID49IDAgJiYgKG9mZl90KShhLT5vZmZzZXQgKyBz aXplKSA+IGEtPmZpbGVzaXplKQorCQlzdGFydF9zaXplID0gc2l6ZSA9IChzaXplX3QpKGEt PmZpbGVzaXplIC0gYS0+b2Zmc2V0KTsKIAogCS8qIFdyaXRlIHRoZSBkYXRhLiAqLwogCXdo aWxlIChzaXplID4gMCkgewpAQCAtNTU1LDcgKzU1Niw3IEBACiAJCQkJaWYgKCpwICE9ICdc MCcpCiAJCQkJCWJyZWFrOwogCQkJfQotCQkJb2Zmc2V0ICs9IHAgLSBidWZmOworCQkJYS0+ b2Zmc2V0ICs9IHAgLSBidWZmOwogCQkJc2l6ZSAtPSBwIC0gYnVmZjsKIAkJCWJ1ZmYgPSBw OwogCQkJaWYgKHNpemUgPT0gMCkKQEAgLTU2MywyMiArNTY0LDI1IEBACiAKIAkJCS8qIENh bGN1bGF0ZSBuZXh0IGJsb2NrIGJvdW5kYXJ5IGFmdGVyIG9mZnNldC4gKi8KIAkJCWJsb2Nr X2VuZAotCQkJICAgID0gKG9mZnNldCAvIGJsb2NrX3NpemUpICogYmxvY2tfc2l6ZSArIGJs b2NrX3NpemU7CisJCQkgICAgPSAoYS0+b2Zmc2V0IC8gYmxvY2tfc2l6ZSArIDEpICogYmxv Y2tfc2l6ZTsKIAogCQkJLyogSWYgdGhlIGFkanVzdGVkIHdyaXRlIHdvdWxkIGNyb3NzIGJs b2NrIGJvdW5kYXJ5LAogCQkJICogdHJ1bmNhdGUgaXQgdG8gdGhlIGJsb2NrIGJvdW5kYXJ5 LiAqLwogCQkJYnl0ZXNfdG9fd3JpdGUgPSBzaXplOwotCQkJaWYgKG9mZnNldCArIGJ5dGVz X3RvX3dyaXRlID4gYmxvY2tfZW5kKQotCQkJCWJ5dGVzX3RvX3dyaXRlID0gYmxvY2tfZW5k IC0gb2Zmc2V0OworCQkJaWYgKGEtPm9mZnNldCArIGJ5dGVzX3RvX3dyaXRlID4gYmxvY2tf ZW5kKQorCQkJCWJ5dGVzX3RvX3dyaXRlID0gYmxvY2tfZW5kIC0gYS0+b2Zmc2V0OwogCQl9 CiAKIAkJLyogU2VlayBpZiBuZWNlc3NhcnkgdG8gdGhlIHNwZWNpZmllZCBvZmZzZXQuICov Ci0JCWlmIChvZmZzZXQgIT0gYS0+bGFzdF9vZmZzZXQpIHsKLQkJCWlmIChsc2VlayhhLT5m ZCwgb2Zmc2V0LCBTRUVLX1NFVCkgPCAwKSB7CisJCWlmIChhLT5vZmZzZXQgIT0gYS0+ZmRf b2Zmc2V0KSB7CisJCQlpZiAobHNlZWsoYS0+ZmQsIGEtPm9mZnNldCwgU0VFS19TRVQpIDwg MCkgewogCQkJCWFyY2hpdmVfc2V0X2Vycm9yKCZhLT5hcmNoaXZlLCBlcnJubywKIAkJCQkg ICAgIlNlZWsgZmFpbGVkIik7CiAJCQkJcmV0dXJuIChBUkNISVZFX0ZBVEFMKTsKIAkJCX0K KwkJCWEtPmZkX29mZnNldCA9IGEtPm9mZnNldDsKKwkJCWEtPmFyY2hpdmUuZmlsZV9wb3Np dGlvbiA9IGEtPm9mZnNldDsKKwkJCWEtPmFyY2hpdmUucmF3X3Bvc2l0aW9uID0gYS0+b2Zm c2V0OwogIAkJfQogCQlieXRlc193cml0dGVuID0gd3JpdGUoYS0+ZmQsIGJ1ZmYsIGJ5dGVz X3RvX3dyaXRlKTsKIAkJaWYgKGJ5dGVzX3dyaXR0ZW4gPCAwKSB7CkBAIC01ODcsMTIgKzU5 MSwxMiBAQAogCQl9CiAJCWJ1ZmYgKz0gYnl0ZXNfd3JpdHRlbjsKIAkJc2l6ZSAtPSBieXRl c193cml0dGVuOwotCQlvZmZzZXQgKz0gYnl0ZXNfd3JpdHRlbjsKKwkJYS0+b2Zmc2V0ICs9 IGJ5dGVzX3dyaXR0ZW47CiAJCWEtPmFyY2hpdmUuZmlsZV9wb3NpdGlvbiArPSBieXRlc193 cml0dGVuOwogCQlhLT5hcmNoaXZlLnJhd19wb3NpdGlvbiArPSBieXRlc193cml0dGVuOwot CQlhLT5sYXN0X29mZnNldCA9IGEtPm9mZnNldCA9IG9mZnNldDsKKwkJYS0+ZmRfb2Zmc2V0 ID0gYS0+b2Zmc2V0OwogCX0KLQlyZXR1cm4gKGJ5dGVzX3dyaXR0ZW4pOworCXJldHVybiAo c3RhcnRfc2l6ZSAtIHNpemUpOwogfQogCiBzdGF0aWMgc3NpemVfdApAQCAtNjA1LDkgKzYw OSw5IEBACiAJX19hcmNoaXZlX2NoZWNrX21hZ2ljKCZhLT5hcmNoaXZlLCBBUkNISVZFX1dS SVRFX0RJU0tfTUFHSUMsCiAJICAgIEFSQ0hJVkVfU1RBVEVfREFUQSwgImFyY2hpdmVfd3Jp dGVfZGlza19ibG9jayIpOwogCi0JciA9IHdyaXRlX2RhdGFfYmxvY2soYSwgYnVmZiwgc2l6 ZSwgb2Zmc2V0KTsKLQotCWlmIChyIDwgMCkKKwlhLT5vZmZzZXQgPSBvZmZzZXQ7CisJciA9 IHdyaXRlX2RhdGFfYmxvY2soYSwgYnVmZiwgc2l6ZSk7CisJaWYgKHIgPCBBUkNISVZFX09L KQogCQlyZXR1cm4gKHIpOwogCWlmICgoc2l6ZV90KXIgPCBzaXplKSB7CiAJCWFyY2hpdmVf c2V0X2Vycm9yKCZhLT5hcmNoaXZlLCAwLApAQCAtNjI1LDcgKzYyOSw3IEBACiAJX19hcmNo aXZlX2NoZWNrX21hZ2ljKCZhLT5hcmNoaXZlLCBBUkNISVZFX1dSSVRFX0RJU0tfTUFHSUMs CiAJICAgIEFSQ0hJVkVfU1RBVEVfREFUQSwgImFyY2hpdmVfd3JpdGVfZGF0YSIpOwogCi0J cmV0dXJuICh3cml0ZV9kYXRhX2Jsb2NrKGEsIGJ1ZmYsIHNpemUsIGEtPm9mZnNldCkpOwor CXJldHVybiAod3JpdGVfZGF0YV9ibG9jayhhLCBidWZmLCBzaXplKSk7CiB9CiAKIHN0YXRp YyBpbnQKQEAgLTY0Niw3ICs2NTAsNyBAQAogCQkvKiBUaGVyZSdzIG5vIGZpbGUuICovCiAJ fSBlbHNlIGlmIChhLT5maWxlc2l6ZSA8IDApIHsKIAkJLyogRmlsZSBzaXplIGlzIHVua25v d24sIHNvIHdlIGNhbid0IHNldCB0aGUgc2l6ZS4gKi8KLQl9IGVsc2UgaWYgKGEtPmxhc3Rf b2Zmc2V0ID09IGEtPmZpbGVzaXplKSB7CisJfSBlbHNlIGlmIChhLT5mZF9vZmZzZXQgPT0g YS0+ZmlsZXNpemUpIHsKIAkJLyogTGFzdCB3cml0ZSBlbmRlZCBhdCBleGFjdGx5IHRoZSBm aWxlc2l6ZTsgd2UncmUgZG9uZS4gKi8KIAkJLyogSG9wZWZ1bGx5LCB0aGlzIGlzIHRoZSBj b21tb24gY2FzZS4gKi8KIAl9IGVsc2Ugewo= --------------020505070000060009050406-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 09:40:07 2009 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 69642106566B; Mon, 26 Jan 2009 09:40:07 +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 20E618FC1F; Mon, 26 Jan 2009 09:40:07 +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 6A16A41C678; Mon, 26 Jan 2009 10:40:05 +0100 (CET) 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 h-p9pSAeQru9; Mon, 26 Jan 2009 10:40:05 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id 0C35E41C670; Mon, 26 Jan 2009 10:40:05 +0100 (CET) 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 A4C5C4448F3; Mon, 26 Jan 2009 09:39:23 +0000 (UTC) Date: Mon, 26 Jan 2009 09:39:23 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: FreeBSD current mailing list In-Reply-To: <20090122225404.U45399@maildrop.int.zabbadoz.net> Message-ID: <20090126093817.H45399@maildrop.int.zabbadoz.net> References: <20090122225404.U45399@maildrop.int.zabbadoz.net> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD net mailing list Subject: Re: Need testers for a network cleanup patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2009 09:40:07 -0000 On Thu, 22 Jan 2009, Bjoern A. Zeeb wrote: Hi, > while cleaning up protosw things I found that rip6_output was most > likely never called from pr_output and after a short talk with Robert > the conclusion was that the same had been true for rip_output. > > Before I am going to remove the initializations I made the two > rip{,6}_output functions calling panic(). > > I have a patch for HEAD here: > http://people.freebsd.org/~bz/20090122-03-pr_output.diff > > and one for 7-STABLE here (compiled but not booted): > http://people.freebsd.org/~bz/20090122-04-pr_output-7STABLE.diff > > > I am confident it will not panic (at least for HEAD;) but not 100% > sure so you can run this on your test or devel machine but I'd not > run it on a production machine. > > If you are going to use the 7-STABLE patch make sure to have debugging > support in your kernel as well so we could get backtraces in the > unlikely event of panic. > > > Please reply directly to me if you have (un)successfully run the > patch and do NOT to the lists. > In case you think you run it successfully mail me after a > 2-3 days, and _not_ with an "it booted" message! ;-) In case you tested, please let me know. /bz -- Bjoern A. Zeeb The greatest risk is not taking one. From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 11:22:29 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D0E210656CF for ; Mon, 26 Jan 2009 11:22:29 +0000 (UTC) (envelope-from michiel@boland.org) Received: from smtp-vbr7.xs4all.nl (smtp-vbr7.xs4all.nl [194.109.24.27]) by mx1.freebsd.org (Postfix) with ESMTP id EDDD88FC24 for ; Mon, 26 Jan 2009 11:22:28 +0000 (UTC) (envelope-from michiel@boland.org) Received: from aja.boland.org (91-43-215.ftth.xms.internl.net [82.215.43.91]) (authenticated bits=0) by smtp-vbr7.xs4all.nl (8.13.8/8.13.8) with ESMTP id n0QBMNXq059123 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 26 Jan 2009 12:22:27 +0100 (CET) (envelope-from michiel@boland.org) Message-ID: <497D9CEF.7020807@boland.org> Date: Mon, 26 Jan 2009 12:22:23 +0100 From: Michiel Boland User-Agent: Thunderbird 2.0.0.19 (X11/20090125) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner Subject: panic in rtrequest1_fib X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jan 2009 11:22:32 -0000 -CURRENT from 25 jan panic: _rw_wlock_hard: recursing but non-recursive rw radix node head @ /usr/src/sys/net/route.c:831 I'll keep vmcore around for a while. #0 doadump () at pcpu.h:246 #1 0xc082f7be in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:420 #2 0xc082fa92 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:576 #3 0xc082d986 in _rw_wlock_hard (rw=0xc577e680, tid=3312676864, file=0xc0bf0410 "/usr/src/sys/net/route.c", line=831) at /usr/src/sys/kern/kern_rwlock.c:592 #4 0xc082e23e in _rw_wlock (rw=0xc577e680, file=0xc0bf0410 "/usr/src/sys/net/route.c", line=831) at /usr/src/sys/kern/kern_rwlock.c:218 #5 0xc08dea95 in rtrequest1_fib (req=2, info=0xe5b22b1c, ret_nrt=0x0, fibnum=0) at /usr/src/sys/net/route.c:831 #6 0xc08df62e in rtrequest_fib (req=2, dst=0xc99a91c0, gateway=0xc99a91d0, netmask=0x0, flags=262167, ret_nrt=0x0, fibnum=0) at /usr/src/sys/net/route.c:680 #7 0xc091deeb in in_rtrequest (req=2, dst=0xc99a91c0, gateway=0xc99a91d0, netmask=0x0, flags=262167, ret_nrt=0x0, fibnum=0) at /usr/src/sys/netinet/in_rmx.c:459 #8 0xc091e42f in in_rtqkill (rn=0xc6032068, rock=0xe5b22bdc) at /usr/src/sys/netinet/in_rmx.c:213 #9 0xc08dc5c5 in rn_walktree (h=0xc577e600, f=0xc091e3b0 , w=0xe5b22bdc) at /usr/src/sys/net/radix.c:1107 #10 0xc091e031 in in_rtqdrain () at /usr/src/sys/netinet/in_rmx.c:330 #11 0xc0921d5d in ip_drain () at /usr/src/sys/netinet/ip_input.c:1210 #12 0xc081e6f2 in mb_reclaim (junk=0x0) at /usr/src/sys/kern/kern_mbuf.c:681 #13 0xc0a6cff9 in vm_pageout () at /usr/src/sys/vm/vm_pageout.c:692 #14 0xc080c728 in fork_exit (callout=0xc0a6c950 , arg=0x0, frame=0xe5b22d38) at /usr/src/sys/kern/kern_fork.c:821 #15 0xc0b16c30 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:270 From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 11:39:45 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A317D106566C for ; Mon, 26 Jan 2009 11:39:45 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from smtp.timeweb.ru (smtp.timeweb.ru [217.170.79.85]) by mx1.freebsd.org (Postfix) with ESMTP id 5B7A28FC14 for ; Mon, 26 Jan 2009 11:39:45 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1LRPof-00022p-HP for freebsd-current@freebsd.org; Mon, 26 Jan 2009 14:39:45 +0300 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 9DA73139DF for ; Mon, 26 Jan 2009 14:40:00 +0300 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id 4D0B7108837; Mon, 26 Jan 2009 14:40:44 +0000 (UTC) Date: Mon, 26 Jan 2009 14:40:44 +0000 From: Dmitry Marakasov To: freebsd-current@freebsd.org Message-ID: <20090126144044.GB6054@hades.panopticon> References: <20090123221826.GB30982@deprived.panopticon> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20090123221826.GB30982@deprived.panopticon> User-Agent: Mutt/1.5.18 (2008-05-17) Subject: Data corruption with checksum offloading enabled (Was: NFS data corruption) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jan 2009 11:39:45 -0000 I was suggested by Andrzej Tobola to try disabling txcsum on a network interface. I've disabled both rxcsum and txcsum, and that solved a problem. Judging from that this helped Andrzej with sk(4) and me with ale(4) driver, that's not a single driver problem. Does his mean that we have global problems with checksum offloading? -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 11:54:56 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E30911065672; Mon, 26 Jan 2009 11:54:56 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from smtp.timeweb.ru (smtp.timeweb.ru [217.170.79.85]) by mx1.freebsd.org (Postfix) with ESMTP id 6945B8FC18; Mon, 26 Jan 2009 11:54:56 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1LRQ3N-00062M-5x; Mon, 26 Jan 2009 14:54:57 +0300 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 04E7213A04; Mon, 26 Jan 2009 14:55:12 +0300 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id 747E1108837; Mon, 26 Jan 2009 14:55:55 +0000 (UTC) Date: Mon, 26 Jan 2009 14:55:55 +0000 From: Dmitry Marakasov To: freebsd-hardware@freebsd.org Message-ID: <20090126145555.GC6054@hades.panopticon> References: <20090119140424.GA56409@hades.panopticon> <20090121124555.GA99191@hades.panopticon> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20090121124555.GA99191@hades.panopticon> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-current@freebsd.org Subject: Re: ASUS mobo for desktop X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jan 2009 11:54:57 -0000 * Dmitry Marakasov (amdmi3@amdmi3.ru) wrote: > > I'm planning to upgrade my desktop to C2D and am picking motherboard > > for it. I prefer ASUS and I guess P5Q model line is actual now, but > > there are quite a bunch of specific models, so it's hard enough to > > pick. Are there any positive experience with those mobos (I.e. no > > problems with onboard NIC, ATA/SATA controllers and other stuff)? > > I'm planning to install 7.1 i386. Also I'm planning to install 4GB > > RAM there - I'll just get my 3.25 or 3.5, right (I think I've heard > > of some freezes with 4GB)? > > I've bought Asus P5Q. For now I've just tested it with my bootable > flash (-CURRENT from around September) - onboard Ethernet (Atheros) > and PATA controller (Marvell) didn't work. However, after updating > kernel to recent CURRENT Ethernet worked and PATA hard drive was > detected). Now I'll check whether I really need CURRENT there (or > 7.1 would suffice), move my desktop to that box, test it for a while > and report some more info. As promised, some more info. - 7.1 is not enough, so I'm using current. - With current, everything works so far. Didn't use it for much serious work yet, but played Quake4 in wine for ~6 hrs :) - There was problem with ale(4) (see thread 'NFS data corruption' on freebsd-current@) - fixed with turning rxcsum and rxcsum off on the interface. - Also nvidia-driver refused to work hanging the system when 4GB RAM were installed in the box. Had to leave only 2GB Unrelated to hardware and current, I've used gjournal for a first time in this install, and found that the system is really unresponsive when writing large files. In general, I'd say I'm satisfied. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 13:05:11 2009 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 5C925106564A for ; Mon, 26 Jan 2009 13:05:11 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: from web63903.mail.re1.yahoo.com (web63903.mail.re1.yahoo.com [69.147.97.118]) by mx1.freebsd.org (Postfix) with SMTP id E77268FC1D for ; Mon, 26 Jan 2009 13:05:10 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: (qmail 90715 invoked by uid 60001); 26 Jan 2009 13:05:10 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID; b=adM1MggafSUUXnSybRJZLON5cz7ajW40Uuz/FrZLbeYyMem4bLWDsI25eK8DmnBhzxFewwI3CNncwawA/X/yy/Z/vJXZMwxOEF/uRyUPk3wIfYQ5wdq3OgxaWsgrxSOa3ipFvWKVOu0EBKf69dkItN1Re+NU21b4gFlOIveISRw=; X-YMail-OSG: 2BIr304VM1kQwR7aVO0hquLDdSEBkkTT2dChl.l1gimq2NO3pbQ4aeaX73LGGjMiYnppli4Phc7gFcwu5cFUQMe1eEOwpjb5OeRVPFf_1eP.Y2BPtGUbJABJ_e449PB2L7uyH0SOyMrJs7kBs6OEP6I7vC0- Received: from [98.242.222.229] by web63903.mail.re1.yahoo.com via HTTP; Mon, 26 Jan 2009 05:05:10 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Mon, 26 Jan 2009 05:05:10 -0800 (PST) From: Barney Cordoba To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <497758.90319.qm@web63903.mail.re1.yahoo.com> Cc: Subject: DMA bounce buffers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: barney_cordoba@yahoo.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, 26 Jan 2009 13:05:11 -0000 I have a problem with the ixgbe driver, where bus_dmamap_load_mbuf_sg() is failing. The underlying failure is reserve_bounce_pages(). It seems that there aren't any bounce pages allocated. What could be the cause of this? Is there some tunable? Barney From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 14:21:59 2009 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 8CB721065670 for ; Mon, 26 Jan 2009 14:21:59 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.185]) by mx1.freebsd.org (Postfix) with ESMTP id 44BD48FC13 for ; Mon, 26 Jan 2009 14:21:59 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: by rn-out-0910.google.com with SMTP id k32so2217667rnd.12 for ; Mon, 26 Jan 2009 06:21:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=0um5dk94S8X+3luA+DgGO8VRH+PlASoXbKUTdWbFcTg=; b=jCiUY4ev/q1dS1LSPf6zbl5Pc7+xIRrhNwUnCorzvaxW2u60eIvP8Z1XPxDhVXONVz PbLa7h2+wqEQ4xQnWsbsIrLLvtHHIafMg4yZbf/om2zuTIpi5U2wZQOBe69aL1E6n9my Q/LJ19bW05/MxgBP75bRI+uAnWmPO967znFsE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=A2RkFte26A1llJeCYP3mCT50TQxrdLk/WhTV/9LuR1XNSyUKcLy1uAIrzlUeiQaFJN 9yiRgRfgxh4qr10s6U0vAWrd0n9A6xHheaw5leiOGksGaYgo9Uzvg5BYkfJnNyswrFMC Za6jFLCLNapAGf1GYtr8kQa559nODWP0L7mqU= MIME-Version: 1.0 Received: by 10.151.147.16 with SMTP id z16mr865327ybn.52.1232978262276; Mon, 26 Jan 2009 05:57:42 -0800 (PST) In-Reply-To: <497758.90319.qm@web63903.mail.re1.yahoo.com> References: <497758.90319.qm@web63903.mail.re1.yahoo.com> Date: Mon, 26 Jan 2009 21:57:42 +0800 Message-ID: From: Sepherosa Ziehau To: barney_cordoba@yahoo.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: DMA bounce buffers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jan 2009 14:21:59 -0000 On Mon, Jan 26, 2009 at 9:05 PM, Barney Cordoba wrote: > I have a problem with the ixgbe driver, where bus_dmamap_load_mbuf_sg() is > failing. The underlying failure is reserve_bounce_pages(). It seems that > there aren't any bounce pages allocated. What could be the cause of this? Is there some tunable? I don't think the hardware supported ixgbe(4) will need bounce pages on RX/TX buffers (according to data sheet, the hardware supports full 64bits address space accessing and no alignment constraints on RX/TX buffer start address). However, the driver's buffer busdma is kinda misconfigured: in ixgbe_allocate_{transmit,receive}_buffers(), the buffers' alignment is set to PAGE_SIZE (?!), this means that almost all TX/RX operation will require bouncing. The best case is poor performance due to additional and unnecessary memory copy in bus_dmamap_sync(); the worst case is completely unfunction NIC due to RX ring could not be filled during ifnet.if_init(). Best Regards, sephe -- Live Free or Die From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 14:29:24 2009 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 723EB106564A for ; Mon, 26 Jan 2009 14:29:24 +0000 (UTC) (envelope-from ken@mthelicon.com) Received: from hercules.mthelicon.com (hercules.mthelicon.com [IPv6:2001:49f0:2023::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3811F8FC0C for ; Mon, 26 Jan 2009 14:29:24 +0000 (UTC) (envelope-from ken@mthelicon.com) Received: from PegaPegII (93-152-14-233.daisydsl.managedbroadband.co.uk [93.152.14.233]) (authenticated bits=0) by hercules.mthelicon.com (8.14.3/8.14.3) with ESMTP id n0QETMW8006760 for ; Mon, 26 Jan 2009 14:29:23 GMT (envelope-from ken@mthelicon.com) Message-ID: <88F83F222F2347A088A7A7AE8ABF2558@PegaPegII> From: "Pegasus Mc Cleaft" To: Date: Mon, 26 Jan 2009 14:29:21 -0000 Organization: Feathers MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6001.18000 X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049 X-Antivirus: avast! (VPS 090125-0, 25/01/2009), Outbound message X-Antivirus-Status: Clean Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: KDE4/DBUS weirdness on -Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Pegasus Mc Cleaft List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2009 14:29:24 -0000 Hello Current,=20 First I appologize for not having much debug information, as I = havent been able to pinpoint an exact cause yet, but I noticed something = odd with -Current 25012009. After updating all my ports while running on = a 23012009-Current and rebooting, everything seemed to work fine; = however, after updating usr/src from about 11pm on 25012009, KDE started = to act really strange.=20 After poking around with various things, I discovered that the dbus = daemon stopped responding. This manifisted its self by clicking on icons = and having the window manager lock up for about 1 minute. After which, a = message came back that the dbus daemon could not be contacted. I tried = dbus-monitor, but got exactly the same message. I tried both USB1 and = USB2 stacks, just to make sure, but could never get things to copperate. = I did find, right after logging in through KDM, I could get a single = application to launch (So DBUS had to been ok at this point) but after = about 5 seconds, DBUS would stop responding) I reverted my kernel to the version before the upgrade (kernel.old) = and everything started to work fine again (I am running on the more = recent world and the old kernel).=20 I am not really sure how to find the exact failure here, but I can = duplicate the fault by loading the 25th's kernel.=20 Machine is a Core2-quad running on AMD64, 8 Gig, USB1 or USB2 stack. Does anyone have any insight to what this might be? (Or how I might = be able to diagnose further) ~Peg From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 15:38:34 2009 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 86AE9106566B for ; Mon, 26 Jan 2009 15:38:34 +0000 (UTC) (envelope-from villa.alberto@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.29]) by mx1.freebsd.org (Postfix) with ESMTP id 3F4798FC17 for ; Mon, 26 Jan 2009 15:38:34 +0000 (UTC) (envelope-from villa.alberto@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so2348954yxb.13 for ; Mon, 26 Jan 2009 07:38:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=xe14auDckkKeFCfK3nK0Udto8GQz7N/jWOkX7HwNjCg=; b=FoF1TebPW5ar+98NvcD2OslqWVtSDr+zgHryYAsa5vRsmdAXLV02nJQAaouC2FAsK5 QXV8PahVsjzKfe75ui4p4zHCNSjamCnEIAWHxyPOtdRBut2FH0gwDp6Va6y9rZucaE2b hpsWr8jQFm0N6Dl4epRPJiSTmn59zCxKpyPtA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=htOwxaBmrW3fV+aEqAR6oeCrA3MhQRByzOByZc+VOu9iTgJ3bzWlXCObWrhBA7Mpa8 3c9TR/qAlqKC0Di8eja/Q7+Xw+vU9R2a7ofiNdOpEdzDv6yZs4TzUc6isA4aSjOg8aV8 0i6lDFb8Uhxn5I3nMkB/JAv+attYMzewv8X28= MIME-Version: 1.0 Received: by 10.151.114.9 with SMTP id r9mr84078ybm.84.1232982678539; Mon, 26 Jan 2009 07:11:18 -0800 (PST) In-Reply-To: References: <88F83F222F2347A088A7A7AE8ABF2558@PegaPegII> Date: Mon, 26 Jan 2009 15:11:18 +0000 Message-ID: From: Alberto Villa To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: KDE4/DBUS weirdness 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: Mon, 26 Jan 2009 15:38:35 -0000 On Mon, Jan 26, 2009 at 3:09 PM, Alberto Villa wrote: > try mailing at kde-freebsd@freebsd.org i'm sorry, it's kde-freebsd@kde.org -- Alberto Villa From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 15:40:35 2009 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 C4FAE106567D for ; Mon, 26 Jan 2009 15:40:35 +0000 (UTC) (envelope-from villa.alberto@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id 78D548FC17 for ; Mon, 26 Jan 2009 15:40:35 +0000 (UTC) (envelope-from villa.alberto@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so2347629ywe.13 for ; Mon, 26 Jan 2009 07:40:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=S1LHZJFacWfRIJtqnKqK+gp0sghLqTIIgHCxaDfgLzQ=; b=saUZhxC3LiHJMgOjO141EPZaJrEZZTsimQnwEpC4Yjn+95Z08/hM0Y8qZW9b8FEcPz QuY+Wc/u+hcqxjgEQ8A+01ywRLz1UML82Wdyioo9GZ8AWaNEgvRhKY0rKw/zVDAcKabG fUmoxCScmrEaDMtcTxNe+gSn0EELG85UX7UXo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=I/dYqqG1IxzREiIPaqUzP0ZVpqhQDxM90icn17Mpz4pQCnyXgYB5H0DAYMK0VIFlRr 9dWYcKhj3uE05YQPDZNQDNniDvcCuxbyBaC9wbL5IMwEo1f//OpYrMjgZA8qdgeqpren UEpDbQtb+QXNeC+fHdCt53pgtvFraGWxF8ADk= MIME-Version: 1.0 Received: by 10.150.122.18 with SMTP id u18mr1846411ybc.170.1232982585061; Mon, 26 Jan 2009 07:09:45 -0800 (PST) In-Reply-To: <88F83F222F2347A088A7A7AE8ABF2558@PegaPegII> References: <88F83F222F2347A088A7A7AE8ABF2558@PegaPegII> Date: Mon, 26 Jan 2009 15:09:45 +0000 Message-ID: From: Alberto Villa To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Pegasus Mc Cleaft Subject: Re: KDE4/DBUS weirdness 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: Mon, 26 Jan 2009 15:40:38 -0000 On Mon, Jan 26, 2009 at 2:29 PM, Pegasus Mc Cleaft wrote: > Does anyone have any insight to what this might be? (Or how I might be able to diagnose further) that's not a new problem, but your information might help try mailing at kde-freebsd@freebsd.org -- Alberto Villa From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 16:37:40 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12DD8106566B for ; Mon, 26 Jan 2009 16:37:40 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from hosting.lissyara.su (hosting.lissyara.su [77.221.149.162]) by mx1.freebsd.org (Postfix) with ESMTP id 667908FC18 for ; Mon, 26 Jan 2009 16:37:37 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from [89.178.150.64] (port=35110 helo=HP.lissyara.su) by hosting.lissyara.su with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LRUSt-000EuA-Ov for freebsd-current@freebsd.org; Mon, 26 Jan 2009 19:37:36 +0300 Message-ID: <497DE6CF.9060509@lissyara.su> Date: Mon, 26 Jan 2009 19:37:35 +0300 From: Alex Keda User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; ru-RU; rv:1.8.1.19) Gecko/20090126 Thunderbird/2.0.0.19 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Description: if spam count > 60 - this is spam X-Spam-Count: 0 X-Descriptions: powered by www.lissyara.su X-Bounce-ID: hosting.lissyara.su Subject: kernel: powernow0: set freq failed, err 6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jan 2009 16:37:40 -0000 HP$ uname -a FreeBSD HP.lissyara.su 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sat Jan 24 22:03:26 MSK 2009 lissyara@HP.lissyara.su:/usr/obj/usr/src/sys/HP amd64 HP$ after last update I have in logs: Jan 26 19:21:44 HP syslogd: kernel boot file is /boot/kernel/kernel Jan 26 19:21:44 HP kernel: Copyright (c) 1992-2009 The FreeBSD Project. Jan 26 19:21:44 HP kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Jan 26 19:21:44 HP kernel: The Regents of the University of California. All rights reserved. Jan 26 19:21:44 HP kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Jan 26 19:21:44 HP kernel: FreeBSD 8.0-CURRENT #0: Sat Jan 24 22:03:26 MSK 2009 Jan 26 19:21:44 HP kernel: lissyara@HP.lissyara.su:/usr/obj/usr/src/sys/HP Jan 26 19:21:44 HP kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Jan 26 19:21:44 HP kernel: CPU: AMD Turion(tm) 64 X2 Mobile Technology TL-60 (1995.01-MHz K8-class CPU) Jan 26 19:21:44 HP kernel: Origin = "AuthenticAMD" Id = 0x60f82 Stepping = 2 Jan 26 19:21:44 HP kernel: Features=0x178bfbff Jan 26 19:21:44 HP kernel: Features2=0x2001 Jan 26 19:21:44 HP kernel: AMD Features=0xea500800 Jan 26 19:21:44 HP kernel: AMD Features2=0x11f Jan 26 19:21:44 HP kernel: Cores per package: 2 Jan 26 19:21:44 HP kernel: usable memory = 1998229504 (1905 MB) Jan 26 19:21:44 HP kernel: avail memory = 1929814016 (1840 MB) Jan 26 19:21:44 HP kernel: ACPI APIC Table: Jan 26 19:21:44 HP kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs Jan 26 19:21:44 HP kernel: cpu0 (BSP): APIC ID: 0 Jan 26 19:21:44 HP kernel: cpu1 (AP): APIC ID: 1 Jan 26 19:21:44 HP kernel: ACPI Error (tbfadt-0516): 32/64X address mismatch in "Pm2ControlBlock": [ 8800] [ 0 8100], using 64X [20070320] Jan 26 19:21:44 HP kernel: ioapic0: Changing APIC ID to 2 Jan 26 19:21:44 HP kernel: ioapic0 irqs 0-23 on motherboard Jan 26 19:21:44 HP kernel: kbd1 at kbdmux0 Jan 26 19:21:44 HP kernel: acpi0: on motherboard Jan 26 19:21:44 HP kernel: acpi0: [ITHREAD] Jan 26 19:21:44 HP kernel: acpi0: Power Button (fixed) Jan 26 19:21:44 HP kernel: unknown: I/O range not supported Jan 26 19:21:44 HP kernel: acpi0: reservation of 0, 8000000 (3) failed Jan 26 19:21:44 HP kernel: acpi0: reservation of 100000, fff00000 (3) failed Jan 26 19:21:44 HP kernel: Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 Jan 26 19:21:44 HP kernel: acpi_timer0: <32-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 Jan 26 19:21:44 HP kernel: acpi_ec0: port 0x62,0x66 on acpi0 Jan 26 19:21:44 HP kernel: pcib0: port 0xcf8-0xcff on acpi0 Jan 26 19:21:44 HP kernel: pci0: on pcib0 Jan 26 19:21:44 HP kernel: pcib1: at device 1.0 on pci0 Jan 26 19:21:44 HP kernel: pci1: on pcib1 Jan 26 19:21:44 HP kernel: vgapci0: port 0x4000-0x40ff mem 0xc0000000-0xc7ffffff,0xd0200000-0xd020ffff,0xd0300000-0xd03fffff irq 19 at device 5.0 on pci1 Jan 26 19:21:44 HP kernel: acpi_video0: on vgapci0 Jan 26 19:21:44 HP kernel: pcib2: at device 4.0 on pci0 Jan 26 19:21:44 HP kernel: pci16: on pcib2 Jan 26 19:21:44 HP kernel: bge0: mem 0xd0000000-0xd000ffff irq 16 at device 0.0 on pci16 Jan 26 19:21:44 HP kernel: miibus0: on bge0 Jan 26 19:21:44 HP kernel: brgphy0: PHY 1 on miibus0 Jan 26 19:21:44 HP kernel: brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jan 26 19:21:44 HP kernel: bge0: Ethernet address: 00:1f:29:89:38:f3 Jan 26 19:21:44 HP kernel: bge0: [ITHREAD] Jan 26 19:21:44 HP kernel: pcib3: at device 5.0 on pci0 Jan 26 19:21:44 HP kernel: pci32: on pcib3 Jan 26 19:21:44 HP kernel: pcib4: at device 6.0 on pci0 Jan 26 19:21:44 HP kernel: pci48: on pcib4 Jan 26 19:21:44 HP kernel: pci48: at device 0.0 (no driver attached) Jan 26 19:21:44 HP kernel: atapci0: port 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f mem 0xd0409000-0xd04093ff irq 16 at device 18.0 on pci0 Jan 26 19:21:44 HP kernel: atapci0: [ITHREAD] Jan 26 19:21:44 HP kernel: atapci0: AHCI Version 01.10 controller with 4 ports PM not supported Jan 26 19:21:44 HP kernel: ata2: on atapci0 Jan 26 19:21:44 HP kernel: ata2: [ITHREAD] Jan 26 19:21:44 HP kernel: ata3: on atapci0 Jan 26 19:21:44 HP kernel: ata3: port not implemented Jan 26 19:21:44 HP kernel: ata3: [ITHREAD] Jan 26 19:21:44 HP kernel: ata4: on atapci0 Jan 26 19:21:44 HP kernel: ata4: port not implemented Jan 26 19:21:44 HP kernel: ata4: [ITHREAD] Jan 26 19:21:44 HP kernel: ata5: on atapci0 Jan 26 19:21:44 HP kernel: ata5: port not implemented Jan 26 19:21:44 HP kernel: ata5: [ITHREAD] Jan 26 19:21:44 HP kernel: ohci0: mem 0xd0401000-0xd0401fff irq 23 at device 19.0 on pci0 Jan 26 19:21:44 HP kernel: ohci0: [GIANT-LOCKED] Jan 26 19:21:44 HP kernel: ohci0: [ITHREAD] Jan 26 19:21:44 HP kernel: usb0: OHCI version 1.0, legacy support Jan 26 19:21:44 HP kernel: usb0: on ohci0 Jan 26 19:21:44 HP kernel: usb0: USB revision 1.0 Jan 26 19:21:44 HP kernel: uhub0: on usb0 Jan 26 19:21:44 HP kernel: uhub0: 2 ports with 2 removable, self powered Jan 26 19:21:44 HP kernel: ohci1: mem 0xd0402000-0xd0402fff irq 17 at device 19.1 on pci0 Jan 26 19:21:44 HP kernel: ohci1: [GIANT-LOCKED] Jan 26 19:21:44 HP kernel: ohci1: [ITHREAD] Jan 26 19:21:44 HP kernel: usb1: OHCI version 1.0, legacy support Jan 26 19:21:44 HP kernel: usb1: on ohci1 Jan 26 19:21:44 HP kernel: usb1: USB revision 1.0 Jan 26 19:21:44 HP kernel: uhub1: on usb1 Jan 26 19:21:44 HP kernel: uhub1: 2 ports with 2 removable, self powered Jan 26 19:21:44 HP kernel: ohci2: mem 0xd0403000-0xd0403fff irq 17 at device 19.2 on pci0 Jan 26 19:21:44 HP kernel: ohci2: [GIANT-LOCKED] Jan 26 19:21:44 HP kernel: ohci2: [ITHREAD] Jan 26 19:21:44 HP kernel: usb2: OHCI version 1.0, legacy support Jan 26 19:21:44 HP kernel: usb2: on ohci2 Jan 26 19:21:44 HP kernel: usb2: USB revision 1.0 Jan 26 19:21:44 HP kernel: uhub2: on usb2 Jan 26 19:21:44 HP kernel: uhub2: 2 ports with 2 removable, self powered Jan 26 19:21:44 HP kernel: ohci3: mem 0xd0404000-0xd0404fff irq 17 at device 19.3 on pci0 Jan 26 19:21:44 HP kernel: ohci3: [GIANT-LOCKED] Jan 26 19:21:44 HP kernel: ohci3: [ITHREAD] Jan 26 19:21:44 HP kernel: usb3: OHCI version 1.0, legacy support Jan 26 19:21:44 HP kernel: usb3: on ohci3 Jan 26 19:21:44 HP kernel: usb3: USB revision 1.0 Jan 26 19:21:44 HP kernel: uhub3: on usb3 Jan 26 19:21:44 HP kernel: uhub3: 2 ports with 2 removable, self powered Jan 26 19:21:44 HP kernel: ohci4: mem 0xd0405000-0xd0405fff irq 17 at device 19.4 on pci0 Jan 26 19:21:44 HP kernel: ohci4: [GIANT-LOCKED] Jan 26 19:21:44 HP kernel: ohci4: [ITHREAD] Jan 26 19:21:44 HP kernel: usb4: OHCI version 1.0, legacy support Jan 26 19:21:44 HP kernel: usb4: on ohci4 Jan 26 19:21:44 HP kernel: usb4: USB revision 1.0 Jan 26 19:21:44 HP kernel: uhub4: on usb4 Jan 26 19:21:44 HP kernel: uhub4: 2 ports with 2 removable, self powered Jan 26 19:21:44 HP kernel: ehci0: mem 0xd0406000-0xd04060ff irq 23 at device 19.5 on pci0 Jan 26 19:21:44 HP kernel: ehci0: [GIANT-LOCKED] Jan 26 19:21:44 HP kernel: ehci0: [ITHREAD] Jan 26 19:21:44 HP kernel: usb5: EHCI version 1.0 Jan 26 19:21:44 HP kernel: usb5: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4 Jan 26 19:21:44 HP kernel: usb5: on ehci0 Jan 26 19:21:44 HP kernel: usb5: USB revision 2.0 Jan 26 19:21:44 HP kernel: uhub5: on usb5 Jan 26 19:21:44 HP kernel: uhub5: 10 ports with 10 removable, self powered Jan 26 19:21:44 HP kernel: pci0: at device 20.0 (no driver attached) Jan 26 19:21:44 HP kernel: atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x5040-0x504f irq 16 at device 20.1 on pci0 Jan 26 19:21:44 HP kernel: ata0: on atapci1 Jan 26 19:21:44 HP kernel: ata0: [ITHREAD] Jan 26 19:21:44 HP kernel: hdac0: irq 16 at device 20.2 on pci0 Jan 26 19:21:44 HP kernel: hdac0: HDA Driver Revision: 20090113_0125 Jan 26 19:21:44 HP kernel: hdac0: [ITHREAD] Jan 26 19:21:44 HP kernel: isab0: at device 20.3 on pci0 Jan 26 19:21:44 HP kernel: isa0: on isab0 Jan 26 19:21:44 HP kernel: pcib5: at device 20.4 on pci0 Jan 26 19:21:44 HP kernel: pci2: on pcib5 Jan 26 19:21:44 HP kernel: cbb0: mem 0xd0100000-0xd0100fff irq 20 at device 4.0 on pci2 Jan 26 19:21:44 HP kernel: cardbus0: on cbb0 Jan 26 19:21:44 HP kernel: pccard0: <16-bit PCCard bus> on cbb0 Jan 26 19:21:44 HP kernel: cbb0: [FILTER] Jan 26 19:21:44 HP kernel: battery0: on acpi0 Jan 26 19:21:44 HP kernel: battery1: on acpi0 Jan 26 19:21:44 HP kernel: acpi_acad0: on acpi0 Jan 26 19:21:44 HP kernel: acpi_button0: on acpi0 Jan 26 19:21:44 HP kernel: acpi_lid0: on acpi0 Jan 26 19:21:44 HP kernel: acpi_tz0: on acpi0 Jan 26 19:21:44 HP kernel: atrtc0: port 0x70-0x71,0x72-0x73 irq 8 on acpi0 Jan 26 19:21:44 HP kernel: atkbdc0: port 0x60,0x64 irq 1 on acpi0 Jan 26 19:21:44 HP kernel: atkbd0: irq 1 on atkbdc0 Jan 26 19:21:44 HP kernel: kbd0 at atkbd0 Jan 26 19:21:44 HP kernel: atkbd0: [GIANT-LOCKED] Jan 26 19:21:44 HP kernel: atkbd0: [ITHREAD] Jan 26 19:21:44 HP kernel: psm0: irq 12 on atkbdc0 Jan 26 19:21:44 HP kernel: psm0: [GIANT-LOCKED] Jan 26 19:21:44 HP kernel: psm0: [ITHREAD] Jan 26 19:21:44 HP kernel: psm0: model IntelliMouse, device ID 3 Jan 26 19:21:44 HP kernel: cpu0: on acpi0 Jan 26 19:21:44 HP kernel: acpi_throttle0: on cpu0 Jan 26 19:21:44 HP kernel: powernow0: on cpu0 Jan 26 19:21:44 HP kernel: cpu1: on acpi0 Jan 26 19:21:44 HP kernel: acpi_throttle1: on cpu1 Jan 26 19:21:44 HP kernel: acpi_throttle1: failed to attach P_CNT Jan 26 19:21:44 HP kernel: device_attach: acpi_throttle1 attach returned 6 Jan 26 19:21:44 HP kernel: powernow1: on cpu1 Jan 26 19:21:44 HP kernel: orm0: at iomem 0xd0000-0xd0fff on isa0 Jan 26 19:21:44 HP kernel: sc0: at flags 0x100 on isa0 Jan 26 19:21:44 HP kernel: sc0: VGA <16 virtual consoles, flags=0x300> Jan 26 19:21:44 HP kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Jan 26 19:21:44 HP kernel: ppc0: cannot reserve I/O port range Jan 26 19:21:44 HP kernel: ugen0: on uhub0 Jan 26 19:21:44 HP kernel: ums0: on uhub1 Jan 26 19:21:44 HP kernel: ums0: 3 buttons and Z dir. Jan 26 19:21:44 HP kernel: Timecounters tick every 1.000 msec Jan 26 19:21:44 HP kernel: cpufreq0: rejecting change, SMP not started yet Jan 26 19:21:44 HP kernel: acpi_tz0: failed to set new freq, disabling passive cooling Jan 26 19:21:44 HP kernel: acd0: DVDR at ata0-master PIO4 Jan 26 19:21:44 HP kernel: ad4: 152627MB at ata2-master SATA300 Jan 26 19:21:44 HP kernel: hdac0: HDA Codec #0: Analog Devices AD1981HD Jan 26 19:21:44 HP kernel: hdac0: HDA Codec #1: Lucent/Agere Systems (Unknown) Jan 26 19:21:44 HP kernel: pcm0: at cad 0 nid 1 on hdac0 Jan 26 19:21:44 HP kernel: SMP: AP CPU #1 Launched! Jan 26 19:21:44 HP kernel: GEOM: ad4s1: geometry does not match label (255h,63s != 16h,63s). Jan 26 19:21:44 HP kernel: Trying to mount root from ufs:/dev/ad4s1a Jan 26 19:21:44 HP kernel: WARNING: TMPFS is considered to be a highly experimental feature in FreeBSD. Jan 26 19:21:44 HP kernel: acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01 Jan 26 19:21:44 HP kernel: (probe0:ata0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Jan 26 19:21:44 HP kernel: (probe0:ata0:0:0:0): CAM Status: SCSI Status Error Jan 26 19:21:44 HP kernel: (probe0:ata0:0:0:0): SCSI Status: Check Condition Jan 26 19:21:44 HP kernel: (probe0:ata0:0:0:0): NOT READY csi:0,0,bb,0 asc:3a,0 Jan 26 19:21:44 HP kernel: (probe0:ata0:0:0:0): Medium not present Jan 26 19:21:44 HP kernel: (probe0:ata0:0:0:0): Unretryable error Jan 26 19:21:44 HP kernel: cd0 at ata0 bus 0 target 0 lun 0 Jan 26 19:21:44 HP kernel: cd0: Removable CD-ROM SCSI-0 device Jan 26 19:21:44 HP kernel: cd0: 16.000MB/s transfers Jan 26 19:21:44 HP kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present Jan 26 19:21:44 HP kernel: ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based forwarding disabled, default to deny, logging disabled Jan 26 19:21:44 HP named[930]: starting BIND 9.4.3-P1 -t /var/named -u bind Jan 26 19:21:45 HP named[930]: command channel listening on 127.0.0.1#953 Jan 26 19:21:45 HP named[930]: command channel listening on ::1#953 Jan 26 19:21:45 HP named[930]: the working directory is not writable Jan 26 19:21:45 HP named[930]: running Jan 26 19:21:47 HP kernel: WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() Jan 26 19:21:47 HP bthidd[1086]: syntax error in line 1 Jan 26 19:21:48 HP kernel: fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 Jan 26 19:21:48 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:21:48 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:21:49 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:21:49 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:21:49 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:21:50 HP last message repeated 5 times Jan 26 19:21:50 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:21:50 HP root: /etc/rc.d/sysctl: WARNING: sysctl dev.pcm.0.vchans does not exist. Jan 26 19:21:50 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:21:50 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:21:51 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:21:51 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:21:51 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:21:57 HP last message repeated 22 times Jan 26 19:21:57 HP kernel: drm0: on vgapci0 Jan 26 19:21:57 HP kernel: vgapci0: child drm0 requested pci_enable_busmaster Jan 26 19:21:57 HP kernel: info: [drm] Initialized radeon 1.29.0 20080613 Jan 26 19:21:57 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:21:58 HP last message repeated 4 times Jan 26 19:21:58 HP kernel: info: [drm] Setting GART location based on new memory map Jan 26 19:21:58 HP kernel: info: [drm] Loading RS690/RS740 Microcode Jan 26 19:21:58 HP kernel: info: [drm] Num pipes: 1 Jan 26 19:21:58 HP kernel: info: [drm] writeback test succeeded in 1 usecs Jan 26 19:21:58 HP kernel: drm0: [ITHREAD] Jan 26 19:21:58 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:22:12 HP last message repeated 55 times Jan 26 19:22:12 HP kernel: info: [drm] Num pipes: 1 Jan 26 19:22:12 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:22:14 HP last message repeated 9 times Jan 26 19:22:14 HP login: ROOT LOGIN (root) ON ttyv1 Jan 26 19:22:15 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:22:46 HP last message repeated 123 times Jan 26 19:24:10 HP last message repeated 335 times Jan 26 19:24:10 HP kernel: info: [drm] Loading RS690/RS740 Microcode Jan 26 19:24:10 HP kernel: info: [drm] Num pipes: 1 Jan 26 19:24:10 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:24:12 HP last message repeated 8 times Jan 26 19:24:12 HP kernel: info: [drm] Num pipes: 1 Jan 26 19:24:12 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:24:13 HP last message repeated 2 times Jan 26 19:24:13 HP kernel: info: [drm] Setting GART location based on new memory map Jan 26 19:24:13 HP kernel: info: [drm] Loading RS690/RS740 Microcode Jan 26 19:24:13 HP kernel: info: [drm] Num pipes: 1 Jan 26 19:24:13 HP kernel: info: [drm] writeback test succeeded in 1 usecs Jan 26 19:24:13 HP kernel: drm0: [ITHREAD] Jan 26 19:24:13 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:24:15 HP last message repeated 5 times Jan 26 19:24:15 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:24:15 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:24:15 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:24:15 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:24:16 HP last message repeated 4 times Jan 26 19:24:16 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:24:17 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:24:25 HP last message repeated 34 times Jan 26 19:24:25 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:24:25 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:24:30 HP last message repeated 18 times Jan 26 19:24:30 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:24:30 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:24:30 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:24:30 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:24:39 HP last message repeated 20 times Jan 26 19:24:39 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:24:40 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:24:40 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:24:40 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:24:41 HP last message repeated 5 times Jan 26 19:24:41 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:24:41 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:24:44 HP last message repeated 5 times Jan 26 19:24:44 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:24:45 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:24:45 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:24:45 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:24:46 HP last message repeated 6 times Jan 26 19:24:46 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:24:48 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:24:57 HP last message repeated 40 times Jan 26 19:24:57 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:24:57 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:24:58 HP last message repeated 2 times Jan 26 19:24:58 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:24:58 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:25:29 HP last message repeated 122 times Jan 26 19:26:53 HP last message repeated 336 times Jan 26 19:26:53 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:26:54 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:26:54 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:26:54 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:26:54 HP kernel: powernow1: set freq failed, err 6 Jan 26 19:26:54 HP kernel: powernow0: set freq failed, err 6 Jan 26 19:27:13 HP last message repeated 74 times From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 16:37:46 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64659106564A for ; Mon, 26 Jan 2009 16:37:46 +0000 (UTC) (envelope-from alexanderchuranov@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.187]) by mx1.freebsd.org (Postfix) with ESMTP id E52918FC1D for ; Mon, 26 Jan 2009 16:37:45 +0000 (UTC) (envelope-from alexanderchuranov@gmail.com) Received: by fk-out-0910.google.com with SMTP id f40so2872956fka.11 for ; Mon, 26 Jan 2009 08:37:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=bBAzvDr/D9w72rw5vCMOlllAlrRVht1Iwvz2t3qYuX0=; b=l+E/XgNzkzQ8g861hj4grJzO9MIG/320EpAlQ2Vh6oTBvUN9iTBZVyA9gShJfl62hv DrZc35ldfddewOQj8IowKOKd95LLZvAS6MLEyYh7dVSHYYzezkCGmp1xMf8mkQuf+MMC rUO2AEsSSH2gpe5uWtwbK0dqDmunn7mhKB/YQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Him2C/7ZdU3ArYOL3NYrU8qOytZxFdoqvMWn3ZCOegh4cqSsS5GaLP9PUHVWx1oX7H lP5WiFZwnVcPGyfC6t6EVqjFENgiw0ZJ0VU+yMxsVwL7wZMoH3lymjzBt0QOUprhh+ct gj6kmMl7XqGbLSIkZQ95R171zq3Rrdk3XulZQ= MIME-Version: 1.0 Received: by 10.181.4.1 with SMTP id g1mr1207544bki.100.1232987864968; Mon, 26 Jan 2009 08:37:44 -0800 (PST) In-Reply-To: <4978B0CC.4070803@boland.org> References: <49789DC7.1050300@boland.org> <49789EBC.1050401@andric.com> <4978B0CC.4070803@boland.org> Date: Mon, 26 Jan 2009 19:37:44 +0300 Message-ID: <3cb459ed0901260837j5f680c1bu1df81d6cc05c34a6@mail.gmail.com> From: Alexander Churanov To: Michiel Boland Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Dimitry Andric , freebsd-current@freebsd.org Subject: Re: panic on boot with today's kernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jan 2009 16:37:46 -0000 Hi folks! I've just updated from HEAD, found that http://docs.freebsd.org/cgi/mid.cgi?200901221016.58349.jhb is already applied to what's in repository. However, the issue remains. The sympthoms are exactly as described by Michiel, and backtrace is the same. 1) What is the estimate for this to be fixed? 2) Is it possible to disable something to get working kernel? I've just looked into the config file and read that ppbus is required. 3) Would checking out the previous stable version of ppbus work? I mean having most recent source code of the whole kernel except for old stable ppbus? Alexander Churanov From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 17:29:03 2009 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 7B14F106564A for ; Mon, 26 Jan 2009 17:29:03 +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 DFB838FC17 for ; Mon, 26 Jan 2009 17:29:02 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.local ([192.168.254.200]) (authenticated bits=0) by pooker.samsco.org (8.14.2/8.14.2) with ESMTP id n0QGqYSo029635; Mon, 26 Jan 2009 09:52:35 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <497DEA52.3040004@samsco.org> Date: Mon, 26 Jan 2009 09:52:34 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Sepherosa Ziehau References: <497758.90319.qm@web63903.mail.re1.yahoo.com> In-Reply-To: X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: barney_cordoba@yahoo.com, current@freebsd.org Subject: Re: DMA bounce buffers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jan 2009 17:29:04 -0000 Sepherosa Ziehau wrote: > On Mon, Jan 26, 2009 at 9:05 PM, Barney Cordoba > wrote: >> I have a problem with the ixgbe driver, where bus_dmamap_load_mbuf_sg() is >> failing. The underlying failure is reserve_bounce_pages(). It seems that >> there aren't any bounce pages allocated. What could be the cause of this? Is there some tunable? > > I don't think the hardware supported ixgbe(4) will need bounce pages > on RX/TX buffers (according to data sheet, the hardware supports full > 64bits address space accessing and no alignment constraints on RX/TX > buffer start address). However, the driver's buffer busdma is kinda > misconfigured: in ixgbe_allocate_{transmit,receive}_buffers(), the > buffers' alignment is set to PAGE_SIZE (?!), this means that almost > all TX/RX operation will require bouncing. The best case is poor > performance due to additional and unnecessary memory copy in > bus_dmamap_sync(); the worst case is completely unfunction NIC due to > RX ring could not be filled during ifnet.if_init(). > Yes, no high-speed NIC should be using bounce buffers. I haven't looked at the ixgbe data sheets, but I'd be highly surprised if this hardware actually needed buffer alignment like that. If it does, then the better thing to do is to either use 4k mbuf clusters (and make sure that the system doesn't try to treat them as jumbo frames), or have the rx ring allocator throw away and reallocate any clusters that aren't already on 4k boundaries (normal clusters are 2k, so it'll have a nominal 50% chance of getting what it needs). Neither of these solutions is ideal, though. Scott From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 18:03:27 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 62A8E10656E0 for ; Mon, 26 Jan 2009 18:03:27 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 187498FC25 for ; Mon, 26 Jan 2009 18:03:24 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: (qmail invoked by alias); 26 Jan 2009 18:03:21 -0000 Received: from p54A3E512.dip.t-dialin.net (EHLO tron.homeunix.org) [84.163.229.18] by mail.gmx.net (mp003) with SMTP; 26 Jan 2009 19:03:21 +0100 X-Authenticated: #1673122 X-Provags-ID: V01U2FsdGVkX18eqdtknKoeJWTuVnfLsp8vduZVVhR6bfNQfj4SNo RVpuu/yPq/Vvq7 Message-ID: <497DFAE2.5030301@gmx.de> Date: Mon, 26 Jan 2009 19:03:14 +0100 From: Christoph Mallon User-Agent: Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Alexander Churanov References: <49789DC7.1050300@boland.org> <49789EBC.1050401@andric.com> <4978B0CC.4070803@boland.org> <3cb459ed0901260837j5f680c1bu1df81d6cc05c34a6@mail.gmail.com> In-Reply-To: <3cb459ed0901260837j5f680c1bu1df81d6cc05c34a6@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.59 Cc: Michiel Boland , Dimitry Andric , freebsd-current@freebsd.org Subject: Re: panic on boot with today's kernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jan 2009 18:03:28 -0000 Alexander Churanov schrieb: > Hi folks! > > I've just updated from HEAD, found that > http://docs.freebsd.org/cgi/mid.cgi?200901221016.58349.jhb is already > applied to what's in repository. However, the issue remains. The sympthoms > are exactly as described by Michiel, and backtrace is the same. > > 1) What is the estimate for this to be fixed? > > 2) Is it possible to disable something to get working kernel? I've just > looked into the config file and read that ppbus is required. > > 3) Would checking out the previous stable version of ppbus work? I mean > having most recent source code of the whole kernel except for old stable > ppbus? There's not need to switch the branch to stable. If you use SVN, you can update just the affected paths to before the change: svn up -r 187575 sys/dev/ppbus sys/dev/ppc Christoph From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 18:15:12 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DAA0210656DF for ; Mon, 26 Jan 2009 18:15:12 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from hosting.lissyara.su (hosting.lissyara.su [77.221.149.162]) by mx1.freebsd.org (Postfix) with ESMTP id 92C788FC1A for ; Mon, 26 Jan 2009 18:15:12 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from [89.178.150.64] (port=48564 helo=HP.lissyara.su) by hosting.lissyara.su with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LRVzK-000A7a-VP for freebsd-current@freebsd.org; Mon, 26 Jan 2009 21:15:10 +0300 Message-ID: <497DFDAD.4060903@lissyara.su> Date: Mon, 26 Jan 2009 21:15:09 +0300 From: Alex Keda User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; ru-RU; rv:1.8.1.19) Gecko/20090126 Thunderbird/2.0.0.19 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <497DE6CF.9060509@lissyara.su> In-Reply-To: <497DE6CF.9060509@lissyara.su> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Description: if spam count > 60 - this is spam X-Spam-Count: 0 X-Descriptions: powered by www.lissyara.su X-Bounce-ID: hosting.lissyara.su Subject: Re: kernel: powernow0: set freq failed, err 6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jan 2009 18:15:14 -0000 Alex Keda пишет: > HP$ uname -a > FreeBSD HP.lissyara.su 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sat Jan 24 > 22:03:26 MSK 2009 lissyara@HP.lissyara.su:/usr/obj/usr/src/sys/HP > amd64 > HP$ After reboot, all OK... Strange behavior. As M$ =) From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 19:36:51 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F23851065672 for ; Mon, 26 Jan 2009 19:36:51 +0000 (UTC) (envelope-from michiel@boland.org) Received: from smtp-vbr1.xs4all.nl (smtp-vbr1.xs4all.nl [194.109.24.21]) by mx1.freebsd.org (Postfix) with ESMTP id 9089F8FC0A for ; Mon, 26 Jan 2009 19:36:51 +0000 (UTC) (envelope-from michiel@boland.org) Received: from aja.boland.org (91-43-215.ftth.xms.internl.net [82.215.43.91]) (authenticated bits=0) by smtp-vbr1.xs4all.nl (8.13.8/8.13.8) with ESMTP id n0QJaoq6041204 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 26 Jan 2009 20:36:50 +0100 (CET) (envelope-from michiel@boland.org) Message-ID: <497E10D1.50601@boland.org> Date: Mon, 26 Jan 2009 20:36:49 +0100 From: Michiel Boland User-Agent: Thunderbird 2.0.0.19 (X11/20090125) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <497D9CEF.7020807@boland.org> In-Reply-To: <497D9CEF.7020807@boland.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: panic in rtrequest1_fib X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jan 2009 19:36:52 -0000 Michiel Boland wrote: > -CURRENT from 25 jan > > panic: _rw_wlock_hard: recursing but non-recursive rw radix node head @ > /usr/src/sys/net/route.c:831 Looks like this happens when routes learned via ICMP redirects are expired. It's easy to reproduce. Guess I'll add some static routes for now but this is now it should work of course. :) > #0 doadump () at pcpu.h:246 > #1 0xc082f7be in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:420 > #2 0xc082fa92 in panic (fmt=Variable "fmt" is not available. > ) at /usr/src/sys/kern/kern_shutdown.c:576 > #3 0xc082d986 in _rw_wlock_hard (rw=0xc577e680, tid=3312676864, > file=0xc0bf0410 "/usr/src/sys/net/route.c", line=831) at > /usr/src/sys/kern/kern_rwlock.c:592 > #4 0xc082e23e in _rw_wlock (rw=0xc577e680, file=0xc0bf0410 > "/usr/src/sys/net/route.c", line=831) at > /usr/src/sys/kern/kern_rwlock.c:218 > #5 0xc08dea95 in rtrequest1_fib (req=2, info=0xe5b22b1c, ret_nrt=0x0, > fibnum=0) at /usr/src/sys/net/route.c:831 > #6 0xc08df62e in rtrequest_fib (req=2, dst=0xc99a91c0, > gateway=0xc99a91d0, netmask=0x0, flags=262167, ret_nrt=0x0, fibnum=0) at > /usr/src/sys/net/route.c:680 > #7 0xc091deeb in in_rtrequest (req=2, dst=0xc99a91c0, > gateway=0xc99a91d0, netmask=0x0, flags=262167, ret_nrt=0x0, fibnum=0) at > /usr/src/sys/netinet/in_rmx.c:459 > #8 0xc091e42f in in_rtqkill (rn=0xc6032068, rock=0xe5b22bdc) at > /usr/src/sys/netinet/in_rmx.c:213 From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 20:13:45 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B668B106566C for ; Mon, 26 Jan 2009 20:13:45 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.227]) by mx1.freebsd.org (Postfix) with ESMTP id 892268FC08 for ; Mon, 26 Jan 2009 20:13:45 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so6133809rvf.43 for ; Mon, 26 Jan 2009 12:13:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=31qfS0hqAwzRyYMcub9pXgNSm+MJeHpl/8GR6FrGsgM=; b=d8CJrzvQmEISBgtsdCKVYKFWgbaAmFcwiq/TSNNYxSOu0dYag2SoEfkfODiSUqhwHV qSn8ZiUeM97re5gYT8TarhdlG+96KpMtFwzZVEewvGP+qqclmx7pgirgY/vsQDb7lOnw Tb8AsCY381cUEX2MnnP3B6e10/9lOD5spC0QQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=maiTrtDeeo8LN6PqWENBYDam4gcBDPed04wH2WXbrsu6iCULFTXBNQAQZLenl15R6w hRnVI9K4pVP4685fRzDzpCf+yj+frE5RkUOBkhvU7Lbva7knxUJYAuWC7voE9tTUyio8 USDix/05/GVZRRUWZdR38jaNRvGixcdIsu3rM= MIME-Version: 1.0 Sender: mat.macy@gmail.com Received: by 10.141.96.19 with SMTP id y19mr2284790rvl.89.1233000825312; Mon, 26 Jan 2009 12:13:45 -0800 (PST) In-Reply-To: <497E10D1.50601@boland.org> References: <497D9CEF.7020807@boland.org> <497E10D1.50601@boland.org> Date: Mon, 26 Jan 2009 20:13:45 +0000 X-Google-Sender-Auth: df672b232be2f2d6 Message-ID: <3c1674c90901261213h6861363frca1b6b498dc14323@mail.gmail.com> From: Kip Macy To: Michiel Boland Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: panic in rtrequest1_fib X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jan 2009 20:13:46 -0000 mea culpa, will fix Thanks, Kip On Mon, Jan 26, 2009 at 7:36 PM, Michiel Boland wrote: > Michiel Boland wrote: >> >> -CURRENT from 25 jan >> >> panic: _rw_wlock_hard: recursing but non-recursive rw radix node head @ >> /usr/src/sys/net/route.c:831 > > Looks like this happens when routes learned via ICMP redirects are expired. > It's easy to reproduce. > Guess I'll add some static routes for now but this is now it should work of > course. :) > >> #0 doadump () at pcpu.h:246 >> #1 0xc082f7be in boot (howto=260) at >> /usr/src/sys/kern/kern_shutdown.c:420 >> #2 0xc082fa92 in panic (fmt=Variable "fmt" is not available. >> ) at /usr/src/sys/kern/kern_shutdown.c:576 >> #3 0xc082d986 in _rw_wlock_hard (rw=0xc577e680, tid=3312676864, >> file=0xc0bf0410 "/usr/src/sys/net/route.c", line=831) at >> /usr/src/sys/kern/kern_rwlock.c:592 >> #4 0xc082e23e in _rw_wlock (rw=0xc577e680, file=0xc0bf0410 >> "/usr/src/sys/net/route.c", line=831) at /usr/src/sys/kern/kern_rwlock.c:218 >> #5 0xc08dea95 in rtrequest1_fib (req=2, info=0xe5b22b1c, ret_nrt=0x0, >> fibnum=0) at /usr/src/sys/net/route.c:831 >> #6 0xc08df62e in rtrequest_fib (req=2, dst=0xc99a91c0, >> gateway=0xc99a91d0, netmask=0x0, flags=262167, ret_nrt=0x0, fibnum=0) at >> /usr/src/sys/net/route.c:680 >> #7 0xc091deeb in in_rtrequest (req=2, dst=0xc99a91c0, gateway=0xc99a91d0, >> netmask=0x0, flags=262167, ret_nrt=0x0, fibnum=0) at >> /usr/src/sys/netinet/in_rmx.c:459 >> #8 0xc091e42f in in_rtqkill (rn=0xc6032068, rock=0xe5b22bdc) at >> /usr/src/sys/netinet/in_rmx.c:213 > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 20:19:25 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67C1C106568A for ; Mon, 26 Jan 2009 20:19:25 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: from iron2.pdx.net (iron2.pdx.net [69.64.224.71]) by mx1.freebsd.org (Postfix) with ESMTP id 299538FC1F for ; Mon, 26 Jan 2009 20:19:24 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: (qmail 26109 invoked from network); 26 Jan 2009 11:52:44 -0800 Received: from 069-064-235-060.pdx.net (HELO ?192.168.1.51?) (69.64.235.60) by iron2.pdx.net with SMTP; 26 Jan 2009 11:52:44 -0800 From: Sean Bruno To: freebsd-current@freebsd.org Content-Type: multipart/mixed; boundary="=-sYAgDJh8g3fdgxHVZjXu" Date: Mon, 26 Jan 2009 11:52:44 -0800 Message-Id: <1232999564.12827.17.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 (2.24.3-1.fc10) X-Mailman-Approved-At: Mon, 26 Jan 2009 20:54:58 +0000 Subject: LPT Panic at assert lpt.c::222 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jan 2009 20:19:26 -0000 --=-sYAgDJh8g3fdgxHVZjXu Content-Type: text/plain Content-Transfer-Encoding: 7bit Just tested today's -current and was greeted with a panic in PPBUS at an assert. The following patch seems to be appropriate. Comments? Sean --=-sYAgDJh8g3fdgxHVZjXu Content-Disposition: attachment; filename="lpt.c.diff" Content-Type: text/x-patch; name="lpt.c.diff"; charset="UTF-8" Content-Transfer-Encoding: 7bit Index: lpt.c =================================================================== --- lpt.c (revision 187738) +++ lpt.c (working copy) @@ -380,8 +380,8 @@ } ppb_wctr(ppbus, LPC_NINIT); + lpt_release_ppbus(dev); ppb_unlock(ppbus); - lpt_release_ppbus(dev); /* declare our interrupt handler */ sc->sc_intr_resource = bus_alloc_resource_any(dev, SYS_RES_IRQ, &rid, --=-sYAgDJh8g3fdgxHVZjXu-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 20:55:33 2009 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 3AF0810656BB; Mon, 26 Jan 2009 20:55:33 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from deepcore.dk (adsl.deepcore.dk [87.63.29.106]) by mx1.freebsd.org (Postfix) with ESMTP id BAA058FC1E; Mon, 26 Jan 2009 20:55:32 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from [192.168.0.138] ([192.168.0.138]) by deepcore.dk (8.14.3/8.14.2) with ESMTP id n0QKMadk093274; Mon, 26 Jan 2009 21:22:36 +0100 (CET) (envelope-from sos@deepcore.dk) Message-Id: From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= To: current , hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v930.3) Date: Mon, 26 Jan 2009 21:22:36 +0100 X-Mailer: Apple Mail (2.930.3) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (deepcore.dk [87.63.29.106]); Mon, 26 Jan 2009 21:22:36 +0100 (CET) Cc: Subject: WANTED! board models with Marvell 61XX chips X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jan 2009 20:55:35 -0000 Hi there! I thought I finally had a motherboard using one of the Marvell SATA/=20 PATA chips coming in, but unfortunately the delivery has been =20 postponed to some unspecified date, oh well.. Thats where you come into the picture as I'd like to get another one, =20= but finding boards that uses these is a bit tricky as most vendors =20 doesn't write such unimportant stuff on their web pages (hell it works =20= in windows!). If you have a motherboard using one of the following Marvell chips, or =20= know for certain a model that does, please send me a private mail with =20= make and model as there is no need to pollute the lists (which I dont =20= follow closely for the time being btw). The chips in question are: Marvell 6111, 6121, 6141 or 6145 It is also important that there is physical access to both the SATA =20 and the PATA port(s) as some boards only utilize one or the other. I know of one PCI-express add-in board that uses the 6145, so if =20 anybody knows how to get ahold of one, that would be very welcomed as =20= well. The board in question is this: = http://www.sunix.com.tw/it/en/Product_Detail.php?cate=3D2&class_a_id=3D35&= sid=3D538 So far I've only found shops in South Africa that has it available, =20 but none of them ships outside the country. So if you have any useful info on this topic please get in touch with =20= me, thanks! -S=F8ren -- From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 21:08:16 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1201A1065689 for ; Mon, 26 Jan 2009 21:08:16 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: from iron2.pdx.net (iron2.pdx.net [69.64.224.71]) by mx1.freebsd.org (Postfix) with ESMTP id C5D8A8FC20 for ; Mon, 26 Jan 2009 21:08:15 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: (qmail 13923 invoked from network); 26 Jan 2009 13:08:14 -0800 Received: from 069-064-235-060.pdx.net (HELO ?192.168.1.51?) (69.64.235.60) by iron2.pdx.net with SMTP; 26 Jan 2009 13:08:14 -0800 From: Sean Bruno To: freebsd-current@freebsd.org Content-Type: multipart/mixed; boundary="=-IFJfGB3IAPIkpKXeckZG" Date: Mon, 26 Jan 2009 13:08:14 -0800 Message-Id: <1233004094.9302.0.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 (2.24.3-1.fc10) Subject: LPT Panic at assert lpt.c::222 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sbruno@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: Mon, 26 Jan 2009 21:08:17 -0000 --=-IFJfGB3IAPIkpKXeckZG Content-Type: text/plain Content-Transfer-Encoding: 7bit Just tested today's -current and was greeted with a panic in PPBUS at an assert. The following patch seems to be appropriate. Comments? Sean --=-IFJfGB3IAPIkpKXeckZG Content-Disposition: attachment; filename="lpt.c.diff" Content-Type: text/x-patch; name="lpt.c.diff"; charset="UTF-8" Content-Transfer-Encoding: 7bit Index: lpt.c =================================================================== --- lpt.c (revision 187738) +++ lpt.c (working copy) @@ -380,8 +380,8 @@ } ppb_wctr(ppbus, LPC_NINIT); + lpt_release_ppbus(dev); ppb_unlock(ppbus); - lpt_release_ppbus(dev); /* declare our interrupt handler */ sc->sc_intr_resource = bus_alloc_resource_any(dev, SYS_RES_IRQ, &rid, --=-IFJfGB3IAPIkpKXeckZG-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 22:01:04 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E99F106566C for ; Mon, 26 Jan 2009 22:01:04 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: from iron2.pdx.net (iron2.pdx.net [69.64.224.71]) by mx1.freebsd.org (Postfix) with ESMTP id 3EC658FC17 for ; Mon, 26 Jan 2009 22:01:04 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: (qmail 5886 invoked from network); 26 Jan 2009 14:01:03 -0800 Received: from 069-064-235-060.pdx.net (HELO ?192.168.1.51?) (69.64.235.60) by iron2.pdx.net with SMTP; 26 Jan 2009 14:01:03 -0800 From: Sean Bruno To: freebsd-current@freebsd.org Content-Type: text/plain Date: Mon, 26 Jan 2009 14:01:03 -0800 Message-Id: <1233007263.9302.2.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 (2.24.3-1.fc10) Content-Transfer-Encoding: 7bit Subject: UFS Witness LoR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sbruno@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: Mon, 26 Jan 2009 22:01:04 -0000 Anyone else seeing this LoR today? SMP: AP CPU #1 Launched! WARNING: WITNESS option enabled, expect reduced performance. GEOM: ad4s1: geometry does not match label (255h,63s != 16h,63s). GEOM: ad4s2: geometry does not match label (255h,63s != 16h,63s). GEOM: ad4s3: geometry does not match label (255h,63s != 16h,63s). Trying to mount root from ufs:/dev/ad4s3a lock order reversal: 1st 0xc456b044 user map (user map) @ /root/bsd/head/sys/vm/vm_map.c:3198 2nd 0xc4911ad0 ufs (ufs) @ /root/bsd/head/sys/kern/vfs_subr.c:2071 KDB: stack backtrace: db_trace_self_wrapper(c0bf0913,c417990c,c087a4b5,c0c1458c,0,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0c1458c,0,c4521728,c4526730,c4179968,...) at kdb_backtrace+0x29 _witness_debugger(c0bf3680,c4911ad0,c0be6d88,c4526730,c0bfa429,...) at _witness_debugger+0x25 witness_checkorder(c4911ad0,1,c0bfa429,817,0,...) at witness_checkorder +0x839 __lockmgr_args(c4911ad0,200501,c4911aec,0,0,...) at __lockmgr_args+0x237 ffs_lock(c4179a78,c087a25b,c0c1697a,200501,c4911a78,...) at ffs_lock +0x8a VOP_LOCK1_APV(c0cf7ca0,c4179a78,c4567e24,c0d0bdc0,c4911a78,...) at VOP_LOCK1_APV+0xb5 _vn_lock(c4911a78,200501,c0bfa429,817,4,...) at _vn_lock+0x5e vget(c4911a78,200501,c4567d80,4b4,0,...) at vget+0xc9 vnode_pager_lock(c187c1f0,0,c0c13f07,127,c4179c18,...) at vnode_pager_lock+0x1e0 vm_fault(c456b000,80db000,2,8,80db620,...) at vm_fault+0x1df trap_pfault(5,0,c0c241d1,2e7,c4565d34,...) at trap_pfault+0x118 trap(c4179d38) at trap+0x289 calltrap() at calltrap+0x6 --- trap 0xc, eip = 0x80480e5, esp = 0xbfbfeef0, ebp = 0xbfbfef10 --- Entropy harvesting: interrupts ethernet point_to_point kickstart. /dev/ad4s3a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad4s3a: clean, 105661 free (3093 frags, 12821 blocks, 1.2% fragmentation) /dev/ad4s3e: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad4s3e: clean, 253809 free (33 frags, 31722 blocks, 0.0% fragmentation) /dev/ad4s3f: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad4s3f: clean, 40575347 free (17139 frags, 5069776 blocks, 0.0% fragmentation) /dev/ad4s3d: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad4s3d: clean, 957308 free (212 frags, 119637 blocks, 0.0% fragmentation) Starting Network: lo0 em0. add net default: gateway 192.168.1.1 em0: link state changed to UP Configuring syscons: blanktime. Jan 26 15:59:33 home-test sm-mta[1121]: My unqualified host name (home-test) unknown; sleeping for retry Jan 26 16:00:33 home-test sm-mta[1121]: unable to qualify my own domain name (home-test) -- using short name Jan 26 16:00:33 home-test sm-msp-queue[1125]: My unqualified host name (home-test) unknown; sleeping for retry Jan 26 16:01:33 home-test sm-msp-queue[1125]: unable to qualify my own domain name (home-test) -- using short name Mon Jan 26 16:01:34 PST 2009 FreeBSD/i386 (home-test) (ttyu0) login: Sean From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 03:41:06 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 524721065673 for ; Tue, 27 Jan 2009 03:41:06 +0000 (UTC) (envelope-from terry@tmk.com) Received: from server.tmk.com (server.tmk.com [204.141.35.63]) by mx1.freebsd.org (Postfix) with ESMTP id 2A5898FC19 for ; Tue, 27 Jan 2009 03:41:06 +0000 (UTC) (envelope-from terry@tmk.com) Received: from tmk.com by tmk.com (PMDF V6.3-x13 #37010) id <01N4RMHR8MWG00FK2Q@tmk.com> for freebsd-current@freebsd.org; Mon, 26 Jan 2009 22:41:04 -0500 (EST) Date: Mon, 26 Jan 2009 22:27:15 -0500 (EST) From: Terry Kennedy In-reply-to: "Your message dated Sun, 25 Jan 2009 14:57:49 +1100" <6FE15EE8-19C2-4AEE-8F3D-D7A453A5D201@ish.com.au> Sender: Terry Kennedy To: freebsd-current@freebsd.org Message-id: <01N4RNVS3TDW00FK2Q@tmk.com> MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=us-ascii; format=flowed; delsp=yes References: <01N4NEOEB7LY00EQWX@tmk.com> Cc: Aristedes Maniatis Subject: Re: Help me select hardware and software options for very large 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: Tue, 27 Jan 2009 03:41:06 -0000 > > I think this system may have the most storage ever configured on a > > FreeBSD system, and it is probably up near the top in terms of CPU and > > memory. > > I doubt it. 8 core systems are very common these days. I've seen > benchmarking with anything up to 64 cores (which I believe is the > current FreeBSD limit). As for memory, there was a recent thread with > someone installing 64Gb also claiming theirs was the biggest, but > others insisting that it certainly wasn't. As for storage, I know Sun > sell systems into the petabyte range which I assume these days are > powered by ZFS. > > The above is not to belittle your project; more to reassure you that > you aren't anywhere near the limits and you should have no troubles if > you tune things properly. Regarding storage, while there are other ZFS deployments (particularly on Sun equipment) which are a lot larger, I haven't seen any discussion of pools of this size on FreeBSD. And I have been keeping an eye on the FreeBSD ZFS discussions. That isn't to say that nobody has one, but if they do, they're keeping pretty quiet about it... Part of the reason for rolling my own is the fun I get from it - other- wise I could just buy a pre-configured Sun / NetApp / whatever box. It is good to know that my CPU / memory choices aren't pushing any limits in FreeBSD. I still think they're probably in the 95th percentile, size-wise. I've always been a bit careful about sizing at the top end - back when I was using BSD/OS, I'd run into problems with configurations with more than a certain amount of memory failing in subtle (and not-so-subtle) ways. I'm sure that people have experimented enough to find the upper limits, at least for quick testing. This is particularly common among hardware vendors and integrators, since they have all those parts sitting around waiting - years ago, I did such a test on a DEC system that shipped with 16MB memory standard and 64MB max. I loaded it up with 768MB to see what would happen (it worked). I'm also the guy that once set up a demo Cisco 2511 with full BGP tables (now *that* was a hack 8-). Terry Kennedy http://www.tmk.com terry@tmk.com New York, NY USA From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 09:42:58 2009 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 B9E9D1065673; Tue, 27 Jan 2009 09:42:58 +0000 (UTC) (envelope-from mike@reifenberger.com) Received: from mail-out.m-online.net (mail-out.m-online.net [212.18.0.10]) by mx1.freebsd.org (Postfix) with ESMTP id 3FC268FC14; Tue, 27 Jan 2009 09:42:57 +0000 (UTC) (envelope-from mike@reifenberger.com) Received: from mail01.m-online.net (mail.m-online.net [192.168.3.149]) by mail-out.m-online.net (Postfix) with ESMTP id 572731C01F85; Tue, 27 Jan 2009 10:25:28 +0100 (CET) Received: from localhost (dynscan2.mnet-online.de [192.168.1.215]) by mail.m-online.net (Postfix) with ESMTP id 3E0599015C; Tue, 27 Jan 2009 10:25:28 +0100 (CET) X-Virus-Scanned: amavisd-new at mnet-online.de Received: from mail.mnet-online.de ([192.168.3.149]) by localhost (dynscan2.mnet-online.de [192.168.1.215]) (amavisd-new, port 10024) with ESMTP id Q-9SykinmLAu; Tue, 27 Jan 2009 10:25:27 +0100 (CET) Received: from mail.reifenberger.com (ppp-93-104-61-113.dynamic.mnet-online.de [93.104.61.113]) by mail.mnet-online.de (Postfix) with ESMTP; Tue, 27 Jan 2009 10:25:26 +0100 (CET) Received: by mail.reifenberger.com (Postfix, from userid 1001) id 5A5222AA34; Tue, 27 Jan 2009 10:25:26 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mail.reifenberger.com (Postfix) with ESMTP id 51FF72AA33; Tue, 27 Jan 2009 10:25:26 +0100 (CET) Date: Tue, 27 Jan 2009 10:25:26 +0100 (CET) From: Michael Reifenberger To: =?ISO-8859-15?Q?S=F8ren_Schmidt?= In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="29518260-508733382-1233048326=:29922" Cc: hackers@freebsd.org, current Subject: Re: WANTED! board models with Marvell 61XX chips X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jan 2009 09:42:59 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --29518260-508733382-1233048326=:29922 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8BIT On Mon, 26 Jan 2009, Søren Schmidt wrote: > Date: Mon, 26 Jan 2009 21:22:36 +0100 > From: Søren Schmidt > To: current , hackers@freebsd.org > Subject: WANTED! board models with Marvell 61XX chips > > Hi there! > > I thought I finally had a motherboard using one of the Marvell SATA/PATA > chips coming in, but unfortunately the delivery has been postponed to some > unspecified date, oh well.. > > Thats where you come into the picture as I'd like to get another one, but > finding boards that uses these is a bit tricky as most vendors doesn't write > such unimportant stuff on their web pages (hell it works in windows!). > > If you have a motherboard using one of the following Marvell chips, or know > for certain a model that does, please send me a private mail with make and > model as there is no need to pollute the lists (which I dont follow closely > for the time being btw). > > The chips in question are: > > Marvell 6111, 6121, 6141 or 6145 > I have an ASUS M2N32 WS Professional which has an 6141 onboard. Both SATA and PATA are accessable. Bye/2 --- Michael Reifenberger Michael@Reifenberger.com http://www.Reifenberger.com --29518260-508733382-1233048326=:29922-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 10:59:12 2009 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 44882106567C; Tue, 27 Jan 2009 10:59:12 +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 E4E238FC1F; Tue, 27 Jan 2009 10:59:11 +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.3/8.14.3) with ESMTP id n0RAx99s087723; Tue, 27 Jan 2009 05:59:09 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0RAx9o9086475; Tue, 27 Jan 2009 05:59:09 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 43A0F7302F; Tue, 27 Jan 2009 05:59:09 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090127105909.43A0F7302F@freebsd-current.sentex.ca> Date: Tue, 27 Jan 2009 05:59:09 -0500 (EST) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2009 10:59:13 -0000 TB --- 2009-01-27 09:33:47 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-01-27 09:33:47 - starting HEAD tinderbox run for ia64/ia64 TB --- 2009-01-27 09:33:47 - cleaning the object tree TB --- 2009-01-27 09:34:27 - cvsupping the source tree TB --- 2009-01-27 09:34:27 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/ia64/ia64/supfile TB --- 2009-01-27 09:34:36 - building world TB --- 2009-01-27 09:34:36 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-27 09:34:36 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-27 09:34:36 - TARGET=ia64 TB --- 2009-01-27 09:34:36 - TARGET_ARCH=ia64 TB --- 2009-01-27 09:34:36 - TZ=UTC TB --- 2009-01-27 09:34:36 - __MAKE_CONF=/dev/null TB --- 2009-01-27 09:34:36 - cd /src TB --- 2009-01-27 09:34:36 - /usr/bin/make -B buildworld >>> World build started on Tue Jan 27 09:34:38 UTC 2009 >>> 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 [...] /src/sbin/ipfw/ipfw2.c:2607: warning: format '%llu' expects type 'long long unsigned int', but argument 4 has type 'uint64_t' /src/sbin/ipfw/ipfw2.c:2607: warning: format '%llu' expects type 'long long unsigned int', but argument 4 has type 'uint64_t' /src/sbin/ipfw/ipfw2.c:2613: warning: format '%llu' expects type 'long long unsigned int', but argument 4 has type 'uint64_t' /src/sbin/ipfw/ipfw2.c:2613: warning: format '%llu' expects type 'long long unsigned int', but argument 4 has type 'uint64_t' /src/sbin/ipfw/ipfw2.c:2628: warning: format '%llu' expects type 'long long unsigned int', but argument 4 has type 'uint64_t' /src/sbin/ipfw/ipfw2.c:2628: warning: format '%llu' expects type 'long long unsigned int', but argument 4 has type 'uint64_t' /src/sbin/ipfw/ipfw2.c:2633: warning: format '%llu' expects type 'long long unsigned int', but argument 4 has type 'uint64_t' /src/sbin/ipfw/ipfw2.c:2633: warning: format '%llu' expects type 'long long unsigned int', but argument 4 has type 'uint64_t' *** Error code 1 Stop in /src/sbin/ipfw. *** Error code 1 Stop in /src/sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-27 10:59:09 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-27 10:59:09 - ERROR: failed to build world TB --- 2009-01-27 10:59:09 - 4228.95 user 324.59 system 5121.21 real http://tinderbox.des.no/tinderbox-head-HEAD-ia64-ia64.full From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 12:10:01 2009 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 3CED01065672; Tue, 27 Jan 2009 12:10:01 +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 EC2408FC1F; Tue, 27 Jan 2009 12:10:00 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0RC9wMw062071; Tue, 27 Jan 2009 07:09:58 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.14.3/8.14.3) with ESMTP id n0RC9vkq039310; Tue, 27 Jan 2009 07:09:57 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id BEA877302F; Tue, 27 Jan 2009 07:09:57 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090127120957.BEA877302F@freebsd-current.sentex.ca> Date: Tue, 27 Jan 2009 07:09:57 -0500 (EST) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 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: Tue, 27 Jan 2009 12:10:01 -0000 TB --- 2009-01-27 11:03:39 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-01-27 11:03:39 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2009-01-27 11:03:39 - cleaning the object tree TB --- 2009-01-27 11:04:02 - cvsupping the source tree TB --- 2009-01-27 11:04:02 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2009-01-27 11:04:09 - building world TB --- 2009-01-27 11:04:09 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-27 11:04:09 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-27 11:04:09 - TARGET=sparc64 TB --- 2009-01-27 11:04:09 - TARGET_ARCH=sparc64 TB --- 2009-01-27 11:04:09 - TZ=UTC TB --- 2009-01-27 11:04:09 - __MAKE_CONF=/dev/null TB --- 2009-01-27 11:04:09 - cd /src TB --- 2009-01-27 11:04:09 - /usr/bin/make -B buildworld >>> World build started on Tue Jan 27 11:04:11 UTC 2009 >>> 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 [...] /src/sbin/ipfw/ipfw2.c:2552: warning: format '%llu' expects type 'long long unsigned int', but argument 4 has type 'uint64_t' /src/sbin/ipfw/ipfw2.c:2552: warning: format '%llu' expects type 'long long unsigned int', but argument 4 has type 'uint64_t' /src/sbin/ipfw/ipfw2.c:2558: warning: format '%llu' expects type 'long long unsigned int', but argument 4 has type 'uint64_t' /src/sbin/ipfw/ipfw2.c:2558: warning: format '%llu' expects type 'long long unsigned int', but argument 4 has type 'uint64_t' /src/sbin/ipfw/ipfw2.c:2573: warning: format '%llu' expects type 'long long unsigned int', but argument 4 has type 'uint64_t' /src/sbin/ipfw/ipfw2.c:2573: warning: format '%llu' expects type 'long long unsigned int', but argument 4 has type 'uint64_t' /src/sbin/ipfw/ipfw2.c:2578: warning: format '%llu' expects type 'long long unsigned int', but argument 4 has type 'uint64_t' /src/sbin/ipfw/ipfw2.c:2578: warning: format '%llu' expects type 'long long unsigned int', but argument 4 has type 'uint64_t' *** Error code 1 Stop in /src/sbin/ipfw. *** Error code 1 Stop in /src/sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-27 12:09:57 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-27 12:09:57 - ERROR: failed to build world TB --- 2009-01-27 12:09:57 - 3176.56 user 313.49 system 3978.05 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 12:35:01 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6F211065674 for ; Tue, 27 Jan 2009 12:35:01 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw2.york.ac.uk (mail-gw2.york.ac.uk [144.32.128.247]) by mx1.freebsd.org (Postfix) with ESMTP id 4BD808FC17 for ; Tue, 27 Jan 2009 12:35:00 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw6.york.ac.uk (mail-gw6.york.ac.uk [144.32.129.26]) by mail-gw2.york.ac.uk (8.13.6/8.13.6) with ESMTP id n0RCYPJR026787; Tue, 27 Jan 2009 12:34:25 GMT Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk) by mail-gw6.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1LRn97-0002Ql-24; Tue, 27 Jan 2009 12:34:25 +0000 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.2/8.14.2) with ESMTP id n0RCYOdQ026500; Tue, 27 Jan 2009 12:34:24 GMT (envelope-from gavin@FreeBSD.org) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.2/8.14.2/Submit) id n0RCYOPP026466; Tue, 27 Jan 2009 12:34:24 GMT (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson To: Paul Tice In-Reply-To: References: <1232712477.89022.7.camel@buffy.york.ac.uk> <1232713174.89022.8.camel@buffy.york.ac.uk> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 27 Jan 2009 12:34:23 +0000 Message-Id: <1233059663.71657.6.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin@freebsd.org Cc: freebsd-current@FreeBSD.org Subject: RE: UFS/VFS lock order reversal on stock 8.0-200812-AMD64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2009 12:35:05 -0000 On Fri, 2009-01-23 at 12:28 -0600, Paul Tice wrote: > -----Original Message----- > From: Gavin Atkinson [mailto:gavin@FreeBSD.org] > Sent: Fri 1/23/2009 6:19 AM > To: Paul Tice > Cc: freebsd-current@FreeBSD.org > Subject: Re: UFS/VFS lock order reversal on stock 8.0-200812-AMD64 > > On Fri, 2009-01-23 at 12:07 +0000, Gavin Atkinson wrote: > > On Thu, 2009-01-22 at 21:33 -0600, Paul Tice wrote: > > > I'm new, so please advise me (gently?) about list protocol and such if needed. > > > > > > Using stock 8.0-CURRENT-200812-amd64, I am getting the messages below. > > > > 8.0-CURRENT is essentially the bleeding-edge of FreeBSD, and is where > > development happens that has not necessarily proven itself as being > > stable. As it is the development branch, it also has a lot of extra > > debugging enabled, which is what you are seeing with the "lock order > > reversals". > > > > If you are not running 8-CURRENT for a specific reason (e.g. because you > > are doing FreeBSD OS development work, or you are prepared to help debug > > issues as you encounter them, or similar), you probably shouldn't be > > running CURRENT. Stick with 7.1. > > >I should have also included (in answer to your actual question): > >Neither the lock order reversals or the corrupted messages on shutdown > >are anything you need worry about. > > >Gavin > > > I wouldn't have asked if I wasn't willing to help debug (as possible, and with very little coding knowledge.) Cool. It's always good to have more people using and testing -CURRENT, I just wanted to make sure you knew what you were getting yourself in for :) > I pulled out the 'extra debugging', made world and kernel, and rebooted. > Notice the 5th line of da7's drive ID being interleaved with 'SMP: AP CPU #1 Launched!' > > I'm fairly sure this is not a good thing, if for no other reason that 'apparent garbage' in dmesg is not useful. It's not a good thing, but it's a known issue and is purely cosmetic. Gavin From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 12:45:45 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E78331065670 for ; Tue, 27 Jan 2009 12:45:45 +0000 (UTC) (envelope-from marius@nuenneri.ch) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.29]) by mx1.freebsd.org (Postfix) with ESMTP id AF3318FC16 for ; Tue, 27 Jan 2009 12:45:45 +0000 (UTC) (envelope-from marius@nuenneri.ch) Received: by yx-out-2324.google.com with SMTP id 8so2522387yxb.13 for ; Tue, 27 Jan 2009 04:45:45 -0800 (PST) MIME-Version: 1.0 Received: by 10.90.86.9 with SMTP id j9mr3317841agb.61.1233060344981; Tue, 27 Jan 2009 04:45:44 -0800 (PST) Date: Tue, 27 Jan 2009 13:45:44 +0100 Message-ID: From: =?ISO-8859-1?Q?Marius_N=FCnnerich?= To: "freebsd-current@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Nvidia's feature requests X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jan 2009 12:45:46 -0000 Hi all, I just updated the wiki page at http://wiki.freebsd.org/NvidiaFeatureRequests as you can see there are 2 points left which have a status of "not started" and have no owner. Is someone willing to take one? With Intel graphics already working on amd64 and amd/ati working on an opensource driver there is just nvidia missing for 3D experience for our amd64 userbase. Over the years I did many FreeBSD booths on OpenSource conferences and I can assure you that this feature is asked about alot. Kind regards Marius From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 12:46:06 2009 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 E814210656BF for ; Tue, 27 Jan 2009 12:46:06 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id 76EDC8FC24 for ; Tue, 27 Jan 2009 12:46:06 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.14.3/jtpda-5.4) with ESMTP id n0RCjw1h039748 ; Tue, 27 Jan 2009 13:45:59 +0100 (CET) X-Ids: 168 Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.14.3/8.14.3) with ESMTP id n0RCjvvj024581; Tue, 27 Jan 2009 13:45:57 +0100 (CET) (envelope-from arno@heho.snv.jussieu.fr) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.14.3/8.14.3/Submit) id n0RCjuP0024578; Tue, 27 Jan 2009 13:45:56 +0100 (CET) (envelope-from arno) To: Dmitry Marakasov From: "Arno J. Klaassen" References: <20090123221826.GB30982@deprived.panopticon> <20090126144044.GB6054@hades.panopticon> Date: Tue, 27 Jan 2009 13:45:56 +0100 In-Reply-To: <20090126144044.GB6054@hades.panopticon> (Dmitry Marakasov's message of "Mon\, 26 Jan 2009 14\:40\:44 +0000") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (shiva.jussieu.fr [134.157.0.168]); Tue, 27 Jan 2009 13:45:59 +0100 (CET) X-Virus-Scanned: ClamAV 0.94.2/8908/Tue Jan 27 09:23:41 2009 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at jchkmail.jussieu.fr with ID 497F0206.00C by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 497F0206.00C/134.157.184.22/heho.snv.jussieu.fr/heho.snv.jussieu.fr/ X-j-chkmail-Score: MSGID : 497F0206.00C on jchkmail.jussieu.fr : j-chkmail score : . : R=. U=. O=. B=0.011 -> S=0.011 X-j-chkmail-Status: Ham Cc: current@freebsd.org Subject: Re: Data corruption with checksum offloading enabled X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2009 12:46:07 -0000 Hello, Dmitry Marakasov writes: > For now I have two cases of corruption - in both cases it is single > difference of one 128 byte block with file offsets 0x65F872 and > 0x61A072. I had a similar problem last April on a 7-stable box reported in a 'nfs-server silent data corruption' thread. I found : - in all failing cases just *one* byte is currupted, 4 or all 8 bits set to zero *and* the original value is one out of the limited subset {1, 8, 9} .... here is the output of `cmp -x $i/BIG $i/BIG2` for some failing cases I saved : 03869a48 09 00 05209d88 09 00 01777148 09 00 00f10f88 09 00 01f4c4c8 11 00 06c3d6c8 11 00 0725ca48 18 00 01608008 09 00 00f3b888 18 00 07aa45c8 29 20 Does your corruption fulfill these characterisations as well? > I was suggested by Andrzej Tobola to try disabling txcsum on a > network interface. I've disabled both rxcsum and txcsum, and that > solved a problem. > > Judging from that this helped Andrzej with sk(4) and me with ale(4) > driver, that's not a single driver problem. Does his mean that we > have global problems with checksum offloading? I could reproduce it with nfe(4) and re(4) ... interestingly enough, I could *not* reproduce it when disabling cpu frequency control ... for what it's worth Best, Arno From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 12:53:00 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98537106564A for ; Tue, 27 Jan 2009 12:53:00 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (77-93-215-190.static.masterinter.net [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id 3A0B38FC14 for ; Tue, 27 Jan 2009 12:52:59 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 17DDE9CB075; Tue, 27 Jan 2009 13:50:32 +0100 (CET) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (lev.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b+0lhB4NFk+r; Tue, 27 Jan 2009 13:50:25 +0100 (CET) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 8AE069CB13B; Tue, 27 Jan 2009 13:50:25 +0100 (CET) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id n0RCoPZF097382; Tue, 27 Jan 2009 13:50:25 +0100 (CET) (envelope-from rdivacky) Date: Tue, 27 Jan 2009 13:50:25 +0100 From: Roman Divacky To: Marius N?nnerich Message-ID: <20090127125025.GA97280@freebsd.org> References: 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" Subject: Re: Nvidia's feature requests X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jan 2009 12:53:00 -0000 On Tue, Jan 27, 2009 at 01:45:44PM +0100, Marius N?nnerich wrote: > Hi all, > > I just updated the wiki page at > http://wiki.freebsd.org/NvidiaFeatureRequests > as you can see there are 2 points left which have a status of "not > started" and have no owner. > Is someone willing to take one? there is some work being done by pcbsd guys: https://trac.pcbsd.org/browser/freebsd-projects/nvidia-work?rev=2390 maybe you can check how things are going there and inform all parties about this and update the wiki? From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 12:57:27 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63B14106566C for ; Tue, 27 Jan 2009 12:57:27 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id 295EC8FC18 for ; Tue, 27 Jan 2009 12:57:26 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from [192.168.2.65] (c-71-56-39-94.hsd1.ga.comcast.net [71.56.39.94]) (authenticated bits=0) by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id n0RCugZ0045074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 Jan 2009 07:56:42 -0500 (EST) (envelope-from rnoland@FreeBSD.org) From: Robert Noland To: Marius =?ISO-8859-1?Q?N=FCnnerich?= In-Reply-To: References: Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-tOEQEUstZugoi2FEP9eg" Organization: FreeBSD Date: Tue, 27 Jan 2009 07:57:18 -0500 Message-Id: <1233061038.1751.57.camel@wombat.2hip.net> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 FreeBSD GNOME Team Port X-Spam-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RCVD_IN_SORBS_DUL,RDNS_DYNAMIC autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gizmo.2hip.net Cc: "freebsd-current@freebsd.org" Subject: Re: Nvidia's feature requests X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jan 2009 12:57:27 -0000 --=-tOEQEUstZugoi2FEP9eg Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable On Tue, 2009-01-27 at 13:45 +0100, Marius N=FCnnerich wrote: > Hi all, >=20 > I just updated the wiki page at > http://wiki.freebsd.org/NvidiaFeatureRequests > as you can see there are 2 points left which have a status of "not > started" and have no owner. > Is someone willing to take one? >=20 > With Intel graphics already working on amd64 and amd/ati working on an > opensource driver=20 amd/ati works now on r500 and below. robert. > there is just nvidia missing for 3D experience for > our amd64 userbase. Over the years I did many FreeBSD booths on > OpenSource conferences and I can assure you that this feature is asked > about alot. >=20 > Kind regards > Marius > _______________________________________________ > 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= " --=-tOEQEUstZugoi2FEP9eg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEABECAAYFAkl/BK4ACgkQM4TrQ4qfROPTrgCfSRvAr0Y9KXU8R5kNo4lH+rII lLgAnRbp33kXnUA4Y7I82LT8lI7FhvPQ =oIYj -----END PGP SIGNATURE----- --=-tOEQEUstZugoi2FEP9eg-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 13:15:31 2009 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 DC5CC106567F for ; Tue, 27 Jan 2009 13:15:31 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id A43028FC21 for ; Tue, 27 Jan 2009 13:15:31 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 1D73573098; Tue, 27 Jan 2009 14:21:02 +0100 (CET) Date: Tue, 27 Jan 2009 14:21:02 +0100 From: Luigi Rizzo To: current@freebsd.org Message-ID: <20090127132102.GA21574@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: duplicate typedefs and system headers ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jan 2009 13:15:32 -0000 In a recent commit tp sbin/ipfw, in an attempt to avoid a large set of header deependencies, i put a 'forward typedef' declaration in a common header, duplicating something that is in a system header: ipfw2.h: typedef struct _ipfw_insn ipfw_insn; netiinet/ip_fw2.h typedef struct _ipfw_insn { /* template for instructions */ ... } ipfw_insn; Sources including both ipfw2.h and /usr/include/netinet/ip_fw2.h However if the duplication occurs in two non-system files, the compiler produces an error for a duplicate typedef. Now i wonder, is there any compiler option to turn off the check for duplicate typedefs also for non-system headers ? BTW the behaviour with duplicate typedefs is curious, you can try this for yourself with a simple example involving e.g. /usr/include/sha.h : make a copy of the file in userspace, and then you can try the following (SHA_CTX is typedef'ed in sha.h --- ok --- typedef struct SHAstate_st SHA_CTX; #include --- ok --- #include typedef struct SHAstate_st SHA_CTX; --- error --- #include "sha.h" typedef struct SHAstate_st SHA_CTX; --- error --- typedef struct SHAstate_st SHA_CTX; #include "sha.h" --- ok (this is surprising to me) -- typedef struct SHAstate_st SHA_CTX; #include typedef struct SHAstate_st SHA_CTX; As you note, it looks like a typedef in a system header removes the error message for duplicates both before and after. cheers luigi From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 13:45:21 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71D93106566C for ; Tue, 27 Jan 2009 13:45:21 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from smtp.timeweb.ru (smtp.timeweb.ru [217.170.79.85]) by mx1.freebsd.org (Postfix) with ESMTP id 2A83A8FC21 for ; Tue, 27 Jan 2009 13:45:21 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1LRoFl-0008EO-VB; Tue, 27 Jan 2009 16:45:22 +0300 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 0FF24A78F; Tue, 27 Jan 2009 16:45:36 +0300 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id 511FD108838; Tue, 27 Jan 2009 16:46:17 +0000 (UTC) Date: Tue, 27 Jan 2009 16:46:17 +0000 From: Dmitry Marakasov To: "Arno J. Klaassen" Message-ID: <20090127164617.GA93440@hades.panopticon> References: <20090123221826.GB30982@deprived.panopticon> <20090126144044.GB6054@hades.panopticon> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-current@freebsd.org Subject: Re: Data corruption with checksum offloading enabled X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2009 13:45:21 -0000 * Arno J. Klaassen (arno@heho.snv.jussieu.fr) wrote: > > For now I have two cases of corruption - in both cases it is single > > difference of one 128 byte block with file offsets 0x65F872 and > > 0x61A072. > > I had a similar problem last April on a 7-stable box reported > in a 'nfs-server silent data corruption' thread. > > I found : > > - in all failing cases just *one* byte is currupted, 4 or all 8 bits > set to zero *and* the original value is one out of the limited > subset {1, 8, 9} .... > > here is the output of `cmp -x $i/BIG $i/BIG2` for some failing > cases I saved : > > 03869a48 09 00 > 05209d88 09 00 > 01777148 09 00 > 00f10f88 09 00 > 01f4c4c8 11 00 > 06c3d6c8 11 00 > 0725ca48 18 00 > 01608008 09 00 > 00f3b888 18 00 > > 07aa45c8 29 20 > > Does your corruption fulfill these characterisations as well? Nope, as I've written before, it's corruption of single 128 byte block. I've deleted samples during the upgrade process, but I think I'll turn *xcsum back on and do some more tests with NFS, and netcat transfers. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 14:05:31 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B860B106566B; Tue, 27 Jan 2009 14:05:31 +0000 (UTC) (envelope-from oliver.pntr@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 1A6598FC12; Tue, 27 Jan 2009 14:05:29 +0000 (UTC) (envelope-from oliver.pntr@gmail.com) Received: by nf-out-0910.google.com with SMTP id h3so1073800nfh.33 for ; Tue, 27 Jan 2009 06:05:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ltHtVMGHRyXp2wojQro94viDdtjSgGAtXmRgxbp/cJc=; b=KRudAJlxG2tyV7q0qgfiRJj3pCeUiCaAJVJieA+BePjNbMEUd5bWzMRMPf6wfBlbGl PnA2F5t5ZPuREchTL4FcAu8Dwsp1JvdqZk3owSaxOkEScbJOLrEQ//lPV17mSWiszLRJ d4a7CAGyIcom4iZqXopXUpIPrQ/uW3ZNeVO0M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=YkKzk5DIEI1pDMLjKGVe2g1NK3770Qrl8/rIkT9nlgmN6fYfbWSLxyGUpAxYjGubUf l8Kz6C8X0ojcJdZXqDDEW0U2WYLryXhph38/C//DmbZbhQbDwAMVTCJpYJc3fa5O22zc jhifvC/mJJtmLB8xraA7XybonsqC75ymFkg2E= MIME-Version: 1.0 Received: by 10.103.248.1 with SMTP id a1mr2520334mus.40.1233065128901; Tue, 27 Jan 2009 06:05:28 -0800 (PST) In-Reply-To: <00163641792bd5eece046142843d@google.com> References: <6101e8c40901240749h106916adya7d6a8caee4ed155@mail.gmail.com> <00163641792bd5eece046142843d@google.com> Date: Tue, 27 Jan 2009 15:05:28 +0100 Message-ID: <6101e8c40901270605g68d3bc3esc89c65841c82fbcd@mail.gmail.com> From: Oliver Pinter To: scott.gasch@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, =?ISO-8859-1?Q?S=F8ren_Schmidt?= , freebsd-amd64@freebsd.org Subject: Re: Re: Problems with ata driver on current / Asus P5Q-E X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jan 2009 14:05:32 -0000 add S=F8ren to CC On 1/25/09, scott.gasch@gmail.com wrote: > Hi Oliver, > > Thanks for the reply. I'm running bios version 02.61 American Megatrends > Inc; it has never been updated. I just got the latest image (1703) from > ASUS and will try flashing it. > > I don't have my controller set on RAID because I don't want hardware > RAID... it's set on AHCI instead. Maybe this is the difference. Are you > doing hardware RAID? > > I'm still looking over your config and dmesg, thanks for sending those. > I'll report back if I figure anything out. > > Thx, > Scott > > > On Jan 24, 2009 7:49am, Oliver Pinter wrote: >> I have the same MB, and it running perfect, but I have only 3 SATA HDD >> >> + 1 SATA DVD-RW >> >> >> >> The ICH is in RAID mode. >> >> >> >> Attached my conf and dmesg >> >> >> >> Which version of BIOS use You? >> >> >> >> [snip] >> >> Southbridge >> >> - 6 x SATA 3Gb/s >> >> - Intel(R) Matrix Storage Technology with RAID 0, 1, 5, 10 support >> >> Marvell 88SE6121 >> >> - 1 x UltraDMA 133/100/66 for up to 2 PATA devices >> >> - 1 x External SATA 3Gb/s port (SATA On-the-Go) >> >> Silicon Image Sil5723 (Drive Xpert technology) >> >> - 2 x SATA 3Gb/s >> >> - Supports EZ Backup and Super Speed functions >> >> [snip] >> >> >> >> > http://www.asus.com/products.aspx?l1=3D3&l2=3D11&l3=3D709&l4=3D0&model=3D= 2267&modelmenu=3D2 >> >> >> >> /* sorry for bad english */ >> >> >> >> On 1/24/09, Scott Gasch scott.gasch@gmail.com> wrote: >> >> > Hi, >> >> > I've been running a 7.1-p1 (amd64) system and and seeing very high > interrupt >> >> > rates on irq19 which is shared between several devices. Over 60% of on= e >> >> > core is used responding to interrupts. The machine also hangs > frequently. >> >> > irq19 is shared by atapci1, atapci2, fwohci0 and uhci4... >> >> > the consensus response to my last question was that "it's probably the > ata >> >> > driver". >> >> > >> >> > Today I tried building and booting a GENERIC current kernel and got > another >> >> > piece of information. The freebsd-current GENERIC kernel does not boot= ; >> >> > shortly after probing the drives it says "Cannot setup DMA" several > times on >> >> > the console and hangs. >> >> > >> >> > This machine is an Asus P5Q-E... I believe it has two ATA controllers: >> >> > a Marvell >> >> > 88SE6121 and a Silicon Image SIL5723. Is one of these chipsets > generating >> >> > interrupts that the driver doesn't understand and/or properly dismiss? > Can >> >> > it be put into a legacy mode that works? This machine has problems in > 7.0, >> >> > 7.1 and current... I'm running out of ideas. >> >> > >> >> > Thx, >> >> > Scott >> >> > _______________________________________________ >> >> > 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 Jan 27 14:07:16 2009 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 116971065693 for ; Tue, 27 Jan 2009 14:07:16 +0000 (UTC) (envelope-from oliver.pntr@gmail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id 6E46C8FC14 for ; Tue, 27 Jan 2009 14:07:14 +0000 (UTC) (envelope-from oliver.pntr@gmail.com) Received: by ewy14 with SMTP id 14so2605437ewy.19 for ; Tue, 27 Jan 2009 06:07:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=0OiLgLEF8rIh89geJ7IzzhFg9i7Azu3OpZ7UgJYqOTw=; b=BH3ATDxi6jwkz8joPdpvg4mpOwtKZZ6MlRKuPQxq8zujj1bBbFLbnhywoA39ShlbTa UqbNh8eYTB6bj14FsL3L+kYmFZywrnUn3qFHub9uRXg2qWeQJ2B91AjwC+/JNTtuG3Ti 3dFL5xfDlzy2mI7i03LhblFSfXknNO/Bv1RVM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=MZB/PYND5AdbwjUWYg3j5WW/kKDe8qmO6cRgmNBoI1BUkXyFPM3p0P3i1B+kSdP5gb DvL1z5jJ8H+KVb5kF4FsaaS+pJ5WzQrHJMOdm/llsyswA0c94YI/2hgMlVBkxsQDpIYY SIwdTZWrSfTItYmkA5sMlZlMvBauRTIdKMIhQ= MIME-Version: 1.0 Received: by 10.102.247.4 with SMTP id u4mr880646muh.128.1233065234058; Tue, 27 Jan 2009 06:07:14 -0800 (PST) In-Reply-To: References: Date: Tue, 27 Jan 2009 15:07:13 +0100 Message-ID: <6101e8c40901270607i73baea4bxf903a6aab95afc29@mail.gmail.com> From: Oliver Pinter To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: hackers@freebsd.org, current Subject: Re: WANTED! board models with Marvell 61XX chips X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jan 2009 14:07:16 -0000 Hi ASUS P5Q-E has 88SE6121 On 1/26/09, S=F8ren Schmidt wrote: > Hi there! > > I thought I finally had a motherboard using one of the Marvell SATA/ > PATA chips coming in, but unfortunately the delivery has been > postponed to some unspecified date, oh well.. > > Thats where you come into the picture as I'd like to get another one, > but finding boards that uses these is a bit tricky as most vendors > doesn't write such unimportant stuff on their web pages (hell it works > in windows!). > > If you have a motherboard using one of the following Marvell chips, or > know for certain a model that does, please send me a private mail with > make and model as there is no need to pollute the lists (which I dont > follow closely for the time being btw). > > The chips in question are: > > Marvell 6111, 6121, 6141 or 6145 > > It is also important that there is physical access to both the SATA > and the PATA port(s) as some boards only utilize one or the other. > > I know of one PCI-express add-in board that uses the 6145, so if > anybody knows how to get ahold of one, that would be very welcomed as > well. The board in question is this: > http://www.sunix.com.tw/it/en/Product_Detail.php?cate=3D2&class_a_id=3D35= &sid=3D538 > So far I've only found shops in South Africa that has it available, > but none of them ships outside the country. > > So if you have any useful info on this topic please get in touch with > me, thanks! > > > -S=F8ren > -- > > > > > > > > > > _______________________________________________ > 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 Jan 27 16:19:53 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84E9010656BC for ; Tue, 27 Jan 2009 16:19:53 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from emh01.mail.saunalahti.fi (emh01.mail.saunalahti.fi [62.142.5.107]) by mx1.freebsd.org (Postfix) with ESMTP id 3F0268FC18 for ; Tue, 27 Jan 2009 16:19:53 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from saunalahti-vams (vs3-12.mail.saunalahti.fi [62.142.5.96]) by emh01-2.mail.saunalahti.fi (Postfix) with SMTP id 1B3A11A8DF for ; Tue, 27 Jan 2009 18:19:52 +0200 (EET) Received: from emh07.mail.saunalahti.fi ([62.142.5.117]) by vs3-12.mail.saunalahti.fi ([62.142.5.96]) with SMTP (gateway) id A02C10CED9E; Tue, 27 Jan 2009 18:19:51 +0200 Received: from a91-153-125-115.elisa-laajakaista.fi (a91-153-125-115.elisa-laajakaista.fi [91.153.125.115]) by emh07.mail.saunalahti.fi (Postfix) with SMTP id 038DD1C6394 for ; Tue, 27 Jan 2009 18:19:50 +0200 (EET) Date: Tue, 27 Jan 2009 18:19:50 +0200 From: Jaakko Heinonen To: freebsd-current@FreeBSD.org Message-ID: <20090127161950.GA3504@a91-153-125-115.elisa-laajakaista.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) X-Antivirus: VAMS Cc: Subject: [patch] nfs attribute cache mount options broken 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: Tue, 27 Jan 2009 16:19:55 -0000 Hi, nfs mount options acregmin, acregmax, acdirmin and acdirmax are broken on CURRENT (unless you use an old mount_nfs binary which passes options differently). The problem is that nfs_mount() (in sys/nfsclient/nfs_vfsops.c) doesn't set flags for those options when they are passed as string options. Also the new code doesn't allow setting the options to 0 which is needed to disable the attribute cache. This patch should fix the problem: http://www.saunalahti.fi/~jh3/patches/nfs-ac-mountopts.diff -- Jaakko From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 17:18:43 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1962A1065673 for ; Tue, 27 Jan 2009 17:18:43 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 8BA098FC0A for ; Tue, 27 Jan 2009 17:18:42 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id n0RHIehg036218; Tue, 27 Jan 2009 18:18:40 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id n0RHIdte036217; Tue, 27 Jan 2009 18:18:39 +0100 (CET) (envelope-from olli) Date: Tue, 27 Jan 2009 18:18:39 +0100 (CET) Message-Id: <200901271718.n0RHIdte036217@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG, terry+freebsd-current@tmk.com, Aristedes Maniatis In-Reply-To: <01N4RNVS3TDW00FK2Q@tmk.com> X-Newsgroups: list.freebsd-current User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 27 Jan 2009 18:18:41 +0100 (CET) Cc: Subject: Re: Help me select hardware and software options for very large ?server X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@FreeBSD.ORG, terry+freebsd-current@tmk.com, Aristedes Maniatis List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2009 17:18:43 -0000 Terry Kennedy wrote: > [Aristedes Maniatis wrote:] > > [Terry Kennedy wrote:] > > > I think this system may have the most storage ever configured on a > > > FreeBSD system, and it is probably up near the top in terms of CPU and > > > memory. > > > > I doubt it. 8 core systems are very common these days. I've seen > > benchmarking with anything up to 64 cores (which I believe is the > > current FreeBSD limit). As for memory, there was a recent thread with > > someone installing 64Gb also claiming theirs was the biggest, but > > others insisting that it certainly wasn't. As for storage, I know Sun > > sell systems into the petabyte range which I assume these days are > > powered by ZFS. > > > > The above is not to belittle your project; more to reassure you that > > you aren't anywhere near the limits and you should have no troubles if > > you tune things properly. > > Regarding storage, while there are other ZFS deployments (particularly > on Sun equipment) which are a lot larger, I haven't seen any discussion > of pools of this size on FreeBSD. And I have been keeping an eye on the > FreeBSD ZFS discussions. That isn't to say that nobody has one, but if > they do, they're keeping pretty quiet about it... Well, I can tell you that your storage setup is _not_ the largest ever configured on a FreeBSD system. Sometimes there are reasons why you cannot disclose details about your (or your customers') setups. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "C++ is the only current language making COBOL look good." -- Bertrand Meyer From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 17:55:39 2009 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 E877B106564A; Tue, 27 Jan 2009 17:55:39 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.freebsd.org (Postfix) with ESMTP id BC4C08FC08; Tue, 27 Jan 2009 17:55:39 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.141] (may be forged)) by mxout4.cac.washington.edu (8.14.3+UW08.09/8.14.3+UW08.11) with ESMTP id n0RHtZS3014179 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 27 Jan 2009 09:55:35 -0800 X-Auth-Received: from [192.168.10.7] (adsl-99-146-97-242.dsl.pltn13.sbcglobal.net [99.146.97.242]) (authenticated authid=youshi10) by smtp.washington.edu (8.14.3+UW08.09/8.14.3+UW08.11) with ESMTP id n0RHtXte011391 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 27 Jan 2009 09:55:34 -0800 Message-Id: <92231DDF-6ACE-467D-AD8F-CF31740F365F@gmail.com> From: Garrett Cooper To: Oliver Pinter In-Reply-To: <6101e8c40901270607i73baea4bxf903a6aab95afc29@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 27 Jan 2009 10:00:28 -0800 References: <6101e8c40901270607i73baea4bxf903a6aab95afc29@mail.gmail.com> X-Mailer: Apple Mail (2.930.3) X-PMX-Version: 5.5.0.356843, Antispam-Engine: 2.6.1.350677, Antispam-Data: 2009.1.27.174318 X-Uwash-Spam: Gauge=IIIIIII, Probability=8%, Report='FORGED_FROM_GMAIL 0.1, BODY_SIZE_1700_1799 0, BODY_SIZE_5000_LESS 0, __BOUNCE_CHALLENGE_SUBJ 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FRAUD_419_LOC 0, __FRAUD_419_WEBMAIL 0, __FRAUD_419_WEBMAIL_FROM 0, __FROM_GMAIL 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_SUBJ_9 0' Cc: hackers@freebsd.org, current , =?ISO-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: WANTED! board models with Marvell 61XX chips X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jan 2009 17:55:40 -0000 On Jan 27, 2009, at 6:07 AM, Oliver Pinter wrote: > Hi ASUS P5Q-E has 88SE6121 > > On 1/26/09, S=F8ren Schmidt wrote: >> Hi there! >> >> I thought I finally had a motherboard using one of the Marvell SATA/ >> PATA chips coming in, but unfortunately the delivery has been >> postponed to some unspecified date, oh well.. >> >> Thats where you come into the picture as I'd like to get another one, >> but finding boards that uses these is a bit tricky as most vendors >> doesn't write such unimportant stuff on their web pages (hell it =20 >> works >> in windows!). >> >> If you have a motherboard using one of the following Marvell chips, =20= >> or >> know for certain a model that does, please send me a private mail =20 >> with >> make and model as there is no need to pollute the lists (which I dont >> follow closely for the time being btw). >> >> The chips in question are: >> >> Marvell 6111, 6121, 6141 or 6145 >> >> It is also important that there is physical access to both the SATA >> and the PATA port(s) as some boards only utilize one or the other. >> >> I know of one PCI-express add-in board that uses the 6145, so if >> anybody knows how to get ahold of one, that would be very welcomed as >> well. The board in question is this: >> = http://www.sunix.com.tw/it/en/Product_Detail.php?cate=3D2&class_a_id=3D35&= sid=3D538 >> So far I've only found shops in South Africa that has it available, >> but none of them ships outside the country. >> >> So if you have any useful info on this topic please get in touch with >> me, thanks! ASUS M3N-HT has a 6111 chipset hooked up to the e-SATA. Is that =20= sufficient for your testing? Let me know and I'll help round up some parts for you... Cheers, -Garrett= From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 18:02:23 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87907106566B for ; Tue, 27 Jan 2009 18:02:23 +0000 (UTC) (envelope-from cdk1@bsd.cl) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by mx1.freebsd.org (Postfix) with ESMTP id 69A568FC1A for ; Tue, 27 Jan 2009 18:02:23 +0000 (UTC) (envelope-from cdk1@bsd.cl) Received: by wa-out-1112.google.com with SMTP id k34so825725wah.27 for ; Tue, 27 Jan 2009 10:02:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.114.59.1 with SMTP id h1mr889090waa.87.1233079342559; Tue, 27 Jan 2009 10:02:22 -0800 (PST) Date: Tue, 27 Jan 2009 15:02:22 -0300 Message-ID: From: Carlos Corona To: freebsd-current@freebsd.org, FreeBSD en castellano Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Mplayer in tty* X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jan 2009 18:02:23 -0000 Hi * I have FreeBSD 8 with mplayer, and VESA support in the kernel, I tried to watch movies on the console type tty *, making audio only, no image. I tried -vo caca,-vo fbdev, vo svglib etc, any thoughts on this? [CdK1@Reina-Tonia ~/Desktop]$ uname -a FreeBSD Reina-Tonia 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sun Jan 18 21:47:13 CLST 2009 root@Reina-Tonia.localhost:/usr/obj/usr/src/sys/Segvfault i386 [CdK1@Reina-Tonia ~/Desktop]$ pkg_info | grep mplayer mplayer-0.99.11_11 High performance media player supporting many formats mplayer-skins-1.1.2_6 Skins for MPlayer's Graphical User Interface (GUI) [CdK1@Reina-Tonia ~/Desktop]$ -- Carlos Corona BSD Chile http://www.bsd.cl From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 18:26:37 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 735731065704 for ; Tue, 27 Jan 2009 18:26:37 +0000 (UTC) (envelope-from llc2w@virginia.edu) Received: from fork2.mail.virginia.edu (fork2.mail.Virginia.EDU [128.143.2.192]) by mx1.freebsd.org (Postfix) with ESMTP id 0E9D88FC14 for ; Tue, 27 Jan 2009 18:26:36 +0000 (UTC) (envelope-from llc2w@virginia.edu) Received: from localhost (localhost [127.0.0.1]) by fork2.mail.virginia.edu (Postfix) with ESMTP id C71DE1BFA8 for ; Tue, 27 Jan 2009 13:06:49 -0500 (EST) Received: from fork2.mail.virginia.edu ([127.0.0.1]) by localhost (fork2.mail.virginia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17007-10 for ; Tue, 27 Jan 2009 13:06:49 -0500 (EST) Received: from mail-gx0-f16.google.com (mail-gx0-f16.google.com [209.85.217.16]) by fork2.mail.virginia.edu (Postfix) with ESMTP id 9F7691BF8B for ; Tue, 27 Jan 2009 13:06:49 -0500 (EST) Received: by mail-gx0-f16.google.com with SMTP id 9so5874953gxk.0 for ; Tue, 27 Jan 2009 10:06:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.231.20.2 with SMTP id d2mr385160ibb.27.1233079609103; Tue, 27 Jan 2009 10:06:49 -0800 (PST) In-Reply-To: References: Date: Tue, 27 Jan 2009 13:06:49 -0500 Message-ID: <792298050901271006t7feb094et97f77b6ee7d290b5@mail.gmail.com> From: L Campbell To: Carlos Corona Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-UVA-Virus-Scanned: by amavisd-new at fork2.mail.virginia.edu Cc: freebsd-current@freebsd.org, FreeBSD en castellano Subject: Re: Mplayer in tty* X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jan 2009 18:26:39 -0000 On Tue, Jan 27, 2009 at 1:02 PM, Carlos Corona wrote: > I have FreeBSD 8 with mplayer, and VESA support in the kernel, I tried to > watch movies on the console type tty *, making audio only, no image. I tried > -vo caca,-vo fbdev, vo svglib etc, any thoughts on this? What about -vo vesa? From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 18:46:32 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6A1C106566B for ; Tue, 27 Jan 2009 18:46:32 +0000 (UTC) (envelope-from ptice@aldridge.com) Received: from starbase.aldridge.com (starbase.aldridge.com [205.196.186.12]) by mx1.freebsd.org (Postfix) with ESMTP id 92B048FC14 for ; Tue, 27 Jan 2009 18:46:32 +0000 (UTC) (envelope-from ptice@aldridge.com) Received: from corporate.aldridge.com (corporate.aldridge.com [216.139.69.10]) by starbase.aldridge.com (8.14.3/8.14.2) with ESMTP id n0RIjXk2092323 for ; Tue, 27 Jan 2009 12:45:33 -0600 (CST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 27 Jan 2009 12:41:20 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Help me select hardware....Some real world data that might help Thread-Index: Acl901Jj6YXzWgeRTR+JrojYu6LVEQC1V+BI References: <01N4NEOEB7LY00EQWX@tmk.com> From: "Paul Tice" To: "Terry Kennedy" , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: RE: Help me select hardware....Some real world data that might help X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jan 2009 18:46:33 -0000 Excuse my rambling, perhaps something in this mess will be useful. I'm currently using 8 cores (2x Xeon E5405), 16G FB-DIMM, and 8 x 750GB = drives on a backup system (I plan to add the other in the chassis one by = one, testing the speed along the way) 8-current AMD64, ZFS, Marvell 88sx6081 PCI-X card (8 port SATA) + = LSI1068E (8 port SAS/SATA) for the main Array, and the Intel onboard = SATA for boot drive(s). Data is sucked down through 3 gigabit ports, with another available but = not yet activated.=20 Array drives all live on the LSI right now. Drives are . ZFS is stable _IF_ you disable the prefetch and ZIL, otherwise the = classic ZFS wedge rears it's ugly head. I haven't had a chance to test = just one yet, but I'd guess it's the prefetch that's the quick killer. = Even with prefetching and ZIL disabled, my current bottleneck is the = GigE. I'm waiting to get new switches in that support jumbo frames, = quick and dirty testing shows almost 2x increase in throughput, and ~40% = drop in interrupt rates from the NICs compared to the current standard = (1500 MTU) frames. Pool was created with 'zpool create backup raidz da0 da1 da2 da3 da4 da5 = da6 da7' I've seen references to 8-Current having a kernel memory limit of 8G = (compared to 2G for pre 8 from what I understand so far) and ZFS ARC = (caching) is done in kernel memory space. (Please feel free to correct = me if I'm wrong on any of this!) Default ZFS (no disables) with a 1536M kern mem limit, and 512M ARC = limit, I saw 2085 ARC memory throttles before the box wedged. Using rsync over several machines with this setup, I'm getting a little = over 1GB/min to the disks.=20 'zpool iostat 60' is a wonderful tool.=20 I would mention something I've noticed that doesn't seem to be = documented: The first reading from 'zpool iostat' (whether single run or with an = interval) is a running average, although I haven't found the time period = averaged yet. (from pool mount time maybe?) The jumbo frame interrupt reduction may be important. I run 'netstat -i = -w60' right beside 'zpool iostat 60', and the throughput is closely = inversely related. I can predict a disk write (bursty writes in ZFS it = seems) by throughput dropping to on the NIC side. The drop is up to 75% = averaging around 50%. Using a 5 interval instead of 60, I see disk out = throughput spikes up to 90MB/s, although 55, 0, 0, 0, 55 is more common. = Possibly, binding interrupts to particular cpu's might help a bit too. I = haven't found, and don't feel competent to write, userspace tools to do = this. CPU usage during all this is suprisingly low. rsync is running with -z, = the files themselves are compressed as they go onto the drives with = pbzip2, and the whole thing runs on (ducking) BackupPC, which is all = perl script.=20 With all that, 16 machines backing up, and 1+GB/Min going to the = platters, CPU is still avg 40% idle using top. I'm considering remaking = the array raidz2, I seem to have enough CPU to handle it. Random ZFS thoughts: You cannot shrink/grow a raidz or raidz2. You can grow a stripe array, = I'm don't know if you can shrink it successfully. You cannot promote a stripe array to raidz/z2, nor demote in the other = direction. You can have hot spares, haven't seen a provision for warm/cold spares. /etc/default/rc.conf already has cron ZFS status/scrub checks, but not = enabled. Anyway, enough rambling, just thought I'd use something not too = incredibly far from your suggested system to toss some data out. Thanks Paul -----Original Message----- From: owner-freebsd-current@freebsd.org on behalf of Terry Kennedy Sent: Fri 1/23/2009 8:30 PM To: freebsd-current@freebsd.org Subject: Help me select hardware and software options for very large = server =20 [I posted the following message to freebsd-questions, as I thought it woule be the most appropriate list. As it has received no replies in two weeks, I'm trying freebsd-current.] -------- [I decided to ask this question here as it overlaps -hardware, = -current, and a couple other lists. I'd be glad to redirect the conversation to a list that's a better fit, if anyone would care to suggest one.] I'm in the process of planning the hardware and software for the = second generation of my RAIDzilla file servers (see = http://www.tmk.com/raidzilla for the current generation, in production for 4+ years). I expect that what I'm planning is probably "off the scale" in terms = of processing and storage capacity, and I'd like to find out and address = any issues before spending lots of money. Here's what I'm thinking of: o Chassis - CI Design SR316 (same model as current chassis, except i2c = link between RAID controller and front panel o Motherboard - Intel S5000PSLSATAR o CPU - 2x Intel Xeon E5450 BX80574E5450P p Remote management - Intel Remote Management Module 2 - AXXRM2 o Memory - 16GB - 8x Kingston KVR667D2D4F5/2GI o RAID controller - 3Ware 9650SE-16ML w/ BBU-MODULE-04 o Drives - 16x 2TB drives [not mentioning manufacturer yet] o Cables - 4x multi-lane SATA cables o DVD-ROM drive o Auxiliary slot fan next to BBU card o Adaptec AHA-39160 (for Quantum Superloader 3 tape drive) So much for the hardware. On the software front: o FreeBSD 8.x? o amd64 architecture o MBR+UFS2 for operating system partitions (hard partition in = controller) o GPT+ZFS for data partitions o Multiple 8TB data partitions (separate 8TB controller partitions or = one big partition divided with GPT?) I looked at "Large data storage in FreeBSD", but that seems to be a = stale page from 2005 or so: http://www.freebsd.org/projects/bigdisk/index.html I'm pretty sure I need ZFS, since even with the 2TB partitions I have = now, taking snapshots for dump or doing a fsck take approximately forever 8-) I'll be using the harware RAID 6 on the 3Ware controller, so I'd only be using ZFS to get filesystems larger than 2TB. I've been following the ZFS discussions on -current and -stable, and I think that while it isn't quite ready yet, it probably will be ready in a few months, being available around the same time I get this hardware asssembled. I recall reading that there will be an import of newer ZFS=20 code in the near future. Similarly, the ports collection seems to be moving along nicely with amd64 support. I think this system may have the most storage ever configured on a FreeBSD system, and it is probably up near the top in terms of CPU and memory. Once I have it assembled I'd be glad to let any FreeBSD devel- opers test and stress it if that would help improve FreeBSD on that type of configuration. In the meantime, any suggestions regarding the hardware or software con- figuration would be welcomed. Terry Kennedy http://www.tmk.com terry@tmk.com New York, NY USA _______________________________________________ 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 Jan 27 20:14:11 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3DC21065689 for ; Tue, 27 Jan 2009 20:14:11 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.freebsd.org (Postfix) with ESMTP id A73C08FC14 for ; Tue, 27 Jan 2009 20:14:11 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id E7EE71A000B17 for ; Tue, 27 Jan 2009 11:42:43 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at smtp.sd73.bc.ca Received: from coal.localnet (unknown [192.168.0.10]) by smtp.sd73.bc.ca (Postfix) with ESMTP id 83B111A000B16 for ; Tue, 27 Jan 2009 11:42:41 -0800 (PST) From: Freddie Cash To: freebsd-current@freebsd.org Date: Tue, 27 Jan 2009 11:42:41 -0800 User-Agent: KMail/1.10.4 (Linux/2.6.26-1-686; KDE/4.1.4; i686; ; ) References: <01N4NEOEB7LY00EQWX@tmk.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901271142.41296.fjwcash@gmail.com> Subject: Re: Help me select hardware....Some real world data that might help X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jan 2009 20:14:12 -0000 On January 27, 2009 10:41 am Paul Tice wrote: > Excuse my rambling, perhaps something in this mess will be useful. > > I'm currently using 8 cores (2x Xeon E5405), 16G FB-DIMM, and 8 x 750GB > drives on a backup system (I plan to add the other in the chassis one by > one, testing the speed along the way) 8-current AMD64, ZFS, Marvell > 88sx6081 PCI-X card (8 port SATA) + LSI1068E (8 port SAS/SATA) for the > main Array, and the Intel onboard SATA for boot drive(s). Data is sucked > down through 3 gigabit ports, with another available but not yet > activated. Array drives all live on the LSI right now. Drives are ST3750640AS K>. > > ZFS is stable _IF_ you disable the prefetch and ZIL, otherwise the > classic ZFS wedge rears it's ugly head. I haven't had a chance to test > just one yet, but I'd guess it's the prefetch that's the quick killer. You probably don't want to disable the ZIL. That's the journal, and an important part of the data integrity setup for ZFS. Prefetch has been shown to cause issues on a lot of systems, and can be a bottleneck depending on the workload. But the ZIL should be enabled. > I've seen references to 8-Current having a kernel memory limit of 8G > (compared to 2G for pre 8 from what I understand so far) and ZFS ARC FreeBSD 8.x kmem_max has been bumped to 512 GB. > Using rsync over several machines with this setup, I'm getting a little > over 1GB/min to the disks. 'zpool iostat 60' is a wonderful tool. gstat is even nicer, as it shows you the throughput to the individual drives, instead of the aggregate that zpool shows. This works at the GEOM level. Quite nice to see how the I/O is balanced (or not) across the drives in the raidz datasets, and the pool as a whole. > CPU usage during all this is suprisingly low. rsync is running with -z, If you are doing rsync over SSH, don't use -z as part of the rsync command. Instead, use -C with ssh. That way, rsync is done in one process, and the compression is done by ssh in another process, and it will use two CPUs/cores instead of just one. You'll get better throughput that way, as the rsync process doesn't have to do the compression and reading/writing in the same process. We got about a 25% boost in throughput by moving the compress out of the rsync, and CPU usage balanced across CPUs instead of just hogging one. > Random ZFS thoughts: > You cannot shrink/grow a raidz or raidz2. You can't add devices to a raidz/raidz2 dataset. But you can replace the drives with larger ones, do a resilver, and the extra space will become available. Just pull the small drive, insert the large drive, and do a "zfs replace ". And you can add extra raidz/raidz2 datasets to a pool, and ZFS will stripe the data across the raidz datasets. Basically, the pool becomes a RAID 5+0 or RAID 6+0, instead of just a RAID 5/RAID 6. If you have lots of drives, the recommendations from the Solaris folks is to use a bunch of raidz datasets comprised of <=9 disks each, instead of one giant raidz dataset across all the drives. ie: zfs create pool raidz2 da0 da1 da2 da3 da4 da5 zfs add pool raidz2 da6 da7 da8 da9 da10 da11 zfs add pool raidz2 da12 da13 da14 da15 da16 da17 Will give you a single pool comprised of three raidz2 datasets, with data being striped across the three datasets. And you can add raidz datasets to the pool as needed. > You can grow a stripe array, > I'm don't know if you can shrink it successfully. You cannot promote a > stripe array to raidz/z2, nor demote in the other direction. You can have > hot spares, haven't seen a provision for warm/cold spares. ZFS in FreeBSD 7.x doesn't support hot spares, in that a faulted drive won't start a rebuild using a spare drive. You have to manually "zfs replace" the drive using the spare. ZFS in FreeBSD 8.x does support auto-rebuild using spare drives (hot spare). > /etc/default/rc.conf already has cron ZFS status/scrub checks, but not > enabled. periodic(8) does ZFS checks as part of the daily run. See /etc/defaults/periodic.conf. However, you can whip up a very simple shell script that does the same, and run it via cron at whatever interval you want. We use the following, that runs every 15 mins: #!/bin/sh status=$( zpool status -x ) if [ "${status}" != "all pools are healthy" ]; then echo "Problems with ZFS: ${status}" | mail -s "ZFS Issues on " \ fi exit 0 -- Freddie fjwcash@gmail.com From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 20:49:07 2009 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 E4DAA106566C for ; Tue, 27 Jan 2009 20:49:07 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: from web63907.mail.re1.yahoo.com (web63907.mail.re1.yahoo.com [69.147.97.122]) by mx1.freebsd.org (Postfix) with SMTP id 75D458FC2A for ; Tue, 27 Jan 2009 20:49:07 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: (qmail 17780 invoked by uid 60001); 27 Jan 2009 20:49:07 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID; b=DltRtNBv7nHnNFZJiIsLFNR0yAfEOLDrNuzPqbW8CSkK8N//RXPQxkHnllKP7o2MGEgJNH5iPplp7GYhApNtYloyRlyLSEvuj8hSJZ73/lqb1kM+QhpOTq0bqhgZ5eQxaWg69PkFp/OlNRUra3D7HK9CkREQbqEgZe41/zoB9fg=; X-YMail-OSG: LpTcrrQVM1lZtct9o4j4eRHvoAZM2FMYD8kSdpBHD2DcxPy.30C9_IuS8ECmXIsRaoqYbdftQHOP0J5qwvToWnGV6YO.91TfhyWEtxaQBzu7ME_7XRa6mY3n0UbjQBlrjiroXD8qeKQKcwf2Mk9lP8N.Pw4- Received: from [98.242.222.229] by web63907.mail.re1.yahoo.com via HTTP; Tue, 27 Jan 2009 12:49:06 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Tue, 27 Jan 2009 12:49:06 -0800 (PST) From: Barney Cordoba To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <20296.17088.qm@web63907.mail.re1.yahoo.com> Cc: Subject: Exporting from a preloaded module X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: barney_cordoba@yahoo.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2009 20:49:08 -0000 I have a module foo that depends on bar. If I load the module bar normally, I can access the function I need in foo with no problem. However if I preload foo in loader.conf, I have a problem: 1) bar can't be loaded because it says foo isn't available if I keep the MODULE_DEPEND declaration. 2) If I remove the dependence, bar gets unresolved externals. It seems that the dependence is broken, as bar is loaded and shows in the module list. Barney From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 21:43:29 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5C45106573C for ; Tue, 27 Jan 2009 21:43:29 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.243]) by mx1.freebsd.org (Postfix) with ESMTP id 8F7A08FC1A for ; Tue, 27 Jan 2009 21:43:29 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: by an-out-0708.google.com with SMTP id b38so1352136ana.13 for ; Tue, 27 Jan 2009 13:43:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:received:received :message-id:date:subject:from:to:user-agent:mime-version :content-type:content-transfer-encoding:x-priority:importance; bh=vQUj7mRRVaXsTDjvS+pT1yYyfKhD9vhXhRDlrl7UCkU=; b=GOKSDA6kRku2m+6mFOzjTfsHJkyAmJHdLQ2V+B2etuZ/Us+jdgCgzghPp0W0bxZ1XY 1vagVN0eAahE89JdmEfFJ+6ULMTIxe3DDoTbsda00tP/t3vbZa0TKnMLgqEH9UXS/lIK bQaun6299WfCkvdXFbGudF2/l6KqQMwHcn+vk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:subject:from:to:user-agent:mime-version :content-type:content-transfer-encoding:x-priority:importance; b=wKAGMcwf2tTY86HaJC9+O+BGaIP7Sd6wsDfU9SJZrP/IZOLi6sOsJGoWXLrV1oPL2T r92CZ7qRBEsIQ6vlbn65atzuNdYQcwYVH+lViKsuonOVwwxfvdF3GV0ZF7PDgSB7KzYe p9AdiERkw8YK4J7HRnfaLdMenM/X9hNHJfoNE= Received: by 10.100.171.10 with SMTP id t10mr4986035ane.53.1233092608837; Tue, 27 Jan 2009 13:43:28 -0800 (PST) Received: from cygnus.homeunix.com ([189.71.8.214]) by mx.google.com with ESMTPS id d29sm19181535and.34.2009.01.27.13.43.26 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 27 Jan 2009 13:43:27 -0800 (PST) Sender: Nenhum_de_Nos Received: by cygnus.homeunix.com (Postfix, from userid 80) id C9142B8061; Tue, 27 Jan 2009 18:43:21 -0300 (BRT) Received: from 189.92.18.120 (SquirrelMail authenticated user matheus) by cygnus.homeunix.com with HTTP; Tue, 27 Jan 2009 19:43:21 -0200 (BRST) Message-ID: <9205533c10f7f0cebe246cd891d7fd2e.squirrel@cygnus.homeunix.com> Date: Tue, 27 Jan 2009 19:43:21 -0200 (BRST) From: "Nenhum_de_Nos" To: freebsd-current@freebsd.org User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: cpu cooler speed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jan 2009 21:43:30 -0000 hail, I have a recent current running on amd64 asus laptop that is hell hot. when in Windows, it spins faster than it is (is almost stopped) and is not hot when not compiling. is there anything I can do to better this ? I made some changes to acpi_asus and it loads for my notebook, but even though is still hot ... thanks, matheus -- We will call you cygnus, The God of balance you shall be From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 21:51:14 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 453741065774 for ; Tue, 27 Jan 2009 21:51:14 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by mx1.freebsd.org (Postfix) with ESMTP id CACAC8FC41 for ; Tue, 27 Jan 2009 21:51:13 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by ey-out-2122.google.com with SMTP id d26so907413eyd.7 for ; Tue, 27 Jan 2009 13:51:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=OLVzzMZA57umSgbWMxX50EabTrGyln2mPcNtRO2b3bQ=; b=sbu5sEECBP0h+L+m1bVk+mo0F7k143eK6i1u9ycDlSo7UZf6RBleEOuU6Ee3zOl/mC hjCnM34tHK2SSZ2opfnAa+38sxw7ZaEGZ7wRhGAmfHgDgzyNjabrr2B4ophh2P3U4u0j vBEMwGD1dEF4pGS9W43cwgjsWmVl04ye3Hli8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=b7zHa62oRWRODOdR9RySVhJYiZe+iBTlUVyAB5+1B/ieAV0wMqppCnLzkub/wE532R CmWPIgE9dM8EXoKCveGscNILFI4K2JN57OlU8QlvehG2DkPBSuVvi0uAiVXlUK8axsbN V3ib/pRFcBG1bt2DPVqFRI+90hJJn2LT5qq8U= MIME-Version: 1.0 Received: by 10.86.31.18 with SMTP id e18mr162556fge.72.1233093072473; Tue, 27 Jan 2009 13:51:12 -0800 (PST) Date: Wed, 28 Jan 2009 00:51:12 +0300 Message-ID: From: pluknet To: freebsd-current Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: panic: 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: Tue, 27 Jan 2009 21:51:16 -0000 After sudo perl-after-upgrade -f: (manually transcribed) --- syscall (4, FreeBSD ELF32, write), ... dev = ad6s3d, block = 885656, fs = /var panic: ffs_blkfree: freeing free block cpuid = 0 KBD: enter: panic [thread pid 27 tid 100053 ] Stopped at kbd_enter+0x3a: movl $0,kbd_why Sorry, keyboard was not attached, no bt this time. -- wbr, pluknet From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 22:02:20 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C2301065689 for ; Tue, 27 Jan 2009 22:02:20 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by mx1.freebsd.org (Postfix) with ESMTP id BFF0A8FC13 for ; Tue, 27 Jan 2009 22:02:19 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by ey-out-2122.google.com with SMTP id d26so908394eyd.7 for ; Tue, 27 Jan 2009 14:02:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=KCPmF+zdVbQflHSAy3WdczICp86LRXGB2d3Nu7hGIO4=; b=dYyW+RYTKYtUKrHh3cvvDJiKCaBkByuOhkZH01A3SA7P2XVCbWNNkvrkd8T8Pvf6pJ iGVJGx4x3yZGeYoJ4JgB5UMGrLkRd10pWubzpGd1c6dF9D8V9O4O2nlXol1+i2Cdp4s5 UL+O9738a8ehKMQ1gZ3ktLzcyrZZ5ZeSnQU6M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=qn8DIXu/yQUycuVxE7KDgUwzfcVwZbbPmKyYWeE3HpTmXrE49Goh9RZWUkKmmHzYR0 VU/B/eWK/KZF0G18PkBr+GSVwxfBZhUtONUaLl55L/yJOJkzE6Bw5sOrdcJEAg6i/A/v 6E98XO2PjSyMw84eefkSTEkIr0NpkW0jiullA= MIME-Version: 1.0 Received: by 10.86.76.20 with SMTP id y20mr253353fga.37.1233093738435; Tue, 27 Jan 2009 14:02:18 -0800 (PST) In-Reply-To: References: Date: Wed, 28 Jan 2009 01:02:18 +0300 Message-ID: From: pluknet To: freebsd-current Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: panic: 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: Tue, 27 Jan 2009 22:02:20 -0000 2009/1/28 pluknet : > After sudo perl-after-upgrade -f: > (manually transcribed) > > --- syscall (4, FreeBSD ELF32, write), ... > dev = ad6s3d, block = 885656, fs = /var > panic: ffs_blkfree: freeing free block > cpuid = 0 > KBD: enter: panic > [thread pid 27 tid 100053 ] > Stopped at kbd_enter+0x3a: movl $0,kbd_why > > Sorry, keyboard was not attached, no bt this time. eyk.. after reboot and fsck -y cleanup got this again on /var, block = 944184: (manually transcribed) > bt Tracing pid 27 tid 100053 td 0xc5964900 kdb_enter panic ffs_blkfree indir_trunc handle_workitem_freeblocks process_worklist_item softdep_process_worklist softdep_flush fork_exit fork_trampoline -- wbr, pluknet From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 22:10:56 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36CFE1065687 for ; Tue, 27 Jan 2009 22:10:56 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id CCD4C8FC24 for ; Tue, 27 Jan 2009 22:10:55 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1LRw8z-000NtL-8Y; Wed, 28 Jan 2009 00:10:53 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n0RMAnl0042565 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Jan 2009 00:10:49 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n0RMAmRl068379; Wed, 28 Jan 2009 00:10:48 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n0RMAmbS068378; Wed, 28 Jan 2009 00:10:48 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 28 Jan 2009 00:10:48 +0200 From: Kostik Belousov To: pluknet Message-ID: <20090127221047.GH2009@deviant.kiev.zoral.com.ua> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QwZB9vYiNIzNXIj" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1LRw8z-000NtL-8Y e76c553cb40bc70e544bb5ee7f4cd500 X-Terabit: YES Cc: freebsd-current Subject: Re: panic: 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: Tue, 27 Jan 2009 22:10:57 -0000 --+QwZB9vYiNIzNXIj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 28, 2009 at 01:02:18AM +0300, pluknet wrote: > 2009/1/28 pluknet : > > After sudo perl-after-upgrade -f: > > (manually transcribed) > > > > --- syscall (4, FreeBSD ELF32, write), ... > > dev =3D ad6s3d, block =3D 885656, fs =3D /var > > panic: ffs_blkfree: freeing free block > > cpuid =3D 0 > > KBD: enter: panic > > [thread pid 27 tid 100053 ] > > Stopped at kbd_enter+0x3a: movl $0,kbd_why > > > > Sorry, keyboard was not attached, no bt this time. >=20 > eyk.. after reboot and fsck -y cleanup got this again on /var, > block =3D 944184: >=20 > (manually transcribed) > > bt > Tracing pid 27 tid 100053 td 0xc5964900 > kdb_enter > panic > ffs_blkfree > indir_trunc > handle_workitem_freeblocks > process_worklist_item > softdep_process_worklist > softdep_flush > fork_exit > fork_trampoline What revision of the sys/ufs/ffs/ffs_inode.c do you use ? --+QwZB9vYiNIzNXIj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkl/hmcACgkQC3+MBN1Mb4j6KQCgzw/+PaU4eBXbrDj5c2yDPNsu SXcAoJguHn+2LWLAf9zRuZsPu5jisBr2 =bAqG -----END PGP SIGNATURE----- --+QwZB9vYiNIzNXIj-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 22:17:29 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 946A0106564A for ; Tue, 27 Jan 2009 22:17:29 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.154]) by mx1.freebsd.org (Postfix) with ESMTP id 22A778FC08 for ; Tue, 27 Jan 2009 22:17:28 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by fg-out-1718.google.com with SMTP id e12so257355fga.35 for ; Tue, 27 Jan 2009 14:17:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=99VJeVX8zJFoMXA/2ByBfFC6/PRgp52TN0wXUCjQjxs=; b=b5iNfwa6Zqn/6YVaxK+kY4qb0UkSbSA05o9Xkim4ivAzjWn9xHLpdpFc9UlbtVsmXy 8bA7J++GnVqpZycilcyyIiMcK64C6rPRTY7XIwDY7hVSEcVB5s1ckWYZPCuEfr/sL7FG SABt/psrOYhHhxA8Xjupfd951Vc0vtkI29qHg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=GnNj2iS1tsau9jhxfJc9K8FhqGns0120bbogkAM/bAiYDhzxJ77h4yJSygC2iBXsSa 5jIRTzzxX7SdeRmZKl+zPixFxo6neyERzsqbwjTWRnasUguNsyRCISP/j8VJu/xAyRot zGbOzYlNfjdq/Wx8x8qgqAVTTFVIjYSR1UwKU= MIME-Version: 1.0 Received: by 10.86.25.17 with SMTP id 17mr455027fgy.39.1233094648156; Tue, 27 Jan 2009 14:17:28 -0800 (PST) In-Reply-To: <20090127221047.GH2009@deviant.kiev.zoral.com.ua> References: <20090127221047.GH2009@deviant.kiev.zoral.com.ua> Date: Wed, 28 Jan 2009 01:17:28 +0300 Message-ID: From: pluknet To: Kostik Belousov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current Subject: Re: panic: 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: Tue, 27 Jan 2009 22:17:29 -0000 2009/1/28 Kostik Belousov : > On Wed, Jan 28, 2009 at 01:02:18AM +0300, pluknet wrote: >> 2009/1/28 pluknet : >> > After sudo perl-after-upgrade -f: >> > (manually transcribed) >> > >> > --- syscall (4, FreeBSD ELF32, write), ... >> > dev = ad6s3d, block = 885656, fs = /var >> > panic: ffs_blkfree: freeing free block >> > cpuid = 0 >> > KBD: enter: panic >> > [thread pid 27 tid 100053 ] >> > Stopped at kbd_enter+0x3a: movl $0,kbd_why >> > >> > Sorry, keyboard was not attached, no bt this time. >> >> eyk.. after reboot and fsck -y cleanup got this again on /var, >> block = 944184: >> >> (manually transcribed) >> > bt >> Tracing pid 27 tid 100053 td 0xc5964900 >> kdb_enter >> panic >> ffs_blkfree >> indir_trunc >> handle_workitem_freeblocks >> process_worklist_item >> softdep_process_worklist >> softdep_flush >> fork_exit >> fork_trampoline > > What revision of the sys/ufs/ffs/ffs_inode.c do you use ? > Hi, Kostik. ffs_inode.c,v 1.115 -- wbr, pluknet From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 22:31:09 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74274106564A for ; Tue, 27 Jan 2009 22:31:09 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id 154658FC08 for ; Tue, 27 Jan 2009 22:31:09 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1LRwSZ-000Ova-PW; Wed, 28 Jan 2009 00:31:07 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n0RMV4jm043790 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Jan 2009 00:31:04 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n0RMV4sR074994; Wed, 28 Jan 2009 00:31:04 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n0RMV48W074993; Wed, 28 Jan 2009 00:31:04 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 28 Jan 2009 00:31:04 +0200 From: Kostik Belousov To: pluknet Message-ID: <20090127223103.GI2009@deviant.kiev.zoral.com.ua> References: <20090127221047.GH2009@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="poJSiGMzRSvrLGLs" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1LRwSZ-000Ova-PW 915c8876a7db4817da058894f1b1668e X-Terabit: YES Cc: freebsd-current Subject: Re: panic: 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: Tue, 27 Jan 2009 22:31:09 -0000 --poJSiGMzRSvrLGLs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 28, 2009 at 01:17:28AM +0300, pluknet wrote: > 2009/1/28 Kostik Belousov : > > On Wed, Jan 28, 2009 at 01:02:18AM +0300, pluknet wrote: > >> 2009/1/28 pluknet : > >> > After sudo perl-after-upgrade -f: > >> > (manually transcribed) > >> > > >> > --- syscall (4, FreeBSD ELF32, write), ... > >> > dev =3D ad6s3d, block =3D 885656, fs =3D /var > >> > panic: ffs_blkfree: freeing free block > >> > cpuid =3D 0 > >> > KBD: enter: panic > >> > [thread pid 27 tid 100053 ] > >> > Stopped at kbd_enter+0x3a: movl $0,kbd_why > >> > > >> > Sorry, keyboard was not attached, no bt this time. > >> > >> eyk.. after reboot and fsck -y cleanup got this again on /var, > >> block =3D 944184: > >> > >> (manually transcribed) > >> > bt > >> Tracing pid 27 tid 100053 td 0xc5964900 > >> kdb_enter > >> panic > >> ffs_blkfree > >> indir_trunc > >> handle_workitem_freeblocks > >> process_worklist_item > >> softdep_process_worklist > >> softdep_flush > >> fork_exit > >> fork_trampoline > > > > What revision of the sys/ufs/ffs/ffs_inode.c do you use ? > > >=20 > Hi, Kostik. >=20 > ffs_inode.c,v 1.115 Please, make sure to use 1.116. I did a mistake that was fixed several hours later. --poJSiGMzRSvrLGLs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkl/iycACgkQC3+MBN1Mb4gQHQCeK7Ju7m9kt2l7L1v3lts49lL/ XcwAn2ufRlBIS4n6a90y3jf03JhPNb2G =Fk86 -----END PGP SIGNATURE----- --poJSiGMzRSvrLGLs-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 22:35:38 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B85810656F7 for ; Tue, 27 Jan 2009 22:35:38 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by mx1.freebsd.org (Postfix) with ESMTP id AC2708FC1E for ; Tue, 27 Jan 2009 22:35:37 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by fg-out-1718.google.com with SMTP id e12so262267fga.35 for ; Tue, 27 Jan 2009 14:35:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=TUaYhvCXuF9+Oy5mALx80xZ/lQE6rrajRqb0TV8T6wI=; b=OwvgjpmbAVNoFJ8QwPJfEx8ZJfPJYC1Dv79ay4PBU752wKxhWU7VL2hfBMrenaOZTA OY0pfMImqgZyY30O6tDN0lgjeuVFvH4XrcnQELUjlXhUN3VUqovdke/k4RPGcobJTJHJ k6T5niBCYPuatpV7bsxXOiIZbcY5izVtMVjv0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=HcVUNVFBWTtWj6L2GsEeQjf2QyAizCvIjrtv/c3KPBYbBNU5ZmlJhsEMH5IL1FaswR 1vaHZUF0mKYZY0Q6N347CYKxFt+yksZSD8hnBbtXtxdKf0B80/cpvFfMWml318l3K+VS F2CP5RsUZ9mGH9K5FyBj7AJlc7vnrbDi61z40= MIME-Version: 1.0 Received: by 10.86.70.3 with SMTP id s3mr850952fga.78.1233095736851; Tue, 27 Jan 2009 14:35:36 -0800 (PST) In-Reply-To: <20090127223103.GI2009@deviant.kiev.zoral.com.ua> References: <20090127221047.GH2009@deviant.kiev.zoral.com.ua> <20090127223103.GI2009@deviant.kiev.zoral.com.ua> Date: Wed, 28 Jan 2009 01:35:36 +0300 Message-ID: From: pluknet To: Kostik Belousov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current Subject: Re: panic: 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: Tue, 27 Jan 2009 22:35:38 -0000 2009/1/28 Kostik Belousov : > On Wed, Jan 28, 2009 at 01:17:28AM +0300, pluknet wrote: >> 2009/1/28 Kostik Belousov : >> > On Wed, Jan 28, 2009 at 01:02:18AM +0300, pluknet wrote: >> >> 2009/1/28 pluknet : >> >> > After sudo perl-after-upgrade -f: >> >> > (manually transcribed) >> >> > >> >> > --- syscall (4, FreeBSD ELF32, write), ... >> >> > dev = ad6s3d, block = 885656, fs = /var >> >> > panic: ffs_blkfree: freeing free block >> >> > cpuid = 0 >> >> > KBD: enter: panic >> >> > [thread pid 27 tid 100053 ] >> >> > Stopped at kbd_enter+0x3a: movl $0,kbd_why >> >> > >> >> > Sorry, keyboard was not attached, no bt this time. >> >> >> >> eyk.. after reboot and fsck -y cleanup got this again on /var, >> >> block = 944184: >> >> >> >> (manually transcribed) >> >> > bt >> >> Tracing pid 27 tid 100053 td 0xc5964900 >> >> kdb_enter >> >> panic >> >> ffs_blkfree >> >> indir_trunc >> >> handle_workitem_freeblocks >> >> process_worklist_item >> >> softdep_process_worklist >> >> softdep_flush >> >> fork_exit >> >> fork_trampoline >> > >> > What revision of the sys/ufs/ffs/ffs_inode.c do you use ? >> > >> >> Hi, Kostik. >> >> ffs_inode.c,v 1.115 > Please, make sure to use 1.116. I did a mistake that was fixed several > hours later. > [csuped and rebuilt] It seems 1.116 really fixes this. Cannot reproduce anymore. Thank you. -- wbr, pluknet From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 22:59:19 2009 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 3CE001065939 for ; Tue, 27 Jan 2009 22:59:19 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 97A1A8FC1C for ; Tue, 27 Jan 2009 22:59:18 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: (qmail invoked by alias); 27 Jan 2009 22:59:16 -0000 Received: from p54A3E59D.dip.t-dialin.net (EHLO tron.homeunix.org) [84.163.229.157] by mail.gmx.net (mp067) with SMTP; 27 Jan 2009 23:59:16 +0100 X-Authenticated: #1673122 X-Provags-ID: V01U2FsdGVkX1/2mSM1cyf2eXJB5jZA9z8RexqcmM2BxDAb5uCXtd AWmMdOEcxKaf/I Message-ID: <497F91C3.7040502@gmx.de> Date: Tue, 27 Jan 2009 23:59:15 +0100 From: Christoph Mallon User-Agent: Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Luigi Rizzo References: <20090127132102.GA21574@onelab2.iet.unipi.it> In-Reply-To: <20090127132102.GA21574@onelab2.iet.unipi.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.6 Cc: current@freebsd.org Subject: Re: duplicate typedefs and system headers ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jan 2009 22:59:23 -0000 Luigi Rizzo schrieb: > In a recent commit tp sbin/ipfw, in an attempt to avoid > a large set of header deependencies, i put a 'forward typedef' > declaration in a common header, duplicating something that is in a > system header: > > ipfw2.h: typedef struct _ipfw_insn ipfw_insn; > > netiinet/ip_fw2.h > typedef struct _ipfw_insn { /* template for instructions */ > ... > } ipfw_insn; This just begs to break, if somebody decides to change the name of the underlying type of the typedef. > Sources including both ipfw2.h and /usr/include/netinet/ip_fw2.h > However if the duplication occurs in two non-system files, the > compiler produces an error for a duplicate typedef. > > Now i wonder, is there any compiler option to turn off the check > for duplicate typedefs also for non-system headers ? No. C forbids multiple typedefs of with the same name, even if they are typedefs for the same type. (Side note: C++ allows this.) > BTW the behaviour with duplicate typedefs is curious, > you can try this for yourself with a simple example > involving e.g. /usr/include/sha.h : make a copy of the file > in userspace, and then you can try the following (SHA_CTX > is typedef'ed in sha.h > > --- ok --- > typedef struct SHAstate_st SHA_CTX; > #include > > --- ok --- > #include > typedef struct SHAstate_st SHA_CTX; > > --- error --- > #include "sha.h" > typedef struct SHAstate_st SHA_CTX; > > --- error --- > typedef struct SHAstate_st SHA_CTX; > #include "sha.h" > > --- ok (this is surprising to me) -- > typedef struct SHAstate_st SHA_CTX; > #include > typedef struct SHAstate_st SHA_CTX; > > As you note, it looks like a typedef in a system header > removes the error message for duplicates both before and after. This is a misfeature in GCC and violates the C standard. Also it seems that this misfeature has a bug, too, because it does not only affect system headers, but the effects radiate into normal code, too. Regards Christoph From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 23:15:32 2009 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 4EEEA1065973 for ; Tue, 27 Jan 2009 23:15:32 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id 13EE18FC17 for ; Tue, 27 Jan 2009 23:15:31 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 4159B73098; Wed, 28 Jan 2009 00:21:03 +0100 (CET) Date: Wed, 28 Jan 2009 00:21:03 +0100 From: Luigi Rizzo To: Christoph Mallon Message-ID: <20090127232103.GA40501@onelab2.iet.unipi.it> References: <20090127132102.GA21574@onelab2.iet.unipi.it> <497F91C3.7040502@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <497F91C3.7040502@gmx.de> User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org Subject: Re: duplicate typedefs and system headers ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jan 2009 23:15:32 -0000 On Tue, Jan 27, 2009 at 11:59:15PM +0100, Christoph Mallon wrote: > Luigi Rizzo schrieb: > >In a recent commit tp sbin/ipfw, in an attempt to avoid > >a large set of header deependencies, i put a 'forward typedef' > >declaration in a common header, duplicating something that is in a > >system header: > > > >ipfw2.h: typedef struct _ipfw_insn ipfw_insn; > > > >netiinet/ip_fw2.h > > typedef struct _ipfw_insn { /* template for instructions */ > > ... > > } ipfw_insn; > > This just begs to break, if somebody decides to change the name of the > underlying type of the typedef. Fortunately this is almost impossible -- the system header is basically frozend and if I could change it I would remove the typedef in the first place. I am more worried of compatibility with different compiler. A workaround that seems to work is putting forward declarations just for "struct _ipfw_insn" and use it (instead of the typedef name) in the place that does not include netiinet/ip_fw2.h Would this be better/more compliant with standards -- i.e., is the following code correct ? gcc seems to have no objections. struct foo; int a(struct foo *); typedef struct foo bar; int a(bar *x) { ... } cheers luigi From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 23:49:03 2009 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 A5919106564A for ; Tue, 27 Jan 2009 23:49:03 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: from iron2.pdx.net (iron2.pdx.net [69.64.224.71]) by mx1.freebsd.org (Postfix) with ESMTP id 8C91C8FC1B for ; Tue, 27 Jan 2009 23:49:03 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: (qmail 25566 invoked from network); 27 Jan 2009 15:22:21 -0800 Received: from 069-064-235-060.pdx.net (HELO ?192.168.1.51?) (69.64.235.60) by iron2.pdx.net with SMTP; 27 Jan 2009 15:22:20 -0800 From: Sean Bruno To: current@freebsd.org Content-Type: text/plain Date: Tue, 27 Jan 2009 15:22:20 -0800 Message-Id: <1233098540.2494.6.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 (2.24.3-1.fc10) Content-Transfer-Encoding: 7bit Cc: Subject: NFS mounts dissapearing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jan 2009 23:49:04 -0000 I've noted that my NFS mount of a directory is vanishing periodically under -current. I am unable to unmount/remount the directory and the system returns Permission Denied on all attempts to access the directory. Is this something that is known and being investigated? Sean From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 23:52:16 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 187D81065696 for ; Tue, 27 Jan 2009 23:52:16 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id B0E648FC08 for ; Tue, 27 Jan 2009 23:52:15 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n0RNqFKt024653 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 27 Jan 2009 15:52:15 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <497F9E2F.1000204@freebsd.org> Date: Tue, 27 Jan 2009 15:52:15 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: multipart/mixed; boundary="------------000206080208020709060605" X-DCC-sonic.net-Metrics: ebb.errno.com; whitelist Subject: HEADS UP: svn commit: r187803 - head/sys/net80211 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jan 2009 23:52:16 -0000 This is a multi-part message in MIME format. --------------000206080208020709060605 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit This requires applications that issue certain 802.11 ioctl's to be rebuilt; at the very least ifconfig; probably also wpa_supplicant, and hostapd. Sam --------------000206080208020709060605 Content-Type: message/rfc822; name="svn commit: r187803 - head/sys/net80211.eml" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="svn commit: r187803 - head/sys/net80211.eml" Return-Path: Received: from ebb.errno.com ([unix socket]) (authenticated user=sam bits=0) by ebb.errno.com (Cyrus v2.2.2-BETA) with LMTP; Tue, 27 Jan 2009 15:49:26 -0800 X-Sieve: CMU Sieve 2.2 Return-Path: Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n0RNnQiD024628 for ; Tue, 27 Jan 2009 15:49:26 -0800 (PST) (envelope-from owner-src-committers@FreeBSD.org) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id B943A1A4E51 for ; Tue, 27 Jan 2009 23:48:21 +0000 (UTC) (envelope-from owner-src-committers@FreeBSD.org) Received: by hub.freebsd.org (Postfix) id B016910656C3; Tue, 27 Jan 2009 23:48:20 +0000 (UTC) Delivered-To: sam@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 538) id A1CAE1065670; Tue, 27 Jan 2009 23:48:18 +0000 (UTC) Delivered-To: src-committers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 622C11065676; Tue, 27 Jan 2009 23:48:13 +0000 (UTC) (envelope-from sam@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:4f8:fff6::2c]) by mx1.freebsd.org (Postfix) with ESMTP id 5132D8FC13; Tue, 27 Jan 2009 23:48:13 +0000 (UTC) (envelope-from sam@FreeBSD.org) Received: from svn.freebsd.org (localhost [127.0.0.1]) by svn.freebsd.org (8.14.3/8.14.3) with ESMTP id n0RNmDtI000652; Tue, 27 Jan 2009 23:48:13 GMT (envelope-from sam@svn.freebsd.org) Received: (from sam@localhost) by svn.freebsd.org (8.14.3/8.14.3/Submit) id n0RNmDCS000651; Tue, 27 Jan 2009 23:48:13 GMT (envelope-from sam@svn.freebsd.org) Message-Id: <200901272348.n0RNmDCS000651@svn.freebsd.org> From: Sam Leffler Date: Tue, 27 Jan 2009 23:48:13 +0000 (UTC) To: src-committers@FreeBSD.org, svn-src-all@FreeBSD.org, svn-src-head@FreeBSD.org Subject: svn commit: r187803 - head/sys/net80211 X-SVN-Group: head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: owner-src-committers@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG X-DCC-sonic.net-Metrics: ebb.errno.com; whitelist Author: sam Date: Tue Jan 27 23:48:13 2009 New Revision: 187803 URL: http://svn.freebsd.org/changeset/base/187803 Log: Extend channel definition with: o max antenna gain o driver private opaque data Note this grows the size of a channel to 16 bytes; which makes the default channel table 4Kbytes (up from 3Kbytes). Modified: head/sys/net80211/_ieee80211.h Modified: head/sys/net80211/_ieee80211.h ============================================================================== --- head/sys/net80211/_ieee80211.h Tue Jan 27 23:43:20 2009 (r187802) +++ head/sys/net80211/_ieee80211.h Tue Jan 27 23:48:13 2009 (r187803) @@ -135,6 +135,9 @@ struct ieee80211_channel { int8_t ic_minpower; /* minimum tx power in .5 dBm */ uint8_t ic_state; /* dynamic state */ uint8_t ic_extieee; /* HT40 extension channel number */ + int8_t ic_maxantgain; /* maximum antenna gain in .5 dBm */ + uint8_t ic_pad; + uint16_t ic_devdata; /* opaque device/driver data */ }; #define IEEE80211_CHAN_MAX 256 --------------000206080208020709060605-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 00:13:49 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E52391065670 for ; Wed, 28 Jan 2009 00:13:49 +0000 (UTC) (envelope-from onemda@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 745EE8FC13 for ; Wed, 28 Jan 2009 00:13:49 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by nf-out-0910.google.com with SMTP id h3so1153956nfh.33 for ; Tue, 27 Jan 2009 16:13:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=1FY5nrYrwGBGP2mJRgR7EtI40FvkedLMdxZVpem5yao=; b=NNAGMxOHd1CTZ7WJRoV4b2HkmaJWxRw+1PpCZ01HgZ9szTZrCn4QkkbdkENA0rVox+ 0+zzYHlheyi2BnKWTxnwXxLlbR+KRl5jY+S2pJM74o+q7+r7aoCuwVxL11+OPHzHzoT4 nWXQYn22LL4bRBOl/w/PnQ+T4T/mmmWRkWA7Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=npAEFizLf35k2mOk52oCHYUikkUqnAV0ckR+6SQnQSHA0/cgORXJLIgmZzQ6E1QokZ b6N2dJGPgY4v4qqVcVOKACG9UVd4XSp/8lvOb4j1VanSZhLEXu8WcEw/hhru/jLHXpgR ZAZBDdgtSEGV2I59PnXgRw/Xle6k7n4fWOoKo= MIME-Version: 1.0 Received: by 10.210.20.17 with SMTP id 17mr875325ebt.25.1233101627979; Tue, 27 Jan 2009 16:13:47 -0800 (PST) In-Reply-To: References: Date: Wed, 28 Jan 2009 01:13:47 +0100 Message-ID: <3a142e750901271613y4c545f8do6d79e1595eb4f1a4@mail.gmail.com> From: "Paul B. Mahol" To: Carlos Corona Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, FreeBSD en castellano Subject: Re: Mplayer in tty* X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 00:13:50 -0000 On 1/27/09, Carlos Corona wrote: > Hi * > > > I have FreeBSD 8 with mplayer, and VESA support in the kernel, I tried to > watch movies on the console type tty *, making audio only, no image. I tried > -vo caca,-vo fbdev, vo svglib etc, any thoughts on this? > > > [CdK1@Reina-Tonia ~/Desktop]$ uname -a > FreeBSD Reina-Tonia 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sun Jan 18 21:47:13 > CLST 2009 root@Reina-Tonia.localhost:/usr/obj/usr/src/sys/Segvfault i386 > [CdK1@Reina-Tonia ~/Desktop]$ pkg_info | grep mplayer > mplayer-0.99.11_11 High performance media player supporting many formats > mplayer-skins-1.1.2_6 Skins for MPlayer's Graphical User Interface (GUI) > [CdK1@Reina-Tonia ~/Desktop]$ > > -- > Carlos Corona > BSD Chile > http://www.bsd.cl > _______________________________________________ > 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" > caca, aa and sdl:driver=vgl works fine here. [for svga I dont have properly compiled vesa.ko to test] -- Paul From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 01:20:52 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE69D106566B for ; Wed, 28 Jan 2009 01:20:52 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from smtp.timeweb.ru (smtp.timeweb.ru [217.170.79.85]) by mx1.freebsd.org (Postfix) with ESMTP id 37FA38FC08 for ; Wed, 28 Jan 2009 01:20:52 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1LRz6p-0001XY-3V; Wed, 28 Jan 2009 04:20:51 +0300 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 353026EC3; Wed, 28 Jan 2009 04:21:10 +0300 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id 81338108838; Wed, 28 Jan 2009 04:21:48 +0000 (UTC) Date: Wed, 28 Jan 2009 04:21:48 +0000 From: Dmitry Marakasov To: "Arno J. Klaassen" Message-ID: <20090128042148.GA1256@hades.panopticon> References: <20090123221826.GB30982@deprived.panopticon> <20090126144044.GB6054@hades.panopticon> <20090127164617.GA93440@hades.panopticon> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-current@freebsd.org Subject: Re: Data corruption with checksum offloading enabled X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2009 01:20:53 -0000 * Arno J. Klaassen (arno@heho.snv.jussieu.fr) wrote: > >> [ .. ] > >> 07aa45c8 29 20 > >> > >> Does your corruption fulfill these characterisations as well? > > > > Nope, as I've written before, it's corruption of single 128 byte > > block. > > ok; I didn't quite understand that; so to be clear, 128 contitguous > bytes are corrupt ? Correct. > > I've deleted samples during the upgrade process, but I think I'll turn > > *xcsum back on and do some more tests with NFS, and netcat transfers. > > Thanx; for me it took often hours to provoke the error > > I'lll test later with -current again after having set up a newe > server Results. Each test was ran in a clean system just after reboot (via rc.local). I used 512MB chunks, but I guess that was not enough, as corruption didn't show itself in all the tests. Also there seem to be some problems with NFS on current witch need specific attention - that's why I lost one sample due to NFS lockup and reboot, and that's why I've used 512MB data pieces. 1. 512MB zeroes with netcat: 5/5 correct 2. 512MB zeroes with NFS: 4/4 correct (there seem to also be some NFS lockups on -current, so I lost one sample; it's also the reason I ve 3. 512MB random bytes with NFS: 2/5 correct also tried 512MB random bytes after 10MB via netcat and same 512MB after that (to check for possible shifts). No corruptions here, though. So I only have 3 corruptions. Will do more tests when I have some time. Those reboots take quite a lot of time and need attention due to possible NFS lockups... For now guess is that corruption may be data from the other place of the stream. So stream of zeroes is not affected (or is affected with much lower possibility). Diffs: --- _r.0.h 2009-01-28 04:16:47.000000000 +0000 +++ _r.2.h 2009-01-28 04:16:57.000000000 +0000 @@ -72519,15 +72519,15 @@ 0011b460 6f 3e 2b a2 b9 d4 5f c6 69 df 4e 38 bc 96 7f ef |o>+..._.i.N8....| 0011b470 56 55 5e 65 e3 ab 1e 4b 7c d6 1d 8a a4 51 4e d2 |VU^e...K|....QN.| 0011b480 9a 11 64 ec 39 be 86 2c 07 06 00 79 80 90 8b 70 |..d.9..,...y...p| -0011b490 70 60 b4 97 4d 52 58 a8 e4 30 27 ce 87 90 a4 5e |p`..MRX..0'....^| -0011b4a0 db 4a 0e 03 3a 45 84 97 60 a4 80 3f 92 36 d1 5f |.J..:E..`..?.6._| -0011b4b0 86 90 0a c0 a7 ca 86 73 21 13 6c da 4f 8f 15 fc |.......s!.l.O...| -0011b4c0 c7 d9 61 b5 9e ac 39 79 c5 b3 99 df 9e aa a5 84 |..a...9y........| -0011b4d0 5d 41 6d c2 05 9d 33 7d 71 78 7e 24 2c 83 98 55 |]Am...3}qx~$,..U| -0011b4e0 3e 86 5d 13 8c 41 36 88 93 c8 d6 8f 38 f9 fe 42 |>.]..A6.....8..B| -0011b4f0 21 e3 ef c2 71 8d d8 87 f3 b6 9c 21 08 fe 99 8c |!...q......!....| -0011b500 d4 84 c9 2f 68 ad a0 75 63 e9 16 7e e5 0a f0 d3 |.../h..uc..~....| -0011b510 85 fa 39 e7 2b 3a 8a 93 58 08 29 b2 a0 0b af fc |..9.+:..X.).....| +0011b490 70 60 af 2e 74 ba 2f 2d 46 af 18 b3 c4 93 8b b2 |p`..t./-F.......| +0011b4a0 47 24 9f 09 4d 5b 7b dc b0 96 76 b0 b2 07 55 56 |G$..M[{...v...UV| +0011b4b0 09 dd ad ac 8c be 92 87 83 92 02 ba b3 42 81 15 |.............B..| +0011b4c0 49 5a 6e c5 4a b0 8a e5 c8 c2 bb e0 d8 ba f4 dc |IZn.J...........| +0011b4d0 6d 81 19 52 87 64 6e b0 6f c7 71 0c bc 75 4b e6 |m..R.dn.o.q..uK.| +0011b4e0 02 1f 2e 3b 18 1b e8 d2 47 bb 01 e4 ed ad ac f5 |...;....G.......| +0011b4f0 8f 13 4c bc 8a be 5a 2e ee bd 2c 1f 1f 02 cd eb |..L...Z...,.....| +0011b500 bd 00 8f 1b 9e fa 7f 69 4a e9 16 a1 34 2d 73 7d |.......iJ...4-s}| +0011b510 e7 c0 39 e7 2b 3a 8a 93 58 08 29 b2 a0 0b af fc |..9.+:..X.).....| 0011b520 47 de 34 b7 99 31 80 58 52 d5 fa d0 b0 4e db 96 |G.4..1.XR....N..| 0011b530 61 49 93 a6 03 a3 06 ca 28 da 29 f3 f1 16 ac 13 |aI......(.).....| 0011b540 c3 53 6f 83 ce 15 8e 0c e3 00 09 4d ae 59 4f 67 |.So........M.YOg| --- _r.0.h 2009-01-28 04:16:47.000000000 +0000 +++ _r.3.h 2009-01-28 04:17:06.000000000 +0000 @@ -27534,15 +27534,15 @@ 0006b8d0 43 10 91 3b c6 90 77 31 55 23 f8 1a d1 aa 41 30 |C..;..w1U#....A0| 0006b8e0 0c cd cc b8 6f 4a 0c 83 16 f8 e7 dc 47 cb a1 65 |....oJ......G..e| 0006b8f0 5c f8 e5 f3 f2 b7 05 e4 cb ab a0 49 ea e3 f0 30 |\..........I...0| -0006b900 21 ca d7 a9 10 06 57 f8 44 8b 82 36 b5 0f 03 33 |!.....W.D..6...3| -0006b910 ba c0 ba bd a2 b1 e0 d1 a7 c5 a7 c4 d7 53 bc 80 |.............S..| -0006b920 ea 1f 0e eb f2 aa fc 37 0e e8 67 35 65 78 65 ae |.......7..g5exe.| -0006b930 d6 41 a2 ed dd b6 58 46 26 17 a1 aa ab b5 13 67 |.A....XF&......g| -0006b940 de bd 6f 97 69 f1 31 10 97 25 9d fc 0b e5 34 44 |..o.i.1..%....4D| -0006b950 83 93 87 c5 34 6b 5b ab 1f 50 49 8c fe dc 87 77 |....4k[..PI....w| -0006b960 9d e5 b6 4d 56 11 e3 e3 55 67 6f 9d fc fe b1 9a |...MV...Ugo.....| -0006b970 92 19 45 ba f8 4e 50 a0 ce bc a8 92 85 fe b8 c4 |..E..NP.........| -0006b980 b1 c4 ef 2f c2 55 46 15 1e 01 f0 ff 66 22 e8 3e |.../.UF.....f".>| +0006b900 21 ca d7 a9 10 06 57 f8 44 8b 82 36 b5 0f 03 b1 |!.....W.D..6....| +0006b910 0d 6b c7 31 21 8a 32 41 b2 40 06 c8 8a df 4b 44 |.k.1!.2A.@....KD| +0006b920 a1 3a 65 29 e9 60 07 63 83 03 f8 9f cd 68 e6 5c |.:e).`.c.....h.\| +0006b930 b3 4d ab f5 d6 71 07 60 b6 d0 e6 49 9e 12 61 25 |.M...q.`...I..a%| +0006b940 d9 07 ac e5 2b 13 e2 56 33 5c 5a f3 3a 86 d3 16 |....+..V3\Z.:...| +0006b950 a8 47 cb 91 f6 a2 45 eb db 65 15 93 8a 44 2d 9f |.G....E..e...D-.| +0006b960 c5 22 d4 77 30 c8 e8 b2 dd 3a 7a 06 de 98 d7 66 |.".w0....:z....f| +0006b970 c4 50 f4 96 32 f5 96 e4 e2 b5 1a 28 62 40 c3 4a |.P..2......(b@.J| +0006b980 d0 2e 75 4e f2 bb 7d b1 cb f9 7d 94 e0 dc da 3e |..uN..}...}....>| 0006b990 d9 f2 78 2b f4 5e 10 84 ff 0f 14 92 c4 96 03 66 |..x+.^.........f| 0006b9a0 15 ed 21 38 46 b4 06 f8 c1 e3 90 b4 47 3c 7c ff |..!8F.......G<|.| 0006b9b0 61 e5 04 20 72 1a e2 1e c7 4e 01 d2 d1 14 35 63 |a.. r....N....5c| --- _r.0.h 2009-01-28 04:16:47.000000000 +0000 +++ _r.4.h 2009-01-28 04:17:10.000000000 +0000 @@ -220065,15 +220065,15 @@ 0035ba00 37 a2 34 91 86 cf d5 ba f3 c0 69 18 17 51 c2 99 |7.4.......i..Q..| 0035ba10 64 8c e6 e1 70 eb a5 bd 19 13 26 6e 12 d8 bf b2 |d...p.....&n....| 0035ba20 1d f3 51 12 af ad 01 0b d1 3e 32 4f d0 f7 41 59 |..Q......>2O..AY| -0035ba30 ee 60 4a 2f 81 b9 ee ff 81 1a ef 0b a5 66 6a 6a |.`J/.........fjj| -0035ba40 58 a3 2b b2 a2 75 38 ad 92 c7 1b ec f5 51 14 79 |X.+..u8......Q.y| -0035ba50 14 5e b9 12 c2 b6 0f ff 20 47 ed 2e bb 56 2b f7 |.^...... G...V+.| -0035ba60 ce 10 fa 79 46 88 ed f5 88 a8 9d 1b 1f ba 3c ff |...yF.........<.| -0035ba70 5e 59 01 3e c7 69 0d ec e9 58 49 b7 df 12 4f 59 |^Y.>.i...XI...OY| -0035ba80 f4 12 df 36 d3 fa 99 e9 3c 96 68 81 6e 31 64 60 |...6....<.h.n1d`| -0035ba90 07 b3 21 c7 da d8 b3 1c 7c ca 12 e9 57 ed b4 f6 |..!.....|...W...| -0035baa0 1f e5 5c 96 ae cf 48 37 97 5b c7 9a f1 93 0f b0 |..\...H7.[......| -0035bab0 10 d6 eb 89 33 56 75 6d 17 fc b3 a1 79 62 4c bc |....3Vum....ybL.| +0035ba30 ee 60 4a 2f 81 b9 ee ff 81 1a d1 88 fd 5f 7f 08 |.`J/........._..| +0035ba40 c5 8e eb 07 00 b6 d4 de 92 e2 40 ab 9d 14 eb 84 |..........@.....| +0035ba50 4f 46 e8 12 32 39 1a 85 8c bd 01 ac 49 c9 65 6b |OF..29......I.ek| +0035ba60 7a 3e c0 1e ca 2d e8 82 7b cf 36 69 41 df f7 ed |z>...-..{.6iA...| +0035ba70 c2 fe e1 43 09 01 c0 07 b8 13 01 65 57 bc eb c4 |...C.......eW...| +0035ba80 af 40 dd bb 4e b4 ef 79 d5 fa e6 18 25 5a 9a 55 |.@..N..y....%Z.U| +0035ba90 33 89 62 d2 88 43 5f c5 b1 e1 8a 6d da 8b 5f b8 |3.b..C_....m.._.| +0035baa0 41 bf c0 f2 42 3f 0d b8 61 b6 16 6e e9 1b 6d eb |A...B?..a..n..m.| +0035bab0 34 8f 31 d1 8b 35 52 91 9b 56 b3 a1 79 62 4c bc |4.1..5R..V..ybL.| 0035bac0 6d a0 49 d2 f9 dd f6 53 a1 6f 35 21 ee e8 03 88 |m.I....S.o5!....| 0035bad0 cf 88 71 79 7c 23 20 a9 a2 31 a0 77 44 f3 63 95 |..qy|# ..1.wD.c.| 0035bae0 da 3e b2 c0 7c c8 59 ed bb 05 2a 12 a1 a8 4b c0 |.>..|.Y...*...K.| -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 02:47:28 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85A2D106566B for ; Wed, 28 Jan 2009 02:47:28 +0000 (UTC) (envelope-from mister.olli@googlemail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.190]) by mx1.freebsd.org (Postfix) with ESMTP id 1082E8FC12 for ; Wed, 28 Jan 2009 02:47:27 +0000 (UTC) (envelope-from mister.olli@googlemail.com) Received: by mu-out-0910.google.com with SMTP id i2so4813382mue.3 for ; Tue, 27 Jan 2009 18:47:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:subject:from:reply-to:to :content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; bh=4LAEslfznFroKFl5LKD3ZBB+JMEYVLwjqzXQe+RDrJE=; b=Bm5qB6h+M9HYhT36G+PXUBgmznB6ALLVLKWFcoOvdcOdOrT0Sb3HbzbF5fgq3z5wkR bVBHAE+msD7arvX+gUZ/LUr8Zrkb6bwbct7Jlp1SUPrY0Ah9HcO6FnosiC877qUfvmZC uCO2QJT+ieoHSgb/T4Tyn0b8gAoIYGq2Snyng= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=subject:from:reply-to:to:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; b=ghIVOqS9HgggTaCih5o4FgB9GhkBy0jx10sijM4KIuiOi6io0JI4vrEi0xI/eDXRNe FL3oJWVMeL0oLJOG5dgBYLM15gjDT+bjFYUXh+L67zW0zX7AkRBybcNkwpKQ87OJkEWQ 8gOLaL1N6qMuB/le7zE2cXNw8h+jityUk/O6k= Received: by 10.102.228.10 with SMTP id a10mr2455441muh.26.1233110846817; Tue, 27 Jan 2009 18:47:26 -0800 (PST) Received: from ?10.30.1.130? (vpn-or.studi-planet.com [78.47.172.52]) by mx.google.com with ESMTPS id u26sm26664701mug.41.2009.01.27.18.47.25 (version=SSLv3 cipher=RC4-MD5); Tue, 27 Jan 2009 18:47:26 -0800 (PST) From: Mister Olli To: freebsd-current@freebsd.org Content-Type: text/plain Date: Wed, 28 Jan 2009 02:10:02 +0100 Message-Id: <1233105002.26641.2.camel@phoenix.blechhirn.net> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 Content-Transfer-Encoding: 7bit Subject: Page fault in CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mister.olli@googlemail.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, 28 Jan 2009 02:47:28 -0000 Hi, The following pagefault just happend on my PV CURRENT domU under Xen 3.3 ================================================================== template_8-CURRENT# pwd /usr Kernel page fault with the following non-sleepable locks held:org/base/head src/ exclusive sleep mutex pmap (pmap) r = 0 (0xc1706ee8) locked @ /usr/src/sys/i386/xen/pmap.c:3711 exclusive sleep mutex vm object (standard object) r = 0 (0xc19c98b8) locked @ /usr/src/sys/vm/vm_pageout.c:771 exclusive sleep mutex vm page queue mutex (vm page queue mutex) r = 0 (0xc052ae84) locked @ /usr/src/sys/vm/vm_pageout.c:447 KDB: stack backtrace: X_db_sym_numargs(c0342b8f,cbe849ac,c010c5f5,c0361da2,1bf,...) at X_db_sym_numargs+0x146 kdb_backtrace(c0361da2,1bf,ffffffff,c04f2c2c,cbe849e4,...) at kdb_backtrace+0x29 witness_display_spinlock(c0344dec,cbe849f8,4,1,0,...) at witness_display_spinlock+0x75 witness_warn(5,0,c036c048,c17a7d80,c,...) at witness_warn+0x1fd trap(cbe84a80) at trap+0x10e alltraps(c0bb2d48,4,c0361da2,1a8,c0361da2,...) at alltraps+0x1b vm_pageout_flush(cbe84ba4,7,0,0,ec1,...) at vm_pageout_flush+0xe5 vm_pageout_flush(c0bb3c78,0,c0361da2,303,32,...) at vm_pageout_flush +0x621 vm_pageout_flush(0,cbe84d38,c033ba96,32d,c1701a90,...) at vm_pageout_flush+0x13ce fork_exit(c02d59b0,0,cbe84d38) at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xcbe84d70, ebp = 0 --- Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xc0863fc8 fault code = supervisor write, protection violation instruction pointer = 0x21:0xc03113df stack pointer = 0x29:0xcbe84ac0 frame pointer = 0x29:0xcbe84ae8 code segment = base 0x0, limit 0xf67ff, type 0x1b = DPL 1, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 6 (pagedaemon) [thread pid 6 tid 100024 ] Stopped at pmap_remove_write+0xbf: lock cmpxchgl %edi,0(%ecx) db> =============================================================== Since I was unable to enter anything at the debugger command line I'm unable to provide a backtrace. sorry. -- Olli From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 04:05:26 2009 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 1F2E2106564A for ; Wed, 28 Jan 2009 04:05:26 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id 690A68FC17 for ; Wed, 28 Jan 2009 04:05:25 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (adsl21-232.kln.forthnet.gr [77.49.148.232]) (authenticated bits=128) by igloo.linux.gr (8.14.3/8.14.3/Debian-5) with ESMTP id n0S45HNZ021179 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 28 Jan 2009 06:05:23 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.3/8.14.3) with ESMTP id n0S45Hk6014466; Wed, 28 Jan 2009 06:05:17 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.14.3/8.14.3/Submit) id n0S45G41014465; Wed, 28 Jan 2009 06:05:16 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) From: Giorgos Keramidas To: "Bjoern A. Zeeb" References: <20090122225404.U45399@maildrop.int.zabbadoz.net> <20090126093817.H45399@maildrop.int.zabbadoz.net> Date: Wed, 28 Jan 2009 06:05:16 +0200 In-Reply-To: <20090126093817.H45399@maildrop.int.zabbadoz.net> (Bjoern A. Zeeb's message of "Mon, 26 Jan 2009 09:39:23 +0000 (UTC)") Message-ID: <87ocxsm5xf.fsf@kobe.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-MailScanner-ID: n0S45HNZ021179 X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.866, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.53, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: FreeBSD current mailing list , FreeBSD net mailing list Subject: Re: Need testers for a network cleanup patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2009 04:05:26 -0000 On Mon, 26 Jan 2009 09:39:23 +0000 (UTC), "Bjoern A. Zeeb" wrote: > On Thu, 22 Jan 2009, Bjoern A. Zeeb wrote: >> Before I am going to remove the initializations I made the two >> rip{,6}_output functions calling panic(). >> >> I have a patch for HEAD here: >> http://people.freebsd.org/~bz/20090122-03-pr_output.diff >> >> and one for 7-STABLE here (compiled but not booted): >> http://people.freebsd.org/~bz/20090122-04-pr_output-7STABLE.diff > > In case you tested, please let me know. Tested for around 4 days now. No panics :-) From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 04:59:45 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 566A4106564A for ; Wed, 28 Jan 2009 04:59:45 +0000 (UTC) (envelope-from ptice@aldridge.com) Received: from starbase.aldridge.com (starbase.aldridge.com [205.196.186.12]) by mx1.freebsd.org (Postfix) with ESMTP id 1650F8FC1A for ; Wed, 28 Jan 2009 04:59:44 +0000 (UTC) (envelope-from ptice@aldridge.com) Received: from corporate.aldridge.com (corporate.aldridge.com [216.139.69.10]) by starbase.aldridge.com (8.14.3/8.14.2) with ESMTP id n0S4wjIV056906 for ; Tue, 27 Jan 2009 22:58:45 -0600 (CST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 27 Jan 2009 22:54:31 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Help me select hardware....Some real world data that might help Thread-Index: AcmAuy/zQFRoSpvKQRWeQ1v6EbNkwAAQtlZE References: <01N4NEOEB7LY00EQWX@tmk.com> <200901271142.41296.fjwcash@gmail.com> From: "Paul Tice" To: "Freddie Cash" Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: RE: Help me select hardware....Some real world data that might help X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 04:59:45 -0000 I just bumped up the kmem, arc.max, enabled zil and reenabled mdcomp. = Prefetch is disabled. Less than 1 minute into a backup run of only 4 machines, I've got a = fresh ZFS wedgie. Ouch. As I understand it, the ZIL is not as much of an integrity boost as a = speed boost, especially since we already have checksum-per-block. I did = see spikes of up to 140MB/s on the ZFS pool in the 2 minutes before ZFS = wedged. I think of ZIL as the equivalent of journaling for more traditional = filesystems. I can certainly see where it would help with integrity for = certain cases, but a good UPS seems to offer many of the same benefits. = ;> =20 (As always, I'm ready to be better informed)=20 =20 I'm intrigued by the ssh/rsync double process throughput bump, but it = does require ssh as well as rsync. Alas, many of the boxes being backed up belong to the dark side, and = many of them are only managed by us.=20 For some reason,many 'dark side' owners trust rsync more than ssh, to = the point of disallowing ssh installation. Realistically, we could do a = lot more with SSH/rsync, since we can start up a Volume Shadow copy, = back it up, then remove the Shadow copy.=20 =20 Good to know there is a pretty high limit to kmem now.=20 =20 I'm not 100% sure about the gstat, I did no slicing/labeling on the = disks, they are purely /dev/adX used by ZFS, would GEOM level even see = this? zpool iostat -v will give the overall plus per device stats, I'm = curious to see what difference there would be between gstat and zpool = iostat -v, if any. =20 I suspected you could upsize raidz pools one disk at a time, I do wonder = how the inner/outer track speed differences would affect throughput over = a one-by-one disk full array replacement. And yes, I might wonder too = much about corner cases. ;> =20 I assume that under 7.x, you could have your cron script take care of = automating the zpool replace. Built in hot sparing is much nicer, but warm spares would be the best = (IMHO), a powered down drive isn't spinning towards failure. Of course, = this is probably too much to ask of any multi-platform FS, since the = method of spinning a drive up (and access required to do so) varies = widely. Sounds like another cron script possibility. :)=20 =20 If I can get the time on the box, I may try graphing 3 disk -> 17 disks = with 2nd axis throughput and 3rd axis CPU usage.Drivewise, 8+1 is = easily understandable as a theoretical best 8 bit+1 parity number of = drives. Assuming you transfer multiple 8 bit bytes per cycle, and your = controller/system/busses can keep up, 16+1 would in theory increase = throughput, both from more bits read at a time, and from 1/2 the parity = calculations per double-byte written to disk. Of course, this assumes = the 'splitting' and parity generation code can optimize for mutiple 8 = bit byte transfers.=20 =20 Anyway, yet another overly long ramble must come to a close. =20 Thanks Paul =20 =20 =20 ________________________________ From: owner-freebsd-current@freebsd.org on behalf of Freddie Cash Sent: Tue 1/27/2009 1:42 PM To: freebsd-current@freebsd.org Subject: Re: Help me select hardware....Some real world data that might = help On January 27, 2009 10:41 am Paul Tice wrote: > Excuse my rambling, perhaps something in this mess will be useful. > > I'm currently using 8 cores (2x Xeon E5405), 16G FB-DIMM, and 8 x = 750GB > drives on a backup system (I plan to add the other in the chassis one = by > one, testing the speed along the way) 8-current AMD64, ZFS, Marvell > 88sx6081 PCI-X card (8 port SATA) + LSI1068E (8 port SAS/SATA) for the > main Array, and the Intel onboard SATA for boot drive(s). Data is = sucked > down through 3 gigabit ports, with another available but not yet > activated. Array drives all live on the LSI right now. Drives are = ST3750640AS K>. > > ZFS is stable _IF_ you disable the prefetch and ZIL, otherwise the > classic ZFS wedge rears it's ugly head. I haven't had a chance to test > just one yet, but I'd guess it's the prefetch that's the quick killer. You probably don't want to disable the ZIL. That's the journal, and an important part of the data integrity setup for ZFS. Prefetch has been shown to cause issues on a lot of systems, and can be = a bottleneck depending on the workload. But the ZIL should be enabled. > I've seen references to 8-Current having a kernel memory limit of 8G > (compared to 2G for pre 8 from what I understand so far) and ZFS ARC FreeBSD 8.x kmem_max has been bumped to 512 GB. > Using rsync over several machines with this setup, I'm getting a = little > over 1GB/min to the disks. 'zpool iostat 60' is a wonderful tool. gstat is even nicer, as it shows you the throughput to the individual drives, instead of the aggregate that zpool shows. This works at the = GEOM level. Quite nice to see how the I/O is balanced (or not) across the = drives in the raidz datasets, and the pool as a whole. > CPU usage during all this is suprisingly low. rsync is running with = -z, If you are doing rsync over SSH, don't use -z as part of the rsync = command.=20 Instead, use -C with ssh. That way, rsync is done in one process, and = the compression is done by ssh in another process, and it will use two CPUs/cores instead of just one. You'll get better throughput that way, = as the rsync process doesn't have to do the compression and reading/writing = in the same process. We got about a 25% boost in throughput by moving the compress out of the rsync, and CPU usage balanced across CPUs instead of just hogging one. > Random ZFS thoughts: > You cannot shrink/grow a raidz or raidz2. You can't add devices to a raidz/raidz2 dataset. But you can replace = the drives with larger ones, do a resilver, and the extra space will become available. Just pull the small drive, insert the large drive, and do a = "zfs replace ". And you can add extra raidz/raidz2 datasets to a pool, and ZFS will = stripe the data across the raidz datasets. Basically, the pool becomes a RAID = 5+0 or RAID 6+0, instead of just a RAID 5/RAID 6. If you have lots of drives, the recommendations from the Solaris folks = is to use a bunch of raidz datasets comprised of <=3D9 disks each, instead of = one giant raidz dataset across all the drives. ie: zfs create pool raidz2 da0 da1 da2 da3 da4 da5 zfs add pool raidz2 da6 da7 da8 da9 da10 da11 zfs add pool raidz2 da12 da13 da14 da15 da16 da17 Will give you a single pool comprised of three raidz2 datasets, with = data being striped across the three datasets. And you can add raidz datasets to the pool as needed. > You can grow a stripe array, > I'm don't know if you can shrink it successfully. You cannot promote a > stripe array to raidz/z2, nor demote in the other direction. You can = have > hot spares, haven't seen a provision for warm/cold spares. ZFS in FreeBSD 7.x doesn't support hot spares, in that a faulted drive = won't start a rebuild using a spare drive. You have to manually "zfs replace" = the drive using the spare. ZFS in FreeBSD 8.x does support auto-rebuild using spare drives (hot = spare). > /etc/default/rc.conf already has cron ZFS status/scrub checks, but not > enabled. periodic(8) does ZFS checks as part of the daily run. See /etc/defaults/periodic.conf. However, you can whip up a very simple shell script that does the same, = and run it via cron at whatever interval you want. We use the following, = that runs every 15 mins: #!/bin/sh status=3D$( zpool status -x ) if [ "${status}" !=3D "all pools are healthy" ]; then echo "Problems with ZFS: ${status}" | mail -s "ZFS Issues on " = \ fi exit 0 -- Freddie fjwcash@gmail.com _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 06:17:16 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B34C106566B for ; Wed, 28 Jan 2009 06:17:16 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175]) by mx1.freebsd.org (Postfix) with ESMTP id F17788FC19 for ; Wed, 28 Jan 2009 06:17:15 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so7266849wfg.7 for ; Tue, 27 Jan 2009 22:17:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=l90MLmUTWj4opWd6FYeFuPmAg7+bltdVnsQzn5dFSus=; b=IkpKO1FpjWzpmaR3+P1Q4NLhRPicSvq2sAt2VZNgUaptukLJBrIpWUtX/BtEgUhp4J qWMphVPxwLsmDJ7mBbOXxqkG3MX65JyBzydG+dYtp9QlFZP/Yrz+5CsIda1cQNLWX99M DDiH79jqXZIw9eVidXCjmj5dhDOn1aCCOhBpY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=S6knDHsFFWJ6r39L9BxFmweFSo3DxYbQYSjKioqdReoqMk7kEs1rk1F1gRT7QdK1Wx 7QboZGmmOPLfbFdzidegzfd+9ooazN+5EdS6JQb452jYCWs2GgV80OU2ZCl/vFDItnZb 3bF55p7xbaOrSffoO/xiF8LT6Ip95u4G60/AQ= MIME-Version: 1.0 Received: by 10.142.43.7 with SMTP id q7mr445072wfq.316.1233123435684; Tue, 27 Jan 2009 22:17:15 -0800 (PST) In-Reply-To: References: <01N4NEOEB7LY00EQWX@tmk.com> <200901271142.41296.fjwcash@gmail.com> Date: Tue, 27 Jan 2009 22:17:15 -0800 Message-ID: From: Freddie Cash To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: Help me select hardware....Some real world data that might help X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 06:17:16 -0000 On Tue, Jan 27, 2009 at 8:54 PM, Paul Tice wrote: > I just bumped up the kmem, arc.max, enabled zil and reenabled mdcomp. > Prefetch is disabled. > Less than 1 minute into a backup run of only 4 machines, I've got a fresh > ZFS wedgie. Ouch. Others more knowledgeable than I will have to jump in here, but getting the kmem_max and arc_max settings set right for each system is a bit of an art unto itself. It took almost 6 weeks to get the settings we are currently using, which keeps the system stable while running backups for 83 servers via rsync+ssh. Others find smaller arc_max settings work better, others find smaller kmem_max work better. Each system is different. > I'm intrigued by the ssh/rsync double process throughput bump, but it does > require ssh as well as rsync. Yes, if you aren't using ssh as the transport, then adding -z to rsync can be benfecial. :) > I'm not 100% sure about the gstat, I did no slicing/labeling on the disks, > they are purely /dev/adX used by ZFS, would GEOM level even see this? Yes. All disk access goes through GEOM. You can't hit the device nodes without going through GEOM. It's quite interesting watching the output of gstat. > I suspected you could upsize raidz pools one disk at a time, I do wonder how > the inner/outer track speed differences would affect throughput over a > one-by-one disk full array replacement. And yes, I might wonder too much > about corner cases. ;> We haven't got that far yet. :) We've only filled 6 TB of the 9, so won't be needing to move to larger drives for several more months. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 09:29:50 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AFCEB1065675 for ; Wed, 28 Jan 2009 09:29:50 +0000 (UTC) (envelope-from nick@van-laarhoven.org) Received: from hpsmtp-eml19.kpnxchange.com (hpsmtp-eml19.KPNXCHANGE.COM [213.75.38.84]) by mx1.freebsd.org (Postfix) with ESMTP id 431668FC1F for ; Wed, 28 Jan 2009 09:29:50 +0000 (UTC) (envelope-from nick@van-laarhoven.org) Received: from cpsmtp-eml109.kpnxchange.com ([10.94.168.109]) by hpsmtp-eml19.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 28 Jan 2009 10:29:48 +0100 Received: from uitsmijter.van-laarhoven.org ([81.207.207.222]) by cpsmtp-eml109.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 28 Jan 2009 10:29:48 +0100 Received: from van-laarhoven.org (hind.van-laarhoven.org [10.66.0.146]) (authenticated bits=0) by uitsmijter.van-laarhoven.org (8.14.3/8.14.3) with ESMTP id n0S9Vqbv080697 for ; Wed, 28 Jan 2009 10:31:52 +0100 (CET) (envelope-from nick@van-laarhoven.org) Received: (nullmailer pid 9034 invoked by uid 1001); Wed, 28 Jan 2009 09:29:41 -0000 To: FreeBSD CURRENT Mailing List Content-Disposition: inline From: Nick Hibma Date: Wed, 28 Jan 2009 10:29:40 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200901281029.41232.nick@van-laarhoven.org> X-Spam-Status: No, score=-2.6 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on uitsmijter.van-laarhoven.org X-OriginalArrivalTime: 28 Jan 2009 09:29:48.0954 (UTC) FILETIME=[F702DFA0:01C9812A] Subject: build in /sys/modules broken / other way of building 1 specific module X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 09:29:51 -0000 Folks, I am not quite sure as to what its status is (and dfr politely explained that I was being wereold-fashioned), but the build in /sys/modules is broken at the moment. Doing cd /sys/modules sudo make does not work due to missing opt_hwpmc_hooks.h files required by the build of genassym. The patch below fixes this (creating empty opt_hwpmc_hooks.h files, any objections?), but I was wondering whether there is another way for building 1 specific module instead of having to wait for 100+ modules to build after typing in cd /sys/i386/compile/HILDE/ make -DNO_MODULES_OBJ modules Nick Index: dtrace/dtrace/Makefile =================================================================== --- dtrace/dtrace/Makefile (revision 187780) +++ dtrace/dtrace/Makefile (working copy) @@ -23,7 +23,7 @@ SRCS+= assym.s # These are needed for assym.s -SRCS+= opt_compat.h opt_kstack_pages.h opt_nfs.h +SRCS+= opt_compat.h opt_kstack_pages.h opt_nfs.h opt_hwpmc_hooks.h .if ${MACHINE_ARCH} == "i386" SRCS+= opt_apic.h Index: acpi/acpi/Makefile =================================================================== --- acpi/acpi/Makefile (revision 187780) +++ acpi/acpi/Makefile (working copy) @@ -58,7 +58,7 @@ # XXX ACPI should not depend on the following headers but this is currently # needed for the build of assym.s. # This obviously needs a better and more structural fix. -SRCS+= opt_kstack_pages.h opt_nfs.h opt_apic.h opt_compat.h +SRCS+= opt_kstack_pages.h opt_nfs.h opt_apic.h opt_compat.h opt_hwpmc_hooks.h # Debugging support DBSRC= dbcmds.c dbdisply.c dbexec.c dbfileio.c dbhistry.c dbinput.c dbstats.c Index: linux/Makefile =================================================================== --- linux/Makefile (revision 187780) +++ linux/Makefile (working copy) @@ -17,7 +17,7 @@ device_if.h bus_if.h assym.s # XXX: for assym.s -SRCS+= opt_kstack_pages.h opt_nfs.h opt_apic.h opt_compat.h +SRCS+= opt_kstack_pages.h opt_nfs.h opt_apic.h opt_compat.h opt_hwpmc_hooks.h OBJS= linux${SFX}_locore.o linux${SFX}_support.o From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 11:39:30 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0DE2106564A for ; Wed, 28 Jan 2009 11:39:30 +0000 (UTC) (envelope-from channa.kad@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.230]) by mx1.freebsd.org (Postfix) with ESMTP id BA27F8FC08 for ; Wed, 28 Jan 2009 11:39:30 +0000 (UTC) (envelope-from channa.kad@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so7022065rvf.43 for ; Wed, 28 Jan 2009 03:39:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=/xliuBc1YalWbBKIzMlb3grCP13kKVpPSAQQHWvWOzs=; b=XhJUPgLrdtj1t11fqm4RHVuv7FoAT5dU8F5v7P9iHynVo6hREQuFRiONtIZc5kQ3eX j+JicQH79KGh5trtJFQ9ZubQi9U1YGMvItTAYr5QdEXIfB5Cq5elC/OwxLlak4QHYCrv ZDxjNzdUKMCqldTn6YinEMmMIvOHio2NMf0wA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=b/v4DOxTluwgSnShF1KPHOUSzolRpyC6jX10a3LvbEpk8IAcbzpe6WQl8dE5vRAtyH I/cY0AqWZkNbbIKFMCQsIoo1t2BHKlJwLRVK6+ARuk0FRml9To8pv7+gzJAuWtRBsk45 1U4jACdDRNCWnCDDfULEBnTxrehrzn+0Y9ZHY= MIME-Version: 1.0 Received: by 10.141.197.21 with SMTP id z21mr860074rvp.9.1233142770272; Wed, 28 Jan 2009 03:39:30 -0800 (PST) Date: Wed, 28 Jan 2009 17:09:30 +0530 Message-ID: <515c64960901280339m17fa9309v2e1bc3f55454ab@mail.gmail.com> From: Channa To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Jemalloc SEGV for 1MB chunk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 11:39:31 -0000 Hi All, I am using jemalloc.c source from FreeBSD-current source. When i allocate 1MB of memory using malloc() and use it as the below test shows #include #include #include int main() { int i; char *buf; size_t size = 1048576 ; buf = malloc(size); for (i = 0; i < 1048576; i++) buf[i] = 'a'; printf("The length of buff is : %d\n",strlen(buf)); free(buf); return 0; } When i try to call strlen(buf) SEGV is recived. This behaviour is seen when only for 1MB chunk if i allocate memory lesser than 1MB no issues noticed. Could anyone see similar problem? Is the above test wrong? Or some issue with huge memory allocation in jemalloc? Your response will be very helpful. Thanks & Regards, Channa From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 11:46:12 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 011181065674 for ; Wed, 28 Jan 2009 11:46:12 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from smtp-1.dlr.de (smtp-1.dlr.de [195.37.61.185]) by mx1.freebsd.org (Postfix) with ESMTP id 8BD418FC12 for ; Wed, 28 Jan 2009 11:46:11 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from beagle.kn.op.dlr.de ([129.247.178.136]) by smtp-1.dlr.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Wed, 28 Jan 2009 12:46:08 +0100 Date: Wed, 28 Jan 2009 12:46:10 +0100 (CET) From: Harti Brandt X-X-Sender: brandt_h@beagle.kn.op.dlr.de To: Channa In-Reply-To: <515c64960901280339m17fa9309v2e1bc3f55454ab@mail.gmail.com> Message-ID: <20090128124535.M26828@beagle.kn.op.dlr.de> References: <515c64960901280339m17fa9309v2e1bc3f55454ab@mail.gmail.com> X-OpenPGP-Key: harti@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 28 Jan 2009 11:46:08.0964 (UTC) FILETIME=[02AD5840:01C9813E] Cc: freebsd-current@freebsd.org Subject: Re: Jemalloc SEGV for 1MB chunk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Harti Brandt List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2009 11:46:12 -0000 On Wed, 28 Jan 2009, Channa wrote: C>Hi All, C>I am using jemalloc.c source from FreeBSD-current source. C>When i allocate 1MB of memory using malloc() and use it as the below C>test shows C> C>#include C>#include C>#include C> C>int main() C>{ C> int i; C> char *buf; C> size_t size = 1048576 ; C> C> buf = malloc(size); C> for (i = 0; i < 1048576; i++) C> buf[i] = 'a'; C> printf("The length of buff is : %d\n",strlen(buf)); C> free(buf); C> return 0; C>} C> C>When i try to call strlen(buf) SEGV is recived. Would be better to terminate the string with a '\0' so that it is really a string. harti C> C>This behaviour is seen when only for 1MB chunk if i allocate C>memory lesser than 1MB no issues noticed. C> C>Could anyone see similar problem? C>Is the above test wrong? C>Or some issue with huge memory allocation in jemalloc? C> C>Your response will be very helpful. C> C>Thanks & Regards, C>Channa C>_______________________________________________ C>freebsd-current@freebsd.org mailing list C>http://lists.freebsd.org/mailman/listinfo/freebsd-current C>To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" C> C> From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 11:46:34 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87F8B106564A for ; Wed, 28 Jan 2009 11:46:34 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id CBEFA8FC17 for ; Wed, 28 Jan 2009 11:46:33 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: (qmail invoked by alias); 28 Jan 2009 11:46:32 -0000 Received: from p54A3E68D.dip.t-dialin.net (EHLO tron.homeunix.org) [84.163.230.141] by mail.gmx.net (mp059) with SMTP; 28 Jan 2009 12:46:32 +0100 X-Authenticated: #1673122 X-Provags-ID: V01U2FsdGVkX18IGSZGV/wIzctebfR4Jm/5vHcqeqRkthp9+Y/tpL BmYHgSZbP4N450 Message-ID: <49804597.6040303@gmx.de> Date: Wed, 28 Jan 2009 12:46:31 +0100 From: Christoph Mallon User-Agent: Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Channa References: <515c64960901280339m17fa9309v2e1bc3f55454ab@mail.gmail.com> In-Reply-To: <515c64960901280339m17fa9309v2e1bc3f55454ab@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.53 Cc: freebsd-current@freebsd.org Subject: Re: Jemalloc SEGV for 1MB chunk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 11:46:34 -0000 Channa schrieb: > Hi All, > I am using jemalloc.c source from FreeBSD-current source. > When i allocate 1MB of memory using malloc() and use it as the below > test shows > > #include > #include > #include > > int main() > { > int i; > char *buf; > size_t size = 1048576 ; > > buf = malloc(size); > for (i = 0; i < 1048576; i++) > buf[i] = 'a'; > printf("The length of buff is : %d\n",strlen(buf)); > free(buf); > return 0; > } > > When i try to call strlen(buf) SEGV is recived. > > This behaviour is seen when only for 1MB chunk if i allocate > memory lesser than 1MB no issues noticed. > > Could anyone see similar problem? > Is the above test wrong? > Or some issue with huge memory allocation in jemalloc? > > Your response will be very helpful. > > Thanks & Regards, > Channa You did not NUL-terminate ('\0') the string. From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 11:47:47 2009 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 A54531065687 for ; Wed, 28 Jan 2009 11:47:47 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id E8DD68FC20 for ; Wed, 28 Jan 2009 11:47:46 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: (qmail invoked by alias); 28 Jan 2009 11:47:45 -0000 Received: from p54A3E68D.dip.t-dialin.net (EHLO tron.homeunix.org) [84.163.230.141] by mail.gmx.net (mp005) with SMTP; 28 Jan 2009 12:47:45 +0100 X-Authenticated: #1673122 X-Provags-ID: V01U2FsdGVkX1/jkOde9MvjcPdHrWssBVFAoLtOza4UQQOdimvLI6 8HAmFnc0OqSijR Message-ID: <498045E0.3050405@gmx.de> Date: Wed, 28 Jan 2009 12:47:44 +0100 From: Christoph Mallon User-Agent: Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Luigi Rizzo References: <20090127132102.GA21574@onelab2.iet.unipi.it> <497F91C3.7040502@gmx.de> <20090127232103.GA40501@onelab2.iet.unipi.it> In-Reply-To: <20090127232103.GA40501@onelab2.iet.unipi.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.59 Cc: current@freebsd.org Subject: Re: duplicate typedefs and system headers ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 11:47:48 -0000 Luigi Rizzo schrieb: > On Tue, Jan 27, 2009 at 11:59:15PM +0100, Christoph Mallon wrote: >> Luigi Rizzo schrieb: >>> In a recent commit tp sbin/ipfw, in an attempt to avoid >>> a large set of header deependencies, i put a 'forward typedef' >>> declaration in a common header, duplicating something that is in a >>> system header: >>> >>> ipfw2.h: typedef struct _ipfw_insn ipfw_insn; >>> >>> netiinet/ip_fw2.h >>> typedef struct _ipfw_insn { /* template for instructions */ >>> ... >>> } ipfw_insn; >> This just begs to break, if somebody decides to change the name of the >> underlying type of the typedef. > > Fortunately this is almost impossible -- the system header is > basically frozend and if I could change it I would remove the > typedef in the first place. > > I am more worried of compatibility with different compiler. > > A workaround that seems to work is putting forward declarations > just for "struct _ipfw_insn" and use it (instead of the typedef > name) in the place that does not include netiinet/ip_fw2.h > > Would this be better/more compliant with standards -- i.e., > is the following code correct ? gcc seems to have no objections. > > struct foo; > int a(struct foo *); > typedef struct foo bar; > int a(bar *x) { ... } What is the problem with just including the correct header? This would be The Right Thing(tm). Everything else is just an ugly hack. From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 12:01:45 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8AAD410656D5 for ; Wed, 28 Jan 2009 12:01:45 +0000 (UTC) (envelope-from channa.kad@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.237]) by mx1.freebsd.org (Postfix) with ESMTP id DA4F28FC17 for ; Wed, 28 Jan 2009 12:01:43 +0000 (UTC) (envelope-from channa.kad@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so7029917rvf.43 for ; Wed, 28 Jan 2009 04:01:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=KVjJmHi6BpyaetgWd46wf0jgsCum7drm4z9aC2Eby1o=; b=Jd48jcPIhkJJ3Isz0ROgLr5LtzOGiSUBJxVbzImmM2Gfz2VUwhlcqu8nc6ZEebO4C4 4lBO3HnEc1VivIyH3dt2B9F3CRuinr9P/b5ourT7mkpZjTVt56lo3LNBbhcHpJp/HuyR zktG2N0Gw7mS5DdKd3qtdCKscCc5u5XbmsVv8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=EFI4j4YaIFOu+dtsCJjXBRc35NfYXhBV6dY6ST4M+g35aT3Dud8cJvHd3R4ZGFRsBb oOvRyhi+RGjF2QwNvzQ2hFHpN+R99clnoCHU1dKaeMX+vMhr5rnmP8NcHcjMHFA+KKos ozbaQfMlwhcWW6m0yMy4m1jziDO1tEcrptWsU= MIME-Version: 1.0 Received: by 10.141.96.10 with SMTP id y10mr5143471rvl.249.1233144103063; Wed, 28 Jan 2009 04:01:43 -0800 (PST) In-Reply-To: <49804597.6040303@gmx.de> References: <515c64960901280339m17fa9309v2e1bc3f55454ab@mail.gmail.com> <49804597.6040303@gmx.de> Date: Wed, 28 Jan 2009 17:31:43 +0530 Message-ID: <515c64960901280401w1e1d08bfx29adc124bc749c4a@mail.gmail.com> From: Channa To: Christoph Mallon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Jemalloc SEGV for 1MB chunk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 12:01:50 -0000 Hi, Thanks for your reply. You mean to say i should modify the test as below: #include #include #include int main() { int i; char *buf; size_t size = 1048576 ; buf = malloc(size); for (i = 0; i <= 1048575; i++) buf[i] = 'a'; buf[size]='\0'; printf("The length of buff is : %d\n",strlen(buf)); free(buf); return 0; } I NULL terminated the string buf[size] = '\0' <== The last character is NULL But still i get a SEGV at strlen. Could you please tell me if my changes above are correct? Regards, Channa On 28/01/2009, Christoph Mallon wrote: > Channa schrieb: > > > > Hi All, > > I am using jemalloc.c source from FreeBSD-current source. > > When i allocate 1MB of memory using malloc() and use it as the below > > test shows > > > > #include > > #include > > #include > > > > int main() > > { > > int i; > > char *buf; > > size_t size = 1048576 ; > > > > buf = malloc(size); > > for (i = 0; i < 1048576; i++) > > buf[i] = 'a'; > > printf("The length of buff is : %d\n",strlen(buf)); > > free(buf); > > return 0; > > } > > > > When i try to call strlen(buf) SEGV is recived. > > > > This behaviour is seen when only for 1MB chunk if i allocate > > memory lesser than 1MB no issues noticed. > > > > Could anyone see similar problem? > > Is the above test wrong? > > Or some issue with huge memory allocation in jemalloc? > > > > Your response will be very helpful. > > > > Thanks & Regards, > > Channa > > > > You did not NUL-terminate ('\0') the string. > From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 12:02:51 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40E4B106574C for ; Wed, 28 Jan 2009 12:02:51 +0000 (UTC) (envelope-from channa.kad@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.225]) by mx1.freebsd.org (Postfix) with ESMTP id 00AC88FC32 for ; Wed, 28 Jan 2009 12:02:27 +0000 (UTC) (envelope-from channa.kad@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so7030222rvf.43 for ; Wed, 28 Jan 2009 04:02:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=gcZs0KOKqiRvN4sMiqBC0ghIyYaTCSYJdJppDJH3Ams=; b=WzozErHaGCq+hdvBhK9N4+ClPuv7Ho9dRMKm+KCdHNzGsYlcVVwYDttKct6jR3AG4T fT2oofiyQh4327usUif3kGoDOaUVtpEHCirJz6clV5WpnXiOI4yulUPdxg2Xsv3q421m 1ygxovtYq2/FxpUjrHBqGnfXgsADxOPYRI1go= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=J5Z2wZiDBqrDPNXDOZaMYvpRFQ/XTRsHMKajyv5rlumCJRGXjYIjIofT3VVal3iQEI C6NjxEUImvbraAYrJadeOZ6FXC+VPl04xmElGXrqBPPLWMVH4CUqujk0rIJC8XKg6kn5 FnvZUXGFfsVlNdbR+OmV9LGPdqoNuG8QXOorw= MIME-Version: 1.0 Received: by 10.141.197.21 with SMTP id z21mr1583237rvp.107.1233144147545; Wed, 28 Jan 2009 04:02:27 -0800 (PST) In-Reply-To: <20090128124535.M26828@beagle.kn.op.dlr.de> References: <515c64960901280339m17fa9309v2e1bc3f55454ab@mail.gmail.com> <20090128124535.M26828@beagle.kn.op.dlr.de> Date: Wed, 28 Jan 2009 17:32:27 +0530 Message-ID: <515c64960901280402s529d243fg8b6e0c58dc90b64@mail.gmail.com> From: Channa To: Harti Brandt Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Jemalloc SEGV for 1MB chunk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 12:03:13 -0000 Hi, Thanks for your reply. You mean to say i should modify the test as below: #include #include #include int main() { int i; char *buf; size_t size = 1048576 ; buf = malloc(size); for (i = 0; i <= 1048575; i++) buf[i] = 'a'; buf[size]='\0'; printf("The length of buff is : %d\n",strlen(buf)); free(buf); return 0; } I NULL terminated the string buf[size] = '\0' <== The last character is NULL But still i get a SEGV at strlen. Could you please tell me if my changes above are correct? Regards, Channa On 28/01/2009, Harti Brandt wrote: > On Wed, 28 Jan 2009, Channa wrote: > > C>Hi All, > C>I am using jemalloc.c source from FreeBSD-current source. > C>When i allocate 1MB of memory using malloc() and use it as the below > C>test shows > C> > C>#include > C>#include > C>#include > C> > C>int main() > C>{ > C> int i; > C> char *buf; > C> size_t size = 1048576 ; > C> > C> buf = malloc(size); > C> for (i = 0; i < 1048576; i++) > C> buf[i] = 'a'; > C> printf("The length of buff is : %d\n",strlen(buf)); > C> free(buf); > C> return 0; > C>} > C> > C>When i try to call strlen(buf) SEGV is recived. > > Would be better to terminate the string with a '\0' so that it is really a > string. > > harti > > C> > C>This behaviour is seen when only for 1MB chunk if i allocate > C>memory lesser than 1MB no issues noticed. > C> > C>Could anyone see similar problem? > C>Is the above test wrong? > C>Or some issue with huge memory allocation in jemalloc? > C> > C>Your response will be very helpful. > C> > C>Thanks & Regards, > C>Channa > C>_______________________________________________ > C>freebsd-current@freebsd.org mailing list > C>http://lists.freebsd.org/mailman/listinfo/freebsd-current > C>To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > C> > C> > From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 12:10:08 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D321D1065D0F for ; Wed, 28 Jan 2009 12:10:08 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 126438FC24 for ; Wed, 28 Jan 2009 12:10:07 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: (qmail invoked by alias); 28 Jan 2009 12:10:06 -0000 Received: from p54A3E68D.dip.t-dialin.net (EHLO tron.homeunix.org) [84.163.230.141] by mail.gmx.net (mp008) with SMTP; 28 Jan 2009 13:10:06 +0100 X-Authenticated: #1673122 X-Provags-ID: V01U2FsdGVkX1+Jm34bFUyJg+6MtG9BlZd8RdqdeoN2OvAWM1/Sn5 tEW0V0jRpXPvYX Message-ID: <49804B1E.7080603@gmx.de> Date: Wed, 28 Jan 2009 13:10:06 +0100 From: Christoph Mallon User-Agent: Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Channa References: <515c64960901280339m17fa9309v2e1bc3f55454ab@mail.gmail.com> <49804597.6040303@gmx.de> <515c64960901280401w1e1d08bfx29adc124bc749c4a@mail.gmail.com> In-Reply-To: <515c64960901280401w1e1d08bfx29adc124bc749c4a@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.6 Cc: freebsd-current@freebsd.org Subject: Re: Jemalloc SEGV for 1MB chunk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 12:10:21 -0000 Channa schrieb: > Hi, > Thanks for your reply. > You mean to say i should modify the test as below: > > #include > #include > #include > > > int main() > { > int i; > char *buf; > size_t size = 1048576 ; > > buf = malloc(size); > for (i = 0; i <= 1048575; i++) > buf[i] = 'a'; > buf[size]='\0'; > printf("The length of buff is : %d\n",strlen(buf)); > free(buf); > return 0; > } > > I NULL terminated the string > buf[size] = '\0' <== The last character is NULL > > But still i get a SEGV at strlen. > > Could you please tell me if my changes above are correct? You write the '\0' one element past the end of the buffer. The buffer has 1.048.576 elements, the indices go from 0 to 1.048.575. This is *the* typical off-by-one error. It most probably does not segfault at the strlen(), but when writing the '\0'. From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 12:12:02 2009 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 7CA011065AA8 for ; Wed, 28 Jan 2009 12:12:02 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id 36D468FC12 for ; Wed, 28 Jan 2009 12:12:02 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id C75DE73098; Wed, 28 Jan 2009 13:17:34 +0100 (CET) Date: Wed, 28 Jan 2009 13:17:34 +0100 From: Luigi Rizzo To: Christoph Mallon Message-ID: <20090128121734.GA64348@onelab2.iet.unipi.it> References: <20090127132102.GA21574@onelab2.iet.unipi.it> <497F91C3.7040502@gmx.de> <20090127232103.GA40501@onelab2.iet.unipi.it> <498045E0.3050405@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <498045E0.3050405@gmx.de> User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org Subject: Re: duplicate typedefs and system headers ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 12:12:10 -0000 On Wed, Jan 28, 2009 at 12:47:44PM +0100, Christoph Mallon wrote: ... > >Would this be better/more compliant with standards -- i.e., > >is the following code correct ? gcc seems to have no objections. > > > > struct foo; > > int a(struct foo *); > > typedef struct foo bar; > > int a(bar *x) { ... } > > What is the problem with just including the correct header? This would > be The Right Thing(tm). Everything else is just an ugly hack. In this context I only need to know that a typedef (or struct) with that name exists, not its internals. The "correct header" defines the actual structure and has tons of other dependencies which make the code harder to read, maintain and compile. Again, if I had a chance to fix the underlying header(s) I would do, but at least right now I don't have such a possibility. cheers luigi From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 12:12:33 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EBB4D1065E8F for ; Wed, 28 Jan 2009 12:12:33 +0000 (UTC) (envelope-from rink@rink.nu) Received: from mx1.rink.nu (gloom.rink.nu [213.34.49.2]) by mx1.freebsd.org (Postfix) with ESMTP id A694E8FC0A for ; Wed, 28 Jan 2009 12:12:33 +0000 (UTC) (envelope-from rink@rink.nu) Received: from localhost (localhost [127.0.0.1]) by mx1.rink.nu (Postfix) with ESMTP id 941DD6D43B; Wed, 28 Jan 2009 13:13:52 +0100 (CET) X-Virus-Scanned: amavisd-new at rink.nu Received: from mx1.rink.nu ([213.34.49.2]) by localhost (gloom.rink.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L8A9vn6EuQXL; Wed, 28 Jan 2009 13:13:49 +0100 (CET) Received: by mx1.rink.nu (Postfix, from userid 1000) id 164116D42B; Wed, 28 Jan 2009 13:13:49 +0100 (CET) Date: Wed, 28 Jan 2009 13:13:49 +0100 From: Rink Springer To: Channa Message-ID: <20090128121349.GJ16902@rink.nu> References: <515c64960901280339m17fa9309v2e1bc3f55454ab@mail.gmail.com> <49804597.6040303@gmx.de> <515c64960901280401w1e1d08bfx29adc124bc749c4a@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <515c64960901280401w1e1d08bfx29adc124bc749c4a@mail.gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Christoph Mallon , freebsd-current@freebsd.org Subject: Re: Jemalloc SEGV for 1MB chunk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 12:12:38 -0000 Hi, On Wed, Jan 28, 2009 at 05:31:43PM +0530, Channa wrote: > size_t size = 1048576 ; > > buf = malloc(size); > for (i = 0; i <= 1048575; i++) > buf[i] = 'a'; > buf[size]='\0'; > printf("The length of buff is : %d\n",strlen(buf)); > free(buf); > return 0; > } > > I NULL terminated the string > buf[size] = '\0' <== The last character is NULL > > But still i get a SEGV at strlen. > > Could you please tell me if my changes above are correct? They are not - because size = 1048576, you will get a buffer of 1048576 bytes, that is, buf[0] ... buf[1048575] = buf[0] .. buf[size - 1]. Thus, you need to do: buf[size - 1] = '\0'; And it'll work. Regards, -- Rink P.W. Springer - http://rink.nu "Chance favours the prepared mind" - Penn From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 12:16:16 2009 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 5FDC610656E1; Wed, 28 Jan 2009 12:16:16 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 1CA9B8FC14; Wed, 28 Jan 2009 12:16:15 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0SCGDid094186; Wed, 28 Jan 2009 07:16:13 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.14.3/8.14.3) with ESMTP id n0SCGD3d091149; Wed, 28 Jan 2009 07:16:13 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id F03DE7302F; Wed, 28 Jan 2009 07:16:12 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090128121612.F03DE7302F@freebsd-current.sentex.ca> Date: Wed, 28 Jan 2009 07:16:12 -0500 (EST) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on i386/pc98 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: Wed, 28 Jan 2009 12:16:19 -0000 TB --- 2009-01-28 10:54:54 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-01-28 10:54:54 - starting HEAD tinderbox run for i386/pc98 TB --- 2009-01-28 10:54:54 - cleaning the object tree TB --- 2009-01-28 10:55:28 - cvsupping the source tree TB --- 2009-01-28 10:55:28 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/i386/pc98/supfile TB --- 2009-01-28 10:55:37 - building world TB --- 2009-01-28 10:55:37 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-28 10:55:37 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-28 10:55:37 - TARGET=pc98 TB --- 2009-01-28 10:55:37 - TARGET_ARCH=i386 TB --- 2009-01-28 10:55:37 - TZ=UTC TB --- 2009-01-28 10:55:37 - __MAKE_CONF=/dev/null TB --- 2009-01-28 10:55:37 - cd /src TB --- 2009-01-28 10:55:37 - /usr/bin/make -B buildworld >>> World build started on Wed Jan 28 10:55:39 UTC 2009 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Wed Jan 28 12:15:48 UTC 2009 TB --- 2009-01-28 12:15:48 - generating LINT kernel config TB --- 2009-01-28 12:15:48 - cd /src/sys/pc98/conf TB --- 2009-01-28 12:15:48 - /usr/bin/make -B LINT TB --- 2009-01-28 12:15:48 - building LINT kernel TB --- 2009-01-28 12:15:48 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-28 12:15:48 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-28 12:15:48 - TARGET=pc98 TB --- 2009-01-28 12:15:48 - TARGET_ARCH=i386 TB --- 2009-01-28 12:15:48 - TZ=UTC TB --- 2009-01-28 12:15:48 - __MAKE_CONF=/dev/null TB --- 2009-01-28 12:15:48 - cd /src TB --- 2009-01-28 12:15:48 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Jan 28 12:15:48 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree [...] ===> usb (cleandir) rm -f export_syms usb.ko usb.kld usb_if.o hid.o uhub.o usb.o usb_mem.o usb_quirks.o usb_subr.o usbdi.o usbdi_util.o usb_ethersubr.o opt_usb.h usb_if.c usb_if.h bus_if.h device_if.h usbdevs.h usbdevs_data.h rm -f @ machine i386 rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> usb2 (cleandir) 1 open conditional: at line 33 (evaluated to false) make: fatal errors encountered -- cannot continue *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-28 12:16:11 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-28 12:16:11 - ERROR: failed to build lint kernel TB --- 2009-01-28 12:16:11 - 3889.76 user 372.78 system 4877.45 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-pc98.full From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 12:20:56 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72B4110658C1 for ; Wed, 28 Jan 2009 12:20:56 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id 2486A8FC13 for ; Wed, 28 Jan 2009 12:20:55 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1LS9Pa-000NBW-Ct; Wed, 28 Jan 2009 14:20:54 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Channa In-reply-to: <515c64960901280401w1e1d08bfx29adc124bc749c4a@mail.gmail.com> References: <515c64960901280339m17fa9309v2e1bc3f55454ab@mail.gmail.com> <49804597.6040303@gmx.de> <515c64960901280401w1e1d08bfx29adc124bc749c4a@mail.gmail.com> Comments: In-reply-to Channa message dated "Wed, 28 Jan 2009 17:31:43 +0530." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Jan 2009 14:20:54 +0200 From: Danny Braniss Message-ID: Cc: Christoph Mallon , freebsd-current@freebsd.org Subject: Re: Jemalloc SEGV for 1MB chunk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 12:21:00 -0000 > Hi, > Thanks for your reply. > You mean to say i should modify the test as below: > > #include > #include > #include > > > int main() > { > int i; > char *buf; > size_t size = 1048576 ; > > buf = malloc(size); > for (i = 0; i <= 1048575; i++) > buf[i] = 'a'; > buf[size]='\0'; > printf("The length of buff is : %d\n",strlen(buf)); > free(buf); > return 0; > } > > I NULL terminated the string > buf[size] = '\0' <== The last character is NULL > > But still i get a SEGV at strlen. > > Could you please tell me if my changes above are correct? > clear case of off by one. you are requesting 'size' bytes, indexing starts at 0, all the way to size-1 which is ALL the bytes you malloc'ed then you zero the size+1 byte, ah, btw, it's not strlen that is SEGV'ing. danny > Regards, > Channa > > > On 28/01/2009, Christoph Mallon wrote: > > Channa schrieb: > > > > > > > Hi All, > > > I am using jemalloc.c source from FreeBSD-current source. > > > When i allocate 1MB of memory using malloc() and use it as the below > > > test shows > > > > > > #include > > > #include > > > #include > > > > > > int main() > > > { > > > int i; > > > char *buf; > > > size_t size = 1048576 ; > > > > > > buf = malloc(size); > > > for (i = 0; i < 1048576; i++) > > > buf[i] = 'a'; > > > printf("The length of buff is : %d\n",strlen(buf)); > > > free(buf); > > > return 0; > > > } > > > > > > When i try to call strlen(buf) SEGV is recived. > > > > > > This behaviour is seen when only for 1MB chunk if i allocate > > > memory lesser than 1MB no issues noticed. > > > > > > Could anyone see similar problem? > > > Is the above test wrong? > > > Or some issue with huge memory allocation in jemalloc? > > > > > > Your response will be very helpful. > > > > > > Thanks & Regards, > > > Channa > > > > > > > You did not NUL-terminate ('\0') the string. > > > _______________________________________________ > 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 Jan 28 12:25:24 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C1AF106594B for ; Wed, 28 Jan 2009 12:25:24 +0000 (UTC) (envelope-from channa.kad@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.228]) by mx1.freebsd.org (Postfix) with ESMTP id E017E8FC22 for ; Wed, 28 Jan 2009 12:25:23 +0000 (UTC) (envelope-from channa.kad@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so7038735rvf.43 for ; Wed, 28 Jan 2009 04:25:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=NdBz7s2mC9iPEaBsPhQ+LCR0q1UWBpbLwnVHgz72eoo=; b=fQSJQaMamjwN00QSTx0BXWXDOFVquMW1tDxUqccyOg9B1cm3vUIXLlm9Tf9GEHy6aV ovwR74RR2ng8UHHGR9ezBlILbzhp+BVMkNLtTV3UAId02jDhA/PE9yk/uODiX76+946h iXXVMURrW9XDwrbEFUZ+Gjs0ox7lbGO2vl8T4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=QLGcAIN/p5aqou2JyjqP7tp+HdtgRB8C/1VnfdM+l2UfpxKldezGLwi6voLPUcx6RY IkoYC/a84XJ2FjwY7tzeu527FAEDKDs6KUZgVtDarkAGEZoY1zjcY5NfI/EVfvZyK5JT metZCbY19sYkfjBKcI2lBQN1tpTFkgGvQyYLM= MIME-Version: 1.0 Received: by 10.140.147.5 with SMTP id u5mr990011rvd.86.1233145523488; Wed, 28 Jan 2009 04:25:23 -0800 (PST) In-Reply-To: References: <515c64960901280339m17fa9309v2e1bc3f55454ab@mail.gmail.com> <49804597.6040303@gmx.de> <515c64960901280401w1e1d08bfx29adc124bc749c4a@mail.gmail.com> Date: Wed, 28 Jan 2009 17:55:23 +0530 Message-ID: <515c64960901280425y642a190ka31409cfc2a2fd8f@mail.gmail.com> From: Channa To: Danny Braniss Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Christoph Mallon , freebsd-current@freebsd.org Subject: Re: Jemalloc SEGV for 1MB chunk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 12:25:25 -0000 Hi, Thanks for the reply. I understand , after terminating the string with NULL character no SEGV is seen. But if i change the request size to a value less than 1MB for eg: 4096 Bytes, As in the below test code: #include #include #include int main() { int i; char *buf; size_t size = 4096 ; buf = malloc(size); for (i = 0; i < size; i++) buf[i] = 'a'; printf("The length of buff is : %d\n",strlen(buf)); free(buf); return 0; } I dont see any issues, without terminating the string with NULL character the test code works fine. The issue is seen only for size 1MB exactly. Can anyone explain this behaviour? Thanks in Advance, Channa On 28/01/2009, Danny Braniss wrote: > > Hi, > > Thanks for your reply. > > You mean to say i should modify the test as below: > > > > #include > > #include > > #include > > > > > > int main() > > { > > int i; > > char *buf; > > size_t size = 1048576 ; > > > > buf = malloc(size); > > for (i = 0; i <= 1048575; i++) > > buf[i] = 'a'; > > buf[size]='\0'; > > printf("The length of buff is : %d\n",strlen(buf)); > > free(buf); > > return 0; > > } > > > > I NULL terminated the string > > buf[size] = '\0' <== The last character is NULL > > > > But still i get a SEGV at strlen. > > > > Could you please tell me if my changes above are correct? > > > > clear case of off by one. > you are requesting 'size' bytes, indexing starts at 0, all the way to size-1 > which is ALL the bytes you malloc'ed > then you zero the size+1 byte, ah, btw, it's not strlen that is SEGV'ing. > > > danny > > > > Regards, > > Channa > > > > > > On 28/01/2009, Christoph Mallon wrote: > > > Channa schrieb: > > > > > > > > > > Hi All, > > > > I am using jemalloc.c source from FreeBSD-current source. > > > > When i allocate 1MB of memory using malloc() and use it as the below > > > > test shows > > > > > > > > #include > > > > #include > > > > #include > > > > > > > > int main() > > > > { > > > > int i; > > > > char *buf; > > > > size_t size = 1048576 ; > > > > > > > > buf = malloc(size); > > > > for (i = 0; i < 1048576; i++) > > > > buf[i] = 'a'; > > > > printf("The length of buff is : %d\n",strlen(buf)); > > > > free(buf); > > > > return 0; > > > > } > > > > > > > > When i try to call strlen(buf) SEGV is recived. > > > > > > > > This behaviour is seen when only for 1MB chunk if i allocate > > > > memory lesser than 1MB no issues noticed. > > > > > > > > Could anyone see similar problem? > > > > Is the above test wrong? > > > > Or some issue with huge memory allocation in jemalloc? > > > > > > > > Your response will be very helpful. > > > > > > > > Thanks & Regards, > > > > Channa > > > > > > > > > > You did not NUL-terminate ('\0') the string. > > > > > > _______________________________________________ > > 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 Jan 28 12:30:09 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A575510659F7 for ; Wed, 28 Jan 2009 12:30:09 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id E66178FC08 for ; Wed, 28 Jan 2009 12:30:08 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: (qmail invoked by alias); 28 Jan 2009 12:30:07 -0000 Received: from p54A3E68D.dip.t-dialin.net (EHLO tron.homeunix.org) [84.163.230.141] by mail.gmx.net (mp037) with SMTP; 28 Jan 2009 13:30:07 +0100 X-Authenticated: #1673122 X-Provags-ID: V01U2FsdGVkX19r9dFQOplrUe1Pp4GpYbuWCvJG6JAO9JvsWG7OWy De8oewkCbBcew5 Message-ID: <49804FCE.7090405@gmx.de> Date: Wed, 28 Jan 2009 13:30:06 +0100 From: Christoph Mallon User-Agent: Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Channa References: <515c64960901280339m17fa9309v2e1bc3f55454ab@mail.gmail.com> <49804597.6040303@gmx.de> <515c64960901280401w1e1d08bfx29adc124bc749c4a@mail.gmail.com> <515c64960901280425y642a190ka31409cfc2a2fd8f@mail.gmail.com> In-Reply-To: <515c64960901280425y642a190ka31409cfc2a2fd8f@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.58 Cc: freebsd-current@freebsd.org Subject: Re: Jemalloc SEGV for 1MB chunk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 12:30:10 -0000 Channa schrieb: > Hi, > Thanks for the reply. > > I understand , after terminating the string with NULL character no SEGV is seen. > > But if i change the request size to a value less than 1MB for eg: 4096 Bytes, > > As in the below test code: > > #include > #include > #include > > int main() > { > int i; > char *buf; > size_t size = 4096 ; > > buf = malloc(size); > for (i = 0; i < size; i++) > buf[i] = 'a'; > printf("The length of buff is : %d\n",strlen(buf)); > free(buf); > return 0; > } > > I dont see any issues, without terminating the string with NULL > character the test code works fine. The issue is seen only for size > 1MB exactly. > > Can anyone explain this behaviour? Undefined behaviour and (bad) luck. You are reading random garbage from memory. For a large allocation like 1MB you get page aligned memory and the page after the allocation is very likely not mapped, so you get a segfault when you try to access it. This really does not belong on freebsd-current@. From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 12:37:19 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 58996106567A for ; Wed, 28 Jan 2009 12:37:19 +0000 (UTC) (envelope-from channa.kad@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.228]) by mx1.freebsd.org (Postfix) with ESMTP id 29A9E8FC0A for ; Wed, 28 Jan 2009 12:37:19 +0000 (UTC) (envelope-from channa.kad@gmail.com) Received: by rv-out-0506.google.com with SMTP id g9so1801157rvb.3 for ; Wed, 28 Jan 2009 04:37:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=snO3NPVxKjENgkQIRCvV505z871rvq1iOnJp8dYZYT8=; b=RBam5HhPJMh588DP2boJcMTNU8mI4BhtcbvnVktZSnc0e9X2dVbALPAwPN6MRfawhc txxF4ynk7OaGH23mjz3JUjD5MDG0y9FnOupqpFkjCNLH9Stj61zInS0efaYgj2vqiG0O wJkP2fHmbT6gCDAAm1GTtj7f0Ht5E/T4nZBsg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=v4XRsYipbATxzhuWQ6FgXINYv657kPWJdQP2plTnqfFniWMxN+CpFFAbmcpF9pjFLZ 5laEPKdjA87k3HwrZpvKguQWHJojGLiC66Shv0SMSYHma3BkaGDuv9YIKeVqr417YYxg lPZsc+HNIuD9eO3mQby6qxVTsMBIL1/OdC2yk= MIME-Version: 1.0 Received: by 10.141.106.14 with SMTP id i14mr1733219rvm.27.1233146238860; Wed, 28 Jan 2009 04:37:18 -0800 (PST) In-Reply-To: <49804FCE.7090405@gmx.de> References: <515c64960901280339m17fa9309v2e1bc3f55454ab@mail.gmail.com> <49804597.6040303@gmx.de> <515c64960901280401w1e1d08bfx29adc124bc749c4a@mail.gmail.com> <515c64960901280425y642a190ka31409cfc2a2fd8f@mail.gmail.com> <49804FCE.7090405@gmx.de> Date: Wed, 28 Jan 2009 18:07:18 +0530 Message-ID: <515c64960901280437hd4f7b2dx36a1774afe2f5646@mail.gmail.com> From: Channa To: Christoph Mallon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Jemalloc SEGV for 1MB chunk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 12:37:19 -0000 Hi, Thanks for the reply. Does the same behaviour seen on FreeBSD environment? I am using FreeBSD libraries to test the test code. So according to you its better to NULL terminate in the test code to avoid this undefined behaviour? Thanks , Channa On 28/01/2009, Christoph Mallon wrote: > Channa schrieb: > > > Hi, > > Thanks for the reply. > > > > I understand , after terminating the string with NULL character no SEGV is > seen. > > > > But if i change the request size to a value less than 1MB for eg: 4096 > Bytes, > > > > As in the below test code: > > > > #include > > #include > > #include > > > > int main() > > { > > int i; > > char *buf; > > size_t size = 4096 ; > > > > buf = malloc(size); > > for (i = 0; i < size; i++) > > buf[i] = 'a'; > > printf("The length of buff is : %d\n",strlen(buf)); > > free(buf); > > return 0; > > } > > > > I dont see any issues, without terminating the string with NULL > > character the test code works fine. The issue is seen only for size > > 1MB exactly. > > > > Can anyone explain this behaviour? > > > > Undefined behaviour and (bad) luck. You are reading random garbage from > memory. For a large allocation like 1MB you get page aligned memory and the > page after the allocation is very likely not mapped, so you get a segfault > when you try to access it. > This really does not belong on freebsd-current@. > From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 12:45:26 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C098106564A for ; Wed, 28 Jan 2009 12:45:26 +0000 (UTC) (envelope-from channa.kad@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by mx1.freebsd.org (Postfix) with ESMTP id 1D2B38FC1C for ; Wed, 28 Jan 2009 12:45:25 +0000 (UTC) (envelope-from channa.kad@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so7046937rvf.43 for ; Wed, 28 Jan 2009 04:45:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=61myyUOk777GYkZ5eLwQ6ASwShhwMmi6yJDOIIGSeiY=; b=LbDC6mtJraFds/KVcfLjAuZ8MqfHHop3UZRpUcltQMAo6fVUHg1tFi0FabIKbUNMfP lf8yBn72FB3U6YTyA2fkd7pkbQYC+OTAcbHisXfznYI9tzRsROIH84Q+WBCcqHrJOO0s YK9bCpjA0H4iW6iBRdy4vI7Y7QZu16DsyE1z4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ojc1thIblyabPtYCn36COgC5iNDmu8Wbr7/NUB2sDrBDXbsFo2fqNFF/cbOA32R/iP GIUEIEd9I5MWlf55oB2igl2xAtOw26QZtvb7tFIQJTFTLBrjXAn2vuHujIHTLg0Fehfb kUK3eJJtedU/MLPab968f1YHEp/Y6uGnwGD0Y= MIME-Version: 1.0 Received: by 10.141.115.20 with SMTP id s20mr1684383rvm.70.1233146725579; Wed, 28 Jan 2009 04:45:25 -0800 (PST) In-Reply-To: <49804FCE.7090405@gmx.de> References: <515c64960901280339m17fa9309v2e1bc3f55454ab@mail.gmail.com> <49804597.6040303@gmx.de> <515c64960901280401w1e1d08bfx29adc124bc749c4a@mail.gmail.com> <515c64960901280425y642a190ka31409cfc2a2fd8f@mail.gmail.com> <49804FCE.7090405@gmx.de> Date: Wed, 28 Jan 2009 18:15:25 +0530 Message-ID: <515c64960901280445l1ab33256sae2e69df30efe502@mail.gmail.com> From: Channa To: Christoph Mallon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Jemalloc SEGV for 1MB chunk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 12:45:26 -0000 Hi, "This really does not belong on freebsd-current@." by this you mean to say in FreeBSD current this problem is not seen. Are you referring to FreeBSD current jemalloc version which is "1.183". Since i am using the same Version of jemalloc to test the code. Could you please elaborate more if my understanding on your statment is correct? Thanks in Advance, Channa On 28/01/2009, Christoph Mallon wrote: > Channa schrieb: > > > Hi, > > Thanks for the reply. > > > > I understand , after terminating the string with NULL character no SEGV is > seen. > > > > But if i change the request size to a value less than 1MB for eg: 4096 > Bytes, > > > > As in the below test code: > > > > #include > > #include > > #include > > > > int main() > > { > > int i; > > char *buf; > > size_t size = 4096 ; > > > > buf = malloc(size); > > for (i = 0; i < size; i++) > > buf[i] = 'a'; > > printf("The length of buff is : %d\n",strlen(buf)); > > free(buf); > > return 0; > > } > > > > I dont see any issues, without terminating the string with NULL > > character the test code works fine. The issue is seen only for size > > 1MB exactly. > > > > Can anyone explain this behaviour? > > > > Undefined behaviour and (bad) luck. You are reading random garbage from > memory. For a large allocation like 1MB you get page aligned memory and the > page after the allocation is very likely not mapped, so you get a segfault > when you try to access it. > This really does not belong on freebsd-current@. > From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 12:53:54 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71753106564A for ; Wed, 28 Jan 2009 12:53:54 +0000 (UTC) (envelope-from sos@freebsd.org) Received: from deepcore.dk (adsl.deepcore.dk [87.63.29.106]) by mx1.freebsd.org (Postfix) with ESMTP id D18CF8FC1D for ; Wed, 28 Jan 2009 12:53:53 +0000 (UTC) (envelope-from sos@freebsd.org) Received: from [172.18.2.117] (axiell-gw1.novi.dk [77.243.61.137]) by deepcore.dk (8.14.3/8.14.2) with ESMTP id n0SCrpG4023816; Wed, 28 Jan 2009 13:53:51 +0100 (CET) (envelope-from sos@freebsd.org) Message-Id: From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= To: Channa In-Reply-To: <515c64960901280445l1ab33256sae2e69df30efe502@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v930.3) Date: Wed, 28 Jan 2009 13:53:50 +0100 References: <515c64960901280339m17fa9309v2e1bc3f55454ab@mail.gmail.com> <49804597.6040303@gmx.de> <515c64960901280401w1e1d08bfx29adc124bc749c4a@mail.gmail.com> <515c64960901280425y642a190ka31409cfc2a2fd8f@mail.gmail.com> <49804FCE.7090405@gmx.de> <515c64960901280445l1ab33256sae2e69df30efe502@mail.gmail.com> X-Mailer: Apple Mail (2.930.3) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (deepcore.dk [87.63.29.106]); Wed, 28 Jan 2009 13:53:52 +0100 (CET) Cc: freebsd-current@freebsd.org Subject: Re: Jemalloc SEGV for 1MB chunk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 12:53:54 -0000 On 28Jan, 2009, at 13:45 , Channa wrote: > Hi, > "This really does not belong on freebsd-current@." by this you mean to > say in FreeBSD current this problem is not seen. > > Are you referring to FreeBSD current jemalloc version which is =20 > "1.183". > Since i am using the same Version of jemalloc to test the code. > > Could you please elaborate more if my understanding on your statment =20= > is correct? You are using strlen() on a string that is not NULL terminated. That =20 is a violation of how strlen() works, and the result is undefined. =20 That means anything can happen including killing you dog, eating your =20= first born child etc etc. To be brutally honest with you, this is one of the most important =20 things you (should) learn when using strings in 'C', that is why it =20 doesn't belong here on the list. -S=F8ren > > > Thanks in Advance, > Channa > > > On 28/01/2009, Christoph Mallon wrote: >> Channa schrieb: >> >>> Hi, >>> Thanks for the reply. >>> >>> I understand , after terminating the string with NULL character no =20= >>> SEGV is >> seen. >>> >>> But if i change the request size to a value less than 1MB for eg: =20= >>> 4096 >> Bytes, >>> >>> As in the below test code: >>> >>> #include >>> #include >>> #include >>> >>> int main() >>> { >>> int i; >>> char *buf; >>> size_t size =3D 4096 ; >>> >>> buf =3D malloc(size); >>> for (i =3D 0; i < size; i++) >>> buf[i] =3D 'a'; >>> printf("The length of buff is : %d\n",strlen(buf)); >>> free(buf); >>> return 0; >>> } >>> >>> I dont see any issues, without terminating the string with NULL >>> character the test code works fine. The issue is seen only for size >>> 1MB exactly. >>> >>> Can anyone explain this behaviour? >>> >> >> Undefined behaviour and (bad) luck. You are reading random garbage =20= >> from >> memory. For a large allocation like 1MB you get page aligned memory =20= >> and the >> page after the allocation is very likely not mapped, so you get a =20 >> segfault >> when you try to access it. >> This really does not belong on freebsd-current@. >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org=20 > " > -S=F8ren From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 12:55:31 2009 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 B965010656BE; Wed, 28 Jan 2009 12:55:31 +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 778DD8FC49; Wed, 28 Jan 2009 12:55:31 +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.3/8.14.3) with ESMTP id n0SCtTwM068156; Wed, 28 Jan 2009 07:55:29 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0SCtTn3018977; Wed, 28 Jan 2009 07:55:29 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 03EC57302F; Wed, 28 Jan 2009 07:55:28 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090128125529.03EC57302F@freebsd-current.sentex.ca> Date: Wed, 28 Jan 2009 07:55:28 -0500 (EST) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2009 12:55:38 -0000 TB --- 2009-01-28 11:34:38 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-01-28 11:34:38 - starting HEAD tinderbox run for ia64/ia64 TB --- 2009-01-28 11:34:38 - cleaning the object tree TB --- 2009-01-28 11:35:15 - cvsupping the source tree TB --- 2009-01-28 11:35:15 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/ia64/ia64/supfile TB --- 2009-01-28 11:35:23 - building world TB --- 2009-01-28 11:35:23 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-28 11:35:23 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-28 11:35:23 - TARGET=ia64 TB --- 2009-01-28 11:35:23 - TARGET_ARCH=ia64 TB --- 2009-01-28 11:35:23 - TZ=UTC TB --- 2009-01-28 11:35:23 - __MAKE_CONF=/dev/null TB --- 2009-01-28 11:35:23 - cd /src TB --- 2009-01-28 11:35:23 - /usr/bin/make -B buildworld >>> World build started on Wed Jan 28 11:35:26 UTC 2009 >>> 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 [...] (cd /src/rescue/rescue/../../sbin/dumpfs && /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/dumpfs/ depend && /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/dumpfs/ dumpfs.o) rm -f .depend mkdep -f .depend -a -DRESCUE /src/sbin/dumpfs/dumpfs.c echo dumpfs: /obj/ia64/src/tmp/usr/lib/libc.a /obj/ia64/src/tmp/usr/lib/libufs.a >> .depend cc -O2 -pipe -DRESCUE -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/dumpfs/dumpfs.c cc1: warnings being treated as errors /src/sbin/dumpfs/dumpfs.c: In function 'pblklist': /src/sbin/dumpfs/dumpfs.c:459: warning: format '%lld' expects type 'long long int', but argument 2 has type 'off_t' *** Error code 1 Stop in /src/sbin/dumpfs. *** Error code 1 Stop in /obj/ia64/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-28 12:55:28 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-28 12:55:28 - ERROR: failed to build world TB --- 2009-01-28 12:55:28 - 3996.66 user 312.59 system 4850.08 real http://tinderbox.des.no/tinderbox-head-HEAD-ia64-ia64.full From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 15:34:32 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A632106566C for ; Wed, 28 Jan 2009 15:34:32 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-fx0-f15.google.com (mail-fx0-f15.google.com [209.85.220.15]) by mx1.freebsd.org (Postfix) with ESMTP id 99A748FC08 for ; Wed, 28 Jan 2009 15:34:31 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by fxm8 with SMTP id 8so614814fxm.19 for ; Wed, 28 Jan 2009 07:34:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=zg4p2By5rtV84g38oDnuZyNkKSkr6OCqWB9SOH2r0gQ=; b=ei50sESDubIKyr0+wEpuoFin0bfm++xRv3Moxer5ZUwkrdynVclWZcH04hfsDtPZMQ Yj8PwMrI/Mnm/8izv6ajGSBJqCHfBfmrnsirmwFHIfOhVY01BJCo4+3y2AR8tngT1efK 1dOIQER1NevUzyAMcQnSeMIJKjEyYGyjiEjsM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=xOXQkCeEMRWCYM2sJi4E+F39M03PfGds7cmwnIZp4edt+7RLkLeIhR+ZQ0rnHk83j/ ZL++D6RBIANorvtOxvIzEH8mwnsc/DsJF0wJB9R/3oS24WJsdwkLUc9vWAzpNJKZVC8R IggNi291Pi2/zitoPcEZqtQbz137PyJUdATwI= MIME-Version: 1.0 Received: by 10.181.205.3 with SMTP id h3mr510725bkq.91.1233156870331; Wed, 28 Jan 2009 07:34:30 -0800 (PST) In-Reply-To: <18808.54543.771955.996924@jerusalem.litteratus.org> References: <20090120175558.GA43333@freebsd.org> <18808.54543.771955.996924@jerusalem.litteratus.org> Date: Wed, 28 Jan 2009 18:34:30 +0300 Message-ID: From: pluknet To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 15:34:32 -0000 I found this article today. It answers some questions about GPLv3. http://www.fsf.org/licensing/licenses/gcc-exception-faq.html -- wbr, pluknet From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 16:17:08 2009 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 EBA74106566C; Wed, 28 Jan 2009 16:17:08 +0000 (UTC) (envelope-from rbgarga@gmail.com) Received: from mail-qy0-f17.google.com (mail-qy0-f17.google.com [209.85.221.17]) by mx1.freebsd.org (Postfix) with ESMTP id 6A5E88FC1A; Wed, 28 Jan 2009 16:17:08 +0000 (UTC) (envelope-from rbgarga@gmail.com) Received: by qyk10 with SMTP id 10so11171623qyk.19 for ; Wed, 28 Jan 2009 08:17:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=9htqIAT6ApDLCdHBY0FNaZxvFbgxTb0vqMW84M7nqqk=; b=unPWqIKqyZ/7ktGUNLLZJFDUJ9ytcwJvulYU9IXCOIt8hYSz6EO2cZH8lSGT8ML0Mx vF3BK9iDTZryjyNzNhGtaoqL+hZkWbohOYMDLIvTKsKx5EVbht3sRAjq1nkLXv+4YjRz 6cTVqAiQ52nwOZApbL3oOaTTupYzvDw2Nem8o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=DARuBHvL4vVnzf6t8xEi0lh+Lx8BboWvQXGOYXXn6fjfS+8eyQsYjvs7bvwvP/65J8 NjF4IhxAhou7k1Lu3CvBuympOogU1BJVT0VNJmB7Hj8GmQWJYN8gpHgL62Z/ML9ENAWs CuRhUjRbwTTO5u7BKg018qXHZ2w/NLfHLpfxo= MIME-Version: 1.0 Received: by 10.215.66.17 with SMTP id t17mr1598715qak.230.1233159427776; Wed, 28 Jan 2009 08:17:07 -0800 (PST) In-Reply-To: <747dc8f30812290753j6ad7582cr7119a13704daad00@mail.gmail.com> References: <20081222214010.GA18389@elvis.mu.org> <200812261723.58897.hselasky@c2i.net> <747dc8f30812290301y15c1292bofe3bf1ea49968438@mail.gmail.com> <200812291243.42984.hselasky@c2i.net> <747dc8f30812290753j6ad7582cr7119a13704daad00@mail.gmail.com> Date: Wed, 28 Jan 2009 14:17:07 -0200 Message-ID: <747dc8f30901280817g269a496p2b02dfec2c9c7a6e@mail.gmail.com> From: Renato Botelho To: Hans Petter Selasky Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, current@freebsd.org, Alfred Perlstein Subject: Re: HEADSUP usb2 (usb4bsd) to become default in 2 weeks. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 16:17:09 -0000 On Mon, Dec 29, 2008 at 1:53 PM, Renato Botelho wrote: > On Mon, Dec 29, 2008 at 9:43 AM, Hans Petter Selasky wrote: >> On Monday 29 December 2008, Renato Botelho wrote: >>> On Fri, Dec 26, 2008 at 2:23 PM, Hans Petter Selasky >> wrote: >>> > On Friday 26 December 2008, Renato Botelho wrote: >>> >> On Wed, Dec 24, 2008 at 4:58 PM, Renato Botelho >> wrote: >>> >> > On Wed, Dec 24, 2008 at 9:12 AM, Hans Petter Selasky >>> >> > >>> > >>> > wrote: >>> >> >> On Wednesday 24 December 2008, Renato Botelho wrote: >>> >> >>> On Mon, Dec 22, 2008 at 7:40 PM, Alfred Perlstein >>> >> >>> >>> >> >>> >> Here are my /var/log/messages: >>> >> >>> >> http://pastebin.com/f6c28d7ca >>> >> >>> >> I still have problems with my keyboard. >>> >> >>> >> BTW, I added a #include of usb2_ioctl.h to fix lack of >>> >> USB_SHORT_XFER_OK definition, could it cause any >>> >> problems? >>> >> >>> >> Thanks >>> > >>> > There are some debugging sysctls which you can try to tune/increase: >>> > >>> > hw.usb2.pr_recovery_delay: 250 >>> > >>> > hw.usb2.ss_delay: 0 >>> > >>> > hw.usb2.ehci.no_hs: 0 // this value is a boolean >>> >>> I kept last one as 0 and tried double first two, last values i >>> tried was 1000 and 4, and there was no changes on the >>> problem. >> >> Have you filed a PR with the original description? > > Here it is, PR# 130024 Like I said in PR followup, since yesterday when I update my box to rev. 187767 everything is working fine garga@botelhor:~> usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.1: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen4.1: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen3.2: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen3.3: at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.4: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON Could I close the PR? Thanks for fixing this!!! -- Renato Botelho From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 16:17:08 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EBA74106566C; Wed, 28 Jan 2009 16:17:08 +0000 (UTC) (envelope-from rbgarga@gmail.com) Received: from mail-qy0-f17.google.com (mail-qy0-f17.google.com [209.85.221.17]) by mx1.freebsd.org (Postfix) with ESMTP id 6A5E88FC1A; Wed, 28 Jan 2009 16:17:08 +0000 (UTC) (envelope-from rbgarga@gmail.com) Received: by qyk10 with SMTP id 10so11171623qyk.19 for ; Wed, 28 Jan 2009 08:17:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=9htqIAT6ApDLCdHBY0FNaZxvFbgxTb0vqMW84M7nqqk=; b=unPWqIKqyZ/7ktGUNLLZJFDUJ9ytcwJvulYU9IXCOIt8hYSz6EO2cZH8lSGT8ML0Mx vF3BK9iDTZryjyNzNhGtaoqL+hZkWbohOYMDLIvTKsKx5EVbht3sRAjq1nkLXv+4YjRz 6cTVqAiQ52nwOZApbL3oOaTTupYzvDw2Nem8o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=DARuBHvL4vVnzf6t8xEi0lh+Lx8BboWvQXGOYXXn6fjfS+8eyQsYjvs7bvwvP/65J8 NjF4IhxAhou7k1Lu3CvBuympOogU1BJVT0VNJmB7Hj8GmQWJYN8gpHgL62Z/ML9ENAWs CuRhUjRbwTTO5u7BKg018qXHZ2w/NLfHLpfxo= MIME-Version: 1.0 Received: by 10.215.66.17 with SMTP id t17mr1598715qak.230.1233159427776; Wed, 28 Jan 2009 08:17:07 -0800 (PST) In-Reply-To: <747dc8f30812290753j6ad7582cr7119a13704daad00@mail.gmail.com> References: <20081222214010.GA18389@elvis.mu.org> <200812261723.58897.hselasky@c2i.net> <747dc8f30812290301y15c1292bofe3bf1ea49968438@mail.gmail.com> <200812291243.42984.hselasky@c2i.net> <747dc8f30812290753j6ad7582cr7119a13704daad00@mail.gmail.com> Date: Wed, 28 Jan 2009 14:17:07 -0200 Message-ID: <747dc8f30901280817g269a496p2b02dfec2c9c7a6e@mail.gmail.com> From: Renato Botelho To: Hans Petter Selasky Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, current@freebsd.org, Alfred Perlstein Subject: Re: HEADSUP usb2 (usb4bsd) to become default in 2 weeks. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 16:17:09 -0000 On Mon, Dec 29, 2008 at 1:53 PM, Renato Botelho wrote: > On Mon, Dec 29, 2008 at 9:43 AM, Hans Petter Selasky wrote: >> On Monday 29 December 2008, Renato Botelho wrote: >>> On Fri, Dec 26, 2008 at 2:23 PM, Hans Petter Selasky >> wrote: >>> > On Friday 26 December 2008, Renato Botelho wrote: >>> >> On Wed, Dec 24, 2008 at 4:58 PM, Renato Botelho >> wrote: >>> >> > On Wed, Dec 24, 2008 at 9:12 AM, Hans Petter Selasky >>> >> > >>> > >>> > wrote: >>> >> >> On Wednesday 24 December 2008, Renato Botelho wrote: >>> >> >>> On Mon, Dec 22, 2008 at 7:40 PM, Alfred Perlstein >>> >> >>> >>> >> >>> >> Here are my /var/log/messages: >>> >> >>> >> http://pastebin.com/f6c28d7ca >>> >> >>> >> I still have problems with my keyboard. >>> >> >>> >> BTW, I added a #include of usb2_ioctl.h to fix lack of >>> >> USB_SHORT_XFER_OK definition, could it cause any >>> >> problems? >>> >> >>> >> Thanks >>> > >>> > There are some debugging sysctls which you can try to tune/increase: >>> > >>> > hw.usb2.pr_recovery_delay: 250 >>> > >>> > hw.usb2.ss_delay: 0 >>> > >>> > hw.usb2.ehci.no_hs: 0 // this value is a boolean >>> >>> I kept last one as 0 and tried double first two, last values i >>> tried was 1000 and 4, and there was no changes on the >>> problem. >> >> Have you filed a PR with the original description? > > Here it is, PR# 130024 Like I said in PR followup, since yesterday when I update my box to rev. 187767 everything is working fine garga@botelhor:~> usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.1: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen4.1: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen3.2: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen3.3: at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.4: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON Could I close the PR? Thanks for fixing this!!! -- Renato Botelho From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 17:18:13 2009 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 B99AC1065672 for ; Wed, 28 Jan 2009 17:18:13 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: from web63901.mail.re1.yahoo.com (web63901.mail.re1.yahoo.com [69.147.97.116]) by mx1.freebsd.org (Postfix) with SMTP id 9DC328FC12 for ; Wed, 28 Jan 2009 17:18:12 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: (qmail 75553 invoked by uid 60001); 28 Jan 2009 17:18:12 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID; b=XPJtWeiZCsrqF6m9YBrmeX6U+Tw/lBV6tdoaU308XNWd1Zyay4VwOxuLJXfuf0IaT1wYzl8/K4PQc0dRD0vmslhHLKE2njqIh1vKkEj2ixrGH7S1vLJauVTacLGE/3YbzJFvLeSpN7RqkayAeIYOakvtxZ1EG7QXfT1CyQ6hyPw=; X-YMail-OSG: lNZEuDsVM1lHoDrq.87S8wFk1Fpy4xNgkLpvt2rufGrluCCCcPKAYwAZy1phctmNYP0Ia7qsCaFqJdM1XUzcZgAKWKdRn0c023s11p0Ebo4BelaLJ.NUVjMaavTbdFBPIBt1v8Zx97Ae__y8rBpAvFbdhcE- Received: from [98.242.222.229] by web63901.mail.re1.yahoo.com via HTTP; Wed, 28 Jan 2009 09:18:11 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Wed, 28 Jan 2009 09:18:11 -0800 (PST) From: Barney Cordoba To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <20490.74948.qm@web63901.mail.re1.yahoo.com> Cc: Subject: SATA drive device moving on 8.0 current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: barney_cordoba@yahoo.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, 28 Jan 2009 17:18:14 -0000 I booted 8.0-current on a machine that was running 7 and the SATA drive came up as ad4 instead of ad8 (as it is detected in 7). This is the case was loading GENERIC. This is going to present a serious problem doing field upgrades as its expected that fstab will be the same. What is the reason for the change and is there any way to make it compatible with device detection in 7? Barney From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 17:47:51 2009 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 5656A106566C for ; Wed, 28 Jan 2009 17:47:51 +0000 (UTC) (envelope-from g.veniamin@googlemail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.freebsd.org (Postfix) with ESMTP id D87FE8FC08 for ; Wed, 28 Jan 2009 17:47:50 +0000 (UTC) (envelope-from g.veniamin@googlemail.com) Received: by ug-out-1314.google.com with SMTP id 30so297381ugs.39 for ; Wed, 28 Jan 2009 09:47:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=ftJZXnnkaknp6Octke+hqSi9DVqGB9f+rhqWUajuOJM=; b=SIv4vGMqCvOx7AOFD0BWz1R6PzcsoIKFRlUQROeMYB2qwChSPpEOpdKD+9JmvO0Fox Zz9gKU4vI9ql4lEQGqZS7wy0uPj4aELSRV2Ydaugv2BC23EIAUBcrYItuFSE7bk8l15F dtY+blkjBdtd9gsnxzpfWsinnwg+VLOiSS2/g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=tMIlMLCZ8LKPmGCAr3Jq0v6T2lnqhN0+P5V2laBa1jOpHOl81WW9FRU1WecEFKCsT9 YqvdexF+hRQmmlSeEzWaDBRwtbpB0klIctnSGm7hrbzBI/GAfobiWccN6JqFsWZ6J5O7 k9q7uBz3I+CMTCDNRy9769rbU8g/WbvEsCUCc= Received: by 10.103.117.8 with SMTP id u8mr2132655mum.123.1233163125473; Wed, 28 Jan 2009 09:18:45 -0800 (PST) Received: from ss.su (zloidemon.kraslan.ru [94.78.205.21]) by mx.google.com with ESMTPS id 1sm48786790nfv.49.2009.01.28.09.18.43 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 28 Jan 2009 09:18:44 -0800 (PST) Message-ID: <49809370.7090304@gmail.com> Date: Thu, 29 Jan 2009 00:18:40 +0700 From: Gvozdikov Veniamin User-Agent: Thunderbird 2.0.0.19 (X11/20090116) MIME-Version: 1.0 To: current@FreeBSD.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: completely stopped work on the ROOT zfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 17:47:51 -0000 I read http://wiki.freebsd.org/ZFSTuningGuide http://wiki.freebsd.org/ZFSKnownProblems set up with defferent amount of memory in a month. file system completely stops its work, even if not very large loads. do not panic the kernel and core file. uname -a FreeBSD ss.su 8.0-CURRENT FreeBSD 8.0-CURRENT #1 r187593: Fri Jan 23 22:58:42 KRAT 2009 zloiadmin@ss.su:/usr/obj/usr/src/sys/zl0_J16 i386 option in my kernel options KVA_PAGES=512 real memory = 2112749568 (2014 MB) avail memory = 2056982528 (1961 MB) ad0: 114473MB at ata0-master UDMA100 ZFS filesystem version 13 ZFS storage pool version 13 acd0: DVDR at ata1-master PIO4 WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from zfs:h loader.conf zfs_load=YES vfs.root.mountfrom="zfs:h" vm.kmem_size="1536M" modify the values of 512 to 1536 vm.kmem_size_max="1536M" and here vfs.zfs.arc_max="150M" of 50 to 700 vfs.zfs.vdev.cache.size="5M" of 1 to 50 vfs.zfs.prefetch_disable="1" vfs.zfs.zil_disable="1" i use script on http://wiki.freebsd.org/ZFSTuningGuide TEXT=12481192, 11,903 MB DATA=634163200, 604,785 MB TOTAL=646644392, 616,688 MB how to get the core-file, or to solve this problem? From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 17:52:32 2009 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 309041065679 for ; Wed, 28 Jan 2009 17:52:32 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.freebsd.org (Postfix) with ESMTP id E0FFB8FC18 for ; Wed, 28 Jan 2009 17:52:31 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.3/8.14.3) with ESMTP id n0SHqVQD061859 for ; Wed, 28 Jan 2009 09:52:31 -0800 (PST) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.3/8.14.3/Submit) id n0SHqVGE061858 for current@freebsd.org; Wed, 28 Jan 2009 09:52:31 -0800 (PST) (envelope-from david) Date: Wed, 28 Jan 2009 09:52:31 -0800 From: David Wolfskill To: current@freebsd.org Message-ID: <20090128175231.GR90849@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , current@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1CdFvSKLaAhspqc3" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: Panic from wpa_supplicant in uma_large_free() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 17:52:32 -0000 --1CdFvSKLaAhspqc3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable After updating HEAD to around r187816 (I'm still using CVS), I get the following on my laptop (which makes an attempt to use wpa_supplicant): <118>/dev/ad0s4e: FILE SYSTEM CLEAN; SKIPPING CHECKS <118>/dev/ad0s4e: clean, 836915 free (2867 frags, 104256 blocks, 0.3% fragm= entation) wlan0: bpf attached wlan0: Ethernet address: 00:05:3c:09:86:46 wlan0: bpf attached <118>Starting wpa_supplicant. <118>ioctl[SIOCG80211, op 98, len 32]: Bad address <118>/etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant <118>Starting Network: lo0. <118>ifconfig: <118>create: bad value <118> <118>Starting wpa_supplicant. Fatal trap 12: page fault while in kernel mode cpuid =3D 0; apic id =3D 00 fault virtual address =3D 0xbfdb9858 fault code =3D supervisor read, page not present instruction pointer =3D 0x20:0xc0a507f5 stack pointer =3D 0x28:0xc4b60a60 frame pointer =3D 0x28:0xc4b60a70 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 863 (wpa_supplicant) db> bt Tracing pid 863 tid 100055 td 0xc520a480 uma_large_free(c5334e20,c0b14908,20,e,c5334dc0,...) at uma_large_free+0x35 free(c5334dc0,c0ca6660,c0,c5334dd0,c5334de0,...) at free+0xdb ieee80211_ioctl_getdevcaps(c4b60ae8,c0805bbc,c4e75a9c,1,c4d20340,...) at ie= ee80211_ioctl_getdevcaps+0xda ieee80211_ioctl_get80211(c0bca91c,c0bb5139,3,c520a480,c4b60b68,...) at ieee= 80211_ioctl_get80211+0x930 ieee80211_ioctl(c51a8c00,c01c69eb,c5334de0,c0e6b644,c51a8c00,...) at ieee80= 211_ioctl+0x2b7 in_control(c532b930,c01c69eb,c5334de0,c51a8c00,c520a480,...) at in_control+= 0xe0a ifioctl(c532b930,c01c69eb,c5334de0,c520a480,c01c69eb,...) at ifioctl+0x322 soo_ioctl(c51fe700,c01c69eb,c5334de0,c4d3c900,c520a480,...) at soo_ioctl+0x= 397 kern_ioctl(c520a480,3,c01c69eb,c5334de0,184d9e0,...) at kern_ioctl+0x1dd ioctl(c520a480,c4b60cf8,c,c0b8dabb,c0ca1db0,...) at ioctl+0x134 syscall(c4b60d38) at syscall+0x2a3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (54, FreeBSD ELF32, ioctl), eip =3D 0x28372c23, esp =3D 0xbfbfe= c9c, ebp =3D 0xbfbfece8 --- db>=20 My build machine -- which does not attempt to use wpa_supplicant -- is using a copy of the same sources, did not show a problem, and had no trouble with its (fxp) NIC: freebeast(8.0-C)[1] uname -a FreeBSD freebeast.catwhisker.org 8.0-CURRENT FreeBSD 8.0-CURRENT #240: Wed = Jan 28 07:07:31 PST 2009 root@freebeast.catwhisker.org:/common/S4/obj/u= sr/src/sys/FREEBEAST i386 freebeast(8.0-C)[2] netstat -nif inet Name Mtu Network Address Ipkts Ierrs Opkts Oerrs = Coll fxp0 1500 172.16.8.0/24 172.16.8.10 111 - 88 - = - lo0 16384 127.0.0.0/8 127.0.0.1 4 - 4 - = - freebeast(8.0-C)[3]=20 And it shows that wpa_supplicant was rebuilt today: freebeast(8.0-C)[3] ls -lT `which wpa_supplicant` -r-xr-xr-x 1 root wheel 272248 Jan 28 09:43:25 2009 /usr/sbin/wpa_suppli= cant freebeast(8.0-C)[4]=20 Since I used the same sources for each machine, and the same commands to perform the source upgrade (from yesterday's HEAD), I believe wpa_supplicant on the laptop was also updated today, per Sam's message. Peace, david --=20 David H. Wolfskill david@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --1CdFvSKLaAhspqc3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEUEARECAAYFAkmAm14ACgkQmprOCmdXAD2xvACfRv1TNOj4GL5nO1RGa5IAfVTE 3h0AmK6N+zwfd/Zk462aKB+WNAGTJPE= =SCpX -----END PGP SIGNATURE----- --1CdFvSKLaAhspqc3-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 18:04:39 2009 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 E51821065672 for ; Wed, 28 Jan 2009 18:04:39 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id A894E8FC14 for ; Wed, 28 Jan 2009 18:04:39 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n0SI4bVc031327 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Jan 2009 10:04:38 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <49809E35.5020400@freebsd.org> Date: Wed, 28 Jan 2009 10:04:37 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: David Wolfskill , current@freebsd.org References: <20090128175231.GR90849@albert.catwhisker.org> In-Reply-To: <20090128175231.GR90849@albert.catwhisker.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-Rhyolite-Metrics: ebb.errno.com; whitelist Cc: Subject: Re: Panic from wpa_supplicant in uma_large_free() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 18:04:40 -0000 David Wolfskill wrote: > After updating HEAD to around r187816 (I'm still using CVS), I get the > following on my laptop (which makes an attempt to use wpa_supplicant): > > Can you try reverting my wpa_supplicant update yesterday? Sam From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 18:06:01 2009 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 E48281065674 for ; Wed, 28 Jan 2009 18:06:01 +0000 (UTC) (envelope-from michiel@boland.org) Received: from smtp-vbr4.xs4all.nl (smtp-vbr4.xs4all.nl [194.109.24.24]) by mx1.freebsd.org (Postfix) with ESMTP id 8248A8FC16 for ; Wed, 28 Jan 2009 18:06:01 +0000 (UTC) (envelope-from michiel@boland.org) Received: from aja.boland.org (91-43-215.ftth.xms.internl.net [82.215.43.91]) (authenticated bits=0) by smtp-vbr4.xs4all.nl (8.13.8/8.13.8) with ESMTP id n0SHq5vK072567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Jan 2009 18:52:06 +0100 (CET) (envelope-from michiel@boland.org) Message-ID: <49809B45.1000703@boland.org> Date: Wed, 28 Jan 2009 18:52:05 +0100 From: Michiel Boland User-Agent: Thunderbird 2.0.0.19 (X11/20090125) MIME-Version: 1.0 To: Sean Bruno References: <1233098540.2494.6.camel@localhost.localdomain> In-Reply-To: <1233098540.2494.6.camel@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner Cc: current@freebsd.org Subject: Re: NFS mounts dissapearing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 18:06:02 -0000 Sean Bruno wrote: > I've noted that my NFS mount of a directory is vanishing periodically > under -current. I am unable to unmount/remount the directory and the > system returns Permission Denied on all attempts to access the > directory. > > Is this something that is known and being investigated? FWIW I am seeing this too, except that I can still umount/remount. It appears to me that TCP connections to remote nfsd use a privileged source port initially, but if the connection is severed and reestablished later the source port is no longer < 1024. Client is -CURRENT, server is solaris with nfssrv:nfs_portmon=1. Cheers Michiel From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 18:06:02 2009 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 5B16D1065675 for ; Wed, 28 Jan 2009 18:06:02 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 10B508FC17 for ; Wed, 28 Jan 2009 18:06:02 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n0SI60BW031346 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Jan 2009 10:06:00 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <49809E88.9060201@freebsd.org> Date: Wed, 28 Jan 2009 10:06:00 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: David Wolfskill , current@freebsd.org References: <20090128175231.GR90849@albert.catwhisker.org> In-Reply-To: <20090128175231.GR90849@albert.catwhisker.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-Rhyolite-Metrics: ebb.errno.com; whitelist Cc: Subject: Re: Panic from wpa_supplicant in uma_large_free() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 18:06:03 -0000 David Wolfskill wrote: > After updating HEAD to around r187816 (I'm still using CVS), I get the > following on my laptop (which makes an attempt to use wpa_supplicant): > > <118>/dev/ad0s4e: FILE SYSTEM CLEAN; SKIPPING CHECKS > <118>/dev/ad0s4e: clean, 836915 free (2867 frags, 104256 blocks, 0.3% fragmentation) > wlan0: bpf attached > wlan0: Ethernet address: 00:05:3c:09:86:46 > wlan0: bpf attached > <118>Starting wpa_supplicant. > <118>ioctl[SIOCG80211, op 98, len 32]: Bad address > <118>/etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant > <118>Starting Network: lo0. > <118>ifconfig: > <118>create: bad value > <118> > <118>Starting wpa_supplicant. > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xbfdb9858 > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc0a507f5 > stack pointer = 0x28:0xc4b60a60 > frame pointer = 0x28:0xc4b60a70 > 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 = 863 (wpa_supplicant) > > db> bt > Tracing pid 863 tid 100055 td 0xc520a480 > uma_large_free(c5334e20,c0b14908,20,e,c5334dc0,...) at uma_large_free+0x35 > free(c5334dc0,c0ca6660,c0,c5334dd0,c5334de0,...) at free+0xdb > ieee80211_ioctl_getdevcaps(c4b60ae8,c0805bbc,c4e75a9c,1,c4d20340,...) at ieee80211_ioctl_getdevcaps+0xda > ieee80211_ioctl_get80211(c0bca91c,c0bb5139,3,c520a480,c4b60b68,...) at ieee80211_ioctl_get80211+0x930 > ieee80211_ioctl(c51a8c00,c01c69eb,c5334de0,c0e6b644,c51a8c00,...) at ieee80211_ioctl+0x2b7 > in_control(c532b930,c01c69eb,c5334de0,c51a8c00,c520a480,...) at in_control+0xe0a > ifioctl(c532b930,c01c69eb,c5334de0,c520a480,c01c69eb,...) at ifioctl+0x322 > soo_ioctl(c51fe700,c01c69eb,c5334de0,c4d3c900,c520a480,...) at soo_ioctl+0x397 > kern_ioctl(c520a480,3,c01c69eb,c5334de0,184d9e0,...) at kern_ioctl+0x1dd > ioctl(c520a480,c4b60cf8,c,c0b8dabb,c0ca1db0,...) at ioctl+0x134 > syscall(c4b60d38) at syscall+0x2a3 > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x28372c23, esp = 0xbfbfec9c, ebp = 0xbfbfece8 --- > db> > > Actually this is my bad. It's the changes to getdevcaps. Let me look at it. Sam From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 18:07:29 2009 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 CFC4D10657B5 for ; Wed, 28 Jan 2009 18:07:29 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: from iron2.pdx.net (iron2.pdx.net [69.64.224.71]) by mx1.freebsd.org (Postfix) with ESMTP id 935D48FC21 for ; Wed, 28 Jan 2009 18:07:29 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: (qmail 19431 invoked from network); 28 Jan 2009 10:07:28 -0800 Received: from 069-064-235-060.pdx.net (HELO ?192.168.1.51?) (69.64.235.60) by iron2.pdx.net with SMTP; 28 Jan 2009 10:07:28 -0800 From: Sean Bruno To: Michiel Boland In-Reply-To: <49809B45.1000703@boland.org> References: <1233098540.2494.6.camel@localhost.localdomain> <49809B45.1000703@boland.org> Content-Type: text/plain Date: Wed, 28 Jan 2009 10:07:28 -0800 Message-Id: <1233166048.3592.1.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 (2.24.3-1.fc10) Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: NFS mounts dissapearing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 18:07:30 -0000 On Wed, 2009-01-28 at 18:52 +0100, Michiel Boland wrote: > Sean Bruno wrote: > > I've noted that my NFS mount of a directory is vanishing periodically > > under -current. I am unable to unmount/remount the directory and the > > system returns Permission Denied on all attempts to access the > > directory. > > > > Is this something that is known and being investigated? > > FWIW I am seeing this too, except that I can still umount/remount. It appears to > me that TCP connections to remote nfsd use a privileged source port initially, > but if the connection is severed and reestablished later the source port is no > longer < 1024. Client is -CURRENT, server is solaris with nfssrv:nfs_portmon=1. > > Cheers > Michiel Here client is -CURRENT, server is linux with default NFS settings. linux sysctl settings: sysctl -a |grep nfs fs.nfs.nlm_grace_period = 0 fs.nfs.nlm_timeout = 10 fs.nfs.nlm_udpport = 0 fs.nfs.nlm_tcpport = 0 fs.nfs.nsm_use_hostnames = 0 fs.nfs.nsm_local_state = 0 fs.nfs.nfs_callback_tcpport = 0 fs.nfs.idmap_cache_timeout = 600 fs.nfs.nfs_mountpoint_timeout = 500 fs.nfs.nfs_congestion_kb = 79232 sunrpc.nfs_debug = 0 sunrpc.nfsd_debug = 0 Sean From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 15:53:44 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2AB021065673 for ; Wed, 28 Jan 2009 15:53:44 +0000 (UTC) (envelope-from talon@lpthe.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id B2E958FC0C for ; Wed, 28 Jan 2009 15:53:43 +0000 (UTC) (envelope-from talon@lpthe.jussieu.fr) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.14.3/jtpda-5.4) with ESMTP id n0SFrfM3061694 for ; Wed, 28 Jan 2009 16:53:42 +0100 (CET) X-Ids: 166 Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41]) by parthe.lpthe.jussieu.fr (Postfix) with ESMTP id 7327E89CF6 for ; Wed, 28 Jan 2009 16:53:40 +0100 (CET) Received: by niobe.lpthe.jussieu.fr (Postfix, from userid 2005) id 4821151; Wed, 28 Jan 2009 16:53:40 +0100 (CET) Date: Wed, 28 Jan 2009 16:53:40 +0100 From: Michel Talon To: freebsd-current@freebsd.org Message-ID: <20090128155340.GA75143@lpthe.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (shiva.jussieu.fr [134.157.0.166]); Wed, 28 Jan 2009 16:53:42 +0100 (CET) X-Virus-Scanned: ClamAV 0.94.2/8914/Wed Jan 28 07:40:00 2009 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at jchkmail.jussieu.fr with ID 49807F85.004 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 49807F85.004/134.157.10.1/parthe.lpthe.jussieu.fr/parthe.lpthe.jussieu.fr/ X-j-chkmail-Score: MSGID : 49807F85.004 on jchkmail.jussieu.fr : j-chkmail score : . : R=. U=. O=. B=0.023 -> S=0.023 X-j-chkmail-Status: Ham X-Mailman-Approved-At: Wed, 28 Jan 2009 18:36:09 +0000 Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 15:53:44 -0000 pluknet wrote: > I found this article today. It answers some questions about GPLv3. > > http://www.fsf.org/licensing/licenses/gcc-exception-faq.html Indeed this is exactly what i said, there are exemptions for code that the compiler brings into the executable (notably this is particularly the case for g++) such that using gcc has absolutely no bearing on the license of the resulting binary. Hence switching to a GPL V3 version of gcc has zero impact on the BSD character of FreeBSD. I don't know if the same is true for binutils however. -- Michel TALON From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 18:40:35 2009 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 53C0C1065676 for ; Wed, 28 Jan 2009 18:40:35 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 16DE08FC27 for ; Wed, 28 Jan 2009 18:40:35 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n0SIeX3L031651 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Jan 2009 10:40:33 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <4980A6A1.8070406@freebsd.org> Date: Wed, 28 Jan 2009 10:40:33 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: David Wolfskill , current@freebsd.org References: <20090128175231.GR90849@albert.catwhisker.org> In-Reply-To: <20090128175231.GR90849@albert.catwhisker.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-Rhyolite-Metrics: ebb.errno.com; whitelist Cc: Subject: Re: Panic from wpa_supplicant in uma_large_free() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 18:40:36 -0000 David Wolfskill wrote: > After updating HEAD to around r187816 (I'm still using CVS), I get the > following on my laptop (which makes an attempt to use wpa_supplicant): > Please update. I'm guessing you've got a non-ath wireless device which would explain why you tripped over this (bad me, didn't test w/ anything but ath). Sam From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 18:50:34 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7583B1065730 for ; Wed, 28 Jan 2009 18:50:34 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by mx1.freebsd.org (Postfix) with ESMTP id 586A48FC1E for ; Wed, 28 Jan 2009 18:50:34 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay11.apple.com (relay11.apple.com [17.128.113.48]) by mail-out4.apple.com (Postfix) with ESMTP id 4E2B0518B8AD; Wed, 28 Jan 2009 10:50:34 -0800 (PST) Received: from relay11.apple.com (unknown [127.0.0.1]) by relay11.apple.com (Symantec Brightmail Gateway) with ESMTP id 319B245C0002; Wed, 28 Jan 2009 10:50:34 -0800 (PST) X-AuditID: 11807130-a8090bb000000fcd-96-4980a8fad2d3 Received: from cswiger1.apple.com (cswiger1.apple.com [17.227.140.124]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay11.apple.com (Apple SCV relay) with ESMTP id 0653428095; Wed, 28 Jan 2009 10:50:34 -0800 (PST) Message-Id: <7508A5B5-C6D2-498A-AEA1-D84E85F1D743@mac.com> From: Chuck Swiger To: Michel Talon In-Reply-To: <20090128155340.GA75143@lpthe.jussieu.fr> Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v930.3) Date: Wed, 28 Jan 2009 10:50:33 -0800 References: <20090128155340.GA75143@lpthe.jussieu.fr> X-Mailer: Apple Mail (2.930.3) X-Brightmail-Tracker: AAAAAA== Cc: freebsd-current@freebsd.org Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 18:50:35 -0000 On Jan 28, 2009, at 7:53 AM, Michel Talon wrote: > pluknet wrote: >> I found this article today. It answers some questions about GPLv3. >> >> http://www.fsf.org/licensing/licenses/gcc-exception-faq.html > > Indeed this is exactly what i said, there are exemptions for code that > the compiler brings into the executable (notably this is particularly > the case for g++) such that using gcc has absolutely no bearing on the > license of the resulting binary. The relevant bit I saw from that page was: > As long as you use an Eligible Compilation Process, then you have =20 > permission to take the Target Code that GCC generates and propagate =20= > it =93under terms of your choice.=94 If you did use GPL-incompatible =20= > software in conjunction with GCC during the Compilation Process, you =20= > would not be able to take advantage of this permission. Since all of =20= > the object code that GCC generates is derived from these GPLed =20 > libraries, that means you would be required to follow the terms of =20 > the GPL when propagating any of that object code. You could not use =20= > GCC to develop your own GPL-incompatible software. Evidently, the FSF is now claiming that all object code produced from =20= GCC 4.2.2 and later is GPLv3-licensed, and only their exception =20 permits you to distribute executables compiled using an "Eligible =20 Compilation Process" under the terms of some other license. I wonder if they make this claim even if -nostartfiles, -nostdlib and/=20= or -nodefaultlibs options are used? Regards, --=20 -Chuck From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 19:17:36 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E8D01065670 for ; Wed, 28 Jan 2009 19:17:36 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id 87F708FC24 for ; Wed, 28 Jan 2009 19:17:35 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: by ewy14 with SMTP id 14so4602280ewy.19 for ; Wed, 28 Jan 2009 11:17:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=O64Jr5QDYaIyN4CwRjJELJ4n28tG0qDqzpCDQDWgWyo=; b=d9T2Y1iwgUCxGRQtapFCRdNTjJrLpAYJes8taCsvzEkbaHWWbMsnNxGvoktrmjfsDI 0t5iGOx5Q7H7bPBIkzpJ/VL6TEKFKHkvmMtUW7DoDo6wYNQEhhL3br2Hj6OJCYzyI7p3 Xa+sW9i5lcNZRTXpC2HBO07dgwHPfh32gNtjo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; b=cUfVBmRjlHMGReahDnr4UBbmt++fA+GjU1aL7QnUTVD8pl/4rtWDL/utxmaeAd3eF3 2PXe+DFTPr3BUZXUoCmAydZ63VWF6rum0dADM1n+mM80xSEwCcohvTaOkCoI9CFhGrl7 JcF/3hw2gBobZ1ecpUsZKJtJI7baxHPOoAuM0= MIME-Version: 1.0 Sender: asmrookie@gmail.com Received: by 10.86.26.11 with SMTP id 11mr238187fgz.40.1233168300745; Wed, 28 Jan 2009 10:45:00 -0800 (PST) Date: Wed, 28 Jan 2009 19:45:00 +0100 X-Google-Sender-Auth: 000fc2ed6eadc845 Message-ID: <3bbf2fe10901281045s7e3280dep5a26df6541595cfe@mail.gmail.com> From: Attilio Rao To: FreeBSD Current , freebsd-fs@freebsd.org Content-Type: multipart/mixed; boundary=000e0cd286e283a38b04618f5e64 Cc: bp@freebsd.org, Robert Watson Subject: [PATCH] improving netncp locking X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 19:17:37 -0000 --000e0cd286e283a38b04618f5e64 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Attached there is a patch that fixes netncp locking. Actually, netncp tries to drain connections without any protection for the nc_id field (which is supposed to discriminate between a valid connection and one under draining). Also, the drain still uses loose ending LK_DRAIN. This patch adds correct locking for draining path adding an interlock, control flags, a refcount and using it accordingly. Ultimately 2 locks are switched to be sx as they don't rely on any particular lockmgr feature. The patch compiles and boots ok, but if someone could test and review it I would appreciate a lot. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein --000e0cd286e283a38b04618f5e64 Content-Type: text/x-diff; charset=US-ASCII; name="netncp.diff" Content-Disposition: attachment; filename="netncp.diff" Content-Transfer-Encoding: base64 X-Attachment-Id: f_fqickktn0 LS0tIC91c3Ivc3JjL3N5cy9uZXRuY3AvbmNwX2Nvbm4uYwkyMDA5LTAxLTEwIDEzOjM5OjQ4LjAw MDAwMDAwMCArMDEwMAorKysgc3lzL25ldG5jcC9uY3BfY29ubi5jCTIwMDktMDEtMjggMTk6MjA6 MDIuMDAwMDAwMDAwICswMTAwCkBAIC0zOCwxMSArMzgsMTMgQEAKICNpbmNsdWRlIDxzeXMvcGFy YW0uaD4KICNpbmNsdWRlIDxzeXMvc3lzdG0uaD4KICNpbmNsdWRlIDxzeXMva2VybmVsLmg+Cisj aW5jbHVkZSA8c3lzL2xvY2suaD4KICNpbmNsdWRlIDxzeXMvbWFsbG9jLmg+CisjaW5jbHVkZSA8 c3lzL211dGV4Lmg+CiAjaW5jbHVkZSA8c3lzL3ByaXYuaD4KICNpbmNsdWRlIDxzeXMvcHJvYy5o PgotI2luY2x1ZGUgPHN5cy9sb2NrLmg+CiAjaW5jbHVkZSA8c3lzL3N5c2N0bC5oPgorI2luY2x1 ZGUgPHN5cy9zeC5oPgogCiAjaW5jbHVkZSA8bmV0bmNwL25jcC5oPgogI2luY2x1ZGUgPG5ldG5j cC9ud2Vycm9yLmg+CkBAIC01MSw2ICs1MywxNyBAQAogI2luY2x1ZGUgPG5ldG5jcC9uY3Bfc29j ay5oPgogI2luY2x1ZGUgPG5ldG5jcC9uY3BfbmNwLmg+CiAKKyNkZWZpbmUJTkNQX1JFRkxDTlQo bmNwKQkoKG5jcCktPm5jX2xvY2tjbnQrKykKKyNkZWZpbmUJTkNQX1JFTExDTlQobmNwKSBkbyB7 CQkJCQkJXAorCShuY3ApLT5uY19sb2NrY250LS07CQkJCQkJXAorCWlmICgobmNwKS0+bmNfbG9j a2NudCA9PSAwICYmCQkJCQlcCisJICAgICgobmNwKS0+ZmxhZ3MgJiBOQ1BGTF9EUkFJTklORykg IT0gMCkgewkJCVwKKwkJTVBBU1MoKG5jcCktPm5jX2lkID09IDApOwkJCQlcCisJCShuY3ApLT5m bGFncyAmPSB+TkNQRkxfRFJBSU5JTkc7CQkJXAorCQl3YWtldXAoJihuY3ApLT5uY19sb2NrY250 KTsJCQkJXAorCX0JCQkJCQkJCVwKK30gd2hpbGUoMCkKKwogU0xJU1RfSEVBRChuY3BfaGFuZGxl X2hlYWQsbmNwX2hhbmRsZSk7CiAKIGludCBuY3BfYnVyc3RfZW5hYmxlZCA9IDE7CkBAIC01OCwx NSArNzEsMTYgQEAKIHN0cnVjdCBuY3BfY29ubl9oZWFkIGNvbm5fbGlzdD17TlVMTH07CiBzdGF0 aWMgaW50IG5jcF9jb25uX2NudCA9IDA7CiBzdGF0aWMgaW50IG5jcF9uZXh0X3JlZiA9IDE7Ci1z dGF0aWMgc3RydWN0IGxvY2sgbGlzdGxvY2s7CitzdGF0aWMgc3RydWN0IHN4IGxpc3Rsb2NrOwog CiBzdHJ1Y3QgbmNwX2hhbmRsZV9oZWFkIGxobGlzdD17TlVMTH07CiBzdGF0aWMgaW50IG5jcF9u ZXh0X2hhbmRsZSA9IDE7Ci1zdGF0aWMgc3RydWN0IGxvY2sgbGhsb2NrOworc3RhdGljIHN0cnVj dCBzeCBsaGxvY2s7CiAKIHN0YXRpYyBpbnQgbmNwX3N5c2N0bF9jb25uc3RhdChTWVNDVExfSEFO RExFUl9BUkdTKTsKIHN0YXRpYyBpbnQgbmNwX2Nvbm5fbG9ja19hbnkoc3RydWN0IG5jcF9jb25u ICpjb25uLCBzdHJ1Y3QgdGhyZWFkICp0ZCwKICAgICBzdHJ1Y3QgdWNyZWQgKmNyZWQpOworc3Rh dGljIHZvaWQgbmNwX2Nvbm5fbG9ja19hc3NlcnQoc3RydWN0IG5jcF9jb25uICpjb25uLCBpbnQg d2hhdCk7CiAKIFNZU0NUTF9ERUNMKF9uZXRfbmNwKTsKIFNZU0NUTF9JTlQgKF9uZXRfbmNwLCBP SURfQVVUTywgYnVyc3RfZW5hYmxlZCwgQ1RMRkxBR19SRCwgJm5jcF9idXJzdF9lbmFibGVkLCAw LCAiIik7CkBAIC03OSw4ICs5Myw4IEBACiBpbnQKIG5jcF9jb25uX2luaXQodm9pZCkKIHsKLQls b2NraW5pdCgmbGlzdGxvY2ssIFBTT0NLLCAibmNwbGwiLCAwLCAwKTsKLQlsb2NraW5pdCgmbGhs b2NrLCBQU09DSywgIm5jcGxoIiwgMCwgMCk7CisJc3hfaW5pdF9mbGFncygmbGlzdGxvY2ssICJu Y3BsbCIsIFNYX1JFQ1VSU0UpOworCXN4X2luaXQoJmxobG9jaywgIm5jcGxoIik7CiAJcmV0dXJu IDA7CiB9CiAKQEAgLTkxLDIxICsxMDUsNTEgQEAKIAkJTkNQRVJST1IoIlRoZXJlIGFyZSAlZCBj b25uZWN0aW9ucyBhY3RpdmVcbiIsIG5jcF9jb25uX2NudCk7CiAJCXJldHVybiBFQlVTWTsKIAl9 Ci0JbG9ja2Rlc3Ryb3koJmxpc3Rsb2NrKTsKLQlsb2NrZGVzdHJveSgmbGhsb2NrKTsKKwlzeF9k ZXN0cm95KCZsaXN0bG9jayk7CisJc3hfZGVzdHJveSgmbGhsb2NrKTsKIAlyZXR1cm4gMDsKIH0K IAordm9pZAorbmNwX2Nvbm5fc2xvY2tsaXN0KCkKK3sKKworCXN4X3Nsb2NrKCZsaXN0bG9jayk7 Cit9CisKK3ZvaWQKK25jcF9jb25uX3hsb2NrbGlzdCgpCit7CisKKwlzeF94bG9jaygmbGlzdGxv Y2spOworfQorCiBpbnQKLW5jcF9jb25uX2xvY2tsaXN0KGludCBmbGFncywgc3RydWN0IHRocmVh ZCAqdGQpCituY3BfY29ubl90cnlfc2xvY2tsaXN0KCkKIHsKLQlyZXR1cm4gbG9ja21ncigmbGlz dGxvY2ssIGZsYWdzIHwgTEtfQ0FOUkVDVVJTRSwgMCk7CisKKwlyZXR1cm4gKHN4X3RyeV9zbG9j aygmbGlzdGxvY2spKTsKK30KKworaW50CituY3BfY29ubl90cnlfeGxvY2tsaXN0KCkKK3sKKwor CXJldHVybiAoc3hfdHJ5X3hsb2NrKCZsaXN0bG9jaykpOwogfQogCiB2b2lkCi1uY3BfY29ubl91 bmxvY2tsaXN0KHN0cnVjdCB0aHJlYWQgKnRkKQorbmNwX2Nvbm5fc3VubG9ja2xpc3QoKQogewot CWxvY2ttZ3IoJmxpc3Rsb2NrLCBMS19SRUxFQVNFLCAwKTsKKworCXN4X3N1bmxvY2soJmxpc3Rs b2NrKTsKK30KKwordm9pZAorbmNwX2Nvbm5feHVubG9ja2xpc3QoKQoreworCisJc3hfeHVubG9j aygmbGlzdGxvY2spOwogfQogCiBpbnQKQEAgLTEyOCwxNyArMTcyLDMxIEBACiB7CiAJaW50IGVy cm9yOwogCi0JaWYgKGNvbm4tPm5jX2lkID09IDApIHJldHVybiBFQUNDRVM7Ci0JZXJyb3IgPSBs b2NrbWdyKCZjb25uLT5uY19sb2NrLCBMS19FWENMVVNJVkUgfCBMS19DQU5SRUNVUlNFLCAwKTsK LQlpZiAoZXJyb3IgPT0gRVJFU1RBUlQpCisJTkNQX0lMT0NLKGNvbm4pOworCWlmIChjb25uLT5u Y19pZCA9PSAwKQorCQlyZXR1cm4gRUFDQ0VTOworCU5DUF9SRUZMQ05UKGNvbm4pOworCWVycm9y ID0gbG9ja21ncigmY29ubi0+bmNfbG9jaywgTEtfRVhDTFVTSVZFIHwgTEtfQ0FOUkVDVVJTRSB8 CisJICAgIExLX0lOVEVSTE9DSywgTkNQX01UWChjb25uKSk7CisJaWYgKGVycm9yID09IEVSRVNU QVJUKSB7CisJCU5DUF9JTE9DSyhjb25uKTsKKwkJTkNQX1JFTExDTlQoY29ubik7CisJCU5DUF9J VU5MT0NLKGNvbm4pOwogCQlyZXR1cm4gRUlOVFI7CisJfQogCWVycm9yID0gbmNwX2Noa2ludHIo Y29ubiwgdGQpOwogCWlmIChlcnJvcikgeworCQlOQ1BfSUxPQ0soY29ubik7CisJCU5DUF9SRUxM Q05UKGNvbm4pOworCQlOQ1BfSVVOTE9DSyhjb25uKTsKIAkJbG9ja21ncigmY29ubi0+bmNfbG9j aywgTEtfUkVMRUFTRSwgMCk7CiAJCXJldHVybiBlcnJvcjsKIAl9CiAKIAlpZiAoY29ubi0+bmNf aWQgPT0gMCkgeworCQlOQ1BfSUxPQ0soY29ubik7CisJCU5DUF9SRUxMQ05UKGNvbm4pOworCQlO Q1BfSVVOTE9DSyhjb25uKTsKIAkJbG9ja21ncigmY29ubi0+bmNfbG9jaywgTEtfUkVMRUFTRSwg MCk7CiAJCXJldHVybiBFQUNDRVM7CiAJfQpAQCAtMTQ3LDYgKzIwNSwxMyBAQAogCXJldHVybiAw OwogfQogCitzdGF0aWMgdm9pZAorbmNwX2Nvbm5fbG9ja19hc3NlcnQoc3RydWN0IG5jcF9jb25u ICpjb25uLCBpbnQgd2hhdCkKK3sKKworCWxvY2ttZ3JfYXNzZXJ0KCZjb25uLT5uY19sb2NrLCB3 aGF0KTsKK30KKwogaW50CiBuY3BfY29ubl9sb2NrKHN0cnVjdCBuY3BfY29ubiAqY29ubiwgc3Ry dWN0IHRocmVhZCAqdGQsIHN0cnVjdCB1Y3JlZCAqY3JlZCwgaW50IG1vZGUpCiB7CkBAIC0xNjcs MTEgKzIzMiwxMSBAQAogCiAJZXJyb3IgPSBuY3BfY29ubl9hY2Nlc3MoY29ubiwgY3JlZCwgbW9k ZSk7CiAJaWYgKGVycm9yKSB7Ci0JCW5jcF9jb25uX3VubG9ja2xpc3QodGQpOworCQluY3BfY29u bl9zdW5sb2NrbGlzdCgpOwogCQlyZXR1cm4gZXJyb3I7CiAJfQogCWNvbm4tPm5jX2x3YW50Kys7 Ci0JbmNwX2Nvbm5fdW5sb2NrbGlzdCh0ZCk7CisJbmNwX2Nvbm5fc3VubG9ja2xpc3QoKTsKIAll cnJvciA9IG5jcF9jb25uX2xvY2tfYW55KGNvbm4sIHRkLCBjcmVkKTsKIAljb25uLT5uY19sd2Fu dC0tOwogCWlmIChjb25uLT5uY19sd2FudCA9PSAwKSB7CkBAIC0xODMsMTkgKzI0OCwxMSBAQAog dm9pZAogbmNwX2Nvbm5fdW5sb2NrKHN0cnVjdCBuY3BfY29ubiAqY29ubiwgc3RydWN0IHRocmVh ZCAqdGQpCiB7Ci0JLyoKLQkgKiBub3RlLCB0aGF0IExLX1JFTEFTRSB3aWxsIGRvIHdha2V1cCgp IGluc3RlYWQgb2Ygd2FrZXVwX29uZSgpLgotCSAqIHRoaXMgd2lsbCBkbyBhIGxpdHRsZSBvdmVy aGVhZAotCSAqLwotCWxvY2ttZ3IoJmNvbm4tPm5jX2xvY2ssIExLX1JFTEVBU0UsIDApOwotfQog Ci1pbnQKLW5jcF9jb25uX2Fzc2VydF9sb2NrZWQoc3RydWN0IG5jcF9jb25uICpjb25uLCBjb25z dCBjaGFyICpjaGVja2VyLCBzdHJ1Y3QgdGhyZWFkICp0ZCkKLXsKLQlpZiAobG9ja3N0YXR1cygm Y29ubi0+bmNfbG9jaykgPT0gTEtfRVhDTFVTSVZFKSByZXR1cm4gMDsKLQlwcmludGYoIiVzOiBj b25uZWN0aW9uIGlzbid0IGxvY2tlZCFcbiIsIGNoZWNrZXIpOwotCXJldHVybiBFSU87CisJTkNQ X0lMT0NLKGNvbm4pOworCU5DUF9SRUxMQ05UKGNvbm4pOworCU5DUF9JVU5MT0NLKGNvbm4pOwor CWxvY2ttZ3IoJmNvbm4tPm5jX2xvY2ssIExLX1JFTEVBU0UsIDApOwogfQogCiB2b2lkCkBAIC0y NDIsNyArMjk5LDkgQEAKIAkgICAgTV9OQ1BEQVRBLCBNX1dBSVRPSyB8IE1fWkVSTyk7CiAJZXJy b3IgPSAwOwogCWxvY2tpbml0KCZuY3AtPm5jX2xvY2ssIFBaRVJPLCAibmNwbGNrIiwgMCwgMCk7 CisJbXR4X2luaXQoJm5jcC0+bmNfaWxvY2ssICJuY3BpbGNrIiwgTlVMTCwgMCk7CiAJbmNwX2Nv bm5fY250Kys7CisJbmNwLT5uY19sb2NrY250ID0gMDsKIAluY3AtPm5jX2lkID0gbmNwX25leHRf cmVmKys7CiAJbmNwLT5uY19vd25lciA9IG93bmVyOwogCW5jcC0+c2VxID0gMDsKQEAgLTI1Nyw5 ICszMTYsOSBAQAogCQluY3AtPmxpLnRpbWVvdXQgPSBOQ1BfUkVUUllfVElNRU9VVDsKIAluY3Bf Y29ubl9sb2NrX2FueShuY3AsIHRkLCBuY3AtPm5jX293bmVyKTsKIAkqY29ubiA9IG5jcDsKLQlu Y3BfY29ubl9sb2NrbGlzdChMS19FWENMVVNJVkUsIHRkKTsKKwluY3BfY29ubl94bG9ja2xpc3Qo KTsKIAlTTElTVF9JTlNFUlRfSEVBRCgmY29ubl9saXN0LG5jcCxuY19uZXh0KTsKLQluY3BfY29u bl91bmxvY2tsaXN0KHRkKTsKKwluY3BfY29ubl94dW5sb2NrbGlzdCgpOwogCXJldHVybiAoZXJy b3IpOwogfQogCkBAIC0yNzAsMjAgKzMyOSwxMiBAQAogbmNwX2Nvbm5fZnJlZShzdHJ1Y3QgbmNw X2Nvbm4gKm5jcCkKIHsKIAlzdHJ1Y3QgdGhyZWFkICp0ZDsKLQlpbnQgZXJyb3I7CiAKLQlpZiAo bmNwID09IE5VTEwpIHsKLQkJTkNQRkFUQUwoIm5jcCA9PSBOVUxMXG4iKTsKLQkJcmV0dXJuIDA7 Ci0JfQotCWlmIChuY3AtPm5jX2lkID09IDApIHsKLQkJTkNQRVJST1IoIm5jX2lkID09IDBcbiIp OwotCQlyZXR1cm4gRUFDQ0VTOwotCX0KKwlNUEFTUyhuY3AgIT0gTlVMTCk7CisJTVBBU1MobmNw LT5uY19pZCAhPSAwKTsKKwluY3BfY29ubl9sb2NrX2Fzc2VydChuY3AsIEtBX1hMT0NLRUQpOwor CiAJdGQgPSBuY3AtPnRkOwotCWVycm9yID0gbmNwX2Nvbm5fYXNzZXJ0X2xvY2tlZChuY3AsIF9f ZnVuY19fLCB0ZCk7Ci0JaWYgKGVycm9yKQotCQlyZXR1cm4gZXJyb3I7CiAJaWYgKG5jcC0+cmVm X2NudCAhPSAwIHx8IChuY3AtPmZsYWdzICYgTkNQRkxfUEVSTUFORU5UKSkKIAkJcmV0dXJuIEVC VVNZOwogCWlmIChuY3BfY29ubl9hY2Nlc3MobmNwLCBuY3AtPnVjcmVkLCBOQ1BNX1dSSVRFKSkK QEAgLTI5MiwyNiArMzQzLDI4IEBACiAJaWYgKG5jcC0+ZmxhZ3MgJiBOQ1BGTF9BVFRBQ0hFRCkK IAkJbmNwX25jcF9kaXNjb25uZWN0KG5jcCk7CiAJbmNwX3NvY2tfZGlzY29ubmVjdChuY3ApOwor CW5jcF9jb25uX3VubG9jayhuY3AsIHRkKTsKIAogCS8qCiAJICogTWFyayBjb25uIGFzIGRlYWQg YW5kIHdhaXQgZm9yIG90aGVyIHByb2Nlc3MKIAkgKi8KKwlOQ1BfSUxPQ0sobmNwKTsKIAluY3At Pm5jX2lkID0gMDsKLQluY3BfY29ubl91bmxvY2sobmNwLCB0ZCk7Ci0JLyoKLQkgKiBpZiBzaWdu YWwgaXMgcmFpc2VkIC0gaG93IEkgZG8gcmVhY3QgPwotCSAqLwotCWxvY2ttZ3IoJm5jcC0+bmNf bG9jaywgTEtfRFJBSU4sIDApOwotCWxvY2ttZ3IoJm5jcC0+bmNfbG9jaywgTEtfUkVMRUFTRSwg MCk7CisJaWYgKG5jcC0+bmNfbG9ja2NudCAhPSAwKSB7CisJCW5jcC0+ZmxhZ3MgfD0gTkNQRkxf RFJBSU5JTkc7CisJCW1zbGVlcCgmbmNwLT5uY19sb2NrY250LCBOQ1BfTVRYKG5jcCksIFBTT0NL LAorCQkgICAgIm5jcCBjb25uZWN0aW9uIGRyYWluIiwgMCk7CisJfQorCU5DUF9JVU5MT0NLKG5j cCk7CiAJbG9ja2Rlc3Ryb3koJm5jcC0+bmNfbG9jayk7CiAJd2hpbGUgKG5jcC0+bmNfbHdhbnQp IHsKIAkJcHJpbnRmKCJsd2FudCA9ICVkXG4iLCBuY3AtPm5jX2x3YW50KTsKIAkJdHNsZWVwKCZu Y3AtPm5jX2x3YW50LCBQWkVSTywibmNwZHIiLDIqaHopOwogCX0KLQluY3BfY29ubl9sb2NrbGlz dChMS19FWENMVVNJVkUsIHRkKTsKKwluY3BfY29ubl94bG9ja2xpc3QoKTsKIAlTTElTVF9SRU1P VkUoJmNvbm5fbGlzdCwgbmNwLCBuY3BfY29ubiwgbmNfbmV4dCk7CiAJbmNwX2Nvbm5fY250LS07 Ci0JbmNwX2Nvbm5fdW5sb2NrbGlzdCh0ZCk7CisJbmNwX2Nvbm5feHVubG9ja2xpc3QoKTsKIAlp ZiAobmNwLT5saS51c2VyKQogCQlmcmVlKG5jcC0+bGkudXNlciwgTV9OQ1BEQVRBKTsKIAlpZiAo bmNwLT5saS5wYXNzd29yZCkKQEAgLTM5MCwxMSArNDQzLDExIEBACiAJc3RydWN0IG5jcF9jb25u ICpuY3A7CiAJaW50IGVycm9yID0gMDsKIAotCW5jcF9jb25uX2xvY2tsaXN0KExLX1NIQVJFRCwg dGQpOworCW5jcF9jb25uX3Nsb2NrbGlzdCgpOwogCVNMSVNUX0ZPUkVBQ0gobmNwLCAmY29ubl9s aXN0LCBuY19uZXh0KQogCQlpZiAobmNwLT5uY19pZCA9PSByZWYpIGJyZWFrOwogCWlmIChuY3Ag PT0gTlVMTCkgewotCQluY3BfY29ubl91bmxvY2tsaXN0KHRkKTsKKwkJbmNwX2Nvbm5fc3VubG9j a2xpc3QoKTsKIAkJcmV0dXJuKEVCQURGKTsKIAl9CiAJZXJyb3IgPSBuY3BfY29ubl9sb2NrMihu Y3AsIHRkLCBjcmVkLCBtb2RlKTsKQEAgLTQxMiw3ICs0NjUsNyBAQAogCXN0cnVjdCBuY3BfY29u biAqbmNwLCAqbmNwMiA9IE5VTEw7CiAJaW50IGVycm9yID0gMDsKIAotCW5jcF9jb25uX2xvY2ts aXN0KExLX1NIQVJFRCwgdGQpOworCW5jcF9jb25uX3Nsb2NrbGlzdCgpOwogCVNMSVNUX0ZPUkVB Q0gobmNwLCAmY29ubl9saXN0LCBuY19uZXh0KSB7CiAJCWlmICgobmNwLT5mbGFncyAmIE5DUEZM X0xPR0dFRCkgIT0gMCB8fAogCQkgICAgc3RyY21wKG5jcC0+bGkuc2VydmVyLGxpLT5zZXJ2ZXIp ICE9IDAgfHwKQEAgLTQyOCw3ICs0ODEsNyBAQAogCX0KIAlpZiAobmNwID09IE5VTEwpIG5jcCA9 IG5jcDI7CiAJaWYgKG5jcCA9PSBOVUxMKSB7Ci0JCW5jcF9jb25uX3VubG9ja2xpc3QodGQpOwor CQluY3BfY29ubl9zdW5sb2NrbGlzdCgpOwogCQlyZXR1cm4oRUJBREYpOwogCX0KIAllcnJvciA9 IG5jcF9jb25uX2xvY2syKG5jcCwgdGQsIGNyZWQsIG1vZGUpOwpAQCAtNDU2LDcgKzUwOSw3IEBA CiAKIAlwYXJ0aWFsID0gKGxpID09IE5VTEwgfHwgbGktPnNlcnZlclswXSA9PSAwIHx8IGxpLT51 c2VyID09IE5VTEwpOwogCWhhdmVzZXJ2ID0gKGxpICYmIGxpLT5zZXJ2ZXJbMF0pOwotCW5jcF9j b25uX2xvY2tsaXN0KExLX1NIQVJFRCwgdGQpOworCW5jcF9jb25uX3Nsb2NrbGlzdCgpOwogCVNM SVNUX0ZPUkVBQ0gobmNwLCAmY29ubl9saXN0LCBuY19uZXh0KSB7CiAJCWlmIChwYXJ0aWFsKSB7 CiAJCQlpZiAoY3JlZC0+Y3JfdWlkID09IG5jcC0+bmNfb3duZXItPmNyX3VpZCkgewpAQCAtNDg2 LDcgKzUzOSw3IEBACiAJfQogCWlmIChuY3AgPT0gTlVMTCkgbmNwID0gbmNwMjsKIAlpZiAobmNw ID09IE5VTEwpIHsKLQkJbmNwX2Nvbm5fdW5sb2NrbGlzdCh0ZCk7CisJCW5jcF9jb25uX3N1bmxv Y2tsaXN0KCk7CiAJCXJldHVybihFQkFERik7CiAJfQogCWVycm9yID0gbmNwX2Nvbm5fbG9jazIo bmNwLCB0ZCwgY3JlZCxtb2RlKTsKQEAgLTUwNywxMiArNTYwLDEyIEBACiAKIAlpZiAoY29ubi0+ dWNyZWQtPmNyX3VpZCAhPSBjb25uLT5uY19vd25lci0+Y3JfdWlkKQogCQlyZXR1cm4gRUFDQ0VT OwotCW5jcF9jb25uX2xvY2tsaXN0KExLX1NIQVJFRCwgY29ubi0+dGQpOworCW5jcF9jb25uX3Ns b2NrbGlzdCgpOwogCVNMSVNUX0ZPUkVBQ0gobmNwLCAmY29ubl9saXN0LCBuY19uZXh0KSB7CiAJ CWlmIChjb25uLT51Y3JlZC0+Y3JfdWlkID09IG5jcC0+bmNfb3duZXItPmNyX3VpZCkKIAkJCW5j cC0+ZmxhZ3MgJj0gfk5DUEZMX1BSSU1BUlk7CiAJfQotCW5jcF9jb25uX3VubG9ja2xpc3QoY29u bi0+dGQpOworCW5jcF9jb25uX3N1bmxvY2tsaXN0KCk7CiAJaWYgKG9uKQogCQljb25uLT5mbGFn cyB8PSBOQ1BGTF9QUklNQVJZOwogCXJldHVybiAwOwpAQCAtNTI2LDE0ICs1NzksMTQgQEAKIHsK IAlzdHJ1Y3QgbmNwX2hhbmRsZSAqcmVmcDsKIAotCWxvY2ttZ3IoJmxobG9jaywgTEtfRVhDTFVT SVZFLCAwKTsKKwlzeF94bG9jaygmbGhsb2NrKTsKIAlTTElTVF9GT1JFQUNIKHJlZnAsICZsaGxp c3QsIG5oX25leHQpCiAJCWlmIChyZWZwLT5uaF9jb25uID09IGNvbm4gJiYgdGQgPT0gcmVmcC0+ bmhfdGQpIGJyZWFrOwogCWlmIChyZWZwKSB7CiAJCWNvbm4tPnJlZl9jbnQrKzsKIAkJcmVmcC0+ bmhfcmVmKys7CiAJCSpoYW5kbGUgPSByZWZwOwotCQlsb2NrbWdyKCZsaGxvY2ssIExLX1JFTEVB U0UsIDApOworCQlzeF94dW5sb2NrKCZsaGxvY2spOwogCQlyZXR1cm4gMDsKIAl9CiAJcmVmcCA9 IG1hbGxvYyhzaXplb2Yoc3RydWN0IG5jcF9oYW5kbGUpLE1fTkNQREFUQSwKQEAgLTU0NSw3ICs1 OTgsNyBAQAogCXJlZnAtPm5oX2lkID0gbmNwX25leHRfaGFuZGxlKys7CiAJKmhhbmRsZSA9IHJl ZnA7CiAJY29ubi0+cmVmX2NudCsrOwotCWxvY2ttZ3IoJmxobG9jaywgTEtfUkVMRUFTRSwgMCk7 CisJc3hfeHVubG9jaygmbGhsb2NrKTsKIAlyZXR1cm4gMDsKIH0KIC8qCkBAIC01NTYsNyArNjA5 LDcgQEAKIHsKIAlzdHJ1Y3QgbmNwX2hhbmRsZSAqcmVmcCA9IGhhbmRsZTsKIAotCWxvY2ttZ3Io JmxobG9jaywgTEtfRVhDTFVTSVZFLCAwKTsKKwlzeF94bG9jaygmbGhsb2NrKTsKIAlyZWZwLT5u aF9yZWYtLTsKIAlyZWZwLT5uaF9jb25uLT5yZWZfY250LS07CiAJaWYgKGZvcmNlKSB7CkBAIC01 NjcsNyArNjIwLDcgQEAKIAkJU0xJU1RfUkVNT1ZFKCZsaGxpc3QsIHJlZnAsIG5jcF9oYW5kbGUs IG5oX25leHQpOwogCQlmcmVlKHJlZnAsIE1fTkNQREFUQSk7CiAJfQotCWxvY2ttZ3IoJmxobG9j aywgTEtfUkVMRUFTRSwgMCk7CisJc3hfeHVubG9jaygmbGhsb2NrKTsKIAlyZXR1cm4gMDsKIH0K IC8qCkBAIC01NzcsMTAgKzYzMCwxMCBAQAogbmNwX2Nvbm5fZmluZGhhbmRsZShpbnQgY29ubkhh bmRsZSwgc3RydWN0IHRocmVhZCAqdGQsIHN0cnVjdCBuY3BfaGFuZGxlICoqaGFuZGxlKSB7CiAJ c3RydWN0IG5jcF9oYW5kbGUgKnJlZnA7CiAKLQlsb2NrbWdyKCZsaGxvY2ssIExLX1NIQVJFRCwg MCk7CisJc3hfc2xvY2soJmxobG9jayk7CiAJU0xJU1RfRk9SRUFDSChyZWZwLCAmbGhsaXN0LCBu aF9uZXh0KQogCQlpZiAocmVmcC0+bmhfdGQgPT0gdGQgJiYgcmVmcC0+bmhfaWQgPT0gY29ubkhh bmRsZSkgYnJlYWs7Ci0JbG9ja21ncigmbGhsb2NrLCBMS19SRUxFQVNFLCAwKTsKKwlzeF9zdW5s b2NrKCZsaGxvY2spOwogCWlmIChyZWZwID09IE5VTEwpIHsKIAkJcmV0dXJuIEVCQURGOwogCX0K QEAgLTU5Niw3ICs2NDksNyBAQAogCXN0cnVjdCBuY3BfaGFuZGxlICpocCwgKm5ocDsKIAlpbnQg aGF2ZW9uZSA9IDA7CiAKLQlsb2NrbWdyKCZsaGxvY2ssIExLX0VYQ0xVU0lWRSwgMCk7CisJc3hf eGxvY2soJmxobG9jayk7CiAJZm9yIChocCA9IFNMSVNUX0ZJUlNUKCZsaGxpc3QpOyBocDsgaHAg PSBuaHApIHsKIAkJbmhwID0gU0xJU1RfTkVYVChocCwgbmhfbmV4dCk7CiAJCWlmIChocC0+bmhf dGQgIT0gdGQpIGNvbnRpbnVlOwpAQCAtNjA1LDcgKzY1OCw3IEBACiAJCVNMSVNUX1JFTU9WRSgm bGhsaXN0LCBocCwgbmNwX2hhbmRsZSwgbmhfbmV4dCk7CiAJCWZyZWUoaHAsIE1fTkNQREFUQSk7 CiAJfQotCWxvY2ttZ3IoJmxobG9jaywgTEtfUkVMRUFTRSwgMCk7CisJc3hfeHVubG9jaygmbGhs b2NrKTsKIAlyZXR1cm4gaGF2ZW9uZTsKIH0KIC8qCkBAIC02MTYsMTEgKzY2OSwxMSBAQAogbmNw X2Nvbm5fbGlzdF9ybV9yZWYocGlkX3QgcGlkKSB7CiAJc3RydWN0IG5jcF9jb25uICpuY3A7CiAK LQluY3BfY29ubl9sb2NrbGlzdChMS19TSEFSRUQsIE5VTEwpOworCW5jcF9jb25uX3Nsb2NrbGlz dCgpOwogCVNMSVNUX0ZPUkVBQ0gobmNwLCAmY29ubl9saXN0LCBuY19uZXh0KSB7CiAJCW5jcF9j b25uX3JtX3JlZihuY3AscGlkLDEpOwogCX0KLQluY3BfY29ubl91bmxvY2tsaXN0KE5VTEwpOwor CW5jcF9jb25uX3N1bmxvY2tsaXN0KCk7CiAJcmV0dXJuOwogfQogKi8KQEAgLTY1Myw3ICs3MDYs NyBAQAogCWVycm9yID0gc3lzY3RsX3dpcmVfb2xkX2J1ZmZlcihyZXEsIDApOwogCWlmIChlcnJv ciAhPSAwKQogCQlyZXR1cm4gKGVycm9yKTsKLQluY3BfY29ubl9sb2NrbGlzdChMS19TSEFSRUQs IHJlcS0+dGQpOworCW5jcF9jb25uX3Nsb2NrbGlzdCgpOwogCWVycm9yID0gU1lTQ1RMX09VVChy ZXEsICZuY3BfY29ubl9jbnQsIHNpemVvZihuY3BfY29ubl9jbnQpKTsKIAlTTElTVF9GT1JFQUNI KG5jcCwgJmNvbm5fbGlzdCwgbmNfbmV4dCkgewogCQlpZiAoZXJyb3IpIGJyZWFrOwpAQCAtNjYz LDYgKzcxNiw2IEBACiAJCW5jcC0+bmNfbHdhbnQtLTsKIAkJZXJyb3IgPSBTWVNDVExfT1VUKHJl cSwgJm5jcywgc2l6ZW9mKG5jcykpOwogCX0KLQluY3BfY29ubl91bmxvY2tsaXN0KHJlcS0+dGQp OworCW5jcF9jb25uX3N1bmxvY2tsaXN0KCk7CiAJcmV0dXJuKGVycm9yKTsKIH0KLS0tIC91c3Iv c3JjL3N5cy9uZXRuY3AvbmNwX2Nvbm4uaAkyMDA4LTAzLTEyIDE0OjU1OjQwLjAwMDAwMDAwMCAr MDEwMAorKysgc3lzL25ldG5jcC9uY3BfY29ubi5oCTIwMDktMDEtMjggMTk6MjA6MDIuMDAwMDAw MDAwICswMTAwCkBAIC02Myw2ICs2Myw3IEBACiAjZGVmaW5lCU5DUEZMX1dBU0xPR0dFRAkJMHgw MjAwCS8qIHRoZXJlIHdhcyBhdCBsZWFzdCBvbmUgc3VjY2Vzc2Z1bGwgbG9naW4gKi8KICNkZWZp bmUJTkNQRkxfU0lHTkFDVElWRQkweDEwMDAJLyogcGFja2V0IHNpZ25pbmcgYWN0aXZlICovCiAj ZGVmaW5lCU5DUEZMX1NJR05XQU5URUQJMHgyMDAwCS8qIHNpZ25pbmcgc2hvdWxkIHN0YXJ0ICov CisjZGVmaW5lCU5DUEZMX0RSQUlOSU5HCQkweDQwMDAJLyogc3RydWN0dXJlIHVuZGVyIGRyYWlu aW5nICovCiAKIC8qIGFjY2VzcyBtb2RlIGZvciBjb25uZWN0aW9uICovCiAjZGVmaW5lCU5DUE1f UkVBRAkJMDQwMAkvKiBhYmxlIHRvIGZldGNoIGNvbm4gcGFyYW1zICovCkBAIC03Miw2ICs3Myw5 IEBACiAjZGVmaW5lCU5DUF9ERUZBVUxUX09XTkVSCSgodWlkX3QpLTEpCiAjZGVmaW5lCU5DUF9E RUZBVUxUX0dST1VQCSgodWlkX3QpLTEpCiAKKyNkZWZpbmUJTkNQX0lMT0NLKG5jcCkJCW10eF9s b2NrKCYobmNwKS0+bmNfaWxvY2spCisjZGVmaW5lCU5DUF9JVU5MT0NLKG5jcCkJbXR4X3VubG9j aygmKG5jcCktPm5jX2lsb2NrKQorI2RlZmluZQlOQ1BfTVRYKG5jcCkJCSgmKG5jcCktPm5jX2ls b2NrKQogCiAvKiBhcmdzIHVzZWQgdG8gY3JlYXRlIGNvbm5lY3Rpb24gKi8KICNkZWZpbmUJbmNw X2Nvbm5fbG9naW5mbwluY3BfY29ubl9hcmdzCkBAIC0xNzMsNiArMTc3LDggQEAKIAlpbnQgCQly ZWZfY250OwkJLyogaG93IG1hbnkgaGFuZGxlcyBsZWFzZWQgKi8KIAlTTElTVF9IRUFEKG5jcF9y ZWZfaGQsbmNwX3JlZikgcmVmX2xpc3Q7LyogbGlzdCBvZiBoYW5kbGVzICovCiAJc3RydWN0IGxv Y2sJbmNfbG9jazsJCS8qIGV4Y2wgbG9ja3MgKi8KKwlzdHJ1Y3QgbXR4CW5jX2lsb2NrOwkJLyog Y29ubmVjdGlvbiBpbnRlcmxvY2sgKi8KKwlpbnQJCW5jX2xvY2tjbnQ7CQkvKiBsb2NrIHJlZmNv dW50ICovCiAJaW50CQluY19sd2FudDsJCS8qIG51bWJlciBvZiB3YW50ZWQgbG9ja3MgKi8KIAlz dHJ1Y3QgdGhyZWFkCSp0ZDsJCQkvKiBwaWQgY3VycmVudGx5IG9wZXJhdGVzICovCiAJc3RydWN0 IHVjcmVkCSp1Y3JlZDsJCQkvKiB1c3IgY3VycmVudGx5IG9wZXJhdGVzICovCkBAIC0yMDEsNyAr MjA3LDYgQEAKIGludCAgbmNwX2Nvbm5fYWNjZXNzKHN0cnVjdCBuY3BfY29ubiAqY29ubixzdHJ1 Y3QgdWNyZWQgKmNyZWQsbW9kZV90IG1vZGUpOwogaW50ICBuY3BfY29ubl9sb2NrKHN0cnVjdCBu Y3BfY29ubiAqY29ubixzdHJ1Y3QgdGhyZWFkICp0ZCwgc3RydWN0IHVjcmVkICpjcmVkLGludCBt b2RlKTsKIHZvaWQgbmNwX2Nvbm5fdW5sb2NrKHN0cnVjdCBuY3BfY29ubiAqY29ubixzdHJ1Y3Qg dGhyZWFkICp0ZCk7Ci1pbnQgIG5jcF9jb25uX2Fzc2VydF9sb2NrZWQoc3RydWN0IG5jcF9jb25u ICpjb25uLGNvbnN0IGNoYXIgKmNoZWNrZXIsc3RydWN0IHRocmVhZCAqdGQpOwogdm9pZCBuY3Bf Y29ubl9pbnZhbGlkYXRlKHN0cnVjdCBuY3BfY29ubiAqbmNwKTsKIGludCAgbmNwX2Nvbm5faW52 YWxpZChzdHJ1Y3QgbmNwX2Nvbm4gKm5jcCk7CiAvKmludCAgbmNwX2Nvbm5fcmVmKHN0cnVjdCBu Y3BfY29ubiAqY29ubiwgcGlkX3QgcGlkKTsKQEAgLTIxMiw4ICsyMTcsMTIgQEAKIGludCAgbmNw X2Nvbm5fZ2V0YnlsaShzdHJ1Y3QgbmNwX2Nvbm5fbG9naW5mbyAqbGksc3RydWN0IHRocmVhZCAq dGQsIHN0cnVjdCB1Y3JlZCAqY3JlZCwgCiAJaW50IG1vZGUsIHN0cnVjdCBuY3BfY29ubiAqKmNv bm5wcCk7CiBpbnQgIG5jcF9jb25uX3NldHByaW1hcnkoc3RydWN0IG5jcF9jb25uICpjb25uLCBp bnQgb24pOwotaW50ICBuY3BfY29ubl9sb2NrbGlzdChpbnQgZmxhZ3MsIHN0cnVjdCB0aHJlYWQg KnRkKTsKLXZvaWQgbmNwX2Nvbm5fdW5sb2NrbGlzdChzdHJ1Y3QgdGhyZWFkICp0ZCk7Cit2b2lk IG5jcF9jb25uX3Nsb2NrbGlzdCh2b2lkKTsKK3ZvaWQgbmNwX2Nvbm5feGxvY2tsaXN0KHZvaWQp OworaW50ICBuY3BfY29ubl90cnlfc2xvY2tsaXN0KHZvaWQpOworaW50ICBuY3BfY29ubl90cnlf eGxvY2tsaXN0KHZvaWQpOwordm9pZCBuY3BfY29ubl9zdW5sb2NrbGlzdCh2b2lkKTsKK3ZvaWQg bmNwX2Nvbm5feHVubG9ja2xpc3Qodm9pZCk7CiBpbnQgIG5jcF9jb25uX2dldGhhbmRsZShzdHJ1 Y3QgbmNwX2Nvbm4gKmNvbm4sIHN0cnVjdCB0aHJlYWQgKnRkLCBzdHJ1Y3QgbmNwX2hhbmRsZSAq KmhhbmRsZSk7CiBpbnQgIG5jcF9jb25uX3B1dGhhbmRsZShzdHJ1Y3QgbmNwX2hhbmRsZSAqaGFu ZGxlLCBzdHJ1Y3QgdGhyZWFkICp0ZCwgaW50IGZvcmNlKTsKIGludCAgbmNwX2Nvbm5fZmluZGhh bmRsZShpbnQgY29ubkhhbmRsZSwgc3RydWN0IHRocmVhZCAqdGQsIHN0cnVjdCBuY3BfaGFuZGxl ICoqaGFuZGxlKTsKLS0tIC91c3Ivc3JjL3N5cy9uZXRuY3AvbmNwX3N1YnIuYwkyMDA5LTAxLTEw IDEzOjM5OjQ4LjAwMDAwMDAwMCArMDEwMAorKysgc3lzL25ldG5jcC9uY3Bfc3Vici5jCTIwMDkt MDEtMjggMTk6MjQ6MDguMDAwMDAwMDAwICswMTAwCkBAIC05MCw3ICs5MCw3IEBACiAJCWlmIChu Y3BfY29ubl9wdXRwcm9jaGFuZGxlcyh0ZCkgPT0gMCkKIAkJCWNvbnRpbnVlOwogCi0JCW5jcF9j b25uX2xvY2tsaXN0KExLX0VYQ0xVU0lWRSwgdGQpOworCQluY3BfY29ubl94bG9ja2xpc3QoKTsK IAkJZm9yIChuY3AgPSBTTElTVF9GSVJTVCgmY29ubl9saXN0KTsgbmNwOyBuY3AgPSBubmNwKSB7 CiAJCQlubmNwID0gU0xJU1RfTkVYVChuY3AsIG5jX25leHQpOwogCQkJaWYgKG5jcF9jb25uX2xv Y2sobmNwLCB0ZCwgdGQtPnRkX3VjcmVkLApAQCAtOTksNyArOTksNyBAQAogCQkJaWYgKG5jcF9j b25uX2ZyZWUobmNwKSAhPSAwKQogCQkJCW5jcF9jb25uX3VubG9jayhuY3AsIHRkKTsKIAkJfQot CQluY3BfY29ubl91bmxvY2tsaXN0KHRkKTsKKwkJbmNwX2Nvbm5feHVubG9ja2xpc3QoKTsKIAl9 CiAJbXR4X3VubG9jaygmR2lhbnQpOwogfQpAQCAtMTM0LDEwICsxMzQsMTAgQEAKIHsKIAlzdHJ1 Y3QgbmNwX2Nvbm4gKmNvbm47CiAKLQlpZihuY3BfY29ubl9sb2NrbGlzdChMS19TSEFSRUQgfCBM S19OT1dBSVQsIE5VTEwpID09IDApIHsKKwlpZiAobmNwX2Nvbm5fdHJ5X3Nsb2NrbGlzdCgpKSB7 CiAJCVNMSVNUX0ZPUkVBQ0goY29ubiwgJmNvbm5fbGlzdCwgbmNfbmV4dCkKIAkJCW5jcF9jaGVj a19jb25uKGNvbm4pOwotCQluY3BfY29ubl91bmxvY2tsaXN0KE5VTEwpOworCQluY3BfY29ubl9z dW5sb2NrbGlzdCgpOwogCX0KIAluY3BfdGltZXJfaGFuZGxlID0gdGltZW91dChuY3BfdGltZXIs IE5VTEwsIE5DUF9USU1FUl9USUNLKTsKIH0K --000e0cd286e283a38b04618f5e64-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 19:28:01 2009 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 156A710656F4 for ; Wed, 28 Jan 2009 19:28:01 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from mailhub.cs.uoguelph.ca (mailhub.cs.uoguelph.ca [131.104.94.205]) by mx1.freebsd.org (Postfix) with ESMTP id AB3BC8FC19 for ; Wed, 28 Jan 2009 19:28:00 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by mailhub.cs.uoguelph.ca (8.13.1/8.13.1) with ESMTP id n0SJCnQ0014157; Wed, 28 Jan 2009 14:12:49 -0500 Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id n0SJGDC23460; Wed, 28 Jan 2009 14:16:13 -0500 (EST) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Wed, 28 Jan 2009 14:16:13 -0500 (EST) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Sean Bruno In-Reply-To: <1233166048.3592.1.camel@localhost.localdomain> Message-ID: References: <1233098540.2494.6.camel@localhost.localdomain> <49809B45.1000703@boland.org> <1233166048.3592.1.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.63 on 131.104.94.205 Cc: Michiel Boland , current@freebsd.org Subject: Re: NFS mounts dissapearing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 19:28:02 -0000 On Wed, 28 Jan 2009, Sean Bruno wrote: > On Wed, 2009-01-28 at 18:52 +0100, Michiel Boland wrote: >> Sean Bruno wrote: >>> I've noted that my NFS mount of a directory is vanishing periodically >>> under -current. I am unable to unmount/remount the directory and the >>> system returns Permission Denied on all attempts to access the >>> directory. >>> >>> Is this something that is known and being investigated? >> >> FWIW I am seeing this too, except that I can still umount/remount. It appears to >> me that TCP connections to remote nfsd use a privileged source port initially, >> but if the connection is severed and reestablished later the source port is no >> longer < 1024. Client is -CURRENT, server is solaris with nfssrv:nfs_portmon=1. >> >> Cheers >> Michiel > You guys might want to try rebuilding a kernel with options NFS_LEGACYRPC and see if that fixes the problem, rick From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 19:35:50 2009 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 67F151065745 for ; Wed, 28 Jan 2009 19:35:50 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (77-93-215-190.static.masterinter.net [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id 0F45E8FC14 for ; Wed, 28 Jan 2009 19:35:49 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 072049CB0EC; Wed, 28 Jan 2009 20:33:21 +0100 (CET) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (lev.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qG4SBv7etpsO; Wed, 28 Jan 2009 20:33:18 +0100 (CET) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id A34FF9CB120; Wed, 28 Jan 2009 20:33:18 +0100 (CET) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id n0SJXIY1042355; Wed, 28 Jan 2009 20:33:18 +0100 (CET) (envelope-from rdivacky) Date: Wed, 28 Jan 2009 20:33:18 +0100 From: Roman Divacky To: current@freebsd.org Message-ID: <20090128193318.GA42071@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pf9I7BMVVzbSWLtt" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: scottl@freebsd.org Subject: sysctl question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 19:35:50 -0000 --pf9I7BMVVzbSWLtt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable hi we dont need Giant to be held for sysctl_ctx_init/SYSCTL_ADD_*, right? if that's true, is this ok for commit? Index: cam/scsi/scsi_da.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- cam/scsi/scsi_da.c (revision 187838) +++ cam/scsi/scsi_da.c (working copy) @@ -1086,7 +1086,6 @@ snprintf(tmpstr, sizeof(tmpstr), "CAM DA unit %d", periph->unit_number); snprintf(tmpstr2, sizeof(tmpstr2), "%d", periph->unit_number); =20 - mtx_lock(&Giant); sysctl_ctx_init(&softc->sysctl_ctx); softc->flags |=3D DA_FLAG_SCTX_INIT; softc->sysctl_tree =3D SYSCTL_ADD_NODE(&softc->sysctl_ctx, @@ -1094,7 +1093,6 @@ CTLFLAG_RD, 0, tmpstr); if (softc->sysctl_tree =3D=3D NULL) { printf("dasysctlinit: unable to allocate sysctl tree\n"); - mtx_unlock(&Giant); cam_periph_release(periph); return; } @@ -1108,7 +1106,6 @@ &softc->minimum_cmd_size, 0, dacmdsizesysctl, "I", "Minimum CDB size"); =20 - mtx_unlock(&Giant); cam_periph_release(periph); } =20 Index: cam/scsi/scsi_cd.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- cam/scsi/scsi_cd.c (revision 187838) +++ cam/scsi/scsi_cd.c (working copy) @@ -555,8 +555,6 @@ snprintf(tmpstr, sizeof(tmpstr), "CAM CD unit %d", periph->unit_number); snprintf(tmpstr2, sizeof(tmpstr2), "%d", periph->unit_number); =20 - mtx_lock(&Giant); - sysctl_ctx_init(&softc->sysctl_ctx); softc->flags |=3D CD_FLAG_SCTX_INIT; softc->sysctl_tree =3D SYSCTL_ADD_NODE(&softc->sysctl_ctx, @@ -565,7 +563,6 @@ =20 if (softc->sysctl_tree =3D=3D NULL) { printf("cdsysctlinit: unable to allocate sysctl tree\n"); - mtx_unlock(&Giant); cam_periph_release(periph); return; } @@ -579,7 +576,6 @@ &softc->minimum_command_size, 0, cdcmdsizesysctl, "I", "Minimum CDB size"); =20 - mtx_unlock(&Giant); cam_periph_release(periph); } =20 thnx! roman --pf9I7BMVVzbSWLtt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmAsv0ACgkQLVEj6D3CBExieQCfY6d50qVGVfHuk6vL8Fwx5Vl5 ghEAnjDwf2i5IrVzoc9aPlOp7E2ta35Y =DA7O -----END PGP SIGNATURE----- --pf9I7BMVVzbSWLtt-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 19:48:44 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94E84106566B for ; Wed, 28 Jan 2009 19:48:44 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.239]) by mx1.freebsd.org (Postfix) with ESMTP id 67CCC8FC21 for ; Wed, 28 Jan 2009 19:48:44 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so7219234rvf.43 for ; Wed, 28 Jan 2009 11:48:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=7pBcusm4hPzRiSMEdO5xkdO8ERRuolBNf7ludNtK6Cw=; b=BqxwkKT3koWf5U5OXZ/oxBbxHWX7uNXpvNDqpfQfL7l3tvc4pnXjbYVzzsBz+tIQZp qqG5ySeCVAN8IW1VePQfjBHX2vC2V+ISTQFEu+3waUidrzP31PTosqwosFZzmqeU3SML aQZIs8avl0FsFoZjqfPXajt2B+P4FXUINRm4Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=Y8v4SFONE76UwPXZDAhkwAz+M+SAfirpzsq6lKbYjjBTG8FyHgXawtKUDT/qZpcb06 4t5PPWOPQ/qgzNaLqNrX6pDppE3L/dHHTIFZAfXMrfWMiZLT96MLzDrQ0V9f6VGcemJi Czcl68eCJXez5FndFvch9wKhLH03Rcb3U+Q08= MIME-Version: 1.0 Sender: mat.macy@gmail.com Received: by 10.141.114.15 with SMTP id r15mr528375rvm.42.1233172123850; Wed, 28 Jan 2009 11:48:43 -0800 (PST) In-Reply-To: <1233105002.26641.2.camel@phoenix.blechhirn.net> References: <1233105002.26641.2.camel@phoenix.blechhirn.net> Date: Wed, 28 Jan 2009 11:48:43 -0800 X-Google-Sender-Auth: 825d85c74e314b81 Message-ID: <3c1674c90901281148i3949ee69r289db344a23b4326@mail.gmail.com> From: Kip Macy To: mister.olli@googlemail.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Page fault 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, 28 Jan 2009 19:48:44 -0000 Will try to fix soon. Thanks, Kip On Tue, Jan 27, 2009 at 5:10 PM, Mister Olli wrote: > Hi, > > > The following pagefault just happend on my PV CURRENT domU under Xen 3.3 > > ================================================================== > template_8-CURRENT# pwd > /usr > Kernel page fault with the following non-sleepable locks > held:org/base/head src/ > exclusive sleep mutex pmap (pmap) r = 0 (0xc1706ee8) locked > @ /usr/src/sys/i386/xen/pmap.c:3711 > exclusive sleep mutex vm object (standard object) r = 0 (0xc19c98b8) > locked @ /usr/src/sys/vm/vm_pageout.c:771 > exclusive sleep mutex vm page queue mutex (vm page queue mutex) r = 0 > (0xc052ae84) locked @ /usr/src/sys/vm/vm_pageout.c:447 > KDB: stack backtrace: > X_db_sym_numargs(c0342b8f,cbe849ac,c010c5f5,c0361da2,1bf,...) at > X_db_sym_numargs+0x146 > kdb_backtrace(c0361da2,1bf,ffffffff,c04f2c2c,cbe849e4,...) at > kdb_backtrace+0x29 > witness_display_spinlock(c0344dec,cbe849f8,4,1,0,...) at > witness_display_spinlock+0x75 > witness_warn(5,0,c036c048,c17a7d80,c,...) at witness_warn+0x1fd > trap(cbe84a80) at trap+0x10e > alltraps(c0bb2d48,4,c0361da2,1a8,c0361da2,...) at alltraps+0x1b > vm_pageout_flush(cbe84ba4,7,0,0,ec1,...) at vm_pageout_flush+0xe5 > vm_pageout_flush(c0bb3c78,0,c0361da2,303,32,...) at vm_pageout_flush > +0x621 > vm_pageout_flush(0,cbe84d38,c033ba96,32d,c1701a90,...) at > vm_pageout_flush+0x13ce > fork_exit(c02d59b0,0,cbe84d38) at fork_exit+0xb8 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0, eip = 0, esp = 0xcbe84d70, ebp = 0 --- > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xc0863fc8 > fault code = supervisor write, protection violation > instruction pointer = 0x21:0xc03113df > stack pointer = 0x29:0xcbe84ac0 > frame pointer = 0x29:0xcbe84ae8 > code segment = base 0x0, limit 0xf67ff, type 0x1b > = DPL 1, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 6 (pagedaemon) > [thread pid 6 tid 100024 ] > Stopped at pmap_remove_write+0xbf: lock cmpxchgl %edi,0(%ecx) > db> > =============================================================== > > Since I was unable to enter anything at the debugger command line I'm > unable to provide a backtrace. sorry. > > -- > Olli > > _______________________________________________ > 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 Jan 28 19:50:51 2009 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 EBAAA106567D for ; Wed, 28 Jan 2009 19:50:51 +0000 (UTC) (envelope-from gtodd@bellanet.org) Received: from smtp116.rog.mail.re2.yahoo.com (smtp116.rog.mail.re2.yahoo.com [68.142.225.232]) by mx1.freebsd.org (Postfix) with SMTP id 7DE6E8FC18 for ; Wed, 28 Jan 2009 19:50:51 +0000 (UTC) (envelope-from gtodd@bellanet.org) Received: (qmail 2688 invoked from network); 28 Jan 2009 19:24:09 -0000 Received: from unknown (HELO wawanesa.iciti.ca) (gtodd@99.246.4.156 with login) by smtp116.rog.mail.re2.yahoo.com with SMTP; 28 Jan 2009 19:24:08 -0000 X-YMail-OSG: 09pf7xAVM1kP62eL21FyhFns6XDddQrFN921kUt4QZWmADoAB12qG8xTkJdbpHb.1g-- X-Yahoo-Newman-Property: ymail-3 Received: from wawanesa.iciti.ca (wawanesa.iciti.ca [192.168.2.4]) by wawanesa.iciti.ca (Postfix) with ESMTP id 1BCA987; Wed, 28 Jan 2009 14:24:09 -0500 (EST) Message-ID: <4980B0D8.9010506@bellanet.org> Date: Wed, 28 Jan 2009 14:24:08 -0500 From: Graham Todd User-Agent: Thunderbird 2.0.0.19 (X11/20090116) MIME-Version: 1.0 To: current@freebsd.org References: <20090122121750.GA14657@sr.se> In-Reply-To: <20090122121750.GA14657@sr.se> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: cy@FreeBSD.org, Gunnar Flygt , shaun@FreeBSD.org Subject: Re: Backporting of Heimdal 1.1 to 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: Wed, 28 Jan 2009 19:50:52 -0000 Gunnar Flygt wrote: > Is there any possibility that heimdal 1.1 that works beautifully in > Current will be backported to FreeBSD-7.x? What if the port was updated to 1.1 to match base in CURRENT or to 1.2.1 for testing? :-) Upstream heimdal is at 1.2.1 but I think there is some pthread trickiness involved in getting it to compile (does anyone know what is missing there?) For 1.1 you can change the values in the distinfo and Makefile in the current port (which is at 1.0.1) and build a new 1.1 package to use on 7.*. The rc script from the version in ports could use modernizing to make more use of rc.subr magic, but things seem to work. If you use PAM with kerberos I think the pam_krb5 in base and in ports is behind the upstream version as well. Russ Allbery maintains pam-krb5 at: http://www.eyrie.org/~eagle/software/pam-krb5/ - it has some options that could be useful for newer kerberos like: try_pkinit, etc. I don't know if much testing of these various new bits has been done on FreeBSD. I believe the pam_krb5 folks are working on some tools that will help people do simple tests before upgrades and the like. > Please CC me since I'm only subscribed to stable, not current. I've cc'ed the maintainers of pam-krb5 and heimdal too :) > Gunnar Flygt > Sveriges Radio Teknik/IT From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 19:56:42 2009 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 C0282106566B; Wed, 28 Jan 2009 19:56:42 +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 5BEFC8FC13; Wed, 28 Jan 2009 19:56:42 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.home (pooker.samsco.home [192.168.254.1]) by pooker.samsco.org (8.14.2/8.14.2) with ESMTP id n0SJuc40061750; Wed, 28 Jan 2009 12:56:38 -0700 (MST) (envelope-from scottl@samsco.org) Date: Wed, 28 Jan 2009 12:56:38 -0700 (MST) From: Scott Long To: Roman Divacky In-Reply-To: <20090128193318.GA42071@freebsd.org> Message-ID: <20090128125607.W16294@pooker.samsco.org> References: <20090128193318.GA42071@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: scottl@freebsd.org, current@freebsd.org Subject: Re: sysctl question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 19:56:43 -0000 If Giant isn't needed here, then great! Scott On Wed, 28 Jan 2009, Roman Divacky wrote: > hi > > we dont need Giant to be held for sysctl_ctx_init/SYSCTL_ADD_*, right? > > if that's true, is this ok for commit? > > Index: cam/scsi/scsi_da.c > =================================================================== > --- cam/scsi/scsi_da.c (revision 187838) > +++ cam/scsi/scsi_da.c (working copy) > @@ -1086,7 +1086,6 @@ > snprintf(tmpstr, sizeof(tmpstr), "CAM DA unit %d", periph->unit_number); > snprintf(tmpstr2, sizeof(tmpstr2), "%d", periph->unit_number); > > - mtx_lock(&Giant); > sysctl_ctx_init(&softc->sysctl_ctx); > softc->flags |= DA_FLAG_SCTX_INIT; > softc->sysctl_tree = SYSCTL_ADD_NODE(&softc->sysctl_ctx, > @@ -1094,7 +1093,6 @@ > CTLFLAG_RD, 0, tmpstr); > if (softc->sysctl_tree == NULL) { > printf("dasysctlinit: unable to allocate sysctl tree\n"); > - mtx_unlock(&Giant); > cam_periph_release(periph); > return; > } > @@ -1108,7 +1106,6 @@ > &softc->minimum_cmd_size, 0, dacmdsizesysctl, "I", > "Minimum CDB size"); > > - mtx_unlock(&Giant); > cam_periph_release(periph); > } > > Index: cam/scsi/scsi_cd.c > =================================================================== > --- cam/scsi/scsi_cd.c (revision 187838) > +++ cam/scsi/scsi_cd.c (working copy) > @@ -555,8 +555,6 @@ > snprintf(tmpstr, sizeof(tmpstr), "CAM CD unit %d", periph->unit_number); > snprintf(tmpstr2, sizeof(tmpstr2), "%d", periph->unit_number); > > - mtx_lock(&Giant); > - > sysctl_ctx_init(&softc->sysctl_ctx); > softc->flags |= CD_FLAG_SCTX_INIT; > softc->sysctl_tree = SYSCTL_ADD_NODE(&softc->sysctl_ctx, > @@ -565,7 +563,6 @@ > > if (softc->sysctl_tree == NULL) { > printf("cdsysctlinit: unable to allocate sysctl tree\n"); > - mtx_unlock(&Giant); > cam_periph_release(periph); > return; > } > @@ -579,7 +576,6 @@ > &softc->minimum_command_size, 0, cdcmdsizesysctl, "I", > "Minimum CDB size"); > > - mtx_unlock(&Giant); > cam_periph_release(periph); > } > > > thnx! > > roman > From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 20:41:06 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19A4E1065874 for ; Wed, 28 Jan 2009 20:41:06 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id DF5CB8FC13 for ; Wed, 28 Jan 2009 20:41:05 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (pool-98-109-39-197.nwrknj.fios.verizon.net [98.109.39.197]) by cyrus.watson.org (Postfix) with ESMTPSA id 8A90746B06; Wed, 28 Jan 2009 15:41:05 -0500 (EST) Received: from localhost (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.14.3/8.14.3) with ESMTP id n0SKekci099624; Wed, 28 Jan 2009 15:40:59 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 28 Jan 2009 14:53:57 -0500 User-Agent: KMail/1.9.7 References: <03a001c96f1b$3fa09b20$bee1d160$@muni.cz> In-Reply-To: <03a001c96f1b$3fa09b20$bee1d160$@muni.cz> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901281453.58214.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, 28 Jan 2009 15:40:59 -0500 (EST) X-Virus-Scanned: ClamAV 0.94.2/8914/Wed Jan 28 01:40:00 2009 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: Petr Holub Subject: Re: 8.0-SNAPSHOT200812 reversed locks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 20:41:06 -0000 On Monday 05 January 2009 4:51:51 am Petr Holub wrote: > Hi all, > > after booting a 8.0-SNAPSHOT200812 DVD on my T61p and entering > the fixit ``live'' mode, I've encountered the following > messages about reversed locks: > > DEBUG: ioctl(3, TIOCCONS, NULL) = 0 (success) > DEBUG: MADT: Found CPU APIC ID 0 enabled > DEBUG: MADT: Found CPU APIC ID 1 enabled > lock order reversal: > 1st 0xc6e43164 isofs (isofs) @ /usr/src/sys/kern/vfs_subr.c:2079 > 2nd 0xda8e7960 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2443 > 3rd 0xc6ed0488 isofs (isofs) @ /usr/src/sys/fs/cd9660/cd9660_vfsops.c:676 > KDB: stack backtrace: > db_trace_self_wrapper(...) at db_trace_self_wrapper+0x26 > kdb_backtrace(...) at kdb_backtrace+0x29 > _witness_debugger(...) at _witness_debugger+0x25 > witness_checkorder(...) at witness_checkorder+0x839 > __lockmgr_args(...) at __lockmgr_args+0x797 > cd9660_vget_internal(...) at cd9660_vget_internal+0x118 > cd9660_lookup(...) at cd9660_lookup+0x73f > VOP_CACHEDLOOKUP_APV(...) at VOP_CACHED_LOOKUP+0xa5 > vfs_cache_lookup(...) at vfs_cache_lookup+0xcc > VOP_LOOKUP_APV(...) at VOP_LOOKUP_APV+0xa5 > lookup(...) at lookup+0x0x57e > namei(...) at namei+0x04db > kern_accessat(...) at kern_accessat+0x94 > kern_access(...) at kern_access+0x36 > access(...) at access+0x29 > syscall(c67d1d38) at syscall+0x2a3 > Xint0x80_syscall() at Xint0x80_syscall+0x20 This one should be fixed by the cd9660 changes today. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 20:41:12 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 873951065753 for ; Wed, 28 Jan 2009 20:41:12 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 5666A8FC1D for ; Wed, 28 Jan 2009 20:41:12 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (pool-98-109-39-197.nwrknj.fios.verizon.net [98.109.39.197]) by cyrus.watson.org (Postfix) with ESMTPSA id 01DC446B5C; Wed, 28 Jan 2009 15:41:11 -0500 (EST) Received: from localhost (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.14.3/8.14.3) with ESMTP id n0SKekcj099624; Wed, 28 Jan 2009 15:41:05 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 28 Jan 2009 15:17:37 -0500 User-Agent: KMail/1.9.7 References: <200901281029.41232.nick@van-laarhoven.org> In-Reply-To: <200901281029.41232.nick@van-laarhoven.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901281517.37362.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, 28 Jan 2009 15:41:06 -0500 (EST) X-Virus-Scanned: ClamAV 0.94.2/8914/Wed Jan 28 01:40:00 2009 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: Nick Hibma Subject: Re: build in /sys/modules broken / other way of building 1 specific module X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 20:41:14 -0000 On Wednesday 28 January 2009 4:29:40 am Nick Hibma wrote: > Folks, > > I am not quite sure as to what its status is (and dfr politely explained > that I was being wereold-fashioned), but the build in /sys/modules is > broken at the moment. Doing > > cd /sys/modules > sudo make > > does not work due to missing opt_hwpmc_hooks.h files required by the build > of genassym. > > The patch below fixes this (creating empty opt_hwpmc_hooks.h files, any > objections?), but I > was wondering whether there is another way for building 1 specific module > instead of having to wait for 100+ modules to build after typing in > > cd /sys/i386/compile/HILDE/ > make -DNO_MODULES_OBJ modules I still build modules this way a lot. Go ahead and commit the patch. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 20:41:19 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38814106575F; Wed, 28 Jan 2009 20:41:18 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 579728FC20; Wed, 28 Jan 2009 20:41:18 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (pool-98-109-39-197.nwrknj.fios.verizon.net [98.109.39.197]) by cyrus.watson.org (Postfix) with ESMTPSA id DF18B46B65; Wed, 28 Jan 2009 15:41:17 -0500 (EST) Received: from localhost (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.14.3/8.14.3) with ESMTP id n0SKekck099624; Wed, 28 Jan 2009 15:41:12 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 28 Jan 2009 15:21:17 -0500 User-Agent: KMail/1.9.7 References: <20090128193318.GA42071@freebsd.org> In-Reply-To: <20090128193318.GA42071@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901281521.17674.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, 28 Jan 2009 15:41:12 -0500 (EST) X-Virus-Scanned: ClamAV 0.94.2/8914/Wed Jan 28 01:40:00 2009 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: Roman Divacky , scottl@freebsd.org Subject: Re: sysctl question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 20:41:21 -0000 On Wednesday 28 January 2009 2:33:18 pm Roman Divacky wrote: > hi > > we dont need Giant to be held for sysctl_ctx_init/SYSCTL_ADD_*, right? Ugh, it looks like the sysctl tree locking is woefully inadequate, so we aren't quite ready for this yet. > if that's true, is this ok for commit? > > Index: cam/scsi/scsi_da.c > =================================================================== > --- cam/scsi/scsi_da.c (revision 187838) > +++ cam/scsi/scsi_da.c (working copy) > @@ -1086,7 +1086,6 @@ > snprintf(tmpstr, sizeof(tmpstr), "CAM DA unit %d", periph->unit_number); > snprintf(tmpstr2, sizeof(tmpstr2), "%d", periph->unit_number); > > - mtx_lock(&Giant); > sysctl_ctx_init(&softc->sysctl_ctx); > softc->flags |= DA_FLAG_SCTX_INIT; > softc->sysctl_tree = SYSCTL_ADD_NODE(&softc->sysctl_ctx, > @@ -1094,7 +1093,6 @@ > CTLFLAG_RD, 0, tmpstr); > if (softc->sysctl_tree == NULL) { > printf("dasysctlinit: unable to allocate sysctl tree\n"); > - mtx_unlock(&Giant); > cam_periph_release(periph); > return; > } > @@ -1108,7 +1106,6 @@ > &softc->minimum_cmd_size, 0, dacmdsizesysctl, "I", > "Minimum CDB size"); > > - mtx_unlock(&Giant); > cam_periph_release(periph); > } > > Index: cam/scsi/scsi_cd.c > =================================================================== > --- cam/scsi/scsi_cd.c (revision 187838) > +++ cam/scsi/scsi_cd.c (working copy) > @@ -555,8 +555,6 @@ > snprintf(tmpstr, sizeof(tmpstr), "CAM CD unit %d", periph->unit_number); > snprintf(tmpstr2, sizeof(tmpstr2), "%d", periph->unit_number); > > - mtx_lock(&Giant); > - > sysctl_ctx_init(&softc->sysctl_ctx); > softc->flags |= CD_FLAG_SCTX_INIT; > softc->sysctl_tree = SYSCTL_ADD_NODE(&softc->sysctl_ctx, > @@ -565,7 +563,6 @@ > > if (softc->sysctl_tree == NULL) { > printf("cdsysctlinit: unable to allocate sysctl tree\n"); > - mtx_unlock(&Giant); > cam_periph_release(periph); > return; > } > @@ -579,7 +576,6 @@ > &softc->minimum_command_size, 0, cdcmdsizesysctl, "I", > "Minimum CDB size"); > > - mtx_unlock(&Giant); > cam_periph_release(periph); > } > > > thnx! > > roman > -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 20:45:27 2009 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 4AF6A10656FF for ; Wed, 28 Jan 2009 20:45:27 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from skerryvore.cs.uoguelph.ca (skerryvore.cs.uoguelph.ca [131.104.94.204]) by mx1.freebsd.org (Postfix) with ESMTP id 0436C8FC0A for ; Wed, 28 Jan 2009 20:45:26 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by skerryvore.cs.uoguelph.ca (8.13.1/8.13.1) with ESMTP id n0SKjOpZ017098; Wed, 28 Jan 2009 15:45:24 -0500 Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id n0SKmnS05456; Wed, 28 Jan 2009 15:48:49 -0500 (EST) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Wed, 28 Jan 2009 15:48:49 -0500 (EST) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Graham Todd In-Reply-To: <4980B0D8.9010506@bellanet.org> Message-ID: References: <20090122121750.GA14657@sr.se> <4980B0D8.9010506@bellanet.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.63 on 131.104.94.204 Cc: shaun@freebsd.org, current@freebsd.org, Gunnar Flygt , cy@freebsd.org Subject: Re: Backporting of Heimdal 1.1 to 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: Wed, 28 Jan 2009 20:45:28 -0000 On Wed, 28 Jan 2009, Graham Todd wrote: > Gunnar Flygt wrote: >> Is there any possibility that heimdal 1.1 that works beautifully in >> Current will be backported to FreeBSD-7.x? > > What if the port was updated to 1.1 to match base in CURRENT or to 1.2.1 > for testing? :-) Upstream heimdal is at 1.2.1 but I think there is some > pthread trickiness involved in getting it to compile (does anyone know > what is missing there?) For 1.1 you can change the values in the distinfo > and Makefile in the current port (which is at 1.0.1) and build a new 1.1 > package to use on 7.*. The rc script from the version in ports could use > modernizing to make more use of rc.subr magic, but things seem to work. > [good stuff snipped] I don't know if this will help or muddy the waters, but... The kerberos code in FreeBSD-CURRENT isn't Heimdal 1.1, but is code derived from it by Doug Rabson, I believe. (So, backporting kerberos from -current isn't the same thing as using Heimdal-1.1 on FreeBSD7.) I have built vanilla Heimdal-1.1 on FreeBSD7 and used it without difficulty, but I never re-linked any system binaries, I just used Heimdal-1.1 for my gssd. So I don't know what issues might be encountered re-linking FreeBSD7 sources against Heimdal-1.1. (Heimdal-1.2 fails to build, because it wants -lpthread added to some linkage, I vaguely recall.) As I said, don't know if this helps, rick From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 20:48:30 2009 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 848D81065723; Wed, 28 Jan 2009 20:48:30 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.freebsd.org (Postfix) with ESMTP id 5260B8FC0C; Wed, 28 Jan 2009 20:48:30 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.3/8.14.3) with ESMTP id n0SKmUah063137; Wed, 28 Jan 2009 12:48:30 -0800 (PST) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.3/8.14.3/Submit) id n0SKmTV1063136; Wed, 28 Jan 2009 12:48:29 -0800 (PST) (envelope-from david) Date: Wed, 28 Jan 2009 12:48:29 -0800 From: David Wolfskill To: Sam Leffler Message-ID: <20090128204829.GV90849@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Sam Leffler , current@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kjD6QjBV1CKugtA4" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org Subject: Re: Panic from wpa_supplicant in uma_large_free() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 20:48:33 -0000 --kjD6QjBV1CKugtA4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 28, 2009 at 10:40:33AM -0800, Sam Leffler wrote: > David Wolfskill wrote: > >After updating HEAD to around r187816 (I'm still using CVS), I get the > >following on my laptop (which makes an attempt to use wpa_supplicant): > > =20 >=20 > Please update. I'm guessing you've got a non-ath wireless device which= =20 > would explain why you tripped over this (bad me, didn't test w/ anything= =20 > but ath). OK; after update, the panic is gone. :-) d254(8.0-C)[1] uname -a FreeBSD d254... 8.0-CURRENT FreeBSD 8.0-CURRENT #934: Wed Jan 28 11:26:37 P= ST 2009 root@d254....:/common/S4/obj/usr/src/sys/CANARY i386 d254(8.0-C)[2]=20 Thanks! Peace, david --=20 David H. Wolfskill david@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --kjD6QjBV1CKugtA4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkmAxJwACgkQmprOCmdXAD3TggCeMbqDi818vGiTKPrOg6RMd52Y 5p4AnR2HMXSuQp+ZepUmK8Hfy/xM4n1G =VZxc -----END PGP SIGNATURE----- --kjD6QjBV1CKugtA4-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 21:00:25 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F31E10656E2 for ; Wed, 28 Jan 2009 21:00:25 +0000 (UTC) (envelope-from michiel@boland.org) Received: from smtp-vbr15.xs4all.nl (smtp-vbr15.xs4all.nl [194.109.24.35]) by mx1.freebsd.org (Postfix) with ESMTP id E83C78FC21 for ; Wed, 28 Jan 2009 21:00:24 +0000 (UTC) (envelope-from michiel@boland.org) Received: from aja.boland.org (91-43-215.ftth.xms.internl.net [82.215.43.91]) (authenticated bits=0) by smtp-vbr15.xs4all.nl (8.13.8/8.13.8) with ESMTP id n0SL0NAF020109 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 28 Jan 2009 22:00:23 +0100 (CET) (envelope-from michiel@boland.org) Message-ID: <4980C766.50207@boland.org> Date: Wed, 28 Jan 2009 22:00:22 +0100 From: Michiel Boland User-Agent: Thunderbird 2.0.0.19 (X11/20090125) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner Subject: console oddities X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2009 21:00:26 -0000 Hi. Some very minor issues in -CURRENT: On boot, the cursor on the vga screen goes to home position. So if you have console=comconsole in loader.conf, the login prompt on the vga terminal is sort-of lost amidst the initial boot output. Also during shutdown the tty settings appear to be incorrect. I am getting the good old staircase effect (line feeds without carriage returns.) This applies to both serial and vga consoles. Cheers Michiel From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 21:14:17 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5283106567F for ; Wed, 28 Jan 2009 21:14:17 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:7b8:613:100::211]) by mx1.freebsd.org (Postfix) with ESMTP id 40B4C8FC2A for ; Wed, 28 Jan 2009 21:14:17 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 38DDA1CDE9; Wed, 28 Jan 2009 22:14:16 +0100 (CET) Date: Wed, 28 Jan 2009 22:14:16 +0100 From: Ed Schouten To: Michiel Boland Message-ID: <20090128211416.GV17198@hoeg.nl> References: <4980C766.50207@boland.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MLcyhLwX/7AHNQNx" Content-Disposition: inline In-Reply-To: <4980C766.50207@boland.org> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: FreeBSD Current Subject: Re: console oddities X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2009 21:14:18 -0000 --MLcyhLwX/7AHNQNx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello Michiel, * Michiel Boland wrote: > On boot, the cursor on the vga screen goes to home position. > So if you have console=3Dcomconsole in loader.conf, the login prompt on t= he=20 > vga terminal is sort-of lost amidst the initial boot output. Ah, it seems we forget to sync the initial cursor position with the hardware cursor if we don't use syscons as the kernel console. Can you try the attached patch? > Also during shutdown the tty settings appear to be incorrect. I am=20 > getting the good old staircase effect (line feeds without carriage=20 > returns.) This applies to both serial and vga consoles. Yes, this is an issue I'll look into very soon. I've been a little busy the last couple of weeks, which means I've not been able to look into this issue yet. I hope to get it fixed somewhere this weekend. Let me know if the patch solves your issue. --=20 Ed Schouten WWW: http://80386.nl/ --MLcyhLwX/7AHNQNx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkmAyqgACgkQ52SDGA2eCwXmHACfcOVXAjQ1AaAT9uEHPrDNZ57U SU4An12TCJjYGBmVnTDaQwy1Kkl6xa80 =5kXD -----END PGP SIGNATURE----- --MLcyhLwX/7AHNQNx-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 21:16:31 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F284810656E4 for ; Wed, 28 Jan 2009 21:16:31 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:7b8:613:100::211]) by mx1.freebsd.org (Postfix) with ESMTP id B00618FC2D for ; Wed, 28 Jan 2009 21:16:31 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 1700D1CEB5; Wed, 28 Jan 2009 22:16:31 +0100 (CET) Date: Wed, 28 Jan 2009 22:16:31 +0100 From: Ed Schouten To: Michiel Boland Message-ID: <20090128211631.GW17198@hoeg.nl> References: <4980C766.50207@boland.org> <20090128211416.GV17198@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XCIqNWEteo88hZlY" Content-Disposition: inline In-Reply-To: <20090128211416.GV17198@hoeg.nl> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: FreeBSD Current Subject: Re: console oddities X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2009 21:16:33 -0000 --XCIqNWEteo88hZlY Content-Type: multipart/mixed; boundary="doUn1Hmx68n+7ij2" Content-Disposition: inline --doUn1Hmx68n+7ij2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Ed Schouten wrote: > Can you try the attached patch? Obviously I forgot to add the attachment. --=20 Ed Schouten WWW: http://80386.nl/ --doUn1Hmx68n+7ij2 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="syscons.diff" Content-Transfer-Encoding: quoted-printable Index: syscons.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- syscons.c (revision 187835) +++ syscons.c (working copy) @@ -2635,6 +2635,19 @@ } =20 static void +sc_sync_cursorpos(scr_stat *scp, int col, int row) +{ + + if (col >=3D scp->xsize) + col =3D 0; + if (row >=3D scp->ysize) + row =3D scp->ysize - 1; + scp->xpos =3D col; + scp->ypos =3D row; + scp->cursor_pos =3D scp->cursor_oldpos =3D row*scp->xsize + col; +} + +static void scinit(int unit, int flags) { =20 @@ -2743,13 +2756,7 @@ (void *)sc_buffer, FALSE); =20 /* move cursors to the initial positions */ - if (col >=3D scp->xsize) - col =3D 0; - if (row >=3D scp->ysize) - row =3D scp->ysize - 1; - scp->xpos =3D col; - scp->ypos =3D row; - scp->cursor_pos =3D scp->cursor_oldpos =3D row*scp->xsize + col; + sc_sync_cursorpos(scp, col, row); =20 if (sc_init_emulator(scp, SC_DFLT_TERM)) sc_init_emulator(scp, "*"); @@ -2763,6 +2770,9 @@ sc->dev[0] =3D sc_alloc_tty(0, "ttyv%r", unit * MAXCONS); scp =3D alloc_scp(sc, sc->first_vty); SC_STAT(sc->dev[0]) =3D scp; + + /* move cursors to the initial positions */ + sc_sync_cursorpos(scp, col, row); } sc->cur_scp =3D scp; =20 --doUn1Hmx68n+7ij2-- --XCIqNWEteo88hZlY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkmAyy8ACgkQ52SDGA2eCwX2NQCffmRxz+hf2OChXl3FSg/11/yF nhEAn0srAqJ7JGtKhaqxXyY8N4FylQ1p =6xjE -----END PGP SIGNATURE----- --XCIqNWEteo88hZlY-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 21:40:42 2009 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 EAB4810656D2 for ; Wed, 28 Jan 2009 21:40:42 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id 7B6718FC1A for ; Wed, 28 Jan 2009 21:40:42 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by ewy14 with SMTP id 14so4823359ewy.19 for ; Wed, 28 Jan 2009 13:40:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=SYMn0Tz12xdrPa1uHx8ZkvJmz1iKA2DKUly/0I85Euo=; b=dC+FLXF0NCuUloXssSSRprYd+zUjfA7AJHTYcix/Bi74OsQrxF3ehqCzC94JWphnju HU4OUnJ73zulgGzowxq1WeEGykPKj+OrWxC15lrK7Xaj5HmLBvmIzovR8JMo8/oTWMj6 AdZIin1GXggx/PNnOdMOgNdPPk1eK8lwh+f9Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Ot5A8MP6oxeyXzpCUZyjEeX9ex6T6lExfhpdlpybUDUi9thNqlY8aEmBk2FkG0kVGR 0A51fmKC2KMPqY1ThqasC2BCzuuazkIbGwIh1xXxtPcx3dqWhiATAJlHAkuT5KQvgELw Okh6fxyIaUYlj6NKNEwfIc+1VKduBGylyiW1Q= MIME-Version: 1.0 Received: by 10.86.76.20 with SMTP id y20mr889654fga.37.1233178841271; Wed, 28 Jan 2009 13:40:41 -0800 (PST) In-Reply-To: <20490.74948.qm@web63901.mail.re1.yahoo.com> References: <20490.74948.qm@web63901.mail.re1.yahoo.com> Date: Thu, 29 Jan 2009 00:40:41 +0300 Message-ID: From: pluknet To: barney_cordoba@yahoo.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: SATA drive device moving on 8.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: Wed, 28 Jan 2009 21:40:44 -0000 2009/1/28 Barney Cordoba : > I booted 8.0-current on a machine that was running 7 and the SATA drive > came up as ad4 instead of ad8 (as it is detected in 7). This is the case > was loading GENERIC. > > This is going to present a serious problem doing field upgrades as its > expected that fstab will be the same. What is the reason for the change and > is there any way to make it compatible with device detection in 7? > > Barney > I encountered this too after updating current.. close to November (do not remember exact date when it was changed). -- wbr, pluknet From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 22:07:36 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AEF351065680; Wed, 28 Jan 2009 22:07:36 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (77-93-215-190.static.masterinter.net [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id 5FA3F8FC1D; Wed, 28 Jan 2009 22:07:35 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 77E7D9CB07C; Wed, 28 Jan 2009 23:05:06 +0100 (CET) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (lev.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z8ShJ13RFD12; Wed, 28 Jan 2009 23:04:55 +0100 (CET) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id DADCD9CB0EC; Wed, 28 Jan 2009 23:04:54 +0100 (CET) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id n0SM4s0G067494; Wed, 28 Jan 2009 23:04:54 +0100 (CET) (envelope-from rdivacky) Date: Wed, 28 Jan 2009 23:04:54 +0100 From: Roman Divacky To: John Baldwin Message-ID: <20090128220454.GA66961@freebsd.org> References: <20090128193318.GA42071@freebsd.org> <200901281521.17674.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200901281521.17674.jhb@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org, scottl@freebsd.org Subject: Re: sysctl question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 22:07:37 -0000 On Wed, Jan 28, 2009 at 03:21:17PM -0500, John Baldwin wrote: > On Wednesday 28 January 2009 2:33:18 pm Roman Divacky wrote: > > hi > > > > we dont need Giant to be held for sysctl_ctx_init/SYSCTL_ADD_*, right? > > Ugh, it looks like the sysctl tree locking is woefully inadequate, so we > aren't quite ready for this yet. what do you mean? should all sysctl_ctx_init/SYSCTL_ADD_* consumers lock Giant? I didnt not find a single one (except the scsi stuff) that locks it... can you explain? thnx roman From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 22:41:37 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 402A510656D8; Wed, 28 Jan 2009 22:41:37 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0F7EE8FC36; Wed, 28 Jan 2009 22:41:37 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (pool-98-109-39-197.nwrknj.fios.verizon.net [98.109.39.197]) by cyrus.watson.org (Postfix) with ESMTPSA id A84AF46B0C; Wed, 28 Jan 2009 17:41:36 -0500 (EST) Received: from localhost (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.14.3/8.14.3) with ESMTP id n0SMfUnD000565; Wed, 28 Jan 2009 17:41:30 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Roman Divacky Date: Wed, 28 Jan 2009 17:41:24 -0500 User-Agent: KMail/1.9.7 References: <20090128193318.GA42071@freebsd.org> <200901281521.17674.jhb@freebsd.org> <20090128220454.GA66961@freebsd.org> In-Reply-To: <20090128220454.GA66961@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901281741.25021.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, 28 Jan 2009 17:41:30 -0500 (EST) X-Virus-Scanned: ClamAV 0.94.2/8915/Wed Jan 28 14:49:32 2009 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-current@freebsd.org, scottl@freebsd.org Subject: Re: sysctl question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 22:41:37 -0000 On Wednesday 28 January 2009 5:04:54 pm Roman Divacky wrote: > On Wed, Jan 28, 2009 at 03:21:17PM -0500, John Baldwin wrote: > > On Wednesday 28 January 2009 2:33:18 pm Roman Divacky wrote: > > > hi > > > > > > we dont need Giant to be held for sysctl_ctx_init/SYSCTL_ADD_*, right? > > > > Ugh, it looks like the sysctl tree locking is woefully inadequate, so we > > aren't quite ready for this yet. > > what do you mean? should all sysctl_ctx_init/SYSCTL_ADD_* consumers lock > Giant? I didnt not find a single one (except the scsi stuff) that locks > it... > > can you explain? thnx The supposed sysctl lock in kern_sysctl.c is actually worthless. None of the routines that actually manipulate the sysctl tree to add and remove nodes use it. Only sysctl itself uses it. It replaces an old 'memlock' hand-rolled lock from 4.xBSD (in 1.1 of kern_sysctl.c) that I think has to do with limiting the amount of wired memory, as it looks like sysctl used to always wire the userland buffers. I've just submitted some changes to p4 to make the sysctl lock actually protect the sysctl tree that I will test soon. Once that stuff is done then Giant can be removed here and other places. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 22:43:46 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 923D7106566B; Wed, 28 Jan 2009 22:43:46 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (77-93-215-190.static.masterinter.net [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id 4AD0E8FC17; Wed, 28 Jan 2009 22:43:46 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 2E9959CB045; Wed, 28 Jan 2009 23:41:17 +0100 (CET) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (lev.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WZbKGmXtEthW; Wed, 28 Jan 2009 23:41:14 +0100 (CET) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 8E3C19CB0EC; Wed, 28 Jan 2009 23:41:14 +0100 (CET) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id n0SMfEwg082900; Wed, 28 Jan 2009 23:41:14 +0100 (CET) (envelope-from rdivacky) Date: Wed, 28 Jan 2009 23:41:14 +0100 From: Roman Divacky To: John Baldwin Message-ID: <20090128224114.GA81550@freebsd.org> References: <20090128193318.GA42071@freebsd.org> <200901281521.17674.jhb@freebsd.org> <20090128220454.GA66961@freebsd.org> <200901281741.25021.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200901281741.25021.jhb@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org, scottl@freebsd.org Subject: Re: sysctl question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 22:43:47 -0000 On Wed, Jan 28, 2009 at 05:41:24PM -0500, John Baldwin wrote: > On Wednesday 28 January 2009 5:04:54 pm Roman Divacky wrote: > > On Wed, Jan 28, 2009 at 03:21:17PM -0500, John Baldwin wrote: > > > On Wednesday 28 January 2009 2:33:18 pm Roman Divacky wrote: > > > > hi > > > > > > > > we dont need Giant to be held for sysctl_ctx_init/SYSCTL_ADD_*, right? > > > > > > Ugh, it looks like the sysctl tree locking is woefully inadequate, so we > > > aren't quite ready for this yet. > > > > what do you mean? should all sysctl_ctx_init/SYSCTL_ADD_* consumers lock > > Giant? I didnt not find a single one (except the scsi stuff) that locks > > it... > > > > can you explain? thnx > > The supposed sysctl lock in kern_sysctl.c is actually worthless. None of the > routines that actually manipulate the sysctl tree to add and remove nodes use > it. Only sysctl itself uses it. It replaces an old 'memlock' hand-rolled > lock from 4.xBSD (in 1.1 of kern_sysctl.c) that I think has to do with > limiting the amount of wired memory, as it looks like sysctl used to always > wire the userland buffers. I've just submitted some changes to p4 to make > the sysctl lock actually protect the sysctl tree that I will test soon. Once > that stuff is done then Giant can be removed here and other places. cool! I found no other places where Giant is used for locking sysctl but please commit at least the patch I posted thnx! roman From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 22:59:57 2009 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 24CA7106564A; Wed, 28 Jan 2009 22:59:57 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id D214B8FC14; Wed, 28 Jan 2009 22:59:56 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0SMxsBX030406; Wed, 28 Jan 2009 17:59:54 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.14.3/8.14.3) with ESMTP id n0SMxsUm095657; Wed, 28 Jan 2009 17:59:54 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id DB0247302F; Wed, 28 Jan 2009 17:59:53 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090128225953.DB0247302F@freebsd-current.sentex.ca> Date: Wed, 28 Jan 2009 17:59:53 -0500 (EST) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on powerpc/powerpc 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: Wed, 28 Jan 2009 22:59:57 -0000 TB --- 2009-01-28 21:20:13 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-01-28 21:20:13 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2009-01-28 21:20:13 - cleaning the object tree TB --- 2009-01-28 21:20:43 - cvsupping the source tree TB --- 2009-01-28 21:20:43 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2009-01-28 21:20:52 - building world TB --- 2009-01-28 21:20:52 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-28 21:20:52 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-28 21:20:52 - TARGET=powerpc TB --- 2009-01-28 21:20:52 - TARGET_ARCH=powerpc TB --- 2009-01-28 21:20:52 - TZ=UTC TB --- 2009-01-28 21:20:52 - __MAKE_CONF=/dev/null TB --- 2009-01-28 21:20:52 - cd /src TB --- 2009-01-28 21:20:52 - /usr/bin/make -B buildworld >>> World build started on Wed Jan 28 21:20:54 UTC 2009 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Wed Jan 28 22:44:43 UTC 2009 TB --- 2009-01-28 22:44:43 - generating LINT kernel config TB --- 2009-01-28 22:44:43 - cd /src/sys/powerpc/conf TB --- 2009-01-28 22:44:43 - /usr/bin/make -B LINT TB --- 2009-01-28 22:44:43 - building LINT kernel TB --- 2009-01-28 22:44:43 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-28 22:44:43 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-28 22:44:43 - TARGET=powerpc TB --- 2009-01-28 22:44:43 - TARGET_ARCH=powerpc TB --- 2009-01-28 22:44:43 - TZ=UTC TB --- 2009-01-28 22:44:43 - __MAKE_CONF=/dev/null TB --- 2009-01-28 22:44:43 - cd /src TB --- 2009-01-28 22:44:43 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Jan 28 22:44:43 UTC 2009 >>> 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 [...] /src/sys/dev/adb/adb_mouse.c: In function 'ams_close': /src/sys/dev/adb/adb_mouse.c:357: error: invalid operands to binary & /src/sys/dev/adb/adb_mouse.c: In function 'ams_poll': /src/sys/dev/adb/adb_mouse.c:369: error: invalid operands to binary & /src/sys/dev/adb/adb_mouse.c: In function 'ams_read': /src/sys/dev/adb/adb_mouse.c:398: error: invalid operands to binary & /src/sys/dev/adb/adb_mouse.c: In function 'ams_ioctl': /src/sys/dev/adb/adb_mouse.c:488: error: invalid operands to binary & *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-28 22:59:53 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-28 22:59:53 - ERROR: failed to build lint kernel TB --- 2009-01-28 22:59:53 - 4792.13 user 403.84 system 5980.43 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 23:03:44 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DAB8F1065670 for ; Wed, 28 Jan 2009 23:03:44 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 28DAB8FC0A for ; Wed, 28 Jan 2009 23:03:43 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: (qmail invoked by alias); 28 Jan 2009 23:03:42 -0000 Received: from p54A3E68D.dip.t-dialin.net (EHLO tron.homeunix.org) [84.163.230.141] by mail.gmx.net (mp058) with SMTP; 29 Jan 2009 00:03:42 +0100 X-Authenticated: #1673122 X-Provags-ID: V01U2FsdGVkX1/ksFE8BdvkwOLKXAbsQW+OhPF2LaherOIRgA/L3G qM0Vo8XirsqxOM Message-ID: <4980E44D.1040604@gmx.de> Date: Thu, 29 Jan 2009 00:03:41 +0100 From: Christoph Mallon User-Agent: Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Channa References: <515c64960901280339m17fa9309v2e1bc3f55454ab@mail.gmail.com> <49804597.6040303@gmx.de> <515c64960901280401w1e1d08bfx29adc124bc749c4a@mail.gmail.com> <515c64960901280425y642a190ka31409cfc2a2fd8f@mail.gmail.com> <49804FCE.7090405@gmx.de> <515c64960901280437hd4f7b2dx36a1774afe2f5646@mail.gmail.com> In-Reply-To: <515c64960901280437hd4f7b2dx36a1774afe2f5646@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.73 Cc: freebsd-current@freebsd.org Subject: Re: Jemalloc SEGV for 1MB chunk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 23:03:45 -0000 Channa schrieb: > Hi, > Thanks for the reply. > Does the same behaviour seen on FreeBSD environment? > I am using FreeBSD libraries to test the test code. > > So according to you its better to NULL terminate in the test code to avoid > this undefined behaviour? You have to avoid undefined behaviour. The moment you cause undefined behaviour the game is over. BTW: The character is named NUL. NULL is the name of the symbolic null pointer constant. From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 23:04:42 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E907C1065675 for ; Wed, 28 Jan 2009 23:04:42 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 379C38FC1A for ; Wed, 28 Jan 2009 23:04:42 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: (qmail invoked by alias); 28 Jan 2009 23:04:41 -0000 Received: from p54A3E68D.dip.t-dialin.net (EHLO tron.homeunix.org) [84.163.230.141] by mail.gmx.net (mp017) with SMTP; 29 Jan 2009 00:04:41 +0100 X-Authenticated: #1673122 X-Provags-ID: V01U2FsdGVkX1/fmZ9HvFjfXWqdyY6uU08RRaC4fNETVnH5KKcLj7 JRDVZ1d5Xj9v1C Message-ID: <4980E488.60302@gmx.de> Date: Thu, 29 Jan 2009 00:04:40 +0100 From: Christoph Mallon User-Agent: Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Channa References: <515c64960901280339m17fa9309v2e1bc3f55454ab@mail.gmail.com> <49804597.6040303@gmx.de> <515c64960901280401w1e1d08bfx29adc124bc749c4a@mail.gmail.com> <515c64960901280425y642a190ka31409cfc2a2fd8f@mail.gmail.com> <49804FCE.7090405@gmx.de> <515c64960901280445l1ab33256sae2e69df30efe502@mail.gmail.com> In-Reply-To: <515c64960901280445l1ab33256sae2e69df30efe502@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.73 Cc: freebsd-current@freebsd.org Subject: Re: Jemalloc SEGV for 1MB chunk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jan 2009 23:04:43 -0000 Channa schrieb: > Hi, > "This really does not belong on freebsd-current@." by this you mean to > say in FreeBSD current this problem is not seen. > > Are you referring to FreeBSD current jemalloc version which is "1.183". > Since i am using the same Version of jemalloc to test the code. > > Could you please elaborate more if my understanding on your statment is correct? It means this belongs on a C beginners list. From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 23:46:14 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66647106566C for ; Wed, 28 Jan 2009 23:46:14 +0000 (UTC) (envelope-from rbgarga@gmail.com) Received: from mail-qy0-f17.google.com (mail-qy0-f17.google.com [209.85.221.17]) by mx1.freebsd.org (Postfix) with ESMTP id 073288FC1B for ; Wed, 28 Jan 2009 23:46:13 +0000 (UTC) (envelope-from rbgarga@gmail.com) Received: by qyk10 with SMTP id 10so11582390qyk.19 for ; Wed, 28 Jan 2009 15:46:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=4DaBgMrgBZ/pac7y3toI28rdHwd89GZcEN8i/GH5LdM=; b=o/aYyPxG0Wgg/uvkMA8iLnF2s3Um/goGPsv+PD/NhWAbGYA5YdN8rJ7nHIl0nYGy1i RY6mS4/XECv20SRdJIb1GczypMd4J9oGfq5XXoPdsTHctqrTRgVXzvyS36oDteNhtKYE D7WADiSmUwdiwwLwKH9nvXgg5nxoHwQgYwIg8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=LAgvtf5ES+SOHgT2Mm+iM6V4aRCMUUG1DLqZfUtM2GPayXsuJgjOjmEvx/mYuY5QNY bEJTgRBweyciqD5F32kDJ721sUfmENj24GsVvIcAVRkREoLWpinGdv8ZBsywqNhTalCS 31ZmJzPUtrhAkmd1QZAFWMImzV37XD8W4mtQ8= MIME-Version: 1.0 Received: by 10.214.43.17 with SMTP id q17mr584218qaq.58.1233186373331; Wed, 28 Jan 2009 15:46:13 -0800 (PST) In-Reply-To: <20090128211416.GV17198@hoeg.nl> References: <4980C766.50207@boland.org> <20090128211416.GV17198@hoeg.nl> Date: Wed, 28 Jan 2009 21:46:13 -0200 Message-ID: <747dc8f30901281546o6803dddey2bdf36e8ced5128@mail.gmail.com> From: Renato Botelho To: Ed Schouten Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Michiel Boland , FreeBSD Current Subject: Re: console oddities X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2009 23:46:14 -0000 On Wed, Jan 28, 2009 at 7:14 PM, Ed Schouten wrote: > Hello Michiel, > > * Michiel Boland wrote: >> On boot, the cursor on the vga screen goes to home position. >> So if you have console=comconsole in loader.conf, the login prompt on the >> vga terminal is sort-of lost amidst the initial boot output. > > Ah, it seems we forget to sync the initial cursor position with the > hardware cursor if we don't use syscons as the kernel console. Can you > try the attached patch? > >> Also during shutdown the tty settings appear to be incorrect. I am >> getting the good old staircase effect (line feeds without carriage >> returns.) This applies to both serial and vga consoles. > > Yes, this is an issue I'll look into very soon. I've been a little busy > the last couple of weeks, which means I've not been able to look into > this issue yet. I hope to get it fixed somewhere this weekend. > > Let me know if the patch solves your issue. I noted something strange here too, i'm using a 1280x1024 console and when I do a shutdown it seems to ignore the resolution and use just a part (left superior) of the screen to show shutdown proccess messages. I'm using recent -current -- Renato Botelho From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 02:04:48 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B4E8106566B; Thu, 29 Jan 2009 02:04:48 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id B332F8FC1C; Thu, 29 Jan 2009 02:04:47 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.localnet (Inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n0T1nK0t023701 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Jan 2009 12:19:21 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org, barney_cordoba@yahoo.com Date: Thu, 29 Jan 2009 12:18:59 +1030 User-Agent: KMail/1.10.3 (Linux/2.6.27-9-generic; KDE/4.1.3; i686; ; ) References: <20490.74948.qm@web63901.mail.re1.yahoo.com> In-Reply-To: <20490.74948.qm@web63901.mail.re1.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5486772.tdyJMEhqBH"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200901291219.17379.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: current@freebsd.org Subject: Re: SATA drive device moving on 8.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: Thu, 29 Jan 2009 02:04:48 -0000 --nextPart5486772.tdyJMEhqBH Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 29 January 2009 03:48:11 Barney Cordoba wrote: > I booted 8.0-current on a machine that was running 7 and the SATA drive > came up as ad4 instead of ad8 (as it is detected in 7). This is the case > was loading GENERIC. > > This is going to present a serious problem doing field upgrades as its > expected that fstab will be the same. What is the reason for the change a= nd > is there any way to make it compatible with device detection in 7? I don't know how you can change it back, but you can use glabel and tunefs = =2DL=20 and then modify /etc/fstab to use /dev/ufs/foo. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart5486772.tdyJMEhqBH Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQBJgQsN5ZPcIHs/zowRAmd5AJ9w6y1QQjyeAxe/74kQtmbS1bUO2gCcCJC2 E3CotZC8ESKYXc3UvrG3mJg= =oZh4 -----END PGP SIGNATURE----- --nextPart5486772.tdyJMEhqBH-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 02:04:48 2009 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 4B4E8106566B; Thu, 29 Jan 2009 02:04:48 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id B332F8FC1C; Thu, 29 Jan 2009 02:04:47 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.localnet (Inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n0T1nK0t023701 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Jan 2009 12:19:21 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org, barney_cordoba@yahoo.com Date: Thu, 29 Jan 2009 12:18:59 +1030 User-Agent: KMail/1.10.3 (Linux/2.6.27-9-generic; KDE/4.1.3; i686; ; ) References: <20490.74948.qm@web63901.mail.re1.yahoo.com> In-Reply-To: <20490.74948.qm@web63901.mail.re1.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5486772.tdyJMEhqBH"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200901291219.17379.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: current@freebsd.org Subject: Re: SATA drive device moving on 8.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: Thu, 29 Jan 2009 02:04:48 -0000 --nextPart5486772.tdyJMEhqBH Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 29 January 2009 03:48:11 Barney Cordoba wrote: > I booted 8.0-current on a machine that was running 7 and the SATA drive > came up as ad4 instead of ad8 (as it is detected in 7). This is the case > was loading GENERIC. > > This is going to present a serious problem doing field upgrades as its > expected that fstab will be the same. What is the reason for the change a= nd > is there any way to make it compatible with device detection in 7? I don't know how you can change it back, but you can use glabel and tunefs = =2DL=20 and then modify /etc/fstab to use /dev/ufs/foo. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart5486772.tdyJMEhqBH Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQBJgQsN5ZPcIHs/zowRAmd5AJ9w6y1QQjyeAxe/74kQtmbS1bUO2gCcCJC2 E3CotZC8ESKYXc3UvrG3mJg= =oZh4 -----END PGP SIGNATURE----- --nextPart5486772.tdyJMEhqBH-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 02:13:05 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A2CD106566B for ; Thu, 29 Jan 2009 02:13:05 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 90C238FC0A for ; Thu, 29 Jan 2009 02:13:04 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.localnet (Inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n0T2D2pn024427 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Jan 2009 12:43:02 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Thu, 29 Jan 2009 12:42:52 +1030 User-Agent: KMail/1.10.3 (Linux/2.6.27-9-generic; KDE/4.1.3; i686; ; ) References: <20090128155340.GA75143@lpthe.jussieu.fr> <7508A5B5-C6D2-498A-AEA1-D84E85F1D743@mac.com> In-Reply-To: <7508A5B5-C6D2-498A-AEA1-D84E85F1D743@mac.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart10919142.Lfm9S8zSC3"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200901291243.00378.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: Michel Talon Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 02:13:05 -0000 --nextPart10919142.Lfm9S8zSC3 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 29 January 2009 05:20:33 Chuck Swiger wrote: > Evidently, the FSF is now claiming that all object code produced from > GCC 4.2.2 and later is GPLv3-licensed, and only their exception > permits you to distribute executables compiled using an "Eligible > Compilation Process" under the terms of some other license. The "eligible compilation process" is where you use GCC and GPL compatible= =20 software. I think for the FreeBSD project that is fine. IANAL of course :) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart10919142.Lfm9S8zSC3 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQBJgRCl5ZPcIHs/zowRAmoSAKCEwRThIYDcsNu03HEI63BQ2jvGawCfSfoI tXgspcm+klG1OqiPHyadtwU= =IfSS -----END PGP SIGNATURE----- --nextPart10919142.Lfm9S8zSC3-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 02:19:58 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 75DBA1065670 for ; Thu, 29 Jan 2009 02:19:58 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 17C738FC08 for ; Thu, 29 Jan 2009 02:19:58 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id BC78728448 for ; Thu, 29 Jan 2009 10:19:55 +0800 (CST) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id 1D149EB8E0B; Thu, 29 Jan 2009 10:19:55 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id byxnk239atPt; Thu, 29 Jan 2009 10:19:50 +0800 (CST) Received: from charlie.delphij.net (adsl-76-237-33-62.dsl.pltn13.sbcglobal.net [76.237.33.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 9DA25EB868A; Thu, 29 Jan 2009 10:19:48 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=VECjyA6d/JOq05ygt9P0LZCNAIJZSGhsY9yCQPNj6AxnPtJP8jDSlYB6vxTQtAmff mfxnwiB0hpeuMKR6m/HzQ== Message-ID: <49811242.7030106@delphij.net> Date: Wed, 28 Jan 2009 18:19:46 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.19 (X11/20090112) MIME-Version: 1.0 To: Daniel O'Connor References: <20090128155340.GA75143@lpthe.jussieu.fr> <7508A5B5-C6D2-498A-AEA1-D84E85F1D743@mac.com> <200901291243.00378.doconnor@gsoft.com.au> In-Reply-To: <200901291243.00378.doconnor@gsoft.com.au> X-Enigmail-Version: 0.95.7 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Michel Talon Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) 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: Thu, 29 Jan 2009 02:19:58 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Daniel O'Connor wrote: > On Thursday 29 January 2009 05:20:33 Chuck Swiger wrote: >> Evidently, the FSF is now claiming that all object code produced from >> GCC 4.2.2 and later is GPLv3-licensed, and only their exception >> permits you to distribute executables compiled using an "Eligible >> Compilation Process" under the terms of some other license. > > The "eligible compilation process" is where you use GCC and GPL compatible > software. > > I think for the FreeBSD project that is fine. I agree, this term seems to be targeted to companies behind closed source optimizers. Speaking for myself, I think FreeBSD would avoid GPLv3 code where possible to minimize the risk it would introduce to commercial users of our codebase, we want our code be used by as many people as possible to better exploit its value. Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmBEkEACgkQi+vbBBjt66D4rwCeKJwDk8Nq1MILSCMTKw5Tx/Eq 5mQAn10cxFjkUfHH1N0J7VJC3KRYBAXB =lMS/ -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 02:38:42 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECAA9106566B for ; Thu, 29 Jan 2009 02:38:41 +0000 (UTC) (envelope-from eitanadlerlist@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.173]) by mx1.freebsd.org (Postfix) with ESMTP id B591B8FC1B for ; Thu, 29 Jan 2009 02:38:41 +0000 (UTC) (envelope-from eitanadlerlist@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so7734276wfg.7 for ; Wed, 28 Jan 2009 18:38:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=J0EqZYBe2BT2gfW1guUU/EpuPZl8+UzYmqX/7q8vqQQ=; b=PeqQSEzgpYvSCFVh066BUVp3Bhr4SHxSrClexmH07WPpToNtMc27vTVywNnE/K1vdr WBjlwezoA8paNlaf++e/y0/bB7mxloYTYnKvKskkW4jJ4Hm3Q3757q/aTeeBehZJ/nAa jMxHr9SiiAqUK2iWMgpvWf9h8UOe1/z9xsRnU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; 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=sr5uDDOEC7127dZ8Algvffk05JwQ84DLA5F0dZt9PUh0nAAp4FjYatAlXmHldDCN8o QNGcqywSG8qqw4v+zHm1YZSOswAE7vf2pqbcO1uvBJsxBSyGTdqn9lkWCHFBBZXn0vM6 JQkk7yFiDLJVmk9IQnzihnTX9forl7H6RHgoo= Received: by 10.142.141.21 with SMTP id o21mr573862wfd.327.1233196721086; Wed, 28 Jan 2009 18:38:41 -0800 (PST) Received: from aargh.lan (ool-182fcc8b.dyn.optonline.net [24.47.204.139]) by mx.google.com with ESMTPS id 32sm10400628wfa.40.2009.01.28.18.38.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 28 Jan 2009 18:38:40 -0800 (PST) Message-ID: <498116AB.2060105@gmail.com> Date: Wed, 28 Jan 2009 21:38:35 -0500 From: Eitan Adler User-Agent: Mozilla (X11; U; FreeBSD i386; en-US; ) Gecko Thunderbird Mnenhy/0.7.5.666 MIME-Version: 1.0 To: d@delphij.net References: <20090128155340.GA75143@lpthe.jussieu.fr> <7508A5B5-C6D2-498A-AEA1-D84E85F1D743@mac.com> <200901291243.00378.doconnor@gsoft.com.au> <49811242.7030106@delphij.net> In-Reply-To: <49811242.7030106@delphij.net> X-Enigmail-Version: 0.95.7 OpenPGP: id=E9C2CCD1; url=pgp.mit.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Michel Talon Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 02:38:42 -0000 Xin LI wrote: > Daniel O'Connor wrote: >> On Thursday 29 January 2009 05:20:33 Chuck Swiger wrote: >>> Evidently, the FSF is now claiming that all object code produced from >>> GCC 4.2.2 and later is GPLv3-licensed, and only their exception >>> permits you to distribute executables compiled using an "Eligible >>> Compilation Process" under the terms of some other license. >> The "eligible compilation process" is where you use GCC and GPL compatible >> software. > >> I think for the FreeBSD project that is fine. > > I agree, this term seems to be targeted to companies behind closed > source optimizers. Speaking for myself, I think FreeBSD would avoid > GPLv3 code where possible to minimize the risk it would introduce to > commercial users of our codebase, we want our code be used by as many > people as possible to better exploit its value. I don't think this is a "where possible" case. While version 4.3 may not include improvements necessary for an operating system future versions will almost surely have some. IMHO avoiding GCC because of its license is pointless. Commercial users will already be avoiding gcc (if it matters to them) because of the GPLv2. The FSF has made it clear that the output of the compiler is (truly) free for anyone who may have had any ounce of doubt. To quote from the FAQ: Who does this change affect? Nobody who is currently using GCC should be affected by this change. If we were replacing a BSD licensed compiler with a GPL licensed compiler it would be a different story. > > Cheers, _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Eitan Adler "Security is increased by designing for the way humans actually behave." -Jakob Nielsen From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 03:00:43 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7A32106564A for ; Thu, 29 Jan 2009 03:00:43 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 1FD458FC1C for ; Thu, 29 Jan 2009 03:00:42 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.localnet (Inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n0T30Kk5026313 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Jan 2009 13:30:21 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: d@delphij.net Date: Thu, 29 Jan 2009 13:30:09 +1030 User-Agent: KMail/1.10.3 (Linux/2.6.27-9-generic; KDE/4.1.3; i686; ; ) References: <20090128155340.GA75143@lpthe.jussieu.fr> <200901291243.00378.doconnor@gsoft.com.au> <49811242.7030106@delphij.net> In-Reply-To: <49811242.7030106@delphij.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1765109.TEC4zHrJ2t"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200901291330.18007.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: freebsd-current@freebsd.org, Michel Talon Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 03:00:44 -0000 --nextPart1765109.TEC4zHrJ2t Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 29 January 2009 12:49:46 Xin LI wrote: > > The "eligible compilation process" is where you use GCC and GPL > > compatible software. > > > > I think for the FreeBSD project that is fine. > > I agree, this term seems to be targeted to companies behind closed > source optimizers. Speaking for myself, I think FreeBSD would avoid > GPLv3 code where possible to minimize the risk it would introduce to > commercial users of our codebase, we want our code be used by as many > people as possible to better exploit its value. Seems like a fairly marginal case (speaking as someone who ships proprietar= y=20 software built by GCC running on FreeBSD). I think for the compiler/tool chain GPLv3 is OK, but for example, in librar= ies=20 it would [very] bad. Luckily I don't see that being a problem for FreeBSD :) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1765109.TEC4zHrJ2t Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQBJgRu75ZPcIHs/zowRAqKFAJ9fG6pujk/kA4mM9QtFDyzuQj2VGQCfQ9lZ ZPpz3gXfeJGU+bMDJzRN1DI= =ljFu -----END PGP SIGNATURE----- --nextPart1765109.TEC4zHrJ2t-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 03:06:13 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B920A106566B; Thu, 29 Jan 2009 03:06:13 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmmtao102.cox.net (eastrmmtao102.cox.net [68.230.240.8]) by mx1.freebsd.org (Postfix) with ESMTP id 35FE48FC25; Thu, 29 Jan 2009 03:06:13 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmimpo03.cox.net ([68.1.16.126]) by eastrmmtao102.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20090129030612.DRXJ8735.eastrmmtao102.cox.net@eastrmimpo03.cox.net>; Wed, 28 Jan 2009 22:06:12 -0500 Received: from serene.no-ip.org ([72.200.37.152]) by eastrmimpo03.cox.net with bizsmtp id 9F6C1b0043Gxf8w02F6CDF; Wed, 28 Jan 2009 22:06:12 -0500 X-Authority-Analysis: v=1.0 c=1 a=qHb3f0E2TVIrIUXHt1AA:9 a=SSqCnDTjqL6rX6zc62AA:7 a=Z7OEIflKUAHBFoiAXdyWz_rlUL8A:4 a=SV7veod9ZcQA:10 a=4vB-4DCPJfMA:10 a=LY0hPdMaydYA:10 X-CM-Score: 0.00 Date: Wed, 28 Jan 2009 21:06:15 -0600 From: "Conrad J. Sabatier" To: =?UTF-8?B?U8O4cmVu?= Schmidt Message-ID: <20090128210615.101b3cd2@serene.no-ip.org> In-Reply-To: <9AB4BB55-6F88-434D-B2BD-1E00DDCF7A8F@FreeBSD.ORG> References: <20090114163846.0dfa6080@serene.no-ip.org> <20090118050045.39b8ab47@serene.no-ip.org> <9AB4BB55-6F88-434D-B2BD-1E00DDCF7A8F@FreeBSD.ORG> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.14.4; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@FreeBSD.ORG Subject: Re: nv-pv2 (Was: I give up) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2009 03:06:14 -0000 On Sun, 18 Jan 2009 13:20:43 +0100 S=C3=B8ren Schmidt wrote: > On 18Jan, 2009, at 12:00 , Conrad J. Sabatier wrote: [snip] > > So where the heck is my CD/DVD connected to? This is one of the > > most bizarre problems I've ever encountered. Pciconf, camcontrol > > both turn up equally blank info. I'm quite at a loss here. >=20 > If the optical device is SATA it might not be detected, the code for =20 > SATA ATAPI is still fragile. Ah, so then there's still some hope on the horizon? :-) > If its PATA it should be detected.. >=20 > > > > > > And what could be the reason for no ATA channels 0 or 1 showing up? >=20 > Those two devices are reserved for the legacy ports. >=20 > -S=C3=B8ren_______________________________________________ Thanks for the followup. Do you think you could maybe e-mail me directly if/when something promising gets imported into the source tree? Thanks! --=20 Conrad J. Sabatier From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 03:10:12 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 618641065670 for ; Thu, 29 Jan 2009 03:10:12 +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 24C378FC1E for ; Thu, 29 Jan 2009 03:10:12 +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.3/8.14.3) with ESMTP id n0T39p87009639; Wed, 28 Jan 2009 19:09:51 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.3/8.14.3/Submit) id n0T39oFg009638; Wed, 28 Jan 2009 19:09:50 -0800 (PST) (envelope-from sgk) Date: Wed, 28 Jan 2009 19:09:50 -0800 From: Steve Kargl To: "Daniel O'Connor" Message-ID: <20090129030950.GA9605@troutmask.apl.washington.edu> References: <20090128155340.GA75143@lpthe.jussieu.fr> <200901291243.00378.doconnor@gsoft.com.au> <49811242.7030106@delphij.net> <200901291330.18007.doconnor@gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200901291330.18007.doconnor@gsoft.com.au> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org, d@delphij.net, Michel Talon Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 03:10:12 -0000 On Thu, Jan 29, 2009 at 01:30:09PM +1030, Daniel O'Connor wrote: > On Thursday 29 January 2009 12:49:46 Xin LI wrote: > > > The "eligible compilation process" is where you use GCC and GPL > > > compatible software. > > > > > > I think for the FreeBSD project that is fine. > > > > I agree, this term seems to be targeted to companies behind closed > > source optimizers. Speaking for myself, I think FreeBSD would avoid > > GPLv3 code where possible to minimize the risk it would introduce to > > commercial users of our codebase, we want our code be used by as many > > people as possible to better exploit its value. > > Seems like a fairly marginal case (speaking as someone who ships proprietary > software built by GCC running on FreeBSD). > > I think for the compiler/tool chain GPLv3 is OK, but for example, in libraries > it would [very] bad. > > Luckily I don't see that being a problem for FreeBSD :) > The FSF has not decided what to do about the runtime libraries. These are currently gplv2+link time exception. In the future, the libraries may be gplv3 + some new link time exception. - Steve From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 03:13:04 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0DAFB106564A for ; Thu, 29 Jan 2009 03:13:04 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by mx1.freebsd.org (Postfix) with ESMTP id B15948FC0C for ; Thu, 29 Jan 2009 03:13:03 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so2898639yxb.13 for ; Wed, 28 Jan 2009 19:13:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:received:received :message-id:in-reply-to:references:date:subject:from:to:user-agent :mime-version:content-type:content-transfer-encoding:x-priority :importance; bh=4MITLAsnqmwcfZgelfgjdUeSrPIFdGN0vKDzU8NwPeg=; b=bdbBi+MRIIExJo9nnadYewXnbjOCfKdYptRoppO2N7sgr8exdz2JmSZqfJszPhy6gN gt7MelKWcogt5eD/2Ry4yiSbMQUIOjdJhkPGYF7yPTOI/+0uxOYtu1dDZQtC1IdIheUV 3ZAYHQyAioP4UUcwNbUoXyDrWOav/E/3y461w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:in-reply-to:references:date:subject:from:to :user-agent:mime-version:content-type:content-transfer-encoding :x-priority:importance; b=vmLQlrlR+8kL8Dl4P4Z1lW6f4KAo7zyG2fTqdKhdn2f83+DCwKWTQC8QCEmy57kxzF YKkplEEo6TwLgx/mObaJuQYCUVrMylgsKv/CZHQa/Ple9zzFb+SwYrPbhJWwmN/oLt5E 6aooJSczELpTl4l6Cm4/vnwbyEVW4mTtv5fMU= Received: by 10.100.33.4 with SMTP id g4mr820350ang.122.1233198783187; Wed, 28 Jan 2009 19:13:03 -0800 (PST) Received: from cygnus.homeunix.com ([189.71.8.214]) by mx.google.com with ESMTPS id c28sm21359624anc.25.2009.01.28.19.13.01 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 28 Jan 2009 19:13:02 -0800 (PST) Sender: Nenhum_de_Nos Received: by cygnus.homeunix.com (Postfix, from userid 80) id 8C7A4B8061; Thu, 29 Jan 2009 00:12:57 -0300 (BRT) Received: from 10.1.1.80 (SquirrelMail authenticated user matheus) by lamneth with HTTP; Thu, 29 Jan 2009 01:12:57 -0200 (BRST) Message-ID: <191beebcb8e400a659afaa9d997462c0.squirrel@lamneth> In-Reply-To: <200901291219.17379.doconnor@gsoft.com.au> References: <20490.74948.qm@web63901.mail.re1.yahoo.com> <200901291219.17379.doconnor@gsoft.com.au> Date: Thu, 29 Jan 2009 01:12:57 -0200 (BRST) From: "Nenhum_de_Nos" To: freebsd-current@freebsd.org User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: SATA drive device moving on 8.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: Thu, 29 Jan 2009 03:13:04 -0000 On Wed, January 28, 2009 23:48, Daniel O'Connor wrote: > On Thursday 29 January 2009 03:48:11 Barney Cordoba wrote: >> I booted 8.0-current on a machine that was running 7 and the SATA drive >> came up as ad4 instead of ad8 (as it is detected in 7). This is the case >> was loading GENERIC. >> >> This is going to present a serious problem doing field upgrades as its >> expected that fstab will be the same. What is the reason for the change >> and >> is there any way to make it compatible with device detection in 7? > > I don't know how you can change it back, but you can use glabel and tunefs > -L > and then modify /etc/fstab to use /dev/ufs/foo. even / can use this ? just current has this feature ? thanks, matheus -- We will call you cygnus, The God of balance you shall be From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 03:28:57 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9687106564A for ; Thu, 29 Jan 2009 03:28:57 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from nschwmtas02p.mx.bigpond.com (nschwmtas02p.mx.bigpond.com [61.9.189.140]) by mx1.freebsd.org (Postfix) with ESMTP id 595EA8FC13 for ; Thu, 29 Jan 2009 03:28:56 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from nschwotgx02p.mx.bigpond.com ([124.188.162.219]) by nschwmtas02p.mx.bigpond.com with ESMTP id <20090129032850.WOIT22514.nschwmtas02p.mx.bigpond.com@nschwotgx02p.mx.bigpond.com> for ; Thu, 29 Jan 2009 03:28:50 +0000 Received: from areilly.bpa.nu ([124.188.162.219]) by nschwotgx02p.mx.bigpond.com with ESMTP id <20090129032850.MKOY6144.nschwotgx02p.mx.bigpond.com@areilly.bpa.nu> for ; Thu, 29 Jan 2009 03:28:50 +0000 Received: (qmail 86779 invoked by uid 501); 29 Jan 2009 03:28:34 -0000 Date: Thu, 29 Jan 2009 14:28:34 +1100 From: Andrew Reilly To: Steve Kargl Message-ID: <20090129032834.GA79291@duncan.reilly.home> References: <20090128155340.GA75143@lpthe.jussieu.fr> <200901291243.00378.doconnor@gsoft.com.au> <49811242.7030106@delphij.net> <200901291330.18007.doconnor@gsoft.com.au> <20090129030950.GA9605@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090129030950.GA9605@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.2.3i X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150204.49812272.005B,ss=1,fgs=0 Cc: freebsd-current@freebsd.org, d@delphij.net, Michel Talon Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 03:28:58 -0000 On Wed, Jan 28, 2009 at 07:09:50PM -0800, Steve Kargl wrote: > The FSF has not decided what to do about the runtime libraries. > These are currently gplv2+link time exception. In the future, > the libraries may be gplv3 + some new link time exception. The libraries in question are those for long long multiply and other low-level code generation short-cuts, aren't they? I understodd that crt0.o and libc.a were both BSD on FreeBSD. So, to the extent that we currently use the gcc/gpl+exception libraries, is it a reasonable proposition to supply versions of our own, or would they necessarily be a derivative work of GCC simply because only gcc requires those particular runtime libraries? Cheers, Andrew From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 03:53:12 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FB90106564A for ; Thu, 29 Jan 2009 03:53:12 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 873EC8FC0C for ; Thu, 29 Jan 2009 03:53:10 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.localnet (Inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n0T3r2F7028676 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Jan 2009 14:23:03 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Thu, 29 Jan 2009 14:22:51 +1030 User-Agent: KMail/1.10.3 (Linux/2.6.27-9-generic; KDE/4.1.3; i686; ; ) References: <20490.74948.qm@web63901.mail.re1.yahoo.com> <200901291219.17379.doconnor@gsoft.com.au> <191beebcb8e400a659afaa9d997462c0.squirrel@lamneth> In-Reply-To: <191beebcb8e400a659afaa9d997462c0.squirrel@lamneth> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1515337.8gjVaEIm4k"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200901291423.00658.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: Nenhum_de_Nos Subject: Re: SATA drive device moving on 8.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: Thu, 29 Jan 2009 03:53:12 -0000 --nextPart1515337.8gjVaEIm4k Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 29 January 2009 13:42:57 Nenhum_de_Nos wrote: > > I don't know how you can change it back, but you can use glabel and > > tunefs -L > > and then modify /etc/fstab to use /dev/ufs/foo. > > even / can use this ? Yep, it works with / - you need to load glabel in the loader of course. > just current has this feature ? I think it is OK in 7.x but I haven't tried running / with it. (It would be easy for you to test on a local machine) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1515337.8gjVaEIm4k Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQBJgSgV5ZPcIHs/zowRAu7kAJ9NUb0rZvrjNaRehRa0LU8mrt8i3gCgi6F/ AJZuAoVoIECWDu6eBDlqIkc= =ppuH -----END PGP SIGNATURE----- --nextPart1515337.8gjVaEIm4k-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 05:31:00 2009 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 C31AA1065673 for ; Thu, 29 Jan 2009 05:31:00 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forwards7.yandex.ru (forwards7.yandex.ru [77.88.61.48]) by mx1.freebsd.org (Postfix) with ESMTP id 76CCE8FC16 for ; Thu, 29 Jan 2009 05:31:00 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp16.yandex.ru (smtp16.yandex.ru [77.88.61.56]) by forwards7.yandex.ru (Yandex) with ESMTP id CED6915093C; Thu, 29 Jan 2009 08:20:26 +0300 (MSK) Received: from ns.kirov.so-cdu.ru ([77.72.136.145]:27076 "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 S12992634AbZA2FUY (ORCPT + 1 other); Thu, 29 Jan 2009 08:20:24 +0300 X-Yandex-Spam: 1 X-Yandex-Front: smtp16 X-Yandex-TimeMark: 1233206424 X-BornDate: 1137963600 X-Yandex-Karma: 0 X-Yandex-KarmaStatus: 0 X-MsgDayCount: 2 X-Comment: RFC 2476 MSA function at smtp16.yandex.ru logged sender identity as: bu7cher Message-ID: <49813CB1.8020405@yandex.ru> Date: Thu, 29 Jan 2009 08:20:49 +0300 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: barney_cordoba@yahoo.com References: <20490.74948.qm@web63901.mail.re1.yahoo.com> In-Reply-To: <20490.74948.qm@web63901.mail.re1.yahoo.com> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: SATA drive device moving on 8.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: Thu, 29 Jan 2009 05:31:01 -0000 Barney Cordoba wrote: > I booted 8.0-current on a machine that was running 7 and the SATA drive > came up as ad4 instead of ad8 (as it is detected in 7). This is the case > was loading GENERIC. > > This is going to present a serious problem doing field upgrades as its > expected that fstab will be the same. What is the reason for the change and > is there any way to make it compatible with device detection in 7? Probably your system now have (or lost) support for some of your ATA/SATA controller. -- WBR, Andrey V. Elsukov From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 06:48:03 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D6E41065679 for ; Thu, 29 Jan 2009 06:48:03 +0000 (UTC) (envelope-from daichi@ongs.co.jp) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.246.90]) by mx1.freebsd.org (Postfix) with ESMTP id 06CCC8FC12 for ; Thu, 29 Jan 2009 06:48:02 +0000 (UTC) (envelope-from daichi@ongs.co.jp) Received: from parancell.ongs.co.jp (dullmdaler.ongs.co.jp [202.216.246.94]) by natial.ongs.co.jp (Postfix) with ESMTPSA id 04CD1125422; Thu, 29 Jan 2009 15:48:01 +0900 (JST) Message-ID: <49815121.9080000@ongs.co.jp> Date: Thu, 29 Jan 2009 15:48:01 +0900 From: Daichi GOTO User-Agent: Thunderbird 2.0.0.19 (X11/20090124) MIME-Version: 1.0 To: Tim Kientzle References: <49796E09.7000805@ongs.co.jp> <497D4F2B.2080506@freebsd.org> In-Reply-To: <497D4F2B.2080506@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: sparse file issue?, dd(1) works well but tar(1) not on different partition X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 06:48:03 -0000 So sorry slow response. Flurry Seagate HDD issue has hit my PC. Ooops X-( Tim Kientzle wrote: > Daichi GOTO wrote: >> >> # cd /localapps/qemu/ >> # tar cpf - disk0image | tar xpf - -S -C /nfshome/user/ >> >> gets follow error message. >> >> # tar cpf - disk0image | tar xpf - -S -C /nfshome/user/ >> disk0image: Write request too large >> tar: Error exit delayed from previous errors. > > Please try the attached patch to > lib/libarchive/archive_write_disk.c, which should fix this. I have checked it. Sparse works well! Go commit :) > Cheers, > > Tim > -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 07:38:45 2009 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 ED2131065679; Thu, 29 Jan 2009 07:38: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 AEFFE8FC1E; Thu, 29 Jan 2009 07:38:45 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0T7ch02056654; Thu, 29 Jan 2009 02:38:43 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.14.3/8.14.3) with ESMTP id n0T7ch7B061491; Thu, 29 Jan 2009 02:38:43 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id EFD8C7302F; Thu, 29 Jan 2009 02:38:42 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090129073842.EFD8C7302F@freebsd-current.sentex.ca> Date: Thu, 29 Jan 2009 02:38:42 -0500 (EST) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on powerpc/powerpc 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: Thu, 29 Jan 2009 07:38:46 -0000 TB --- 2009-01-29 05:59:41 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-01-29 05:59:41 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2009-01-29 05:59:41 - cleaning the object tree TB --- 2009-01-29 06:00:08 - cvsupping the source tree TB --- 2009-01-29 06:00:08 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2009-01-29 06:00:16 - building world TB --- 2009-01-29 06:00:16 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-29 06:00:16 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-29 06:00:16 - TARGET=powerpc TB --- 2009-01-29 06:00:16 - TARGET_ARCH=powerpc TB --- 2009-01-29 06:00:16 - TZ=UTC TB --- 2009-01-29 06:00:16 - __MAKE_CONF=/dev/null TB --- 2009-01-29 06:00:16 - cd /src TB --- 2009-01-29 06:00:16 - /usr/bin/make -B buildworld >>> World build started on Thu Jan 29 06:00:18 UTC 2009 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Thu Jan 29 07:24:04 UTC 2009 TB --- 2009-01-29 07:24:04 - generating LINT kernel config TB --- 2009-01-29 07:24:04 - cd /src/sys/powerpc/conf TB --- 2009-01-29 07:24:04 - /usr/bin/make -B LINT TB --- 2009-01-29 07:24:04 - building LINT kernel TB --- 2009-01-29 07:24:04 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-29 07:24:04 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-29 07:24:04 - TARGET=powerpc TB --- 2009-01-29 07:24:04 - TARGET_ARCH=powerpc TB --- 2009-01-29 07:24:04 - TZ=UTC TB --- 2009-01-29 07:24:04 - __MAKE_CONF=/dev/null TB --- 2009-01-29 07:24:04 - cd /src TB --- 2009-01-29 07:24:04 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Jan 29 07:24:04 UTC 2009 >>> 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 [...] /src/sys/dev/adb/adb_mouse.c: In function 'ams_close': /src/sys/dev/adb/adb_mouse.c:357: error: invalid operands to binary & /src/sys/dev/adb/adb_mouse.c: In function 'ams_poll': /src/sys/dev/adb/adb_mouse.c:369: error: invalid operands to binary & /src/sys/dev/adb/adb_mouse.c: In function 'ams_read': /src/sys/dev/adb/adb_mouse.c:398: error: invalid operands to binary & /src/sys/dev/adb/adb_mouse.c: In function 'ams_ioctl': /src/sys/dev/adb/adb_mouse.c:488: error: invalid operands to binary & *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-29 07:38:42 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-29 07:38:42 - ERROR: failed to build lint kernel TB --- 2009-01-29 07:38:42 - 4787.34 user 406.83 system 5941.33 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 07:55:17 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CDF76106566B for ; Thu, 29 Jan 2009 07:55:17 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.freebsd.org (Postfix) with ESMTP id A074A8FC08 for ; Thu, 29 Jan 2009 07:55:17 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9] (may be forged)) by mxout2.cac.washington.edu (8.14.3+UW08.09/8.14.3+UW09.01) with ESMTP id n0T7ssFI002638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 28 Jan 2009 23:54:55 -0800 X-Auth-Received: from [192.168.10.3] (adsl-99-146-97-242.dsl.pltn13.sbcglobal.net [99.146.97.242]) (authenticated authid=youshi10) by smtp.washington.edu (8.14.3+UW08.09/8.14.3+UW09.01) with ESMTP id n0T7sss9025438 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 28 Jan 2009 23:54:54 -0800 Message-Id: From: Garrett Cooper To: Andrew Reilly In-Reply-To: <20090129032834.GA79291@duncan.reilly.home> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Wed, 28 Jan 2009 23:59:51 -0800 References: <20090128155340.GA75143@lpthe.jussieu.fr> <200901291243.00378.doconnor@gsoft.com.au> <49811242.7030106@delphij.net> <200901291330.18007.doconnor@gsoft.com.au> <20090129030950.GA9605@troutmask.apl.washington.edu> <20090129032834.GA79291@duncan.reilly.home> X-Mailer: Apple Mail (2.930.3) X-PMX-Version: 5.5.0.356843, Antispam-Engine: 2.6.1.350677, Antispam-Data: 2009.1.29.74045 X-Uwash-Spam: Gauge=IIIIIII, Probability=8%, Report='FORGED_FROM_GMAIL 0.1, BODY_SIZE_1000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_900_999 0, __BOUNCE_CHALLENGE_SUBJ 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FRAUD_419_WEBMAIL 0, __FRAUD_419_WEBMAIL_FROM 0, __FROM_GMAIL 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: freebsd-current@freebsd.org, d@delphij.net, Michel Talon , Steve Kargl Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 07:55:18 -0000 On Jan 28, 2009, at 7:28 PM, Andrew Reilly wrote: > On Wed, Jan 28, 2009 at 07:09:50PM -0800, Steve Kargl wrote: >> The FSF has not decided what to do about the runtime libraries. >> These are currently gplv2+link time exception. In the future, >> the libraries may be gplv3 + some new link time exception. > > The libraries in question are those for long long multiply and > other low-level code generation short-cuts, aren't they? I > understodd that crt0.o and libc.a were both BSD on FreeBSD. > > So, to the extent that we currently use the gcc/gpl+exception > libraries, is it a reasonable proposition to supply versions of > our own, or would they necessarily be a derivative work of GCC > simply because only gcc requires those particular runtime > libraries? > > Cheers, > > Andrew I believe we're still using libgcc.so though, which is a runtime library used at multiple levels IIRC, and GPLv3 along with the compiler no doubt. -Garrett From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 08:27:04 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B4071065675 for ; Thu, 29 Jan 2009 08:27:04 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 66C4F8FC18 for ; Thu, 29 Jan 2009 08:27:02 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: (qmail invoked by alias); 29 Jan 2009 08:27:01 -0000 Received: from p54A3E7E9.dip.t-dialin.net (EHLO tron.homeunix.org) [84.163.231.233] by mail.gmx.net (mp049) with SMTP; 29 Jan 2009 09:27:01 +0100 X-Authenticated: #1673122 X-Provags-ID: V01U2FsdGVkX1+i9RkK+FeiGV11gF+K5t1I7Pe7K6o2W+mY3UULmq FaIoQa0R1XL8CN Message-ID: <49816854.9060909@gmx.de> Date: Thu, 29 Jan 2009 09:27:00 +0100 From: Christoph Mallon User-Agent: Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Eitan Adler References: <20090128155340.GA75143@lpthe.jussieu.fr> <7508A5B5-C6D2-498A-AEA1-D84E85F1D743@mac.com> <200901291243.00378.doconnor@gsoft.com.au> <49811242.7030106@delphij.net> <498116AB.2060105@gmail.com> In-Reply-To: <498116AB.2060105@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.57 Cc: freebsd-current@freebsd.org, d@delphij.net, Michel Talon Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 08:27:05 -0000 Eitan Adler schrieb: > Xin LI wrote: >> Daniel O'Connor wrote: >>> On Thursday 29 January 2009 05:20:33 Chuck Swiger wrote: >>>> Evidently, the FSF is now claiming that all object code produced from >>>> GCC 4.2.2 and later is GPLv3-licensed, and only their exception >>>> permits you to distribute executables compiled using an "Eligible >>>> Compilation Process" under the terms of some other license. >>> The "eligible compilation process" is where you use GCC and GPL compatible >>> software. >>> I think for the FreeBSD project that is fine. >> I agree, this term seems to be targeted to companies behind closed >> source optimizers. Speaking for myself, I think FreeBSD would avoid >> GPLv3 code where possible to minimize the risk it would introduce to >> commercial users of our codebase, we want our code be used by as many >> people as possible to better exploit its value. > I don't think this is a "where possible" case. While version 4.3 may > not include improvements necessary for an operating system future > versions will almost surely have some. IMHO avoiding GCC because of its > license is pointless. Commercial users will already be avoiding gcc (if > it matters to them) because of the GPLv2. The FSF has made it clear > that the output of the compiler is (truly) free for anyone who may have > had any ounce of doubt. To quote from the FAQ: > Who does this change affect? > Nobody who is currently using GCC should be affected by this change. Let me repeat that: "Nobody who is currently using GCC *should* be affected by this change." Emphasize mine. > If we were replacing a BSD licensed compiler with a GPL licensed > compiler it would be a different story. >> Cheers, From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 08:28:55 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8399E1065705 for ; Thu, 29 Jan 2009 08:28:55 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id C40438FC22 for ; Thu, 29 Jan 2009 08:28:54 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: (qmail invoked by alias); 29 Jan 2009 08:28:53 -0000 Received: from p54A3E7E9.dip.t-dialin.net (EHLO tron.homeunix.org) [84.163.231.233] by mail.gmx.net (mp006) with SMTP; 29 Jan 2009 09:28:53 +0100 X-Authenticated: #1673122 X-Provags-ID: V01U2FsdGVkX1+kgDZ2KOekUD8QEiY9Hqa3t6lZfgSQlUndMghSRk iHdKmkyE3NNa7e Message-ID: <498168C2.4050803@gmx.de> Date: Thu, 29 Jan 2009 09:28:50 +0100 From: Christoph Mallon User-Agent: Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Andrew Reilly References: <20090128155340.GA75143@lpthe.jussieu.fr> <200901291243.00378.doconnor@gsoft.com.au> <49811242.7030106@delphij.net> <200901291330.18007.doconnor@gsoft.com.au> <20090129030950.GA9605@troutmask.apl.washington.edu> <20090129032834.GA79291@duncan.reilly.home> In-Reply-To: <20090129032834.GA79291@duncan.reilly.home> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.67 Cc: freebsd-current@freebsd.org, d@delphij.net, Michel Talon , Steve Kargl Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 08:28:56 -0000 Andrew Reilly schrieb: > On Wed, Jan 28, 2009 at 07:09:50PM -0800, Steve Kargl wrote: >> The FSF has not decided what to do about the runtime libraries. >> These are currently gplv2+link time exception. In the future, >> the libraries may be gplv3 + some new link time exception. > > The libraries in question are those for long long multiply and > other low-level code generation short-cuts, aren't they? I > understodd that crt0.o and libc.a were both BSD on FreeBSD. > > So, to the extent that we currently use the gcc/gpl+exception > libraries, is it a reasonable proposition to supply versions of > our own, or would they necessarily be a derivative work of GCC > simply because only gcc requires those particular runtime > libraries? You would just be implemeting an interface. This does not make the implementation a derivate work. From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 08:33:13 2009 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 373331065675 for ; Thu, 29 Jan 2009 08:33:13 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from emh05.mail.saunalahti.fi (emh05.mail.saunalahti.fi [62.142.5.111]) by mx1.freebsd.org (Postfix) with ESMTP id E61348FC22 for ; Thu, 29 Jan 2009 08:33:12 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from saunalahti-vams (vs3-11.mail.saunalahti.fi [62.142.5.95]) by emh05-2.mail.saunalahti.fi (Postfix) with SMTP id AB5E78C361; Thu, 29 Jan 2009 10:16:59 +0200 (EET) Received: from emh01.mail.saunalahti.fi ([62.142.5.107]) by vs3-11.mail.saunalahti.fi ([62.142.5.95]) with SMTP (gateway) id A0184EA5226; Thu, 29 Jan 2009 10:16:59 +0200 Received: from a91-153-125-115.elisa-laajakaista.fi (a91-153-125-115.elisa-laajakaista.fi [91.153.125.115]) by emh01.mail.saunalahti.fi (Postfix) with SMTP id 3599C4BB65; Thu, 29 Jan 2009 10:16:55 +0200 (EET) Date: Thu, 29 Jan 2009 10:16:55 +0200 From: Jaakko Heinonen To: Sean Bruno Message-ID: <20090129081654.GB854@a91-153-125-115.elisa-laajakaista.fi> References: <1233098540.2494.6.camel@localhost.localdomain> <49809B45.1000703@boland.org> <1233166048.3592.1.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1233166048.3592.1.camel@localhost.localdomain> User-Agent: Mutt/1.5.18 (2008-05-17) X-Antivirus: VAMS Cc: Michiel Boland , current@freebsd.org Subject: Re: NFS mounts dissapearing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 08:33:13 -0000 On 2009-01-28, Sean Bruno wrote: > > It appears to me that TCP connections to remote nfsd use a > > privileged source port initially, > > but if the connection is severed and reestablished later the source > > port is no longer < 1024. Client is -CURRENT, server is solaris with > > nfssrv:nfs_portmon=1. > > Here client is -CURRENT, server is linux with default NFS settings. Indeed it looks like the new RPC code (I didn't verify that the old works though) doesn't honour the resvport mount option on reconnects. To confirm that this is your problem try using the "insecure" export option on Linux server to allow connections from from all ports. -- Jaakko From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 07:37:32 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 231821065672; Thu, 29 Jan 2009 07:37:32 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id 0648A8FC0A; Thu, 29 Jan 2009 07:37:31 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 97A668C084; Thu, 29 Jan 2009 01:37:31 -0600 (CST) Date: Thu, 29 Jan 2009 01:37:31 -0600 To: freebsd-stable@FreeBSD.org, freebsd-current@FreeBSD.org, freebsd-net@FreeBSD.org Message-ID: <20090129073731.GB8695@soaustin.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) From: linimon@lonesome.com (Mark Linimon) X-Mailman-Approved-At: Thu, 29 Jan 2009 12:27:18 +0000 Cc: Subject: reminder: bugathon upcoming this weekend X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 07:37:32 -0000 Starting this Friday, we are going to hold a bugathon to work through some of the network-related PRs. More details, and a list of resources, are available at http://wiki.freebsd.org/Bugathons/January2009. I have come up with a page that details a subset of those PRs as a set of suggested PRs: http://people.freebsd.org/~linimon/annotated_prs_bugathon.html Please join us to work through some PRs. Thanks! mcl From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 12:28:24 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C6751065674 for ; Thu, 29 Jan 2009 12:28:24 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 66DBF8FC1A for ; Thu, 29 Jan 2009 12:28:23 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id n0TCHr48067956 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 29 Jan 2009 13:17:54 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by cicely5.cicely.de (8.14.2/8.14.2) with ESMTP id n0TCHpnn098483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Jan 2009 13:17:51 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id n0TCHpsO078059; Thu, 29 Jan 2009 13:17:51 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id n0TCHofi078058; Thu, 29 Jan 2009 13:17:50 +0100 (CET) (envelope-from ticso) Date: Thu, 29 Jan 2009 13:17:50 +0100 From: Bernd Walter To: Channa Message-ID: <20090129121750.GO74490@cicely7.cicely.de> References: <515c64960901280339m17fa9309v2e1bc3f55454ab@mail.gmail.com> <49804597.6040303@gmx.de> <515c64960901280401w1e1d08bfx29adc124bc749c4a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <515c64960901280401w1e1d08bfx29adc124bc749c4a@mail.gmail.com> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=0.053, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Cc: Christoph Mallon , freebsd-current@freebsd.org Subject: Re: Jemalloc SEGV for 1MB chunk 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: Thu, 29 Jan 2009 12:28:24 -0000 On Wed, Jan 28, 2009 at 05:31:43PM +0530, Channa wrote: > Hi, > Thanks for your reply. > You mean to say i should modify the test as below: > > #include > #include > #include > > > int main() > { > int i; > char *buf; > size_t size = 1048576 ; > > buf = malloc(size); > for (i = 0; i <= 1048575; i++) > buf[i] = 'a'; > buf[size]='\0'; > printf("The length of buff is : %d\n",strlen(buf)); > free(buf); > return 0; > } > > I NULL terminated the string > buf[size] = '\0' <== The last character is NULL > > But still i get a SEGV at strlen. > > Could you please tell me if my changes above are correct? buf[size - 1]='\0'; It should panic with this line instead of strlen, because you tried writing one byte behind allocation. Originally your code wasn't terminating the string at all so strlen was the first one to access behind allocation. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 13:35:39 2009 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 930201065672 for ; Thu, 29 Jan 2009 13:35:39 +0000 (UTC) (envelope-from paul@fletchermoorland.co.uk) Received: from hydra.fletchermoorland.co.uk (93-152-14-233.daisydsl.managedbroadband.co.uk [93.152.14.233]) by mx1.freebsd.org (Postfix) with ESMTP id D1E0F8FC19 for ; Thu, 29 Jan 2009 13:35:38 +0000 (UTC) (envelope-from paul@fletchermoorland.co.uk) Received: from demophon.fletchermoorland.co.uk (demophon.fletchermoorland.co.uk [192.168.0.188]) by hydra.fletchermoorland.co.uk (8.14.2/8.14.2) with ESMTP id n0TD2w7J002665; Thu, 29 Jan 2009 13:02:58 GMT (envelope-from paul@fletchermoorland.co.uk) From: Paul Wootton Organization: Fletcher Moorland To: current@freebsd.org Date: Thu, 29 Jan 2009 13:02:05 +0000 User-Agent: KMail/1.10.1 (FreeBSD/8.0-CURRENT; KDE/4.1.1; amd64; ; ) References: <88F83F222F2347A088A7A7AE8ABF2558@PegaPegII> In-Reply-To: <88F83F222F2347A088A7A7AE8ABF2558@PegaPegII> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200901291302.05756.paul@fletchermoorland.co.uk> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: Pegasus Mc Cleaft Subject: Re: KDE4/DBUS weirdness 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, 29 Jan 2009 13:35:40 -0000 >On Monday 26 January 2009 14:29:21 Pegasus Mc Cleaft wrote: >> Hello Current, >> > >> First I appologize for not having much debug information, as I havent >> been able to pinpoint an exact cause yet, but I noticed something odd with >> -Current 25012009. After updating all my ports while running on a >> 23012009-Current and rebooting, everything seemed to work fine; however, >> after updating usr/src from about 11pm on 25012009, KDE started to act >> really strange. >> >> After poking around with various things, I discovered that the dbus >> daemon stopped responding. This manifisted its self by clicking on icons >> and having the window manager lock up for about 1 minute. After which, a >> message came back that the dbus daemon could not be contacted. I tried >> dbus-monitor, but got exactly the same message. I tried both USB1 and USB2 >> stacks, just to make sure, but could never get things to copperate. I did >> find, right after logging in through KDM, I could get a single application >> to launch (So DBUS had to been ok at this point) but after about 5 seconds, >> DBUS would stop responding) >> >> I reverted my kernel to the version before the upgrade (kernel.old) and >> everything started to work fine again (I am running on the more recent >> world and the old kernel). >> >> I am not really sure how to find the exact failure here, but I can >> duplicate the fault by loading the 25th's kernel. >> >> Machine is a Core2-quad running on AMD64, 8 Gig, USB1 or USB2 stack. >> >> Does anyone have any insight to what this might be? (Or how I might be >> able to diagnose further) >> >> ~Peg >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >On Monday 26 January 2009 15:09:45 Alberto Villa wrote: > On Mon, Jan 26, 2009 at 2:29 PM, Pegasus Mc Cleaft wrote: > > Does anyone have any insight to what this might be? (Or how I might be > > able to diagnose further) > > that's not a new problem, but your information might help > try mailing at kde-freebsd@freebsd.org Hi All, I have just csup-ed my src tree from 13/01 to 28/01 and am now seeing the same problem as Peg. If this is as Alberto said "not a new problem" and indeed a KDE issue, then why have I not seen this before, and it has only just happened after a new kernel and world. I managed to launch xterm and then konqueror from the shell. Knoqueror eventually loads after about 2 minutes and gives a title of "Error: Cannot initiate the http Protocol" and the page displays "The requested operation could not be completed Cannot Initiate the http Protocol Technical Reason: Unable to Launch Process Details of the Request: URL: http://********************* Protocol: http Date and Time: Thursday 29 January 2009 12:26 Additional Information: Cannot talk to klauncher: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Description: The program on your computer which provides access to the http protocol could not be started. This is usually due to technical reasons." However, I can run dbus-monitor and there are messages flowing through If I revert back to the old kernel but still use the new world the problem seems to go away Have anyone else seen this issue? Cheer Paul From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 13:57:17 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DAA9106566C for ; Thu, 29 Jan 2009 13:57:17 +0000 (UTC) (envelope-from cdk1@bsd.cl) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.225]) by mx1.freebsd.org (Postfix) with ESMTP id 502FF8FC24 for ; Thu, 29 Jan 2009 13:57:17 +0000 (UTC) (envelope-from cdk1@bsd.cl) Received: by rv-out-0506.google.com with SMTP id b25so7627612rvf.43 for ; Thu, 29 Jan 2009 05:57:17 -0800 (PST) MIME-Version: 1.0 Received: by 10.114.190.18 with SMTP id n18mr55281waf.101.1233237435875; Thu, 29 Jan 2009 05:57:15 -0800 (PST) Date: Thu, 29 Jan 2009 10:57:15 -0300 Message-ID: From: Carlos Corona To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Panic with NTFS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 13:57:17 -0000 HI * After updating my FreeBSD 8 sources, create and install the world, to mount an NTFS partition I was induced the following error, I should note that before this update, sat perfectly: System: Reina-Tonia kern # uname -a FreeBSD Reina-Tonia 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Thu Jan 29 20:36:35 CLST 2009 CdK1@Reina-Tonia:/usr/obj/usr/src/sys/Segvfault i386 Reina-Tonia kern # Panic: panic:__lockmgr_args: Invalid requested operation @ /usr/src/sys/kern/vfs_default.c:331 cpuid = 0 KDB: enter: panic [thread pi 2313 tid 100087) Stopped at kdb_enter+0x3a:mavl $0,kdb_why db> thanx ;) -- Carlos Corona BSD Chile http://www.bsd.cl From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 13:57:37 2009 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 9EAE31065714 for ; Thu, 29 Jan 2009 13:57:37 +0000 (UTC) (envelope-from paul@fletchermoorland.co.uk) Received: from hydra.fletchermoorland.co.uk (93-152-14-233.daisydsl.managedbroadband.co.uk [93.152.14.233]) by mx1.freebsd.org (Postfix) with ESMTP id 1ABB58FC27 for ; Thu, 29 Jan 2009 13:57:36 +0000 (UTC) (envelope-from paul@fletchermoorland.co.uk) Received: from demophon.fletchermoorland.co.uk (demophon.fletchermoorland.co.uk [192.168.0.188]) by hydra.fletchermoorland.co.uk (8.14.2/8.14.2) with ESMTP id n0TDv7oJ003696; Thu, 29 Jan 2009 13:57:07 GMT (envelope-from paul@fletchermoorland.co.uk) From: Paul Wootton Organization: Fletcher Moorland To: Andrzej Tobola Date: Thu, 29 Jan 2009 13:56:06 +0000 User-Agent: KMail/1.10.1 (FreeBSD/8.0-CURRENT; KDE/4.1.1; amd64; ; ) References: <88F83F222F2347A088A7A7AE8ABF2558@PegaPegII> <200901291302.05756.paul@fletchermoorland.co.uk> <20090129135230.GB83549@amp2.iem.pw.edu.pl> In-Reply-To: <20090129135230.GB83549@amp2.iem.pw.edu.pl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901291356.06836.paul@fletchermoorland.co.uk> Cc: Pegasus Mc Cleaft , current@freebsd.org Subject: Re: KDE4/DBUS weirdness 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, 29 Jan 2009 13:57:37 -0000 On Thursday 29 January 2009 13:52:30 you wrote: > On Thu, Jan 29, 2009 at 01:02:05PM +0000, Paul Wootton wrote: > > ................... > > The program on your computer which provides access to the http protocol > > could not be started. This is usually due to technical reasons." > > > > However, I can run dbus-monitor and there are messages flowing through > > > > If I revert back to the old kernel but still use the new world the > > problem seems to go away > > > > Have anyone else seen this issue? > > Yes. In my case it is a problem with select() introduced on 25. > The last working kernel is from 24. > > -at This would make sense and also falls in to Pegs window between the 23rd and 25th Paul From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 14:01:53 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38EE21065695 for ; Thu, 29 Jan 2009 14:01:53 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id BBDD98FC1B for ; Thu, 29 Jan 2009 14:01:52 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: by ewy14 with SMTP id 14so5494438ewy.19 for ; Thu, 29 Jan 2009 06:01:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=XkkTjA38eP9r79bMQ+fBSljQ5jMfXKgf3lgOXJOj4zs=; b=My0o6EOnJ1a43DEIRd0S7dOUO8K/fEwPNePiL459zhm8NsvAmA1dF8sN1LTEumCxik i1w9gAlR3Za2huFzbskk0jrzhZIT2a0JVvwqR8fwInj4kbzeVgoZtKRkSBvVfXxnjjzb oK2Xh6zUHOaS9gf1KjBih6KyMs/mJc/YxGwqA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=n3+caHCLo/N5ZcizYnO4pO77qS0QgRDmzXYW9a7uDeP9cGxtMT2AZWPV94JhjJAojP wiZ8JePfys26mNwmgN4jvTj0Jdq8/ESbO0T/viMAoJVSPqgT1+G27vQa3T/SFSeGzDI9 fIFp+9jYgEzl4A3tV9N/n5iY2/nnU7aXiaGbE= MIME-Version: 1.0 Sender: asmrookie@gmail.com Received: by 10.86.92.9 with SMTP id p9mr103580fgb.15.1233237711000; Thu, 29 Jan 2009 06:01:51 -0800 (PST) In-Reply-To: References: Date: Thu, 29 Jan 2009 15:01:50 +0100 X-Google-Sender-Auth: bd17dceb2f01f5cf Message-ID: <3bbf2fe10901290601p664b6fc0qedb094f4fae30943@mail.gmail.com> From: Attilio Rao To: Carlos Corona Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Panic with NTFS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 14:01:54 -0000 2009/1/29 Carlos Corona : > HI * > > After updating my FreeBSD 8 sources, create and install the world, to mount > an NTFS partition I was induced the following error, I should note that > before this update, sat perfectly: > > System: > > Reina-Tonia kern # uname -a > FreeBSD Reina-Tonia 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Thu Jan 29 20:36:35 > CLST 2009 CdK1@Reina-Tonia:/usr/obj/usr/src/sys/Segvfault i386 > Reina-Tonia kern # > > > Panic: > > > panic:__lockmgr_args: Invalid requested operation @ > /usr/src/sys/kern/vfs_default.c:331 > cpuid = 0 > KDB: enter: panic > [thread pi 2313 tid 100087) > Stopped at kdb_enter+0x3a:mavl $0,kdb_why > db> Could you please type 'bt' when the 'db>' prompt is shown and report what happens? (in particular with the arguments passed to the __lockmgr_args() and prior 2-3 functions). Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 14:48:57 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D621106566B for ; Thu, 29 Jan 2009 14:48:57 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 80FAF8FC08 for ; Thu, 29 Jan 2009 14:48:56 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id n0TEmmR3061259; Thu, 29 Jan 2009 15:48:49 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id n0TEmmiO061258; Thu, 29 Jan 2009 15:48:48 +0100 (CET) (envelope-from olli) Date: Thu, 29 Jan 2009 15:48:48 +0100 (CET) Message-Id: <200901291448.n0TEmmiO061258@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG, ptice@aldridge.com In-Reply-To: X-Newsgroups: list.freebsd-current User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Thu, 29 Jan 2009 15:48:49 +0100 (CET) Cc: Subject: Re: Help me select hardware....Some real world data that might help X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@FreeBSD.ORG, ptice@aldridge.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2009 14:48:57 -0000 Paul Tice wrote: > I just bumped up the kmem, arc.max, enabled zil and reenabled > mdcomp. Prefetch is disabled. Less than 1 minute into a backup > run of only 4 machines, I've got a fresh ZFS wedgie. How exactly did you bump up kmem? As far as I know, it is not necessary anymore on 8-current/amd64, because the defaults are already much larger. In fact it might be possible that your tuning made things worse. > As I understand it, the ZIL is not as much of an integrity boost as > a speed boost, especially since we already have checksum-per-block. The checksum feature works purely on a block level, while the intent log (ZIL) records certain changes to meta data on the file system, similar to a journal, which can be used for recovery after a crash (power outage, hardware failure, kernel panic, human error). Both features are completely orthogonal, one cannot replace the other. Therefore I recommend to keep the ZIL enabled. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "In My Egoistical Opinion, most people's C programs should be indented six feet downward and covered with dirt." -- Blair P. Houghton From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 15:20:13 2009 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 2BB2A1065679 for ; Thu, 29 Jan 2009 15:20:13 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from emh04.mail.saunalahti.fi (emh04.mail.saunalahti.fi [62.142.5.110]) by mx1.freebsd.org (Postfix) with ESMTP id D8E5B8FC17 for ; Thu, 29 Jan 2009 15:20:12 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from saunalahti-vams (vs3-10.mail.saunalahti.fi [62.142.5.94]) by emh04-2.mail.saunalahti.fi (Postfix) with SMTP id DE53813BB33; Thu, 29 Jan 2009 17:20:11 +0200 (EET) Received: from emh03.mail.saunalahti.fi ([62.142.5.109]) by vs3-10.mail.saunalahti.fi ([62.142.5.94]) with SMTP (gateway) id A066ADDFBAB; Thu, 29 Jan 2009 17:20:11 +0200 Received: from a91-153-125-115.elisa-laajakaista.fi (a91-153-125-115.elisa-laajakaista.fi [91.153.125.115]) by emh03.mail.saunalahti.fi (Postfix) with SMTP id 99BC9158A66; Thu, 29 Jan 2009 17:20:07 +0200 (EET) Date: Thu, 29 Jan 2009 17:20:07 +0200 From: Jaakko Heinonen To: Sean Bruno Message-ID: <20090129152006.GA3790@a91-153-125-115.elisa-laajakaista.fi> References: <1233098540.2494.6.camel@localhost.localdomain> <49809B45.1000703@boland.org> <1233166048.3592.1.camel@localhost.localdomain> <20090129081654.GB854@a91-153-125-115.elisa-laajakaista.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090129081654.GB854@a91-153-125-115.elisa-laajakaista.fi> User-Agent: Mutt/1.5.18 (2008-05-17) X-Antivirus: VAMS Cc: Michiel Boland , current@freebsd.org Subject: Re: NFS mounts dissapearing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 15:20:14 -0000 On 2009-01-29, Jaakko Heinonen wrote: > > > It appears to me that TCP connections to remote nfsd use a > > > privileged source port initially, > > > but if the connection is severed and reestablished later the source > > > port is no longer < 1024. Client is -CURRENT, server is solaris with > > > nfssrv:nfs_portmon=1. > > Indeed it looks like the new RPC code (I didn't verify that the old > works though) doesn't honour the resvport mount option on reconnects. I think I found the bug. The new RPC code doesn't properly elevate privileges before bindresvport() call in clnt_reconnect_connect(). For initial connection bindresvport() succeeds because the process has elevated privileges at that time. Does this patch fix the problem for you? %%% Index: sys/rpc/clnt_rc.c =================================================================== --- sys/rpc/clnt_rc.c (revision 187877) +++ sys/rpc/clnt_rc.c (working copy) @@ -181,11 +181,12 @@ again: rpc_createerr.cf_error.re_errno = 0; goto out; } - if (rc->rc_privport) - bindresvport(so, NULL); oldcred = td->td_ucred; td->td_ucred = rc->rc_ucred; + if (rc->rc_privport) + bindresvport(so, NULL); + if (rc->rc_nconf->nc_semantics == NC_TPI_CLTS) rc->rc_client = clnt_dg_create(so, (struct sockaddr *) &rc->rc_addr, rc->rc_prog, rc->rc_vers, %%% -- Jaakko From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 16:25:04 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FEFF106568A for ; Thu, 29 Jan 2009 16:25:04 +0000 (UTC) (envelope-from mister.olli@googlemail.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 8B46C8FC1A for ; Thu, 29 Jan 2009 16:25:03 +0000 (UTC) (envelope-from mister.olli@googlemail.com) Received: by nf-out-0910.google.com with SMTP id h3so1348767nfh.33 for ; Thu, 29 Jan 2009 08:25:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:subject:from:reply-to:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=l3KVxeNzPaxahXd/xvl7L6V03z81/krtR4YUyxfqoWA=; b=D7wPQo0RnzPGUtRBo/uy+A9g8bRkbvXtogBuD+QbOo1gfNpUU2kmx6sUwZHuCGWCXL 2ylaCennpjCWgsMLS0HzPatMANllHeYyVZIVQEA1IvsDWPXCpklGpjhq+dCZ1h4d63Gk OAPYqyvkZA5JNnShHupz2VqTuCe4ABoxVE4nk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=subject:from:reply-to:to:cc:in-reply-to:references:content-type :date:message-id:mime-version:x-mailer:content-transfer-encoding; b=Z8IVKrj4v0F2Aba7f9Q0gJ3NPxeL2PXR8/IPg4YBwFGV5XzdCzuyLIZVgB9lguZxYP ve+Dow4mHqPxoXZBEW5c3/Odo2Iweu4BMWNEyUSjZV61PpwvhVQsomASzcXryNQ+zGGl +sJ41sG1y2OafP6bm0nu7BpJvfvd5xpGTYnwM= Received: by 10.103.2.14 with SMTP id e14mr119688mui.48.1233246302446; Thu, 29 Jan 2009 08:25:02 -0800 (PST) Received: from ?10.30.1.130? (vpn-or.studi-planet.com [78.47.172.52]) by mx.google.com with ESMTPS id y37sm1298429mug.36.2009.01.29.08.25.01 (version=SSLv3 cipher=RC4-MD5); Thu, 29 Jan 2009 08:25:01 -0800 (PST) From: Mister Olli To: Kip Macy In-Reply-To: <3c1674c90901281148i3949ee69r289db344a23b4326@mail.gmail.com> References: <1233105002.26641.2.camel@phoenix.blechhirn.net> <3c1674c90901281148i3949ee69r289db344a23b4326@mail.gmail.com> Content-Type: text/plain Date: Thu, 29 Jan 2009 17:24:28 +0100 Message-Id: <1233246268.27150.15.camel@phoenix.blechhirn.net> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Page fault in CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mister.olli@googlemail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2009 16:25:04 -0000 Hi... If there's anything a can help drop me a message. -- Mr. Olli Am Mittwoch, den 28.01.2009, 11:48 -0800 schrieb Kip Macy: > Will try to fix soon. > > Thanks, > Kip > > On Tue, Jan 27, 2009 at 5:10 PM, Mister Olli wrote: > > Hi, > > > > > > The following pagefault just happend on my PV CURRENT domU under Xen 3.3 > > > > ================================================================== > > template_8-CURRENT# pwd > > /usr > > Kernel page fault with the following non-sleepable locks > > held:org/base/head src/ > > exclusive sleep mutex pmap (pmap) r = 0 (0xc1706ee8) locked > > @ /usr/src/sys/i386/xen/pmap.c:3711 > > exclusive sleep mutex vm object (standard object) r = 0 (0xc19c98b8) > > locked @ /usr/src/sys/vm/vm_pageout.c:771 > > exclusive sleep mutex vm page queue mutex (vm page queue mutex) r = 0 > > (0xc052ae84) locked @ /usr/src/sys/vm/vm_pageout.c:447 > > KDB: stack backtrace: > > X_db_sym_numargs(c0342b8f,cbe849ac,c010c5f5,c0361da2,1bf,...) at > > X_db_sym_numargs+0x146 > > kdb_backtrace(c0361da2,1bf,ffffffff,c04f2c2c,cbe849e4,...) at > > kdb_backtrace+0x29 > > witness_display_spinlock(c0344dec,cbe849f8,4,1,0,...) at > > witness_display_spinlock+0x75 > > witness_warn(5,0,c036c048,c17a7d80,c,...) at witness_warn+0x1fd > > trap(cbe84a80) at trap+0x10e > > alltraps(c0bb2d48,4,c0361da2,1a8,c0361da2,...) at alltraps+0x1b > > vm_pageout_flush(cbe84ba4,7,0,0,ec1,...) at vm_pageout_flush+0xe5 > > vm_pageout_flush(c0bb3c78,0,c0361da2,303,32,...) at vm_pageout_flush > > +0x621 > > vm_pageout_flush(0,cbe84d38,c033ba96,32d,c1701a90,...) at > > vm_pageout_flush+0x13ce > > fork_exit(c02d59b0,0,cbe84d38) at fork_exit+0xb8 > > fork_trampoline() at fork_trampoline+0x8 > > --- trap 0, eip = 0, esp = 0xcbe84d70, ebp = 0 --- > > > > > > Fatal trap 12: page fault while in kernel mode > > cpuid = 0; apic id = 00 > > fault virtual address = 0xc0863fc8 > > fault code = supervisor write, protection violation > > instruction pointer = 0x21:0xc03113df > > stack pointer = 0x29:0xcbe84ac0 > > frame pointer = 0x29:0xcbe84ae8 > > code segment = base 0x0, limit 0xf67ff, type 0x1b > > = DPL 1, pres 1, def32 1, gran 1 > > processor eflags = interrupt enabled, resume, IOPL = 0 > > current process = 6 (pagedaemon) > > [thread pid 6 tid 100024 ] > > Stopped at pmap_remove_write+0xbf: lock cmpxchgl %edi,0(%ecx) > > db> > > =============================================================== > > > > Since I was unable to enter anything at the debugger command line I'm > > unable to provide a backtrace. sorry. > > > > -- > > Olli > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 17:03:19 2009 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 4FAEB10656C5 for ; Thu, 29 Jan 2009 17:03:19 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: from web63903.mail.re1.yahoo.com (web63903.mail.re1.yahoo.com [69.147.97.118]) by mx1.freebsd.org (Postfix) with SMTP id D750B8FC1C for ; Thu, 29 Jan 2009 17:03:18 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: (qmail 44732 invoked by uid 60001); 29 Jan 2009 17:03:18 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Message-ID; b=GJ112Nxn4RqN2PKQ0a7LajukZvuLJuO5iesnTIjrWnb6GHIg0c7qfZ2AzLREAsLrMN0iq8WFZsYdpLqWFvZH+pIL4voEvaRCpVFJeYQcR/E73elykE1cbsxoynowgQTSs2NZaHqcmR9TfHOsllfC0JoWE/MgcsbGoYV0R3YrGP0=; X-YMail-OSG: XuP5b.EVM1k8TSb5n8P5Qc26UnRsrDVM0CLnxXBRxYnKD4Co3nC4.zZZ5cyFURHjps.bBvnIdZQQszlCvqA2dQpCgQC5MTr6Gl9IkpAQY9I6zNtMb8ZAfZ7CrGapGbiwRrVBKHWVkH6FgPReo7Psi086s.p89LNveyF73xai_m42__rqrv3r.YIC4_A8 Received: from [98.242.222.229] by web63903.mail.re1.yahoo.com via HTTP; Thu, 29 Jan 2009 09:03:18 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Thu, 29 Jan 2009 09:03:18 -0800 (PST) From: Barney Cordoba To: "Andrey V. Elsukov" In-Reply-To: <49813CB1.8020405@yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <234885.44369.qm@web63903.mail.re1.yahoo.com> Cc: current@freebsd.org Subject: Re: SATA drive device moving on 8.0 current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: barney_cordoba@yahoo.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2009 17:03:20 -0000 --- On Thu, 1/29/09, Andrey V. Elsukov wrote: > From: Andrey V. Elsukov > Subject: Re: SATA drive device moving on 8.0 current > To: barney_cordoba@yahoo.com > Cc: current@freebsd.org > Date: Thursday, January 29, 2009, 12:20 AM > Barney Cordoba wrote: > > I booted 8.0-current on a machine that was running 7 > and the SATA drive > > came up as ad4 instead of ad8 (as it is detected in > 7). This is the case > > was loading GENERIC. > > > > This is going to present a serious problem doing field > upgrades as its expected that fstab will be the same. What > is the reason for the change and > > is there any way to make it compatible with device > detection in 7? > > Probably your system now have (or lost) support for some of > your ATA/SATA controller. Theres only 1 controller with 4 ports, so it was probably something that was fixed. We were never quite sure why it started at different indexes on different machines with similar architecture. Barney From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 17:36:45 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C35FE106566C for ; Thu, 29 Jan 2009 17:36:45 +0000 (UTC) (envelope-from michiel@boland.org) Received: from smtp-vbr12.xs4all.nl (smtp-vbr12.xs4all.nl [194.109.24.32]) by mx1.freebsd.org (Postfix) with ESMTP id 46A668FC0C for ; Thu, 29 Jan 2009 17:36:45 +0000 (UTC) (envelope-from michiel@boland.org) Received: from aja.boland.org (91-43-215.ftth.xms.internl.net [82.215.43.91]) (authenticated bits=0) by smtp-vbr12.xs4all.nl (8.13.8/8.13.8) with ESMTP id n0THaP7X069420 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Jan 2009 18:36:25 +0100 (CET) (envelope-from michiel@boland.org) Message-ID: <4981E919.5060405@boland.org> Date: Thu, 29 Jan 2009 18:36:25 +0100 From: Michiel Boland User-Agent: Thunderbird 2.0.0.19 (X11/20090125) MIME-Version: 1.0 To: Ed Schouten References: <4980C766.50207@boland.org> <20090128211416.GV17198@hoeg.nl> <20090128211631.GW17198@hoeg.nl> In-Reply-To: <20090128211631.GW17198@hoeg.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner Cc: FreeBSD Current Subject: Re: console oddities X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2009 17:36:46 -0000 Ed Schouten wrote: > * Ed Schouten wrote: >> Can you try the attached patch? Hi. Sorry about the delay. It does not appear to have any effect. I'll try something myself later this evening. Cheers Michiel From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 18:14:33 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D969106564A for ; Thu, 29 Jan 2009 18:14:33 +0000 (UTC) (envelope-from cryx-freebsd@h3q.com) Received: from mail.h3q.com (mail.h3q.com [213.73.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id BD7118FC1C for ; Thu, 29 Jan 2009 18:14:32 +0000 (UTC) (envelope-from cryx-freebsd@h3q.com) Received: (qmail 60834 invoked from network); 29 Jan 2009 17:47:50 -0000 Received: from unknown (HELO goa.local) (smtpsend@85.179.6.101) by mail.h3q.com with AES256-SHA encrypted SMTP; 29 Jan 2009 17:47:50 -0000 Message-ID: <4981EBC6.1000907@h3q.com> Date: Thu, 29 Jan 2009 18:47:50 +0100 From: Philipp Wuensche User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Solaris live upgrade like FreeBSD ZFS-rootfs 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: Thu, 29 Jan 2009 18:14:33 -0000 Hi, I'm playing a lot with ZFS root filesystems for FreeBSD and using zfsboot with GPT. So far it works perfecly for me on three not-so production servers and I would like to thank everybody that helped make this work! With ZFS suddenly some neat stuff is easly possible with FreeBSD, like the Solaris Live Upgrade feature. The idea behinde Live Upgrade is that you have more than one bootable-environment to boot from making it very painless to upgrade to newer FreeBSD versions without loosing the possibility to boot your known-good boot-environemt. So you can't end up with a broken userland or kernel and you can even go back to your old userland and kernel if the new ones do not work for you. Particularly with tracking CURRENT this becomes very handy! I wrote a shell script to create, activate and delete boot-environments in FreeBSD. Its far from feature complete and some bits are still missing but creating and activating boot-environments should be more or less feature-complete. In case anyone is interested or maybe wants to base a FreeBSD userland-tool on it, take a look at http://outpost.h3q.com/patches/manageBE/ Bug reports and suggestions are welcome! Biggest part that is missing in the ZFSboot stuff right now is being able to choose from the available boot-environments in the loader. If that would work, updating a FreeBSD box would be down to one reboot without any risk. greetings, cryx From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 19:22:43 2009 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 4930F1065673 for ; Thu, 29 Jan 2009 19:22:43 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: from mail.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb::3]) by mx1.freebsd.org (Postfix) with ESMTP id C6BCF8FC19 for ; Thu, 29 Jan 2009 19:22:42 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: by mail.0x20.net (Postfix, from userid 1002) id 78E1233C0D; Thu, 29 Jan 2009 20:22:41 +0100 (CET) Date: Thu, 29 Jan 2009 20:22:41 +0100 From: Lars Engels To: current@FreeBSD.org Message-ID: <20090129192241.GZ60948@e.0x20.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="22hJjvOmZW2O/jbw" Content-Disposition: inline X-Editor: VIM - Vi IMproved 7.1 X-Operation-System: FreeBSD 5.5-RELEASE-p19 User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: sam@FreBSD.org Subject: ath cannot find my wireless network any more X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Lars Engels List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2009 19:22:44 -0000 --22hJjvOmZW2O/jbw Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Hi all, hi Sam, I just build world && kernel from todays sources. Now my Atheros 5212 pccard cannot find my wireless network any more, but still sees other networks: lars@pts/3 # ifconfig wlan0 up scan SSID BSSID CHAN RATE S:N INT CAPS Arcor-C6DE58 00:1a:2a:c6:de:56 9 54M -95:-96 100 EPS RSN WPA WME WLAN-AFCB47 00:1d:19:af:cb:e0 1 54M -96:-96 100 EPS WPS RSN WPA WME 0x0000 00:03:c9:54:18:bb 8 54M -94:-96 100 EP WPA In contrast to this, the internal wpi chip still finds and connects to the network: lars@pts/3 # ifconfig wlan1 scan SSID BSSID CHAN RATE S:N INT CAPS dd-wrt 00:18:39:c7:6a:dd 6 54M 22:0 100 EP RSN WME I also don't know why wpi only finds my own network. Some additional information: lars@pts/3 # dmesg | egrep 'ath0|wpi0' ath0: mem 0x88000000-0x8800ffff irq 20 at device 0.0 on cardbus0 ath0: [ITHREAD] ath0: WARNING: using obsoleted if_watchdog interface ath0: mac 5.9 phy 4.3 radio 3.6 wpi0: mem 0xd4000000-0xd4000fff irq 16 at device 0.0 on pci2 wpi0: [ITHREAD] wpi0: need multicast update callback wpi0: need multicast update callback wpi0: need multicast update callback # ifconfig wpi0: flags=8843 metric 0 mtu 2290 ether 00:13:02:3f:0d:e4 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated [...] wlan1: flags=8843 metric 0 mtu 1500 ether 00:13:02:3f:0d:e4 inet 192.168.10.135 netmask 0xffffff00 broadcast 192.168.10.255 media: IEEE 802.11 Wireless Ethernet OFDM/18Mbps mode 11g status: associated ssid dd-wrt channel 6 (2437 Mhz 11g) bssid 00:18:39:c7:6a:dd country US authmode WPA2/802.11i privacy ON deftxkey UNDEF TKIP 2:128-bit txpower 0 bmiss 7 scanvalid 60 protmode CTS roaming MANUAL ath0: flags=8843 metric 0 mtu 2290 ether 00:0f:b5:9a:47:47 media: IEEE 802.11 Wireless Ethernet autoselect mode 11a status: associated wlan0: flags=8843 metric 0 mtu 1500 ether 00:0f:b5:9a:47:47 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect ) status: no carrier ssid "" channel 160 (5800 Mhz 11a Turbo) country US ecm authmode WPA1+WPA2/802.11i privacy ON deftxkey UNDEF txpower 17.5 bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 12 wme burst ff dturbo roaming MANUAL bintval 0 lars@pts/3 # grep wlan /etc/rc.conf wlans_ath0=wlan0 ifconfig_wlan0="WPA DHCP" wlans_wpi0=wlan1 ifconfig_wlan1="WPA DHCP" # cat /etc/wpa_supplicant.conf ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel ap_scan=1 network={ ssid="dd-wrt" psk="secret" priority=9 } lars@pts/3 # uname -a FreeBSD maggie.bsd-geek.de 8.0-CURRENT FreeBSD 8.0-CURRENT #2: Thu Jan 29 18:25:30 CET 2009 lars@maggie.bsd-geek.de:/usr/obj/usr/src/sys/USB2 i386 --22hJjvOmZW2O/jbw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkmCAgEACgkQKc512sD3afhMUwCdEmxzTv3WQbvw385Lu48Je7jD LtgAoMzEwgzIqGd0txPSYXv74LGKMIZG =rNVs -----END PGP SIGNATURE----- --22hJjvOmZW2O/jbw-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 19:28:35 2009 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 DA53C1065670 for ; Thu, 29 Jan 2009 19:28:35 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from pele.citylink.co.nz (pele.citylink.co.nz [202.8.44.226]) by mx1.freebsd.org (Postfix) with ESMTP id 9AB688FC08 for ; Thu, 29 Jan 2009 19:28:35 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by pele.citylink.co.nz (Postfix) with ESMTP id 0278BFEFA; Fri, 30 Jan 2009 08:28:35 +1300 (NZDT) X-Virus-Scanned: Debian amavisd-new at citylink.co.nz Received: from pele.citylink.co.nz ([127.0.0.1]) by localhost (pele.citylink.co.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qmzwvtdk9CY9; Fri, 30 Jan 2009 08:28:31 +1300 (NZDT) Received: from citylink.fud.org.nz (unknown [202.8.44.45]) by pele.citylink.co.nz (Postfix) with ESMTP; Fri, 30 Jan 2009 08:28:31 +1300 (NZDT) Received: by citylink.fud.org.nz (Postfix, from userid 1001) id E6A1E1142E; Fri, 30 Jan 2009 08:28:30 +1300 (NZDT) Date: Thu, 29 Jan 2009 11:28:30 -0800 From: Andrew Thompson To: Lars Engels Message-ID: <20090129192830.GE73709@citylink.fud.org.nz> References: <20090129192241.GZ60948@e.0x20.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090129192241.GZ60948@e.0x20.net> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: sam@FreBSD.org, current@FreeBSD.org Subject: Re: ath cannot find my wireless network any more X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 19:28:36 -0000 On Thu, Jan 29, 2009 at 08:22:41PM +0100, Lars Engels wrote: > Hi all, > hi Sam, > > I just build world && kernel from todays sources. > Now my Atheros 5212 pccard cannot find my wireless network any more, but > still sees other networks: > > lars@pts/3 # ifconfig wlan0 up scan > SSID BSSID CHAN RATE S:N INT CAPS > Arcor-C6DE58 00:1a:2a:c6:de:56 9 54M -95:-96 100 EPS RSN WPA WME > WLAN-AFCB47 00:1d:19:af:cb:e0 1 54M -96:-96 100 EPS WPS RSN WPA WME > 0x0000 00:03:c9:54:18:bb 8 54M -94:-96 100 EP WPA > > In contrast to this, the internal wpi chip still finds and connects to the network: > lars@pts/3 # ifconfig wlan1 scan > SSID BSSID CHAN RATE S:N INT CAPS > dd-wrt 00:18:39:c7:6a:dd 6 54M 22:0 100 EP RSN WME > > I also don't know why wpi only finds my own network. If you go 'ifconfig wlan0 list chan' does it show #6 as available? Andrew From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 19:48:27 2009 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 A0D8B106566B; Thu, 29 Jan 2009 19:48:27 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: from mail.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb::3]) by mx1.freebsd.org (Postfix) with ESMTP id 5925F8FC18; Thu, 29 Jan 2009 19:48:27 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: by mail.0x20.net (Postfix, from userid 1002) id 7FD8933C26; Thu, 29 Jan 2009 20:48:26 +0100 (CET) Date: Thu, 29 Jan 2009 20:48:26 +0100 From: Lars Engels To: Andrew Thompson Message-ID: <20090129194826.GA60948@e.0x20.net> References: <20090129192241.GZ60948@e.0x20.net> <20090129192830.GE73709@citylink.fud.org.nz> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mz5eWKkhz39mMVQV" Content-Disposition: inline In-Reply-To: <20090129192830.GE73709@citylink.fud.org.nz> X-Editor: VIM - Vi IMproved 7.1 X-Operation-System: FreeBSD 5.5-RELEASE-p19 User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: sam@FreBSD.org, current@FreeBSD.org Subject: Re: ath cannot find my wireless network any more X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Lars Engels List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2009 19:48:27 -0000 --mz5eWKkhz39mMVQV Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 29, 2009 at 11:28:30AM -0800, Andrew Thompson wrote: > On Thu, Jan 29, 2009 at 08:22:41PM +0100, Lars Engels wrote: > > Hi all, > > hi Sam, > >=20 > > I just build world && kernel from todays sources. > > Now my Atheros 5212 pccard cannot find my wireless network any more, but > > still sees other networks: > >=20 > > lars@pts/3 # ifconfig wlan0 up scan > > SSID BSSID CHAN RATE S:N INT CAPS > > Arcor-C6DE58 00:1a:2a:c6:de:56 9 54M -95:-96 100 EPS RSN WPA = WME > > WLAN-AFCB47 00:1d:19:af:cb:e0 1 54M -96:-96 100 EPS WPS RSN = WPA WME > > 0x0000 00:03:c9:54:18:bb 8 54M -94:-96 100 EP WPA > >=20 > > In contrast to this, the internal wpi chip still finds and connects to = the network: > > lars@pts/3 # ifconfig wlan1 scan > > SSID BSSID CHAN RATE S:N INT CAPS > > dd-wrt 00:18:39:c7:6a:dd 6 54M 22:0 100 EP RSN WME > >=20 > > I also don't know why wpi only finds my own network. > =20 > If you go 'ifconfig wlan0 list chan' does it show #6 as available? Yes, it's there: lars@pts/3 # ifconfig wlan0 list chan Channel 1 : 2412 Mhz 11g Channel 48 : 5240 Mhz 11a Turbo Channel 2 : 2417 Mhz 11g Channel 50 : 5250 Mhz 11a Turbo Channel 3 : 2422 Mhz 11g Channel 52 : 5260 Mhz 11a Channel 4 : 2427 Mhz 11g Channel 56 : 5280 Mhz 11a Turbo Channel 5 : 2432 Mhz 11g Channel 58 : 5290 Mhz 11a Turbo Channel 6 : 2437 Mhz 11g Turbo Channel 60 : 5300 Mhz 11a Channel 7 : 2442 Mhz 11g Channel 64 : 5320 Mhz 11a Channel 8 : 2447 Mhz 11g Channel 149 : 5745 Mhz 11a Channel 9 : 2452 Mhz 11g Channel 152 : 5760 Mhz 11a Turbo Channel 10 : 2457 Mhz 11g Channel 153 : 5765 Mhz 11a Turbo Channel 11 : 2462 Mhz 11g Channel 157 : 5785 Mhz 11a Channel 36 : 5180 Mhz 11a Channel 160 : 5800 Mhz 11a Turbo Channel 40 : 5200 Mhz 11a Turbo Channel 161 : 5805 Mhz 11a Turbo Channel 42 : 5210 Mhz 11a Turbo Channel 165 : 5825 Mhz 11a Channel 44 : 5220 Mhz 11a --mz5eWKkhz39mMVQV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkmCCAoACgkQKc512sD3afgs/ACgjsYk4tdeFJi+9sjp3ugTW1L/ Y6kAn1FA1AgCshoUzkXTv4FTWsBE1Dno =ipdr -----END PGP SIGNATURE----- --mz5eWKkhz39mMVQV-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 20:16:45 2009 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 82D1B1065672 for ; Thu, 29 Jan 2009 20:16:45 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 346E18FC0A for ; Thu, 29 Jan 2009 20:16:44 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n0TKGiak040896 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Jan 2009 12:16:44 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <49820EAC.5090400@freebsd.org> Date: Thu, 29 Jan 2009 12:16:44 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: Lars Engels References: <20090129192241.GZ60948@e.0x20.net> <20090129192830.GE73709@citylink.fud.org.nz> <20090129194826.GA60948@e.0x20.net> In-Reply-To: <20090129194826.GA60948@e.0x20.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-Rhyolite-Metrics: ebb.errno.com; whitelist Cc: current@freebsd.org Subject: Re: ath cannot find my wireless network any more X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 20:16:45 -0000 Lars Engels wrote: > On Thu, Jan 29, 2009 at 11:28:30AM -0800, Andrew Thompson wrote: > >> On Thu, Jan 29, 2009 at 08:22:41PM +0100, Lars Engels wrote: >> >>> Hi all, >>> hi Sam, >>> >>> I just build world && kernel from todays sources. >>> Now my Atheros 5212 pccard cannot find my wireless network any more, but >>> still sees other networks: >>> >>> lars@pts/3 # ifconfig wlan0 up scan >>> SSID BSSID CHAN RATE S:N INT CAPS >>> Arcor-C6DE58 00:1a:2a:c6:de:56 9 54M -95:-96 100 EPS RSN WPA WME >>> WLAN-AFCB47 00:1d:19:af:cb:e0 1 54M -96:-96 100 EPS WPS RSN WPA WME >>> 0x0000 00:03:c9:54:18:bb 8 54M -94:-96 100 EP WPA >>> >>> In contrast to this, the internal wpi chip still finds and connects to the network: >>> lars@pts/3 # ifconfig wlan1 scan >>> SSID BSSID CHAN RATE S:N INT CAPS >>> dd-wrt 00:18:39:c7:6a:dd 6 54M 22:0 100 EP RSN WME >>> >>> I also don't know why wpi only finds my own network. >>> >> >> If you go 'ifconfig wlan0 list chan' does it show #6 as available? >> > > > Yes, it's there: > lars@pts/3 # ifconfig wlan0 list chan > Channel 1 : 2412 Mhz 11g Channel 48 : 5240 Mhz 11a Turbo > Channel 2 : 2417 Mhz 11g Channel 50 : 5250 Mhz 11a Turbo > Channel 3 : 2422 Mhz 11g Channel 52 : 5260 Mhz 11a > Channel 4 : 2427 Mhz 11g Channel 56 : 5280 Mhz 11a Turbo > Channel 5 : 2432 Mhz 11g Channel 58 : 5290 Mhz 11a Turbo > Channel 6 : 2437 Mhz 11g Turbo Channel 60 : 5300 Mhz 11a > Channel 7 : 2442 Mhz 11g Channel 64 : 5320 Mhz 11a > Channel 8 : 2447 Mhz 11g Channel 149 : 5745 Mhz 11a > Channel 9 : 2452 Mhz 11g Channel 152 : 5760 Mhz 11a Turbo > Channel 10 : 2457 Mhz 11g Channel 153 : 5765 Mhz 11a Turbo > Channel 11 : 2462 Mhz 11g Channel 157 : 5785 Mhz 11a > Channel 36 : 5180 Mhz 11a Channel 160 : 5800 Mhz 11a Turbo > Channel 40 : 5200 Mhz 11a Turbo Channel 161 : 5805 Mhz 11a Turbo > Channel 42 : 5210 Mhz 11a Turbo Channel 165 : 5825 Mhz 11a > Channel 44 : 5220 Mhz 11a > > Not sure about the wpi complaint. For ath I need mac+phy revs and any regulatory setting (output sysctl dev.ath.0 will show it). You might also enable scan debug to see if the ap shows up but isn't recorded for some reason; e.g. wlandebug -i ath0 scan. I committed major hal changes as a single commit so you can easily back it out to see if it's the reason. The other recent changes to net80211 should not matter if you rebuilt world to match the kernel (the size of the channel structure changed so kernel+apps need to match). Sam From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 20:26:34 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7902210656FB for ; Thu, 29 Jan 2009 20:26:34 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from smtp8.server.rpi.edu (smtp8.server.rpi.edu [128.113.2.228]) by mx1.freebsd.org (Postfix) with ESMTP id 0AF278FC1F for ; Thu, 29 Jan 2009 20:26:33 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp8.server.rpi.edu (8.13.1/8.13.1) with ESMTP id n0TKQUv3026060; Thu, 29 Jan 2009 15:26:32 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: <49816854.9060909@gmx.de> References: <20090128155340.GA75143@lpthe.jussieu.fr> <7508A5B5-C6D2-498A-AEA1-D84E85F1D743@mac.com> <200901291243.00378.doconnor@gsoft.com.au> <49811242.7030106@delphij.net> <498116AB.2060105@gmail.com> <49816854.9060909@gmx.de> Date: Thu, 29 Jan 2009 15:26:29 -0500 To: Christoph Mallon From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Bayes-Prob: 0.0001 (Score 0) X-RPI-SA-Score: 0.60 () [Hold at 20.00] J_CHICKENPOX_43,22490(-25) X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.228 Cc: freebsd-current@freebsd.org Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 20:26:35 -0000 At 9:27 AM +0100 1/29/09, Christoph Mallon wrote: >Eitan Adler schrieb: >>To quote from the FAQ: >>Who does this change affect? >> Nobody who is currently using GCC should be affected by this change. > >Let me repeat that: >"Nobody who is currently using GCC *should* be affected by this change." > >Emphasize mine. There have been a couple of different issues brought up in this thread, and I've lost track of which one we're on. But one of the issues is the use of LLVM+gcc, and my guess is that the above statement would not apply to that. That is just my guess, of course. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 20:43:25 2009 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 303911065675; Thu, 29 Jan 2009 20:43:25 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: from mail.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb::3]) by mx1.freebsd.org (Postfix) with ESMTP id 574178FC08; Thu, 29 Jan 2009 20:43:24 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: by mail.0x20.net (Postfix, from userid 1002) id 6F7FE33C14; Thu, 29 Jan 2009 21:43:23 +0100 (CET) Date: Thu, 29 Jan 2009 21:43:23 +0100 From: Lars Engels To: Sam Leffler Message-ID: <20090129204323.GB60948@e.0x20.net> References: <20090129192241.GZ60948@e.0x20.net> <20090129192830.GE73709@citylink.fud.org.nz> <20090129194826.GA60948@e.0x20.net> <49820EAC.5090400@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BtNCO5h84ExDStzY" Content-Disposition: inline In-Reply-To: <49820EAC.5090400@freebsd.org> X-Editor: VIM - Vi IMproved 7.1 X-Operation-System: FreeBSD 5.5-RELEASE-p19 User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: current@freebsd.org Subject: Re: ath cannot find my wireless network any more X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Lars Engels List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2009 20:43:25 -0000 --BtNCO5h84ExDStzY Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 29, 2009 at 12:16:44PM -0800, Sam Leffler wrote: > Lars Engels wrote: > >On Thu, Jan 29, 2009 at 11:28:30AM -0800, Andrew Thompson wrote: > > =20 > >>On Thu, Jan 29, 2009 at 08:22:41PM +0100, Lars Engels wrote: > >> =20 > >>>Hi all, > >>>hi Sam, > >>> > >>>I just build world && kernel from todays sources. > >>>Now my Atheros 5212 pccard cannot find my wireless network any more, b= ut > >>>still sees other networks: > >>> > >>>lars@pts/3 # ifconfig wlan0 up scan > >>>SSID BSSID CHAN RATE S:N INT CAPS > >>>Arcor-C6DE58 00:1a:2a:c6:de:56 9 54M -95:-96 100 EPS RSN WPA= WME > >>>WLAN-AFCB47 00:1d:19:af:cb:e0 1 54M -96:-96 100 EPS WPS RSN= WPA WME > >>>0x0000 00:03:c9:54:18:bb 8 54M -94:-96 100 EP WPA > >>> > >>>In contrast to this, the internal wpi chip still finds and connects to= the network: > >>>lars@pts/3 # ifconfig wlan1 scan > >>>SSID BSSID CHAN RATE S:N INT CAPS > >>>dd-wrt 00:18:39:c7:6a:dd 6 54M 22:0 100 EP RSN WME > >>> > >>>I also don't know why wpi only finds my own network. > >>> =20 > >> If you go 'ifconfig wlan0 list chan' does it show #6 as available? > >> =20 > > > > > >Yes, it's there: > >lars@pts/3 # ifconfig wlan0 list chan > >Channel 1 : 2412 Mhz 11g Channel 48 : 5240 Mhz 11a Turbo > >Channel 2 : 2417 Mhz 11g Channel 50 : 5250 Mhz 11a Turbo > >Channel 3 : 2422 Mhz 11g Channel 52 : 5260 Mhz 11a > >Channel 4 : 2427 Mhz 11g Channel 56 : 5280 Mhz 11a Turbo > >Channel 5 : 2432 Mhz 11g Channel 58 : 5290 Mhz 11a Turbo > >Channel 6 : 2437 Mhz 11g Turbo Channel 60 : 5300 Mhz 11a > >Channel 7 : 2442 Mhz 11g Channel 64 : 5320 Mhz 11a > >Channel 8 : 2447 Mhz 11g Channel 149 : 5745 Mhz 11a > >Channel 9 : 2452 Mhz 11g Channel 152 : 5760 Mhz 11a Turbo > >Channel 10 : 2457 Mhz 11g Channel 153 : 5765 Mhz 11a Turbo > >Channel 11 : 2462 Mhz 11g Channel 157 : 5785 Mhz 11a > >Channel 36 : 5180 Mhz 11a Channel 160 : 5800 Mhz 11a Turbo > >Channel 40 : 5200 Mhz 11a Turbo Channel 161 : 5805 Mhz 11a Turbo > >Channel 42 : 5210 Mhz 11a Turbo Channel 165 : 5825 Mhz 11a > >Channel 44 : 5220 Mhz 11a > > > > =20 >=20 > Not sure about the wpi complaint. For ath I need mac+phy revs and any > regulatory setting (output sysctl dev.ath.0 will show it). You might > also enable scan debug to see if the ap shows up but isn't recorded > for some reason; e.g. wlandebug -i ath0 scan. Here is the output for sysctl: ars@pts/3 # sysctl dev.ath.0 dev.ath.0.%desc: Atheros 5212 dev.ath.0.%driver: ath dev.ath.0.%location: slot=3D0 function=3D0 dev.ath.0.%pnpinfo: vendor=3D0x168c device=3D0x0013 subvendor=3D0x1385 subdevice=3D0x4610 class=3D0x020000 dev.ath.0.%parent: cardbus0 dev.ath.0.smoothing_rate: 95 dev.ath.0.sample_rate: 10 dev.ath.0.sample_stats: 0 dev.ath.0.countrycode: 0 dev.ath.0.regdomain: 0 dev.ath.0.slottime: 9 dev.ath.0.acktimeout: 48 dev.ath.0.ctstimeout: 48 dev.ath.0.softled: 0 dev.ath.0.ledpin: 0 dev.ath.0.ledon: 0 dev.ath.0.ledidle: 2700 dev.ath.0.txantenna: 0 dev.ath.0.rxantenna: 2 dev.ath.0.diversity: 1 dev.ath.0.txintrperiod: 5 dev.ath.0.diag: 0 dev.ath.0.tpscale: 0 dev.ath.0.tpc: 0 dev.ath.0.tpack: 63 dev.ath.0.tpcts: 63 dev.ath.0.fftxqmin: 2 dev.ath.0.fftxqmax: 50 dev.ath.0.intmit: 1 dev.ath.0.monpass: 24 lars@pts/3 # wlandebug -i ath0 scan wlandebug: expecting a wlan interface name So I ran # wlandebug -i wlan0 scan net.wlan.0.debug: 0x0 =3D> 0x200000 But nothing new then: lars@pts/3 # ifconfig wlan0 up scan SSID BSSID CHAN RATE S:N INT CAPS WLAN-AFCB47 00:1d:19:af:cb:e0 1 54M -93:-96 100 EPS RSN WPA WME = WPS neumann 00:1b:2f:db:4f:dc 11 54M -95:-96 100 EPS 0x0000 00:03:c9:54:18:bb 8 54M -94:-96 100 EP WPA Arcor-C6DE58 00:1a:2a:c6:de:56 9 54M -93:-96 100 EPS RSN WPA WME > I committed major hal changes as a single commit so you can easily > back it out to see if it's the reason. The other recent changes to > net80211 should not matter if you rebuilt world to match the kernel > (the size of the channel structure changed so kernel+apps need to > match). I re-built world, so the net80211 commit should not be the issue. The ath device worked with sources from last week, so if there was no other wireless related commit, I guess the new hal changes caused the problem. I can back out the hal commit if you don't see anything obvious in my configuration. Lars --BtNCO5h84ExDStzY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkmCFOsACgkQKc512sD3afiF3QCgy4y2fxYcPMW7zsJmE2sDSZet LEUAoIcROg7H3ejbgaaYw6v789l82SIc =tl7i -----END PGP SIGNATURE----- --BtNCO5h84ExDStzY-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 21:28:05 2009 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 78A141065690 for ; Thu, 29 Jan 2009 21:28:05 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id D1CE98FC23 for ; Thu, 29 Jan 2009 21:28:04 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by ewy14 with SMTP id 14so438154ewy.19 for ; Thu, 29 Jan 2009 13:28:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=UuxuCJuSz7nVQZpL5z61O0KBzQR506B3ekYi/mMo8NI=; b=lR8Lt327ZU5JLcC+Y6K5ynbHsF7WC/WwpDdJtYbKnZhcgEBShBxOR3G5eEqR9Jg/HC CmaY4y+WnhvojXdG4wSS5hpy2s0cITma6Z1VL66gEDRUs8rkXlWAM1iJAIQ9lGBQen2y RYb/9DtxXCOGBdzTo/MCeno9yQKGk1C5Jy0/U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=jtcP/NC6sfqM3IOz+vxnwMgey+ihern0JuD4CRk3/CFYGY4Yl3Ki5k0y3InemqiNoK iXKozVARKAmFGyE/XCR8os8vy8zUdQE+JO3gkM0WbzOiIbyDx3qyN6eKxMjywVqdGgHJ DcGo0p8A5NHh/X3sHBhIj0YvrLlm+A6kmpOKM= MIME-Version: 1.0 Received: by 10.210.105.2 with SMTP id d2mr609158ebc.17.1233264483587; Thu, 29 Jan 2009 13:28:03 -0800 (PST) In-Reply-To: <20090129204323.GB60948@e.0x20.net> References: <20090129192241.GZ60948@e.0x20.net> <20090129192830.GE73709@citylink.fud.org.nz> <20090129194826.GA60948@e.0x20.net> <49820EAC.5090400@freebsd.org> <20090129204323.GB60948@e.0x20.net> Date: Thu, 29 Jan 2009 22:28:03 +0100 Message-ID: <3a142e750901291328w537b2070t216e393a0fd5b8ba@mail.gmail.com> From: "Paul B. Mahol" To: Lars Engels Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: ath cannot find my wireless network any more X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 21:28:06 -0000 On 1/29/09, Lars Engels wrote: > On Thu, Jan 29, 2009 at 12:16:44PM -0800, Sam Leffler wrote: >> Lars Engels wrote: >> >On Thu, Jan 29, 2009 at 11:28:30AM -0800, Andrew Thompson wrote: >> > >> >>On Thu, Jan 29, 2009 at 08:22:41PM +0100, Lars Engels wrote: >> >> >> >>>Hi all, >> >>>hi Sam, >> >>> >> >>>I just build world && kernel from todays sources. >> >>>Now my Atheros 5212 pccard cannot find my wireless network any more, >> >>> but >> >>>still sees other networks: >> >>> >> >>>lars@pts/3 # ifconfig wlan0 up scan >> >>>SSID BSSID CHAN RATE S:N INT CAPS >> >>>Arcor-C6DE58 00:1a:2a:c6:de:56 9 54M -95:-96 100 EPS RSN WPA >> >>> WME >> >>>WLAN-AFCB47 00:1d:19:af:cb:e0 1 54M -96:-96 100 EPS WPS RSN >> >>> WPA WME >> >>>0x0000 00:03:c9:54:18:bb 8 54M -94:-96 100 EP WPA >> >>> >> >>>In contrast to this, the internal wpi chip still finds and connects to >> >>> the network: >> >>>lars@pts/3 # ifconfig wlan1 scan >> >>>SSID BSSID CHAN RATE S:N INT CAPS >> >>>dd-wrt 00:18:39:c7:6a:dd 6 54M 22:0 100 EP RSN WME >> >>> >> >>>I also don't know why wpi only finds my own network. If such behavior was from start(not regression) it can means only wpi problem/feature. >> >>> >> >> If you go 'ifconfig wlan0 list chan' does it show #6 as available? >> >> >> > >> > >> >Yes, it's there: >> >lars@pts/3 # ifconfig wlan0 list chan >> >Channel 1 : 2412 Mhz 11g Channel 48 : 5240 Mhz 11a Turbo >> >Channel 2 : 2417 Mhz 11g Channel 50 : 5250 Mhz 11a Turbo >> >Channel 3 : 2422 Mhz 11g Channel 52 : 5260 Mhz 11a >> >Channel 4 : 2427 Mhz 11g Channel 56 : 5280 Mhz 11a Turbo >> >Channel 5 : 2432 Mhz 11g Channel 58 : 5290 Mhz 11a Turbo >> >Channel 6 : 2437 Mhz 11g Turbo Channel 60 : 5300 Mhz 11a >> >Channel 7 : 2442 Mhz 11g Channel 64 : 5320 Mhz 11a >> >Channel 8 : 2447 Mhz 11g Channel 149 : 5745 Mhz 11a >> >Channel 9 : 2452 Mhz 11g Channel 152 : 5760 Mhz 11a Turbo >> >Channel 10 : 2457 Mhz 11g Channel 153 : 5765 Mhz 11a Turbo >> >Channel 11 : 2462 Mhz 11g Channel 157 : 5785 Mhz 11a >> >Channel 36 : 5180 Mhz 11a Channel 160 : 5800 Mhz 11a Turbo >> >Channel 40 : 5200 Mhz 11a Turbo Channel 161 : 5805 Mhz 11a Turbo >> >Channel 42 : 5210 Mhz 11a Turbo Channel 165 : 5825 Mhz 11a >> >Channel 44 : 5220 Mhz 11a >> > >> > >> >> Not sure about the wpi complaint. For ath I need mac+phy revs and any >> regulatory setting (output sysctl dev.ath.0 will show it). You might >> also enable scan debug to see if the ap shows up but isn't recorded >> for some reason; e.g. wlandebug -i ath0 scan. > > Here is the output for sysctl: > > ars@pts/3 # sysctl dev.ath.0 > dev.ath.0.%desc: Atheros 5212 > dev.ath.0.%driver: ath > dev.ath.0.%location: slot=0 function=0 > dev.ath.0.%pnpinfo: vendor=0x168c device=0x0013 subvendor=0x1385 > subdevice=0x4610 class=0x020000 > dev.ath.0.%parent: cardbus0 > dev.ath.0.smoothing_rate: 95 > dev.ath.0.sample_rate: 10 > dev.ath.0.sample_stats: 0 > dev.ath.0.countrycode: 0 > dev.ath.0.regdomain: 0 > dev.ath.0.slottime: 9 > dev.ath.0.acktimeout: 48 > dev.ath.0.ctstimeout: 48 > dev.ath.0.softled: 0 > dev.ath.0.ledpin: 0 > dev.ath.0.ledon: 0 > dev.ath.0.ledidle: 2700 > dev.ath.0.txantenna: 0 > dev.ath.0.rxantenna: 2 > dev.ath.0.diversity: 1 > dev.ath.0.txintrperiod: 5 > dev.ath.0.diag: 0 > dev.ath.0.tpscale: 0 > dev.ath.0.tpc: 0 > dev.ath.0.tpack: 63 > dev.ath.0.tpcts: 63 > dev.ath.0.fftxqmin: 2 > dev.ath.0.fftxqmax: 50 > dev.ath.0.intmit: 1 > dev.ath.0.monpass: 24 > > > lars@pts/3 # wlandebug -i ath0 scan > wlandebug: expecting a wlan interface name > > So I ran > # wlandebug -i wlan0 scan > net.wlan.0.debug: 0x0 => 0x200000 > > But nothing new then: Interesting output is not available from ifconfig it is printed by kernel on console. > lars@pts/3 # ifconfig wlan0 up scan > SSID BSSID CHAN RATE S:N INT CAPS > WLAN-AFCB47 00:1d:19:af:cb:e0 1 54M -93:-96 100 EPS RSN WPA WME > WPS > neumann 00:1b:2f:db:4f:dc 11 54M -95:-96 100 EPS > 0x0000 00:03:c9:54:18:bb 8 54M -94:-96 100 EP WPA > Arcor-C6DE58 00:1a:2a:c6:de:56 9 54M -93:-96 100 EPS RSN WPA WME > > >> I committed major hal changes as a single commit so you can easily >> back it out to see if it's the reason. The other recent changes to >> net80211 should not matter if you rebuilt world to match the kernel >> (the size of the channel structure changed so kernel+apps need to >> match). > > I re-built world, so the net80211 commit should not be the issue. > The ath device worked with sources from last week, so if there was no > other wireless related commit, I guess the new hal changes caused the > problem. I can back out the hal commit if you don't see anything obvious > in my configuration. > > Lars > -- Paul From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 21:53:44 2009 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 B2CD1106564A for ; Thu, 29 Jan 2009 21:53:44 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: from iron2.pdx.net (iron2.pdx.net [69.64.224.71]) by mx1.freebsd.org (Postfix) with ESMTP id 8C5CE8FC0C for ; Thu, 29 Jan 2009 21:53:44 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: (qmail 32205 invoked from network); 29 Jan 2009 13:53:43 -0800 Received: from 069-064-235-060.pdx.net (HELO ?192.168.1.51?) (69.64.235.60) by iron2.pdx.net with SMTP; 29 Jan 2009 13:53:43 -0800 From: Sean Bruno To: Jaakko Heinonen In-Reply-To: <20090129152006.GA3790@a91-153-125-115.elisa-laajakaista.fi> References: <1233098540.2494.6.camel@localhost.localdomain> <49809B45.1000703@boland.org> <1233166048.3592.1.camel@localhost.localdomain> <20090129081654.GB854@a91-153-125-115.elisa-laajakaista.fi> <20090129152006.GA3790@a91-153-125-115.elisa-laajakaista.fi> Content-Type: text/plain Date: Thu, 29 Jan 2009 13:53:43 -0800 Message-Id: <1233266023.3592.1082.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 (2.24.3-1.fc10) Content-Transfer-Encoding: 7bit Cc: Michiel Boland , current@freebsd.org Subject: Re: NFS mounts dissapearing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 21:53:45 -0000 On Thu, 2009-01-29 at 17:20 +0200, Jaakko Heinonen wrote: > On 2009-01-29, Jaakko Heinonen wrote: > > > > It appears to me that TCP connections to remote nfsd use a > > > > privileged source port initially, > > > > but if the connection is severed and reestablished later the source > > > > port is no longer < 1024. Client is -CURRENT, server is solaris with > > > > nfssrv:nfs_portmon=1. > > > > Indeed it looks like the new RPC code (I didn't verify that the old > > works though) doesn't honour the resvport mount option on reconnects. > > I think I found the bug. The new RPC code doesn't properly elevate > privileges before bindresvport() call in clnt_reconnect_connect(). For > initial connection bindresvport() succeeds because the process has > elevated privileges at that time. > > Does this patch fix the problem for you? > > %%% > Index: sys/rpc/clnt_rc.c > =================================================================== > --- sys/rpc/clnt_rc.c (revision 187877) > +++ sys/rpc/clnt_rc.c (working copy) > @@ -181,11 +181,12 @@ again: > rpc_createerr.cf_error.re_errno = 0; > goto out; > } > - if (rc->rc_privport) > - bindresvport(so, NULL); > > oldcred = td->td_ucred; > td->td_ucred = rc->rc_ucred; > + if (rc->rc_privport) > + bindresvport(so, NULL); > + > if (rc->rc_nconf->nc_semantics == NC_TPI_CLTS) > rc->rc_client = clnt_dg_create(so, > (struct sockaddr *) &rc->rc_addr, rc->rc_prog, rc->rc_vers, > %%% > Yes. This patch resolves my issues. Thanks for the quick fix! Commit! Sean Bruno From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 21:54:25 2009 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 B971B106566B for ; Thu, 29 Jan 2009 21:54:25 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: from mail.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb::3]) by mx1.freebsd.org (Postfix) with ESMTP id 4A3028FC18 for ; Thu, 29 Jan 2009 21:54:25 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: by mail.0x20.net (Postfix, from userid 1002) id 8BE3633C9B; Thu, 29 Jan 2009 22:54:24 +0100 (CET) Date: Thu, 29 Jan 2009 22:54:24 +0100 From: Lars Engels To: "Paul B. Mahol" Message-ID: <20090129215424.GC60948@e.0x20.net> References: <20090129192241.GZ60948@e.0x20.net> <20090129192830.GE73709@citylink.fud.org.nz> <20090129194826.GA60948@e.0x20.net> <49820EAC.5090400@freebsd.org> <20090129204323.GB60948@e.0x20.net> <3a142e750901291328w537b2070t216e393a0fd5b8ba@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sKosZo66cxuwvnFI" Content-Disposition: inline In-Reply-To: <3a142e750901291328w537b2070t216e393a0fd5b8ba@mail.gmail.com> X-Editor: VIM - Vi IMproved 7.1 X-Operation-System: FreeBSD 5.5-RELEASE-p19 User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: current@freebsd.org Subject: Re: ath cannot find my wireless network any more X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Lars Engels List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2009 21:54:26 -0000 --sKosZo66cxuwvnFI Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 29, 2009 at 10:28:03PM +0100, Paul B. Mahol wrote: > On 1/29/09, Lars Engels wrote: > > On Thu, Jan 29, 2009 at 12:16:44PM -0800, Sam Leffler wrote: > >> Lars Engels wrote: > >> >On Thu, Jan 29, 2009 at 11:28:30AM -0800, Andrew Thompson wrote: > >> > > >> >>On Thu, Jan 29, 2009 at 08:22:41PM +0100, Lars Engels wrote: > >> >> > >> >>>Hi all, > >> >>>hi Sam, > >> >>> > >> >>>I just build world && kernel from todays sources. > >> >>>Now my Atheros 5212 pccard cannot find my wireless network any more, > >> >>> but > >> >>>still sees other networks: > >> >>> > >> >>>lars@pts/3 # ifconfig wlan0 up scan > >> >>>SSID BSSID CHAN RATE S:N INT CAPS > >> >>>Arcor-C6DE58 00:1a:2a:c6:de:56 9 54M -95:-96 100 EPS RSN = WPA > >> >>> WME > >> >>>WLAN-AFCB47 00:1d:19:af:cb:e0 1 54M -96:-96 100 EPS WPS = RSN > >> >>> WPA WME > >> >>>0x0000 00:03:c9:54:18:bb 8 54M -94:-96 100 EP WPA > >> >>> > >> >>>In contrast to this, the internal wpi chip still finds and connects= to > >> >>> the network: > >> >>>lars@pts/3 # ifconfig wlan1 scan > >> >>>SSID BSSID CHAN RATE S:N INT CAPS > >> >>>dd-wrt 00:18:39:c7:6a:dd 6 54M 22:0 100 EP RSN = WME > >> >>> > >> >>>I also don't know why wpi only finds my own network. >=20 > If such behavior was from start(not regression) it can means only wpi > problem/feature. I can't tell because I haven't used wpi for months... But now I am glad that it can still connect to my wireless network. :) > > So I ran > > # wlandebug -i wlan0 scan > > net.wlan.0.debug: 0x0 =3D> 0x200000 > > > > But nothing new then: >=20 > Interesting output is not available from ifconfig it is printed by > kernel on console. Ahhh, thanks for the hint. There's a lot of scanning going on in /var/log/messages but no sign of my own network. --sKosZo66cxuwvnFI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkmCJZAACgkQKc512sD3afiY6ACfRuhYT4BoyAIoyTQb7iA6695f VvwAn3eNlq12ts7NLGDN8Jm0mD2NYj0X =+d/G -----END PGP SIGNATURE----- --sKosZo66cxuwvnFI-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 22:15:19 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86918106567B for ; Thu, 29 Jan 2009 22:15:19 +0000 (UTC) (envelope-from das@FreeBSD.ORG) Received: from zim.MIT.EDU (ZIM.MIT.EDU [18.95.3.101]) by mx1.freebsd.org (Postfix) with ESMTP id 468E08FC26 for ; Thu, 29 Jan 2009 22:15:19 +0000 (UTC) (envelope-from das@FreeBSD.ORG) Received: from zim.MIT.EDU (localhost [127.0.0.1]) by zim.MIT.EDU (8.14.3/8.14.2) with ESMTP id n0TLvKbh003023; Thu, 29 Jan 2009 16:57:20 -0500 (EST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by zim.MIT.EDU (8.14.3/8.14.2/Submit) id n0TLvKge003022; Thu, 29 Jan 2009 16:57:20 -0500 (EST) (envelope-from das@FreeBSD.ORG) Date: Thu, 29 Jan 2009 16:57:20 -0500 From: David Schultz To: Philipp Wuensche Message-ID: <20090129215720.GA2889@zim.MIT.EDU> Mail-Followup-To: Philipp Wuensche , freebsd-current@FreeBSD.ORG References: <4981EBC6.1000907@h3q.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4981EBC6.1000907@h3q.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Solaris live upgrade like FreeBSD ZFS-rootfs 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: Thu, 29 Jan 2009 22:15:20 -0000 On Thu, Jan 29, 2009, Philipp Wuensche wrote: > With ZFS suddenly some neat stuff is easly possible with FreeBSD, like > the Solaris Live Upgrade feature. The idea behinde Live Upgrade is that > you have more than one bootable-environment to boot from making it very > painless to upgrade to newer FreeBSD versions without loosing the > possibility to boot your known-good boot-environemt. So you can't end up > with a broken userland or kernel and you can even go back to your old > userland and kernel if the new ones do not work for you. Nice. Right now, upgrading from source involves the multi-step dance of: - build - installkernel - reboot in single user mode - mergemaster -p - installworld - mergemaster This sequence is designed to maximize the odds that you can recover easily if something goes wrong, but many users don't know how to recover, and you can still shoot yourself in the foot if installworld fails, e.g., due to a new bug in libc. But since both ZFS and UFS support snapshots now, it would be great if the process were something like: - drop to single user mode - take snapshots of / and /usr - install everything - reboot But if something goes wrong, only ZFS has the ability to roll back to the last snapshot, and even then I'm not sure if you can actually boot from that snapshot in order to recover. Nonetheless, perhaps it's worth incorporating the idea of "take a snapshot before you upgrade" into the documented upgrade procedure. More than once, it's saved me the headache of finding a CD with a version of libc that will work with my kernel. From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 22:32:38 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13242106567D for ; Thu, 29 Jan 2009 22:32:38 +0000 (UTC) (envelope-from nakal@web.de) Received: from fmmailgate01.web.de (fmmailgate01.web.de [217.72.192.221]) by mx1.freebsd.org (Postfix) with ESMTP id 7FD398FC25 for ; Thu, 29 Jan 2009 22:32:37 +0000 (UTC) (envelope-from nakal@web.de) Received: from smtp05.web.de (fmsmtp05.dlan.cinetic.de [172.20.4.166]) by fmmailgate01.web.de (Postfix) with ESMTP id 16048FC75BAD; Thu, 29 Jan 2009 23:32:36 +0100 (CET) Received: from [217.236.2.27] (helo=zelda.local) by smtp05.web.de with asmtp (TLSv1:AES128-SHA:128) (WEB.DE 4.110 #277) id 1LSfR5-00069m-00; Thu, 29 Jan 2009 23:32:35 +0100 Date: Thu, 29 Jan 2009 23:32:20 +0100 From: Martin To: sbruno@freebsd.org Message-ID: <20090129233220.1ed64e6d@zelda.local> In-Reply-To: <1233007263.9302.2.camel@localhost.localdomain> References: <1233007263.9302.2.camel@localhost.localdomain> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: nakal@web.de X-Sender: nakal@web.de X-Provags-ID: V01U2FsdGVkX19Pxn9kt1aPsbb4dTQzMpnUXa6XDz3ler2d6mt/ 560sHPLbWZPhk7xCx7Vx97Y0DssmoQwUdyORFG2pFpcqJpiGDg J/09KJkWU= Cc: sean.bruno@dsl-only.net, freebsd-current@freebsd.org Subject: Re: UFS Witness LoR + 5 other LoRs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jan 2009 22:32:41 -0000 Am Mon, 26 Jan 2009 14:01:03 -0800 schrieb Sean Bruno : > Anyone else seeing this LoR today? > > lock order reversal: > 1st 0xc456b044 user map (user map) > @ /root/bsd/head/sys/vm/vm_map.c:3198 > 2nd 0xc4911ad0 ufs (ufs) @ /root/bsd/head/sys/kern/vfs_subr.c:2071 > KDB: stack backtrace: > db_trace_self_wrapper(c0bf0913,c417990c,c087a4b5,c0c1458c,0,...) at > db_trace_self_wrapper+0x26 > kdb_backtrace(c0c1458c,0,c4521728,c4526730,c4179968,...) at > kdb_backtrace+0x29 > _witness_debugger(c0bf3680,c4911ad0,c0be6d88,c4526730,c0bfa429,...) at > _witness_debugger+0x25 > witness_checkorder(c4911ad0,1,c0bfa429,817,0,...) at > witness_checkorder +0x839 > __lockmgr_args(c4911ad0,200501,c4911aec,0,0,...) at > __lockmgr_args+0x237 > ffs_lock(c4179a78,c087a25b,c0c1697a,200501,c4911a78,...) at ffs_lock > +0x8a VOP_LOCK1_APV(c0cf7ca0,c4179a78,c4567e24,c0d0bdc0,c4911a78,...) > at VOP_LOCK1_APV+0xb5 > _vn_lock(c4911a78,200501,c0bfa429,817,4,...) at _vn_lock+0x5e > vget(c4911a78,200501,c4567d80,4b4,0,...) at vget+0xc9 > vnode_pager_lock(c187c1f0,0,c0c13f07,127,c4179c18,...) at > vnode_pager_lock+0x1e0 > vm_fault(c456b000,80db000,2,8,80db620,...) at vm_fault+0x1df > trap_pfault(5,0,c0c241d1,2e7,c4565d34,...) at trap_pfault+0x118 > trap(c4179d38) at trap+0x289 > calltrap() at calltrap+0x6 > --- trap 0xc, eip = 0x80480e5, esp = 0xbfbfeef0, ebp = 0xbfbfef10 --- Hi, I have similar LORs. One of them might be affecting Gnome2. I cannot even save anything once the LOR happened. nautilus is also hanging around. I cannot even kill it. This occurs since I migrated my /usr/home to ZFS (see fourth, fifth LoR). Here one like yours: lock order reversal: 1st 0xffffff0002402070 user map (user map) @ /usr/src/sys/vm/vm_map.c:3198 2nd 0xffffff0002b8a7f8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2071 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x81e __lockmgr_args() at __lockmgr_args+0xca8 ffs_lock() at ffs_lock+0x8c VOP_LOCK1_APV() at VOP_LOCK1_APV+0x9b _vn_lock() at _vn_lock+0x47 vget() at vget+0x8b vnode_pager_lock() at vnode_pager_lock+0x1d0 vm_fault() at vm_fault+0x1e2 trap_pfault() at trap_pfault+0x128 trap() at trap+0x51c calltrap() at calltrap+0x8 --- trap 0xc, rip = 0x40014f, rsp = 0x7fffffffee70, rbp = 0x7fffffffee90 --- Here a second one: lock order reversal: 1st 0xfffffffe803eb610 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2443 2nd 0xffffff00080d2000 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:275 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x81e _sx_xlock() at _sx_xlock+0x55 ufsdirhash_acquire() at ufsdirhash_acquire+0x33 ufsdirhash_add() at ufsdirhash_add+0x19 ufs_direnter() at ufs_direnter+0x88b ufs_mkdir() at ufs_mkdir+0x633 VOP_MKDIR_APV() at VOP_MKDIR_APV+0x93 kern_mkdirat() at kern_mkdirat+0x2b1 syscall() at syscall+0x1bf Xfast_syscall() at Xfast_syscall+0xab --- syscall (136, FreeBSD ELF64, mkdir), rip = 0x800719e9c, rsp = 0x7fffffffed08, rbp = 0x7fffffffef76 --- Here the third: lock order reversal: 1st 0xffffff0008648248 filedesc structure (filedesc structure) @ /usr/src/sys/kern/kern_descrip.c:1076 2nd 0xffffff0019110ba8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:4057 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x81e __lockmgr_args() at __lockmgr_args+0xc2a ffs_lock() at ffs_lock+0x8c VOP_LOCK1_APV() at VOP_LOCK1_APV+0x9b _vn_lock() at _vn_lock+0x47 knlist_remove_kq() at knlist_remove_kq+0x73 knote_fdclose() at knote_fdclose+0x177 kern_close() at kern_close+0xe6 syscall() at syscall+0x1bf Xfast_syscall() at Xfast_syscall+0xab --- syscall (6, FreeBSD ELF64, close), rip = 0x800e35e8c, rsp = 0x7fffffffe678, rbp = 0x801063a00 --- And thes two are really nasty (ZFS): lock order reversal: 1st 0xffffff00195ed620 zfs (zfs) @ /usr/src/sys/kern/vfs_vnops.c:531 2nd 0xffffff00080ab360 user map (user map) @ /usr/src/sys/vm/vm_map.c:3198 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x81e _sx_slock() at _sx_slock+0x55 vm_map_lookup() at vm_map_lookup+0x47 vm_fault() at vm_fault+0xfe trap_pfault() at trap_pfault+0x128 trap() at trap+0x347 calltrap() at calltrap+0x8 --- trap 0xc, rip = 0xffffffff8081ed4b, rsp = 0xfffffffe97261850, rbp = 0xfffffffe972618d0 --- copyout() at copyout+0x3b dmu_read_uio() at dmu_read_uio+0x98 zfs_freebsd_read() at zfs_freebsd_read+0x56d vn_read() at vn_read+0x267 dofileread() at dofileread+0xa1 kern_readv() at kern_readv+0x60 read() at read+0x54 syscall() at syscall+0x1bf Xfast_syscall() at Xfast_syscall+0xab --- syscall (3, FreeBSD ELF64, read), rip = 0x80647becc, rsp = 0x7ffffffed8c8, rbp = 0x806682f80 --- lock order reversal: 1st 0xffffff0019bc2270 zfs (zfs) @ /usr/src/sys/kern/vfs_subr.c:2071 2nd 0xffffff0019a77448 filedesc structure (filedesc structure) @ /usr/src/sys/kern/vfs_syscalls.c:1720 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x81e _sx_slock() at _sx_slock+0x55 kern_symlinkat() at kern_symlinkat+0x1f8 syscall() at syscall+0x1bf Xfast_syscall() at Xfast_syscall+0xab --- syscall (57, FreeBSD ELF64, symlink), rip = 0x8049cb13c, rsp = 0x7fffffffd6f8, rbp = 0x7fffffffdd10 --- And one with NFS: lock order reversal: 1st 0xffffff00080a6940 user map (user map) @ /usr/src/sys/vm/vm_map.c:3198 2nd 0xffffff00566a9ba8 nfs (nfs) @ /usr/src/sys/kern/vfs_subr.c:2071 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x81e __lockmgr_args() at __lockmgr_args+0xca8 vop_stdlock() at vop_stdlock+0x39 VOP_LOCK1_APV() at VOP_LOCK1_APV+0x9b _vn_lock() at _vn_lock+0x47 vget() at vget+0x8b vnode_pager_lock() at vnode_pager_lock+0x1d0 vm_fault() at vm_fault+0x1e2 trap_pfault() at trap_pfault+0x128 trap() at trap+0x347 calltrap() at calltrap+0x8 --- trap 0xc, rip = 0xffffffff8081edcd, rsp = 0xfffffffe972b67d0, rbp = 0xfffffffe972b6850 --- copyin() at copyin+0x3d ffs_write() at ffs_write+0x2f8 VOP_WRITE_APV() at VOP_WRITE_APV+0xfe vn_write() at vn_write+0x23f dofilewrite() at dofilewrite+0x85 kern_writev() at kern_writev+0x60 write() at write+0x54 syscall() at syscall+0x1bf Xfast_syscall() at Xfast_syscall+0xab --- syscall (4, FreeBSD ELF64, write), rip = 0x80072beac, rsp = 0x7fffffffe5d8, rbp = 0x800537000 --- Can you beat my 6 LoRs? ;) FreeBSD zelda.local 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Thu Jan 29 22:15:16 CET 2009 root@zelda.local:/usr/obj/usr/src/sys/ZELDA amd64 -- Martin From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 22:41:48 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D6C610657BB for ; Thu, 29 Jan 2009 22:41:48 +0000 (UTC) (envelope-from cryx-freebsd@h3q.com) Received: from mail.h3q.com (mail.h3q.com [213.73.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id 92D4A8FC1E for ; Thu, 29 Jan 2009 22:41:47 +0000 (UTC) (envelope-from cryx-freebsd@h3q.com) Received: (qmail 33060 invoked from network); 29 Jan 2009 22:41:46 -0000 Received: from unknown (HELO goa.local) (smtpsend@85.179.24.35) by mail.h3q.com with AES256-SHA encrypted SMTP; 29 Jan 2009 22:41:46 -0000 Message-ID: <498230AA.8080803@h3q.com> Date: Thu, 29 Jan 2009 23:41:46 +0100 From: Philipp Wuensche User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: das@FreeBSD.ORG References: <4981EBC6.1000907@h3q.com> <20090129215720.GA2889@zim.MIT.EDU> In-Reply-To: <20090129215720.GA2889@zim.MIT.EDU> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.ORG Subject: Re: Solaris live upgrade like FreeBSD ZFS-rootfs 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: Thu, 29 Jan 2009 22:41:49 -0000 David Schultz wrote: > > But since both ZFS and UFS support snapshots now, it would be > great if the process were something like: > > - drop to single user mode > - take snapshots of / and /usr > - install everything > - reboot > > But if something goes wrong, only ZFS has the ability to roll back > to the last snapshot, and even then I'm not sure if you can > actually boot from that snapshot in order to recover. You can't boot from a snapshot, but you can boot off a cloned filesystem and that is more or less what this script does. - It creates a snapshot of your known-good root-filesystem - It clones this snapshot into a new root-filesystem (requiring no additional disc-space!) which you then update to the new freebsd version - It configures the zpool to boot from the new root-filesystem The known-good root-filesystem is not touched in any way and in case anything goes wrong you can still boot from it. As of now we can't select a root-filesystem in the loader to load kernel and userland from, so it still involves two reboots to be able to go back to the known-good root-filesystem without getting stuck in a broken kernel or userland. This is due to the fact that the loader currently blindly loads the kernel from the root-filesystem configured in the zpool bootfs property and if this kernel is broken or the userland you would boot from this filesystem is damaged, you are screwed as you are not able to set the bootfs property back to the known-good root-filesystem. If we could select a root-filesystem in the loader it would be down to one reboot without any drop to single-user or risk getting stuck in an unusable system. greetings, Philipp From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 22:49:13 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB9F8106566C for ; Thu, 29 Jan 2009 22:49:13 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from keltia.freenix.fr (keltia.freenix.org [IPv6:2001:660:330f:f820:213:72ff:fe15:f44]) by mx1.freebsd.org (Postfix) with ESMTP id 6A41B8FC12 for ; Thu, 29 Jan 2009 22:49:13 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from localhost (localhost [127.0.0.1]) by keltia.freenix.fr (Postfix/TLS) with ESMTP id 555963BC0D; Thu, 29 Jan 2009 23:49:12 +0100 (CET) X-Virus-Scanned: amavisd-new at keltia.freenix.fr Received: from keltia.freenix.fr ([127.0.0.1]) by localhost (keltia.freenix.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l4SD6RcbzksF; Thu, 29 Jan 2009 23:49:12 +0100 (CET) Received: by keltia.freenix.fr (Postfix/TLS, from userid 101) id EFCBE3BC0B; Thu, 29 Jan 2009 23:49:11 +0100 (CET) Date: Thu, 29 Jan 2009 23:49:11 +0100 From: Ollivier Robert To: freebsd-current@freebsd.org Message-ID: <20090129224911.GA23573@keltia.freenix.fr> References: <4981EBC6.1000907@h3q.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4981EBC6.1000907@h3q.com> X-Operating-System: MacOS X / Macbook Pro - FreeBSD 7 / Dell D820 SMP User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Philipp Wuensche Subject: Re: Solaris live upgrade like FreeBSD ZFS-rootfs 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: Thu, 29 Jan 2009 22:49:14 -0000 According to Philipp Wuensche: > I'm playing a lot with ZFS root filesystems for FreeBSD and using > zfsboot with GPT. So far it works perfecly for me on three not-so > production servers and I would like to thank everybody that helped make > this work! Excellent, care to submit an entry for the FreeBSD wiki explining all the steps you took? :) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr Dons / donation Ondine : http://ondine.keltia.net/ From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 22:58:46 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4A851065672 for ; Thu, 29 Jan 2009 22:58:46 +0000 (UTC) (envelope-from cryx-freebsd@h3q.com) Received: from mail.h3q.com (mail.h3q.com [213.73.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id DC2DA8FC29 for ; Thu, 29 Jan 2009 22:58:45 +0000 (UTC) (envelope-from cryx-freebsd@h3q.com) Received: (qmail 36690 invoked from network); 29 Jan 2009 22:58:44 -0000 Received: from unknown (HELO goa.local) (smtpsend@85.179.24.35) by mail.h3q.com with AES256-SHA encrypted SMTP; 29 Jan 2009 22:58:44 -0000 Message-ID: <498234A4.6040102@h3q.com> Date: Thu, 29 Jan 2009 23:58:44 +0100 From: Philipp Wuensche User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Ollivier Robert References: <4981EBC6.1000907@h3q.com> <20090129224911.GA23573@keltia.freenix.fr> In-Reply-To: <20090129224911.GA23573@keltia.freenix.fr> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Solaris live upgrade like FreeBSD ZFS-rootfs 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: Thu, 29 Jan 2009 22:58:52 -0000 Ollivier Robert wrote: > According to Philipp Wuensche: >> I'm playing a lot with ZFS root filesystems for FreeBSD and using >> zfsboot with GPT. So far it works perfecly for me on three not-so >> production servers and I would like to thank everybody that helped make >> this work! > > Excellent, care to submit an entry for the FreeBSD wiki explining all the > steps you took? :) Sure, all the stuff is on the net already but a complete run-down maybe would be helpful to get more people into using ZFS :-) I guess I will write something up in the next days. greetings, Philipp From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 00:10:11 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95B9C106566B for ; Fri, 30 Jan 2009 00:10:11 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from warped.bluecherry.net (unknown [IPv6:2001:440:eeee:fffb::2]) by mx1.freebsd.org (Postfix) with ESMTP id 318D48FC08 for ; Fri, 30 Jan 2009 00:10:11 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (morganw-1-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:47e::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by warped.bluecherry.net (Postfix) with ESMTPSA id 0B99AA1CAF6F; Thu, 29 Jan 2009 18:10:09 -0600 (CST) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id n0U0A2jP059087; Thu, 29 Jan 2009 18:10:04 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Thu, 29 Jan 2009 18:10:02 -0600 (CST) From: Wes Morgan To: Nenhum_de_Nos In-Reply-To: <191beebcb8e400a659afaa9d997462c0.squirrel@lamneth> Message-ID: References: <20490.74948.qm@web63901.mail.re1.yahoo.com> <200901291219.17379.doconnor@gsoft.com.au> <191beebcb8e400a659afaa9d997462c0.squirrel@lamneth> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: SATA drive device moving on 8.0 current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2009 00:10:11 -0000 On Thu, 29 Jan 2009, Nenhum_de_Nos wrote: > > On Wed, January 28, 2009 23:48, Daniel O'Connor wrote: >> On Thursday 29 January 2009 03:48:11 Barney Cordoba wrote: >>> I booted 8.0-current on a machine that was running 7 and the SATA drive >>> came up as ad4 instead of ad8 (as it is detected in 7). This is the case >>> was loading GENERIC. >>> >>> This is going to present a serious problem doing field upgrades as its >>> expected that fstab will be the same. What is the reason for the change >>> and >>> is there any way to make it compatible with device detection in 7? >> >> I don't know how you can change it back, but you can use glabel and tunefs >> -L >> and then modify /etc/fstab to use /dev/ufs/foo. > > even / can use this ? > just current has this feature ? Did you, by any chance, remove ATA_STATIC_ID from your kernel config? From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 01:14:15 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1E1E106564A for ; Fri, 30 Jan 2009 01:14:15 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from nskntmtas04p.mx.bigpond.com (nskntmtas04p.mx.bigpond.com [61.9.168.146]) by mx1.freebsd.org (Postfix) with ESMTP id 65F308FC0A for ; Fri, 30 Jan 2009 01:14:15 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from nskntotgx02p.mx.bigpond.com ([124.188.162.219]) by nskntmtas04p.mx.bigpond.com with ESMTP id <20090130011413.IGSL1877.nskntmtas04p.mx.bigpond.com@nskntotgx02p.mx.bigpond.com> for ; Fri, 30 Jan 2009 01:14:13 +0000 Received: from areilly.bpa.nu ([124.188.162.219]) by nskntotgx02p.mx.bigpond.com with ESMTP id <20090130011409.HCRE12531.nskntotgx02p.mx.bigpond.com@areilly.bpa.nu> for ; Fri, 30 Jan 2009 01:14:09 +0000 Received: (qmail 86814 invoked by uid 501); 30 Jan 2009 01:13:52 -0000 Date: Fri, 30 Jan 2009 12:13:52 +1100 From: Andrew Reilly To: Garance A Drosihn Message-ID: <20090130011352.GA85741@duncan.reilly.home> References: <20090128155340.GA75143@lpthe.jussieu.fr> <7508A5B5-C6D2-498A-AEA1-D84E85F1D743@mac.com> <200901291243.00378.doconnor@gsoft.com.au> <49811242.7030106@delphij.net> <498116AB.2060105@gmail.com> <49816854.9060909@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150201.49825461.0036,ss=1,fgs=0 Cc: Christoph Mallon , freebsd-current@freebsd.org Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jan 2009 01:14:16 -0000 On Thu, Jan 29, 2009 at 03:26:29PM -0500, Garance A Drosihn wrote: > At 9:27 AM +0100 1/29/09, Christoph Mallon wrote: > >Eitan Adler schrieb: > >>To quote from the FAQ: > >>Who does this change affect? > >> Nobody who is currently using GCC should be affected by this change. > > > >Let me repeat that: > >"Nobody who is currently using GCC *should* be affected by this change." > > > >Emphasize mine. > > There have been a couple of different issues brought up in this thread, > and I've lost track of which one we're on. But one of the issues is > the use of LLVM+gcc, and my guess is that the above statement would not > apply to that. That is just my guess, of course. It seems to me that LLVM+gcc is precicely the condition that the GCC maintainers are attempting to prevent with the GPLv3 version of the libgcc exception. It almost certainly doesn't constitute an "Eligible Compilation Process". They've historically refused to break out a useful intermediate (parse tree or RTL) form explicitly so that gcc couldn't be used as a convenient front end for a proprietary code generator. But, on the other hand, they didn't seem to mind adding the pico-java back-end, which is much the same idea, so perhaps this speculation is totally wrong. In that case I have no idea what use case they're so keen to prevent. Cheers, Andrew From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 02:07:42 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1773D1065670 for ; Fri, 30 Jan 2009 02:07:42 +0000 (UTC) (envelope-from chris@young-alumni.com) Received: from mail.oldschoolpunx.net (cpe-72-177-10-243.austin.res.rr.com [72.177.10.243]) by mx1.freebsd.org (Postfix) with ESMTP id D5DEE8FC08 for ; Fri, 30 Jan 2009 02:07:41 +0000 (UTC) (envelope-from chris@young-alumni.com) Received: by mail.oldschoolpunx.net (Postfix, from userid 58) id BD90C8B478; Thu, 29 Jan 2009 19:51:41 -0600 (CST) Received: from [192.168.8.199] (unknown [192.168.8.199]) by mail.oldschoolpunx.net (Postfix) with ESMTPSA id 4FB918B459 for ; Thu, 29 Jan 2009 19:47:47 -0600 (CST) Message-Id: <03037737-0CFE-4DA1-8952-2CEED059EC98@young-alumni.com> From: Chris Ruiz To: freebsd-current@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Thu, 29 Jan 2009 19:47:46 -0600 X-Mailer: Apple Mail (2.930.3) Subject: uhub_reattach_port:413: could not allocate new device! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jan 2009 02:07:42 -0000 I've stumbled across another problem with usb2 recently that seems to be a regression. In the past with usb2 I was able to plug in flash drives after boot and they would successfully attach, now that is no longer the case. I boot from a usb flash drive that is mounted as / dev/da0s1a and I have no problems accessing it. error message: Jan 29 19:34:38 attack kernel: usb2_alloc_device:1436: getting device descriptor at addr 3 failed! Jan 29 19:34:39 attack kernel: usb2_pc_common_mem_cb:429: Page offset was not preserved! Jan 29 19:34:39 attack kernel: usb2_req_re_enumerate:1366: addr=3, set address failed! (ignored) Jan 29 19:34:39 attack kernel: usb2_pc_common_mem_cb:429: Page offset was not preserved! Jan 29 19:34:39 attack kernel: usb2_req_re_enumerate:1379: getting device descriptor at addr 3 failed! Jan 29 19:34:40 attack kernel: usb2_pc_common_mem_cb:429: Page offset was not preserved! Jan 29 19:34:40 attack kernel: usb2_req_re_enumerate:1379: getting device descriptor at addr 3 failed! Jan 29 19:34:40 attack kernel: ugen3.3: <> at usbus3 (disconnected) Jan 29 19:34:40 attack kernel: uhub_reattach_port:413: could not allocate new device! kernel: FreeBSD attack.young-alumni.com 8.0-CURRENT FreeBSD 8.0-CURRENT #0 r187791M: Tue Jan 27 13:09:13 CST 2009 root@:/usr/obj/usr/src/sys/ FAILWHALE amd64 Thanks, Chris Ruiz From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 06:48:42 2009 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 47F971065673 for ; Fri, 30 Jan 2009 06:48:42 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 73ADE8FC0C for ; Fri, 30 Jan 2009 06:48:41 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.123.2.23] (h-66-166-149-52.snvacaid.covad.net [66.166.149.52]) by kientzle.com (8.12.9/8.12.9) with ESMTP id n0U6PFC1038675 for ; Thu, 29 Jan 2009 22:25:26 -0800 (PST) (envelope-from kientzle@freebsd.org) Message-ID: <49829D49.10306@freebsd.org> Date: Thu, 29 Jan 2009 22:25:13 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "'current@FreeBSD.org'" Content-Type: multipart/mixed; boundary="------------040708020804040103060208" Cc: Subject: RFC: Change mtree nsec handling? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jan 2009 06:48:42 -0000 This is a multi-part message in MIME format. --------------040708020804040103060208 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit In looking at interoperability between libarchive's mtree support and the mtree(8) program, I found that mtree formats timestamps rather strangely. For example, a timestamp of 1233295862.000001 (1233295682 seconds and 1000 nanoseconds) will be printed like this by mtree: time=1233295862.1000 Unsurprisingly, the mtree parsing works the same way in reverse. Basically, mtree is printing (and reading) the time as whole seconds and nanoseconds separated by a period, which 90% of the time is the same as a decimal floating-point number of seconds, but not the other 10% of the time. This is not documented in mtree.8. I was quite surprised by it. The attached patch changes this to use a more conventional notation (although the patch could use a little more tweaking to handle >9 digits after the decimal point). Any concerns about this? Tim --------------040708020804040103060208 Content-Type: text/x-patch; name="mtree_nsec.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="mtree_nsec.patch" Index: create.c =================================================================== --- create.c (revision 187909) +++ create.c (working copy) @@ -212,7 +212,7 @@ output(indent, &offset, "size=%jd", (intmax_t)p->fts_statp->st_size); if (keys & F_TIME) - output(indent, &offset, "time=%ld.%ld", + output(indent, &offset, "time=%ld.%09ld", (long)p->fts_statp->st_mtimespec.tv_sec, p->fts_statp->st_mtimespec.tv_nsec); if (keys & F_CKSUM && S_ISREG(p->fts_statp->st_mode)) { Index: spec.c =================================================================== --- spec.c (revision 187910) +++ spec.c (working copy) @@ -172,6 +172,7 @@ mode_t *m; int value; char *ep; + int i; for (; (kw = strtok(t, "= \t\n")); t = NULL) { ip->flags |= type = parsekey(kw, &value); @@ -258,6 +259,8 @@ val = ep + 1; ip->st_mtimespec.tv_nsec = strtoul(val, &ep, 10); + for (i = ep - val; i < 9; ++i) + ip->st_mtimespec.tv_nsec *= 10; } else ip->st_mtimespec.tv_nsec = 0; if (*ep) --------------040708020804040103060208-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 09:42:01 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E9ED1065675 for ; Fri, 30 Jan 2009 09:42:01 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.swip.net [212.247.154.161]) by mx1.freebsd.org (Postfix) with ESMTP id E7ECD8FC1C for ; Fri, 30 Jan 2009 09:42:00 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=ajV_e_qu9Q8A:10 a=pkpoxy8g4UkA:10 a=6I5d2MoRAAAA:8 a=T8IKFdjkN0As-C2j8CwA:9 a=JCo5qOJds8I5FFw8SqopT732cSsA:4 a=LY0hPdMaydYA:10 Received: from [85.19.218.115] (account mc467741@c2i.net HELO [10.37.1.92]) by mailfe06.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 1189018657; Fri, 30 Jan 2009 10:41:58 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Fri, 30 Jan 2009 10:44:21 +0100 User-Agent: KMail/1.9.7 References: <03037737-0CFE-4DA1-8952-2CEED059EC98@young-alumni.com> In-Reply-To: <03037737-0CFE-4DA1-8952-2CEED059EC98@young-alumni.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200901301044.22545.hselasky@c2i.net> Cc: Chris Ruiz Subject: Re: uhub_reattach_port:413: could not allocate new device! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jan 2009 09:42:01 -0000 On Friday 30 January 2009, Chris Ruiz wrote: > Jan 29 19:34:39 attack kernel: usb2_pc_common_mem_cb:429: Page offset =A0 > was not preserved! Hi, =46irst of all thanks for reporting! The issue you are experiencing is a known problem with busdma, because you = are=20 using a 64-bit platform. See "http://wiki.freebsd.org/USB" for a resolution. =2D-HPS From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 09:44:07 2009 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 C65AB10656F6 for ; Fri, 30 Jan 2009 09:44:07 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk1.360sip.com [72.236.70.240]) by mx1.freebsd.org (Postfix) with ESMTP id 8C4498FC2F for ; Fri, 30 Jan 2009 09:44:07 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from [192.168.1.38] (S0106001372fd1e07.vs.shawcable.net [70.71.171.106]) (authenticated bits=0) by sippysoft.com (8.13.8/8.13.8) with ESMTP id n0U9i5CA002072 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Jan 2009 01:44:06 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Message-ID: <4982CBC7.5050102@FreeBSD.org> Date: Fri, 30 Jan 2009 01:43:35 -0800 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Tim Kientzle References: <49829D49.10306@freebsd.org> In-Reply-To: <49829D49.10306@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "'current@FreeBSD.org'" Subject: Re: RFC: Change mtree nsec handling? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jan 2009 09:44:10 -0000 Tim Kientzle wrote: > In looking at interoperability between libarchive's > mtree support and the mtree(8) program, I found > that mtree formats timestamps rather strangely. > > For example, a timestamp of 1233295862.000001 > (1233295682 seconds and 1000 nanoseconds) > will be printed like this by mtree: > time=1233295862.1000 > Unsurprisingly, the mtree parsing works the same > way in reverse. > > Basically, mtree is printing (and reading) the time > as whole seconds and nanoseconds separated by a period, > which 90% of the time is the same as a decimal > floating-point number of seconds, but not the other > 10% of the time. This is not documented in mtree.8. > I was quite surprised by it. > > The attached patch changes this to use a more conventional > notation (although the patch could use a little more tweaking > to handle >9 digits after the decimal point). > > Any concerns about this? Given the age of mtree(8) I guess there are lot of existing mtree specs out there who rely on this behavior. Therefore, IMHO the right thing to do would be either note this in the documentation and let it be, or mark "time" keyword as depreciated and add some new keyword for example "timestamp". The new keyword will be generated by default by mtree(8) instead of "time" and will do the right thing. Then, in few years from now "time" could be deorbited. -Maxim From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 10:10:15 2009 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 CBF651065672; Fri, 30 Jan 2009 10:10:15 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 7FE2D8FC16; Fri, 30 Jan 2009 10:10:15 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id 6BE923F129; Fri, 30 Jan 2009 10:10:14 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.3/8.14.3) with ESMTP id n0UAAEkn030969; Fri, 30 Jan 2009 10:10:14 GMT (envelope-from phk@critter.freebsd.dk) To: Tim Kientzle From: "Poul-Henning Kamp" In-Reply-To: Your message of "Thu, 29 Jan 2009 22:25:13 PST." <49829D49.10306@freebsd.org> Date: Fri, 30 Jan 2009 10:10:14 +0000 Message-ID: <30968.1233310214@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: "'current@FreeBSD.org'" Subject: Re: RFC: Change mtree nsec handling? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jan 2009 10:10:16 -0000 In message <49829D49.10306@freebsd.org>, Tim Kientzle writes: >mtree support and the mtree(8) program, I found >that mtree formats timestamps rather strangely. > >For example, a timestamp of 1233295862.000001 >(1233295682 seconds and 1000 nanoseconds) >will be printed like this by mtree: > time=1233295862.1000 >Unsurprisingly, the mtree parsing works the same >way in reverse. >Index: spec.c >=================================================================== >--- spec.c (revision 187910) >+++ spec.c (working copy) >@@ -172,6 +172,7 @@ > mode_t *m; > int value; > char *ep; >+ int i; > > for (; (kw = strtok(t, "= \t\n")); t = NULL) { > ip->flags |= type = parsekey(kw, &value); >@@ -258,6 +259,8 @@ > val = ep + 1; > ip->st_mtimespec.tv_nsec > = strtoul(val, &ep, 10); >+ for (i = ep - val; i < 9; ++i) >+ ip->st_mtimespec.tv_nsec *= 10; Why is this bit needed ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 10:10:48 2009 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 013441065679; Fri, 30 Jan 2009 10:10:48 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id B697A8FC0A; Fri, 30 Jan 2009 10:10:47 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id E6B803F130; Fri, 30 Jan 2009 10:10:46 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.3/8.14.3) with ESMTP id n0UAAkbu030974; Fri, 30 Jan 2009 10:10:46 GMT (envelope-from phk@critter.freebsd.dk) To: Maxim Sobolev From: "Poul-Henning Kamp" In-Reply-To: Your message of "Fri, 30 Jan 2009 01:43:35 PST." <4982CBC7.5050102@FreeBSD.org> Date: Fri, 30 Jan 2009 10:10:46 +0000 Message-ID: <30973.1233310246@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Tim Kientzle , "'current@FreeBSD.org'" Subject: Re: RFC: Change mtree nsec handling? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jan 2009 10:10:48 -0000 In message <4982CBC7.5050102@FreeBSD.org>, Maxim Sobolev writes: >Tim Kientzle wrote: >> Any concerns about this? > >Given the age of mtree(8) I guess there are lot of existing mtree specs >out there who rely on this behavior. Therefore, IMHO the right thing to >do would be either note this in the documentation and let it be, or mark >"time" keyword as depreciated and add some new keyword for example >"timestamp". The new keyword will be generated by default by mtree(8) >instead of "time" and will do the right thing. Then, in few years from >now "time" could be deorbited. This is way overkill. We are not in the business of rococo decoration. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 11:23:10 2009 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 BB8251065672; Fri, 30 Jan 2009 11:23:10 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail14.syd.optusnet.com.au (mail14.syd.optusnet.com.au [211.29.132.195]) by mx1.freebsd.org (Postfix) with ESMTP id 4E00F8FC12; Fri, 30 Jan 2009 11:23:10 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-216-167.belrs3.nsw.optusnet.com.au [122.106.216.167]) by mail14.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n0UBN7Rw024704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Jan 2009 22:23:08 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id n0UBN7AZ064869; Fri, 30 Jan 2009 22:23:07 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id n0UBN729064868; Fri, 30 Jan 2009 22:23:07 +1100 (EST) (envelope-from peter) Date: Fri, 30 Jan 2009 22:23:07 +1100 From: Peter Jeremy To: Maxim Sobolev Message-ID: <20090130112307.GJ1755@server.vk2pj.dyndns.org> References: <49829D49.10306@freebsd.org> <4982CBC7.5050102@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="eNMatiwYGLtwo1cJ" Content-Disposition: inline In-Reply-To: <4982CBC7.5050102@FreeBSD.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Tim Kientzle , "'current@FreeBSD.org'" Subject: Re: RFC: Change mtree nsec handling? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jan 2009 11:23:11 -0000 --eNMatiwYGLtwo1cJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2009-Jan-30 01:43:35 -0800, Maxim Sobolev wrote: >Tim Kientzle wrote: >> For example, a timestamp of 1233295862.000001 >> (1233295682 seconds and 1000 nanoseconds) >> will be printed like this by mtree: >> time=3D1233295862.1000 >> Unsurprisingly, the mtree parsing works the same >> way in reverse. > >Given the age of mtree(8) I guess there are lot of existing mtree specs=20 >out there who rely on this behavior. The existing code to read nanoseconds will handle either the old format or a %09d format (the for() loop that Tim added is unnecessary) so existing specs won't have a problem. I think adding leading zeroes is the correct way to proceed. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --eNMatiwYGLtwo1cJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmC4xsACgkQ/opHv/APuIcABgCfTqyAKRapbqC3vxs+e+pkDEQN /Q8AoIbHHBx0qL5Cfo8saFjvRD464XVO =4WKO -----END PGP SIGNATURE----- --eNMatiwYGLtwo1cJ-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 11:38:33 2009 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 3D0011065674; Fri, 30 Jan 2009 11:38:33 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk1.360sip.com [72.236.70.240]) by mx1.freebsd.org (Postfix) with ESMTP id 04FD28FC1F; Fri, 30 Jan 2009 11:38:32 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from [192.168.1.38] (S0106001372fd1e07.vs.shawcable.net [70.71.171.106]) (authenticated bits=0) by sippysoft.com (8.13.8/8.13.8) with ESMTP id n0UBcV5v008194 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Jan 2009 03:38:32 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Message-ID: <4982E698.1090204@FreeBSD.org> Date: Fri, 30 Jan 2009 03:38:00 -0800 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Peter Jeremy References: <49829D49.10306@freebsd.org> <4982CBC7.5050102@FreeBSD.org> <20090130112307.GJ1755@server.vk2pj.dyndns.org> In-Reply-To: <20090130112307.GJ1755@server.vk2pj.dyndns.org> Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit Cc: Tim Kientzle , "'current@FreeBSD.org'" Subject: Re: RFC: Change mtree nsec handling? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jan 2009 11:38:33 -0000 Peter Jeremy wrote: > On 2009-Jan-30 01:43:35 -0800, Maxim Sobolev wrote: >> Tim Kientzle wrote: >>> For example, a timestamp of 1233295862.000001 >>> (1233295682 seconds and 1000 nanoseconds) >>> will be printed like this by mtree: >>> time=1233295862.1000 >>> Unsurprisingly, the mtree parsing works the same >>> way in reverse. >> Given the age of mtree(8) I guess there are lot of existing mtree specs >> out there who rely on this behavior. > > The existing code to read nanoseconds will handle either the old > format or a %09d format (the for() loop that Tim added is unnecessary) > so existing specs won't have a problem. I think adding leading zeroes > is the correct way to proceed. My point is that it would not restore correct timestamp, not that it would not read it. The 1233295862.000001 before change would become 1233295862.1000 after. I don't know how important is it, but I can imagine some applications where it could be an issue (e.g. incremental backup). -Maxim From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 12:18:19 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EAF14106566B for ; Fri, 30 Jan 2009 12:18:18 +0000 (UTC) (envelope-from chris@young-alumni.com) Received: from mail.oldschoolpunx.net (cpe-72-177-10-243.austin.res.rr.com [72.177.10.243]) by mx1.freebsd.org (Postfix) with ESMTP id AE9108FC34 for ; Fri, 30 Jan 2009 12:18:18 +0000 (UTC) (envelope-from chris@young-alumni.com) Received: by mail.oldschoolpunx.net (Postfix, from userid 58) id E284F4B183; Fri, 30 Jan 2009 06:18:17 -0600 (CST) Received: from [192.168.8.199] (unknown [192.168.8.199]) by mail.oldschoolpunx.net (Postfix) with ESMTPSA id DB6B54B145; Fri, 30 Jan 2009 06:13:49 -0600 (CST) Message-Id: <85E9BD4B-553D-45F8-8E7F-C4E663C347E1@young-alumni.com> From: Chris Ruiz To: freebsd-current@freebsd.org In-Reply-To: <200901301044.22545.hselasky@c2i.net> Mime-Version: 1.0 (Apple Message framework v930.3) Date: Fri, 30 Jan 2009 06:13:49 -0600 References: <03037737-0CFE-4DA1-8952-2CEED059EC98@young-alumni.com> <200901301044.22545.hselasky@c2i.net> X-Mailer: Apple Mail (2.930.3) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Hans Petter Selasky Subject: Re: uhub_reattach_port:413: could not allocate new device! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jan 2009 12:18:19 -0000 On Jan 30, 2009, at 3:44 AM, Hans Petter Selasky wrote: > On Friday 30 January 2009, Chris Ruiz wrote: >> Jan 29 19:34:39 attack kernel: usb2_pc_common_mem_cb:429: Page offset >> was not preserved! > > Hi, > > First of all thanks for reporting! > > The issue you are experiencing is a known problem with busdma, > because you are > using a 64-bit platform. > > See "http://wiki.freebsd.org/USB" for a resolution. > I manually applied the changes to r187913 by hand (I don't know how to generate patches from p4) and have successfully tested them. -- new kernel: FreeBSD attack.young-alumni.com 8.0-CURRENT FreeBSD 8.0-CURRENT #0 r187913M: Fri Jan 30 05:35:09 CST 2009 root@attack.young- alumni.com:/usr/obj/usr/src/sys/FAILWHALE amd64 device messages: Jan 30 06:04:43 attack kernel: ugen3.3: at usbus3 Jan 30 06:04:43 attack kernel: umass1: on usbus3 Jan 30 06:04:43 attack kernel: umass1: SCSI over Bulk-Only; quirks = 0x0000 Jan 30 06:04:44 attack kernel: umass1:2:1:-1: Attached to scbus2 Jan 30 06:04:44 attack kernel: (probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Jan 30 06:04:44 attack kernel: (probe0:umass-sim1:1:0:0): CAM Status: SCSI Status Error Jan 30 06:04:44 attack kernel: (probe0:umass-sim1:1:0:0): SCSI Status: Check Condition Jan 30 06:04:44 attack kernel: (probe0:umass-sim1:1:0:0): UNIT ATTENTION asc:28,0 Jan 30 06:04:44 attack kernel: (probe0:umass-sim1:1:0:0): Not ready to ready change, medium may have changed Jan 30 06:04:44 attack kernel: (probe0:umass-sim1:1:0:0): Retrying Command (per Sense Data) Jan 30 06:04:44 attack kernel: da1 at umass-sim1 bus 1 target 0 lun 0 Jan 30 06:04:44 attack kernel: da1: Removable Direct Access SCSI-0 device Jan 30 06:04:44 attack kernel: da1: 40.000MB/s transfers Jan 30 06:04:44 attack kernel: da1: 7743MB (15858688 512 byte sectors: 255H 63S/T 987C) Jan 30 06:04:45 attack kernel: GEOM_LABEL: Label for provider da1p1 is msdosfs/EFI. Jan 30 06:04:50 attack kernel: umass1: at ushub3, port 4, addr 3 (disconnected) Jan 30 06:04:50 attack kernel: (da1:umass-sim1:1:0:0): lost device Jan 30 06:04:50 attack kernel: (da1:umass-sim1:1:0:0): removing device entry Jan 30 06:04:50 attack kernel: ugen3.3: at usbus3 (disconnected) Jan 30 06:04:50 attack kernel: GEOM_LABEL: Label msdosfs/EFI removed. Jan 30 06:05:01 attack kernel: ugen3.4: at usbus3 Jan 30 06:05:01 attack kernel: umass2: on usbus3 Jan 30 06:05:01 attack kernel: umass2: SCSI over Bulk-Only; quirks = 0x0000 Jan 30 06:05:03 attack kernel: umass2:3:2:-1: Attached to scbus3 Jan 30 06:05:03 attack kernel: da2 at umass-sim2 bus 2 target 0 lun 0 Jan 30 06:05:03 attack kernel: da2: Removable Direct Access SCSI-2 device Jan 30 06:05:03 attack kernel: da2: 40.000MB/s transfers Jan 30 06:05:03 attack kernel: da2: 122MB (250879 512 byte sectors: 64H 32S/T 122C) Jan 30 06:05:03 attack kernel: GEOM_LABEL: Label for provider da2s1a is ufs/usbboot. Jan 30 06:05:07 attack kernel: umass2: at ushub3, port 4, addr 4 (disconnected) Jan 30 06:05:07 attack kernel: (da2:umass-sim2:2:0:0): lost device Jan 30 06:05:07 attack kernel: (da2:umass-sim2:2:0:0): removing device entry Jan 30 06:05:07 attack kernel: ugen3.4: at usbus3 (disconnected) Jan 30 06:05:07 attack kernel: GEOM_LABEL: Label ufs/usbboot removed. -- I'll keep testing throughout the day to make sure there aren't any gremlins lurking about. Can this be committed soon if no problems come up? Thanks, Chris Ruiz > --HPS > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org > " From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 13:09:32 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A78D1065675 for ; Fri, 30 Jan 2009 13:09:32 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe11.swipnet.se [212.247.155.65]) by mx1.freebsd.org (Postfix) with ESMTP id 98AAB8FC0C for ; Fri, 30 Jan 2009 13:09:31 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=ajV_e_qu9Q8A:10 a=pkpoxy8g4UkA:10 a=6I5d2MoRAAAA:8 a=QrE0wPtG0yJGtEpY9ssA:9 a=up4Vsw_w_BQIfW8H5kEA:7 a=XQrXA7IinkL_aVV6baEzZ-NL9lkA:4 a=1X9tdw6F7KoA:10 a=LY0hPdMaydYA:10 Received: from [85.19.218.115] (account mc467741@c2i.net HELO [10.37.1.92]) by mailfe11.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 1016087579; Fri, 30 Jan 2009 14:09:29 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Fri, 30 Jan 2009 14:11:53 +0100 User-Agent: KMail/1.9.7 References: <03037737-0CFE-4DA1-8952-2CEED059EC98@young-alumni.com> <200901301044.22545.hselasky@c2i.net> <85E9BD4B-553D-45F8-8E7F-C4E663C347E1@young-alumni.com> In-Reply-To: <85E9BD4B-553D-45F8-8E7F-C4E663C347E1@young-alumni.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901301411.54973.hselasky@c2i.net> Cc: Chris Ruiz Subject: Re: uhub_reattach_port:413: could not allocate new device! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jan 2009 13:09:32 -0000 On Friday 30 January 2009, Chris Ruiz wrote: > On Jan 30, 2009, at 3:44 AM, Hans Petter Selasky wrote: > > On Friday 30 January 2009, Chris Ruiz wrote: > >> Jan 29 19:34:39 attack kernel: usb2_pc_common_mem_cb:429: Page offset > >> was not preserved! > > > > Hi, > > > > First of all thanks for reporting! > > > > The issue you are experiencing is a known problem with busdma, > > because you are > > using a 64-bit platform. > > > > See "http://wiki.freebsd.org/USB" for a resolution. > > I manually applied the changes to r187913 by hand (I don't know how to > generate patches from p4) and have successfully tested them. > > -- > > new kernel: > > FreeBSD attack.young-alumni.com 8.0-CURRENT FreeBSD 8.0-CURRENT #0 > r187913M: Fri Jan 30 05:35:09 CST 2009 root@attack.young- > alumni.com:/usr/obj/usr/src/sys/FAILWHALE amd64 > > device messages: > > Jan 30 06:04:43 attack kernel: ugen3.3: at usbus3 > Jan 30 06:04:43 attack kernel: umass1: class 0/0, rev > 2.00/11.00, addr 3> on usbus3 > Jan 30 06:04:43 attack kernel: umass1: SCSI over Bulk-Only; quirks = > 0x0000 > Jan 30 06:04:44 attack kernel: umass1:2:1:-1: Attached to scbus2 > Jan 30 06:04:44 attack kernel: (probe0:umass-sim1:1:0:0): TEST UNIT > READY. CDB: 0 0 0 0 0 0 > Jan 30 06:04:44 attack kernel: (probe0:umass-sim1:1:0:0): CAM Status: > SCSI Status Error > Jan 30 06:04:44 attack kernel: (probe0:umass-sim1:1:0:0): SCSI Status: > Check Condition > Jan 30 06:04:44 attack kernel: (probe0:umass-sim1:1:0:0): UNIT > ATTENTION asc:28,0 > Jan 30 06:04:44 attack kernel: (probe0:umass-sim1:1:0:0): Not ready to > ready change, medium may have changed > Jan 30 06:04:44 attack kernel: (probe0:umass-sim1:1:0:0): Retrying > Command (per Sense Data) > Jan 30 06:04:44 attack kernel: da1 at umass-sim1 bus 1 target 0 lun 0 > Jan 30 06:04:44 attack kernel: da1: Removable > Direct Access SCSI-0 device > Jan 30 06:04:44 attack kernel: da1: 40.000MB/s transfers > Jan 30 06:04:44 attack kernel: da1: 7743MB (15858688 512 byte sectors: > 255H 63S/T 987C) > Jan 30 06:04:45 attack kernel: GEOM_LABEL: Label for provider da1p1 is > msdosfs/EFI. > Jan 30 06:04:50 attack kernel: umass1: at ushub3, port 4, addr 3 > (disconnected) > Jan 30 06:04:50 attack kernel: (da1:umass-sim1:1:0:0): lost device > Jan 30 06:04:50 attack kernel: (da1:umass-sim1:1:0:0): removing device > entry > Jan 30 06:04:50 attack kernel: ugen3.3: at usbus3 > (disconnected) > Jan 30 06:04:50 attack kernel: GEOM_LABEL: Label msdosfs/EFI removed. > > Jan 30 06:05:01 attack kernel: ugen3.4: at usbus3 > Jan 30 06:05:01 attack kernel: umass2: Mini, class 0/0, rev 2.00/0.20, addr 4> on usbus3 > Jan 30 06:05:01 attack kernel: umass2: SCSI over Bulk-Only; quirks = > 0x0000 > Jan 30 06:05:03 attack kernel: umass2:3:2:-1: Attached to scbus3 > Jan 30 06:05:03 attack kernel: da2 at umass-sim2 bus 2 target 0 lun 0 > Jan 30 06:05:03 attack kernel: da2: > Removable Direct Access SCSI-2 device > Jan 30 06:05:03 attack kernel: da2: 40.000MB/s transfers > Jan 30 06:05:03 attack kernel: da2: 122MB (250879 512 byte sectors: > 64H 32S/T 122C) > Jan 30 06:05:03 attack kernel: GEOM_LABEL: Label for provider da2s1a > is ufs/usbboot. > Jan 30 06:05:07 attack kernel: umass2: at ushub3, port 4, addr 4 > (disconnected) > Jan 30 06:05:07 attack kernel: (da2:umass-sim2:2:0:0): lost device > Jan 30 06:05:07 attack kernel: (da2:umass-sim2:2:0:0): removing device > entry > Jan 30 06:05:07 attack kernel: ugen3.4: at > usbus3 (disconnected) > Jan 30 06:05:07 attack kernel: GEOM_LABEL: Label ufs/usbboot removed. > > -- > > I'll keep testing throughout the day to make sure there aren't any > gremlins lurking about. Can this be committed soon if no problems > come up? Hi, I think Warner M. Losh and Scott Long is working on this. Please sync with them. There has been a long off-list discussion going through all aspects of this patch. --HPS From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 15:28:39 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE46F1065675 for ; Fri, 30 Jan 2009 15:28:39 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: from web63904.mail.re1.yahoo.com (web63904.mail.re1.yahoo.com [69.147.97.119]) by mx1.freebsd.org (Postfix) with SMTP id 8B7D78FC1E for ; Fri, 30 Jan 2009 15:28:39 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: (qmail 54244 invoked by uid 60001); 30 Jan 2009 15:28:38 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Message-ID; b=1ITyHj88s1X0a1wRKN/u0jbikUP8BsN5JxLZkIGAAXZQJUxEcoGjmXdoM7ljX7yuU3qOsPJTXheUM2ri6eThsXjnEgk5Fy5AOL8/lOjdmxiUvbUtmTRk/sKUAHsE0Oxw3rHFRDu0g+peuqqtWIJ0fLdRKDfH3B1U8p9NrQvanfY=; X-YMail-OSG: Ifd2xuUVM1k34aSIyYnnmRmUxKrXKvxuuJ4gQ5.BjP7ksJkdSRP8zjPKKpaUeINkmcJvWRx58NvRtguPdx9ZR13ZPJ27fZu.Jnb7JgCFKiqQ9BG70GLPpnqU0GoVDQl9hu0gjwDft4cZp5d6OJcgZYjU6APnYlcjNSCZeIjuS74KAS2toImW57nsBw226JkpPNgdrQ-- Received: from [98.242.222.229] by web63904.mail.re1.yahoo.com via HTTP; Fri, 30 Jan 2009 07:28:38 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Fri, 30 Jan 2009 07:28:38 -0800 (PST) From: Barney Cordoba To: Nenhum_de_Nos , Wes Morgan In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <899487.53579.qm@web63904.mail.re1.yahoo.com> Cc: freebsd-current@freebsd.org Subject: Re: SATA drive device moving on 8.0 current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: barney_cordoba@yahoo.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, 30 Jan 2009 15:28:40 -0000 --- On Thu, 1/29/09, Wes Morgan wrote: > From: Wes Morgan > Subject: Re: SATA drive device moving on 8.0 current > To: "Nenhum_de_Nos" > Cc: freebsd-current@freebsd.org > Date: Thursday, January 29, 2009, 7:10 PM > On Thu, 29 Jan 2009, Nenhum_de_Nos wrote: > > > > > On Wed, January 28, 2009 23:48, Daniel O'Connor > wrote: > >> On Thursday 29 January 2009 03:48:11 Barney > Cordoba wrote: > >>> I booted 8.0-current on a machine that was > running 7 and the SATA drive > >>> came up as ad4 instead of ad8 (as it is > detected in 7). This is the case > >>> was loading GENERIC. > >>> > >>> This is going to present a serious problem > doing field upgrades as its > >>> expected that fstab will be the same. What is > the reason for the change > >>> and > >>> is there any way to make it compatible with > device detection in 7? > >> > >> I don't know how you can change it back, but > you can use glabel and tunefs > >> -L > >> and then modify /etc/fstab to use /dev/ufs/foo. > > > > even / can use this ? > > just current has this feature ? > > > Did you, by any chance, remove ATA_STATIC_ID from your > kernel config? No From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 15:46:12 2009 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 C2FF2106572E for ; Fri, 30 Jan 2009 15:46:12 +0000 (UTC) (envelope-from richardtector@thekeelecentre.com) Received: from mx0.thekeelecentre.com (mx0.thekeelecentre.com [IPv6:2001:470:1f09:16f:2::3]) by mx1.freebsd.org (Postfix) with ESMTP id 7D0158FC19 for ; Fri, 30 Jan 2009 15:46:12 +0000 (UTC) (envelope-from richardtector@thekeelecentre.com) Received: from localhost (filter.mx0.thekeelecentre.com [217.206.238.165]) by mx0.thekeelecentre.com (Postfix) with ESMTP id 9A94645048; Fri, 30 Jan 2009 15:46:11 +0000 (GMT) X-Virus-Scanned: amavisd-new at thekeelecentre.com Received: from mx0.thekeelecentre.com ([217.206.238.167]) by localhost (filter.mx0.thekeelecentre.com [217.206.238.165]) (amavisd-new, port 10024) with ESMTP id ZKr4wcwv8CrR; Fri, 30 Jan 2009 15:46:08 +0000 (UTC) Received: from [10.0.2.50] (daffy.tector.org.uk [82.71.32.9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx0.thekeelecentre.com (Postfix) with ESMTPSA id C937C45020; Fri, 30 Jan 2009 15:46:07 +0000 (GMT) Message-ID: <498320B1.40503@thekeelecentre.com> Date: Fri, 30 Jan 2009 15:45:53 +0000 From: Richard Tector User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: barney_cordoba@yahoo.com References: <234885.44369.qm@web63903.mail.re1.yahoo.com> In-Reply-To: <234885.44369.qm@web63903.mail.re1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: SATA drive device moving on 8.0 current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2009 15:46:13 -0000 Barney Cordoba wrote: > > > --- On Thu, 1/29/09, Andrey V. Elsukov wrote: > >> From: Andrey V. Elsukov >> Subject: Re: SATA drive device moving on 8.0 current >> To: barney_cordoba@yahoo.com >> Cc: current@freebsd.org >> Date: Thursday, January 29, 2009, 12:20 AM >> Barney Cordoba wrote: >>> I booted 8.0-current on a machine that was running 7 >> and the SATA drive >>> came up as ad4 instead of ad8 (as it is detected in >> 7). This is the case >>> was loading GENERIC. >>> >>> This is going to present a serious problem doing field >> upgrades as its expected that fstab will be the same. What >> is the reason for the change and >>> is there any way to make it compatible with device >> detection in 7? >> >> Probably your system now have (or lost) support for some of >> your ATA/SATA controller. > > Theres only 1 controller with 4 ports, so it was probably something that > was fixed. We were never quite sure why it started at different indexes > on different machines with similar architecture. > > Barney If you could post a dmesg for both 7 and -current, that would be useful. Richard From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 17:05:28 2009 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 7301F106567D for ; Fri, 30 Jan 2009 17:05:28 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 47F6C8FC29 for ; Fri, 30 Jan 2009 17:05:28 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.123.2.23] (h-66-166-149-52.snvacaid.covad.net [66.166.149.52]) by kientzle.com (8.12.9/8.12.9) with ESMTP id n0UH5OC1041808; Fri, 30 Jan 2009 09:05:27 -0800 (PST) (envelope-from kientzle@freebsd.org) Message-ID: <49833352.3010208@freebsd.org> Date: Fri, 30 Jan 2009 09:05:22 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <30968.1233310214@critter.freebsd.dk> In-Reply-To: <30968.1233310214@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: "'current@FreeBSD.org'" Subject: Re: RFC: Change mtree nsec handling? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jan 2009 17:05:28 -0000 Poul-Henning Kamp wrote: > In message <49829D49.10306@freebsd.org>, Tim Kientzle writes: > >>mtree support and the mtree(8) program, I found >>that mtree formats timestamps rather strangely. >> >>For example, a timestamp of 1233295862.000001 >>(1233295682 seconds and 1000 nanoseconds) >>will be printed like this by mtree: >> time=1233295862.1000 >>Unsurprisingly, the mtree parsing works the same >>way in reverse. > >>@@ -258,6 +259,8 @@ >> val = ep + 1; >> ip->st_mtimespec.tv_nsec >> = strtoul(val, &ep, 10); >>+ for (i = ep - val; i < 9; ++i) >>+ ip->st_mtimespec.tv_nsec *= 10; > > > Why is this bit needed ? > This is the part that converts 1233295862.000001 into 1000 nanoseconds (instead of 1 nanosecond). Two reasons: 1) Documentation. It's much easier to document "decimal seconds" than "period followed nine digits representing the number of nanoseconds past the whole second." 2) Interoperability. I originally noticed this testing other mtree-producing code against our mtree implementation. For example, since FreeBSD filesystems never (?) store higher resolution than microseconds, there's really no reason to write more than 6 digits after the decimal point. It seems a tad naive to assume that everyone will always write 9 digits. I can leave this out for a cycle if there's real concern. Fractional seconds occur so rarely on FreeBSD systems (to my knowledge, the kernel never spontaneously generates them so they can only be created by tools like touch that explicitly call utimes()) that I didn't think this would affect any real applications. But if I'm wrong.... Tim From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 20:05:49 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 866331065691 for ; Fri, 30 Jan 2009 20:05:49 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from hosting.lissyara.su (hosting.lissyara.su [77.221.149.162]) by mx1.freebsd.org (Postfix) with ESMTP id 3E5E68FC12 for ; Fri, 30 Jan 2009 20:05:49 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from [89.178.147.80] (port=62346 helo=HP.lissyara.su) by hosting.lissyara.su with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LSzcY-000LSm-VM; Fri, 30 Jan 2009 23:05:47 +0300 Message-ID: <49835D99.9070401@lissyara.su> Date: Fri, 30 Jan 2009 23:05:45 +0300 From: Alex Keda User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; ru-RU; rv:1.8.1.19) Gecko/20090129 Thunderbird/2.0.0.19 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: Nenhum_de_Nos References: <9205533c10f7f0cebe246cd891d7fd2e.squirrel@cygnus.homeunix.com> In-Reply-To: <9205533c10f7f0cebe246cd891d7fd2e.squirrel@cygnus.homeunix.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Description: if spam count > 60 - this is spam X-Spam-Count: 0 X-Descriptions: powered by www.lissyara.su X-Bounce-ID: hosting.lissyara.su Cc: freebsd-current@freebsd.org Subject: Re: cpu cooler speed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jan 2009 20:05:50 -0000 Nenhum_de_Nos пишет: > hail, > > I have a recent current running on amd64 asus laptop that is hell hot. > when in Windows, it spins faster than it is (is almost stopped) and is not > hot when not compiling. > > is there anything I can do to better this ? > > I made some changes to acpi_asus and it loads for my notebook, but even > though is still hot ... /etc/rc.d/powerd forcestart From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 20:50:08 2009 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 8F756106570B for ; Fri, 30 Jan 2009 20:50:08 +0000 (UTC) (envelope-from antab@valka.is) Received: from smtp-vbr19.xs4all.nl (smtp-vbr19.xs4all.nl [194.109.24.39]) by mx1.freebsd.org (Postfix) with ESMTP id 2E9FA8FC20 for ; Fri, 30 Jan 2009 20:50:08 +0000 (UTC) (envelope-from antab@valka.is) Received: from dumb.farm.antab.is (farm.antab.is [80.101.60.195]) by smtp-vbr19.xs4all.nl (8.13.8/8.13.8) with ESMTP id n0UKo07B037784; Fri, 30 Jan 2009 21:50:01 +0100 (CET) (envelope-from antab@valka.is) Message-Id: <3CF1FDD7-11C8-4761-B775-57ED90B02238@valka.is> From: Arnar Mar Sig To: current@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Fri, 30 Jan 2009 21:50:00 +0100 X-Mailer: Apple Mail (2.930.3) X-Virus-Scanned: by XS4ALL Virus Scanner Cc: Hans Petter Selasky Subject: Problem with usbconfig, not working X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jan 2009 20:50:10 -0000 It seems usbconfig is not working for me (-CURRENT from Jan 29, amd64) What i'm trying to do is turn off power to a usb device (actually i wanted to turn off all ports, no matter if there was a device there or not) For all commands I get the error message: "No device match or lack of permissions." Also imo its not really clear in man usbconfig what -u and -a should be. What should it be for ums0 at uhub0? -u 0 -a 0 (uhub0 usm0) -u 0 -a 1 (from usbdevs output: /dev/usb0 port 1) -u 0 -a 2 (from usbdevs output: /dev/usb0 addr 2) I tried all, same error message. I also tried without -u and -a, same # usbdevs -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), nVidia(0x0000), rev 1.00 port 1 addr 2: low speed, power 98 mA, config 1, USB-PS/2 Optical Mouse(0xc012), Logitech(0x046d), rev 13.20 port 2 powered port 3 powered port 4 powered port 5 powered port 6 powered port 7 powered port 8 powered Controller /dev/usb1: addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), nVidia(0x0000), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered port 5 powered port 6 powered port 7 powered port 8 powered Greets Arnar Mar Sig Valka ehf From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 21:08:52 2009 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 2E6EF1065673; Fri, 30 Jan 2009 21:08:52 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id C0FF88FC18; Fri, 30 Jan 2009 21:08:51 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1LT00b-0003gn-Fm; Fri, 30 Jan 2009 22:30:37 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n0UKUYKW053714 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Jan 2009 22:30:34 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n0UKUYJn017005; Fri, 30 Jan 2009 22:30:34 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n0UKUX5P017004; Fri, 30 Jan 2009 22:30:33 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 30 Jan 2009 22:30:33 +0200 From: Kostik Belousov To: Tim Kientzle Message-ID: <20090130203033.GB52415@deviant.kiev.zoral.com.ua> References: <30968.1233310214@critter.freebsd.dk> <49833352.3010208@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mxv5cy4qt+RJ9ypb" Content-Disposition: inline In-Reply-To: <49833352.3010208@freebsd.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1LT00b-0003gn-Fm c76b5b6e10fa092a8901cfb78cb387e0 X-Terabit: YES Cc: Poul-Henning Kamp , "'current@FreeBSD.org'" Subject: Re: RFC: Change mtree nsec handling? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jan 2009 21:08:52 -0000 --mxv5cy4qt+RJ9ypb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 30, 2009 at 09:05:22AM -0800, Tim Kientzle wrote: > Poul-Henning Kamp wrote: > >In message <49829D49.10306@freebsd.org>, Tim Kientzle writes: > > > >>mtree support and the mtree(8) program, I found > >>that mtree formats timestamps rather strangely. > >> > >>For example, a timestamp of 1233295862.000001 > >>(1233295682 seconds and 1000 nanoseconds) > >>will be printed like this by mtree: > >> time=3D1233295862.1000 > >>Unsurprisingly, the mtree parsing works the same > >>way in reverse. > > > >>@@ -258,6 +259,8 @@ > >> val =3D ep + 1; > >> ip->st_mtimespec.tv_nsec > >> =3D strtoul(val, &ep, 10); > >>+ for (i =3D ep - val; i < 9; ++i) > >>+ ip->st_mtimespec.tv_nsec *=3D 10; > > > > > >Why is this bit needed ? > > >=20 > This is the part that converts 1233295862.000001 into > 1000 nanoseconds (instead of 1 nanosecond). >=20 > Two reasons: > 1) Documentation. It's much easier to document > "decimal seconds" than "period followed nine digits > representing the number of nanoseconds past the whole > second." > 2) Interoperability. I originally noticed this testing > other mtree-producing code against our mtree implementation. > For example, since FreeBSD filesystems never (?) store Look at the vfs.timestamp_precision sysctl in sys/kern/vfs_subr.c > higher resolution than microseconds, there's really > no reason to write more than 6 digits after the decimal > point. It seems a tad naive to assume that everyone > will always write 9 digits. >=20 > I can leave this out for a cycle if there's real concern. > Fractional seconds occur so rarely on FreeBSD systems > (to my knowledge, the kernel never spontaneously generates > them so they can only be created by tools like touch that > explicitly call utimes()) that I didn't think this > would affect any real applications. >=20 > But if I'm wrong.... >=20 > Tim > _______________________________________________ > 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" --mxv5cy4qt+RJ9ypb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkmDY2kACgkQC3+MBN1Mb4jNRgCg27il8U7YkkoDwrKn++AzkjyB AVYAni0NYYRkZJIBO4F3o4Sc3jspkd+p =hpK9 -----END PGP SIGNATURE----- --mxv5cy4qt+RJ9ypb-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 21:13:19 2009 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 C62471065672 for ; Fri, 30 Jan 2009 21:13:19 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe04.swip.net [212.247.154.97]) by mx1.freebsd.org (Postfix) with ESMTP id 5D1A98FC25 for ; Fri, 30 Jan 2009 21:13:19 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=dyfCM7niMg0A:10 a=L3UWJZNBNYbMt0azfyMA:9 a=_WbF-q2Y9llc99JbU5wA:7 a=8DWnvhPs6Nw1Lnt9ndG1VEr-XDwA:4 a=LY0hPdMaydYA:10 Received: from [85.19.218.115] (account mc467741@c2i.net HELO [10.37.1.92]) by mailfe04.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 1188345663; Fri, 30 Jan 2009 22:13:17 +0100 From: Hans Petter Selasky To: Arnar Mar Sig Date: Fri, 30 Jan 2009 22:15:40 +0100 User-Agent: KMail/1.9.7 References: <3CF1FDD7-11C8-4761-B775-57ED90B02238@valka.is> In-Reply-To: <3CF1FDD7-11C8-4761-B775-57ED90B02238@valka.is> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901302215.41627.hselasky@c2i.net> Cc: current@freebsd.org Subject: Re: Problem with usbconfig, not working X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jan 2009 21:13:20 -0000 On Friday 30 January 2009, Arnar Mar Sig wrote: > It seems usbconfig is not working for me (-CURRENT from Jan 29, amd64) > > What i'm trying to do is turn off power to a usb device (actually i > wanted to turn off all ports, no matter if there was a device there or > not) > For all commands I get the error message: "No device match or lack of > permissions." Hi, "usbconfig" does not work with the old USB stack which is what you have loaded. --HPS > > Also imo its not really clear in man usbconfig what -u and -a should > be. What should it be for ums0 at uhub0? > -u 0 -a 0 (uhub0 usm0) > -u 0 -a 1 (from usbdevs output: /dev/usb0 port 1) > -u 0 -a 2 (from usbdevs output: /dev/usb0 addr 2) > I tried all, same error message. I also tried without -u and -a, same > > # usbdevs -v > Controller /dev/usb0: > addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), > nVidia(0x0000), rev 1.00 > port 1 addr 2: low speed, power 98 mA, config 1, USB-PS/2 Optical > Mouse(0xc012), Logitech(0x046d), rev 13.20 > port 2 powered > port 3 powered > port 4 powered > port 5 powered > port 6 powered > port 7 powered > port 8 powered > Controller /dev/usb1: > addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), > nVidia(0x0000), rev 1.00 > port 1 powered > port 2 powered > port 3 powered > port 4 powered > port 5 powered > port 6 powered > port 7 powered > port 8 powered > > Greets > Arnar Mar Sig > Valka ehf From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 21:18:08 2009 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 B7BFE1065670 for ; Fri, 30 Jan 2009 21:18:08 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from pele.citylink.co.nz (pele.citylink.co.nz [202.8.44.226]) by mx1.freebsd.org (Postfix) with ESMTP id 7EC6D8FC16 for ; Fri, 30 Jan 2009 21:18:08 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by pele.citylink.co.nz (Postfix) with ESMTP id B5972FF05 for ; Sat, 31 Jan 2009 10:18:07 +1300 (NZDT) X-Virus-Scanned: Debian amavisd-new at citylink.co.nz Received: from pele.citylink.co.nz ([127.0.0.1]) by localhost (pele.citylink.co.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LPv3WsRZ9jaR for ; Sat, 31 Jan 2009 10:18:04 +1300 (NZDT) Received: from citylink.fud.org.nz (unknown [202.8.44.45]) by pele.citylink.co.nz (Postfix) with ESMTP for ; Sat, 31 Jan 2009 10:18:04 +1300 (NZDT) Received: by citylink.fud.org.nz (Postfix, from userid 1001) id 6C5C21142A; Sat, 31 Jan 2009 10:18:04 +1300 (NZDT) Date: Fri, 30 Jan 2009 13:18:04 -0800 From: Andrew Thompson To: current@freebsd.org Message-ID: <20090130211804.GC10578@citylink.fud.org.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Subject: zyd(4) adapter X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jan 2009 21:18:09 -0000 Hi, I am not having much luck finding a Zydas wireless adapter in order to test some usb net80211 enhancements. Does anyone have a spare one that they would be willing to donate (ship to Canada)? Needs to work with the zyd(4) driver. cheers, Andrew From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 21:19:10 2009 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 237AA1065726; Fri, 30 Jan 2009 21:19:10 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id CE7D78FC12; Fri, 30 Jan 2009 21:19:09 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id B550F3F130; Fri, 30 Jan 2009 21:19:08 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.3/8.14.3) with ESMTP id n0ULJ86b068254; Fri, 30 Jan 2009 21:19:08 GMT (envelope-from phk@critter.freebsd.dk) To: Kostik Belousov From: "Poul-Henning Kamp" In-Reply-To: Your message of "Fri, 30 Jan 2009 22:30:33 +0200." <20090130203033.GB52415@deviant.kiev.zoral.com.ua> Date: Fri, 30 Jan 2009 21:19:08 +0000 Message-ID: <68253.1233350348@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Tim Kientzle , "'current@FreeBSD.org'" Subject: Re: RFC: Change mtree nsec handling? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jan 2009 21:19:15 -0000 In message <20090130203033.GB52415@deviant.kiev.zoral.com.ua>, Kostik Belousov writes: >> >>@@ -258,6 +259,8 @@ >> >> val = ep + 1; >> >> ip->st_mtimespec.tv_nsec >> >> = strtoul(val, &ep, 10); >> >>+ for (i = ep - val; i < 9; ++i) >> >>+ ip->st_mtimespec.tv_nsec *= 10; >> > >> > >> >Why is this bit needed ? >> > >> >> This is the part that converts 1233295862.000001 into >> 1000 nanoseconds (instead of 1 nanosecond). But that wouldn't happen, because no mtree file has that content. Either it has 1233295862.000001000 from the new %09d or it has 1233295862.1000 from the old %d Please leave this out, it can only cause problems. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 21:27:07 2009 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 A1546106566B for ; Fri, 30 Jan 2009 21:27:07 +0000 (UTC) (envelope-from antab@valka.is) Received: from smtp-vbr19.xs4all.nl (smtp-vbr19.xs4all.nl [194.109.24.39]) by mx1.freebsd.org (Postfix) with ESMTP id 3F09F8FC21 for ; Fri, 30 Jan 2009 21:27:06 +0000 (UTC) (envelope-from antab@valka.is) Received: from dumb.farm.antab.is (farm.antab.is [80.101.60.195]) by smtp-vbr19.xs4all.nl (8.13.8/8.13.8) with ESMTP id n0ULR5t8044528; Fri, 30 Jan 2009 22:27:05 +0100 (CET) (envelope-from antab@valka.is) Message-Id: <7C9D5C0E-57AE-4BE9-B7FE-3181FBFED5C0@valka.is> From: Arnar Mar Sig To: Hans Petter Selasky In-Reply-To: <200901302215.41627.hselasky@c2i.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Fri, 30 Jan 2009 22:27:04 +0100 References: <3CF1FDD7-11C8-4761-B775-57ED90B02238@valka.is> <200901302215.41627.hselasky@c2i.net> X-Mailer: Apple Mail (2.930.3) X-Virus-Scanned: by XS4ALL Virus Scanner Cc: current@freebsd.org Subject: Re: Problem with usbconfig, not working X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jan 2009 21:27:08 -0000 On Jan 30, 2009, at 10:15 PM, Hans Petter Selasky wrote: > On Friday 30 January 2009, Arnar Mar Sig wrote: >> It seems usbconfig is not working for me (-CURRENT from Jan 29, >> amd64) >> >> What i'm trying to do is turn off power to a usb device (actually i >> wanted to turn off all ports, no matter if there was a device there >> or >> not) >> For all commands I get the error message: "No device match or lack of >> permissions." > > Hi, > > "usbconfig" does not work with the old USB stack which is what you > have > loaded. Ahh, my bad, just did a quick look at kldstat where usb2_core.ko was loaded, but forgot the old stack was compiled in. going to recompile and try again. Thanks > --HPS > >> >> Also imo its not really clear in man usbconfig what -u and -a should >> be. What should it be for ums0 at uhub0? >> -u 0 -a 0 (uhub0 usm0) >> -u 0 -a 1 (from usbdevs output: /dev/usb0 port 1) >> -u 0 -a 2 (from usbdevs output: /dev/usb0 addr 2) >> I tried all, same error message. I also tried without -u and -a, same >> >> # usbdevs -v >> Controller /dev/usb0: >> addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), >> nVidia(0x0000), rev 1.00 >> port 1 addr 2: low speed, power 98 mA, config 1, USB-PS/2 Optical >> Mouse(0xc012), Logitech(0x046d), rev 13.20 >> port 2 powered >> port 3 powered >> port 4 powered >> port 5 powered >> port 6 powered >> port 7 powered >> port 8 powered >> Controller /dev/usb1: >> addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), >> nVidia(0x0000), rev 1.00 >> port 1 powered >> port 2 powered >> port 3 powered >> port 4 powered >> port 5 powered >> port 6 powered >> port 7 powered >> port 8 powered >> >> Greets >> Arnar Mar Sig >> Valka ehf From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 22:19:36 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B57B1065675; Fri, 30 Jan 2009 22:19:36 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id EB0248FC18; Fri, 30 Jan 2009 22:19:35 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1LT1i3-0007HS-80>; Fri, 30 Jan 2009 23:19:35 +0100 Received: from e178024083.adsl.alicedsl.de ([85.178.24.83] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1LT1i3-0000Rq-57>; Fri, 30 Jan 2009 23:19:35 +0100 Message-ID: <49837CFD.4080603@mail.zedat.fu-berlin.de> Date: Fri, 30 Jan 2009 23:19:41 +0100 From: "O. Hartmann" User-Agent: Thunderbird 2.0.0.19 (X11/20090129) MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-questions@freebsd.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Originating-IP: 85.178.24.83 X-Mailman-Approved-At: Fri, 30 Jan 2009 22:24:06 +0000 Cc: Subject: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.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, 30 Jan 2009 22:19:36 -0000 After upgrading one of my FreeBSD 8.0-CUR/amd64 boxes to new xorg-7.4 and having done hurting recompiling nearly everything/package twice now firefox3 still doesn't work properly and hits me when starting with this error message: Xlib: extension "Generic Event Extension" missing on display ":0.0". Then firefox3 freezes forever, showing something like the background or pixel remnants of windows/picograms moving over its window. I recompiled three times libxcb and its dependencies, two times Xlib/Xserver/xf86-input-* to be sure having compiled everything and then I recompiled everything again what's necessary to build Firefox3. No effect. I now recompile everything needed to build Xlib to get rid of the above shown error message because I suspect this causing my firefox3 not working. On another box, also amd64, but FreeBSD 7.1-STABLE (SMP) I had to do the same procedure and firefox3 is working properly. Bot boxes do have ATI graphics (driver radeon). I also tried deleting my personal .mozille directory and started firefox from scratch. But after some download-save-requester opened (when trying to download a file from a location in the web) firefox freezes also eating up 100% cpu. In all cases Firefox3 can be killed. Any help is appreciated. Oliver From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 22:45:15 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5996E106564A for ; Fri, 30 Jan 2009 22:45:15 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (brucec-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:c09::2]) by mx1.freebsd.org (Postfix) with ESMTP id 16A198FC22 for ; Fri, 30 Jan 2009 22:45:15 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 7987F1901D; Fri, 30 Jan 2009 17:45:13 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on muon X-Spam-Level: X-Spam-Status: No, score=-2.5 required=8.0 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.2.5 Received: from gluon (unknown [IPv6:2a01:348:10f:0:240:f4ff:fe57:9871]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA; Fri, 30 Jan 2009 17:45:13 -0500 (EST) Date: Fri, 30 Jan 2009 22:45:07 +0000 From: Bruce Cran To: Alexander Best Message-ID: <20090130224507.60650747@gluon> In-Reply-To: References: X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.9; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: fdisk: Class not found X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2009 22:45:15 -0000 On Sun, 18 Jan 2009 15:07:24 +0100 (CET) Alexander Best wrote: > when i'm trying to do the following: > > fdisk -B adX > > i get the following error message: > > fdisk: Class not found > fdisk: Failed to write sector zero > > i'm running FreeBSD moshnroll 8.0-CURRENT FreeBSD 8.0-CURRENT #0 > r187392M: Sun Jan 18 14:42:30 UTC 2009 > root@moshnroll:/usr/obj/usr/src/sys/ARUNDEL i386 and rebuild and > reinstalled fdisk. It seems that message is generated when geom_mbr isn't loaded. I was running fdisk against an md(4) disk and after loading geom_mbr I got a new message saying it couldn't find geom "md0". The new partition table showed up when I ran fdisk again, but after detaching and reattaching using mdconfig the changes hadn't been saved. -- Bruce Cran From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 22:54:06 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D438C106583D; Fri, 30 Jan 2009 22:54:06 +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 8D81F8FC32; Fri, 30 Jan 2009 22:54:06 +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.3/8.14.3/NETPLEX) with ESMTP id n0UMbtVA000775; Fri, 30 Jan 2009 17:37:56 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Fri, 30 Jan 2009 17:37:56 -0500 (EST) Date: Fri, 30 Jan 2009 17:37:55 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: "O. Hartmann" In-Reply-To: <49837CFD.4080603@mail.zedat.fu-berlin.de> Message-ID: References: <49837CFD.4080603@mail.zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0". 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: Fri, 30 Jan 2009 22:54:09 -0000 On Fri, 30 Jan 2009, O. Hartmann wrote: > After upgrading one of my FreeBSD 8.0-CUR/amd64 boxes to new xorg-7.4 > and having done hurting recompiling nearly everything/package twice now > firefox3 still doesn't work properly and hits me when starting with this > error message: > > Xlib: extension "Generic Event Extension" missing on display ":0.0". > > Then firefox3 freezes forever, showing something like the background or > pixel remnants of windows/picograms moving over its window. > > I recompiled three times libxcb and its dependencies, two times > Xlib/Xserver/xf86-input-* to be sure having compiled everything and then > I recompiled everything again what's necessary to build Firefox3. No > effect. I now recompile everything needed to build Xlib to get rid of > the above shown error message because I suspect this causing my firefox3 > not working. > > On another box, also amd64, but FreeBSD 7.1-STABLE (SMP) I had to do the > same procedure and firefox3 is working properly. Bot boxes do have ATI > graphics (driver radeon). > > I also tried deleting my personal .mozille directory and started firefox > from scratch. But after some download-save-requester opened (when trying > to download a file from a location in the web) firefox freezes also > eating up 100% cpu. In all cases Firefox3 can be killed. > > Any help is appreciated. Perhaps it's a little overkill, but what I usually do when I perform upgrades like this, is to move /usr/local out of the way (along with /var/db/pkg), and remove any X/KDE/QT stuff in /tmp, /var/.., etc. Then I install (portupdate -NR) everything from scratch. If something goes wrong, I just have to move the original /usr/local back until I work out the problems. -- DE From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 23:36:24 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EBE95106566C for ; Fri, 30 Jan 2009 23:36:24 +0000 (UTC) (envelope-from alex-goncharov@comcast.net) Received: from QMTA08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by mx1.freebsd.org (Postfix) with ESMTP id 952358FC1F for ; Fri, 30 Jan 2009 23:36:24 +0000 (UTC) (envelope-from alex-goncharov@comcast.net) Received: from OMTA03.westchester.pa.mail.comcast.net ([76.96.62.27]) by QMTA08.westchester.pa.mail.comcast.net with comcast id 9mwv1b0070bG4ec58zP9lq; Fri, 30 Jan 2009 23:23:09 +0000 Received: from daland.home ([24.34.211.11]) by OMTA03.westchester.pa.mail.comcast.net with comcast id 9zP81b00c0FJTGg3PzP9kB; Fri, 30 Jan 2009 23:23:09 +0000 Received: from algo by daland.home with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LT2hX-0003NJ-He; Fri, 30 Jan 2009 18:23:07 -0500 From: Alex Goncharov To: "O. Hartmann" In-reply-to: <49837CFD.4080603@mail.zedat.fu-berlin.de> (ohartman@mail.zedat.fu-berlin.de) References: <49837CFD.4080603@mail.zedat.fu-berlin.de> Message-Id: Sender: Alex Goncharov Date: Fri, 30 Jan 2009 18:23:07 -0500 Cc: freebsd-current@freebsd.org, freebsd-questions@freebsd.org, freebsd-ports@freebsd.org Subject: Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0". X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alex Goncharov List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2009 23:36:26 -0000 ,--- You/O. (Fri, 30 Jan 2009 23:19:41 +0100) ----* | After upgrading one of my FreeBSD 8.0-CUR/amd64 boxes to new xorg-7.4 | and having done hurting recompiling nearly everything/package twice now | firefox3 still doesn't work properly and hits me when starting with this | error message: | | Xlib: extension "Generic Event Extension" missing on display ":0.0". Interesting -- I just did my comprehensive upgrade, as a part of which xorg-server went from 1.5.3_1,1 to 1.5.3_2,1. And this is what I see now, for the first time, and consistently: ---------------------------------------- $ xterm& [3] 12585 $ emacs & [4] 12644 Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". ---------------------------------------- The garbage still pollutes my windows periodically, so, I guess, my next xorg-server will be 1.4. For reference, my system is: i386 FreeBSD 7.1-STABLE Sun Jan 25 06:28:38 EST 2009 It not being CURRENT, I took the liberty of cc: freebsd-ports@freebsd.org. -- Alex -- alex-goncharov@comcast.net -- From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 23:40:18 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0DD21106567A for ; Fri, 30 Jan 2009 23:40:18 +0000 (UTC) (envelope-from me@janh.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mx1.freebsd.org (Postfix) with ESMTP id 9948C8FC17 for ; Fri, 30 Jan 2009 23:40:17 +0000 (UTC) (envelope-from me@janh.de) Received: from janh.freebsd (e177246003.adsl.alicedsl.de [85.177.246.3]) by mrelayeu.kundenserver.de (node=mrelayeu7) with ESMTP (Nemesis) id 0ML2xA-1LT2ls12Cq-0002fW; Sat, 31 Jan 2009 00:27:36 +0100 Message-ID: <49838CE0.7080808@janh.de> Date: Sat, 31 Jan 2009 00:27:28 +0100 From: Jan Henrik Sylvester User-Agent: Thunderbird 2.0.0.19 (X11/20090115) MIME-Version: 1.0 To: "O. Hartmann" References: 49837CFD.4080603@mail.zedat.fu-berlin.de Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX185IaS6Kpe38WSSaOTpi3PBtkCgoKdelFwPBlA M3q8ZNnlU0o1yezfmOWcYnDOqY6MwKS1WmgHQ7hn4sMDi9HjCa TyQxfAmLLJ4GdGUgt3x/w== X-Mailman-Approved-At: Sat, 31 Jan 2009 00:08:58 +0000 Cc: current-list freebsd Subject: Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.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, 30 Jan 2009 23:40:18 -0000 O. Hartmann wrote: > Xlib: extension "Generic Event Extension" missing on display ":0.0". > > Then firefox3 freezes forever, showing something like the background or > pixel remnants of windows/picograms moving over its window. Today, I had this error, too, but not with firefox3 (IIRC). It was after the update of libXext-1.0.4,1 to 1.0.5,1 -- going back seemed to have fixed it. (I still had a package from after the xorg 7.4 upgrade last week.) I have not got time to look into it and try to reproduce it. (There were some other updates and configurations changes around the same time.) BTW: It was on 7.1. I do use the radeon driver, too. Cheers, Jan Henrik From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 23:48:05 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBB561065675 for ; Fri, 30 Jan 2009 23:48:05 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from mail.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 9C5D08FC13 for ; Fri, 30 Jan 2009 23:48:05 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (mail.rachie.is-a-geek.net [192.168.2.101]) by mail.rachie.is-a-geek.net (Postfix) with ESMTP id 4CF43AFBCCB; Fri, 30 Jan 2009 14:30:07 -0900 (AKST) From: Mel To: freebsd-questions@freebsd.org Date: Fri, 30 Jan 2009 14:30:06 -0900 User-Agent: KMail/1.9.10 References: <49837CFD.4080603@mail.zedat.fu-berlin.de> In-Reply-To: <49837CFD.4080603@mail.zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901301430.07087.fbsd.questions@rachie.is-a-geek.net> X-Mailman-Approved-At: Sat, 31 Jan 2009 00:32:06 +0000 Cc: "O. Hartmann" , freebsd-current@freebsd.org Subject: Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.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, 30 Jan 2009 23:48:06 -0000 On Friday 30 January 2009 13:19:41 O. Hartmann wrote: > After upgrading one of my FreeBSD 8.0-CUR/amd64 boxes to new xorg-7.4 > and having done hurting recompiling nearly everything/package twice now > firefox3 still doesn't work properly and hits me when starting with this > error message: > > Xlib: extension "Generic Event Extension" missing on display ":0.0". > > Then firefox3 freezes forever, showing something like the background or > pixel remnants of windows/picograms moving over its window. http://lists.freedesktop.org/archives/xorg/2008-October/039134.html -- Mel Problem with today's modular software: they start with the modules and never get to the software part. From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 01:08:57 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11D431065670 for ; Sat, 31 Jan 2009 01:08:57 +0000 (UTC) (envelope-from dylan@dylex.net) Received: from datura.dylex.net (datura.dylex.net [216.27.141.80]) by mx1.freebsd.org (Postfix) with ESMTP id D74128FC19 for ; Sat, 31 Jan 2009 01:08:56 +0000 (UTC) (envelope-from dylan@dylex.net) Received: from dylan by datura.dylex.net with local (Exim 4.69) (envelope-from ) id 1LT4Lv-00025b-Pi for freebsd-current@FreeBSD.ORG; Fri, 30 Jan 2009 20:08:55 -0500 Date: Fri, 30 Jan 2009 20:08:55 -0500 From: Dylan Alex Simon To: freebsd-current@FreeBSD.ORG Message-ID: <20090131010855.GA7991@datura.dylex.net> References: <8cb6106e0901200641x4b0bda9ag31e6f059f13035a7@mail.gmail.com> <200901201829.n0KITE8V072323@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200901201829.n0KITE8V072323@lurza.secnetix.de> Jabber-ID: dylan@dylex.net Cc: Subject: Re: SATA DMA errors on second ICH10 bus X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 31 Jan 2009 01:08:57 -0000 > That advice seems to be particularly valuable given the > current firmware problems that particular Seagate disks > are exhibiting. I've confirmed with Seagate and others that the firmware these disks already have (CC1F) is not affected by the firmware problems. The instability (as described in kern/130726) continues with a kernel from today. I've traced it down to exclusively and reliably being caused by access to disks on multiple channels simultaneously (access to any pair of disks on the same channel works fine). If anyone has any suggestions or any other data I should collect let me know as I will have to put these machines into production shortly (without freebsd unfortunately). :-Dylan From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 12:21:59 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A214C106564A for ; Sat, 31 Jan 2009 12:21:59 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id E1A818FC17 for ; Sat, 31 Jan 2009 12:21:58 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: (qmail invoked by alias); 31 Jan 2009 12:21:57 -0000 Received: from p54A3DF7B.dip.t-dialin.net (EHLO tron.homeunix.org) [84.163.223.123] by mail.gmx.net (mp069) with SMTP; 31 Jan 2009 13:21:57 +0100 X-Authenticated: #1673122 X-Provags-ID: V01U2FsdGVkX1+a2ZMKSEWarX4AW/zsLXzOgfjSDZ+EpR/EQ/e40L PWIzB2dEc/z/tX Message-ID: <49844264.7000300@gmx.de> Date: Sat, 31 Jan 2009 13:21:56 +0100 From: Christoph Mallon User-Agent: Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Dylan Alex Simon References: <8cb6106e0901200641x4b0bda9ag31e6f059f13035a7@mail.gmail.com> <200901201829.n0KITE8V072323@lurza.secnetix.de> <20090131010855.GA7991@datura.dylex.net> In-Reply-To: <20090131010855.GA7991@datura.dylex.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.61 Cc: freebsd-current@FreeBSD.ORG Subject: Re: SATA DMA errors on second ICH10 bus X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 31 Jan 2009 12:21:59 -0000 Dylan Alex Simon schrieb: >> That advice seems to be particularly valuable given the >> current firmware problems that particular Seagate disks >> are exhibiting. > > I've confirmed with Seagate and others that the firmware these disks already > have (CC1F) is not affected by the firmware problems. The instability (as > described in kern/130726) continues with a kernel from today. I've traced it > down to exclusively and reliably being caused by access to disks on multiple > channels simultaneously (access to any pair of disks on the same channel works > fine). If anyone has any suggestions or any other data I should collect let > me know as I will have to put these machines into production shortly (without > freebsd unfortunately). I suspect I see the same problem with some nvidia SATA controller. If there is high load on both channels of one controller, there are exactly the errors you showed. Your kernel does not use INVARIANTS, is this correct? Otherwise you should see a very specific panic caused by a KASSERT(). I analysed the problem a bit. You can see my findings in the thread "Question about panic in brelse()". I suspect a hardware bug plus incorrect error handling in the driver in FreeBSD. As a workaround, I suggest you connect each disk to a separate controller - if you have not more disks than controllers. From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 15:11:02 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A44931065698; Sat, 31 Jan 2009 15:11:02 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id 4BECF8FC13; Sat, 31 Jan 2009 15:11:02 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from [192.168.2.171] (c-71-56-39-94.hsd1.ga.comcast.net [71.56.39.94]) (authenticated bits=0) by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id n0VFAHwX077510 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 31 Jan 2009 10:10:17 -0500 (EST) (envelope-from rnoland@FreeBSD.org) From: Robert Noland To: Alex Goncharov In-Reply-To: References: <49837CFD.4080603@mail.zedat.fu-berlin.de> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-jWFDHpA5MOoX4ySEL3HZ" Organization: FreeBSD Date: Sat, 31 Jan 2009 10:10:37 -0500 Message-Id: <1233414638.1554.4.camel@ferret.2hip.net> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 FreeBSD GNOME Team Port X-Spam-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RCVD_IN_SORBS_DUL,RDNS_DYNAMIC autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gizmo.2hip.net Cc: "O. Hartmann" , freebsd-current@freebsd.org, freebsd-questions@freebsd.org, freebsd-ports@freebsd.org Subject: Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.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, 31 Jan 2009 15:11:03 -0000 --=-jWFDHpA5MOoX4ySEL3HZ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2009-01-30 at 18:23 -0500, Alex Goncharov wrote: > ,--- You/O. (Fri, 30 Jan 2009 23:19:41 +0100) ----* > | After upgrading one of my FreeBSD 8.0-CUR/amd64 boxes to new xorg-7.4 > | and having done hurting recompiling nearly everything/package twice now > | firefox3 still doesn't work properly and hits me when starting with thi= s > | error message: > |=20 > | Xlib: extension "Generic Event Extension" missing on display ":0.0". >=20 > Interesting -- I just did my comprehensive upgrade, as a part of which > xorg-server went from 1.5.3_1,1 to 1.5.3_2,1. >=20 > And this is what I see now, for the first time, and consistently: >=20 > ---------------------------------------- > $ xterm& > [3] 12585 >=20 > $ emacs & =20 > [4] 12644 > Xlib: extension "Generic Event Extension" missing on display ":0.0". > Xlib: extension "Generic Event Extension" missing on display ":0.0". > Xlib: extension "Generic Event Extension" missing on display ":0.0". > Xlib: extension "Generic Event Extension" missing on display ":0.0". > Xlib: extension "Generic Event Extension" missing on display ":0.0". > Xlib: extension "Generic Event Extension" missing on display ":0.0". This is harmless, it indicates that libXext has support for generic events, but the server does not yet. robert. > ---------------------------------------- >=20 > The garbage still pollutes my windows periodically, so, I guess, my > next xorg-server will be 1.4. >=20 > For reference, my system is: >=20 > i386 FreeBSD 7.1-STABLE Sun Jan 25 06:28:38 EST 2009 >=20 > It not being CURRENT, I took the liberty of cc: freebsd-ports@freebsd.org= . >=20 > -- Alex -- alex-goncharov@comcast.net -- > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" --=20 Robert Noland FreeBSD --=-jWFDHpA5MOoX4ySEL3HZ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEABECAAYFAkmEae0ACgkQM4TrQ4qfROPjWwCfUwdvKXe7LhZNCLr18f/mO1vD PDUAnj0xZ7+bF46uC0I021tIc74eHem9 =q30l -----END PGP SIGNATURE----- --=-jWFDHpA5MOoX4ySEL3HZ-- From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 18:20:31 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2586A10656CA for ; Sat, 31 Jan 2009 18:20:31 +0000 (UTC) (envelope-from giffunip@tutopia.com) Received: from web32702.mail.mud.yahoo.com (web32702.mail.mud.yahoo.com [68.142.207.246]) by mx1.freebsd.org (Postfix) with SMTP id C95318FC17 for ; Sat, 31 Jan 2009 18:20:30 +0000 (UTC) (envelope-from giffunip@tutopia.com) Received: (qmail 81536 invoked by uid 60001); 31 Jan 2009 18:20:30 -0000 X-YMail-OSG: Ex79mEYVM1mQAFRp7J0xRfxQN9KBziG9GveXS39sii.9tp5hNZmDJ957hofO.0Xt3tPh67VhTCIQCxUzUYJcuP2lasa2X0mmSWfOBrDhimBGZ.s38mfdsn1Pugkd2r9a_uoZZmp6sQleCT7.JU6F7WXWzVUBzqBu6B1E6LwsqSdSU6t6Pg80xOrMz60B Received: from [190.157.124.207] by web32702.mail.mud.yahoo.com via HTTP; Sat, 31 Jan 2009 10:20:30 PST X-RocketYMMF: giffunip X-Mailer: YahooMailWebService/0.7.260.1 Date: Sat, 31 Jan 2009 10:20:30 -0800 (PST) From: "Pedro F. Giffuni" To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <271992.81366.qm@web32702.mail.mud.yahoo.com> X-Mailman-Approved-At: Sat, 31 Jan 2009 20:20:08 +0000 Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: giffunip@tutopia.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2009 18:20:31 -0000 I admit I find this thread surprisingly persistent. Just wondering ... Didn't the FreeBSD Foundation hire some lawyers to study the implications of the GPL3? If there is no legally qualified opinion, than I'd say the GPL2 is already too restricted for my taste and if FreeBSD moves to a GPL3'd toolchain without an extremely compelling reason then I would consider a move to another OS. A poll would probably show I am not alone in my stance. Pedro. From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 20:45:54 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED5CA1065714 for ; Sat, 31 Jan 2009 20:45:54 +0000 (UTC) (envelope-from millenia2000@hotmail.com) Received: from bay0-omc1-s18.bay0.hotmail.com (bay0-omc1-s18.bay0.hotmail.com [65.54.246.90]) by mx1.freebsd.org (Postfix) with ESMTP id D57558FC18 for ; Sat, 31 Jan 2009 20:45:54 +0000 (UTC) (envelope-from millenia2000@hotmail.com) Received: from BAY126-DS7 ([65.55.131.34]) by bay0-omc1-s18.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 31 Jan 2009 12:33:54 -0800 X-Originating-IP: [69.243.68.197] X-Originating-Email: [millenia2000@hotmail.com] Message-ID: From: "Sean Cavanaugh" To: , References: <271992.81366.qm@web32702.mail.mud.yahoo.com> In-Reply-To: <271992.81366.qm@web32702.mail.mud.yahoo.com> Date: Sat, 31 Jan 2009 15:33:48 -0500 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 Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8050.1202 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8050.1202 X-OriginalArrivalTime: 31 Jan 2009 20:33:54.0452 (UTC) FILETIME=[3C049D40:01C983E3] Cc: Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 31 Jan 2009 20:45:55 -0000 FreeBSD is not GPL code. It is BSD Licensed. The issue is a lot of open source applications that it can run are GPL licensed. I know there was an effort to replace the core OS apps that were GPL with 100% BSD licensed equivalents. -------------------------------------------------- From: "Pedro F. Giffuni" Sent: Saturday, January 31, 2009 1:20 PM To: Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) > I admit I find this thread surprisingly persistent. Just wondering ... > > Didn't the FreeBSD Foundation hire some lawyers to study the implications > of the GPL3? > > If there is no legally qualified opinion, than I'd say the GPL2 is already > too restricted for my taste and if FreeBSD moves to a GPL3'd toolchain > without an extremely compelling reason then I would consider a move to > another OS. A poll would probably show I am not alone in my stance. > > Pedro. > > > > > > _______________________________________________ > 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 Jan 31 21:08:55 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D66AA1065708 for ; Sat, 31 Jan 2009 21:08:55 +0000 (UTC) (envelope-from giffunip@tutopia.com) Received: from web32706.mail.mud.yahoo.com (web32706.mail.mud.yahoo.com [68.142.207.250]) by mx1.freebsd.org (Postfix) with SMTP id 85C898FC08 for ; Sat, 31 Jan 2009 21:08:55 +0000 (UTC) (envelope-from giffunip@tutopia.com) Received: (qmail 81538 invoked by uid 60001); 31 Jan 2009 21:08:54 -0000 X-YMail-OSG: U9ZAZdwVM1kYb0ucg0kIj9Gv1ap9usfkDYJQphk7gFg9xpcYC9c.jCQzpS.xqj5Up8C5Apfex00uUwW9hJHdZ8JM5A.iB5nNFbWWKI37kEN1xRj4aA73RaD73yJz._Gt9NrZefFWbKj.nm6Sjcn4bRbnQzqtt6yy2SU3A7jp.GQ3tTZI_w8ht6zZNLym6ku1fqECiVfK1.Kvnw7ERESs7DKqLZ0xKZSj Received: from [190.157.124.207] by web32706.mail.mud.yahoo.com via HTTP; Sat, 31 Jan 2009 13:08:54 PST X-RocketYMMF: giffunip X-Mailer: YahooMailWebService/0.7.260.1 Date: Sat, 31 Jan 2009 13:08:54 -0800 (PST) From: "Pedro F. Giffuni" To: freebsd-current@freebsd.org, Sean Cavanaugh MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <779523.80455.qm@web32706.mail.mud.yahoo.com> X-Mailman-Approved-At: Sat, 31 Jan 2009 21:32:02 +0000 Cc: Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: giffunip@tutopia.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2009 21:08:56 -0000 --- On Sat, 1/31/09, Sean Cavanaugh wrote: ... > FreeBSD is not GPL code. It is BSD Licensed. I am aware of this .. thank you ;-). > The issue is a lot of open source applications that it can run are > GPL licensed. I know there was an effort to replace the core OS apps > that were GPL with 100% BSD licensed equivalents. The effort didn't go far enough. Why haven't we removed GNU readline ? Pedro. From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 21:48:57 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 157B51065715 for ; Sat, 31 Jan 2009 21:48:57 +0000 (UTC) (envelope-from dylan@dylex.net) Received: from datura.dylex.net (datura.dylex.net [216.27.141.80]) by mx1.freebsd.org (Postfix) with ESMTP id D06598FC08 for ; Sat, 31 Jan 2009 21:48:56 +0000 (UTC) (envelope-from dylan@dylex.net) Received: from dylan by datura.dylex.net with local (Exim 4.69) (envelope-from ) id 1LTNhv-0002NX-HG; Sat, 31 Jan 2009 16:48:55 -0500 Date: Sat, 31 Jan 2009 16:48:55 -0500 From: Dylan Alex Simon To: Christoph Mallon Message-ID: <20090131214855.GA9123@datura.dylex.net> References: <8cb6106e0901200641x4b0bda9ag31e6f059f13035a7@mail.gmail.com> <200901201829.n0KITE8V072323@lurza.secnetix.de> <20090131010855.GA7991@datura.dylex.net> <49844264.7000300@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49844264.7000300@gmx.de> Jabber-ID: dylan@dylex.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: SATA DMA errors on second ICH10 bus X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 31 Jan 2009 21:48:57 -0000 > I suspect I see the same problem with some nvidia SATA controller. If > there is high load on both channels of one controller, there are exactly > the errors you showed. > Your kernel does not use INVARIANTS, is this correct? Otherwise you > should see a very specific panic caused by a KASSERT(). I analysed the > problem a bit. You can see my findings in the thread "Question about > panic in brelse()". > I suspect a hardware bug plus incorrect error handling in the driver in > FreeBSD. As a workaround, I suggest you connect each disk to a separate > controller - if you have not more disks than controllers. When I do turn INVARIANTS on I ultimately get a number of different failures, depending on what sort of operation I'm doing. I think I've seen the brelse panic you mentioned but not recently. Here's one from today doing cp on ufs: ad0: FAILURE - load data ad0: setting up DMA failed g_vfs_done():ad0s1e[READ(offset=1843986432, length=65536)]error = 5 vnode_pager_getpages: I/O read error vm_fault: pager read error, pid 819 (cp) kernel trap 9 with interrupts disabled Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x8:0xffffffff802ae9fe stack pointer = 0x10:0xfffffffeb61bfae0 frame pointer = 0x10:0xfffffffeb61bfb00 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = resume, IOPL = 0 current process = 12 (irq14: ata0) lock order reversal: (Giant after non-sleepable) 1st 0xffffffff80628750 bio queue (bio queue) @ /usr/src/sys/geom/geom_io.c:68 2nd 0xffffffff8062b8c0 Giant (Giant) @ /usr/src/sys/dev/kbdmux/kbdmux.c:1044 KDB: stack backtrace: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127 cpuid = 0 I certainly agree that there's some problems in error handling, but I'm more concerned about the underlying problem causing the errors. :-Dylan From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 21:49:00 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A19FF1065729 for ; Sat, 31 Jan 2009 21:49:00 +0000 (UTC) (envelope-from bf2006a@yahoo.com) Received: from web39104.mail.mud.yahoo.com (web39104.mail.mud.yahoo.com [209.191.87.32]) by mx1.freebsd.org (Postfix) with SMTP id 4BA468FC0A for ; Sat, 31 Jan 2009 21:49:00 +0000 (UTC) (envelope-from bf2006a@yahoo.com) Received: (qmail 67772 invoked by uid 60001); 31 Jan 2009 21:48:59 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=DrwS0ChDVgac0FshLhGz/+88fRd8GcdZhKWurezV/aX9tblsNeng0UJWVqL5Dpu3iJ8I+kqGRjbvFBqWW6YMJgcJE8mjHvzn1zcOdxy8SDhnou3+Bleo8pFuwsSsh+5lkD737zbyrm1nnM550sc9TuUaE8o+h+wy8iiN/IxjJA8=; X-YMail-OSG: Pkc0BR0VM1n0Q3_WW5DLCkSKiZfGEd1FR4dI9iJfMnqWmF0xOFZX._cVxND5N.krusRhtBb4YfU66y3KR44OuUuBNh_fl4Rne.VBd.6mMfkJcS2L44tpTC1E1yRNSCTj5rBVHI1.IhfTOLAzJf7r8DlDUxpAKp6SQzTZXi8BXe2CpbUww5ClUx9fnMsFKRW5s7Ar9C7s3mJiAss- Received: from [88.178.196.88] by web39104.mail.mud.yahoo.com via HTTP; Sat, 31 Jan 2009 13:48:59 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Sat, 31 Jan 2009 13:48:59 -0800 (PST) From: bf To: freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <763068.66528.qm@web39104.mail.mud.yahoo.com> X-Mailman-Approved-At: Sat, 31 Jan 2009 23:14:29 +0000 Cc: giffunip@tutopia.com Subject: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bf2006a@yahoo.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2009 21:49:00 -0000 >> The issue is a lot of open source applications that it can run are >> GPL licensed. I know there was an effort to replace the core OS apps >> that were GPL with 100% BSD licensed equivalents. > The effort didn't go far enough. Why haven't we removed GNU readline ? > Pedro. I think you know very well why we haven't removed that, and other pieces of software with the GPL from the tree: no one has written and submitted suitable replacements with more permissive licenses. (Of course you could, if it really bothers you.) It may offend your sensibility, but have you really been prevented from doing something by the GPL? b. From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 22:12:37 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A3A51065707 for ; Sat, 31 Jan 2009 22:12:37 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id 5C67A8FC08 for ; Sat, 31 Jan 2009 22:12:37 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id E775F8C06F; Sat, 31 Jan 2009 16:12:36 -0600 (CST) Date: Sat, 31 Jan 2009 16:12:36 -0600 To: "Pedro F. Giffuni" Message-ID: <20090131221236.GA27303@soaustin.net> References: <779523.80455.qm@web32706.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <779523.80455.qm@web32706.mail.mud.yahoo.com> User-Agent: Mutt/1.5.13 (2006-08-11) From: linimon@lonesome.com (Mark Linimon) X-Mailman-Approved-At: Sat, 31 Jan 2009 23:44:47 +0000 Cc: Sean Cavanaugh , freebsd-current@freebsd.org Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 31 Jan 2009 22:12:38 -0000 On Sat, Jan 31, 2009 at 01:08:54PM -0800, Pedro F. Giffuni wrote: > The effort didn't go far enough. Why haven't we removed GNU readline ? Probably either because someone hasn't written a BSD-licensed one, or someone hasn't done the work to test-compile src and ports on all the appropriate architectures. mcl