From mboxrd@z Thu Jan 1 00:00:00 1970 From: Salam Noureddine Subject: Re: Null pointer dereference in tg3_poll_work running linux-3.4 Date: Tue, 28 Mar 2017 15:12:43 -0700 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: Network Development , "michael.chan@broadcom.com" , "prashant.sreedharan@broadcom.com" , Siva Reddy Kallam To: Michael Chan Return-path: Received: from mail-vk0-f48.google.com ([209.85.213.48]:35188 "EHLO mail-vk0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932157AbdC1WMp (ORCPT ); Tue, 28 Mar 2017 18:12:45 -0400 Received: by mail-vk0-f48.google.com with SMTP id r69so105185095vke.2 for ; Tue, 28 Mar 2017 15:12:44 -0700 (PDT) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Tue, Mar 28, 2017 at 11:53 AM, Michael Chan wrote: > I don't remember any bug fixes related to this logic. One possibility > is that there is DMA corruption and we are getting a bad opaque value. > If you have the core dump, it will be useful to look at the receive > completion ring. These opaque values are simple index values and > should be in sequence. Unfortunately I don't have a core dump, this has happened around 5 times on boxes that have been up between 2 and 7 months. So it seems extremely rare. So far, the only information I have is the stack trace.