From owner-freebsd-questions@FreeBSD.ORG Tue Feb 24 19:36:06 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A16D10657C9 for ; Tue, 24 Feb 2009 19:36:06 +0000 (UTC) (envelope-from prvs=pschmehl_lists=2991e1bfd@tx.rr.com) Received: from ip-relay-002.utdallas.edu (ip-relay-002.utdallas.edu [129.110.20.112]) by mx1.freebsd.org (Postfix) with ESMTP id CD0CD8FC1B for ; Tue, 24 Feb 2009 19:36:05 +0000 (UTC) (envelope-from prvs=pschmehl_lists=2991e1bfd@tx.rr.com) X-Group: RELAYLIST X-IronPort-AV: E=Sophos;i="4.38,260,1233554400"; d="scan'208";a="6967927" Received: from smtp3.utdallas.edu ([129.110.20.110]) by ip-relay-002.utdallas.edu with ESMTP; 24 Feb 2009 13:07:35 -0600 Received: from utd65257.utdallas.edu (utd65257.utdallas.edu [129.110.3.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.utdallas.edu (Postfix) with ESMTPSA id E0C008F83 for ; Tue, 24 Feb 2009 13:07:35 -0600 (CST) Date: Tue, 24 Feb 2009 19:07:35 +0000 From: Paul Schmehl To: FreeBSD Questions Message-ID: <591F97E51551F72295A54D9D@utd65257.utdallas.edu> X-Mailer: Mulberry/4.0.6 (Linux/x86) X-Munged-Reply-To: Figure it out MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: RELENG_7 != STABLE? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2009 19:36:08 -0000 I have this in my /etc/cvsupfile: *default tag=RELENG_7 Yet, when I recompiled world and kernel yesterday, I ended up with this: FreeBSD hostname.utdallas.edu 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #10: Mon Feb 23 18:15:12 CST 2009 root@utd65257.utdallas.edu:/usr/obj/usr/src/sys/GENERIC i386 I thought that tag got me the STABLE branch? Also, I can now no longer even attach a umass device (much less try to fsck or mount it.) It actually renders X unusable and eventually locks up the machine. The device is detected correctly: kernel: da0 at umass-sim0 bus 0 target 0 lun 0 kernel: umass0: on uhub5 kernel: da0 at umass-sim0 bus 0 target 0 lun 0 But I see tons of these on the console: kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT kernel: umass0: BBB reset failed, TIMEOUT Apparently the usb(1) code went from bad to worse? -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* Check the headers before clicking on Reply.