Re: WARNING: CPU: 0 PID: 0 at net/ipv4/af_inet.c:155 inet_sock_destruct+0x1c4/0x1dc

From	Florian Fainelli <f.fainelli@gmail.com>
Newsgroups	linux.kernel
Subject	Re: WARNING: CPU: 0 PID: 0 at net/ipv4/af_inet.c:155 inet_sock_destruct+0x1c4/0x1dc
Date	2016-07-06 00:00 +0200
Message-ID	<rRGxP-6u-1@gated-at.bofh.it> (permalink)
References	(3 earlier) <rRAVt-4Ms-39@gated-at.bofh.it> <rRBov-5cR-45@gated-at.bofh.it> <rRF8J-7G3-9@gated-at.bofh.it> <rRG4N-8lJ-9@gated-at.bofh.it> <rRGxP-6u-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 07/05/2016 02:51 PM, Mason wrote:
>>> Therefore, loss of context cannot possibly explain the
>>> warning I am seeing.
>>
>> No, but if you go all the way down to trying to suspend and the last
>> step is the firmware failing, anything you have suspended needs to be
>> unwinded, for your ethernet driver that means that you went through a
>> successful suspend then resume cycle even if it failed down later when
>> the platform attempted to suspend.
> 
> So it is the driver's responsibility to "shut down" on resume?

It is the driver responsibility to know how to suspend and resume a
device it manages, and it does that by implementing appropriate
suspend/resume callbacks.

> (I had the vague impression that the suspend framework would
> "disable" the device through the appropriate callback.)

The suspend framework knows which drivers implement suspend/resume and
calls them appropriately (based on parenting/bus hierarchy), but it
won't automatigally do anything because there is no such thing as magic
when it comes to suspending hardware, this needs to be a controlled
sequence.
-- 
Florian

Thread

WARNING: CPU: 0 PID: 0 at net/ipv4/af_inet.c:155  inet_sock_destruct+0x1c4/0x1dc Mason <slash.tmp@free.fr> - 2016-07-05 15:40 +0200
  Re: WARNING: CPU: 0 PID: 0 at net/ipv4/af_inet.c:155  inet_sock_destruct+0x1c4/0x1dc Mason <slash.tmp@free.fr> - 2016-07-05 17:00 +0200
    Re: WARNING: CPU: 0 PID: 0 at net/ipv4/af_inet.c:155  inet_sock_destruct+0x1c4/0x1dc Florian Fainelli <f.fainelli@gmail.com> - 2016-07-05 17:30 +0200
      Re: WARNING: CPU: 0 PID: 0 at net/ipv4/af_inet.c:155  inet_sock_destruct+0x1c4/0x1dc Mason <slash.tmp@free.fr> - 2016-07-05 18:00 +0200
        Re: WARNING: CPU: 0 PID: 0 at net/ipv4/af_inet.c:155  inet_sock_destruct+0x1c4/0x1dc Florian Fainelli <f.fainelli@gmail.com> - 2016-07-05 18:30 +0200
          Re: WARNING: CPU: 0 PID: 0 at net/ipv4/af_inet.c:155  inet_sock_destruct+0x1c4/0x1dc Mason <slash.tmp@free.fr> - 2016-07-05 22:30 +0200
            Re: WARNING: CPU: 0 PID: 0 at net/ipv4/af_inet.c:155  inet_sock_destruct+0x1c4/0x1dc Florian Fainelli <f.fainelli@gmail.com> - 2016-07-05 23:30 +0200
              Re: WARNING: CPU: 0 PID: 0 at net/ipv4/af_inet.c:155  inet_sock_destruct+0x1c4/0x1dc Florian Fainelli <f.fainelli@gmail.com> - 2016-07-06 00:00 +0200
              Re: WARNING: CPU: 0 PID: 0 at net/ipv4/af_inet.c:155  inet_sock_destruct+0x1c4/0x1dc Mason <slash.tmp@free.fr> - 2016-07-06 00:00 +0200

csiph-web