Netdev List
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	netdev@vger.kernel.org, linux-sh@vger.kernel.org,
	Simon Horman <horms@verge.net.au>,
	Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH] sh_eth: r8a7790: Handle the RFE (Receive FIFO overflow Error) interrupt
Date: Tue, 30 Jul 2013 16:20:10 +0200	[thread overview]
Message-ID: <4760883.hI1JN8gopV@avalon> (raw)
In-Reply-To: <51F7CADE.5070801@cogentembedded.com>

Hi Sergei,

On Tuesday 30 July 2013 18:17:02 Sergei Shtylyov wrote:
> On 30-07-2013 4:08, Laurent Pinchart wrote:
> > The RFE interrupt is enabled for the r8a7790 but isn't handled,
> > resulting in the interrupts core noticing unhandled interrupts, and
> > eventually disabling the ethernet IRQ.
> > 
> > Fix it by adding RFE to the bitmask of error interrupts to be handled
> > for r8a7790.
> 
> So, Simon hasn't synced his patch to my late bug fix in 3.10... Did this
> patch help you with your NFS boot issue, Laurent?

Yes, it fixes the "disabling interrupt, nobody cared" problem. I still have 
intermittent NFS issues, but at least I can now boot.

> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2013-07-30 14:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30  0:08 [PATCH] sh_eth: r8a7790: Handle the RFE (Receive FIFO overflow Error) interrupt Laurent Pinchart
2013-07-30  2:10 ` Simon Horman
2013-07-30 14:17 ` Sergei Shtylyov
2013-07-30 14:20   ` Laurent Pinchart [this message]
2013-07-30 14:47     ` Sergei Shtylyov
2013-09-12 19:45     ` Sergei Shtylyov
2013-07-31  0:32   ` Simon Horman
2013-07-30 20:41 ` Sergei Shtylyov

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=4760883.hI1JN8gopV@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=horms@verge.net.au \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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