From: Francois Romieu <romieu@fr.zoreil.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: nic_swsd@realtek.com, netdev@vger.kernel.org
Subject: Re: r8169 OOPSen in rtl_rx
Date: Fri, 6 Sep 2013 01:09:30 +0200 [thread overview]
Message-ID: <20130905230930.GA25360@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <20130905152026.GB31370@twins.programming.kicks-ass.net>
Peter Zijlstra <peterz@infradead.org> :
[...]
> Yay, it triggered..
Bingo.
Can you display the whole descriptor entry (opts1 and opts2) and its
index (cur_rx) when abnormal packets are detected ?
We can always check the packet size but I'd welcome some more specific
pattern in the remaining bits of the descriptor.
Btw, you may try to revert aee77e4accbeb2c86b1d294cd84fec4a12dde3bd
("r8169: use unlimited DMA burst for TX") and see if it changes the
Rx / Tx balance. It would only be a bandaid though.
--
Ueimor
prev parent reply other threads:[~2013-09-05 23:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 9:43 r8169 OOPSen in rtl_rx Peter Zijlstra
2013-08-13 21:15 ` Francois Romieu
2013-08-14 9:29 ` Peter Zijlstra
2013-08-14 9:52 ` Peter Zijlstra
2013-09-05 15:20 ` Peter Zijlstra
2013-09-05 23:09 ` Francois Romieu [this message]
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=20130905230930.GA25360@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=peterz@infradead.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