From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 199561] sungem: RX MAC fifo overflow smac[03910440]
Date: Mon, 21 Oct 2019 19:11:03 +0000 [thread overview]
Message-ID: <bug-199561-206035-wD5NoJCSo4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199561-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199561
Erhard F. (erhard_f@mailbox.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |linuxppc-dev@lists.ozlabs.o
| |rg
Hardware|PPC-64 |PPC-32
Kernel Version|4.19.19 |5.4-rc4
--- Comment #4 from Erhard F. (erhard_f@mailbox.org) ---
On 5.4-rc4 I am getting now:
[ 43.822417] sungem_phy: PHY ID: 2060e1, addr: 0
[ 43.831184] gem 0002:20:0f.0 enP2p32s15f0: Found BCM5421 PHY
[ 47.502223] gem 0002:20:0f.0 enP2p32s15f0: Link is up at 1000 Mbps,
full-duplex
[ 47.502697] gem 0002:20:0f.0 enP2p32s15f0: Pause is enabled (rxfifo: 10240
off: 7168 on: 5632)
[ 47.503173] IPv6: ADDRCONF(NETDEV_CHANGE): enP2p32s15f0: link becomes ready
[...]
[ 423.097905] gem 0002:20:0f.0 enP2p32s15f0: Memory squeeze, deferring packet
[ 423.125951] gem 0002:20:0f.0 enP2p32s15f0: Memory squeeze, deferring packet
[ 423.148828] gem 0002:20:0f.0 enP2p32s15f0: Memory squeeze, deferring packet
[ 423.156830] gem 0002:20:0f.0 enP2p32s15f0: RX MAC fifo overflow
smac[00910440]
[ 423.243823] gem 0002:20:0f.0 enP2p32s15f0: Memory squeeze, deferring packet
--
You are receiving this mail because:
You are on the CC list for the bug.
next parent reply other threads:[~2019-10-21 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-199561-206035@https.bugzilla.kernel.org/>
2019-10-21 19:11 ` bugzilla-daemon [this message]
2020-04-05 21:58 ` [Bug 199561] sungem: RX MAC fifo overflow smac[03910440] bugzilla-daemon
2020-04-05 22:00 ` bugzilla-daemon
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=bug-199561-206035-wD5NoJCSo4@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 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.