[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0835B3720019904CB8F7AA43166CEEB2D2E47EB4@RTITMBSV06.realtek.com.tw>
Date: Wed, 16 May 2018 10:00:09 +0000
From: Hayes Wang <hayeswang@...ltek.com>
To: Oliver Neukum <oneukum@...e.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: Hangs in r8152 connected to power management in kernels at least up v4.17-rc4
Oliver Neukum [mailto:oneukum@...e.com]
> Sent: Wednesday, May 16, 2018 4:27 PM
[...]
> >
> > Would usb_autopm_get_interface() take a long time?
> > The driver would wake the device if it has suspended.
> > I have no idea about how usb_autopm_get_interface() works, so I don't know
> how to help.
>
> Hi,
>
> it basically calls r8152_resume() and makes a control request to the
> hub. I think we are spinning in rtl8152_runtime_resume(), but where?
> It has a lot of NAPI stuff. Any suggestions on how to instrument or
> trace this?
Is rtl8152_runtime_resume() called? I don't see the name in the trace.
I guess the relative API in rtl8152_runtime_resume() are
ops->disable = rtl8153_disable;
ops->autosuspend_en = rtl8153_runtime_enable;
And I don't find any possible dead lock in rtl8152_runtime_resume().
Besides, I find a similar issue as following.
https://www.spinics.net/lists/netdev/msg493512.html
Best Regards,
Hayes
Powered by blists - more mailing lists