Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753531AbYKGBzd (ORCPT ); Thu, 6 Nov 2008 20:55:33 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751143AbYKGBzV (ORCPT ); Thu, 6 Nov 2008 20:55:21 -0500 Received: from mx2.redhat.com ([66.187.237.31]:50723 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750814AbYKGBzU (ORCPT ); Thu, 6 Nov 2008 20:55:20 -0500 Date: Thu, 6 Nov 2008 18:54:11 -0700 From: Pete Zaitcev To: Alan Stern Cc: Norbert Preining , Mattia Dongili , Kernel development list , USB list Subject: Re: usb device not showing up Message-Id: <20081106185411.144984ab.zaitcev@redhat.com> In-Reply-To: References: <20081106171958.GA17270@gamma.logic.tuwien.ac.at> Organization: Red Hat, Inc. Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 779 Lines: 19 On Thu, 6 Nov 2008 14:34:53 -0500 (EST), Alan Stern wrote: > I have to wonder... Did you remove any part of the trace? Did usbmon > malfunction? Did parts of the initialization for those two buses > really get skipped (I can't imagine how)? > > Pete, any ideas? It is possible for usbmon to lose events. There's a counter to monitor it, in 0s file. I do not commonly run across such problems, but it can happen. If it's a problem, one can try to bump the limits way higher, if RAM allows. -- Pete -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/