This repository has been archived by the owner on Dec 4, 2020. It is now read-only.
Repeated excessive logging about unsuccessful port reset during device enumeration #283
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…up flooding syslog
|
Hi, Could u please open a bug report in bugs.freebsd.org. I think this is a pola change, due to the fact it helps your system, but for others it might hide useful information after the patch is applied. Thank you in advance. |
|
Hello I raised this on FreeBSD bug tracker: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235625 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reduce log level for message about unsuccesful port reset which ends up flooding syslog
The following sysctl configuration also helps to get rid of excessive logging but the downside that certain USB device (Create SoundBlaster) are not even getting recognized by USB hub controller.
Here is sample logging in question:
I tested it on my machine and confirmed that excessive logging disappered and my USB devices are successfully recognized and connected