linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: r8169 only works in promisc mode
Date: Sun, 10 Mar 2019 15:26:16 +0100	[thread overview]
Message-ID: <2fbb9488-198f-0a9c-af3b-bb45bf424884@gmail.com> (raw)
In-Reply-To: <20190310071853.3c726dbc@shemminger-XPS-13-9360>

On 10.03.2019 15:18, Stephen Hemminger wrote:
> On Sat, 9 Mar 2019 10:33:40 +0100
> Heiner Kallweit <hkallweit1@gmail.com> wrote:
> 
>> On 09.03.2019 03:16, Alex Xu (Hello71) wrote:
>>> After suspending, my r8169 (not actually 8169, just that driver) only 
>>> receives packets when in promiscuous mode. I have tried disabling all 
>>> offload features except highdma [fixed], and it doesn't fix the issue.
>>>
>>> I am using torvalds/linux, compiled about two days ago (not sure which 
>>> commit). I think this happened after a recent upgrade (some time in the 
>>> past week). Given the long testing cycle, I don't really want to bisect; 
>>> I am hoping someone has some idea of where the issue could be.
>>>   
>> The provided information isn't enough to say anything. Please create a
>> bug ticket in bugzilla. Needed information:
>> - Last working and first failing kernel version (as reported by uname -a)
>> - Is 5.0 ok?
>> - Full dmesg log
>> - lspci -vv output for the network card
>> - If the issue happens only after resume from suspend, diff of the
>>   chip registers (ethtool -d) before and after suspend.
>> - Does removing / reloading the r8169 module fix the issue?
>>
>>> Please CC me on replies.
>>>
>>> Thanks,
>>> Alex.
>>>   
>> Heiner
> 
> Bugzilla is not really used by Linux network developers.
> I just filter/forward mail from bugzilla into netdev.
> 
To make sure I understand you correctly:
Are you just saying "network developers don't actively scan bugzilla"
or do you want to say that bugzilla shouldn't be used in general for
netdev bugs/issues? What would be the right tool then?

  reply	other threads:[~2019-03-10 14:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-09  2:16 r8169 only works in promisc mode Alex Xu (Hello71)
2019-03-09  9:33 ` Heiner Kallweit
2019-03-09 16:53   ` Alex Xu
2019-03-10 14:18   ` Stephen Hemminger
2019-03-10 14:26     ` Heiner Kallweit [this message]
2019-03-10 18:59       ` Stephen Hemminger
2019-03-19 13:48 ` Alan Cox
2019-03-23  1:26 ` Alex Xu

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=2fbb9488-198f-0a9c-af3b-bb45bf424884@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=alex_y_xu@yahoo.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    /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;
as well as URLs for NNTP newsgroup(s).