diff options
| author |   Chun-Hao Lin <hau@realtek.com> | 2016-02-24 14:18:42 +0800 |
|---|---|---|
| committer |   David S. Miller <davem@davemloft.net> | 2016-02-25 16:17:45 -0500 |
| commit | f09cf4b7832d029fb22d8f476eac12fc27dde61f (patch) | |
| tree | d21bd5a9bb76d2d0a6f0da759b779d111dc06b9d /.gitignore | |
| parent | net: fix bridge multicast packet checksum validation (diff) | |
| download | linux-dev-f09cf4b7832d029fb22d8f476eac12fc27dde61f.tar.xz linux-dev-f09cf4b7832d029fb22d8f476eac12fc27dde61f.zip | |
r8169:fix "rtl_counters_cond == 1 (loop: 1000, delay: 10)" log spam.
There will be a log spam when there is no cable plugged. Please refer to
following links. https://bugzilla.kernel.org/show_bug.cgi?id=104351
https://bugzilla.kernel.org/show_bug.cgi?id=107421
This issue is caused by runtime power management. When there is no cable
plugged, the driver will be suspend (runtime suspend) by OS and NIC will be
put into the D3 state. During this time, if OS call rtl8169_get_stats64()
to dump tally counter, because NIC is in D3 state, the register value read
by driver will return all 0xff. This will let driver think tally counter
flag is not toggled and then sends the warning message "rtl_counters_cond
== 1 (loop: 1000, delay: 10)" to kernel log.
For fixing this issue, 1.add checking driver's pm runtime status in
rtl8169_get_stats64(). 2.dump tally counter before going runtime suspend
for counter accuracy in runtime suspend.
Signed-off-by: Chunhao Lin <hau@realtek.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions