[Bug 1694675] Re: After pm-suspend and resume, can't use rtl8169 NIC for networking

2017-07-05 Thread Seyeong Kim 
Thanks a lot Kai-Heng, it fixes this. no issue after installing it

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694675

Title:
  After pm-suspend and resume, can't use rtl8169 NIC for networking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694675/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1694675] Re: After pm-suspend and resume, can't use rtl8169 NIC for networking

2017-06-28 Thread Kai-Heng Feng 
Give "r8168-dkms" a try:
$sudo apt install r8168-dkms

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694675

Title:
  After pm-suspend and resume, can't use rtl8169 NIC for networking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694675/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1694675] Re: After pm-suspend and resume, can't use rtl8169 NIC for networking

2017-06-28 Thread Seyeong Kim 
hmm. I got this issue even i didn't run pm-suspend after running machine
some hours or days.

then I roll back to 4.4, it happens as well without pm-suspend..

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694675

Title:
  After pm-suspend and resume, can't use rtl8169 NIC for networking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694675/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1694675] Re: After pm-suspend and resume, can't use rtl8169 NIC for networking

2017-06-22 Thread Kai-Heng Feng 
What if you use normal suspend?
$ systemctl suspend
... instead of pm-suspend?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694675

Title:
  After pm-suspend and resume, can't use rtl8169 NIC for networking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694675/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1694675] Re: After pm-suspend and resume, can't use rtl8169 NIC for networking

2017-06-22 Thread Seyeong Kim 
rc6 seems upstream..

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694675

Title:
  After pm-suspend and resume, can't use rtl8169 NIC for networking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694675/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1694675] Re: After pm-suspend and resume, can't use rtl8169 NIC for networking

2017-06-21 Thread Seyeong Kim 
hmm 4.12.0-041200rc6 has still issue.

I'm going to try upstream one

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694675

Title:
  After pm-suspend and resume, can't use rtl8169 NIC for networking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694675/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1694675] Re: After pm-suspend and resume, can't use rtl8169 NIC for networking

2017-05-31 Thread Kai-Heng Feng 
Does latest mainline kernel have the issue?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694675

Title:
  After pm-suspend and resume, can't use rtl8169 NIC for networking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694675/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1694675] Re: After pm-suspend and resume, can't use rtl8169 NIC for networking

2017-05-31 Thread Seyeong Kim 
apport information

** Tags added: apport-collected xenial

** Description changed:

  [Impact]
  
  After pm-suspend and resume, can't use rtl8169 NIC for networking
  
  [TestCase]
  
  you need rtl8192 NIC on your machine
  
  reproducer
  
  1. pm-suspend
  2. resume it
  3. you can see a lot of err msgs in kern.log
     and network connection keep changing in and out
  
  There are around 4~5 commits from Chun-Hao Lin 
  
  but it doesn't seem to fix this issue ( 100% sure, just cherrypicked
  them but failed )
  
  hwe kernel ( -edge as well ) didn't help
  
  [Other info]
  
  I can't test the other releases for this issue
  
  
  please refer to below msgs
  
  Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0
  20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27
  15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62)
  
  May 31 09:22:44 mnode01 kernel: [  361.994034] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:22:44 mnode01 kernel: [  361.994093] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:23:02 mnode01 kernel: [  379.994504] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:23:02 mnode01 kernel: [  379.994564] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:23:10 mnode01 kernel: [  388.154990] r8169 :06:00.0 enp6s0: 
rtl_counters_cond == 1 (loop: 1000, delay: 10).
  May 31 09:23:10 mnode01 kernel: [  388.167721] r8169 :06:00.0 enp6s0: 
rtl_counters_cond == 1 (loop: 1000, delay: 10).
  May 31 09:23:12 mnode01 kernel: [  389.948606] r8169 :06:00.0 enp6s0: 
rtl_counters_cond == 1 (loop: 1000, delay: 10).
  May 31 09:23:12 mnode01 kernel: [  389.961218] r8169 :06:00.0 enp6s0: 
rtl_counters_cond == 1 (loop: 1000, delay: 10).
  May 31 09:23:20 mnode01 kernel: [  398.002922] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:23:20 mnode01 kernel: [  398.002978] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:23:32 mnode01 kernel: [  409.995280] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:23:32 mnode01 kernel: [  409.995337] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:23:44 mnode01 kernel: [  421.995590] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:23:44 mnode01 kernel: [  421.995649] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:23:56 mnode01 kernel: [  433.04] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:23:56 mnode01 kernel: [  433.65] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:24:08 mnode01 kernel: [  446.000178] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:24:08 mnode01 kernel: [  446.000227] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:24:20 mnode01 kernel: [  458.004472] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:24:20 mnode01 kernel: [  458.004532] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:24:31 mnode01 kernel: [  469.033314] r8169 :06:00.0 enp6s0: 
rtl_counters_cond == 1 (loop: 1000, delay: 10).
  May 31 09:24:31 mnode01 kernel: [  469.046073] r8169 :06:00.0 enp6s0: 
rtl_counters_cond == 1 (loop: 1000, delay: 10).
  May 31 09:24:31 mnode01 kernel: [  469.058512] r8169 :06:00.0 enp6s0: 
rtl_counters_cond == 1 (loop: 1000, delay: 10).
  May 31 09:24:32 mnode01 kernel: [  470.000793] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:24:32 mnode01 kernel: [  470.000851] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:24:44 mnode01 kernel: [  481.997147] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:24:44 mnode01 kernel: [  481.997206] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:24:56 mnode01 kernel: [  494.001403] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:24:56 mnode01 kernel: [  494.001453] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:25:08 mnode01 kernel: [  505.997768] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:25:08 mnode01 kernel: [  505.997826] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:25:20 mnode01 kernel: [  518.002082] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:25:20 mnode01 kernel: [  518.002141] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:25:32 mnode01 kernel: [  530.002331] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:25:32 mnode01 kernel: [  530.002379] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:25:38 mnode01 kernel: [  536.588896] SGI XFS with ACLs, security 
attributes, realtime, no debug enabled
  May 31 09:25:39 mnode01 kernel: [  536.637037] JFS: nTxBlock = 8192, nTxLock 
= 65536
  May 31 09:25:39 mnode01 kernel: [  536.712978] ntfs: driver 2.1.32 [Flags: 
R/O MODULE].
  May

[Bug 1694675] Re: After pm-suspend and resume, can't use rtl8169 NIC for networking

2017-05-31 Thread Seyeong Kim 
** Description changed:

- a lot of err msgs in kern.log
+ [Impact]
  
- and network connection keep changing in and out
+ After pm-suspend and resume, can't use rtl8169 NIC for networking
  
+ [TestCase]
+ 
+ you need rtl8192 NIC on your machine
+ 
+ reproducer
+ 
+ 1. pm-suspend
+ 2. resume it
+ 3. you can see a lot of err msgs in kern.log
+and network connection keep changing in and out
+ 
+ There are around 4~5 commits from Chun-Hao Lin 
+ 
+ but it doesn't seem to fix this issue ( 100% sure, just cherrypicked
+ them but failed )
+ 
+ hwe kernel ( -edge as well ) didn't help
+ 
+ [Other info]
  please refer to below msgs
  
  Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0
  20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27
  15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62)
- 
  
  May 31 09:22:44 mnode01 kernel: [  361.994034] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:22:44 mnode01 kernel: [  361.994093] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:23:02 mnode01 kernel: [  379.994504] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:23:02 mnode01 kernel: [  379.994564] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:23:10 mnode01 kernel: [  388.154990] r8169 :06:00.0 enp6s0: 
rtl_counters_cond == 1 (loop: 1000, delay: 10).
  May 31 09:23:10 mnode01 kernel: [  388.167721] r8169 :06:00.0 enp6s0: 
rtl_counters_cond == 1 (loop: 1000, delay: 10).
  May 31 09:23:12 mnode01 kernel: [  389.948606] r8169 :06:00.0 enp6s0: 
rtl_counters_cond == 1 (loop: 1000, delay: 10).
  May 31 09:23:12 mnode01 kernel: [  389.961218] r8169 :06:00.0 enp6s0: 
rtl_counters_cond == 1 (loop: 1000, delay: 10).
  May 31 09:23:20 mnode01 kernel: [  398.002922] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:23:20 mnode01 kernel: [  398.002978] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:23:32 mnode01 kernel: [  409.995280] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:23:32 mnode01 kernel: [  409.995337] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:23:44 mnode01 kernel: [  421.995590] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:23:44 mnode01 kernel: [  421.995649] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:23:56 mnode01 kernel: [  433.04] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:23:56 mnode01 kernel: [  433.65] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:24:08 mnode01 kernel: [  446.000178] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:24:08 mnode01 kernel: [  446.000227] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:24:20 mnode01 kernel: [  458.004472] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:24:20 mnode01 kernel: [  458.004532] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:24:31 mnode01 kernel: [  469.033314] r8169 :06:00.0 enp6s0: 
rtl_counters_cond == 1 (loop: 1000, delay: 10).
  May 31 09:24:31 mnode01 kernel: [  469.046073] r8169 :06:00.0 enp6s0: 
rtl_counters_cond == 1 (loop: 1000, delay: 10).
  May 31 09:24:31 mnode01 kernel: [  469.058512] r8169 :06:00.0 enp6s0: 
rtl_counters_cond == 1 (loop: 1000, delay: 10).
  May 31 09:24:32 mnode01 kernel: [  470.000793] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:24:32 mnode01 kernel: [  470.000851] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:24:44 mnode01 kernel: [  481.997147] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:24:44 mnode01 kernel: [  481.997206] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:24:56 mnode01 kernel: [  494.001403] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:24:56 mnode01 kernel: [  494.001453] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:25:08 mnode01 kernel: [  505.997768] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:25:08 mnode01 kernel: [  505.997826] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:25:20 mnode01 kernel: [  518.002082] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:25:20 mnode01 kernel: [  518.002141] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:25:32 mnode01 kernel: [  530.002331] r8169 :06:00.0 enp6s0: 
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
  May 31 09:25:32 mnode01 kernel: [  530.002379] r8169 :06:00.0 enp6s0: 
link up
  May 31 09:25:38 mnode01 kernel: [  536.588896] SGI XFS with ACLs, security 
attributes, realtime, no debug enabled
  May 31 09:25:39 mnode01 kernel: [  536.637037] JFS: nTxBlock = 8192, nTxLock 
= 65536
  May 31 09:25:39 mnode01 kernel: [  536.712978] ntfs: driver 2.1.32 [Flags: 
R/O MODULE].
  May 31 09:25:39 mnode01 kernel: [

[Bug 1694675] Re: After pm-suspend and resume, can't use rtl8169 NIC for networking

2017-05-31 Thread Seyeong Kim 
not 100% sure latest release doesn't have this issue yet

** Changed in: linux (Ubuntu)
   Status: Fix Released => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694675

Title:
  After pm-suspend and resume, can't use rtl8169 NIC for networking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694675/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1694675] Re: After pm-suspend and resume, can't use rtl8169 NIC for networking

2017-05-31 Thread Seyeong Kim 
@kaihengfeng

No, I can't.

changed subject

** Summary changed:

- r8169:fix "rtl_counters_cond == 1 (loop: 1000, delay: 10)" log spam.
+ After pm-suspend and resume, can't use rtl8169 NIC for networking

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694675

Title:
  After pm-suspend and resume, can't use rtl8169 NIC for networking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694675/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs