mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Network Development <netdev@vger.kernel.org>
Subject: Re: 4.9-rc7: (forcedeth?) BUG: sleeping function called from invalid context at kernel/irq/manage.c:110
Date: Tue, 29 Nov 2016 23:55:12 +0200 (EET)	[thread overview]
Message-ID: <alpine.LRH.2.20.1611292352270.31348@math.ut.ee> (raw)
In-Reply-To: <CA+55aFwUFPLbcqpoccKXHsGj_80ANaMwCSgwTUqgxMFmNRHkaQ@mail.gmail.com>

> On Nov 29, 2016 11:58 AM, "Eric Dumazet" <eric.dumazet@gmail.com> wrote:
> >
> > nv_do_nic_poll() is simply buggy and needs a fix.
> >
> > synchronize_irq() can sleep.
> 
> Yes, but why did it start showing up now? None of this has changed as far as I can see?

Found one thing that changed - compiler from 6.2.0-9 to 6.2.1-5 and 
binutils too in debian unstable (explicitly upgraded to get fix to the 
binutils bug that broke 64-bit kernels).

> Is it just timing and the transmit queue being busy? Perhaps due to the sheer size of messages? Meelis does seem to have a ton of debugging enabled..

Well, the dmesg is not too verbose but when I debugged some earlier 
problem, netconsole and many other debugging options were left on.

-- 
Meelis Roos (mroos@linux.ee)

  parent reply	other threads:[~2016-11-29 20:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 20:26 Meelis Roos
2016-11-29 19:11 ` Linus Torvalds
2016-11-29 21:16   ` Meelis Roos
2016-11-29 19:50     ` Linus Torvalds
2016-11-29 19:58     ` Eric Dumazet
     [not found]       ` <CA+55aFwUFPLbcqpoccKXHsGj_80ANaMwCSgwTUqgxMFmNRHkaQ@mail.gmail.com>
2016-11-29 21:55         ` Meelis Roos [this message]
2016-11-29 23:00         ` Eric Dumazet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LRH.2.20.1611292352270.31348@math.ut.ee \
    --to=mroos@linux.ee \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®