Bug ID 1186194
Summary Many processes and up in D state after system resume (5.12.3-1-default, git 25d4ec7)
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Kernel
Assignee kernel-bugs@opensuse.org
Reporter lpechacek@suse.com
QA Contact qa-bugs@suse.de
CC oneukum@suse.com
Found By ---
Blocker ---

Created attachment 849440 [details]
Output of SysRq-T

I'm using a Dell laptop (Inspiron 7373) with a USB ethernet adapter (17ef:7205
Lenovo Thinkpad LAN, driver r8152). Sometimes, after resume, network-related
utilities (e.g. ip, ping) freeze in D state. No communication over IP networks
is possible. Attached is SysRq-T from the malfunctioning state.

From my POV, the following stand out:

May 18 11:00:34 fmn kernel: task:teams           state:D stack:    0 pid:  316
ppid:  3234 flags:0x00000000
May 18 11:00:34 fmn kernel: Call Trace:
May 18 11:00:34 fmn kernel:  __schedule+0x2ee/0x950
May 18 11:00:34 fmn kernel:  schedule+0x46/0xb0
May 18 11:00:34 fmn kernel:  rpm_resume+0x19c/0x7b0
May 18 11:00:34 fmn kernel:  ? wait_woken+0x80/0x80
May 18 11:00:34 fmn kernel:  rpm_resume+0x2e7/0x7b0
May 18 11:00:34 fmn kernel:  ? kernfs_fop_open+0x2a8/0x3a0
May 18 11:00:34 fmn kernel:  __pm_runtime_resume+0x4a/0x80
May 18 11:00:34 fmn kernel:  usb_autopm_get_interface+0x18/0x50 [usbcore]
May 18 11:00:34 fmn kernel:  rtl8152_get_link_ksettings+0x27/0x80 [r8152]
May 18 11:00:34 fmn kernel:  speed_show+0x6e/0xb0
May 18 11:00:34 fmn kernel:  dev_attr_show+0x19/0x40
May 18 11:00:34 fmn kernel:  sysfs_kf_seq_show+0xa6/0xe0
May 18 11:00:34 fmn kernel:  seq_read_iter+0x1e1/0x510
May 18 11:00:34 fmn kernel:  new_sync_read+0x115/0x1a0
May 18 11:00:34 fmn kernel:  vfs_read+0x14b/0x1a0
May 18 11:00:34 fmn kernel:  ksys_read+0x5f/0xe0
May 18 11:00:34 fmn kernel:  do_syscall_64+0x33/0x80
May 18 11:00:34 fmn kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xae

AND

May 18 11:00:34 fmn kernel: task:kworker/3:2     state:D stack:    0 pid:23489
ppid:     2 flags:0x00004000
May 18 11:00:34 fmn kernel: Workqueue: pm pm_runtime_work
May 18 11:00:34 fmn kernel: Call Trace:
May 18 11:00:34 fmn kernel:  __schedule+0x2ee/0x950
May 18 11:00:34 fmn kernel:  schedule+0x46/0xb0
May 18 11:00:34 fmn kernel:  schedule_timeout+0x8b/0x140
May 18 11:00:34 fmn kernel:  ? __next_timer_interrupt+0x100/0x100
May 18 11:00:34 fmn kernel:  msleep+0x2a/0x40
May 18 11:00:34 fmn kernel:  napi_disable+0x2b/0x70
May 18 11:00:34 fmn kernel:  rtl8152_suspend+0x2ad/0x340 [r8152]
May 18 11:00:34 fmn kernel:  usb_suspend_both+0x9d/0x230 [usbcore]
May 18 11:00:34 fmn kernel:  usb_runtime_suspend+0x2b/0x70 [usbcore]
May 18 11:00:34 fmn kernel:  ? usb_autoresume_device+0x50/0x50 [usbcore]
May 18 11:00:34 fmn kernel:  __rpm_callback+0x81/0x140
May 18 11:00:34 fmn kernel:  rpm_callback+0x4f/0x70
May 18 11:00:34 fmn kernel:  ? usb_autoresume_device+0x50/0x50 [usbcore]
May 18 11:00:34 fmn kernel:  rpm_suspend+0x147/0x6f0
May 18 11:00:34 fmn kernel:  ? __switch_to+0x26f/0x450
May 18 11:00:34 fmn kernel:  pm_runtime_work+0x8e/0x90
May 18 11:00:34 fmn kernel:  process_one_work+0x1df/0x370
May 18 11:00:34 fmn kernel:  worker_thread+0x50/0x400
May 18 11:00:34 fmn kernel:  ? process_one_work+0x370/0x370
May 18 11:00:34 fmn kernel:  kthread+0x11b/0x140
May 18 11:00:34 fmn kernel:  ? __kthread_bind_mask+0x60/0x60
May 18 11:00:34 fmn kernel:  ret_from_fork+0x22/0x30


You are receiving this mail because: