All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: VDR User <user.vdr@gmail.com>
Cc: Alexander Duyck <alexander.h.duyck@linux.intel.com>,
	netdev@vger.kernel.org
Subject: Re: r8169 driver from kernel 5.0 crashing - napi_consume_skb
Date: Mon, 18 Mar 2019 19:36:56 +0100	[thread overview]
Message-ID: <b5313072-b814-82aa-043e-128021b77fec@gmail.com> (raw)
In-Reply-To: <CAA7C2qi9rbiM4KZBq6TorFyew83A1P3Hc2t_Af2Uaf4i7V+Z9g@mail.gmail.com>

On 18.03.2019 17:17, VDR User wrote:
> Just a quick check-in...  I was able to do a decent amount of testing
> yesterday after applying Heiner's patches that "removes an extra PCI
> register read in the
> interrupt handler" and adds some debug logging. So far I haven't seen
> any crashes, everything has been smooth. It may be worth noting that
> the last few crashes I saw occurred with less testing than I did
> yesterday. I'm not sure if luck is involved and will continue to test
> over the next few days unless otherwise instructed. Just wanted to
> keep you guys informed what I've seen so far.
> 
Thanks a lot for the feedback and your efforts! If the issue doesn't
occur again in the next days I'll submit the fix.

> Best regards,
> Derek
> 
Heiner

  reply	other threads:[~2019-03-18 18:37 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-10 19:02 r8169 driver from kernel 5.0 crashing VDR User
2019-03-10 19:35 ` Heiner Kallweit
2019-03-14  3:04   ` VDR User
2019-03-14  6:43     ` Heiner Kallweit
2019-03-14 15:10       ` VDR User
2019-03-14 18:08         ` Heiner Kallweit
2019-03-14 21:36           ` VDR User
2019-03-15 20:09             ` VDR User
2019-03-15 20:26               ` r8169 driver from kernel 5.0 crashing - napi_consume_skb Heiner Kallweit
2019-03-15 20:40                 ` Alexander Duyck
2019-03-15 20:46                   ` Heiner Kallweit
2019-03-15 22:09                     ` Alexander Duyck
2019-03-15 22:27                       ` Heiner Kallweit
     [not found]                         ` <b470f0ee6071bded8e78e15e18df14ffbc32cd18.camel@linux.intel.com>
2019-03-16  9:07                           ` Heiner Kallweit
2019-03-16 14:38                           ` VDR User
2019-03-16 15:10                             ` Heiner Kallweit
2019-03-16 17:08                               ` Alexander Duyck
2019-03-17  8:25                                 ` Heiner Kallweit
2019-03-17 11:35                             ` Heiner Kallweit
2019-03-17 15:23                               ` VDR User
2019-03-17 15:41                               ` VDR User
2019-03-17 15:49                                 ` Heiner Kallweit
2019-03-18 16:17                                   ` VDR User
2019-03-18 18:36                                     ` Heiner Kallweit [this message]
2019-03-21 19:35                                       ` VDR User
2019-03-22 19:03                                         ` Heiner Kallweit
2019-03-22 20:44                                           ` VDR User
2019-04-04 14:28                                             ` VDR User
2019-04-04 19:41                                               ` Heiner Kallweit
2019-04-04 22:11                                                 ` VDR User

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=b5313072-b814-82aa-043e-128021b77fec@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=alexander.h.duyck@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=user.vdr@gmail.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.