On 12/07/2016 16:38, Mason wrote:
> With Eric's patch applied, I get this warning at boot:
>
> [4.668309] nb8800 26000.ethernet eth0: Link is Up - 1Gbps/Full - flow
> control rx/tx
> [4.688609] Sending DHCP requests ., OK
> [4.711935] IP-Config: Got DHCP answer from 172.27.200.1, my
On 12/07/2016 16:25, Eric Dumazet wrote:
> Could you try this debug patch ?
Note: I've been unable to trigger the warning again. Dunno what has changed...
With your patch applied, I get a warning at boot:
[4.668309] nb8800 26000.ethernet eth0: Link is Up - 1Gbps/Full - flow
control rx/tx
On Tue, 2016-07-12 at 11:53 +0200, Mason wrote:
> On 05/07/2016 17:28, Florian Fainelli wrote:
>
> > Le 05/07/2016 07:50, Mason wrote:
> >
> >> On 05/07/2016 15:33, Mason wrote:
> >>
> >>> I was testing suspend/resume sequences where the suspend operation
> >>> fails and returns without having
this warning in v4.1 and v4.4)
>
> What's going wrong here? Is it related to NFS?
>
> Here is the defconfig I'm using
> http://pastebin.ubuntu.com/19160299/
>
>
> [ 317.940133] ----[ cut here ]--------
> [ 317.944815] WARNING: CPU: 1 PID: 0 at net/ipv4
ng
http://pastebin.ubuntu.com/19160299/
Regards.
[ 317.940133] ----[ cut here ]--------
[ 317.944815] WARNING: CPU: 1 PID: 0 at net/ipv4/af_inet.c:155
inet_sock_destruct+0x1c4/0x1dc
[ 317.953223] Modules linked in:
[ 317.956305] CPU: 1 PID: 0 Comm: swapper/1 Not tainted
4.7.0-rc6-0001
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
On 05/07/2016 23:22, Florian Fainelli wrote:
> On 07/05/2016 01:26 PM, Mason wrote:
>> On 05/07/2016 18:20, Florian Fainelli wrote:
>>> On 07/05/2016 08:56 AM, Mason wrote:
On 05/07/2016 17:28, Florian Fainelli wrote:
> nb8800.c does not currently show suspend/resume hooks
On 07/05/2016 01:26 PM, Mason wrote:
> On 05/07/2016 18:20, Florian Fainelli wrote:
>> On 07/05/2016 08:56 AM, Mason wrote:
>>> On 05/07/2016 17:28, Florian Fainelli wrote:
>>>
nb8800.c does not currently show suspend/resume hooks implemented, are
you positive that when you suspend, you
On 05/07/2016 18:20, Florian Fainelli wrote:
> On 07/05/2016 08:56 AM, Mason wrote:
>> On 05/07/2016 17:28, Florian Fainelli wrote:
>>
>>> nb8800.c does not currently show suspend/resume hooks implemented, are
>>> you positive that when you suspend, you properly tear down all HW, stop
>>> transmit
On 07/05/2016 08:56 AM, Mason wrote:
> On 05/07/2016 17:28, Florian Fainelli wrote:
>
>> nb8800.c does not currently show suspend/resume hooks implemented, are
>> you positive that when you suspend, you properly tear down all HW, stop
>> transmit queues, etc. and do the opposite upon resumption?
On 05/07/2016 17:28, Florian Fainelli wrote:
> nb8800.c does not currently show suspend/resume hooks implemented, are
> you positive that when you suspend, you properly tear down all HW, stop
> transmit queues, etc. and do the opposite upon resumption?
I am currently testing the error path for
ks ... done.
>> -sh: echo: write error: Input/output error
>> [ 93.860411] nb8800 26000.ethernet eth0: Link is Up - 1Gbps/Full - flow
>> control rx/tx
>>
>> (The error message is expected, as my suspend routine returns -EIO
>> on failure.)
>>
>> I left the syst
rol rx/tx
>
> (The error message is expected, as my suspend routine returns -EIO
> on failure.)
>
> I left the system to idle at the prompt; then 5 minutes later,
> the system printed the following trace.
>
> [ 400.718491] ----[ cut here ]----
> [ 400.723175]
tem printed the following trace.
[ 400.718491] [ cut here ]
[ 400.723175] WARNING: CPU: 0 PID: 0 at net/ipv4/af_inet.c:155
inet_sock_destruct+0x1c4/0x1dc
[ 400.731582] Modules linked in:
[ 400.734689] CPU: 0 PID: 0 Comm: swapper/0 Not tainted
4.7.0-rc6-00010-gd07031bdc433
14 matches
Mail list logo
