From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 19:56:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE09916A4CE for ; Mon, 4 Oct 2004 19:56:38 +0000 (GMT) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6BCD43D1D for ; Mon, 4 Oct 2004 19:56:38 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id E0369C4AB; Mon, 4 Oct 2004 15:56:37 -0400 (EDT) Received: by canoe.dclg.ca (Postfix, from userid 101) id DA4051D1CAA; Mon, 4 Oct 2004 15:56:33 -0400 (EDT) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16737.43761.839340.382960@canoe.dclg.ca> Date: Mon, 4 Oct 2004 15:56:33 -0400 To: "M. Warner Losh" In-Reply-To: <20041004.115442.84363176.imp@bsdimp.com> References: <16733.37521.568515.842497@canoe.dclg.ca> <20041002.194515.99052407.imp@bsdimp.com> <16737.32607.772875.17590@canoe.dclg.ca> <20041004.115442.84363176.imp@bsdimp.com> X-Mailer: VM 7.17 under 21.5 (beta17) "chayote" (+CVS-20040321) XEmacs Lucid cc: freebsd-current@FreeBSD.ORG cc: dgilbert@dclg.ca Subject: Re: USB hub issue adendum. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: 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, 04 Oct 2004 19:56:39 -0000 >>>>> "M" == M Warner Losh writes: M> Sicne it isn't the same crash, I think I need more information M> about what it is you are seeing. Let's start there. What is the M> random corruptuion that you were seeing? I believe I posted it back a week or two ago to the list. Here's the previous email: http://lists.freebsd.org/pipermail/freebsd-current/2004-September/037524.html Now... this may be a tough bug as it has appeared and disappeared with cvsups dating back well into the summer. The exact form of the crash can be different --- which leads me to think that it's some form of random corruption. At one point, the crash only happened with a certain sequence of events, then another cvsup and it would happen for this hub disconnecting, but not my 4 port, then another cvsup and no crashes, then another cvsup and the 4 port would cause a crash, etc. So far, the crashes have been hard and have not allowed a dump to occur. Since the machine's almost always in X, DDB hasn't been helpful, either. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================