Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753254AbdGETx7 (ORCPT <rfc822;w@1wt.eu>);
        Wed, 5 Jul 2017 15:53:59 -0400
Received: from mga06.intel.com ([134.134.136.31]:51651 "EHLO mga06.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1753179AbdGETxv (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 5 Jul 2017 15:53:51 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.40,313,1496127600"; 
   d="scan'208";a="107447614"
Date: Wed, 5 Jul 2017 22:53:46 +0300
From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= <ville.syrjala@linux.intel.com>
To: Michal Kubecek <mkubecek@suse.cz>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
        Eric Dumazet <edumazet@google.com>,
        "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org, Francois Romieu <romieu@fr.zoreil.com>,
        whiteheadm@acm.org
Subject: Re: [regression v4.11] 617f01211baf ("8139too: use
 napi_complete_done()")
Message-ID: <20170705195345.GW12629@intel.com>
References: <20170407181754.GL30290@intel.com>
 <1491590329.10124.86.camel@edumazet-glaptop3.roam.corp.google.com>
 <20170619144445.GA27063@unicorn.suse.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20170619144445.GA27063@unicorn.suse.cz>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 2510
Lines: 64

On Mon, Jun 19, 2017 at 04:44:45PM +0200, Michal Kubecek wrote:
> On Fri, Apr 07, 2017 at 11:38:49AM -0700, Eric Dumazet wrote:
> > On Fri, 2017-04-07 at 21:17 +0300, Ville Syrj?l? wrote:
> > > Hi,
> > > 
> > > My old P3 laptop started to die on me in the middle of larger compile
> > > jobs (using distcc) after v4.11-rc<something>. I bisected the problem
> > > to 617f01211baf ("8139too: use napi_complete_done()").
> > > 
> > > Unfortunately I wasn't able to capture a full oops as the machine doesn't
> > > have serial and ramoops failed me. I did get one partial oops on vgacon
> > > which showed rtl8139_poll() being involved (EIP was around
> > > _raw_spin_unlock_irqrestore() supposedly), so seems to agree with my
> > > bisect result.
> > > 
> > > So maybe some kind of nasty thing going between the hard irq and
> > > softirq? Perhaps UP related? I tried to stare at the locking around
> > > rtl8139_poll() for a while but it looked mostly sane to me.
> > > 
> > 
> > Thanks a lot for the detective work, I am so sorry for this !
> > 
> > Could you try the following patch ?
> > 
> > I do not really see what could be wrong, the code should run just fine
> > on UP.
> > 
> > Thanks.
> > 
> > diff --git a/drivers/net/ethernet/realtek/8139too.c b/drivers/net/ethernet/realtek/8139too.c
> > index 89631753e79962d91456d93b71929af768917da1..cd2dbec331dd796f5296cd378561b3443f231673 100644
> > --- a/drivers/net/ethernet/realtek/8139too.c
> > +++ b/drivers/net/ethernet/realtek/8139too.c
> > @@ -2135,11 +2135,12 @@ static int rtl8139_poll(struct napi_struct *napi, int budget)
> >  	if (likely(RTL_R16(IntrStatus) & RxAckBits))
> >  		work_done += rtl8139_rx(dev, tp, budget);
> >  
> > -	if (work_done < budget && napi_complete_done(napi, work_done)) {
> > +	if (work_done < budget) {
> >  		unsigned long flags;
> >  
> >  		spin_lock_irqsave(&tp->lock, flags);
> > -		RTL_W16_F(IntrMask, rtl8139_intr_mask);
> > +		if (napi_complete_done(napi, work_done))
> > +			RTL_W16_F(IntrMask, rtl8139_intr_mask);
> >  		spin_unlock_irqrestore(&tp->lock, flags);
> >  	}
> >  	spin_unlock(&tp->rx_lock);
> 
> Eric,
> 
> we have a bugreport of what seems to be the same problem:
> 
>   https://bugzilla.suse.com/show_bug.cgi?id=1042208
> 
> Do you plan to submit the patch above or is the conclusion that this is
> rather a hardware problem?

Could someone please push this patch forward? My machine just died again
with a fresh kernel because I forgot that I still need this patch.

-- 
Ville Syrj?l?
Intel OTC