summaryrefslogtreecommitdiff
path: root/net/wireless
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2017-01-29 14:25:17 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2017-01-29 14:25:17 -0800
commit566cf877a1fcb6d6dc0126b076aad062054c2637 (patch)
treec6d5b5de629b0adfaced9d629ed06777c6b6a26c /net/wireless
parent39cb2c9a316e77f6dfba96c543e55b6672d5a37e (diff)
Linux 4.10-rc6
Diffstat (limited to 'net/wireless')
0 files changed, 0 insertions, 0 deletions
d on a multicast address that we are not subscribed to. Because the hardware initiates the Rx timestamp as soon as possible, it will latch an RXTIME register, but then drop the packet. This results in users being confused by the message as they are not expecting to see dropped timestamp messages unless their application also indicates that timestamps were missing. Resolve this by reducing the severity and frequency of the displayed message. We now only print the message if 3 or 4 of the RXTIME registers are stalled and get cleared within the same watchdog event. This ensures that the common case does not constantly display the message. Additionally, since the message is likely not as meaningful to most users, reduce the message to a dev_dbg instead of a dev_warn. Users can still get a count of the number of timestamps dropped by reading the ethtool statistics value, if necessary. Change-ID: I35494442226a444c418dfb4f91a3070d06c8435c Signed-off-by: Jacob Keller <jacob.e.keller@intel.com> Tested-by: Andrew Bowers <andrewx.bowers@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat