All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Gloudon <jamie.gloudon@gmail.com>
To: netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>, rl@hellgate.ch, romieu@fr.zoreil.com
Subject: Re: [BUG] via-rhine: NOHZ: local_softirq_pending 08
Date: Tue, 29 Jan 2013 23:54:19 -0400	[thread overview]
Message-ID: <51089971.132a650a.2c30.06ca@mx.google.com> (raw)
In-Reply-To: <20130130000432.GA28621@electric-eye.fr.zoreil.com>

On Wed, Jan 30, 2013 at 01:04:32AM +0100, Francois Romieu wrote:
> David Miller <davem@davemloft.net> :
> [...]
> > I don't think you can't keep using dev_kfree_skb_irq() there.
> > 
> > Francois any objections to this patch?
> 
> None.
> 
> I have almost surely broken via-rhine with NOHZ as I broke the r8169
> driver before 7dbb491878a2c51d372a8890fa45a8ff80358af1. Something like
> the patch below could be needed as well (quick shot before bed time
> and ~24h delay if Jamie wants to try something now).
> 
> diff --git a/drivers/net/ethernet/via/via-rhine.c b/drivers/net/ethernet/via/via-rhine.c
> index 7992b3e..5c7e900 100644
> --- a/drivers/net/ethernet/via/via-rhine.c
> +++ b/drivers/net/ethernet/via/via-rhine.c
> @@ -2010,11 +2010,7 @@ static void rhine_slow_event_task(struct work_struct *work)
>  	if (intr_status & IntrPCIErr)
>  		netif_warn(rp, hw, dev, "PCI error\n");
>  
> -	napi_disable(&rp->napi);
> -	rhine_irq_disable(rp);
> -	/* Slow and safe. Consider __napi_schedule as a replacement ? */
> -	napi_enable(&rp->napi);
> -	napi_schedule(&rp->napi);
> +	iowrite16(RHINE_EVENT & 0xffff, rp->base + IntrEnable);
>  
>  out_unlock:
>  	mutex_unlock(&rp->task_lock);

Francois's patch fixed the issue for me. thanks!

Regards,
Jamie Gloudon

      parent reply	other threads:[~2013-01-30  3:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-24  0:08 [BUG] via-rhine: NOHZ: local_softirq_pending 08 Jamie Gloudon
2013-01-24  1:04 ` Jamie Gloudon
2013-01-29 22:47 ` David Miller
2013-01-30  0:04   ` Francois Romieu
2013-01-30  3:53     ` David Miller
2013-01-30  4:00       ` Jamie Gloudon
2013-01-30  3:54     ` Jamie Gloudon [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=51089971.132a650a.2c30.06ca@mx.google.com \
    --to=jamie.gloudon@gmail.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=rl@hellgate.ch \
    --cc=romieu@fr.zoreil.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.