From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 199561] sungem: RX MAC fifo overflow smac[03910440]
Date: Sun, 05 Apr 2020 21:58:18 +0000 [thread overview]
Message-ID: <bug-199561-206035-NFE9cMszjH@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
----------------------------------------------------------------------------
Attachment #280931|0 |1
is obsolete| |
--- Comment #5 from Erhard F. (erhard_f@mailbox.org) ---
Created attachment 288223
--> https://bugzilla.kernel.org/attachment.cgi?id=288223&action=edit
dmesg (5.6.2, PowerMac G4 DP)
Still in recent kernels (5.6.2).
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-04-05 21:59 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 ` [Bug 199561] sungem: RX MAC fifo overflow smac[03910440] bugzilla-daemon
2020-04-05 21:58 ` bugzilla-daemon [this message]
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-NFE9cMszjH@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 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).