linux-kernel - Re: [PATCH] usbcore: Limit number of 'unable to enumerate USB device' messages

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.0810251058050.3569-100000@netrider.rowland.org>
Date:	Sat, 25 Oct 2008 10:59:19 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Larry Finger <Larry.Finger@...inger.net>
cc:	Greg KH <greg@...ah.com>, USB list <linux-usb@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] usbcore: Limit number of 'unable to enumerate USB device'
 messages

On Fri, 24 Oct 2008, Larry Finger wrote:

> Greg KH wrote:
> > 
> > The latest tree should warn you if you load the host controller drivers
> > in the wrong order, so this shouldn't really be an issue anymore, right?
> 
> I have not seen such warhings, thus I expect loading is in the proper order.
> > 
> > Like Alan said, proper log messages would be helpful here.
> 
> Agreed, but I have no idea what I should be looking for. For the moment, I have
> lots of test prints looking for the sequence of events that lead to this
> spamming of the logs.

Just build your test kernel with USB debugging enabled, and when you 
get that spamming, post the complete dmesg log.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/