Bug 1344757
Summary: | NetworkManager warning/error on T460s/p during suspend | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Oliver Ilian <oliver> |
Component: | NetworkManager | Assignee: | Thomas Haller <thaller> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | aloughla, atragler, bgalvani, lrintel, oliver, rkhan, thaller, vbenes |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | NetworkManager-1.4.0-0.5.beta1.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-03 19:22:45 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Comment 2
Thomas Haller
2016-06-14 14:51:08 UTC
Yes, it is 1.0.6-29 of rhel-7.2 Hi Oliver, Can you still reproduce this easily? Could you enable debug-logging and reproduce it? (do that, by configuring /etc/NetworkManager/NetworkManager.conf with [logging] level=TRACE followed by `systemctl restart NetworkManager`). Is the use of kernel 3.10.0-429.el7.BZ1332712_usbv4.6 kernel essential to reproduce this? Thank you. I can still see it with 3.10.0-461.el7.x86_64 uname -a Linux dhcp-64-242.muc.redhat.com 3.10.0-461.el7.x86_64 #1 SMP Mon Jul 4 09:36:53 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux log file with TRACE enabled attached. created with : journalctl | grep -A 50 -B 200 wpa_supplicant1 thanks Oliver. the <warn> message is bogus and upstream already suppresses it: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=6596ceee1442d37ea715be06f8a65195082db627 Note, that the logging message is an annoyance, but harmless. As we rebase NetworkManager with rhel-7.3, this bug will be fixed automatically. Cannot see these errors anymore. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-2581.html |