public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: poma <pomidorabelisima@gmail.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org,
	Mailing-List fedora-kernel <kernel@lists.fedoraproject.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
	Jamal Hadi Salim <jhs@mojatatu.com>,
	Stanislaw Gruszka <sgruszka@redhat.com>,
	Josh Boyer <jwboyer@redhat.com>,
	"Justin M. Forbes" <jforbes@redhat.com>,
	Dan Williams <dcbw@redhat.com>,
	Thomas Haller <thaller@redhat.com>
Subject: Re: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280()
Date: Sun, 09 Mar 2014 00:30:14 +0100	[thread overview]
Message-ID: <531BA806.4080509@gmail.com> (raw)
In-Reply-To: <20140308123528.GA2052@electric-eye.fr.zoreil.com>

On 08.03.2014 13:35, Francois Romieu wrote:
...
> It applies fine against b01d4e68933ec23e43b1046fa35d593cefcf37d1 but
> a bug hides behind the 'start' variable. You may replace it with the
> patch below. The "netif_info(..., "frags ..." debug statement is noisy
> when enabled. Don't use it.
...

You're right!
Thanks.

These are the results with your patch:

- RTL8110s RTL-8169 S3 TEST & r8169-RTL8110s-xmit-v2.patch
https://bugzilla.redhat.com/attachment.cgi?id=872287

- r8169 RTL8110s pacchetto
https://bugzilla.redhat.com/attachment.cgi?id=872299
https://bugzilla.redhat.com/attachment.cgi?id=872299&action=diff


poma



      reply	other threads:[~2014-03-08 23:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 10:15 WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280() poma
2014-02-19  4:37 ` poma
2014-03-06 23:32   ` poma
2014-03-07 16:30     ` poma
2014-03-08  1:33       ` poma
2014-03-08 12:35         ` Francois Romieu
2014-03-08 23:30           ` poma [this message]

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=531BA806.4080509@gmail.com \
    --to=pomidorabelisima@gmail.com \
    --cc=dcbw@redhat.com \
    --cc=jforbes@redhat.com \
    --cc=jhs@mojatatu.com \
    --cc=jwboyer@redhat.com \
    --cc=kernel@lists.fedoraproject.org \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    --cc=sgruszka@redhat.com \
    --cc=thaller@redhat.com \
    /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